Connect transformer evidence to APM decisions

GridAPM Ai is built to work from the evidence transformer teams already use: diagnostic reports, test files, inspection notes, maintenance history, loading context, and enterprise asset records.

Every record needs context

Diagnostic values are not enough. GridAPM Ai is designed to preserve the source, timing, test quality, operating context, uncertainty, and decision relevance behind each record.

DGA and oil quality

Gas trends, generation rates, ratios, moisture, acidity, furan context, and lab report provenance.

PRPD and partial discharge

Pattern families, phase reference quality, calibration notes, noise context, and likely source review.

SFRA and winding movement

Baseline comparison, frequency-band deviation, test setup notes, and mechanical integrity context.

Thermal and loading

Top-oil, hot-spot estimates, cooling state, ambient context, loading profiles, and aging assumptions.

Inspection records

Field notes, photos, oil leaks, bushings, tap changer observations, and maintenance follow-up.

Enterprise context

CMMS, EAM, historian, SCADA context, asset hierarchy, work orders, and fleet criticality.

What to prepare before a GridAPM pilot

A successful pilot starts with clear boundaries: which assets, which evidence, which workflow, who reviews output, and what decision the team wants to improve.

Asset identifiers and hierarchy
Approved historical records
Source system owners
Data sensitivity classification
Review workflow and decision owners
Pilot success criteria

Questions data and engineering teams ask

Does GridAPM require full enterprise integration on day one?

No. The recommended pilot path starts with approved datasets and a narrow decision workflow before expanding to enterprise systems.

Which evidence stream should a pilot start with?

Many pilots can start with DGA plus one or two supporting streams such as PRPD, SFRA, loading, inspections, or maintenance records.

How should teams prepare data for GridAPM?

The most useful preparation is mapping assets, evidence sources, file owners, review owners, sensitivity level, and the decision workflow to be evaluated.