OBLYTECH Logo
OBLYTECH Logo
Energy & Utilities

Why Choose Oblytech for Your Energy & Utilities IT Needs?

The energy and utilities sector is undergoing a significant transformation, driven by the need for sustainable energy sources, smart grid technologies, and improved operational efficiency. Oblytech understands the complex challenges faced by energy and utility companies, and we offer IT solutions that help them optimize operations and deliver reliable services to their customers.

Shot of a young group of businesspeople using a computer while working in the office at night.

Our Data Migration & Integration Services

Implement smart grid technologies to improve energy efficiency, reduce costs, and enhance grid reliability.

Enable real-time energy consumption monitoring and data collection for better demand forecasting and customer engagement.

Streamline outage response and restoration, improving customer communication and reducing downtime.

Optimize asset performance, maintenance, and lifecycle management for improved operational efficiency and cost savings.

Integrate renewable energy sources into your grid, supporting a sustainable energy future.

Use data analytics to gain valuable insights into energy consumption patterns, identify inefficiencies, and optimize resource allocation.

Migrate your applications and data to the cloud for enhanced scalability, agility, and cost-effectiveness.

Streamline IT service management, incident response, and change management with ServiceNow’s solutions.

Who this page is for inside a utility

This page is for the operators of electricity, gas, water and district energy businesses who are deciding how far their service management platform should reach. The usual readers are the head of IT operations, the director of customer operations, a network or field services manager, and the person responsible for regulatory reporting. Each of them has a different picture of what a platform should do. The field manager thinks of crews and restoration. The customer director thinks of call volumes during an outage. The regulatory lead thinks of records that must be kept for a review.

The page does not cover the control systems that run generation, transmission or distribution equipment. Those sit in the operational technology estate, where safety and availability rules are different, and a service management platform should not be the system that issues commands to them. Keeping that boundary explicit is the first design choice a utility should make.

Where the IT and operational technology boundary sits

Utilities run two estates side by side. The information technology estate holds customer accounts, billing, asset records, work orders and corporate services. The operational technology estate holds the systems that monitor and control physical equipment. The two are connected, usually through a small number of interfaces that carry readings, alarms and status. A workflow platform should sit on the information side of those interfaces. It can receive an alarm, open a case, route it to a crew and record the outcome. It should not be designed to change the state of a substation.

That boundary also affects who approves a change. A configuration change to a work order form is an information technology change. A change that alters how an alarm is interpreted by a control room is an operational change, and it belongs in the process the operations team already uses for safety-critical changes. Mixing the two often produces a change board that people stop trusting.

Outage and restoration as the first real test

A storm, a flood or an equipment failure is the moment when a utility’s service workflows are actually tested. Customers call in large numbers, field crews need to be dispatched in an order that reflects safety and the number of people affected, and the status shown to the public has to be consistent with what the control room knows. A platform that handles routine work well may still fail under that load if the routing rules were never designed for a surge.

Event typeWho must actInformation the crew needs before arriving
Single customer supply faultLocal field teamPremises reference, meter reading history and access notes
Street or feeder outageControl room with a field supervisorAffected customer count, switching status and safety isolation point
Storm damage across a regionIncident commander with mutual aid crewsPriority list, road access status and the restoration sequence agreed by operations
Public safety hazard reportNearest qualified crew, with immediate escalationLocation, the reporter’s description and any known hazard already logged

The incident and major incident management page covers incident and problem management on the platform. The field service coordination page covers field service case coordination from assignment through closure. The buyer’s own question is which of these events are routed automatically and which must stay with a person who can make a judgment about safety.

Asset records carry most of the workflow

Much utility work depends on an accurate picture of assets: what is installed, where it is, what it connects to and when it was last inspected. When those records are wrong, every workflow built on them inherits the error. A crew may arrive at the wrong transformer, a maintenance schedule may skip a critical asset, and a fault report may point to equipment that was replaced years earlier. The configuration management and asset lifecycle pages cover configuration data and asset lifecycle ownership on the platform. The practical point for a utility is that asset data ownership needs a name, a review cycle and a way for field staff to correct a record from the field, rather than only from the office.

  • Establish one authoritative source for each asset class, with the owning department named in the record.
  • Give crews a short, mobile route to report a mismatch between the record and the site.
  • Review the high-consequence assets, such as those tied to critical customers, more often than the rest.
  • Keep a history of changes so that a restoration decision can be explained after the event.

After every significant event, the record of decisions should be reviewed while the people involved still remember the sequence. A short review that compares the routing decisions with the restoration order shows which rules helped and which slowed crews down. The changes that follow are small and specific, and they are far more useful than a general lessons-learned document written weeks later.

Renewable and distributed connections are an integration problem

Connecting renewable generation, storage and customer-owned equipment to the grid adds integration load that older utility processes did not anticipate. Applications for connection, inspection requests, metering changes and status updates arrive from many parties, in many formats, and many carry a regulatory deadline. A workflow platform can carry that process well if the integration points are defined clearly: what data the applicant submits, which internal system validates it, what the status means for the applicant, and who is accountable when a deadline is at risk.

The enterprise platform integrations page covers connecting the platform to other systems around a service journey, data ownership and failure paths. For a utility, the difficult part is agreeing the status model, because an applicant seeing “in progress” may mean very different things to the engineer, the commercial team and the customer.

Questions to ask before a utility commits to a scope

A provider should be able to say how the platform would be separated from operational technology, and how that separation would be tested. Ask which events would open cases automatically and which would require a human decision, and what the provider has done to keep both lists short. Ask how the platform behaves when the network to a field crew is down, because rural and storm-hit areas are often where connectivity fails. Ask how the records needed for regulatory review are produced, and how they are retained. Finally, ask how many people in the utility’s own operations team would be able to change the routing rules, and whether those changes are reviewed before they take effect.

Common questions from utility IT and operations leaders

Can a workflow platform control equipment in the field?

It should not be designed to. A platform can dispatch work, record a status and receive a reading from an integration. Commands that change the state of physical equipment belong in operational technology systems with their own safety processes.

Where should we start if our asset records are weak?

Start with the assets that carry the most consequence if they are wrong. Correct those records first, assign owners and build the field correction route before expanding the workflow to other asset classes.

How do we keep the public status consistent during an outage?

Agree one status source and one set of status words before the event. The public message should be generated from the same record the control room and crews use, not typed separately by each team.

Does this change the regulatory evidence we keep?

It can improve it, because the records of decisions, dispatches and restorations are created as the work happens. The retention rules still come from the regulator and from your own obligations, and the platform has to be configured to meet them.

Next step for utility operations leaders

If your utility is considering a wider role for its service management platform, the most useful first conversation is about where the boundary with operational technology sits and which outage workflows must be designed first. Operators in manufacturing can see how that sector is described on the manufacturing page.

Energy and utilities IT: what to build first and what to leave alone

For an energy or utilities business, the sensible order is to fix the information workflows that touch customers and crews first, then connect alarms, and only then widen scope. Anything that changes the state of physical equipment should stay outside the service platform.

The reason is simple. Early wins come from work that already happens on paper, in email or in a spreadsheet: logging a fault, assigning a crew, recording what was done. Those steps are low risk and easy to check.

A practical sequence

  • Start with the fault and work record: one place where a report becomes a job, with an owner and a closing note.
  • Add the asset reference next, so each job points to a record that someone is responsible for.
  • Bring in alarms and readings from monitoring systems only after the job record is stable. Filtering them before they open cases matters, because a flood of automatic cases buries the real ones; the event management and alert correlation page explains the idea.
  • Leave the extra integrations, such as connection applications and partner portals, until the first three are trusted.

A decision rule for each new automation

Before adding a rule, ask three questions. Could a wrong result put a person at risk? Could it be undone by a person within minutes? Does a named operations role agree to own it? If the first answer is yes, the rule does not belong on the service platform. If the second is no, a person should approve it before it runs. If the third is no, do not build it yet.

Common mistakes

  • Designing only for the storm day. Routine faults show the team how the process behaves before it is stressed, and the routing rules still need a surge check.
  • Letting each department invent its own status words, which makes the public message inconsistent.
  • Skipping field testing. Ask crews, not only office staff, to run the new steps with a poor connection; the business-owned UAT article covers how to plan that validation.
  • Changing routing rules without review. Treat rule changes as controlled changes, as described under change governance and release management.

How do we know the first phase worked?

Look for plain signs: crews close jobs with notes that another person can follow, the control room and the customer team quote the same status, and a manager can reconstruct a restoration decision a week later without asking around.

Customer requests that never reach a crew still need a routing rule

A utility customer request belongs in self-service when the answer already sits in the customer’s account and nothing needs a judgment call. It goes to a person when it changes money owed, changes a supply point, or depends on a reading that someone has to check. Many non-fault requests can be sorted into one of those two groups, though some will need a judgment call.

Many of the things customers ask a utility have nothing to do with a fault: a bill they do not understand, a reading they think is wrong, or a connection not yet energised. Each still needs an owner, or the request waits in a shared inbox.

RequestRouteWhat the agent needs on the case
Bill explanation with no disputed chargeSelf-service, with a case if the customer still disagreesTariff, billing period and the line items
Meter reading disputePerson, with the device history attachedReading history, meter identifier and last access date
Move-in or move-out supply changePerson, with a scheduled datePremises, effective date and the meter read at the change
Connection timing questionSelf-service if the stage is recorded, person if it is notApplication stage and the next recorded step

The routing decision belongs at case creation. The case should carry the account, the supply point, the request type and its response deadline, so the agent does not start by asking the customer to repeat themselves. The customer service case routing approach sets out how queues and assignment rules are built for this kind of work. The customer self-service portal decides which answers the customer can read directly and where the portal should hand off to a case.

Self-service works best while the knowledge behind it is current. Give each billing article an owner and review it whenever the tariff wording changes. The knowledge and self-service review covers how to keep those answers useful.

Check the routing once a month for the first quarter after go-live. Count the cases that were reassigned from one queue to another. A rising count usually means a request type has been placed in the wrong category. A typical fix is a change to the routing rule rather than more agents on the queue.