J-L Partnership

ETRM / CTRM·Energy and commodity trading

Configured, migrated, live.

We implement, configure and support trading and risk systems for energy and commodity trading, from the first workshop to go-live and beyond.

  • Implementation
  • Configuration
  • Migration
  • Integration
  • Support

01·About

A small team, close to the work.

J-L Partnership is a consultancy working in energy and commodity trading technology. We implement, configure and support ETRM and CTRM systems, and the people you speak to at the start are the people who do the work.

That has practical consequences. Nothing is lost in a handover from a sales team to an architect to a delivery team, because there isn’t one. Decisions are made by the people who will carry them out.

  • Direct

    You work with the people doing the configuration, not an account layer above them.

  • Continuous

    The same people from scoping to hypercare, so context isn’t re-learned at every phase.

  • Focused

    We keep the number of engagements we take on small, so each one gets proper attention.

02·Services

The work between signature and go-live.

  1. Implementation & configuration

    Planning and delivering the system end to end, and setting it up to reflect how you actually trade: reference and static data, deal capture, valuation and risk settings, workflows, and the reports people rely on each morning.

    • Scoping
    • Design
    • Build
    • Reporting

  2. Data migration

    Moving trades, positions, counterparties and history out of legacy systems and spreadsheets. We map, cleanse, transform and reconcile, so the opening position in the new system matches the closing position in the old one.

    • Mapping
    • Cleansing
    • Reconciliation

  3. Integration

    Connecting the system to what surrounds it: market data and price feeds, trading venues and confirmation platforms, accounting and ERP, credit and regulatory reporting. Interfaces are specified, built or configured, and monitored.

    • Feeds
    • Interfaces
    • Downstream systems

  4. Testing

    A test strategy, scripted scenarios and parallel runs that prove the system calculates, settles and reports correctly. Defects are triaged and tracked to closure before anyone signs off.

    • Strategy
    • Scenarios
    • Parallel runs
    • Automated testing

  5. Go-live & support

    Cutover planning, rehearsals and go-live itself, then hypercare and ongoing support once the system is in daily use: fixes, configuration changes, upgrades, and the questions nobody thought to ask during the project.

    • Cutover
    • Hypercare
    • Ongoing support

  6. AI-assisted delivery

    We use AI tools where they make implementation and testing faster without making them less careful: drafting configuration and mapping documentation, generating test scenarios and data, and checking results at volume. Nothing is relied on until we’ve reviewed it.

    • Documentation
    • Test generation
    • Review

  7. Project & programme management

    Planning, governance and reporting for the programme as a whole, run by people who also know how the system is configured, so the plan reflects what the work really involves.

    • Planning
    • Governance
    • Reporting

03·Delivery

Running the programme, knowing the detail.

Some engagements need the whole programme run as well as the system configured. We do both, so plans, governance and reporting stay grounded in how the system actually works.

  1. 01

    Delivery of multi-year trading, risk, compliance and technology programmes

  2. 02

    Front-to-back workflow analysis across physical and financial trading

  3. 03

    Requirements gathering, process mapping and solution design

  4. 04

    Agile and hybrid delivery methodologies

  5. 05

    Portfolio planning, governance and reporting

  6. 06

    Vendor management and third-party coordination

  7. 07

    Change management, training and business readiness

  8. 08

    Cross-commodity system integration and upgrade leadership

04·Approach

How an engagement runs.

Engagements differ in scale, but the shape is consistent, and every step ends with something you can check.

  1. Understand

    We start with how you trade and how the business runs today: products, processes, the reports people depend on and the workarounds they’ve built. The output is a scope and a plan you can hold us to.

  2. Design

    We turn that into a target design: how the system will be configured, where data comes from and goes to, and what changes for the people using it. It’s agreed in writing before build starts.

  3. Build

    Configuration, interfaces and migration routines, built in increments and shown to your users early, so surprises surface in a demo rather than in testing.

  4. Prove

    Structured testing and reconciliation against your current numbers. Nothing moves to production until the results match, or until the differences are understood and signed off.

  5. Go live

    A rehearsed cutover with a clear go/no-go decision, followed by hypercare while the system beds in. After that, support for as long as it’s useful.

On site in London or remote, whichever the phase calls for.

05·Contact

Tell us what you’re running.

Whether you’re choosing a system, partway through an implementation, or living with one that doesn’t quite fit, we’re glad to talk it through. Email is the quickest way to reach us.

contact@j-lpartnership.com
Email
contact@j-lpartnership.com
Address
3 KT10 8EE, UK
Working
On site in London, or remote