CPS Energy: Smart Streetlight & Smart City Operations

San Antonio's streets were going dark, residents were losing confidence in a city service nobody could explain, and the repair loop, spanning resident intake, SAP, dispatch, and field crews, had no clear owner. I took accountability for the product, program, and service design that connected all of it, cutting repair calls by 73%, shrinking repair windows from roughly 3 weeks to 1–4 days, and reducing truck rolls by 43%.

CPS Energy smart streetlight program
At-a-glance

Smart City Modernization

San Antonio had 200K+ streetlights and a repair process that was breaking down at every handoff. I owned the product and program work to rebuild it, from resident intake through field execution to system integration, delivering measurable reductions in call volume, truck rolls, and repair time.

73%
Fewer repair calls
43%
Fewer truck rolls
1≤4
Day repair window (from ~3 weeks)
200K+
Streetlights in scope
Problem Statement

Homes in Darkness

San Antonio residents were dealing with dark streets, slow repair timelines, and a broken support experience. The problem was bigger than maintenance: the workflow was fragmented across resident intake, call-center, SAP, dispatch, field updates, and follow-up orders. Ownership was unclear across CPS Energy and Dalkia, and the service model was opaque. Project drama played out in public.

Client
CPS Energy
Industry
Public Utilities / Smart City
Timeline
August 2024 – April 2025
Tools Used
Figma
Figma
Azure
Azure
SAP
SAP
Smartsheet
Smartsheet
For us, this is more than just a streetlight program, it's about creating a safer, greener, and more connected San Antonio. By embracing smart technologies, we are enhancing public safety, improving energy efficiency, and paving the way for a more sustainable future.
Richard Medina
Richard Medina
Chief Energy Delivery Officer, CPS Energy
My Role

Program & Product Lead

6 systems to integrate. 15 people across two organizations that didn't naturally agree. I held the product direction, the program structure, and the accountability that made it all move.

Program LeadershipProduct DirectionService DesignSystem Integration
6
System integrations
$2M
Program budget
15
Team size
8 mo
Program timeline

I Made the Machine Work Together

The street-level symptoms were visible: dark lights, slow repairs, residents calling in the same outage multiple times because nobody closed the loop. The real problem was inside the operation. Ownership was split between CPS Energy and Dalkia with no clear model for who owned what. The workflow ran across SAP, IVR intake, dispatch, and field follow-ups in a way that reliably lost orders between steps.

I owned the product direction for resident reporting and the field operations workflow. I drove SAP to the top of the integration roadmap over competing priorities, a decision that unlocked the critical path. I partnered with engineering to built a proof of concept and used it to end all scope debates. This pushed the project into successful delivery.

1
Built the in-field iPad workflow that gave Dalkia crews real-time work orders, status updates, and a direct data connection back to CPS systems.
2
Owned the resident reporting product so anyone could find the exact streetlight, submit the issue, and get status back without ever having to call.
3
Forced SAP integration to the top of the roadmap, held it against competing priorities, and drove it through to a clear delivery path.

This project directly benefitted 1.5 million people in a meaningful way, and changed the course of smart city projects. Plus, we won an award.

Solution

We Built Perpetual Motion Green Tech for Smart Cities

One front door for residents. One operational flow for crews. One service model CPS could actually run. This was not a feature rollout, it was a restructured digital product pipeline.

In This Project, Ditigal Tech & The Streets Danced Together

Yes, the issue started with smart bulbs, but it was really about lack of end-to-end ownership. Residents reported outages and heard nothing back. Crews showed up to jobs with incomplete orders. Operations had no real-time picture of what was happening across 200K streetlights. The work rebuilt those connections so a report from the street or a ping from a smart streetlight could make automation valuable for $1.5 million people.

1
Digital issue submission by customers + autmated outage tracking reduced city services burden & cash burn across the board.
2
Real-time field updates replaced follow-up orders that could disappear between teams.

As you'll see in the Press & Accolades section below, this project moved the needle from 'pitchforks & torches' to 'international awards.'

Impact

The Results I Drove

Our war was fought on three fronts: customer experience, crew operations, and the public budget. I led us to victory on all three.

Bad Press
PM Leadership
Good Press
73%
Fewer repair calls
43%
Fewer truck rolls
1≤4
Day repair window
200K+
Streetlights in scope

Before & After

A coherent digital transformation turned fragmented systems into a unified repair & reporting pipeline residents and operators could trust.

Before

Fragmented

  • Residents used inefficient channels with no visibility.
  • Operations were fragmented and lost
  • No ownership across CPS, Dalkia, and city ops.
After

Connected

  • Digital reporting gave residents a front door & visibility.
  • In-field iPads connected crews & systems in real time.
  • One clear operating model aligned all operations.
1

In-field iPad Workflow

I drove alignment around in-field iPads tied to Dalkia & CPS systems so crews could receive work + update status in real time, closing the gap between systems and execution.

2

Resident Reporting UX

I led the UI and product direction for a customer reporting experience. Residents could identify their exact streetlight outage and get it fixed.

3

SAP Prioritization & Stakeholder Alignment

I brought the right stakeholder groups together to prioritize SAP work over competing roadmap items and kept negotiations moving until we delivered an award-winning technical program.

Implementation

Delivery Phases

The Time Between Dark Homes and Global Recognition

5 phases across 8 months. The first two were about finding root causes and getting two organizations to agree on what they were actually building. The middle phase was design and integration work. Finally, proof of concept and launch, holding the operating model together through go-live.

Phase 01

Diagnose

Map breakdowns across intake, dispatch, and systems.

Phase 02

Align

Lead CPS & Dalkia to agreement on scope, ownership, and the product.

Phase 03

Design

Define resident reporting UX, in-field iPad workflow, and SI path, SAP, Terrago, GIS.

Phase 04

Prove

Used POC as a force function to drive stakeholder debate to delivery.

Phase 05

Launch

Deploy repair workflow systems, close resident-to-operations loop, track service outcomes.

This is the city's first official initiative to widely install solar-powered LED street lights within city limits. Together we are lighting the path to a brighter future!
Ron Nirenberg
Ron Nirenberg
Mayor, San Antonio, TX