Find it in the files, not the field.
Machine-speed analysis of technical specifications. Find contradictions, gaps, and duplicates before sign-off.
Find it in the files, not the field.
Machine-speed analysis of technical specifications. Find contradictions, gaps, and duplicates before sign-off.
Aerospace requirements & certification analysis
DO-178C, ARP4754A, and DO-254 all trace forward from the same source: a requirements baseline split across system, hardware, and software levels, usually written by different teams on different suppliers’ schedules. Wyzer Detective checks that baseline as one document, catching the cross-level contradiction certification review finds late and expensively.
Applied to the aerospace requirements you already write, in the review step you already run.
Flags system requirements with no corresponding software or hardware requirement downstream, and software requirements with no traceable system-level parent. Both surface before a certification auditor finds the hole in the traceability matrix.
When a supplier baseline is integrated into the platform specification, Wyzer checks it against every other package it now sits alongside, not just the interface control document it was written to.
Requirements that pass a checklist for existence and still fail a DO-178C objective for verifiability: vague qualifiers, missing tolerances, acceptance criteria nothing can measure. Flagged before a stage-of-involvement audit.
Large platform specifications accumulate requirements re-stated with small wording differences across revisions. Wyzer finds the near-duplicates that inflate verification effort without adding coverage.
Wyzer Detective doesn’t replace the process. It checks the requirement set the process depends on.
A Level A avionics baseline with roughly 12,000 system and software requirements, integrated from four supplier-furnished packages. Each package is internally consistent, because each supplier reviewed their own. Two of them then define conflicting timing tolerances for the same shared bus message, which stays invisible until somebody reads both documents side by side. Wyzer Detective does that on the integrated baseline at every revision.
The example above illustrates the class of defect Wyzer Detective catches. It is not a specific customer engagement.
Wyzer’s findings (contradictions, gaps, ambiguity, duplicates) are the defect classes DO-178C verification objectives exist to catch. Results are delivered per requirement, ready to fold into your existing traceability matrix.
Yes. That is the primary use case. Upload the integrated ReqIF baseline and Wyzer checks it as one document, regardless of how many supplier packages fed into it.
Same day. Export a ReqIF baseline, upload it, and Sherlock returns quality scores, contradictions, and coverage gaps within minutes. No configuration, no training data, no integration project.
No. Customer data is not used to train the system and is not exposed to other customers or external models. Data is encrypted at rest.
In the EU. Wyzer's infrastructure runs in an EU region, isolated to your environment, with standard retention capped at 90 days by default.
No practical one. Sherlock has been tested to tens of thousands of requirements with no degradation in output quality: it processes specifications in parallel batches rather than reading them end to end.
No. Reviewers keep working in the requirements tool they already use. Wyzer Detective runs before or alongside the existing review, and relevant findings get applied back into that review. It's a quality-gate step, not a new system to adopt.
Credit-based pricing that scales with the number of requirements in your specification and how complex they are (plain text vs. requirements with tables or diagrams). There's no fixed per-seat licence. Get in touch for a quote sized to your specification. Searching a finished analysis with a defect or failure description (the Requirement Scan API, in beta) costs one credit per query, whatever the size of the specification.
Yes. Any ReqIF export works as the reference: a published standard, an internal template, last year's baseline, whatever you want the current spec measured against. The comparison runs requirement by requirement, not as a single aggregate score, so you can see exactly which ones fall short.
Export a ReqIF baseline and get a full Wyzer Detective analysis within minutes: quality scores, contradictions, and coverage gaps.
← Back to all industries