IT systems · Practical guide

Empower: managing changes to processing methods

The name of a processing method can stay the same while its parameters change. The result record needs to identify the version actually used. Follow one case from raw data through the processing method and result to review.

Table of contents

At a glance

What should you check after a processing method changes in Empower?

Check which Empower processing parameters may change, who can change them and which method version belongs to the saved result. Assess the impact on integration, calculations and existing results. Reprocessing must not obscure the original data and decision context.

Scope and Applicability

Waters describes system policies and granular privileges for data processing. Its specific impact depends on the empowerment level and configuration. The article addresses control of computerized data evaluation, not the full analytical method validation.

Sources: [1] [2]

Allow integrations changes and effectively restrict them

Not every change to integration parameters is unauthorized. However, such changes must be professionally justified and carried out within controlled rights and procedures. A blanket prohibition may hinder legitimate work; unbounded change rights, on the other hand, may facilitate targeted optimization of results.

Test combinations of broad and more specific privileges. A broad permission can override an intended restriction. Use the configurations assigned to actual users and attempt changes they should be unable to make.

Sources: [1] [2]

Identify raw data, analysis method, and results separately

A chromatographic result is derived from raw data and an applied analysis. Therefore, capture the raw data set, processing method, relevant parameters, and the resulting outcome. A published method under a known name is insufficient if a different version or alternative processing was subsequently used.

Waters defines system policies and user-type privileges that influence processing within the review context. The manufacturer documentation also highlights version-dependent differences. Therefore, no privilege recommendations should be adopted without reference to the installed Empower version and your laboratory workflow. The vendor provides functionalities; your organization determines the intended use.

Distinguish professionally justified post-processing from uncontrolled exploration. A re-integration may be required, but must be traceable and logically aligned with the prescribed evaluation process. A simple ban on any manual action may be professionally inappropriate. Similarly, an unbounded approach in which only the most favorable outcome is visible is professionally unsuitable.

Sources: [1] [2]

Evaluate method rights and system policies jointly

Capture who is authorized to create, modify, save, lock, or optionally unlock methods. Verify actual combinations of privileges. Waters explains that broader storage rights can be overridden by more granular sub-privileges. Therefore, considering a restricted sub-right in isolation does not always reflect the true user scope.

Name relevant global processing settings. A unchanged processing method may have different implications under a modified system policy. Therefore, the assessed state should consider both levels. A method version number alone may be insufficient for complete reconstruction.

Internal Work Aid: Jointly evaluate method rights and system policies
Testing levelOwn questionSuitable evidence
Raw data Which dataset is being processed? Clear reference and maintenance of baseline
Method Which version and parameters apply? Method Identity and Relevant Settings
User What processing may he actually perform? Effective Privileges and Action Review
System Policy Which global regulation impacts the outcome? Designated configuration state
Result Which stage is assessed and reported? Connection to Method, Raw Data, and Review

Sources: [1] [2]

Example and inspection table: identical raw data, modified integration

A known chromatographic dataset is processed using Processing Method M-4. Subsequently, a relevant integration parameter is deliberately altered, and the same dataset is reprocessed. The internal evaluation aims to demonstrate whether the change, the resulting data, and the subsequent assessment remain clearly traceable and interpretable.

Document the raw data set, method status, users, and relevant policies initially. Generate the first result. Then modify the specified parameter using an assigned role and generate the second version. Compare the expected impact on the process against an appropriate independent reference. The article does not specify a universally correct integration value.

Check whether both results are clearly visible in the review and report. The reviewer should be able to assess the change and its rationale. A report containing only the most recently selected value may be inadequate if essential context is missing. The specific report layout and selection criteria will be derived from your process.

A deviation in results is not automatically indicative of a software defect. Associate the expected impact of parameter changes with the relevant analytical assessment. Method status, actual user privileges, and global system policies collectively form the evaluation basis.

Internal Work Aid: Processing, Rights and Historical Review
Test caseActionExpected finding
Initial data evaluation Process known data with M-4 Unambiguous method and result traceability
System Policy Capture global processing setting The entire basis for the evaluation is known
Authorized Change Critical parameters controlled to change Changes and new status are traceable
Unauthorized change Attempt identical action with restricted role The specified permission boundary works
Reprocessing Process the raw data using the changed version Results remain distinguishable and traceable
Historical Review First result re-evaluate again Damaliger context available
Report Output assessed results Selection and relevant changes are clearly understood

Sources: [1] [2]

Do not prematurely interpret manual labeling

Software labels must be understood based on their documented meanings. For example, Waters indicates that results stored in the review window may be marked as "manual," even if no manual integration has been performed. Therefore, a professional conclusion should not be drawn from a single label without verifying the actual actions taken.

Conversely, automated processing does not automatically ensure correct evaluation. Incorrect parameters, inappropriate peak assignment, or a mismatched method version can also be applied automatically. Review requires an appropriate foundation to identify relevant deviations. Labeling serves as an indication only and does not constitute a complete quality decision.

Test the actual workflows used in the laboratory. This may include batch processing, review, reprocessing, and report selection. The test scope should cover critical differences. A pure demonstration of an ideal first run provides little insight into subsequent changes and future traceability.

Sources: [1] [2]

Distinguishing method changes from analytical suitability

The system validation assesses whether rights, versions, processing, and documentation functions as intended. It does not automatically replace the technical evaluation of an analytical method. When an integration parameter is modified, additional assessment should be conducted to determine whether the scientific data evaluation remains appropriate. These responsibilities should be explicitly assigned within the project.

Describe the change procedure for Processing Methods and global policies. Identify affected methods, projects, and result types. A global adjustment may involve a broader scope than a single method copy. The test plan should clearly illustrate this dependency and justify which validation evidence can be reused.

Upon acceptance, the actual target value is confirmed. Approval of a change request does not prove that the correct policy is actively in effect. Appropriate reference data and targeted access reviews can verify the expected impact. Open discrepancies are evaluated prior to corresponding usage.

Sources: [1] [2]

Equip reviewers and administrators with specific responsibilities.

A reviewer requires access to relevant raw data, method protocols, and change records. A report lacking appropriate information or featuring an overloaded presentation may complicate the review. Define which changes require special attention and specify how an unresolved evaluation shall be handled.

Administrators require a clear role and policy model. Routine laboratory activities should not be performed under broad administrative oversight for convenience. If privileged interventions are necessary, the purpose and actual actions must remain clearly traceable. Appropriate controls should align with the specific architecture and risk assessment.

Pass reference cases, configuration status and evaluation criteria. A later release or a new method can thus be specifically checked for the affected functions. The statement "Empower is validated" should always be related to the intended use and proven status.

Sources: [1] [2]

Next steps

  • Define permitted changes and professional justifications.
  • Record the policies and the privileges users actually have.
  • Methodology change, storage, and end-to-end review to be verified.
  • Assess the impact on prior results following error corrections.
Further reading:

Project experience and collaboration

Check reprocessing against the settings actually used

Laboratory owners select a known raw dataset and two clearly identified processing versions. A deliberate parameter change shows whether method, system policy, permissions and result can later be reconstructed together. Suitable existing evidence can be supplemented. Unclear result assignment or an alternative storage route needs further focused cases. We support system testing and review. Your laboratory experts assess the analytical justification for the change.

Frequently asked questions about Processing methods in Empower

Is manual integration always a data integrity violation?

No. What is decisive are professional justification, controlled execution, and traceable evaluation. An ungrounded selection of favorable results would be problematic.

Sources: [1] [2]

Is the method name sufficient in the results report?

Only when the required specific status is clearly defined. A name may not adequately distinguish between different versions or copies. Use the unique method and result reference appropriate to the employed Empower system and verify whether the historical status can be traced back from the results.

Sources: [1] [2]

How robust is a locked processing method as a safeguard?

The lock is a potential control, but it does not constitute a version-independent overall validation. Review available unlock and storage rights, global policies, and alternative processing pathways at the installed site. Even with a protected method, result selection and subsequent processing must remain traceable. Permissions and review responsibilities must align with the actual laboratory process.

Sources: [1] [2]

Does the manual labeling indicate a manual integration?

Not in every documented context. Assess the significance of the labeling for the actual system in use and the true processing pathway. The manufacturer's documentation describes instances in which storing in the review window generates this labeling. Therefore, professional evaluation must include action, methodology, and result linkage, rather than an isolated interpretation of the label.

Sources: [2]

How do we verify the claim of a results report?

Compare the results used, raw data references, and methodological basis, as well as any required change information. The reviewer should be able to understand the rationale for the selected data. A neatly formatted report is not sufficient evidence if relevant prior processing or a critical change remains unclear in the intended investigation pathway.

Sources: [1] [2]

Sources and review date

The sources provide the technical foundation. Tables, checklists, and examples are derived methodological tools, not verbatim regulatory requirements. Manufacturer information must be referenced to the specific version and configuration in use.

  1. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  2. Waters: System Policies and Privileges for Processing Data in Empower SoftwareSupplier source for product functionalities. Availability and behavior depend on version, edition, license, and configuration; no general compliance certification.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Processing Method and Review to be jointly evaluated

Provide a known dataset, the employed methods, and the actually implemented policies. We will thus assign appropriate checks for processing, rights, and result review.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →