Replacing Mission-Critical Software in a 24/7 Environment: TotalEnergies’ Approach

Replacing Mission-Critical Software in a 24/7 Environment: TotalEnergies’ Approach

bedrijfskritische-software-vervangen-totalenergies-m2q-cronosgroep.jpg

Anyone replacing mission-critical software while operations continue 24/7 needs clear agreements regarding releases, quality, and testing from day one. That was the core of M2Q’s role in TotalEnergies’ Omega project. Together with other companies in the Cronos Group, we collaborated on an integrated solution, with M2Q serving as the partner for release, quality, and test management.

In this article, you’ll learn what the challenge was, how we tackled it, and what lessons you can apply to your own software replacement project.

What made TotalEnergies’ Omega project complex?

The Omega project was complex because internally developed software was being replaced by COTS solutions in an environment that must remain available 24/7. COTS stands for Commercial Off-The-Shelf: ready-made software that you purchase or license, rather than having it custom-developed. TotalEnergies is a French energy multinational that, by the end of 2023, will have more than 100,000 employees in nearly 120 countries.

Four factors made this program particularly challenging:

  • 24/7 operations: The software must be available continuously and reliably.
  • Customization versus off-the-shelf software: A COTS solution sometimes requires compromises compared to what the in-house software did.
  • A rare type of project: Large-scale software replacement is uncommon in an organization, so experience often needs to be built up.
  • Limited resources: the available capacity had to be deployed strategically.

What did M2Q do as part of the Omega project?

M2Q was responsible for release, quality, and test management, from the bidding process through to overseeing the rollout. That role consisted of three parts.

  1. Bidding: We participated in the bidding process for program management and helped streamline responsibilities within that process.
  2. Guidelines and Rollout: We developed guidelines for release, quality, and test management and helped implement them. We also supported TotalEnergies in the acceptance and implementation of the software solutions.
  3. Guidance: We helped ensure that software vendors delivered according to specifications and advised on program implementation and the replacement with COTS solutions.

How do you bring structure to release and test management?

You bring structure by defining environments, processes, criteria, and reporting in advance, even before the first release. At TotalEnergies, these building blocks were:

  • Separate environments: development, test, and production environments, each with a clear purpose.
  • Defect management: a defined process for tracking findings, with KPIs for releases and quality.
  • Test management in Jira: set up with Xray, a test management add-on for Jira.
  • Release and testing processes: with clear criteria and communication and implementation plans.

Why Waterfall with incremental deliveries?

The program followed the Waterfall methodology with incremental deliveries, allowing solutions to be validated early on. This combines the predictability of a fixed schedule with feedback throughout the process, rather than only at the very end.

Program boards and burn-up and burn-down charts kept progress visible to all teams involved.

Five lessons for those replacing software with a COTS solution

  1. Include test management as early as the bidding phase. That way, responsibilities and quality requirements will be established before implementation begins.
  2. Agree on acceptance criteria with your suppliers. This allows you to objectively verify whether a delivery meets the specifications.
  3. Make compromises explicit. Determine in advance where the standard software may deviate from your existing software and where it may not.
  4. Validate in stages. Incremental deliveries reveal problems faster than a single large delivery.
  5. Include communication in your planning. In a 24/7 environment, everyone needs to know what is changing and when.

Frequently Asked Questions

What is a COTS solution? COTS stands for Commercial Off-The-Shelf. It is off-the-shelf software that you purchase and configure, rather than developing it yourself from scratch. Well-known examples include SAP, Microsoft Dynamics 365, and Salesforce.

What is the difference between release management, quality management, and test management? Release management determines what goes live and when. Quality management defines the requirements that the result must meet. Test management organizes how you demonstrate compliance through testing.

Why test when you buy off-the-shelf software? Because you also need to validate the configuration, the integrations, and the connection to your processes. That’s the aspect that only your organization can assess.

Can the Waterfall model still work in a large software project? Yes. In the Omega project, the Waterfall model was combined with incremental deliveries to enable early validation.

When is the best time to bring in a partner for test management? As early as possible—preferably during the preparation or bidding phase. That way, you can establish criteria and responsibilities before implementation begins.

Are you planning to replace your software?

M2Q helps organizations with release, quality, and test management, from the bidding process through go-live. Schedule a free 30-minute consultation or contact us.

Gerelateerde blogs