Integrations

Connect transformer evidence to APM decisions

GridAPM works from the evidence transformer teams already have: diagnostic reports, test files, inspection notes, maintenance history, loading context, and enterprise asset records.

Map your evidence Review pilot scope

Start with approved datasets
Preserve source provenance
Connect records to asset identity
Expand after controlled pilot review

AgenticGrid Pro Transformer APM

The other GridAPM product ProtectionAI Relay testing

Compare both products

Evidence flow

One map from source to decision

Every supported source lands in the local-first workbench, passes a quality gate, and leaves as an engineer-reviewed output. There is no autonomous OT connection; OpenAI assistance uses controlled outbound requests.

Evidence sources

DGA lab files
Online DGA monitors
PRPD / SFRA test sets
Thermal imaging
Inspection records
CMMS / EAM
Historian / SCADA

Local-first workbench

Controlled OpenAI egress

Reviewed outputs

Work packages
Evidence packs
CMMS handoff

Source reference

Every record needs context

Diagnostic values alone are not enough. GridAPM preserves the source, timing, test quality, operating context, uncertainty, and decision relevance behind each record.

DGA lab files

Format: Lab reports — PDF, CSV, XLSX
What the agent reads: Gas trends, generation rates, ratios, moisture, acidity, furan context, and lab report provenance.
Quality gate: Unit checks, detection limits, sampling-date consistency, and duplicate-report reconciliation before any value enters a trend.

Online DGA monitors

Format: Monitor exports — CSV, vendor report files
What the agent reads: Continuous gas and moisture channels, sensor status, and alarm context, aligned with the latest lab benchmarks.
Quality gate: Sensor-drift and calibration flags; monitor values are cross-checked against the most recent lab sample before trending.

PRPD / SFRA test sets

Format: Test-set exports — XML, CSV, PDF reports
What the agent reads: PRPD pattern families, phase-reference quality, calibration and noise context, plus SFRA baseline comparison and frequency-band deviation.
Quality gate: Calibration and noise-floor notes are required; each SFRA trace is matched to a named baseline before any deviation is scored.

Thermal imaging

Format: Radiometric images and survey reports — JPEG, PDF
What the agent reads: Top-oil and hot-spot estimates, cooling state, ambient context, loading profiles, and aging assumptions.
Quality gate: Emissivity and ambient conditions recorded; spot temperatures are tied to the load at the time of the survey.

Inspection records

Format: Field forms, photos, and notes — PDF, images
What the agent reads: Field notes, photos, oil leaks, bushings, tap-changer observations, and maintenance follow-up.
Quality gate: Dated, asset-tagged entries; free text is kept verbatim with the record so nothing is silently normalized.

CMMS / EAM

Format: Work-order exports — CSV, XLSX, API extracts
What the agent reads: Work orders, maintenance history, asset hierarchy, and fleet criticality context.
Quality gate: Asset identifiers reconciled against the master hierarchy; open and closed work clearly distinguished.

Historian / SCADA

Format: Historian extracts — CSV files, not live connections
What the agent reads: Loading profiles, temperatures, tap position, and the operating context around each diagnostic event.
Quality gate: Timestamp alignment and gap checks; every series is mapped to the asset and sensor it came from.

Deployment boundary

No OT connection required

GridAPM reads exported files and approved extracts. It never connects to relays, RTUs, or control networks. Operational records stay local; requested AI assistance uses the controlled OpenAI connection.

What to prepare before a pilot

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

OT boundary

Site network

Workstation

GridAPM

Controlled OpenAI connection

Evidence in

Operational records and deterministic processing stay local. Requested OpenAI assistance sends only the approved bounded context needed for that operation through the controlled outbound connection.

CMMS / EAM handoff

Decisions land back in your system of record

After engineer sign-off, GridAPM assembles the recommendation into a work package: prioritized tasks, parts context, an outage-window note, and the evidence chain behind each line.

Mapped to your fields: Task lines carry the asset, priority, and work-type fields your CMMS or EAM import expects.
Provenance preserved: Every task links back to the evidence pack and the engineer decision that produced it.
File-based export: Work packages export as CSV for CMMS import and PDF for review — no write access to your systems is required.

GridAPM Workbench — local deployment Synthetic demo data

WP-2026-0141 TX-47 thermal follow-up APPROVED

Signed: M. Okafor, P.E. · 2026-07-10 14:32

Task list

P1 Oil re-sample + DGA lab analysis due 2026-07-24 · Field services
P2 IR follow-up scan, B-phase LV bushing due 2026-08-07 · Thermography
P3 Inspect & re-torque LV connection outage window 2026-09 · Maintenance

CMMS handoff SAP PM work order draft · SS12-TX-47 Ready

Export

PDF report
CSV task list
CMMS XML

Local-first
No OT connection
Audit log on

Product screen: work package WP-2026-0141 for TX-47 — prioritized task list, CMMS handoff and export options after engineer approval.

Integration FAQ

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.

Does GridAPM connect to SCADA or OT networks directly?

No. GridAPM reads exported files and approved historian extracts on an engineer workstation inside your perimeter. Relays, RTUs, and control systems are never touched. OpenAI receives only the context approved for a requested AI operation.

Map your evidence to a pilot

Send your source list — evidence intake is the first two weeks of every pilot.

Map your evidence Review pilot scope