IT systems · Practical guide

Validating GxPReady Suite: calibration, maintenance and equipment use

Maintenance is complete, calibration is overdue and the qualification report is still current. May the instrument be used? In GxPReady Suite, define what each equipment programme controls, then trace the status and record handovers. Supplier evidence and focused local tests can help a smaller GMP team agree what QA, metrology, maintenance and IT need to demonstrate.

Table of contents

At a glance

What do you need to validate in GxPReady Suite?

Test whether the configured system links equipment, due date, event and record correctly and supports a justified decision on equipment use. Keep maintenance, calibration and qualification as distinct prerequisites. Match supplier evidence to local rules, data and responsibilities. A completed order or attached certificate alone does not establish overall equipment suitability or a technically enforced block on use.

  • GxPReady Suite is described as a SaaS-based CMMS featuring Core functionality and three functional modules.
  • Calibration, maintenance, and qualification are separate programs with distinct statements.
  • A schedule status applies only through an actually defined and appropriate operational process.
  • Structured event data, external attachments, and subsequent exports must remain traceable and comprehensible when combined.

Separate managed device inspections in the CMMS.

The GxPReady Suite is offered as a SaaS system for device management, calibration, maintenance, and validation tracking. The core platform provides shared functions for devices, users, configurations, and reporting. Determine the exact scope of the contract and the current number of active customers. A reliable public numerical version identifier is not specified in the manufacturer's information provided.

The validation of a computerized system and a documented device qualification represent distinct forms of evidence. A module may manage qualification timelines and reports without providing validation that the technical evaluation of the device was performed in full and appropriately. Similarly, a stored calibration certificate does not establish assurance regarding the suitability of the entire digital workflow.

This guide addresses the use within human medicinal product GMP. Annex 11 covers computerized systems; Chapter 3 includes considerations for appropriate equipment, maintenance, and calibration. Other regulatory application areas require separate assessment. General FDA or EMA suitability cannot be inferred from the product name or a sectoral list.

Sources: [1] [2] [4] [8] [9] [13]

Three programs for a justified device selection combine

The manufacturer provides separate calibration, maintenance, and validation modules. For maintenance and qualification, multiple recurring schedules may be implemented per device. Therefore, define which programs are relevant to the intended use and which events specifically alter their status. The most recent completed activity must not be interpreted as a comprehensive validation evidence without proper documentation and review.

The following matrix serves as an internal reference tool for professional boundary definition. It does not describe any proven automated status logic of GxPReady. Please enter your specific prerequisites and evaluate how they reach the end-user at the device level. Technical and organizational controls may contribute to this, but their actual suitability must be assessed.

Work Aid: Separate Programs and Their Statement Limits
ProgrammeEvent or recordNot derivable therefromAdditional decision
Calibration Termin, Result, Certificate Every previous measurement was correct Assess findings and potential implications for use
Preventive Maintenance Execution and Completion Calibration is valid again Evaluate other relevant requirements separately
Corrective Maintenance Repair report The device may be immediately reactivated. Investigations following intervention determine required testing.
Qualification Protocol, report, recurring plan All subsequent changes are covered Evaluate changes and remaining validity
Device usage Business Usage Decision CMMS automatically blocks the machine or laboratory task Verify the actual information and control pathway
History/Export Event and associated documentation Every legible report constitutes the complete electronic record Check required context and readability

Sources: [2] [3] [5] [4] [7] [9] [13] [10]

Device identity and source data to be verified first

A reliable schedule report must begin with unambiguous device data. Define the identifier that links the physical device, the dataset, and external reports. Similar identifiers or location changes must not rely solely on memory for assignment. Also verify how offline devices and replaced components are handled in the actual agreed-upon scope.

When transferring data from tables or legacy systems, identity, most recent valid verification, current plan, and open activities are more critical than a simple count of imported rows. A historical maintenance closure must not be inadvertently treated as the current calibration status. Compare selected differing initial scenarios, including incomplete and inconsistent datasets.

GxPReady describes support for data entry and transfer as an additional service. Please be specifically shown which fields, relationships, and documents are transferred. The decision on the required historical scope remains aligned with the intended purpose of traceability. A clean start-up in the system does not automatically justify the loss of previously required historical information.

Sources: [1] [2] [6] [9] [10]

Turn a potential fault into an effective action at the device level

The module descriptions include schedule management, recurring plans, and notifications. Verify the expiration rule you have defined, including date, time zone, and handling of weekends. A monthly interval may generate different expectations than a fixed number of days. The actual rule used by the customer system must be substantiated through configuration and testing.

A reminder is not equivalent to usage control. Who receives it, who evaluates the situation, and how does the user determine the authorized device status? The manufacturer's FAQ explicitly states that the product is not designed for pre-configured complex integrations. Therefore, an automatic machine, MES, or LIMS lockout is not assumed.

When schedule changes occur, the reason, authority, and implications must remain clear. A revised date must not obscure an existing factual situation. Define when a technical assessment is required and how its outcome is documented. Solely from the calendar, neither a general extension of deadlines nor the definitive conclusion that all prior results are incorrect can be inferred.

Sources: [3] [5] [4] [7] [9] [13]

Example: Maintenance completed, calibration pending

The example involves device W17 on 6 October 2026. According to the example schedule, calibration was due on 30 September; maintenance was completed on 5 October, and qualification evidence is valid until 31 October under this directive. Internal policy requires that the intended activity be performed only after a full assessment of all relevant prerequisites. This is not a claimed automated software function.

For a single stored check point, 100.00 g of reference, 100.18 g prior to adjustment, and 100.03 g after adjustment are applied. The example limit is ±0.10 g. These figures assess only acceptance, accounting, and decision context; they do not constitute a complete calibration method, measurement uncertainty evaluation, or actual product specification.

A conspicuous as-found value can also affect uses prior to the due date. Therefore, do not start the review first with the deadline overrun. In the example, the period since the last completed calibration is recorded; the responsible experts explain on the basis of the finding which uses can actually be affected and whether the observation period has to be adjusted.

Example: Status matrix with separate status and a notable inspection point
Test caseSource dataIndependently established expected resultDecision or evidence
Deadline Due by 30.09.; Review due 06.10. 6 calendar days after the example date Keep open calibration point visibly evident despite completed maintenance
As found 100.18 g at reference 100.00 g Error +0.18 g; 0.08 g outside ±0.10 g Find outside example rule; assign investigation
As left 100.03 g after adjustment Error +0.03 g within the example limit Retain the earlier finding. No retrospective conclusion of acceptability
Prior use Last successful calibration in the example on 30.06.; documented usages since then, including on 01., 03. and 05.10. Capture usages since the last calibrated verification as the basis for the affected assessment. No automatic fault; document technical evaluation
Certificate Appendix Comprehensive report available; dataset incorrectly assigned An attachment cannot establish the correct link between the instrument and event Compare identifiers and key values
Resumption Activity completed; evaluation still open Completion alone does not yet meet the example rule Justified device usage decision with authorized responsibility

Sources: [3] [5] [4] [9] [13] [11] [10]

Review structured values and certificate attachments together

The calibration range describes event history and documentation for certificates or reports. Determine which data elements in the structured dataset are decision-relevant and which information is solely present in the annex. The device identifier, calibration date, and the relationship between test result and subsequent action should not be inconsistent.

When operations record only selected key results, the rationale for this selection must be justified. Such a selection may suffice for attendance tracking, while an investigation may require additional individual values and conditions from the certificate. Therefore, review a complete case including supporting documentation, a different finding, correction, and the associated decision. A report generated from a different event must not inadvertently produce the same conclusion without proper acknowledgment.

A calibrated value that is within acceptable limits does not automatically invalidate a previous result. Review the available records to identify any prior usage that may be affected and determine what additional information is required for proper evaluation. The outcome may vary; the software should provide transparent, traceable data, not replace an unvalidated automated root cause or batch determination.

Sources: [3] [6] [11] [13] [10] [9]

Further reading:

Roles, stored changes, and signatures differ

For the Core platform, the manufacturer specifies module-specific rights for administration, usage, or exclusion of access. Review concrete role scenarios: who is authorized to modify a schedule, record a result, assign a report, and evaluate usage? A small team may consolidate multiple responsibilities, provided that authorizations and, if necessary, required independence are appropriately defined.

The Trust Center distinguishes authenticated data set modifications and review actions from externally generated electronically signed documents attached to them. Do not conflate these pathways. A modification stored under a user account does not inherently fulfill all required electronic signature functions. Similarly, an electronically signed attachment does not automatically validate the entire dataset or any subsequent modification thereto.

For relevant records, define which events and changes need review and who reviews them. Access control and a history support traceability, but unusual events still require assessment. Establish the actual record and signature scope separately before drawing conclusions about FDA Part 11.

Sources: [2] [6] [9] [12]

Integrate flash validation and in-house verification evidence following coverage completion

GxPReady describes Flash Validation as an approach that links existing platform qualifications to the intended customer usage. Public disclosures reference configuration, processes, and operating environment; complete methodologies and detailed documentation are not generally made available. Request the specific scope for your project prior to deriving an abbreviation for particular tests.

Check which requirements, versions and results are documented. Do instrument programs, permissions and data transfer match the test conditions? Ask the supplier to explain limits and open findings. Reuse suitable evidence and add checks for local decisions and handovers it does not cover.

A dedicated method label, an available IQ/OQ package, or a manufacturer's description does not constitute automatic use authorization. Identify the responsible personnel for requirements, result evaluation, and operation. An actual, substantiated traceability chain is more important than the unverified transfer of document names. A fixed number of additional tests cannot be reasonably specified without a clearly defined scope.

Sources: [1] [6] [9]

Plan operations, modifications, and data access following contract end

For the SaaS system, responsibilities regarding changes, disruptions, backup, and recovery must be defined. The Trust Center outlines corresponding operational procedures but does not publish all detailed evidence. Obtain the information required for your specific use and evaluate how changes are communicated and assessed for impact on local programs.

Particularly specific is the public exit description: A data export package shall include structures, relationships, and associated electronic information. Additional readable reports are explicitly not intended as the sole or complete representation. Therefore, early review of format, appendices, change information, and the possibility of retrieving required relationships outside the system is recommended.

The website states in the standard agreement that data availability is guaranteed for 90 calendar days after termination. This is a contractual term, not a regulatory retention period; the actual written agreement holds legal weight. Clarify required retention, timely takeover, and future readability independently of this. A monthly termination clause does not indicate whether an unplanned system exit has been technically prepared.

Sources: [6] [7] [9] [10]

Further reading:

KMU-Start and Decision-Making Checklist for Usage Evaluation

Start with a manageable group of instruments and their actual programmes. Metrology and maintenance provide rules and sample records. The process team explains instrument use, IT explains operation and QA assesses its place in the quality system. Assign work according to competence and authority. There is no universal signature sequence.

Effort arises particularly from inconsistent legacy data, multiple programs per device, historical equipment, and unclear operational guidelines. Prepare these issues prior to scheduling. The following internal checklist combines data preparation, delivery receipts, and operational readiness. It does not replace a comprehensive risk assessment of your specific application.

  • Equipment, programs, operating procedures, and actual software version are clearly documented.
  • Expirations, interval rules, and changes are professionally defined.
  • Maintenance closure, calibration results, and qualification are evaluated separately.
  • The intended device state is reliably reached by the actual end user.
  • Dataset, certificate, and critical values are correctly assigned.
  • Roles and unauthorized changes were reviewed based on specific cases.
  • Invoices have been reviewed; remaining local gaps have supporting documentation.
  • Changes, failure procedures, data export, and subsequent retention are the responsibility of the responsible party.

Sources: [2] [6] [9] [13] [10]

Project experience and collaboration

Resolve outstanding equipment requirements before use

With equipment owners, we choose a device whose maintenance, calibration and qualification may have different statuses. We establish which prerequisite for intended use is missing and how that information reaches staff at the workstation. A focused change in mapping or workflow may suffice. Unclear device identities, source data or responsibilities need attention first. With IT, we then match supplier evidence and local tests to the process. A completed work order does not by itself establish that the device is fit for use.

Frequent Questions on GxPReady and Device Usage

Is GxPReady Suite a local software or a cloud-based system?

The vendor describes GxPReady Suite as a SaaS-based CMMS with a dedicated database per customer. A numerically current release version is not publicly available. Therefore, assess the actual delivered version, modules, and operational responsibilities within the project. The presence of a customer-specific database does not necessarily validate all security controls nor the suitability of the solution to your specific equipment and record-keeping processes.

Sources: [1] [2] [9]

Does the Validation module automatically validate our devices?

No. The description pertains to planning and traceability of validation or qualification activities, including status and documentation. Whether technical qualification was appropriately conducted is determined by its technical evidence. Separately, the computerized system is assessed for its intended administrative and decision-making purposes. The presence of a dataset or term completion does not substitute for either of these two evaluations.

Sources: [4] [9] [13]

Does a completed maintenance make an overdue calibration valid again?

This conclusion is not justified. Maintenance and calibration address different questions and are described as separate programs. Evaluate the relevant prerequisites for usage individually. In the example presented in this article, calibration remains open, even though maintenance has been completed. An automated cross-cutting release or status logic is not supported by the publicly available functional specifications.

Sources: [3] [5] [13]

Does GxPReady automatically deactivate a overdue device?

Such machine or process coupling is not publicly documented. The FAQ does not describe the platform as pre-configured for complex integrations. You must define how a pending or unclear state reaches the user and prevents unauthorized use. Assess the actual technical or organizational control in place for suitability; a simple reminder alone is insufficient as evidence of this effect.

Sources: [7] [3] [9] [13]

Can we simply postpone calibration deadlines due to personnel shortages?

A change of date should reflect a technically justified, authorized decision and make existing facts comprehensible. Whether and under what conditions a change is acceptable depends on the device, use and previous evidence. The software offers appointment management, but no general regulatory extension. Check the change history, justification and the following usage rule.

Sources: [3] [6] [9] [13]

Is an appropriate As-left value sufficient after calibration?

In the respective testing context, the state following the intervention is assessed. A previous as-found result outside the defined limits remains subject to evaluation. In the example provided in this article, a post-intervention value of +0.03 g falls within the established limits, whereas a prior value of +0.18 g was recorded. This does not automatically imply that all prior usages were safe or that such usages should be universally rejected. The relevant time period and potential implications must be assessed on a professional and scientific basis.

Sources: [3] [11] [13] [10]

Is a attached signed PDF already the complete device record?

No, the file format or signature alone cannot be used to determine this. The attachment must relate to the correct device and event. Additional information may be present in structured data, relationships, or changes. Therefore, verify which records jointly meet your decision-making and retention objectives. Furthermore, an externally signed document does not automatically confirm subsequent changes to another data set.

Sources: [6] [10] [9]

What does the offered Flash Validation package actually save us?

Appropriate existing platform documentation can reduce the need for independent assessments. However, the specific tasks undertaken by the Flash Validation package can only be determined from its content and your configuration. The public description references platform documentation and the evaluation of customer-specific conditions; the full content has not been reviewed. Compare requirements, version, results, and limitations. Data transfer, local rules, or special roles may require additional validation evidence.

Sources: [1] [6] [9]

Are our data automatically permanently available after the end of the contract?

The public standard description specifies an export package and 90 calendar days of retrievability; however, the written contract is decisive. This does not constitute a guaranteed, unlimited archiving right nor a general regulatory deadline. Proactively clarify required formats, relationships, attachments, and future readability. The system must ensure retention of required data even after the end of the SaaS agreement.

Sources: [6] [7] [10] [9]

What preparation is required for a small company?

Prepare a cleaned device list, current software versions, representative validation evidence, and known open cases. Clarify who defines rules, captures data, and evaluates device usage. Then request appropriate supplier documentation and export examples. This preparation makes effort drivers visible; a one-size-fits-all onboarding duration or a blanket cost for required validation evidence cannot be inferred from it.

Sources: [2] [6] [9]

Sources and review date

As of October 6, 2026. Reference: publicly described GxPReady Suite as a SaaS-based CMMS with Core, Calibration, Validation Tracking, and Maintenance modules. No verifiable public numerical version or complete administration manual has been identified. The Flash-Validation Package and detailed assessments were not fully reviewed. Human medicinal product GMP with Annex 11 and Chapters 1, 3, and 4; contractual terms and regulatory retention requirements are separated. Examples provided are internal reference guides only, not calibration activities or product testing.

  1. GxPReady — Validated CMMS
  2. GxPReady Core Platform
  3. Calibration Management Module
  4. Validation Tracking Module
  5. Maintenance Management Module
  6. GxPReady Quality & Trust Center
  7. GxPReady Frequently Asked Questions
  8. European Commission: EudraLex Volume 4
  9. EU GMP Annex 11: Computerised Systems, January 2011 revision
  10. EU GMP Chapter 4: Documentation, January 2011
  11. EU GMP Chapter 1: Pharmaceutical Quality System
  12. FDA: Part 11, Electronic Records; Electronic Signatures — Scope and Application
  13. EU GMP Chapter 3: Premises and Equipment

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Integrate device programs and validation evidence effectively

We support you in distinguishing actual usage, evaluating delivery receipts, and developing clear checks for data transfer, status, roles, and operational usage decisions.

  • 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 →