Procedures (What)

Procedures are the smallest component of a checklist. Each line in a checklist, represents a procedure. This ensures a high level of granularity when creating checklists. This implies one procedures can be used in multiple checklists.

eg. Procedure: "Check the pressure of a valve" can be used in the following checklists: "Change over checklist", "operational checklist (weekly)", "start-up checklist (after maintenance)".

Mandatory fields

• Name - The name will become visible in the checklist or in the individual check.

• Owner - Persons with the authority to edit the content of the procedure

  • Individual users - Selection of active users to be able to edit this procedure

  • Team members - Members of teams will be able to edit this procedure

  • With favorite workstations - Employees that have selected or were assigned the selected workstation(s)

  • By profile - Users with the selected profiles linked to them, will be able to edit this procedure

  • In a profile group - Users with with a profiles linked to them that's part of the selected profile group, will be able to edit this procedure

  • By position - Users assigned to a certain position will be able to edit this procedure

  • With acquired skills - Users who have acquired the selected skills will be able to edit this procedure

Prerequisites owner selection

• Team members - Team members configured via Training › Teams

• Profile - Profiles configured via Settings › Skills & Training › Profiles

• Profile groups- Profiles configured via Settings › Skills & Training › Profile groups

• Acquired skills - Skills configured via Settings › Skills & Training › Skills

NOTE: One needs to have the permission "Can edit own checklist definitions and procedures" to edit procedures someone is the owner for. This individual permission can be overwritten with "Can edit all checklist definitions and procedures"

• Measurement type -There are different options to enter data. More information on the measurement types can be found in the detailed page

  • Choice

  • Numeric

  • Textual

  • Date

  • Time

  • DateTime

  • Material

  • Staging

  • Use by Date (DLC)

  • EAN

Note: all of the checks, can be accompanied by picture evidence. To activate this request, toggle "photo required" in.

Additional details on how-to

Main slide

• Title - When filled in, this overwrites the "name" of the procedure

• Description - Smaller details of a check in text format.

• Media - Any uploaded image or GIF that need to be shown

See below the editor (left), details view (middle) and table view (collapsed & expanded) (right)

Procedure document

• Upload - One can upload a new document (in case the Document Module is not being used)

• Link URL - One can hyperlink an online doc (in case the Document Module is not being used)

• Select document - One can select a document from the Document Module, taking advantage of approval versions and smart notifications in the future.

Additional details for reporting

• Equipment - One can select equipment where the procedure can be executed. Apart from being part of a checklist, procedures can be "standalone" and be administered individually. Their completion can be manually initiated or can be linked to to scanning a QR-code. n most cases however, they are linked to checklists.

• Labels - xxx

Generating a QR code for a procedure

When one or more equipment are assigned to the procedure, one can create a QR code. This is useful for single, event driven checks.

To generate a QR code, one need to click on start , select an equipment and workstation and press

At the procedure level, one can check how often the QR code is being scanned

Often used when time is unknown and employees are at the location to do an action, they can register their activity eg adding a material to an equipment.

General

• Execute check during - Indicate whether the check needs to be carried out

  • Downtime - Line or equipment is expected to be down to be able to do the check

    eg. An inspection inside a machine, cleaning of a part, etc

  • Uptime - Line or equipment is expected to be down to be able to do the check eg. The operational pressure or temperature of an equipment

  • Both - One can always execute the check, regardless of the equipment state

  The selection is also visually shown in the table of a checklist with corresponding arrows

• Troubleshooting - Reference to the reaction standard or explanation to overcome non-conformities of a check.

• Labels - One can link individual labels to a procedure, simplifying reporting issues across checklists or equipment tree. Often used for functional indication eg Techical check, food safety check, safety inspection, operational,...

Important to know...

A significant benefit is that procedures can be reused in different checklists. A certain parameter potentially need to be checked periodically (timebased), but also during specific events like maintenance, at machine installation / set-up or during troubleshooting. Ensuring the value is logged versus the same standard, gives a rich context for future analysis.

On top, this allows to look for the value of a procedure across checklists, teams and lines. A fast way to interrogate your data.