Comment on page
Runs are instances of activities in your manufacturing process
A Run is an activity or activities in your manufacturing process. In a simple case, a run is an instance of a procedure acted out in the real world. Technicians or engineers execute runs on real hardware on the factory floor.
A run is made up of a list of Run Steps. When creating a run from a procedure, all the procedure steps will be copied into the run along with their dependencies.
From here, click the green "Create runs" button in the top right of the page. ION will present a form that allows you to name the run, select the procedure to use for the run, set a due date, and assign it to someone at your company. You can also assign the run to someone at a later time. Once you create the run, it will appear as a new run that is in Todo.
You can also create runs in bulk via CSV, or bulk create them in the UI by clicking "Add Run". You can also make multiple copies of a run using the copy run button.
If you select a procedure for a run, it will be created with a copy of all the steps from the procedure. If you don't select a procedure it will be created with no initial steps. You can always redline in additional steps to a run after creation.
By default, choosing a part will create a new inventory for the run to build. You can optionally enter a serial or lot number. These can also be autogenerated. When this inventory is created, it will be created in
wipstatus to signify that is is being built. You can also instead link an existing inventory if you have an existing part that is getting work added to it. Toggle the "Use existing inventory" option to choose an existing inventory.
You can also use the Bulk create runs button to create runs in bulk from an Excel sheet or CSV file.
You can also create a run from a released procedure. Go to the procedure that you would like to use for a new run and select the "Create run" button next to the "Released" button. From here, ion will present a form to allow you to create a run. The procedure will be pre-populated in the run creation menu.
If a run is assigned to you, it will appear in your "Todos" list on the main application home page. Clicking on that "todo" will take you right into the execution screen for the step you are assigned to. From here, you can move your step from "todo" to "in progress" , input all of the requested data for the run (as defined in the procedure) in this run step, and finally move the step to "complete". Marking a step as complete will automatically enter you into the next step in the the dependencies tree. There are also options to put steps "on hold" and in a "redline" state.
You can also assign runsteps to different people than who the run is assigned to in order to more effectively manage your factory.
On Hold means that you need to pause progress on that step and to let anyone who views the run that there is an issue that needs to be worked out.
Redline allows the editing of a step in the middle of the run by someone with the appropriate role. This allows you to edit a mistake in a procedure or add information to the step execution.
If you accidentally make a run or want to stop work on a run, use the Cancel option in the run menu. This will cancel all remaining steps in the run that are unfinished. If you change your mind you can change the step states from canceled back to a workable state.
Cancel option in run menu
If you want to hide a run from the runs list, archive it using the Archive option in the run menu.
Archiving a run is permanent
Here's a quick video below on how to archive a run.