Within Zaptic, Units represent the hierarchy of factories or products, against which reports can be submitted.
An example of a common unit hierarchy within Zaptic can be seen below -
Location > Site > Department > Line > Machine
Each of the above groups are known as Unit Types within Zaptic, within which individual Units can exist.
When viewing the data management page as below, you can see the existing Unit Types.
After selecting a Unit Type, you can view more information about that Unit Type as well as seeing all the individual Units within. This is shown below, with the list of individual units towards to the bottom of the screenshot and the additional unit Information highlighted towards the left side.
Relationships between units
Individual Units are part of Unit Types, but these also have relationships with other unit types within the unit hierarchy.
This is enabled by the use of -
- Parents - The Unit type above / The Unit type one-step higher up
- Children - The Unit type below / The Unit type one-step lower down
As an example, if the hierarchy uses Departments > Lines > Machines as its Unit Types, then an Individual Unit within the Unit Type 'Lines' can have a parent from the Unit Type 'Departments' and a child from the Unit Type 'Machines'.
This helps form relationships between different parts of the hierarchy, as using this you will be able to see which units are part of which lines, and which lines are part of which department. These relationships between units often map-out the hierarchy within the site.
Unit Types as report subjects
Units are important as they are selected as the subject when you submit a workflow against them.
When authoring a workflow, you choose which Unit Type you want the users to be able to select Units from to complete the workflow against. An example of this would be Clean Inspect and Lubricate workflows, which can be created to use the Unit Type of Machines - which would allow the users to select from all machine units to choose the machine that the workflow is being completed against.
You would then be able to access the machine unit selected through data management, for example a Packer machine, and you could see all of the reports submitted against this specific unit. You could also view that units parent, to see what line that machine is a part of.
If accessing the report from the procedures page, you would be able to see the unit chosen as the subject, which would tell the viewer which unit the report was completed against. If they needed additional information about that machine, they can follow the unit hierarchy within the data-management tab to go up and see that machines line, then department and so on.