Related Topics:
	Customer Support

Customer Support Summary Area

The Customer Support Summary area of the CSI page displays the unit commissioning information that has been defined for the customer support record. This area is not displayed while you are creating a new customer support record.

Note: The fields that appear in the interface are based on the currently selected entity, and can be configured (including names and any options available for selection) by the system administrator. This topic is not intended to be a comprehensive guide to all possible fields. Instead, it provides additional information on some commonly used fields in cases where the field's purpose and/or functionality may not be readily apparent.

• Time Metrics Field displays up to three types of time measurements that have been reported for the unit at the time of the incident. Note that the XFRACAS system administrator maintains the time metric field names. Therefore, the name of the Time Metrics field used in your system may be different and, depending on the settings chosen by the system administrator, this field may display one, two or three time metrics. The system default is Run Hrs/Starts, which displays the total system hours and the number of starts that have been reported for the unit at the time of the incident. You can click the Add icon, , to add a report on system hours and/or starts. You can click the link to display the System Run Hours utility, which displays a summary of all system hours and number of starts reports that have been made for the unit. System hours reports that were made manually (i.e., that are not from an incident) can be deleted from this table.

• System Status displays the current operational status of the unit based on the highest status code for all the incidents associated to the serialized system. The rankings of the status codes are determined by the system administrator. If there are multiple incident reports applying to the system, the overall system status is determined by the system status with the highest precedence. For example, let us say that the list of available statuses contains (in order of increasing precedence):

• • Available

  • Idle

  • Running - Needs Service

  • Down - Waiting on Service

If there are two incident reports applying to the system, one with a status of Running - Needs Service and one with a status of Down - Waiting on Service, the overall system status would be Down - Waiting on Service. Once the service is applied to that incident, the system status would change to Running - Needs Service.

• System Configuration provides a link to the Serialized page for the unit.

• MTBF/MTBFE displays the mean time between failures (based on reported hours and based on estimated system hours) for the system, assuming a constant failure rate.

• MTBCF/MTBCFE displays the mean time between chargeable incidents, or failures (based on reported hours and based on estimated system hours), for the system, assuming a constant failure rate.

• MTBNCF/MTBNCFE displays the mean time between non-chargeable incidents, or suspensions (based on reported hours and based on estimated system hours), for the system, assuming a constant failure rate.

• MTBI/MTBIE displays the mean time between incidents (based on reported hours and based on estimated system hours) for the system, assuming a constant failure rate.

• Chargeable Incidents displays the total number of chargeable incidents (failures) for the system.

• Non Chargeable Incidents displays the total number of non-chargeable incidents (suspensions) for the system.

• Under Warranty displays an indication of whether or not the unit is currently under warranty and, if applicable, the expiration date of the warranty period.

• Operational Availability displays the percentage of total time during which the system was not down. Total time is the time from when the unit was commissioned, shipped or built. Downtime is the time between occurrence dates and repair dates for all incidents on the system. If the System Down Event incident detail is available in the current entity, only incidents for which that detail is checked count toward downtime; otherwise, all incidents are considered. Note that if no repair date is given for an incident, the system is considered to be down from the occurrence date on.