Clickable Business Models eBusiness Education Acronyms Cross References
B2B Content Standards EC Technology Standards Glossary Implementation Guidelines
Implementation Options General Recommendations References Methodology/Legends
 Home | Copyright Notice and Legal Disclaimers | Navigation Help | Tour! | Downloads | Contact Us | Site Index | Search
Implementation Options | Technical Basics | Internet Commerce Model  | Architecture |
Implementation (Technology) Options

Implementation Option 5a (Buyer's Web Application) - How It Works:  Design Time  
 
Special Notes:    

 
    Initial Implementation
   Identify First Trading Partner
   Establish Trading Partner Agreement
   Requirements Definition
   Select Network Provider(s)
   Define User Interface
   Assess Requirements for Back-end Applications
   Implement Gateway Components
   Define Messaging (Transport and Routing) Requirements
    New Trading Partner, New Business Processes/New Business Process Document
Back to Implementation Option 5a Index

All the implementation steps here are on the buyer's side.  All the items listed in the Basics of Implementations:  Initial eBusiness Implementation are required, with exceptions noted below.  The assumption is that the majority of the trading partners are Small-to-Medium Enterprises (SMEs).  Again, the assumption on the buyer's side is that an existing legacy EDI infrastructure and back-end is being utilized.

The initial implementation of an internet gateway and buyer's web application from 2 to 6 months.

  1.  The first step, of course is to identify potential partners.   This is likely to be manual, since few SMEs participate in registry services.
  1. The trading partner agreement process is likely to be manual.  If the partner doesn't have back-end integration for business processes, it is unlikely that an investment has been made in automating the creation of TPAs.
  1. Assess requirements and develop implementation plan
  1. Develop maps needed to translate legacy EDI interface files to/from OAGI XML if   OAGI files are used as the interface file format for the web application.
  1. Identify network provider.
  1. Develop user interfaces for web application.
  1. Implement any changes needed to buyer's back-end integration.   There are two aspects of back-end integration for the web application.
  1. From the buyer's perspective, the web application has back-end integration functionality in that exchanges between the buyer's back-end application and the web application are automated
  2. From the supplier's perspective, limited integration may be supported if functionality is built into the web application to allow for downloading data in one or two standard file formats.  The application owner (buyer) will have to decide how many standard formats will be supported for downloads, and what the standards will be.  For example, the application owner may decide to make download files available in RosettaNet XML format, EDIFACT format (legacy EDI), and provide a proprietary file format as well.
  1. Evaluate, select and implement internet gateway components.
  1. Evaluate, select and implement communications methods.
    1. For the communication between the buyer's intranet gateway and extranet gateway, secure FTP - FTP with SSL, a/k/a SFTP - may be used.
    2. The web application may support HTTPS - HTTP with SSL - for secure supplier access.

The buyer owns the web application and is responsible for seeing that it supports the security requirements of Privacy, Authentication, Integrity (of the data) and Non-repudiation of origin and content.

  1. The web application may support HTTPS - HTTP with SSL - for secure supplier access.
For the remaining implementation steps, this implementation option does not have any differences than what is presented in the Basics of Implementations:  Initial eBusiness Implementation .

 


2.  New Trading Partner

All steps in the Basics of Implementations:  New Trading Partner implementations and Basics of Implementations:  New Business Process/New Business Document implementations apply to this implementation option, except, of course, with the differences mentioned above.  In summary, the differences are:


Last updated 02 March 2003