Join Auros as we lead a discussion exploring key questions and answers around automotive requirements, including:

• What are state of the art requirements engineering for Tier 1s?
• How can AI be used and integrity maintained in the process?
• How can requirements validation be seamlessly automated?
• How does the new requirements management lead to more intelligent responses?

Recognizing The Scope & Associated Challenges

Tier 1 suppliers operate at the nexus of complex product development and regulatory expectations. Unlike OEMs who author requirements, Tier 1s are recipients and implementers, which translate volumes of external specifications into internal procedures, digital artifacts, and quality checks. However, these requirements come from multiple directions:

• OEM customers each issue unique and detailed specifications
• Regulatory bodies (e.g., NHTSA, EPA, EU Commission) enforce regional or global compliance standards
• Standards organizations (e.g., SAE, ISO, ASTM) issue continuously evolving industry norms

This creates a high-cadence, high-volume inflow of requirements. But today’s methods are often based on disconnected documents, spreadsheets, and tribal knowledge, that force engineering teams to manually reconcile requirements with in-progress designs and work instructions. 

Assessing The Results:

• Duplicate and conflicting interpretations of similar requirements across programs or teams
• Missed or outdated requirements in design, test, or manufacturing phases
• Inefficient audits and handovers, with poor traceability back to authoritative sources
• Substantial rework when requirements change mid-program

These inefficiencies compound risk including quality escapes and delays to lost business due to failed customer audits or unmet compliance conditions.

Implementing The Solutions:

What Tier 1s need is not just better storage of requirements, but a structured and scalable way to:

• Ingest static requirements from multiple sources
  Convert them into modular, traceable models that can be reused across products and programs
• Dynamically provision these models into tools and workflows (e.g., CAD, PLM, MES)
• Track conformance in real time and adapt as requirements evolve