CapabilitiesIndustrial ontology and asset context
Industrial ontology and asset context
Give a machine, component, measurement and work order a common identity across systems. This lets engineering and maintenance teams refer to the same equipment even when their systems use different names.
Product documentation · Updated 15 November 2026
- Who uses it
- Process engineers, reliability engineers and plant data owners
#Resolve asset identity
Start with one machine. Map its plant register entry, historian tags, ERP equipment number, drawing reference and aliases. Preserve the source identifiers so a reader can trace every link. If two tags could belong to the same fan, record the ambiguity and ask the asset owner to resolve it.
#Describe relationships and operating context
Represent the plant, line, machine, component and sensor position, then connect the applicable failure modes, documents and maintenance events. Preserve units, operating mode, validity dates and the source of a relationship. A bearing replacement should change the component history while keeping the parent fan identifiable.
#Return context and capture corrections
A context request for a vibration channel should identify the bearing position, machine, operating regime and relevant source records. A technician who finds a wrongly mapped sensor supplies evidence for a reviewed correction. POLYCRON’s intended progression is MYCEL for foundational definitions, NEXUS for linked context and APIs, and KEVAL for time-aware knowledge and verified feedback.
#Outcome and verification
- What the team gets
- A traceable asset record that an application or engineer can use to join evidence correctly.
- How to verify it
- Ask which bearing a reading described before and after a replacement. The answer should retain both component identities and the evidence for the change.