EPSILONOperations Intelligence

SIMS · Document control

SOP Data HubOne approved procedure, and everyone reads it

SIMS
Document control

Store · Revise · Retrieve How a procedure document lives in the Hub

REVISESTORERETRIEVE a working copy, separate from the approved onethe library — one controlled record per document number, filed by plant › unit › sub-unitsuperseded revisions stay behind the current one — readable, never editablethe right revision for the right personauthor records what changes and why · a different person approvesbecomes current on approval DraftCheckApprove Rev 00Rev 01Rev 02Rev 03 · currentRev 04 Auditors · reviewersfull history and workflow record, read-onlyReaders · operatorsthe current approved revision only

SOP Data Hub is where a company's procedure documents live: one controlled library, organised plant by plant, that always shows the latest approved revision — and records exactly how it got there.

Changing a procedure never touches the approved copy. An author starts a working revision, a checker reviews it and a separate approver signs it off. Only then does it become current, and the old revision is marked superseded.

Unique document numbersPrepared · checked · approvedScoped accessControlled copies

One source of truth

A single current approved revision per document number; a draft can never be mistaken for it.

Findable

Search by document number, title, keyword, owner or status — the current revision always comes first.

Separation of duties

Author, checker and approver are distinct roles, taken from your own directory and sign-on.

Immutable history

Every edit, approval, download and permission change is logged; approved revisions cannot be deleted.

The revision lifecycle

Every state recorded, every hand-off dated

1

Draft

Author starts a working copy — the approved version stays untouched

2

Review

Checker confirms, or sends it back with comments

3

Approve

A different person approves or rejects, with reasons

4

Current

Locked, stamped and published; the old revision is superseded

5

Archive

Superseded revisions stay readable to those allowed, never editable

Who does what

Access follows the plant tree

A plant team sees its own branch, a corporate function sees across plants. Each role gets only the actions it needs, from your own directory and sign-on — and every action is logged.

Author

Creates a procedure or starts a revision of the current one, records what is changing and why, and picks an eligible checker.

Checker

Reviews the working copy, comments, and either sends it back for changes or confirms the technical review — never approves.

Approver

A different person from the checker. Approves or rejects the reviewed revision, with a reason on record either way.

Reader

Operators and engineers. Browse and search their permitted plants; open or download the current approved revision only.

Auditor

Read-only across approved and historical revisions, the workflow record and the audit log — sees everything, changes nothing.

Administrator

Sets up plants, hierarchy, groups, workflow rules and retention. Administration carries no approval rights of its own.

The audit trail

  • Every creation, edit, assignment, comment, review, rejection, approval, publication, download and permission change is logged — who, when, what changed.
  • Approved revisions cannot be deleted from the interface; retention and archival follow the policy your administrators set.
  • Downloads and printouts carry the document number and revision, and are labelled controlled or uncontrolled.

Nothing stalls quietly

  • Assignments, change requests and approval requests reach the right person by email and in the app.
  • Overdue reviews and approvals are chased automatically; upcoming review dates are flagged before a procedure goes stale.
  • Concurrent edits are controlled — a working copy is checked out by one author at a time, or conflicts are detected before anything is lost.

What the Hub guarantees

Built for controlled documents

  1. One source of truth — a single current approved revision per document number; drafts can never be mistaken for it.
  2. Plant-wise hierarchy — plant, unit, department, category; people see only the branches they are cleared for.
  3. Findable — search by document number, title, keyword, owner or status; the current revision comes first.
  4. Separation of duties — author, checker and approver are distinct roles, taken from your own directory and sign-on.
  5. Immutable history — every edit, approval, download and permission change is logged; approved revisions cannot be deleted.
  6. Nothing stalls quietly — assignments, overdue reviews and upcoming review dates reach the right person.

Inside SIMS

The rest of the product

SIMSOpeNimationTM

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

Explore

SIMSSIMS overview

Standard Operating Procedures (SOP), interactive and auto-reporting

Back to overview

Next step

The document the operator runs is the document you approved.

Talk to us about bringing your SOP library into SOP Data Hub as part of a SIMS pilot.

Talk to us about a pilot Download the SIMS summary