E5 2000 Kickoff

1
E5 2000 Kickoff

• Presented by
• Gary M. Morin
• BCE Emergis Co-Chair Message Routing WG

2
What is E-5 2000

• A way to reliably and securely send documents
  from one trading partner to another over the ANX
  or the Internet.
• A major revision of the AIAGs Guideline for
  Electronic Commerce Routing Over TCP/IP Networks
  (Document number E-5)

3
The E-5 Story

• In 1996, when we began talking seriously about
  ANX we realized that we needed a common way to
  send EDI and other EC documents across this or
  other TCP/IP based networks.
• We investigated numerous alternatives both open
  and proprietary.
• Settled on a variant of the Gas Industry Standard
  based on HTTP, the Web protocol.

4
E-5 Requirements

• Reliable
• Secure
• Scaleable
• OEMs at 1 billion transactions/yr
• Tier 1s at 100,000 transactions/yr
• Tier N at 12 transactions/yr
• Open

5
Reliable

• The fastest way to get your company in trouble
  with its customers is to drop some EDI
  transactions!
• The TPs need to know immediately if the
  transaction failed.

6
Secure

• We have the IPSec security for ANX based
  transactions.
• We needed a secure method for Public network
  (Internet) transactions.
• E-5 and E-5 2000 work with SSL

7
Scaleable

• We have some of the biggest and the smallest
  companies in the world, (and everything in
  between) that need to interoperate.
• Conversion is going to be a real pain. We need
  to make it as easy as possible!

8
Open

• Cant be tied to any particular vendors
  approach, there are just to many trading
  partners.
• Must be deployable on any platform.
• Standard Off the shelf parts.

9
GISB Standard

• Based on HTTP, the protocol used for the World
  Wide Web.
• Sends back immediate delivery status.
• Uses MIME to wrap or envelope the data with
  routing information.
• Uses RFC 1867 Form data to upload.
• Uses PGP Pretty Good Privacy to encrypt
  documents.
• Approximately 500 organizations using today.

10
AIAG E-5

• GISB minus the PGP.
• Allows for SSL security on the Internet.
• Demonstrated at AutoTech 1997.
• Approved by AIAG BOD in March 1998.
• First commercial products available AutoTech
  1999.
• Installed base today about 1000. Mostly inside
  the Harbinger network.

11
E-5 Behaviors

• Deliver
• Sends a document to a TP
• Obtain
• Picks up a document from a TP
• Retrieve
• Picks up a document (requeue)
• List
• Lists the contents of a mailbox
• Exit

12
E-5 Overview
Client
Server
Server
Client
Client
EDIApp.
EDIApp.
13
PushMe - PullYou

• If both parties have E-5 servers and automated
  clients then you never need to go to an EDI mail
  box ever again!
• Obtain and Retrieve functions exist for small
  mail box applications.
• We continue to map to the AIAG M-3 and M-5
  Business Processes.

14
Why E-5 2000

• There is Open and there is Open.
• Forced all forms to be the same
• Why make silicon life forms act like carbon life
  forms?

15
Changes in E-5 2000

• Separate Silicon (machine) and Carbon (human)
  interfaces. (Faster)
• Single post to logon and to transfer data in
  Silicon . (Faster)
• Basic Authentication security (Standards)
• XML based routing elements (Standards)
• TP Callable API (Flexibility, Implementation)

16
Separate Interfaces

• Machines dont need all of the interactive help
  so why make them go through the extra steps?
• You must have a human interface but we dont
  specify what it looks like.
• No specific human interface is specified so go
  knock yourself out.

17
Single logon/post

• Sends the logon and the data in one package.
• Each E-5 behavior has its own URL
• Allows stateless operation so it is easy to
  implement a High Availability solution.

18
Basic Authentication

• Standards based HTTP logon.
• Supported by all of the big Web servers.
• We can move to a PKI when one is available and
  eliminate usernames and passwords.

19
XML based Routing Elements

• Routing data is in XML format.
• Easier to parse out the Information.
• Easy to move to the next step, XML based EDI.

20
TP Callable API

• Have my server call your server.
• Finally, a first cut at a callable
  implementation guide.
• Results sent back are in XML format
• Built in loop back to validate the setup.
• A logical next step, the call to a directory
  service (LDAP).

21
E-5 Stack Example
HTTP Headers
MIME Boundary
XML (routing info)
Deliver Request
MIME Boundary
EDI/Data
MIME Boundary End
Follows RFC 1867 Form-based File Upload
22
XML

• DTDs for all XML documents are included in the
  specification.
• Adds tremendous flexibility in specifying EC
  documents and how they are to be routed.
• Provides us with some protocol independence.
  (SMTP, FTP, OFTP could now be used but there is
  no specification yet)

23
Example XML
lt?xml version1.0 encodingUTF-8
standaloneno ?gtlt!DOCTYPE E5_V20_Deliver_Submit
SYSTEM E5_V20_Deliver_Submit.dtdgtltfromgt1
23456lt/fromgtlttogt56789lt/togtltdocumentDescriptiongtR
elease 05/09/2000 lt/documentDescriptiongt
ltmimeTypegtapplication/EDI-X12 lt/mimeTypegt
ltsubSubMimeTypegt862 lt/subSubMimeTypegt
ltapplicationgtEDIGENlt/applicationgtltdocumentRefere
nceNumbergt12345 lt/documentReferenceNumbergtlt/E5_V2
0_Deliver_Submitgt
24
EDI/Data Package

• This can be literally any kind of electronic
  package not just EDI.
• Much of the testing was done with MP3 music
  files.
• We support any MIME type so files can be zipped
  to reduce their size.

25
Other Stuff

• Standardized status messages.
• Date and Time specifications.
• Information about Date and Time Services.
• Sample Directory Schema.
• Lets you know who and where to call.
• Silicon interface has a Human form used for
  testing purposes.

26
Current Status

• E-5 2000 was approved by the AIAG Board of
  Directory in March 2000.
• AIAG Document publication is imminent.
• Two organizations Michigan Blue Cross/ Blue
  Shield and Beaumont Hospital have agreed to pilot
  their X12 270-271 insurance verification process
  on V2000 starting this May over the ANX

27
The Future

• Presented to ebXML for consideration as the
  standard transport.
• BCBS Beaumont Testing in May 2000

28
Questions

• www.aiag.org
• www.efive.com
• Why E-5 document