Manage Your Critical Situations with OpFab
summary
Operator Fabric (OpFab) runs in production at RTE for two years after four years of development and coordinates real‑time crisis actions across eight control rooms, using templated cards to transmit structured orders (example: shedding 200 of 500 MW in a region) and showing status changes live. It averages under 10 cards per day in normal use, supports API + Kafka integration for other systems, offers maps and customizable templates (cards require JavaScript to extend, not a UI), and cuts phone traffic while keeping ~100 active users per project.
AI-written summary · about
chapters (7)
- 0:00Introduction to Operator Fabric
- 1:26What is a TSO and control rooms
- 3:12Main features of Operator Fabric
- 5:22Crisis management use case
- 7:57Operator Fabric in the LF Energy ecosystem
- 9:24Conclusion and resources
- 16:27User feedback and usability
related talks
31mTSO-DSO Coordination Using OperatorFabric
40mExtreme Ops: Platform Operations at The Home Depot
31mConnecting LF Energy’s Projects: A Mini-City Prototype for the Digital Grid Ecosys...
15mSystematising Production Operations: Reddit Control Tower
15mHow Our SREs Safeguard Nanosecond Performance—at Scale—in an Environment Built to Fail
34mGrid Enhancement Platform: Operationalizing Open Source for Real-Time, Risk-Aware Gri...
22mBuilding Building Blocks
32mService Fabrik – Manage Enterprise-Grade Backing Services for an Enterprise-Grade Cloud Foundry