The requirements have been assessed. Now the question is whether an existing product or variant fulfills them and where evidence is missing.
Scattered product knowledge
Features live in data sheets, network folders, and the heads of individual colleagues.
Variants that are hard to compare
Variants are documented differently. A direct comparison per requirement is often manual work.
Dependence on experts
Which solution fits depends on the knowledge of individual specialists. If that person is unavailable, the inquiry waits.
GUIDED WORKFLOW
Select a step. The matrix shows every cell with text and symbol, not just color. A cell opens requirement, product evidence, and assessment side by side.
INPUT
{{ cur.eingabe }}
SUPPORT FROM DECOTA
{{ cur.decota }}
YOUR TEAM’S ACTION
{{ cur.team }}
RESULT
{{ cur.ergebnis }}
CONFIGURE-TO-ORDER
Variants that fit in principle are selected from the portfolio based on the requirements. Rule-based configuration, pricing, and bills of materials remain in your existing systems.
SCOPE
If a requirement remains uncovered, it becomes a development question. That clarification is a separate application with its own workflow.
Clarify development needs →WORK RESULT
Your team sees per variant which requirements are covered, where deviations exist, and which evidence is still missing. The result can be reused in the inquiry, in development, and for the next similar requirement.
VARIANT ASSESSMENT · PACKAGING LINE NORTH
ILLUSTRATIVE EXAMPLEVariant B, revision 4
Candidate, confirmed by expertsCovered: R-024 throughput, R-027 temperature · Evidence open: R-033 format change, request measurement report · Owner: application engineering
Variant A, revision 3
Deviation in throughputCovered: R-027, R-033 · Deviation: R-024, 100 instead of 120 units per minute · Can be continued as a development question
Variant C, revision 1
DeferredDeviation: R-027 temperature · Evidence open: R-024 performance data not on record
BENEFITS
BEFORE
Data sheets and product versions are gathered anew for every inquiry.
AFTER
Features sit next to the requirement with version and source.
Metric: time to an expert-reviewed variant selection
BEFORE
The decision for a variant is hard to justify after the fact.
AFTER
Per requirement, it is visible which evidence was used and how it was assessed.
Metric: unresolved product evidence
BEFORE
Missing coverage often surfaces only during detailed planning.
AFTER
Deviations and open evidence appear in the matrix before the commitment.
Metric: gaps known before the commitment
Your potential time savings
Run your own scenario with your own assumptions in the ROI calculator.
WHAT COMES NEXT
A deviation such as the one for variant A becomes a development question with assembly, owner, and open effort.
To the application →BEFORE THIS
The requirements for the comparison come from the jointly assessed inquiry with source and ownership.
To the application →No. DECOTA narrows down existing products and variants based on the requirements. Rule-based configuration, pricing, and bills of materials remain in your systems.
DECOTA draws on the product information and documented product revisions you have stored. Attributes remain linked to their source. If a property is not sufficiently substantiated, the evidence stays open. Your specialists then determine whether information is missing or an actual technical deviation exists.
The comparison shows which requirements are covered by the information on hand, where deviations exist, and which evidence is missing. Your specialists review the results against the underlying sources. What governs the selection is the confirmed suitability of the specific product revision.
Bring one requirement and two variants. We show the comparison with your documents or with prepared sample data.
Book a demo