Core concepts

The Veracity Asset Model allows you to view or edit the system that has been instantiated, as well as the taxonomy used. The same functionality is available...

The Veracity Asset Model allows you to view or edit the system that has been instantiated, as well as the taxonomy used. The same functionality is available using APIs.

https://assetmodel.veracity.com


Core concepts

The Veracity Asset Model is a platform capability that provides a unified Asset Registry, enabling multiple services to store, manage, and access metadata for assets such as solar plants, wind farms, vessels, and more. Its purpose is to ensure consistent and standardized representation of assets across services and technologies. By offering a common naming standard for describing assets, it facilitates seamless data exchange between services (e.g., analytics, monitoring, reporting) and reduces duplication and misalignment.

When modelling assets such as solar plants and wind farms, predefined system types (entities) are used. These system types are defined according to the ontology for the given domain. Veracity Ontology allows administrators to define the concepts for the domain, the properties and signals associated with them as well as the relationships between these concepts.

Terminology

Terminology Description
Ontology The shared vocabulary and rules that give data meaning: the types of things (concepts), their properties, how they relate to one another, and the rules that apply to them. Ontology is described in abstract terms and without reference to any particular syntax. It says what things are, not which things exist; for example, that a vessel has engines and that fuel consumption is measured in tonnes. More than a schema (structure only) or a taxonomy (hierarchy only). Reference: W3C OWL 2.
RDF (Resource Description Framework) The W3C standard data model for describing things on the web as statements of three parts, called triples: subject – predicate – object, for example Vessel A – hasEngine – Engine 1. Each thing and each relation is named by a URI (IRI), so statements from different sources can be merged into one graph. RDF is a format and data model, not a database; it can be written as Turtle, JSON-LD or RDF/XML. Reference: W3C RDF 1.1 Concepts.
RDFS (RDF Schema) A small vocabulary on top of RDF for describing the types in the data: classes (rdfs:Class), sub-classes (rdfs:subClassOf), properties and sub-properties, and which class a property applies to (rdfs:domain) and points to (rdfs:range). It gives a basic ontology, such as "a main engine is a kind of engine". Reference: W3C RDF Schema 1.1.
OWL (Web Ontology Language) OWL extends RDF/RDFS mainly by adding richer ways to describe classes, properties, relationships, constraints, and logical rules. It adds richer semantics such as cardinality ("a vessel has at least one engine"), class equivalence, disjoint classes ("an engine is not a hull"), property characteristics, inverse properties (hasEngine / isEngineOf) and classes defined by conditions. A reasoner can use these rules to infer facts that were not stated and check that data is consistent. It assumes an open world: a missing fact is unknown, not false. OWL cannot show that a fact is absent. SHACL checks for completeness. Reference: W3C OWL 2 Overview.
Business rules Statements set by the business, a regulation or a contract about what must, may or must not happen, and how values are calculated. Three common kinds: constraints ("a voyage report names exactly one vessel"), calculations ("FuelEU GHG intensity is calculated per reporting period from the fuel used") and permissions and approvals ("only the technical manager may approve an engine change"). The decision gate applies the permission rules and the approval rules. Constraints are SHACL shapes. Calculations are measure files, and kg-tools runs them. Permissions are in the action registry. Data can break a business rule, so it is checked and breaches are reported. Business rules are written with the terms of the ontology, so one rule applies to every asset of a type.
Taxonomy A taxonomy is a way of classifying and organizing items into categories. It is commonly used in data catalogs, ontologies, and metadata systems.
IEC 81346 RDS A Reference Designation System (RDS) is a formal engineering method for identifying and structuring technical systems, components, and functions. It originates from industrial standards such as IEC/ISO 81346, widely used in energy sectors—including wind turbines and solar plants.

System types

A system type represents any concept in the ontology and includes a list of properties and a list of signals:

  • Properties: Descriptive attributes that characterize the asset, e.g., Manufacturer, RatedPower, Location.
  • Signals (if applicable): Definitions of sensor-related attributes, e.g., Voltage, Temperature, EnergyOutput.
  • Technologies: System types are grouped under broader technology domains such as Solar, Wind, Storage, and Maritime.
  • Datatypes: Standardized data formats used across technologies to ensure consistent representation of metadata and signal values.

Blueprints

Blueprints define reusable hierarchical templates composed of system types. They enable consistent construction of asset structures, such as predefined turbine configurations. When an asset instance is created using one or more blueprints, the complete hierarchy is instantiated according to these templates.

Asset Instance

Asset instances represent real-world assets. They are created based on system type definitions and include actual metadata values (e.g., Manufacturer = Siemens, RatedPower = 3.2 MW). An asset instance can consist of a single system type or a structured hierarchy of related systems. These hierarchies can be constructed by:

  • Instantiating individual system types.
  • Applying one or more blueprints.

In addition to properties values, an asset instance may include the set of signals monitored for that specific asset.