What problem does it solve? Operating a Siemens Opcenter Execution MES through an AI assistant is risky: a single Track Out posts WIP and backflushes material in one transaction, an electronic signature is permanent under 21 CFR Part 11, and a wrong disposition can scrap stock or release a nonconforming batch. This Skill gives the model the operator judgment to classify every MES action as read, reversible write, committing write, or destructive so consequential actions pause for human approval. ## Core Features & Use Cases - Action classification and gating: Maps Opcenter operation families (Track In/Out, backflush, holds, NC disposition, e-sign, batch approval, split/merge, spec edits) to read / write / destructive risk classes with explicit gate rules. - State and genealogy reasoning: Models containers, manufacturing orders, routings, specs, holds, NCs, and batch records as state machines, including split/merge genealogy branching, re-entrant routing, and review-by-exception flows. - Recovery playbooks: Provides forward-correction paths for mistakes such as wrong backflush, failed ERP goods receipt, erroneous scrap, or approved batch records, since the Part 11 audit trail is immutable. - Use Case: A user asks the assistant to complete a work order on a Camstar line. The Skill directs it to re-read the container's current step and holds, recognize that Track Out backflushes component lots into the as-built record, and require human approval before committing. ## Quick Start Ask the assistant how to safely track out a container at a routing step in Siemens Opcenter and what approvals are required before committing the move.
