Connected Vehicle Engineering
心を動かす会話

Function Oriented Systems Engineering

Vehicle development is no longer a chain of isolated disciplines function oriented engineering connects requirements, components and teams so complexity remains traceable as products evolve
会議のスケジューリング
ポッドキャストを聴く
-15
+15
0:00
/
0:00
Complexity compounds faster than engineering silos can absorb it
WHY THIS “FUNCTION-ORIENTED SYSTEMS ENGINEERING” CHALLENGE?
When functions, requirements and components drift apart, change becomes harder to control

Automated driving, connected services, functional safety, homologation and new cybersecurity and software-update requirements are adding pressure across automotive R&D. Engineering organizations need development processes that can manage this complexity without losing traceability from what a vehicle must do to the components and systems that make it possible

主なメリット
Engineering Around Functions Changes the Shape of Complexity

A function oriented approach reorganizes development around what the product must achieve linking requirements, reusable components and systems through a more continuous engineering mode

チェックアイコン
Trace the intent, not just the artifact

Maintain a clear path from functional requirements through components and systems as development decisions evolve

チェックアイコン
Reuse the logic. Reduce the reinvention

Structure functionality into reusable components that can support future product and service development

チェックアイコン
Put compliance inside the engineering flow

Align processes, methods and tools with A-SPICE Level >=2 requirements and growing safety, cybersecurity and software-update obligation

チェックアイコン
Let disciplines move as one system

Bring interdisciplinary teams into a shared engineering model that supports more efficient collaboration across organizational boundaries

NTTデータのサポート体制は?

01
Build the engineering backbone

Define an integrated Process, Methods and Tools approach that supports continuous systems engineering across future product and service development

Engineering Backbone
02
Connect functions to what gets built

Establish traceability from requirements and functions through reusable components and the systems in which they operate

Function-to-Component Traceability
03
Turn collaboration into an operating model

Structure multidisciplinary engineering around scaled agile planning, iterative delivery and regular feedback across teams and organizational clusters

Scaled Agile Engineering
04
Make capability part of the transformation

Train and coach engineering teams and leadership so new processes and working methods can be applied consistently across the program

Capability Building
05
Stay until the new way of working holds

We don’t stop at process definition. We coach planning, team routines, delivery criteria and improvement cycles until the operating model becomes actionable

Team-Owned Engineering Rhythm
実証済みの効果
Functions aligned. Requirements traceable. Engineering complexity brought under control
重要な結果
Transformation at the Scale of the Engineering Organization

The source demonstrates adoption at program, team and workforce level rather than isolated experimentation

チェックアイコン
Mobilize transformation capacity.

>120 consultants actively engaged

チェックアイコン
Embed new ways of working.

Around 200 employees across 13 teams coached and supported

チェックアイコン
Expand engineering capability.

~300 employees trained and onboarded in Agile ways of working

チェックアイコン
Move beyond a short-term pilot.

First transformation phase structured over 3 years

Complex products need more than more engineering — they need engineering that stays connected

Shape the dialogue that makes automotive complexity manageable→

ドラッグ