How a 600-Person German Grid Operator Unified Field Crew Management Software

A regional grid operator in Bavaria came to us with a problem their SCADA Manager summarized bluntly: "Our field techs spend more time on the phone with dispatch than actually fixing equipment."

The company operates 2,400 km of medium and high voltage lines, 89 substations, and employs roughly 600 people. Their field operations team: 47 technicians across 6 service centers.

The Situation Before: Four Systems, Zero Coordination

The operations team had accumulated systems over 15 years of "solutions" to immediate problems:

SCADA (GE PowerOn) for real-time grid monitoring
SAP PM for planned maintenance and work orders
A 2009-vintage CMMS for equipment history (nobody trusted the data, but compliance required it)
Excel trackers and WhatsApp groups for actual daily dispatch

The Head of Grid Operations described morning dispatch meetings: "We'd have SCADA alerts from overnight, SAP PM work orders due this week, and emergency calls coming in. The dispatcher would alt-tab between four screens, then send WhatsApp messages to crews. If a tech needed equipment specs, they'd call the office. If dispatch needed location updates, they'd call the tech."

Sound familiar? We've seen this exact pattern at other utilities struggling with SCADA data silos.

The Problem: 11 Hours of Dispatch Overhead Per Day

We spent two days shadowing the dispatch team. The numbers:

Average phone calls between dispatch and field per day: 34
Average call duration: 8 minutes (including hold time while dispatchers looked up information)
Time dispatchers spent manually updating Excel after crew status changes: 2.5 hours/day
Work orders created in SAP PM that didn't reflect actual field work completed: 23% (found during monthly reconciliation)
Compliance documentation lag: 3-5 days between field work completion and proper system entry

The Grid Operations Manager put it this way: "We're paying senior technicians EUR 45/hour to sit in trucks reading us serial numbers over the phone. And we're paying dispatchers to be human middleware between systems that should talk to each other."

The annual cost of this coordination overhead, calculated during our assessment:

Phone coordination: 34 calls × 8 min × 260 days = 1,182 hours/year
Dispatcher manual entry: 2.5 hours × 260 days = 650 hours/year
Field tech admin time: estimated 45 min/tech/day × 47 techs × 260 days = 9,165 hours/year
Monthly reconciliation: 16 hours × 12 months = 192 hours/year

Total: ~11,189 hours/year
At blended rate of EUR 42/hour: EUR 470,000/year in coordination overhead

Here's what their dispatch workflow actually looked like:

flowchart TD
    A[SCADA Alert<br/>GE PowerOn] --> B[Dispatcher Views Alert]
    B --> C[Dispatcher Checks SAP PM<br/>for Related Work Orders]
    C --> D[Dispatcher Checks Excel<br/>for Crew Availability]
    D --> E[Dispatcher Sends WhatsApp<br/>to Crew Lead]
    E --> F[Crew Lead Calls Back<br/>for Equipment Details]
    F --> G[Dispatcher Looks Up<br/>Legacy CMMS]
    G --> H[Dispatcher Reads Info<br/>Over Phone]
    H --> I[Crew Drives to Site]
    I --> J[Crew Calls Dispatch<br/>for SCADA Readings]
    J --> K[Work Completed]
    K --> L[Crew Calls Dispatch<br/>with Status Update]
    L --> M[Dispatcher Updates Excel]
    M --> N[Dispatcher Creates SAP PM<br/>Service Entry - Later]
    
    style A fill:#ffcccc
    style D fill:#ffcccc
    style E fill:#ffcccc
    style F fill:#ffcccc
    style J fill:#ffcccc
    style L fill:#ffcccc
    style M fill:#ffcccc

Every red node is a manual handoff. Every handoff is a delay, an error opportunity, and a compliance risk.

What We Built: Field Crew Management Software That Actually Integrates

The request from the Grid Operations Manager was specific: "I don't want another system. I want the systems we have to work together, with one interface for dispatch and one for field crews."

We delivered a working prototype in 7 days. Full deployment across all 6 service centers took 8 weeks.

For Dispatchers (Desktop Dashboard):

A unified view pulling real-time data from:

SCADA alerts with automatic severity classification and affected asset mapping
SAP PM work orders with crew skill matching
Live crew locations (GPS from tablets) and current status
Equipment specs and recent maintenance history from the legacy CMMS

Dispatchers drag-and-drop to assign work. The system handles the rest: work order creation in SAP PM, crew notification, documentation packet assembly.

For Field Crews (Ruggedized Tablet Interface):

Current assignment with all relevant SCADA readings pre-loaded (updated every 60 seconds)
Equipment specs, schematics, and last 5 maintenance records (pulled from legacy CMMS via API we built)
One-tap status updates that simultaneously update Excel tracker (for managers who insisted), SAP PM, and dispatch dashboard
Photo capture with automatic metadata tagging for compliance documentation

The Technical Details That Made It Work:

The legacy CMMS had no API. We built a parser that reads its nightly database export and handles 23 different equipment record formats accumulated over 15 years of data entry inconsistency. Equipment IDs alone had 4 different naming conventions depending on when they were entered.

The SAP PM integration required handling their customized work order types. 31 custom fields their SAP consultant added in 2014. We mapped each one.

SCADA integration via OPC-UA, polling every 30 seconds for alerts, every 60 seconds for readings crews might need.

sequenceDiagram
    participant SCADA as GE PowerOn<br/>SCADA
    participant Platform as TIMPIA<br/>Platform
    participant SAP as SAP PM
    participant CMMS as Legacy CMMS
    participant Dispatch as Dispatcher<br/>Dashboard
    participant Field as Field Crew<br/>Tablet

    SCADA->>Platform: Alert (OPC-UA, 30s polling)
    Platform->>Platform: Classify severity,<br/>map to asset
    Platform->>SAP: Check existing work orders
    SAP-->>Platform: Related WOs
    Platform->>CMMS: Pull equipment history
    CMMS-->>Platform: Last 5 maintenance records
    Platform->>Dispatch: Unified alert + context
    Dispatch->>Platform: Assign to Crew 3
    Platform->>SAP: Create work order
    Platform->>Field: Push assignment + docs
    Field->>Platform: Status: En route
    Platform->>Dispatch: Update (real-time)
    Field->>Platform: Status: Work complete + photos
    Platform->>SAP: Close work order
    Platform->>CMMS: Log maintenance record
    Platform->>Dispatch: Update (real-time)

The key architectural decision: the platform is the integration layer, not a replacement for existing systems. SAP PM remains the system of record for maintenance. SCADA remains the monitoring authority. We just eliminated the human middleware.

For context on why we built custom instead of connecting existing tools, this post on outgrowing no-code solutions explains the breaking points.

The Results: Before and After

Measurements taken 90 days after full deployment:

Phone Calls Between Dispatch and Field:

Before: 34 calls/day
After: 6 calls/day (complex situations only)
Reduction: 82%

Dispatcher Time on Manual Data Entry:

Before: 2.5 hours/day
After: 20 minutes/day (exceptions only)
Reduction: 87%

Average Time from SCADA Alert to Crew Dispatch:

Before: 23 minutes (including phone coordination)
After: 4 minutes
Reduction: 83%

Work Order Accuracy (field work matching SAP PM records):

Before: 77%
After: 96%
Improvement: 19 percentage points

Compliance Documentation Lag:

Before: 3-5 days
After: Same day (automatic)
Reduction: 100%

Estimated Annual Savings Calculation:

Eliminated coordination hours:
- Phone time: 28 fewer calls × 8 min × 260 days = 970 hours
- Dispatcher entry: 2.2 hours saved × 260 days = 572 hours
- Field admin: 35 min saved/tech/day × 47 techs × 260 days = 7,121 hours
- Reconciliation: 12 hours saved × 12 months = 144 hours

Total hours saved: 8,807 hours/year
At EUR 42/hour blended rate: EUR 370,000/year

Implementation cost: EUR 89,000
ROI timeline: 2.9 months

The Grid Operations Manager's summary after 90 days: "My dispatchers dispatch. My technicians fix equipment. Nobody reads serial numbers over the phone anymore."

What This Means for Audit Prep

A secondary benefit the Compliance Lead hadn't anticipated: audit preparation time dropped dramatically.

Before: Compliance documentation for quarterly EU Network Code reporting required pulling data from four systems, cross-referencing manually, and formatting for submission. Three people, four days.

After: One click generates the report. Compliance Lead reviews for 2 hours, submits.

The field crew management software we built wasn't designed for compliance. But when every field action is logged with timestamps, photos, and equipment IDs at the moment it happens, compliance documentation becomes a byproduct of operations, not a separate project.

Would This Work for Your Operations?

The pattern we solved for this Bavarian grid operator appears in nearly every mid-market utility we've assessed:

Multiple systems that don't talk to each other
Field crews as the "last mile" of manual data entry
Dispatchers as human routers between systems
Compliance documentation that happens days after the work

If your field crew management looks like the "before" diagram, we can show you the "after" in 7 days. The proof-of-concept costs EUR 3,500, connects to your actual systems (SCADA, SAP PM, whatever legacy CMMS you're running), and you keep the working prototype regardless of whether you proceed.

Book a technical assessment and bring your messiest integration challenge. We'll show you what unified field crew management software actually looks like with your data.