VIC 7.1 DIGITALISATION — APPLICATION NOTE ========================================= Leon Steer · C. Steinweg Oman, Port of Sohar · 1 October 2026 A working prototype of the VIC exists and can be clicked through. This note sets out what it already does, what it still needs, what the technical assessment will want to know, and the points in VIC 7.1 that have to be settled before those parts can be built. What the application already does --------------------------------- - The three checklists. All inspection points in English and Arabic, with a remarks field on each. - Handheld first. Built for the Zebra handhelds used at the berth; also works on a desktop browser. - Works without signal. Answers are held on the device and sent when the connection returns. The screen shows what is still waiting. - Defect recording. An answer of No opens a mandatory note. A defect without a description cannot be signed off. - Electronic sign-off. Signed with the account the user is logged in to, with the date and time recorded automatically. A second signature is captured as a typed name, stored separately so the two are never confused. - Record is immutable. Once signed, answers can no longer be changed — by anyone. A correction means a new inspection. - Audit trail. Every answer, change and sign-off is recorded with who and when. - Management overview. Which vessels are blocked right now, and the trend over the last weeks. - Print and save as PDF. From the completed record. - User guidance. An in-app manual covering each screen. What it still needs for VIC 7.1 ------------------------------- - VIC 7.1 content. The 7.1 inspection points loaded in place of the current set. - Photographs and evidence. Upload against an inspection, with the storage location to be decided by the technical assessment. - Gas test record. A record in its own right with its own signature. - Re-visit. The re-visit register and its separate sign-off. - Full signature set. VIC 7.1 lists four signatories; the application captures two. - Automatic PDF. Generated on sign-off rather than printed by hand. - Controlled distribution. Emailed to a defined list when a record is closed. For the technical assessment ---------------------------- - Application. Node.js web application (Next.js). Ships as a Linux container image, around 200 MB. Stateless — it can be restarted or scaled without losing anything. - Database. PostgreSQL today. The data layer is Prisma, so Azure SQL or SQL Server is a configuration change rather than a rewrite — worth testing rather than assuming. Roughly 400 rows per completed inspection. - File storage. For photographs. Blob storage or a mounted share, set by connection string. Nothing is written to the application server itself. - Outbound mail. An SMTP relay, for distribution of the completed record. Optional — without it the application still works, it just does not notify. - Sign-in. Local accounts today. Entra ID is the preferred route; the application already identifies users by email address so that the two can be matched. - Roles. Four roles exist in the data model. Which rights each one carries is for this project to define. - Devices. Zebra handhelds at the berth, desktop browsers in the office. No installation on the device. Open points that affect the build --------------------------------- Each of these is a build decision that VIC 7.1 does not settle. They are listed as questions rather than answered here, because the answers are operational rather than technical. - Do all four signatures have to be present before a record is closed? VIC 7.1 states: "VIC to be signed off by: Chief Officer (Vesse Stamped/date/time) · SV4-3 · GSV · HSE & Tally SV". Whether the application must refuse to close a record until all four are captured, or allow it to be released with some outstanding, changes how the sign-off screen behaves. - Is a re-visit part of the same record, or a record of its own? The re-visit register on the form holds: Revisit #, Date, Time/shift, Conducted by, Signature — and it is signed off by three signatories rather than four. Whether that attaches to the original inspection or stands alone decides how records are stored and retrieved. - What does a gas test attach to? To the vessel visit, to a specific hold, or to a crane. This decides where the record lives and how it is found later. - Which answers, if any, must stop the vessel? The application today refuses to release a vessel when certain items are answered No. We have not found anything in VIC 7.1 that designates which items those are, so that rule needs confirming before it blocks anything in practice. - What does a photograph attach to? The inspection as a whole, a single question, or a defect. This decides whether a photograph can be found from the record later. - Retention and distribution How long a completed record is kept, and who receives it when it is closed.