|
CARRIER ROUTING INSTRUCTION v. 2.0.2 |
|
|
|
|
|
Problem
Statement |
|
|
Foundational
messages are needed to electronically pass transportation routing instructions
similar to the paper based VICS Routing Guide standard. The messages consist of a buyer’s carrier
routing instructions and buyer’s party cross reference (Store, Distribution
Centre, Department) to the seller.
Current
Situation
- Buyer provides predefined
carrier routing instructions to the seller.
This is used to determine ship to and carrier and or service level. Buyer also provides the party cross
reference.
- Standards do not exist
for deployment, change notification, or basic format of a transportation routing
instruction, and this leads to manual process by seller.
- The current process does
not enable sellers to ensure consistent compliance with buyer’s requirements,
which leads to unnecessary costs for all parties, misdirected shipments and
needless delays in moving product to the buyer.
- Typically,
transportation routing instructions are embedded within a buyer’s vendor
compliance manual, which is a primary source of information about the rules of
engagement between buyer and seller.
·
|
|
|
Objective |
|
|
The objective is to create a business message standard to develop
transactional messages to communicate a buyer’s carrier routing instructions in
a static routing guide environment.
Static routing guide is defined as a document or message that contains
routing instructions which remain constant for a specific period of time.
The objective excludes, the framework for a central routing guide
repository, party cross reference, and a standard change management process.
|
|
|
Audience |
|
|
The audience of the standards would be any participant in the global
supply chain management. This would
include carriers, and their customers and partners
|
|
|
Business
Context
|
|
|
Industry:
All
Geopolitical: All
Product:
All
Process: Deliver
System
Capabilities: EAN.UCC
Official
Constraints: None
|
|
|
Business
Transaction View
|
|
|
|
|
|
Business
Transaction Use Case
Diagram |
|
|
|
|
|
Use Case
Description
|
|
|
| Use
Case Name: |
Exchange Transportation Routing Instructions
|
| Use
Case Description: |
None |
| Actors
(Goal): |
Buyer: Owner
and publisher of the transportation routing instructions.
Seller: Complies with the transportation routing instructions
|
| Performance
Goals: |
None
|
| Preconditions:
|
The buyer:
- Needs to have carrier
routing instructions and party cross-reference.
- Should have the ability to
electronically transmit carrier routing instructions and party cross reference.
- Should maintain an archive
of the carrier routing instructions and party cross reference. It is best practice for the new carrier
routing instructions to entirely replace the previous carrier routing instructions.
The seller:
- Should have the ability to
receive and support electronic carrier routing instructions, and party cross
reference.
- Should maintain an archive of the carrier routing
instructions and party cross reference.
It is best practice for the new carrier routing instructions to entirely
replace the previous carrier routing instructions.
|
| Postconditions: |
A successful implementation results in a seller receiving and the
implementation of the buyer’s transportation routing instructions.
A
failed condition results if the seller is not able to either receive and implement
a buyer’s transportation routing instructions.
|
| Scenario: |
Begins when Buyer: Extract the routing guide information from their
internal system
Continues with...
|
Step #
|
Actor
|
Activity Step
|
|
1
|
Buyer
|
Translates
the routing guide information into the carrier routing instruction message format
|
|
2
|
Buyer
|
Transmits
the carrier routing instruction to seller
|
|
3
|
Seller
|
Receives
the carrier routing instruction
|
|
4
|
Seller
|
Translates
the carrier routing instruction to their internal system
|
Ends
when Seller: Loads
the carrier routing instructions to their internal system
|
Alternative
Scenario:
|
None |
Related
Requirements:
|
N/A
|
Related
Rules:
|
N/A
|
|
|
|
Business
Transaction Activity Diagram |
|
|
Not available |
|
|
|
|
|
Business
Transaction Sequence Diagram |
|
|
Not available |
|
|
|
|
|
TOP
|
|
|
|
|
