Skip to main content
Back to selected work

Convergent IS / Energy / AI Workflows

87% fewer manual touch-points in field ticketing with Rio.

Rio turns hydrocarbon field tickets into approved SAP service entry sheets through AI extraction, exception handling and orchestrated approvals.

Role
Staff Product Designer, end-to-end UX
Team
North American energy operator
Company
Convergent IS

87%

Fewer manual touch-points

Zero

Re-keying into SAP

One

Connected operational workflow

SAP

Automated service-entry posting

The Problem

Contractor labour, equipment and materials sheets arrived as paper tickets, duplicated, error-prone and re-keyed by hand into SAP through multiple touch-points.

What I Did

Led the design of an AI-powered workflow for automated ticket extraction, purchase-order validation, exception-first review and orchestrated approvals.

The Outcome

Rio cut manual touch-points by 87%, replacing manual re-keying with one connected system across field and back-office operations.

The redesign at a glance

SES flow prototype showing how Rio moves field tickets through extraction, review, approval and SAP posting.

Decision 01 / 03

Let extraction do the typing.

Field tickets carry dozens of labour, equipment and materials lines. Rio extracts them into structured draft sheets automatically, shifting the reviewer's job from data entry to verification while keeping every value traceable to its source.

Result → manual touch-points down 87%

Rio extracts field-ticket data into a structured draft ready for verification.

Decision 02 / 03

Review only what needs reviewing.

Every extracted line is validated against the purchase order. Clean sheets flow through untouched; only mismatches ask for human attention, with a reason captured for every accepted exception or rejected line.

Result → errors caught before they reach SAP

Exception handling focuses attention on mismatches that need human judgment.

Decision 03 / 03

Approvals as a workflow, not an inbox.

Construction managers, coordinators and back-office roles see the sheets waiting on them as sequenced tasks with clear statuses. When the final approval lands, Rio posts the service entry sheet into SAP automatically.

Result → zero re-keying into SAP

Role-based approvals are sequenced and tracked through to SAP posting.

The tradeoff

Automate the work, not the judgment.

Full automation was technically possible, but these sheets move real money against contracts. Rio keeps people exactly where judgment matters: exceptions, rate disputes and final approval. Everything routine is automated; everything consequential is reviewed.

Impact

What changed.

Manual touch-points

-87%

SAP entry

Re-keying → automated posting

Ticket intake

Paper → extracted drafts

Systems in the flow

Many → one connected workflow

Errors and duplicates

Caught before posting

Operational visibility

A shared queue replaced the paper pile

Human review

Focused on consequential exceptions

Status model

Shared across field and back-office teams

Process

Mapping Rio's flow before designing the screens

Stakeholder and field-team interviews, legacy ticket and SAP audit, end-to-end workflow mapping across roles and statuses, SAP Fiori alignment, high-fidelity flows and prototypes, and iteration with operations and back-office users.

A single approval workflow, from exception review through to SAP posting.
Approval stages and role-based task flow.

Next case study

$60 million in cost savings through Amazon Return Kiosks.

Read next