In this webinar, we will explore the usage of Waters NuGenesis LMS as a platform to manage laboratory operations, exploring the pros and cons of this platform when compared to market-standard options such as a LIMS.

We will discuss when it make sense to leverage NuGenesis LMS capabilities, and the most common scenarios in which this platform is implemented with some case studies for demonstration.

Key takeaways

• Benefits of using NuGenesis LMS as a lab management system
• Comparison between LMS and LIMS capabilities
• Integration capabilities
• Case study demonstration

The post On Demand Webinar – NuGenesis LMS – A Guide to Innovative Benefits and Proven Tactics for Conquering Lab Challenges appeared first on Astrix.

Waters Empower 3 is continuously upgraded to meet the changing needs of laboratories across all industries – pharmaceutical QC/RD, food and beverage, oil and gas, petrochemical, water and environmental, manufacturing, contract labs, and more. Each new feature release of Empower 3 contains new functionality that is built upon feedback and customer input from these sectors and could thus bring significant benefits to the Laboratory user.

Potential benefits to upgrading your Empower software include:

• Implement known bug fixes to improve the system
• Bring validated system to current release
• Opportunity for new servers, new updated OS, redesigned architecture and High Availability (HA)/Disaster Recovery (DR) solutions
• Opportunity for a new Empower administration approach (i.e., naming conventions, project hierarchy)
• Implement newer and more reliable Instrument Driver Pack with new features to improve laboratory workflow and result output

In this blog, we will discuss tips for upgrading Empower that will help to ensure you maximize the business value for your organization.

Tips for Upgrading Empower

Do Strategic Planning. A strategic informatics roadmap is critical for helping your organization leverage IT investments to achieve maximum business value. An informatics roadmap is essentially a plan for the evolution of the architectural aspects of your laboratory informatics ecosystem over the next 3-5 years. The roadmap will help inform your decision as to whether or not upgrading Empower makes sense at this time.

Gather Information on the Existing Environment. Once the decision to upgrade has been made, you’ll want to gather all relevant information on the existing environment:

• Run verify files to generate the environment checksum
• Run Empower Inventory Viewer, or manually take a lab by lab inventory and document all the existing instruments in the laboratory. In a consolidated Empower network environment, there might be a number of instruments and drivers that will not be compatible with the new version of the system.
• Review the existing architecture (database size, technology in use, High Availability, etc…), and plan the hardware/software specifications considering the number of sites, users, instruments, type of data (Mass Spec vs 2D vs 3D channels) and latency between any remote sites and the Empower server(s).

Determine Whether You Want to Do an In-Place or In-Parallel Upgrade.

An In-Place upgrade is the scenario that allows in-place server, client and LAC/E upgrades using Empower automated installer and is typically done in smaller all Windows environment.

Pros:

• All system objects and all data are upgraded at once. There is no need to recreate nodes, systems, users, security grid, or convert data, etc…

Cons:

• Requires planning and downtime of entire environment – cannot run new samples until the process has been completed.
• Requires a good backup plan in the event the upgrade hits a road block part way through.
• Cannot be done in every scenario (i.e. Empower 2 to Empower 3) due to Oracle version incompatibility, Operating System incompatibility, Hardware requirements of the new version, etc…

An In-Parallel upgrade is the scenario where a completely new environment of Dev, QA and/or Prod is built while the older version is in use. This approach can be used with any size of installation, and is typically the “go to” approach for larger, multi-site WAN based installations. System Objects migration can be used to transfer all users, user types, nodes, message center and system audit trail to the new database.

Pros:

• Opportunity for new servers, new updated Operating System, redesigned architecture and High Availability (HA) and Disaster Recovery (DR) solutions.
• Can carefully plan the upgrade, conduct testing and execute the entire environment prior to cutover to production.
• Allows to move existing environment to the new at any granularity – from least to high impact sites, least to the greatest number of instruments connected to the system, etc…

Cons:

• Temporary consumption of IT resources (VM memory, network bandwidth, disk space, Citrix servers) during the period where both Empower installations coexist.
• Time for project completion is bigger compared to “In-Place” approach due to the multi-disciplinary nature of the implementation and interdependent activities that need to take place (i.e. system architecture design planning, system installation, system validation, training, etc.).

Create Good Project Documentation. For regulatory requirements, the system owners need to document all the relevant information about the system, and track changes to the system after the project ends. As part of the upgrade project, the following documentation should be created:

• Project Plan – Formalizes all the planning to execute, control and close the project. Assigns responsibilities, establishes a communication plan, creates a project timeline, etc.
• Validation Plan (VP) – The VP should provide an overview of the project, identify success metrics and define the acceptance criteria for the system’s release.
• User Requirements Specification (URS) – Defines what the user wants the system to do. Further verification of these requirements will be performed to ensure that the user requirements have been met through technical or procedural methods.
• System Design Specification (SDS) – Documents how the system is configured to ensure User Requirements are met. The SDS provides a detailed description of the user/system interfaces and the individual components of the Empower 3 System. This central record provides documentation of baseline configuration parameters for configuration management procedures.
• Risk Assessment – Created to determine the appropriate level of validation based on factors such as impact and possibility of error detection. The Risk Assessment determines the testing strategy used to verify each requirement and/or specification.
• Testing Documentation – IQ/OQ/PQ scripts or protocols for validation testing will be performed in a verifiable manner, to assure that the requirements, design and characteristics of the system and its components are as expected.
• Requirements Traceability Matrix (RTM) – The RTM provides a map to ensure verification of all User Requirements has been achieved. The RTM traces each specification contained in the URS document to a design component, operating procedure and test where verification of each requirement is established.
• Validation Summary Report – This report will be written to review the VP deliverables and to document the status of the entire validation process.

Develop a Solid and Reliable Training Plan. Before moving into the new version of the system, it is important that users are comfortable on how to operate Empower 3 in order to avoid any performance decrease in the laboratory. Having a good training strategy will reduce the time it takes for a new analyst to be prepared for the laboratory operations.

Create the Right Project Team.  Key members of the project team will include:

• Project Manager – Responsible for assistance with project planning, scope definitions, cost/resource monitoring and coordination, project timeline development, tracking project milestones and reporting throughout the project.
• Informatics Architect – Assesses existing architecture and provides input on the design of the system architecture (Bandwidth, solution for High Availability, Hardware/Software Specifications).
• Informatics Engineer – Responsible for installation of the system on the network infrastructure, developing custom fields and reports, data integrity assessments, system configuration and data migrations.
• Validation Specialist- Develops Computer System Validation deliverables for regulated environment – Validation Plan, User Requirement Specification, Design Specification, IQ, OQ, PQ, Traceability Matrix and Validation Report.

Conclusion

Empower 3 software enables your organization to effectively manage data generated by all your chromatography instrumentation, plus run different detection techniques and applications, method development and validation, integrated chemical structures, and polymer analysis. As discussed in this blog, upgrading Empower is a great way to improve your overall laboratory informatics ecosystem, but there are a number of best practice recommendations that are important to follow in order to maximize the benefits of the upgrade for your organization.

Astrix has been helping scientific organizations implement and integrate laboratory informatics systems since 1995. The Astrix Team contains highly experienced and knowledgeable Empower experts that can help your organization implement innovative solutions that turn data into knowledge, increase organizational efficiency, improve quality and facilitate regulatory compliance.

The post Tips for Upgrading Your Waters Empower System appeared first on Astrix.

With massive increases in data volume over the last decade, and the growing concern from regulatory agencies around data integrity, integration between informatics systems has become a necessity, especially on systems that generate large amounts of data or that are crucial to the overall laboratory data workflow. Two examples of systems that fall into this category are LIMS (Laboratory Information Management System) and CDS (Chromatography Data System).

Waters Empower 3 is a chromatography data system (CDS) that links to chromatographic instruments to help facilitate management of chromatography test results through data acquisition, processing, reporting and distribution. This system is utilized by organizations across many different sectors – pharmaceuticals, food and beverage, fine chemicals and clinical. Empower 3 generates lots of data with complex calculations and detailed reports and has several tools that address compliance and data integrity concerns such as electronic signatures and audit trails.

Integrating LIMS with Empower 3 provides a number of important benefits for your laboratory:

• Data integrity is improved, since data transcription can be avoided by this integration.
• Higher lab throughput, as all calculations are executed automatically with minimal to no user intervention
• With the usage of electronic signatures on both Empower and LIMS, having a paperless lab becomes much easier.
• Data turnover can be improved by using tools (e.g., remote access or Empower Mobile) that enable users to review and approve data remotely.
• The integration between Empower and your LIMS allows information to be shared across sites globally and helps facilitate site harmonization (e.g., global methods instead of site-specific methods for the same testing, harmonization of processes between sites on where to perform calculations, etc).
• Standardized data workflows and processes make the overall system easier to maintain and support.
• Your lab staff can be reallocated to execute much more meaningful and profitable tasks, as less data transcription is required.
• Instrument OEE (Overall Equipment Effectiveness) can be improved as the overall data approval cycle can be reduced, effectively speeding up your ROI (Return On Investment)

Best Practices for Integrating LIMS with Empower

A few of the key best practices that need to be considered when integrating LIMS with Empower include:

Develop SOPs that guide your company on how to develop and maintain empower projects, templates and customized calculations.

When integrating Empower with LIMS, data can be transferred from Empower to LIMS through different routes depending on the chosen LIMS – direct data transfer, parsing of data from reports, etc. Whatever the integration solution is, changes to the Empower data organization must follow strict controls and thorough analysis to avoid any disruption to the integration between applications. For example, changes in a customized calculation naming convention or report method formatting might impact the LIMS system parsing script capability of capturing information from reports accurately. As such, having SOPs provides a roadmap to be taken each time new requirements or changes arise. These SOPs must include clearly defined responsibilities, comprehensive workflows and enough information to guarantee proper systems operation, maintenance and support throughout the entire systems lifecycle.

Make sure your data is secure throughout the integration process.

Some LIMS systems rely on the parsing of files such as “.csv” to capture data from external systems, and Empower can provide a multitude of exported files through its export method functionality. This can lead to a challenge, however, as these exported files have to be kept somewhere that the LIMS can sweep to identify candidates for parsing. This place can sometimes be a shared folder in the network, or even a local folder on a client computer (depending on LIMS requirements). As these systems generally require some level of read-write access, data security/integrity can become an issue if access privileges are not tightly controlled in order to prevent regular users from accidentally or purposely altering the data. In addition, it is important to develop testing scripts that deliver certainty that data integrity is maintained in all data transfer processes. Making sure that data is secure at every step of the integration between Empower and LIMS is key to assure regulatory agencies that your company has a strong quality culture and is focused on customer safety and product quality.

Build solid, reusable and consistent customized calculations in Empower.

Chromatography data calculations can be complicated and time consuming. They can include multiple formulas and data coming from external systems such as balances and Karl Fisher. In the past, companies relied on Empower in conjunction with external tools such as validated Excel spreadsheets in order to conduct advanced calculations, with the results then later on transcribed into other systems like LIMS or ERP to give continuity to data workflow.

Empower has a powerful tool for customized calculations called custom fields. It is a default functionality from Empower that can be used for a series of applications, such as:

• Create input fields that can receive information typed in by the user (i.e. sample label claimed amount)
• Create fields that will be used by LIMS to transfer data from LIMS to Empower (i.e. the sample id # in LIMS)
• Execute customized calculation based on one or multiple samples (i.e. blank area subtraction, content uniformity, total impurities calculation, etc.)

Having customized calculations developed in Empower is a good way of delivering readily available data to your LIMS, reducing the amount of work your company might have in developing calculations in a much more complex environment (e.g., LIMS). It also brings immediate benefits for the laboratory workload, considering that the final result is already available in Empower during data review process and no extra data treatment is required, making the overall process more time-efficient for the lab analyst. To achieve these benefits, it is imperative that SOPs are established for the proper development, testing, validation and maintenance of these customized calculations.

Figure out if the integration between Empower and the chosen LIMS needs to be bidirectional.

Although bidirectional communication might sound like the most logical way to integrate two applications, the benefits may not outweigh the extra complexity introduced for implementation, maintenance and especially support of this more complete integration. Careful consideration needs to be given to determine if bidirectional communication is the best option.

For example, a typical QC lab usually has a number of system suitability injections that can vary from test method to test method. This makes a scenario where the sample set could be transferred over from LIMS to Empower without any user input/adjustments (adding/removing injections, adding equilibrate/condition column lines, etc.) improbable. As a result, one directional communication from Empower to LIMS would likely be the most cost-effective solution.

In this case, Empower sample set templates could be created with most of the required information filled in, and with some additional custom fields to hold information required by the LIMS such as the LIMS sample ID. These sample ID’s could be added to this sample set manually or using barcode readers, and then after analysis is completed, data would be captured by LIMS through the one direction integration available.

The benefit in this one direction scenario is reducing system complexity and maintenance/support requirements. When the time comes for major upgrades to Empower (e.g., software versioning, Oracle upgrades, etc.), having a cleaner integration will allow you to execute these upgrades with less chances of finding unmapped incompatibilities in the process.

On the other hand, a clinical analysis laboratory with hundreds of samples per day throughput requirements and patient information confidentiality concerns might want to avoid manual user data inputs, so a bidirectional integration would be a good way to guarantee a good lab throughput without compromising on data integrity and patient safety. In addition, clinical analysis laboratories tend to keep technologies for longer periods with no upgrades due to the sensitive nature of their business, so any effort invested in developing a bidirectional integration might last longer in such environments.

Have a proper mapping of where the required data is located within Empower.

Empower data can be located in different tables depending on the data type, but not all data is readily available for extraction, depending on the tools used by your LIMS for data extraction. Some common examples are the summary calculations (i.e., average, sum, %RSD, etc.) that can be added to report method tables. These calculations are executed on the go once you open the report method for data review, but these values are not saved in the Empower database. So in order to extract these values to LIMS, there are two possible pathways your company might have:

• Use parsing tools to parse the Empower report method and extract the required values from it.
• Create customized calculations to execute those report calculations that are not saved in the Empower database, allowing it to be saved once data is processed.

In this example, it is evident that a proper mapping of data location is vital to determine not only the amount of customization required in Empower, but also if your LIMS has all the required tools to fulfill the integration requirements. If your company already owns Empower and is looking at purchasing a LIMS, having a proper knowledge of the available tools within Empower might help your company narrow down the LIMS options to the ones that will better accomplish integration requirements right out of the box.

Conclusion

Integrating different systems and applications within today’s laboratory environment is critical to establishing digital continuity across the product lifecycle, optimizing operational efficiency, enhancing innovation, establishing a foundation for future growth, and maintaining regulatory compliance. This is especially true for global organizations with dispersed laboratories.

As discussed in this blog, integrating Empower and a LIMS is a great way to improve your overall laboratory informatics ecosystem, but there are a number of best practice recommendations that are important to follow in order to maximize the benefits of the integration for your organization. Astrix Technology Group has been helping scientific organizations implement and integrate laboratory informatics systems since 1995. The Astrix Team contains highly experienced and knowledgeable Empower and LIMS experts that can help your organization implement innovative solutions that turn data into knowledge, increase organizational efficiency, improve quality and facilitate regulatory compliance.

The post Best Practices for Integrating LIMS with Empower appeared first on Astrix.