Incidents

Use the Incident page to record and view information for a single occurrence of an issue (e.g., failure, planned downing event, customer request, etc.).

If you have permissions to create a new incident, choose Home > Create > Incident.

If the incident wizard is enabled for the current entity, the page will either display all fields in a single form or a wizard that prompts you to enter data one step at a time. To toggle the display, choose Use Incident Wizard, , or Use Single Form, .

After you have entered all required fields (highlighted with red boxes), choose Home > Create > Incident to save the new record.

Selecting or Identifying the Entity

If your XFRACAS website has more than one entity, the fields and options may be configured differently in each. When applicable, a drop-down list at the top of the page allows you to select which entity is currently active before you create a new record.

When you are viewing a record that already belongs to a particular entity, the name of the entity will be displayed at the top of the page and the entity will also be reflected in the prefix for the record ID.

Selecting the Incident Type

Depending on the settings for the current entity, you may choose from up to three incident types.

Serialized Incident - an incident for a specific serialized system.
Part Incident - an incident that is tied only to a part number, not a specific serialized system.
Simple Incident - an incident that is not tied to any particular serialized system or part number.

Areas and Fields

The fields in the page depend on the incident type and the configurable settings for the entity. The following topics discuss some types of fields that may be used in each area of the page.

Incident Summary area - a summary of key details for an existing incident.
System/Component Information area - in a serialized incident or part incident, information about the system or part that the incident applies to. (The area will also appear if there are custom details within this section.)
Incident Disposition area - information about the incident that occurred or the issue that may need to be addressed.
Incident Repair Information area - information about what was done to resolve the issue, including details for any parts that were repaired, replaced, removed and/or found to be failed.

If the system administrator has configured additional fields to meet your organization's specific needs, they may be integrated into the areas mentioned above or grouped together in a separate Incident Details area at the bottom of the page.

Selecting the Serial Number and/or Part Number

In a serialized incident or part incident, there are multiple ways to specify the system or part that the incident pertains to. (See Part and Serial Number Selection Utilities.)

If the incident is not related to a specific system or part, you can leave the fields blank. Alternatively, you can hide the "System/Component Information" area by selecting "Simple Incident" for the incident type.

If you choose to specify this info, it cannot be changed after the incident is saved.

Assigning the Responsible Part(s)

The Responsible Part field identifies the part(s) that caused the incident to occur. If the settings for the current entity allow you to select multiple parts, click the Edit icon, , to view the tree. If the settings for the current entity don't allow multiple parts then you will just see a drop-down list of parts that have a responsible engineer assigned to them.

This field uses the generic system Template(s) that have been defined for the entity. Each template part can be associated with an Owner who may receive an e-mail when the part is assigned as a responsible part for an incident. This user may also be assigned as the Owner for the incident, if applicable.

Click the History icon, , to view a list of any change to the responsible part that have been saved for the incident. (This field is required and cannot be disabled or hidden.)

Assigning the Owner and Creator

If you create a new incident without selecting the incident owner and creator, they will be set automatically when the record is saved.

The Owner will be set to the user who is responsible for the first responsible part.
The Creator will be set to the user who created the incident.

You can use the drop-down lists to change this at any time.

Assigning a Team

If enabled for the current entity, the Team Members field identifies the users who will be working on the incident, and their roles on the team. This field is not displayed until the record is created.

Click the Assign/Remove icon, , to select the users and their roles. (See Assign Team Members Utility.)

After users have been assigned to the team, you can click the link for any team member's name to send an e-mail regarding the incident. (See Send E-Mail Utility.)

Depending on the configurable settings for the entity, the team members may also receive e-mails when a status update is added or modified. (See Adding Status Updates.)

Assigning Actions

The Actions field contains a list of specific assignments (tasks) that need to be tracked and completed in order to address the incident. The field is not displayed until the record is created.

Click Create New Action, , to add a new assignment for the current incident. (See Actions.)

The table displays the actions that have already been assigned. Click the action number link to open the action window, or click the expand icon, , to show more of the details in the table. Click to view the list of actions in a report grid that you can filter, sort, export to Excel, etc.

Adding Status Updates

If enabled for the current entity, a Status detail field allows users to add notes about the progress made for the incident, and also send e-mail notifications if applicable. This type of field is not displayed until the record is created. (See Status Fields.)

Associating Files or Links

If enabled for the current entity, an Associated Files detail field allows users to upload file attachments, links to files in another location (e.g., a document management website) or link to another record in XFRACAS. This type of field is not displayed until the record is created. (See Attachments.)

Repairing or Replacing Parts

The Repair or Replace Parts feature allows you to list all the parts that were repaired, replaced, removed or found to be failed due to the incident (if any). If you are extracting data to Weibull++ or RGA, this is used to obtain failure and suspension times based on part number. (See Repairing and Replacing Parts.)

Assigning an Incident to a Problem

The Assigned to Problem # field in the incident summary links to any problems that the incident is associated with.

Click Create New Problem, , to create a new problem record and automatically assign the incident at the same time.

Click Assign/Remove Problem, , to assign the incident to an existing problem or change the problem(s) that the incident is currently assigned to.

Closing an Incident

Depending on the settings for the current entity, the incident's State field may contain one or multiple options to indicate that an incident is closed (e.g., "Closed," "Closed - Insufficient Data," etc.).

You may not be able to close an incident until all associated actions are completed and/or all associated failure analysis reports are closed.

The incident may be "read-only" after it is closed. When that preference is enabled, only users with specific permissions will be able to re-open a closed incident.

Tip: If the incident pertains to a serialized system that you are also tracking via the Customer Support page, we recommend to update the System Status (e.g., "Running," "Down - Waiting on Part," etc.) before you close the incident. The system status displayed in the CSI page will be based on all incidents reported for that serialized system.