Understanding Service History Types
Service history types define the main attributes for service history of a certain type. Types might include maintenance, inspection, service, test, measurement, and so on.
Service history types are defined by the following:
• Service History Business Object: The business object used to create service history records of this type.
• Category: The category to which service history records of this type belong. The base package includes the following categories:
◦ Downtime
◦ Failure
◦ Inspection
◦ Maintenance
◦ Repair
• Subclass: The specific subclass of the service history type, based on the Service History Business Object. Oracle Utilities Customer To Meter supports two subclasses of service history types:
◦ Operational Device Service History
◦ Questionnaire Service History
Each service history type subclass includes other specific configuration information, outlined below.
Operational Device Service History Types
Operational Device Service history types are also defined by the following:
• Service Schedules: One or more template work orders and time intervals that should be used to schedule work order generation for service history records of this type
Questionnaire Service History Types
Questionnaire Service history types are also defined by the following:
• Follow-up Actions: One or more actions intended as “follow-up” actions for service histories of the service history type, such as work orders or work order activities, users can configure those follow-up actions on the service history type. Note that if a regulatory compliance requirement is associated with a follow-up action, a compliance type must be specified. For example, a Service History Type of “Grade 2 Gas Leak”, might include a follow-up action of “Recheck” which could be configured with a “30 day” Compliance Type and a follow-up action of “Repair” which could be configured with a “1 year” Compliance Type.
• Stop Processing Service History Type: One or more service history types that should stop the processing of Follow-ip Actions. For example, certain problem that needs follow up actions was reported. Then another service history, which indicates the problem has been fixed or its severity has changed, is recorded. Businesses might want to stop/cancel the follow up actions based on the original problem/severity.
• Questions: A list of one or more questions used to guide inspection of an asset. Questions are defined in the Questions portal.