ETRM Managed Services and Post Go-Live Support
Lanshore supports energy trading systems after go-live, when the implementation team has gone and the trade capture, scheduling and settlement interfaces have to keep running every day. The work covers incident response against an agreed operating calendar, monitoring of the interfaces to scheduling and finance, an enhancement backlog worked in priority order rather than through change requests, and regression testing of vendor releases before they reach production. Lanshore selects and implements ETRM systems as well, so the team supporting the system understands why it was configured the way it was.
Doug Erb, Founder & CEO · Updated
Doug Erb founded Lanshore and has designed, built and run sales compensation systems since 2000, from Callidus and Trilogy through Varicent, Xactly, CaptivateIQ, Performio and SAP Commissions. He also leads the firm's AI and automation practice and its energy programs, including program management of a $53M greenfield S/4HANA implementation at PEMEX.
Who it is for
Energy trading, midstream and oilfield services companies that have gone live on an ETRM system and now have to run it. Typically the caller is a CIO, an IT program director or a head of trading operations who has a system in production, a backlog of changes nobody is working, and either no internal team or a team of one or two who cannot cover a trading day. It also fits companies whose implementation partner has rolled off and left hypercare behind with nothing after it, and companies whose first month-end close after go-live went badly.
The problems it solves
Hypercare ends and nothing replaces it
Implementation contracts end at a date, often a few weeks after go-live, and the system is at its least stable exactly then. The first quarter-end and the first month with a full trading book are where configuration gaps surface. Teams discover the gap between hypercare and a support arrangement after they are already in it.
Interfaces fail quietly
An ETRM sits between trade capture, scheduling, risk and finance, and the failure that costs most is not an outage, it is a feed that ran and delivered incomplete data. Nobody notices until positions or settlements look wrong, often days later. Monitoring that confirms a job ran is not the same as monitoring that confirms what it moved.
The enhancement backlog never moves
After go-live, every change becomes a change request with a scoping cycle attached, so small improvements that would make traders and schedulers faster never get done. The backlog grows, confidence in the system drops, and people rebuild the missing capability in spreadsheets beside it.
Vendor releases arrive untested
ETRM vendors ship upgrades on their own schedule, and the regression risk sits on customizations and interfaces rather than on core functions. Without a regression pack built from your own configuration, each release is either taken on trust or delayed indefinitely, and both of those are decisions nobody wants to own.
Knowledge leaves with the project
The reasoning behind configuration decisions usually lives with the people who made them. When the implementation team departs, what remains is a system whose behavior can be observed but not explained, which makes every subsequent change riskier than it should be.
How Lanshore delivers it
- 1
Take over with a documented handover
We start by capturing what the system does and why: configuration decisions, interface map, known workarounds, the open defect and enhancement list, and whatever the implementation left undocumented. This is the artefact support runs on, and on most handovers it has to be reconstructed rather than received.
- 2
Run incident response on an agreed calendar
Coverage is set around your trading day and your close calendar rather than a generic business-hours window, with the escalation path and the named people agreed in writing. Lanshore publishes no standard support SLA; the operating calendar and coverage are agreed per client.
- 3
Monitor interfaces for content, not just completion
We watch the feeds between trade capture, scheduling, risk and finance for the failures that matter: partial loads, silent rejections, records that moved but did not reconcile. Checks are built against expected volumes and balances so an incomplete run raises an alert rather than a green tick.
- 4
Work the enhancement backlog in priority order
Small changes are delivered as part of the service rather than scoped individually, prioritized with your team on a regular cadence. The intent is that routine improvements stop being projects, which is what keeps users inside the system instead of beside it in Excel.
- 5
Test vendor releases before they land
We build a regression pack from your own configuration and interfaces and run it against each vendor release in a non-production environment, so the upgrade decision is made on evidence about your system rather than on release notes about the product.
Related case studies
- Selecting and implementing an ETRM system for PetroChina International America
ETRM vendor chosen from a shortlist of three and the selected system implemented
- Revolutionizing oilfield invoicing with automation
Invoice processing cut from hours to minutes per ticket
- Taking a $53M greenfield ERP program from RFP to go-live at PEMEX
A $53M, two-phase greenfield ERP program taken from partner selection to go-live
Related: Energy systems: ETRM and ERP programs · ETRM implementation services for energy trading · ETRM vendor selection for energy trading teams · Energy ERP program management services
ETRM Managed Services and Post Go-Live Support: FAQ
- What does ETRM support after go-live actually include?
- Incident response against an agreed operating calendar, monitoring of the interfaces to scheduling, risk and finance, an enhancement backlog worked in priority order, regression testing of vendor releases before they reach production, and keeping the configuration documentation current as the system changes. The distinction from hypercare is that hypercare stabilizes a new go-live and ends, while support is the ongoing operation.
- Do you publish a support SLA?
- No. Lanshore publishes no standard support SLA. Coverage hours, response expectations and the escalation path are agreed per client around the trading day and close calendar, and written into the engagement. Ask for them in writing from any provider, including us, and be specific about what happens during month-end and quarter-end rather than on an ordinary Tuesday.
- Can you support a system another firm implemented?
- Yes. It starts with a handover exercise to reconstruct what the system does and why, because that reasoning usually left with the project team. We document the configuration, interface map, known workarounds and open items before taking on response commitments, so support is not being provided against a system nobody has read.
- How is this different from hypercare in an implementation?
- Hypercare is the tail of a project. Lanshore's implementation hypercare runs through the first month-end closes and ends on agreed exit criteria rather than on a date. Managed services is the arrangement that follows: an ongoing operating responsibility with its own calendar, backlog and release process, rather than a fixed window to catch go-live defects.
- Do you only support systems you implemented?
- No, though it is the easier case, because the team already knows why the configuration is what it is. For a system implemented by someone else, the handover exercise closes that gap first. Lanshore selects and implements ETRM systems and resells no trading system, so the support relationship does not come with pressure to move you onto a particular product.
Talk to Lanshore
A 30-minute call. We look at your systems, your timeline, and where this would take risk out of the program first.
