One operational model. Many ways to use it.
TOKNITH's architecture is organized around a shared operational model.
Layers
Defines objects, relationships, processes, resources, constraints, state, behavior, physical properties, and agent rules.
Provides the shared operational clock.
Resolves discrete events, continuous processes, and agent behavior.
Receives observations from the real operation.
Compares expected and observed behavior.
Creates alternative operational futures.
Represents model state.
Connects the model to operational systems, equipment, sensors, and other sources of information.
The model owns state.
The visualization represents it. The simulation advances it. The live operation provides observations against it. Branches represent possible future states derived from it.
The result is not a collection of independent applications.
Everything else is required to agree with it.
Continuous state, discrete events, agent behavior, physical observations, and branching rehearsal share the same temporal and state model.
The same state drives the picture. The same clock advances the physical process. The same clock resolves operational events. The same model governs agent behavior. The same model receives observations from reality. The same model records residuals. The same model can be branched for rehearsal.
That is the underlying advantage. Not the visualization. Not the simulation engine. Not the integrations. The model.
One model supports many modes of operation.
One clock. One model. Many futures. One reality.
Model the operation. Rehearse the change. Connect it to reality.
Request a Demo