Maersk Domain Model
Download and install the Preflight Desktop tool to work with JSON and Avro schemas. Preflight Desktop Access GitHub repo with Maersk Domain Model schemas, including JSON- and Avro schemas, SQL table statements, Java and .NET and more. Schemas
Data
Package
Class
Attribute
Enumeration
Literal
Relationship
Agreement Representative 135afdd2-7edf-ed11-b82b-44e517a1f1d9 Agreement true A party who signs the Agreement and can either represent itself or another party. The relationship between Agreement and Party must be indirect and represented by this class, as there are specific attributes on the Agreement Representative, such as sequence, signature type, date, requirement, etc. true false Transactional Internal N/A
Selected Clause Variable 4b0df349-dbef-ed11-b82d-44e517a1f1d9 Agreement true Holds the actual selection that a customer (or other similar party) has made in regards to a set of choices within a Standard Clause Variable. Agreement Clauses may or not have Selected Clause Variables, depending on the business use case of an Agreement Clause. true false Transactional Internal N/A
Agreement Type 6f363a81-b4fc-e911-80eb-9cd21e38f3a4 Agreement true Indicates and classifies the type (and/or subtype) of Agreement. Examples of types and subtypes: - Shipping Agreement - Service Contract - Detention & Demurrage - Market Rate - Tariff - Shipping Commitment - Vessel Sharing Agreement - Slot Charter Agreement - Pricing - Delivery/ Shipment - Labor - Payment - Advertising - Accounts - Sales Transaction - Vendor/ Purchase Order true false Reference Internal N/A
Agreement Line 73363a81-b4fc-e911-80eb-9cd21e38f3a4 Agreement true A specific agreement line associated with an Agreement, typically specifying details on prices, products, quantities, etc. It is referred to by other names as well, such as "price sheet", "rate", or "rate line". true false Transactional Confidential Competitive Strategic Information
Shipping Commitment 84363a81-b4fc-e911-80eb-9cd21e38f3a4 Agreement true An agreement between a Transport Provider and a Customer, whereby a customer commits to ship a given number of equipment units (typically containers) within a specific time period. true true Transactional Internal Competitive Strategic Information
Agreement 8a363a81-b4fc-e911-80eb-9cd21e38f3a4 Agreement true Also known as contract, an agreement specifies certain legally enforceable rights and obligations pertaining to two or more mutually agreeing parties. It typically involves the transfer of goods, services, money, or a promise to transfer any of those at a future date, as well as terms and conditions to do so. Agreements can either contain Agreement Lines (specifying details on prices, products, quantities, etc.), Agreement Clauses (specifying details on terms and conditions), or both. Examples: Contracts with Customers regarding charge rates and other terms and conditions for the shipping of cargo Rate agreements with Suppliers for intermodal transport Proposed contracts and templates for contracts Standard terms and conditions and charge rates defined by the Enterprise, such as Base Rate Tariffs of Tiered Contracts Agreements regarding Network Capacity. E.g. Slot Charter Agreements, Vessel Sharing Agreements Position Lease Agreement for empty positioning with partners Exclusion: Customer Requirements (confirmed or otherwise) such as Bookings or standing requirements regarding the nature and mode of communication. true true Transactional Confidential Competitive Strategic Information
Agreement Clause 93363a81-b4fc-e911-80eb-9cd21e38f3a4 Agreement true A clause included in the Agreement, typically specifying details on terms and conditions. Clauses can be based on a Standard Clause, hosted in the Standard Clause Library. We, therefore have 3 options: The clause may be exactly as specified in the standard clause library; The clause may be based on specification in the standard clause library, but changed as part of negotiations; The clause may not be based on the standard clause library, and directly specified by negotiations. true true Transactional Confidential Competitive Strategic Information
Agreement Line Type bb363a81-b4fc-e911-80eb-9cd21e38f3a4 Agreement true A classification an Agreement Line. In the case of a Slot Charter Agreement, Slot Charter Agreement Commitment Lines can be of various types. Possible examples include: - Zone-Zone - Port-Port - Round trip - Committed Price - Flexible Commitment true false Reference Internal N/A
Agreement Status bf363a81-b4fc-e911-80eb-9cd21e38f3a4 Agreement true Defines the status of an Agreement. Examples: Draft Proposed Declined Accepted Approved Updated Notified Effective Expired Agreement Line status can be Active Cancelled Expired true false Reference Internal N/A
Agreement Relation Reason c6363a81-b4fc-e911-80eb-9cd21e38f3a4 Agreement true Describes the type of relationship between two agreements such as one agreement is a subset of another agreement, one agreement is an amendment to another agreement, one agreement is a replacement for another agreement, etc... true false Reference Internal N/A
Clause Type ce7f565b-69c9-ed11-b826-44e517a1f1d9 Agreement true Indicates the type of clause. These include, among others, legal clauses, commercial clauses, summaries, contract cover pages, etc. true false Reference Internal N/A
Clause Review Type d07f565b-69c9-ed11-b826-44e517a1f1d9 Agreement true Indicates type of governance/ revision that the clause must have, therefore having implications on who are its revisors. true false Reference Internal N/A
Agreement Relation ee0e29ff-904b-ee11-a1ba-9a42c5ca5684 Agreement true Allows an agreement to be related to other agreement for a specific reason. true false Transactional Internal N/A
Equipment Lease Agreement Line 53a87f81-dd2f-ed11-a1a0-bf3947c3094d Asset Agreement true Equipment Lease Agreement details that pertains to pick up or drop off, of leased equipment from location points within a pool. Pick up is also referred to as on-hire while drop off is referred to as off-hire. true false Transactional Internal N/A
Equipment Lease Agreement 7441f113-1faf-eb11-ab7f-5c879c3c5a54 Asset Agreement true An agreement between Equipment owners and Leasing party for the duration of the equipment lease true true Transactional Internal Competitive Strategic Information
Rate Line 09eee72f-bedd-ed11-b82b-44e517a1f1d9 Rate true Represents an individual Line on a Rate. The values on price, rate basis, unit of measurement, charge type, etc. are captured in the related composed Charge instance. true false Transactional Internal N/A
Rate d09a2fa1-bcdd-ed11-b82b-44e517a1f1d9 Rate true A set of estimated prices for goods and services, that go logically together. It can be represented in the shape of a document in certain business scenarios, namely for Purchase Rates. For Maersk, Sales Rates (also called "Prices") are stored in a Price Engine that retrieves them to other capabilities that consume them, such as Product, Contract (Agreement), or Booking. true false Transactional Internal N/A
Insurance Agreement 0b7d22b1-e2be-ed11-a1ac-ffabf0d7d350 Insurance Agreement true An insurance agreement, or policy, is a document that outlines the terms and conditions of an insurance contract between an insurer (the insurance company) and an insured (the policyholder). The policy sets out what risks are covered by the insurance, how much the policyholder will pay for the insurance coverage, and what benefits the policyholder will receive in the event of a covered loss or claim. true true Transactional Internal Competitive Strategic Information
Vessel Insurance Agreement 96363a81-b4fc-e911-80eb-9cd21e38f3a4 Insurance Agreement true The minimum insurance cover for core marine activity consists of: Hull & Machinery (H&M) covers the assureds losses resulting from physical damage to a vessel and on-board equipment. Additionally the insurance covers the assureds liability in respect of collision with another vessels or contact damage to fixed and floating objects and installations War Insurance covers damages as a result of war, sabotage, strikes etc. (risks which are excluded under H&M property insurance (whether or not there has been a formal declaration of war) Protection & Indemnity (P&I) covers the shipowners legal liability to third parties and certain costs and expenses arising from owning and/or operating vessels such as clean-up costs following pollution from the vessels, cargo claims, removal of wrecks and certain fines FD&D covers the expense of obtaining legal advice and assistance, including the cost of employing experts as may be necessary to pursue or defend such disputes. As such, it is sometimes also called "Defense Costs" insurance. FD&D insurance does not, however, cover the principal subject matter disputed. Equipment Insurance covers total of the assured's container and other equipment and liabilities arising out of the operations of the containers/equipment Charterers Liability to Hull (CLH) covers Charterers liability under the charterparty for damages to the vessels hull. true true Transactional Internal Competitive Strategic Information
Standard Clause Variable 5baa3e37-6592-ed11-b81b-44e517a1f1d9 Standard Clause true Represents the different aspects of a clause that can be chosen or configured. true false Master Internal Competitive Strategic Information
Standard Clause b3363a81-b4fc-e911-80eb-9cd21e38f3a4 Standard Clause true A standardized version of an Agreement Clause, typically stored in a library, to be re-used when making Agreements. Multiple standard clauses can be bundled in a Standard Clause Group, effectively making it a hierarchy of standard clauses. Standard Clauses and Standard Clause Groups can be attached to an Agreement Template, on an Agreement Template Library. This is modelled in Agreement (via inheritance from Document). . true true Master Internal Competitive Strategic Information
Pricing Parameter 4708335f-cf12-ed11-a19f-cacbfc25e2af Demurrage and Detention Agreement true Pricing parameter which influence the price differentiation. The pricing parameters might be at the agreement level or at the agreement line level. true false Master Internal N/A
Demurrage and Detention Agreement 50363a81-b4fc-e911-80eb-9cd21e38f3a4 Demurrage and Detention Agreement true Defines the specific Detention and Demurrage contract with a specific Party relative to prices, terms and conditions. Example: The terms between a Third Party and an Enterprise as it relates to the pricing of products and services. true false Transactional Internal Competitive Strategic Information
Demurrage and Detention Agreement Line df363a81-b4fc-e911-80eb-9cd21e38f3a4 Demurrage and Detention Agreement true DnD Agreement Line is the detailed specification of an Agreement line for either a Detention or a Demurrage Agreement. true false Transactional Internal Competitive Strategic Information
Negotiation Instrument 04a4625a-6016-ee11-b834-44e517a1f1d9 Negotiation true The negotiation instrument represents the components that need to be negotiated as part of the negotiation. The instrument specifies the component type and provides a reference to the component with the owner of the component. For a commercial price negotiation, the instruments typically would be: Product, T&C, Price (and allocation if Ocean or inland product). true false Transactional Internal N/A
Negotiation 1cc39242-fe13-ee11-b833-44e517a1f1d9 Negotiation true A negotiation is the activity of orchestrating the interaction of 2 or more internal or external parties, with the aim of establishing 1 or more agreements. Most negotiations will be an interaction between Maersk and an external party to establish one or more agreements. Negotiations aiming to establish more complex agreements can require extensive internal alignment within the company, which is also a type of negotiation. true true Transactional Internal N/A
Negotiation Instrument Type 248a28af-6016-ee11-b834-44e517a1f1d9 Negotiation true The different types of Negotation Instruments that one can have. Negotiation Instruments have subtypes in a hierarchy. The top hierarchy is also known as "domain" and the bottom hierarchy as "subdomain". Examples of domains are: Price, Product, T&C, Inventory. Examples of subdomains are for instance: Inland, Ocean, Price, ... true false Reference Internal N/A
Negotiation Instrument Status 34425b8a-dd26-ee11-b83f-44e517a1f1d9 Negotiation true The diferent business status (i.e. stages) that a Negotiation Instrument can be at. Because therer are several Negotiation Instrument Types, the set of status can be diferent depending on the Negotiation Instrument Type. true false Reference Internal N/A
Negotiation Round e45b1834-0414-ee11-b833-44e517a1f1d9 Negotiation true A negotiation round is defined as the interactions from the start of the round until a draft agreement is sent/received for approval with/from an external party. A negotiation can run over several rounds, each producing new draft agreements. For customer facing negotiation, each round will produce a new draft quote for the customer to approve or reject. For vendor facing negotiation, each round will produce a draft quote for the company to approve or reject. true false Transactional Internal N/A
Crane 0c560381-b4fc-e911-80eb-9cd21e38f3a4 Crane true A crane is a type of machine used for lifting, generally equipped with a hoist (device) or winder wire ropes or chains and sheaves, that can be used both to lift and lower materials and to move them horizontally. true true Master Internal N/A
Crane Type 16560381-b4fc-e911-80eb-9cd21e38f3a4 Crane true Maersk names for Equipment Type of Crane. Classification of cranes - typical types are: Rubber-Tyred Gantry Crane (RTG) Gantry Crane (GC) Mobile Crane (MbC) Rail-mounted Gantry crane (RMG) Reach Stacker Straddle Carrier (SC) Rail-Mounted Quayside Crane (RMQC) These might be physically represented in the Equipment Type table, where the Parent Equipment Type is Crane. true false Reference Internal N/A
Depreciation Schedule 3e21c9c3-0903-ed11-a19f-cacbfc25e2af Asset true The calculated depreciation of an asset for all years until end of life. For example if an asset depreciates over 5 years, there will be 5 entries. true false Master Confidential N/A
Asset Type 40540381-b4fc-e911-80eb-9cd21e38f3a4 Asset true A type of asset. This can be: Either one of the major (next level) Asset subtypes, which include categories such as Vehicle Equipment Crane Facility Software Component Or, a type for which a specific subtype is not defined. These types can be hierarchical. For example, if an 'Office Stationery' instance of Asset Type existed, then additional instances could, if required, be added for (say) 'Box of Pens' and 'Photocopier'. If required, these could be further subdivided (eg 'Box of 50 Black Pens', or 'Canon Photocopier type 42'.). Other examples include: Remote Container Management Device Global Positioning Device Reefer Controller Mobile Communications Device true false Reference Internal N/A
Multi Item Asset Content Type 47540381-b4fc-e911-80eb-9cd21e38f3a4 Asset true An indication that an Asset of one type can form part of another true false Reference Internal N/A
Compatible Asset Type Set 48540381-b4fc-e911-80eb-9cd21e38f3a4 Asset true A set of Asset Types that are compatible with one another (eg a type of computer motherboard and a type of CPU that are compatible with one anotther) true false Reference Internal N/A
Multi Item Asset Content 53560381-b4fc-e911-80eb-9cd21e38f3a4 Asset true Links multiple assets together to make up compositions of assets. true false Master Internal Competitive Strategic Information
Asset 5e560381-b4fc-e911-80eb-9cd21e38f3a4 Asset true An asset is a tangible (e.g. a vessel, a container, or a crane) or intangible (e.g. software) object. An asset must also have a value and be owned or controlled by Maersk. An asset may also have financial value. This could include items such as equipment, vehicles, or other resources that contribute to the company's financial standing. This financial value is characterised by its acquisition value, net purchase price, and net sales price among other properties. It also includes references to related elements like depreciation profiles and schedules. true true Master Internal Competitive Strategic Information
Asset Relationship Purpose 7c86e8bf-2ca5-ea11-adb1-40b034e2c22b Asset true Defines the purpose of the relationship between 2 or more Assets true false Reference Internal N/A
Depreciation Profile dd9dbbd4-0903-ed11-a19f-cacbfc25e2af Asset true A profile specifying how an asset will depreciate over time. This is used for both individual assets and for lease agreements, where a depreciation of asset is agreed with lessor. true false Master Confidential N/A
Observation 50520381-b4fc-e911-80eb-9cd21e38f3a4 Sensor Observation true Measurement of the condition, circumstance and performance of an asset (equipment, vessel, truck etc.). Readings can be captured through sensors built into or mounted on an asset or through other ways of manual or semi manual capture. For non-sensor observations the sensor is not recorded but the observed property will designate what the observation is about. E.g. if a piece of equipment where to be recorded as "Turned On" this would be the observed property and the observation would record that as a boolean value set to true. Likewise if an equipment was observed at a postion the observed propertye could be "Postion", all values would be empty but the position would be populated. Notes on datatypes: Specific attributea are provided for each of the following datatypes: Decimal, Integer, Boolean and String. The reason for this is to avoid unnecessary and potentially incorrect conversion from a string value to e.g. decimal or integer. Some observed properties can also be of boolean value, e.g. "Humidity Control On". A descriminator called "Observation Datatype" is provided so that it is easy to derive in which datatype the observation has been logged. true true Transactional Internal N/A
Sensor Type 5e520381-b4fc-e911-80eb-9cd21e38f3a4 Sensor Observation true The type of component that logs the reading for the asset. I.e. a temperature for a reefer container would be read by a reefer controller. It is not always necessary to know what kind of component logged the reading so it is optional. Examples: Reefer Controller Mobile Communication Device Global Positioning Device Engine Controller true false Reference Internal N/A
Feature Of Interest Type 8baaa20e-b1f5-eb11-833a-06b9e9a82a4d Sensor Observation true Descriminates the feature of interest to the type it is. E.g. a vessel, equipment, container, reefer, truck etc. true false Reference Internal N/A
Sensor 8e99242b-c8f4-eb11-833a-062fd80a5823 Sensor Observation true The sensor which observed the value being logged. E.g. a Reefer Controller mounted on a refrigerated container. true true Master Internal N/A
Observed Property aa5781e5-c9f4-eb11-833a-062fd80a5823 Sensor Observation true A list of properties that can be observed and logged in the observation value. Note on unit of measurment: The unit of measurement is not limited on the observed property. I.e. one could set that a temperature has the unit of Celsius. But if the observation being logged from the sensor is in Fahrenheit the unit coming via observed property would be wrong. Below some examples for a Reefer Controller device: Ventilation Volume Supply Temperature Return Temperature CO2 Percentage CO2 Setpoint Humidity Percentage O2 Percentage O2 Setpoint Air Exchange Ambient Temperature Cargo Temperature Compressor Discharge Temperature Compresso Suction Temperature Compressor Frequency Current Discharge Pressure Evaporator Motor Status Evaporator Temperature Extended Operating Mode Finished Defrost Heater On Time Heater Percentage Hot Gas Valve Opening Humidity Humidity Control On Humidity Setpoint Line Frequency Power Frequency Power Status On Power Supply DC Voltage Power Voltage Relative Humidity Return Temperature Suction Modulation Valve Opening Suction Pressure Suction Temperature Supply Temperature Temperature Setpoint Time To Defrost Total Current Draw USDA Temperature Ventilation Setpoint Below some examples for a Vessel: Fuel Inlet AE Inlet BLR Inlet Vessel Position Draught Speed Through Water true false Reference Internal N/A
Feature Of Interest f89948ea-aef5-eb11-833a-06b9e9a82a4d Sensor Observation true Features or feature collections that represent the identifiable object(s), e.g. a vessel, equipment, asset, truck etc., on which sensor systems are making observations. In the case of an in-situ sensor or observations being attributes of the thing, the feature of interest could be the thing itself. For remote sensors, this may be the geographical area or volume that is being sensed. If for example a air quality is being measured on for a street the feature of interest would be the street. true false Transactional Internal N/A
Fire Suppression System 0d7f71b1-0348-11f0-056d-122e28535636 Facility true A facility uses multiple fire suppression systems. These systems have different types, for example: * Water * Foam * Dry chemical * CO2 (carbon dioxide) * Wet chemical * Clean Agent (e.g. FM-200, NOVEC 1230) * Inert gas (e.g. Argonite, Inergen) * Water mist * Halon * Aerosol-based fire suppression system * Hybrid suppression agent (e.g. nitrogen-water systems) * Other agent * None true false Reference Internal N/A
Refrigerant 24f23591-309c-11f0-14c8-96109e803296 Facility true Typically, a cooling system is designed to operate with a specific type of refrigerant. Mixing different refrigerants can lead to performance issues, and possible damage to the system. However, some dual refrigerant or multi-split systems exist which can accomodate different types of refrigerants across separate circuits or components. As an example, cold storage units may use different refrigerants for high temperatures and for extremely low temperatures. true false Master Internal N/A
Port 3bf010cb-f519-ed11-a1a0-bf3947c3094d Facility true A port is a maritime facility comprising one or more wharves or loading areas, where ships load and discharge cargo. true true Master Public N/A
Facility Asset Feature 4f5e8681-eede-11ef-4d73-26789e28917f Facility true A facility feature describes a capability or function which the facility contains or supports. The feature can be anything which sets the facility apart from others. It should be used to denote things like special security installations, technical installations, safety equipment or features which are part of HSSE requirements. Some examples are: * has oil water separator * has underground storage tank * has automated access management * has emergency lights * has pedestrian crossings * has vehicle landing zones * has separated battery charging area * has restrooms * has break rooms true false Master Internal N/A
Container Handling Equipment Type 51168ddd-dfd7-11ef-3a77-922eb47883a8 Facility true Administers the type(s) of container handling equipment (CHE) which the facility contains. This does not include cranes, which exist as separate entities within a facility. true false Reference Internal N/A
Facility Availability 55550381-b4fc-e911-80eb-9cd21e38f3a4 Facility true Specifies when a facility is available, e.g. opening hours, work shifts or when the facility is available as a specific type to Maersk, e.g. as a Container Yard. Opening hours: Using this class it is possible to define opening hours for a specified day for a Facility. Relating the Facility to a set of weekdays with start and end times and setting the 'Facility Availability Type' to 'Opening Hours'. Specific date ranges can be defined, in which the facility will have alternating opening and closing hours. For this the date range attributes are used. To indicate that Facility is not open during a date range or certain weekdays, both start and end time is set to 00:00. Work shifts: It is also possible to define work shift during particular week days or date ranges. true false Master Public N/A
Gate 5a550381-b4fc-e911-80eb-9cd21e38f3a4 Facility true The physical point where a container interchanges from a facility to a transportation provider and vice versa. Some gate facilities have automated scanning of incoming and outgoing containers to optimize the gate in/out capacity. true true Master Public N/A
Facility Status 6b79d65d-301e-ef11-a1c5-f3ef5fbf2395 Facility true The status of the Facility examples Decommissioned Active Inactive true false Reference Internal N/A
Facility Offering 77550381-b4fc-e911-80eb-9cd21e38f3a4 Facility true A Facility offering is any kind of tangible or intangible service/offering/utility particular to a specified Facility. It typically includes services such as crane-lifting, spreader utilisation, provision of internet access, wi-fi, and utility provision such as water, electricity, telephone. Examples: Crane-moving Container-storage Printing Internet Access Cargo Consolidation Reefer HandlingWhether the Facility, Warehouse etc. can handle or accepts reefer containers Dangerous GoodsWhether the Facility, Warehouse etc. can handle or accepts dangerous goods Cold Storage Cold Chain Logistics For Contract Logistics (WND) Consolidation Deconsolidation Fulfilment For Contract Logistics (Depot) Full container storage Container preparation Customer depot Stuffing De-stuffing Note: It is possible that for example "Crane-moving" might be segmented into multiples with specific weight-handling capacity, such as "Crane-moving, less than 10 tonnes", "Crane-moving, 10-20 tonnes" etc. true false Master Public N/A
Facility Power 7a60f811-df14-11ef-06cc-6294512195f3 Facility true Information about available power capabilities at the facility. true false Master Internal N/A
Facility Power Type 7a60f813-df14-11ef-06cc-6294512195f3 Facility true Type of facility power consumption. This is currently focused on types of emergency power. The various types of emergency power can have sub types, as follows: Conventional Generator-based systems * Diesel Generator * Natural Gas Generator * Bi-Fuel Generator (Diesel + Natural Gas) * Propane Generator (LPG) Battery & UPS Systems * Battery Backup / UPS (Uninterruptible Power Supply) * Battery Energy Storage System (BESS) Grid-Based / Utility Backup * Electrical (Utility Backup via Dual Feed) * Onsite Substation with Emergency Feed Renewable and Hybrid Systems * Solar with Battery Storage * Wind with Battery Storage * Hybrid System (e.g., Solar + Diesel + Battery) * Fuel Cell System (Hydrogen or Natural Gas) true false Master Internal N/A
Facility 7f550381-b4fc-e911-80eb-9cd21e38f3a4 Facility true A building, construction or installation designed to serve a specific function. Facility can be linked to subsidiary Facilities within its hierarchy to enable high-level multi-function Facilities (such as Ports) to be made up of subsidiaries such as Marine Container Terminals, Container Yards, Warehouses, Customs Buildings, Railheads, and Docks. Example Port of Algeciras has 2 marine container terminals, a ferry terminal, a rail terminal and a depot in the existing master data set. Facility Type DEPOT Facility Code ESALR03 Facility Name STAR CONTAINER DEPOT - COMESA Facility Type TERMINAL Facility Code ESALRTM Facility Name Algeciras - ML Terminal Facility Type TERMINAL Facility Code ESALR04 Facility Name TTIA HANJIN ALGECIRAS Facility Type TERMINAL Facility Code ESALR05 Facility Name Ferry Terminal Facility Type RAIL TERMINAL Facility Code ESALR01 Facility Name Algeciras Rail Station Note: The relationship between the Port and Marine Container Terminal can be handled via the Facility Relationship. Legacy Note: To allow for backwards compatability some Facilities will be one-to-one with Sites. In these cases the unique code of the Facility should be the same as the Site. For example for Vessel Schedules it is necessary to have the Marine Container Terminals like UNYCTRM which is also a Site due Maersk legacy master data. The Site can still have multiple other Facilities associated without the same code. true true Master Public N/A
Warehouse 8c639dd0-99e3-11f0-6647-9e6a8bfe0eb1 Facility true
Facility Cooling System 8e5cf6e2-dfd5-11ef-3a77-922eb47883a8 Facility true Facility cooling can consist of multiple cooling systems. These systems are of different types: * Air-Cooled Systems * Water-Cooled Systems * DX (Direct Expansion) Systems * Chilled Water Systems * VRF/VRV Systems * Hybrid Cooling Systems * Geothermal Cooling (Ground Source Heat Pumps) * Absorption Chillers * Portable/Spot Coolers * Underfloor Air Distribution (UFAD) * Displacement Ventilation * Fan Coil Units (FCUs) A mix of different cooling systems (of different types) can exist within a single Facility. true false Master Internal N/A
Facility Availability Type 91fad1e5-ae19-eb11-adce-40b034e2c22b Facility true The type of availability that defines the entry in 'Facility Availability'. Examples: Container Yard - an availability type that allows to store information about when a facility is available as a container yard. Maersk may be using certain facilities types within certain time periods as we procure right to use them. This kind of availability type can of course also be created for Warehouse, Maintenance Shop and so forth. Opening Hours - allows the setup of when a facility is open for business. Work Shift - allows setup of when a facility has work shifts set up. For example to denote that there are work shift from 8.00am to 4.00pm and then another entry in Facility Availability for same type from 4:00pm to 1:00am true false Reference Public N/A
Maintenance Shop 9a550381-b4fc-e911-80eb-9cd21e38f3a4 Facility true A facility design to undertake maintenance and/or repair work on equipment. Also known as M&R (Maintenance and Repair) shop. Example: Repairs of containers or chassis when broken down Scheduled maintenance of containers true true Master Public N/A
Facility Type a7550381-b4fc-e911-80eb-9cd21e38f3a4 Facility true Types of Facilities. Note that there can be many types which are not depicted as specific subtypes of Facility. If they carry no specific attributes there is little reason to subtype. Top level facility types: * Operational Facility * Commercial Facility Administrative, service and sales activities and functions only for Maersk- or Maersk affiliate facilities. Facility sub-typed examples: Operational Facility subtypes * Port The main facility for harbour activities. Typically a port has facilities like one or more marine container terminals or container yards etc. * Marine Container Terminal (aka. Terminal) Can be part of a Port * Container Yard * Gate * Warehouse A building for the storage of goods used by different parties like manufacturers, importers, exporters, customs, wholesalers and transport businesses * Maintenance and Repair Station * Berth * Intermodal Container Transfer Facility * Airport * Maintenance Shop * Customs Office Facility non-subtyped examples: These are facility types without any parent type and they are not subtypes of Facility itself. * Railhead * Reefer Depot * Waterway * Port City Container Depot Commercial Facility child types These are child types of the Customer Facility type but not subtypes of Facility itself. * Office Also known as an office block or business centre which is a form of commercial building containing spaces mainly designed to be used for offices. * Shop Office child types These are child types of the Office facility type but not subtypes of Facility itself. * 3rd Party Agent * 3rd Party Counter Agent * Brand Office * Vessel Agent Intermodal Container Transfer Facility child types These are child types of the ICTF facility type but not subtypes of Facility itself. * On-dock Intermodal Container Transfer Facility is a facility for loading containers directly onto trains at an on-dock loading facility without traveling on public roads. * Near-dock Intermodal Container Transfer Facility is nearby, but requires travel on public streets to/from berths. * Off-dock Intermodal Container Transfer Facility is removed from the port, such as the downtown/East Los Angeles yards. Marine Container Terminal child types These are child types of the MCT facility type but not subtypes of Facility itself. * Feeder Terminal (aka. Feeder Port) which is generally for "domestic" transport and normally has tidal variations. * Ocean Terminal (aka. Ocean Port) which is a deep sea terminal and has little to no tidal variation. * Barge Terminal which is generally for canal shipping purposes or low depth waters. Commercial Facility Administrative, service and sales activities and functions only for Maersk- or Maersk affiliate facilities. Operational Facility Physical structure where Goods; Cargo and Equipment are transferred, handled or taken care of. Any facility that Maersk works with. true false Reference Public N/A
Facility Relationship Type ab550381-b4fc-e911-80eb-9cd21e38f3a4 Facility true A type of Facility Relationship. Examples: Terminal in Port Gate in Terminal Office in Port Customs Receiver for (when submitting manifests or other customs documents for a specific port, airport, etc., sometimes they don't have the ability to receive such customs submission, and another related port, airport, etc., called the "receiver", will receive the customs submission on behalf). Customs Office for (specifies what is the official Customs Office handling customs at a specific facility, like a port, airport, etc. -- it should be noted that 1 Customs Office can also in some cases cover multiple ports, airports, etc., and that 1 port, airport, etc. can have more than 1 Customs Office in certain business scenarios). true false Reference Internal N/A
Facility Relationship b4550381-b4fc-e911-80eb-9cd21e38f3a4 Facility true A relationship between Facilities. Examples include: Port Algeciras has Marine Container Terminal ESALRTM Marine Container Terminal ESALRTM has 3 GATES The relationships can be one to many (e.g. as in ordinary Hierarchy), or can be many to many (e.g. if there can be a network of peer to peer relationships between Facilities). true false Master Internal N/A
Airport bb4e781e-366e-ea11-ada3-40b034e2c22b Facility true An airport is an aerodrome with extended facilities, mostly for commercial air transport. Airports often have facilities to store and maintain aircraft, and a control tower. true true Master Public N/A
Canal ca1ddbb8-6cd3-ee11-a1c1-a83983aea769 Facility true A Canal is a man-made waterway constructed to allow the passage of boats or ships inland or to convey water for irrigation. It serves multiple purposes, including facilitating maritime trade by connecting two bodies of water, thus providing a navigable route for shipping and transportation. Examples are Suez or Panama Canal, which are crucial for international maritime trade by enabling ships to bypass lengthy and hazardous sea routes. true true Master Public N/A
Container Yard Stowage Slot d1550381-b4fc-e911-80eb-9cd21e38f3a4 Facility true A space (of a specified size and type) in a specific Container Yard, that can be used to stow a Container. A Yard Block will be operated on by a RTG. This type of crane has an inverted "U"-shape and can only move in one dimension. true true Master Public N/A
Container Yard d6550381-b4fc-e911-80eb-9cd21e38f3a4 Facility true Facility designated by the carrier for receiving, assembling, holding, storing, and delivering containers, and where containers may be picked up by shippers or redelivered by consignees. Examples of different types of Container Yards: Rail yards, Trucker yards, Inland depots. true true Master Public N/A
Intermodal Container Transfer Facility e8550381-b4fc-e911-80eb-9cd21e38f3a4 Facility true A facility where cargo containers are transferred between different land vehicles, for onward transportation. The transhipment is from land vehicle to land vehicle for example from truck to train or truck to truck. Goes under the acronym ICTF; also known as Inland Container Terminal. This kind of facility can be on-dock, near-dock or off-dock to indicate how far it is from a related marine container terminal. true true Master Internal N/A
Asset Profile a54ce843-42b5-11f0-14c8-96109e803296 Asset Profile true true false Reference Internal N/A
Vehicle Profile a54ce845-42b5-11f0-14c8-96109e803296 Asset Profile true true false Reference Internal N/A
Approach Channel b5550381-b4fc-e911-80eb-9cd21e38f3a4 Terminal true Approach channel to the marine container terminal. There can be multiple approach channels, e.g. one of the terminals in Shanghai has 2: MAIN CHANNEL MIN DEPTH IN APPROACH: 12.5 M WAIGAOQIAO INSHORE CHANNEL MIN DEPTH IN APPROACH : 12.0M true true Master Public N/A
Pilotage Duration c7550381-b4fc-e911-80eb-9cd21e38f3a4 Terminal true The default length of time it takes to pilot a vessel, of specified Capacity Class, arriving or departing at/from a particular Marine Container Terminal. true false Master Internal N/A
Berth f1550381-b4fc-e911-80eb-9cd21e38f3a4 Terminal true The specific quayside location, usually within a port or harbour, where a vessel may be docked, usually for the purposes of loading and unloading cargo. The berths comprising a container terminal can have different data, e.g. different drafts and lengths. E.g. in APM Terminal in Kobe there are berths called C-1, C-2, C-3 and C-4. C1-C4 has draft of 13 meters. C-5 has 15 meters. They also have different lengths. true true Master Public N/A
Marine Container Terminal fa550381-b4fc-e911-80eb-9cd21e38f3a4 Terminal true A facility where cargo containers are transhipped between different land and ocean transport vehicles, for onward transportation. The transhipment is from Vessel to Vessel or form Vessel to land vehicle, for example train or truck. true true Master Public N/A
Transport Asset Requirement 29288487-80f2-ea11-a3b7-a0510b9e9705 Transport Asset Requirement true Defines what are the required transport assets (i.e. vehicles and/or equipment, such as containers) for a given shipment, transport, cargo, etc. The requirements can include the size and the type of vehicle/ equipment, as well as quantity of assets, and requirements for range of temperature on temperature controlled assets, etc. true true Transactional Internal N/A
Transport Asset Priority 6c657bae-c3ae-eb11-831a-06f40a4cb289 Transport Asset Requirement true Customer specified priorities for the equipment that they want for their shipments. Example: customer may send us 2 TAR for the same Shipment/ Booking/ etc. one TAR being for 3 dry 40" containers another TAR being for 4 dry 20" containers then first TAR has priority name "high" and group "black friday" second TAR has priority name "low" and group "regular season" this then means, for carrier, that he should prioritise ensuring the 3 dry 40" over the 4 dry 20" containers. true false Reference Internal N/A
Haulage Requirement 964d0381-b4fc-e911-80eb-9cd21e38f3a4 Transport Asset Requirement true A specific subtype of Transport Asset Requirement, applicable to both truck, chassis or trailer. that holds specific attributes and relationships that are only applicable to haulage. true true Reference Internal N/A
Stuffing Requirement 9ae8cdab-83e8-eb11-a3d5-a0510b9e9705 Transport Asset Requirement true All requirements pertaining to how the stuffing of the transport asset is to be performed. true true Transactional Internal N/A
Loading Type f48ec19d-560d-ed11-a19f-cacbfc25e2af Transport Asset Requirement true Loading Type States the loading type that is planned / actually used when stuffing the cargo, for example "Snake loading by order number" or "Load by carton size". true false Reference Internal N/A
Temperature Setpoint 29703705-029c-eb11-ade6-40b034e2c22b Environment Control true A temperature setting that is applicable to a given time period. These temperature settings can be sequenced in order to obtain a programmed schedule/ profile of variable temperatures. true false Transactional Internal N/A
Temperature Profile 44ca8ead-4720-ec11-a3db-a0510b9e9705 Environment Control true Temperature settings, namely when they change during journey, can be defaulted via a Temperature Profile. This Temperature Profile will define upfront how many probes and set points are required, as well as specifying what are the default values of each set point (sequence, degrees, duration, start, end). NOTE 1 (Single Set Points) Temperature Profiles can also be specified for when temperature settings are fixed (don't change during journey), as one might want to create profiles for single temperature set point transportations. NOTE 2 (Default vs Required) Temperature Profiles will provide Default Set Points, i.e. a Master Data template, via the relationship "defaults". Values here will be "copied" to the Required Set Points, i.e. the instances of "Temperature Set Point" via the relationship "has required". Then, one can change or adjust its default values to specific business needs on the Required Set Points. The master data, i.e. the Default Set Points, cannot be changed. NOTE 3 (Profile not used) In line with what is described in NOTE 2, one can also choose to have Temperature Requirement having 0 Temperature Profiles (i.e. not use a default), and have the Temperature Set Points completly customized as one time only setting. Temperature Profile Types and Granularity Temperature Profiles also have types, for the sake of classifying them within a operating, or cargo type category, providing additional business meaning. Possible types include, among others, Cold Treatment, Fruit Ripening, Ripening Prevention, etc. It should be noted that a temperature profile is more granular than a profile type. For instance, these would be possible Temperature Profiles: cold treatment for frozen fish fruit ripening for bananas fruit ripening for mangoes It should be noted that granularity is not necessarily by cargo or commodity type. true true Reference Internal N/A
Temperature Profile Type 46ca8ead-4720-ec11-a3db-a0510b9e9705 Environment Control true Temperature Profiles have types, for the sake of classifying them within a operating, or cargo type category, providing additional business meaning. Possible values include (among others): Cold Treatment Fruit Ripening Ripening Prevention true false Reference Internal N/A
Environment Control 4d29be98-253e-ec11-a3dd-a0510b9e9705 Environment Control true A set of features and information relating to control of environment settings, such as temperature, ventilation, humidity or atmosphere. Typically used for the proper conservation of goods and commodities which are otherwise perishable or degradable, if not maintained under the specified environment conditions. They can be applicable to either transport assets (containers, ULD's, trucks, aircrafts, etc.) or storage assets (warehouses, etc.). true true Transactional Internal N/A
Ventilation Control 89aa4410-029c-eb11-ade6-40b034e2c22b Environment Control true All features pertaining to ventilation control on an environment controlled asset, e.g. a reefer container, a reefer truck, a cold storage warehouse, commodity etc. true true Transactional Public N/A
Humidity Control ac06b9e4-019c-eb11-ade6-40b034e2c22b Environment Control true All features pertaining to humidity control on an environment controlled asset, e.g. a reefer container, a reefer truck, a cold storage warehouse, commodity etc. true true Transactional Internal N/A
Atmosphere Control d3cdac22-029c-eb11-ade6-40b034e2c22b Environment Control true All features pertaining to atmosphere control on an environment controlled asset, e.g. a reefer container, a reefer truck, a cold storage warehouse, commodity etc. true true Transactional Internal N/A
Temperature Control e6dc90c2-019c-eb11-ade6-40b034e2c22b Environment Control true All features pertaining to temperature control on an environment controlled asset, e.g. a reefer container, a reefer truck, a cold storage warehouse, commodity, etc. Variable Temperature Settings The temperature setting can either be fixed (stays the same throughout the whole journey) or variable (changes during the journey). When temperature changes during the journey, then it will have multiple "set points" (modelled via the Temperature Set Point class). When temperature is fixed, then there will be 1 ocurrence of Temperature Set Point only. Temperature Profile Above mentioned temperature settings, namely when they change during journey, can be defaulted via a Temperature Profile. true true Transactional Internal N/A
Container Floor 032eed6e-67ef-eb11-8336-069408b64bc1 Container Interior Fitting true A floor that is installed in a container, e.g. made of bamboo or wood. true false Master Internal N/A
Floor Treatment 090229d4-6aef-eb11-8336-069408b64bc1 Container Interior Fitting true Types of treatment that can be applied to a floor in a container. true false Transactional Internal N/A
Hanger Specification 1b13f66a-47b3-ee11-a1c0-97e99c96f3d2 Container Interior Fitting true Generic hanger specification super class. true true Transactional Internal N/A
Protective Lining 2f3ae100-68ef-eb11-8336-069408b64bc1 Container Interior Fitting true A sheet covering the internal of the container in order to protect the cargo from any dirt or scratching that may come from the inside walls of the container. This is used for example when installing garments on hangers. true false Transactional Internal N/A
Desiccant Bag Type 74b3f70a-888b-eb11-ade5-40b034e2c22b Container Interior Fitting true Moisture absorbent bags that are typically placed in containers with garments to avoid the garments becoming moldy. true false Reference Internal N/A
Protective Lining Type 9297d434-8c8b-eb11-ade5-40b034e2c22b Container Interior Fitting true Typically a plastic wrapping that lines the inside of the container before garments are hung on bars, beams, strings or straps. true false Reference Internal N/A
Partition 9e54f025-5591-eb11-8314-06954a68324f Container Interior Fitting true A divider installed in the container to split e.g. carton boxes and bulk load. true false Reference Internal N/A
Garment On Hanger Direct Bar Specification afd40d3b-be91-eb11-ade6-40b034e2c22b Container Interior Fitting true When hangers are hung directly on the bar this specification can be used to give details. true false Reference Internal N/A
Garment On Hanger Tier b47a5ba6-8b8b-eb11-ade5-40b034e2c22b Container Interior Fitting true Specifies how the garment bars/beams should be installed in the container. Note The term 'Bar' is used synonymously with beam for this class. I.e. if a bar distance is given it is also usable for beams. true false Reference Internal N/A
Desiccant Bag Specification c309cdb9-6391-eb11-8314-06954a68324f Container Interior Fitting true A specification for how desiccant bags are placed for garment on hangers. true false Master Internal N/A
Container Interior Fitting Purpose de0cd58c-428c-eb11-8310-068fa0e84c57 Container Interior Fitting true To indicate clearly what the interior fitting is for. Examples: Garment on Hangers Unknown true true Reference Public N/A
Container Interior Fitting e8da8496-571a-eb11-adcf-40b034e2c22b Container Interior Fitting true Fitting that go inside the container for e.g. garment on hangers or to partition cargo inside the container. Typically used for Garment on Hangers configurations that are sent to warehouse or carrier in preparation for container loading. Examples: Cross beams with straps for garment on hanger Cross beams with strings for garment on hanger Bars for garment on hangers Protective lining inner Protective lining outer Partition Note The term 'Bar' is used synonymously with beam for this class. I.e. if a bar count is given it is also usable for beams. true true Reference Public N/A
Garment On Hanger String Specification eaa9eac4-8b8b-eb11-ade5-40b034e2c22b Container Interior Fitting true Typically a thin string in white color that hangs from a bar or beam in side the container. The string will have knots where the hangers with garment can be hung from. true false Reference Internal N/A
Garment On Hanger Strap Specification ffc138ea-8b8b-eb11-ade5-40b034e2c22b Container Interior Fitting true Typically made of webbing and has sewn loops on so garment hangers can be put in to the loops and hang inside the container. true false Reference Internal N/A
Slot Displacement 2ff93b60-c1e3-eb11-a3d5-a0510b9e9705 Slot Displacement true Any requirements regarding slot displacement, i.e. when cargoes and/or equipments exceed the space within an equipment and/or vehicle. This includes: Excess height over the roof of equipment/ vehicle. Excess length at the front of equipment/ vehicle. Excess length at the rear of equipment/ vehicle. Excess width left. Excess width right. Displaced Slots Count, i.e. number of slots on the vessel that cannot be used ('killed slots') as a result of loading cargo and/or equipment (includes the slot that would have in any case been used had the cargo or equipment have not caused displacement). true true Transactional Internal N/A
Block Stowage Type 503a2bef-a79e-eb11-a3cb-a0510b9e9705 Stowage true A code that indicates how the containers are to be grouped and stowed on the vessel. Some possible values: ABC, AL1, BC1, BC2, BCD, BS1, BS2, BS3, BS4, BS5, BS6, CHI, CP1, CP2, CP3, CP4, DE1, DE3, GE1, GE2, JA1, LA3, LA4, LA8, LE1, LGN, LS1, LS2, LS3, MA1, MA2, MA3, MA6, MA7, MO1, MO2, NW0, NW1, NW2, NWO, PO1, PO2, PS1, PS2, PS3, QQQ, RO1, SS1, TST. true false Reference Internal N/A
Stowage 5bbdb169-58f9-ed11-b82e-44e517a1f1d9 Stowage true Represents the act of stowing objects within/ inside another bigger and containing object. In the context of transport and logistics, this is typically stowing cargo within a container, equipment or vehicle, or stowing containers and equipments within a vehicle. Stowage can have multiple different requirements, according to the specific needs of a shipment, which are specified via this class. Stowage can be both planned or actual. true true Transactional Internal N/A
Stowage Type 79f3b252-d3ea-eb11-a3d6-a0510b9e9705 Stowage true Any typified stowage requirements and/or stowage related instructions. Examples of values: AFH AWAY FROM HEAT (HEAT SENSITIVE) BLK BLOCK STOWAGE PREFERRED DOF DOOR OFF HOT HOT HATCH STOWAGE PREFERRED NOT NOTHING ON TOP OND ON DECK STOW PREFERRED OPD OPEN DOOR (container positioned with access to the door) SHS SHADED STOWAGE PREFERRED TOP TOP UND UNDER DECK STOWAGE PREFERRED O Required On-Deck U Required Under-deck B Both On-Deck and under-deck permitted true false Reference Internal N/A
Fumigation b04f0381-b4fc-e911-80eb-9cd21e38f3a4 Fumigation true Fumigation is a method of pest control, or the removal of harmful micro-organisms, by completely filling an area with gaseous pesticides, or fumigants, to suffocate or poison the pests within. It is used to control pests in buildings, soil, produce, and most importantly during processing of goods to be imported or exported, to prevent transfer of exotic organisms. This method also affects the structure itself, affecting pests that inhabit the physical structure, such as woodborers and drywood termites. Fumigation can be applied to Cargo Packages, Vehicles, Containers and other Equipments, Warehouses, etc. This class will specify Fumigation requirements and details. true true Transactional Internal N/A
Fumigation Substance ed4f0381-b4fc-e911-80eb-9cd21e38f3a4 Fumigation true Contains possible values for substances that may be used in the fumigation process. true false Master Public N/A
Inquiry Milestone 0c4e0381-b4fc-e911-80eb-9cd21e38f3a4 Case Management true Represents a milestone (required step in a customer support process) on a Inquiry. true false Transactional Internal N/A
Case 1a4e0381-b4fc-e911-80eb-9cd21e38f3a4 Case Management true Matter or problem that needs attension and handling. true true Transactional Internal Competitive Strategic Information
Claim 1d4e0381-b4fc-e911-80eb-9cd21e38f3a4 Case Management true An assertion by a Party that a loss has been incurred and that the Enterprise has a responsibility in regard to the provision of recompense. true false Transactional Internal Competitive Strategic Information
Case Status 204e0381-b4fc-e911-80eb-9cd21e38f3a4 Case Management true Classifying the status of a Case Values : * New * Triaged * Qualified * In Progress * Awaiting * Closed Status Codes when Claim: *Potential Claim *Handled (Active) Claim *Paid *Rejected *Cancelled or Withdrawn *Recovery Pursued *Recovery Obtained *Recovery Failed Case Codes for Waiver Draft: Waiver is created, but not submitted to Global Authority Matrix (GAM) for Approval. Typically this status happens when Waiver team are still gathering facts on the reason for the waiver. Request Clarification: The Approver needs further information, before decision on the waiver. Request Clarification By Endorser: The Endorser needs further information, before decision on the waiver. Approved: The Waiver has been approved and the instruction can be passed on to the finance area to issue relevant credit note. Cancelled: Waiver is cancelled - usually occurs if the waiver is a duplicate or incorrectly captured. Denied: The waiver is denied and no credit note will be issued. true false Reference Internal N/A
Milestone Type 284e0381-b4fc-e911-80eb-9cd21e38f3a4 Case Management true Represents a milestone (required step in a customer support process) on a Inquiry. Available values: Triage Qualify Resolve true false Reference Internal N/A
Case Reason 29326d01-aeb9-ed11-b80e-c403a888648f Case Management true The Case reason Examples AB24-Arrival Notice issues AB24-Capacity full AB24-Commercial - Deal filing request not sent by sales AB24-Commercial Incentive AB24-Commercial overbooking AB24-Customs Restriction AB24-Damaged container AB24-Delayed request sent by sales AB24-Discount on top of free time AB24-Donations true false Reference Internal N/A
Claim Amount 2c4e0381-b4fc-e911-80eb-9cd21e38f3a4 Case Management true A Claim holds multiple different amount from the amount that a Customer file to the amount negotiated to be paid The Claim Amount Types are: Claim Filed - Amount filed in US Dollars by claimant. Submitted Offer Claim Paid - Amount agreed in US Dollars with claimant. Claim Pay Out Costs Incurred - The cost incurred of the Survey Estimated Settlement Maximum Liability 3rd Party Amount - Amount persued in US Dollars from 3rd. Party PANDI Amount - Amount paid from the P & I Vessel Insurance true false Transactional Internal Competitive Strategic Information
Inquiry 314e0381-b4fc-e911-80eb-9cd21e38f3a4 Case Management true Logging the activity on a a customer contacting the organisation regarding an issue such as a customers feedback, problem, or question. true true Transactional Internal Competitive Strategic Information
Case Type 444e0381-b4fc-e911-80eb-9cd21e38f3a4 Case Management true Example of Case Types: Inquiry Claim Dispute Waiver Correction Complaint Question Some Case types can be further detailed into subtypes which can be:. Amend Request missing Documentation Request Waiver General Request Complaint Feedback Submit Question Subtypes of Dispute Types used by the business to determine the different Disputes AB24 : (Commercial settlements & Force Majeures) Settlement is applicable when invoice issued is correct and service has been delivered as per Bill of Lading terms but waiver is given as a Goodwill gesture. All Commercial waivers come under this clause. AB30 - PCD - Commercial Price Calculation Date change AB36 : (Disputes (Invoice errors & service failure confirmation on ISR) When Maersk delivers service exactly as agreed with the customer but the invoice is incorrect due to internal process. Maersk recognizes the error through matching and re-pricing through pricing systems or through documentation proof where available or confirmation on the Maersk service/process failure by relevant internal party (via ISR or email in case management). These email or ISRs will be subject to audit by Transaction Quality control team. AB50 (Auctioned Cargo) This section is to waive off the D&D invoices when they are generated after the cargo is auctioned or disposed of, where Freight is Write off If the cargo is for re-selling, then AB24 applies as this still has a commercial approach Approver needs to ensure that the relevant legal documentation is kept ready for audit purposes. E.g., Customs documentation attesting cargo auction / disposal AB54 - Commercial waiver of late payment fees AB55 (Service failure for non-disputed invoices) Service failure is applicable, when invoice issued is correct, however service has not been delivered as per Bill of Lading terms and customer is disputing the charges. Subtype of Claim Shortage of Equipment Cargo Damage Non-Delivery Delay true false Reference Internal N/A
Claim Amount Type 524e0381-b4fc-e911-80eb-9cd21e38f3a4 Case Management true A Claim holds multiple different amount from the amount that a Customer file to the amount negotiated to be paid The Claim Amount Types are: Claim Filed - Amount filed in US Dollars by claimant. Submitted Offer Claim Paid - Amount agreed in US Dollars with claimant. Claim Pay Out Costs Incurred - The cost incurred of the Survey Estimated Settlement Maximum Liability 3rd Party Amount - Amount persued in US Dollars from 3rd. Party PANDI Amount - Amount paid from the P & I Marine Insurance (P&I : Protection & Indemnity for Cargo Liability) true false Reference Internal N/A
Case Root Cause 5679c5ad-3ab8-ed11-b80e-c403a888648f Case Management true Identifies the root cause of the Case Examples for Dispute or Waiver Manifest Issue - the information manifested has some errors in the information RKEM-GCSS interface issue - identifies system issues with regard to reconciliation of date. Rate revised but, BC not sent - a rate was revised, but a new Booking Confirmation was not sent to customer example for Claims Shortage: * Theft & Robbery * Weight Loss / Slackage Non-Delivery* * Lost Overboard * Mis-delivery * Release Without Original B/L Cargo Damage* * Cargo Sweat * Condensation * Weather * Flooding * Hole / Container * Fire * Wrong Packing * Wrong Stuffing * Stuffing Damage * Stripping Damage * Hot-Stuffing * Booking Error * Container Handling Damage * Leakage * Inherent Vice * Latent Defect * Pre-shipment * PSL Exceeded * Wrong Vessel Stowage * Container Off Power * Wrong setting Reefer Unit * Breakdown Reefer Unit Delay: * Bad Weather * Delay by Authorities * Operational Matter * Commercial Matter true false Reference Internal N/A
Dispute 594e0381-b4fc-e911-80eb-9cd21e38f3a4 Case Management true Case concerning disagreement on invoice settlement. true true Transactional Internal Competitive Strategic Information
Case Line 6559d144-5f1f-ee11-b82d-c403a888648f Case Management true A Line in the case, containing the details on the individual issues or charges true false Transactional Internal N/A
Case Outcome 6ed2d316-291f-ee11-b82d-c403a888648f Case Management true The Case outcome example Resolved, Rejected true false Reference Internal N/A
Case Impact 73e41f2a-291f-ee11-b82d-c403a888648f Case Management true The impact of the Case examples High, Medium, Low true false Reference Internal N/A
Waiver 748d7acb-ca1c-ee11-b82d-c403a888648f Case Management true The agreement that identifies the amount of money that does not have to be paid. true true Transactional Internal Competitive Strategic Information
Case Category aef2089d-63c9-ed11-b811-c403a888648f Case Management true Categories created by the business to group the Cases, Classifying and setting a subject to what Customer Contact Case is about. Primary values can be if it related to a shipment: * Booking * Claims * Delivery of Cargo * Documentation * Invoicing * Pre Booking * Transportation of Cargo each these can then again be divided into sub subjects Waiver and Dispute examples are - PAYER_CODE_TO_BE_REVISED - INCORRECT_CHARGE - MDG_REQUIREMENT - REVISION_AS_PER_FCR/HBL/DIVISION/DUE_DATE true false Reference Internal N/A
Case Priority e2ce1a21-291f-ee11-b82d-c403a888648f Case Management true The priority of the Case examples : High, Medium, Low true false Reference Internal N/A
Exception Category 0eb60c3a-5c29-eb11-adcf-40b034e2c22b Business Exception Handling true An Exception Category is specified for a single business data object, e.g. a "Shipper Booking" or a "Cargo Stuffing". Examples: General Booking ExceptionAn exception category for Shipper Booking business object Reason for Late ReceivingA exceptioncategory for Shipper Booking business object true false Reference Internal N/A
Exception Log 4c17e7a8-6229-eb11-adcf-40b034e2c22b Business Exception Handling true An exception entry for a specific business object, e.g. a Shipper Booking. Multiple exceptions logs can be made aganst each business object. They must have an exception category and an exception specfied to indicate their kind. Optionally an exception log can also state the reason for the exception and a status for the exception. Example: During receival of cargo operations found that cargo was missing and could not set the shipper booking to being recevied. Exception Category:Reason for Late Receiving Exception:Quality Control Activities Exception Reason:Cargo Missing Exception Status:Open Remark:Awaiting feedback from shipper Exception Log Value 1:Quantity: 10 Exception Log Value 2:Unit: Carton true false Transactional Internal Competitive Strategic Information
Business Object 82610165-6629-eb11-adcf-40b034e2c22b Business Exception Handling true A business data object is for example "Shipper Booking" or "Cargo Stuffing". true false Transactional Internal Competitive Strategic Information
Exception Status beb1fed4-5f29-eb11-adcf-40b034e2c22b Business Exception Handling true Pre-defined statuses for an Exception Status. Examples: Open Resolved by Shipper Resolved by Consignee Invalid true false Transactional Internal N/A
Exception bed1c646-5c29-eb11-adcf-40b034e2c22b Business Exception Handling true Specifies a specific exception that can occur within an Exception Category. Note that an Exception can "live alone", .i.e. it is not mandatory to have any reasons or statuses associated with the exception. Examples: Late System Update Quality Control Check Skipped Quality Inspection Failed Quality Inspection Passed Quality Control Check Selected - Removal Quality Control Check Skipper - Removal Quality Inspection Fail - Removal Quality Inspection Passed - Removal true true Transactional Internal Competitive Strategic Information
Exception Reason c0d1c646-5c29-eb11-adcf-40b034e2c22b Business Exception Handling true Pre-defined statuses for an Exception Reason. Examples: Wet Carton Deformation Cargo Damaged Cargo Shortage Cargo Overage Cargo Missing Cargo Mismatch Overweight Carton/Set Other true true Transactional Internal N/A
Constraint 39865e98-93d5-eb11-832d-06dde3c572dd Constraint true Could be weight restriction at terminals, restriction on fuel types or dual purpose commodities. Each constraint will be supported by one or more constraint items detailing e.g. where and what is banned/mandated for the constraint. Examples: EU stating that "Maximum sulphur content in fuel" of 0,2% is applicable. This will be a Constraint Item under the fuel type constraint. Dual Purpose commodities, where the corelation between an HS code and a STA code is only specific to a certain country or region. These will be constraint items under a commodity constraint. Allowed combination of locations, e.g. only certain Place of Delivery, First Load Port, Last Discharge Port are allowed to be used together. Setting "roles" for defined areas, i.e. that larger areas are allowed to be used for Place of Receipts or Load Ports. Meaning all locations in the defined area are allowed to be used for what the constraint item defines by a Location Funcation for the defined area(s). true true Master Internal N/A
Constraint Item 623a3a81-b4fc-e911-80eb-9cd21e38f3a4 Constraint true Enables the contraint to be comprised of multiple items which together defines the whole constraint. For example to define the fuel type constraint, the Constraint Items could be as follows: One constraint item being a group of ports that has value type "Maximum sulphur content in fuel" set to value 0,3 and Unit of Measurement set to "Percentage". One constraint item for the defined area EU that has value type "Maximum sulphur content in fuel" set to value 0,2 and Unit of Measurement set to "Percentage". One constraint item for a group of countries that has the fuel type "Heavy fuel oil" setting "IsBanned" to "true". As more and more fuel constraints are introduced, additional Constraint Items will be added. Note on references: A constraint can be be allowing or restricting virtually anything in the operating environment. Therefore it has been chosen to use the reference pattern with typed references to allow for adding "anything" to the contraint for allowance or restrictions. true false Master Internal N/A
Constraint Participant 6f717605-b86b-ed11-a1a4-dac57d1c6c19 Constraint true Represents a "participant" taking part in a constraint, e.g. a specific facility or business defined area. true false Transactional Internal N/A
Constraint Item Type 893a3a81-b4fc-e911-80eb-9cd21e38f3a4 Constraint true Types of constraint values that can apply to e.g. marine container terminal, commodity, defined area etc. or association between any of these. Examples: Maximum weightIn relation to maximum weight of vessel at terminal Maximum sulphur content in fuel ImportIn relation to whether the constraint of e.g. commodities are related to importing into a country ExportIn relation to whether the constraint of e.g. commodities are related to exporting from a country Trans-shipmentIn relation to whether the constraint of e.g. commodities are related to trans-shipping in the country TemperatureIn relation to a commodity that must be shipped at a certain temperature OFAC BlacklistedIn relation to organisation or individuals that the enterprise should not do business with Internal BlacklistedIn relation e.g. blacklisting a customer, note we might still want to use the organization behind as supplier true false Reference Internal N/A
Constraint Type 913a3a81-b4fc-e911-80eb-9cd21e38f3a4 Constraint true A Constraint Type is a set of limitations/mandates imposed for purposes of prohibiting unacceptable practices or ensuring compliance. Examples: Commodity Constraint Document Constraint Fuel Type Constraint Weight Constraint Product Constraint Product Component Constraint Product Feature Constraint Sanction/ Embargo Constraint true false Reference Internal N/A
Risk Location 75201b83-b3ac-11ef-61a3-865a2ac79532 Survey true Location at which the Risk was discovered. The Risk Location may contain a sub location, e.g:when a Risk was found in the Engine Room, with a boiler or part of an engine. true true Transactional Internal N/A
Survey 75201b93-b3ac-11ef-61a3-865a2ac79532 Survey true A Survey is a systematic method of collecting data and insights from a group of respondents to identify potential risks related to a particular subject. This process involves questionnaires and various meetings designed to uncover any potential risks. A survey can be based on a template. If it is, then the template is the survey's parent. true true Transactional Internal N/A
Survey Item 75201bab-b3ac-11ef-61a3-865a2ac79532 Survey true A Survey Item is any part of a Survey. It may refer to a meeting, an interview or to a questionnaire. It can also refer to a question or comment within a questionnaire, which is why it is recursive. Typically, a Survey will consist of a few meetings: * opening meeting * closing meeting * personnel interviews One or more questionnaires will also be part of a survey. Each questionnaire itself consists of a list of questions, organised in sections. Survey Items can be based on a template. Nothing is changed in the transactional instance compared to its equivalent master data class. However, the transactional instance is needed to organise the transactional responses. true true Transactional Internal N/A
Survey Item Response b03f8923-b3ae-11ef-61a3-865a2ac79532 Survey true The response given to one survey item. This can be in the form of free text or as an answer to a multiple choice question. This depends on the value of Survey Item Type, which is related to the Survey Item. true true Transactional Internal N/A
Survey Item Type b03f8928-b3ae-11ef-61a3-865a2ac79532 Survey true Possible types: * Executive Summary * Care for Seafarers * Opening meeting * Personnel interviewed * Closing meeting * Best practices * Compute score * Questionnaire * Multiple choice question * Free text question This is recursive, so that question can be part of questionnaire, for example. true false Reference Internal N/A
Survey Risk b03f8930-b3ae-11ef-61a3-865a2ac79532 Survey true A Survey Risk must be created if: 1. The flag "Is Risk Trigger" is set to "true" in Survey ItemAND 2. The Survey Item Response does not match the Compliant Response as set in the Survey Item true false Reference Internal N/A
Survey Status b03f8938-b3ae-11ef-61a3-865a2ac79532 Survey true Defines the status of a Survey. Statuses are dependent on the Survey Type. Examples: * Requested * Planned * In Progress * Completed * Cancelled true false Reference Internal N/A
Survey Type b03f8940-b3ae-11ef-61a3-865a2ac79532 Survey true Indicates and classifies the type of Survey. Examples of types: * Inspection * Audit * Customer * Internal audit * Navigation assessment * Vessel condition assessment * S&R Survey - VAS * MAS Other Inspections * Internal technical inspection * S&R Survey - MAS true false Reference Internal N/A
Standard Reason Type 85353a81-b4fc-e911-80eb-9cd21e38f3a4 Activity Plan Template true Groups 'Standard Reason' by providing reason type, e.g.: Delay Reject Ommision Missing Execution Rejection during Clear Allocation true false Reference Internal N/A
Work Process Specification 89353a81-b4fc-e911-80eb-9cd21e38f3a4 Activity Plan Template true Specifications for processes and sub-processes are defined in this entity. E.g. some stages of the entire shipping process is called 'Booking', 'Cargo Release', 'Cargo Execution' and so on. A process specification named 'Shipping Process' with these examples of sub-processes can be stored in this entity. Relationships to sub processes are handled via Work Process Specification Sequence class. E.g. 'Cargo Execution' process has 'Discharge', 'Load', 'Vessel Release' as sub-processes. Consumers of these data would mostly use a parent process as identifier for which sub-processes, activities and potentially issues/reasons exist for that entire process. E.g 'Cargo Execution' or 'Online Booking'. true true Transactional Internal N/A
Work Activity Specification 8f353a81-b4fc-e911-80eb-9cd21e38f3a4 Activity Plan Template true An step within a process. In some relations this is referred to as an 'Issue Category' as it is the step where an issue can arise. Examples of activities within processes: Submit Special Cargo Manifest Create Final Load-list Handle Vessel Release Customs Equipment Gate-in Equipment Gate-out Discharge Load true true Transactional Internal N/A
Standard Reason 95353a81-b4fc-e911-80eb-9cd21e38f3a4 Activity Plan Template true Pred-defined standard reasons that can be applied when e.g. raising an issue during Maersk process activities (these could e.g. be Delay Reasons, Activity Handover Reason etc.). Examples of standard reasons could be: Late advice on discrepancies on carrier details Late Receipt of Terminal Data Late for train Cannot find route Rail Issue These standard reasons are for example used by customers, truckers or internal staff to select from when logging actual issues. In other words reasons for things happening during the process activities. The actual issues logged with a reason are kept in transactional solutions and not kept within the master data. The reasons are also used for other purposes, e.g. that an internal user selects a reason if he has to do 'Consult Customer' or 'Handover to country office' activity during executing activities of the process 'Process Shipment'. true false Master Internal N/A
Work Process Activity Specification 9b353a81-b4fc-e911-80eb-9cd21e38f3a4 Activity Plan Template true As work process activities can be reused among processes in different sequences they are related to the work process specification with a class where it is possible to specify their sequence when used in a particular process. true true Reference Internal N/A
Work Activity Specification Output 9e353a81-b4fc-e911-80eb-9cd21e38f3a4 Activity Plan Template true Allows a work activity to define which outputs are produced. true false Reference Internal N/A
Work Activity Specification Input a1353a81-b4fc-e911-80eb-9cd21e38f3a4 Activity Plan Template true Allows a work activity in a process to define which inputs are consumed. true false Reference Internal N/A
Work Activity Type a4353a81-b4fc-e911-80eb-9cd21e38f3a4 Activity Plan Template true Allows for a higher-level grouping or classification of Work Activities. Example: Automated Requires manual intervention true false Reference Internal N/A
Work Process Type a9353a81-b4fc-e911-80eb-9cd21e38f3a4 Activity Plan Template true Allows for a higher-level grouping or classification of Work Process Specifications. Example: Customer Services processes Vehicle maintenance processes true false Reference Internal N/A
Work Process Specification Sequence b0353a81-b4fc-e911-80eb-9cd21e38f3a4 Activity Plan Template true Lists the sequence in which child processes "under" a parent process must be executed. The relationships allows for child processes to also be parent process, creating a tree of processes and in which seqeunce to execute these. For example in the case of Booking Process and Document Process, they both have a sub process of Call Customer. In the Booking Process the sequence is: 1. Open up system 2. Call Customer 3. ... In Document Process: 1. Open up system 2. Identify Problem 3. Call Customer The Work Process Specification for Document Process will have 3 entries in Work Process Specification Sequence. Document Process to Open up system: - Parent Hierarchy Level set to 1 - Child Hierarchy Level set to 2 - Child Sequence set to 1 Document Process to Identify Problem: - Parent Hierarchy Level set to 1 - Child Hierarchy Level set to 2 - Child Sequence set to 2 Document Process to Call Customer: - Parent Hierarchy Level set to 1 - Child Hierarchy Level set to 2 - Child Sequence set to 3 true false Reference Internal N/A
Resolution Routing b3353a81-b4fc-e911-80eb-9cd21e38f3a4 Activity Plan Template true Specifies which team should resolve an issue when something happens, due to a specific Standard Reason. The resolution routing must capture the Standard Reason, the team and the geography that the team covers, e.g. a country and city. true false Transactional Internal N/A
Work Activity Event Type c1353a81-b4fc-e911-80eb-9cd21e38f3a4 Activity Plan Template true Pre-defined codes for work activity events. Examples: Instance Created Instance End Activity In Activity Out Instance Aborted Instance Grabbed Subflow Instance Created true false Reference Internal N/A
Work Activity Status d0353a81-b4fc-e911-80eb-9cd21e38f3a4 Activity Plan Template true Pre-defined activity statuses. Each work activity specification can define a number of allowable statuses that that a work activity can be in when it is actualised. The name is deliberately set to 'Work Activity Status' and excludes the 'specification' as it is not the status for the specification but the status for the activity once it becomes actualized/running. Examples: Not started Selected for execution Suspended Completed Aborted true false Reference Internal N/A
Work Process Status f659702c-dcd7-eb11-832d-06bc7cf3dccf Activity Plan Template true Pre-defined process statuses. Each work process specification can define a number of allowable statuses that tha work process can be in when it is actualised. The name is deliberately set to 'Work Process Status' and excludes the 'specification' as it is not the status for the specification but the status for the process once it becomes actualized/running. For example the work process "Maersk Flow - Booking" could define the following statuses: Submitted Sent To Customer Sent To Carrier Partially Confirmed Confirmed Carrier Rejected Amendment Submitted Amendment Sent to customer Amendment Requested Amendment Rejected Cancel Submitted Cancel Requested Cancelled Delivered true false Reference Internal N/A
Comment 015f0f1d-ff57-ec11-836c-06c8d72459ad Comment true Any specific comments relevant to any party, that one may wish to indicate. The comments may originate from Maersk, or from a 3rd party (typically but not exclusively the customer). Example for Vessel Port Call comment where it is a free-format comment from the master of the vessel for a particular port call at a specific time. I.e. a textfield merging all comments cannot be used for this purpose. Example: From Majestic Maersk at Algeciras port call on Marts 3rd 2016: "Divert vessel from PTM to ALR due to last minute notice from PTM that they can not handle 9 tier high" true false Transactional Internal N/A
Comment Type 2d93bcae-ff57-ec11-836c-06c8d72459ad Comment true Typifies the Comments. Possible types can include for example: External, Internal, Validation Issue or Revision Note. true false Reference Internal N/A
Quality Control Profile 49c6343e-32ae-ec11-8382-0677cd8be49d Quality Control true Specifies how to carry out quality control of something, e.g. a commodity or a container. true false Reference Public N/A
Quality Control b39bfd6f-7f25-ec11-8359-060ba67ce1d5 Quality Control true Logs data about actual quality control performed on items, equipment etc. Quality control parties: It is possible to indicate the party who requested the quality control to be carried out, i.e. the customer who are purchasing the products from the manufacturer. It is also possible to indicate the party who must carry out the quality control. I.e. a pre-production inspection would normally be carried out by the factory. While a container loading inspection could be carried out by the logistics provider in case of LCL and consolidation. true true Transactional Internal N/A
Quality Control Type c4d775da-7f25-ec11-8359-060ba67ce1d5 Quality Control true The types of quality control that can be carried out. Examples: Pre-Production Inspection (PPI) First Article Inspection (FAI) During Production Inspection (DPI) Pre-Shipment Inspection (PSI) Container Loading Inspection (CLI) true false Reference Internal N/A
Work Activity Event be353a81-b4fc-e911-80eb-9cd21e38f3a4 Activity Plan true Captures events that occur as a work activity is performed thereby tracking what has happened to the Work Activity in its lifetime. This is needed because one of the requirements of a workflow is to keep accurate track of all activities that has been executed and how long they were in certain states etc. so as to be able to improve the processes and find bottlenecks in the business processes etc. Examples: Activity instance created Activity instance grabbed (work activity is picked by user) Activity instance un-grabbed Activity instance suspended Activity instance resumed true true Transactional Internal N/A
Work Activity c9353a81-b4fc-e911-80eb-9cd21e38f3a4 Activity Plan true Captures the actual individual activities that were performed within a work process. Examples: Space availability checked for the booking of a particular shipment Intermodal arranged true true Transactional Internal N/A
Work Process d4353a81-b4fc-e911-80eb-9cd21e38f3a4 Activity Plan true Data about the planning and execution of series of tasks/activities required in business processes. The actual performance of a Work Process (such as the performance of a service). Examples: An instance of Process Shipment, i.e., booking an order for a particular shipment. An instance of Shipment Amendment, i.e. a booking is being amended after it has been confirmed. An instance of Cargo Execution. true true Transactional Internal N/A
Instruction 0368a698-99b1-ec11-a3f8-a0510b9e9705 Instruction true Any specific instructions relevant to any party, that one may wish to indicate. The instructions may originate from Maersk, or from a 3rd party (typically but not exclusively the customer). These typically refer to how cargo should be handled or transported, or notes and instructions for transport providers, truck drivers, etc. Examples: Cargo Handling Instructions Dangerous Cargo Handling Instructions Inland and Haulage Instructions Distribution Centre Handling Instructions Instructions for Truck Drivers etc. It's possible to have instructions within instructions. true true Transactional Internal N/A
Instruction Type 0568a698-99b1-ec11-a3f8-a0510b9e9705 Instruction true Typifies the Instructions. Possible types can include (but not exclusively): - Inland/ haulage instructions - DC handling - Cargo handling - Dangerous Cargo handling - instructions for drivers - Advanced Manifest Filing instructions - etc. Instruction types can also have subtypes. Instruction types can also correspond to standard UN instruction types, typically used in EDIFACT. true false Reference Internal N/A
Approval 474f0381-b4fc-e911-80eb-9cd21e38f3a4 Approval true Information about the approval conditions and related statuses, that is associated with another data or business element. This can be, for instance, an approval status for a shipment, or part of a shipment (for some aspect of its progress), a booking, a cargo, a move, etc. See Approval Type for more examples. Approvals that must be made by an external party have an (external) Approval Party Role Type. Examples include: Load Port Operations Transhipment Port Operations Discharge Port Operations VSA Operators Approval Hierarchy/ Composition: Approvals can be composed of other smaller individual approvals. This is the case, for instance, of approval of a dangerous cargo shipment with multiple different dangerous cargo risks (flammable, toxic, etc.), where each risk or commodity type must be individually approved by a different party. Another example is when the approval must be decomposed in smaller different approval steps. true true Transactional Internal N/A
Approval Type 694f0381-b4fc-e911-80eb-9cd21e38f3a4 Approval true Types of approvals, e.g.: Reefer Cargo Booking Dangerous Cargo Booking OOG Cargo Booking Break-Bulk Cargo Booking Credit' 'Freight Auditor Approval Freight Prepaid Approval Freight Collect Approval Credit (Export) Credit (Documentation) Credit (Import) true false Reference Internal N/A
Approval Status a090088b-758a-ec11-a3ed-a0510b9e9705 Approval true An Approval must be in a given status. Because different Approval Types can have different separate sets of Approval Status, it's not possible to have this class as predictable enumeration. Example: Approval Type "Financial Invoice" might have possible approval statuses {open, pending, in progress, closed, cancelled}. While Approval Type "Out of Gauge" might have possible approval statuses {request outstanding, ready for request, requested, approved, approved conditionally, rejected, void}. true false Reference Internal N/A
Deadline Parameter Type 02363a81-b4fc-e911-80eb-9cd21e38f3a4 Deadline true This allows a deadline and its offsets to be based off any necessary business data, e.g. a Commodity Code, Transport Mode, Service, Vessel Schedule etc. The list of identified offset reference types are below, however any additional ones should be able to be added by adding a code/name to a dataset. Cargo Type Commodity Classification Operator Delivery Agreement Type Facility Vessel Port Call Vessel Schedule Cardinal Direction Party Service Transport Mode true false Reference Internal N/A
Deadline Offset 0b363a81-b4fc-e911-80eb-9cd21e38f3a4 Deadline true For example the deadline 'Dangerous Goods Declaration Check for Load (LC)' with global offset to 12 hours, the 12 hours offset is stored here (in minutes). The deadline defintion will always have at least one entry for storing the global offset. In this case the entry will have 'IsGLobalDeadlineOffset' boolean value set to true. It is only allowed to have one 'IsGLobalDeadlineOffset' entry set to true, for each deadline. Another example could be port cut-offs. The deadline 'Port Cut-off' will be defined as a deadline defintion. There will be a global offset in the offset data which will not relate to any particular Facility via deadline offset parameters. Further offsets can then be stored for all other relevant ports throughout the world relating to the master data Facility for those ports. The deadline offset can be based on several types of business data, for example a specific Commodity Code or Transport Mode. The offset can also be based on multiple business data, e.g. a set of commodity codes and some transport modes for which the deadline offset is then valid. These 'offset references' are kept as a list and each of them typed. true false Transactional Internal N/A
Deadline Occurrence 5a8be6a8-998e-ea11-adab-40b034e2c22b Deadline true A specific instance of a deadline which has been given a timestamp either calculated from an offset or simply input by business for a certain data object (e.g. a container load plan, carrier booking or shipping instruction). The "Deadline Occurance" is a re-usable data object that can be utilized across multiple data objects. For example a VGM cut-off can be calculated based on a deadline offset and stored in the deadline occurance and then associated to a cargo stuffing. The indication of which deadline the occurance is for is handled via the realtionship to "Deadline" which is a list of deadlines available to use. true false Transactional Internal N/A
Deadline 96db6ed4-a38e-ea11-adab-40b034e2c22b Deadline true List of Deadlines, their code, name and a description. Examples: Container Yard Cut-off: When is the latest time a container can be delivered to the container yard. Site or Facility based Deadline. Port Cut-off: When does the container need to be at the port in order to make it on a vessel leaving that port. Site or Facility based Deadline. Shipping Instruction Cut-off: When must the shipping instructions latest be sent to the carrier. Operator, Site, Facility parameters could be relevant. Amendments Cut-off: When is the latest time that a data object, e.g. Carrier Booking, can be amended before it is too late. For ocean related carrier bookings suc cut-off would be based on vessel schedule or vessel port call. Verified Gross Mass Filing Cut-off: The latest time that the VGM filing can be done if a container needs to be onboard the vessel it is intended for. Dangerous Goods Declaration Check for Load (LC): A deadline for when the DG declaration needs to be performed latest in order to allow the container onboard. Manifest Submission Deadline: deadline for manifest submission to port authorities. true true Master Public N/A
Deadline Offset Type e8353a81-b4fc-e911-80eb-9cd21e38f3a4 Deadline true The offset type is applicable for all offsets that are set against the deadline. I.e. you cannot mix multiple offset kinds against the same deadline - if you have VGM cut-off defined as a deadline the offset type for all offsets will be 'Deadline'. Examples: DEA - DeadlineIndicates that a deadline is offset against another deadline. Cut-offs are also considered deadlines. Any deadline which is a cut-off can be named accordingly, e.g. "Verified Gross Mass Cut-off" ETA - Estimated Time of Arrival ETD - Estimated Time of Departure true false Master Internal N/A
Deadline Parameter ec353a81-b4fc-e911-80eb-9cd21e38f3a4 Deadline true Specifies which of the parameters are mandatory input and which are not via enumeration. Service, Operator, Transport Mode etc. together with each parameters precedence in order to identify the importance of the parameter. Note: The reference to the actual parameter (e.g. a Vessel Schedule Number) is manged via Deadline Offset Parameter. true false Master Internal N/A
Deadline Group f0353a81-b4fc-e911-80eb-9cd21e38f3a4 Deadline true Grouping of Deadlines for a specific purpose or e.g. Marine Deadlines are all based on a Vessel Schedule for a Vessel like ETA/ETD where other Deadlines can be based on a transaction time. true false Master Internal N/A
Deadline Offset Parameter f4cfb7c6-5cc7-eb11-8321-067bbd788b59 Deadline true The relationship to the actual data is kept here, for example if a Deadline Offset is related to multiple vessel schedules the vessel schedule numbers will in Deadline Offset Parameter and they will be of type "Vessel Schedule". Vessel Schedule example: These can be any form of deadlines that are associated to the vessel schedule in its entirety. E.g. if a VGM cut-off should be defined for the entire schedule (e.g. be applied to all port calls) the vessel schedule number can be kept here. Vessel Port Call These can be any form of deadlines or cut-offs that are associated to the specific vessel port call. For example if a carrier booking or shipping instruction amendment cut-off is based on when the vessel leaves the port that the carrier booking wants to use as port of loading, vessel port call can be identified here with the port code in the Deadline Offset Parameter and the type "Vessel Port Call". true false Master Internal N/A
Deadline Definition f5353a81-b4fc-e911-80eb-9cd21e38f3a4 Deadline true The definition of a deadline (stored in Deadline Definition) is together with its relative time-offset (stored in Deadline Offset) used to calculate an occurance at a date/time on, after or before which a specified kind of event must occur (can be stored in Deadline Occurance). The code and name of the Deadline itself is kept in Deadline. Specific example: For example delivery of an empty container must occur a minimum of 120 minutes before the gate-closure time of a specified customer site. This entity defines the deadline, its name and type and how the deadline is associated to possibly multiple deadline offsets. E.g. the deadline named 'Dangerous Goods Declaration Check for Load (LC)' will be stored as the Deadline Name and set up as follow: 'Deadline Offset Type' set to 'ETA' 'Deadline Type' set to 'Earliest Start' 'Deadline Parameters' entries for 'Site' (Mandatory), Service' (Not mandatory ) and 'Operator' (Not mandatory) The deadline entry itself will together with the parameters for the deadline define how the deadline rules can be set and maintained for the deadline in the offset. Each entry in the offset will then combine Site, Service and Operator to create offsets that are relevant for the combinations. Other examples: CYCO - Container Yard Cut-offWhen is the latest time a container can be delivered to the container yard. Site or Facility based Deadline. POCO - Port Cut-offWhen does the container need to be at the port in order to make it on a vessel leaving that port. Site or Facility based Deadline. SICO - Shipping Instruction Cut-offWhen must the shipping instructions latest be sent to the carrier. Operator, Site, Facility parameters could be relevant. See "Deadline" class documentation for further examples. true false Master Internal N/A
Bucket Band 0a500381-b4fc-e911-80eb-9cd21e38f3a4 Uptake Plan true Bucket Band Specifies the Bucket Band of the related Bucket. Possible Values are: Green 1 Green 2 Green 3 Yellow 1 Yellow 2 Yellow 3 Orange 1 Orange 2 Orange 3 Red The values are combination of the colours Green, Yellow, Orange and Red, plus a number from 1-3, with exception of Red, which has no number, Shipments in Green Buckets are the most desirable from a Yield perspective. Shipments in Yellow Buckets are somewhat desirable from a Yield perspective. Shipments in Orange Buckets are the least desirable from a Yield perspective. Shipments in the Red Bucket are undesirable from a Yield perspective. true false Reference Internal N/A
Bucket 0e500381-b4fc-e911-80eb-9cd21e38f3a4 Uptake Plan true Bucket An instance of a categorized threshold band, used for categorizing cargo based on its Contribution Yield (CY), and determining if the cargo, or booking, can therefore be accepted (i.e. it's profitability is worthwhile). See class "Bucket Set" documentation for more details. NOTE: a Bucket belonging to the same Bucket Set cannot have the same Bucket Band of another Bucket belonging to the same Bucket Set. true true Transactional Internal N/A
Bucket Set 18500381-b4fc-e911-80eb-9cd21e38f3a4 Uptake Plan true Bucket Set A set of categorized threshold bands, called "buckets", used for categorizing cargo based on its Contribution Yield (CY), and determining if the cargo, or booking, can therefore be accepted (i.e. it's profitability is worthwhile). There is a Bucket Set for each unique combination of Route, Service, Cargo Type and Vessel Port Call, i.e. each port call on a vessel schedule has a Bucket Set for each Cargo Type, for a specific Route and Service. Sometimes there are also different Bucket Sets for specific Equipment SIze Types (within the above mentioned unique combination). Buckets within the same Bucket Set are organized in bands (i.e. levels), from lowest bucket to highest bucket, i.e. from the highest CY threshold bucket to the lowest CY threshold bucket. Each bucket contains: Bucket Band Code: identifying what is the band/ level of the bucket within the highest to lowest structure. Typically bands are identified with a colour + a number, from Green 1 to Red. Contribution Yield Threshold: a monetary value indicating the yield threshold (lower limit) for that band. Cargo Distribution Percentage: percentage of cargo volumes falling into that band. Depending on settings, this could either be a percentage of total equioment value (in either TEU or FFE), or a percentage of total weight (typically in metric tons). Example: A customer places a booking, with Port of Loading in Hong Kong, with a CY of 3000 USD. Checking the applicable Bucket Set, the threshold of Green 1 is 3500 USD, so booking cannot be accepted for a Green 1 bucket. But threshould of Green 2 is 2000 USD, so booking can be accepted for a Green 2 bucket. But cargo distribution percentage for Green 2 is 15%. So, booking can only be accepted if Green 2 is still not "full", i.e. it hasn't reach 15% yet. true true Transactional Internal N/A
Shipping Commitment Consumption 700b919f-91fe-eb11-a3d6-a0510b9e9705 Shipment Consumption true Shipping Commitment Consumption The total record of the equipment units (typically containers) that have been used (i.e. "consumed") for a given Shipping Commitment, therefore adding up Shipping Consumptions that relate to the same Shipping Commitment. Equipment Unit Count The counting of equipment units is typically done in FFE (forty-feet equivalent), but MIM allows it to be counted in TEU as well, via relationship with "Equipment Measure Unit". Hence why equipment unit attribute fields are of type decimal: to allow for .5 values when using FFE. Equipment Units Consumed Outside Commitment Equipment units can be consumed outside of what was previously committed either because: the total number of equipment units exceeds the number that was committed/ agreed. some units consumed don't match the criteria of the commitmment/ agreement. For instance, they are units of an non-agreed equipment type, they are units that were used for a non-agreed cargo type, etc. true true Transactional Internal N/A
Uptake Validation Outcome 9a4d0381-b4fc-e911-80eb-9cd21e38f3a4 Shipment Consumption true Uptake Validation Outcome Provides details on the result of the Uptake Validation by uptake management. Possible Codes and Values: OP Online Pricing IA Insufficient Contract Allocation YA WS Yield Accepted YA WS Non-Yield Accepted MX Mixed NS No Steering MX Mixed EC Elite Customer MX Mixed FTS Full Trade Switch CC CC/CC Shipment BB WS BB/BB Shipment YR Yield Rejected OG WS OOG Containers YA Non-Yield Accepted MX Mixed NO WS Vessel not open YA Yield Accepted DC Steered Port Closed CHS Capacity Hard Stop YA WS Yield Accepted OG OOG Containers HA Historically Accepted MX Mixed YR WS Non-Yield Rejected YR WS Yield Rejected YA Yield Accepted NO Vessel not open FC Fully Committed YA Non-Yield Accepted MB MLL Booking YA WS Non-Yield Accepted YR Non-Yield Rejected BB BB/BB Shipment true false Reference Internal N/A
Shipment Consumption 9e4d0381-b4fc-e911-80eb-9cd21e38f3a4 Shipment Consumption true Shipment Consumption A record of the equipment units (typically containers) that have been used (i.e. "consumed") for a given Shipment. Typically this record of "consumed equipment units" is done against an existing commitment agreement, whereby the customer has agreed upfront that he will use a given number of equipment units. The Shipment Consumption will be the record of the actual consumer units versus the ones committed to. The Shipment Consumption will also hold details on Contribution Yield (CY) acceptance, i.e. if the yield obtained with the related Shipment is within acceptable values by Maersk. Yield validation is directly linked to the business area of Uptake Management. Equipment Unit Count The counting of equipment units is typically done in FFE (forty-feet equivalent), but MIM allows it to be counted in TEU as well, via relationship with "Equipment Measure Unit". Hence why equipment unit attribute fields are of type decimal: to allow for .5 values when using FFE. Equipment Units Consumed Outside Commitment Equipment units can be consumed outside of what was previously committed either because: the total number of equipment units exceeds the number that was committed/ agreed. some units consumed don't match the criteria of the commitmment/ agreement. For instance, they are units of an non-agreed equipment type, they are units that were used for a non-agreed cargo type, etc. true true Transactional Internal N/A
Shipment Equipment Consumption fd63eedf-e900-ec11-a3d7-a0510b9e9705 Shipment Consumption true Shipment Equipment Consumption The breaking down of the Shipment Consumption per Equipment Size Type, i.e. there shall be 1 Shipment Equipment Consumption instance, within same Shipment Consumption, for each different Equipment Size Type that was used in the related Shipment. Equipment Unit Count The counting of equipment units is typically done in FFE (forty-feet equivalent), but MIM allows it to be counted in TEU as well, via relationship with "Equipment Measure Unit". Hence why equipment unit attribute fields are of type decimal: to allow for .5 values when using FFE. Equipment Units Consumed Outside Commitment Equipment units can be consumed outside of what was previously committed either because: the total number of equipment units exceeds the number that was committed/ agreed. some units consumed don't match the criteria of the commitmment/ agreement. For instance, they are units of an non-agreed equipment type, they are units that were used for a non-agreed cargo type, etc. true true Transactional Internal N/A
Empty Repositioning Order Line 5f4e0381-b4fc-e911-80eb-9cd21e38f3a4 Empty Repositioning Order true An Operational Transport Order can consist of a number of containers possibly within different Container Groups. Each Container Group is covered by an Operational Transport Item true false Transactional Internal N/A
Empty Repositioning Order 654e0381-b4fc-e911-80eb-9cd21e38f3a4 Empty Repositioning Order true A requirement for operational activity to move Equipment from one pool to another pool. Also Know as an Order To Transfer (OTT). It is a Vessel/Voyage combination or a simple corridor defined by Load port and Discharge port consisting of a number of containers possibly within different Container Groups (sub-types). An OTT can exist in the planning phase or it can have been executed i.e. it has already been loaded on a vessel. true true Transactional Internal N/A
Ocean Allocation 1b0c59ef-983d-ef11-a1c5-f3ef5fbf2395 Transport Allocation true An allocation of a specific number of containers and their unit, or a percentage, for a specific carrier on a specific transportation lane (port of loading to port of discharge). true true Transactional Internal N/A
Transport Allocation Group 3c9736a1-282e-ef11-a1c5-f3ef5fbf2395 Transport Allocation true A group of parties that are relevant to the carrier allocation. true false Master Confidential Competitive Strategic Information
Transport Allocation b03b87cd-272e-ef11-a1c5-f3ef5fbf2395 Transport Allocation true A transport allocation is a setup for particular parties that can specify how many containers should be allocated on certain ocean lanes in a certain time frame. It can alsocontain information about a party's carrier ranking, to prioritse carrier selection. true true Master Confidential Competitive Strategic Information
Ocean Allocation Consumption fba901eb-9d3d-ef11-a1c5-f3ef5fbf2395 Transport Allocation true An individual consumption of an ocean allocation, specific for a certain party. true false Transactional Internal N/A
Capacity Measurement Group 1bb55ba6-7d50-ef11-a1c7-c5eaed93d8bd Capacity true true false Reference Internal N/A
Capacity 34c2095c-15a5-ec11-8382-060656193b39 Capacity true General Capacities General capacity concept to support Vehicle-, Facility-, Network-, and Agreement Capacity. A capacity value is given in the attribute 'Value'. It is mandatory to supply a 'Capacity Type', e.g. 'Facility Capacity' and a 'Capacity Measurement', e.g. 'Container Handling Count'. The unit, e.g. TEU or FFE, of the 'Container Handling Count' is given via the 'Unit of Measurement'. Example: Logging an estimated Network Capacity in TEU, based on bookings received that will have containers on a specific vessel leg. Value: 100 Unit of Measurement: Twenty foot Equivalent Unit Capacity Type: Network Capacity Capacity Measurement: Container Count Bookings Capacity Utilisation: Utilised Capacity Scope: Estimated Capacities for Facilities and Storage Any capacity about a facility, areas within facility or capacities within the facility's available timings.. Example for Capacity wihtin a Facility Availability: A given warehouse during its opening hours has a capacity of '10', 'Forty Foot Equivalent Unit' for 'Container Unloading Count' for customer 'BENIKEHQ' Examples of Capacity for Facility Storages: Area capacity of the storage location in terms of cubic meters Area capacity saleable in terms of cubic meters Storage capacity in terms of cubic meters Storage capacity saleable in terms of cubic meters Capacities for Vehicles Capacity information about vessels, trucks, aircrafts, trailers etc. Note that such capacities is not only for containers in terms of TEU and FFE but can also be fuel-, ballast tanks-, fresh water capacity and so forth. true true Master Confidential Competitive Strategic Information
Capacity Measurement 3efd9a2a-bca8-ec11-8382-06d9560b963b Capacity true Defines the measurements that a capacity can be logged for. The measurement can be things like Container Count, Reefer Plug Count, Volume, Gross Weight, Loading Dock Count etc. The measurement is named in singular noun phrase and a code uniquely identifying it must be defined for each. A Capacity Measurement is defined for a specific Capacity Type so that all measurements for a Capacity Type is grouped together. For example, all capacity measurements relevant for vehicles are grouped by Vehicle Capacity. Below are examples of capacity measurements for each capacity type. Capacity Measurements for Vehicle Capacity Maersk Exclusive Container Count This is used for vessels which takes part in a vessel sharing agreement. Effective Slot Count For example taking account of maximum physical capacity of a Vessel according to its design specification, as modified by factors such as lost / killed slots due to break bulk or out of gauge cargo. Truck Haulage Volume Fuel Volume Lube Oil Volume People Count Liquid Volume Liquid Gas Volume Oil Volume Ballast Tank Count Fresh Water Tank Count Salt Water Ballast Tank Count Reefer Container CountReefer Container Count for example expressed in terms of TEU describes the capacity of reefer containers on a vessel Container CountContainer Count for example expressed in terms of TEU to describe the capacity of container ships. Reefer Plug CountTotal Number of Reefer Plugs available on a vessel. Container 14 Tons CountA maximum container load capacity if all containers average 14-ton total weight - used with TEU unit of measurement. Crane Lifting WeightUsed for indicating the crane capacity available on vessel, typically in metric tonnes. Capacity Measurement for Facility Capacity Loading Dock Count Slot Count Receiving Door Count Receiving Ramp Count Container Unloading Count Container Loading Count Container Handling Count Package Handling Count Container CountContainer Count for example expressed in terms of TEU to describe the capacity container terminals. Capacity Measurement for Network Capacity Container Count Maximum Container Count Total Container Count Additional Container Count Sold Back Container Count BookingsAn estimated capacity based on bookings taken Container Count Bookings ConfirmedAn estimated capacity based on bookings confirmed Container Count PoR DepartedAn estimated capacity based on number of containers known to have left the place of receipt Container Count PoL ArrivedAn estimated capacity based on number of containers known to have arrived at the load terminal Container Count LoadedAn actual capacity based on containers loaded Container Volume Container Total Gross Weight Reefer Plug Count Gross Weight Total Gross Weight Maixmum Capacity Measurement for Agreement Capacity Capacity Allocated to a String on a 'pay as used' basis Capacity Allocated to a String under a Slot Charter Agreement Capacity Allocated for a Partner Operator under a Vessel Sharing Agreement Capacity Allocated to the Enterprise under a Vessel Sharing Agreement Capacity Allocated for Lead String Cargo to be loaded at a particular Load Port at the start of a Dated leg to which the Network Connection Capacity is associated (Unallocated Capacity available to the Lead String is not a logical attribute, but is derivable by subtracting all Allocated Capacity from Effective Capacity) Capacity Committed in a two way arrangement in which the Customer commits to place a certain amout of Cargo transport business with the Enterprise, and the Enterprise commits to carry the agreed amount of Cargo The Network Connection Capacity Types are 'unit agnostic'. For example, capacity of type 'Available to a String under a Slot Charter Agreement' could refer to '20ft Slot's, '40ft Slots', or 'Kilograms' true false Reference Public N/A
Network Capacity a3510381-b4fc-e911-80eb-9cd21e38f3a4 Capacity true A type of capacity that can be associated with transport networks or links in networks. This could be capacities that are defined as part of an entire service, for specific transport legs (scheduled or planned). Service using Network Capacity Keeps nominal capacity information, summarized at the Service level (e.g. volume, reefer plug count, weight). These are average weekly capacity calculations for all vehicles on the service. If the weeks are actualised the Time Period is used, if the weeks are abstract the Unit Of Measurement is used together with the Time Frame attribute. true true Transactional Confidential Competitive Strategic Information
Agreement Capacity bc64fdc3-e0a8-ec11-8382-069336f3048f Capacity true All capacities that are defined as part of agreements made for e.g. Slot Charter Agreements or Vessel Sharing Agreements. The Agreement Capacity may have associations with one or more of: String Vessel Sharing Agreement Line (VSA line) Slot Charter Agreement Commitment Line (SCA commitment line) Shipping Commitment Line (SC line) For example, an Agreement Capacity may specify a number of forty foot equivalent unit Container Slot Count, allocated to a String under a Slot Charter Agreement. If so, the Agreement Capacity has a relationship with the relevant SCA commitment line under which the capacity has been purchased. true true Master Confidential Competitive Strategic Information
Dangerous Cargo Emergency Contact a866f594-c269-ea11-a3a9-a0510b9e9705 Dangerous Cargo true It's always mandatory for Dangerous Cargo to have at least 1 occurrence of a contact information for emergency cases. This emergency contact infromation must be either provided by Customer, Shipper or Consignee, and can come in either a: Unstructured Format: i.e. free text, and then all information is stored in field "Emergency Contact Information". Structured Format: whereby these fields will be used: - Person Name (mandatory) - Phone (mandatory) - Fax (optional) - Mobile (optional) - Email (optional) - Contact Information (optional -- can still be used for any additional free text) If structured format is followed, then 2 options can be followed: data is considered master data from "Party Role Type" = "Dangerous Cargo Emergency Contact Information Party" data is considered transactional and no relationship to "Party Role Type" exists. This is because "Dangerous Cargo Emergency Contact" can be different for every shipment within a customer, so storing it all the time as master data becomes meaningless and inefficient. true true Transactional Public N/A
Dangerous Cargo Information d401d766-0d53-ea11-a3a2-a0510b9e9705 Dangerous Cargo true This class represents the ACTUAL set of dangerous cargo information that must go together with Customer Product, Cargo Package, "Lines" (i.e. Shipment Line, Customer Order Line, etc.), Transport Leg, Carrier Booking, or "Headers" (i.e. Shipment, Transport Document, etc.). true true Transactional Internal Competitive Strategic Information
Cargo Classification Type 2d393a81-b4fc-e911-80eb-9cd21e38f3a4 Cargo Type true Cargo Classification Type defines characteristics of cargo in order to distinguish if special considerations apply for handling. Examples: US Military (NON UNIT MOVE) US Gov't Military HHG's (NON FLAG) Veterinary Cargo Not Veterinary Cargo US Gov't Food Aid US Military Multimodal (MM) US Gov't EU Exempt Aid Cargo US Gov't Project (GPJ) US Military (USM) Emergency Relief Cargo US Gov't Military HHG's (US FLAG) Military Cargo US Gov Project NON SECURE/NON FLAG US Gov't EAR99 US Gov't Military Household Goods (MHG) US Govt Project (US FLAG) Not Emergency Relief Cargo US Military Personally Owned Vehicles (POV) US Gov't Food Aid (ADS) US Military (UNIT MOVE) US Foreign Military Sales (FMS) US Gov't Project (SECURE & US Flag) Special Commodities (SPC) US Govt Project (SECURE) US Gov't ITAR Regulated true false Reference Internal N/A
Cargo Type 35393a81-b4fc-e911-80eb-9cd21e38f3a4 Cargo Type true A cargo characteristic that is relevant to transport order execution. Each characteristic is also categorised as either 'Standard' or 'Special'. Examples of Cargo Types and Standard/Special categorisations are: Dry - (Standard) Live Reefer - (Special) Dangerous (often also referred to as Hazardous) - (Special) Out Of Gauge (OOG) - (Special) Break Bulk - (Special) Military Additional examples of Cargo Types, used by Logistics and Services: N - Normal - Used in case we do not have any special requirement for the account F - Flat pack D - Dangerous cargo M - Mixed/other G - Garment on hangers H - Hanger on Flatpack - Stored in a big carton, in which cargo is hanging inside R - Reefer Hierarchy: Hierarchies are allowed, to allow both for categorisation and/or sub-specification of types. Higher-level categorisation of Cargo Type, into the following two classes: Standard Special Note: Not all instances of Cargo Type have to be classified into this higher-level classification. true true Reference Public N/A
Commodity Classification Correlation Purpose 70393a81-b4fc-e911-80eb-9cd21e38f3a4 Commodity Classification true Any instance of a Commodity Classification Correlation - which joins two Commodity Classifications togather - must nominate one of the possible reasons for its existence (purpose) from this list: Suggested possible purposes are: "replaces" "is equivalent of" "links to a potential Dual Purpose" true false Reference Public N/A
Commodity Classification Measurement 74393a81-b4fc-e911-80eb-9cd21e38f3a4 Commodity Classification true Specifies measurements relevant for a specific commodity using a specific certain equipment size-type for a specific cargo type. Example: Commodity Classification09.05.10 - Vanilla, Neither crushed nor ground Cargo TypeDry (Standard) Equipment Size Type45 High Cube true false Master Public N/A
Commodity Group a4393a81-b4fc-e911-80eb-9cd21e38f3a4 Commodity Classification true A group that is used to bundle certain commodities together. Example of groups: DAIRY PRODUCTS NON-FROZEN GRAIN, FLCOUR, SEED & PULSES SCRAP METAL true false Master Public N/A
Commodity Group Purpose b9393a81-b4fc-e911-80eb-9cd21e38f3a4 Commodity Classification true Used for assigning a purpose to Commodity Groups, e.g. 'Pricing Group'. Each Commodity Group are specifically typed for one purpose - e.g. groups commodities together for the purpose of pricing. This can be used in for example rate systems to then set prices from. true false Reference Public N/A
Commodity Coding System be393a81-b4fc-e911-80eb-9cd21e38f3a4 Commodity Classification true As there exists several commodity coding systems that are used in different places of the worl it is necessary to be able to assign the commodities to their respective system. Examples of commodity coding systems: HS - Harmonized System from WCOHarmonized Commodity Description and Coding System containing 6 digits. TARIC - Integrated Tariff of the European CommunitiesBuilds on the HS and adds additional 2 digits. EZT - German Custom TariffBuilds on the TARIC and adds 1 additional digit to a total of 11 digits. UK Trade TariffBuilds on HS and adds 4 digits. HTSUS - Harmonized Tariff Schedule of the United StatesBuilds on the HS and adds 4 digits UNSPSC - United Nations Standard Products and Services CodeHas its own commodity codes which do not align to HS WA - Wassenaar Arrangement Munitions ListCovering most European countries, USA, Australia, Russia etc. It is an arms List, containing 22 main entries on items designed for military use with categories such as:- Small Arms & Light Weapons (and related ammunition)- Tanks and other Military Armed Vehicles- Combat Vessels (surface or underwater)- Armoured/Protective Equipment- Aircraft & Unmanned Airborne Vehicles, Aero Wassenaar Arrangement for dual-use goodsClassifying dual-use goods and technologies, which identifies specific commodities via its "Export Classification Control Number" (ECCN) - sometimes also known as the "Category Code" - a five-character code (eg 1A002, 4D003, or 9E102), whose first character defines the "category" as follows:- Category 0 Nuclear Materials, Facilities and Equipment- Category 1 Materials, Chemicals, Microorganism and Toxins- Category 2 Material Processing- Category 3 Electronics- Category 4 Computers- Category 5 Part 1 Telecommunications- Category 5 Part 2 Information Security- Category 6 Sensors and Lasers- Category 7 Navigation and Avionics- Category 8 Marine- Category 9 Propulsion STA - 2010 "Strategic Trade Act"A number of countries, such as Malaysia, publishes a "Strategic Items" list covering Dual Use, which appears to be utilising the same WA, EU-issued, five-character ECCN Maersk will also have its own internal commodity coding system, this is the case for AFLS for example where pricing is based off an HS6 like system but with certain commodity groups and additional commodity codes for "Project Cargo" or "Diplomatic Cargo". References: http://www.unspsc.org/, http://en.wikipedia.org/wiki/Harmonized_System, http://en.wikipedia.org/wiki/Taric_code, http://en.wikipedia.org/wiki/Harmonized_Tariff_Schedule_for_the_United_States Note on commodity system tiers: Most commodity coding systems uses levels referred to as tiers to make a hierarchy of commodity codes. Example: HS - Harmonised System has three tiers which are called "Chapter" (level 1), "Heading" (level 2) and "Subheading" (level 3). UNSPSC - the tiers would be 'Segment' (level 1), 'Family' (level 2) and 'Class' (level 3), "Commodity" (level 4), and optionally "Business Function" (level 5). WA for dual-use codes - tiers would be 'Technical Category' (level 1, character-position 1), 'Product Group' (level 2, character-position 2), 'Regime Origin' (level 3, character-position 3) and 'Item Number' (level 4, character-positions 4 and 5). Note that 'Technical Category' is a number between 0 and 9 meaning:0 = Nuclear Materials, Facilities and Equipment 1 = Materials, Chemicals, Microorganism and Toxins 2 = Material Processing 3 = Electronics 4 = Computers5 - Part 1 = Telecommunications 5 - Part 2 = Information Security 6 = Sensors and Lasers 7 = Navigation and Avionics 8 = Marine 9 = Propulsion true false Reference Public N/A
Commodity Classification Correlation c4393a81-b4fc-e911-80eb-9cd21e38f3a4 Commodity Classification true One commodity's code, name and description can be substituted/linked by another commodity's code, name and description, this is e.g. the case when some commodity codes of a commodity coding system is substituted with commodity codes that is specified by Maersk. Another example is the correlation between HS codes and STA codes, also referred to as dual-use codes or dual purpose codes. Another example is the issue of correlation tables when authorities issues new versions of their commodity codes. The WCO has for example issued correlation tables between 2012 and 2017 versions of their commodity codes including notes on why these are correlated. true false Master Public N/A
Commodity Classification cb393a81-b4fc-e911-80eb-9cd21e38f3a4 Commodity Classification true A classification of goods or products. Encapsulates all possible commodity codes from all of the different Commodity Coding Systems. For example the set of Harmonized (HS six-character, sometimes abbreviated to HS6) commodity codes and their corresponding names will sit alongside (often similar) sets of commodity codes from the likes of TARIC and UNSPSC. These classifications will also potentially occupy different tiers in their respective hierarchies, from top-level groups like "Live Animals" (chapter "01" in the HS system) through middle-tier "Other live animals" (chapter/heading "01.06" in the HS system) to fine-granularity classifications such as "Birds of prey" (chapter/heading/subheading "01.06.31" in the HS system). Note: In Maersk designed commodity systems like the one for AFLS there exists commodity codes for things like: Diplomatic Cargo, non US flag Diplomatic Cargo, US flag Project Cargo, non US flag Project Cargo, US flag true true Master Public N/A
Commodity Measurement 057564c2-12ab-ec11-8382-061907b0b249 Commodity true Information about a commodity's various units of measure (UoM). Only one active Commodity Measurement is allowed per conversion factor for a Commodity. The units can be meter, kilogram etc. but can also be related to package attributes, which is why the cargo package specification is related to the commodity measurement. Scenario Some customers have different commodity measurements for the same commodity. The commodity might be shoes, but the measurement for inbound receiving could be each/carton/box etc. and have associated handling, load and other details associated for that measurement. true false Master Public N/A
Customer Product Identifier 34651a71-0f17-ea11-ad8b-40b034e2c22b Commodity true In retail vertical these are typically called style or size code and numbers and are data coming from the customer that helps uniquely identify the product for that customer. Example: For a pair of jeans it might be: Style 1: W32 Style 2: L34 Mapping this to the Customer Product Identifier: Sequence: 1 Name: Style Value: W32 Description: null Sequence: 2 Name: Style Value: L34 Description: null Example from Primark: In the JSON a style code (9210526) and style description (null) is present. Mapping this would become as follows: Sequence: 1 Name: Style Value: 9210526 Description: null Note on Shipper system: In Maersk Shipper these fields are called "Category" and are available from 1-4. When the Purchase Order Line comes in via interface the Style 1-4 is mapped to the Category 1-4 fields in Shipper. true false Transactional Internal Competitive Strategic Information
Trace Control 7b1db61a-4eaa-ec11-8382-06f67abeaacb Commodity true Specifies how the commodity must be traced when handled in warehouse / facility. E.g. that serial number of the commodity must be traced when coming inbound. true false Master Public N/A
Commodity Item 90e3ccdc-c136-ec11-835e-06e53d9d360b Commodity true Represents a single commodity item, i.e. the physical object itself. This could be a pair of shoes, Xmas tree, wooden desk etc. Most times when these individual items are represented as data it is because they can be uniquely identified e.g. via a barcode, RFID or the like. true false Transactional Internal N/A
Customer Product 9c5a1982-fb16-ea11-ad8b-40b034e2c22b Commodity true Represents master data about a product which is bought, sold or produced by a vendor of a Maersk customer. This could be product data for any vertical: Retail: frames, Xmas trees etc. Apparel: Shoes, tshirts etc. Chemical: Barrels of acids, oil etc. true true Transactional Internal Competitive Strategic Information
Commodity Symbol dd8a8c01-f2bd-11ef-3a77-922eb47883a8 Commodity true A symbol or pictogram identifying the commodity - for example if the commodity is t-shirts the symbol will be a 2 dimensional picture of a black and white t-shirt. true false Reference Internal N/A
Commodity e16e67ca-c136-ec11-835e-06e53d9d360b Commodity true Master data about any kind of product that can be shipped, stored, moved etc. Note: This is also referred to as a stock item in Storage and Distribution. Absence of Gross Weight and Gross Volume Commodity has no gross weight because this level is just the commodity and there is no cargo package. For same reason, volume here refers to volume of commodity and there is no need from gross or net volume. true false Master Internal N/A
Universal Product Code f4a901c3-e051-ea11-ad9c-40b034e2c22b Commodity true Universal Product Codes are used for generating barcodes. To address the need for having multiple different universal product codes associated with a product, this class has been introduced. The concept of product identifier (e.g. UPC) allows for identification of products down to a style level - not the identification of a singular individual product item. Note: this class is not only intended for the UPC standard, but should be used for any type of universally accepted product codes. We observed that customers are sending multiple types of product identifiers to us via their customer orders. Example from Primark: We receive a UPC and the older standard of Kimball. Value examples: Name: KimballNo (This map to the Universal Product Code Type) Value: 36998 (This would map to the Universal Product Code) Name: KimballDesc Value: BLUSH UNICORN TOTE (This would map to the Description) true false Transactional Internal N/A
Cargo Package Type 3f539e55-8c4c-ea11-ad9c-40b034e2c22b Cargo Package true See "Cargo Package" class documentation for important notes of business scenarios on the usage of "Cargo Package" and "Cargo Package Type" classes. A type of Cargo Package that can be used to contain specific commodities/ customer products, and/or other cargo packages. This includes Cargo Package Types such as Carton, Case, Bag, Box, Pallet, Crate, Sack, Drum, Keg, Jerrican, Bundle, Tray, Tin, etc. However, it should be noted that Cargo Package Types are actually be more granular than just defining, for instance, something like "Drum" or "Crate". In realtity, and using same example, there are 27 types of drums and 14 types of crates, and therefore master data will have to carry all of those. It should be noted too that typically there is also an entry with "undefined", for cases when it is unknown or irrelevant what is the exact type to be used. Examples: Code: 1G_ZZZ_56 Name: Drum, Fibre Code: QF_1H1_13 Name: Drum, Plastic, Non-removable head Code: DR_ZZZ_ZZZ Name: Drum, undefined UN Package Types There is an international standard of package type codes maintained by the United Nations (UN). However, this standard is not granular enough, i.e. it doesn't contemplate all cargo package types, namely subtypes for different materials or variations. The standard is nevertheless mandatory, i.e. any non-contemplated subtypes will still have to correspond to a master UN Package Type Code. For this reason, all Cargo Package Type entries will always have to correspond to 1 UN package type. Although, the same UN Package Type may correspond to more than 1 internal Cargo Package Type. The UN Package Type Code is used for the first block of characters (2 characters) of the internal Cargo Package Type Code. IMDG Package Types Another international standard of package type codes is IMDG, which is applicable exclusively for standardized cargo packages used for containement of hazardous and dangerous cargo (although not all hazardous cargo package types are contemplated in IMDG). For this reason, some Cargo Package Type entries will have an IMDG Package Type, but some will not. It should also be noted that IMDG Package Types, when applicable, are usually more granular than the UN Package Types. The IMDG Package Type Code is used for the second block of characters (3 characters) of the internal Cargo Package Type Code. true false Reference Internal N/A
Cargo Package Specification 40370e07-ed11-ea11-80ed-9cd21e38f3a4 Cargo Package true The Cargo Package Specification (CPS) is about how products should be packed after production or after being sold. Such data would come together with a Customer Order (CO). The CPS is also used for Packing Lists (PL), where the PL lines (PLL) need to show how products have been packed. Inner Cargo Package: The concept of defining inner cargo package specifications is solved with the recursive relationship on CPS. In other words a CPS can have a parent CPS. This is a non-cyclic tree structure because a CPS cannot be in two or more other CPSs. Note: The quantity of any inner CPS can be derived from the inner CPS information itself and therefore not kept as an "Inner Cargo Package Quantity" attribute on the CPS itself. Should derived data like total quantities of all CPSs be needed, this must be calculated by traversing the tree of inner CPSs. Example Data: Ommiting non relevant attributes for easy readability. LvlNet WeightGross Weight11012 1.156 1.1.12.53 1.1.22.53 1.256 1.2.12.53 1.2.22.53 true true Transactional Internal Competitive Strategic Information
Cargo Package 6f8495f4-b256-ea11-ad9d-40b034e2c22b Cargo Package true Represents one single instance of a Cargo Package, i.e. a carton box, or a pallet. Any actual measurements performed on the cargo package must be stored here. Such actual measurements are carried out in some warehouse operations upon receiving the cargo packages. It is also mandatory to measure cargo packages when they are transported via air carrier. Business Scenario Logic & Flexibility Typically this class is used (i.e. has a relationship with) by "line" classes (i.e. Shipment Line, Shipping Instruction Line, Packing List Line, Shipper Booking Line, etc.). Also, typically, such relationship should have a cardinality of 0..* Cargo Packages for each Line, combined with a relationship of 0..1 Cargo Package Types for each Line. This is because it allows more flexibility, and covers all these scenarios: Simplified Scenario: we may want to have a Line that specifies Cargo Package Quantities + 1 Cargo Package Type, but has no related Cargo Package instance (i.e. we don't want or need to further specify/ detail). Detailed Scenario: we may want to have a Line that specifies Cargo Package Quantities, with the Line itself having 0 Cargo Package Types, and then having a related Cargo Package instance, where the Cargo Package Type is specified, along with any required Inner Cargo Package Levels, and their own Cargo Package Types and quantities. Package Level Logic Cargo Packages can go inside other Cargo Packages. This happens on the business scenario where a commodity (i.e. a Customer Product) is stored inside a Cargo Package, which is in turn stored inside another Cargo Package. Hence why this class has a recursive relationship. When this happens, typically the most outer Cargo Package is known as "outer package", and subsequent inward Cargo Package levels are known as "inner package" and "inner inner package". Example: 5 t-shirts (commodity) are stored inside a carton (inner inner package); 10 cartons are placed inside a box (inner package); 4 boxes are placed inside a pallet (outer package). It should be noted, however, that more levels of Cargo Packages can occur, and that the model effectively allows an unlimited number of Cargo Package levels. Boolean attribute "Has Outer Cargo Package" is used to indicate if "Cargo Package" instance has another instance hierarchically above. Boolean attribute "Has Inner Cargo Package" is used to indicate if "Cargo Package" instance has another instance hierarchically below. Weight Logic The weight of each Cargo Package level shall have the following weight measurements: Gross Weight: at the lowest hierarchical Cargo Package level, this will be the weight of the commodity, plus its containing Cargo Package. At subsequent outward Cargo Package levels, this will be the weight of the contained Cargo Packages, plus its containing Cargo Package. Net Weight: at the lowest hierarchical Cargo Package level, this will be the weight of the commodity. At subsequent outward Cargo Package levels, this will be the weight of the contained Cargo Packages. Net Net Weight: often the commodity has a product packaging of its own (a package which is part of the product, and not part of the cargo packaging which exclusively used for transportation). Example: when the commodity is a bag of peanuts, or a bag of nails. The "Net Net Weight" will then be the weight of the contained peanuts or nails without the product packaging. While the "Net Weight" will be the weight of the contained peanuts or nails with the product packaging. Net Net Weights are calculated at all Cargo Package levels (i.e. without both the cargo packages and product packages). Using above example, let's assume that: 1 t-shirt with product package weights 100g 1 t-shirt without product package weights 95g 1 carton package weights 50g 1 box package weights 200g 1 pallet package weights 5kg Then: Inner Inner Package Net Net Weight: 5x95g=475g Inner Inner Package Net Weight: 5x100g=500g Inner Inner Package Gross Weight: 50g+500g=550g Inner Package Net Net Weight: 10x475g=4750g Inner Package Net Weight: 10x550g=5500g Inner Package Gross Weight: 200g+5500g=5700g Outer Package Net Net Weight: 4x4750g=19000g Outer Package Net Weight: 4x5700g=22800g Outer Package Gross Weight: 5000g+22800g=27800g true true Transactional Internal Competitive Strategic Information
Cargo Package Identifier Type 970203a2-0fc1-ec11-8387-063e63b947ef Cargo Package true Sets the type of identifier used on the cargo package in the cargo package identifier attribute, e.g. Serial Shipping Container Code, Package Identifier, Serial Number etc. true false Reference Internal N/A
IMDG Package Type cb0482b3-2a4e-ea11-ad9c-40b034e2c22b Cargo Package true International Standard of codes that represent Cargo Package Types used for transport of Hazardous and Dangerous Goods. The majority of IMDG Package Type codes follow a convention of kind code + material code + category, represented respectively by 1 number, 1 letter and 1 number. Example: code 1A1 represents a steel drum with non removable head, where the first 1 stands for drum, the letter A stands for steel, and the last 1 stands for non-removable head. However, a few IMDG codes don't follow this logic. This is the case, for instance, of codes BK1, BK2, and BK3. ATTENTION: Only some Cargo Package Types have a corresponding IMDG Package Type code. Namely package types that can be used for transporting Hazardous and Dangerous Goods. Source: https://shippinginsouthafrica.files.wordpress.com/2012/06/haz-packaging-codes-guide1.pdf true false Reference Public N/A
Cargo Package Product Code d26669ff-234e-ea11-ad9c-40b034e2c22b Cargo Package true Information on how to identify products within/on cargo packages (also used in prepack scenario where it is typically given by the purchaser to instruct the seller how to label the packages when commodities inside are mixed). A Cargo Package can have multiple product codes associated. There are scenarios where a number of the quantities in the cargo package has some product code information (UPC numbers or EAN numbers) while other quantities of the same cargo package has other product codes. Note on Barcode Type: The Cargo Package Product Code is reserved for barcode related identification as these identifies products to a style level and not to individual product item level. If using e.g. RFID tags for product items these must be defined on Commodity Item Level. Note on Product: The detailed product information is kept on the Customer Order Line or Packing List Line level which relates to the Customer Product / Commodity. Note on current implementation: In the current SCM system landscape the concept of this class is referred to as the "PrePack" information. It is by this structure possible to define how many of the cargo packages should be labelled with a specific UPC number and its barcode. true true Transactional Internal Competitive Strategic Information
Segregation Group 12559c27-7367-ea11-a3a7-a0510b9e9705 Hazardous Classification true Determined via the UNDG number. This code is used to determine what commodities can and cannot be shipped together, via grouping them in "segregation groups". There will always be an occurrence of Segregation Group, as there is a value for when no Segregation Group applies ("0", which means "none"). NOTE (relationships): Relationship states that 1 Hazardous Classification will always have 1 occurrence of this class (not 0..1), even if it's not Ocean. This is because both classes are Master Data, so the statement being made here is that 1 Hazardous Classification must always specify what is the Segregation Group applicable to the commodity, regardeless if it will be used or not for a particular shipment. List of all possible values: CodeName0None1Acids2Ammonium compounds3Bromates4Chlorates5Chlorites6Cyanides7Heavy metal and their salts (including their organometallic compounds)8Hypochlorites9Lead and its compounds10Liquid halogenated hydrocarbons11Mercury and mercury compounds12Nitrites and their mixtures13Perchlorates14Permanganates15Powdered metals16Peroxides17Azides18Alkalis References: http://www.shashikallada.com/segregation-groups/ https://dgm.world/blog/27-legal-updates/72-segregation-update-in-the-imdg-code-amendment-39-18 true false Reference Public N/A
Fire Emergency Schedule 2d15d4cf-7467-ea11-a3a7-a0510b9e9705 Hazardous Classification true Determined via the UNDG number. EmS means Emergency Response Procedures for Ships Carrying Dangerous Goods (EmS Guide) and EmS codes are assigned to each UN Number in column 15 of Dangerous Goods List in IMDG Code chapter 3.2. EmS is a two part code. The first part is for fire, starting with letter F, and second part for spillage, starting with letter S. The fire schedule codes are from F-A to F-J. The spillage schedule codes are from S-A to S-Z. This class is the first part of the EmS code, related to fire schedule codes from F-A to F-J. NOTE (relationships): Relationship states that 1 Hazardous Classification will always have 1 occurrence of this class (not 0..1), even if it's not Ocean. This is because both classes are Master Data, so the statement being made here is that 1 Hazardous Classification must always specify what is the Fire Emergency Schedule to the commodity, regardeless if it will be used or not for a particular shipment. Full list of codes here: http://www.shashikallada.com/what-is-ems-and-how-this-is-used/ Relationship with UNDG number here: https://www.grosse-seefahrt.de/download-pakete/neu/ems.pdf true false Reference Public N/A
Spillage Emergency Schedule 3cb13c48-7767-ea11-a3a7-a0510b9e9705 Hazardous Classification true Determined via the UNDG number. EmS means Emergency Response Procedures for Ships Carrying Dangerous Goods (EmS Guide) and EmS codes are assigned to each UN Number in column 15 of Dangerous Goods List in IMDG Code chapter 3.2. EmS is a two part code. The first part is for fire, starting with letter F, and second part for spillage, starting with letter S. The fire schedule codes are from F-A to F-J. The spillage schedule codes are from S-A to S-Z. This class is the second part of the EmS code, related to spillage schedule codes from S-A to S-Z. NOTE (relationships): Relationship states that 1 Hazardous Classification will always have 1 occurrence of this class (not 0..1), even if it's not Ocean. This is because both classes are Master Data, so the statement being made here is that 1 Hazardous Classification must always specify what is the Spillage Emergency Schedule to the commodity, regardeless if it will be used or not for a particular shipment. Full list of codes here: http://www.shashikallada.com/what-is-ems-and-how-this-is-used/ Relationship with UNDG number here: https://www.grosse-seefahrt.de/download-pakete/neu/ems.pdf true false Reference Internal N/A
Radioactive Details 453d4aea-992d-ec11-a3dc-a0510b9e9705 Hazardous Classification true For dangerous commodities of HazMat Class 7 (i.e. radioactive commodities), an additional set of details must be provided, contemplated on this class. Radioactivity Values It should be noted that Radioactivity levels are not modelled as a specific attribute on this class because they are a Measurement. As such, Radioactivity levels should be instantiated in class "Additional Measurement", with Measurement Function being "Radioactivity" and Measurement Unit being one of the possible Becquerel SI units (Bq, kBq, MBq, GBq, TBq or PBq). true true Master Public N/A
Hazardous Classification 96393a81-b4fc-e911-80eb-9cd21e38f3a4 Hazardous Classification true When a commodity is considered "dangerous cargo", then, under the United Nations Dangerous Cargo (UNDG) standard, it must be classified with a UNDG number, assigned by the United Nations Committee of Experts on the Transport of Dangerous Goods. The entire "Hazardous Classification" (all classes and attributes) can be ultimately derived from the UNDG number, as the UNDG number is univocal for the entire "Hazardous Classification" data. UNDG Number Logic The UNDG Number ranges from UN0001 to about UN3600. Although not official, special UNDG Number "UN9999" can sometimes be used for commodities which are not considered dangerous cargo (corresponding unofficial UNDG Text is "non-dangerous goods"). Reason why code "UN9999" is sometimes used is because sometimes non-dangerous goods are shipped together with dangerous ones. And then on DG declarations code "UN9999" will be used to generate text "non-dangerous goods" for non-dangerous ones. Of course, when code is "UN9999", then other "Hazardous Classification" classes and attributes are expected to have value NULL or "no" (for booleans). Granularity The "UNDG Classification" is not as granular as "Commodity Classification", hence why we can have 1..* commodity classifications for the same UNDG Number. Some examples: UNDG code "UN0102" covers both commodities "fuse, detonating metal clad" and "cord, detonating, metal clad, 1.2D". UNDG code "UN0118" covers both "Hexotol, dry or wetted with less than 15% water, by weight" and "Hexolite, dry or wetted with less than 15% water, by weight". UNDG code "UN2422" covers both "Refrigerant gas R 1318" and "Octafluorobut-2-ene". Alternative Code Standards (NADG and AIRDG) There are 2 other international standards, alternative to the UNDG, to classify dangerous goods: the North American (NADG) and the Air Transport (AIRDG, defined by ICAO, not IATA). These 2 code sets have mostly the exact same Number and Name values as the UNDG set (with NADG having prefix "NA" instead of "UN", ranging from NA0001 to about NA3600, and AIRDG not having any prefix, ranging from 0001 to about 3600), with only a few isolated discrepancies (roughly there are about 20-30 codes which mean different commodities). Therefore, modelling these 2 alternative code standards can be easily solved by considering them attributes of UNDG. References https://en.wikipedia.org/wiki/UN_number https://en.wikipedia.org/wiki/Lists_of_UN_numbers true true Master Public N/A
Required Dangerous Package Type 9d393a81-b4fc-e911-80eb-9cd21e38f3a4 Hazardous Classification true Determined via the UNDG number. As per Dangerous Goods regulations, each dangerous commodity must be transported in a specific Cargo Package Type. This class specifies what Cargo Package Type will relate to which Dangerous Commodity (i.e. UNDG number). Typically (and quite often), a dangerous commodity must have multiple levels of packaging, hence why the self-relationship in this class. The different levels of packaging are typicaly called: Outer Package Inner Package Inner Inner Package true false Master Internal N/A
Medical First Aid Guide a9588b98-2169-ea11-a3a8-a0510b9e9705 Hazardous Classification true Determined via the UNDG number. Information on medical first aid is provided in the IMO/WHO/ILO Medical First Aid Guide for use in accidents Involving dangerous Goods (MFAG), which is the chemicals supplement to the International Medical guide for ships (IMGS) which is published by the World Health Organization (WHO), Geneva. The revised text of the Guide was adopted by the Maritime Safety Committee in May 1998, for use in association with the IMDG Code, and will be further amended as and when necessary. The Guide is reproduced in the Supplement of the IMDG Code.​ NOTE (relationships): Relationship states that 1 Hazardous Classification will always have 1 occurrence of this class (not 0..1), even if it's not Ocean. This is because both classes are Master Data, so the statement being made here is that 1 Hazardous Classification must always specify what is the IMDG Medical First Aid Guide to the commodity, regardeless if it will be used or not for a particular shipment. http://www.imo.org/en/OurWork/Safety/Cargoes/DangerousGoods/Pages/MFAG.aspx true false Reference Public N/A
Hazardous Properties Group ac78250a-2669-ea11-a3a8-a0510b9e9705 Hazardous Classification true Determined via the UNDG number. Actually known in the industry simply by the name of "Classification Code" (the term "Hazardous Properties Classification" is used here to make it unambiguous). It classifies the hazardous properties of a substance or object, such as toxic (T) or flammable (F), for instance. These properties can also occur in combination, for example toxic and corrosive (TC). This classification is typically used as a more granular/ subsidiary classification of the HazMat (risk and sub-risk) classification. It's also typically used when a more granular specification of the danger that the commodity poses is required to be stated for legal or transport reasons. For instance, lithium batteries are transported under HazMat Class 9 (miscellaneous), but they require in some countries a specific Placard type for the combination of Class 9 + Lithium Batteries, which is obtained via using the Classification Code. Full table of possible values can be found here: https://www.dgg.bam.de/quickinfo/en/help/classificationcode More details here (column 3b): https://www.unece.org/fileadmin/DAM/trans/danger/publi/adn/adn2011/English/7-TableC-E.pdf true false Reference Public N/A
Dangerous Cargo Placard c7393a81-b4fc-e911-80eb-9cd21e38f3a4 Hazardous Classification true Any placard pictograms that must be affixed to either a Cargo Package, Equipment, or Vehicle, in order to identify visually the specific dangers that the cargo being transported poses, and/or the correct ways to handle it and correct regulation that applies. There are 3 types: Placard (also known as "diamond" in the industry), Label, and Plate. For details on each type, please visit documentation of "Dangerous Cargo Placard Type" class/ enumeration. Placards There is 1 pre-defined international standard Placard for each unique HazMat Code (Class and Division). The pre-defined placards are also the basis for the placards used in IMO (IMDG) for Ocean, in IATA/ ICAO for Air, and other international (or local) transport regulators. Placard Variations Some variations of HazMat Placards exist depending on the Transport Mode and/ or Country, where slightly different pictograms might be used. For instance, USA and Canada use slightly different versions, and so does Road transport in a number of countries. Hence why relationship with Transport Mode and Country. On top of local and transport mode variations, there are subset variations of the placards for specific situations: Packing Group might be required legally to be present on the Placard, to further specify risks and danger, in which case there are 3 variations (1 for each Packing Group) of each Placard. For HazMat Class 6.1, the Hazard Zone might be also required to be present in the Placard, introducing as well subset variations. Finally, in some specific cases, the Hazardous Properties Classification Code might also imply subset variations of HazMat Placards. For instance, lithium batteries are transported under HazMat Class 9 (miscellaneous), but in some countries a specific Placard variation for the combination of Class 9 + Lithium Batteries is required. See documentation on classes Packing Group, Hazard Zone and Hazardous Properties Classification Code for more details. This means that any combination of HazMat Class + any (or none) of the 5 elements is possible: HazMat code HazMat code + transport mode HazMat code + transport mode + ISO country HazMat code + packing group HazMat code + packing group + hazard zone HazMat code + hazard zone HazMat code + transport mode + packing group HazMat code + transport mode + ISO country + packing group HazMat code + transport mode + ISO country + packing group + hazard zone HazMat code + classification code HazMat code + transport mode + ISO country + classification code etc. Labels Additionally to the HazMat Placard, additional labels might be required to be affixed together. For instance, for dangerous commodities maintained at an elevated temperature, an additional label pictogram identifying "Elevated Temperature" might be required (depending also on country and transport mode). These additional labels are typically more detailed than the HazMat Placard, and therefore require UNDG Number to be correctly determined. A Label will be an instance of "Dangerous Cargo Placard" where Dangerous Cargo Placard Type = "Label". When a Placard and a Label need to be used together, that therefore means 2 instances of "Dangerous Cargo Placard". Plates Typically affixed in trucks (or other vehicles) for road transport, they are mandatory under some specific dangerous cargo local conventions (like ADR or HAZCHEM), and/ or some specific Dangerous Commodities (UNDG Number). Like Label, they are supplementary to the Placard and they require UNDG Number to be correctly determined. Typically the plates are an orange square or rectangle, divided in 2 smaller horizontal rectangles by a black line divider, containing: on the top rectangle, called "Upper Part", a code that is specific to the local convention (ADR, HAZCHEM, etc.) and has a specific meaning within such convention. on the bottom rectangle, called "Lower Part", the UNDG Number. It should be noted that it's possible to have more than 1 plate for the same UNDG Number (for instance, the case of UK that uses both ADR and HAZCHEM). References https://en.wikipedia.org/wiki/Dangerous_goods#Transport_documents https://en.wikipedia.org/wiki/Dangerous_goods#Transport_documents https://adrbook.com/en/2017/ADR/5.3.1.7 https://adrbook.com/en/2017/ADR/5.3.2.2 https://www.ilo.org/legacy/english/protection/safework/cis/products/safetytm/tranann5.htm https://en.wikipedia.org/wiki/ADR_(treaty) https://en.wikipedia.org/wiki/Hazchem true true Master Public N/A
HazMat Class d6d681ea-e769-ea11-a3a9-a0510b9e9705 Hazardous Classification true The Hazardous Material Class (also known as HazMat) classifies Dangerous Cargo commodities in specific groups, according to the specific hazard or danger that they pose. This classification is used then to generate proper Dangerous Cargo Placards (also known as "Diamonds") that are used to label cargo, containers/equipment or vehicles, and derive the proper Dangerous Cargo handling and regulations. This classification is also the base used by the different classifications used around the world, and/or maintained by specific transport mode regulating authorities, such as IMDG (IMO) for Ocean, or IATA for Air. Code Logic The HazMat code has 2 parts, separeted by a dot: The first part specifies the HazMat CLASS. There is a total of nine classes: Class 1 Explosives Class 2 Gases Class 3 Flammable liquids Class 4 Flammable solids Class 5 Oxidizing substances and organic peroxides Class 6 Toxic and infectious substances Class 7 Radioactive material Class 8 Corrosive substances Class 9 Miscellaneous dangerous substances and articles The second part specifies the HazMat DIVISION. Not all classes have subdivisions: Example: Class 2 is further divided in to: 2.1 Flammable Gases 2.2 Non-Flammable, Non-Toxic Gases 2.3 Toxic Gases Each class (or division within a class) has a unique identifying label (commonly known as a 'diamond'). References https://en.wikipedia.org/wiki/Dangerous_goods#Transport_documents https://www.unece.org/fileadmin/DAM/trans/danger/publi/adn/adn2011/English/7-TableC-E.pdf true true Reference Public N/A
Commodity Classification Association f6cc7d9b-a543-ec11-a3e2-a0510b9e9705 Commodity Classification Association true A generic association to support both master and transactional data associations to Commodity Classifications.Holds any related commodity classifications on the transactional classes it relates to. Can also be used because of: Missing Master Data: This class has its own "Commodity Code" and "Commodity Name" attributes to allow the possibility of recording them directly as transactional data, for the cases where the required Commodity Classification master data doesn't exist yet. Country Specific Data: There can be more than 1 commodity classification, to cover for cases where different countries of the transport journey require different codes. Customer Specific Data: Recording customer values, that might be different from the actual and/or final commodity value, is also possible via "Commodity Code" and "Commodity Name" attributes. Note: A commodity code can be related to the commodity code master data set or exist here with code and description if it cannot be related to the master data set. The same goes for country codes and the manufacturer of the cargo. true false Transactional Internal N/A
Regulation 10f5e67a-bfd7-11f0-64d1-e682385842d0 Regulation true An official regulation is a formal rule or directive issued by an authorised body, typically a government agency, that has the force of law and governs specific conduct within its jurisdiction. It is usually adopted in its final form through an official order and filed with the appropriate regulatory registrar or authority. Examples are FMC, OFAC and SSE. true false Reference Public N/A
Regulatory Obligation 46071d81-9920-11f0-52c7-e62eed53f945 Regulation true Specifies the Regulatory Obligations, i.e. actions or behaviours that must be observed or followed, related to a given Regulation. true false Reference Internal N/A
Regulation Type ed5dac88-332f-ef11-8184-c403a888648b Regulation true Regulations can be classified into various regulation types. Economic Regulations, which would include Antitrust laws or price controls. Environmental Regulations which would include emission standards or waste management. Health and Safety regulations which would include food and drug regulations or public health regulations. Financial regulations which would include banking regulations or consumer protection laws. Privacy and Data Protection regulations which would include GDPR. true false Reference Public N/A
Procurement Category 4fbfa265-8feb-ee11-8179-c403a888648f Procurement true Is used within the purchasing function to group similar goods or services. This categorization helps in streamlining the procurement process, enabling better management and control over purchasing activities. Example: Category:Customs House Brokerage true true Master Internal N/A
Procurement Project 52db8a50-eefb-ee11-817d-c403a888648f Procurement true A procurement project refers to a specific set of activities and cost evaluations undertaken to acquire goods, services, or works from external sources. This process involves several stages such as identifying needs, defining specifications, evaluating finances, sourcing potential suppliers, conducting competitive bidding or negotiations, selecting vendors, contract management and finally managing the delivery and implementation of the procured items. true true Transactional Internal N/A
Project Period Spend 0b0ef6d6-e7fb-ee11-817d-c403a888648f Investment Project true Project spend refers to the total amount of monies that are allocated and spent on a specific project, as well as some standard project management monetary values. true false Transactional Confidential N/A
Project Cost Effect 4b1fcefb-12ec-ee11-8179-c403a888648f Investment Project true There can be multiple cost effect type, and the percentage effect on the total baseline spend (100 %) are allocated to the individual cost effect types. true false Transactional Confidential N/A
Project Investment Type 84c4fa61-fd99-11ef-3bf7-96109e803296 Investment Project true Project Investment Type provides additional information on how an investment was done. Some examples of investment types are: - Self-developed - Build-to-suit - Lease / Retrofit true false Master Internal N/A
Project Vendor d56cbfd2-3e2a-ef11-8183-c403a888648b Investment Project true The relationship of the vendor to the transactional Investment project. Identifying if the vendor is incumbent for existing procurement work and whether for that specific project the vendor is regulated by government requirements true false Transactional Internal N/A
Project Cost Effect Type d98985dc-04ed-ee11-8179-c403a888648f Investment Project true The type of cost effect on the project. Some examples Standard / UC Effect Volume Effect Bunker/Fuel Effect Cash Flow Effect (working capital) true false Reference Internal N/A
Project Type e63f10ab-e9fb-ee11-817d-c403a888648f Investment Project true Project type is the categorization or classification of project activities based on the specific characteristics, scope, and requirements of a project.It defines the nature of Project and link with relevant Objective Some examples of project types are Contract Expiration - Renegotiation of an expiring agreement Spot Opportunity - Breaking and/or re-negotiating an existing contract -one-off projects with savings potential Emission surcharge (ESG) - Pass-on cost per regulatory requirements from Feeder operators etc Green OPEX cost from suppliers (ESG) - Green OPEX extra cost will be transferred to Maersk through tariffs or contracts. true false Reference Internal N/A
Cost Performance Index f307861a-6929-ef11-8183-c403a888648b Investment Project true Project can include CPI percentages for the years the project is active.. true false Transactional Internal N/A
Investment Project f4545d43-8eeb-ee11-8179-c403a888648f Investment Project true Refers to a specific initiative or venture undertaken with the aim of generating returns on the invested capital. This could involve investing in assets such as machinery, infrastructure, technology systems, or even new business ventures. true true Transactional Internal N/A
TIR Voucher 08a4e0c8-7847-ec11-8364-0650f4158fe5 Transit Document true TIR Voucher A TIR carnet may have 4, 6, 14, or 20 vouchers, as one pair of vouchers is used per country. The number of vouchers indicates the number of countries that can be transited, including the countries of departure and countries of destination, under cover of this type of carnet, e.g. a 20-voucher carnet may be used for a TIR transport through up to 10 countries. true false Transactional Internal N/A
TIR Carnet 2843b795-7847-ec11-8364-0650f4158fe5 Transit Document true A document issued pursuant to the TIR (Transport International Routier) permitting sealed road transport shipments to traverse TIR-members countries without undergoing customs inspection until reaching the destination country. Each TIR Carnet has a unique reference number. A TIR Carnet may have 4, 6, 14, or 20 vouchers, as one pair of vouchers is used per country; the number of vouchers indicates the number of countries that can be transited, including the countries of departure and destination, under cover of this type of Carnet (e.g. a 20-voucher Carnet may be used for a TIR transport through up to 10 countries). Each individual TIR Carnet can be used for only one TIR transport. Once the TIR transport has been terminated at the Customs office of destination of the goods, the driver is handed back the TIR Carnet duly endorsed by the Customs authorities of destination. TIR documents can be issued for multi modal transport but the rules is that the transport always has to include a road transportation if TIR is to be used. true true Transactional Internal N/A
Transit Document f6f48993-d6f0-ee11-b886-44e517a1f1d9 Transit Document true A document that must accompany cargo and/or shipments under the business scenario where cargo crosses a border and enters a country, but has not been customs cleared yet, and will be cleared at an inland location, typically a bonded warehouse or similar customs bonded facility. true true Transactional Internal N/A
Transit Document Type f8f48993-d6f0-ee11-b886-44e517a1f1d9 Transit Document true Defines the type of Transit Document. Examples are: TIR Carnet, T1, T2, etc. true false Reference Internal N/A
Customs Guarantee 09531361-dcb7-11ef-06cc-6294512195f3 Customs Declaration true A customs guarantee is an agreement designed to cover debts arising from customs duty, import VAT, and excise. These debts can be classified as either actual debt, which has already arisen, or potential debt, which may arise in the future. Customs guarantees are often required when duties are not paid at the time of import or export, or when the value of import duties is unknown or disputed. The guarantee must be provided at the moment of lodging the customs declaration for the specific customs procedure. true false Transactional Confidential Sensitive Personal Information
Customs Declaration 1589d467-3442-ec11-a3e1-a0510b9e9705 Customs Declaration true Represents 1 instance of a submission of Customs Clearance, on behalf of 1 particular customer, for 1 particular shipment, to 1 particular Customs Authority, for the purpose of clearing the cargo, and authorize either its entry, exit or move within a specific customs zone (typically a country or region). It should not be confused with Manifest, as this customs submission refers to the individual cargo of 1 specific customer, submitted by said customer or on its behalf, and not to an entire vessel, aircraft, etc. submitted by the related carrier. The Customs Clearance can be broke down (although not mandatory) in Customs Clearance Lines that provide further details. true true Transactional Internal N/A
Customs Guarantee Type 2a2cd121-dd7f-11ef-3a77-922eb47883a8 Customs Declaration true Several types of customs guarantee exist, depending on local and regional regulations. An individual guarantee covers a single operation and is considered the default case. In contrast, a comprehensive guarantee covers the customs debt and other charges of multiple operations over a longer period. To use a comprehensive guarantee, an economic operator must apply for authorization from the competent Customs Authority. true false Reference Public N/A
Customs Declaration Status 30501336-cb48-ee11-b846-44e517a1f1d9 Customs Declaration true A customs declaration, which is sent to a customs authority, is assigned a status by said customs authority. This status is not generic but is specific to the customs authority, the customs declaration type and any related scenarios. true false Reference Internal N/A
Customs Valuation Method 53091a01-d80b-11ef-04e0-922eb47883a8 Customs Declaration true Customs valuation determines the value of imported goods for the purpose of calculating customs duties. The customs value is typically based on the transaction value, which is the price actually paid or payable for the goods, including the cost of transport and insurance. true false Reference Internal N/A
Customs Transaction Type 80715f01-d268-11ef-0ce9-6e7ff58ec67d Customs Declaration true The customs transaction type, also known within the customs domain as "transaction nature", refers to the nature of the underlying agreement of the movement of goods. The breakdown by customs transaction type is necessary to determine whether there is economic transfer of ownership and financial compensation. true false Transactional Internal N/A
Customs Procedure 85f82bf1-e56b-11ef-06cc-6294512195f3 Customs Declaration true A Customs Procedure Code (CPC) is a code used in international trade to identify the customs and/or excise regimes that goods are being entered into or removed from. CPCs are essential for businesses involved in importing and exporting as they help categorize and track goods through customs processes, ensuring compliance with legal and regulatory requirements. Key Functions of CPCs: Identification: CPCs identify the purpose of an import or export, such as whether goods are for permanent import, temporary import, re-export, or transit. Customs Procedures: They determine how goods are entered into or removed from appropriate customs and/or excise regimes, such as import/export procedures, transit procedures, or temporary storage procedures. Duties and Taxes: CPCs influence the collection of duties and taxes by specifying the applicable customs procedure. Importance of CPCs: Compliance: CPCs ensure that goods comply with the correct legal and regulatory requirements, reducing the risk of errors and delays in customs clearance. Cost and Time Efficiency: By standardizing the way goods are categorized and tracked, CPCs help businesses minimize the costs and time associated with customs procedures. Trade Statistics: CPCs enable the collection of accurate trade statistics, which are crucial for monitoring and analyzing international trade flows. This data informs trade policies and negotiations. CPC Format: CPCs typically follow a standard format consisting of a four-digit heading code followed by a two-digit subheading code, indicating the specific procedure to be applied. For example, a CPC might look like "1234.56". true false Reference Public N/A
Customs Tariff Quota a2281c5e-7c57-ea11-ad9e-40b034e2c22b Customs Declaration true In international trade, a customs tariff quota is a regulatory measure that limits the quantity or value of specific goods that can be imported over a defined period for a defined tariff. Customs Tariff Quotas are used to manage trade flows and protect domestic industries by restricting the volume of foreign goods entering a market. Together with tariffs, which impose financial charges on imports, quotas influence market access and competition. Each customs tariff quota is defined by a quota quantity, which specifies the maximum volume or value of goods permitted under the quota during its validity period. This quantity is essential for enforcing the quota and ensuring compliance. Additionally, a customs tariff quota reference is used to identify and track the specific terms and conditions of the quota, including the applicable goods, timeframes, and duty rates. These references support transparency and facilitate the administration of trade policies. true false Transactional Internal N/A
Customs Declaration Type b4a4640a-e5b0-ec11-a3f8-a0510b9e9705 Customs Declaration true Customs Entries have mandatory types. The types depend on local rules of each Customs Authority country/ region, and they vary on a multitude of different criteria. For instance, in some countries, the types are based on type of cargo, while on others they depend on what state department must be involved. Example For Customs Entry Type of 'AMF' 'Advanced Manifest Filing' there are different types per country ACI → Advance Commercial Information (Canada) ACI → Advance Cargo Information​ (Egypt) ENS → Entry Summary Declaration​ (European Union) ISF ACE true false Reference Internal N/A
Customs Declaration Line c1c753a0-7cf0-ec11-a404-a0510b9e9705 Customs Declaration true Breaks down the Customs Declaration into individual lines that carry details on quantities, measurements, goods value and duty amount, among others. Customs Declaration Lines can be further broken down in to Child Customs Declaration Lines, for designated business scenarios and use cases. true false Transactional Internal N/A
Customs Declaration Rejection fe58e5b1-78e8-11f0-14c8-96109e803296 Customs Declaration true true false Transactional Internal N/A
Manifest Total 16540381-b4fc-e911-80eb-9cd21e38f3a4 Manifest true Manifest Total Manifests can carry a multitude of possible totals, depending on the country/region of the customs. These can include totals grouped by container, or certain container types, or by tranport document. On each Manifest Total instance, a count will be provided (i.e. count the number of containers, the number of transport documents, etc.), as well as the related aggregated sum of weights and measurements. true false Transactional Internal N/A
Manifest 1a1c075d-b43c-ec11-a3dd-a0510b9e9705 Manifest true A Manifest is a consolidated list of all cargo on board a vehicle (vessel, aircraft, etc.), plus vehicle attributes, and route details. It can list either cargo or passengers, including crew members. Typically, a cargo manifest lists all Transport Documents and the associated total number of goods shown on each Transport Document. Totals for the whole Manifest can then be derived and presented as well. Customs Authorities at the respective ports, airports, etc. will need to review and confirm the cargo manifest against the actual cargo being loaded/ unloaded at these locations. Without this confirmation, cargo cannot be loaded/ unloaded. Typically, the Manifest will list all the goods on vehicle, though it may be meant for several different destinations. Generally, the following details are shown in cargo manifests: Operator name and details; Transport Document number; Consignor(s) information; Consignee(s) information; Shipping route; Quantity, type, and description of goods, including item name, quantity, weight, and type of item; In most cases, the cost of each item is also shown. Notifications On top of Manifests, Customs Authorities also typically request to receive the so-called Notifications, where a Carrier notifies of the arrival or departure of a vehicle (vessel, aircraft, train, etc.) at a location under the jurisdiction of the Customs Authorities. Because the Notifications share the same data structure and attributes of Manifest (with the only significant difference being that Notifications don't specify all the Transport Documents), they are modelled here together in the Manifest subject area. First Port of Entry (and other additional locations) A Vessel Schedule may contain more than 1 port call within the same country. When this happens, then Manifests submitted for port calls which are not the first port call of that same country must specify which port was the first port of entry in the country. For some countries, regions, or business scenarios, it may also be required/ mandatory to indicate other port calls within the Vessel Schedule. All of these locations can be instantiated by resorting to the "Location Association", inherited from Document (see class Location Association in Document subject area). true true Transactional Internal N/A
Manifest Consignment e50153e7-0672-ec11-a3e6-a0510b9e9705 Manifest true Manifest Consignment Represents an instance of 1 element that is aggregated by the Manifest. Typically this element is a Transport Document, although certain business scenarios exist, specially outside Ocean, where the element might be a piece of equipment (container, ULD, etc.) or vehicle (truck, train, etc.). There are specific attributes to the Manifest Consignement, in the sense that the instantiation of the use of 1 Transport Document by 1 particular Manifest has its own attributes, such as sequence, submission stage and type, movement type, cargo classification type, etc. For the cases where the element is a piece of equipment or vehicle, then it must be either a Cargo Stuffing (for Logistics & Services), or a Shipment Equipment Cargo Distribution (for Ocean). This is because we will need the data from a specific use of that equipment or vehicle, i.e. the specific cargo details of the specific shipment that the equipment or vehicle was used for. true true Transactional Internal N/A
Customs Service Order 6a48d235-60d0-ec11-a400-a0510b9e9705 Customs Service Order true A type of Service Order that relates to Customs Clearance services only. It relates to 1 particular shipment of 1 particular customer, although same shipment of same customer may have more than 1 Customs Service Order (for origin, destination, in transit, etc.). The Customs Service Order aggregates Commercial Invoices of related shipment for the purpose of customs clearance requests and submissions. It also aggregates any related submitted Customs Entries. true true Transactional Internal N/A
Customs Filing Scheme 99e1b352-0c65-eb11-addc-40b034e2c22b Customs Filing Profile true Reference data for all customs filing schemes used around the world. Examples: ACI (Advance Commercial Information) ISF (Importer Security Filing) EEI (Electronic Export Information) true false Reference Internal N/A
Customs Filing Profile acab1f8a-3d64-eb11-addc-40b034e2c22b Customs Filing Profile true A profile describing for a specific customer how customs filing is done, depending on export- and import country as well as a specific export- and and and import location, if necessary. With this profile it is possible to specify any number of compbinations for import/export filing scenarios and handle these based on what the transportation dictates in terms of locations. The profile can also specify a transport mode such that filing can be set up for ocean, air, rail, truck etc. Further the profile includes an integration configuration section. This is for identification of for example EDI setups and file formats needed to communicate with customs on import/export side. true true Reference Internal N/A
Integration Configuration e3e9e63d-3f64-eb11-addc-40b034e2c22b Customs Filing Profile true Defines a configuration for how integration is between Maersk and a trading partner. true false Reference Internal N/A
Commercial Invoice 4a6c7ecf-fa16-ea11-ad8b-40b034e2c22b Commercial Invoice true The Commercial Invoice (CI) is a document issued by the shipment's shipper/seller to the consignee/buyer, for the goods that the former is selling and shipping to the latter. It should therefore not be confused with invoices issue by Maersk to its customers. The Commercial Invoice is only relevant to Maersk for the purpose of customs clearance. Among other, the Commercial Invoice contains an accurate description of the merchandise, country of origin, duties, etc. All items are itemized and with actual prices. Status indications: The timestamps associated with the status of the business object is considered a physical implementation. Examples of these include "BookedTimestamp", "CancelledTimestamp" and "ConfirmedTimestamp". true true Transactional Internal N/A
Commercial Invoice Line 4dda1ade-0322-ea11-ad90-40b034e2c22b Commercial Invoice true A line in a Commercial Invoice (CI). Each line indicates quantities, measurements, price, duties, etc. for a given commodity/ customer product that the shipper/seller is selling to the consignee/buyer. A CI line might be based on, related to, and/or detailed in a Customer Order Line or a Shipper Booking Line. true false Transactional Internal N/A
Free Trade Agreement fb45c4dc-3e24-ed11-a1a0-bf3947c3094d Commercial Invoice true A free-trade agreement (FTA) or treaty is an agreement according to international law to form a free-trade area between the cooperating states. Few examples of free trade agreement are: EFTA, European Free Trade Association ASEAN, Association of Southeast Asian Nations NAFTA, North America Free Trade Agreement true true Transactional Public N/A
Rail Schedule Location 3405bbbe-4388-ea11-adaa-40b034e2c22b Rail Schedule true Represents a location that the train originates from, passes through or terminates at. Note: If location is origin only Scheduled Departure and Public Departure timestamps will be available. If location is terminating only scheduled arrival and public arrival will be populated true true Transactional Public N/A
Rail Schedule 90fd25a6-4288-ea11-adaa-40b034e2c22b Rail Schedule true The Rail schedule is a published Schedule including a Train identifier and a list of Locations(with arrival and departure times) that the Train will call at for the published schedule true true Transactional Public N/A
Rail Leg ab8ef9c7-6771-ed11-8bf8-5c879c3c5a54 Rail Schedule true The transit between a pair of adjacent, consecutive railway locations. Identifies both the starting rail schedule location and the ending rail schedule location for a particular Rail Schedule. true false Transactional Public N/A
Vessel Leg 30510381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Schedule true The transit between a pair of adjacent, consecutive port call pairs. Identifies both the starting port call and the finishing port call for a particular Vessel Schedule. true true Transactional Public N/A
Vessel Port Call 35510381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Schedule true A commitment that a specific vessel will call at a specific port on an absolute date and time. Example: Sequence 2The sequence of the port call - all the port call together makes up vessel's voyage. Proforma Time of Arrival 2008-06-01 15:00The generated dated proforma is never changed. The port call will have a relative arrival date from rotation start, for example day 4 at 15:00 Estimated Time of Arrival 2008-06-01 16:30This value can change depending on various conditions. Actual Time of Arrival 2008-06-01 16:20Records when the vessel actually arrived at the port Proforma Time of Departure 2008-06-02 10:00The generated dated proforma is never changed. The port call will have a relative departure dates from rotation start, for example day 5 at 10:00 Estimated Time of Departure 2008-06-02 11:30This value can change depending on various conditions, e.g. if the loading is taking longer than expected. Actual Time of Departure 2008-06-02 12:00Records when the vessel actually departed the port Also known as: Dated Site Call (GSIS) true true Transactional Public N/A
Vessel Schedule 43510381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Schedule true A Vessel Schedule is a commitment by an ocean carrier that a specific vessel will call at specific ports on specific dates and times. A vessel schedule is denoted by a vessel, carrier, its voyage number and a list of port calls during that voyage. Internally in Maersk vessel operations Vessel Schedules are required for Maersk vessels and for some non-Maersk vessels such as Foreign Feeders and vessels participating from Vessel Sharing Agreements. In supply chain business vessel schedules are needed from many different ocean carriers in order to support the multi-carrier aspect of the business and Maersk therefore needs to source schedule information from many different carriers versus only maintaining schedules for their own liner business. Vessel Schedules are typically published online at ocean carrier websites or received via EDI from either the carriers themselves or aggregators like BlueOcean. Note: A Vessel Schedule used to be called a "Dated Voyage" and then later renamed to a "Dated Schedule". As Maersk integrated with logistics there was a need to rename it to "Vessel Schedule" to clearly distinguish vessel-, air- and rail schedules. Also known as: Voyage (GSIS) Dated Schedule Dated Voyage true true Transactional Public N/A
Vessel Port Call Deviation 49510381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Schedule true A record of a change to the estimated or actual arrival or departure date/time of a Vessel Port Call, or of a port omission. Schedule exceptions (deviations) occur if/when a vessel is unable to maintain the intended schedule due to unforeseen events (e.g. weather, port congestion, technical issues etc.). Port Omission When a ship does not call at a port included in the Long Term Schedule that was planned at the start of the voyage. Planned (foreseen) cut and run operation When a port call is reduced in time and move counts due to foreseen delay/congestion. Unplanned (unforeseen) cut and run operation When a ship terminates its discharge/loading operations prematurely due to unforeseen events. Inducement call (ad hoc call) An additional port call made on a specific voyage that was not originally included in the Long Term Schedule . Port call swap When the vessel port call rotation is changed after publication of the Long Term Schedule. Blank Sailing When an already announced voyage is cancelled. In this case, the voyage number is retained, and planned port calls are blanked. true false Transactional Public N/A
Fuel Gauge Reading 4e510381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Schedule true Gauge readings for fuel- and other types of oil on arrival and departure. Example types of fuel oil HSFO - High Sulphur Fuel Oil LSFO - Low Sulphur Fuel Oil Marine - Marine Oil Other true false Transactional Internal N/A
Piloting 80b04bb3-99fd-ec11-a19e-9be14a14f3d5 Vessel Schedule true Data about piloting of the vessel for the port call true false Transactional Internal N/A
Vessel Port Call Function 81c1eec1-9294-ee11-a1be-d7e14702d112 Vessel Schedule true States the kind of function that the vessel port call encompasses. Examples of values: - Cargo Operations - Waterway Passage - Canal Passage - Bunkering - Charter Transition true true Reference Public N/A
Deviation Reason cc5da2a9-94b9-ea11-adb7-40b034e2c22b Vessel Schedule true Reasons for why a there was a deviation for the port call, e.g. vessel was delayed for, or did not make, a port call, examples below: Port Omission Deviation To Avoid Bad Weather true false Reference Public N/A
Proforma Waypoint 240cb99e-5d56-ed11-a1a3-cda225df246b Vessel Schedule Planning true A waypoint is an intermediate point or place on a route or line of travel, a stopping point or point at which course is changed. It breaks up the proforma leg in detailed GPS coordinates that enables drawing the travel route on map and indicating things like entering ECA/SECA zones. true false Transactional Internal N/A
Rotation 59510381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Schedule Planning true A rotation is a trip that can be undertaken by a vessel and is a planning unit for vessel schedules. It can be defined as the connection of individual port calls that occur in a set sequence, starting from a default starting point. As such it is non-dated framework of how vessels are to be operated to provide movement of goods, in terms of: Transport Mode Marine container terminals (MCT) that can be called on Sequence of MCTs Time intervals between the MCTs MCT-to-MCT connections Also known as: Rotation (GSIS) Proforma (Schedule Planner, clearly mentions rotation when speaking about capacities that can be set) true true Transactional Confidential Competitive Strategic Information
Proforma Schedule 66510381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Schedule Planning true A Proforma Schedule is defined in the planning stages as a sub-string of the port calls of a rotation. It has a date of departure (the departure date of its first port call) and a date of arrival (the arrival date of its last port call). Also known as: Non-Dated Voyage (GSIS) Non-Dated Schedule (GSIS) true true Transactional Internal N/A
Proforma Port Call 6f510381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Schedule Planning true A Proforma Port Call is a relative (non-dated) vessel call, for yet to be defined vessel, at a marine container termnal (MCT). A port call represents a place where a vessel temporarily halts to discharge or take on freight and to refuel. Together the list of Proforma Port Calls define the sequence of MCTs and the target interval between arrival at, and departure from a MCT. Also known as: Non-Dated Vessel Port Call Non-Dated Site Call Port of Call Port-Call Site Call true true Transactional Internal N/A
Proforma Leg 7e510381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Schedule Planning true The Proforma Leg is the transit between a pair of adjacent, consecutive Proforma Port Calls (PPC). Identifies both the starting PPC and the ending PPC. Can act as a data gathering-entity for properties such as spare slot-capacity (for current and future-scheduled adjacent PPC pairs), and for storing metrics such as expected wind-speed, expected transit time, expected distance, and expected speed. In certain circumstances (i.e. when more than one Service is deployed on a Rotation) this entity also identifies the Service at each leg of the Rotation. The network of Proforma Legs, making up a Rotation, may indicate that the Service for which vessels assigned to the Rotation operate switches during the Rotation. It may also indicate that one Service covers more than one Rotation. The distance between two adjacent Proforma Port Calls. Distance in each leg is measured as Pilot-to-Pilot, not Terminal-to-Terminal. Also known as: Non-Dated Vessel Leg true true Transactional Internal N/A
Directed Service bc1472f9-5d4f-ed11-a1a3-cda225df246b Vessel Schedule Planning true A Service is directed and assigned to one rotation - Directed Service is used for this. A Service can be partitioned using compass directions. This breaks a Service up into several pieces, which are connected at single port calls. The start and end port call enables this. Like a Proforma Schedule, a Service can overlap with other Services. Consequently, several sales agents/Maersk offices instead of one are doing business in the ports where the overlap takes place. Also know as: Directed String (GSIS) true false Transactional Internal N/A
Proforma Port Call Assignment e5f07328-df50-ed11-a1a3-cda225df246b Vessel Schedule Planning true Attributes which are specific to a proforma port call when it is assigned to a Proforma Schedule or to a Rotation. The arrival and departure elapsed times are examples attributes that will depend on the assigned port calls. A rotation may have 10 candidate port calls, but for one proforma schedule maybe 6 are assigned. Therefore the elapsed time for each port call cannot be the same for the rotation as for the proforma schedule. true false Transactional Internal N/A
Routing Note 6d70d7e1-bcad-ed11-a1a9-88da74af6119 Routing true Notes generated or input for the routing. This could be for examples warnings that the customer needs to be aware of. true false Transactional Internal N/A
Routing Note Type 6f70d7e1-bcad-ed11-a1a9-88da74af6119 Routing true A type specifying the routing note, e.g. that it is considered a warning. true false Reference Internal N/A
Routing 7222d7a3-8190-ed11-a1a6-a5e58e79069f Routing true The Routing class represents the concept of product offering between a desired origin and destination. It is generated based on the network master data on an adhoc basis when a customer requests a routing for a shipment. true true Master Internal N/A
Routing Leg c7f6ceac-8190-ed11-a1a6-a5e58e79069f Routing true The Routing Leg class represents a routing between two locations for any transport mode. It captures the carriage details via the "Carriage" class. true false Master Internal N/A
Named Account Routing f12c7370-b0ad-ed11-a1a9-88da74af6119 Routing true Specific, stored routings for customers who need that. true false Master Internal N/A
Route 83510381-b4fc-e911-80eb-9cd21e38f3a4 Trade Lane true A route is primarily used for grouping 1 or more journeys, and are then used as definitions for what a Maersk operator can sell in terms moving cargo on the transportation network. A route therefore defines where the cargo can go in the operator's network. Note on Maersk Line Route system: The Route system provides a system for the storing and maintenance of Route Codes and the combinations (journeys) that make up each route for the carriers i.e. MSL, SCL, MCC and SEA. It is used by the operational systems to either validate route codes that are entered in the system or to provide the route code for a particular routing or combination e.g. GCSS. All routes are based on Cargo Type (Break Bulk, Dry and Reefer) but this is only used by Safmarine at present. All MSL, MCC and SEA routes are applicable to all Cargo Types. The concept is driven and defined by Finance and Liner Management. Route codes are used for financial budgeting and follow-up purposes. Journeys detail Routes and are the combinations that represent all the possible ways of getting cargo from place of receipt to place of delivery. They are defined by: Place of Receipt city - mapped to a financial area (GEO Business Defined Area) First load port (GEO city) Last discharge port (GEO city) Place of Delivery city - mapped to a financial area (GEO Business Defined Area) With each combination assigned to a specific Route code. true true Master Internal N/A
Trade Lane 87510381-b4fc-e911-80eb-9cd21e38f3a4 Trade Lane true A trade lane is a high level specification of where cargo moves from and to. It can group multiple routes together to indicate that these form part of the trade lane. A trade lane can be between two geographical areas or within a single geographical area. Examples: AFR - AfricaA trade lane name used in Maersk Line LCL-DE-US - Maersk LCL from​ Germany to USAA trade lane name used for Maersk LCL business which has 3 routes; DEHAM - USNYC, DEHAM USCHI and DEHAM USATL Also known as: Line Trade true true Master Internal N/A
Journey 8b510381-b4fc-e911-80eb-9cd21e38f3a4 Trade Lane true A journey is a specification between two geographies where cargo can move in a certain direction. Note on Maersk Line journey specifics: A journey can be used for detailing a route with business defined areas (BDA): Place of Receipt BDA - where the cargo comes from Place of Delivery BDA - where the cargo goes to Journey can be further detailed with: First Load Port Last Discharge Port Cargo Type Direction Note: First load port and last discharge port must both be either present or both missing, a journey cannot have just a single first load- or last discharge port associated. true true Transactional Internal N/A
Vessel Sharing Partnership 9c4a2dcf-e938-ef11-a1c5-f3ef5fbf2395 Service true A partnership that Maersk has formed with another carrier, e.g. Gemini with Hapag Lloyd. true true Master Internal N/A
Vessel Sharing Service 9c7e5dc9-f238-ef11-a1c5-f3ef5fbf2395 Service true A partnership for a specific service, e.g. a Gemini partnership that is effective during a certain time for a service. true true Master Internal N/A
Service 9e510381-b4fc-e911-80eb-9cd21e38f3a4 Service true A Service is a sales unit offered to the customer. Like a Proforma Schedule, it comprises several consecutive Proforma Port Calls (via Directed Service) for the purpose of segmenting commercial activity and organisational responsibility. Elements of the Service are points at which customers can bring in and pick up freight. A Service is directed and assigned to one rotation - Directed Service is used for this. Also known as: String (GSIS) true true Master Internal N/A
Network Leg Detail 15fcaa54-066b-ed11-a1a4-dac57d1c6c19 Network true A detailed level breakdown of the network leg, e.g. per Maersk brand, with ifnormation about the prorities. true true Master Confidential Competitive Strategic Information
Network Leg a2317d48-056b-ed11-a1a4-dac57d1c6c19 Network true Represents a point to point, area to area transportation leg for a specific transport mode so the leg can have associated costs, priorites per brand, standard transit time etc. Network legs are used to construct/compose an offer (Routing) to a customer for transporting their goods end to end. true true Master Confidential Competitive Strategic Information
Network Leg Cost fce86a50-056b-ed11-a1a4-dac57d1c6c19 Network true Maersk incurred costs for transportation of cargo, from origin to destination, transport mode, carrier etc. as per the network leg. true true Master Confidential Competitive Strategic Information
Transport Leg 1e719c21-9a18-11f0-52c7-e62eed53f945 Transport true The distance and applicable route between two geographical points, which can also represent a leg, namely within a sequence of legs.
Leg Connection ce073f0c-c91b-ef11-a1c4-a610861322cc Transport true Stores information about a connecting leg for any transport related legs; e.g. Service Plan Leg, Transport Leg etc. For certain use cases related to planning and execution a leg can combine- or split from/to multiple legs, and it is a must to know what the prior- and/or subsequent legs are. true false Transactional Public N/A
Distance Type fdc2f281-9fa4-11f0-6647-9e6a8bfe0eb1 Transport true The type of distance recorded for a Transport. Examples: - Default Sail Distance - Vessel Conceptual Sail Distance - Vessel Physical Waypoint Distance - Truck Driving Distance - Rail Distance - Flight Distance - Direct Line Distance or more detailed examples - Berth to Berth - Pilotage to Berth true false Reference Internal N/A
Inland Water Carriage 0492ce14-0e96-ed11-83f5-068bdc802de1 Carriage true A specific type of carriage for inland water transportation. true false Transactional Internal N/A
Air Carriage 3e13d928-0e96-ed11-83f5-068bdc802de1 Carriage true A specific type of carriage for air transportation. true false Transactional Internal N/A
Carriage 58929dfa-7f3e-ed11-a421-a0510b9e9705 Carriage true Carriage holds relevant details on the actual or offered transport, i.e. schedules, vessel or other vehicle, voyage number, flight number, locations, etc., depending on the mode used (ocean, air, rail, road or inland water). true true Transactional Internal N/A
Rail Carriage 5a8787d1-58d0-ec11-a400-a0510b9e9705 Carriage true A specific type of carriage for rail transportation. true false Transactional Internal N/A
Ocean Carriage 6501d00b-1cca-ec11-a3fe-a0510b9e9705 Carriage true A specific type of carriage for ocean transportation. true false Transactional Internal N/A
Road Carriage 7fb6610d-0e96-ed11-83f5-068bdc802de1 Carriage true A specific type of carriage for road transportation. true false Transactional Internal N/A
Flight Service Type 231dfba3-a342-ec11-8364-060557247501 Flight Schedule true IATA flight service type codes when scheduling flights. Examples: A, ADDITIONAL_FLIGHTS, CARGO_MAIL, Cargo/Mail B, ADDITIONAL_FLIGHTS, PASSENGER, Shuttle Mode C, CHARTER, PASSENGER, Passenger Only true false Reference Public N/A
Flight Leg 9997cbee-816f-ea11-bd82-34f39a7a061f Flight Schedule true Flight leg denotes a flight plan. It documents the journey of the Flight , as per the flight schedule, from one airport to another airport in a flight leg, along with other technical details. A flight plan will typically be filed prior a flight by either a pilot or dispatcher. true true Transactional Public N/A
Flight Schedule e5198365-906d-ea11-bd82-34f39a7a061f Flight Schedule true A Flight Schedule is a commitment by an air carrier that a specific Flight will Depart and Arrive at specific airports on specific weekdays and times. true true Transactional Public N/A
Document Recipient 093caeb3-1f17-ee11-b834-44e517a1f1d9 Document true Specifies details on a party who will receive document, identifying such party, as well as the communication means to receive document, and any other relevant additional details. true false Transactional Internal N/A
Document Pouch 0df30fb0-6c33-ea11-ad93-40b034e2c22b Document true Collection of documents which are relevant to a shipment or customs or the like. Normally collected together at origin and submitted to destination in order to allow cargo to be released. true false Transactional Internal N/A
Document Group 24540381-b4fc-e911-80eb-9cd21e38f3a4 Document true Document Group is grouping of Document Type true false Reference Internal N/A
Document Template 34f636a8-a635-ea11-ad93-40b034e2c22b Document true A template that can be applied when a document is created. E.g. when creating an FCR the user can choose to apply template which will then fill marks and numbers, description and parties on the FCR. This is not to be confused with a rendering template which will specify how the data will apear on a printable document like a PDF. Transport Document Template Templates for HBL, HSWB, that can be created by shippers themselves as preparation. Forwarders Cargo Receipt (FCR) Template A template containing pre-filled data for creating a Forwarders Cargo Receipt (FCR). For example a template having certain parties pre-filled or certain charges. It is used to increase efficiency in operations and for shippers that create their own draft FCRs so they do not have to type or select all data every time they create an FCR. Shipper Booking Template A template containing pre-filled data for creating a Shipper Booking (SBK). For example a template having certain parties pre-filled or certain charges. It is used to increase efficiency in operations and for shippers that create their own SBK's so they do not have to type or select all data every time they create an SBK. true false Transactional Internal N/A
Rendering Template 351823c0-3767-ea11-ada0-40b034e2c22b Document true Inspired by the FCR printing configuration where a Maersk office can have multiple different templates when they need to print FCRs. These templates can have differetn watermarks and company logos and office postal addresses. They can also carry different signatures which are just an image of a signature by a senior customer service person of the office. The printouts can also have attachments with local legal clauses. This is for example mandatory in China where a full page of legal clauses are appended to each FCR issued. Most of this functionality is to be captured in the print generation tool. But there should be some data element that allows the end user to select which template should be used when performing the printout of PDF generation of a document. true false Transactional Internal N/A
Document 3e35249d-6a33-ea11-ad93-40b034e2c22b Document true A general representation of a document including relevant relationships that are comment to document subtypes, e.g. data files of scans or renders, owning office and soft coded values Hard copies: A scanned copy of a signed hard copy business contract can be kept via the Document construct where the document can be rendered as a file. true true Transactional Internal N/A
Document Pouch Document 653d7810-f3ab-ec11-8382-0658eee7c7f5 Document true Represent a document in a document pouch. Tells whether a document of a specific pouch has been released with the pouch or not and if released what date and time it was released. true false Transactional Internal N/A
Document Type 9566d400-1f38-ea11-ad93-40b034e2c22b Document true A type of document used internally or externally in the enterprise - this could be documents that are not created by the enterprise itself but received from business partners in the transportation scenarios. Examples: Tally Sheet, Tax Invoice, Packing Slip, Fumigation Certificate, Certificate of Origin Examples: Shipper Booking Packing List Forwarders Cargo Receipt Commercial Invoice Carrier Booking Cargo Stuffing Advance Shipping Notice Arrival notice Haulage Order Delivery Order (CY) Delivery Order (SD) Export Collection Order (SD shipment only) Booking Confirmation Booking Confirmation for Dry (General) Cargo Booking Confirmation for Dangerous Cargo Bill of Lading Equipment Release Order Shipping Instruction Special Cargo Acceptance Request This Reference data is maintained in GITHUB true false Reference Internal N/A
Printed Document accd5365-b594-11f0-6647-9e6a8bfe0eb1 Document true This represents a physical instance of a document, in other words: a document as printed on paper. true false Transactional Internal N/A
Document Filing Type bf8186f4-3264-ed11-b815-44e517a1f1d9 Document true Identifies the type of filing. true false Reference Internal N/A
Document Filing Status e4461d71-59f0-eb11-ab88-5c879c3c5a54 Document true The different statuses that an Document Filing can have. The set of possible statuses deeply varies and depends on the Document Filing Type, and therefore, it's not possible to determine a predictable and closed enumerated set of values. FMC (Federal Maritime Commission) For the purpose of FMC, and for guidance on that particular type of Document Filing, since it's a very common one, the possible statuses are: - NOT_FMC - FMC_DISABLED - FMC_EXEMPTED - NOT_FILED - FILED true false Reference Internal N/A
Document Filing e956cc0f-3264-ed11-b815-44e517a1f1d9 Document true A submission of the Document to a relevant government, tax, customs, labor, or other regulatory authority, typically for the purpose of complying to laws or regulations, or other similar requirements. true true Transactional Confidential N/A
Letter of Credit 36fa01bc-756d-ea11-ada2-40b034e2c22b Letter of Credit true ATTENTION: not to be confused with the Financial Letter of Credit. For the Finantial one, which is used a payment method, please check subject area "Payment Terms" in "Finance" domain. A document issued by a bank per instructions from a buyer (i.e. the Consignee) of goods authorizing the seller (i.e. the Shipper) to draw a specified sum of money under specified terms usually the receipt by the bank of certain documents within a given time. The Letter of Credit (LC) is a guarantee for the goods ordered by the consignee, i.e. the bank acts as underwriter. The LC is between bank and consignee and shipper can use it to go to the bank to get money for the goods and in turn the consignee will pay the bank. It is a "legal" document but for Maersk logistics it consists of a number and a type. Commercial LCs are primary payment method in international trade. These commercial credits are used mainly in exporting and importing business. This class holds information about the Letter of Credit number together with the type of Letter of Credit. Example from Shipper Booking scenario: When documents presented do not conform to the requirements of the LC, it is referred to as a "discrepancy". Banks will not process LCs which have discrepancies. They will refer the situation back to the buyer and/or seller and await further instructions. Letter of Credit Types Many of our documents need to associate to a Letter of Credit. There can be several different types of LCs - for example the CI will have a master LC and a transfer LC - therefore it has been decided to make this general across our subject areas. CO, SBK, FCR, PL and CI relates to a class keeping LC number and the LC can be typed. true true Transactional Internal N/A
Letter of Credit Type 66802bcc-756d-ea11-ada2-40b034e2c22b Letter of Credit true Letter Of Credit Type Type of Letter of Credits (LC). Examples: FirstGenerally considered the type of the "normal" LC that is mostly observed in the data Maersk receives or must store for their customers. This type can be used for the general Letter of Credit field. TransferableA Transferable LC is a documentary credit under which the beneficiary (first beneficiary) may request the bank specifically authorised in the credit to transfer the credit, available in whole or part, to one or more secondary beneficiary(ies). Non-transferableA non-transferable letter of credit is when the bank makes credit available to the beneficiary only and cannot be transferred to any other party. IrrevocableAn irrevocable letter of credit is an official correspondence from a bank that guarantees payment for goods or services being purchased by the individual or entity, referred to as the applicant, that requests the letter of credit from an issuing bank. An irrevocable letter of credit cannot be canceled, nor in any way modified, except with the explicit agreement of all parties involved: the buyer, the seller, and the issuing bank. RevocableA revocable letter of credit is a type of letter of credit in which the issuing bank can amend the terms of the letter of credit or cancel the letter of credit completely without giving prior notice to the beneficiary. ConfirmedA confirmed letter of credit is a guarantee a borrower gets from a second bank in addition to the first letter of credit. The second letter guarantees the second bank will pay the seller if the first bank fails to do so. UnconfirmedA letter of credit which has not been guaranteed or confirmed by any bank other than the bank that opened it. The advising bank merely informs the beneficiary of the letter of credit terms and conditions. RestrictedA restricted letter of credit refers to a letter of credit which restricts negotiation to the bank which the issuing bank has nominated in the credit. In a restricted negotiable letter of credit, the authorization from the issuing bank to pay the beneficiary is restricted to a specific nominated bank. Freely NegotiableWhen the letter of credit does not put any condition for the negotiation of documents, it is a freely negotiable letter of credit. This letter of credit can be negotiated through any willing bank. RevolvingA revolving letter of credit is a single letter of credit that covers multiple transactions over a long period of time. It is very specific in a way that it is used for regular shipments of the same commodity between the same buyer (importer) and the seller (exporter). Back to BackA back-to-back letter of credit involves two letters of credit to secure financing for a single transaction. These are usually used in a transactions involving an intermediary between the buyer and seller. Back-to-back letters of credit are used primarily in international transactions. Red ClauseA Red Clause Letter of Credit is a specific type of letter of credit in which a buyer extends an unsecured loan to a seller. Red Clause Letters of Credit permit documentary credit beneficiaries to receive funds for any merchandise outlined in the letter of credit. Green ClauseGreen Clause Letters are an extension of the Red Letter, as it enables the advance of not only the purchase of raw materials, processing and packaging of goods but it also takes pre-shipment warehousing at the port of origin and insurance into account. Deferred Payment (aka.: Usance)Deferred Letter of Credit is a type of Letter of Credit in which a conditional undertaking is taken by the bank to pay the seller on behalf of the buyer on a specified future date after completion of the transaction. StandbyA standby letter of credit is a legal document that guarantees a bank's commitment of payment to a seller in the event that the buyer-or the bank's client-defaults on the agreement. A standby letter of credit helps facilitate international trade between companies that don't know each other and have different laws and regulations. Assignment of ProceedsAn assignment of letter of credit proceeds is an assignment (or transfer) of future debt payable under a letter of credit from the beneficiary to another person (ie, the assignee). It enables the assignee, instead of the beneficiary, to receive payment under the letter of credit. true false Reference Internal N/A
Equipment 09550381-b4fc-e911-80eb-9cd21e38f3a4 Equipment true A specific piece of equipment that is used in the transportation process. The Equipment will in most cases have a unique number like an ISO container number or a ULD IATA code. Examples include: ISO shipping containers for ocean and intermodal freight Unit Load Device for air cargo Ancillary equipment such as Gensets and chassis Note: The identification number, serial number and the like have been moved to subclasses because they differ greatly between e.g. ISO and ULD containers. true false Master Internal N/A
Inactivation Reason 0d907e8d-1cf4-eb11-8336-062cc11ed047 Equipment true Reasons for why equipment has been inactivated. Examples: Scrapped Damaged Sold Lost Donated true false Reference Internal N/A
Container Grade 0e54ea9b-6df3-eb11-8336-0697801388e1 Equipment true A Maersk internal grading of the quality and cleanliness of a shipping container. The grading is given in accordance with Maersk Container Inspection Criteria (MCIC). A grade can be given to for example indicate that the container is is acceptable for food shipment. There are 5 different grades currently in MERC+ to ensure Maersk customers have been provided with the best suited equipment for their cargo needs. Grades: S - Flexi-bags shipments and Premium Food grade M - Food grade type shipments K - General cargo - Clean container/Premium shipments E - General cargo shipments Q - Scrap cargo shipments true false Master Internal N/A
Chassis 14550381-b4fc-e911-80eb-9cd21e38f3a4 Equipment true Another word for an open trailer frame, usually hauled by a truck tractor-unit, onto which containers can be attached. true true Master Internal N/A
Generator Set 1d550381-b4fc-e911-80eb-9cd21e38f3a4 Equipment true Generator Sets ("Gensets") - are portable diesel fueled generators and important tools used to power the reefer containers, thereby maintaining the set temperature during rail or road transportation (when a reefer is carried on a containership, it is usually plugged into the containership's main power supply). The majority of the gensets are of the clip-on type, meaning that the gensets are clipped on to the upper front of the reefer container. The tank capacity ranges from 150 litres (39 gallons) up to 455 litres (120 gallons), equal to a running time from 36 hours to 5 days. Maersk Line also operates underslung gensets, which are mounted under the chassis. true true Master Internal N/A
Container 21550381-b4fc-e911-80eb-9cd21e38f3a4 Equipment true Container is a shipping container registered by the enterprise. Container can be also termed as a synonym of an equipment sometimes. Container Safety Convention CSC related attributes cover the CSC safety inspection to ensure that containers are maintained in safe condition during their operating lives in accordance with the Convention for Safe Containers (CSC Agreement). true true Master Internal N/A
Engine 39550381-b4fc-e911-80eb-9cd21e38f3a4 Equipment true An engine used on e.g. a power pack or genset to power a generator. true true Master Internal N/A
Damage Type 53540381-b4fc-e911-80eb-9cd21e38f3a4 Equipment true The degree of damage if the container is not sound. Example values: 1 -Total Loss + Lost or stolen containers - Do not Move (Container to be sold) 2 - Damaged Box 3 - Damaged box and damaged Reefer unit 4 - Damaged reefer unit (Reefer Machinery damaged, container can be used for dry cargo Note: If no value is given on the Equipment for Damage Type it means the equipment is not damaged. true false Reference Internal N/A
Machinery Modification Status 6e2d81d8-e125-ee11-a1b7-a91983107b1b Equipment true Status of a machinery modification. true false Reference Internal N/A
Equipment Default Ownership Type 9ca11803-b561-ee11-a1bb-fab3d952de1e Equipment true Indicates the default ownership type to assign to an equipment of a specific size and type, when the equipment is created, based on the equipment profile. true false Master Internal N/A
Machinery Modification b5af8483-e125-ee11-a1b7-a91983107b1b Equipment true Represents a modification done to a piece of equipment, e.g. a reefer container that has had its refrigeration machinery modified. true true Master Internal N/A
Attachment e18a23f5-35ef-eb11-8336-069408b64bc1 Equipment true Specifies attributes needed for handling equipment that is attached to other equipment. E.g. a genset can be attached to a reefer container. This attachment relationship can also be used to track engines installed in a powerpack or a remote container management device that is attached to a reefer container. The attachment must be indicated whether it is a parent or child attachment. This is for example used when a flat rack is having 4 entries of other flat racks which are "children". Each of the children has an entry in attachment as well with relationship to the "parent" which is the bottom flat rack. true false Transactional Internal N/A
Unit Load Device e3062414-005d-ea11-ad9f-40b034e2c22b Equipment true A unit load device (ULD) is a pallet or container used to load luggage, freight, and mail on wide-body aircraft and specific narrow-body aircraft. It allows a large quantity of cargo to be bundled into a single unit. true true Master Public N/A
Reefer Profile 1f530381-b4fc-e911-80eb-9cd21e38f3a4 Equipment Profile true A container profile with specfics about an atmosphere-controlled container, specialised type of Container, which can be referigerated, heated or ambient temperature. It has various controls and monitoring of the atmosphere, filtering etc. true true Reference Public N/A
IMO Tank Type 20eb9308-49f3-eb11-8336-0697801388e1 Equipment Profile true Examples: IMO Type 1Designed for hazardous IMO Type 2Designed for low hazardous IMO Type 5Designed for gas Note that this classification has been replaced by T-Code (see. Tank Code). true false Reference Public N/A
Open Profile 2325be15-01f4-eb11-8336-062cc11ed047 Equipment Profile true An open container, either on the sides, top or both. true false Master Internal N/A
Refrigerant Type 3f530381-b4fc-e911-80eb-9cd21e38f3a4 Equipment Profile true Type of refrigerant used for cooling. A refrigerant is a substance used in a heat cycle usually including, for enhanced efficiency, a reversible phase change from a liquid to a gas. List of refrigerants: CFC - Chlorofluorocarbon CFO - Chlorofluoroolefin HCFC - Hydrochlorofluorocarbon HCFO - Hydrochlorofluoroolefin HFC - Hydrofluorocarbon HFO - Hydrofluoroolefin HCC - Hydrochlorocarbon HCO - Hydrochloroolefin HC - Hydrocarbon HO - Hydroolefin (Alkene) PFC - Perfluorocarbon PFO - Perfluoroolefin PCC - Perchlorocarbon PCO - Perchloroolefin H - Halon/Haloalkane true false Reference Internal N/A
Fire Fighting System 49530381-b4fc-e911-80eb-9cd21e38f3a4 Equipment Profile true E.g. 'CO2', 'Halon', 'Foam' true true Reference Public N/A
Power Pack Profile 4d530381-b4fc-e911-80eb-9cd21e38f3a4 Equipment Profile true A Powerpack is an equipment that can provide electrical power, typically to multiple Containers. Unlike a Genset, it is not an attachment to another item of equipment but instead generators and engines inside an ISO container. Note that the relationship between the actual power pack container and any installed engines are handled in the equipment subject area. The profile specifies general specifications for the power pack. Note: Length- and weight units inherited from Equipment Profile. true true Reference Internal N/A
Generator Set Profile 51530381-b4fc-e911-80eb-9cd21e38f3a4 Equipment Profile true A group of properties of a category of Genset. A Genset can be attached to another item of Equipment (eg Container, Chassis) for the purpose of providing electrical power. true false Reference Public N/A
Chassis Container Support 69530381-b4fc-e911-80eb-9cd21e38f3a4 Equipment Profile true Defines which kind of container lengths are supported by the chassis profile. true false Reference Internal N/A
Chassis Profile 6c530381-b4fc-e911-80eb-9cd21e38f3a4 Equipment Profile true A group of properties of a category of Chassis. Note: Length- and weight units inherited from Equipment Profile. true false Reference Internal N/A
Bulk Profile 765eb8a8-0af4-eb11-8336-062cc11ed047 Equipment Profile true Bulk (or bulk cargo) containers have loading hatches in the roof. On the door side, there are discharge hatches, which are sometimes equipped with short discharge tubes for guiding the bulk cargo. Alternatively, unloading hatches may be mounted in the doorways, for emptying the containers. Such containers may also be used for general cargo. Lashing rings are mounted in the top side rails for securing the cargo. Some bulk containers are equipped with forklift pockets, which allow handling by forklift trucks. true false Master Internal N/A
Tarpaulin Sheet Type 7a122b62-4df3-eb11-8336-0697801388e1 Equipment Profile true Different types of tarpaulin sheet that can be used with e.g. open top containers. true false Reference Internal N/A
Equipment Profile Type 81530381-b4fc-e911-80eb-9cd21e38f3a4 Equipment Profile true Equipment Profile Type discriminates the Equipment Profile. Some of the Profiles can be subdivided into other Profile Types like the subtypes. Not all equipment profile types need to have a specific subtype. Examples are: * Container Profile * Reefer Profile * Power Pack Profile * Tween Deck Profile * Flat Rack Profile * Chassis Profile * Generator Set Profile true false Reference Public N/A
Construction Material 9a530381-b4fc-e911-80eb-9cd21e38f3a4 Equipment Profile true Construction materials of various kind, used i.e. for exterior container construction material and container flooring. PLW - Plywood BAM - Bambo PLK - Plankwood COM - Composit LAM - Laminated wood STL - Steel ALU - Aluminium GRP - Glassfiber Reinforced Plywood COR - Corten steel MGS - Mufler Grade Stainless steel SST - High grade stainless steel true false Reference Public N/A
Container Profile a2530381-b4fc-e911-80eb-9cd21e38f3a4 Equipment Profile true A group of properties of a category of Container. Note: Length- and weight units inherited from Equipment Profile. true false Reference Public N/A
Electrical Property b8b9d099-edf3-eb11-8336-062cc11ed047 Equipment Profile true Records the voltage that the equipment supports for either the generator or the plugs available. Some generators for example supports dual voltage, designed to operate on 190/230 or 380/460 volts A.C, 3 phase, 50-60 hertz power. Each entry in the properties can specific a low and high range of voltage. This is also applicable for plug voltage. If an equipment profile must specify two plug voltages there has to be two entries, e.g.: Entry 1: Voltage Low Range: 190 Voltage High Range: 230 Electrical Property Type: Generator Current Type: AC Phase Count: 3 Hertz Low Range: 50 Hertz High Range: 60 Entry 2: Voltage Low Range: 380 Voltage High Range: 460 Electrical Property Type: Generator Current Type: AC Phase Count: 3 Hertz Low Range: 50 Hertz High Range: 60 Relevance on sub-types: Reefer Profile Tank Profile Power Pack Profile Genset Profile true false Master Internal N/A
Flat Rack Profile df41869c-5df3-eb11-8336-0697801388e1 Equipment Profile true For flat racks and tween-decks. ISO flat rack is a special container designed to provide maximum flexibility for cargo loading and is primarily used for break-bulk, over-width or over-height cargo on container ships. Flush folding - the end walls fold on top of the deck. Note: Length- and weight units inherited from Equipment Profile. true false Master Internal N/A
Equipment Profile e0530381-b4fc-e911-80eb-9cd21e38f3a4 Equipment Profile true An equipment profile describes characteristics and can be shared among one or more types of pieces of equipment. Equipment series: Profiles can be used to create a number of equipments when initially creating the equipment. The profile is then shared for those pieces of equipment via relation. Product profiles: The profile can also describe product related profiles - for example the characteristics of reefer containers that are used as something being sold as specific product. These comes in diferent varieties with controlled atmosphere, ventilation and cooling capabilities. These "product" profiles can have names like 'STAR FRESH', 'MAGNUM', 'STARVENT'. 'SUPER FREEZER', 'STUFFIE', 'SORTIE', 'BLAST FREEZER' etc. names for container profiles known and used within Maersk. Examples of product related equipment profiles: - Magnum - Standard - Fresh Mist - Super Freezer - Starfresh - Starfresh Plus - Starvent - Transfresh - Tank - Starcare CA - StarRipe true false Reference Public N/A
Tank Code e429f92f-46f3-eb11-8336-0697801388e1 Equipment Profile true T-Code instructions apply to dangerous goods of classes 1 and 3 to 9. Class 2, or non-refrigerated liquified gases are covered by the T50 code. true false Master Internal N/A
Tank Profile e6220d0e-22f3-eb11-8336-0697801388e1 Equipment Profile true A profile with attributes about tank containers. Tank containers are used for bulk transportation of fluids, gasses and powders. Note: Length- and weight units inherited from Equipment Profile. true false Master Internal N/A
ISO Container 8d530381-b4fc-e911-80eb-9cd21e38f3a4 Equipment Size Type true ISO 6346 provides special codes which denote the size and type for intermodal shipping containers. The standard is maintained by the BIC (International Container Bureau). The units are not from Unit of Measurement class as the ISO standard fixes the units on the properties. true true Master Public N/A
Equipment Size 9e530381-b4fc-e911-80eb-9cd21e38f3a4 Equipment Size Type true Maersk's own names for container size, e.g. '45' which indicates the length is 45 feet, this corresponds to the 'L1' ISO container length. Examples include: - 10 ft - 20 ft - 40 ft - 45 ft Note that Equipment Size may not necessarily be the actual length but rather a classification code (Eg 45 could be used even if the ISO length is 49). true false Master Internal N/A
Equipment Height cf5c9ddf-9319-eb11-adce-40b034e2c22b Equipment Size Type true A Maersk representation for height of Equipment. true false Master Internal N/A
Equipment Type e8530381-b4fc-e911-80eb-9cd21e38f3a4 Equipment Size Type true A Maersk representation for type of Equipment. Examples include: - Container - Chassis - Genset - Engine - Tank Hierarchy: There is a hierarchy of equipment types. For example, equipment type "Container" may have subtypes of: - Dry - Reefer - Open top container - Tank container - Flat rack Reefers: Examples of second level Sub-Types (in some situations referred to as Reefer Sub-Types) include: - Blast Freezer - Controlled atmosphere plus high humidity - Super Freezer - Banana Box - Water Cooled - Water Cooled Magnum - Aqualife (a type of Container designed to carry live seafood) Chassis: For chassis the following types exist: - Flatbed chassis - Gooseneck chassis - Pintlehook chassis - Skeletal dual purpose chassis - Skeletal flat chassis - Skeletal flat slider chassis - Skeletal gooseneck chassis - Skeletal gooseneck extendable chassis - Chassis transporter tweendeck These might be physically represented in the Equipment Type table, where the Parent Equipment Type is Chassis. true false Reference Internal N/A
Equipment Size Type f5530381-b4fc-e911-80eb-9cd21e38f3a4 Equipment Size Type true Maersk internal size and type codes for equipment. Collects the allowed equipment and size type combinations together. Enables other master data attributes to be associated with these combinations, e.g. whether a size/type is Bookable or not. Maersk size-type versus ISO size-type: - 20 is a Maersk size code, BULK is a Maersk type code - For each of this "high level" Maersk size-type code multiple ISO container size-type code exists, e.g. 22B0 and 22BU true true Reference Internal N/A
Event Type 03ec45d3-516a-ea11-ada1-40b034e2c22b Event true Specifies what type of Event the entry is - also if it is a further subtype of Event - e.g. Event -> Vessel Event -> Vessel Incident the type would be set to "Vessel Incident". Note: Not every type of Event needs to be sub-types of Event. If the attributes and relationships on Event is enough for the type of Event to captured there is no need to sub-type. It is also legal to add additional Event Types even though a sub-type does not exist. Examples: EventThe general event can be used where there is no sub-type needed to specifically identify the event. Equipment Event Transport Event Vessel EventList also to include e.g. Vessel Incident and Bunker Delivery which are sub-types of Vessel Event Document Event Reefer Controller EventConcept from Remote Container Management project Mobile Communications Device EventConcept from Remote Container Management project Container Safety Convention Check Event Pre Trip Inspection Event Shipment Event Warehousing Event Production Event Cargo Event Rail Event Air Event Truck Event Customs Event true false Reference Internal N/A
Event 1ace3fe5-8236-ea11-ad93-40b034e2c22b Event true An event for something that is planned or estimated to occur or something that has already occured. The Event is associated with a Event Trigger which explains what kind of event the date is for. Example "Receival at Origin", "Arrival at Destination" or "Stuffed". The Event is also associated with an Event Timing which designates whether the event is planned, actual, estimated or something else. Descriptive examples: Actual container loaded on board a vessel at a specific time Container was gated in at the terminal An equipment inspection is planned to happen or actually occurred Examples of Event, its trigger and timing: Format: "" "" "" "Receival at Origin" "Earliest" The earliest time that the cargo can be received either in the warehouse for stuffing or a full container at the terminal. Typically send by the customer as part of Customer Order. "Receival at Origin" "Expected" The time that the customer expects that the cargo is received at warehouse or terminal. Typically send by the customer as part of Customer Order. "Receival at Origin" "Latest" Customer requirement of the latest acceptable time that the cargo is precevied at warehouse or terminal. Typically send by the customer as part of Customer Order. "Receival at Origin" "Planned" The time when Maersk plans the cargo to be received either in the warehouse for stuffing or a full container at the terminal. "Delivery at Destination" "Planned" The time we expect the Customer to have the Cargo Delivered (at Destination) "Place of Delivery" "Planned" Cargo expected date to be received at customer location "Departure from Origin" "Earliest" Part of shipping window - i.e. when the cargo should be shipped within this (e.g. on first vessel for ocean.) "Departure from Origin" "Latest" Part of shipping window - i.e. when the cargo should be shipped within this (e.g. on first vessel for ocean.) "Departure from Origin" "Planned" When will the cargo (maybe inside a container - could also be an airplane) leave the origin (often referred to as ETD - estimated time of departure). Scenario: Notify on non-occurrance of planned event. Some customers want's to be notified if certain events that are expected or planned does not happen. In order to achieve this these events must be stored as planned or estimated to occur at a certain time. If the actual event for that planned or estimated event does not occur before the planned or estimated time a notification can be sent. The planned or estimated event should be related to the actual event when it occurs. Scenario: Notify on data update of particular field. In some cases there are requirements to sent out updated documentaion or simple notifications based on when a certain field gets updated. In such scenario the field must be configured as a an event trigger to which the customer is configured to receive notifications. It is up to the custmer configuration what must be sent out upon triggering the event. When the event occurs this event is then logged with the timestamp it occurred. Notifications can then subsequently be generated to the right parties based on event occurance. true true Transactional Internal N/A
Message Level 1f508cb4-6a6a-ea11-ada1-40b034e2c22b Event true The data objects that an Event can connect through via Event Connection. As these are not only document types that can trigger Events, but also other concepts like container or trucks etc. it is needed to have this class to define message level(s) for the Event Trigger. Examples: Carrier Booking Shipper Booking Shipper Booking Line Cargo Stuffing Cargo Stuffing Line Customer Order Customer Order Line House Bill of Lading Carrier Bill of Lading House Airway Bil Master Airway Bill Party Role- Consignee- Shipper Facility- Port of Loading- Port of Discharge true false Reference Internal N/A
Event Reliability Rating 283af671-df11-ec11-834b-0604ac7a8e8b Event true A reference data set for rating how reliable an event is/was. Example set: CF-100100No discrepancies or doubts about the event#00FF00 CF-7575Minor discrepancies that are warnings. Main data is reliable#FFFF00 CF-5050A major discrepancy such as vessel/voyage for this event. Data should be verified#FFA500 CF-2525Event persisted but cannot be relied upon. Correction required#FF0000 true true Master Internal N/A
Event Reliability Rating Group 3b913543-3314-ec11-834b-065640472e19 Event true A code and name that can group Event Reliability Rating. This is needed in order to allow multiple event reliabilities for an event. Use Case: An event may be assigned an reliability rating in COMET and another reliability rating by TradeLens. The two groups used here would then be COMET and TradeLens each having a number of ratings available to "stamp" the event with. Examples: COMET Flow TradeLens SCM Event Engine NSCP Event and Milestones true false Master Internal N/A
Event Relationship Purpose 469db79b-0d7e-ea11-ada7-40b034e2c22b Event true Specifies a purpose for why the events are related to eachother. This is needed for e.g. Equipment Events to log relationship during container twinning operations. Examples of Equipment Event purposes: Equipment Main OperationAn operation of a piece of equipment, which the current operation may be a part (Liner specific) Equipment MergeTriangulated operation of equipment (Liner specific) Container Twinned OperationWhen two containers are lifted or dropped together from a vessel (Liner and Terminal specific) Multiple updates to same eventUsed for when the same event gets several updates (all events are kept!) and related together for full tracability TimelineEvents are related to eachother becuase they together form a meaningful timeline in some context that cannot be constructed from the objects related to the events via Event Connection. Next EventThis is used for ease of getting to the next event in the chain of events. An event that has actually happened may benefit from having its next planned event related true false Transactional Internal N/A
Event Connection 4fc5ad5d-6f6a-ea11-ada1-40b034e2c22b Event true The structure allows the Event itself to relate to many different data objects so that events can be "grouped" together in multiple contexts. This is because an Event can be relevant for both a Shipper Booking, Cargo Stuffing, Packing List and Transport Plan (only an example). By having all the data objects relating directly to the Event Connection there is one place of picking up all events against their data concept counterparts. Examples: Shipper Booking Cargo Stuffing House Bill of Lading Container Carrier Bill of Lading House Airway Bill Master Airway Bill Work Order Number Scenario: Three customer orders (customer A, B and C) are booked for transport by three different shippers. They are all stuffed in to one container by Maersk. The three customer orders have different cargo planning events like earliest cargo receipt date. The shipper bookings also contain different events relvant for the shippers and customers. But they all share the same cargo stuffing. Picking up all the events that are relevant to customer A can be done by querying based on the customer order, getting all the events related to that because we assume that the shipper booking placed for that customer order will be related to the events for the customer order as well. The cargo stuffing events, shared by all, will be related to customer order and shipper booking events as well. Of course when sending out events to shippers and customers, or allowing them to view online, it must be ensured that only events relevant to them are visible (derived from party on the customer order and shipper booking). Note of physical implementation: Ideally there would be one field for the surrogate key for the data object and then the data object type would be looked up in the Message Level class so that it is known where to locate the data object itself. However it might not be possible due to legacy needs to have everything represented by surrogate keys in which case it could suffice to have columns for each supported data relation. true false Transactional Internal N/A
Event Trigger Group 5a913d0a-546a-ea11-ada1-40b034e2c22b Event true This is a classification of Event Trigger at a higher level. Examples: LogisticsThese could be e.g. gate related moves and events like In-gate, Out-gate etc. OceanVessel related events or moves like Loaded on Vessel, Loaded on Barge etc. AdministrativeCustoms Hold, Carrier Release, Container Available etc. RailEvents and moves related to rail operations like Loaded on Rail, Rail Arrival at Inland Transit Point etc. TruckTrucking and intermodal related events and mvoes like Pickup Appointment Date and Time, Loaded on Truck etc. WarehousingFactory Scan, Inbound Scan, Outbound Scan etc. OperationsPertaining to for example vessel operations and events for same. CustomsPertaining to for example customs clearances, inspections, etc. true false Reference Internal N/A
Event Reason 698737cf-639e-eb11-ade6-40b034e2c22b Event true Reason for the event to occur. Examples: Export Import Positioning Vessel Sharing Agreement For export/import: Typically used in container move completion. Also known as the "Event Direction" when used with Equipment Event, typically for a container moves. true false Reference Internal N/A
Event Relationship 9be65552-5a6a-ea11-ada1-40b034e2c22b Event true An event can be related to other events by using this structure. The identifier of an event will migrate to the Event Relationship and together with an Event Relationship Identifier and a purpose code from Event Relationship Purpose, make a unique entry. Example: An event records that a vessel has an estimated time of arrival (ETA) at a certain port. Subsequently another event is received which gives a new ETA for the same vessel at the same port. The two events can be related to eachother with the purpose of "Multiple updates to same event". true false Transactional Internal N/A
Event Timing a2551f14-3e4d-ea11-ad9c-40b034e2c22b Event true Classifies the event by a timing type. Values available: ExpectedExample: Customers expectation to when an event is supposed to occur. EstimatedExample: Maersk's estaimte to when an event will occur, e.g. an estimated time of arrival. EarliestExample: Events that informs about the earliest time something is allowed to occur, e.g. a earliest pick-up of an empty container. LatestExample: Events that informs about the latest time something is allowed to occur, e.g. a latest arrival at a warehouse. PlannedExample: Events that inform about planned timings, e.g. planned vessel arrival will not change but estimated vessel arrival can change. UnplannedExample: Used for events that happened unexpectedly. Specifically available for Vessel Events ActualExample: Events that informs about the actual time something occured, e.g. actual vessel arrival. PredictedExample: Used for events that informs about predicted timings of when something will occur. Typically used for AI/ML predictions (aka.: forecasted timings) DueExample: Used by documentation events to inform about when something is due. true true Reference Internal N/A
Event Trigger cd735fda-3c4d-ea11-ad9c-40b034e2c22b Event true List of all known triggers that can cause an event to occur. The event trigger must carry a code and a name. The code is an internally defined one in Maersk. There will be external standard codes for many of these triggers, but not for all. Note: For the core SCM landscape the Event Engine is the main event receiver/generator. For a list of event triggers accepted by this engine see: https://more.damco.com/MOREgenericWeb/page?pid=2927&id=1 Example with code and name: CUSL - Customs Clearance FASC - Factory Scan Warehousing Event examples: Factory Scan Inbound Scan Outbound Scan Export Warehouse Receival Import Warehouse Receival Distribution Center Receival Loaded on Truck Stuffing Production Event examples: Production Start Production End Vessel Event examples: Classification of Events involving vessel operations. When a Vessel is allocated and available various event takes place during the voyages. Vessel operational events: Barge Arrival Barge Departure Vessel Arrival Vessel Departure Vessel is approaching a port: Start of port report - Timer starts Arrival pilot station Pilot on board All fast Cargo Operation start Cargo Operation end Last line on board Pilot off Closure of port report Timers Stops Vessel taking bunker: All Fast (start bunker timer) Barge alongside Hose connected Start pumping (Start Operational State) Stop pumping (Stop Operational State) Hose disconnected Barge departure Last line (stop bunker timer) Vessel Events affecting availability of vessels: In fleet Out of fleet Rebuilt start Rebuilt end Dry dock start Dry dock end Equipment Event examples: Names of triggers kept in present tense; the timing will define whether it is planned, actual etc. Gate In Gate Out Load on Rail Unload from Rail Stuffing Stuffing - on land Stripping - on land Stuffing - on vessel Stripping - on vessel Lease In Lease Out In Fleet Out of Fleet Load on Truck Unload from Truck Load on Vessel Unload from Vessel Discharge Shift cell position on board vessel Shift one cell position to new one via pier Purchase Dispose Pickup at Origin Dropoff at Destination Positioning Repositioning Delivery Redelivery GeoFence In GeoFence Out Export Import Damage Repair Registration - Vessel Sharing Agreement Registration - Shipper Owned Empty Return Empty Dispatch Attach (one equipment to another) Detach (one equipment to another) Bundle (flat racks on top of eachother) Activate Power On Power Off Inspection Pre-trip Inspection CSC Events that have been found in analysis but should be replaced with another trigger from above list or given better name: Domestic Rate not maintained Arrival at Container Freight Station One-off movement Cargo Event examples: Cargo Available For Pickup Cargo Gate Out From Warehouse Cargo Receival In Warehouse Cargo Release To Maersk Cargo Remove From Warehouse (At Origin) Cargo Stuffing In Container Carrier Cargo Release Ready at Origin Receival at Origin Receival at Maersk Import Warehouse Receival in Export Hub Receival in Maersk Import Hub Storage Ended Storage Started Agricultural Inspection End Agricultural Inspection Start Rail Event examples: Export Rail Arrival Export Rail Departure Import Rail Arrival Import Rail Departure Air Event examples: Delivery to departure airline Freight acceptance at airlines arrival warehouse Freight on hand with airline at departure Ready for carriage at departure airline Flight departure Flight arrival Truck Event examples: Truck Departure From Maersk Import Hub Truck Departure From Export Warehouse Customs Cargo Event examples: Export Customs Cleared Export Customs Inspection Finished Export Customs Inspection Required Import Customs Cleared Import Customs Inspection Finished Import Customs Inspection Required Import Customs Released Carrier And Customs Released Customs Conveyance Event examples: Vehicle Arrival Vehicle Arrival Overdue Vehicle Arrival Cancellation Customs Hold Customs Release All Loads Manifested Not Manifested Document Event examples: Air Waybill Data Transmision To Carrier Air Waybill Issue Arrival Notice Issue To Consignee Bill Of Lading Confirmation Bill Of Lading Produced Booking Confirmation Booking Cancelled Booking Receival Booking Rejection Carrier Booking Confirmation Carrier Booking Sent Client Invoice End Client Invoice Start Document Receival From Carrier Documents Hand Over To Third Party Export Documentation Collection From Shipper Export Trucking Order Issue Import Trucking Order Issue Forwarders Cargo Receipt Release Freight Booking Confirmation By Airline Freight Booking Request To Airline Freight and Documents Ready For Maersk Collection Import Documents Receival from Origin Maersk House Bill of Lading surrender by Consignee Shipping Instructions Confirmation Receival From Carrier Shipping Instructions Receival from Shipper Shipping Instructions Sent to Carrier Transfer of E-Manifest Transport Event examples: Arrival at Destination Arrival at Place of Delivery Available for Delivery Delivery Complete at Place of Delivery Departure from Pickup Location Departure from Origin Devanning at Container Freight Station Dispatch to Consignee Dropoff at Destination Location Pickup at Origin Location Pickup from Shipper Shipment Event examples: Shipment Delay Alert Event examples (general events): ComplianceFor example to support CSC or pre-trip equipment check, compliance would be the trigger for that event to happen Third Party Appointment Third Party Notified true true Reference Internal N/A
Shipment Journey Leg 25fcaf7d-62ae-ed11-a1a9-88da74af6119 Shipment Journey true A single leg of the shipment journey. E.g. trucking from an inland point to a port or air carriage from one airport to another. true true Transactional Public N/A
Shipment Journey 43ef5e86-62ae-ed11-a1a9-88da74af6119 Shipment Journey true Shipment journey is a visibility, or tracking, entity, providing means to collect any number of references to identify and search for a unit of tracking. The shipment journey is broken down in to legs which represents the steps in the journey that the unit of tracking will traverse from start to finish. true true Transactional Public N/A
Unit of Tracking 84e673e5-62ae-ed11-a1a9-88da74af6119 Shipment Journey true Represent the unit that is being tracked, that the shipment journey provides transport visibility for. It can be an entire booking, a container, a piece of equipment, a single parcel etc. true false Transactional Internal N/A
Container Itinerary 36db1284-6d67-eb11-addc-40b034e2c22b Container Itinerary true A validated flow of container events. The container events can be planned, estimated, predicted, actual etc. The itinerary should depict the empty to empty list of container events as they are to be executed and as they has been executed, i.e.planned and actual. Based on the planned list of container events the itinerary can be used for input to validation against what actual container events happening and flagging errors or out-of-expected events to further processing, analytics and so forth. The itinerary can also be used for proactive alerting if events do not actualise as they are expected to. The itinerary can be constructed based on input from e.g. booking, shipment, vessel schedule etc. true true Transactional Internal N/A
Equipment Itinerary 74a21a59-2a27-ed11-a1a0-bf3947c3094d Container Itinerary true A general itinerary for equipment. In certain cases the itinerary cannot be for a container only, for example if is not always based on a container number, in which case it is needed to have the generic equipment level fields available for handling that. true true Transactional Internal N/A
Container Itinerary Type a7a025a2-499e-eb11-ade6-40b034e2c22b Container Itinerary true Examples of itinerary types: Commercial Vessel Sharing Empty Inland true false Reference Internal N/A
Vessel Incident 02530381-b4fc-e911-80eb-9cd21e38f3a4 Vehicle Event true Special event for incidents that occur to a vessel. true true Transactional Internal N/A
Vehicle Event 07931011-71f5-11f0-65ed-e2196509a2e3 Vehicle Event true true true Transactional Internal N/A
Truck Event 0793101d-71f5-11f0-65ed-e2196509a2e3 Vehicle Event true Examples of event triggers: Exit Facility Enter Facility Stopped Started GPS reading true true Transactional Internal N/A
Vessel Event 1f500381-b4fc-e911-80eb-9cd21e38f3a4 Vehicle Event true Actions and happenings involving a Vessel. Examples of event triggers: Fueling start Fueling end Entry into fleet Removal from fleet Rebuild start Rebuild end Dry dock period start Dry dock period end Example of event: The vessel's entry in to the fleet. Since these events can recur (i.e. a vessel can be taken out of a fleet and can later be brought back in) this data cannot be a set of simple attributes of the Vessel entity. true true Transactional Internal N/A
Fuel Delivery 27500381-b4fc-e911-80eb-9cd21e38f3a4 Vehicle Event true Special event for fuel delivery to a vessel. true true Transactional Internal N/A
Vessel Incident Type fe520381-b4fc-e911-80eb-9cd21e38f3a4 Vehicle Event true Used for keeping a list of incident types and names for incidents that can occur for a Vessel. For example "Fire" or "Oil Spillage". true false Reference Internal N/A
Equipment Event e54d0381-b4fc-e911-80eb-9cd21e38f3a4 Equipment Event true An event involving an item of Equipment being physically moved or having another action done like sealing or inspection. The equipment event is a super class of more specific events like container events. At the equipment event level trailer, chassis, ULD events can be recorded in case they do not need specialisation. Business terminology: Generally anything that constitutes a physical movement of container/equipment is referred to as "Equipment Move" anything else is "Equipment Event". Versioning: Events should be versioned so that full traceability is possible. I.e. if a planned gate out event exist for a piece of equipment set to 2021-10-10 and the transport plan is then updated to have gate out at 2021-10-11 both equipment events should be persisted somewhere. Inspection example: An equipment event could be an inspection that has been carried out. E.g. a pre-trip inspection or CSC inspection. Logging such an equipment event the event trigger would be set to e.g. "Inspection Pre-trip" or "Inspection CSC". The scope of the inspection can include the equipment item itself and/or other items of attached to it (e.g. a generator set or RCM device). true true Transactional Internal N/A
Container Event 20e45fe1-459e-eb11-ade6-40b034e2c22b Container Event true A specialisation of an Equipment Event specific to containers - note that this covers anything that has an ISO container number, e.g. also flat racks and tank containers etc. The container event is used for Container Itinerary such that the itinerary can "build" a list of planned container events from shipment and/or transport plan (aka. Shipment Route). The container event naturally inherits all properties of both Event and Equipment Event through its inheritance hierarchy. This means that Event Trigger, Event Timing etc. is defined not on the Container Event itself but on the super classes. true true Transactional Internal N/A
Financial Job Line 71efa853-eef6-ec11-a406-a0510b9e9705 Job Costing true An item line in a Financial Job, relating to one single estimate of either a cost or a revenue for the related Financial Job. The quantities and monetary amounts involved are expressed in the form of a charge. true false Transactional Confidential Competitive Strategic Information
Financial Job c809f529-eef6-ec11-a406-a0510b9e9705 Job Costing true A Financial Job is an instance of a "Job" within the accounting process known as "Job Costing". The word "Financial" before "Job" is used here for the purpose of disambiguation with the HR definition of Job. Job costing is accounting which tracks the costs and revenues by "job" and enables standardized reporting of profitability by said job (like an overall profit & loss statement for the firm, but is specific to each job number). So, typically to support job costing, one must allow job numbers to be assigned to individual items of expenses and revenues. A job can be defined to be a specific project done for one customer, or a single unit of product manufactured, or a batch of units of the same type that are produced together, which means one can have a job per any sensible business item/ concept: container, truck, aircraft, equipment, bill of lading, transport document, shipment, cargo, etc. Costs and revenues are recorded in ledger accounts throughout the life of the job and are then summarized in the final trial balance. When all costs and revenues are realized, the job is "closed" and its final P&L statement issued. Currency and Exchange Rate A Financial Job header only has 1 currency and doesn't need an exchange rate. It's the individual Financial Job Lines that will carry multiple currencies and related exchange rates. In other words, individual Financial Job Lines might have different exchange rates and currencies. true true Transactional Confidential Competitive Strategic Information
Chart Of Accounts 43f3df2d-1bb2-ee11-b872-44e517a1f1d9 Chart of Accounts true A collection of General Ledger Accounts that must be applied to the recording of all financial accounting transactions for a given organisational unit(s) and/or business unit(s). A Chart of Accounts is typically legally mandatory within local laws of a specific country (or countries in some special cases). For intents of corporate reporting, Charts of Accounts can be hierarchically placed under Group Chart of Accounts (hence the parent child relationship), so that different local Ledger Accounts and General Ledger Accounts can be sensibly and clearly corresponded to one uniform Group General Ledger Account. true true Master Internal N/A
Ledger Account 503d3a81-b4fc-e911-80eb-9cd21e38f3a4 Chart of Accounts true An account from a Chart of Accounts that supports and enables the recording of financial accounting transactions, in a way that is consistent with applicable financial accounting rules, and which supports the production of financial statements. Ledger Accounts come largely in 3 types, depending on which Chart of Accounts they belong to (the types must therefore be obtained by the related Chart of Accounts): Group Ledger Account: an account from the Group Chart of Accounts, that can be used as the basis of consolidated financial statements for the Maersk Group. General Ledger Account: an account from the Operational Chart of Accounts, that will be used to record daily financial accounting transactions. Country Ledger Account: an account from a Country Chart of Accounts (there will be a chart for each country) that must correspond to a General Ledger Account, as is used for compliance with local laws and regulations, as well as local reporting. Ledger Accounts from one Chart of Accounts can match and correspond to Ledger Accounts from different Charts of Accounts. The different types relate in this way: 1 General Ledger Account must match 1 Group Ledger Account (but 1 Group Ledger Account can match multiple General Ledger Accounts). 1 Country Ledger Account must match 1 General Ledger Account (but 1 General Ledger Account can match multiple Country Ledger Accounts). true true Master Internal Competitive Strategic Information
Invoice 1a540381-b4fc-e911-80eb-9cd21e38f3a4 Invoice true A document issued by a seller to a buyer, relating to a sales transaction, and indicating the products, quantities, and agreed-upon prices for products or services the seller has provided to the buyer. From a seller's point of view, an Invoice is a Sales Invoice. From a buyer's point of view, an Invoice is a Purchase Invoice. Therefore, a Sales Invoice will be issued by Maersk (i.e. Maersk is the seller), and a Purchase Invoice will be issued to Maersk (i.e. Maersk is the buyer). true true Transactional Confidential Competitive Strategic Information
Invoice Line 2b540381-b4fc-e911-80eb-9cd21e38f3a4 Invoice true A Line in an Invoice, containing the details on the charge (quantities, amounts, price, currency, etc.). true true Transactional Confidential Competitive Strategic Information
Invoice Relation 76ed0633-d75c-ee11-a1bb-fab3d952de1e Invoice true Specifies a relation between different Invoices. true false Transactional Internal N/A
Invoice Relation Reason 78ed0633-d75c-ee11-a1bb-fab3d952de1e Invoice true The purpose to why the Invoices have been related. true false Reference Internal N/A
Payment Mode Supplement 59aa3363-4518-ef11-b88e-44e517a1f1d9 Payment Terms true Provides additional details, or variations, for a specific payment method. These details or variations can cover may different topics, and often serve as a means to provide additional instructions. They are typically mastered on a finance and accounting transaction system. true false Reference Internal N/A
Payment Term 9c454be7-783b-ea11-b540-b46bfcaea91a Payment Terms true Payment terms that are agreed between a seller and a buyer. Examples: Credit Cash on Delivery (COD) Cash in Advance (CIA) Payment in Advance (PIA) Forward Collection Bill of Exchange - A promise to pay at a later date, usually supported by a bank Letter of Credit - A documentary credit confirmed by a bank, often used for export Note: Some of these values are given in order references today. See also: https://www.unece.org/fileadmin/DAM/cefact/recommendations/rec17/rec17_1982_ecetrd142.pdf https://www.nibusinessinfo.co.uk/content/payment-terms-commonly-used-invoice-payment-terms-and-their-meanings true true Reference Internal N/A
Payment Condition a4468634-ed51-ec11-a3e3-a0510b9e9705 Payment Terms true The way in which a payment is agreed to be performed. It's a combination of 3 elements (those 3 elements being master data classes of their own): The what (Payment Mode): what mode is use to perform the payment, such as: wire transfer, cash, credit card, etc. The how (Payment Term): how payment will be performed, such as: on credit, on delivery of goods, in advance, etc. The when (Credit Term): at what moment must be payment be performed, such as: immediately, in 30 days, 7 days after a designated moment, at end of the month, etc. It should be noted that we can specify a Payment Condition to either customers or vendors of Maersk, and that we can also specify them for one specific transactional use (one time only), or for a long-term use, namely within the context of an Agreement. true false Reference Public N/A
Credit Term ed1bf1b9-bbe3-ea11-a3b7-a0510b9e9705 Payment Terms true Credit terms that are agreed between a seller and a buyer. Examples: Net 7 - Payment seven days after invoice date Net 10 - Payment ten days after invoice date Net 30 - Payment thrity days after invoice date Net 60 - Payment sixty days after invoice date Net 90 - Payment ninety days after invoice date EOM - End of month 21 MFI - 21st of the month following invoice date 1% 10 Net 30 - 1% discount if payment received within ten days otherwise payment 30 days after invoice date true true Reference Public N/A
Financial Order Line Allocation 3578fd08-eb22-ed11-a415-a0510b9e9705 Financial Order true Financial Order Lines can relate to each other. This relation is between Financial Order Lines of different Financial Orders. This typically happens when a Purchase Order Line must be related to 1 or many Sales Order Lines, in order to specify: how much a Sales Order Line represents in a Purchase Order Line.As an example: if there are 4 Sales Order Lines of quantity 40 to 1 Purchase Order Line of quantity 160, then each related Sales Order Line represents 25% of the Purchase Order Line how much of a Sales Order Line was allocated to a Purchase Order Line.As an example: if a Sales Order Line has quantity 100, but only 50 relate to a Purchase Order Line. true false Transactional Internal N/A
Financial Order 392cc8f4-285c-ec11-ab9a-5c879c3c5a54 Financial Order true The Financial Order is an abstract concept, that refers to both Purchase Order (PO) and Sales Order (SO), generalising them. In other words, PO and SO are subtypes of Financial Order. This is done for ease of modelling, as the attributes and relationships of both PO and SO are largely (if not all) the same. A Purchase Order (PO) is a commercial document issued by Maersk to a supplier or vendor, indicating types, quantities, and agreed prices for products or services that Maersk wishes to buy and/or contract from said supplier or vendor. This document is subsequently used to control the purchasing and delivery/ execution of the contracted products and services. The sales order (SO), is an order issued by Maersk to a customer, for products and/or services purchased by said customer. An SO is an internal document, meaning it is generated by Maersk itself. This document is subsequently used to control the delivery/ execution of the contracted products and services. true true Transactional Confidential Competitive Strategic Information
Financial Order Line f624dca4-e94d-ec11-ab99-5c879c3c5a54 Financial Order true An item line within a Purchase Order or Sales Order. The quantities and monetary amounts involved are expressed in the form of a charge. true false Transactional Confidential Competitive Strategic Information
Related Accounting Transaction c31b5443-d511-ef11-b88c-44e517a1f1d9 Accounting Transaction true Accounting Transactions can relate to other Accounting Transactions for multiple reasons. This class allows to represent such relationships. Among others, the reasons for Accounting Transactions to relate to each other might include: cancelling and/or correctiing Accounting Transactions, clearing and/or consolidating records, fiscal period closing, accruals, etc. true false Transactional Internal N/A
Accounting Transaction Line e13c3a81-b4fc-e911-80eb-9cd21e38f3a4 Accounting Transaction true A debit or credit record, known as a "posting" in accounting jargon, of a currency amount made against a General Ledger Account. Note on Tax Amounts: It should be noted that by definition Accounting Transaction Lines cannot have an amount for tax. This is because any tax amounts must be recorded in their own separate Accounting Transaction Line instances, due to the rules of accounting, namely these rules: The sum of all debits must equal the sum of all credits. Tax amounts are posted against their own General Ledger Account. Example: Let's imagine we are making an Accounting Transaction to record an invoice for Office Supplies, where we purchased 500 EUR of Office Supplies, taxed at 20% VAT. We will have these 3 instances of Accounting Transaction Lines (for simplicity, let's ignore Transaction Currency and Group Currency): Line 1: General Ledger Account Number = 4100000; General Ledger Account Name = Bank Current Account; Local Currency Amount = 600; Local Currency = EUR; Account Posting Type = Credit Line 2: General Ledger Account Number = 5221000; General Ledger Account Name = Office Supplies; Local Currency Amount = 500; Local Currency = EUR; Account Posting Type = Debit Line 3: General Ledger Account Number = 2505000; General Ledger Account Name = Input VAT; Local Currency Amount = 100; Local Currency = EUR; Account Posting Type = Debit Notice how debits equal credits (600 = 500 + 100), and how the tax amount has its own line (Line 3). true false Transactional Confidential N/A
Accounting Transaction ea3c3a81-b4fc-e911-80eb-9cd21e38f3a4 Accounting Transaction true An official record, on the financial accounting ledgers, of a financial transaction ocurred within a company, or between said company and a third party. This can include recording sales and purchases performed by a company, as well as bank transfers, asset purchasing and depreciations, investments, expenses, or salaries, among many other possible financial transactions. Accounting transactions are typically recorded for both internal auditing, external auditing, internal reporting, external reporting, and/or legal and local law requirement reasons. Once created, an Accounting Transaction instance can never be deleted, as that would violate legal rules of accounting. Instead, a "cancelling" Accounting Transaction instance must be created, whereby postings of the original Accounting Transaction instance are reversed. No Totals or Quantity Fields Due to the nature of how accounting transactions work, i.e. the accounting "golden rule" that the sum of all debits in an accounting transaction must always be equal to the sum of all credits in the same accounting transaction, the total amount of all Accounting Transactions (i.e. the sum of all its lines) is by definition always zero, and can never be anything other than zero. Therefore the Accounting Transaction class (i.e. the "header") does not have, and can never have, attributes for recording totals or amounts. Fiscal Periods The fiscal period, typically fiscal month and fiscal year, to which the Accounting Transaction belongs to, shall be obtained via relationship with Time Period. An Accounting Transaction will typically have 1 fiscal month, and the fiscal month in turn has 1 fiscal year. true true Transactional Confidential N/A
Tax Jurisdiction 00393a81-b4fc-e911-80eb-9cd21e38f3a4 Tax true The tax jurisdiction defines the tax authority to which taxes must be paid. Such tax authority will depend on the geography (country, region, state, etc., or any group of such geographic elements) on which such authority holds the jurisdiction. A tax jurisdiction can be responsible for defining multiple different taxes of different tax types, as well as the possible tax rates within each tax. true false Master Internal N/A
Tax Category 1d11b943-d8d1-11ef-04e0-922eb47883a8 Tax true A category, potentially belonging to a set of categories, defined by the Tax Authority of applicable Tax Jurisdiction, under which the Tax Authority categorizes and groups tax payers, typically for statistical and/or processing purposes. true false Reference Public N/A
Tax Rate 220315f9-d022-ed11-a415-a0510b9e9705 Tax true A rate at which a tax can be levied. Taxes often have multiple different tax rates with different specific applicabilities. For instance: value added taxes may have different rates according to the type of product or service, income taxes may have different rates according to the type and amount of income, etc. It should be noted that tax rates are considered master data from a Finance perspective, and therefore are modelled as such. true false Master Internal N/A
Tax Identification Type 384a0381-b4fc-e911-80eb-9cd21e38f3a4 Tax true Indicates the type of Tax Identification. Examples include: - Tax Number 1, Tax Number 2 - VAT Number (Value Added Tax) - ICMS - IPI - ICMS Law - IPI Law - SubTrib Number (Tax Substitution) - PAN Number - TIN/SSN (SSN in this case used in the US as tax number for one-man businesses, e.g. truckers) true false Master Internal N/A
Tax Requirement 5f629d3d-5d18-ef11-b88e-44e517a1f1d9 Tax true Identifies the applicable requirements (if any) to a particular set of Tax Information. This is done together with the Tax Jurisdiction (typically at Country level) that the Tax Information belongs to. For example, if the Tax Requirement is "Registered", and the Tax Jurisdiction (country) is India, then having Tax Identifications "Tax No1" and "Tax No 3" is mandatory. true false Master Internal N/A
Tax Type 66690b68-d122-ed11-a415-a0510b9e9705 Tax true Indicates the type of Tax. Possible types include: income tax, trade tax, duty tax, value added tax, etc. true false Master Internal N/A
Tax 6ec85787-5ebf-ee11-b875-44e517a1f1d9 Tax true Taxes are mandatory contributions levied on individuals or corporations by a government entity, whether local, regional, or national. Tax revenues finance government activities. From an accounting perspective, there are various taxes to consider, including payroll taxes, federal and state income taxes, and sales taxes. true true Master Internal N/A
Withholding Tax a9dc1a43-951d-ef11-b890-44e517a1f1d9 Tax true Tax withholding (also known as tax retention, pay-as-you-earn tax, or tax deduction at source) is income tax paid to the government by the payer of the income, rather than by the recipient of the income. The tax is thus withheld or deducted from the income due to the recipient. IT SHOULD NOT BE CONFUSED WITH A TYPE OF TAX. Withholdong tax is a means to collect tax, not a type of tax. In most jurisdictions, tax withholding applies to employment income. Many jurisdictions also require withholding taxes on payments of interest or dividends. In most jurisdictions, there are additional tax withholding obligations if the recipient of the income is resident in a different jurisdiction, and in those circumstances withholding tax sometimes applies to royalties, rent or even the sale of real estate. Governments use tax withholding as a means to combat tax evasion, and sometimes impose additional tax withholding requirements if the recipient has been delinquent in filing tax returns, or in industries where tax evasion is perceived to be common. true false Master Internal N/A
Tax Exemption abdc1a43-951d-ef11-b890-44e517a1f1d9 Tax true Defines a case where an exemption from a tax or a withholding tax is applicable. true false Master Internal N/A
Tax Exemption Reason addc1a43-951d-ef11-b890-44e517a1f1d9 Tax true Defines an official reason that can be invoked for a tax or a withholding tax exemption. true false Master Internal N/A
Tax Recipient afdc1a43-951d-ef11-b890-44e517a1f1d9 Tax true Defines an official type of tax recipient that is subject to the related tax and/or eligible for related withholding tax. Examples include: residents, non-residents, dividends, domestic vendors, partnerships, identity card, etc. true false Master Internal N/A
Withholding Tax Type e187513e-f91c-ef11-b890-44e517a1f1d9 Tax true Specifies the type of Withholding Tax. true false Master Internal N/A
Charge 3f373a81-b4fc-e911-80eb-9cd21e38f3a4 Charge true Charge represents a line with a monetary amount, and other related financial details, typically pertaining to the cost of an item and/or service. Multiple different objects can have Charges attached to them, ranging from Invoices, Purchase Orders, Rates, or Transport Documents, just to name a few, which means the Charge can represent both an actual due amount, as well as merely the description of an agreed one. Note on Demurrage and Detention charges: Pricing tier for demurrage and detention will be handled using upper and lower rate basis value. For example demurrage can be 100 USD from day 10 to day 14 and 200 from day 15 - day 25. The rate basis will be set to Per Time Period and unit to Day. true true Transactional Internal N/A
Rate Basis a7373a81-b4fc-e911-80eb-9cd21e38f3a4 Charge true The basis for the rate basis value which is used to calculate the charge amount. For instance: Example Values: Per Unit/ Item (default value: simple count) Per Container Per Chassis Per Unit Load Device (ULD) Per % of other Charge Per % of sum of other Charges Per Cargo Item Per Cargo Package Per Volume Per Weight Per Best of Weight or Volume Per Transport Document Per Time Period (hour, day, month, etc.) When required, the Rate Basis will also specify the applicable Unit of Measurement. For instance, for charges per volume, we need to specify if the volume is measured in litres, cubic meters, or cubic feet. It's also possible to have a rate basis that is based in more than one criteria. For instance, a storage charge that is both per kg and per day. If one has to pay 10 USD for each kg on each day of storage, and we store 5kg for 4 days, then the total charge amount is: 10 x 5 x 4 = 200 USD. For this reason, it's allowed to array Units of Measurement under Rate Basis. It's also possible to have a Rate Basis based on another Charge (or Charges) instance. For example a fee charge of 5% over a freight charge. For this reason, we have a the relationship "based on charges" from Rate Basis back to Charge. true true Reference Public N/A
Rate Basis Type ea7e681f-b28f-ef11-b8ac-44e517a1f1d9 Charge true The type of rate basis which is used for the Rate Basis. For instance: Example Values: Per Unit/ Item (default value: simple count) Per Container Per Chassis Per Unit Load Device (ULD) Per % of other Charge Per % of sum of other Charges Per Cargo Item Per Cargo Package Per Volume Per Weight Per Best of Weight or Volume Per Transport Document Per Time Period (hour, day, month, etc.) true true Reference Internal N/A
Validation 50492a31-4ab3-ee11-a1c0-97e99c96f3d2 Validation true A single validation of a data object. A data object can contain any number of validations. This can be used to communicate any errors, warnings, informations about a data object. true false Transactional Internal N/A
Term Postfix Configuration 8c6ff0ba-62f8-ee11-a1c1-a83983aea769 Alternate Term Dictionary true Allowed terms and postfixes that in combination yields a match if a term is validated against them. For example, if the term "portOfDischargeCode" is given for comparision, and the list of permitted terms has "portOfDischarge" and the list of permitted postfixes contains" Code", it will be a match. true false Master Internal N/A
Alternate Term Dictionary aa67fe93-61f8-ee11-a1c1-a83983aea769 Alternate Term Dictionary true Represents a dictionary containing one or more terms that are allowed as alternate matches. true false Master Internal N/A
Term Alias ad67fe93-61f8-ee11-a1c1-a83983aea769 Alternate Term Dictionary true A term listed in an alternate term dictionary, for example, a Maersk Domain Model term like "Invoice" could be listed, if it has aliases like "Billing Document", and that alias is considered to be allowed to use instead of "Invoice". true false Master Internal N/A
Batch 24f290ab-19d6-ee11-a1c1-a83983aea769 Event Notification true Information about batching to allow consumer to assemble all necessary message payloads that must together be considered a batch. true false Transactional TBA N/A
Message 29e5343b-8382-ee11-a1be-d7e14702d112 Event Notification true Payload envelope for an embedded message of the event stream notification. The content of this should be replaced with whatever object is relevant to communicate with the event. For example it could be an object representing a Packing List. true false Transactional Internal N/A
Event Stream Notification Header 40dbf324-8182-ee11-a1be-d7e14702d112 Event Notification true Transport layer headers that can be utilized before deserialization of the payload true false Transactional Internal N/A
Event Stream Notification 438f701d-8182-ee11-a1be-d7e14702d112 Event Notification true A wrapper for communicating events for streaming technology e.g. Maersks Kafka implementation to send a notification with a small message payload and/or with claim check. true false Transactional Internal N/A
Resource 957eddec-aa82-ee11-a1be-d7e14702d112 Event Notification true Gives the receiver information about what type of resource is available as the message data. I.e. MDOM model and model version. true false Reference Internal N/A
Meta Data b440d15e-a982-ee11-a1be-d7e14702d112 Event Notification true Meta data about the message send within this payload envolope. true false Transactional Internal N/A
Event Stream Notification Key c07ac92f-8182-ee11-a1be-d7e14702d112 Event Notification true Key used for partitioning the events in the stream. true false Transactional Internal N/A
Causation Id c9ac3aad-a982-ee11-a1be-d7e14702d112 Event Notification true Child identifiers that create an Event Notification. E.g. Customer Order identifiers for a Shipper Booking, Sipper Bookings for Carrier Booking etc. true false Transactional Internal N/A
Resources cbbb9544-4a83-ee11-a1be-d7e14702d112 Event Notification true Meta data about where the message data is stored in case it is not part of the event stream notification itself, e.g. if the data is too large to be sent but instead stored in a BLOB storage or custom API for the consumer to fetch. true false Transactional Internal N/A
Storage ec32fea8-ab82-ee11-a1be-d7e14702d112 Event Notification true Meta data about where the message data is stored in case it is not part of the event notification itself, e.g. if the data is too large to be sent but instead stored in a BLOB storage for the consumer to fetch. true false Transactional Internal N/A
File 080da1c3-ef5a-ef11-8190-db4390e09088 Generics true A generic File class to be used to provide details of file attachments that are attached to either the header or Line. It includes details about the file name, path, extension and content type true false Transactional Confidential N/A
Header 25561dee-0c6e-ee11-a1be-d7e14702d112 Generics true A generic header class to be inherited by any class that represents a header, e.g. booking, packing list and so forth. true false Transactional Internal N/A
Line 27561dee-0c6e-ee11-a1be-d7e14702d112 Generics true A generic line class to be inherited by any class that represents a line, e.g. booking line, packing list line and so forth. true false Transactional Internal N/A
Data Object 85638bdb-0c6e-ee11-a1be-d7e14702d112 Generics true Data object with soft coded values and additional measurements. true false Transactional Internal N/A
Expired Business Identifier e64faee5-0c6e-ee11-a1be-d7e14702d112 Generics true Expired business identifier for a data object. Scenario: When a customer sends an order where the customer order number has changed, the previous order number can be stored here. It is of course necessary that customer sends both previous and new order number for Maersk to handle this scenario. The customer order lines need to also have their previous identifers stored here as they will typically comprise of the order number together with some other data.\n\nSame goes for Shipper Bookings, Packing Lists etc. that Maersk can receive from external. If the business identifers change, the previous ones are stored here. true false Transactional Internal N/A
Function 0c395c55-fe2a-eb11-add0-40b034e2c22b Feature Toggling true Specific functions within a feature area of a system. Examples: NSCP Document Management Document Management Document Upload Pouch Sbmission Administration Configure Customer true false Reference Internal N/A
Feature Type 3829a5b3-542d-eb11-add2-40b034e2c22b Feature Toggling true A way to group features in to specific types like integration or uder interface. Examples: Integration User Interface true false Reference Internal N/A
Feature Toggle 5d260adf-052b-eb11-add0-40b034e2c22b Feature Toggling true Entry will enable a feature within a system in the toggle profile. true false Reference Internal N/A
Feature 6597154d-fe2a-eb11-add0-40b034e2c22b Feature Toggling true Features of a system may fall in to categories of integration or user interface etc. This is set via the Feature Type. Examples: NSCP Alerting and Exception Rules Management Escalation Management NSCP Load Planning Rules Management NSCP Document Management Document Management Administration NSCP Origin Management Customer Order Upload Shipper Booking Shipper Booking Upload Packing List NSCP Transport Management Pre-advice Advance Shipment Notification NSCP Event and Milestones Standard 6+2 true false Reference Internal N/A
Capability 6897154d-fe2a-eb11-add0-40b034e2c22b Feature Toggling true A list of systems, capabilities, micro services etc. that can be configured to be part of a toggle profile. Examples: NSCP Destination NSCP Document Management NSCP Alerting and Exception NSCP Event and Milestones NSCP Detention and Demurrage NSCP Load Planning NSCP Supply Chain Intelligence NSCP Self Service Business Intelligence NSCP Origin Management NSCP Transport Management true true Master Internal N/A
Capability Toggle 7552f05f-052b-eb11-add0-40b034e2c22b Feature Toggling true Entry will enable the system in the toggle profile. true false Reference Internal N/A
Function Toggle abb2440f-062b-eb11-add0-40b034e2c22b Feature Toggling true Entry will enable a function of a feature within a system in the toggle profile. true false Reference Internal N/A
Toggle Profile aec15b1f-052b-eb11-add0-40b034e2c22b Feature Toggling true A feature toggling profile that can be either default (no party associated) or can be for a specific party. true false Reference Internal N/A
Country 3f3a3a81-b4fc-e911-80eb-9cd21e38f3a4 Geography true A nation with its own governement, occupying a particular territory. Note: Maersk takes into consideration only the countries recognised by UN. International Standard Organization information about a country (ISO 3166-1): This list of countries is from the ISO 3166-1 standard (Part 1 - Country codes, defines codes for the names of countries, dependent territories, and special areas of geographical interest. It defines three sets of country codes). Note on ISO 3166: There are multiple parts to this standard. Part one are the countries and part 2 are the subdivisions of countries. true true Master Public N/A
Location 4538cadd-7383-ee11-a1be-d7e14702d112 Geography true A generic location which can represent either a simple location object on its own or be used via one of its subtypes like Defined Area, Facility etc. true true Master Internal N/A
Defined Area 4a3a3a81-b4fc-e911-80eb-9cd21e38f3a4 Geography true A geographically delimited area which has positional, commercial, jurisdictional, administrative or economic significance. Examples: - Continent - Country - Territorial Unit - City - Site - Zone - Region - Subdivision Locations can be associated with a geographic boundary, information about addresses and postal code, information about the time zones applicable in different geographic boundaries and specific geographical coordinates. Notes on subtypes: A Defined Area need not be fully specialised in a sub-classes like for example Country is. It can be a Defined Area by itself together with a specific type, e.g Liner Operation Cluster, which "contains" countries and/or cities managed via the Defined Area Relationship. Note on relationships between Defined Areas: The name or function of any relationships that the Defined Area can have with other Defined Areas, e.g. NATO, NEU Sales Region, EU, Nearest Port and so on, are managed via the Defined Area Relationship Type. true false Reference Public N/A
City 523a3a81-b4fc-e911-80eb-9cd21e38f3a4 Geography true City in a country and/or in a subdivision, e.g. Charlotte in North Carolina in the United States of America. true true Master Public N/A
Perimeter Point 563a3a81-b4fc-e911-80eb-9cd21e38f3a4 Geography true A point in a series of longitude and latitiude pairs that make up a geographic pertimeter. The longitude and latitude pair dotted on a map in the specified sequence will create the geographic perimeter. These data can be used as input to map software to create an "overlay" graphic to display the geographic perimeter (aka. geofence). true false Master Internal N/A
Position 7f2eba87-f8a2-eb11-8314-061ca927c90b Geography true Represents a position in longitude and latitude as well as altitude. true false Master Internal N/A
Location Function 8aed32ad-ed4e-ea11-ad9c-40b034e2c22b Geography true A "Location Function" will specify what purpose the relationship with the location serves. Many times this will be a specific site but can also be a country if the function is for example "Origin". Examples of such could be that a location should be treated as a: - Free on Board Point - Free on Board Country - Hub Port - Port of Loading - Port of Discharge - Final Destination - Place of Origin - Place of Receipt - Place of Delivery - Place of Transshipment - Shipper Place of Delivery - Carrier Place of Delivery - FCR Release Place - Origin - Empty Equipment Pickup - Empty Equipment Return - Global Procurement Office - Warehouse - Ship To - Drop - Ship To - Distribution Center - Ship Via - Supplier Site - INCO Term Location - Customs Clearance Location - Place of Transaction - Foreign Port - Container Stuffing Location - Terminal - Packing Location - Redelivery Location (used for Lease Agreement so one way lease can indicate where to return equipment to) Note: It is advisable to align these to the UNECE code list for location functions: https://service.unece.org/trade/untdid/d19b/tred/tred3227.htm true false Reference Internal N/A
Subdivision ae5fc756-60a4-ec11-abac-5c879c3c5a54 Geography true A subdivision can be a any geographic boundary that a country contains, e.g. states, provinces, counties, emirates. Subdivisions are also used for cities, where they can be boroughs, districts, arrondissements, etcetera. In contrast with country subdivisions, city subdivisions are less strictly governed. Several territorial units within countries have an ISO standard code, e.g. the 7 emirates in UAE one of them is AE-AZ Abu Zaby [Abu Dhabi]. ISO 3166-2 is part of the ISO 3166 standard published by the International Organization for Standardization (ISO). It defines codes for the names of the principal subdivisions (e.g., provinces or states) of all countries coded in ISO 3166-1. The official name of the standard is Codes for the representation of names of countries and their subdivisions - Part 2: Country subdivision code. It was first published in 1998. Note on ISO 3166: There are multiple parts to this standard. Part one are the countries and part 2 are the subdivisions of countries. true true Master Internal N/A
Location Relationship c4956485-9640-ee11-a1b8-cb7e5cf1e083 Geography true Depicts the various and complex associations between Locations. This includes relationships between "Business Defined Areas" (BDA), "Defined Areas" (DA), or both. The relationship can also be between a City and a Facility, or 2 cities, to denote e.g. the "Nearest CY" to a city or "Nearest City" to another city. Another example is "Capital of", e.g. Melbourne is the capital of Victoria, Canberra is the capital of Australia. true false Master Internal N/A
Site d4393a81-b4fc-e911-80eb-9cd21e38f3a4 Geography true A site is a location that is of relevance to the enterprise, it can be a harbour, inland point etc. true true Master Public N/A
Continent db7e4b4e-c0c3-ee11-a1c0-97e99c96f3d2 Geography true Continent true true Master Internal N/A
Defined Area Status ed393a81-b4fc-e911-80eb-9cd21e38f3a4 Geography true Contains statuses that a Defined Area can be assigned. Could be used to denote clean-up statuses as well Examples: - Update Required - Cleansing Required - Cleansing in Progress - Incomplete true false Reference Internal N/A
Location Relationship Type f6393a81-b4fc-e911-80eb-9cd21e38f3a4 Geography true Describes how Locationss can be related. Examples: BDAC - Business Defined Area ContentFor the relationship between a Defined Area like Cluster or Sales Region and the Countries and Cities that belongs to them. NECY - Nearest Container YardTo relate the nearest Facility, that has a container yard, from a City. NTRM - Nearest Marine Container TerminalTo relate the nearest Facility, that has a terminal, from a City. NRAI - Nearest Rail Drop OffTo relate nearest Facility, that has a rail, from a City. NCTY - Nearest CityUsed for some remote Facilities that is not in any City, so that the nearest City can be derived. PART - Part ofUsed for maintaining relationship to Subdivision (for example the state of North Carolina) is part of a country (for example United States of America).Further examples where "part of" can be used to define the relationship be for Administrative Regions like UN Region, UN Sub-Region, NAFTA Region (Economic region), CAFTA Region (Economic region), NATO. true false Reference Internal N/A
Defined Area Type fa393a81-b4fc-e911-80eb-9cd21e38f3a4 Geography true Specifies the type of defined area and can be used for setting custom type defined areas used in Maersk, like Cluster, Area etc. Top level Defined Area types: Business Defined Area Country Subdivision City Postal Code Subdivision subtypes: The classification type of a subdivision which can be a any geographic boundary that a country contains. State Province County Emirate District Borough Business Defined Area subtypes: Subtypes of Business Defined Area (BDA): ClusterSometimes referred to as Country Cluster or just Cluster. The important thing is that these can actually consists of both countries and cities and therefore the name Cluster or Country Cluster is not really good. This wording is chosed to be more high level and can therefore be used for other types of clusters e.g. 'North China, 'South China' and 'East China'. Area Flow Area PoolA Business Defined Area defined for the purpose of recording equipment flows and associated empty equipment costs. RegionA Business Defined Area grouping together a set of Zones, e.g. the "North American" region (NAM) and the "European" region (EUR). ZoneA Business Defined Area - which may be defined for financial/economic reasons - containing a set of Ports, e.g. the "West African" zone and the "Indian Ocean Islands" zone. City Sub Area A Business Defined Area within a City - which may be defined for pricing or inland delivery reasons. Cluster subtypes: Liner Operation ClusterA geographic cluster which is grouping sites (operational facilities) Reefer Operation Cluster Financial ClusterA geographic cluster grouping countries or locations for financial purposes. Also sometimes referred to as Subareas. Country ClusterA geographic cluster grouping countries. Other examples: Territory Cabotage Region Canton District Parish Governorate Department Federal Island Autonomous Republic Rayon Jurisdictional Zone Federal Zone Administrative Region true false Reference Internal N/A
Location Association 62457bc0-aeae-ea11-adb4-40b034e2c22b Location Association true This class represents transactional data (not Master Data). The related Master Data classes are reachable via this class. A data object can specify a number of locations related to the transport. Examples: - Service Plan: These locations must be specified in the Service Plan associated to the Shipper Booking and derived from there. If those locations are to be placed at this level as well they must be kept up to date with Service Plan level locations. - Customer Order Line: A Customer Order Line (COL) can specify a number of desired locations for the transport. These typically are sent via EDI with the COL to Maersk. Examples: Free on Board Point, Incoterm location and Destination. - Cargo Stuffing: For locations that are only relevant to the CS, these can be specified at this level, e.g. Container Stuffing Location. - Commercial Invoice: For locations that are only relevant to the CI, these can be specified at this level. - Forwarders Cargo Receipt: For locations that are only relevant to the FCR, these can be specified at this level. Note that print locations are handled at Transport Document level. - Packing List: For locations that are only relevant to the PL, these can be specified at this level, e.g. Packing Location. - Shipping Instruction: For locations that are only relevant to the SI, these can be specified at this level, e.g. Required Original BL Print Place, Required Telex Release Place. Why are locations needed on this level? Locations are needed on the indivudal document levels like Packing List, Commercial Invoice, Cargo Stuffing etc. because it is possible to mix Shipper Booking Lines from multiple Shipper Bookings and these can have all have different locations on their Service Plan. That means that there is no single place that stores the correct locations for the related documents. The correct locations must be derived at time of creation of the document and can then be actively modified by users, but only within the allowable locations according to the Service Plans which are related to the Shipper Bookings. true false Transactional Internal N/A
Time Zone ee383a81-b4fc-e911-80eb-9cd21e38f3a4 Time Zone true The Time Zone class, as part of a local time system, is modeled after the TZ (Time Zone) database. This class is designed to provide comprehensive support for world time zones. true true Reference Public N/A
Daylight Saving Time Displacement fa383a81-b4fc-e911-80eb-9cd21e38f3a4 Time Zone true This entity holds data required to derive the proper DST via rules. Contains the individual daylight savings time displacement, meaning the offset in minutes from the time in the timezone (be aware that the timezone has offset from UTC!). The displacement has a start and end date and time, where the displacement will take and cease effect. (see http://www.unit-conversion.info/othertools/daylight-saving-time/ for details). Example of how the data is held: Daylight saving time in Portugal in 2022 From: Tuesday March 29, 2022 Until: Tuesday October 25, 2022 (see https://www.timeanddate.com/worldclock/full.html for details on timezones). true true Reference Public N/A
Job Requisition 07346996-04d5-eb11-ab86-5c879c3c5a54 Job Position true The Job Requisition includes many details that will later compose the information for Worker and Position. The data fields listed here are only the ones that are mandatory for creating a Job Requisition. true true Master Confidential N/A
Job Family Group 14f0c1f9-fcd4-eb11-ab86-5c879c3c5a54 Job Position true Job Family Groups are used to organise and group Job Families. They focus on the content of the Job Families, and they are not supposed to reproduce the company's organisational chart. true false Master Internal N/A
Workforce Plan 393cbce3-01d5-eb11-ab86-5c879c3c5a54 Job Position true The organisational plan for the period - This is HR Master Data and contains information regarding recruitment requirements to fulfill the business strategy with regard to resources. These resources maybe filled internally or externally depending on the skills and competencies required. - This holds the data behind the plan to meet the business need true true Transactional Confidential N/A
Benefit Eligibility 518bfd86-bae0-eb11-ab86-5c879c3c5a54 Job Position true Identifies if the Job Position is eligible for the specific benefit for example is the Job position eligible for Medical Aid benefit true true Transactional Internal Sensitive Personal Information
Compensation Eligibility 5759922d-f5e3-eb11-ab86-5c879c3c5a54 Job Position true Identifies if the Job Position is elegbile for the specific Compensation for example is the Job position eligible for Car Allowance true true Transactional Internal Sensitive Personal Information
Pay Group 7a8b5792-27ea-eb11-ab88-5c879c3c5a54 Job Position true Different Pay Groups are set up - depending on the salary and allowances applicable to the Job Position true false Master Confidential N/A
Job Profile 8e6d6ce9-fcd4-eb11-ab86-5c879c3c5a54 Job Position true The Job Profile captures the generic features and characteristics of a job, such as management level, classifications, pay rate type, compensation, skills, and other qualifications. One same Job Profile can be assigned to multiple Positions. true false Master Internal Sensitive Personal Information
Employee Contract 9b78762b-29e6-eb11-ab86-5c879c3c5a54 Job Position true The Employee Contract contains specific information regarding the actual employment contract between the employee and the employer. Note that 'Contigent Worker' will not have a link to an contract as this work is delivered via SOW and Purchase Order... true true Master Confidential Sensitive Personal Information
Job Family a1365bf3-fcd4-eb11-ab86-5c879c3c5a54 Job Position true Job Families are used to organise and group Job Profiles, broadly defining the line of work associated with the Job Profiles assigned to it. Job Families focus on the content of the Jobs, and they are not supposed to reproduce the company's organisational chart. true false Master Internal N/A
Job Classification a8523784-fed4-eb11-ab86-5c879c3c5a54 Job Position true This field is often used for job-related regulatory reporting and can be used to categorise job profiles (e.g. EEO-1, DOA, DOT, Safety Tier, Finance regulatory etc..). Examples may vary by function. Some examples below are: CEO Office - CEO HR - C Level (CHRO) - Director (HR Director) - Manager (HR Manager) - Analyst (HR Analyst) Finance - C Level (CFO) - Director (Finance Director) - Manager (Finance Manager) - Analyst (Finance Analyst) Marketing - C Level (CMO) - Director (Marketing Director) - Manager (Marketing Manager) - Analyst (Marketing Analyst) true false Reference Internal N/A
Job Position b71615dc-fcd4-eb11-ab86-5c879c3c5a54 Job Position true A Position is a seat to be filled by a Worker. Positions are the basis of the Staffing Model we have by default: Position Management. Positions are created within Supervisory Organisations. With the Staffing Model we have, there must be an open Position in a Supervisroy Org before we can staff it. Vacant positions appear in a Supervisory Organization as unfilled, and remain that way until they are either filled or closed. true true Master Internal Sensitive Personal Information
Collective Agreement f44fde41-93d5-eb11-ab86-5c879c3c5a54 Job Position true Collective Agreement records the information regarding agreements made with trade unions regarding pay and working hours for employees in particular businesses and locations. true true Master Internal N/A
Compensation Plan 085fcd90-97d5-eb11-ab86-5c879c3c5a54 Benefit and Compensation true The specific compensation plan amount true false Master Confidential N/A
Compensation Frequency 40e253c8-c0e0-eb11-ab86-5c879c3c5a54 Benefit and Compensation true The frequecy the Allowance Plan, Bonus Plan or Salary Plan is paid to the employee. Examples : Weekly, Monthly, Annually,etc true false Reference Internal N/A
Benefit 50aa4c80-97d5-eb11-ab86-5c879c3c5a54 Benefit and Compensation true The Benefit entity covers the benefit plans across the enterprise. A plan is then applied against a particular job and position and then assigned to an individual. true true Master Confidential N/A
Benefit Enrolment Type 86d53455-7ce5-eb11-ab86-5c879c3c5a54 Benefit and Compensation true The defined Enrolment plan for the Benefit Package. Benefits need to be enrolled on either once or at recurring intervals true false Reference Internal N/A
Compensation cabc6478-97d5-eb11-ab86-5c879c3c5a54 Benefit and Compensation true Compensation covers the compensation packages across the enterprise. A package is then applied against a particular job and position and then assigned to an individual true true Master Confidential N/A
Talent Pool 17da0a0c-9cd5-eb11-ab86-5c879c3c5a54 Talent and Performance true The Talent Pool holds information of talented individuals that may be suitable for future Maersk roles. These can be candidates who have applied previously or existing employees who may be ready for a career development move. The pool is used to search each time a new role becomes available. true true Transactional Confidential Sensitive Personal Information
Succession Plan 6fa6981b-9cd5-eb11-ab86-5c879c3c5a54 Talent and Performance true Succession plan identifies employees who can replace existing employees when those existing employees leave, retire or move from the current role. true true Transactional Confidential Sensitive Personal Information
Performance Review 99194115-9cd5-eb11-ab86-5c879c3c5a54 Talent and Performance true The Performance Entity contains specific information regarding an employees performance, development, objectives and role expectations including competencies and skills. It forms the basis for permance management and employee development and is carried out in cycles true true Transactional Confidential Sensitive Personal Information
Absence 308a1fe0-f9d4-eb11-ab86-5c879c3c5a54 Attendance true Absence refer as the nonattendance of an employee or contingent worker to work for various reasons. true true Transactional Confidential Sensitive Personal Information
Absence Balance 98565361-b6e0-eb11-ab86-5c879c3c5a54 Attendance true Every employee or contingent worker has a limit absence quota on a particular leave types, for e.g. annual leave, casual leave, sick leave, etc. true false Transactional Confidential Sensitive Personal Information
Honorific 1f4b0381-b4fc-e911-80eb-9cd21e38f3a4 Employee true An honorific is a word or expression with connotations conveying esteem or respect when used in addressing or referring to a person, e.g. Mr., Miss and Mrs. Non-english honorifics also exist like Sensei and San in Japanese which comes after the surname of a person or Monsieur or Madame in French. true false Reference Internal N/A
Name Format 274b0381-b4fc-e911-80eb-9cd21e38f3a4 Employee true This entity dictates each possible combination of name-elements (and their order from left to right) to be concatenated to construct a full name from its various possible components (attributes of the Person entity). Each instance will be specific to a particular language, since the order in which a full name is composed is largely cultural and linked to a spoken language (such as putting "San" as a Japanese honorific, but suffixed after the Family Name). Examples of possible instances might be: FamilyName ", " FirstName FirstName FamilyName FamilyName ", " NickName Honorific NamePrefix FirstName FamilyName NameSuffix true false Reference Internal N/A
Name Suffix 374b0381-b4fc-e911-80eb-9cd21e38f3a4 Employee true A suffix is a word attached to the end of a name e.g. John Doe "Jr.". true false Master Internal N/A
Employee 744b0381-b4fc-e911-80eb-9cd21e38f3a4 Employee true Represents a person employed directly by the company or a contingent worker. Note on contingent worker: Contigent workers differ from employees in three important ways. 1. Contingent workers are not on the company payroll. 2. Contingent workers are hired on-demand for a defined period of time. 3. Contingent workers aren't eligible for benefits. Types of Contingent Workers: 1. Temporary contingent workers: Though these contingent workers are employed by a staffing agency, they typically work onsite at their temporary work assignments. 2. Consultants: Experts in their fields, consultants professionally advise businesses within their area of expertise. 3. Independent contractors: This category includes freelancers and consultants who are not represented or employed by any type of staffing agency or consulting firm. true true Master Confidential Sensitive Personal Information
Marital Status cb4a0381-b4fc-e911-80eb-9cd21e38f3a4 Employee true Marital status is the legally defined marital state. There are several types of marital status: single, married, widowed, divorced, separated and, in certain cases, registered partnership. true false Reference Confidential Sensitive Personal Information
Name Format Purpose d64a0381-b4fc-e911-80eb-9cd21e38f3a4 Employee true The purpose for which a particular name-format is intended. For example, there might be a purpose called "Global Reporting" which can be associated with Name Formats which following the pattern "Family Name, First Name" so that names would be constructed such as "Flintstone, Fred" and "Simpson, Homer". Other purposes might be "Addressee formal" or "Addressee colloquial" (which would be the format to be used following the word "Dear..." at the start of a letter, giving for example "Dear Mr Flintstone" or "Dear Fred") ...or "Address Label Name" (which would construct the name from its elements such that it would be suitable for printing onto an address label). ...or "Local Reporting" might involve more complex rules which might invoke the "Second Last Name" if the language is Spanish or the "Nickname" if the language is one of a set of Oriental languages true false Reference Internal N/A
Gender da4a0381-b4fc-e911-80eb-9cd21e38f3a4 Employee true The gender the person is used to describe the characteristics of women and men that are socially constructed true false Reference Confidential Personal Identifiable Information
Name Prefix de4a0381-b4fc-e911-80eb-9cd21e38f3a4 Employee true Separate component of a employee's full name which comes in front of the "family name". Although these components still form part of the employee's officially-recognised Family Name, by separating them it allows better text-searching and indexing of Family Names. Typical examples are: "van der" or "van den" (in Netherlands/Belgium) "de" or "de la" (in France) "della" or "di" (in Italy) "von" (in Germany) "Den" or "op de" or "ten" or "Van 't" (in Denmark) true false Master Internal N/A
Spoken Language ea4a0381-b4fc-e911-80eb-9cd21e38f3a4 Employee true Includes purposes and types. E.g. 'native', 'fluent', 'limited' etc. true false Reference Internal N/A
Citizenship fa4a0381-b4fc-e911-80eb-9cd21e38f3a4 Employee true Identifies the citizinship of a person. Most interesting for HR related data on employees. true false Master Confidential Personal Identifiable Information
Maintenance Cost Recovery Damage Type 16d79c09-2af5-eb11-ab8a-5c879c3c5a54 Maintenance Cost Recovery true Description of the type of Damage (Maintenance) that occurred - examples Heavy Cleaning Required Light Cleaning Required Debris/Residue Missing Items true false Reference Internal N/A
Maintenance Cost Recovery Cost Damage Location 4f4fe3a1-2af5-eb11-ab8a-5c879c3c5a54 Maintenance Cost Recovery true identifies where the Damage (Maintenance) occurred - examples Bottom Rail Corner Post Door Flooring true false Master Internal N/A
Maintenance Cost Recovery Line 8a42dacf-23f5-eb11-ab89-5c879c3c5a54 Maintenance Cost Recovery true Individual Line items (Charges) identified to be recovered for the Case. true false Transactional Internal N/A
Maintenance Cost Recovery Damage Size a19f7e5a-e6f8-eb11-ab8a-5c879c3c5a54 Maintenance Cost Recovery true Description of the size of Damage (Maintenance) that occurred - examples Small size repair: 25cm * 25cm Large size repair: 100cm * 100cm Whole container: All true false Master Internal N/A
Maintenance Cost Recovery Other Charge b0b925dc-e4f8-eb11-ab8a-5c879c3c5a54 Maintenance Cost Recovery true holds the Description of the Other Charges raised manually true false Transactional Internal N/A
Maintenance Cost Recovery bfd2ddf7-6af4-eb11-ab89-5c879c3c5a54 Maintenance Cost Recovery true Maintenance Cost Recovery cases are created when additional costs are incurred against containers (by example repairs or cleaning). The cases are then reviewed to identify if a third party (Customer or Service Provider) is liable for the additional incurred costs, and if so costs are sent to Finance to invoice the relevant party. true true Transactional Internal N/A
Maintenance Cost Recovery Average Cost ca172231-2ef5-eb11-ab8a-5c879c3c5a54 Maintenance Cost Recovery true A list of Average costs in USD for the different activities that have incurred costs. true false Master Internal N/A
Part Number 165a53c2-7cd2-eb11-ab85-5c879c3c5a54 Maintenance Type true The catalogue of Parts that can be used for each maintenance type true true Reference Internal N/A
Maintenance Preparation Time 55f5a3b9-7ed2-eb11-ab85-5c879c3c5a54 Maintenance Type true Maintenance preparation time is a catalogue of agreed preparation times for the different Maintenance types. They are agreed between the Carrier and the Repair shop. true false Master Internal N/A
Maintenance Type Requires Part Quantity 69be2c9e-a2d2-eb11-ab85-5c879c3c5a54 Maintenance Type true Some Maintenance and Repair Types with high value parts (i.e. compressors and controllers) have a list of acceptable parts for that code. This to insure that only the correct parts are used for these repairs. May also include a Maximum Parts that can be used for the Maintenance and Repair Type true false Master Internal N/A
Maintenance Type a119a2ba-73d2-eb11-ab85-5c879c3c5a54 Maintenance Type true Maintenance Type is the catalogue of Maintenance or repair codes that are used on the Maintenance and Repair orders. They are a set of agreed values between the carrier and the repair shops. some examples 1317~~~~~~~ 00~~~ MAER~~~ Roof Ceiling Patching 875x1250 1318~~~~~~~ 00~~~ MAER~~~ Roof Ceiling Patching 1025x1550 1319~~~~~~~ 00~~~ MAER~~~ Roof Ceiling Patching 1225x1550 1321~~~~~~~ 00~~~ MAER~~~ Roof Ceiling First intermediate panel 1322~~~~~~~ 00~~~ MAER~~~ Roof Ceiling adjacent panel 1323~~~~~~~ 00~~~ MAER~~~ Roof Ceiling Panel in front or rear 1421~~~~~~~ 00~~~ MAER~~~ Replace Entire Roof 20ft (non sandwich) 1422~~~~~~~ 00~~~ MAER~~~ Replace Entire Roof 40ft (non sandwich) 1612~~~~~~~ 00~~~ MAER~~~ Roof panel spec Sec. non sandwich-1200 true true Reference Internal N/A
Part Group a7defbc9-7cd2-eb11-ab85-5c879c3c5a54 Maintenance Type true Part Group codes denotes to which reefer unit type the part belong. Soem examples:RDST : Reefer Daikin Standard RCCA : Reefer Carrier Controlled Atmosphere RCCH : Reefer Carrier Controlled atmosphere with Humidity control. RCCO : Reefer Carrier Common meaning the part is common for several units true false Reference Internal N/A
Maintenance Type Mode a97f49cd-73d2-eb11-ab85-5c879c3c5a54 Maintenance Type true Maintenance Mode type is ???? Examples Equipment TypeStandardsOff Hirenon -reefer containers01,03-1082-89reefer box00,0281-82reefer unit41-4581-82genset31-3332chassis1112powerpacks71blast freezer ctrs48delivery of spares to vsl47 true false Reference Internal N/A
Equipment Damage 0579b794-3bd0-eb11-ab85-5c879c3c5a54 Maintenance Order true Equipment damage is a set of codes that indicate the kind of damage. example values TU UNEVEN TREAD IR IMPROPER REPAIR OD OUT-OF-DATE RC CONVERSION REQUIRED BU BULGED BR BROKEN/SPLIT RA REMOVE FOR ACCESS SR SHRUNK FD FORKLIFT DAMAGE GO GRP SURFACE CRACK RF RUN FLAT LF LOW FLUID LEVEL true false Transactional Internal N/A
Maintenance Order Man Hours 39fc2bde-cc5b-ef11-8190-db4390e09088 Maintenance Order true The man hours spent on the maintenance order true false Transactional Internal N/A
Maintenance Order 4ab02d30-3ad0-eb11-ab85-5c879c3c5a54 Maintenance Order true The Maintenance Order is the instruction for a Maintenance shop or Vessel team to do repairs or Maintenance on equipment in the fleet. true true Transactional Internal N/A
Maintenance Order Status 598090fe-3fd0-eb11-ab85-5c879c3c5a54 Maintenance Order true The Status of the Maintenance and Repair Order. Example Values Draft Rejected Pending Approver Approval Suspend to EMR Specialist Completed Paid true false Reference Internal N/A
Maintenance Order Line 66731391-43d0-eb11-ab85-5c879c3c5a54 Maintenance Order true Maintenance Order Line - itemises the maintenance and repairs that need to be carried out in the order. true false Transactional Internal N/A
Maintenance Repair Location 8516026b-3bd0-eb11-ab85-5c879c3c5a54 Maintenance Order true The Maintenance Repair location specifies the area on the Equipment where the repairs must be carried out. It identifies the damages within an area as large as a complete face of the container or as small as a nominal 1200 mm x 1200 mm (4 ft x 4 ft) square, or even less for the main components located on its edges (rails, corner posts). Some example values are IL INTERIOR PANELS, LEFT IR INTERIOR PANELS, RIGHT IX ALL INTERIOR LB SIDE PANELS, BOTTOM HALF LG SIDE BOTTOM RAIL LH SIDE TOP RAIL LT SIDE PANELS, TOP HALF LX SIDE PANELS, BOTH HALVES true false Transactional Internal N/A
Maintenance Order Remark 96a2b332-42d0-eb11-ab85-5c879c3c5a54 Maintenance Order true Maintenance Order remarks allow remarks to be exchanges within the Maintenance Order. true false Transactional Internal N/A
Maintenance Repair Mode f0474781-c75b-ef11-8190-db4390e09088 Maintenance Order true The repair mode identifies the high level type of repairs that will be done true false Reference Internal N/A
Maintenance Order Part f7915bc9-42d0-eb11-ab85-5c879c3c5a54 Maintenance Order true Maintenance Order part identifies the actual parts ( and their serial numbers) used in the repair.. true true Transactional Internal N/A
Sales Target a04e0381-b4fc-e911-80eb-9cd21e38f3a4 Sales Target true A Sales Target is a fixed amount of sales that the organization wants to achieve foir a set of products. true true Transactional Confidential Competitive Strategic Information
Sales Target Detail b34e0381-b4fc-e911-80eb-9cd21e38f3a4 Sales Target true The details of the Target usually either volume based or Revenue based or Yield based. true false Transactional Confidential Competitive Strategic Information
Market Condition 53196cc6-352f-ef11-8184-c403a888648b Marketing true Identifies the market Condition Example values are Monopoly - There is only one vendor covering a given market. There is no business alternative to the given vendor Seller`s Market - There is more than one vendor in the market, but the leverage power is still on supplier side (example: duopolies, oligopolies, highly utilized market, strong limitations for cargo mobility) Balanced Markets - There is more than one vendor in the market, and there is not a clear definition of leverage power, the market is equalized. Buyer`s Market - There is more than one vendor in the market, and the leverage power is on buyer`s side (example: competitive markets, over capacity, new vendors entrance) true false Reference Internal N/A
Procurement Method 7067732d-502a-ef11-8183-c403a888648b Marketing true The method for that procurement project, determining whether it will be Auction or RFX, direct procurement, etc true false Reference Internal N/A
Opportunity Type 2011a6db-8aab-ed11-8c0b-5c879c3c5a54 Sales Opportunity true Type of Opportunity Example of Opportunity type 'Sales' The Sales opportunity can have the following child types : Acquisition: Transactions done with a customer that has not done business with Maersk previously or an existing Maersk customer that has not done Ocean and/or L&S business in the previous calendar year. Renewal: A straight forward buy it again, same condition and product i.e Double Down opportunities from 2021 Additional Business: If you are selling a new product, new lanes or product family, then its additional business. One-off : Non reoccurring business true false Reference Internal N/A
Opportunity 924e0381-b4fc-e911-80eb-9cd21e38f3a4 Sales Opportunity true Opportunity may be a sale or pending deal. Opportunites are classfied in to three categories and they are Acquisition, Renewal, and Transactional. Transactional Business having a short validity, often for one-off shipments, typically price-driven. Renewal Existing business from an existing customer. Acquisition Brand new customer or new trade route/direction for an existing customer. The Opportunity StageName field controls several other fields on an opportunity. If the StageName is updated, then the ForecastCategoryName, IsClosed, IsWon, and Probability are automatically updated based on the stage-category mapping.The Seven distinct Pick List values values are Lead, Qualify, Value Proposition, Quote, Negotiate, Closed Lost, Closed Won. The first five stages are open status and the last two are closed status. true true Transactional Confidential Competitive Strategic Information
Opportunity Line Item a94e0381-b4fc-e911-80eb-9cd21e38f3a4 Sales Opportunity true Represents an opportunity line item, which is a member of the list of Product2( Route and Direction codes ) products associated with an Opportunity. true false Transactional Confidential Competitive Strategic Information
Opportunity Line Item Schedule bb4e0381-b4fc-e911-80eb-9cd21e38f3a4 Sales Opportunity true Represents information about the quantity, revenue distribution, and delivery dates for a particular OpportunityLineItem. true true Transactional Internal Competitive Strategic Information
Opportunity Close Reason bf4e0381-b4fc-e911-80eb-9cd21e38f3a4 Sales Opportunity true Explanation for the closure of a Sales Opportunity. The values are: Lost - Disagreement on contract terms and conditions Lost - Uncompetitive price Lost - Solution/Product features not meeting customer needs Lost - Credit requirements Lost - Implementation failure Lost - Lack of capacity/space/resources Lost - Delay in quoting Lost - Others Rejected - Not Profitable Rejected - Not aligned with Area Business plan Rejected - Asset/resource/tech investment limitation Rejected - Lack of integrated solution capabilities Rejected - Duplicate System - End Date Passed Won - Price (market relevant pricing position) Won - Service (reliable, quality, quicker) Won - Solution/Product (features, components meeting customer needs) Won - Relationship (loyalty, partnership, trust, supporter) Won - Others true false Reference Internal N/A
Opportunity Team ec77e21d-6819-ed11-abc1-5c879c3c5a54 Sales Opportunity true The Sales team associated to the Sales Opportunity. Usually made up of more than 1 associate. true false Master Internal N/A
Shipment 784f0381-b4fc-e911-80eb-9cd21e38f3a4 Shipment true A Shipment is an order given to the carrier (i.e. Maersk Line or to its related brands) to transport cargo and / or equipment from one place to another. E.g. a supermarket chain orders 3 containers of bananas to be shipped from São Paulo, Brazil, to Rotterdam, Netherlands. A Shipment includes one or several cargo items (Transport Items). All cargo items that are part of one shipment need to share the same values for the contractual customer, the place of receipt (POR), the place of delivery (POD) and the planned departure date. A Shipment may be modified or cancelled, either by the customer or by the carrier (Maersk Line) at any time before departure. It may also be split into two or more parts, in case not all cargo items can be transported together, i.e. in case any of the defining attributes (contractual customer, POR, POD, departure date) change for a subset of the cargo items. Cargo items may be added to or removed from a shipment later on. Booking and Shipping Instruction It should be noted that Shipments are typically created upon receival of Booking, and updated upon receival of Shipping Instruction. Status indications The timestamps associated with the status of the business object is considered a physical implementation. Examples of these include "BookedTimestamp", "CancelledTimestamp" and "ConfirmedTimestamp". true true Transactional Internal Competitive Strategic Information
Shipment Line a54f0381-b4fc-e911-80eb-9cd21e38f3a4 Shipment true NOTE: the Shipment Line is also known, in legacy terms (GCSS), as "Cargo Line" or "Cargo". The Shipment Line will specify what customer products, and their corresponding quantities, measurements, descriptions, packages, etc. will be part of a Shipment. They can be seen as a grouping or unit of cargo, of a particular Commodity, that forms part of a Shipment, and which can be used/ mentioned in a Transport Document, to describe the cargo being shipped. Booking and Shipping Instruction It should be noted that Shipment Lines are typically created upon receival of Booking, and updated upon receival of Shipping Instruction. This also means that the total number of Shipment Lines might change upon receival of Shipping Instruction. Examples: Booking originally has 2 Shipment Lines, Shipping Instruction updates it to 4 Shipment Lines. When this happens, booked quantities (weight, volume, etc.) on Shipment Lines 3 and 4 will all be zero/ null. Booking originally has 3 Shipment Lines, Shipping Instruction updates it to 2 Shipment Lines. When this happens, shipped quantities (weight, volume, etc.) on Shipment Line 3 will all be zero/ null. Reefer and Dangerous Cargo In order to know if a cargo is dangerous or reefer type, that information should be obtained via relationship with Cargo Type class. true false Transactional Internal Competitive Strategic Information
Promise bd191e05-0b4e-ed11-b80f-44e517a1f1d9 Shipment true WIP true false Transactional Confidential N/A
Carrier Booking Rejection Reason 093f1869-7c85-eb11-a3c6-a0510b9e9705 Carrier Booking true Reasons for a Carrier Booking Rejection can be picked from a pre-defined list of rejection reaons. The rejection codes and corresponding text should be aligned with (or copied from) the UN/ EDIFACT standard. true false Reference Internal N/A
Carrier Booking Request 4b67a799-7e4e-ea11-acfe-e470b8c7d5cf Carrier Booking true See main class "Carrier Booking" documentation first for all details and logic which are common/ inherited from main class. The Carrier Booking Request is a booking for transport carriage with a Transportation Provider (internal or external provider). It inherits from the Carrier Booking because the request and the response shares commonalities that can be assigned to a superclass. Relationship with Carrier Booking main class See main class "Carrier Booking" documentation for details. ID Logic See main class "Carrier Booking" documentation for details. Relationship with Carrier class There are business scenarios where we actually send multiple CBK requests (for the same CBK) to different carriers, at same time. Then we either pick the one carrier that accepted the CBK (if only one accepted), or the Carrier that provided the best CBK response. Hence why Carrier must be associated with CBK Request, and not with CBK main class. See CBK main class documentation for more details. true true Transactional Internal Competitive Strategic Information
Carrier Booking Response 598ba19f-7e4e-ea11-acfe-e470b8c7d5cf Carrier Booking true See main class "Carrier Booking" documentation first for all details and logic which are common/ inherited from main class. The Carrier Booking Response is the carrier response to a Carrier Booking Request. The response(s) is related to the request so that it can be tracked what the request was and what the response(s) were that came back. It inherits from the Carrier Booking because the request and the response shares commonalities that can be assigned to a superclass. Relationship with Carrier Booking Request class See main class "Carrier Booking" documentation for details. ID Logic See main class "Carrier Booking" documentation for details. Carrier Booking Rejections Carrier Booking Responses can also be rejections by Transport Provider. When this happens, Transport Provider is expected to provide a reason for rejection (see class "Pre-Defined Carrier Booking Rejection Reason" for more details). Responses with Changes The Carrier Booking Response provided by Carrier might have changes, compared to its corresponding Request, namely changes to requested equipment (see documentation on main class for more details). true true Transactional Internal Competitive Strategic Information
Carrier Booking 9e1270e1-7836-ea11-ad93-40b034e2c22b Carrier Booking true Also known as "Delivery Order". See documentation on "Carrier Booking Type" for more details. A Carrier Booking is an order for transport and/or carriage sent to a Transport Provider. It should be noted that Transport Provider here means either a Carrier or a Freight Forwarder. It should also be noted that any transport mode can be ordered (i.e. Ocean, Air, Rail, Road, Inland Water, and their multiple multimodal combinations), and therefore the concept of Carrier Booking is applicable for any type or mode of order of transport from any Transport Provider (i.e. sea carriers, air carriers, truck companies, etc.). Requests and Responses The Carrier Booking is sent to the Transport Provider as a request. The Transport Provider will send response(s) to the corresponding request. Examples: A Carrier Booking Request is sent to CMA CGM, for ocean transport, asking for 10 40ft containers, going from Shanghai to Rotterdam. CMA CGM sends a response back that they can supply 8 40ft container and 4 20ft containers, for the requested dates and route. A Carrier Booking Request is sent to a local trucking company, requesting to pick-up a container from a port to a warehouse, on a specific date. The trucking company replies they accept request and will perform it on requested date. Requests and Responses as SubClasses The Requests and Responses are modelled in MIM as subclasses of Carrier Booking. This is for 3 reasons: Because both the Requests and Responses should carry the same attributes and relationships as the main class Carrier Booking. Because Requests and Responses can hold values which differ from their parent Carrier Booking. Because of business scenario where Multiple Carrier Booking Requests are sent to multiple different Transport Providers at the same time, for the purpose of seeing who provides the best option and/or who replies the soonest. Example: Using same example as above (when requesting for 10 40ft containers, but getting response with 8 40ft + 4 20ft), we can see that Request and Response will both use relationship and attributes of Transport Asset Requirement, but each will have their own different values of Transport Asset Requirement. Requests and Responses Relationships It should be noted that 1 instance of a Carrier Booking can spawn multiple Carrier Booking Requests (hence why main class "Carrier Booking" also has a 0..* relationship with "Carrier Booking Request"). This is because of 2 business scenarios: Changes to the booking are necessary after Transport Provider has already accepted booking. Multiple Carrier Booking Requests are sent to multiple different Transport Providers at the same time, for the purpose of seeing who provides the best option and/or who replies the soonest. It should also be noted that 1 instance of a Carrier Booking Request can spawn multiple Carrier Booking Responses (hence why class "Carrier Booking Request" has a 0..* relationship with "Carrier Booking Response"). This is because of 1 business scenario: Transport Provider has the need to send us an updated Response, informing of changes made to the booking. Carrier Booking Rejections Carrier Booking Requests can also be rejected by Transport Provider. When this happens, Transport Provider is expected to provide a reason for rejection (see subclass "Carrier Booking Response" for more details). It should also be noted that when this happens, the business lifecycle of that instance of the "Carrier Booking" main class ends, and a new instance of the "Carrier Booking" main class must be created. Carrier Booking Number and Identification Logic Carrier Booking Number: a pure internal identifier of the Carrier Booking (main class). Carrier Booking Request Number: a number which is sent on the Carrier Booking Request, for the purpose of identifying it and referencing it within the Transport Provider. Because Carrier Booking is 0..* with Carrier Booking Request (see above), the Carrier Booking Request Number cannot be the same as the Carrier Booking Number. For this reason also, the Carrier Booking Request Number will be present at the Carrier Booking Request subclass only. Carriers Own Booking Number: the actual booking number, provided by the Transport Provider, via Carrier Booking Response, upon acceptance of the booking. ATTENTION: there is a specific business scenario (Pre-Assigned Booking Numbers), whereby Transport Provider has give upfront a range of booking numbers to be used for Carrier Booking Requests. When this is the case, then the "Carriers Own Booking Number" must also be provided in the Carrier Booking Request. Hence why attribute "Carriers Own Booking Number" is located in Carrier Booking main class, and not on Carrier Booking Response subclass. Required vs Planned vs Actual The Carrier Booking can have its own values for the following: Shipping Contract Shipment Service Type Container Service Type Cargo Service Type Incoterm Freight Term Haulage Term Vessel Freight Term Transport Asset Requirement These can all be different from the ones found in the Service Plan and Transport Plan associated with the Carrier Booking. This is because of 2 reasons: Service Types on Service Plan and Transport Plan are requested/ planned service types, whereas Carrier Booking service types are actual. Service Types on Service Plan cover the service of Maersk O&L, while Carrier Booking covers service of Transport Provider. Cargo, Commodity and Measurements The Carrier Booking doesn't have lines, but however, a total value of weight, volume and/or packages can still be present and will, according to each business scenario, even be mandatory. Weight and Volume can also be defined individually for each container and/or vehicle requested, in which case they will be in the related instance of class "Transport Asset Requirement". In this scenario, the total weight and volume at Carrier Booking main class will be derived. Typically, weights and volumes for each container will only be provided when using FCL mode. Typically total package quantity will only be provided when using LCL mode. A Commodity Classification and Cargo Type should also be provided, but only 1 Commodity Classification and only 1 Cargo Type for the whole booking. They will therefore be of a more generic nature then that which one would find, for instance, in a Customer Order Line or a Shipper Booking Line. Actual Containers and Rolled Containers Actual container numbers will be recorded in relationship with class "Container". Information on whether a container was rolled or not shall be obtained via Events linked to either the Container, the Carrier Booking or the Transport Order. true true Transactional Internal Competitive Strategic Information
Carrier Booking Status eadab3d5-1138-ea11-acf7-e470b8c7d5cf Carrier Booking true Refers to the different statuses a Carrier Booking, and its Requests and Responses can have within its lifecycle. ATTENTION: In order to reflect business logic correctly, it should be noted that it's possible that some Carrier Booking Statuses will only be applicable for Carrier Booking Requests, and some only for Carrier Booking Responses. For each Carrier Booking Status, it must be defined if it can be used for Request, Response or both. Status examples: Draft - Draft status and information is not sent to other party yet. user can modify most of the data field. Carrier Booked - CB has been checked and sent to carrier. No carrier response is received. Carrier Accepted - CB has been received or accepted by carrier. Depend on carrier integration method, carrier response details including SI & VGM cutoff will be updated. Carrier Rejected - CB has been rejected by carrier. End of state, user cannot take any further action. Partial Accepted - CB is partially accepted by carrier. Either by response from carrier as Partial confirmed or CB checks the request vs response and updates status as Partial Accepted. Doc Received - CB confirmation PDF document is received by Docman 2.0 or via email for manual response. Doc Mismatch - CB has been sent to carrier but there is mismatched content between CB request and carrier document response (booking confirmation). It indicates that user need to either accept the changes in CB (take carrier response as confirmed one) or Resend the CB to carrier with further revision clarification. Doc Confirmed - CB confirmation PDF is received by Docman 2.0 and validated against the requested details. Doc Released - CB confirmation is released to related party. Finished - CB process is complete and no more changes are expected. Normally after ATD. It is not a end user manual change status. Cancelled - CB request placed intially is requested to cancel and carrier have confirmed as the CB is cancelled. Or end user decide to cancel the carrier booking. true false Reference Internal N/A
Service Plan 48eb726d-4f85-ea11-a3ad-a0510b9e9705 Service Plan true The Service Plan (SPL) defines the scope of the service that Maersk is providing for a specific end-to-end shipment journey of a specific customer, such as: where/when Maersk service starts/ends; where/when are specific services to occur; what products and product add-ons are included; what service features are included (MCC, Milk Run, etc.); what moments of the journey are included (i.e. consolidation, deconsolidation, distribution centre, last mile, customs brokerage, etc.). 1 Service Plan will be for 1 Customer, and 1 Customer only. 1 Service Plan can only be for 1 specific end-to-end shipment journey. The SPL will typically be created/ generated either from: 1 Booking (once its received); a document/ request equivalent to a Booking (to be defined/ modelled in the future), in the case of some specific products, like Warehouse Shipment in WND; manually, by Maersk customer service. 1 Service Plan can only relate to 1 Booking. This is because we are saying the Booking is the moment when customer informs us what is exactly the scope of services he will be contracting with Maersk O&L for a given E2E shipment journey. Service Plan Legs and Locations Logic The extensive list and illustration of all possible business scenarios for generation of Service Plan Legs and Service Plan Locations can be found here: https://teamsite.maerskgroup.com/:b:/r/teams/maerskinformationmodel-communityofpractice/Shared%20Documents/01%20MIM%20Subject%20Areas/31%20-%20Service%20Plan/Service%20Plan.pdf?csf=1&web=1&e=4BFy3F Shipment Service Type (SST) A SPL will have a SST pair of values (as per SST definition) that will define respectively the Origin and Destination Service. These will in turn define respectively where (in the end-to-end shipment journey) does Maersk service starts and ends. This means the SST pair of values will literally and effectively define Service Plan Locations and Service Plan Legs. More concretely: if SST = "PORT/ PORT", then we'll have (at least) SPL Locations Port of Loading (POL) and Port of Discharge (POD), with (at least) 1 Service Plan Leg between them. Maersk Service will start at POL and end at POD. if SST = "DOOR/ PORT", then we'll have (at least) SPL Locations Place of Receipt (POR), Port of Loading (POL) and Port of Discharge (POD), with (at least) 2 Service Plan Legs between them. Maersk Service will start at POR and end at POD. if SST = "PORT/ DOOR", then we'll have (at least) SPL Locations Port of Loading (POL), Port of Discharge (POD) and Final Destination (FD), with (at least) 2 Service Plan Legs between them. Maersk Service will start at POL and end at FD. if SST = "DOOR/ DOOR", then we'll have (at least) SPL Locations Place of Receipt (POR), Port of Loading (POL), Port of Discharge (POD) and Final Destination (FD), with (at least) 3 Service Plan Legs between them. Maersk Service will start at POR and end at FD. Above, of course, implies that SST cannot be different for SPL legs of same SPL. Container Service Type (CST) A SPL will have a CST pair of values (as per CST definition) that will define respectively the Load and Discharge Service. These will in turn define respectively if Maersk service will include consolidation at origin and/or deconsolidation at destination. This means the CST pair of values will literally and effectively define additional Service Plan Locations and Service Plan Legs. More concretely: if CST = "CY/ CY", then no additional SPL locations or legs. if CST = "CFS/ CY", then 1 additional SPL location: Origin CFS, and instead of 1 leg between POR and POL, it will be 2 legs: between POR and Origin CFS, and between Origin CFS and POL. if CST = "CY/ CFS", then 1 additional SPL location: Destination CFS, and instead of 1 leg between POD and FD, it will be 2 legs: between POD and Destination CFS, and between Destination CFS and FD. if CST = "CFS/ CFS", then 2 additional SPL location: Origin CFS and Destination CFS, with both the same implications of CY/CFS and CFS/CY. Above, of course, implies that CST cannot be different for SPL legs of same SPL. MCC, DC and Milk Runs Additionaly to SST and CST, these also impact locations and legs: MCC Indicator: MCC stands for Multi Country Consolidation, and it's a business scenario where there is an additional SPL Location between POL and POD, called MCC Hub (HUB), where cargo from multiple POL to one POD is consolidated. This additional location will split the SPL leg between POL and POD in 2 legs (POL to HUB, and HUB to POD). ATTENTION: this Service Plan Scenario should not be confused with having multiple Transport Plan Legs for the same Service Plan Leg. DC Indicator: DC stands for Distribution Centre (a warehouse-like facility at Destination, where cargo is shipped to multiple Final Destinations). This additional location will either: (a) split the SPL leg between POD and FD in 2 legs (POD to DC, and DC to FD), if Discharge CST = "CY", or (b) split the SPL leg between CFS and FD in 2 legs (CFS to DC, and DC to FD), if Discharge CST = "CFS". ATTENTION: if DC = FD (i.e. they are the same location), then DC Indicator = "no", because the DC is the place where Maersk service ends, i.e. no additional SPL Leg is required. Origin Milk Run Indicator: if a customer has multiple shipper locations at origin, all shipping small quantities, he might choose to have 1 single truck picking cargo from all those shipper locations, effectively breaking the Origin Leg in to many multiple legs between each shipper location and, eventually, arriving at either the CFS or CY. ATTENTION: this business scenario must not be confused with a multiple customer milk run, where a truck picks from multiple shipper locations too, but each shipper is for a different customer. In such scenario, because its multiple customers, each leg will belong to a different Service Plan, and therefore the milk run is constructed via a Transport Plan. Destination Milk Run Indicator: same as Origin Milk Run Indicator, but for multiple Final Destinations. The Milk Run can start at either a CY, a CFS or a DC. Other Locations We might also require to store other additional key locations such as: Inspection Location, Customs Location, etc. These additional SPL locations may or not imply additional SPL legs. NOTE 1 (Factory Load): There is no Factory Load Indicator (MODS legacy field), because it's not needed: when Origin SST = "DOOR", and Load CST = "CY", that already means factory load. true true Transactional Internal Competitive Strategic Information
Service Plan Leg 648cfc77-4f85-ea11-a3ad-a0510b9e9705 Service Plan true See main class "Service Plan" for details on logic on generation of Service Plan Legs. The extensive list and illustration of all possible business scenarios for generation of Service Plan Legs can be found here: https://teamsite.maerskgroup.com/:b:/r/teams/maerskinformationmodel-communityofpractice/Shared%20Documents/01%20MIM%20Subject%20Areas/31%20-%20Service%20Plan/Service%20Plan.pdf?csf=1&web=1&e=4BFy3F The Service Plan (SPL) will specify where/when Maersk O&L service starts/ends, and what moments of the journey are included. This means the SPL will define Service Plan Legs, which will connect 2 SPL Locations. Not all Locations will necessarily have Legs (for instance, Place of Inspection), but all Legs must have 2 Locations. Legs will be 1 of 3 types: Origin Leg, Main Leg, Destination Leg. Relationship Between Service Plan (Legs) and Transport Plan Each Service Leg can be seen as an individual service request by a Customer, to move cargo from one Service Plan Location to another. The Transport Plan is the actual execution of that service, whereby Maersk O&L contracts a Transport Provider to execute 1 or more of the Service Legs. The Transport Plan (via Transport Order) can group Service Legs from same Service Plan, but also group Service Legs from different Service Plans (this is the case, for instance, of LCL business scenario). The Transport Legs will be the actual physical stages of the transport, performed by a vehicle (vessel, truck, aircraft, etc.), and therefore, wont necessarily match the Service Legs. true true Transactional Internal Competitive Strategic Information
Service Status 72aad415-b7f4-ed11-b82d-44e517a1f1d9 Service Plan true Describes the completeness and acceptance status of a particular Service Plan Location or Service Plan Leg, for instance indicating if planning is completed, or transport is ongoing, etc. true false Reference Internal N/A
Service Plan Update 8830b1a9-26fb-ee11-b887-44e517a1f1d9 Service Plan true When a Service Plan is updated/ changed, then in some business scenarios a reason for such update/change must be provided. true false Reference Internal N/A
Service Plan Relation 919a6101-bee4-11f0-64d1-e682385842d0 Service Plan true Allows a service plan to be related to other service plans for a specific reason. true false Transactional Internal N/A
Service Plan Relation Reason 919a6103-bee4-11f0-64d1-e682385842d0 Service Plan true Describes the type of relationship between two service plans such as: a service plan for a booking made at origin related to one (or more) made at destination. a service plan for a booking that got split in smaller bookings. a service plan for a booking for return of cargo, related to an original one. etc. true false Reference Internal N/A
Service Plan Location bd4afdf4-4f85-ea11-a3ad-a0510b9e9705 Service Plan true An instance of a Location where a non-transport service, within the Service Plan, will occur. These non-transport services can include amog others: customs clearance, inspections, consolidation/ deconsolidation, labelling and scanning, storage, fumigation, VGM measurement, change of vehicle/ equipment, etc. Expressing the Location details The location itself will be identified via an instance of "Location Association" (role-named "Location" on physical schemas), where the code, name, and function of the location (among other possible attributes) will be specified. Example: Code: PTLIS Name: Lisboa Function: Place of Inspection Locations will also have Name Alias and Alternative Codes. These will alow to express codes and names used by Customers and/or by other applications. Expressing Service Dates Events (role-named "Service Dates" on physical schemas) will allow customer to define (if it wants) requested service dates for the service. true true Transactional Internal Competitive Strategic Information
Cargo Stuffing Line 00db763c-0422-ea11-ad90-40b034e2c22b Cargo Stuffing true The breakdown of cargo that is stuffed inside a piece of equipment or a vehicle. Scanning: The scanning of the Cargo Packages are handled via Scan Events associated with the Cargo Packages. Note: The Cargo Stuffing Line is equivalent to the SSCS in MODS today (S/O Spec C/S Split) true false Transactional Internal Competitive Strategic Information
Cargo Stuffing Position 1bd3a12b-d685-ea11-adaa-40b034e2c22b Cargo Stuffing true Records the stuffing position of a cargo item inside a piece of equipment (e.g. an ISO or ULD container) or inside a vehicle (trailer, truck, airplane etc.). Used for either planning purpose or for recording the actual stuffing position. The position need not be for a specific commodity item or package, in case it jst represent a simple load sequence for an entire booking- or warehouse shipment line. true false Transactional Internal Competitive Strategic Information
Advance Shipping Notice Status 43cdc9c5-b135-ea11-ad93-40b034e2c22b Cargo Stuffing true Holds information about whether the ASN message has been created, is ready for sending or has already been sent. The ASN itself is not modelled as MIM does not model typical EDI messages. An ASN is referred to as various terms depending on the EDI standard used. In the GS1 EANCOM standard, it is called the DESDAV, despatch advice message, whereas in the ANSI X12 EDI standard it is called the EDI 856 Advance Ship Notice, also sometimes called a Ship Notice/Manifest. true false Reference Internal N/A
Cargo Stuffing Relation 52c71ecb-0c64-ea11-ada0-40b034e2c22b Cargo Stuffing true Cargo Stuffings need to be able to be related to eachother so that we can handle the scenario where an ISO container might be unstuffed in order to ship the cargo with Air instead. This happens in cases where the customer requests Air transport instead if the ocean shipping is getting delayed. In the above mentioned case the ULD Cargo Stuffing(s) will relate to the ocean container Cargo Stuffing. Note on how to use: The relationship between Cargo Stuffings are maintained by creating an entry in Cargo Stuffing Relation with a unique identifier, cargo stuffing number and purpose code. This enables that a Cargo Stuffing can take part in multiple relationships with other Cargo Stuffings for different purposes. If we group by relationship identifer we will get all the Cargo Stuffings that are related together and the purpose for why they are related. true false Transactional Internal Competitive Strategic Information
Cargo Stuffing 5df03928-a061-ea11-ada0-40b034e2c22b Cargo Stuffing true Generalization of the stuffing concept. The Cargo Stuffing class represents both the Equipment- and Vehicle Stuffings. This is done to be able to handle multiple different scenarios using the same data and structures: Cargo is stuffed in to a piece of equipment e.g. an ISO container for ocean freight or a ULD container for air cargo Cargo is stuffed directly in to a vehicle e.g. a Trailer, Van or Airplane. Status indications: The timestamps associated with the status of the business object is considered a physical implementation. Examples of these include "BookedTimestamp", "CancelledTimestamp" and "ConfirmedTimestamp". Equipment Stuffing: A Cargo Stuffing which is of type Equipment Stuffing represents a collection of cargo that is planned to be or has been loaded inside a piece of equipment which is ready to be transported. This Cargo Stuffing is meant to represent both a planned stuffing as well as the actual stuffing. Note on Container Load Plan: A Cargo Stuffing of type Equipment Stuffing, which is in the "Planned" state is also referred to as a "Container Load Plan" or CLP. A container load plan can be created in Maersk systems by the shipper who will prepare it based on Shipper Booking. The CLP can also be prepared by Maersk operators on behalf of the shipper, typically the Shippers will send Excel based CLPs that need to be input in to the system or imported somehow. Note on Container Load Result: A Cargo Stuffing of type Equipment Stuffing, which is in the "Stuffed" state is also referred to as a "Container Load Result" or CLR. A container load result can be created in Maersk systems by the shipper who will prepare it based on Shipper Booking. The CLR can also be prepared by Maersk operators on behalf of the shipper. The CLR is used to trigger for example advance shipping notice to some customers. Note on Air cargo: Cargo Stuffings of type Equipment Stuffing, are not prepared for Air corgo according to business process experts. However, we know for a fact that air cargo equipment has seal numbers for example. Note on MICP or MCC: MICP or MCC (Multi Country Consolidation) are client specific hub port consolidations where all the LCL shipments (coming in from different origins) for the specific client are consolidated into one container before being shipped to the final destination. true true Transactional Internal Competitive Strategic Information
Equipment Stuffing Size Type d234612f-115d-ea11-ad9f-40b034e2c22b Cargo Stuffing true For planned Cargo Stuffing (of type Equipment Stuffing) it is possible to indicate what size-type of equipment can be used as equipment for the cargo. It is envisioned that in some cases it is possible to use multiple different types of equipment to substitute the assigned type. E.g. if a 20FT general purpose container has been booked/requested, it is possible that 20FT reefer or even a 40FT general purpose or reefer could be used as substitution (Substitute=true). For finalized equipment stuffings the indicators are used as well for booked/requested/chargeable (to client) equipment size/type. true false Reference Internal N/A
Booking Relation 091efbba-e84d-ee11-a1ba-9a42c5ca5684 Booking true Allows a booking to be related to other booking for a specific reason. true false Transactional Internal N/A
Booking Line 800f5d55-67af-ec11-a3f8-a0510b9e9705 Booking true Represents a line of cargo on a Booking. The booking lines are typically organized at customer's discretion and can therefore have different organizing logics, i.e. 1 line per commodity type, 1 line per cargo type, etc. The booking line typically carries information on the nature of the cargo, and its quantities, weights and measurements. true false Transactional Internal N/A
Booking Equipment 9a60ed17-74ac-ed11-b820-44e517a1f1d9 Booking true Represents one piece of equipment on a Booking, as required by the customer. It therefore only carries information about what the customer has requested/ indicated, and no information about what Maersk will actually deliver. Typically used by the customer to indicate how much cargo, and its quantities, weights and measurements, is estimated or expected to be on an equipment, as well as its nature (i.e. cargo type, commodity type, etc.). Destination/ Import Bookings: For inland bookings at destination (i.e. "import bookings"), typically we already know a series of information, that we wouldn't normally know for bookings at origin, due to the fact that at destination typically containers are already stuffed and known, such as the container number, seal numbers, etc. Such information can be specified as "References". true false Transactional Internal N/A
Booking a95a8c67-59af-ec11-a3f8-a0510b9e9705 Booking true A Booking is a request from a customer for arranging and/ or reserving services to be executed at a particular time. Typically, in shipping and logistics, the Booking is a contract of carriage evidencing the agreement to transport goods, and other possible related services, such as storage, transit, clearance, etc. Those services can be provided by various suppliers, in a subcontracted form. A Booking also typically includes the agreement on transport conditions such as price, time and liability. Booking Status Time Stamps The timestamps associated with the status of a Booking is considered a physical implementation. Examples of these include "BookedTimestamp", "CancelledTimestamp" and "ConfirmedTimestamp". Service Plan A Booking will always have and contain a Service Plan. The Service Plan is the place where all Booking details around requested services shall be recorded. This includes, among others, required Commercial Products, Incoterms, Service Type (Port, Door, CFS, CY, etc.), Service Locations, Service Legs, Transport Provider, Transport Mode, Equipment/ Vehicle Requirements, etc. Service Locations are points between Service Legs (Place of Receipt, Port of Discharge, Final Destination, etc.), but also points of service (Place of Inspection, Place of Consolidation, etc.). true true Transactional Internal N/A
Booking Relation Reason ba049f16-d98d-ed11-b81b-44e517a1f1d9 Booking true Describes the type of relationship between two bookings such as: a booking made at origin related to one (or more) made at destination. a booking that got split in smaller bookings. a booking for return of cargo, related to an original one. etc. true false Reference Internal N/A
Transport Document Status 4d4c6124-68eb-ea11-a3b7-a0510b9e9705 Transport Document true Refers to the different statuses a Transport Document can have. Because different Transport Document Types can have different separate sets of Transport Document Status, it's not possible to have this class as predictable enumeration. Example: Transport Document Type "Convention de Merchandise par Route" might have possible approval statuses {open, pending, in progress, closed, cancelled}. While Approval Type "Bill of Lading" might have possible approval statuses {request outstanding, ready for request, requested, approved, approved conditionally, rejected, void}. true false Reference Internal N/A
Transport Document Clause 5a2be107-395d-ee11-b850-44e517a1f1d9 Transport Document true Transport Documents can contain clauses, that specify conditions for the handling of cargo or of the shipment, as well as written instructions, legally required information, etc. Clauses have types and can have pre-defined texts. true false Transactional Internal N/A
Transport Document Clause Type 5c2be107-395d-ee11-b850-44e517a1f1d9 Transport Document true Transport Document Clauses have types, which will be obtained via "Transport Document Clause Type". true false Reference Internal N/A
Predefined Transport Document Clause 5e2be107-395d-ee11-b850-44e517a1f1d9 Transport Document true Some Transport Document Clauses can be pre-defined, and in certain business and/or legal scenarios, such pre-definitions might actually be mandatory. When clauses are pre-defined, the clause text in "Transport Document Clause" class shall be automatically populated with the default value from the "Pre-Defined Transport Document Clause" class. true false Master Internal N/A
Transport Document 61540381-b4fc-e911-80eb-9cd21e38f3a4 Transport Document true Transport documents provide an accounting record of the transaction, instructions on where and how to ship the goods and a statement giving instructions for handling the shipment. Examples of transport documents are: Bill of Lading, AirWay Bill, SeaWay Bill, House Bill of Lading, Convention de Merchandise par Route, etc. Each transport document type is used for a specific transport mode (sea, air, etc.), and there are also specific transport documents for multimodal transport services. Master and House Transport Documents Transport Documents can be divided in to 2 large types: Master and House. A Master Transport Document can only be issued by a Carrier, and is always issued for a transport. The Master is issued to the party that requested the service from the Carrier (be that party a Customer or a Freight Forwarder). A House Transport Document is issued by a Freight Forwarder (or similar) to a Customer, and is typically issued when a Customer contracts the transport service from a Freight Forwarder instead of directly with a Carrier. For this reason, the same Master Transport Document can group/ relate to multiple House Transport Documents, because a Freight Forwarder might group cargo from multiple customers in to 1 single shipment, and then make 1 single shipment request to a Carrier. Self-Relationship For the reasons stated above in "Master and House Transport Document", if and only if a Transport Document is a House, then it will be a child of a Master Transport Document. If Maersk O&L uses a House Transport Document, we might choose to record the Master Transport Document as well, for which relationship is 0..1 on parent side. For the same reason, if we use a Master Transport Document, we might choose to record its corresponding Houses (if it's a business scenario in which they exist, of course), for which relationship is 0..* on child side. true true Transactional Internal Competitive Strategic Information
Transport Document Type 75540381-b4fc-e911-80eb-9cd21e38f3a4 Transport Document true A classification of a Transport Document (TD). Examples: Bill of Lading (BL) Sea Way Bill (SWB) House Bill of Lading (HBL) House Sea Way Bill (HSWB) Air Way Bill (AWB) House Air Way Bill (HAWB) Convention de Merchandise par Route (CMR) Pro Bill of Lading (PBL) (for Truck in US) Multimodal Bill of Lading (MBL) Self-Relationship (Parent and Child) (see "Transport Document" class documentation on "Master and House Transport Documents" for additional context) Transport document types can be child of other transport document types. Examples: House Bill of Lading (HBL) is child of Bill of Lading (BL) House Sea Way Bill (HSWB) is child of Sea Way Bill (SWB) House Air Way Bill (HAWB) is child of Air Way Bill (AWB) ATTENTION: it should be noted, however, that 1 specific transport document type can only be a child/parent of 1 specific document type. In other words, and using an example, House Air Way Bill (HAWB) is child of Air Way Bill (AWB), and can only be child of Air Way Bill (AWB), it cannot be child of other transport document types, such as Bill of Lading (BL) for instance. This is reason why cardinalities are 0..1 for parent and 0..1 for child (it can never be more than 1). It should also be noted that if a transport document type is a parent of another transport document type (i.e. it's a "Master"), then it cannot be a child of another transport document type. And, for the same reason, when a transport document type is a child of another transport document type (i.e. it's a "House"), then it cannot be a parent of another transport document type. In other words, a transport document type cannot be both a parent and a child at the same time. NVOCC, Negotiable, Switchable, Unfreighted (Memo), Government, etc. Transport Documents that are Negotiable, Switchable, Unfreighted (Memo), NVOCC issued, Government issued, etc., will NOT be considered separate Transport Document Types, as they are simply variations of the same Transport Document Type. So, instead, these variations will be obtained via Boolean attributes on the Transport Document Type class. Negotiable: a TD version whereby TD is a contract of carriage that can be transferred to a third party. Switchable: a TD version whereby Consignee, Notify Parties and final destination of shipment can be changed during journey. Unfreighted: also known as "Memo" (example: Memo Bill of Lading). A TD version whereby TD is a non-negotiable, non-transferable, unfreighted TD, that is only used as a receipt of goods and does not classify as a document of title. ATTENTION: this means that when field "Is Unfreighted" = "Yes", then field "Is Negotiable" must always necessarily be = "No". NVOCC: a TD version that is issued by a NVOCC (Non-Vessel Operating Common Carrier). For this specific case, we have a relationship with Carrier Type class, instead of a Boolean. Government: a TD version that is issued by a Government, or Government Agency, or equivalent state or public entity, from a specific country. In this case, on top of the respective Boolean attribute, it will also have a relationship with Class "Country". Local: any other possible country local versions of a TD. In this case, instead of a Boolean attribute, it will have a relationship with Class "Country". true false Reference Internal N/A
Transport Document Line d1ef16f1-8f40-ec11-a3e0-a0510b9e9705 Transport Document true Breaks down the transport document in to lines representing shipped cargo in more details. true false Transactional Internal N/A
Carrier Response Type 3c963fe5-4f3b-ea11-ad95-40b034e2c22b Verified Gross Mass true The types of responses are kept here so that all responses received from carriers are standardized. Note that also error codes are kept here and should be accompanied with a description of what the error code means. true false Reference Internal N/A
Filing 8c3dfb91-806c-ee11-a1be-d7e14702d112 Verified Gross Mass true Explains how filing is done, e.g. via Cargo Smart and what the properties are related to that. true false Transactional Internal N/A
Carrier Response a7364ad1-4f3b-ea11-ad95-40b034e2c22b Verified Gross Mass true This is the response that comes back from the carrier after the VGM has been filled. The response can be an acknowledgement but could also be an error or decline. true false Transactional Internal N/A
Verified Gross Mass Template dd20de52-4f3b-ea11-ad95-40b034e2c22b Verified Gross Mass true User can set up templates that can be applied when filling the Verified Gross Mass. This makes it easy for the user to easily file based on either master data entries or on directly input data that should be applied when filing. true false Transactional Internal N/A
Verified Gross Mass de9a6618-7936-ea11-ad93-40b034e2c22b Verified Gross Mass true The VGM filling constitutes a number of mass measurements that is submitted to a vessel carrier before the container is put onboard a vessel. The carrier must accept the VGM filing before the container is actually put on the vessel. It is a requirement that VGM filings are versioned whenever there is change. Status indications: The timestamps associated with the status of the business object is considered a physical implementation. Examples of these include "BookedTimestamp", "CancelledTimestamp" and "ConfirmedTimestamp". true true Transactional Internal N/A
Service Order 09f59496-cabf-ec11-a3fa-a0510b9e9705 Work Order true A type of Work Order that specifies non-transported related services, such as customs clearance, maintenance and repair, fumigation, sorting, labelling and scanning, etc. true true Transactional Internal N/A
Transport Order 88a12532-253b-ea11-ad95-40b034e2c22b Work Order true A type of Work Order that relates to transport services only. The Transport order is how the shipment operations will be requested per what is required in Service Plan and Transport Plan. It is a construct that handles the complexity of the many-to-many relationship between Service Plan (via Service Plan Legs), Transport Plan and Load Plan (i.e. Cargo Stuffing). This triple many-to-many relationship is due to complexity of business scenarios and possible combinations of Service Plan, Transport Plan and Load Plan. This includes, among others, scenarios of LCL, Milk Run, MCC, Multimodal, Intermodal, Transport by Carrier, Transport by Forwarder, etc., as well as combinations of such scenarios. The extensive list and illustration of all possible business scenarios for generation of Service Plan Legs can be found here: https://teamsite.maerskgroup.com/:b:/r/teams/maerskinformationmodel-communityofpractice/Shared%20Documents/01%20MIM%20Subject%20Areas/31%20-%20Service%20Plan/Service%20Plan.pdf?csf=1&web=1&e=4BFy3F Relationship Between Service Plan (Legs), Transport Plan, Transport Order, Transport Leg Service Plan (Legs) can be seen as an individual service request by a Customer to move cargo from one location to another and perform other logistics services. Transport Plan is the actual execution of that service, whereby Maersk O&L contracts a Transport Provider to execute 1 or more of the Service Legs. Transport Order can consider and combines Service Plan Legs from same Service Plan and/can group Service Plan Legs from different Service Plans (this is the case, for instance, of LCL business scenario) to execute delivery of the service Transport Legs will be the actual physical stages of the transport, performed by a vehicle (vessel, truck, aircraft, etc.), and therefore, wont necessarily match the Service Legs. Operational factors include (not exhaustive): Location match, Type of Cargo combination, Cost, Service available by transport providers in that area, Time requirements by customer etc Grouping of Service Plan Legs - IMPORTANT The Transport Order considers factors on what can logically go together from a shipment operations perspective. Operational factors include (not exhaustive): Location match, Type of Cargo combination, Cost, Service available by transport providers in that area, Time requirements by customer etc Relationship Between Service Plan (Legs) and Transport Plan Each Service Plan Leg can be seen as an individual service request by a Customer, to move cargo from one Service Plan Location to another. The Transport Plan is the actual execution of that service, whereby Maersk O&L contracts a Transport Provider to execute 1 or more of the Service Plan Legs. The Transport Plan (via Transport Order) can group Service Plan Legs from same Service Plan, but also group Service Plan Legs from different Service Plans (this is the case, for instance, of LCL business scenario). The Transport Legs will be the actual physical stages of the transport, performed by a vehicle (vessel, truck, aircraft, etc.), and therefore, wont necessarily match the Service Legs. Cargo Stuffing and VGM A TO may have 0 CS, for the business scenario where Maersk O&L is not the consolidator. When this happens VGM must be obtained via direct relationship with VGM class (see documentation on that relationship). If Maersk O&L is the consolidator, then we'll have a relationship to Cargo Stuffing, but we won't have a direct relationship to VGM (as VGM will be obtained indirectly by Cargo Stuffing). If Maersk O&L is not the consolidator, then we won't have a relationship to Cargo Stuffing, and we will have a direct relationship to VGM, in order to obtain VGM. true true Transactional Internal N/A
Work Order b3c47963-a3c0-ec11-a3fa-a0510b9e9705 Work Order true A Maersk internal order/ instruction to carry out the delivery of services that were requested by a customer, typically via a booking or similar request. The Work Order can therefore include and indicate work processes and activities to be carried out by Maersk employees. The Work Order can also include services to be executed out by vendors contracted by Maersk. Work Orders can be classified by Transport Activity (import, export, etc.) and/ or by Product (Ocean, Supply Chain, Inland, Booking Agent, etc.). true true Transactional Internal N/A
Seal 47550381-b4fc-e911-80eb-9cd21e38f3a4 Seal true Equipment (ISO-, or ULD container) and Truck seals are door seals that are attached once a shipment is loaded in order to ensure no tampering has happened during transport. A seal is meant to stay on through to the equipment- or truck's final destination and is removed by the consignee. Each seal has its own unique number as identification that is listed on the shipping paperwork. Some seals may also carry a barcode for easy scanning of the seal number. More advanced seal also comes with RFID. Note: All containers moving under a Maersk bill of lading must have a high security bolt seal, meeting the criteria of ISO PAS 17712, affixed to it at all times during transport. Air cargo: Seals are also applied to air cargo equipment. Land cargo: Seals are also applied to vehicle like trucks. true true Transactional Internal N/A
Transport Plan Relation 0caab6d2-bee8-11f0-64d1-e682385842d0 Transport Plan true Allows a transport plan to be related to other transport plans for a specific reason. true false Transactional Internal N/A
Transport Plan Relation Reason 0caab6d4-bee8-11f0-64d1-e682385842d0 Transport Plan true Describes the type of relationship between two transport plans such as: a transport plan for a booking made at origin related to one (or more) made at destination. a transport plan for a booking that got split in smaller bookings. a transport plan for a booking for return of cargo, related to an original one. etc. true false Reference Internal N/A
Transport Plan Update 3adfd4f9-26f7-ee11-b887-44e517a1f1d9 Transport Plan true When a Transport Plan is updated/ changed, then in some business scenarios a reason for such update/change must be provided. true false Transactional Internal N/A
Transport Provider Option 3e8a8dd6-1f86-ea11-a3ad-a0510b9e9705 Transport Plan true A Transport Plan can only have 1 Transport Provider. Nevertheless, a Transport Plan can have more 1 Transport Provider Option. The rationale behind this is that more than 1 Transport Provider Option can be planned for the same Transport Plan, and these options can even be prioritized in a list. Then, 1 and only 1 Transport Provider will be selected from that list. If, for any business reasons, the originally selected Transport Provider needs to be changed later on, then another Transport Provider Option must be picked (if a prioritized list was made, this would be option 2). This ability of having Transport Provider Options is a key feature of the value of a Transport Plan. Field Logic When a Transport Provider Option is the one selected, field "Is Selected" = Yes, and that same field must be "No" for all other Transport Provider Option instances. Field "Selection Priority" is not mandatory, and will contain priority selection order of each Transport Provider Option. Carriers, Freight Forwarders and Multimodal The term "Transport Provider" was chosen, because it can be either a Carrier (so-called "2PL") or a Freight Forwarder (so-called "3PL") providing transport services to Maersk O&L. It should be noted that, because a Transport Plan has multiple Transport Legs, then a Transport Plan can be multimodal (ex: sea-air, sea-rail, etc.) or intermodal (ex: sea w/ haulage, air w/ haulage, etc.). Typically, in a multimodal scenario, the Transport Provider will be a Freight Forwarder. Contract A Transport Provider Option may have associated with it a specific Shipping Contract (i.e. agreement with Transport Provider) stating financial conditions for the transport. This means that there is also the possibility that you may have 2 or more Transport Provide Options for the same Transport Provider but under different contracts. true false Transactional Internal Competitive Strategic Information
Transport Plan 7b7d4b86-e84e-ea11-ad9c-40b034e2c22b Transport Plan true (see class "Transport Plan Type" for other names by which "Transport Plan" is known) The Transport Plan represents the planning and actual execution of a transport service (i.e. the physical journey Maersk O&L is planning for a specific transport, its locations, transportation legs, and events associated with that transport), whereby Maersk O&L contracts a Transport Provider to execute it. Such transport service will be the actual execution of a transport service request by a Customer. Typically (but not necessarily), such transport service request comes in the shape of a Service Plan Leg from a Service Plan (see Transport Order and Service Plan domains for more details). There will be 1 Transport Plan for 1 service by 1 Transport Provider. In other words, 1 Transport Plan for 1 Carrier Booking. true true Transactional Internal Competitive Strategic Information
Transport Plan Leg 9bc710d8-e84e-ea11-ad9c-40b034e2c22b Transport Plan true A leg of a Transport Plan. Represents an actual leg of the actual execution of a transport. The intention is that any means of transport can be handled via this class by setting the correct transport mode and associated data, if such exists (e.g. Vessel Leg, Flight Schedule. etc.). There will be 1 Transport Plan Leg per Vehicle. That is, each Transport Plan has a minimum of 1 Transport Plan Leg, and there will only be an additional leg for each additional vehicle. Examples: Transport Mode of Transport Plan is Ocean, 1 vessel will be used: then 1 Transport Plan Leg. Transport Mode of Transport Plan is Ocean, 3 vessels will be used (i.e. we have transshipment): then 3 Transport Plan Legs. Transport Mode of Transport Plan is Sea-Air, with 2 vessels and 1 aircraft: then 3 Transport Plan Legs Transport Mode of Transport Plan is Ocean, 1 vessel will be used + haulage at destination by carrier included: then 2 Transport Plan Legs, 1 for vessel, another for truck. It should be noted that tracking the multiple vessel port calls by same vessel is still possible and covered. This is explained below in "Ocean Mode and Vessel Port Calls". Transport Mode and Multimodality It should be noted that a Transport Plan can have a multimodal Transport Mode (like sea-air, sea-rail, etc.), but a Transport Plan Leg can't, as a Leg must necessarily be of a single transport mode only. In other words, and using an example, if Transport Plan mode is Sea-Air, then at least 2 Transport Plan Legs must exist, 1 covering the Sea part (Mode for that Leg is "Ocean"), and another covering the Air part (Mode for that Leg is "Air"). Cargo Service Type Cargo Service Type (FCL, LCL, Conventional, etc.), will be maintained on each Transport Plan Leg. This is because a Transport Plan can be multimodal, which in turn may imply that different parts of the transport (i.e. different legs) might have different Cargo Service Types. Schedules and Vehicles Depending on Transport Mode, Transport Plan Leg can be either associated with a schedule (via "Carriage" classes) or a vehicle: If Mode is Ocean, Air or Rail, then Transport Plan Leg will have a schedule via respectively, Vessel Port Calls, Flight Legs or Rail Schedule Locations. In this case, the Vehicle is obtained indirectly, via the Schedule. If Mode is Road or Inland Water, then Transport Plan Leg will have either, respectively, a Truck or a Barge. This is because there are no specific schedules for these modes. Carriage and Start and End Points When mode of a Transport Plan Leg is either Ocean, Air or Rail, it will relate (via proper Carriage class) to 2 schedule locations (either via Vessel Port Calls, Flight Legs, or Rail Schedule Locations). The reason we have 2 points instead of 1 is because the Transport Plan Leg's start location and end location (modelled via relationships to Facility) won't necessarily coincide with the start and end of a schedule leg. Example: Transport Plan Leg start is Port B Transport Plan Leg end is Port E Vessel Schedule has 7 ports in this sequence: A, B, C, D, E, F, G. Then, Transport Plan Leg will relate to 2 Vessel Port Calls: B and E Therefore, Transport Plan Leg will indirectly relate to 3 vessel legs: B to C, C to D, and D to E. This will also allow more granular tracking of schedules, when there is a business need for that. Scheduled, Estimated and Actual Dates The key dates (departure and arrival) of a transport plan leg are kept here, in both scheduled, estimated and actual, for ease of reference, and in cases where the transport plan leg is not related to any scheduled legs. These could be handled via treating them as Transport Events as well. ETD and ETA from a forwarder would also be stored on the transport plan legs level. Detention and Demurrage Dates Demurrage: Charged when containers are still full and under the control of the shipping line, and have not been cleared through customs or picked up by the consignee. Detention: Costs incurred by a customer for using equipment beyond the given free time, typically outside of the terminal. Six date-times are introduced to handle scheduled, estimated and actual last free dates and last free delivery dates to support detention and demurrage scheduling. true true Transactional Internal Competitive Strategic Information
Withholding Tax Information 0c393a81-b4fc-e911-80eb-9cd21e38f3a4 Taxation Information true To enable withholding tax to be posted and the amounts to be reported to the vendor and the tax authorities, you must enter certain information in the system. You must specify a withholding tax code to enable the system to calculate the tax amount. This code is defaulted from the vendor master record when you enter a line item if the vendor is subject to withholding tax. true true Master Confidential N/A
Inter Company Activity 124e5916-96e7-ee11-b885-44e517a1f1d9 Taxation Information true Defines what type of Inter Company Activities can be carried out for a given Party within a given Tax Jurisdiction. true false Reference Internal N/A
Tax Information 334a0381-b4fc-e911-80eb-9cd21e38f3a4 Taxation Information true All Tax Information related to a Party, within a specific Tax Jurisdiction that is applicable to said Party. There will be 1 Tax Information instance per Tax Jurisdiction. There is typically 1 Tax Jurisdiction per Country, but other jurisdictions (city, regional, inter-country, etc.) can happen too. true true Master Confidential N/A
Tax Identification 3c4a0381-b4fc-e911-80eb-9cd21e38f3a4 Taxation Information true Tax information numbers are constructed of a tax information type (ex. that it is a 'Tax Number' or 'VAT Number') together with either a relation to predefined tax information or an ad-hoc entered tax information number. This entity allows the customer/vendors to be associated with several diferent kinds tax information, either predefined or typed in upon setting up/maintaining the customer/vendor. true true Master Confidential N/A
Vendor Service Type 0590e906-1c9b-ed11-8c00-5c879c3c5a54 Vendor true Identifies the services the vendor is providing to the organization Examples: Security Services Trucking CFS Terminal Operations true false Reference Internal N/A
Vendor Business Unit Profile 3055b1f1-25d6-ee11-b882-44e517a1f1d9 Vendor true Details and features of Vendor that are specific and only applicable within a specific Business Unit or Division of Maersk. Such Business Units/ Divisions are typically Company Codes or Purchasing Organisations. true false Master Internal N/A
Vendor 6ed39a52-5fc7-ee11-b87a-44e517a1f1d9 Vendor true A Vendor is a type of party that provides/ sells products or services to Maersk and/or Maesk Business Unit(s). true true Master Internal N/A
Email Address 414a0381-b4fc-e911-80eb-9cd21e38f3a4 Contact Address true Email address. true true Master Confidential Personal Identifiable Information
Telecommunication Number 574a0381-b4fc-e911-80eb-9cd21e38f3a4 Contact Address true A number that can be used for contact via a telecommunications system. Examples include: Phone number (land line) Mobile or cell phone number Fax number Pager number true true Master Confidential Personal Identifiable Information
Contact Address 634a0381-b4fc-e911-80eb-9cd21e38f3a4 Contact Address true A specific entry for a contact address or end-point used in order to get in touch with a party, a role played by a party, facilities, vessels etc. Examples include: Web Page Address Email Address Telecommunications Number Postal Address true true Master Confidential N/A
Postal Address 6a4a0381-b4fc-e911-80eb-9cd21e38f3a4 Contact Address true A physical mailing address. Typically, a street address. It is the particulars of the place where an organisation is situated. An address consists of different attributes such as house/street number, street name, city, district, state/region and country. Note: The address may not "literally" be able to receive mail, for various reasons. true true Master Confidential Personal Identifiable Information
Contact Address Purpose 744a0381-b4fc-e911-80eb-9cd21e38f3a4 Contact Address true Each data object which can have contact addresses associated (e.g. Party, Party Role, Vessel etc.) may indicate a specific purpose for the contact address. For instance in the Party Role contact address scenario, there may be specific addresses for: Mailing address Shipping address Billing address Drop off address Service address Headquarter For customers they may have: Primary email address Secondary email address For employees they may have: Home email address Work email address true false Reference Confidential N/A
Web Page Address 768696be-7f83-ee11-a1be-d7e14702d112 Contact Address true Web page address. true true Master Internal N/A
Party Function 550b14bc-42b0-ee11-a1c0-97e99c96f3d2 Party Association true A "Party Function" will specify what purpose the relationship with the party serves. Examples of such could be that a Party should be treated as: Agent Consignee Buyer Carrier Vendor Supplier Manufacturer Shipper Notify Party Seller Ship To Consolidator Other Consumer Importer of Record Factory Office Customs House Agent Origin Handling Party Destination Handling Party Sold To First Notify Party Additional Notify Party Customs Authority To order (associated with the role of Consignee) Same as consignee (associated with the role of First Notify Party) Customer Owner Invoice Party Credit Party Dangerous Cargo Emergency Contact Person Approver Weigher true false Reference Internal N/A
Party Association eee6bf7e-ecb4-ea11-adb6-40b034e2c22b Party Association true A generic association to support both master and transactional data associations to parties. Transactional data support Name and address is deliberately kept on the class as members to signify that it can be stored transactionally where such is need to be kept as it was at the creation time. If the data needs to be refreshed from the master data set, this must be a conscious action. The data also needs to be editable to support non master data based party entries. Customer Order Several parties are associated with the Customer Order. Examples: Consignee Agent Buyer Carrier Vendor Supplier Note: The consignee on an order is always mandatory to have in master data set. Note: Many of these are today kept in the order references. Some of the parties are merely a name of a person, e.g.: "Buyer", "Solene Fouladian" Customer Order Line E.g. the master data for Chu Kwun Key party as a shipper is kept with the Party Function, including address, identifiers, keys etc. and the fact that this party acts as Shipper on the order line is kept via the Party Function Code (e.g. using an enum literal "SHIPPER" or a code "SHIP"). Example parties: Shipper Consignee Notify Party Seller Buyer Ship To Consolidator Other Supplier Consumer Carrier Importer of Record Note on physicalization: We might need the actual Contact Address related here unless we can rely on getting that via the Party. Shipper Booking Examples of party Functions that should be supported: Vendor Factory Consignee Office Shipper Buyer Notify Party Customs House AgentAlso referred to as the CHA which is assigned by the shipper. This is used in India where the CHA must be identified on the Cargo Stuffing Lines (when doing container load plans) that comes from the Shipper Booking Lines. Further to the classic parties mentioned above there is a need to indicate what internal parties are relevant for the Shipper Booking. These include e.g.: Origin Handling Party Destination Handling Party Packing List As the Shipper can change parties on the Packing List and edit these this structure must be present. Examples: Factory Sold To Supplier Transport Document Examples: Shipper Consignee First Notify Party Additional Notify Party Customs Authority Carrier A Transport Document typically has associated Party master data. However, in some cases it is instead associated with a pre-defined TPDoc Party Special Text. This is to support cases where a Transport Document is required to be produced with such special text rather than a party name or identification. Examples of pre-defined TPDoc Party Special Texts include: "To order" associated with the role of Consignee "Same as consignee" associated with the role of First Notify Party Carrier Booking Name and address is members needed to signify that it needs to be stored transactionally as it must be kept as it was at the creation time. The transaction data is not updated on the master data. Carrier Booking party examples: Customer Supplier Owner Carrier Shipper Consignee Notify Party Invoice Party Credit Party Dangerous Cargo Emergency Contact Person true false Transactional Confidential Personal Identifiable Information
Certification Level 021b3f31-99be-ee11-816b-c403a888648f Party true The level of Certification examples : Gold, Silver or 6 stars, 5 stars, etc true false Reference Confidential N/A
Assessment 34925591-059b-ed11-8c00-5c879c3c5a54 Party true Assessments completed by Maersk of the Party and the date of the assessment. This can be either at Organisation or Person level. true false Master Internal N/A
Party Relationship Type 3b4b0381-b4fc-e911-80eb-9cd21e38f3a4 Party true A type of Party Relationship. Examples include: Organizational Relationship Employment Relationship Team member relationship Contact Relationship Alternate Payee Default Internal Organization (for a carrier / country combination) Party Relationships can also exist at a more granular level. Examples include: Member of a Concern Part of Examples of relationships to external information provided by Bureau van Dijk or Dun & Bradstreet Party to BVD: used to create a link between a party record (customer, vendor, etc.), i.e. a record created as per data provided by the party itself, and a BVD record, i.e. a record created as per official data provided by BVD. BVD to BVD HQ: creates link between a BVD record and corresponding BVD HQ record. BVD to BVD GUO: creates link between a BVD record and corresponding BVD GUO record. true false Reference Internal N/A
Industry Classification 3f4b0381-b4fc-e911-80eb-9cd21e38f3a4 Party true A code and name for a particular industry classification from a specific classification system. Examples: APMM as a group orgnization will be involved in Energy and Shipping Maersk Line as an organization might be related to Shipping WalMart might be related to Retail BASF would be Chemical Toyota would be Automotive Standard Classification Systems Industries can be classified according to standardized classification systems, such as: NAICS is an example of an externally governed classification system. There will be a code and a title for each industry.Code: 4821Name: Rail TransportationCode: 482111Name: Line-Haul Railroads SIC is another example of an external industry classificationCode: 53Name: General Merchandise Stores Maersk Industry Classification (a.k.a Verticals) Industries can also be classified according to internally defined industry codes. Maersk uses these to classify customers according to industries which are relevant from a commercial perspective. Examples: retail, chemical, automotive, defense, frozen food, etc. true true Master Internal N/A
Responsibility 4b4b0381-b4fc-e911-80eb-9cd21e38f3a4 Party true A party role can have responsibilities. These can be associated with a defined area or not. Examples: A Global Service Center team in Mumbai (a Party Role) is responsible for handling bookings coming from a United States of America. In this case an "Organisation Unit" representing with name "GSC - Mumbai" will be "Booking Responsible" for "United States of America". A "Carrier" (for example Maersk Line, MSC or Safmarine) can be the "'Default Carrier" for a certain region. An "Organisation Unit" can be "Liner Operation" responsible for a certain geographic cluster. A Customer can be owned by a country cluster - this is resolved via this class with the responsibility type set to "Country Cluster Ownership". A Customs Office is responsible for a certain country, part of a country (state, province etc.) or a group of countries like the EU. true false Master Internal N/A
Responsibility Type 4e4b0381-b4fc-e911-80eb-9cd21e38f3a4 Party true Responsibility types, e.g. (should be read as 'Front Office' for, in the sense that a certain organisational unit is the front office responsible for a certain customer): Booking Responsible Booking Administrator Booking Processor Default Country Business Unit Import Default Country Business Unit Export Front Office Liner Operation Customer Service Country Cluster Ownership true false Reference Internal N/A
Assessment Type 52f97ca2-059b-ed11-8c00-5c879c3c5a54 Party true The system which controls the assessments chosen for the selected Party. Examples: ESG Environmental, Social and Governance A set of standards measuring a business's impact on society, the environment, and how transparent and accountable it is. true false Reference Public N/A
Segment Type 616e68f9-ae66-ef11-b8a3-44e517a1f1d9 Party true Defines the type of Segmentation. It's not mandatory as there might be scenarios where typing the segmentation is unnecessary. Examples of segment type include: - Vertical - Value Proposition - Attractiveness true false Reference Public N/A
Sales Account 624b0381-b4fc-e911-80eb-9cd21e38f3a4 Party true Represents a specific engagement between an organisation and a connected customer in terms of sales of products. true true Master Internal N/A
Brand 684b0381-b4fc-e911-80eb-9cd21e38f3a4 Party true A name, term, design, symbol, or combination of these, under which products and services of an organisation are sold. Examples: Internal: Maersk, Sealand, Hamburg Sud External: Coca-Cola, Sprite, Fanta, Aquarius true true Master Internal N/A
Ocean Carrier 884a0381-b4fc-e911-80eb-9cd21e38f3a4 Party true A carrier that transports cargo by maritime means. NVOCC An NVOCC (Non Vessel Operating Common Carrier) is a common carrier that holds itself out to the public to provide ocean transportation, issues its own house bills of lading or equivalent document, but does not operate the vessels by which ocean transportation is provided. Examples are: DB Schencker SCAC code DBSC DAMCO SCAC code DMCQ The NVOCC accepts the liabilities of a carrier in certain cases. A freight forwarder does not accept the liabilities of a carrier in any case. SCAC The Standard Carrier Alpha Code (SCAC) is a unique code used to identify transportation companies, e.g. MAEU for Maersk Line, SAFM for SafMarine, MCPU for MCC Transport etc. The SCAC code is issued by a US transport organization and therefore not all ocean carriers will have a SCAC. SMDG The Ship Message Design Group Code is another code which identifies some of the ocean carriers in the world. true true Master Internal N/A
Contact 994a0381-b4fc-e911-80eb-9cd21e38f3a4 Party true A person or team communicating on behalf of an organisation for a particular purpose. true true Master Internal N/A
Party Type b74a0381-b4fc-e911-80eb-9cd21e38f3a4 Party true A type that a Party can act in, in the context of Maersk's business environment. Value examples Party Type: Customer Vendor Carrier Ocean Carrier Air Carrier Road Carrier Rail Carrier Freight Forwarder Banking Institution Classification Society Internal party type examples: Party Types can also apply to internal Maersk organisations or people, such as: String Manager Customer Service Team Customer Service Associate Operations Team Operations Associate Department true false Reference Internal N/A
Segment bb4a0381-b4fc-e911-80eb-9cd21e38f3a4 Party true A segment is a category into which Maersk can classify its relationship with their customers. An entry in the segment list can have a segment type to allow for coarse grained and fine grained segmentation. A second level segregation of segment is often referred as 'segment value'. Example of top level segments Efficiency Value Proposition Example of hierarchy with second level segments: 1. Efficiency 2. Digital Innovator 2. Specialised Freight Forwarder 1. Value Proposition 2. Advancement 2. Ambition 2. Ease 2. Efficiency 2. Expertise 2. Simplicity The second level segment above must have the segment code of the parent in their parent segment code column/attribute. true true Reference Internal N/A
Party bb4b0381-b4fc-e911-80eb-9cd21e38f3a4 Party true An organisation or individual of interest to the enterprise or engaged with the enterprise. Value examples: Party: Puma HP Maersk Bureau Van Dijk true true Master Internal N/A
Party Relationship c34b0381-b4fc-e911-80eb-9cd21e38f3a4 Party true A relationship between Parties. Examples include: - Customer A uses Customer B as a Forwarder Broker. - Contact C is a contact party for Customer D. - Sales Account X owns Customer A. The relationships can be one to many (e.g. as in the case of a larger Organisational Unit containing multiple smaller Organisational Units), or can be many to many (e.g. if there can be a network of peer to peer relationships between Organisational Units). The relationship can also be used to specify people or departments that are child of organisations. E.g.: Kuehne and Nagel is both a customer and supplier. There are 2 entries in the Party table for Kuehne and Nagel, one for each type. Each type that Kuehne and Nagel performs will be associated with Maersk Line (acting in 'Organization Unit') via the 'Party Relationship' table. Where Kuehne and Nagel acts as suppliers or customers for other organisational units, e.g. DAMCO, this will likewise be entries in 'Party Relationship' table between Kuehne and Nagel's roles and DAMCO as Organization Unit role. true true Master Internal N/A
Communication Preference cba9c75d-6ad8-ed11-b813-c403a888648f Party true Standard or personalized prefered settings for format, content and transmission of information in party-to-party communication. Communication Preference can be used for defining both Export and Import documentation communication channel. true false Master Internal N/A
Industry Classification System cf4a0381-b4fc-e911-80eb-9cd21e38f3a4 Party true The system which controls the set of Organisation Classifications chosen to classify the selected Organisation. Examples: NAICS SIC GICS Or an internal classification system which could for example be named 'Maersk Defined Industry Vertical'. true false Master Internal N/A
Certification d7a03a88-059b-ed11-8c00-5c879c3c5a54 Party true Certifications held by a Party and the date of the certification. This can be either at Organisation or Person level. Certificates can also be given to facilities. true false Master Internal N/A
Certification Type f4d3edb8-059b-ed11-8c00-5c879c3c5a54 Party true The system which controls the set of Certifications chosen to classify the selected Party. Examples: ISO 9001 Certificate The international standard that specifies requirements for a quality management system (QMS). AEO Certificate Authorized Economic Operator, ie the company works in compliance with standards that are set out by the World Customs Organization. University Degrees for Person true false Reference Public N/A
Driver f884d955-5094-ec11-8378-06d53be9dabf Party true A driver of a truck, van or other means of road transportation. true true Master Internal Personal Identifiable Information
Air Carrier f9a7ddd9-346e-ea11-ada3-40b034e2c22b Party true A carrier that transports cargo via air, using aircraft. true true Master Internal N/A
Customer a94b0381-b4fc-e911-80eb-9cd21e38f3a4 Customer true A person or an organization, purchasing services from Maersk Group. true true Master Internal N/A
Dunning Type c69ee431-8dea-ee11-b885-44e517a1f1d9 Customer true Dunning is the activity of following up on customer payments and settlement of unpaid and due invoices. This includes activities like sending account statements, monitor and follow-up payments, or send reminders and notifications, as well as actions in case of non-payment. The exact dunning type of procedure can be different, and this class will specify it. true false Reference Internal N/A
Customer Business Unit Profile f00b5a6c-30e8-ee11-b885-44e517a1f1d9 Customer true Details and features of Customer that are specific and only applicable within a specific Business Unit or Division of Maersk. Such Business Units/ Divisions are typically Company Codes or Purchasing Organisations. true false Master Internal N/A
Credit Information f73b65d4-dcac-eb11-a3cd-a0510b9e9705 Customer true Represents information, typically obtained from an official recognized external source, such as BVD or D&B, that illustrates financial figures (or similar) that can be used to evaluate if a party can be given credit. true true Transactional Internal N/A
Business Activity Type 0f56c759-ec02-ef11-b88a-44e517a1f1d9 Business Unit true Specifies the type of Business Activity. There can be many types, potentially dozens. Types can include Corporate, GSC, Agency, HQ, Support Functions, etc. true false Reference Internal N/A
Reporting Key 39fb3383-4a18-ef11-b88e-44e517a1f1d9 Business Unit true A key used to sort and display items in reports. Typically each Reporting Unit (company code, purchasing organisation, etc.) uses 1 key of each type. true false Reference Internal N/A
Activity Group 5da6d790-4a18-ef11-b88e-44e517a1f1d9 Business Unit true An identifier for groups (or categories) carrying out activities and/or processes. true false Reference Internal N/A
Business Activity c3a5b35a-1502-ef11-b889-44e517a1f1d9 Business Unit true An aggregational financial reporting unit that represents a type of activity, carried within Maersk, that is common to all Maersk Business Units (or at least can be common to multiple Maersk Business Units). This is used for reporting aggregation purposes. For instance, to aggregate financial figures on all Business Units that represent Ocean business activities. true true Master Internal N/A
Business Unit cd5e2c1c-9bfc-ee11-b889-44e517a1f1d9 Business Unit true A Business Unit is a branch or dependency within Maersk, that typically represents a particular Maersk brand (or brands) within a particular local geography (or geographies). Examples: Maersk Portugal, Maersk Netherlands, Maersk Logistics Netherlands, Maersk Logistics China, APM Terminals China, Maersk China, etc. A Business Unit is typically also 1 legal entity, but it doesn't necessarily have to be so, as in some business scenarios the same Maersk legal entity owns multiple Business Units. This complexity is handled via inheritance from Party, as Party contains a provision to express hierarchies of Parties, and therefore of Parties/ Legal Entities that own Business Units. Examples: Maersk Greece Ltd. may own the local representation of the brands Maersk and Hamburg Sud, but the have 1 Business Unit for each: Maersk Greece and Hamburg Sud Greece. Maersk China Ltd. may have 4 Business Units, 1 for each regional geography: Maersk South China, Maersk East China, Maersk North China, Maersk West China. A Business Unit is, by definition, equivalent to a Company Code within the Finance world. true true Master Internal N/A
Reporting Unit df03f25e-a0fc-ee11-b889-44e517a1f1d9 Business Unit true Accounting Transactions and financial figures are typically posted against Company Codes, Sales Organisations, Purchase Organisations, Profit Centres, and/or Cost Centres, among other possible constructs, for reporting and auditing purposes. This abstract class represents any such possible Reporting Units. It should be noted that 1 Maersk Business Unit will by definition always own 1 Company Code.Also, there will be a hierarchy for the different Reporting Unit Types. The hierarchy shall be handled via the recursive relationship. The recursive relationship is ready to handle the current hierarchy or any future hierarchies if changes occur. The current hierarchy is the following: 1 Company Code can own multiple Sales Organisations. 1 Company Code can own multiple Purchase Organisations. 1 Company Code can own multiple Profit Centres. 1 Profit Centre can own multiple Cost Centres. 1 Cost Centre can own multiple Internal Orders. It should also be noted that this abstract construct of "Reporting Unit" also allows for different hierarchies or types of reporting units that may exist in the future. It should finally be noted that Reporting Units, specially Company Codes, must also ultimately report in to larger Business Activities for reporting aggregation purposes. true true Master Internal N/A
Banking Institution e04b0381-b4fc-e911-80eb-9cd21e38f3a4 Bank Details true Is an Organisation that offers financial products and solutions under a Banking License. A Banking Institution is involved in various types of lending, such as corporate finance, housing, project finance, retail, short-term finance, small-medium enterprises, trade, and others. Alternatively, the focus of a banking institution may be only on specific transactions with clients that meet certain requirements and within certain industry sectors. true true Master Confidential N/A
Bank Account e84b0381-b4fc-e911-80eb-9cd21e38f3a4 Bank Details true That part of a bank's service offering which is specific to one of that bank's customers (which can play any one of a number of possible Party Roles, within The Enterprise or external to it. true true Master Confidential Sensitive Personal Information
Product Relationship 02fd1278-b83e-ef11-b89b-44e517a1f1d9 Product true Defines and details relationships between Products, and their nature. true false Master Internal N/A
Product Configuration 0df8e0b1-3d7a-ed11-b81a-44e517a1f1d9 Product true The Product Configuration expresses the available options, conditions, or information related to a Product Element. The Product Element to which a Product Configuration will relate must be a Product Element instance at the bottom of a Product Element hierarchy. true false Transactional Internal N/A
Product Group a444911d-472f-ec11-a3dc-a0510b9e9705 Product true Products can be grouped in to Product Groups. These groups can be for commercial or organisational purposes. Product Groups can be structured in hierarchies, where Product Groups are further grouped in to Parent Product Groups. Currently in Maersk, the hierarchy (top to bottom) goes like this: Product Portfolio, Product Family, and Product. Due to perennial nature of Product Groups, as they often change according to commercial strategies, the Product Group class is kept as abstract and as business scenario inclusive/ agnostic as possible. This means all of these are customizable: the number of Product Group levels/ hierarchies (via the recursive relationship); the naming of Product Group levels (via field Product Group Level Label); the very existence of Product Group levels, i.e. Products may even not relate to a Product Group at all (cardinality is 0..*). true true Master Internal N/A
Sales Channel a844911d-472f-ec11-a3dc-a0510b9e9705 Product true The Sales Channel is a marketing concept that specifies which instances of media are to be used by a customer in order to access a product. It should not be confused with the communication media itself that is used to realize the Sales Channel. For clarity, some examples of Sales Channels are: Maersk.com newsletters Maersk Mobile App magazines While some examples of Communication Media are: email phone fax post website web app true true Master Internal N/A
Product Element Relationship b468f59b-bd3e-ef11-b89b-44e517a1f1d9 Product true Defines and details relationships between Product Elements, and their nature. true false Master Internal N/A
Product d4882db6-e2ba-ea11-a3b3-a0510b9e9705 Product true The standardized service that a customer can purchase as stand-alone, and is replicable across many customers. A Product is offered and sold to a customer as a whole, and cannot have its components sold separately. A complete and updated version of all Products offered by Maersk can be obtained on the Maersk Product Catalogue page: https://teamsite.maerskgroup.com/sites/TransformationOffice/SitePages/Maersk-Product-Catalogue.aspx ATTENTION: It should be noted that only the values of Product defined by the Maersk Product Catalogue can be used. It is not allowed to have Product names/ values either customized and/ or not approved by Maersk Product Catalogue team. true true Master Internal N/A
Product Configuration Option e27ebe17-a47b-ed11-b81a-44e517a1f1d9 Product true A possible value within a range that belongs to a Product Configuration. It shall match an Enumerated Value within a range that belongs to the Predefined Attribute of parent Product Configuration. true false Reference Internal N/A
Product Element fb2e925d-7320-ec11-a3db-a0510b9e9705 Product true Products can be broke down on Product Elements can compose it. And Product Elements can be further broke down/ composed of other Product Elements, establishing a hierarchy. It should be noted that not all levels are mandatory, namely one can choose which level will be the atomic one (lowest possible). It should also be noted that, just like Product, Product Elements can have Variants (via Boolean field). When this is the case, the recursive relationship will indicate what product element was used as the base for the variation. Also like Product, Product Elements can be constrained, i.e. be restricted to specific geographies (country, region, etc.), cargo types, commodities, vessel types, equipment types, etc. true true Master Internal N/A
Material 553d3a81-b4fc-e911-80eb-9cd21e38f3a4 Material true Also known by the business terms "Charge Type" or "Article", the "Material" is a master record containing information about the goods and services that an Enterprise can purchase, sell, produce, or store. The "Material" is typically used within the Lines and Items of Invoices, Purchase Orders, Sales Orders, Rates and Quotations, Contracts and Agreements, Job Costing, or Profit and Loss Statements, to name a few. true true Master Internal Competitive Strategic Information
Material Linkage 7638e60f-de53-ef11-b89f-44e517a1f1d9 Material true Provides the relationship of what materials can be used as counterparts of cost and revenue. For instance, when Material A is used for cost estimates, then Material B should be used as the primary for revenue estimates, and Materials C, D, and E can also be used as alternate choices for revenue estimates. true false Master Internal N/A
Material Group cb2ea4eb-f121-ed11-a415-a0510b9e9705 Material true A group of materials that go logically together from a business point of view. true false Reference Internal N/A
Material Local Name e969c45c-1a91-ef11-b8ad-44e517a1f1d9 Material true Specifies a local name for a Material in an appicable local language. true false Master Internal N/A
Product Offer b00c15f0-1d0f-ec11-a3da-a0510b9e9705 Product Offer true A Product Offer represents a bookable offer presented to a customer for a certain set of request parameters. The product offer consists one or more Products that the offer covers, an agreement/contract that the offer is related to (possibly a freesale one), as well as the rates (price) for each of the products in the offer. The product offer is also associated to one or more elements in a service plan. true true Transactional Confidential N/A
Selected Product Configuration c59e7529-21e8-ed11-b82d-44e517a1f1d9 Product Offer true A Selected Product Configuration represents the product configuration choices made for a given master data Product. The Selected Product Configuration is owned by a Selected Product and does not exist without the context of the Selected Product. For a certain Product Configuration of a Product Element, the Selected Product Configuration is indicating which options have been selected for that configuration. The selected options can be zero, one or multiple options - depending what is allowed by the Product Configuration configurability options. true false Transactional Internal N/A
Selected Product ef0226ef-a4f0-ed11-b82d-44e517a1f1d9 Product Offer true A Selected Product represents a transactional use of a certain master data Product. The Selected Product references exactly one Product and may contain configuration choices for the configurable elements of the Product selected. A Selected Product instance will be for 1 Product, and 1 Product only. However, for the specific scenario where "Is Available" = "false", then Selected Product instance will have 0 Products. true true Transactional Internal N/A
Range Value 032b6abd-ad3a-ec11-835e-06ed1165cb7d Soft Coded Value true Sets an allowable range for the predefined attribute. It is possible to have ranges for date-time, decimal and integer data types. true false Reference Internal N/A
Entity 424700bb-815e-ea11-ad9f-40b034e2c22b Soft Coded Value true Describes a data entity. Example could be "Customer Order" or "Shipper Booking" having 1 or more Predefined Attributes associated. An entity can be made customer specific so that any Predefined Attributes for that entity only applies to that specific customer. Likewise an Entity can be for a particual industry vertical (via Industry Classification). The identification of an Entity as it relates to either a vertical or customer must carry through to the Predefined Attribute and identiy it. true false Transactional Internal N/A
Predefined Attribute Collection 48434807-f5ae-ec11-8382-0666856b4ac5 Soft Coded Value true A way to group a number of predefined attributes for a purpose other than by its entity. This is for example used when grouping predefined attributes in warehouse management system into a group for DECON. true false Master Internal N/A
Soft Coded Value 6caabfd1-a343-ec11-a3e2-a0510b9e9705 Soft Coded Value true A data element for handling soft coded values primarily needed by the Maersk customer - but can also be used to support internal processes. The data is used for various purposes in the customers integration into both Maersk systems and their own benefit having their data represented in downstream documentation. These data elements are many times carried over to generated shipping related documentation and fed into reporting, dashboard and analytics solutions for Maersk and customers benefit. Custom Cargo Package Details For the specific business use case of Custom Cargo Package Details, it should be noted that the value and sequence will be recorded in the "Additional Value" class and the so-called "header" or "column" name will be recorded as "Attribute Name" in the related class "Predefined Attribute" from the "Soft Coded Value" domain. Standardising values Below are suggested standards to be followed for soft coded values Boolean - Use lowercase true or false Decimal - Use punctuation as decimal separator Datetime - Use ISO8601 standard true false Transactional Internal N/A
Default Value 7bc21e15-ad3a-ec11-835e-06ed1165cb7d Soft Coded Value true Sets the default value of the attribute if applicable. It is possible to have default values for date-time, decimal, integer, string and boolean data types. true false Reference Internal N/A
Predefined Attribute d3fa717e-b83c-ea11-ad96-40b034e2c22b Soft Coded Value true Meta data about an attribute used to describe softcoded values. If the details about attribute meta-data is not known upon storing the softcoded value it can be given the data type of "String". The meta-data needs to support the systems currently in place so that their softcoded values can be migrated to the new platform. That means we need to keep the concept of softcoded attributes like L1, P1 etc. Upon migration better suited Predefined Attribute names should be used. It is vitally important that there is no limit on the number of references in future implementations (e.g. only up to L5). This design approach will enable limitless softcoded values. For new customer implementations more meaningful and aligned Predefined Attribute names for softcoded values must be used e.g. for entity "Customer Order" an attribute name could be "Accounting Period" or "Plant Code". For "Customer Order Line" entity it could be "Season" Custom Fields on User Interface This construct also supports custom fields for certain customers on certain documents. For example today Macys is heavily using customized fields on Packing List and Commercial Invoice. Many fields that would not be relevant to other customers. These are today known as "Dynamic Data" and can be booleans, drop downs (enumerations) and text inputs. Examples of values: Note: the Entity name is migrated as foreign key from "Entity" class Entity Name: Customer Order Attribute Code: O1 Attribute Name: Accounting Period Data Type: String Maximum Length: 0 (no limit on String field length) Minimum Multiplicity: 0 (attribute is optional) Maximum Multiplicity: 1 (only a single value expected per Customer Order) Entity Name: Customer Order Line Attribute Code: L1 Attribute Name: Season Data Type: String Maximum Length: 0 (no limit on String field length) Minimum Multiplicity: 1 (attribute is mandatory) Maximum Multiplicity: 1 (only a single value expected per Customer Order Line) Entity Name: Customer Order Line Attribute Code: L2 Attribute Name: Best Before Date Data Type: Datetime Maximum Length: 0 Minimum Multiplicity: 0 (attribute is optional) Maximum Multiplicity: 1 (only a single value expected per Customer Order Line) Notes: In MODS system we currently use values like L1, L2, L3 (Line Reference), P1, P2, P3 (Product Reference) etc. for indicating what Attribute the soft coded value is for. These do not actually tell what the attribute is about. Going forward we need to standardize the usage of "Predefined Attribute" so that it actually describes what the vaue is. In Shipper database these soft coded value types are kept in the Sequence column of the reference tables, but it is essentially considered the Predefined Attribute. Just as above governance must be applied so the the Predefined Attribute actually describes what the value is. If some ordering must be performed based on the type, this can be implemented in the programming code. Suggested start list for Predefined Attributes: Customer Order Brand Accounting Period Program Code Promotional Deal Sub Brand Month Range Season Name Season Code Calendar Week Customer Order Line Quote Sheet Global Procurement Office Brand Special Allowance Season Name Season Code Event Continuity Calendar Week Shipper Booking GSP Certificate Number true false Transactional Internal N/A
Enumerated Value d8fd3fda-825e-ea11-ad9f-40b034e2c22b Soft Coded Value true It is possible to restrict an attribute to have a number of allowed values that can be assigned to the softcoded value. true false Transactional Internal N/A
International Character Set 0b5f1db2-39b5-ee11-8168-c403a888648f Language true A character set is an element of internationalization that maps and translates an alphabet; that is, the characters that are used in a particular language. Examples could be Japanese Katakana, Greek, Arabic. . true false Reference Internal N/A
Language 3b393a81-b4fc-e911-80eb-9cd21e38f3a4 Language true ISO 639 is the International Standard for language codes. The purpose of ISO 639 is to establish internationally recognised codes (either 2, 3, or 4 letters long) for the representation of languages or language families. true true Reference Public N/A
Shipping Terms cb6cb021-a442-11f0-52c7-e62eed53f945 Shipping Terms true
Incoterm fa190c01-8936-ea11-ad93-40b034e2c22b Shipping Terms true The Incoterms, also known as International Commercial Terms, are a series of pre-defined commercial terms published by the International Chamber of Commerce (ICC), relating to international commercial law. The Incoterms define the responsibilities of exporters and importers in the arrangement of shipments and the transfer of liability involved at various stages of the transaction. The Incoterms inform and define obligations, costs, and risks involved in the delivery of goods from the seller to the buyer, but they do not themselves conclude a contract, determine the price payable, currency or credit terms, govern contract law or define where title to goods transfers. When the ICC officially defines each possible of Incoterms, they designate an official 3-letter code for each Incoterm. It should be noted that the ICC periodically revises the list of Incoterms (typically every 10 years), either removing or adding new values, or even updating the meaning of some of them. true true Reference Public N/A
Exchange Rate Markup 5f179696-de93-ea11-adab-40b034e2c22b Currency true Maersk normally marks up exchange rate at origin e.g. 3% or 5%, when a customer would like to pay in different currency (e.g. when a terminal handling charge is qouted in USD but Shipper would like to pay in CNY). true false Transactional Internal N/A
Exchange Rate 91373a81-b4fc-e911-80eb-9cd21e38f3a4 Currency true An exchange rate is given for conversion from a unit currency to a quotation currency. Example: USD is the unit currency and AED is the quotation currency and the exchange rate is 3.67312 true true Transactional Public N/A
Exchange Rate Source 96373a81-b4fc-e911-80eb-9cd21e38f3a4 Currency true The source that provided the exchange rate. Examples: Reuters Danske Bank Local National Bank true false Reference Public N/A
Exchange Rate Type 9a373a81-b4fc-e911-80eb-9cd21e38f3a4 Currency true Exchange rates for different purposes for the same date are defined as exchange rate types. If you need to carry out currency exchanges between a number of different currencies, you can simplify exchange rate maintenance by entering a unit currency for the exchange rate type instead of entering exchange rates between every single currency, you then only need specify the exchange rate between each currency and the unit currency. All currency exchange rates then take place in two steps - into the unit currency and from the unit currency into the qoutation currency. Examples: Monthly Average Rate End of Period Rate Daily Rate Reference RateThe Reference Rate is the exchange rate fixed by central banks for all currencies, usually on a daily basis. They are based on a regular daily concertation procedure involving all of the banks governed by that central bank. true false Reference Public N/A
Currency 9e373a81-b4fc-e911-80eb-9cd21e38f3a4 Currency true An internationally recognized currency with ISO code and name. Example: - USD - DKK - AED true true Reference Public N/A
Exchange Rate Markup Type d76a6490-60e8-ee11-b885-44e517a1f1d9 Currency true Defines the type of Exchange Rate Markup. true false Reference Internal N/A
Reference 29354719-f7a2-eb11-8314-061ca927c90b Reference true A reference is used for storing any kind of text or numeric reference that a data object may need in order to refer to other data artefact, be it transactional or master. It could be an Accounting Transaction which needs to keep multiple references to e.g. a Container Number, a Maersk Vessel Code and a Facility Code. This generic "reference pattern" is useful when it is not known in advance what all possible reference types may be relevant, or when there are too many reference types making it infeasible to "hard code" all of them on the data object itself. Each reference must be typed, so it can clearly be identified, what the reference is for, e.g. a Reference with entry "MRKU7324915" is a "Container Number". Every reference is "owned" by the object having the reference; i.e. the reference is an aggregation seen from the owning objects point of view. As an example, if a Container Itinerary has references associated with it, and the Container Itinerary is deleted, all its references will be deleted as well. Examples of transactional data references: - Reference: 981981239 - Reference Type: GCSS Booking Number - Reference: R4078203 - Reference Type: Bill of lading Number - Reference: 1294893 - Reference Type: Customer Order Number - Reference: Reference: SGN9123556 - Reference Type: Forwarders Cargo Receipt Number Examples of master data references: - Reference: 40REEF - Reference Type: Equipment Size Type - Reference: 20 - Reference Type: ISO Container Size Code - Reference: DRY - Reference Type: Cargo Type - Reference: MRKU7324915 - Reference Type: Container Number - Reference: USLAXTRM - Reference Type: Facility Code - Reference: USLAX - Reference Type: City Code - Reference: US - Reference Type: Country Code true true Reference Internal N/A
Reference Type da4301ca-499e-eb11-ade6-40b034e2c22b Reference true A Reference Type defines a Reference so that it is always possible to know the type, for example Reference "MRKU7324915" is a "Container Number". Examples: - GCSS Booking Number - Customer Order Number - Shipper Booking Number - Vessel Code - Equipment Size Type Container Itinerary use case: Examples of reference types that are relevant for the itinerary: - GCSS Booking Number - ROCK OTT Number - Globe Booking Number - SAP TM Forwarding Order Number - VSA Container Number true false Reference Internal N/A
Transport Mode 60510381-b4fc-e911-80eb-9cd21e38f3a4 Modality true Method of transport used for the carriage of goods. The transport mode is for high level categorisation, but also enables sub-types via the recursive relationship for e.g. mutlimodal combinations. The UN Mode of Transport recommendation explains that sub-types can be introduced to the high level ones given in that standard. Note that classifications like Feeder, Barge, Mother Vessel etc. must be set via Transport Means. Examples of top level: These top-level Transport Modes align with the UN standard for Transport Mode. - Maritime - Rail - Road - Air - Mail - Multimodal transport - Fixed transport installations - Inland water transport - Mode unknown Examples of multimodal subtypes: - Rail and Road combined - Rail and Air combined - Sea and Air combined true true Reference Public N/A
Transport Means 730ab3ce-d338-ef11-a1c5-f3ef5fbf2395 Modality true Describes a the type or role of a a vehicle used for transportation. The UN standard for Means of Transport can be used, but this data also covers Maersk specific needs, like Feeder, Trunk, Shuttle, Mother Vessel etc. so the dataset is not only for particular vehicles. Examples: - General Cargo Vessel - Freightbarge - Feeder - Mother Vessel true false Reference Public N/A
Modality a34204ef-97ab-11f0-6647-9e6a8bfe0eb1 Modality true true false Reference Internal N/A
Measurement 5d7fa997-0e62-ea11-a3a5-a0510b9e9705 Unit of Measurement true This class represents transactional data (not Master Data). The related Master Data classes are reachable via this class. Holds any measurements that are not available as hard coded attributes on the transactional class it relates to. Example 1: A chemical producer has sold biodiesel to a buyer and needs to indicate that the flash point is 130 degrees Celsius in order to have it transported. The flash point value of 130 must be stored in the "Value" attribute; There will be no value stored in the "Bottom Interval Value" attribute; There will be no value stored in the "Top Interval Value" attribute; The foreign key to "Measurement Function" in "Measurement Function Requires Unit of Measurement" (MFRUM) will identify that the measurement is a 'Flash Point'; The foreign key to "Unit of Measurement" in MFRUM will identify that the "Value" is defined in 'Celsius'. Example 2: An American corporation is sourcing tofu from a seller and wishes to specifiy that it must be packed within 35.2 and 41 degrees Fahrenheit temperature limits. There will be no value stored in the "Value" attribute; The minimum packaging temperature of 35.2 must be stored in the "Bottom Interval Value" attribute; The maximum packaging temperature of 41 must be stored in the "Top Interval Value" attribute; The foreign key to "Measurement Function" in "Measurement Function Requires Unit of Measurement" (MFRUM) will identify that the measurements are for Filling Temperature'; The foreign key to "Unit of Measurement" in MFRUM will identify that the "Top Interval Value" and "Bottom Interval Value" are given in 'Fahrenheit'. Relationships to Master Data: This class also handles the *..* relationship between Units of Measurement and Measurement Functions. Units of Measurement can have 0..* Measurement Functions Some examples to illustrate: Degrees Celsius (º) can be used to measure Flash Point, Boiling Point, Melting Point, etc.; Meters (m) can be used to measure carton width, container height, etc.. Defined as 0..* to allow the possibility of UOMs not assigned to a Measurement Function yet. Measurement Functions will have 1..* Units of Measurement Examples again: Flash point can be measured in Celsius, Fahrenheit or Kelvin; Volume can be measured in cubic meters or cubic feet. Measurement Functions cannot, of course, have 0 UOM, otherwise measurement cannot be expressed. true false Reference Public N/A
Unit of Measurement 7d373a81-b4fc-e911-80eb-9cd21e38f3a4 Unit of Measurement true Examples shown under their respective types: Airflow unit Cubic feet per minute Consumption unit Litres per Hour Gallons per hour Dimension unit Centimeter Meter Inch Foot Yard Distance unit Mile Kilometer Nautical Mile Item unit Pieces Power Unit Voltage Ampere Pressure unit Pounds per square inch Temperature unit Celsius Fahrenheit Time unit Second Hour Day Year Velocity unit Knot per hour Kilometers per Hour Volume unit Litre Gallon, US Weight Unit Gram Kilogram Tonne Pound, UK Container Unit Container Unit - as in a container box, where the container size does not matter, e.g. number of boxes in a network capacity Twenty Foot Equivalent Unit - part of UoM list when consumer needs multiple units and cannot fix to enumeration Forty Foot Equivalent Unit - part of UoM list when consumer needs multiple units and cannot fix to enumeration true true Reference Public N/A
Measurement System 83373a81-b4fc-e911-80eb-9cd21e38f3a4 Unit of Measurement true The system specifying a number of Unit of Measurements. Examples: S.I. (Metric) Imperial US Customary Units Time Industry Standard true false Reference Public N/A
Measurement Function aba0cac0-c75e-ea11-a3a5-a0510b9e9705 Unit of Measurement true Specifies what is being measured. Examples: Unit Net Weight Unit Gross Weight Total Net Weight Total Gross Weight Chargeable Net Weight Item Gross Weight Item Net Weight Tare Weight Chargeable Volume Gross volume Net volume Humidity Voltage Density pH Boiling Point Flash Point Melting Point Filling Temperature Maximum Permitted Temperature Each of above measurement functions will have an internal Maersk defined code. The reason we have an internal defined code is because international standard codes (such as UN/EDIFACT) are not extensive enough to contain all possible measure functions. true false Reference Public N/A
Time Frequency 66cb269e-2427-ef11-b894-44e517a1f1d9 Calendar true Defines the frequency of a given event within a time frame. true false Reference Internal N/A
Time Period b8383a81-b4fc-e911-80eb-9cd21e38f3a4 Calendar true A time range between 2 specific dates, that is typically identifiable and recognizable, such as a year, month, quarter, week or day. It can also be used to define other time period types, such as fiscal and accounting periods (such as fiscal years and fiscal quarters), or local time periods (such as a chinese year). true true Reference Public N/A
Time Period Type d5383a81-b4fc-e911-80eb-9cd21e38f3a4 Calendar true The possible standard types of time periods that can exist, such as Year, Quarter, Month, Week, Day, Fiscal Year, Fiscal Month, Accounting Period, Chinese Year, etc. true false Reference Public N/A
Communication Media Type 804a0381-b4fc-e911-80eb-9cd21e38f3a4 Communication Media true Mode of communication between parties. Examples: Email Fax Post Electronic Data Interchange, Classic Application Programmers Interface Website (e.g. for Web based Booking) Telephone Telex true false Reference Internal N/A
Alternative Code 750ae5a6-1843-ea11-ad97-40b034e2c22b Alternative Term true Holds an entry of an alternative code to a piece of data. The alternative code is type by an Alternative Code Type. Examples of alternative code include: - RKST code - RKTS code - GEO ID - IATA code - FIRMS code - Business Unit Identifier, e.g. DZALGMSL1 - Business Partner Code - Business Partner Location Code - Federal Maritime Commission (FMC) code for Organisation - ANSI X12 315 (Event codes for Ocean cargo) - ANSI X12 214 (Event codes for Air cargo) - Schedule K codes - Schedule D codes - DoDAAC (US Department of Defense Activity Address Code) -- used only for US military shipments, for both parties and locations involved (https://en.wikipedia.org/wiki/Department_of_Defense_Activity_Address_Code) - ISO Container Size Type - UN Package Type - IMDG Package Type - Other Package Type Standards An example scenario is when it is necessary to convert our customer's codes internal Maersk used codes. This could be upon receiving EDI data from Walmart Canada, and they use a specific code for their shipper which needs to be converted to a Maersk specific code for the same shipper party (Party Role). This scenario takes place both on incoming and outgoing data to/from the enterprise. true false Reference Internal N/A
Name Alias Type 90f93aad-1843-ea11-ad97-40b034e2c22b Alternative Term true Defines what type a Name Alias is. Examples: Business Partner Name Alias Location Alias Vessel Name Company Name true false Reference Internal N/A
Alternative Code Type 953783b9-1843-ea11-ad97-40b034e2c22b Alternative Term true Defines what type of Alternative Code the entry in Alternative Code is. This class represents the alternative code types (e.g. internal types as RKST, SCV, and external types such as DUNS, CAGE, DoDAAC) These types are the group that the actual alternative code belongs to. The alternative code is a code used somewhere else (internally or externally) and there is a need to map to/from entities stored with internal identification. Examples: Business Partner Code Business Partner Location Code Business Partner City Code Business Partner Country Code Business Partner Carrier Code Business Partner Equipment Code Business Partner Vessel Code Business Partner Equipment Code RKST City Code RKST Country Code MODS Site Code SCV Customer Number SCV Person Code DUNS Organization Code CAGE Organization Code Vessel Code DoDAAC Federal Maritime Commission (FMC) code for Organisation Shipping Association Number Registration of Companies (ROC) Company Registration Number Import Export Code Business Registration Number (BRN) Unique Entity Number (UEN) Economic Operators Registration and Identification number (EORI) Type examples: Business Partner Code: A code that is used by a business partner, e.g. Walmart, to identify one of their business partners, e.g. one of their Shippers. Business Partner City Code: A code for a city used by a business partner, e.g. Walmart, to identify a city in their systems. This will then be mapped to internal Maersk city code for lookup. CAGE: The Commercial And Government Entity Code, or CAGE Code, is a unique identifier assigned to suppliers to various government or defense agencies, as well as to government agencies themselves and also various organizations. DUNS: The Data Universal Numbering System, abbreviated as DUNS or D-U-N-S, is a system developed and regulated by Dun & Bradstreet (D&B) that assigns a unique numeric identifier, referred to as a DUNS number, to a single business entity. DoDAAC: Relevant to US Military only (Department of Defense Automatic Addressing-system Centre) is a 6-character-code identifier of a US military shipper, consignee, and possibly supplier. Each DoDAAC is a unique reference that corresponds to a specific building or office address (e.g. Warehouse 'A', Warehouse 'B', Building 'A', etc.). Applicability examples: - For a site an alternative code could be DoDAAC codes for US military. - For persons the codes relevant could be data like 'USI Person ID', 'USI Common Name', 'SCV Person Code' etc. - For Vessel code alias relevant could be 'Lloyd Code', 'Official Registration Number' - For organizations external identification codes, e.g. Tax ID's, VAT ID's, DUNS, CAGE etc. true false Reference Internal N/A
Name Alias bd70b2a0-1843-ea11-ad97-40b034e2c22b Alternative Term true A Name Alias to some business relevant entity. The name aliases can be used for example to convert inbound EDI traffic where Maersk customers give a certain name to a business partner but in Maersk we give that same business entity a different name. This could e.g. be "Chu K. K. Ltd." if Walmart Canada's name for this shipper is such. Upon receiving the data from Walmart Canada we apply the conversion to the transactional data and store it. If we then need to send data back to Walmart Canada we can convert it back to their Name Alias. true false Reference Internal N/A
Alternative Code Scheme cd30a05d-bf74-ea11-ada5-40b034e2c22b Alternative Term true Holds values for different kinds of classification schemes, it could be 'Organization' for supporting e.g. DUNS numbers or 'Defined Area' for e.g. UN Location codes or internal legacy codes, it could also be 'Vessel' or 'Equipment' etc. true false Reference Internal N/A
Warehouse Area 1a97f3b9-fbe5-eb11-8336-06892ccaedcb Warehouse Storage true An area, section or zone of a warehouse. Typically, these groups a number of racks and/or aisles but can also be sections that do not have any racks and/or aisles, for example a staging area or bulk storage area. Some warehouses will be divided into a number of zones which are the divided into areas. This tree structure is solved with the recursive relationship on warehouse section. true false Master Internal N/A
Warehouse Storage Function 3b47db94-61aa-ec11-8382-06f67abeaacb Warehouse Storage true Functions for the Warehouse Storage Association, e.g. Pick Bin Default, Pick Location Default. true false Reference Internal N/A
Warehouse Storage Type 3f3d636f-921d-11f0-52c7-e62eed53f945 Warehouse Storage true The type of Warehouse Storage. Because Warehouse Storage is recursive, the Warehouse Storage type works on different levels: * A Warehouse contains Warehouse Areas * A Warehouse Area contains Aisles * An Aisle contains Units * A Unit contains Shelves * A Shelf contains Bins * A Bin can be of a type, e.g. for large or small pallets true false Reference Internal N/A
Warehouse Area Type 5fc031cb-ce36-ec11-835e-06e53d9d360b Warehouse Storage true Some examples of types: Zone Section Area Door Goods Receipt Area Goods Issue Area High Rack Shelves Bulk Storage Area Outside Storage Area Open Storage Area Picking Area Staging Area true false Reference Internal N/A
Warehouse Storage 919f3f34-1736-ec11-835e-06750336c553 Warehouse Storage true Represents a place where items or packages can be stored. The Warehouse Storage can be used to represent a whole warehouse, repair station etc. or it can be sub-divisions within a facility like areas, aisles, bins and so forth - typically the latter is used for warehouse configurations. Use for Warehouse example: A warehouse should always have at least one Warehouse Storage to document the area, cubic capacity etc. - if the warehouse is not divided in to sub areas the entire warehouse area, are maintained as a Warehouse Storage type of "Warehouse". true true Master Internal N/A
Warehouse Storage Association a287117c-60aa-ec11-8382-06f67abeaacb Warehouse Storage true Allows an object to be associated with multiple, typed, Warehouse Storages. For example a commodity master data object will need to specific a default pick location and a default pick bin location. true false Transactional Internal N/A
Warehouse Storage Status b6882624-598e-ee11-a1be-d7e14702d112 Warehouse Storage true Gives the status of a Warehouse Storage. The status can describe for example, Empty, Filled, Partially Filled, Locked and so forth. true false Reference Internal N/A
Loading Dock d59c88b5-e627-ec11-8359-064588704927 Warehouse Storage true Represents one loading dock where a truck can load/unload or place a container for load/unload. Loading docks are typiclly just numbered 1,2,3,4 etc. at a facility. true true Master Internal N/A
Replenishment Type 1413abb9-7d30-ec11-835e-0646afcad5a9 Inventory Management true Examples: Min-max - triggers restocking activity when a certain product reaches a predetermined minimum threshold Demand inventory - replenishment quantity should be just enough to fulfill a pending order or group of orders without leaving excess stock behind Top-off - similar min/max thresholds as the min/max replenishment model and usually runs on set schedule Periodic - if stock levels fall below the minimum threshold, replenishment orders are placed. Otherwise, they are skipped until the next review point true false Reference Internal N/A
Supply 2f8c4f11-7f30-ec11-835e-0646afcad5a9 Inventory Management true Specifies how the supply of a certain commodity is in general terms. For example what is the typical lead time or shipping lead time for a commodity at a specific facility. true false Master Internal N/A
Inventory Management 7c8362c9-6735-ec11-835e-0678e0d2d5a7 Inventory Management true A super class abstracting several different kind of inventory management that can be used to control inventories at a facility. true true Master Internal N/A
Inventory Control 810ab886-7830-ec11-835e-0646afcad5a9 Inventory Management true How to control the inventory at a particular warehouse. Minimum units to have, maximum units etc. true false Master Internal N/A
Replenishment a4e6755b-7d30-ec11-835e-0646afcad5a9 Inventory Management true Specifies how to control replenishmnet of commodities in the facility. true false Master Internal N/A
Inventory Transaction Relation Reason 01b09755-c85c-ee11-a1bb-fab3d952de1e Inventory true Describes the type of relationship between two inventory transactions. true false Reference Internal N/A
Commodity Inventory 12140c02-2536-ec11-835e-06750336c553 Inventory true Represents the inventory of Commodities at a warehouse storage. A Commodity is master data about a Commodity Item so this inventory basically tells quantities, volume etc. about commodities and does not relate to the individual items (e.g. identified by RFID). Note that a warehouse storage is anything from the warehouse itself down to a specific bin. true false Transactional Internal N/A
Cargo Package Inventory 14f4c6df-1936-ec11-835e-06750336c553 Inventory true Represents the inventory of Cargo Packages at a warehouse storage. Note that a warehouse storage is anything from the warehouse itself down to a specific bin. true false Transactional Internal N/A
Return Reason 1e661ccd-8c30-ec11-835e-0646afcad5a9 Inventory true Reasons for why goods were returned. The reasons can be used for when goods are returned from a buyer of goods or for when Maersk returns goods to a supplier. true false Master Internal N/A
Inventory 26a36eb4-7930-ec11-835e-0646afcad5a9 Inventory true How much stock of commodities, cargo packages or specific commodity items are currently held in the inventory of the at a particular date and time at a particular storage location (which can be part of or a warehouse, but does not have to be, i.e. it can be a maintenance and repair station for tracking internal goods movement). The inventory is subtyped into specific inventory types: Commodity Inventory, tracks stock of general products, their quantities, volume etc. Commodity Item Inventory, tracks stock of specific items, their quantities, volume etc. Cargo Package Inventory, tracks stock of specific cargo packages, their quantities, volume etc. true true Transactional Internal N/A
Inventory Reason 3c46c48f-0e36-ec11-835e-06750336c553 Inventory true Indicates the reason for the Inventory Transaction. Examples: Consumption: Maintenance and Repair Wastage: Spoiled, Damaged, Beyond expiration date Transfer: Normal DC Transfer, Store supply to support promo, Returns from Store to DC Audit: Normally scheduled stock count, exception count, Quality Control On Hold: Layaway sale, Reserved due to Customer Order, Picked (as part of fulfillment) Fulfilment: Available, Allocated, Shipped true false Reference Internal N/A
Inventory Transaction Line 449ee8b0-7f30-ec11-835e-0646afcad5a9 Inventory true Represents the transaction happening in a storage location (within a facility; warehouse, repari station or the like) where commodites are handled by Maersk for inbound-, outbound- or internal movement. The Package Quantity, Product Quantity, Product Item Quantity, Net Weight, Net Net Weight, Gross Weight, Volume will be used to represent these attributes in the context of the type of ITL - e.g. with a fulfillment Inventory Transaction Line (ITL) the attributes will represent quantity, weight and volume of what was fulfilled. Note on Inventory Transaction types: The ITL is typed via the Inventory Transaction (IT) so that it is possible to identify if the purpose is Fulfillment, Vendor Receipt, Return, Vendor Return etc. Fulfillment Is negative inventory adjustment made due to the allocation/fulfillment/sale of goods. ITL represents can represent actual Commodity Item, general Commodity or specific Cargo Package in the fulfillment. If more Commodity Items or Cargo Packages were fulfilled they will have one ITL each. Example: 10 Wooden Desk style H14 can be documented via Commodity (master data) and quantity volume etc. be sum of the number of the 10 desks fulfilled OR each of the 10 desks can be represented with an ITL each related to a Commodity representing each desk. Vendor Receipt Is positive inventory adjustment made due to the receipt of goods/commodities from a Supplier/Vendor. The ITL is information about a specific commodity item, general commodity or cargo package contained in a vendor receipt. Return Is positive inventory adjustment made due to the return of goods from a customer back to Maersk (possibly because Maersk is contracted for return handling). The ITL can specify the actual commodity item being returned or the quantity and details about the commodity via Commodity. The customer may be entitled to a refund or an exchange. If the commodity is being exchanged the boolean value for indicating this is set. Vendor Return Is negative inventory adjustment due to items returned to a vendor, when they are observed to be damages, malfunctioning, etc. The ITL can specify the actual commodity item being returned to the vendor or the quantity and details about the commodity via Commodity. true false Transactional Internal N/A
Commodity Item Inventory 7b2ecde9-1936-ec11-835e-06750336c553 Inventory true Represents the inventory of Commodity Items at a warehouse storage. Note that a warehouse storage is anything from the warehouse itself down to a specific bin. true false Transactional Internal N/A
Inventory Transaction Relation 92f30927-c85c-ee11-a1bb-fab3d952de1e Inventory true Used to for example relate a return transaction to an fulfillment transaction, e.g. if the returned product is being exchanged. Another example is a Request Inventory Transaction which should be linked to all outbound transactions that result from the request. true false Transactional Internal N/A
Inventory Transaction a5874325-7730-ec11-835e-0646afcad5a9 Inventory true Captures a number of inventory transaction lines that represents material moving in of, out of or internally within a facility storage (part of a Facility). It is possible to capture detailed inventory transaction for any type of facility storage; from the very high level on e.g. for a warehouse down to the individual bin. This is made possible by the facility storage being a super class of all other facility storage types. true true Transactional Internal N/A
Outbound Warehouse Shipment 0d31d0a6-f9e5-eb11-8336-06892ccaedcb Warehouse Shipment true Represents a shipment and the cargo that is to leave a storage location. Examples: Despatch, generic despatching of cargo from a location. Does not have to be initiated by a customers sales-, transfer- or vendor return order, but can be initiated by Maersk without customers involvement. Fulfilment, goods were sold, e.g. customer made a sales order, and goods must now leave the location to go to the buyer Transfer, goods are instructed to leave a location. A transfer scenario can be between locations or between storage locations inside a facility Vendor Return, an instruction that Maersk is returning goods they purchased, or on behalf of a customer, to a vendor and those must now leave the storage location true true Transactional Internal N/A
Pick 2c1e8a96-6b7f-ee11-a1be-d7e14702d112 Warehouse Shipment true Details about picking of the commodities that is shipped out from the warehouse. true false Transactional Internal N/A
Hold Reason 38886845-d557-ec11-836c-06c8d72459ad Warehouse Shipment true Reason codes for why a number of products are being held back at a e.g. a warehouse. true false Reference Internal N/A
Inbound Warehouse Shipment Line 51d028ec-c87c-ec11-836c-06359a670063 Warehouse Shipment true A specialisation of Warehouse Shipment Lines holding attributes that are specific to inbound commodities like received quantities. true false Transactional Internal N/A
Outbound Warehouse Shipment Line 5652971a-c97c-ec11-836c-06359a670063 Warehouse Shipment true A specialisation of Warehouse Shipment Lines holding attributes that are specific to outbound commodities like the shipped quantities, of a specific commodity. true false Transactional Internal N/A
Warehouse Shipment Line 566c7e25-d953-ec11-8368-065196153da5 Warehouse Shipment true The Warehouse Shipment Line (WSL) details in to commodities and/or cargo packages what is arriving, or what is to leave, a warehouse. Any need for load sequence and the WSL will have to be under a cargo stuffing line via the appropriate hierarchy level. true false Transactional Internal N/A
Warehouse Shipment Relation Reason 7dd93c37-d65c-ee11-a1bb-fab3d952de1e Warehouse Shipment true The purpose to why the Warehouse Shipments have been related. true false Reference Internal N/A
Putaway cfa942cc-6f7f-ee11-a1be-d7e14702d112 Warehouse Shipment true Details about putaway of the commodities that is shipped in to the warehouse. true false Transactional Internal N/A
Warehouse Shipment da058895-f9e5-eb11-8336-06892ccaedcb Warehouse Shipment true The Warehouse Shipment (WS) represents an advice to or from a storage location (which is always part of a Facility) that cargo is arriving inbound or departing outbound. There are many different scenarios to cover for WSs and it is broken in to two subclasses; inbound and outbound to more clearly denote their different usages. Note on internal transferring: When performing internal transferring of goods, products etc. between different storage locations or internally within a storage location, the Outbound Warehouse Shipment (OWS) and Inbound Warehouse Shipment (IWS) should be created such that removing commodities from an internal storage location is documented in an OWS and storing it in another storage location is documented with an IWS. Note on Cargo Stuffing: To document how cargo has been stuffed in to equipment or vehicle it is necessary to have the warehouse shipment relate cargo stuffings. However, to be able to support all business requirement and the many to many relationships that exist in complex scenarios the navigation will have to be: Warehouse Shipment -> Service Plan -> Service Plan Leg -> Transport Order -> Cargo Stuffing. Outbound, for loading Cargo has been stuffed according to the Cargo Stuffing (CS), equipment, vehicle, load sequences etc. are documented at CS level Inbound, for unloading Cargo inbound is arriving in containers, trailers, trucks and stuffed according to the cargo stuffing Note on legacy implementations: Process - Description - Legacy data object Inbound Instruction - client informs us goods are arriving - Advance Shipment Notice with Purchase Order (ASN and PO) Inbound Notification - we inform client about goods that has arrived - Goods Receipt Notice (GRN). The message when send to customer may be tagged with Goods Receipt Notice for example. Outbound Instruction - client informs us to ship goods - Shipping Order (SO) Outbound Notification - we inform client on goods that has been shipped - Container Load Result (CLR). The message when send to customer may be tagged with Goods Shipped Notice for example. Note on measurements for damaged cargo: Measurements for damaged cargo applies to both inbound- and outbound warehouse shipments. On inbound damage can be reported during inspection, on outbound Maersk could receive an Outbound Receipt Notification listing damaged measurements. true false Transactional Internal N/A
Inbound Warehouse Shipment da37ba9f-f9e5-eb11-8336-06892ccaedcb Warehouse Shipment true Represents a shipment for cargo that is to arrive at a storage location. The Inbound Warehouse Shipment (IWS) is used in several use case, see examples below. Examples: Receipt, generic receival or cargo (e.g. for deconsolidation or a customers purchase order) a container, trailer, truck is arriving at a location and need to be deconsolidated. If details are provided about equipment, vehicle and how goods were stuffed in to this the Cargo Stuffing (CS) can be used to document these details. Return, instruction that goods are being, or must be, returned from a customer and Maersk may be handling the return. If Maersk is arranging for the transport of the return goods, this can be documented fully via the Service Plan (SP) including transport details. If Maersk is not arranging the transportation and all that is known are some goods/commidity details the Outbound Warehouse Shipment Lines will detail these. Vendor Receipt, instruction that goods procured by Maersk is being brought in to a Maersk facility by some 3rd party carrier. For example spare parts for cranes at a terminal. Transfer, (aka. movement) goods coming to a location in a transfer scenario; can be between locations in different facilities or between storage locations in a facility. If there is a need to know the details about the transportation SP can be used. true true Transactional Internal N/A
Sort Type e6ad5d17-78d2-ec11-a199-b8589406e3e5 Warehouse Shipment true Code and name for different ways of sorting cargo when being received. E.g. sort by destination. true false Reference Internal N/A
Warehouse Shipment Relation f65bae1a-d65c-ee11-a1bb-fab3d952de1e Warehouse Shipment true Allows warehouse shipments to be related together e.g. for inbound containers that are being de-consolidated and multiple warehouse shipments exists for the outbound handling and shipping of these. Even internal transferring of goods, products etc. should be created as outbound and inbound shipments such that taking something out from an internal storage location is in an outbound instruction and putting it in to another storage location is an inbound instruction. true false Transactional Internal N/A
Barcode 434e5b1d-be56-ea11-ad9d-40b034e2c22b Label and Scanning true A specific type of scannable identifier which looks like a series of vertical lines in different widths. It is used by barcode scanners to read the barcode as a number so that the item having the barcode can be identified. true true Transactional Internal N/A
Radio Frequency Identification Tag 494e5b1d-be56-ea11-ad9d-40b034e2c22b Label and Scanning true Typically an RFID tag carries no more than 2 kilobytes (KB) of data-enough to store some basic information about the item it is on. Simple "license plate" tags contain only a 96-bit or 128-bit serial number. Uniqueness RFID can give an "electronic ID card" to every item in the Internet of Things. Each RFID electronic tag has a globally unique number (the label cannot be copied), which can realize anti-counterfeiting, traceability and anti-smuggling of the product. true true Transactional Internal N/A
Scannable Identifier 4eca8702-be56-ea11-ad9d-40b034e2c22b Label and Scanning true A tag, barcode or other type to scan an item to identify it containing the indentifying number. In warehousing cargo packages, e.g. pallets, physical container, carton, will sometimes have a license plate number which is scannable. In such case it can be kept here. Examples: - Barcode - RFID true false Reference Internal N/A
Label 731d5009-244e-ea11-ad9c-40b034e2c22b Label and Scanning true Printed or burned on to e.g. Cargo Packages. true true Reference Internal N/A
Scan Event 85457883-3f58-ea11-ad9e-40b034e2c22b Label and Scanning true To capture events whenever a Scannable Identifier is scanned. It could when a product item passes through an RFID tunnel at a warehouse or distribution center. Or when a carton barcode box is scanned upon warehouse receival. Examples: - When cargo leaves the factory the they will submit scanned file to Maersk via EDI (normally through a 3rd party platform assigned by customer like GTNEXUS or TradeLinkOne) - When cargo arrives at our CFS warehouse - we call it inbound scanning - When cargo is stuffed into container at our CFS warehouse - we call it outbound scanning true true Transactional Internal N/A
Scan Validation Type abd5a314-5e58-ea11-ad9e-40b034e2c22b Label and Scanning true Scan validation types. Examples: Factory versus Inbound Inbound versus Outbound Factory versus Outbound true false Reference Internal N/A
Scan Validation bf64f498-5d58-ea11-ad9e-40b034e2c22b Label and Scanning true Stores if scan events validates against eachother. E.g. if factory scan matches inbound scan matches outbound scan. true false Transactional Internal N/A
Barcode Type eb5d319d-fb16-ea11-ad8b-40b034e2c22b Label and Scanning true Type of barcode. General examples include: - UPC - EPC - EAN - JAN - GTIN - ASIN - ISBN - QR - GS1-128 - IFT-14 - GS1-DataBar - GS1-DataMatrix - GS1-QRCode - GS1-CompositeBarcode - EPC HF Gen 1 - EPC UHF Gen 2 Older product code types include Kimball Number which are still submitted to Maersk from certain customers to track their products, e.g. Primark. Examples: "UPC", "Universal Product Code" "EPC", "Electronic Product Code" "EAN", "European Article Number" true false Reference Internal N/A
Appointment Relation 23c4821e-e74d-ee11-a1ba-9a42c5ca5684 Appointment true Allows an appointment to be related to other appointments for a specific purpose. true false Transactional Internal N/A
Security Code 4292ffaf-d79d-eb11-a3cb-a0510b9e9705 Appointment true A code used for authentication when picking up or dropping off cargo, for example picking up a container from a port. The security code is given to the carrier who is picking up the cargo so that they can use the code to either enter the facility or authenticate at security gate via security personel. true false Transactional Internal N/A
Appointment Relationship Purpose 906d28f1-1edb-ec11-a19a-cfb0be0d6083 Appointment true Purpose or reasons why an appointment is related to other appointments. It could for example be for grouping appointments together for a specific business purpose. Another example could be for an appointment for dropping off cargo and picking some up at the same place. For this two appointments should be created and related. true false Transactional Internal N/A
Appointment c4a5f973-1757-ec11-836c-06971f1d0419 Appointment true Represents a single appointment. The appointment can be for a land based vehicle (truck and/or trailer) at a storage location or even used to schedule specific items being stored at/picked from a specific location. An appointment can be for a first, second, customer expected option etc. and be requested by the business partner for certain time slots. Once the appointment is scheduled the state changes and scheduled attributes are used to signify the exact scheduled times and duration. If an appointment is for a truck dropping off some cargo but also picking some up at the same time, two appointment entries should be made and they can be related via the recursive relationship. true true Transactional Internal N/A
Pick Put Profile 3d88d5a8-2eae-ec11-8382-0677cd8be49d Warehouse Operations true A profile with rules about how to pick and put-away a commodity or commodity unit in a warehouse. A set of pick put rules are used to determine optimal picking and put-away locations for a commodity or commodity unit. true false Master Internal N/A
Load Profile 3f45d30f-40ae-ec11-8382-0677cd8be49d Warehouse Operations true Specifies how an object is allowed to be loaded. Used for for example for Commodity Measurement to specify how it is allowed to be loaded inside a Cargo Package. It can also be used at Cargo Package Specification level to tell how a cargo package is allowed to be loaded inside other cargo packages. true false Master Internal N/A
Handling Profile b54ed543-58ae-ec11-8382-0677cd8be49d Warehouse Operations true Information about how to handle a commodity or package containing commodites inside a warehouse. For example how many can be grabbed at one time, whether it is conveyable etc. true false Master Internal N/A
Cross Dock Profile c7b98aae-30ae-ec11-8382-0677cd8be49d Warehouse Operations true Descriptive rules about how a commodity is to be handled when doing cross docking that involves the commodity. Cross dock profile is about the rules how the cargo crosses the dock. In this process, cargo will be directly transfered to the outbound dock from inbound dock without doing putaway. true false Master Internal N/A
Value Added Service Profile d4b7520a-cc71-ec11-836c-06ff3fef2475 Warehouse Operations true A profile for Value Added Services (VAS) is specific for certain customer, and this profile code could indicate a complex set of VAS (i.e, packing, labeling, etc.). In a typical warehouse managment system each customer has one profile controlling the VAS setup. Each customer will have different requirements for a same VAS and the relationships between a profile and the VAS are always same (like VAS operation sequence, etc.) true false Master Internal N/A
Putaway Class f35188e3-e5af-ec11-8382-0624820b6803 Warehouse Operations true Stores commodity put-away classes within the warehouse. Each class may have an associated overflow class for situations when the class is unavailable. true false Master Internal N/A
Forwarders Cargo Receipt Document 03912be3-493c-ea11-94fa-d4d25239b33f Forwarders Cargo Receipt true Documents that are required and received in relation to the Forwarders Cargo Receipt. Tracking if documents required have been received must be derived from the required versus the received quantity. true false Transactional Internal Competitive Strategic Information
Forwarders Cargo Receipt 3d370e07-ed11-ea11-80ed-9cd21e38f3a4 Forwarders Cargo Receipt true The Forwarders Cargo Receipt (FCR) is a document stating that the cargo has been duly received by a Forwarder, or equivalent Logistics Operator. The FCR is issued to the Shipper. The Shipper can then use the FCR as proof of cargo handover in order to receive a payment (for instance, based on a Letter of Credit, in an bank agreed with Buyer/ Consignee). Status indications: The timestamps associated with the status of the business object is considered a physical implementation. Examples of these include "BookedTimestamp", "CancelledTimestamp" and "ConfirmedTimestamp". Units: In case of mixed package units at line level the header level will use 'Package' as unit. true true Transactional Internal Competitive Strategic Information
Forwarders Cargo Receipt Line 71229fcd-0522-ea11-ad90-40b034e2c22b Forwarders Cargo Receipt true The Forwarders Cargo Receipt Line (FCRL) details the amount of cargo indicated on the Shipper Booking Line (SBKL) relevant for issuing the FCR. The FCRL construct allows mixing SBKLs from various SBKs, i.e. the FCRLs need not all originate from the same SBK. true false Transactional Internal Competitive Strategic Information
Dock Receipt c7c5e9ec-d26b-ee11-a1bd-fc682fdb7b46 Forwarders Cargo Receipt true Dock receipt. true false Transactional Internal N/A
Export License e8f509f7-d26b-ee11-a1bd-fc682fdb7b46 Forwarders Cargo Receipt true Refers to a permit required to engage in the export of certain commodities to certain destinations. Lists of such goods are found in the comprehensive Export Schedules issued by the Bureau of Foreign Commerce. An export license is a document issued by the appropriate licensing agency after which an exporter is allowed to transport his product in a foreign market. The license is only issued after a careful review of the facts surrounding the given export transaction. Note: The export license numbers on this level must conform with the ones on associated Shipper Bookings, i.e. one must expect that the export license numbers are derived from the associated Shipper Bookings if they are needed here. true false Transactional Internal N/A
Cargo Package Allocation 3236e1b8-f7c7-ea11-adbb-40b034e2c22b Customer Order true Is the entry point to the reusable cargo package structure which allows a Cargo Package Specification (CPS) to be used for multiple Customer Order Lines (COL) when necessary. In a complete drill down from above mentioned data entities it will be possible to derive the actual cargo packages that are relevant in their instantiated context. For example a booking may book transportation for customer products that should be packed only in a number of the cargo packages specificed via the CPS. In turn only a number of those actual cargo packages ends up being stuffed in to a piece of equipment on the Equipment Stuffing (EQS). Covered Scenarios from Customer Order: Single Pack: All products of the same SKU are packed according to a shared CPS. In this scenario COLs for the same SKUs can use the same CPS. Pre-pack/Mixed Cargo Package: In this scenario a CPS is used to mix together multiple SKUs or SKU/Style combinations from different products according to quantities. In this scenario the COL's mix quantity will be defined on the CPA in 'Product Quantity Allocation'. Mixed Lines: This is when 1 COL is split in multiple CPSs (example: 50% of COL #1 goes in CPS #A, and 50% of COL #1 goes in CPS #B - this is the case, for instance, of our customer Puma). Mixed Cargo Package and Mixed Lines: When multiple COLs are split in multiple CPSs (example: 50% of COL #1 goes in CPS #A, 50% of COL #1 and 20% of COL #2 go in CPS #B, and 80% of COL #2 and 100% of COL #3 go in CPS #C - again the case for customers like Puma). true false Transactional Internal Competitive Strategic Information
Customer Order Line Transfer 67370e07-ed11-ea11-80ed-9cd21e38f3a4 Customer Order true Relates two Customer Order Lines (COL) together in a transfer scenario. The concept of transferring a COL, or a collection of COLs, to another manufacturer is used in triangular trade. Maersk's systems need to support triangular trade so that the vendors working for a Maersk customers can assign orders to manufacturers that they sub-contract the manufacturing to. The relationships between the COL and the Customer Order Line Transfer is created so that a "chain" or graph of COLs are possible to create. The current limitation on consecutive COL transfers is set to 7 in Maersk Shipper to avoid unlimited transfers. A source COL can be transferred to multiple target lines, e.g. a part of the quantities transferred to factory A while another portion of the quantiies are transferred to factory B. true false Transactional Internal N/A
Customer Order 6e370e07-ed11-ea11-80ed-9cd21e38f3a4 Customer Order true The customer order (CO) is a commercial document and first official offer issued by a buyer to a seller indicating types, quantities, and agreed prices for products or services. It is used to control the purchasing of products and services from external suppliers. Different types of customer orders can exist, e.g. Purchase Order, Sales Order, Production Order etc. Examples: Factory Purchase Order:The Purchase Order issued by the importer on an overseas Vendor. A factory purchase order can be issued 1:1 against an internal customer purchase order or can be a bulk order aggregating volume to satisfy a number of customer purchase orders. This wil be represented by a 'Customer Order' of type 'Purchase Order' having the designated vendor as a party. Customer Purchase Order:This is the order from either the store, 3rd party customer (in the case of a lifestyle brand or wholesaler). This would be represented by having a 'Customer Order' of type 'Purchase Order' having the store or 3rd party customer together with the internal customer as parties on the CO. true true Transactional Internal N/A
Customer Order Line 71370e07-ed11-ea11-80ed-9cd21e38f3a4 Customer Order true Describes order specifics like quantities, volume, pricing etc. of a certain product that a Maersk customer is purchasing from their vendor. To find out how much of the products has actually been booked for transportation the Shipper Bookings need to be queried. To find out how much of the products has actually been delivered for the transportation the Shipper Booking or Cargo Stuffings need to be queried. true false Transactional Internal N/A
Customer Order Relation c38a30b6-c86b-ee11-a1bd-fc682fdb7b46 Customer Order true Allows a customer order to be related to other customer orders for a specific reason. true false Transactional Internal N/A
Customer Order Relation Reason ef4d165a-c96b-ee11-a1bd-fc682fdb7b46 Customer Order true Describes the type of relationship between two customer orders. For example to relate back to a previous version. true false Reference Internal N/A
Shipper Booking 80370e07-ed11-ea11-80ed-9cd21e38f3a4 Shipper Booking true The Shipper Booking (SBK) is a contract of carriage, evidencing the agreement to transport goods, used in the Lead Logistics and Contract Logistics area (i.e. supply chain management, 4PL, warehousing, etc.). Notes: The SBK is also known as Vendor Booking or Shipping Order (SO). Status indications: The timestamps associated with the status of the business object is considered a physical implementation. Examples of these include "BookedTimestamp", "CancelledTimestamp" and "ConfirmedTimestamp". Units: In case of mixed package units at line level the header level will use 'Package' as unit. true true Transactional Internal Competitive Strategic Information
Shipper Booking Line 82370e07-ed11-ea11-80ed-9cd21e38f3a4 Shipper Booking true A Shipper Booking Line (SBKL) represents transport booking for one or more Customer Products (CP), which have been ordered by consigenee on Customer Order Line (COL). Blank Booking In case the shipper does not have a CO and COLs to base the SBK and SBKLs on, they can enter the data so that this is materialized in to the CO, COL, CP structrues. This avoids having to replicate all the CO and COL fields to the SBK and SBKL levels respectively. The COL in such case is a placeholder with very little information but the structure of Customer Product should be re-used. Note on existing systems: This is equivalent to SOSP in MODS true false Transactional Internal Competitive Strategic Information
Packing List Line 87370e07-ed11-ea11-80ed-9cd21e38f3a4 Packing List true A Packing List Line (PLL) which details the packaging of commodities/products. A PLL can be created based on the following scenarios: - From a Shipper Booking (SBK) where one or more of the SBK Lines (SBKL) are related to the PLLs. - From a Customer Order (CO) where one or more of the CO Lines (COL) are related to the PLLs - From external PL data where there is no relationship to SBK or CO. true false Transactional Internal Competitive Strategic Information
Packing List 88370e07-ed11-ea11-80ed-9cd21e38f3a4 Packing List true The packing list is a detailed list of packed cargo items, typically prepared by the shipper. Status indications: The timestamps associated with the status of the business object is considered a physical implementation. Examples of these include "BookedTimestamp", "CancelledTimestamp" and "ConfirmedTimestamp". true true Transactional Internal Competitive Strategic Information
Production Plan 043c46e4-b77c-ec11-836c-06359a670063 Manufacturer Production Plan true A number of planned production events. true true Transactional Internal N/A
Production Event 7b303f9b-421a-ea11-ad8c-40b034e2c22b Manufacturer Production Plan true Combinations of steps and date types with their date time. Examples: "Production Start", "Earliest" "Production End", "Latest" true true Transactional Internal Competitive Strategic Information
Hull 2e311470-cc65-ee11-8153-c403a888648f Vessel Specification true The main body of a ship or vessel. It includes various aspects related to the design, structure, and characteristics of a ship's body, inclkuding the Draft and paint type true false Master Internal N/A
Hull Class 61fe50a0-c116-ed11-a19f-cacbfc25e2af Vessel Specification true Classifies the vessel by its hull. Examples of hull classes are: Guanzhou 314 (G Wenchong 1700 - Kalliroe) Hangzhou 2005-04 (TC 710 - Viola) Imbari 2133 (Imbari Millenium) true false Reference Internal N/A
Vessel Specification 76c33001-3d68-ee11-8155-c403a888648f Vessel Specification true The detailed description of a ship or vessel's characteristics and capabilities. This includes information such as the breadth or width of the vessel at its widest point, measured at the nominal waterline. It also includes information related to the Hull, including Propeller details true false Master Internal N/A
Waste Heat Recovery System 0a095ba0-34b7-ec11-abb1-5c879c3c5a54 Vessel Machinery true Details about the Waste Heat Recovery Systems (WHRS) installed on the vessel true false Master Internal N/A
Main Engine 0ed21ab9-fc66-eb11-a69b-b88a608bad70 Vessel Machinery true Details related to the Main Engines installed on the vessel. The Main engines are used for propulsion true false Master Internal N/A
Bonjean Curve 26560381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Machinery true Curves of areas of transverse sections and their moments about the base line of a ship used in making calculations (as to determine the force of buoyancy during launching) true false Master Internal N/A
Thruster 62a72579-34b7-ec11-abb1-5c879c3c5a54 Vessel Machinery true Thrusters are engines used to manover the vessel at low spreeds true false Master Internal N/A
Auxiliary Engine 87fa2731-fd66-eb11-a69b-b88a608bad70 Vessel Machinery true Details about the Auxiliary engines installed on the vessel. The Auxiliary engine(s) provide energy for functions other than propulsion true false Master Internal N/A
Hydrostatic Curve 95520381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Machinery true The variations of ship hydrostatic data with draught are shown by a set of curves. Extremely useful in the assessment of end draughts and the stability of a ship in various conditions of loading. true false Master Internal N/A
Shaft Generator 96ccf57f-34b7-ec11-abb1-5c879c3c5a54 Vessel Machinery true Details on the Shaft Generators installed on the Vessel true false Master Internal N/A
Vessel Machinery a306a79d-72cf-ec11-abb4-5c879c3c5a54 Vessel Machinery true Vessel Characteristics brings together all the discreet characteristics relevant for the vessel true false Master Internal N/A
Vessel Engine b5520381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Machinery true Stores the data about the engines that are installed on a vessel. true true Master Internal N/A
Boiler de96b76a-34b7-ec11-abb1-5c879c3c5a54 Vessel Machinery true Details on the Boilers installed on the vessel true false Master Internal N/A
Tank Type e8520381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Machinery true Fresh water, ballast, fuel etc. true false Master Internal N/A
Tank ec520381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Machinery true A tank onbaord the vessel, e.g. for fuel, fresh water, ballast water, waste water etc. true false Master Internal N/A
Bulkhead f7520381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Machinery true A bulkhead is an upright wall within the hull of a ship. true false Master Internal N/A
Draft Type 20e030e3-c25b-ef11-8190-db4390e09088 Fuel Consumption true The draft type for the specific fuel consumption examples : departure even keel, departure aft keel true false Reference Internal N/A
Vessel Fuel Consumption 3ce2eb1b-ae08-ee11-a1b3-b17a5c988744 Fuel Consumption true A Vessel Fuel Consumption data point based on given parameters. E.g. the vessel going at a certain velocity at a specific draft. true true Transactional Internal N/A
Fuel Consumption de3153ef-887f-ee11-a1be-d7e14702d112 Fuel Consumption true Fuel consumption data point based on certain parameters as example vehicles consumption given like 3 miles per gallon, or it can be multiple entries that states in more detail specific fuel consumptions under specific circumstances. true true Transactional Internal N/A
Lubricating Oil Type 37520381-b4fc-e911-80eb-9cd21e38f3a4 Fuel true A thick fatty oil used to lubricate machinery E.g. 'Diesel Engine Lubricant' code '15W-40 ' true false Reference Internal N/A
ISO Fuel 3b520381-b4fc-e911-80eb-9cd21e38f3a4 Fuel true ISO fuel definitions from ISO 8217 Fuel Standard, Fourth Edition 2010 For marine distillate fuels and for marine residual fuels. In the maritime industry the following type of classification is used for marine fuel oils: MGO (Marine gas oil)Roughly equivalent to No. 2 fuel oil, made from distillate only MDO (Marine diesel oil)A blend of heavy gasoil that may contain very small amounts of black refinery feed stocks, but has a low viscosity up to 12 cSt/400 C so it need not be heated for use in internal combustion engines IFO (Intermediate fuel oil)A blend of gasoil and heavy fuel oil, with less gasoil than marine diesel oil MFO (Marine fuel oil)Same as HFO (just another naming) HFO (Heavy fuel oil)Pure or nearly pure residual oil, roughly equivalent to No. 6 fuel oil Distalate Fuels: DMX, DMA, DMZ and DMB Marine Residual Fuels: RMA10, RMB30, RMD80, RME80, RMG180, RMG380, RMG500, RMG700, RMK380, RMK500 and RMK700 true true Reference Public N/A
ISO Fuel Characteristic 4a520381-b4fc-e911-80eb-9cd21e38f3a4 Fuel true Each ISO fuel has a number of characteristics (aka. requirements) associated with it, e.g. 'Micro Carbon Residue' which is specified at either max or min values and a unit of measurement like '% m/m'. Other examples include viscosity at 50 degrees celsius, density at 15 degrees celsius etc. true false Reference Public N/A
Fuel Type ab28ee79-27f3-eb11-8336-0697801388e1 Fuel true Different types of fuel, e.g. Diesel, Gasoline, Biofuel, Methanol etc. true false Reference Internal N/A
Vessel Stowage Slot 06530381-b4fc-e911-80eb-9cd21e38f3a4 Vessel true A container slot on a vessel; it is uniquely identified by the bay, row and tier number assigned to it. true true Master Internal N/A
Stowage Layout 24b912cd-0c75-eb11-a6a0-b88a608bad70 Vessel true Holds the details of the Minimum and Maximum Slots based on the Bays, Rows and Tiers true false Master Internal N/A
Vessel Retrofit 5a9cdae7-bec7-ec11-abb2-5c879c3c5a54 Vessel true Details of the vessel Retrofit, including dates and what retrofit work was completed true false Master Internal N/A
Vessel 68520381-b4fc-e911-80eb-9cd21e38f3a4 Vessel true A seagoing self-propelled structure designed for the transport of cargo and/or passengers. true true Master Internal N/A
Ice Class 8c86a8ad-35c2-ec11-abb1-5c879c3c5a54 Vessel true Ice Class of the vessel (strengthened of the hull to enabling the vsl to navigate through sea ice). Ice class refers to a notation assigned by a classification society or a national authority to denote the additional level of strengthening as well as other arrangements that enable a ship to navigate through sea ice. Some ice classes also have requirements for the ice-going performance of the vessel. true false Reference Internal N/A
Vessel Offering Type 8d520381-b4fc-e911-80eb-9cd21e38f3a4 Vessel true Reference data listing all of the types of Vessel Offering that can exist, particularly for example "mobile onboard crane-moving" true false Reference Internal N/A
Vessel Communication 9122d3df-b765-ee11-8153-c403a888648f Vessel true A vessel may e.g. be contacted via satelite phone (SAT C) or via call sign. Merchant and naval vessels are assigned call signs by their national licensing authorities. In the case of states such as Liberia or Panama, which are flags of convenience for ship registration, call signs for larger vessels consist of the national prefix plus three letters (for example, 3LXY, and sometimes followed by a number, i.e. 3LXY2). true false Master Internal N/A
SAT C 9e67f22c-b56a-eb11-a69d-b88a608bad70 Vessel true Details about the make and model of the Communication devices available on the Vessel true false Master Internal N/A
Vessel Offering cf520381-b4fc-e911-80eb-9cd21e38f3a4 Vessel true A vessel offering is any kind of tangible or intangible service/offering/utility particular to a specified Vessel. Particularly includes services such as crane-lifting, spreader utilisation and internet access - any offering which can be delivered onboard a vessel. true false Master Internal N/A
Truck 7b540381-b4fc-e911-80eb-9cd21e38f3a4 Vehicle true Land-based road vehicle designed for the transport of cargo. Can either contain cargo in itself or be a type of truck that attaches a trailer and moves cargo in the trailer. true true Master Public N/A
Train 81540381-b4fc-e911-80eb-9cd21e38f3a4 Vehicle true A series of connected railway carriages or wagons moved by a locomotive or by integral motors. true true Master Public N/A
Aircraft 84eb26ae-f689-ea11-adaa-40b034e2c22b Vehicle true A vehicle (such as an airplane or helicopter) for traveling through the air, designed for the transport of cargo and/or passengers. true true Master Public N/A
Vehicle Type 87540381-b4fc-e911-80eb-9cd21e38f3a4 Vehicle true Types and sub-types of vehicles. The Vehicle Type can be subtyped in to for example Aircraft Types that has records the capabilities of typical aircraft types such as cargo volume and payload weight.. Examples of super types: - Train - Truck - Barge - Vessel - Trailer - Aircraft Examples of sub-types: Aircraft- Airbus A300-600F- Antonov An-225- Boeing 737-700C- Douglas DC-10-30 Trailer - Tautliner - Tiltliner - Jumbo - Frigo true false Reference Public N/A
Trailer 8c540381-b4fc-e911-80eb-9cd21e38f3a4 Vehicle true A non-automotive vehicle drawn by truck, used especially in hauling freight by road. Examples: - Dry trailers - Refrigerated trailers - Flatbed trailers These typically comes with alumimium or tarpaulin sides, the latter being able to remove the side completely for side loading. Note on chassis: Trailer does not include chassis for shipping containers. Those are modelled specifically as equipment and has equipment profile. true true Master Public N/A
Vehicle 90540381-b4fc-e911-80eb-9cd21e38f3a4 Vehicle true A specific transportation device designed for moving cargo and/or people. Examples: - Named vessel - Particular truck with a registration number - Specific barge - Specific trailer with license plate true true Master Internal N/A
Vessel Trim Class 1c560381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Classification true Groupings of Maersk vessels with the same or similar characteristics of design whose names begin with the same first letter. Albatros, Anocrane, A-type, B-183, C1, C2, C3, CV 1100 etc. true false Reference Internal N/A
Vessel Size Class 2d560381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Classification true Suezmax, Panamax, New Panamax, Capesize, ULCC, VLCC, Chinamax, Q-max, Seawaymax, Aframax, Wafmax, Malaccamax, Handyzize Bulker, Minibulker. true false Reference Internal N/A
Vessel Capacity Class 36560381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Classification true Grouping of vessels into same (or near-same) capacity - this implies groupings of similar length, beam, displacement, slot-capacity and reefer-plug count. A capacity class consist of one or more fuel classes, this is to calculate the bunker propulsion of a capacity class (for the cost calculation) Examples include: PanaMax, Post-PanaMax, Suez-Max Ultra Large Container Ships (ULCS), Post Suez-Max, MalaccaMax, Post-Malacca-Max, ULCC (Ultra Large Crude Carriers), VLCC (Very Large Crude Carriers), AfraMax, HandySize Bulker, MiniBulker, HandyMax Bulker, CapeSize. true true Master Internal N/A
Vessel Fuel Class 43560381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Classification true Subdivision of vessel capacity classes into subgroups having the same bunker consumption curves. Classes of vessels having similiar bunker consumption curves, this classification is based on the vessel normally having same engine and hull dimensions. E.g. of fuel classes are 'Odense 6500', 'Odense 15000', 'Odense 8300' or 'Samsung 9000' true false Reference Internal N/A
Vessel Classification Society bf520381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Classification true The name, description and code for the external classification scheme depending on the classification society. E.g. for Lloyds classification it could be A1 with a description and/or spelled out name for that classification. A classification society specifies several diferent schemes that will classify a vessel. ABS for example will typically classify a container vessel as: A1, E, CPS, AMS, ACCU, SH, SHCM and UWILD. Note: that these classification schemes could apply not only to container vessels. Examples A1 - Hull has been built under ABS survey for unrestricted ocean service E - Ship complies with the ABS requirements for anchoring and mooring equipment CPS - Coatings applied to the dedicated seawater ballast tanks meet the requirements of the IMO Performance Standard for Protective Coatings AMS - Ships machinery, boilers and systems have been constructed and installed in accordance with the requirements of the ABS Rules ACCU - Ship has the means to control and monitor an unmanned propulsion machinery space in an approved manner from the navigation bridge and from a centralized control and monitoring station installed in, or adjacent to the propulsion machinery space SH - Hull has been evaluated using ABS Eagle SafeHull SHCM - Ship was subject to enhanced inspection during construction in conformance with the SafeHull Construction Monitoring procedure UWILD - Ship meets the ABS requirements for underwater inspection in lieu of drydocking true false Master Internal N/A
Vessel Financial Capacity Class db520381-b4fc-e911-80eb-9cd21e38f3a4 Vessel Classification true A Financial Grouping of vessels by Capacity, to compare vessel revenue of similiar vessels. Examples include but may not be forever limited to: Minimum TEU Maximum TEU 1 2000 2001 5000 5001 10000 true false Reference Internal N/A
Vessel Classification e2a1b8e6-2f68-ee11-8155-c403a888648f Vessel Classification true The classification of vessels based on various characteristics and specifications. This classification includes several aspects such as: Capacity Class: Grouping of vessels into same (or near-same) capacity - this implies groupings of similar length, beam, displacement, slot-capacity and reefer-plug count. Financial Capacity Class: This classification is not explicitly defined in the context provided. Fuel Class: Subdivision of vessel capacity classes into subgroups having the same bunker consumption curves. Size Class: Classification based on size categories like Suezmax, Panamax, New Panamax, Capesize, ULCC, VLCC, Chinamax etc. Trim Class: Groupings of Maersk vessels with the same or similar characteristics of design whose names begin with the same first letter. Vessel Classification Societies: A classification society is a non-governmental organization that establishes and maintains technical standards for the construction and operation of ships and offshore structures. true true Master Internal N/A
Packages: 176
Classes: 797
Attributes: 3695
Enumerations: 242
Literals: 954
Relationships: 2747
 Includes all classes, attributes, enumerations, literals and relationships in the model.
Total elements: 8435
View raw data of the model in tables.