Audit-ready by design
Electronic signatures, immutable execution records, and traceability enforcement are native. Regulated programs do not have to bolt compliance onto generic QA tools.
OpenText • Application lifecycle management
Application Quality Management is the regulated QA product carrying the Quality Center and ALM lineage into modern packaging.
Merito keeps the proven audit posture of Application Quality Management intact, migrating Quality Center test, defect and execution history and configuring the regulated workflow your auditors expect.
What it is
Most customers still know OpenText Application Quality Management (AQM) as HPE ALM, and before that as Quality Center. It is the regulated QA product, with test case libraries, requirement traceability, defect workflows, execution evidence, and 21 CFR Part 11 compliance patterns that survive an FDA or auditor review. Life sciences, financial services, government, and defense programs keep AQM specifically because the audit posture is proven.
AQM's closest modern alternative in the OpenText catalog is Core Software Delivery Platform, and for unregulated programs Core SDP could be the right upgrade path. For regulated programs, the conservative call is often to stay on AQM until the regulated-workflow coverage in Core SDP matches AQM's depth. Merito's engagement clarifies which path fits the customer's compliance profile.
The implementation work on AQM is mostly about workflow rigor and defect lifecycle rules, traceability enforcement, electronic signatures where required, and evidence export that survives an audit. The product configuration enforces the process; the process design is where Merito adds value.
Ideal use cases
What it is best at
Electronic signatures, immutable execution records, and traceability enforcement are native. Regulated programs do not have to bolt compliance onto generic QA tools.
The Quality Center / ALM lineage is deployed across pharma, banking, and defense programs globally. The audit-acceptance posture is known to regulators.
AQM enforces defect lifecycles and requirement traceability that regulated programs cannot skip. The rigor is the product.
Core capabilities
Test case libraries, plans, runs, and bidirectional requirement traceability.
Test case and test plan libraries
Hierarchical test libraries with versioning and reuse across releases.
Requirement and defect traceability
Bi-directional links from requirements through tests to runs to defects.
Coverage analysis
Coverage reports on requirements, risk, and business processes.
Execution records, electronic signatures, and audit-ready evidence export.
Electronic signatures
21 CFR Part 11 compliant signatures on test execution and defect closure.
Immutable execution records
Execution history with full evidence trail for auditor review.
Evidence export
Regulated evidence packages for FDA, EMA, and financial auditors.
Defect lifecycles, custom workflows, and cross-team governance.
Custom workflows
Defect and test lifecycle customization to match regulated process requirements.
Multi-project and multi-team structures
Shared libraries and cross-project reporting for enterprise QA organizations.
Business Process Testing
Reusable business-component libraries for regression across releases.
Where it fits in the stack
Deployment and implementation
Licensing and packaging
AQM standard
Test management, requirement traceability, defect workflows, and execution evidence.
Best for: Regulated QA programs with formal validation requirements.
AQM with Business Process Testing
Standard plus Business Process Testing for reusable regression libraries.
Best for: Large regulated programs with long-running regression scope.
Merito services
Pick the engagement that matches where you are in the lifecycle.
Workflow design, electronic signature configuration, evidence export, and regulated-audit preparation.
Explore serviceQuality Center and HPE ALM to OpenText Application Quality Management transitions without losing audit history.
Explore serviceNamed engineer, priority SLAs, and release-time coverage for AQM in regulated production.
Explore serviceLong-term run support for AQM including workflow evolution as regulations change.
Explore serviceRole-based training for test authors, validators, defect managers, and compliance reviewers.
Explore serviceAQM licensing
Have your regulated scope ready, whether 21 CFR Part 11, SOX or DORA, along with user counts by role and any Quality Center history that has to carry over.
Merito point of view
For unregulated portfolios, moving off AQM onto Core Software Delivery Platform can make sense, and agile teams may move to Core SDP or a third-party test management tool. Regulated portfolios should almost always stay on AQM until the regulated-workflow coverage in the alternative matches AQM's depth. The cost of a failed audit is larger than the cost of staying on a less modern product.
For hybrid programs (some regulated, some not), Merito usually recommends AQM for the regulated footprint and Core SDP or Software Delivery Management for the non-regulated footprint, with integration between the two. That is better than forcing one product to cover both and compromising on either regulated depth or agile flow.
Quality Center to AQM transitions are primarily a modernization of the hosting and licensing shape rather than a re-platform. The test and defect history is preserved; the workflow configuration carries over. Expect a three-to-five-month project, not a year.
What buyers usually underestimate
Related from Merito
Related solutions
Related services
Related products
Frequently Asked Questions
Consultation request
Share your regulated scope (21 CFR Part 11, SOX, DORA, or equivalent) and current QA posture. A Merito regulated QA specialist follows up within one business day.
Audit-first configuration
The regulated workflow is designed first, and AQM is configured to enforce it. The audit is the outcome, not a retrofit.
History preserved
Merito's migration approach preserves test, defect, and execution history so the audit trail is continuous.
Next step
A Merito AQM engagement starts with the regulated workflow, signature rules, and evidence export requirements. Product configuration follows the workflow, not the other way around.
Proof and resources
Upgrade your OpenText ALM or Quality Center faster and smarter. See how Merito’s automation-driven approach delivers multi-version upgrades in hours with zero data loss, no downtime, and full compliance.
OpenText AQM vs Tricentis qTest is a decision on QA governance and delivery model. This guide helps enterprises choose based on risk, traceability, and scalable SDLC outcomes.