A marine survey and inspection company — whether it's running hull thickness gauging on bulk carriers calling at Houston and Gulf Coast ports, condition surveys ahead of a sale, or NDT work supporting newbuild inspection at a shipyard in Canada — operates under a set of workflow requirements that don't map onto a typical field-services business. Surveyors work against class society rules that differ by flag state and society, vetting inspections follow tanker-industry-specific protocols, and a single vessel call might require coordinating a surveyor's travel, port agent scheduling, tide and berth windows, and same-day report turnaround before the vessel sails. Generic ERP or job-management software built for landside industrial inspection work usually has no concept of any of this. Here's what actually needs to be built into a system supporting marine survey and inspection operations.
\nThe International Association of Classification Societies (IACS) is the umbrella body whose member societies — ABS, DNV, Lloyd's Register, Bureau Veritas, ClassNK, RINA, and others — set and enforce classification rules that determine a vessel's structural and mechanical fitness to operate under a given flag. Each society publishes its own rules for hull surveys, and the timing of special surveys (typically every five years), intermediate surveys, and annual surveys is governed by the vessel's class notation and age, with additional requirements kicking in under the IACS Common Structural Rules and enhanced survey programs for older tonnage. A survey company doing thickness gauging or structural NDT work in support of these surveys needs its records organized around vessel identity (IMO number, not just a job number), class society, survey type, and due-date windows that are vessel-specific and society-specific — not a generic \"next inspection date\" field borrowed from a plant-inspection template.
\nThis matters practically because a single survey company might be working under an ABS special survey scope on one vessel and a DNV intermediate survey scope on another in the same week, each with different reporting formats, different acceptance criteria for gauging results (IACS Unified Requirement UR Z10 series governs hull survey and thickness measurement standards that member societies reference), and different documentation the class surveyor attending on behalf of the society will expect to review.
\nTanker vetting inspections — run under frameworks like OCIMF's SIRE (Ship Inspection Report Programme) and TMSA (Tanker Management and Self Assessment), or the dry-bulk equivalent RightShip inspections — are commercial risk assessments charterers and oil majors use to decide whether to fix a vessel, and they operate on an entirely different cadence and documentation standard than class surveys. A survey or inspection company supporting vetting work needs to track inspector accreditation separately (SIRE inspectors, for instance, go through OCIMF's own accreditation and observation process, distinct from ASNT NDT qualifications), manage report submission into the SIRE VIQ (Vessel Inspection Questionnaire) database format, and handle much faster turnaround expectations — a vetting inspection often needs to be reported within days because it's gating a charter decision, not a five-year class cycle.
\nRunning both classification-support NDT work and vetting-adjacent inspection work through the same operational system means the ERP needs to cleanly separate these workflows rather than force them into one generic \"inspection job\" template. Mixing up a class survey due date with a vetting inspection expiration is the kind of error that looks small on a spreadsheet and becomes a real commercial problem when a charterer finds an expired vetting report during a fixture negotiation.
\nSurvey and NDT work supporting newbuild construction — increasingly relevant for companies working with shipyards in the US and Canada, as well as coordinating remote or third-party inspection oversight on vessels built overseas — follows yet another distinct workflow from in-service class surveys or vetting inspections. Newbuild NDT typically involves weld inspection (radiography and ultrasonic testing on hull and structural welds per the applicable class society's construction rules and often referencing AWS D1.1 or an equivalent structural welding code for specific joint types), progressive inspection hold points tied to the build schedule, and close coordination with a resident class surveyor who's tracking the vessel's construction against the classification society's approved plans. A survey company supporting this work needs scheduling and reporting structured around build milestones and hold points rather than the vessel's operational calendar, since a newbuild doesn't have \"port calls\" in the operational sense — it has a fixed sequence of fabrication and inspection stages that a delay in one stage cascades through the entire schedule. Tracking which hold points have been inspected, which are pending, and which NDT results are still outstanding against a specific block or section of the hull is a fundamentally different data structure than tracking recurring survey due dates on an operating vessel.
\nBeyond class society and vetting requirements, marine inspection and survey data frequently feeds into insurance underwriting and Protection and Indemnity (P&I) club requirements, particularly for older tonnage or vessels renewing hull and machinery coverage. Underwriters and P&I clubs often want condition survey history, not just a pass/fail class certificate, when assessing risk on a vessel — which means a survey company's ability to produce a clean, chronological condition history for a specific vessel, across multiple surveys and multiple years, can directly support (or complicate) a client's insurance renewal process. Flag state administrations layer on their own statutory survey and documentation requirements as well, which can differ meaningfully from the classification society's own rules even though the two are often coordinated. A system that can't cleanly distinguish class society requirements, flag state statutory requirements, and insurance-driven condition survey requests — treating them as one undifferentiated \"vessel inspection\" bucket — makes it much harder to respond quickly when a client's broker or P&I correspondent asks for a specific type of documentation on short notice.
\nThe core entity in the system should be the vessel — tracked by IMO number for permanent identity regardless of name changes or flag changes — with survey history, class society, gauging history, and vetting inspection history all attached to that vessel record across every port call and every survey company engagement, not scattered across disconnected job files.
\nMarine survey work happens against vessel arrival and departure windows, not a standard nine-to-five job schedule. A dispatcher needs to coordinate surveyor travel, port access credentials, and equipment mobilization against a berth window that might be twelve hours, and the system needs to support that kind of tight, date-and-time-specific scheduling rather than a generic weekly calendar.
\nA marine NDT technician typically holds ASNT SNT-TC-1A qualifications for the actual gauging and inspection methods, while a surveyor attending on behalf of a class society or conducting vetting work holds separate accreditations from that society or from OCIMF. The system needs to track both without conflating them — a common and costly error when companies try to force marine credentials into a template built for land-based ASNT tracking alone.
\nA survey company working ports on both sides of the US-Canada border, or handling international vessel calls, needs invoicing that handles USD and CAD cleanly, along with the documentation requirements that differ by port state and flag state.
\nWhen a vetting inspection report needs to reach a charterer or the SIRE database within days, or a class surveyor needs gauging results formatted to a specific society's reporting template before the vessel sails, the speed and structure of report generation is a commercial necessity, not a nice-to-have. This is exactly where the connection between the operational ERP and dedicated NDT reporting software pays off — structured thickness data captured in the field should flow directly into a report formatted to the class society's or client's specification, rather than requiring a survey team to manually reformat gauging results after every job.
\nMarine NDT equipment — UT thickness gauges, MPI yokes for weld inspection, sometimes portable radiography equipment for newbuild weld verification — has to travel to the vessel, often through port security and terminal access procedures that add real time to mobilization, and sometimes overseas for vessels calling at foreign yards for repair or drydock work. Equipment calibration status needs the same rigor covered elsewhere for any NDT operation, but marine work adds a logistics layer: an ERP tracking equipment for marine survey work benefits from being able to flag when a piece of equipment scheduled for a vessel call is still in transit from its last job, physically at a different port, or held up in customs on an international mobilization, rather than only tracking calibration due dates in isolation from physical location and transit status.
\nA vessel's name, and sometimes its flag and owner, can change multiple times over its operating life — a bulk carrier delivered under one owner's naming convention might be sold, renamed, and reflagged two or three times over a twenty-year hull life. Software built around name-based identity, rather than the IMO number that stays permanently assigned to the hull regardless of ownership changes, will silently fracture a vessel's survey history every time it changes hands — the \"new\" vessel under its new name shows up as having no inspection history at all, even though the physical hull has a complete gauging record under a previous name. This sounds like an edge case until you consider how common vessel sales and renaming actually are in the secondhand tonnage market that a large share of independent survey work serves. Getting vessel identity right at the data model level, from day one, is the difference between a survey company that can pull up twenty years of hull condition trend data on request and one that effectively starts every relationship with a \"new\" vessel from a blank slate.
\nMarine survey work in North American ports frequently involves interacting with vessel crews, port agents, and terminal operators from a wide range of nationalities and primary languages, and class society and vetting documentation itself often needs to satisfy both the operator's expectations and the specific formatting conventions a given class society or the SIRE VIQ database requires. A system that supports standardized, code-referenced reporting — thickness readings tied to a specific frame or station number, findings referenced against the applicable class rule or VIQ question number — produces documentation that's unambiguous regardless of who on the vessel or in the charterer's office is reviewing it, which matters more in marine work than in most facility-based inspection contexts where everyone involved typically shares a single employer's internal documentation conventions.
\nNone of this requires a marine-industry-specific proprietary platform costing a fortune to license — it requires an ERP flexible enough to be configured around vessel-centric records, dual credentialing tracks, and tight scheduling windows, built by a team that actually understands the difference between a class survey and a vetting inspection. That's the specific configuration work behind Atlantis NDT ERP for marine-sector clients: the same extensible core used for land-based inspection companies, configured around IMO-number vessel tracking, dual qualification paths for technicians and surveyors, and report generation aligned to class society and OCIMF formatting expectations. Pairing that operational backbone with rigorous technician qualification tracking and, where a company is building out its written practice for marine NDT work, ASNT Level III consulting, closes the loop between what the system enforces and what your written practice actually requires — which matters just as much on a bulk carrier hull survey as it does on a refinery turnaround.
\nMarine survey operations depend on the same operational discipline that runs every other line of NDT work:
\n\nAtlantis NDT pairs field expertise with software: NDT inspection management software — Atlantis ERP, a digital twin platform for asset integrity, and NDT reporting software. Build your team with NDT training & certification (ASNT SNT-TC-1A) and ASNT certification pathways, or bring in ASNT Level III consulting. Affordable, accessible, fully customizable — book a free consultation.
\n