The operation is one system.
One model. One clock. Reality and rehearsal.
Discrete work happens at a time.
Continuous processes change through time.
Agents move, interact, and respond.
TOKNITH brings them together in one operational model.
Model it. Run it. Branch it. Connect it to reality.
Events · continuous processes · agents · one clock
A warehouse. A hospital. A factory. A complex facility.
Different operations. Same fundamental problem:
Physical systems and operational work have to interact in time.
An order moves through a warehouse while conveyors continue running and workers move through the facility.
A patient moves through a hospital while beds, rooms, elevators, staff, equipment, and treatment processes change continuously.
A part moves through a factory while machines operate, buffers fill, operators move between work centers, and failures change what happens next.
The operation is not just a workflow. It is a system.
TOKNITH models the system as one.
Three ways an operation behaves.
Real operations are not purely discrete or purely continuous. They contain different kinds of behavior that interact constantly.
Events happen.
An order releases. A job completes. A truck arrives. A machine fails. A patient is assigned a bed. A wave closes. A shipment leaves.
Processes evolve.
A conveyor moves. A tank fills. A temperature changes. A battery charges. A buffer accumulates. A vehicle travels.
Agents act.
A worker moves through a facility. A forklift chooses its next task. An AMR travels between locations. A patient moves through care.
TOKNITH resolves all three within one model and one clock.
These are not three separate simulations. They are three forms of behavior within one operational model. Agents here means agent-based modeling, not AI agents.
The measured pattern of the operation.
The name TOKNITH comes from the Hebrew toknith, associated with a measured plan, pattern, proportion, or complete design.
TOKNITH is not simply a picture of an operation. It is a model of how the operation is supposed to behave. The model can be run, examined, changed, branched, compared, and ultimately connected to the real operation.
The model is the authority.
- Physical system
- Operational system
- Time
- Behavior
- State
- Run
- Branch
- Compare
- Connect
The picture is not allowed to lie.
Visualization is not a separate presentation layer that invents what the operation looks like. It is a representation of model state.
- If the model says the liquid rose, the picture shows it rising.
- If the model says a worker is blocked, the picture shows the worker blocked.
- If the model says a conveyor backed up, the accumulation exists.
- If reality disagrees with the model, that disagreement belongs to the model.
Rehearse before you change.
Range is TOKNITH without the wire connected to the live operation. Build the model. Run the operation. Change it. Branch it. Compare alternatives. Test failures. Explore capacity. Evaluate automation. Change staffing. See what happens.
Range allows the operation to be explored without making the real operation pay for the experiment.
Range answers: What could happen?
- Model
- Branch
- Run
- Compare
- Expected
- Observed
- Residual
- Understand
Connect the model to reality.
Campus is TOKNITH with the wire connected. The same model. The same objects. The same process definitions. The same clock. The same event semantics. The same physics.
Now the operation provides observations. TOKNITH compares what should be happening with what is happening. Expected state. Observed state. Residual. History. Ownership.
Campus answers: What is happening?
From rehearsal to operation.
The model used to evaluate the change becomes the model used to understand the resulting operation. TOKNITH does not throw the model away when the operation goes live.
- Model
- Range
- Branch
- Compare
- Commit
- Campus
A rehearsal does not silently become live. A person promotes it.
Commit is the promotion boundary. It separates what is possible, what is expected, what has been approved, and what is actual.
Model the operation you actually have.
Answer the customer-fit question with a model instead of a spreadsheet and a guess.
Model patients, staff, beds, rooms, and movement as one operational model.
Model machines, people, materials, buffers, processes, automation, and time together.
Model facilities, transportation, inventory, yards, docks, labor, vehicles, and customers as one network.
Solve the operational question, not just the industry problem.
Not just simulation.
TOKNITH uses simulation as a capability, not as the category.
| Traditional approach | TOKNITH |
|---|---|
| DES models events | Events + continuous processes + agents |
| Physics simulation models physical behavior | Physical + operational behavior |
| Digital twin represents a facility | Executable operational model |
| Workflow systems manage work | Model the physical consequences of work |
| Visualization shows state | Visualization derives from state |
| Scenario tools create isolated simulations | Branches derive from the operational model |
| Live systems report what happened | Model compares expected and observed behavior |
The difference is not another feature. It is the model.
The moat is the model, and the fact that everything else is required to agree with it.
The same state drives the picture. The same clock advances the operation. The same model receives observations from the floor, records disagreement, and can be branched to explore another future.
Read the architectureOne clock. One model. Many futures. One reality.
Model the operation. Rehearse the change. Connect it to reality.
Request a Demo