Products
From the field crew to the boardroom, every team works from the same facts about your pipe, each in its own view. Start with Core, add a package as each team comes on, and let agents keep watch in between. Your people make every call.
PeopleA view for each role. People decide.
Each role sees the same record its own way. A person approves every action, and every approval is on the record.
finished work goes up · nothing is dispatched on its own
3AgentsWatch every package, between reviews
each agent reads the packages under it
2PackagesAdd one, another team joins
Compliance & Assurance
Which rules apply to each asset, when they are due, and the proof each was met.
Compliance · regulatory
Decision Support
Every dataset read together: lines ranked with the reason, runs compared joint by joint.
Senior engineers
Environmental
Air, water and waste obligations on the same sites as their corrosion history.
Environmental · right-of-way
Financial Planning
Spend ranked by risk and cost, capital and operating, against the regulatory clock.
Finance · the board
every package reads the same record
1CoreThe base, and the engine under everything
Core · the engineLive
One clock · one centerline · one hierarchy · Esri-compatible
↑ everything you connect ↑
Your data66 kinds, as you hold them
Core. Your footprint from the public record on day one, then your GIS and your readings lined up on one clock, one centerline and one hierarchy, with work orders and the field app on your crews' phones to get the work done.
Each package brings another team onto the same record: compliance, senior engineers, environmental, finance. It reads everything the others already hold, so each one answers questions the last could not.
Agents are built to do the repetitive checking around the clock. Each will watch across the packages between reviews and hand an engineer finished work: the finding, the evidence and a recommendation. A person decides, every time.
Who it serves
The field, operations, engineering, compliance, environmental, finance and management teams each see the same record their own way: their own question, their own screen, the same facts. Here is one finding, TS-13, as each of them sees it.
Core and Decision Support · Is it real, and what should go out?
High · CP instant-off below criterion · TS-13, Line 3
Financial Planning · Do we fund it, and from which budget?
Operating budget, this quarter
Core: work orders and the field app · Where do my crews go first?
Core: the field app · What do I do here, and how do I prove I did it?
Compliance & Assurance · Can I prove each one was met?
Environmental · What does the work touch?
Every package · Is the risk going down, and what did it cost?
Line 3 risk, after the dig
One decision, seven views, one record: every row traces back to TS-13 · Sample data
The question each team brings
| Team | The question they bring | What answers it |
|---|---|---|
| Field | What do I do at this site today, and how do I prove I did it? | Core: work orders and the field app, every reading stamped who, when and where |
| Operations | Where do my crews go first? | Core: work orders and the field app |
| Engineering | Which lines need a look, where, and why? | Core, then Decision Support: every dataset read together, studies, the workbench |
| Compliance | Which obligations apply to this asset, when are they due, and can we prove each was met? | Compliance & Assurance: PHMSA and Texas pipeline regulations, kept current and applied to each asset. |
| Environmental | Which air, water and waste obligations bind each site? | Environmental |
| Finance | What should we spend, where, next year, and what does each choice buy down? | Financial Planning |
| Management | Where is the risk across the whole system, and are we on top of it? | Every package, on one record; Agents keeping watch between reviews |
The packages
Core comes first, and every package sits on it. Each one unlocks new screens and brings another team onto the same record. Core and two packages are live today; more are on the way. Pick one to see what it unlocks, what it looks like and who it brings on.
Core at the bottom. Pick one.
The engine. The base. Everything else sits on it.
What it unlocks
Who it brings on
The proof. PHMSA and Texas pipeline regulations, kept current and applied to each asset. Sits on Core.
What it unlocks
Who it brings on
The correlated picture. Sits on Core.
What it unlocks
Who it brings on
The other regulator. Sits on Core.
What it unlocks
Who it brings on
The money. Sits on Core and Decision Support.
What it unlocks
Who it brings on
The standing analysts. Sits on Core and Decision Support.
What it unlocks
Who it brings on
What the live ones look like
Core and two packages are live. Each one takes a job your team does every week, the same steps you take today, and puts every step on the same record, signed. Sketches of the screens, on invented data.
CoreLive
Flag the reading below criterion, write the work order, send a technician, wait for the paperwork, type it back in. Here is that same job on one record: TS-13, from the finding on Mar 3 to the signed re-read on Mar 5.
How this task is done today
For
01 · Office · Mar 3
The finding
High: CP instant-off below criterion at TS-13, Line 3.
−0.72 V against −0.85 V, flagged by the CP criterion agent.
02 · Office · Mar 3
The work order
WO-2417: re-read TS-13 and check the rectifier.
Signed in: integrity engineer
Signed off: integrity engineer · Mar 3, 9:14 AM. Assigned to a field technician.
03 · Field · Mar 5
On the phone
It arrives with the reading, the limit it crossed and what to collect. Due Mar 6.
Signed in on the phone: field technician
04 · Field · Mar 5
At the test station
Signed off: field technician · Mar 5, 11:04 AM
05 · Office · Mar 5
Back on the record
The re-read lands on TS-13's history and confirms it. The repair is proposed from here.
Reviewed and signed off: corrosion engineer · Mar 5, 2:40 PM
WO-2417, office and field: the re-read comes back as TS-13's history · Sample data
One work order, office and field →
Compliance & AssuranceLive
Track the clocks, chase the crews, file the forms, then rebuild the evidence the week before the audit. Here is one check on rectifier R-4, from the rule to the filed proof. Nothing is re-keyed, and there is no side spreadsheet or separate database to keep in step.
How this task is done today
For
01 · Office · Jan 2
The rule
49 CFR 192.465(b)Rectifier check, six times each calendar year, at intervals not exceeding 2½ months.
Signed in: compliance lead
02 · Office · Mar 3
The clock
R-4 checkdue Mar 14
TS-13's re-read already goes out on Mar 5, past R-4. One trip does both jobs.
Signed off: compliance lead · Mar 3, 9:20 AM
03 · Field · Mar 5
The form, on the phone
It opens with the rule, the last reading and the band the output has to sit in.
Signed in on the phone: field technician
04 · Field · Mar 5
Read and signed at R-4
Signed off: field technician · Mar 5, 11:04 AM
05 · Office · Mar 5
The proof, filed
R-4 checks, 2026
The proof is WO-2417 itself: who went, when, what they read, the photo and the signature. Next due by May 20. Nothing is re-keyed.
Reviewed and signed off: compliance lead · Mar 5, 3:05 PM
Rectifier R-4 on Line 3: the rule, the clock, the form and the proof, all on WO-2417 · Sample data
The Compliance & Assurance page →
Decision SupportLive
Line the new run up against the last one, weld by weld, decide what really grew, check it against CP and coating, then justify the dig. Here is one feature at STA 13+02, from two runs to the dig and the corrected run.
How this task is done today
For
01 · Office · Jan 20
Two runs, lined up
Signed in: integrity engineer
02 · Office · Jan 20
What grew
STA 13+02: 22% to 31% of wall. Outside the scatter between the two tools, so it is growth, not noise.
03 · Office · Mar 9
Read with everything else
Inline inspection31% of wall CP at TS-13−0.72 V Coating surveyholiday Overheadpower line
Signed off: corrosion engineer · Mar 9. Line 3 ranks High; dig at STA 13+02 approved.
04 · Field · Apr 7
The dig
Signed off: dig crew lead · Apr 7, 1:30 PM
05 · Office · Apr 8
Back on the record
Run31% Dig33%
The finding closes, and the run is corrected: that tool reads 2 points low on Line 3, so every later comparison knows how far to trust it.
Reviewed and signed off: integrity engineer · Apr 8, 10:15 AM
The feature at STA 13+02: two runs, one finding, one dig, and the run corrected · Sample data
What it decides
Every finding also carries what it would cost to deal with, which budget it comes out of, and what waiting does to it. Ranked together, that is next year's plan rather than a list of problems.
Five findings, in the order they were found.Each one urgent to the person who found it.
What do we fix now?Ranked against each other, not one at a time: a program has one budget and one crew.
Capital or operating?A rebuild and a survey come out of different budgets and different approvals. Each finding takes its own.
What goes in next quarter?The ones that will not change by then, and the ones that are cheaper while a crew is already on that stretch.
Found in arrival order
All five placed
This month fix now
Line 3 · protection below criterion
TS-13 crossed; a holiday and a growing feature under a power line
If it waitsthe feature keeps growing
Line 1 · metal loss growing
Confirmed across two runs, no dig on record
If it waitsthe rate is measured; so is the date
Line 5 · no survey on file
Not enough data to rank: no survey in three years
If it waitsnothing on it can be ranked
OpEx × 2CapEx × 1
Next quarter can wait, safely
Line 6 · rectifier drifting
Three readings down; the survey is due anyway
If it waitscheaper with the survey crew there
Line 2 · coating survey due
Within criterion at every station this year
If it waitsnothing is moving; it rides along
OpEx × 2
We will start from the data you already hold and show you what it can tell you.