System Architecture Leader_CoAMS_HMI

The System Architecture Leader defines the technical response system* at optimum quality, cost, lead time, and diversity, responding to regulatory conflicts, the needs expressed by brands, and service requirements.

He ensures the design and validation of the characteristics and functions of its system in a range cross-functional vision, open to series evolutions, in

responsibilities exercised

He ensures compliance with the "Design and Validate Systems" process within his system’s scope by ensuring that expectations and deliverables at milestones are met to ensure safe design.

*Examples of systems: Multimedia system, ADAS Parking system, access system and vehicle protection

Outside the project cycle / in a transversal way

• As a technical transversal manager, he functionally coordinates the network of actors contributing to his system. (System Function Specialist/Engineer, System Development Specialists/Engineers, System Engineering Drivers, Component Design Engineers/Drivers, Electrical Architect/System Electronics, Dependability Engineer)
• He identifies, formalizes, negotiates, and contracts with the stakeholders.

Activities significant

• (service, regulations, factory, logistics, General Product Safety,
• Operational Safety, ...), all the requirements applicable to its system,
• for the purpose of drafting the System’s specifications (and the file
• system architecture- then ensures that they have been taken into account in
• the development of its generic system

• It participates in upstream studies to identify the impacts of innovations on its system and ensures technological monitoring within its scope to prepare for future developments.

• He is responsible for maintaining an MBSE model (system modeling) and a variation of the requirements at his system level.

Sheet

• He structures his System scope, creating operational, functional, and organic architectures.
• He defines and implements the validation strategy and plan

• He is responsible for the production safety files on each developed variant,

• He shares his system roadmap and variants within the Alliance to maximize opportunities.

In project mode:

• Together with all system stakeholders, he is responsible for deploying the technical definition of his system over all phases of the life cycle and on all projects, with a quality-cost/delivery (QCDP) objective and in response to the technical definition of the vehicle.

• It contracts, in the context of the project, the specific requirements inherent to the needs of the project, integrates innovations and commits to the safe design of its system
• He participates in the design reviews of his system (System Design Review) and in project meetings that require arbitration if necessary.

• He leads the resolution of problems and ensures capitalization within his scope.

• Its activity is controlled by the provision of quality-level deliverables,
• cost, deadlines, expected services.
• Its deliverables are defined in the process "Design and validate the
• systems', in particular:

• the system modeling of its system,
• defining the need and requirements, functional architecture and software and control requirements,

Autonomy and latitude of action

• -   the configuration management of its system
• He is autonomous in structuring and organizing his System scope,
• (system functions under his responsibility, organization of the system team,
• validation strategy) and in the creation of new variants, in accordance with
• Engineering Managers/Department Heads to finance the charge entry.
• He proposes and validates to his director his roadmap for the years to come,
• and he is guarantor of it.
• He advances his profession: He capitalizes and is responsible for improvement, of the update and deployment of the system standard, business rules, processes,
• tools on the system perimeter.
• Internal contacts
• -   Daily interactions/animation (with the) design actors
• Systems, software, and parts for designing and validating the system and its

Main

variants (construction of functional and organic architectures of the

system, project contracting)

Labour relations

He works closely with:

• The stakeholders of the System to capture and prioritize needs on its system, including security, regulations, and services

• The group’s other System Architecture Leaders to contribute to shared and optimized features

-   The actors of innovation and the sector Expertise to build