Lanshore: Advancing Intelligence

Solutions

ETRM Implementation Services for Energy Trading

Lanshore implements energy trading and risk management systems and supports them after go-live: configuration against the deal structures you actually trade, interfaces to scheduling, market data, accounting and the general ledger, data migration with reconciliation gates, parallel runs against live positions, a cutover plan with explicit go or no-go criteria, and hypercare through the first month-end closes. The team works from the Houston area and Costa Rica on Central time, so trading hours and support hours are the same hours.

Who it is for

Heads of trading, risk officers, finance leaders, and IT owners at energy companies who have selected a trading system and need it delivered, or who are mid-implementation and behind. It fits first-time implementations, replacements of a legacy system that has reached end of support, consolidations of several systems after an acquisition, and programs already in test where positions do not reconcile. It assumes the measure of success is traders working in the new system at the first month-end with a close that ties out, not a configuration sign-off.

The problems it solves

Configuration starts before the deal structures are documented

Implementations usually begin with the straightforward trades because those are easy to agree on, and the structured deals get deferred. Those deferred deals are the ones that determine whether the system works: multi-location physical movements, storage and transport agreements, index-plus-differential pricing, embedded optionality, and the trades that only one desk does. Writing down every deal structure in use, with a worked example of each, before configuration starts is what stops a rebuild in test.

Interfaces are scheduled late and discovered to be hard

A trading system is only as good as the data around it: market data and forward curves, scheduling and nominations, counterparty and credit data, and the outbound flows to accounting and the general ledger. These are often planned as a late phase on the assumption they are plumbing. In practice they carry the hardest mapping decisions and depend on teams outside the program, so they need to be specified and sequenced with the configuration, not after it.

Positions do not reconcile and nobody can say why

The moment that decides an ETRM program is the first time the new system's position and valuation are compared with the current one and they differ. Without a reconciliation method agreed in advance, that difference becomes an argument. Each variance has to be traceable to a cause: a deliberate valuation change, a curve or holiday calendar difference, a migration rule, or a defect. Variances that cannot be explained are defects until proven otherwise.

Migration of open positions and history is underestimated

Open deals, their lifecycle status, settled history for year-to-date reporting, counterparty and credit data, and static data such as locations and calendars all have to arrive accurately. Open positions are the sensitive part, because a migration error there is a mispriced book rather than a reporting inconvenience. Load sequencing, reconciliation at each stage, and a repeatable rehearsal are what turn migration from an event into a routine.

Cutover lands in the middle of a trading month

Markets do not pause for a go-live. Deals are struck the day before cutover and the day after, and the two systems have to agree on which holds which. Without a written statement of the source of truth by trade date, a plan for in-flight deals and open nominations, and agreed criteria for proceeding or stopping, cutover becomes a weekend of judgment calls made by tired people.

The program ends at go-live and the team disperses

Traders hit edge cases in the first weeks, month-end close surfaces accounting differences, and the people who know why the system was configured as it was have rolled off. The handover has to include documented configuration decisions, a trained internal team, and named support through at least the first closes.

How Lanshore delivers it

  1. 1

    Deal structure inventory before configuration

    We catalogue every deal type and structure currently traded, each with a real worked example, including the ones that only one desk does and the ones that currently live in a spreadsheet alongside the trading system. That inventory becomes the configuration backlog and the test library, and it is the reference the program is held to when scope is questioned later.

  2. 2

    Configuration against your own book

    We configure trade capture, valuation, position and risk reporting, credit, scheduling and logistics, and settlement against the documented structures, and demonstrate each one with your own example rather than sample data. Decisions that change how a desk works are raised as decisions with options and a recommendation, not absorbed silently into configuration.

  3. 3

    Interfaces specified and sequenced with the build

    We specify each interface as a contract: source, fields, frequency, failure behaviour, and who is called when it breaks. Market data and curves, scheduling and nominations, counterparty and credit, and the outbound accounting and general ledger flows are built and tested on the same schedule as the configuration. Lanshore also builds the automation and integrations around the system where work is being re-keyed between trading, plant and finance.

  4. 4

    Data migration with reconciliation gates

    We sequence the loads, static data first, then counterparties and credit, then settled history, then open positions, and put a reconciliation gate after each: record counts, control totals, and for open positions a valuation comparison against the current system. A load that does not pass its gate is not followed by the next one. The sequence is rehearsed often enough that the real migration is a repeat, not a first attempt.

  5. 5

    Parallel runs against live positions

    We run the new system in parallel with the current one across full trading days and at least one month-end, comparing positions, valuations, and settlement output, and reconciling every variance to a named cause. The parallel period is what converts confidence into evidence, and it is the input to the go or no-go decision rather than a formality after it.

  6. 6

    Cutover runbook and go or no-go criteria

    We write the cutover as a timed runbook: every task, its owner, its duration, its dependencies, and its rollback. The plan states the source of truth by trade date, how in-flight deals and open nominations are handled, and the criteria that have to be met to proceed, agreed with trading, risk and finance in advance so the decision on the night is a check against criteria rather than a debate.

  7. 7

    Hypercare through the first closes

    The people who built the system stay through the first month-end closes. We work the exception queues with your team, triage and fix defects, support the first settlements and accounting tie-out, and hand over configuration documentation and runbooks as your administrators take over. Hypercare ends on agreed exit criteria rather than on a date.

  8. 8

    Ongoing support and back-office automation

    After hypercare, Lanshore can continue to support the system, and can automate the manual work that collects around it: re-keying between trading, scheduling, plant and finance systems, recurring reconciliations, and report preparation. That automation work is the same practice that delivers Lanshore's RPA and agent engagements, including field ticket to invoice automation for an oilfield services company.

Get an assessment

Related case studies

Related: Energy systems: ETRM and ERP programs · ETRM Vendor Selection for Energy Trading Teams · Energy ERP Program Management Services · Oil and gas industry work

ETRM Implementation Services for Energy Trading: FAQ

Which firms implement ETRM systems for energy companies?
Vendors implement their own products, the large consultancies run ETRM delivery inside wider energy practices, and a set of specialist firms including Lanshore implement across vendors. Lanshore's distinction is that it resells no trading system, and that the same people who run the selection carry the requirements into delivery. Whoever you use, ask who on the named team has taken a trading system through a month-end close, not just through configuration.
Can an ETRM go live mid-month?
It can, and sometimes has to, but it costs more than a month boundary. Going live mid-month means two systems hold trades for one accounting period, so the close has to be assembled from both and the reconciliation is manual for that period. Where the date is fixed by a contract or an end-of-support deadline, we plan the bridge explicitly: source of truth by trade date, a combined close procedure, and who signs it.
How do you prove the new system values the book correctly?
By running it in parallel with the current system across full trading days and at least one month-end, comparing positions, valuations, and settlement output, and reconciling every variance to a named cause. Deliberate differences, such as a valuation method the program chose to change, are recorded as expected and signed off. Anything unexplained is treated as a defect until it is traced.
What happens if the program is already behind when you arrive?
The first work is an honest assessment rather than more activity: what is genuinely complete against the deal structure inventory and interface list, what has been signed off without evidence, and what the remaining critical path really is. That usually produces a replan with options, including which scope can move to a later phase. Programs recover far more often by narrowing phase one than by adding people.
Do you support the system after go-live?
Yes. Hypercare runs through the first month-end closes and ends on agreed exit criteria rather than a date, and Lanshore can continue in a support role after that. The operating calendar and coverage are agreed per client; Lanshore publishes no standard support SLA.

Talk to Lanshore

A 30-minute call. We look at your plans, your systems, and where this would change your comp operations first.

832-466-8069Book a call