This document describes how to set up an as-built structure and report meter readings on an equipment with several similar systems installed, when each of these installed systems can be used independently of the other. For instance, several rock drills installed in the same equipment when either one of them or all of them can operate at a given date and time.
The most common scenario is one where meters are defined and their readings are reported on the main equipment/operational unit and the same meters are cascaded down the as-built structure. The scenario described in this document is an exception to the normal scenario. In this case, the meter readings must only be cascaded down within a specific leg of the structure.
All preconditions specified in these documents must be satisfied:
A one-to-one relationship must exist between a placeholder position and an item to ensure that the placeholder item and serial numbers are automatically created in the as-built structure.
In 'Model/Site. Open' (MOS400), specify 'System level reporting' in the 'Model' field.
In 'Model/Site. Connect Position' (MOS440):
For each of the systems where meter readings should be reported, specify 'Meter reporting level' in the Position field.
For each position where a real physical component is not installed, select the 'Placeholder' check box.
In 'As-Built Structure. Open' (MOS256), select function F15='Create Positions'. For configuration positions marked as placeholders, serialized items will be automatically created, with the same item as the configuration position and the same serial number as the main equipment. The positions will then be filled in (MOS256) with this serialized item.
A check for additional placeholders at a lower level in the structure (sub-assemblies) is systematically performed and serialized items will be created for these in the same way. This functionality assists the user by populating all placeholder positions automatically and removes the need for manual intervention in (MOS256).
The meters for the equipment must be identical for the complete structure, for instance, calendar meters such as days, months, and so on.
In addition, the equipment must have a calculated meter as the sum for all systems. For example, 'Impact hours total (IHRS T)', which is the sum of all 'Impact hours (IHRS)' reported on the different systems and will be used for meter based invoicing.
The calculated meter '(IHRS T)' must be set up in 'Meter. Open' (MMS051) and have an associated calculation program in 'Meter Calculation Program. Open' (MMS052). For example, for impact hours, specify the 'Meter' as 'IHRS' and the 'Operator' as 'S-Sum up to operational unit'.
The system level reporting entities and all components below must have meters that are independently reported for each leg, for example, 'Impact hours (IHRS)', 'Drilled meters (MTRS)', and so on. These are the meters that will drive service requirements planning.
This diagram illustrates how an as-built structure could be configured to support the collection and aggregation of meter readings from a specific leg of the structure that spans all levels of the as-built configuration:
In 'Operation Plan. Open' (MOS380), the forecast for a meter must be defined for the system level reporting entities. This ensures that service requirements planning functions as required.
Meter reporting is performed using sorting order 12='Position' in (MOS160). With this, all configuration positions defined as 'Meter reporting level' will be listed with the installed reporting entity, item, serial number, and meter. One line for each meter in an open sub-file will be reported, allowing meter readings to be directly reported on the B panel.
Current meter readings for the operational unit can be displayed in 'Equipment/Ser Item. Open Meter Reading' (MMS241), using sorting order 2='System lvl rpt'. All meters for the operational unit and reporting entities will be displayed.
Corrections can be performed in 'Model/Site Individual. Open Op Cycle Readings' (MOS271) and API MOS160MI, CorrMeterRead. In this case the 'Model/Site Individual. Open Op History' (MOS270) and (MOS271) records are created against the reporting entities/serialized items instead of the operational unit.
In 'Work Request. Open' (MOS170), the remaining time calculation is different in this scenario. As the operational unit does not have the same meters as the installed components, you cannot show the remaining time for the operational unit on (MOS170/F). Instead, the functionality of the virtual fields '&MVB0' and '&MES0', selectable in the dynamic views, is used. In this scenario, '&MESO' displays the selected meter of the component and '&MVB0' displays the remaining time for the selected meter of the components. This allows the planner to keep track of both due date and remaining time and also to plan for the service to be performed before the meter reading due date.