Skip to main content

Observations

Jérémy Martinez avatar
Written by Jérémy Martinez
Updated this week

Definition

"Observations" are one of the fundamental pillars of an element's compliance, since for equipment to be compliant, it must not have any observations that would result in non-compliance. An observation is an anomaly, a remark or a reservation made by an inspector during an inspection and included in the inspection report for an item. It may or may not result in non-compliance.

Utility

"Observations" allows each user to implement a compliance action plan, distribute observations to the various parties involved, and document the resolution of observations.

Functionality

"Observations" consists of the following fields:

This observation:

  • Characteristics:

    • The element: Information about the item concerned by the observation.

    • Data from the report: Information relating to the observation noted by the inspector.

    • Processing: Information relating to the action plan for resolving the observation.

    • Integration: Information from the report to be integrated into the CMMS system.

Related objects:

  • Elements: list of element related to the observation

  • Documents: list of documents related to the observation

  • Maintenance intervention: list of maintenance interventions related to the observation

"Observations" is broken down into several parts:

  • "All": List of all observations, regardless of status.

  • "To be planned": List of observations for which maintenance intervention is to be planned

  • "Scheduled": List of observations for which maintenance has already been scheduled.

  • "Completed": List of observations that have been resolved.

  • "No Action": List of observations that will not be resolved for various reasons (lack of resources, action not feasible or relevant, etc.).

You can perform various actions in "Observations", such as:

Which package?

"Observations" is available in

.

Did this answer your question?