Work Instructions Example
A simple example of how you can use work instructions to guide workers and capture data
This application is meant to provide an example of a simple, static work instruction. Static work instructions operate in the same way each time that they run and do not change their content depending on the product selected.
There is no setup required for this application, as it does not use Tables and all content required to run the application is built into its logic and design.
How it works
Users enter in (or scan) a work order number. They then begin the operation of assembling a rotor (which is an example assembly item). This first screen also displays performance metrics using Analytics.
To begin the order, the user must enter Lot number information for the components that are going into the assembly. There are custom widgets next to each input which give the user visual feedback. In this example, lot numbers must be 5 characters long.
After entering in Lot information, the app presents the user with step-by-step instructions. The user can click the next/previous button or simply click on the bottom row of images to skip to a specific assembly step.
On the final step, the user may begin logging completed units. There is logic to prevent the user from signing off the order until all units are complete, as well as preventing the user from logging more units than are required. The user can also log defects from any step in the assembly.
Once the order is complete, the user is prompted to review the production record and provide an Electronic Signature.
All of the data gathered in this application is stored in Completion data.
The user can log defects by selecting the component with the issue and declaring a quantity and reason.
The user can press the andon button which may be used to alert support staff that the area needs assistance and production has stopped.