Hi, Brad
I know a little bit about this type of thing - my prior company was sold
to Tyco Electronics and I had to prepare this type of thing myself.
First thing to do is list ALL of your trading partners, contact names,
EDI ID and qualifier information, and transaction types. Also, all VAN
information such as mailboxes, logins, billing information and
transmission/reception schedules.
Second, get all of your Trading Partner specs together along with sample
data for each transaction.
Third, get accurate counts of volume both in and out - # of transactions
in per TP/transaction, # of each transaction, # of batches &
transmissions and byte count - daily/weekly/monthly if possible.
Fourth, document all current and ongoing problems and all new
implementations pending or in progress.
That should take you to where they will come back and ask you specific
information
Kelly Babcock
EDI/Messaging Architect
MedAssets.com
3755 Mansell Road
Suite 300
Alpharetta, GA 30022
Phone: 678-323-2542
Email: [EMAIL PROTECTED]
-----Original Message-----
From: Brad [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 27, 2000 12:25 PM
To: [EMAIL PROTECTED]
Subject: A little off subject but
Hi,
I have a problem well more like a series of problems that I am not sure
I can handle. I am not an EDI expert by any means (heck I am not a
programmer) but when I took on the job I have now EDI was not part of my
responsibilities nor did I ever say or imply I had any expertise in EDI.
I am a sys admin plus help desk plus hardware repair person for a small
company. AS you can gather I was put in a place where I needed to learn
by the shear fact there was no one else. So on to the problem the
company I am working for is being acquired by another company they are
an even bigger company than we are infact about twice our size, but they
have even less expertise with IT than my present company. I know nothing
about this new company except rumor and bits and pieces of things that
people have heard from other people. I am given to understand they use a
Unix system 10 years old and has not been updated (I have admin'ed a few
SCO systems in my day but in the past but my current tool set is five
years out of date on Unix based systems) We on the other hand use a MS
Windows NT/Novell system based network and Harbinger's TrustedLink/STX
windows product which seems to me to be a very good product for our
application. Well how can I put this it seems that I have been asked to
be the lead on integrating our systems. I have no information and I do
have some ideas on where to start but can any one on this list provide
some sort of EDI parameter check list. I figure I will be looking for a
different job in a short bit because of the way this new company does
their IT I get the impression its all out-sourced and besides their
based in New Jersey and I am a California boy myself. But I do not want
to leave my friends at my present job with a set of bad decisions on my
part which will cause them problems. I have more fear than I think I
need to but any help with check lists or ideas about areas or items I do
not want to overlook. I would appreciate any experience or insights the
list may have.
Brad Burns
[EMAIL PROTECTED]
ннннннннннннннннннннннни signoff the EDI-L list,
mailto:[EMAIL PROTECTED]
To subscribe, mailto:[EMAIL PROTECTED]
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
