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
 Product Identification | Partner/Location IDs | Doc/Reference IDs | Dates | Other Best Practices |
EIDX General Supporting Documentation
Status:  Provisional draft.  Adapted from previous published version (Balloted and Ratified by Membership, June 1997)

Business Best Practices


Contents

See also


Assumptions

Unless otherwise stated, EIDX Business Models and Scenarios are based on an assumption that the parties involved have a pre-established relationship, and exchanges are for products that are purchased repetitively.  The following types of information have been exchanged in advance: 

  • Product information
    • Buyer's part number
    • Part revision or engineering change number
    • Seller's part number
    • 3rd party's part number (if applicable)
    • Other relevant part numbers (e.g. UPC)
    • Customs article number (if applicable)
    • Relevant product specifications
  • Partner Identification information
    • Sender/Receiver IDs
    • Addresses cross-referenced to address codes
    • Identification of3rd parties
    • Global Terms and Conditions (between Trading Partners) - terms that apply to all purchase orders; may be overridden on individual purchase orders.  See Terms and Conditions Agreement in Best Practices.
    • Established pricing (quote, catalog, or contract)
    • Tax Identification Number (e.g. resale or VAT number)
    • Default shipping instructions (carriers, modes, service levels)

Assumptions are also made about what events may or may not have preceded others:

  • Orders
    • The purchase order process has been preceded with a quoting or contracting cycle.  The buyer may send planning forecast to seller.  (Optional - depends on which Replenishment Scenario is being used).
  • Consignment:
    • Normally, a supplier is not going to consign inventory to a new, relatively unknown trading partner.  We assume that consignment process has been preceded with negotiation and establishment of a Trading Partner Agreement covering the terms and liabilities of the relationship.
  • Financial:
    • Account information, such as bank identifier and account number

Terms and Conditions Agreements

Terms and Conditions Agreement - Describes agreed general terms of doing business, regardless of whether the business is conducted electronically or manually.  To achieve efficiency in processing, any information that is static, or is to be applied across all transactions/messages exchanged between trading partners, e.g., orders and forecasts, should be covered in a Terms and Conditions agreement or other applicable type of contract.  The TCA is not to be confused with a Trading Partner Agreement (TPA), which governs electronic messaging.  See also Collaboration Protocol Agreement.

Types of information to be covered in a TCA may include:

    • FOB instructions
    • Pricing schedules
    • Terms of sale
    • Lead time
    • Authorization and liability clauses
    • Quality and warranty clause
    • Confidentiality clause
    • General ship/delivery requirements (e.g., anti-static packaging, etc.)
    • Default paperwork requirements (e.g. Certificates of Conformance, etc.)
    • Import/export requirements
    • Cancellation clause
    • Supplier-managed inventory terms
    • Length of commitment (effective and expiration dates)
    • Terms for when standard lead times do or don't apply
    • Primacy clauses (what takes precedence if two agreements have conflicting terms)

The TCA is then referenced in the electronic transaction/message, and only information which is specific to the individual transaction/message needs to be processed by the trading partners. This eliminates the need to transmit a lot of redundant data with each individual transaction/message.

Types of data usually specified on individual transactions/messages may include:

    • Reference to Terms and Conditions Agreement (TCA)
    • Effective and expiration dates (if not specified in TCA)
    • Item unit price (for systems requirements or information if price is per TCA)
    • Total quantity or total value amount (e.g. total dollar amount) authorized
    • Rates (not-to-exceed amount per month, if applicable)
    • Supersedes (previous order number, previous revision, etc., if applicable)

Trading Partner Agreements

Trading Partner Agreement (TPA) - Agreement between trading partners that defines agreed Electronic Commerce interactions and communication procedures, such as transport protocols and the business processes, business messages and standards that will be used.  A Trading Partner Agreement may be created electronically by computing the intersection of two partners' Trading Partner Profiles.  See also Terms and Conditions Agreement, Collaboration Protocol Agreement.

Types of information to be covered in a TPA may include:

  • Information about the trading partners
    • Electronic identification
    • Electronic addresses
    • Contact names
    • Role definitions
  • Information needed for electronic trading
    • URIs used for electronic communications
    • Default business process protocols
    • Communications protocols
      • e.g. use of VAN protocols and/or internet protocols
      • Security protocols, including defining methods for privacy, authentication, data integrity assurance, and non-repudiation, including requirements for encryption and electronic signatures
    • Descriptions for interpreting business processes that are expressed in machine-readable form, including default message flows between the invoker and the service provider, responsiveness, failure handling, and other attributes.
  • Information about the documents and data being exchanged
    • Description of data formats used
    • Default interpretations of data fields (to avoid ambiguity)
  • Business terms that apply to electronic trading
    • Which partner pays for which parts of exchanges
      • e.g. whether both partners pay network charges or only one partner bears the cost
    • Handling of disputes, termination of the TPA, and other exception conditions.
    • Default implementation process, including requirements for testing prior to engaging in production exchanges.
    • Relationship between the TPA and the TCA and which takes precedence in the case of conflicting terms; this is not usually contained in the TCA, because a TCA exists even when no TPA exists, i.e. when all messaging is manual.

 

 

 

Last updated 06 February 2003