Table of contents
At a glance
How do you validate ETQ Reliance, now Octave Reliance?
Identify the QMS processes and product version actually used. Assess the scope and applicability of supplier documents and add evidence for local workflows, roles, data relationships, signatures and operation. The supplier now identifies ETQ Reliance as Octave Reliance. A product or compliance claim does not establish the suitability of the customer configuration.
Clarify current product names and currently used product versions
The manufacturer describes Reliance as the rebranded continuation of ETQ Reliance under Octave. Therefore, both search identifiers are relevant to customers. The current manufacturer website is a product overview and does not constitute a complete specification of your installation. Capture version, operating model, utilized applications, and customer-specific customizations. Existing documentation under the previous name may still be relevant but must be aligned with the current actual state.
Verify sources for currency. An outdated ETQ address may currently redirect to a different Octave offering. Such a match does not constitute reliable current functionality evidence for Reliance. Use appropriate manufacturer documentation and contractually accessible materials. This contribution describes a methodological validation strategy. It does not claim a uniform delivery scope across all Reliance versions.
Sources: [1]
Determine QMS scope in accordance with the quality processes employed
Reliance is offered for various quality processes. Determine which of these you actually use: for example, quality incidents, CAPA, document control, training, or supplier assessment. Not every available process automatically falls within your validation scope. At the same time, a critical link must not be missing, simply because two applications are licensed separately or assigned to different organizational teams.
Describe the lifecycle of relevant records. Who creates them, which information is reviewed, who makes the decision, and what follow-up actions arise? For example, a change to documents and training may result from a CAPA. The system boundary includes only the actual required transitions. Requirements also depend on product, market, and applicable quality framework. A general Part 11 statement does not constitute a complete assessment of applicability across all regulated industries.
Compare supplier package and customer-specific documentation
Request the documentation appropriate for your site. Assess development, relevant testing, known limitations, change information, and operational performance. Availability of evidence will be confirmed with the supplier. A general marketing claim does not substitute for a specific statement regarding the tested functional scope. Accepted evidence will be linked to internal requirements and evaluated for transferability.
Complete the actually configured customer application. This includes mandatory fields, states, decision rules, roles, deadlines, relationships, and integrations. A standard workflow may have been correctly tested yet still not align with the approved process. Document deviations and configuration decisions. Avoid redundant repetition of appropriate supplier testing, but do not close gaps with a general manufacturer confirmation. The user is responsible for determining suitability for their intended use.
Sources: [2]
Example: Quality incident with CAPA
In the example, an employee records a recurring quality incident. The responsible party assesses the impact and root cause and initiates a justified CAPA. A corrective action modifies a work instruction; a subsequent review evaluates the effectiveness after a defined period. The process may only be closed in accordance with the established criteria. These criteria represent a process example, not a universal reliance-standard configuration.
The reference set includes a complete routine case, missing mandatory information, an unauthorised attempt to close a case and an ineffective action. Also check the links to the changed document and any training needed. A completed task alone does not establish that the action addressed the cause. The following matrix is our own worksheet connecting business decisions to system evidence. It prescribes no legally required document structure.
| Process step | Expected finding | Targeted test batch |
|---|---|---|
| Data capture | Event clearly and completely documented | Missing critical information |
| Assessment | Responsible party determines | Unauthorized evaluation attempt |
| Cause | Analysis traceable | Symptom only renamed |
| Action | Implemented by responsible party | Open mandatory step |
| Compound | Correct document and training alignment | Incorrect revision assigned |
| Effectiveness | Evaluation of result against criterion | The measure remains ineffective. |
Separate workflow status from professional judgment.
A status such as closed, approved, or completed requires a clearly defined meaning. Describe entry conditions, authorized roles, and required documentation. Assess reverse transitions: Can a task be completed without the necessary information? Can an administrator change the status without the required context remaining visible? The actual capabilities will be evaluated based on the specific system version in use.
Deadlines and escalation paths support process control but do not replace evaluation. An automatically flagged action requires a responsible handler and a feasible follow-up process. A postponement of a scheduled activity must not obscure the historical timeline. For corrective actions, effectiveness is assessed using appropriate criteria. A green dashboard initially displays a calculated representation; whether this is clinically valid is verified against a known population.
Verify data relationships, signatures, and history
Quality records are frequently interlinked. Assess relationships between events, CAPA, document, training, and affected product. An existing link must point to the correct object and, if applicable, the correct historical version. Modifications to current master data must not inadvertently reinterpret a previous decision. Define which information is required for future investigations.
For electronic signatures, the scope of use and specific requirements are considered separately. Evaluate signer, significance, timing, and record linkage. Login and authorization are distinct functions. For relevant data modifications, assess required history and review. A manufacturer's indication of audit trail functionality serves as the starting point, not the full review outcome. Test the events and pathways actually used in your process.
Consider operations, integration, and restoration.
Describe user management, changes, disruptions, data retention, and supplier communication. If Reliance is integrated with ERP, identity service, or other applications, verify critical handoffs and error scenarios. A technically successful import may result in an incorrect status or incomplete relationship. Therefore, the evidence considers the intended end state and controlled re-execution following interruptions.
Evaluate security, export, and recovery in accordance with the operational model. What services does the supplier provide, and which retrieval checks remain the responsibility of the end user? Assess the required usage following an appropriate recovery scenario. A readable export does not automatically constitute a complete copy of dynamic relationships. For a supplier change or system decommissioning, data, history, and required contextual information are considered under the exit concept.
Sources: [2]
Fitness for purpose and improvement throughout the lifecycle
The closure integrates scope, supplier certifications, customer configuration, internal testing, and operating conditions. Open items will be evaluated based on their actual impact. Release shall not be granted for unused applications or unverified enhancements. Assign responsibility for process, configuration, and operations. Quality management and IT must understand and align on the same states and decisions.
New workflows, forms, permissions, interfaces, and releases require a corresponding impact assessment. Maintain known reference cases for targeted recurrences. Consider process improvement: recurring delays or ineffective actions may indicate inappropriate rules. Robust QMS validation supports an executable quality process. It confirms not only that all screen fields can be saved.
Project experience and collaboration
Trace quality decisions through the Reliance workflow
For your Reliance environment, we start with a quality event and the decisions associated with it. With QA, process owners and IT, we trace tasks, CAPA, effectiveness assessment and the underlying data links. A gap in an existing configuration may concern one handover. When several processes are introduced or revised, we first agree roles and shared status rules. We use suitable manufacturer evidence. A product name change alone neither changes intended use nor replaces assessment of the version in use.
Frequent Questions on Reliance Process and Evidence Requirements
Is ETQ Reliance currently Octave Reliance?
The manufacturer describes Reliance as a rebranded continuation of ETQ Reliance. For specific functional statements, the actual product and version status must be used. Existing documentation must be appropriately aligned. A name change alone does not constitute evidence of unchanged configuration or identical delivery scope.
Sources: [1]
Does the manufacturer's validation package suffice?
Appropriate documentation can provide essential evidence. Assess the current status, scope, and transferability against your requirements. Customer-specific workflows, roles, integrations, and operating rules require appropriate enhancements. A generic manufacturing reference does not confirm that your own quality process is accurately represented.
Must every offered Reliance application be validated?
The scope aligns with actual usage and its regulatory significance. Unused offerings are not automatically included. However, relevant connections between utilized applications should be assessed. Any organizational or licensing separation must not disrupt an essential traceability chain.
Is a closed CAPA automatically effective?
No. The system status must reflect the decision established in the process. Efficacy is evaluated against appropriate criteria and documented in a traceable manner. Completion of a corrective action item can confirm implementation, but does not provide sufficient evidence that the root cause has been permanently controlled.
Sources: [3]
Which changes require additional testing?
Evaluate, among other aspects, workflow rules, mandatory fields, roles, signatures, relationships, and interfaces. The scope aligns with the relevant risks and statements. A new field may be trivial; a minor status rule could alter a central decision. Document the specific impact rather than general categories.
What is important regarding historical quality records?
The following are required: clear content, identity, timing, relevant history, and correct relationships. Assess whether subsequent master data or document amendments may affect the historical integrity of the information. Current views and exports must demonstrate their scope and extent. The presence of a dataset alone does not constitute full investigative capability.
Sources and review date
As of October 14, 2026. Regulatory classification and manufacturer responsibilities are separately documented. Examples, test matrices, and templates are standalone reference tools; they are customized for actual usage purposes.
- Octave: Reliance, formerly ETQ RelianceCurrent manufacturer website confirms the renaming of ETQ Reliance. Functional and compliance statements are manufacturer declarations and do not constitute independent certification; verified on 14.10.2026.
- 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.
- EMA / ICH: Q10 Pharmaceutical Quality System, Step 5 (2008)Section 3.2.2: Root Cause Analysis, CAPA, and Effectiveness Evaluation. Specific action plans and exercises provided in the contribution are standalone methodological aids.
- PIC/S: PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection Guidance on Data Integrity; in particular electronic data, transmission, access, and review.
- eCFR: 21 CFR Part 11, Electronic Records; Electronic SignaturesScope and in particular Sections 11.50, 11.70, 11.100, and 11.200. No general obligation arises solely from the use of a registration. Reviewed on 14.10.2026.
Sources checked: .
How we can support you
Daniel Herrmann Consulting combines professional assessment with hands-on work on the specific system. During the first meeting, we clarify your intended use, existing documentation, and the next most appropriate action step.
- 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.

