IBM Maximo Integration for NDT Inspection Data
Pull Maximo work orders into Atlantis as NDT jobs and send approved results, report PDFs and technician certification status back against the same work order and asset, using the Maximo REST/JSON API and Atlantis's open REST API.
Who this is for
Maximo is common at refineries, utilities, pipelines and large manufacturing sites, which means it is common at the clients of NDT service companies. If your client issues inspection work as Maximo work orders and expects results logged back, or your own maintenance organisation runs Maximo but needs a purpose-built system for NDT methods, procedures, certifications and calibration, this is the integration to scope.
What data flows, and in which direction
| Record | Direction | Notes |
|---|---|---|
| Work order | Maximo → Atlantis | Creates or updates an Atlantis job with work-order number, site, asset and location. |
| Asset and location | Maximo → Atlantis (reference) | Keys that tie each report to the client's asset register; Maximo remains the register. |
| Inspection result and status | Atlantis → Maximo | Result and status recorded against the work order once the report is approved, for example as a work log entry. |
| Report PDF | Atlantis → Maximo | Attached to the work order as a document where attachments are enabled. |
| Follow-up request | Atlantis → Maximo | A rejectable finding raised as a service request so Maximo's own triage decides the follow-up work. |
| Work order completion | Maximo → Atlantis | Closes the NDT job and supports invoicing. |
Typical architecture
Maximo Manage exposes its business objects through object structures, and the Maximo REST/JSON API (built on the same code base as the older OSLC REST API) reads and writes them. The Maximo Integration Framework adds publish channels and enterprise services for event-driven and batch exchanges. The integration uses the route your Maximo administrators prefer, with a dedicated integration user holding only the permissions the agreed object structures need.
In steady state Maximo stays the system of record for assets, locations and the work-order workflow, and Atlantis holds the evidence of how each inspection was done: technician and certification, instrument and calibration, procedure revision, method data and result. Maximo is not modified beyond the integration configuration your administrators agree to.
Maximo Application Suite
Maximo Manage inside Maximo Application Suite uses the same object structures and REST API, with MAS authentication in front. The integration pattern does not change; the credential setup does, and that is part of the access step below.
What the Atlantis side offers
Atlantis ERP has an open REST API. The same API the offline field app uses to fetch assigned jobs and issued equipment and to submit reports is available for integration, and the records an NDT company cares about are reachable through it: jobs and team assignments, NDT reports and their status, technician certifications with their computed status (active, expiring soon, expired, revoked), equipment with calibration status and due dates, timesheets, quotations and invoices. Which objects are exposed, in which direction and to which system is agreed during implementation, because every integration is scoped to the customer's landscape rather than shipped as a fixed connector.
- No prebuilt, certified connector is claimed. The integration is built against your system's published API and Atlantis's REST API during implementation.
- Your system stays the system of record for whatever it owns today, whether that is the asset register, the general ledger or the customer master.
- Mapping is agreed in writing before anything is built: object, field, direction, trigger, and what happens when a record fails validation.
What gets configured during implementation
- Scope workshop. Which records move, in which direction, and who owns each field. Anything not agreed here is not built.
- Access on both sides. A dedicated integration user or app registration on your system with the minimum permissions for the agreed objects, and API credentials on the Atlantis side.
- Key mapping. How a record in one system is found in the other: work-order number, equipment or functional-location ID, customer number, invoice number.
- Field mapping and code lists. Status values, units, methods and result codes translated between the two systems.
- Triggers and timing. Event-driven (on approval, on posting) or scheduled, depending on what your system supports and what the business needs.
- Errors and retries. Where a failed record is logged, who is told, and how it is re-sent once fixed.
- Test in a sandbox, then a controlled go-live on a small set of records before the full flow is switched on.
What this integration does not do
Atlantis does not calculate inspection intervals, corrosion rates or remaining life, and does not perform risk-based inspection or fitness-for-service assessments, so it does not write those values into Maximo job plans or PM records. It supplies the inspection records those processes rely on.
Why integrate instead of re-keying
Every NDT company that works for large asset owners ends up typing the same facts twice: the work order number from the client's system onto the job, and the result from the report back into the client's system or into accounts. Re-keying is where report numbers get transposed, where a rejected weld is closed as accepted in someone else's system, and where invoices wait because nobody has matched the timesheet to the purchase order. An integration removes the second keystroke for the records that matter, and leaves an audit trail showing what was sent, when, and what the other system replied.
If your work arrives as Maximo work orders, book an integration scoping call and bring a sample work order export. See also the integrations overview, the NDT Reports app and the Certificates app.
Frequently asked questions
Which Maximo API is used?
Usually the Maximo REST/JSON API against the relevant object structures, or Maximo Integration Framework publish channels and enterprise services where your administrators prefer event-driven or batch exchange.
Does it work with MAS Manage?
Yes. Maximo Manage in Maximo Application Suite uses the same object structures and REST API; only the authentication setup differs.
Will Atlantis change our Maximo configuration?
Only by the integration configuration your Maximo administrators approve, such as an integration user and the object structures it can access. The data model is not extended by Atlantis.
Can historical inspection records be moved from Maximo?
Historical records can be imported during implementation if they are needed in Atlantis; what moves and how it is mapped is part of the scope.
Is this a certified connector?
No. Atlantis does not claim a certified or marketplace connector. The integration is built during implementation against your system's published API and the Atlantis REST API, scoped to the records you need.
Who owns the integration once it is live?
That is agreed in the scope: typically Atlantis maintains the Atlantis side and the mapping, and your IT team owns credentials and permissions on your system. Changes to the mapping are handled as change requests.
Sources
- SAP Business Accelerator Hub (S/4HANA APIs)
- IBM Maximo Manage REST APIs
- NetSuite OAuth 2.0 for REST web services
- QuickBooks Online API (Intuit developer help)
- Business Central API v2.0 endpoints
Speak to an ASNT NDT Level III
Discuss your inspection requirements with Atlantis NDT. Include the asset, method, location and documents you need reviewed.