GE Vernova Asset Performance Management

This is the product formerly marketed as GE Digital APM, and before that as Predix APM. After General Electric separated into GE Vernova, GE Aerospace and GE HealthCare, the APM software line went to GE Vernova, where it sits under the Electrification Software business. The product page carries a GE Vernova copyright and the navigation presents the family as Meridium, SmartSignal and Platform, so the Meridium and SmartSignal brands GE acquired years ago are still visible rather than retired. Anyone searching for GE Digital APM is looking at this product.

Sensor requirement: GE Vernova does not require you to buy its sensors. The product page describes APM as beginning with ingestion of mission critical data from sensors, edge devices, IT systems and OT systems, and the FAQ states that it should integrate with EAM, CMMS, historians and other data sources. That is a software layer over an existing instrumentation and historian estate, not a hardware purchase. The page stops short of naming which historians or which protocols, so a buyer should treat connector coverage as something to confirm in a technical workshop.

The suite is sold as modules that can be deployed individually or together, which is how GE Vernova gets to a range of buyers from a single reliability team to a multi-site integrity programme. The marketing emphasises a composable, microservices architecture and a collaboration with AWS for elastic scaling. What the public pages do not do is describe the mechanism behind the predictive claims. The page says the software can predict potential equipment failures and refers to predictive maintenance, advanced analytics and automated alerts, but it does not say what models are used, what data history they need, or which failure modes are covered. On the evidence available, failure prediction and anomaly detection are recorded here as unknown rather than supported, because a claim is not a description.

What is reasonably well evidenced is the breadth: asset health, reliability assessment, asset strategy, integrity and inspection all appear as named areas, and the Meridium heritage is genuinely a reliability and integrity engineering heritage rather than a dashboard one. This is a suite for organisations that already have an EAM system and a historian and want a reliability layer above both.

• Deployment: cloud delivery is described; on-premises and hybrid options are not stated on the product page.
• Pricing: not published. The only route is a contact form, a brochure or a demo hub.
• Integrations: AWS is named explicitly. Historians, EAM and CMMS are referenced generically in the FAQ without naming products.

Fits: large industrial and energy operators, particularly power generation, oil and gas, chemicals, mining and water, that run critical rotating and static assets and already have a historian and an EAM system. It suits organisations with a formal reliability or mechanical integrity function, because the Meridium lineage assumes someone owns asset strategy as a discipline. Multi-site operators benefit most, since the modular licensing lets a central reliability group standardise method across plants.

Does not fit: small and mid-sized maintenance teams looking for their first step beyond a spreadsheet. There is no published entry price, no free tier and no self-serve path, which is itself a signal about the intended deal size. It is also a poor fit for a buyer who wants a packaged predictive model they can switch on in weeks, because the public material gives no indication of model transparency, training data requirements or supported failure modes.

Typical use cases: fleet-wide asset health monitoring across generating stations; mechanical integrity and inspection planning for fixed equipment; standardising reliability assessment and asset strategy across sites; feeding prioritised work into an existing EAM system.

Buyer caution: because the product has moved through Predix APM, GE Digital APM and now GE Vernova APM, documentation, analyst notes and third-party reviews are scattered across three brand names and several architectures. Ask explicitly which codebase and which release a quote refers to, and ask for the connector list in writing.