Incident Management for Airports and Utilities

Airports and power utilities operate under strict regulatory frameworks. When equipment fails, documentation requirements are intense. This guide covers how UniAsset's Incident Mode helps you meet industry-specific compliance needs.

Why Regulated Industries Need Special Attention

Airports and utilities share common challenges:

Challenge	Impact
High-value equipment	Failures cost millions in downtime
Public safety responsibility	Lives depend on equipment reliability
Regulatory scrutiny	FAA, NERC, state PUCs review incidents
Insurance complexity	Coverage requires detailed documentation
Legal exposure	Failures may result in litigation

UniAsset's Incident Mode is designed specifically for these high-stakes environments.

Airport Operations

Common Airport Assets Requiring Incident Management

Airside Equipment

Runway lighting systems
Navigation aids (ILS, VOR, DME)
Radar systems
De-icing equipment
Fuel storage systems

Ground Support Equipment

Belt loaders
Pushback tugs
Air conditioning units
Ground power units
Baggage systems

Passenger-Facing Systems

Jet bridges
Escalators and elevators
PA systems
Security screening equipment

FAA Compliance Considerations

The FAA requires airports to maintain detailed records of:

Equipment inspections
Maintenance activities
Equipment failures and resolutions
Corrective action plans

How UniAsset Helps:

FAA Requirement	UniAsset Feature
Document equipment state at failure	Immutable snapshot
Record maintenance history	Maintenance tracking
Track certifications	Document management with expiry
Establish timeline	Investigation notes with timestamps
Demonstrate corrective action	Status progression and notes

Airport-Specific Incident Workflow

1. Runway Lighting Failure

Ground crew notices lights out → Report incident → 
Snapshot captures: last maintenance, bulb inventory, 
inspection certifications → Investigate → 
Document repair → Close incident

2. Jet Bridge Malfunction

Operations reports stuck bridge → Report incident →
Snapshot captures: assigned terminal, last inspection,
maintenance vendor → Emergency repair documented →
Root cause: hydraulic seal failure → Close with notes

3. Fuel System Alert

Monitoring alerts fuel pressure drop → Report incident →
Snapshot captures: pump status, last calibration,
environmental permits → Investigation identifies valve issue →
Corrective action documented → Regulatory notification filed

Airport-Specific Best Practices

Report immediately - FAA timelines start at incident, not report
Include severity context - A runway system failure is CRITICAL, a single cart is MEDIUM
Document regulatory notifications - Note when FAA/TSA were informed
Link to NOTAMs - Reference any notices issued related to the incident
Track Part 139 items - Certification-related equipment needs extra attention

Power Utilities

Common Utility Assets Requiring Incident Management

Generation

Turbines
Generators
Cooling systems
Control systems
Emissions monitors

Transmission

Transformers
Circuit breakers
Capacitor banks
Relay equipment
SCADA systems

Distribution

Substation equipment
Smart meters
Reclosers
Voltage regulators
Line equipment

NERC CIP Compliance

North American Electric Reliability Corporation (NERC) Critical Infrastructure Protection (CIP) standards require:

Incident documentation
Root cause analysis
Corrective action plans
Audit-ready records

How UniAsset Helps:

NERC CIP Element	UniAsset Feature
CIP-008: Incident Reporting	Immutable incident records
CIP-010: Configuration Management	Snapshot preserves config state
CIP-007: System Security	Document tracking for patches
Audit trail requirements	Timestamped investigation notes

Utility-Specific Incident Workflow

1. Transformer Failure

Control room receives alarm → Report incident →
Snapshot captures: last oil test, maintenance history,
load patterns → Field investigation → 
Root cause: insulation breakdown → 
Replacement documented → Close incident

2. SCADA System Outage

Loss of visibility reported → Report incident →
Snapshot captures: last security patch, configuration,
access credentials expiry → IT investigation →
Network issue identified → Corrective action documented

3. Smart Meter Data Loss

Billing detects data gaps → Report incident →
Snapshot captures: meter firmware, last test,
communications status → Field inspection →
Communications module failure → Replacement logged

State PUC Considerations

Public Utility Commissions often require:

Outage cause documentation
Mean Time to Repair (MTTR) tracking
Customer impact assessment
Preventive measures documentation

UniAsset's incident timeline and notes provide the evidence needed for PUC reporting.

Utility-Specific Best Practices

Capture control system state - SCADA readings at incident time in notes
Document customer impact - Number of customers affected, duration
Reference work orders - Link external work management systems
Track mutual aid - Document if neighboring utilities assisted
Note weather conditions - Environmental factors in investigation notes

Common Patterns Across Regulated Industries

Severity Mapping

Both airports and utilities should standardize severity:

Severity	Airport Example	Utility Example
CRITICAL	Runway system failure	Substation outage
HIGH	Jet bridge down at busy gate	Feeder circuit failure
MEDIUM	GSE equipment failure	Smart meter batch issue
LOW	Terminal display malfunction	Office equipment failure

Timeline Management

Regulatory bodies expect specific timelines:

Industry	Reporting Requirement
FAA Part 139	Within 24 hours for safety-related
NERC	1 hour for cyber incidents, 24 hours for physical
State PUC	Varies, typically 24-48 hours

Use UniAsset investigation notes to document when each notification occurred.

Evidence Retention

Both industries require long-term record retention:

Record Type	Retention Period
Incident reports	5-7 years minimum
Maintenance logs	Life of equipment + 3 years
Certifications	Until superseded + 3 years

UniAsset retains all incident data indefinitely, satisfying all retention requirements.

Implementation Guide

For Airport Operations Managers

Inventory critical assets - Identify all FAA Part 139 equipment
Assign ownership - Ensure each asset has clear assignment
Upload certifications - Load all inspection certificates with expiry dates
Train operations - Ensure all shifts know incident reporting procedures
Test process - Run a drill with non-critical equipment

For Utility Asset Managers

Identify CIP assets - Know which assets fall under NERC CIP
Map to UniAsset - Ensure all regulated equipment is tracked
Document configurations - Load baseline configurations where applicable
Integrate workflows - Connect UniAsset incidents to work management
Audit preparation - Review incident history before annual audits

Frequently Asked Questions

Does UniAsset satisfy FAA/NERC requirements directly?

UniAsset provides the documentation and evidence management that supports compliance. Actual compliance depends on your complete program, not just software.

Can we customize fields for our industry?

Yes. UniAsset supports custom fields and categories that can be tailored to airport or utility terminology.

How do we handle confidential CIP information?

UniAsset's tenant isolation ensures your data is separated. For highly sensitive assets, use investigation notes judiciously and follow your internal security policies.

Can multiple departments access incident data?

Yes. Role-based access control allows Operations, Maintenance, and Compliance teams to view and contribute to incidents appropriately.

Does UniAsset integrate with our existing systems?

UniAsset provides data export capabilities. For specific integrations, contact your account representative.

Related Resources

Previous: Preparing for Audits After an Asset Failure

Topics: All Knowledge Base Articles

Need Help?

If you have questions not covered in this article, our support team is here to help.

Contact Support