Skip to content
Okko Oulasvirta
Energy & Utilities

Customer & Contract Workspace

One view of a customer's connections, contracts, consumption and open issues, so the person serving them can resolve it in one contact.

The decision it supports

What does this customer hold and owe, what is going wrong, and what is the right resolution?

What changes

Faster resolution, fewer transfers, and advisers who can see supply, billing and service as one relationship. Actions are logged against the customer.

Data domains

  • Customers
  • Contracts and tariffs
  • Metering
  • Finance and cost
  • Field service

Interactive preview

Customer & Contract Workspace is described here as an opportunity rather than shown as a working demonstration. The interactive build for this industry is Asset Health & Field Operations Twin — it uses the same primitives, the same governed data model and the same decision-to-action pattern this application would.

We build one flagship per industry properly rather than four shallow ones. The pattern transfers.

The workflow

  1. 01The customer and their connections are recognised across systems
  2. 02Contracts, tariffs, consumption and open cases are shown together
  3. 03The likely cause of a query — a bill, an outage, a meter — is surfaced
  4. 04Resolution options are proposed with the reason for each
  5. 05The adviser acts — an adjustment, a job or an update
  6. 06The action is written back and logged against the customer

Platform capabilities most relevant here

  • OneLake

    One governed copy of enterprise data that analytics, AI and applications can all build on.

  • Curated business entities

    Agree once what an order, an asset or a customer means — then reuse it everywhere.

  • Generated data APIs

    Let application teams consume governed data without rebuilding the data foundation.

  • Fabric Apps

    Build the application where the governed data already lives, instead of copying it out.

  • Application state

    Remember decisions, assignments and approvals — the things a report cannot hold.

  • Microsoft Entra identity

    People see exactly the data they are entitled to see, in the application as well as the report.

  • Enterprise APIs

    Turn a decision into a change in the system that actually runs the process.

Not every application needs every capability. This is the subset that this decision actually depends on.

Talk about building this