The Challenge: Increasing Complexity and the Limits of Traditional Methods

The development of highly complex technical systems is increasingly becoming a strategic challenge for companies. In the automotive industry in particular, rising and rapidly changing customer demands, technological innovation, and expanding connectivity are pushing product development into a new dimension of complexity. Today’s vehicles are no longer merely mechanical constructs—they are integral components of a broader mobility ecosystem. They interact with external infrastructure, digital services, and IoT platforms. This shift demands a fundamental rethinking of traditional development approaches.

A key issue in this context is the management of so-called emergent phenomena— system properties that do not arise from individual components but from the way those components interact. Examples include overall vehicle weight, driving dynamics, and aerodynamics. These cross-functional properties cannot be effectively managed through conventional development processes, as they span organizational boundaries and involve complex technical and economic trade-offs.

This raises the central question: How can companies ensure that their development processes manage complexity rather than be overwhelmed by it?

The Solution: New Roles to Understand the Properties of Complex Systems

A leading German automotive OEM has recognized that conventional development structures no longer meet today’s demands. The solution: redefine roles and responsibilities to enable focused management of properties (non-functional system attributes such as weight or aerodynamics) and features (customer-relevant functionalities such as driver assistance systems).

These specialized roles ensure that overarching properties and functions are managed consistently from the concept phase through to series production. This prevents conflicts of objectives, improves communication between departments, and ensures transparent control of the development process.

The New Role Structure at a Glance

The new role model includes both property and feature roles:

Property Roles: Managing Cross-Functional System Attributes

• Property Manager (PM) — has overall responsibility for the strategic management and objectives of a property, coordinates development across different departments, and ensures that commercial and technical requirements are optimally balanced.
  
• Property Responsible (PR) – Assumes operational responsibility for implementing and managing the property within a specific system context.
  
• Property Implementer (PI) – Focuses on implementing the property at the component level, ensuring technical execution.

Feature Roles: Meeting Customer Expectations

• Feature Responsible (FR) – Oversees the development and integration of a feature across all system layers.
  
• Customer Function Responsible (CFR) – Represents the customer’s perspective and defines requirements based on user needs.
  
• Technical Function Responsible (TFR) – Translates functional requirements into technical solutions and coordinates with system architects.

This clear differentiation of roles ensures seamless management, prevents organizational silos, and significantly improves cross-functional collaboration.

Transforming Systems Engineering Through Clear Ownership

The introduction of these roles fundamentally reshapes the development process. While traditional models often break down at organizational boundaries, the new roles establish true end-to-end ownership across the product lifecycle.

A concrete example is the property “overall vehicle weight.” In traditional structures, each department attempts to reduce weight independently, often leading to misaligned goals. With the new model, a dedicated Property Manager defines strategic weight targets, which are then operationalized by Property Responsibles and implemented at the component level by Property Implementers. This structure makes it possible to proactively identify and resolve conflicts between weight, safety, and cost at a strategic level.

For companies, this translates into greater efficiency, increased transparency, and lower development risk.

Properties and features are tightly integrated into the existing V-model. From early requirements engineering through architecture management and system validation, they are systematically identified, structured, and verified to meet quality and performance targets.

[um_loggedin show_lock=”yes” lock_text=”Bitte loggen Sie sich ein, um den kompletten Artikel zu lesen. “]

Strategic Competitive Advantages for the Enterprise

Implementing this systems engineering approach offers multiple benefits:

1. Better management of emergent phenomena through clearly defined ownership of cross-functional product attributes.
   
   
2. Increased transparency and traceability through systematic tracking of features and properties throughout the development process.
   
   
3. Optimized interdisciplinary collaboration through structured responsibilities that reduce friction between teams.
   
   
4. Reduce development risk by addressing conflicts early and ensuring that goals are aligned.
   
   
5. Sustainable competitive advantage through consistent, scalable development strategies in an increasingly complex market.
   
   

Conclusion: Shaping the Future of Systems Engineering

As complexity continues to increase, it becomes essential to challenge and evolve traditional development approaches. Introducing specialized roles for Properties and Features is a key step in aligning technical excellence with organizational agility.

Companies that embrace this transformation early—by redefining roles and embedding them in their systems engineering strategy—will be best positioned to navigate digital disruption and lead future innovation.

Explore best practices in cutting-edge product development and learn how your organization can benefit from a modern systems engineering approach.

[/um_loggedin]