Job Description Baselining Activity (Baselining) Creation of the Initial Baseline: This baseline represents the initial state of all configurable elements, including specifications, drawings, hardware components, software, technical documentation, etc. Change Management: Changes can be proposed at any time and can concern any element of the project, such as a design change, a software update, a component change, etc. Comparison with the Initial Baseline: At each step of the baselining process, changes are compared to the initial baseline to evaluate their impact and their conformity to the project specifications and requirements. Updating the Baseline: When a change is approved and validated, it is incorporated into the next baseline to create a new reference. Through this process, the baseline evolves continuously throughout the project. Traceability and Consistency: The baseline serves as the reference for tracking changes applied to components. It guarantees traceability, meaning the ability to follow the history of changes over time, and ensures consistency between the different parts of the project. Verification and Audit: Configuration management, including the creation of baselines, is subject to periodic verification and audit to ensure its compliance with standards, regulations, and project requirements. 2. Change Management Activity: Identifying the Change Request: The process begins with identifying a change request, originating, for example, from the software development team, users who have encountered a problem with their vehicle, or a regulatory compliance audit. Change Request Evaluation: Once identified, the request is evaluated according to several criteria: its relevance, its impact on the components and systems concerned, and the criticality of the associated risks. This initial analysis determines whether the request is admissible and can be submitted for approval. Change Proposal Creation: If the request is deemed relevant, a proposed technical solution is developed. This must include detailed information on the nature of the modification, its objective, the configurable parameters impacted, and the risks associated with its implementation. Review and Approval: The change proposal is reviewed and evaluated by a decision committee. The requester presents the solution to experts who analyze its feasibility, relevance, and impacts. Change Implementation: Once approved, the change can be implemented. In the case of an electronic control unit (ECU), this may involve modifying the embedded software code, the electronic microcomponent, or updating the calibration or configuration files. Tests and verification:After implementation, regression tests are performed to verify that the change has been correctly integrated, that it has not generated any new malfunctions, and that it meets the project requirements. Validation: Following successful testing and verification, the change is validated to confirm that it meets the project needs and can be integrated into the overall configuration. Documentation: All steps of the change management process (requests, proposals, approvals, tests, verifications, and validations) are fully documented to ensure complete traceability.

Desired Candidate Profile

Industrial engineering degree (or equivalent) Experience: 6 months - 1 year in the automotive sector Mechanical knowledge: Solid foundation in mechanical and production engineering, strength of materials, Machinery Directive, welded assemblies Technical English