Milad Ekrami Nia

Outage Management System

Outage Management System

A modern command center for utility operations

Modern Outage Management System (OMS) for electricity distribution companies — enabling faster detection, smarter response, and rapid restoration of power outages.

ScopeMission-critical operations
StackReact + TypeScript
OutcomeEfficient Outage Management System
RoleLead Senior Frontend Engineer

Project Overview

// section.overview

01
A unified platform for utility operations and incident response.
Built to support fast, informed decision-making in complex environments.

A modern digital platform for managing power outages

The Kesinti Yönetim Sistemi (KYS / Outage Management System) is a comprehensive web-based platform developed for electricity distribution companies in Turkey. It helps control center operators and field teams quickly detect, analyze, manage, and resolve both planned and unplanned power outages across the Turkish electricity grid.The system integrates with SCADA, GIS, and customer information systems to deliver real-time visibility, intelligent incident management, and coordinated restoration efforts — ultimately reducing outage duration and improving service reliability for millions of customers.

A complete digital transformation for auto service centers
Operational visibilityReal-time awarenessBring outage activity, alerts, and system status into one view.
Workflow efficiencyStreamlined executionReduce manual coordination and eliminate fragmented processes.
Decision supportContext-rich insightsLeverage interactive maps and structured data to guide response.
Responsive performanceFast, reliable interactionsKeep critical workflows smooth across dashboards, maps, and incident views.

Project Problem

// section.problem

02

Slow and fragmented outage response in Turkey’s distribution network

The main challenge for Turkish electricity distribution companies was the absence of a unified, modern, and user-friendly system to manage power outages effectively. Control center operators and field teams were forced to work with outdated manual processes, fragmented tools, and disconnected systems. This resulted in slow response times, heavy reliance on phone calls and paper-based records, and significant operational inefficiencies.
Delayed detection and inaccurate localization of outages
Lack of real-time visibility across the grid and affected customers
Difficult coordination between control center, field teams, and customer service
Manual incident logging and tracking
Challenges in providing accurate restoration times to customers
Low overall productivity due to complex and time-consuming workflows
Difficulty in generating reliable reports for EPDK compliance

Stakeholder Needs

// section.stakeholder.needs

03
What operations leaders and dispatch teams required from the platform.

Real-time situational awareness

Surface outages, impacted areas, and crew status in a single dashboard so operators can act quickly.

Fast, reliable workflows

Enable dispatch and incident management flows that reduce manual handoffs and improve team coordination.

Actionable reporting

Deliver clear operational metrics and exports for compliance and post-incident review.

Rapid incident triage

Make it easy to identify priority issues, review details, and escalate without unnecessary clicks.

Clear operational hierarchy

Present the most critical signals first so teams stay focused when timelines are tight.

User Needs

// section.customer.needs

04
The needs that shaped the experience for operators and field teams.
Fast access to outage status and impacted customer information.
A stable interface that performs under pressure for control room operators.
Seamless transitions between incident tracking, team dispatch, and communications.
Interactive map views that provide spatial context for outage response.
Responsive interactions that support quick reviews on desktop and tablet workflows.
Clear visual hierarchy for alerts, severity, and next actions.

Design Process

// section.design.process

05

  1. Requirements

    Gathered product needs, technical constraints, and stakeholder priorities.

  2. Architecture

    Defined component structure, layout systems, and data flow for the app.

  3. Development

    Built responsive UI components, interactive dashboards, and map views.

  4. Design System

    Integrated reusable tokens and visual patterns for consistency.

  5. Integration

    Connected UI components with real-time outage data and backend APIs.

  6. Quality

    Validated behavior with testing, accessibility checks, and performance review.

  7. Delivery

    Deployed the frontend and documented the handoff for future development.

Solution

// section.solution

06
A modern frontend platform designed for mission-critical utility operations.

Interactive dashboards

Dashboard

Built responsive dashboards that surface outage alerts, incident status, and key operational metrics in real time.

Incident workflows

Workflow

Implemented structured outage and notification flows to improve coordination between control room and field teams.

Map-first operations

Maps

Created interactive geospatial views that reveal outage impact and help teams locate affected assets quickly.

Component-driven UI

Frontend

Built reusable interface modules for tables, filters, alerts, and detail panels so the experience stayed scalable and consistent.

Key Screens

// section.key.screens

07
Core interfaces that power the platform experience.
Operations Dashboard
Outage Management
Notifications Center
Map View
Reports
Reports
Reports
Reports
Reports
Reports
Reports
Reports
Reports
Reports

Key Learnings

// section.learning.reflections

08
Insights gained from building a demanding operational platform.
01

Design for scale

Built a modular frontend structure capable of supporting future analytics, reporting, and field operations features.

02

Prioritize clarity

Focused on clear data presentation and streamlined interactions so operators can work faster with less error.

03

Balance depth with usability

Delivered a rich operational experience without overwhelming users with too much information at once.

04

Build for reliability

Designed interactions and data flows to stay dependable even during peak load and changing incident conditions.

05

Adapt to varied teams

Worked across teams with different processes, priorities, and technical experience while keeping delivery aligned.

06

Balance customer and technical needs

Managed customer expectations and operational requirements while shaping the frontend solution for real-world constraints.

Next Project

Continue to my design system work

Front-End Developer

tailwind
react
mui
next
ts
profile

Let's Talk

Ready to build something great together?

I'm currently available for new opportunities and exciting projects.
Feel free to reach out — I usually reply within 24 hours.