Understanding work templates

The anticipated repair commitments (SOR codes) that are relevant to a broad range of works order fulfilment scenarios can be consolidated into a collection of work templates. For instance, through the creation of a specific work template, a baseline of SOR tasks might be cascaded down to specific asset classifications that are identified through an active void rule, the completion or cancellation of which being deemed mandatory before a void property is considered available for shortlisting. Once a void episode commences, the relevant tasks mapped to the matching template will then be automatically ascribed to the asset in the form of a consolidated works order. When creating such work templates, the well-established bulk selection window is available to map relevant SOR codes to the template definition en masse, expanding the applicable SOR table, component and repair type headings to access the associated task subset.

Work templates can also be employed in the efficient management of reactive repairs and planned maintenance upgrades, where consistent and accurate task instructions can be distributed to in-house resources as well as external contractors. As the variations between such templates may be only minimal, it is possible to clone an original template, retaining all the attributes (Priority, Repair Type, Analysis, etc.) and configuration settings for the applicable tasks, before applying the necessary adjustments to the specific scope i.e. adding, removing or editing individual SOR codes to refine the work instruction. When a series of repair tasks are generated against an asset in this way, they will inherit all the characteristics of the source work template, and adopting consistent naming conventions for the work templates in circulation ensures that SOR tasks are matched correctly to the applicable scenario.

See related topics...

To create a new repairs work template

To add a SOR code to a repairs work template

To add a materials part to a repairs work template