How does a market opportunity become a released, mass-produced product?
Customer requirements, specifications, design, simulation, and verification reside in different systems. A lack of integration, duplicate components, and delayed clarification hinder well-informed development decisions.
Connecting requirements, development knowledge, components, tests and changes across the entire product lifecycle.
01 · Product Planning & Strategy
Initial situation: Customer needs, lost sales, service problems, and market observations are often considered separately. This leaves it unclear which product development promises the greatest customer benefit and economic contribution.
The AIDA solution: AIDA condenses this information into evaluated product opportunities and prepares decisions for the product roadmap.
Identify recurring customer needs from CRM, inquiries, and service cases.
Compare needs with existing product features and available competitive information.
Use sales figures, prices, costs and complaint handling expenses for economic evaluation.
Prepare product ideas, including benefits, costs, uncertainties, and sources, as a decision-making tool.
Concrete result: A prioritized list of justified product opportunities.
The benefit: Development resources can be more effectively focused on products and functions with recognizable market potential.
02 · Requirements Engineering
Initial situation: Specifications often contain incomplete, contradictory, or difficult-to-verify requirements. Open issues are sometimes only identified during the design or testing phase.
The AIDA solution: AIDA reviews incoming specifications, structures requirements, and prepares for technical clarification with the customer.
Extract requirements from specifications, emails, and supplementary documents.
Unclear wording, contradictions, duplications and a lack of acceptance criteria are noticeable.
Compare with approved requirements, legacy projects, and stored rule sets.
Create specific questions and suggestions for clearly verifiable formulations.
Concrete result: A requirements catalog with references to sources, areas for clarification and proposed acceptance criteria.
The benefit: A more robust development basis and less rework due to misunderstandings recognized late.
03 · System design
Initial situation: Mechanical, electronic, and software engineering develop their solutions in parallel. Unresolved interfaces and contradictory assumptions often only become apparent during integration.
The AIDA solution: AIDA supports the verification of whether the planned system architecture consistently distributes the requirements across functions, components, and domains.
Link requirements with functions and intended components.
Identify unassigned requirements and incompletely described interfaces.
Highlight contradictions between mechanical, electrical, and software interface descriptions.
Provide known error patterns and previous architectural decisions for design reviews.
Concrete result: A prepared architecture review with open interfaces, dependencies and clarification tasks.
The benefit: Identifying integration risks earlier and improving collaboration between development disciplines.
04 · Domain Design Mechanics
Initial situation: Proven components, previous calculations and experience in manufacturing and quality are available, but cannot be reliably found in new designs.
The AIDA solution: AIDA searches for suitable existing solutions for a design task and compiles their operating conditions.
Research existing parts and assemblies based on technical characteristics, materials, and operating conditions.
Combine related drawings, calculations, and design guidelines.
Display known manufacturing problems and quality deviations from proposed solutions.
Highlight the differences to the new use case and the necessary technical tests.
Concrete result: A reasoned selection of reusable solutions, including their limitations.
The benefits: saving development time, utilizing proven knowledge and avoiding unnecessary redesigns.
Geometric similarity searches can also be performed via connected CAD/PDM functions.
05 · Domain Design Electrical/Electronics
Initial situation: A technically suitable electronic component can become a project risk due to supply bottlenecks, product discontinuation, or price increases. Replacement components require time-consuming comparisons.
The AIDA solution: AIDA evaluates the component selection based on technical and procurement-related information and prepares alternative checks.
Compare bills of materials with datasheets, inventory levels, and current supplier information.
Prioritize critical components based on availability, life cycle, and procurement risk.
Compare possible alternatives based on defined electrical, thermal, and mechanical criteria.
Document any differences and necessary adjustments to the circuit, layout, or software.
Concrete result: A component risk list with alternatives and specific testing requirements.
The benefit: Early consideration of supply risks and reduction of costly redesigns. Technical interchangeability is confirmed by the responsible experts.
06 · Domain Design Software
Initial situation: When software changes are made, it is often difficult to understand which requirements, interfaces, and tests are affected. Knowledge is scattered across source code, tickets, and documentation.
The AIDA solution: AIDA creates a comprehensible analysis of the affected software components and required checks for each change request.
Link change requests with documented software components, interfaces, and tickets.
Identify existing tests and known errors related to the affected functions.
Include results from builds and static analysis in the evaluation.
Suggest additional test cases and a targeted regression test scope.
Specific result: A change impact analysis with affected components, risks and test recommendations.
The benefit: Changes can be planned more thoroughly and testing gaps can be closed more effectively. Missing links are identified as uncertainties.
07 · Modeling & Simulation
Initial situation: Previous simulations, model assumptions, and test bench results are difficult to compare. New calculations are sometimes performed even though usable results are already available.
The AIDA solution: AIDA supports the selection of suitable simulation cases and the traceable evaluation of their results.
Research similar simulations with model status, boundary conditions, and results.
Compile load cases and target values from requirements for simulation planning.
Prepare variant comparisons and calculation orders for connected tools.
Compare results with target values and measurement data, and highlight deviations.
Concrete result: A structured evaluation of variants with assumptions, goal achievement and open questions.
The benefit: To make better use of existing calculations and to translate simulation results into development decisions more quickly.
The calculation is performed in the respective simulation tool.
08 · Integration, Verification, Validation
Initial situation: Before a product can be released, it must be clarified whether all relevant requirements have been sufficiently checked and the evidence has been assigned to the correct product status.
The AIDA solution: AIDA combines requirements, test results, open errors and documentation statuses into a release overview.
Compare requirements with test cases and existing results.
Identify missing, failed, or outdated evidence (due to changes).
Check the associated hardware, software, and document versions.
Prepare any outstanding deviations and missing documents for the approval committee.
Concrete result: A verification matrix with transparent release status and specific remaining tasks.
The benefit: Less manual effort for documentation and a more informed approval decision by those responsible.
09 · Industrialization & Purchasing
Initial situation: A released development status does not yet mean that materials, manufacturing, suppliers and testing processes are ready for series production.
The AIDA solution: AIDA assesses the launch status of a product across all participating areas and reveals missing prerequisites.
Check the transition from design to manufacturing bill of materials for open assignments.
Combine material availability, supplier status, and initial sample approvals.
Identify missing work plans, test documentation, and open measures from the process FMEA.
Prioritize startup-critical tasks according to their impact on deadlines and dependencies.
Concrete result: An overview of the series launch, including bottlenecks, responsible parties, and next steps.
The benefit: Eliminating start-up obstacles earlier and better coordinating development, purchasing, production and quality.
10 · Series & Change Management
Initial situation: A technical change often affects multiple products, inventory levels, open orders, and units already delivered. The consequences can only be assessed through cross-departmental research.
The AIDA solution: AIDA creates a structured impact assessment for a change request and prepares the changeover.
Identify affected parts, assemblies, variants and documents regarding proof of use.
Include inventory levels, open orders, and purchase orders.
Link relevant complaints and field failures to the reason for the change.
Compare conversion scenarios including cost implications, deadlines, and necessary measures.
Concrete result: A decision proposal outlining the scope of the affected area and a proposed conversion plan.
The benefit: To introduce changes in a more controlled manner and to reduce residual stocks and contradictory product levels.
11 · Platform & Modular Planning
Initial situation: Product families often grow in a customer-driven way. This results in different solutions for similar functions, even though shared modules would be ideal.
The AIDA solution: AIDA identifies potential for shared modules across multiple product families and prepares their economic evaluation.
Compare customer requirements, features, and bills of materials for different variants.
Identify recurring functional groups and existing technical commonalities.
Evaluate standardization potential based on sales, costs, and customer relevance.
Demonstrate the impact of shared modules on interfaces and configuration rules.
Concrete result: A proposal for the further development of the modular system with prioritized modules and justified exceptions.
The benefit: To derive future products faster and combine customer-specific diversity with an economical platform.
12 · Complexity Management
Initial situation: Similar parts, duplicate master data and rarely used special variants cause effort in purchasing, warehousing, manufacturing and documentation.
The AIDA solution: AIDA examines the existing parts landscape and proposes specific candidates for standardization or phase-out.
Group similar parts based on characteristics, classification, and use.
Mark suspected duplicates and incomplete master data.
Consider usage frequency, inventory levels, and available process cost data.
Compile a list of cleanup candidates, including affected products and required tests.
Concrete result: A prioritized list of clean-up items with economic justification and implementation requirements.
The benefit: To selectively reduce existing diversity and lower the ongoing effort per part or variant.
13 · Project, Knowledge, Governance
Initial situation: Project reports show deadlines and activities, while the actual maturity of the development results remains difficult to discern. As a result, missing decisions or evidence are noticed late.
The AIDA solution: AIDA prepares the project status from the underlying work results and supports the preparation of milestone decisions.
Compare milestones with required results, approvals and open tasks.
Evaluate logs and tickets for outstanding decisions and dependencies.
Compare reported progress with documented results.
Create gate documentation including sources, risks, responsible parties, and decision-making requirements.
Concrete result: A verifiable project status with concrete action requirements for project management and steering committee.
The benefit: Less effort for status reports and earlier visibility of maturity level and deadline problems.
Find components and verify their reusability
Before assigning a new part number, research existing components based on function, dimensions, material, and operating conditions. ERP, PLM, PDM, and document information provide candidates with technical matches, deviations, and open verification points.
The designer confirms the technical suitability. If a new system is required, the justification and approval are documented. Missing data does not count as proof of suitability. This ensures that decisions and approved applications can be reused for later projects.
Data, systems and protected development knowledge
PLM/PDM, requirements management, CAD/ECAD, ERP, MES/CAQ, DMS/Wiki, CRM, tickets and connected simulation and testing tools.
Technical assessments, component suitability, and approvals remain with the responsible experts. Simulations are performed using integrated specialist tools. Proposals indicate sources, versions, release statuses, and missing data. The operating model and permissions are defined jointly; on-premise is a possible basis for protected development knowledge.
A clearly defined entry point
The requirements review and clarification assistant is suitable as a first pilot project: it examines existing specifications for inconsistencies, missing acceptance criteria, and open customer questions. Results are then reviewed by experts and compared with current working methods.
Clarification time for requirements; reuse rate; new part numbers per project; completeness of the verification matrix; open risks and tasks at gate.