Digital mockup deployment method

ALTEN

Digital mockup deployment method

1. Baselining activity (referencing)

Creation of the initial baseline:

• This baseline represents the initial state of all configurable elements, including specifications, plans, hardware components, software, technical documents, etc.

Change management:

• Modifications can be proposed at any time and can relate to any element of the project, such as a design change, a software update, a component change, etc.

Comparison with the initial baseline:

• At each stage of the baseline process, the changes are compared to the initial baseline in order to assess their impact and their conformity to the specifications and requirements of the project.

Baseline update:

• 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.

Workability and coherence:

• The baseline serves as the reference for tracking changes applied to components. It guarantees traceability, that is, 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 checks and audits to ensure its compliance with standards, regulations and project requirements.

2. Change Management Activity

Identification of the change request:

• The process begins with the identification of a change request, originating for example from the software development team, from users who have encountered a problem with their vehicle, or from a regulatory compliance audit.

Evaluation of the change request:

• Once identified, the request is evaluated according to several criteria: its relevance, its impact on the components and systems concerned, as well as the criticality of the associated risks. This initial analysis determines whether the request is admissible and can be submitted for approval.

Creation of the proposed change:

• If the request is deemed relevant, a technical solution proposal 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 proposed change is reviewed and evaluated by a decision committee. The requester presents the solution, and experts analyze its feasibility, relevance, and impacts.

Implementation of the change:

• Once approved, the change can be implemented. In the case of an electronic control unit (ECU), this may involve a modification of the embedded software code, the electronic microcomponent, or an update of the calibration or configuration files.