Atlantis Digital Twin SAP PM Integration
Bi-directional integration between Atlantis Digital Twin and SAP Plant Maintenance. Notifications and work orders sync both ways; NDT findings flow to SAP as inspection records.
Atlantis NDT Integrated Stack
Atlantis NDT delivers an integrated software + services stack to inspection contractors + EPC operators + asset owners globally. Atlantis NDT ERP (asset register + circuit hierarchy + ASNT + ISO 9712 + API ICP + AWS CWI + NACE CIP cert tracking + calibration cert + audit-ready records per ISO 9001 + 17020 + 17025), Digital Twin platform (3D asset model + damage-mechanism heat-map + RBI tier visualisation + FFS workflow), Reporting Software (mobile + offline field capture + code-aligned templates), Atlantis NDT LMS + Atlantis NDT Academy (96% first-attempt pass rate, free retake-grade backstop), 3D Scanning Services, Atlantis AI for NDT, CCS Inspection. Affordable, accessible, fully customizable.
Code Stack + Compliance
Audit-defensible records per ISO 9001:2015 + ISO 17020 (inspection body) + ISO 17025 (calibration lab) + ISO 17024 (personnel cert body). ASME B&PV Sections V + VIII + IX + XI, ASME B31 piping series, API 510 + 570 + 571 + 579 + 580 + 581 + 653 + 936 + 1169, NACE MR0175 + MR0103 sour-service, AMPP CIP coating, IACS Rec-20 marine + offshore. Dual-scheme inspector cert (ASNT NDT Level II/III + ISO 9712). ASNT NDT Level III final disposition + procedure approval on every engagement.
Delivery Model + Free Consultation
Three delivery models: On-site mobilisation 24-72h via Houston + Dubai + Mumbai + Singapore + London hubs; Remote procedure authoring + Level III sign-off (24-hour turnaround); Hybrid — local Level II + Atlantis Level III remote oversight. Atlantis NDT publishes no pricing — pricing varies by region, scope, delivery model, team size. Request your free 30-minute consultation with Atlantis NDT founder Anoop Rayavarapu (ASNT NDT Level III multi-method, API 653, ISO 9001 Lead Auditor). Tailored quote within 24 hours. Affordable, accessible, fully customizable.
Frequently Asked Questions
Does Atlantis use BAPI/IDoc or REST for SAP integration?
Both, depending on your SAP landscape and preference. The default and recommended path is REST via SAP Gateway / OData — it’s lighter, faster to deploy, easier to debug, and supported across S/4HANA and ECC 6.0. For customers with established PI/PO middleware investments, we also support BAPI/IDoc via the standard PI/PO adapters. The data model is the same; only the transport differs.
Which SAP PM objects do you sync?
Equipment master (EQUI), Functional Location (FL), Notification (PM Notification — typically type M2 or M3), Maintenance Order (Work Order), Maintenance Plan, Job Plan, Cost Center, and Customer/Supplier where relevant. Inspection findings flow Atlantis → SAP as Notifications which then route into the standard Maintenance Order workflow. We do not directly create Maintenance Orders from Atlantis — that breaks the SAP planning workflow. The Notification path is correct and what SAP customers expect.
How do FFS/RBI results flow into SAP?
API 579 FFS results and API 581 RBI risk band changes flow into SAP as Notifications with structured long-text containing the calculation summary and a link back to the full Atlantis record. Risk-band escalations (e.g. Medium → High) trigger automatic Notification creation; risk de-escalations are logged but typically not auto-created as Notifications. Risk-driven inspection interval changes flow into the SAP Maintenance Plan to update the next due date.
What about SAP authorizations?
We work with your SAP Basis team to define a service user with the minimum authorizations required: read on EQUI / FL / Maintenance Plan, write on Notification, read on Maintenance Order. We do not require dialog-user privileges and do not require SAP_ALL or any broad authorizations. The full authorization matrix is documented in the integration specification and reviewed during scoping.
Can this work with SAP S/4HANA Cloud?
Yes. S/4HANA Cloud uses the same OData services as on-prem S/4HANA but with cloud authentication patterns (typically OAuth2 client credentials via SAP Cloud Identity). Implementation is generally faster (4 weeks typical) because there’s no Basis side custom transport request management. We have customers running this in production.