The Manufacturing Execution System (MES) is critical for ensuring operational efficiency and quality in the life sciences industry. From the initial considerations of reasons for software development, frequency of upgrades, execution challenges, and best practices, this article aims to provide a comprehensive understanding of the endeavor involved in upgrading MES software.

Managing software-based systems in the highly regulated life science industry is rarely simple. Any proposed change, no matter how small, must be thoroughly evaluated and justified, with a focus on minimizing risk and maintaining compliance. The significance of maintaining stability in validated production processes cannot be overestimated.

This means that life sciences organizations must carefully balance innovation, improvement and efficiency with the need to maintain the integrity of validated processes. Often, the desire to remain at the forefront of the industry is tempered by an inclination to limit any interference with already validated processes. This also applies to MES software upgrades.

A software upgrade is the process of moving from an older version of a software application or operating system to a newer version. This typically involves enhancements, new features, improved performance, and security updates that are not present in the older version. Upgrades often address bugs and vulnerabilities discovered in previous versions and may also include user interface changes, support for new hardware, and additional functionalities.

The software upgrade dilemma

The trend in the industry is towards out-of-the-box MES software where the vendor usually releases a new version of the system every 6 months. This typically involves enhancements, new features, improved performance, and security updates. Upgrades can also address bugs and vulnerabilities discovered in previous versions and include user interface changes, support for new hardware, and additional functionalities.

For each new release, system users face a dilemma: Spend the time and resources to implement the new upgrade or risk missing out on the benefits.

You can almost hear the objections echoing throughout the organization: ‘We just finished an upgrade and the vendor has already released another version of the system? Do we really have to upgrade our MES software this often? Is it possible to avoid software upgrades?’.

No matter how inconvenient the recurring MES upgrades can seem, changes are part of the continuous improvement process. In the context of MES system in the pharmaceutical industry, it is particularly important to ensure that any change introduced into software will not negatively impact product quality and patient safety.

This requires good analysis and verification, and raises issues like:

• Regulatory Compliance

• Validation

• Risk Management

• Recipe Verification

• User Training

• Production Downtime

• Allocating resources to solve potential issues 24/7

Prioritizing which MES software version to implement

Considering the effort and resources required for MES software upgrades in a life sciences setting, it is natural for pharmaceutical companies to ask:

• How do we minimize the costs?

•  How do we approach the upgrade in the simplest possible way

• How do we achieve re-validated state of the system in the most efficient way?

• Is it necessary to deploy each released version of the MES software?

The answer is that MES software suppliers do not require users to implement every single released version of the system. Instead, they offer clients some flexibility to choose version of the system best suited to their manufacturing processes and business goals.

By providing visibility into the evolution of the software, vendors present a roadmap of the enhancements and upgrades introduced in each version. This empowers life sciences companies to make informed decisions tailored to their specific needs, whether it is optimizing efficiency, solving specific challenges or capitalizing on new features.

It is important to note that the more software versions and feature upgrades that are skipped, the more changes need to be analyzed. The effort needed to maintain perspective and keep track of changes is not the only complication. Skipping too many upgrades can result in:

      Security issues: Delaying upgrades leaves the system vulnerable to security breaches, as patches for known vulnerabilities are not applied promptly. As cyber threats evolve rapidly, outdated systems become prime targets for malicious actors looking to exploit vulnerabilities.

      Compatibility issues: If the MES upgrades are out of sync with other software and hardware components, it can complicate overall system performance. This can result in reduced efficiency, increased downtime, and ultimately, higher costs associated with troubleshooting and maintenance.

·        Opportunity cost: Missing out on valuable new features, enhancements, and optimizations that could improve productivity, streamline workflows, and provide a competitive edge.

Most companies lack the in-house capabilities needed to fully evaluate the impact of each new feature on their existing systems and processes. In this situation, it is often wise to bring in a specialized consultancy partner with the expertise and experience to navigate the regulatory landscape and recommend best practices in system validation.

The external partner can help ensure the upgraded system meets safety, accuracy, and data integrity standards. They can provide useful advice on improving workflows and processes in the new system, using their experience to make operations more efficient and productive. They can also assist with project management to ensure the upgrade is finished on time, stays within budget, and causes minimal disruption to daily operations.

Ultimately, this approach fosters a collaborative an mutually beneficial relationship between the client, the consulting partner and the MES vendor. It enables the client to prioritize system upgrades that ensure ongoing security, stability, and functionality, safeguarding both the integrity of the system and the continuity of business operations.

A structured approach to MES software upgrades

Any MES system upgrade requires a structured approach to ensure hassle-free transition, optimal functionality and system validation. The required effort and level of complexity increases with each change the vendor has introduced in the new system version and each subsequent version of the system that has been implemented.

A structured system upgrade can be broken down into six stages:

1.     Gathering of information

The initial phase focuses on gathering detailed information about the new system version, including analysis of release notes, vendor manuals and Delta Documentation to compare the current and new functionalities. Documentation should clearly link system functionality with  production process. If needed, the supplier can provide process examples for clarification.

2.     Impact assessment

To assess the new system's impact on MES-driven manufacturing processes, consider system functionality, procedural impact, and technological impact. Recipe verification often takes the most time, as each process must be tested thoroughly and each changed functionality considered individually. For example, if the changes relate to material flow, the potential impact on the weighing process should be verified. System functionality changes that impact MBRs or settings must also trigger a review of related SOPs and Work Instructions. Additionally, verify hardware and peripheral compatibility to avoid issues like crashes or unresponsive devices, which can cause downtime and increased costs.

3.     Risk assessment

A thorough risk assessment is vital to identify potential pitfalls in advance and develop robust mitigation strategies. On the other hand, the risk assessment may show that even significant changes to the system do not affect the functionalities used by the client. A good understanding and thorough analysis of the requirements of the process may seem time-consuming but in the bigger picture it will help avoid repeating test cases, and later save the trouble of running tests. For this reason, a common-sense approach to validation is extremely important. CSA (Computer Software Assurance) - which is a new, risk-based approach to CSV, emphasizes the importance of using critical thinking, and drives efforts and time constraints. Proper risk analysis reduces the effort needed to ensure the system works as intended by identifying risks, defining mitigations, and integrating vendor test documentation like Factory Acceptance Testing (FAT) and Site Acceptance Testing (SAT) into the CSV framework. Automated testing further enhances efficiency and accuracy by handling repetitive tasks and minimizing errors.

4.     Data migration planning

Before migrating data between the development, validation, and production environments, it is essential to conduct a thorough analysis. This analysis should focus on key aspects such as the methods used for data extraction, the specific requirements for migration, the procedures for validation, and the creation of detailed rollback plans to address any potential issues. These steps ensure a smoother migration process and minimizes the risk of errors or data loss.

5.     Re-validation planning

Initiating re-validation planning is essential to outline downtimes and phases where the validation and production environments may become unusable or invalid, thus ensuring continuity of operations. Communication of downtime windows to stakeholders and implementation of contingency plans to address unforeseen issues or failures during the upgrade process should be also a part of this planning.

6.     Execution

The actual execution of the upgrade should be approached with cautious optimism, ensuring that every action meticulously follows the planned strategies and preparations. By doing so, the upgrade can be carried out effectively, minimizing risks and maximizing the likelihood of a successful outcome.

How to simplify the software upgrade process

Simplifying the software upgrade process goes beyond merely following a structured approach.

Below are recommendations for streamlining different parts of the process:

Risk assessment:

• Focus resources on areas where potential system errors pose the highest risk to production or compliance.

• Avoid excessive testing by targeting process-critical functionalities rather than every change introduced in the software.  

Testing:

• Base the scope and form of testing (e.g., static, dynamic, end-to-end) on the results of the risk assessment and the role of each functionality in the production process.

• Leverage vendor documentation to reduce redundant testing. For example, supplier-verified functionalities may not require retesting if sufficient evidence is provided.

• Prioritize testing in the development environment to maintain the integrity of validation and production systems.

• Begin testing with the most impactful processes, such as those involving material flow or integration with other systems.

Automation:

• Introduce automated testing where practical. While the initial investment can be significant, automation pays off quickly, especially with frequent vendor upgrades.

• Implement automated Installation Qualification (IQ) processes to reduce effort. Automated IQ can be pre-planned and require minimal documentation.

Documentation:

• Emphasize concise, meaningful documentation that supports verification and compliance without unnecessary overhead.

• Integrate vendor-supplied test documentation, such as FAT/SAT results, into validation records using traceability matrices

Downtime minimization:

• Schedule upgrades during off-hours, weekends, or other low-production periods to reduce disruption.

• Train operators early to ensure they are prepared to navigate new system features and functionalities, minimizing delays post-upgrade.

Recipe verification:

• Use risk assessment to identify processes most likely to be affected by software changes and prioritize their validation.

• Test for impacts on material flow, process flow, and equipment integration as part of the Electronic Batch Record (EBR).

• Ensure compatibility between the upgraded MES software and other integrated systems.

Communication:

• Establish clear lines of communication between all stakeholders, including development, testing, operations, and external consultants.

• Align teams on objectives, timelines, and responsibilities to streamline coordination and mitigate risks during implementation.

Overall, we can see how careful consideration, structural approach and partnering with a specialized consulting company can help life sciences organizations navigate complexities of MES upgrades.

This can ensure optimized processes and a successful and compliant implementation, ultimately driving operational excellence and enhancing patient safety.

Want our help solving your most pressing problems?

Contact us to learn more about our approach to partnerships and vendor selection.