Data Capture provides the facility for users to define additional data metrics for consumption by Digitalised Work Instruction Platforms (DWIP’s). These metrics will define the questions within the DWIP’s presented to users while executing a work instruction document per activity (e.g. check engine oil)
Orien provides very flexible implantation allowing for easy integration but also standardisation across the system. Facilitating more accurate data with less variance or corruption.
Data Capture Flags
- Define properties of a specific data capture definition type.
- Values are provided at the data definition level.
- Special flags for data capture definition “options”
- Allowed value types: Text, Numeric, Dropdown, Boolean
- Example: Image Capture Type (Dropdown: Image, Photo, Drawing)
Data Capture Customisations
- Define properties for user entry at the Activity Level.
- Allocated to Data Capture Definitions
- Allowed value types: Text, Numeric, Dropdown, Boolean
- Example: Range – Max number value (Numeric)
Data Capture Definitions
- Define properties for user entry at the Activity Level.
- Links Flags and Customisations together to form a “template” users can be allocated against activities.
- Standardises the user input allowing for accurate data is self-service API
- Ability for the site to define an “approved” list of data captures that will be rolled out throughout the system.
- Define multiple “steps” of required data to complete the activity.
- Has an “Option” type which is captured at the DWIP layer. An example of this is the standard “1 | 2 | 3 | 4” response found on existing work instruction documents. These options have a description, code, and any special “Option Flag Only” Data Capture Flag values.
- Types available: Checkbox, Date, Image, Numeric, Option, Text, and Time. For example:
-
-
Definition: Temperature
-
- Step 1: Record oil Temp.
- Type: Numeric Type
- Customizations: Upper Range, Lower Range, Precision (provided per activity)
- Flags: Mandatory (true)
-
-
Definition: Temperature
-
User Guide for Data Capture Points
While viewing the Data Capture Definitions, you can view the Steps to see what activities these Definitions are Used In. The Used In button shows each location where the data capture is currently being used. This can be used to identify where a Data Capture point is used database-wide.
Steps
The steps assigned to each data definition are the stages of each data capture point that need to be completed.
Each step can be allocated to be one of the selected capture types. These are:
- Check Box
- Date
- Image
- Numeric
- Option
- Text
- Time
Customisations
Once the Capture type has been defined, you'll be able to apply any customisations that have been set previously to the data capture definition. These customisations can be configured to only appear for specific data capture types e.g. Lower Limit on a Numeric Capture Type.
Flags
Once the customisations have been selected, you'll need to fill in the Data Capture Flags that have been assigned to the Data Type. In the example below we have 3 flags assigned to the data capture type of Image: Forced Criticality (Dropdown), Forced Required (Checkbox), and Image Capture Type (Dropdown).
Allocating Data Capture Points
Now that you have created your components and associated activities, you can now allocate Data Capture Points to these activities.
Let's review the process in more detail.
- Choose the appropriate item in your hierarchy, select the Tactics module, and then the Data Capture Tab. This will show all activities in the structure and their assigned Data Capture Definition.
- Select the activity that you want to allocate to a Data Capture Definition, then select Allocate. Select which Data Capture Definition you want to allocate. Once allocated, you'll be prompted to input values depending on the Steps and Customisations assigned to the Definition.
Note
An activity can be allocated to multiple data capture points.
- Data Capture allocations can be edited by selecting the allocations and selecting Edit.
- Data Capture allocations can be exported, edited, and imported to edit multiple activities at once.