ERP Modules — Pick What You Need

11 production-ready modules. Run any single module, build a tailored bundle for your industry, or deploy the full suite. Used by NDT inspection, calibration laboratories, welding fabrication shops, marine survey, pipeline integrity, aerospace QC, and metrology labs across 80+ cities.

Atlantis NDT ERP modules are not independent apps bolted together — certification tracking, calibration management, work orders and reporting share one data model, so a technician's current certification status, the calibration state of the instrument they are assigned, and the project they are dispatched to are always read from the same underlying record rather than three systems that can silently drift apart.

A generic ERP treats "who is certified," "what is calibrated" and "what job is scheduled" as three unrelated tables, which is exactly how a decertified technician gets dispatched with an overdue instrument on a live work order — nobody's fault, just three systems that never talked to each other. Atlantis configures these as one connected model: a work order cannot be assigned to a technician whose certification for that method has lapsed, and a technician cannot be paired with an instrument outside its calibration window. The modules below are the visible surface of that shared model, not separate products.

Source: ISO 9712 (personnel certification) and ISO 17025 (calibration) as the two schemes the module interdependency is built around

How the modules actually interlock

Certification tracking is the gate the other modules read from, not a standalone register. When a work order module schedules a UT inspection, it checks the assigned technician's current UT certification level and expiry against SNT-TC-1A or ISO 9712 before the job confirms — the same check a client audit performs manually, done automatically at dispatch time instead of discovered after the fact.

Calibration management works the same way against equipment. An instrument due for recalibration is flagged in the calibration module, and that flag is visible to the work-order module before a crew is assigned it for a field job — not as a separate report someone has to remember to cross-check.

Reporting closes the loop: every report the system generates carries the technician's certification state and the instrument's calibration state as they stood at the moment of inspection, not as they stand today. That distinction is what a client audit actually asks for — a snapshot, not a current status.

Can we run only the modules we need, not the full platform?

Yes — modules are configured to what the business actually runs; a company doing only field inspection work does not need the ERP's manufacturing-adjacent modules turned on. The interlocking checks (certification-gates-dispatch, calibration-gates-assignment) apply to whichever modules are active.

What happens if a technician's certification lapses mid-project?

The work-order module blocks new assignments to that technician for the affected method the moment the certification-tracking module marks it expired; work already dispatched is flagged for review rather than silently continuing.

Does adding a module require re-entering existing data?

No — modules read from the same technician, equipment and project records already in the system; turning on a new module extends what those records can do rather than duplicating them.