DATA

AAS

A common infrastructure that gives every plant asset a standard digital identity and connects the data of every system

WORKFLOW

Four workflows that turn data into an asset

Each capability has its own flow, and a check it passes before moving on.

Define what data exists, and where.

  1. 01

    Survey sources

    equipment · systems · documents

  2. 02

    Classify items

    meaning · unit · interval

  3. 03

    Assign owners

    owner · standard · permissions

  4. 04

    Link to use

    business and AI needs

Recorded alongside

01

Data list

02

Items · units · owners

03

Collection and use scope

Operating check

Are the location and meaning of the data needed clear?

YES

Clear → design the standard model

NO

Unclear → recheck sources and owners

An example workflow · the detailed links and criteria are set to suit your floor.

SYSTEM ARCHITECTURE

Where AAS sits in the plant's data flow

Floor sources and business history are organised into one common model, so operations, AI and environmental analysis use the same data.

01 / INPUT

01Floor sourcesOT, equipment and energy signals
02Business historyMES, ERP, quality and lots
03Operating standardsItems, processes, equipment, standards

MANUFACTURING DATA PLATFORM

Manufacturing Data Platform

Common identifiers and AAS models
Consistency, lineage and permissions
Data served through a lakehouse and APIs

03 / OUTPUT

✓Common dataOne basis for units, time and codes
✓Digital threadItems, lots, processes and equipment linked
✓Usable dataDX, AI, GX and Digital Twin
Linked by common identifiers, master data and historyResults checked → fed into the next run
Who uses itManufacturing data ownersMES and ERP operatorsAI and carbon analysts

INTEROPERABILITY

Follow the standard and the integration is built once

What to model against, in which format to exchange it and over which interface to ask for it are all defined.

What it is built against

AAS is an open specification rather than a product. Systems from different vendors read the same data as long as they hold to the specifications below.

Category
Specification
Standards
IEC 63278IDTA specificationsIndustrie 4.0
Data model
SubmodelConcept DescriptionSemantic IDIRI / IRDI
Exchange formats
AASXJSONXMLRDFCSV
Interfaces
REST APIOPC-UAMQTT

PROCESS

Four steps from assessment to rollout

Not every asset at once: narrow the scope, set the standard, prove it, then widen.

  1. Assess

    • Choose the assets and lines
    • Survey data sources and tags
    • Confirm submission and integration needs
  2. Model

    • Design hierarchy and Types
    • Select standard submodels
    • Assign identifiers and semantic IDs
  3. Connect and deploy

    • Map source tags and link values
    • Set up repository and registry
    • Open REST API and OPC-UA with access control
  4. Validate and expand

    • Check conformance and required properties
    • Confirm AASX package exchange
    • Widen to more assets and lines

EFFECT

What changes once the standard is in place

Integration stops repeating, asset information is reused, submissions are automated, and nothing is locked to one vendor.

  • A 3D illustration of asset modules arranged around and linked to a central data core
  • 01

    Integration is not rebuilt each time

    A new system connects over one standard interface, and per-vendor mappings are not defined again, so integration work stops repeating.

    Integrationmappinginterfaces
  • 02

    Asset information is reused

    Assets of the same model share one Type; replacement and expansion only add a registration, so specifications, documents and settings are not assembled from scratch.

    Shared Typesreplacementexpansion
  • 03

    Submissions are automated

    The properties being asked for are already in the submodel, so far less is collected and retyped by hand at submission time.

    Required propertiescollectionmanual work
  • 04

    Nothing is locked to one vendor

    The specification is open, so the data survives a system change and the company keeps the master copy of its asset information.

    Open standarddata ownershipsystem change

CONNECT THE NEXT

Connected solutions

The solutions that take the data AAS organises and carry it on.

See all solutions →

START WITH YOUR FACTORY

Start with your factory's own challenges

Check where you stand with the AX readiness check first, then carry on to a consultation.

Request a consultation