Carrier (CA)

DCSA Repository / Glossary of Terms / DCSA Glossary of Terms / All terms / Carrier (CA)

Project:

Carrier (CA) : Public <<ArchiMate_BusinessActor>> BusinessActor

Created:	6/7/2023 4:37:18 AM
Modified:	12/20/2024 10:42:05 AM
Author:	DCSA
Version:	2024.4

Project:
Author:	DCSA
Version:	2024.4
Phase:	1.0
Status:	Published
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{08652528-8383-4742-A627-40C395F4B555}
Appears In:	Carrier, Booking - Conceptual Model, Shipment - Conceptual Model, Transport - Conceptual Model, Arrival Notice Simple CM, Involved Parties and Locations - Conceptual Model, Customs CM, Arrival Notice CM - LDM Mapping, Transport Document CM - LDM Mapping, Actors / Element Type Mapping, Transport Document - Conceptual Model, Transport - Conceptual Model, Arrival Notice Extended CM, Overview, Bill of Lading (B/L), Trade Formal Documents, Vessel - Conceptual Model, Business Glossary, [DRAFT] Commercial Schedules CM - LDM Mapping, Vessel Journey LDM (Trial based on existing classes)., Arrival Notice Conceptual Model, Arrival Notice Stakeholder Conceptual Model, Booking - Conceptual Model, Booking Stakeholders - Conceptual Model DRAFT, Transport Roles - Foundation Model, SK - Carrier - Logical Data Model, WIP - Vessel - Logical Data Model, CREATE LOADLIST, eBL Possession - Conceptual Model, WIP - CS - New Terms - Conceptual Models, CS - Stakeholder Model, Vessel schedule - Conceptual Model, Booking 2.0.0 and Bill of Lading 3.0.0 - State Transition Conceptual Model CM, eBL Business Rules - Business Rule Model, eBL Possession - Conceptual Model - GM Adjustments, CS - Point to Point - Sequence Model, CS - Generic Commercial Schedule - Sequence Diagram, Transport Plan - Conceptual Model, Previous - eBL Possession - State Transistion Model CM, Issuance Request - Conceptual Model DRAFT, MAP - Transport Document - Mapping Model, Issuance API - Conceptual Model DRAFT, PINT API - Conceptual Model DRAFT, JIT - Stakeholder - Conceptual Model, Shipper Internal System DRAFT, Booking 2.0.0 and Bill of Lading - Transport Document - Information Sources - Conceptual Model, Publish Draft Transport Document - Conceptual Model, Booking API - Conceptual Model REVIEW, Scenario - Issue to Issue Party To Party Platform - Sequence Model DRAFT, Scenario - Issue to Issue Party To Party on Different Platform - Happy Flows - Sequence Model DRAFT, Scenario - Issue to Issue Party To Party on Different Platform - Unhappy Flows - Sequence Model DRAFT, JIT2.0.0 Application Components and APIs - Conceptual Model, Booking 2.0.0 - Generic - Sequence Model, Booking 2.0.0 - Poll Notifications - Sequence Model, Booking 2.0.0 - Send to all subscribers / Full Push Notifcations - Sequence Model, Booking 2.0.0 - Lightweight Notification - Sequence Model, Booking 2.0.0 - Use Case 3 Submit updated Booking Request - Sequence Model, Booking 2.0.0 - Use Case 1 Submit Booking Request - Sequence Model, Booking 2.0.0 - Use Case 5 Confirm Booking Request - Sequence Model, Booking 2.0.0 - Use Case 7 Request amendment to Confirmed Booking - Sequence Model, Booking 2.0.0 - Use Case 8 Process Amendment to Confirmed Booking - Sequence Model, eBL 3.0.0 - Use Case 1 Submit Shipping Instructions - Sequence Model, eBL 3.0.0 - Use Case 6 Publish Draft Transport Document - Sequence Model, eBL 3.0.0 - Use Case Shipper downloads copy of Transport Document - Sequence Model, eBL 3.0.0 - Use Case 7 Approve Draft Transport Document - Sequence Model, eBL 3.0.0 - Use Case 8 Issue Transport Document - Sequence Model, eBL 3.0.0 - Use Case 9 Request surrender Transport Document (Amendment) - Sequence Model, eBL 3.0.0 - Use Case 10 Process Transport Document surrender request (amendment)] - Sequence Model, eBL 3.0.0 - Use Case 11 Void original Transport Document and issue amended Transport Document - Sequence Model, eBL 3.0.0 - Use Case 12 Request surrender Transport Document (delivery) - Sequence Model, eBL 3.0.0 - Use Case 13 Process Transport Document surrender request (delivery) - Sequence Model, eBL 3.0.0 - Use Case 3 Submit updated Shipping Instructions - Sequence Model, eBL 3.0.0 - Use Case 2 Request to Update Shipping Instructions - Sequence Model, eBL 3.0.0 - Use Case 4 Process updated Shipping Instructions - Sequence Model, eBL 3.0.0 - Use Case 5 Cancel update to Shipping Instructions - Sequence Model, Booking 2.0.0 - Use Case 4 Reject Booking Request - Sequence Model, Booking 2.0.0 - Use Case 6 Request to amend Confirmed Booking - Sequence Model, Booking 2.0.0 - Use Case 9 Cancel Amendment to Confirmed Booking - Sequence Model, Booking 2.0.0 - Use Case 10 Decline Booking by Carrier - Sequence Model, Booking 2.0.0 - Use Case 11 Cancel Booking by Shipper - Sequence Model, Booking 2.0.0 - Use Case 12 Confirm Booking Completed - Sequence Model, Booking 2.0.0 - Use Case 2 Request to update Booking Request - Sequence Model, Booking 2.0.0 - Use Case 13 Cancel confirm Booking Completed by Shipper- Sequence Model, Booking 2.0.0 - Use Case 14 Process Booking cancellation - Sequence Model, Booking 2.0.0 - Use Cases Overview - Use Case Model, eBL 3.0.0 - Send to all subscribers (SI) / Full Push Notifications - Sequence Model, eBL 3.0.0 - Send to all subscribers (TD) / Full Push Notifications - Sequence Model, Booking 2.0.0 and Bill of Lading 3.0.0 - Conceptual Model - WIP, eBL 3.0.0 - Use Case Overview - Use Case Model, Business Rules Carriers - Business Rules Model, eBL 3.0.0 - SI Poll Notifications - Sequence Model, eBL 3.0.0 - TD Poll Notifications - Sequence Model, eBL 3.0.0 - SI Lightweight Notification - Sequence Model, eBL 3.0.0 - TD Lightweight Notification - Sequence Model

Carrier means any person, organization or government undertaking the transport of goods by any means of transport.<br/>

Attributes
Operations
Associations To
Associations From
Messages To
Messages From
Advanced
Other Links

Attribute	Scope	Type
Is successfully issued	Private	int

Operation

Public
Provide Port Call Service () : void

Details:

[ Is static False. Is abstract False. Is return array False. Is query False. Is synchronized False. ]

Public
Validate and/or Update Booking () : void

Details:

[ Is static False. Is abstract False. Is return array False. Is query False. Is synchronized False. ]

Element	Source Role	Target Role
«ArchiMate_BusinessProcess» Publish Draft Transport Document BusinessProcess «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Update Draft Transport Document (by Carrier) Activity «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Hand over TD for Issuance of eBL BusinessProcess «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Reject Approved Transport Document BusinessProcess «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessEvent» Arrival notice BusinessEvent «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_Contract» Container Release Order (CRO) Contract «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Approve Draft Transport Document on Departure Activity «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessObject» Carrier booking number BusinessObject «ArchiMate_Composition»	Name:	Name:
Details:
«ArchiMate_Resource» Vessel (VSL) Resource «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Void and Reissue Transport Document BusinessProcess «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Commercial Vessel-related Scheduling BusinessProcess «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» CREATE LOADLIST BusinessProcess «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_Contract» Carrier clauses Contract «ArchiMate_Composition»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Publish Approved Transport Document BusinessProcess «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Carrier haulage BusinessProcess «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Service BusinessProcess «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Transport BusinessProcess «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_Contract» CONTRACT OF CARRIAGE BY SEA Contract «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_Contract» Draft B/L Contract «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessActor» Carriers Agent at Destination BusinessActor «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_ApplicationComponent» Carrier Internal System ApplicationComponent «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_Contract» Commercial (Vessel) Schedule Contract «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessEvent» Draft Transport Document Published BusinessEvent «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessActor» Transport document issuer BusinessActor «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Voyage BusinessProcess «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_Contract» Haulage requirements Contract «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_Contract» Master B/L Contract «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Create Transport Document BusinessProcess «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_Contract» Customs manifest Contract «ArchiMate_Association»	Name:	Name:
Details:

Element	Source Role	Target Role
«ArchiMate_BusinessEvent» Departure BusinessEvent «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Transfer Possession to Carrier BusinessProcess «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessActor» PARTY BusinessActor «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Booking BusinessProcess «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessActor» Carrier Agent (unece) BusinessActor «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessEvent» Arrival BusinessEvent «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_Contract» Transport document (TD) Contract «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_Resource» Vessel (VSL) Resource «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessActor» Shipping Agent BusinessActor «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessActor» Local agent (AG) BusinessActor «ArchiMate_Association»	Name:	Name:
Details:

Element	Message
«ArchiMate_ApplicationComponent» Carrier Internal System	Confirm Booking()
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	>Decline Booking()
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	>Void Original Transport Document and issue amended Transport Document()
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	>Accept Amendment to Confirmed Booking()
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	=Update and/or Confirm the Shipping Instructions()
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	>Confirm Booking Completed()
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	>Reject Booking Request()
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	>Publish Draft Transport Document()
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	Issue of(Transport document (TD))
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	=Update and/or Confirm the Booking()
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	>Decide to Decline the Booking Cancellation()
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	Issue of(Transport document (TD))
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	>Reassess Booking()
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	>Issue Transport Document()
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	Issue of(Transport document (TD))
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	>Decide to Decline the Booking Cancellation()
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	=Update and/or Confirm the Transport Document()
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	=Update and/or Confirm the Shipping Instructions()
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	=Update and/or Confirm the Transport Document()
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System	>Decline Amendment to Confirmed Booking()
Details: Type: Sequence Synchronous Call

Element	Message
«ArchiMate_ApplicationComponent» Carrier Internal System
Details: Type: Sequence Synchronous Call
«ArchiMate_ApplicationComponent» Carrier Internal System
Details: Type: Sequence Synchronous Call

Property	Value
_HideUmlLinks:	True
_defaultDiagramType:	ArchiMate3::Business
isFinalSpecialization:	0

Object	Type	Connection	Direction	Notes
Trade Party (unece)	BusinessActor	Generalization	To
Carrier	Class	Dependency	From
Service	Class	Dependency	From
BR EBL Carrier: A Carrier issues a Draft B/L	Requirement	Dependency	From
Carrier	Actor	Dependency	From
BR EBL Carrier: If the Shipper fails to approve the Draft Transport Document before Vessel Departure the Carrier will Issue the Transport Document regardless	Requirement	Dependency	From
BR EBL Shipper: Responsibility for Communication with the Carrier	Requirement	Dependency	From
EBL - CM I think the issuer of the B/L type is the shipper. So the other way around.	Issue	Dependency	From
Issuing Party	BusinessActor	Generalization	To
Arrival Notice	Class	Dependency	From
«Pool» Carrier	Pool	Abstraction	From
IBP Value Stream Team	Class	Abstraction	To
Port Call Service Consumer	BusinessActor	Generalization	To
BR EBL Carrier: A Carrier authorises Delivery when a Straight B/L is shown	Requirement	Dependency	From
Port Call Service Provider	BusinessActor	Generalization	To
Transport Document - AN	Class	Dependency	From
Possessor	BusinessActor	Generalization	To