Getting Started

The Audit & Inspect module covers four areas — audits, inspections, management of change and conditions of class — which are processed in the same way and may be split across HSSEQ and Technical. What the module contains and how a report is created is described in the documentation under Audit & Inspect, with the screenshots for each step.

This page gives the order in which the subject is best learned. For the way an inspection runs from planning to final verification, see the Inspection Workflow.

Suggested order

1. Find out how your installation is set up. The four areas can appear as one module under HSSEQ, or split — audits and management of change under HSSEQ, inspections and conditions of class under Technical. Whoever looks for inspections under HSSEQ on a split installation does not find them, and that is the setup, not a fault.
2. Understand the difference between New and New (additional) before creating the first report. New puts the report into the planning routine; New (additional) deliberately leaves it out. Correcting this afterwards is more work than deciding it beforehand.
3. Decide whether the type works with a questionnaire. With one, findings come from the questionnaire and are not entered on the deficiencies tab; without one, they are entered there directly. See Add Report.
4. Fill in the details completely, then use Get Title. The title is built from the data — pressing it too early produces a wrong title, and the system does not check it afterwards.
5. A report without findings still has to say so. Tick no deficiencies found and save; a report that is simply left empty is not finished.
6. Then look at the follow-up: findings get a responsible person and a due date, are completed on board, and are confirmed by the office afterwards. Completed on board is not closed.
7. Learn the icons last, once the process is familiar — the legend makes far more sense when you know what the states mean.

Good to know beforehand

A report can only have one inspector, internal or external. Internal ones are picked from the list by rank, external ones typed as free text.

Master and chief engineer come from the crew list with Get. Without a crew list in the system, both are entered by hand — so an empty list here means the crew list, not a broken field.

Closing the questionnaire is what creates the items. Until then there is nothing to assign, and that is why responsible persons and due dates are given afterwards, not during the inspection.