The Vessel Insight Asset Model is essential for accessing the timeseries and states data. It offers a mapping between sensors from the data sources and standardized paths.
Asset Model
Data for a vessel is organized according to a standardized tree structure, which is a Kongsberg Digital standard. This tree structure is a breakdown of vessel subsystems, and it includes a comprehensive model that accommodates various vessel types and sizes. It can be viewed in different ways to suit users from different maritime segments. Each vessel model is a subset of the global model based on its onboard system topology. This provides a unified way to address data across vessels and fleets when referencing data in the API.
Sensors onboard vessels are mapped into this model. Some paths may not be mapped due to e.g. that there is no corresponding sensor available.
Example model from a vessel with a diesel engine propulsion system:
The below figure shows the conceptional relationship between data sources and the asset model in a fleet perspective.
Concepts
Some asset model concepts:
- Nodes: Each element in the asset model.
- Edges: Child node of a node.
- Node Types: Nodes can be of various types, such as "Ship", "<System>", "<Subsystem>+n", timeseries or states.
- Asset Path: The complete path from the fleet to the data. Also referred to as "Path" or "Node Path".
- Views: Different ways to present the tree structure. Currently we offer:
- V1 (merchant style)
- V2 (LNG/Offshore-style)
- Extending: Kongsberg Digital extends the structure with new elements as demand arises.
Paths
Paths are exposed as strings in API's and are constructed the following way :
- The node path starts with:
/Fleet/imo<IMOnumber> - Continues with:
/<system>/<subsystem>/ - Ends with a leaf node:
/<timeseries or state>
Examples:
/Fleet/imoXXX/Bridge/Hull/Trim
/Fleet/imoXXX/Engines/Main/1/FO_Flow
/Fleet/imoXXX/Bridge/Navigation/Longitude
/Fleet/imoXXX/Bridge/Navigation/Latitude
/Fleet/imoXXX/Engines/Main/1/Engine_Power
/Fleet/imoXXX/Bridge/Navigation/SOG
/Fleet/imoXXX/Bridge/Navigation/STW
/Fleet/imoXXX/Engines/Main/1/Shaft_Torque
Key points about paths:
- Mapping: Sensors from vessels are bound to paths if they are mapped
- Uniqueness: Node paths are globally unique, and can identify data from vessels
- Immutability: Paths are immutable, meaning they typically do not change.
- Backward Compatibility: Paths remain backward compatible when updates to the vessel model are applied.
AssetModel endpoint
The assets for a vessel can be retrieved from the API using the AssetModel endpoint.
A guide to navigating the asset model can be found in Get asset model data.
