Patrick O'Mara

Patrick O'Mara

Biotech IT and Digital Leader

Core LIMS Upgrade from v5.2.4 to v5.3.9

Project Overview:
This project involved upgrading the Core LIMS platform from version 5.2.4 to 5.3.9 to enable new functionality, apply vendor fixes, and maintain platform supportability. The upgrade was executed in close collaboration with database administrators and business stakeholders. A detailed run book was created to guide execution, and the full upgrade was validated in a test environment before being successfully deployed to production with zero issues and no downtime during business hours.

Objectives

  1. Upgrade Core LIMS from v5.2.4 to v5.3.9 in alignment with vendor recommendations.
  2. Ensure database integrity and application stability throughout the upgrade.
  3. Validate all functionality in a test environment prior to production deployment.
  4. Maintain uninterrupted business operations during normal working hours.
  5. Create a clear, repeatable run book for execution and rollback.
  6. Document all testing and validation activities for audit readiness.

Background

Core LIMS supported critical laboratory workflows and data management processes across the organization. Remaining on an older version increased operational risk and limited access to vendor fixes and enhancements. The upgrade was required to ensure continued platform stability, compliance, and supportability.

Problem

Upgrading a production LIMS platform posed risks related to database schema changes, custom configurations, and integrations with downstream systems. The upgrade required precise coordination with database administrators to execute vendor-provided database scripts and careful validation to ensure laboratory operations were not disrupted. Downtime during business hours was not acceptable.

Features

  1. Cross-Functional Collaboration

    • Worked closely with database administrators and business stakeholders throughout planning, testing, and execution.
    • Ensured technical changes aligned with operational laboratory needs.
  2. Test Environment Validation

    • Executed the full Core LIMS upgrade in a test environment prior to production.
    • Performed functional, integration, and regression testing.
    • Documented all test cases, expected results, and outcomes.
  3. Run Book Development

    • Authored a detailed upgrade run book outlining pre-checks, execution steps, validation criteria, and rollback procedures.
    • Used the run book to ensure consistent, controlled execution.
  4. Database Script Execution

    • Coordinated with database administrators to review and run vendor-supplied database scripts.
    • Verified schema changes, data migrations, and object validity post-execution.
  5. Controlled Production Deployment

    • Deployed the upgrade to production following successful test sign-off.
    • Scheduled and executed the deployment to ensure zero downtime during business hours.
    • Monitored system health and user impact throughout the deployment.
  6. Post-Upgrade Validation

    • Confirmed application functionality, data integrity, and system performance.
    • Verified integrations and reporting continued to function as expected.
    • Ensured operational readiness before formally closing the change.

Technology Stack

  • LIMS Platform: Core LIMS v5.2.4 → v5.3.9
  • Database: Oracle (vendor-managed schema updates)
  • Deployment Artifacts: Vendor upgrade packages, database scripts
  • Documentation: Run books, test plans, validation evidence

Outcome

The Core LIMS upgrade from v5.2.4 to v5.3.9 was successfully validated in a test environment and deployed to production with zero issues and zero downtime during business hours. All laboratory workflows, integrations, and reporting remained fully operational. The documented run book and test validation artifacts provided audit-ready evidence and established a repeatable, low-risk approach for future LIMS upgrades.