Commodity Systems Integration
The connections between your ETRM and pipelines, terminals, measurement and accounting, designed so every record crossing a boundary has an owner.
Delivery. A written integration design first, then the build, one interface or one consolidation at a time.
A commodity or IT lead whose ETRM is sound but whose month-end still runs through re-keyed confirmations, emailed tickets and a reconciliation spreadsheet.
Actualization runs days behind, the book and the terminal disagree on inventory, an acquisition has left you running two systems under a transition agreement, or a scheduler has become the integration.
What you are buying
The work we do
- map every record that crosses between the ETRM and pipelines, terminals, measurement, ERP and credit
- decide the system of record for each one, and what happens when two sources disagree
- write integration specifications a scheduler and an accountant can both sign
- build the interfaces, the reconciliations and the exception queues
- test against a closed month and reconcile the result to the book
- plan the move from two books to one against the transition agreement's end date
What you receive
- an integration inventory with a system of record and an owner for every data flow
- specifications written in the business's terms, not only the interface's
- working interfaces with reconciliations that flag a break before month-end does
- documentation your team could hand to someone new
- a sequenced exit plan from the transition agreement, with the data you need to own named
How we know it is finished
Each interface is finished when a live month has run through it and reconciled without manual correction. A consolidation is finished when the transition agreement can end without losing a record.
What we need from you
- The scheduler or accountant who currently bridges the gap by hand
- Access to sample statements, tickets and confirmations from a closed month
- Technical contacts for the ETRM, the ERP and any vendor portals
A well-chosen ETRM still produces a bad month-end when the data around it arrives by email. Pipeline confirmations get re-keyed. Terminal lifting data lands as a spreadsheet. Measurement statements are compared by eye. The person doing it has quietly become the integration.
Every record needs a system of record
The design question is not how to move data. It is which system is right when two disagree. The ETRM says one volume, the pipeline statement says another, and measurement will say a third after a prior-period adjustment. We decide that for every flow before anything is built, and write the reconciliation that catches the break.
Acquisitions and transition agreements
Buying an asset usually means inheriting its commercial system under a transition services agreement with an end date. The question is which deals, balances, contracts and history you need to own before that date, in what shape, and in which book. We plan backwards from the date.
Where agents help
Some of this work is reading documents rather than moving structured data: nomination confirmations, bills of lading, statements from counterparties who will never send a file. That is where an agent earns its place, matching the document to the deal and raising the exceptions for a person to decide.
What you keep
The code and the data·Your existing relationships·Approval and control·The ability to stop·The off switchWhat that means
ETRM Selection
Choosing an ETRM against how your crude, gas, NGLs or refined products actually move, not against the vendor's demo book.
Learn more ↗ETRM Program Assurance
Someone on your side of an ETRM implementation who has run one before, whether the program is starting or already in trouble.
Learn more ↗Start with a 45-minute briefing.
Bring the program, the proposal or the month-end that will not close. We will tell you honestly where to start.