ECGrid & ECGridOS EDI Communications Services:An Executive Briefing for CTO's and Product Mangers of B2B Systems, Software, and Platforms

By Alan D. Wilensky, ECGridOS Evangelistawilensky@ld.com(412) 353-9269Connection Architectures and Contract Models for B2B SoftwareOEMsin multi-model EDI Productsectors.

Executive Summary

This briefing will cover the essential issues facing Capital Line Software businesses contemplating a keytransition from

consumer

of EDI communications services, to

owner / operator

of their own EDI networkvia Loren Data Corp's

ECGrid

Network, and

ECGridOS

Web Services Network Management API.

Definitions:

ECGrid is a wholesale EDI Interconnect and message routing cluster. ECGrid hosts 18,000 native tradingpartner ID's, and has clear routes to dozens of electronic commerce service providers and Value AddedNetworks. ECGrid, in continuous operation since 2001, is owned and operated by Loren Data Corp, acompany founded in 1987. Many prestigious B2B service providers use ECGrid as their EDI carrier infrastructure of choice. More information about ECGrid can be found athttp://www.LD.com.ECGridOS is the Web Services (WSDL / SOAP) interface to ECGrid. Software developers can createcustom virtual EDI networks for integration in capital line systems (ERP, 3PL, VMI), and the newvanguard of B2B cloud commerce ventures can embed EDI communications in their platform.

Using ECGrid

ECGrid is accessed like other VANs, via FTP, AS2, and VPN. Administration is via a simple webinterface. ECGrid is the only VAN with a universal directory service. Companies that have traditionallybeen large users of in-house AS2 and FTP have found ECGrid an economical alternative.ECGridsupports any combinations of inbound connections, and large partner migrations are are a regular occurrence at ECGrid.All ECGrid accounts can be controlled via the API - the only difference is the connection protocol andmethod, and such methods may be freely mixed, with some sites and accounts dedicated to FTP, yetequally accessible via the API for reporting and account control, while other accounts may rely entirely onthe API for control and communications.ECGrid, used in its typical and robust standard connection model as a routing system, or as a private /hybridcommunications cluster, is a viable alternative to any VAN, regardless of market size or ostensiblereputation.

Using ECGridOS

Programmers use ECGridOS to build network operations functions into software and hosted platforms.Such Netops functions grant a developer operational control of a fully functional EDI Communicationsnetwork with the power to manage accounts, credentials, access, reporting, interconnections, all fromwithin your application's code.Furthermore, ECGridOS allows you to convey a Grant of Network Authorityto subordinate or Clientnetworks. OEM Software vendors may now, due to the flexibility of ECGridOS, accomplish the following:1) Run and Administer their own branded EDI Comms service with authority to control the subordinatemailboxes and QIDs.2) Grant autonomous Network Ops authority to their qualified customers, who may in turn fully administer their trading partners, inter-network relations, and special features.As ECGridOS is based on standard Web Services, communications and parcel transmission can all occur over a unified port 80 interface. This greatly reduces network support issues.

Account Models and Control Authority

The following graphic shows the ops hierarchy for an ECGrid Network accessed or created withECGridOS:

Your Product is The Primary Use Case-EDI Built in.

Companies that use retail EDI services viaValue Added Networksconfigure at least one communications

channel per application server installation. All traffic flows via FTP, AS2, etc. On-Demand businesses(SAAS, Cloud B2B) have large populations of segregated user communities that require even morenetwork controls - and configuration. Enhancing your platform's EDI network services repertoire, providesmore freedom and features for your users.Access to VANs is undifferentiated; even if multiple user ID's and credentials are configured, there is noconcept of messages belonging to any department, process, or user. All messages are identified via ISAAddress Segments, your sever or application code is used to 'de-funk' the message routing andownership. Furthermore, it is impossible to innovate any services, differentiate your product's EDIfeatures, or enhance exception handling in your native code.ECGridOS allows OEMs and On-Demand B2B operators to assert full authority over user access,themessage stream, and inter network operations. Software developers have come to expect control over allother IP network functions and messaging protocols, except EDI. The leading VANs have trained the B2Bcommunity to expect less, and they have mostly succeeded in lowering expectations, until now.Such was the rationale for creating ECGridOS. Now, all EDI communications functions are native to your code, and with your Network ID in hand,

Your Company is the VAN

. Once the EDI functions areintegrated, there are no more calls to the VAN for account configuration -admins and authorized usersmay enter account and administrative data to set up trading partners and communications.Applicationscommunicate as if using native IP message layers at the OS level with a rich palette of services that allowfor the continual evolution of your product over time.

Native EDI Communications Integration does not mean lack of administrative control or poor operational visibility

All of the functions normally reserved for a VANs legacy Net Ops is available to the software vendor or SAAS operator via centralized administrative interfaces that can be coded by your developers (usingLoren Data supplied sample code libraries), or as licensed, ready to use Data Center qualityadministrative control panels available from our partners (NetEDI).

Operations Model

Here are some of the ways our ECGridOS developers are using the API to make a difference inoperations:None of the following models are exclusive, they may be freely combined, changed on the fly in software,or new models can be innovated bysmart people.1)

EDI Code built in to the Application - Outsourced Account Support

The end users administer trading partner set up via the application's UI. The best ECGridOS user facingadmin UI's hide the gory details and users find it easy to add trading partners, see message status, etc.Netops support for account level issue resolution may be provided by Loren Data or its Partners. Thevendor need not staff a supervisory console, as failures can trigger automated email to designatedsupport staff.2)

Your Company's VAN Ops

In addition to native code integration, Your Company can create or license a full Net Ops suite andservice its application users for account level services.Beyond support, your developers can add billing,reports, etc.