EDI layered architecture

 EDI layered architecture

  1. Semantic (or application) layer
  2. Standards translation layer
  3. Packing (or transport) layer
  4. Physical network infrastructure layer



EDI semantic layer:

  • Describes the business application
  • Procurement example
    - Requests for quotes
      - Price quotes
        - Purchase orders
          - Acknowledgments
            - Invoices

            • Specific to company & software used


            EDI Standard layer(Standards translation):

            • Specifies business form structure so that information can be exchanged
            • Two competing standards:- 

            1. The ANSI ASC X12 Standards 

            • The X12 standard defined a set of documents, which are referred to as transaction sets. • The common documents and their corresponding transaction set numbers: 850 P.O, 810 Invoice, 855 P.O. Ack., 856 Ship Notice 

            2. EDIFACT Standards 

            • A combination of the ASC X12 standards and the Trade Data Interchange (TDI) standards developed in the United Kingdom and used throughout Europe.

               

            2) EDI transport layer

            • How the business form is sent, e.g. post, UPS, fax
            • Increasingly, e-mail is the carrier
            • Differentiating EDI from e-mail

            1. Emphasis on automation
            2. EDI has certain legal status


            3) Physical network infrastructure layer

            Dial-up lines, Internet, a value-added network, etc.


            Comments

            Popular posts from this blog

            Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?

            Suppose that a data warehouse consists of the four dimensions; date, spectator, location, and game, and the two measures, count and charge, where charge is the fee that a spectator pays when watching a game on a given date. Spectators may be students, adults, or seniors, with each category having its own charge rate. a) Draw a star schema diagram for the data b) Starting with the base cuboid [date; spectator; location; game], what specific OLAP operations should perform in order to list the total charge paid by student spectators at GM Place in 2004?

            Discuss classification or taxonomy of virtualization at different levels.