Service Patterns are created and managed using a tree structure interface consisting of three layers:

 

Layer 1: Service Group

'Service Groups' represent the top layer of the servicing patterns which can be applied to Assets.  In other words each Asset in the fleet can be linked to a single 'Service Group' to define the services which apply to it.  For example, Service Groups of '5 Weekly Safety' and '6 Weekly Safety' can be defined.  A single asset can belong to either the '5 Weekly Safety' or the '6 Weekly Safety' group.

 

Layer 2: Cycles within Groups

'Service Groups' contain 'Cycles'.  'Cycles' are used to group items that operate independently of each other.  Within the '5 Weekly Safety' group for example two 'Cycles' could be defined - one which includes Safety Inspections and another which included Tachograph checks and Re-calibrations.  If the pattern of the Safety Inspections were to be changed the Tachograph Checks would not be affected.

 

Layer 3: Service Types within Cycles

Within each Service Cycle any number of 'Service Items' can be linked.  Note that 'Service Items' that are linked to Cycles are picked from a list of 'Service Types'.  A single 'Service Type' can be linked within a single Cycle many times.  The way in which they are linked defines:

• the interval from the service item above it,
• the duration of the service,
• the analysis codes including 'Type', 'Sub-Type', 'Component' and 'Reason'.