Investigations application
You use the Investigations application to address unresolved defects and incidents. The goal of an investigation is to prevent or minimize the impact of future similar defects and incidents.
In the Investigations application, you can perform the following
activities:
- Classify an investigation as worldwide, regional, or local.
- Delegate and track activity work orders for the investigation.
- Report time spent on the investigation and its activities.
- Use failure classes and failure codes to identify trends and isolate the probable cause of failure.
- Specify and describe component-level failures.
- Specify and describe failure mechanism codes in support of ISO 14224.
- Specify the method or activity by which failures are discovered, including barrier failures. You can also specify the type of barrier that failed.
- Specify audit and survey records to track originating events.
- Specify safety-related system failures, such as safety-critical or hardware failures. You can specify a reference to an element that is associated with a regulation, such as a performance standard. You can also indicate that the failure requires action to maintain system integrity.
- Associate existing solutions and lessons learned with investigations.
- Record the results of after-action reviews, root cause failure analyses, and failure mode effect and criticality analyses.
- Add the sequence of events that occurred, and information about witnesses to the events.
If the investigation requires follow-up tickets or work orders,
you can generate the following types of records from this application:
- Action
- Communication
- Improvement
- Incident
- Investigation
- Management of change
- Management of change request
- Release
- Risk assessment
- Service request
- Work order