Table of contents
At a glance
What do you validate in the GUS-OS Suite?
Demonstrate that the installed GUS-OS environment supports the intended GMP workflows. Assess the modules, recipes, status rules, roles and interfaces actually in use. Supplier documentation can provide evidence where it covers your process. The product name alone does not establish a validated state or the suitability of every configuration.
- Recipe approval, the decision to use a material and batch certification are separate decisions.
- A visible QK status must be effectively displayed at the intended booking paths.
- Workflow templates and supplier assessments require a clear link to their intended use.
- Exceptions, repetitions and subsequent changes are considered.
1. Document the actual GMP usage and product status
GUS describes the GUS-OS Suite as an ERP system for the process industries. Its pharmaceutical product page describes recipe management and batch records for tracing where materials came from and where they were used. Use this as a starting point for documenting your processes. Record the release, patch level, licensed modules, customisations, connected systems and a responsible contact for your installation.
The integration page references on-premise, hybrid, and cloud deployment models. Document who is responsible for your model's infrastructure, data backup, access controls, interfaces, and changes. A cloud-based Digital Hub also refers to a single point of access; this does not imply that the entire ERP installation operates in the same manner.
This article focuses on GMP-related processes for human medicinal products. Annex 11 aligns with regulated activities. Purely commercial functions may fall outside the scope of this document, although commonly shared master data can have an impact. For FDA-regulated records, the Part 11 applicability must be determined separately based on recordkeeping obligations and actual electronic use.
2. From the process to a verifiable traceability chain
Start with a specific question: What incorrect system decision could render an inappropriate material usable, trigger an incorrect formulation, or compromise a quality decision? Formulate a corresponding observable requirement. "Batch management available" is insufficient as a test objective; "a raw material batch that is locked cannot be used in the intended sampling process" can be verified accordingly.
GUS provides support for the validated implementation and explicitly states that software cannot be considered fully validated unless it is actually deployed. Therefore, assign existing specifications and test evidence accordingly: Which standard functions, which version, and what prerequisites were evaluated? For custom workflow paths or alternative configurations, targeted questions remain open. The following matrix serves as an internally developed planning aid.
| Process object | Key question | Reasonable demonstration |
|---|---|---|
| Recipe version | Which version may a new order use? | Release, validity and actually implemented status |
| Raw material batch | When may this batch be used for this purpose? | Status, relevant deadlines and sample take-off |
| Verification scope | What findings support the decision? | Test specifications, complete results, and evaluation |
| Workflow | Who is authorized to initiate the next step? | Test roles, including exceptions and deputies |
| Link to finished goods | Which batches are assigned? | Forward and backward traceability with quantity reconciliation |
3. Connect formulation development and operational use
GUS describes development recipes and version management in the GUS-OS product development module. Check the transition to operational use. Which version is approved, when does it take effect and which version remains associated with an existing production order? The supplier's description leaves these decisions to your implementation.
An appropriate in-house test begins with two clearly distinct recipe states. For example, alter the quantity of a component in the new version. Compare an existing order against a subsequently newly created order. Entries, calculations, and generated batch information should conform to previously defined version rules; a silent mixing would constitute a investigable finding.
Also consider copied formulations and subsequent master data modifications. A correctly filled release field provides little assurance if the operational content later appears different without notice. Describe which changes trigger a renewed professional assessment and who is responsible for making that determination. A mere cost change should be evaluated differently from a changed usage volume.
4. Separate QK Status, Post-testing, and Usability Assessment
GUS describes incoming and in-process inspection in GUS-OS quality control, together with monitoring of release, retest and expiry dates. Materials management tracks inventory by attributes such as QC status and storage location. Establish which combinations actually allow material issue, stock transfer or delivery.
Prepare a concise status summary outlining permitted and prohibited actions. A material may be physically present, commercially available, and yet unsuitable for a specific manufacturing step. Assess the timing of the control: at reservation, upon withdrawal, or during a subsequent booking? A deprecated status from a prior reservation must not be unverified and used as a current decision.
Expiration and retest dates have distinct professional implications. Define the expected behavior for each specific scenario rather than consolidating both dates into a single general stability rule. A successful retest does not automatically extend the usability of any material; for such extensions, relevant material specifications and the approved process must be referenced.
5. Test batch traceability through partial quantities and corrections
The pharmaceutical specification includes origin and usage documentation. For internal review, employ a complete and manageable material flow: incoming raw material batch, partial withdrawal, processing into a bulk batch, and assignment to finished product. Subsequently trace both forward—from the batch in use—to the finished product, and backward—from the released product to the batch that was used.
Include a valid correction or reversal. Can the original transaction, correction, and remaining quantity still be clearly reconciled? When multiple storage locations are involved, a search should not inadvertently exclude parts of the inventory. Additionally, verify the reporting for an unauthorized user: does the user have read rights for traceability and rights to modify assignments for different tasks?
A compelling batch list is still not a validated recall process. Responsibilities, reachable recipients, decision points, and additional records must align with the intended workflow. This article limits the example to the ERP-side reliability of assignment and does not claim complete recall qualification.
6. Separate evaluation of workflow release, audit trail, and signature
GUS describes a graphical workflow designer, role-based tasks, optional second-person checks and version-controlled checklists. For your configuration, examine repeated steps, alternative branches and deputy arrangements. For example, test whether a rejected recipe goes through the intended process review again after correction.
The quality section references an audit trail module. Please demonstrate its specific coverage: for example, changes to a relevant formulation quantity or to a quality decision. Together with QA, assess whether the change—including its contextual relationship—is clearly evaluable, who has the authority to modify the record, and how required reviews are conducted. A manufacturer's description does not substitute for this evaluation.
A completed work step is not automatically an electronic signature. Similarly, material release is not equivalent to legally regulated batch certification. If the ERP system represents such decisions, the significance, authorization, and record linkage must be explicitly defined and reviewed against applicable requirements.
7. Investigate scale integration and Digital Hub as process transitions
The integration page describes a scale connector for production, enabling the incorporation of weighing results into the production order. It also references the Digital Hub Service and its REST interface. These components should only be included within your scope if they are actually in use; the description does not guarantee error-free data transmission.
For a balance interface, test a clearly identified order, material, batch, instrument and unit. Interrupt the connection at a planned point and distinguish results already transferred from those still pending. A retransmitted result should not silently become a second weighing. Agree the expected response with the process owner before testing.
In the Digital Hub, the same level of attention must be given to rights and technical evaluations: What data may an external party modify, and what decisions may be derived in the ERP system as a result? A technically successful API call only confirms a data transfer pathway; it does not validate correct assignment or authorization.
8. Example: Reserved batch is subsequently blocked
A production order utilizes an approved formula and reserves a raw material batch. Prior to withdrawal, a quality result is issued; the batch is placed in the designated hold status as defined in the testing system. The testing objective is: the intended process prevents further use or implements the specifically defined, professionally authorized exception pathway.
Run the example through the transaction paths you actually use. A block on the standard ERP screen does not demonstrate that a separate mobile process or an interface posting enforces the same restriction. The table sets out expected observations for this example. It makes no assurance about GUS-OS Suite functionality.
| Test step | Expectation in the defined example | Supporting document to be retained |
|---|---|---|
| Withdrawal after blocking | Use is prevented at the relevant process step. | Booking pathway status, sequence, and reaction |
| Alternative booking pathway | The specified control remains effective there as well. | Comparison of the used surface or interface |
| Unauthorized status change | The user cannot lift the restriction independently. | User role and outcome of the change trial |
| Approved Exception | Rationale, decision-making and limited impact remain evident. | Exception record and subsequent batch movement |
| Repeat upon termination | No undetected double withdrawal occurs. | Batch identifiers and quantities before and after repetition |
Sources: [7]
9. Migration, Updates, and Recovery of the Process Measurement System
When moving to GUS-OS or making a major change, a matching overall stock quantity is insufficient migration evidence. Select representative records with different quality statuses, dates and recipe references. Compare their business meaning before and after the transfer. Historical links can be missing even when item numbers and quantities look right.
For updates, assign changes to the relevant processes. If a release affects workflow control or material booking, the corresponding cases should be re-evaluated. Unaltered documentation may be retained for further use following a justified assessment; neither blanket full revalidation nor unverified acceptance constitutes an acceptable standard.
A restoration test should also result in a professionally usable environment. Can the selected batches, recipes, and decision criteria be read? Do the application and its associated components align? Prior to a failure, clarify who will assess the restart and how interim activities will be traced.
10. Start with a common checklist to ensure readiness and operational capability
For a small and medium-sized enterprise (SME), the bottleneck is often the availability of the right personnel and documentation. QA assesses quality risks and provides evidence, while production and storage teams explain actual booking pathways, and quality control clarifies decision-making on release status. IT and system owners supplement operations, access rights, and integration points. The implementation partner must ensure that configuration and technical limitations are clearly traceable.
Explicitly include this involvement in the planning. A test may be technically feasible yet fail to enable a decision if the acceptable exception handling remains unclarified. The checklist below supports project initiation; the scope and formal approvals are determined according to your own quality management requirements.
- Intended use, affected locations, and relevant records to be described.
- Release, Module, Operating Mode and Customizations to be inventoried.
- Clarify recipe statuses and rules for currently ongoing orders.
- Define material status, date rules, and allowable exception pathways.
- Prepare representative test data including locked and corrected actions.
- Assign supplier proofs to own requirements and identify gaps.
- Agree on roles, interfaces, migration and recovery with the people responsible.
- Evaluate deviations and document the decision regarding intended production operation.
Project experience and collaboration
Check the recipe versions and status changes for an actual production order
Process owners select a known order and trace the recipe and master data versions actually used. In a suitable test configuration, we check permitted changes, status boundaries and the necessary history. Relevant manufacturer records may support your tests. Custom extensions need additional cases. With IT and Quality, we define evidence for the actual process. An industry-specific product label does not demonstrate suitability for your use.
Frequently asked questions about GUS-OS Suite
Is the GUS-OS Suite already validated when it is offered for pharmaceutical use?
No. Even GUS distinguishes between the software and its specific implementation within the company. What matters are your processes, configurations, components, and working methods. Existing supplier certifications can support internal documentation, provided their scope and prerequisites are aligned. Therefore, do not rely solely on a general validation assurance; instead, provide traceable documentation demonstrating the specific software version in use.
Which GUS-OS version is addressed by this guideline?
The evaluated public pages describe functional areas but do not specify a binding, current build for all installations. Therefore, the article does not assume any version number to be universally valid. For your project, release version, patch level, modules, and configuration must be documented. Version-specific support and agreed-upon functionalities take precedence over general product pages for specific functions.
Must we evaluate the entire suite at the same level of depth?
No. Start with GMP-relevant decisions and data. A financial accounting function may be assessed differently from a raw material usage rule. When evaluating, jointly review master data and interfaces: Even a seemingly administrative change can impact a quality-critical downstream process. The justification should be based on the actual usage and associated risks.
Is a QK release status already a medicinal product batch release?
Not automatically. A quality status may represent the usability of a material or a testing step. This must be distinguished from the legally mandated certification of a medicinal product batch. Document the significance of each status within your process and identify which party is legitimately responsible for making each decision. A field name alone does not answer this technical question.
How do we test recipe changes without having to trace and validate every single order?
Select distinct recipe states and representative order states: created prior to the change, created after the change, and optionally deliberately modified. Compare the imported contents against your predefined rules. Add risk-based, relevant boundary and exception cases. This is a proposed test design; justify which cases are sufficient based on your configuration and impact.
Does the Scale Connector replace the evaluation of manual checks?
No. Electronic transfer alters the sources of error but does not automatically eliminate all risks. Specifically assess mapping, unit, interruption, and repetition, as well as residual manual entries. The additional controls required depend on the process. The connector manufacturer's specification does not justify a general waiver of applicable accuracy controls.
Are the standard workflows and the audit trail module sufficient as evidence?
You provide functions whose suitability you evaluate specifically. For workflows, the established branches, roles, and repetitions are critical; for audit trails, the relevant records and their usefulness for technical review. Determine which supplier audits are transferable and which settings or process deviations require independent validation evidence.
What must a small and medium-sized enterprise provide prior to startup?
Useful are a current system overview, described core processes, module and version details, contact points at the partner, and existing specifications and test evidence. Identify QA, IT, and relevant process owners with available time. Unclear status rules or missing test data should be visible as specific preparation tasks prior to initiating a detailed test plan.
What factors determine effort and duration?
Crucial factors include the number and diversity of processes, existing workflows, interfaces, data quality, and availability of departmental expertise. The current state of existing documentation and the availability of an appropriate test system also influence planning. Initially assess a representative process chain. From this, the additional resource requirements can be better derived than from user count or a general time estimate.
What remains to be done after the regular introduction?
Monitor changes, disruptions, and new usage patterns. Assess relevant release decisions, modified recipe or status logic, and new interfaces prior to implementation. Also consider rights, recovery options, and the technical usability of archived data. Regular evaluation should confirm that prerequisites and supporting evidence remain aligned with current operations.
Sources and review date
Public GUS product pages and regulatory sources were checked on 6 October 2026. The product pages do not identify one build for every installation. Check modules, hosting model, licences and settings against your own environment. The tables and test scenarios are our practical examples and do not establish that the product features were tested.
- GUS ERP, GUS-OS Suite for pharmaceuticals
- GUS ERP: Quality Management
- GUS ERP: Materials Management and Logistics
- GUS ERP: Workflow Management
- GUS ERP: Integration and Interconnection
- GUS ERP: ERP Validation for Pharmaceutical Companies
- European Commission: EU GMP Annex 11, January 2011 revision
- European Commission: EU GMP Annex 16 – Certification by a Qualified Person and Batch Release
- EMA: GMP/GDP Questions and Answers – Annex 11
- FDA: Part 11 – Scope and Application
- European Commission: EudraLex Volume 4
Sources checked: .
Define which tests your GUS-OS processes need
Daniel Herrmann Consulting supports you in integrating existing documentation, critical process transitions, and outstanding evidence into a justified work plan.
- 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.

