Electronic data interchange (EDI)

Summary

The lecture explains how businesses exchange data across different information systems, focusing on traditional Electronic Data Interchange (EDI), internet-based EDI, and XML.

Interoperability Challenges

Connecting software directly at the object level using remote procedure calls (RPCs) can be difficult across organizational networks. It may require knowledge of another system’s software and can be complicated by proxies and address translation. Data-exchange standards allow organizations to exchange information without needing to know how each other’s systems work internally.

Why Data Standards Are Needed

Organizations may store information in different structures. Even a shared field name can have different meanings—for example, “price” may include or exclude tax. Standards aim to reduce these structural and semantic differences.

EDI Basics

EDI is the standardized electronic exchange of business documents, such as purchase orders. A typical process includes:

1. Preparing a document.
2. Translating it into an EDI format.
3. Transmitting it.
4. Translating it at the receiving end.
5. Processing it.

The goal is to avoid manual re-entry, which can be slow and error-prone. EDI documents may look cryptic to people, but they are structured for software to interpret.

Standards and Compatibility

Trading partners must use compatible standards. The lecture mentions ANSI X12, UN/EDIFACT, and industry-specific standards. Organizations often need to coordinate on a common standard across a group of trading partners.

EDI Networks

Partners can connect directly or use a value-added network (VAN) as an intermediary. A VAN can route transactions, retransmit documents, provide audit information, and support different communication methods.

Direct connections may suit large companies, while a VAN is operated by a third party for a fee.

Internet-Based EDI

The basic EDI concept remains the same over the internet, although transmission standards differ. The lecture names AS1, AS2, AS3, and AS4, and notes that AS3 uses FTP.

Implementation Costs

EDI adoption can involve costs for:

• Translation software and maintenance
• Internal integration work
• Hardware and networking
• Staff and vendor training
• Additional resources or specialized equipment
• VAN fees
• Legal agreements
• Consulting

XML as an Alternative

XML is presented as a flexible markup language from which industry or partner standards can be created. Database information can be converted into XML, transmitted, and read by an XML parser at the receiving end.

XML uses tags to pair field names with values and can represent hierarchical data, such as customers, orders, and order items.

EDI and XML Compared

XML is described as human- and machine-readable, platform-independent, Unicode-capable, and suited to structured and hierarchical data. It is generally more verbose and may require partners to establish or agree on standards.

Traditional EDI is established and trusted, and can be compact and efficient. However, it is less readable and can be costly to implement.

The lecture also mentions RosettaNet, an XML-based industry standard used by many electronics and computer companies.

Guides, Reviews, or Tutorials

This is an instructional lecture, not a product review. It covers EDI concepts, a purchase-order exchange example, network models, implementation costs, and XML’s role. It does not provide a separate step-by-step software tutorial.

Main Speaker and Source

An unidentified lecturer presents the course lecture. The video source/channel is E-business.