Checklists

introduction the list application manages the complete lifecycle of checklists, standard operating procedures (sops), and process inspection forms it is designed to guide operators through structured, repeatable process steps equipment checks before a shift starts, cleaning procedures between production runs, startup routines when a new order begins, or periodic verifications during production checklists are focused on the process and the equipment they ensure the right steps are followed at the right time, in the right way, by the right person checklists versus quality management knowing which to use both the list application and the qm module present operators with questions to answer during production the distinction lies in purpose and scope list application quality management purpose verify process steps and equipment readiness verify product meets specification tied to a production order, equipment, location, or time trigger a specific material and batch result validation completion confirmation, expected values tolerance ranges, pass/fail criteria versioning yes, with approval workflow yes, with approval workflow traceability per execution, per list per batch, per characteristic typical use startup checklists, cleaning verification, operator sops, equipment checks dimensional checks, lab results, visual inspection of product as a rule of thumb if the question is about the process or the equipment, use the list application if the question is about the product itself, use the qm module how lists are triggered one of the key strengths of the list application is its flexible trigger model a checklist does not need to be started manually by an operator; it can be initiated automatically based on a wide range of conditions order based triggers link a checklist to a specific moment in the production order lifecycle a startup checklist fires when an order begins; a shutdown or handover checklist fires when an order ends the order cockpit initiates these automatically as part of the routing step time based triggers fire on a fixed schedule regardless of what is running on the line a daily equipment check or a shift start procedure are typical examples frequency based triggers fire after a defined number of produced pieces or cycles this is useful for periodic in process checks that are tied to output volume rather than time manual triggers allow an operator or supervisor to start a checklist on demand, for situations that do not fit a predefined schedule because lists are linked to a running production order rather than to a specific production lot, they capture process compliance at the order level this is the key distinction from the qm module, where every inspection is tied to a specific material batch how the module is structured the list application separates the configuration of checklists from their execution, following the same version controlled lifecycle used across the mantsu suite list creation and configuration covers the definition of each checklist its trigger, its checks, the answer types, execution mode, and any linked documents a list must pass through a review and approval cycle before it can be activated for use on the shop floor execution is where operators interact with the list once triggered, the operator works through each check in sequence, records their answers, and submits the list depending on the configured execution mode, a second independent execution or a supervisor approval step may follow before the list is closed execution modes the list application supports four execution scenarios, allowing quality engineers to configure the level of verification required for each checklist single execution requires one operator to complete the list once all checks are answered successfully, the list is closed two execution requires a second operator to independently complete the same list this is useful for critical steps where a double check is required approval routes the completed list to a supervisor or approver, who reviews the answers before the list is finalized two execution with approval combines both a second independent execution followed by a supervisor sign off if any check fails, the list is closed with a failed status regardless of the execution mode roles role responsibility quality engineer / admin create and maintain list templates, manage the review and approval cycle, configure triggers and execution modes operator execute checklists triggered from the order cockpit or manually on the shop floor validator review list versions submitted for review and approve or reject them approver activate new list versions and sign off on completed executions where required supervisor monitor execution status, trigger manual lists, follow up on failed executions versioning and lifecycle every checklist follows a controlled version lifecycle draft, for review, reviewed, activated, and deactivated only one version of a given checklist can be active at any time when a change is required, a new draft version is created and goes through the full review cycle while the current active version remains available for execution this ensures there is no disruption to ongoing production during a revision full traceability of every status transition is maintained, including who made the change, when, and any comments entered at the time list creation process docid\ f 8ddxuet3 ygs0gjv6ry how to manage the checklists execution process docid\ cufumwqq belx9t0woxme execute a checklist