Template Naming Conventions
There is no right or wrong way to name Templates. An organisation should do some research to decide what is right for your digital implementation. This will require some analysis of Inspections, Standard Jobs and work processes in your general day-to-day operations.
A good naming convention should be easily understood by all users. This covers not just the users that create checklist templates but also complete them on the mobile device. The naming convention should easily and quickly identify the checklist and what it does. It is not meant to be a description.
-
Keep the names short but meaningful.
-
Include unique identifiers, for example model numbers, if appropriate.
Example
1.
Name: CAT789 Monthly
Template Type: Inspection
2.
Name: CAT789 Monthly
Template Type: Work
3.
Name: CAT 789 Monthly
Template Type: Inspection
Example number 3 is not recommended practice, because the mobile user will not understand the difference between the checklists. The checklist name is unique however, due to the space between the T and 7.
-
Be consistent.
-
Site or Fleet designations may be important. For example, a D10 dozer that works in a hot, dry sandy environment may have a different inspection regime from one operating in a high altitude, wet mining operation. This would mean that there are two separate checklists written for this D10 with tags applied in the template for the different sites.
Example
Monthly Inspection on a Warman HTP Pump used on the Brisbane site.
| Item | Description |
|---|---|
| 1 | Location/Site |
| 2 | Frequency |
| 3 | Manufacturer |
| 4 | Model |
| 5 | Sizing/Capacity |