Data collection fields

You can include data collection fields that you want to collect when the Procedure gets executed in a Run. For example, let's say you want to know the running torque value for every run that uses a given Procedure. You can define that field in the procedure, and the technician/operator will input that when she/he executes the run.


The date and time for a certain event. Use this field to track events and their times in production. For example, if you want to track when something was put into a thermal oven.

Boolean (checkbox)

True or false. This gives the operator a simple option for whether something is true or false. For example, use this field for a simple pass/fail data collection.

String (text)

A simple text field data collection field. Useful for freeform responses from the factory floor.

Number - includes the unit for data collection

Similar to a string, except this field type enforces that the data collected is a numerical value. Unlike other fields, number fields can have calculations, i.e. validations. See the Validations section below for more information on how to use validations to automate checking values in operation.


Use this to provide a list of options to select on the floor. The select field only allows one response. For more responses, use multiselect.


A list of options which allow for more than one items to be selected in operation. This is useful if you want to collect multiple attributes or conditions from the operator. For example, "scratched", "bent", and "discolored" can all be multiselect options, and it might be that the operator found all three attributes to be true.


See the Signoff fields section below for more detail.

File attachment

Use this to attach a file. You can, of course, use the attachments in the run step, which is a lot more flexible and preferred. A file attachment field type can be useful when you know that you want a very specific file, such as a CSV upload from a machine or similar.

Signoff fields

Signoff fields allow procedure builders to define signoffs required on a step to ensure quality. Signoffs are defined by role, which is then enforced during the Run. For example, a procedure builder can define a Procedure step requires someone with the Quality Inspection role to signoff before continuing. During the run, Quality Inspector Susie can signoff on the step, but Assembly Technician Michael cannot. ion maintains that Susie signed off on the field with a digital signature.

As a workspace admin, you can manage which roles exist in your organization and who has which roles in your organization settings.

Creating an "engineer" signoff field in the Procedure editor
Signoff verification in Run summary

Field validations to automate calculations in the operation

Number fields in ion allow for setting up validations, or calculations, to automate numerical checking out on the floor. This is very useful for setting up conditions for passing. For example, if a torque value must be within a certain range, such as greater than 5 ft-lb but less than 10 ft-lb, you can use validations to set up your limits. Validations automatically run when a value is input in a run. If you have the relavant organization settings for automatically creating an issue when a value exceeds the criteria, an issue will automatically be created in ion.

Setting up validations in the procedure fields definition
Automatic indication when a value exceeds the setup validation criteria set in the procedure