|
LTL PICKUP NOTIFICATION v. 2.0.2 |
|
|
|
|
|
Problem
Statement |
|
|
A simple XML message is needed to
satisfy notification to the Carrier from the Shipper, Consignee or 3rd
Party that a shipment is available for pick up.
|
|
|
Audience |
|
|
This work was initiated through the BRG Deliver and is
intended for North American Motor 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
|
|
|
A standard pickup notification for
LTL would provide the North American
Motor Freight industry an alternative electronic means of communicating advance
pickup information to the Carrier from the Shipper, Consignee or 3rd
Party that a shipment is available for pickup.
Less Than Truckload Pickup Notification is
a process by which a record is created that documents the Goods that were
collected for shipments.
|
|
|
Business
Transaction Use Case
Diagram |
|
|
|
|
|
|
|
|
Use Case
Description
|
|
|
|
Use Case ID
|
UC-1
|
|
Use Case Name
|
Notify for pickup |
|
Use
Case Description
|
A standard pickup notification for LTL would provide the North American Motor
Freight industry an alternative electronic means of communicating advance
pickup information to the Carrier from the Shipper, Consignee or 3rd
Party that a shipment is available for pickup. |
|
Actors (Goal)
|
There are three actors in this process, the Carrier,
Shipper, and Consignee with another possible actor named 3rd
Party. Actors can be people or systems
acting upon the use case or connected to it in some way. A use case is generally a representation of
actions in a given system (such as pickup notification) that produces an end
value. |
|
Performance Goals
|
None
|
|
Preconditions
|
The trading partners (that utilize carriers) must have
completed all planning and have a signed agreement in place.
|
| Post
conditions
|
The Seller receives an item, order or request for
payment message using payment terms extension and sends an acknowledgement as
receipt of the message to the buyer or seller depending on the transaction. |
|
Scenario
|
Begins when goods are ready and/or scheduled to be picked up.
- Goods ready and/or scheduled to be picked up.
- Shipper, Consignee or 3rd Party notifies Carrier for pickup
- Carrier receives notification for pickup
Ends when... the Consignee, Shipper, or 3rd Party
receives the Acknowledgment Message from the Carrier (The acknowledgment is
indicated as the end-state but is optional).
The acknowledgment is considered a process unto itself and is utilized
by this process and others. Acknowledgment will be addressed in another BRD
|
|
Alternative Scenario
|
None
|
|
Related Requirements
|
None
|
|
Related Rules
|
None |
|
|
|
|
|
|
Business
Transaction Activity Diagram
|
|
|
|
|
|
Business
Transaction Sequence Diagram |
|
|
|
|
|
Code Lists |
|
|
TOP
|
|
|
|
|
