Procedures
Instructions for work to be done
Procedures are ways to record work instructions, data collection, and workflow in ION. Procedures are made up of steps and their child steps that define what work is to be done and what data is to be collected.
Users must have the engineer role to create and release a procedure.
Procedure edit view
To create a procedure, go to the Procedures section in ION. You will see a list of procedures created at your company. Click New procedure to create a new procedure.
Enter the title and description of your new procedure. Don't worry, you can change these while your procedure is still in draft.
Select a procedure type. Build procedures and Inspection Procedures have the same functionality, with one exception -- an inspection procedure can be used in an inspection run, which would be automatically created at the time of receipt of Purchase Order while using the workflow here.
You can only update procedures that are in draft. Once a procedure has been released, that version can no longer be modified. To modify a procedure, go to the Procedures section and select a procedure to modify. Now, you can modify the procedure's steps, attachments, and data collection fields.
Procedures can have multiple steps. Each step has its own content, attachments, and fields. During a run, each step will be presented in the Technicians view in sequence.
Procedures are version-controlled, and runs use specific versions of procedures, so that the exact procedure that was used in production is always traceable. There can only be one version of a procedure in draft for a given procedure. From a released or archived procedure, you can "Create new draft", which will create the next incremental procedure version in draft.
When you are done updating a new version of a procedure, you can submit it for review. In the procedure action selector, select "For review". From there, you can add the reviewers who should review the procedure.
Reviewers will see the pending review requests in their home dashboard. Clicking into the review request will take the reviewer to the procedure to leave a review. Once all reviewers have approved the procedure, it will be automatically set to "released" so that it can be used in production runs.
Last modified 10mo ago