Voyage

DCSA Repository / Glossary of Terms / DCSA Glossary of Terms / All terms / Voyage

Project:

Voyage : Public <<ArchiMate_BusinessProcess>> BusinessProcess

Created:	10/24/2023 11:57:01 AM
Modified:	12/20/2024 10:41:41 AM
Author:	DCSA
Version:	2024.4

Project:
Author:	DCSA
Version:	2024.4
Phase:	1.0
Status:	Published
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{74EFCE2E-80A4-486d-883D-F28CEF534B1E}
Appears In:	Booking - Conceptual Model, Vessel - Conceptual Model, Shipment - Conceptual Model, Port - Conceptual Model, Equipment, Arrival Notice Simple CM, Involved Parties and Locations - Conceptual Model, Transport - Conceptual Model, Arrival Notice Extended CM, Port Location and Port Roles - Foundation Model , Vessel - Conceptual Model, Business Glossary, [DRAFT] Commercial Schedules CM - LDM Mapping, Vessel Journey LDM (Trial based on existing classes)., WIP - Voyage - Logical Data Model, WIP - Vessel - Logical Data Model, WIP - CS - New Terms - Conceptual Models, Vessel schedule - Conceptual Model, Transport Plan - Conceptual Model

A part of a service roundtrip that normally changes at the geographical “end-point” of a vessel rotation and as such that specific port call can have two voyages – One for the discharge of final shipments on the “current” voyage, and a new voyage number identifying the commencement of loading shipments (for allocation purposes). One rotation will normally have 2 voyages, one on each haul / direction.<br/>

Associations To
Associations From
Advanced
Other Links

Element	Source Role	Target Role
«ArchiMate_BusinessObject» Blank Sailings BusinessObject «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_Location» Port of discharge Location «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» SERVICE ROUNDTRIP Activity «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Port call BusinessProcess «ArchiMate_Composition»	Name:	Name:
Details:
«ArchiMate_BusinessEvent» ARRIVAL BERTH (EVENT) BusinessEvent «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_Location» Port of loading Location «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessEvent» PRE-ARRIVAL (EVENT) BusinessEvent «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessObject» Voyage number BusinessObject «ArchiMate_Composition»	Name:	Name:
Details:
«ArchiMate_BusinessObject» Port omission BusinessObject «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_Location» Tradelane Location «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessObject» Shipment BusinessObject «ArchiMate_Association»	Name:	Name:
Details:

Element	Source Role	Target Role
«ArchiMate_BusinessProcess» Transport Call BusinessProcess «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_Resource» Vessel (VSL) Resource «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Vessel Journey BusinessProcess «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Service BusinessProcess «ArchiMate_Aggregation»	Name:	Name:
Details:
«ArchiMate_BusinessActor» Carrier (CA) BusinessActor «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_Resource» Equipment Resource «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_Location» Transport leg Location «ArchiMate_Association»	Name:	Name:
Details:
«ArchiMate_BusinessProcess» Vessel rotation BusinessProcess «ArchiMate_Association»	Name:	Name:
Details:

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

Object	Type	Connection	Direction	Notes
Commercial Voyage	Class	Dependency	From
«ArchiMate_BusinessProcess» Transport	BusinessProcess	Generalization	To
APV Value Stream Team	Class	Abstraction	To
Commercial Voyage	Class	Dependency	From
Voyage	Class	Dependency	From