All are visible continuously. Current tooling surfaces them at the gate, when the cost of fixing them is highest.
Engineers manually trace what needs retesting, if they trace it at all. Gaps surface at CDR. By then rework is measured in schedule weeks.
No continuous view of approved vs. open artefacts or traceability coverage. CDR readiness is a manually compiled snapshot that is already out of date when it reaches the board.
RTMs in spreadsheets or DOORS exports are static the moment they are generated. The record presented at review reflects the programme as it stood when someone last exported it.
Each contractor holds their own DOORS module. Nobody has a consolidated view of programme state across the supply chain. Integration gaps surface at system-level review, when the cost of fixing them is at its highest.
Under schedule pressure, approvals go through without test evidence attached. The deficiency stays hidden until a SQEP assessor or gate reviewer checks the link manually. By that point it is already on the critical path.
A CR is approved and the source artefact is updated. The downstream tests, design outputs, and evidence documents that now need re-verification go unidentified. Engineers find out when they check manually, or they miss it entirely.
Every change propagates immediately to connected artefacts and the gate readiness score.
Every artefact is a node. Every dependency, verification link, and evidence chain is an edge. State changes propagate in real time. No manual refresh. No stale snapshots.
Select any node and describe a proposed change. MAETRIX returns severity-coded findings for every affected downstream artefact before any edit is made to the programme record.
Gap Analysis, Requirement Quality, DEF STAN / JSP clause mapping, and GSN assurance case generation. Each covers the full programme. Results on first run.
Approved artefact coverage, open gaps, safety nodes without evidence, and suspect links factored into a single score against your target gate. Updated on every state change.
When an upstream artefact changes state, every verification and evidence link downstream is immediately flagged suspect. Nothing silently passes a gate on stale coverage.
Every approval, rejection, and edit is timestamped and attributed. Gate reviewers and auditors see exactly who changed what, and when, without leaving the graph.
Nodes and edges span organisational boundaries. Prime, sub-contractors, and IPTs see the same live state without sharing systems or duplicating data across programmes.
No artefact can be self-approved. MAETRIX enforces a second-person rule at node and gate level, with reviewer identity captured in the audit record.
Generate a full RTM from the living intelligence layer at any point in the programme lifecycle. Columns, coverage, and gap flags are computed from current state, always reflecting the programme as it stands now.
Connect your CI pipeline in one step. Every test run updates node health on the programme graph in real time. Pass, fail, partial. If something fails, downstream artefacts are flagged immediately so the team knows what is at risk before anyone has to ask.
Requirements your SQEP assessor will check. Built into the platform, enforced at system level, independent of process discipline.
The artefact creator's approval carries zero weight on their own work. A second named individual is required at system level, independent of process discipline and seniority, with identity captured in the audit record.
When a node changes, every connected link is automatically flagged suspect. Engineers must re-confirm each one against the updated content before it is trusted again. Unconfirmed links are visible to the whole team.
Moving any artefact to In Review or Approved requires a written justification. The rationale is stored in version history with a full snapshot, visible on screen and part of the permanent record.
A locked baseline is a point-in-time snapshot of the full programme graph: every node, every link, every maturity state. The evidence artefact for CDR, PDR, or SRR. Irrecoverable by design.
Once frozen, any edit to an artefact requires a raised and approved change request. Every unlock is traced to its CR reference. The record is complete from start to finish.
Every state change, approval, and rationale is cryptographically chained. When the gate comes, the record is already there. It was written as the programme ran.
Most programmes are contractually locked into DOORS. The rest of the programme state lives in spreadsheets, shared drives, and email threads. MAETRIX runs above all of it, adding the intelligence layer none of them were designed to provide.
| Capability | IBM DOORS Next | MAETRIX |
|---|---|---|
| Requirements authoring and module management | ✓ | — |
| Suspect link detection on node change | ✓ | ✓ |
| Configuration baseline snapshots | ✓ | ✓ |
| Second-person approval workflow | ✓ | ✓ |
| Live cross-programme graph with gap visualisation | — | ✓ |
| Automated change impact analysis across all downstream artefacts | — | ✓ |
| Continuously computed gate readiness score | — | ✓ |
| AI gap analysis across full programme | — | ✓ |
| DEF STAN / JSP clause mapping per requirement | — | ✓ |
| GSN assurance case generation | — | ✓ |
| Immutable audit log with cryptographic chain | — | ✓ |
MAETRIX runs on your servers. Nothing leaves your network. No cloud dependency, no third-party data processing, no egress by design.
Deployed inside your programme environment. Operates entirely within your existing security boundary with no external dependencies at runtime.
Architecture designed for IL2 and IL3 environments. Air-gap deployment available for programmes with stricter classification requirements.
Data handling, access control, and audit logging aligned to JSP 440. No third-party data processing without explicit programme approval.
No commitment. We're mapping where the problem is felt most and who we build with first.