Skip to content
SmartFACT HelpHandbooksWatch and practise
Handbooks: SmartFACT Automation

Start here: Operator

Recognise Automation's requirement list and keep production work in its owning product.

Review edition · 25 October 2026 · For Operator

On this page

The Operator role can open Automation's requirement list, but it does not grant rule authoring, detailed requirement review or native release approval. Use your owning product for its permitted production tasks. Approved rules run there under that product's current authority.

Recognise what the workspace represents

Your organisation's rules lists retained requirement titles and revisions. A requirement is a statement of intended behaviour, not proof that a rule has been released. Saving one does not change live production. A later revision in the list is also not evidence that the corresponding product has activated a new release.

Operator alone does not open requirement details or the native editing and review workflow. If a linked destination refuses your role, follow the refusal and ask the organisation administrator for the working role your responsibility actually needs. Do not use a colleague's Author or Reviewer session.

Carry out floor work in its product

Follow the owning product's task instructions, source identities and current holds. Automation does not create stock simply by describing it, certify an inspection, book a courier or prove physical printing. A rule explaining what should happen remains separate from the event that establishes what did happen.

When a product says a prerequisite is missing, keep the work held and give the Supervisor the actual unit, order or component reference and visible reason. Do not infer that a named requirement in Automation overrides that local refusal.

Give useful feedback

Describe the physical situation, the source facts and what result was expected. Include the exact product record and the message shown. An Author can use those facts to prepare a case, and an independent Reviewer can decide whether a new rule is justified.

Do not change observations to fit the existing rule. The engineering and operational record needs the actual outcome even when it is inconvenient. Read Understand release evidence if you need to understand the stages colleagues mention, while leaving those actions to their authorised roles.