Back to blog
Industry Jan 20, 2026 5 min read

Energy & Utilities: Modernizing Grid Management and Asset Tracking Systems

A North American utility we worked with runs 312 Oracle Forms screens to dispatch field crews and track substation assets. The system was built in 1998. It still processes every outage ticket the company receives.

In utilities, “still works” is the highest compliment a system can earn. It’s also the reason these estates rarely get touched.

What’s actually inside a utility Forms estate

Energy and utility Forms applications tend to manage the most operationally critical workloads in the enterprise:

  • Asset lifecycle tracking for substations, transformers, and meters
  • Work order management for field crews
  • Outage management and restoration tracking
  • NERC CIP regulatory reporting
  • Customer billing and meter reading

The cost of a failed migration here isn’t measured in lost productivity. It’s measured in blackouts.

What’s pushing modernization to the top of the list

Four forces are now stronger than the inertia.

SCADA integration. Streaming sensor data from the grid needs to flow into asset management in real time. Oracle Forms can’t consume a sensor feed.

Mobile field access. Line workers want to update work orders from a tablet at the pole, not a desktop back at the yard. Forms is desktop-bound by design.

Predictive maintenance. Combining asset age, weather data, and historical failure rates to forecast equipment failure requires an analytics layer Forms simply doesn’t have.

Regulatory dashboards. NERC CIP compliance now expects real-time monitoring of cybersecurity controls, access logs, and configuration drift. Manual extraction at audit time no longer clears the bar.

Why parallel operation is non-negotiable

Utilities can’t accept operational disruption during migration. Our approach runs the new TypeScript application alongside the Oracle Forms system, both connected to the same Oracle Database through a secure REST API layer. Field crews keep working in Forms while we validate the new application module by module.

The cutover only happens once testing confirms identical behavior — same calculations, same validations, same business rules, same outputs against the same inputs. For energy companies, that parallel operation period isn’t a luxury. It’s the entire migration strategy.