✅ Configuration checklist

the checklist application allows the user to configure, review, and activate quality checklists such as 5s checks, audits, or equipment inspections creating a new checklist when logged in as the correct user, new checklists can be created from the configuration area click new a pop up window appears select the checklist scope equipment class equipment location depending on the selected scope, different parameters must be completed checklist scope configuration equipment class–based checklist when creating a checklist based on an equipment class the equipment class allocation is selected core application automatically pre fills equipment class references structural links context parameters you only need to select the applicable class trigger configuration each checklist must have a trigger , defining when it should be executed available triggers daily check triggered once per day at a predefined time start of order triggered every time a new production order starts end of order triggered when a production order is completed start of shift triggered at the beginning of a shift end of shift triggered at the end of a shift every 1000 usages triggered after every 1000 usages or completed orders on the equipment manual triggered manually by the user by clicking the checklist each trigger has its own execution behavior based on production or operational events general checklist information when configuring the checklist, the following fields must be completed checklist id unique identifier for the checklist plant automatically pre filled based on the selected equipment or location description can be maintained in multiple languages (e g english, dutch) once created, the checklist is saved with the status draft version & execution settings in the version details section, additional parameters can be configured execution behavior delay between questions defines a time delay (e g 10 seconds) between questions instead of moving automatically execution mode sequential (questions must be completed in order) non sequential (questions can be completed freely) execution roles & approval execution levels execution level 1 execution level 2 approval (only one approval level) for each execution level one or more user roles can be assigned if multiple roles are assigned, the first user to start the checklist can execute it examples operator and supervisor both assigned to execution level 1 operator executes first, supervisor executes second approval is done by a designated qa role attachments attachments (documents, images, references) can be added to the checklist and will be visible during execution this allows us to give general information about the checklist to the user adding checks to a checklist before sending a checklist for review, checks must be added click add check on the right hand side a pop up window opens check configuration each check contains barcode (optional) forces the user to scan a barcode to confirm they are at the correct location before executing the check check type predefined check (e g measurement) free text input valid answer defines acceptable input for the check picture needed or not if free text is optional, mandatory, or not applicable review & activation workflow after all checks are added, the checklist can be sent for review status changes from draft to in review a quality inspector reviews and accepts the checklist the creator can then activate the checklist decline it for further changes once activated, the checklist becomes available based on its configured trigger