Load the demo furnace and follow material lineage

Worked example

Example: compare two furnace visits

Two materials can pass through the same station at different times. Select the actual recorded visit for each material before comparing temperatures; a common topic alone does not identify the production run.

Procedure

Follow the task in order

1. 1
   Select the complete worked-example profile before starting dataOn a clean installation choose Hot rolling example — start in Setup. Alternatively inspect that exact profile in Solutions & packages → Solution catalog and use its normal reviewed installation/transition while the demo is stopped. The profile composes reusable Manufacturing, quality, energy, utilities, units and material-traceability 1.2.0 packages with the separate examples.hot-rolling 1.0.0 example. Manufacturing essentials is intentionally smaller and does not provide the material relationships. Do not select a hidden compatibility profile, overwrite package ownership or install a similarly named raw schema preset.
2. 2
   Install services and check the material contractsThrough Micro services install compatible rtt-demo-app 6.1.26, UNS Archiver 5.2.25 and API Global 4.1.20 or newer compatible releases. Load config-development-podman.json for a Controller-managed container instance. Review service access for the fictional forge-group/novasteel/hot-rolling/# branch. Start Archiver and wait for input readiness, then API and demo. In Schema verify material, location, previous-material, previous-materials, split-from-material, merge-from-materials and material-renumbering/split/merge are active. The profile does not create Assets, approve publishers or start services; use the demo’s visible Setup and data journey → Review preparation for its roots.
3. 3
   Open Hot rolling demoFrom Micro services open the demo operator page. Check simulator readiness and the live production line. A reachable page with no producer is not a running simulation.
4. 4
   Load a bounded batchChoose Recipe, First material identifier and Pieces in Load the furnace. Review the generated material names and advanced options, then choose Load furnace. Each piece enters the production queue; do not reuse an existing identifier without understanding the simulator’s rule.
5. 5
   Follow production and relationshipsFollow the first ordinary piece until it completes. Open its Material details → Split material, enter two fresh output identifiers and choose Split into two outputs. Pieces in Load the furnace are separate inputs, not a split. For an independent merge, load two new pieces, expand Advanced options, enable Merge these pieces after rolling and enter a fresh merged output identifier. These two scenarios produce separate complete declarations; do not claim the split children were reused for the merge.
6. 6
   Open the complete operation reviewIn Unified namespace expand the station and material branch. Open the source material’s node menu, choose Details, then Review split. For a merge, open the output material and choose Review merge. These are material relationship reviews; Explore of one attribute reads that attribute’s values and does not approve the operation.
7. 7
   Check every declared input and outputThe producer declaration lists the concrete material paths and a producer operation ID. Compare received and expected links. A split with 1 of 2 links received is still waiting; the view names the missing pair and disables group decisions. Choose Refresh operation after a delayed event arrives. A timeout or restart never makes a missing member complete. Conflicting declarations remain blocked for investigation.
8. 8
   Review the current complete snapshot togetherWhen every declared link is present, valid and still suggested, review all inputs, outputs and links, select the acknowledgment checkbox, then choose Accept all links or Reject all links. One recorded decision covers the entire operation. If another writer changes a member, endpoint or contract, refresh and review again; the earlier snapshot cannot silently overwrite it.
9. 9
   Recover a lost confirmation responseThe result shows a review request ID separately from the producer operation ID. If the response is lost, keep the pending request and choose Check result to read its matching receipt, including after reopening. Do not create another request or approve individual links to work around an unknown result. No receipt yet does not prove the first request was never applied. The split and merge each have their own relationship review receipt. These are distinct from simulator command receipts; accepting relationship evidence does not run another production command.
10. 10
    Open the archived material traceSearch/select the material with its owner and time window. Inspect recorded visits, repeated visits and quality evidence. Open a measurement or event in Explore from the selected visit to retain the exact bounds and historical source. Demo 6.1.24 and newer resume the same compatible instance journal after restart; older versions keep job and command state only in memory.
11. 11
    Compare two concrete visitsChoose each material/batch and its explicit station visit, then the measurement. Align the comparison by the relevant visit/event context while retaining each source’s original time window. If a recorded visit is missing, select it again; the UI does not substitute another visit silently.
12. 12
    Save or share the selectionName the comparison for this browser or copy its versioned link. Reopen it and check both materials, visits and measurement. Each read is authorized again. Browser bookmarks are not centrally shared records; a link is a repeatable query, not an immutable export of the results.

Expected result

What you should have

Boundaries

Important boundaries

• The worked-example profiles are introduced in Controller 2.2.31 and are not included in Runtime 2.2.30. If Hot rolling example — start is absent, install a release containing it before following this procedure. An incomplete model must not be repaired by manually inserting links.
• The simulator is fictional and does not establish calibrated physics, production quality or safety of physical equipment.
• Trace and history queries have bounds; missing archives, incomplete relationships and denied intervals must remain visible.
• Do not infer new material identity from a renamed path. Transformations and physical equipment moves are different operations.
• Upgrade all Controller readers/writers before the manifest-emitting demo. If reverting below Controller 2.2.13, stop demo 6.1.23 first; a downgrade does not convert archived declarations back to legacy values.
• Legacy evidence without a complete producer declaration remains individually reviewable, but registered links alone cannot prove a complete split or merge. Multiple producer operations on one material path remain blocked for separate reconciliation.
• A complete declaration proves that all declared links arrived. It does not prove physical quantity conservation, a signed producer attestation or execution of a real production action.
• Since demo 6.1.24, the same compatible instance journal retains the run ID, batches, command receipts and pending material publications across restart. Keep the journal with the instance. Reuse the original command ID to check an uncertain result; do not submit another command. Corrupt, full or incompatible journals block instead of silently resetting. Earlier versions start a new run after restart. This is not an exactly-once MQTT guarantee or a tested cross-host migration.
• External relationship integrations must read the current revision and provide expectedRevision when updating an existing link. Stale edits and updates to deleted IDs are rejected.
• These component versions do not imply that every Runtime bundle already contains them. Check the installed Controller version and the selected add-on releases before enabling this workflow.
• Controller source releases and Runtime image/artifact publication are separate. Before starting, verify that the Runtime you download actually contains Controller 2.2.31 or newer; a component release alone does not establish that availability.

FAQ

Common questions

Related guides

Continue from here