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.
Cycling & e-mobility requirements analysis
A battery pack spec, a charging/BMS spec, and a motor controller spec are usually written by three different suppliers, each internally consistent, each reviewed on its own. Wyzer Detective checks them as one integrated specification, catching the cross-supplier contradiction a single-document review structurally cannot.
Applied to the cycling requirements you already write, in the review step you already run.
A battery pack spec, a motor controller spec, and a charging/BMS spec are usually written by three different suppliers. Wyzer checks all three together for the contradictory thermal-cutoff or current threshold a single-document review won't catch. That is the defect class behind recent battery-fire recalls.
Flags safety requirements that are present but carry no measurable acceptance value: pedal-assist cutoff speed, structural fatigue limits, braking distance. A type-approval test plan has nothing to work from.
Checks a frameset submission package against the UCI's structural, dimensional, and material requirements for the gap an approval lab finds during testing, not before submission.
Consumer bike programmes assemble from dozens of component suppliers: motor, battery, brakes, frame. Wyzer checks each supplier's spec against the platform-level integration spec it has to fit.
Wyzer Detective doesn’t replace the process. It checks the requirement set the process depends on.
A mid-volume e-bike programme integrates a battery pack spec from one supplier and a charging/BMS spec from another. Both are internally consistent, and both passed their own supplier review. The battery spec sets a hard thermal cutoff at 60°C. The charging spec assumes a 65°C ceiling before it throttles current. Neither supplier's reviewer ever sees the other's document. Wyzer Detective reads both together at every revision, because that five-degree disagreement is the kind that ends up in a fire report rather than a review comment.
The example above illustrates the class of defect Wyzer Detective catches. It is not a specific customer engagement.
Yes. That's the primary cross-supplier conflict class Wyzer is built to catch: contradictory thresholds between a battery pack spec and a charging/BMS spec written by different suppliers.
Wyzer checks the requirement set behind a submission (structural, dimensional, and material requirements) for internal contradictions and gaps before it goes to the approval lab. It doesn't replace UCI's own testing process.
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