Incident Disposition Area

The Incident Disposition area of the Incident page contains information about the incident that occurred or the issue that may need to be addressed.

Note that the fields and features in this area depend on the configurable settings for the entity, and whether it is a new or existing record. Your implementation may have different fields enabled, with different names, and/or may be used in a different way that fits the needs of your organization.

Title and Description - a description of the incident is always required. If enabled for the current entity, you can also specify a short title.

Occurrence Date - the date/time when the incident occurred. (This field is required and cannot be disabled or hidden.)

State - the current state of the incident (e.g., "Open," "Under Review," "Closed," etc.). This may change over time as you proceed to review and address the incident. Click the History icon, , to view a list of all states that have been saved for the incident. (This field is required and cannot be disabled or hidden.)

Depending on the configurable settings for the entity, there may be special conditions for the state(s) that indicate the incident is closed. (See Closing an Incident.)

Report Type - how the incident was observed or reported (e.g., "Internal Testing," "Planned Field Event," etc.). (This field is required and cannot be disabled or hidden.)

Incident Category - for the purpose of reliability data analysis, some categories may be "chargeable" (e.g., "Component Failure," "Production Error," etc.) and others may be "non-chargeable" (e.g., "Customer Information Request"). (See Repairing and Replacing Parts.) (This field is required and cannot be disabled or hidden.)

Responsible Part - generic template part(s) that the incident pertains to. (See Assigning the Responsible Part(s).) (This field is required and cannot be disabled or hidden.)

Click the History icon,

, to view a list of any changes to the responsible part that have been saved for the incident.

Owner and Creator - if you do not specify the owner and creator, they will be set automatically upon save. (See Assigning the Owner and Creator.)

Team Members - the users who will be working on the incident, and their roles on the team. (See Assigning a Team.)

Actions - the specific assignments that need to be tracked and completed in order to address the incident. (See Assigning Actions.)

Failure Mode - if enabled for the current entity, the failure mode and root cause responsible for the incident.

Potential Criticality and Actual Criticality - if enabled for the current entity, criticality metrics are calculated based on the selections in the drop-down lists (e.g., schedule, cost, etc.) and the formulas specified by a system administrator. (See "Configuring the Criticality and Time Metrics" in the admin documentation.)

E-mail Link

	Related Topics:
	Incidents