Atlantis Digital Twin GE Vernova APM Integration
GE Vernova APM (formerly Meridium) integration. Asset hierarchy fully mirrored; inspection and thickness data exchanged in both directions for the owner's own programmes (Atlantis does not offer RBI or FFS); inspection findings pushed.
Frequently Asked Questions
Is GE Vernova APM the same as GE APM?
Yes — same product line, post-2024 corporate badging. GE split into three companies in 2024: GE Aerospace, GE HealthCare, and GE Vernova. The APM products went to GE Vernova. The platform code base, data model, and APIs are continuous from Meridium → GE APM → GE Vernova APM. Our integration supports the entire lineage.
How does this differ from the Meridium APM integration page?
Functionally identical — they describe the same integration. The Meridium APM page covers the legacy / pre-Vernova product naming and is geared toward customers with older installs. This page covers the current GE Vernova APM product naming and includes notes specific to the power generation APM modules (turbines, generators, balance-of-plant, transmission) that are most relevant to Vernova’s customer base. The technical architecture is the same.
What about GE Vernova’s power-gen specific APM modules?
GE Vernova has deepened the APM modules covering gas turbines, steam turbines, generators, transformers, and balance-of-plant equipment. Atlantis integrates with these modules natively — turbine blade inspection records, generator winding inspections, transformer DGA results, etc. flow into the appropriate Atlantis equipment record. For wind farm assets (a strategic Vernova focus area), Atlantis adds blade inspection workflow native to the platform.
Migration vs coexistence?
Most GE Vernova APM customers choose coexistence for the first 12–24 months; some migrate fully when the APM contract is up for renewal.
Are there any GE-specific gotchas to know about?
A few. (1) GE Vernova APM’s authentication requires a service account with specific Family Manager privileges — your APM admin needs to provision this. (2) Some custom Family templates from older Meridium installs need mapping work — we handle this during scoping. (3) The recent shift from on-prem SQL Server to GE Vernova’s cloud-hosted APM changes some authentication and rate-limit details — we have current connector code paths for both.