Scenario 61 - High Tech Logistics - Customer Operated Hub

61.0 Overview

Scenario #61 describes the integration for supplier party applications to integrate with transportation party (Carrier), distribution center party (Customer Hub) and customer party applications to accomplish a business model called a customer operated hub.

The purpose of this scenario is to enable the visualization of the participants in the process and the dialogs between them for this specific integration. This scenario is not meant to be the only model for integrating general ledger applications to a budget applications. This is simply one model that may be used to guide one’s own integration efforts.

61.1 Scenario Diagram

The scenario below contains the participants involved in the interaction, the dialog flows or conversation between them, certain assumptions about the sequence of events, and assumptions about the technical approach, for example, publish and subscribe.

This is a model to be used as a design recommendation, not a required approach.

61.2 Assumptions

This scenario assumes a loosely coupled, asynchronous approach with transaction management required but not explicitly defined.

It also presumes that this scenario can be applied as a B2B interaction between enterprises, as an internal A2A exchange within an enterprise or as an B2M exchange from a business to a mobile device following the same canonical business messaging model.

61.3 Participant Definitions

This scenario contains four participants or roles:

  • Supplier party
  • Transportation party (Carrier)
  • Distribution center party (Customer Hub)
  • Customer party

The definitions and details of these participants are left to the designer but are assumed to contain the functionality as defined by what is commonly sold in the commercial market place today. This definition is broadly accepted by the scenario designers and is a direct result of the decision not to define how the processing takes place within any individual application.

Each application must be able perform the services defined by the message BOD (business object document), but the internals of the application are not required or desired to be exposed at this level of standardized abstraction.

The most important factors in defining these participants is to ensure that an integration designer can communicate the requirements precisely enough to detail the interfaces needed and their interrelationships.

61.4 Business Workflow (Sequence)

The business workflow is graphically represented by starting at the Scenario top and reading from top down and from left to right.

This scenario contains the following events in the workflow sequence:

  1. Communicate a request to process an planning schedule to the supplier
  2. Indicate the acceptance or rejection of the proposed planning schedule
  3. Interact with events that may update a purchase order from the supplier
  4. Communicate a request to process a shipment to the transportation (Carrier)
  5. Indicate acceptance or rejection of the proposed shipment from the carrier
  6. Communicate the commercial invoice to the carrier
  7. Communicate a shippers letter of instruction to the carrier
  8. Communicate the approporiate export declaration to the carrier
  9. Communicate the hazardous material shipment document to the carrier
  10. Carrier then actually makes a pick up
  11. Communicate that the shipment is leaving from the supplier
  12. Communicate that the shipment is leaving from the supplier to the carrier
  13. Communicate information concerning the shipment unit to and from the distribution center (Customer Hub) and the supplier
  14. Communicate the receipt of the shipment from the carrier to the supplier
  15. Communicate a request to process an invoice to the customer from the supplier
  16. Indicate the acceptance or rejection of the invoice from the supplier
  17. Communicate that the customer has initiated the payment and how and when supplier can expect to receive payment.

61.5 Exception Handling

Exception handling is highly localized as the result of an implementation’s infrastructure, managment and business rules. As such, this section of the Scenario is planned to be used as a guide to help understand the additional intent of this Scenario designers. If no exceptions are noted here, then it can be assumed that the Scenario designers agreed that the Scenario is straight forward and has no additional neeeds:

  • Note that the Confirm BOD is not shown in the scenario and that it is the most obvious method for providing an application level exception and feedback mechanism between business software components. Full Confirm BOD use is described in other OAGIS documentation in detail, but it should be noted that the specific use of the Confirm BOD may vary significantly from scenario to scenario and from integration to integration.

The Confirm BOD is typically intended to be used by the recieving application to communicate to the sending application that the information it sent in the message BOD was received and understood and can be processed.

If the information was not received or not understood, or contained errors of any type, it is accepted practice for OAGIS to presume that the data was not acted on and in the abscense of a Confirm BOD within an agreed to time limit to resend. As errors and assumptions are the bane of any implementation, it is strongly recommended that the Confirm BOD be used to prevent this potential problem althought it is not a requirement by OAGIS.


OAGi and its members welcome your feedback.