INDUSTRIES

Automation for EPC and energy teams.

EPC work moves through engineering, procurement, vendors, document control, field execution, and leadership reporting. I build the operational layer around those crossings so status travels with the work and the next owner is clear.

RLS is based in Oklahoma City and serves EPC and energy teams in Oklahoma City, Tulsa, and Dallas-Fort Worth.

The seams I work.

ENGINEERING, PROCUREMENT, AND FIELD HANDOFFS

A package can be complete in one function and invisible to the next. I define the handoff record, required context, next owner, and exception path so procurement and field teams can act without reconstructing the history.

REVIEW CYCLES, TRANSMITTALS, APPROVALS, AND DOCUMENT CONTROL

The workflow tracks what entered review, who owns the next action, what changed, and what can move forward. It supports the document-control system and keeps formal review authority with the designated people.

PORTFOLIO AND EXECUTIVE REPORTING

Leadership needs a stable view across projects, packages, milestones, and risks. I build reporting around agreed definitions so the weekly picture does not change based on who assembled it.

VENDOR AND COMPLIANCE TRACKING

Vendor documents, approvals, expirations, and exceptions need named owners and visible due dates. I build the collection and escalation rhythm while the compliance owner keeps responsibility for the requirement itself.

Tulsa, midstream, and the tools already in place.

Tulsa is a practical market for this work because EPC and midstream teams coordinate engineering packages, procurement status, vendor records, approvals, and field needs across company lines. The operating problem is usually not a missing platform. It is the work that still happens between platforms.

Primavera and Aconex can be reference points in capital project environments. I can design workflows adjacent to them using approved exports, access, and existing team processes, but any direct connection is validated against the client environment. RLS is not claiming an Oracle integration or partner relationship.

Oracle Primavera P6 product informationOracle Aconex documentation

Common questions

RLS can automate routing, reminders, status capture, document handoffs, vendor follow-up, and reporting around engineering, procurement, and field execution. Technical judgment, acceptance, and formal approval remain with the accountable team.

RLS can design adjacent workflows around data exports, approved access, and the processes teams run outside Primavera or Aconex. Any direct connection depends on the client environment, licensing, access, and technical validation, and RLS does not claim a vendor partnership.

Yes. RLS can improve intake rules, transmittal preparation, review reminders, status visibility, and exception handling around the current document-control platform when its access and configuration support the workflow.

Yes. RLS serves Tulsa and works with EPC and energy teams when the operating problem fits, including midstream workflows involving engineering packages, vendors, approvals, document control, and portfolio reporting.

Give me your worst workflow.

Bring the package, approval cycle, vendor chase, or portfolio report that keeps getting rebuilt.

Book the audit