HSQE managers
Own the change register, prepare revisions and chase acknowledgments across the fleet
- The places a change lands, mapped by agents
- Checklists a search misses, found before audit
- Acknowledgments counted per person, not by scan
Features
Safety management system shipping software, from audit finding to crew answer
HSQE managers, technical superintendents and the DPA work through them to carry one change through the SMS manual and the fleet. The screens follow a crane rule across a bulk fleet.
demoThe manager, its fleet, the crew, documents and numbers on screen are sample data.
- 01Change ripple
One SMS change mapped as rings of procedures, forms, ships and people aboard
- Each place a change lands, on one screen. The HSQE manager sees the procedures, forms, ships and people a rule or finding touches before drafting a word.
- Rings that fill as work is approved and acknowledged. Progress reads from the center out, so a gap on the ships ring is a master who has not confirmed the old copy removed.
- Each agent's step, source and confidence beside the map. The HSQE manager sees what each agent read and how sure it was before relying on its work.
- 02Impact search
Impact search across the SMS manual by equipment, then by ship and crew
- Manuals, forms and checklists found by subject. The search reads for the equipment and the step, so a change reaches documents filed under other headings.
- A confidence beside each finding. The HSQE manager sees which finds are less certain and where to look twice before any drafting starts.
- 03Auditor's read
Draft revisions read as a flag or class ISM auditor would, before signing
- Points written with the question the auditor would ask. The HSQE manager meets likely ISM audit findings while the revision can still change.
- Drafts by the agents held to the same test. A step dropped from a drafted section is caught and restored before any signature.
- Points for people sent by name. Each decision the agents may not take reaches the person who owns it: the DPA, the HSQE manager or the superintendent.
- 04Redlines
Each revision redlined change by change, with a source on each change
- Deleted and inserted text on the company's own page. Reviewers read the revision as it will look aboard, header block included.
- A source under each change. The reason for a change travels with it, so nobody hunts through email during an audit.
- 05Maker request
Current manual and test intervals asked of the equipment maker in fixed fields
- Fixed fields set against what is on file. The value on file sits beside each question, so the superintendent sees which intervals rest on an old manual revision.
- Draft changed only through the fields. Only an answer in a fixed field or an attached extract can change the procedure; free text from the maker goes to a person.
- Open until the maker answers. The request shows sent and waiting with its due date, and the sections that rest on it wait with it.
- 06Technical review
Technical review held until the maker's answer reaches the draft
- Review held while the maker's answer is open. A section that rests on the maker's manual cannot pass technical review while its test interval is still a question.
- Sign-off chain with each reader's progress. Technical review, preparer and approver show who has read how much of the package before anyone signs.
- Planned maintenance point for the superintendent. Ships already past their renewal survey are listed beside the draft, so the superintendent books their first annual crane examinations in planned maintenance.
- 07Crew question
Crew questions answered only from the revision in force on that ship
- Answers cite section and revision. A crew member follows the procedure that applies aboard today, never a draft or one the ship has not yet received.
- Equipment calls left to named people. Asked whether a crane may be used, the assistant quotes the procedure and names the master and the superintendent.