WARNING: The Evaluation
mode of the Framework EDI component has the following restrictions:
Has a file size limitation of 3 KB.
Will parse only "test" EDI files indicated by a "T"
(X12) or "1" (UN/EDIFACT) in the control segment.
Has an expiration date and will stop functioning
in about 30 days.
If you wish to
obtain a serial number to remove the above
restrictions (except for the expiration date) simply email us for it,
or fill up the form at About EDIdEv LLC
and let us exchange company
information. Note that we will never share your email
and other information with
marketers outside EDIdEv.
The recommended minimum system requirement for Framework EDI:
256 MB RAM
1GB available disk space
Windows 2000/2003/2008/XP/Vista/7
Prerequisites: Some
systems may require Microsoft Redistributable Package to be installed first
to support:
A brief description of the Framework EDI component, and its utilities.
Product Evaluation Guideline
Since time can be an issue when evaluating a product, (which if not checked
can become very costly), we have not only provided a full
featured evaluation copy of Framework EDI, but also a guideline to assist users
during their evaluation.
One must have the basic knowledge and understanding of the product
before evaluating it to form an adequate expectation of the product. Some
points to determine are:
It is important to determine the kind of support you're getting during the
evaluation phase because it reflects and would inevitably be the kind of support you'll
receive after the purchase of the product.
When evaluating an EDI product, one must expect the basic functions
to be included (as part of the
features of the product) that are
essential for exchanging EDI files between one another. Basic features of an EDI product are:
The limitations of the product must be determined before purchasing it to
avoid future problems. The performance of the product must meet all
your present expectations. Also, one should try to be aware of the vendor's
vision and future plans of the product to compare if it is parallel to your
own, so that you can determine if your future requirements would be met.
5. Obtain sample EDI files, and their implementation guidelines from your trading partner.
6. Find the SEF file equivalent to
the implementation guideline of your trading partner from our website http://www.edidev.com/SEF.htm.
For example, if your trading partner's implementation guideline is based on the
850 4010 Transaction Set, then you should use an 850_4010.SEF file with the
FREDI component for processing their EDI files.
7. Load the SEF file into the SEF
Manager Utility and compare the rules in the SEF file with those of the implementation guideline
documentation that you received from your trading partner. You can make
the necessary changes to the SEF file with the SEF Manager so that it matches
with your trading partner's guideline. For more details, please read http://www.edidev.com/articles/createIG/HowToCreateIG.html.
8. Load your trading partner's sample EDI file into the eFilemanager Utility, and familiarize yourself with the EDI file structure (e.g. area,
data segments, data elements), and compare it with the SEF file as viewed in the
SEF Manager.
10. Finally, just dive in and get started. We offer remote
consulting/training sessions to help you with your project and train you at
the same time. For more details, please read http://www.edidev.com/edidev_sessions.htm.
Definition
EDIdEv Framework EDI is an EDI development tool that
includes an ActiveX / COM and application utilities to facilitate the development
of EDI systems. Return
Purpose
Framework EDI provides a set of commonly used, well tested functions for
processing EDI files to programmers so that more of their
programming time will be used in developing the business logic of their
application, and not spent on the tedious and complicated task of manipulating data to conform to the
rules and regulations of the EDI standard. Return
Requirements
One must be able to develop with a programming language that supports COM
components to fully utilize the Framework EDI software. We
also recommend that Framework EDI be installed in a computer with at least 256Mb RAM,
and a CPU speed of 1Ghz. Return
Cost
For programming development, one needs either the Professional license ($995) or the Enterprise
license ($2850). When
your programs are deployed, a Runtime License ($100) is required per
computer, or a Server/Site Runtime License ($450) per site. In addition,
you would need a SEF file for every type of Transaction Set/Message you will be
supporting. SEF file prices range from $30 to $90. Email support is
free, and there are no yearly fees. Return
Solution and niche of the product
In most companies (if not all) the responsibility of their EDI system is
designated to their IT (computer) department. Aware of this, we've
provided a product to empower IT programmers of managing EDI processing by
giving them the flexibility to create tailored yet robust EDI solutions that
directly tackle their company's EDI needs. Return
Documentation
Framework EDI includes a help documentation that explains its methods (functions) and
properties. Updates of this documentation can be downloaded at our
"Documentation Update" web page, which also includes PowerPoint
presentations to help users get started with Framework EDI. Return
Free Email
Support
We provide free email support to our customers as well as to users who are evaluating our product.
Email: support@edidev.com. You can
also reach us by phone if you have any inquiries (no support questions, please)
at our main line#: (818)
569-4542. Return
Sample Programs
To jump start some EDI projects, we've provided a variety of sample programs
that includes HIPAA, business, web applications etc. These sample programs
can be downloaded from our "Sample Programs" web pages. Return
SourceCodeMaker
In addition to the sample programs, we've provided the SourceCodeMaker tool that
will create the source code for either generating or translating an EDI
file that was provided to it. Return
Customer Support Web Page
When users buy Framework EDI, they will receive a UserID and password to login to our Customer Support
web page so that they can continue to download the latest updates of Framework EDI. Return
Supports X12 and
UN/EDIFACT standards
Framework EDI supports all versions and transaction sets (documents) of EDI ASC X12 and
UN/EDIFACT standards, including industrial versions (that follow X12 and EDIFACT) for example HIPAA and
VICS. This is achieved by the means of using an open
standard exchange format (SEF) file. These SEF files can be downloaded
from our "SEF Files" web page. If the SEF files you're looking
for are not available, we can create them for you. Return
Parse EDI files
Framework EDI components parses (translates) EDI files down to their data elements and exposes
their values through methods or properties of objects. Programmers
only need to map these values from the objects to database fields or any output
variables. Sample programs can be downloaded from our "Sample
Programs" web pages. Return
Constructs EDI files
Framework EDI components constructs (generates) EDI files. Programmers do not have to concern
themselves with manipulating data to create a correctly formatted EDI document
because the components does it automatically for them. They only need to map values
from their database fields or variables to the properties of the components' object.
Sample programs can be downloaded from our "Sample Programs" web
pages. Return
Acknowledging an EDI file
Functional acknowledgments 997 (X12) and Syntax Messages CONTRL (UN/EDIFACT) can automatically be created
by simply enabling a property of the Framework EDI component.
Sample programs can be downloaded from our "Sample Programs" web
pages. Return
Securing EDI files
Before sending EDI files to their destination, it is prudent to secure them to
keep the confidentiality and integrity of the message safe. Framework EDI supports
X12.58 Security Structures standard, and EDIINT AS2 for securing EDI files. Sample programs can be
downloaded from our "Security X12.58" and "AS2 EDIINT" web
pages. Return
Transmitting EDI files
Framework EDI provides various methods for sending and receiving EDI files over the Internet.
The file transport protocol supported are FTP, SMTP, HTTP, HTTPS and AS2. Return
Versions
Framework EDI can parse and construct all versions and transaction sets (documents) of EDI ASC X12 and
UN/EDIFACT standards. However, for the current version of Framework EDI, some
features are only supported for the X12 standard files. Please see
table: Return
Standards
Parse
Construct
Acknowledge
X12.58
EDIINT AS2
Transmit
ASC X12
Yes
Yes
Yes
Yes
Yes
Yes
UN/EDIFACT
Yes
Yes
Yes
No
Yes
Yes
Quantity of EDI files
There is no limit to the number of EDI files Framework EDI can parse or construct.
From our test, there is no degradation in performance that is related to the
number of EDI files. We do however recommend that when dealing with high
volumes of EDI files, the program should run on NT technology operating
systems e.g. NT4.0, Win2000, and WinXP. We have provided sample programs at our "Performance
Test" web page for you to download if you wish to test Framework EDI's performance on your own
machine. Return
Size of EDI files
With the cursor type of the Framework EDI component set to Forward, there is no
size limitation to an EDI file it can process. We have provided
sample programs at our Performance
Test web page (then scroll to the bottom) for you to download so that you can test
the component's performance on your own
machine.
Return
