DCP MIDSTREAM · 2018–2020 Field Reporting · Oil & Gas Compliance

EVE Mobile Environmental Events Reporting — lead designer, six states

A field-reporting app that let gas controllers and environmental engineers document spills, leaks, and emissions the moment they happened — with gloves on, in direct sun, on a signal that came and went.

6
States covered
8
Field operators tested
4
Oil & gas regions
2,500
Field users on launch
Learn — The Problem

A reporting tool nobody trusted

Environmental events — gas leaks to atmosphere, spills to soil, spills to water — trigger different regulatory workflows in every state DCP operates in. Some are rigorous, some relaxed. The legacy tool, OPSTools, had a bad reputation in the field and low adoption. Operators worked around it instead of through it.

My goal: capture events in the moment, route the right data to EHSS/Enablon for emissions and spill calculations, and make the whole thing simple enough that a field operator would actually reach for it under pressure.

Field Incident — Sample Scenario

Operator Billy Ops, Giddings Gas Plant, Permian TX. Condensate breaches secondary containment from Tank 3A, flows toward a pond.

He shuts off the pump, notifies his supervisor, photographs the site, and logs the event on his phone — before ever reaching a desk.

Learn — Research

Built the flow with the people who'd use it

I met with Environmental Specialists, Managers, and Operators to walk through an initial hypothesis flow, then challenged it directly against how people actually work a spill in the field. That produced a simple four-part sequence — Location → Impact → Details → Review — with a modular recording step so an event could be logged as air, soil, water, or any combination, instead of forcing operators through fields that didn't apply.

  • 8+ field & plant operators
  • 8+ environmental specialists & managers
  • 4+ technologists
  • Tested on-site across Permian, Midcon, Panhandle, and Northern Colorado

I led the project and was the face of it for every user and region involved — directing a research/design consultant's time on this work, and coordinating with the designer building the shared component library that Eve's funding and priority made possible.

Build — The Interface

Map-first, offline-first, gloves-on

In the field, operators report while managing an active situation — often wearing gloves, in direct sunlight, with signal that drops in and out. That ruled out the dense, form-heavy pattern of the legacy tool. I replaced it with a map-first interface built to work with no connection at all, syncing the moment signal returned.

9:41●●●● 🔋
EVE · Report Event

⚠ Offline — changes will sync when signal returns

LocationGiddings Gas Plant · Tank 3A
TypeSpill — Soil + Water
Discovered09:12 · Billy Ops
Photo1 attached
Continue to Details →
📍 Location💧 Impact📋 Details✓ Review
Stage 1–2 · Location → Impact
Recreated for illustration — DCP's actual UI is proprietary, not shown here.

What changed from the legacy tool

  • Modular by design — air, soil, water, or a combination, instead of one rigid form
  • Offline-first — every field logs locally and syncs later, no lost reports on dead signal
  • Photo + location first — evidence captured before the operator has to type anything
  • State-aware routing — the same flow adapts to each state's Enablon/EHSS requirements underneath
Build — Delivery

Two builds, driven by what testing surfaced

VersionWhat shipped
V1Enhanced OPSTools with Enablon fields for every state workflow. Virtual usability testing across all regions.
V2Full rebuild on a new Angular Material design system, then Ionic Mobile. Validated on-site, in the field, across all four regions.
Test — Usability Validation

Honest results, not a highlight reel

Eight field operators tested the full flow on location. The library and its overall value validated at 8/8 — but individual moments in the flow told a more specific story about where the design still had work to do.

4 / 8
Understood exactly when the spill was first discovered
4 / 8
Gave varied responses on equipment detail fields
6 / 8
Understood the four-stage sequence correctly
8 / 8
Validated the tool and its library as valuable

Validation framework: 8/8 = validated · 5–7/8 = marginal, needs rework · <5/8 = invalidated. The discovery-moment and equipment-detail gaps directly shaped the V2 rebuild.

Deliver — Outcome

From workaround to standard

100%
Increase in reporting efficiency
1
Standard workflow, six states
2,500
Field users connected day one
6
States meeting compliance
3
SaaS offers — Shell, Exxon, Phillips 66
3
Legacy tools sunsetted
Field-Proven Pattern

The same structure, eight years later

The Location → Impact → Details → Review sequence validated here in 2018 became the backbone of Earth Steward, my 2026 MIT xPRO capstone — proof this pattern holds up across an entirely different domain, from oil-field spills to forest stewardship.

See it applied in Earth Steward →