This section captures critical identification and location data to ensure precise asset tracking and rapid response coordination. Accurate microgrid identification is essential for centralized monitoring and historical failure pattern analysis.
Microgrid Unique Identifier (MGID)
Microgrid System Name
Physical Site Address & Landmarks
Incident First Detected (System Time)
Field Engineer Arrival Time on Site
Field Engineer Employee ID
Field Engineer Certification Level
Site Access Conditions at Time of Arrival
Unrestricted Access
Partial Access - Safety Barriers Active
Restricted Access - Hazardous Conditions
Emergency Access Only - Lockout/Tagout Required
Are backup communication systems available on-site?
Specify backup communication method and signal strength
Describe communication contingency plan implemented
Environmental Conditions Observed (Select all that apply)
Normal Weather
Extreme Temperature (>40°C or <-10°C)
Precipitation (Rain/Snow)
High Winds (>25 m/s)
Lightning Activity
Flooding or Water Ingress
Corrosive Atmosphere
Dust or Debris Contamination
Upload Site Access Photos (Control Room, Battery Enclosure, External Conditions)
This section documents the electrical characteristics of the incident, focusing on islanding detection, voltage deviations, frequency excursions, and load impact. Accurate measurement of voltage delta (ΔV) and frequency deviation is critical for root cause analysis and protection system validation. All measurements should be cross-referenced with SCADA timestamps.
Pre-Incident Microgrid Operational Mode
Grid-Tied (Parallel Operation)
Intentional Islanding (Planned)
Unintentional Islanding (Fault-Induced)
Off-Grid (Standalone)
Black Start Mode
Was the islanding event detected by automatic protection systems?
Specify protection device name, model, and trip setting that activated
Describe manual detection method and time lag between event and detection
Three-Phase Voltage Measurements at Key Time Intervals
Measurement Point | Pre-Incident L-N Voltage (V) | During Event L-N Voltage (V) | Post-Event L-N Voltage (V) | Voltage Delta ΔV (%) | ||
|---|---|---|---|---|---|---|
A | B | C | D | E | ||
1 | POC Grid Side | 240 | 0 | 0 | 100 | |
2 | Microgrid Bus A | 240 | 235 | 240 | 2.083333333 | |
3 | Critical Loads Panel | 240 | 238 | 240 | 0.833333333 | |
4 | 0 | |||||
5 | 0 | |||||
6 | 0 | |||||
7 | 0 | |||||
8 | 0 | |||||
9 | 0 | |||||
10 | 0 |
Frequency & Power Quality Analysis
Parameter | Pre-Incident Value | During Event Value | Deviation (%) | Duration of Excursion | ||
|---|---|---|---|---|---|---|
A | B | C | D | E | ||
1 | Frequency (Hz) | 50.02 | 49.85 | 0.339864054 | 12:02 AM | |
2 | THD-V (%) | 1.2 | 4.8 | 300 | 12:03 AM | |
3 | Power Factor | 0.98 | 0.91 | 7.142857143 | 12:02 AM | |
4 | 0 | |||||
5 | 0 | |||||
6 | 0 | |||||
7 | 0 | |||||
8 | 0 | |||||
9 | 0 | |||||
10 | 0 |
Did automatic load shedding activate during the event?
Load Shedding Execution Details
Load Priority Level | Load Description | Shed Successfully? | Load Capacity (kW) | ||
|---|---|---|---|---|---|
A | B | C | D | ||
1 | Priority 3 | HVAC Non-Critical | Yes | 150 | |
2 | Priority 2 | Production Line B | 250 | ||
3 | |||||
4 | |||||
5 | |||||
6 | |||||
7 | |||||
8 | |||||
9 | |||||
10 |
Explain why load shedding did not activate and what load stabilization measures were taken
Critical Loads Affected by Power Disruption (Select all that apply)
Hospital/Medical Equipment
Data Center/IT Infrastructure
Industrial Process Control
Emergency Lighting
Fire Safety Systems
Water Pumping/Treatment
Telecommunications
No Critical Loads Affected
Protection Relay & SCADA System Performance Assessment
Poor | Fair | Good | Excellent | Outstanding | |
|---|---|---|---|---|---|
Rate the accuracy of islanding detection timing | |||||
Rate the completeness of SCADA data logging during event | |||||
Rate the responsiveness of protection relay coordination | |||||
Rate the clarity of HMI alarm notifications |
Describe any unusual electrical phenomena observed (e.g., voltage flicker, harmonic distortion, phase imbalance)
Upload SCADA Event Logs, Oscillography Files, and Protection Relay Trip Records
This section focuses on deep diagnostic assessment of battery storage systems, inverter power electronics, and thermal management infrastructure. Battery State of Charge (SOC) and State of Health (SOH) deviations can indicate cell degradation or balancing issues. Thermal runaway prevention requires meticulous monitoring of temperature gradients and cooling system efficacy. All diagnostic data must correlate with BMS alarm histories.
Battery Energy Storage System (BESS) Unit ID
Inverter Manufacturer & Model
Battery State Parameters at Time of Incident
Parameter | Pre-Incident Value | During Event Value | Post-Event Value | Acceptable Range | ||
|---|---|---|---|---|---|---|
A | B | C | D | E | ||
1 | State of Charge (%) | 85 | 42 | 45 | 20-95 | |
2 | State of Health (%) | 98 | 98 | 98 | >95 | |
3 | DC Bus Voltage (V) | 750 | 735 | 745 | 720-780 | |
4 | ||||||
5 | ||||||
6 | ||||||
7 | ||||||
8 | ||||||
9 | ||||||
10 |
Did the Battery Management System (BMS) generate any fault codes?
BMS Fault Code Analysis
Fault Code ID | Fault Description | Timestamp | Acknowledged? | Engineer Diagnostic Notes | ||
|---|---|---|---|---|---|---|
A | B | C | D | E | ||
1 | F-301 | Cell Overvoltage Warning | 1/15/2025, 2:32 PM | Yes | Transient spike during grid disconnection | |
2 | ||||||
3 | ||||||
4 | ||||||
5 | ||||||
6 | ||||||
7 | ||||||
8 | ||||||
9 | ||||||
10 |
If no BMS faults were recorded, consider investigating sensor calibration, communication integrity, or latent firmware issues that may suppress fault reporting.
Thermal Management System Performance Metrics
Measurement Location | Temperature (°C) | Status | Cooling Active? | Within Normal Range? | ||
|---|---|---|---|---|---|---|
A | B | C | D | E | ||
1 | Battery Module 1 - Top | 28 | Normal | Yes | Yes | |
2 | Inverter Heat Sink | 65 | Elevated | Yes | ||
3 | Control Cabinet Ambient | 35 | Normal | Yes | Yes | |
4 | ||||||
5 | ||||||
6 | ||||||
7 | ||||||
8 | ||||||
9 | ||||||
10 |
Inverter Power Electronics Health Assessment (Rate 1-5, where 5 is Optimal)
IGBT switching performance | |
DC capacitor bank condition | |
AC filter effectiveness | |
Gate driver circuit integrity | |
Communication latency to central controller |
Were any cell voltage imbalances detected during post-event analysis?
Cell Voltage Imbalance Details
Battery Module ID | Max Cell Voltage (V) | Min Cell Voltage (V) | Voltage Deviation (mV) | Requires Balancing? | ||
|---|---|---|---|---|---|---|
A | B | C | D | E | ||
1 | BM-03 | 3.85 | 3.72 | 130 | Yes | |
2 | 0 | |||||
3 | 0 | |||||
4 | 0 | |||||
5 | 0 | |||||
6 | 0 | |||||
7 | 0 | |||||
8 | 0 | |||||
9 | 0 | |||||
10 | 0 |
Describe any audible noise, vibration, or physical anomalies observed from battery enclosures or inverter cabinets
Upload Thermal Imaging Photos, Inverter Display Screens, and Physical Damage Documentation
This section outlines the systematic approach to safely re-energize the microgrid connection, ensuring zero voltage phase difference, frequency matching, and adherence to anti-islanding protection protocols. The re-synchronization sequence must prioritize personnel safety, equipment protection, and grid code compliance. Any deviation from standard procedures requires explicit justification and elevated approval.
Has the utility grid operator been formally notified of the islanding event?
Utility Coordination Log
Notification Time | Grid Operator Contact | Acknowledgment Reference | Grid Permission to Reconnect Obtained? | ||
|---|---|---|---|---|---|
A | B | C | D | ||
1 | 1/15/2025, 2:45 PM | Grid Control Center - Operator Smith | ACK-7742 | ||
2 | |||||
3 | |||||
4 | |||||
5 | |||||
6 | |||||
7 | |||||
8 | |||||
9 | |||||
10 |
Justify why utility notification was not possible and describe alternative safety measures implemented
Grid Re-Synchronization Parameters Verification
Parameter | Microgrid Value | Grid Value | Allowable Tolerance | Within Tolerance? | ||
|---|---|---|---|---|---|---|
A | B | C | D | E | ||
1 | Voltage Magnitude (V) | 415 | 416 | 5 | Yes | |
2 | Frequency (Hz) | 50.01 | 50.02 | 0.2 | Yes | |
3 | Phase Angle (°) | 0 | 2 | 5 | ||
4 | ||||||
5 | ||||||
6 | ||||||
7 | ||||||
8 | ||||||
9 | ||||||
10 |
Anti-Islanding Protection Verification Status
Passed - All Functions Operational
Partial - Minor Sensor Drift Detected
Failed - Requires Manual Override
Not Tested - Emergency Reconnection Protocol
Is a staged load restoration sequence required?
Rank the following load categories in order of restoration priority (1 = First to Restore)
Critical Life Safety Systems | |
Data Center/IT Infrastructure | |
Industrial Process Critical Loads | |
HVAC & Climate Control | |
General Lighting & Non-Critical Loads | |
EV Charging Stations |
Safety Equipment & Lockout/Tagout Verification Checklist
Safety Item | Inspected & Verified? | Inspector Initials | Remarks | ||
|---|---|---|---|---|---|
A | B | C | D | ||
1 | Insulated Gloves (1000V Rated) | Yes | JD | Passed dielectric test | |
2 | Arc Flash PPE Category 2 | Yes | JD | Properly donned | |
3 | Lockout/Tagout Applied at PCC | Yes | JD | 3 locks applied | |
4 | |||||
5 | |||||
6 | |||||
7 | |||||
8 | |||||
9 | |||||
10 |
Potential Grid Re-Synchronization Risks Identified (Select all that apply)
Voltage Phase Angle Mismatch
Frequency Stability Uncertainty
High Grid Impedance
Residual Voltage on Grid Side
Protection Relay Desynchronization
Communication Failure with Grid Operator
Load Inrush Current Concerns
No Significant Risks Identified
Detail the step-by-step re-synchronization procedure executed, including time delays, verification checkpoints, and any deviations from standard operating procedures
Was the re-synchronization successful on the first attempt?
Document reasons for failure and corrective actions taken before subsequent attempts
Upload Synchroscope Screenshots, Breaker Status Indicators, and Post-Reconnection Load Flow Data
This final section requires comprehensive review and formal authorization from the Chief Operations Engineer (COE) or designated authority. The COE must validate all diagnostic findings, risk assessments, and re-synchronization outcomes before the microgrid can return to normal operational status. This sign-off represents organizational accountability and ensures all safety and technical standards have been met.
Have all previous four sections been completed in full with supporting documentation attached?
Identify which sections require completion and assign corrective action to responsible personnel
Chief Operations Engineer Review & Risk Assessment
Unacceptable | Needs Improvement | Adequate | Good | Excellent | |
|---|---|---|---|---|---|
Technical accuracy of field engineer diagnostics | |||||
Completeness of root cause analysis | |||||
Adequacy of corrective actions implemented | |||||
Compliance with safety protocols | |||||
Readiness for return to normal operations |
Overall Incident Severity Classification
Level 1 - Minor Event (No Equipment Damage)
Level 2 - Moderate Event (Limited Impact)
Level 3 - Major Event (Equipment Damage, Service Disruption)
Level 4 - Critical Event (Safety Risk, Extended Outage)
Are additional preventive maintenance actions required before resuming normal operations?
Specify required maintenance tasks, responsible teams, and completion deadlines
Recommended Follow-Up Actions (Select all that apply)
Firmware Update for BMS/Inverter
Protection Relay Setting Optimization
Thermal Management System Overhaul
Load Shedding Logic Revision
Staff Training on Updated Procedures
Equipment Replacement (Specify in Notes)
Enhanced Monitoring System Installation
No Further Action Required
Chief Operations Engineer Final Comments & Operational Recommendations
Chief Operations Engineer Digital Signature
COE Approval Timestamp
Chief Operations Engineer Employee ID
Has this incident been logged in the central asset management system for trend analysis?
Provide reason for not logging and alternative tracking method
Upload Final System Status Screenshots and Post-Incident Stability Monitoring Data
To configure an element, select it on the form.