Industrial Guided Task standard form
The following table describes the field values for the Industrial Guided Task standard form.
| Field | Description |
|---|---|
| Number | System-generated unique number for the standard. |
| Category | Enables you to differentiate between processes in a factory. |
| Allow ad-hoc request | When enabled, it enables you to initiate tasks directly from the Standards hub. |
| State | Automatically set to Draft, not editable. |
| Task expires after | Can be None or Custom time. |
| Custom time for expiration | Available if Task expires after is set to Custom. Specifies the custom expiration time for the task. |
| Enable scoring | When enabled, it enables the score field to be displayed and used on guided tasks. |
| Target score |
A numerical value (float), which represents the desired score set as a performance goal. If a target score is set, the score status indicates whether the task result is Successful or Unsuccessful. If no target score is set, the score status is set to No target available and only the total score is displayed on the guided task. |
| Short description | Short description or title for the standard. |
| Owner group | Group of users who own the standard and can approve it. |
| Author | Auto-populated with the name of the user who initiated the process of creation, can be edited. |
| Document scope | Specifies whether the standard applies to a single site (local) or across all sites (global). |
| Location | Required for the document scope local. Factory that the standard is used for. |
| Material classifications | Groups of materials based on their properties and applications. Stored in the Enterprise model classification [sn_ent_model_classification] table. |
| Material models | Categories of finished goods based on the materials they are made from. Stored in the Enterprise good models [sn_ent_model] table. |
| CMDB assignment type | Options are:
|
| Functional locations | Work area where the standard is executed. |
| Equipment models | Group of equipment items. This field is required if the CMDB assignment type is set to Equipment models. Available options vary depending on the selected functional location. Note: To make the filtering by equipment model work, make sure that the equipment is related to the equipment model. This connection is established by using the model ID reference field to establish the relationship. When you select a functional location, this relationship is then used to filter down the equipment models. |
| Equipment | Piece of equipment or machinery used to execute the standard. This field is required if the CMDB assignment type is set to Specific equipment. Available options vary depending on the selected functional location. |
| Failure modes | Failure mode to which the standard relates. Available options depend on the selected functional location or equipment. |
| LOTO level | Lockout/Tagout safety procedures with possible values of 0-3. |
| Line status | Information about the status of the production line. Options are:
|
| Required skills | Defines the set of skills required for task eligibility. Only operators with these skills can perform the task. |
| Knowledge Article | Knowledge articles that are related to the standard and provide more information about the standard for the operator who executes the task. |
| Attachments | Attachment that can be used for descriptive purposes. |
Insights Overview tab
The Insights Overview tab displays embedded shopfloor insights for the published standard. This tab is visible on every IGT standard record in the Digital Factory Workspace when the standard is not in Draft or Review state.
| Filter | Description |
|---|---|
| Functional location | Filter by functional location. All available functional locations are displayed by default. You can manually select the functional locations, which you want to filter. |
| Equipment | Filter by equipment. Only equipment relevant to the selected functional location is shown. |
| Date filter | Filter by time period. Options include:
|
| Version | Filter by standard version to compare execution results across versions and track how changes affect performance. |