Simple, fast UI
Built for review, not data entry. Bulk actions, queues that surface what needs your attention.
Requirements Manager extracts requirements from raw specifications and classifies every one at domain-expert level. The kickstart to the product lifecycle.
Built for review, not data entry. Bulk actions, queues that surface what needs your attention.
Each classification ships with plain-language reasoning, citing the prior requirements behind every decision.
Jump from any requirement back to its source document, page and section. No hunting through PDFs.
No setup needed to start extracting. Configure ontology mappings later, only if you need them.
ReqIF, Word, PDF, Excel. Structured or unstructured, no preprocessing required.
Move classified requirements into PLM, ALM, or a plain spreadsheet for downstream teams.
Compare thousands of incoming requirements against prior programs. SPREAD separates what is covered, what is new, what is only partial and what conflicts with known engineering reality.
Classifying a requirement as covered, partial, conflicting or new is subjective work. Senior engineers disagree on borderline cases, especially the line between partial and conflicting. So we measure SPREAD against expert agreement itself, the real human ceiling for this task.
SPREAD agrees with domain experts as often as experts agree with each other. We measure parity, not absolute accuracy, because subjective boundaries cannot be checked against an imagined single truth.
Stratified benchmark across automotive safety, performance and interface domains. Expert labels adjudicated to consensus.
The boundary between partial and conflicting is genuinely ambiguous. SPREAD surfaces those cases for review with calibrated confidence instead of pretending the boundary is clean.
Instead of another isolated spreadsheet row, each requirement is attached to your engineering data: affected systems, implemented functions, variants, standards, tests and previous programs.
Ingests PDFs, RfQs, standards and specification documents with no manual cleanup or preprocessing.
Extracts requirement candidates, classifies engineering meaning and preserves source traceability for review.
Attaches every requirement to your engineering ontology: functions, components, tests, variants and prior programs.
Marks each requirement as covered, partial, conflicting or new, so engineers decide before architecture and delivery work inherit the risk.
Book a 20-minute walkthrough.
We will map a real requirements workflow and show where SPREAD connects to your product ontology.