New for 10.1.5 (draft preview). This demo ships with FrameworX 10.1.5 (planned April 2026). The feature is not available in 10.1.4 or earlier. Content under review.

This demo showcases industrial ontology integration through an ISA-88 batch-control mini-plant: import an RDF/OWL file, materialize UDTs and tags, round-trip metadata to a graph store.

How-to → Examples → Architecture → Industrial Ontology Demo


Download the Demo files:

  • Local AI Ontology Demo.dbsln (solution, 514 KB)
  • Local AIOntology Demo Source.rj (RDF/JSON ontology, 21 KB)
  • Local AI Ontology Demo Policy.json (import policy, 2 KB)

This demo showcases, among other features, the following:

  • Import a hand-crafted ISA-88 RDF/OWL ontology into a FrameworX solution.
  • Materialize 8 ISA-88 UDTs (Enterprise, Site, Area, ProcessCell, Unit, EquipmentModule, Operation, Batch) with full semantic metadata.
  • Create 13 typed instance tags, one for each OWL individual, following the /Attr convention (PharmaCo/Attr, NewBoston_Plant/Attr, and so on).
  • Auto-create 13 AssetTree folders from the containment paths. No manual folder writes.
  • Round-trip 5 metadata columns: DisplayText, Labels, SourceIri, Description, Attributes.
  • Populate 20 Reference edges: the containment network and the executesOn / belongsToBatch Operation links.
  • Export the whole UNS back to RDF/JSON for diff, archive, or GraphDB upload.
  • Generate a Mermaid visual of UDTs, AssetTree, and Reference edges with one click.
  • Drive the full pipeline through the Designer wizard (human) or the import_graph_model MCP tool (AI assistant).
  • Demonstrate idempotent re-import. Running the import twice produces zero duplicates and replays safely.


Summary

The Industrial Ontology Demo is the reference solution for the 10.1.5 RDF/OWL integration. It starts from a hand-authored ISA-88 mini-ontology (21 KB RDF/JSON) and ends with a fully populated UNS: 8 UDTs, 13 tags, 13 AssetTree folders, and 20 Reference edges between them. Every fact in the solution traces back to a triple in the source file.

The demo is small enough to read end to end in one sitting and complete enough to exercise every column in the 10.1.5 schema additions. Use it as a reference for your own ontology imports.

Technical Information

Key facts about the demo solution:

  • Source file: Industrial Ontology Demo Source.rj (21 KB, W3C RDF/JSON).
  • Policy file: Industrial Ontology Demo Policy.json (one override, namedIndividualThreshold: 0, to keep the 8 individuals as typed tags and out of the Enumerations grid).
  • 8 OWL classes become 8 UDTs: Enterprise, Site, Area, ProcessCell, Unit, EquipmentModule, Operation, Batch.
  • 7 ObjectProperties drive containment and the Operation links (hasSite, hasArea, hasProcessCell, hasUnit, hasEquipmentModule, executesOn, belongsToBatch).
  • 3 DatatypeProperties on Operation and Batch: CreateTime, StartTime, EndTime.
  • 13 OWL NamedIndividuals become 13 typed Tags under the /Attr convention.
  • 13 AssetTree folders auto-created from the slashed paths.
  • 20 Reference edges populated at Pass 2 of the import.
  • Full annotations round-trip: rdfs:label, skos:altLabel, skos:definition, dcterms:identifier.

The ISA-88 ontology shipped with the demo

The source file is a hand-crafted ISA-88 mini-ontology. It is NOT customer data, so the demo ships with the product. The ontology models one fictional pharma company (PharmaCo Holdings), one plant (New Boston), two process areas (Granulation and Coating), and a small Batch with two Operations.

ISA-88 physical model (containment):

  • Enterprise → PharmaCo Holdings
  • Site → NewBoston_Plant
  • Area → Granulation_Area, Coating_Area (Coating is intentionally empty, to show space for future instantiation)
  • ProcessCell → Cell_A (inside Granulation)
  • Unit → Mixer_M101, Reactor_R101
  • EquipmentModule → Stirrer_S101, Heater_H101 (inside Mixer_M101), Stirrer_S102 (inside Reactor_R101)

ISA-88 procedural model (Operation + Batch):

  • Batch → Batch_001 (with CreateTime, StartTime, EndTime)
  • Operation → Op_Charge_001 (executes on Mixer_M101), Op_Mix_001 (executes on Mixer_M101). Both belong to Batch_001.

Every entity carries rdfs:label (primary display name), skos:altLabel (searchable alternatives), skos:definition (human-readable description), and dcterms:identifier (audit ID preserved in Attributes).

Import workflow

The demo supports two import paths. Pick the one that matches how you work.

Designer wizard (human path)

  1. Open the demo solution in Designer.
  2. Go to Solution → Import Tags → Graph / RDF file.
  3. Pick the source file: Industrial Ontology Demo Source.rj.
  4. Pick the policy: Industrial Ontology Demo Policy.json.
  5. Click Import. Watch Pass 1 (UDTs), Pass 2 (References), Pass 3 (Enumerations, skipped here), Pass 4 (Tags).
  6. After the import, the Unified Namespace page shows 8 UDTs, the Tags page shows 13 rows, the Asset Tree shows 13 folders.

See Import an OWL/RDF ontology into your UNS for the full wizard reference.

MCP tool (AI assistant path)

An AI assistant connected to Designer runs the same engine via the import_graph_model MCP tool:

import_graph_model(
  source="file",
  file_path="Demos/Industrial Ontology Demo Source.rj",
  policy="Demos/Industrial Ontology Demo Policy.json",
  dry_run=true
)
# review the summary, then re-run with dry_run=false

Always run dry_run=true once. The preview reports class count, instance count, BaseUserType cycle warnings, and label collisions before any row is written.

Re-running the import on the same solution produces all-modify, zero-create, no duplicates. The plan is replay-safe.

Round-trip export

Export the whole UNS back to a graph file for diff, archive, or upload to a triple store:

  1. In Designer, open Unified Namespace → Tags.
  2. Click Export Tags.
  3. In the Format dropdown, pick RDF / JSON.
  4. Click Export. The file lands in the Exchange folder as Industrial_Ontology_Demo_UNS_Graph.rj.

Or via the MCP tool:

export_graph_model(format="rj", output_name="ontology-demo-roundtrip")

The exported file round-trips at the UserType level: import it into a fresh solution, get the same 8 UDTs + 13 tags + 13 folders back. See Export your UNS to RDF/OWL/GraphDB for round-trip details.

Visual report

Generate a Mermaid diagram of the UNS with one click:

  1. Open Unified Namespace → Asset Tree.
  2. Click Relationship Graph on the toolbar.
  3. A Markdown file with embedded Mermaid diagrams opens in the default viewer. The file lands in the Exchange folder under Visualizations/.

The output shows the 8 UDTs as a class diagram with Reference members, the 13 tags as AssetTree nodes with /Attr leaves, and the cross-links between them. Hover any element to see its SourceIri (the OWL source IRI).

See Generate a visual report of your UNS for the full visual-report reference.

What to inspect inside the solution

Open the demo, then browse these pages in order for a guided tour of the 10.1.5 ontology columns:

  • Unified Namespace → UserTypes. Select any UDT (e.g., Enterprise). The properties grid shows the new ontology columns: DisplayText, Labels, SourceIri, BaseUserType, Attributes. Labels are semicolon-delimited; for Enterprise the value reads Company;Corporation.
  • Unified Namespace → Tags. Filter by Category = MCP to see the 13 typed instance tags. Each has DisplayText, SourceIri, and an Attributes JSON column. The Type column shows the UDT name.
  • Unified Namespace → Asset Tree. Expand the tree to see the 13 folders (PharmaCo, NewBoston_Plant, and so on). Each folder holds one Tag with the /Attr leaf name. The folders were not authored directly; the importer materialized them from the containment paths.
  • UDT member grid (select any UDT, Members tab). Reference members carry the target UDT ID and the SourceIri of the original OWL predicate. On export, the SourceIri restores the predicate IRI in the output triples.

Related

In this section...