Your OQ program is only as strong as what you can prove.

EWN keeps your operator qualification records current, verifiable, and audit-ready for every employee and contractor, in one system.

Black circle with a white check mark icon

Real-Time OQ Visibility

White checkmark in a black circle icon on a white background

Audit-Ready Records

White check mark inside a black circle icon.

Field-Proven Content

White checkmark in a black circle icon

Former PHMSA & State Regulators on Staff

We support the safest operators and contractors in the industry.

Black hard hat safety icon on a white background

Safe Operations

Ensure every worker performing a covered task is qualified so your people go home safe and your program holds up under scrutiny.

Document icon with user profile and checkmark on a black background

Compliant Programs

Maintain a verifiable, audit‑ready OQ record that satisfies federal and state regulators (PHMSA, OSHA).

Efficient Workflows

Cut time spent on paperwork and administration. Focus on the work, not the documentation behind it.

Control Your Operator Qualification Program

Keep your qualification data current, your covered tasks tracked, and every competency in your program auditable, all without your team needing to chase it manually. Control your content and configuration so your OQ plan reflects how your organization actually works. No administrative lag waiting for your provider to make updates, just point and click.

Laptop and phone showing a dark-themed analytics dashboard with charts and metrics

Our Platform

The EWN Platform is purpose-built for risk-averse operators who can’t afford qualification gaps, audit surprises, or field misalignment. From compliance oversight to training, asset tracking, and safety program maturity, EWN brings your people, tools, and data into one connected, audit-ready system.

  • OQ Program Management
  • Learning Management System
  • TRACER Asset Management
  • Program Assessment Tool
Black ID badge icon with a user silhouette and a check mark badge

OQ Program Management

Get full visibility across your entire workforce, including employees and contractors. Your OQ dashboards highlight qualification risk by contractor, evaluator, and qualification state before an incident occurs. One source of truth with no spreadsheets or guesswork.

White icon of a person at a computer monitor with speech bubbles on screen

Learning Management System (LMS)

Field-proven training, aligned to covered tasks and industry standards. Build, manage, and deploy the training content your field teams depend on.

Black truck icon on a white background

TRACER Asset Management

Track qualifications, spot gaps, and stay ahead of expirations before they create a compliance problem. Across every crew and contractor network, you always know what's up to date and what isn't.

Black outlined magnifying glass with a small checkmark above it on a white background

Program Assessment

Your reality check for Pipeline Safety Management Systems. Co-developed with APGA SIF, this tool helps you measure where your PSMS stands against API 1173, identify improvement priorities, and document your program maturity so you can approach every review with confidence.

2,600+ operators trust EWN to keep their workforce qualified and compliant.

We needed to find the right partner to take this journey with us… We needed the right system to be able to make sure that our records were safe, that our records and our data were accurate, [and] that we had real time access to that information not only internally but also externally.

Julie Roppelt

OQ Program Specialist, NiSource

Insights & Resources

By EWN Marketing • November 17, 2026
Energy Worldnet (EWN) hosted the Compliance Leadership Forum (CLF) —a peer-to-peer space designed Multi-state OQ compliance: make the program your own One of the most detailed exchanges addressed a familiar pain point—staying compliant across states with different OQ requirements. Kevin Speicher walked through how states like Connecticut and New York have gone beyond the federal baseline: eliminated the old four-part test, made AOC questions critical (missing one means failing the evaluation), addressed span of control (New York left it to the operator with documentation; Connecticut capped it at one-to-one), and added a required OQ effectiveness review. Key takeaway: enhanced state requirements generally apply to intrastate operators. Interstate operators still fall under 49 CFR 192's four-part test, though state damage prevention laws (like warning tape requirements) can still apply. The panel's advice for multi-state contractors: Open communication channels with clients, operators, and regulators. Lean on resources like the Distribution Contractors Association and NAPSR's state compendium. Build your OQ program around your actual equipment and procedures—not an off-the-shelf template you can't modify. Regulator's Notes: CA, ME, NJ, OH, and WA have included new construction as covered tasks. Does OQ actually reduce incidents? Asked directly whether two decades of Operator Qualification requirements have moved the needle, the panel was candid. Alan Mayberry traced OQ's origins to an over-pressure incident and noted real gaps remain—OQ still doesn't cover construction, and carries an exception for emergency response. Kevin Speicher observed that training quality dipped in some corners early on (schools teaching to the test) but has steadily improved, with many contractor programs now rivaling operator programs. Jeff Wiese offered the sharpest framing: OQ was never meant to be about passing a test—it's about quality and genuine competence, the kind that catches problems before they become incidents. Steve Allen pointed to where this is headed next: using AI and better data (drawing on RP 1186's emerging KPIs) to actually measure program effectiveness instead of assuming it. Damage prevention and leak detection: two areas to watch In the speed round, two items stood out: A damage prevention professional certification program is currently in development through Utility Safety Partners, with Steve Allen and Jeff Wiese both serving on the advisory council. The upcoming PHMSA public meeting on advanced leak detection (tied to Section 722) will likely continue focusing on prioritizing large leaks and performance-based outcomes over specific technologies, per Alan Mayberry and Jeff Wiese. Steve Allen's closing note on damage prevention: be intentional, be data-driven, communicate constantly, and lean on the Common Ground Alliance's Damage Prevention Institute rather than reinventing the wheel. Speed Round Highlights To close, each panelist fielded a rapid-fire question from host James Cross: Making OQ your own (Kevin Speicher): the program should reflect your actual system and operational realities—your tasks, your training, your evaluations. If it's your program, you shouldn't need permission to adapt it. How safe is safe? (Alan Mayberry): there's no fixed acceptable-risk threshold in the code—operators weigh multiple factors, from internal risk models to state commission requirements, in a landscape with little public tolerance for pipeline incidents. Where SMS falls short (Jeff Wiese): stakeholder engagement remains a major growth area—true engagement means listening, not just informing—along with weak continuous improvement cycles. Reducing excavation damage (Steve Allen): be intentional, be data-driven, communicate constantly, and use the Common Ground Alliance's Damage Prevention Institute. What's next EWN will continue answering unaddressed questions directly and keep the conversation going through LinkedIn and future events. The next Compliance Leadership Forum is expected in Q4. James wrapped up the session: "Glad we were able to get into some of the hard-hitting questions—looking forward to answering more in the future."
By EWN Compliance Team • September 16, 2026
Up to half the utility workforce could retire within a decade. Here's why OQ onboarding speed, not headcount alone, is becoming the real safety variable.
By Energy Worldnet (EWN) • August 17, 2026
Every OQ program rests on 9 provisions in 49 CFR 192.805. Here's each one explained in full, with the specific requirement behind it.
Show more