Release process

Before a maintenance procedure can be scheduled, it must be fully defined and approved. Until then, the procedure is considered a work in progress. Only after it is released can it be executed against assets.

Typically, these prerequisites must be met:

  1. All maintenance steps must be defined
  2. Images should be uploaded where applicable
  3. Spare part materials must be specified
  4. Planned hours must be allocated
  5. Competent personnel must be identified
  6. Required documents should be linked

Release version

After a procedure is complete, it must be released as a version. Only released versions are eligible for scheduling. In global deployments, released procedures are replicated across plants for execution.

Revisions

Any modifications to a released procedure require a revision. The revised procedure is edited separately while the current version remains in use. After updated, the revised procedure is re-released and becomes the new active version. All revisions are stored historically.

Delete and retire

Deletion of a procedure can be done only if no data has been recorded against it. After a procedure has been performed, deletion is no longer possible.

Retiring a procedure prevents it from being scheduled but retains all historical data. Retired procedures are excluded from default views unless explicitly requested in reports.