Does DER and Load Visibility Pilot Scoper upload asset data?

No. The tool runs in the browser and does not upload files, asset identifiers, work orders, feeder data, or tool inputs to GridAPM.

How does this connect to a GridAPM pilot?

Use the output to frame a controlled pilot around approved evidence sources, reviewer roles, AI-assist boundaries, security expectations, and measurable workflow outcomes.

GridAPM tool

DER and Load Visibility Pilot Scoper

Q: Is DER and Load Visibility Pilot Scoper diagnostic advice?

No. It is a planning aid for pilot scoping and evidence readiness. It does not diagnose transformer condition, approve maintenance, certify compliance, set operating limits, or replace qualified engineering review.

Evaluate whether DER, large-load, feeder, and transformer evidence is ready for a bounded visibility pilot conversation.

Open tool Scope a pilot

DER and load visibility Audience: DSO planners, utility operations, data centers, and industrial sites Output: Visibility pilot scope Tool inputs stay in your browser. Optional site analytics, when accepted, records page-level usage only.

Interactive visibility tool

DER and Load Visibility Pilot Scoper

Estimate whether DER, large-load, and transformer visibility evidence is ready for a bounded GridAPM pilot conversation.

Client-only. No feeder files, equipment IDs, or server submission; tool inputs stay local.

Visibility inputs

Select generic planning pressure and the evidence categories your team can review today.

Organization context Visibility pressure Review horizon Observability level

Transformer-to-feeder mapping Transformer groups, feeders, sites, and voltage levels can be connected for review. Load profiles Recent interval load history, peaks, seasonality, and known gaps are available. DER register DER, storage, EV charging, or large-load assets are listed with location context. Topology, phase, and voltage context Feeder topology, phase/voltage assumptions, and switching context are reviewable. Power-quality and protection events Alarms, events, voltage issues, relay records, or customer notes can be linked. Ratings, cooling, and spares Transformer ratings, cooling context, spares, and replacement constraints are known. Thermal and condition evidence Thermal/loading, inspections, DGA, or other condition records are available. Provenance, timestamps, and units Sources, timestamps, units, and data owners are documented enough for review. Named reviewer path Planning, operations, protection, and asset reviewers are identified.

Visibility result

71% Coordinated DER/load review candidate

The evidence is broad enough for a coordinated DER and large-load review, with engineer approval still required before planning conclusions.

Suggested first pilot

DER/load-to-transformer visibility map with evidence gaps and reviewer questions

Priority gaps

Pilot evaluation Platform Utilities Security Data handling Sample pack

Visibility evidence matrix

Planning question	Evidence needed	Human decision point
Where is load changing?	Load profiles, DER register, feeder mapping, and forecast assumptions.	Planning validates whether the evidence is sufficient for review.
Which transformers need attention?	Ratings, cooling, thermal context, spares, and maintenance history.	Asset engineers decide whether a transformer group needs deeper review.
What should AI draft?	Source list, open questions, missing evidence, and reviewer-specific handoff notes.	Qualified teams approve, reject, or edit any resulting package.

This scoper is a planning aid only. It does not calculate hosting capacity, approve interconnections, determine real-time operating limits, set protection settings, diagnose transformer condition, or recommend operational action.

Pilot boundary

Use the result as a review-starting point.

Public tool outputs are designed to help utility, TSO, DSO, generation, data center, oil and gas, and industrial teams frame a controlled GridAPM discussion before approved evidence enters a local-first transformer APM workflow.

No diagnostic authority The tool does not determine transformer condition, approve maintenance, certify standards compliance, or replace qualified engineering judgment.

No private source intake Do not enter confidential asset names, work-order IDs, network details, customer data, or proprietary measurements into public planning tools.

Human review remains central GridAPM positions AI draft output as review material until authorized reviewers approve, edit, reject, or escalate it.

Next step

Turn the tool output into a pilot conversation.

Share the non-confidential result with GridAPM to discuss approved evidence sources, security boundaries, reviewer ownership, and a measurable first workflow.

Request pilot Read research context

Define approved source evidence

Name reviewer roles and approval states

Confirm security and data handling expectations

Select a measurable first workflow

Related tools

Continue scoping the pilot surface.

These adjacent tools help convert readiness, evidence gaps, governance questions, and handoff fields into a stronger pilot brief.

Pilot brief

Pilot Brief Builder

Generate a first-pass GridAPM pilot brief for transformer APM evidence, workflow pain, reviewer roles, data boundaries, and success metrics.

Open tool

Work package

Transformer Maintenance Work Package Builder

Draft a human-reviewed transformer maintenance work-package outline from condition evidence, maintenance history, criticality, approval states, and CMMS/EAM handoff fields.

Open tool

OT AI risk

Utility OT AI Risk Register Builder

Create a first-pass risk register for approval-gated transformer APM AI workflows across OT boundaries, source approvals, agent permissions, cybersecurity review, and audit artifacts.

Open tool