Lanshore: Advancing Intelligence

Solutions

Energy ERP Program Management Services

Lanshore runs the program office for ERP transformations at energy companies: one integrated plan across the system integrator, the software vendor and internal IT, budget ownership with monthly financial reporting, a working risk and issue log, change control, steering committee reporting, and cutover and go-live management through hypercare. Lanshore's founder, Doug Erb, has served as program manager on a $53M greenfield S/4HANA program at PEMEX since October 2023 and managed the finance workstream of an S/4HANA migration at ConocoPhillips.

Who it is for

CIOs, IT directors, finance leaders, and transformation sponsors at energy companies running an ERP implementation, a conversion to S/4HANA, or a post-acquisition consolidation. It fits programs that are starting and want the governance right from the beginning, and programs already underway where the plan has stopped being believable, the integrator and the internal team disagree about status, or a go-live date is being defended rather than tested. It assumes you want a program office that tells you when the date is at risk early enough to do something about it.

The problems it solves

Each vendor reports against its own plan

The system integrator reports green against its statement of work, the software vendor reports against its own deliverables, and internal IT tracks its tasks in another tool. None of the three is lying, and the program still misses, because no plan contains the dependencies between them. A single integrated plan that every party is held to, with cross-party dependencies named and dated, is the difference between status reporting and program management.

Status is reported as colour rather than evidence

A workstream reports amber for weeks, then jumps to red a month before a milestone. The underlying problem was visible earlier in test pass rates, defect ageing, data load results, and unstaffed roles, but none of those reached the steering committee. Status has to be defined against evidence, with the measures agreed in advance, so a colour is a conclusion the committee can check rather than an opinion it has to trust.

Scope changes arrive as assumptions rather than decisions

In a long program, scope moves constantly: a requirement reinterpreted in a design session, an interface quietly deferred, a report added because someone senior asked. Unmanaged, these surface at test as defects and at go-live as gaps. Change control that is actually used, where a change is costed, decided, and recorded before it is built, is what keeps the budget and the plan connected to reality.

Data migration is treated as a late technical task

Energy ERP programs carry difficult data: assets and equipment hierarchies, joint venture structures, production and revenue accounting, contracts, and master data that has diverged across acquired entities. Treated as a late task owned by a technical team, migration becomes the reason a go-live slips. Treated as a workstream with its own mock loads, reconciliation gates, and business ownership of data quality, it becomes predictable.

Go or no-go is a meeting rather than a measurement

If the criteria for going live are written in the week of the decision, they will be written to fit what has been achieved. Criteria agreed months in advance, tested at each mock cutover and dress rehearsal, turn the decision into a measurement. That also makes a decision to delay defensible, which is what allows it to be made at all.

The program ends at go-live and support is not ready

Hypercare is often scoped as a few weeks of the implementation team staying on, with no exit criteria and no plan for who owns the system afterwards. The result is a long tail where nobody is clearly accountable. Hypercare needs entry and exit criteria, a triage path, and a dated transition into the support model that will run the system.

How Lanshore delivers it

  1. 1

    One integrated plan across every party

    We build a single plan covering the integrator, the software vendor, internal IT, and the business, with cross-party dependencies explicit and dated. Every party works to that plan and reports against it. On the PEMEX program, holding SAP, Accenture and internal IT to a single integrated plan is the mechanism that makes the program's status mean one thing.

  2. 2

    Budget ownership and monthly financial reporting

    We own the program budget, including contingency, and report monthly on spend against plan, forecast to complete, and the cost of approved changes. Doug Erb owned the PEMEX budget including a 15 percent contingency with monthly financial reporting. Sponsors see the cost consequence of a decision at the time the decision is made, not at the next quarterly review.

  3. 3

    RAID governance that is used rather than maintained

    Risks, assumptions, issues, dependencies and decisions are kept in one log with owners and dates, scored so the committee can see what matters, and reviewed in a working session rather than read out. Decisions are recorded with the options considered, which is what stops the same question being reopened three months later by different people.

  4. 4

    Change control with cost attached

    Every proposed change is written up with scope, effort, cost, schedule impact, and a recommendation, and goes to a change board that meets on a schedule. Nothing gets built that has not been decided. The cumulative effect of approved changes is reported alongside the budget, so scope creep is visible as a number rather than felt as a slip.

  5. 5

    Status defined against evidence

    We agree in advance what evidence defines each workstream's health: test pass rates and defect ageing by severity, data load reconciliation results, interface readiness, staffing against plan, and milestone forecast versus baseline. The weekly report and the steering committee pack are built from those measures, so a red is a conclusion the committee can interrogate.

  6. 6

    Data migration run as a workstream

    Migration gets its own plan, business owners for data quality by domain, a load sequence, and reconciliation gates that have to pass before the next load runs. Mock loads repeat on a schedule so that by the final dress rehearsal the load has been run and reconciled several times. Lanshore has delivered this work on energy programs including the ConocoPhillips S/4HANA finance workstream, where the month-end close was redesigned and documented for the S/4 target state.

  7. 7

    Cutover, go or no-go, and dress rehearsals

    We write the cutover runbook task by task with owners, durations, dependencies and rollback points, and rehearse it. Go or no-go criteria are agreed early, measured at each rehearsal, and presented to the committee as a measurement. The runbook names the point of no return and what happens on either side of it.

  8. 8

    Hypercare with exit criteria and a transition to support

    Hypercare runs with a defined triage path, daily command centre reporting while volumes are high, and written exit criteria covering defect backlog, close completion, and business readiness. It ends by transitioning into the named support model, whether that is your team, the integrator, or Lanshore.

Get an assessment

Related case studies

Related: Energy systems: ETRM and ERP programs · ETRM Implementation Services for Energy Trading · ETRM Vendor Selection for Energy Trading Teams · Enterprise SPM for CRM and ERP Integration · Oil and gas industry work

Energy ERP Program Management Services: FAQ

Which firms provide program management for energy ERP transformations?
The large integrators provide program management alongside the implementation they are delivering, and a set of independent firms including Lanshore provide it separately from delivery. The separation matters when the program office has to report on the integrator's performance. Lanshore's founder has run a $53M greenfield S/4HANA program at PEMEX as program manager since October 2023 and managed the finance workstream of an S/4HANA migration at ConocoPhillips.
Should the program office be independent of the system integrator?
In most cases yes, because the program office reports on whether the integrator is meeting its commitments, and an integrator reporting on itself has an obvious conflict. An independent program office also holds the internal side to account, which an integrator cannot do. What matters more than independence on paper is whether the program manager has the standing to tell a sponsor that a date will not be met.
Can you take over a program that is already in trouble?
Yes, and the first deliverable is an assessment rather than a replan: what is genuinely complete against evidence, where the critical path actually runs, which risks have been accepted without being decided, and what the realistic date is. That produces options with costs attached, usually including a narrower phase one. Recovery almost always comes from reducing scope and fixing governance rather than from adding people.
How do you decide whether a go-live date is achievable?
By measuring against criteria agreed in advance and tested at each mock cutover: defect counts and ageing by severity, test pass rates, data migration reconciliation results, interface readiness, cutover rehearsal timings against the window, and business readiness including training and support coverage. If the criteria are only written in the week of the decision, they will be written to fit the situation, which is why they are agreed early.
What does the steering committee actually get each month?
A program on a page with milestone forecast against baseline, workstream health with the evidence behind each rating, the top risks and issues with owners and dates, decisions needed at this meeting, budget against plan with forecast to complete, and the cumulative impact of approved changes. The purpose of the pack is to surface the decisions the committee has to make, not to report that work happened.

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