EPSILONOperations Intelligence

SIMS · Playable format

OpeNimationTMThe playable SOP — a procedure you watch, hear and confirm

SIMS
Playable format
The OpeNimation player at a decision point

An OpeNimationTM is what a procedure becomes in SIMS: an annotated 3D animation of the work, cut into steps, each carrying its own clip, its written instruction and a spoken version of it.

The player shows one step at a time and moves on only when the responsible role confirms it. The same file plays as an operations run, a training run, or a coordinated session between field and panel — and every play-through leaves a record.

Clip per stepSpoken instructionConfirm to advanceAny device

See exactly this step

Each step plays its own segment of the master animation — the exact equipment, the exact action with exact details, not a lengthy video.

Hear it, hands free

Instructions are narrated from the step text, so the operator's eyes and hands stay on the equipment.

Steps that know their kind

Actions, notes, warnings and decision points look different and behave differently — cautions are read, not skimmed.

Every play-through on record

Who confirmed each step, when and on which device, with any issue raised against it — kept as the run record, without a form to fill in afterwards.

The format

What is inside an OpeNimationTM

From master animation to playable steps

InputMaster animation

one annotated 3D render of the whole procedure, start to finish

ProcessParser

uses prepared, extracted time-codes to find the segments of each step, and match them with the right rows.

ProcessSegmentation & step matching

cuts the animation into clips and matches each clip to its step

OutputOpeNimationTM

playable steps with role gating and step-by-step confirmation

Anatomy of a step · from the player

What the operator gets, every time

  1. 1
    The AnimationA 3d-rendered animation played back specifically for this action, accompanied by step-relevant on-screen annotation specifying the action considerations.
  2. 2
    Role SpecificEvery step is specified for a specific role, and the playback system handles it all with the right user being prompted to take action, and the other being shown progress and informed of when their role will be required again. with hand-off and step confirmation built in.
  3. 3
    The instructionShort, clear instructions naming parts and action required are the foundational part of every step. placed in a neat panel, usually in bullet form, coordinated with the on-screen demonstration.
  4. 4
    The narrationEach block of instruction is reworked and performed by high-quality voice models for natural sounding verbal instruction that doesn't feel like someone reading a text book.
  5. 5
    The controlsAll playback, animation and voice, adhere to simple familiar playback controls, allowing the user to scrub back and forth to clarify instructions or inspect missed lines and details.

How an OpeNimationTM is made

The Initial Generation Process

SIMS is delivered with its content. Our team takes your plant's CAD files and existing SOP documents and — working alongside your process engineer — turns them into rich, annotated 3D animations of each procedure, with human models for correct scale and action. No filming on site, no drafting from scratch, and nothing for your team to model.

1

Inputs

Plant CAD files and the SOPs you already have, reviewed with your process engineer.

2

Visualise

Our animation team renders the activity in 3D — annotated, to scale, with a human model demonstrating each action.

3

Write

Our copywriters draft two sets of clear, digestible instructions — one written to be heard, the other to be read — for accuracy at the equipment.

4

Composite

The final animation is composited into motion-graphics annotated video files, then integrated with data derived from the SOP documentation to create interactive checklists — organised and played back on our platform.

An annotated 3D render of an operator at a valve, generated from plant CAD
OpeNimationTMYour plant, your procedure, demonstrated to scaleRendered from your own CAD, so the valve, the platform and the reach are the real ones — and a human model shows exactly what the step asks for.

You provide

  • Plant CAD files (Navisworks, SmartPlant, AVEVA E3D, etc.) and P&ID files where available
  • Existing SOP documents, however informal
  • A process engineer's time for review sessions

We deliver

  • Annotated 3D animations of every procedure, step by step
  • Spoken and written instructions per step, reviewed and approved by you
  • Procedures loaded, tested and live in SIMS — ready to assign

Three ways to play

SOP playback for different users and cases

The same OpeNimationTM plays for a technician alone at the equipment, for a new starter learning the job, and for a field-and-panel crew working the procedure together. What changes is who confirms, what gets recorded, and where it counts.

Production runGuided execution

The operator sees the current step, hears it, does it, confirms it. Nothing advances until the role that owns the step says so. A run interrupted by a shift change or a dropped connection resumes at the same step with its history intact.

What it leaves behindA time-stamped record of every confirmation, issue and halt — the run report, archived as PDF the moment the last step is confirmed.
  • Role-gated confirmation per step
  • Issues raised on the step, run paused until dealt with
  • Resume where you left off

Training runSame checklist, no production record

New staff walk the exact procedure they will later perform — same clips, same narration, same confirmations — without it counting as a production run. Supervisors can see who has trained on what, and require it before a first live assignment.

What it leaves behindA training record kept apart from production runs: who practised which procedure, when, and how far they got.
  • Identical to the live procedure, clearly marked as training
  • Visible to supervisors as a readiness signal
  • Never mixed into production history or reports

Coordinated runField and panel, in one session

Participants join a lobby with a short code and take a role. Everyone sees the same step list; each confirms their own steps and watches the other side's confirmations land live. Decision points become recorded branch choices; anyone can request a halt for the supervising engineer to decide on.

What it leaves behindOne record for the whole crew — who confirmed what, which branch was taken and by whom, every halt and its decision.
  • Join code · per-person confirmation
  • Branch decisions with chooser and time
  • Halt requests with severity and reason

Runs in the browser, on whatever is in your hand

OpeNimationTM plays in a standard web browser — nothing to install, nothing to keep updated. The same player works on the tablet at the equipment, the panel PC in the control room, a phone in the field and a desktop in the office, on any operating system — and a run started on one device can be picked up on another.

Guided execution

Running a procedure

The procedure, shown and spoken, one step at a time

At the equipment, the operator sees the current step: the clip from the master animation, the written instruction and a spoken version of it. Nothing advances until the step is confirmed by the role it belongs to.

Steps that are notes or warnings are visually distinct from actions, so cautions are read rather than skimmed. A training mode lets new staff walk the same checklist without it counting as a production run.

Clip per stepSpoken instructionRole gatingTraining mode

Clip, not chapter

Each step plays exactly its own segment of the procedure animation — the operator sees the valve, the panel, the reading, not a 20-minute film.

Hands-free instruction

Instructions are narrated automatically from the step text, regenerated whenever the wording changes.

Report a problem in place

Anything unexpected is raised against the step it happened on, with the run paused until it is dealt with.

Resume where you left off

A run interrupted by a shift change or a dropped connection is picked up at the same step, with the history intact.

Run mode · step 1.A.1 in a live procedure — repeat, confirm & continue, or report an issue

Field and panel, together and in sync

Many procedures are a conversation between the field and the control room. SIMS runs them as one coordinated session: participants join a lobby with a short code, each takes a role, and the checklist advances only when the responsible people have confirmed their step.

Decision points become branch choices recorded with who made them; anyone can raise an issue or request a halt, with a severity and reason, for the supervising engineer to decide on.

Join codePer-person confirmBranch decisionsHalt requests

One session, many hands

Field and panel technicians see the same step list; their own steps are highlighted and the other side's confirmations appear live.

Decisions on record

Where the procedure forks — abnormal reading, alternate route — the choice, the chooser and the time are captured with the run.

Controlled halts

A halt request carries a severity, a reason and the step it was raised at; the supervisor's decision and message go back to every participant.

Talk while you work

A meeting link can be attached to the session so voice stays with the checklist instead of a separate radio channel.

Coordinated run · the lobby — the run starts only once every role has confirmed presence

Inside SIMS

The rest of the product

Next step

See an OpeNimation™ of one of your own procedures.

Hand us one CAD model and one SOP; our content team returns it as a playable procedure you can run in training mode.