How we work
We start withone machine
We do not move a whole plant into virtual space at once. One machine, one line or one procedure is chosen; once the pilot scenario runs, we measure — then we scale.
Big projectsstart small
The best-known trap in industrial software is setting the scope large on day one. Someone tries to twin the entire line, the scenario list swells, and six months later there is still nothing to show.
We do the opposite. One machine and one procedure first. Once that scenario runs, two questions have been answered: is the team actually using it, and is the measurement useful? If the answers hold, scaling is easy — the digital twin already exists.
That is why scope grows after the pilot, not in the first meeting.
Fivestages
These durations are typical. Machine complexity, the state of your CAD data and the number of scenarios move the ranges.
Discovery and scope
Which training repeats most, costs most, carries most risk? The answer becomes the pilot scenario. Goals and the success measure are written in this step.
1–4 weeksDigital twin
CAD data is optimised into a model that runs in real time. Where there is no CAD, the machine is measured by 3D scanning.
1–2 weeksScenario writing
Assembly steps, fault set-ups and safety instructions are coded into ordered tasks: precondition, correct action, typical mistake and feedback.
3–6 weeksTest and pilot
The first sessions run with real staff. Steps that read unclearly, and tasks that turn out too hard or too easy, are corrected here.
1 weekRollout and updates
The scenario is distributed to every unit. When the machine is revised, the changed step is updated centrally; the content is not rebuilt.
Ongoing
What we ask from you
How ready these inputs are is the single biggest factor in project speed.
- CAD data or technical drawings for the machine (3D scanning is planned where there is none)
- Operating instructions, assembly sequence or maintenance procedure
- Risk assessment and near-miss records for safety scenarios
- A group of three to five people for the pilot sessions
- One point of contact on your side
What gets delivered
The concrete things you hold at the end of the pilot.
- A digital twin that runs in real time
- A working scenario built from ordered tasks
- A short guide for the instructor and for participants
- A report from the pilot sessions: time, error types, completion
- A scope and schedule proposal for scaling
The pilot is where the decision to continue is made. If the measurement falls short of the expectation, we see that together; results are the condition for widening scope. That is exactly why we keep the first step small.
Let's start withone machine
We pick the pilot scenario together, make it run, and measure it. The results decide what comes next.