What you can do
From a live signal to reusable operational context
Use these workflows to evaluate the released components through concrete user tasks. The value is in the connected path: discover a signal, understand its shape, investigate an event, reopen the analysis and retain identity when equipment moves.
Compare measurements and states
Select several numeric series and string/status lanes, move the time window, inspect the historical query, save a view and export Excel. SQL explains supported reads; direct QuestDB access remains separately configured.
Keep the same Asset through location changes
Asset history resolves verified Attribute intervals from stable identity. Identity-based saved views, dashboard cells and explicitly registered Catalog references reopen through that identity. Topic-only selections retain their own path semantics. The mobile demo includes a cassette and two independently identified rolls, with temperature and operating parameters. Only observations inside confirmed binding intervals belong to identity history.
Relate measurements to a production visit
Load the fictional furnace, inspect material visits and review the full declared input/output set of a split or merge as one operation. Missing events stay pending; an immutable decision receipt lets you check a lost response. Compare selected visits against telemetry. A shared comparison re-runs authorized queries; it is not a frozen evidence snapshot.
Expose a reusable data product
A service can register description, parameters and response schema beside its operations. The public furnace Catalog example returns JSON, CSV and Parquet over one source without changing the producer.
Move from a condition to recorded evidence
Triggers detect focused conditions. Captures record selected values during windows or other configured modes. Runtime confirmation, recent fires/sessions and session-filtered Explore make the outcome inspectable.
Operate the data path and review changes
Inspect versions, process metrics, dependency health, routes and local secret readiness. Review compatible workload moves and bounded semantic changes before distinct confirmations. Qualified incidents have recorded history, reviewed personal recipients and a signed external webhook with bounded retries. An uncertain delivery remains separate from service recovery.
Review meaning before changing its consumers
Preview a candidate’s known impact on bindings, archive mappings, views, dashboards, automations and declared service contracts. Fresh review can permit restricted additive, display-metadata or State/Action changes. Unknown consumers and unsupported conversions remain explicit blocks. The optional simulator contract has a separate trusted handoff, adoption and recovery flow.
Evaluate the complete path in your own environment
- Current and historical are differentLive delivery does not establish archived coverage. Inspect source time, mappings, retention and authorization.
- Identity requires evidenceNames and parent nesting do not approve a publisher or prove that two paths are the same Asset.
- Recovery has distinct layersCreating a signed recovery point, moving it off-host and successfully restoring it are separate results.
- Focused automation and governanceNo automatic arbitrary consumer migration, coordinated fleet rollback, physical control safety or complete high-availability certification is claimed.
- Private development stays separateBroader Assistant/RAG, automatic trusted contract delivery and Ignition UDT/Sparkplug import are not provided by these workflows.