IBR Event Evidence Readiness Checker

Scope inverter-based resource event evidence across relay, PMU, controller, model, commissioning, timeline, and reviewer boundaries.

IBR event evidence Audience: TSO, DSO, generation, renewables, operations, reliability, and protection teams Output: IBR event evidence package Tool inputs stay in your browser. Optional site analytics, when accepted, records page-level usage only.

IBR Event Evidence Readiness Checker

Public client-only planning tool for inverter-based resource event evidence readiness for utility, TSO, DSO, generation, renewable owner, and reliability teams.

Client-only. No uploads or server submission; tool inputs stay local.

Event evidence inputs

Use generic ranges only. Do not enter plant names, asset IDs, customer data, model files, protection settings, or live operating details.

Readiness result

58% Focused IBR evidence pilot

The event has enough evidence shape for a focused IBR pilot, but missing sources and approval boundaries should constrain the first scope.

Suggested first pilot scope

Human-reviewed IBR disturbance timeline with source-linked logs, event records, and reviewer questions

Top missing gaps

    Controlled event evidence path

    1. ScopeChoose one event window, source boundary, and reviewer owner.
    2. AlignNormalize timestamps, versions, provenance, and timeline references.
    3. DraftAI assists with evidence organization and reviewer questions.
    4. ReviewQualified people approve, edit, reject, or escalate outputs.
    5. PackageProduce a traceable evidence pack for the approved pilot scope.

    IBR event evidence comparison

    Event source Evidence needed Agentic AI assist Human approval boundary
    PMU, relay, SCADA, or event records Time-aligned event files, targets, alarms, sequence markers, export dates, and source owners. Assemble a disturbance timeline, identify gaps, and draft reviewer questions with source references. Operations, protection, reliability, or engineering reviewers accept the timeline and any escalations.
    Inverter, plant controller, or OEM logs Read-only logs, controller status, firmware context, model/version references, and plant/customer notes. Organize log evidence, compare timestamps, and summarize candidate questions for qualified reviewers. Owner, OEM, generation, or utility reviewers decide what can be used, shared, or escalated.
    Models, commissioning, and protection context Model/version records, change logs, commissioning tests, settings evidence, and documented assumptions. Flag mismatches between event evidence and documented context without approving settings or models. Formal studies, compliance, legal, protection, and interconnection approvals stay outside the tool.

    This checker is a client-only planning aid: no uploads and no server submission; tool inputs stay local. Optional site analytics, when accepted, does not receive selected tool values. It is not root-cause authority, EMT/RMS simulation, NERC compliance/legal advice, protection-setting approval, interconnection approval, or autonomous operations.

    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.

    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.

    Define approved source evidence
    Name reviewer roles and approval states
    Confirm security and data handling expectations
    Select a measurable first workflow

    Continue scoping the pilot surface.

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