Table of contents
At a glance
How do you validate CASQ-it for a GMP process?
Validate the CASQ-it modules and configuration against the intended quality process. Link inspection instructions, measurements, actions, decisions and ERP handovers in the requirements. Assess supplier evidence and fill gaps locally. A task status, progress percentage or transmitted decision alone does not establish that an action was effective or that subsequent material use was correct.
- CASQ-it is a modular CAQ solution; the specific application matters, not a general industry designation.
- Task execution, effectiveness assessment, and accountable process closure are distinct forms of documentation.
- The ERP feedback and inspection tool assignment are verified against the actual data transfers.
- Product functionalities and industrial methods do not replace the classification of the human medicinal product GMP process.
1. Identify the CASQ-it modules used together
CASQ-it is the modular CAQ solution from Böhme & Weihs. Current manufacturer websites also use the designation Böhme & Weihs CAQ or B&W CAQ. The offering includes quality planning, testing, complaints, and corrective actions, with integrations to ERP and MES. MESQ-it is presented as a standalone solution for production management; its functions are not automatically included in your CASQ-it installation.
Capture product status, modules, licenses, configuration, interfaces, and operating mode. Public product pages do not provide a consistent and up-to-date build number. For example, access to a task management interface does not confirm that the entire system operates as a SaaS solution. What matters most are your actually documented installation and contractual responsibilities.
This guide addresses processes involved in the manufacture of human medicinal products under EU GMP. The shared manufacturer responsibility for pharmaceuticals and medical devices does not negate their distinct regulatory scopes. References to ISO standards or FDA guidelines do not constitute general compliance assurance. Assess which specific function impacts product quality, patient safety, or data integrity.
2. Define modules based on their decision logic and data transfers
Instead of incorporating all available functions into validation, a representative process based on the actually used combination is followed. Which directive governs it? Where is a measurement value generated? Who evaluates the result? Which other application uses the output? These interfaces define the specific requirements.
The following internal work aid matches documented manufacturer functions to corresponding inspection questions. It does not describe a standard configuration. Supplement each version with your specific version, the leading data object, and the responsible process step. Modules not installed are not included in the scope of validation solely due to product family.
| Area | Documented function | Own decisive evidence |
|---|---|---|
| WEP and ERP | Delivery inspection task; feedback with usage decision. | Correct delivery and product assignment, as well as intended processing in the ERP system. |
| PMM and Testing | Measurement equipment management, expiry and availability verification. | Suitable inspection equipment and effective action when its use is not permitted. |
| RUF and QWM | Complaint, mandatory fields and configurable workflow. | Required findings, roles, and decisions within your own workflow. |
| TMS and Origin Tracking Process | Linked tasks, progress, and timeline monitoring. | The processing status remains distinguishable from efficacy and release decision. |
3. Test specifications and measurement values to be compared against an independent target value
CASQ-it WEP describes integrated testing protocols and the transfer of attribute values from attached test methods or measurement devices. This results in targeted testing questions: Is the value correctly assigned to the intended attribute? Are the unit and decimal representation preserved? Does the applied reference truly pertain to the product and the shipment?
Prepare a small, independent reference dataset. It includes the expected identifiers, units, edge cases, and one intentionally mismatched assignment. Compare not only a screen overview with a report derived from the same potentially flawed data source. The original reference dataset remains unchanged, ensuring that any transmission error can be detected.
The manufacturer also specifies end-point dynamic validation and morphological feature categories. Such a function does not constitute general authorization to reduce GMP inspections. For starting materials intended for finished pharmaceutical products, particular attention must be given to identity testing and the conditions for accepting third-party test results, as specified in EU GMP Chapters 5.35 and 5.36. The approved testing scope and its exceptions must be clearly defined. Subsequently, verify that the configured rule precisely selects this scope and appropriately handles a changed starting state.
4. Demonstrate separately the status and suitability of measurement instruments
CASQ-it PMM manages calibration instruments, calibration data, history, and expiry dates. The product description includes usage-based interval calculations and availability checks within linked test modules. For your process, it must be clearly defined which information permits, warns against, or prevents usage. An amber light indicator alone does not adequately address this question.
Suitable test cases include a released calibration device, a defective calibration device, and a disputed expiry date at the specified cut-off time. Document the expected response for the actually used calibration path prior to use. Also evaluate whether an exception could be triggered and determine the required technical or scientific decision for such an event.
The described XML integration with external calibration service providers enables the transfer of information, results, and certificates. Upon receipt, compare the measuring instrument identifier, test order, and certificate reference. Successful import of a certificate does not validate the suitability of every measurement nor guarantee error-free assignment. Calibration status, measurement process, and software processing require appropriate, interlinked supporting evidence.
5. Complaint, responsibility, and effectiveness evaluation differ
The RUF product specification lists configurable mandatory fields and individual workflows via QWM. TMS links actions to their originating process and updates the progress status of that process. This constitutes a different form of evidence than the professional assertion that a root cause has been appropriately addressed and a corrective action has proven effective.
Define when a finding is to be investigated, what immediate actions are required, and who decides on further processing. Not every task or every technical defect necessitates an automatic full CAPA process. Conversely, a closed task list must not conceal an ongoing quality issue. The decision must align with the implications, level of uncertainty, and existing evidence.
Chapter 1 of the EU GMP Guideline addresses appropriate root cause analysis and suitable corrective or preventive actions, evaluated with a risk-based effectiveness assessment. The 8D method described on the RUF side represents a possible work structure, not a general GMP requirement. In own procedures, identify the necessary decision points, rather than adopting an industrial form without review as a benchmark.
6. Test example: 100 percent processing, but still no positive closure
The following scenario represents a standalone review draft. It describes no completed CASQ-it test. For test procedure C-17, four equally weighted tasks are defined: root cause assessment, implement correction, controlled revision of work instruction, and conduct effectiveness testing. Completion rate counts only tasks that have been completed.
The closure rule in this example requires a positive effectiveness assessment and a decision by an authorised person. An effectiveness check can be performed and still fail. Keep completion of the check distinct from its outcome. The four tasks show one possible structure. An urgent containment action may be necessary independently of that sequence.
| Test case | Undetermined defined state | Calculation | Expected decision |
|---|---|---|---|
| C-A | Three tasks completed; effectiveness assessment still pending. | 3 ÷ 4 × 100 = 75 % | No positive conclusion; open inspection visibly maintained. |
| C-B | Four tasks completed; effectiveness assessment negative. | 4 ÷ 4 × 100 = 100% processed | No positive conclusion; assess the finding and determine next steps. |
| C-C | Four tasks completed; positive efficacy demonstrated and authorized release decision available. | 4 ÷ 4 × 100 = 100% processed | Closure possible according to own defined rules. |
7. Track ERP notifications up to the decision point at which the decision was made
The WEP page outlines the pathway from ERP material delivery to inspection task assignment and the feedback of results with usage decisions. For validation, it is insufficient to merely document the successful transmission of messages. The target system must correctly receive and process the intended workflow and its associated meaning.
For example, define what should occur in cases of no response, double transfer, or unknown delivery identifier. Should the process be visibly paused? Can it be controlled and retried? Which source determines the status in case of conflicting status information? These questions pertain to your interface; a specific technical implementation is not required.
In addition, verify the technical accuracy of the assigned code mappings. A usage decision such as special release or acceptance with reservations must not be treated as unconditionally accepted due to an inappropriate code assignment. Clearly define prerequisites and decision authorities. The digital processing must be evaluated in conjunction with the actual storage or production workflow, not as a guarantee of physical locking.
8. Rights, change history, and reports for one's own process to be reviewed
The industry description references a rights concept, electronic signature, and change control. The actions and data fields actually covered by your environment should be demonstrated through selected critical changes. Test not only the authorized user but also a person who is not authorized to make the relevant decision.
An appropriate review process shall include the original assessment, relevant changes, responsible individual, timestamp, and the subsequent decision. When electronic signatures are used, their meaning and association with the correct data set must be clearly defined. A modified report must not implicitly suggest that the original evaluation had already appeared in that form.
TMS provides evaluations and progress calculations based on a predefined or custom schema. Therefore, document the evaluation logic: what counts as open, what as completed, and which activities are included in the numerator? A correctly calculated percentage can adequately address an otherwise inappropriate technical question. The inspection example in Section 6 precisely illustrates this boundary.
9. Supplier evidence, changes, and operational proofs to be consolidated
Request documentation on the delivered version and module scope and align it with your requirements. A suitable supplier test can constitute part of the evidence. A general industry presentation or an ISO statement does not demonstrate whether your specific field regulation or ERP assignment functions as intended. Ensure visibility of coverage, prerequisites, and remaining gaps.
Evaluate changes to rules, interfaces, roles, and reports, as well as software updates. A new mandatory field condition may block an existing process; a modified key performance indicator may alter the presentation of historical reports. Assess relevant impacts on unaltered functions as well. Existing supporting documentation does not need to be completely replaced solely due to a new version name.
For operational purposes, recovery, access, retention, and future readability constitute part of the validation evidence. Define how a process and its associated links remain understandable after a restore or export operation. Retention periods and review intervals shall align with specific requirements and regulatory frameworks, not with a general presumption from this document.
10. Contribution and checklist for SMEs
The most critical preparatory step is a jointly agreed process. QA determines the technical decisions and permissible exceptions. Validators and operational responsibility holders provide original specifications and defect cases. IT and the implementation partner describe data flows, configurations, and operational procedures. The system owner consolidates requirements, documentation, and open findings.
The effort increases significantly due to different module variants, unclear interfaces, and inconsistent decision rules. Early alignment on these differences is more effective than a generic number of test cases. Use the following list for preparation and supplement it with specific document references and responsible parties.
- Clearly document installed modules, product stands, hosting arrangements, and point of contact.
- Leading requirements and data objects for a representative quality process are defined.
- Verify measurement values, units, testing equipment, and result assignment against independent target values.
- Processing yield, effectiveness assessment, and release authorization to be defined separately.
- Trace ERP codes and error handling on both sides.
- Review critical rights, signatures, and changes throughout the complete process.
- Match supplier documents with own configuration and open justifications.
- Control of change evaluation, restoration, and legible retention during operation.
Project experience and collaboration
Trace an inspection finding through to the assessed action
A completed CASQ-it workflow can still have an unresolved quality question. With your quality team, we trace a finding through the action, effectiveness assessment and any message to the ERP system. The task status and quality decision are recorded separately. Targeted handover tests may suffice for an established workflow. For newly connected modules, we first identify the data, responsibilities and evidence needed. Your team sets the operational acceptance criteria. We work with the technical teams to trace dependencies and identify gaps in testing.
Frequent Questions on Validation of CASQ-it
Is CASQ-it automatically GMP-compliant because the manufacturer is addressed to the pharmaceutical sector?
A sector description initially demonstrates the availability and specified functionalities. Whether its implementation is appropriate depends on modules, configuration, data pathways, and operating procedures. Map requirements to the actual process and verify appropriate supplier documentation. Human medicinal product GMP, medical device requirements, and FDA references must not be equated solely due to a common product line.
Must all CASQ-it modules be validated together?
The scope aligns with the intended use and dependencies. Functions not installed are not automatically included. However, an integrated module or ERP system may be relevant for a critical decision, even if only a portion of it is evaluated. Describe the system boundary together with data transfers and justify the coverage.
Can dynamic validation checks at the warehouse receipt be reduced?
Under pharmaceutical GMP, only within the scope of applicable testing requirements. For starting materials, finished pharmaceutical product manufacturers must, according to EU GMP Chapter 5.35, verify the identity of each batch in accordance with Annex 8. The use of manufacturer- or supplier-provided results is subject to the conditions specified in 5.36, including qualified supplier relationships, appropriate audits, and periodic full analyses. Software dynamic capabilities do not override these limitations. Define the approved testing scope and exceptions and evaluate their applicability across different starting material conditions.
Does a green test instrument status serve as evidence for the measurement value?
No. In addition to the status, verify the appropriate calibration tool, its assignment, the suitable measurement process, and the unaltered handling of the results. Also assess how the specific application addresses an inappropriate use. A calibration certificate can provide important evidence, but it does not automatically replace all the validation evidence required for the intended measurement.
Does 100 percent in the action report indicate that the CAPA is closed?
No. In the example of this article, the completion rate only includes tasks that have been performed. Even a fully executed but negatively concluded effectiveness test results in 100% completion. Nevertheless, the CAPA closure still requires the evaluation as defined in the quality procedure and a duly authorized decision. Therefore, a report must clearly distinguish between completion status, efficacy outcome, and closure status.
Is an 8D report always required for a pharmaceutical process?
No, this does not imply a general GMP obligation. RUF describes 8D as an supported industrial approach alongside simpler workflows. For the own process, appropriate investigation, actions, and where applicable, effectiveness evaluation are decisive. Select an appropriate structure and justify its scope. Avoid both unnecessary forms and a simple "completed" note when a quality issue remains open.
How do we verify the transition from CASQ-it to ERP?
First, define identifiers and the professional meaning of transferred values. Then, compare an appropriate source process with the processing in the target environment. Supplement missing, duplicated, or incorrectly assigned feedbacks as controlled negative cases. A transport confirmation alone is insufficient if the ERP subsequently derives an incorrect usage decision. The actual interface determines the implementation.
Does the manufacturer's stated change control cover each required validation evidence?
A general manufacturer description does not demonstrate coverage of every relevant action within your configuration. Review selected changes to specifications, results, and decisions with role and time references. Additionally, assess how a subsequent reader would understand the context and which associated applications are involved. From this, it becomes evident which additional supporting evidence is missing.
Must all tests be repeated following an update?
Not at all. Evaluate changes, affected requirements, existing supplier receipts and effects on linked processes. Also unchanged functions can be affected, for example by a new interface assignment. Document which previous documents continue to apply and which targeted checks are necessary. The version change alone does not determine zero tests or a complete new test.
Sources: [8]
What documentation should QA and IT prepare prior to the project?
Useful are module and version lists, process flowcharts, role definitions, testing requirements, interface descriptions, reporting criteria, and existing supplier documentation. Supplement a representative process with independently defined expected outcomes and known failure cases. This enables early identification of missing evidence or unclarified decision rules. This provides a more robust planning basis than the number of installed screen layouts.
Sources and review date
Source date: 6 October 2026. Public manufacturer websites list CASQ-it or Böhme & Weihs CAQ and its modules without consistent, up-to-date build numbers. Specific licenses, configurations, and customer documentation must be verified on a project basis. Regulatory reference: Human medicinal product GMP; other areas require individual assessment.
- CASQ-it: CAQ Software for end-to-end quality management
- Manufacturing and Quality Management for Medical Devices and Pharmaceuticals
- CASQ-it WEP: Goods receipt inspection and supplier management
- CASQ-it PMM: Testing Equipment Management
- CASQ-it TMS: Corrective and Preventive Action Management
- Böhme & Weihs CAQ RUF: Complaint Management
- European Commission: EudraLex Volume 4
- EU GMP Annex 11: Computerised Systems
- EU GMP Chapter 4: Documentation
- EU GMP Chapter 1: Pharmaceutical Quality System
- European Commission: EU-GMP Chapter 5 – Production, valid since March 2015Targeted original comparison on 18 October 2026: No. 5.35 and 5.36 for starting material testing in finished pharmaceutical products. Other regulatory areas to be separately categorized.
Sources checked: .
Demonstrate the key CASQ-it transition milestones
Daniel Herrmann Consulting supports you in the delimitation of the module network, the evaluation of existing evidence and concrete tests of your quality decisions. Together with QA and IT, open evidence and operational responsibilities become tangible.
- 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.

