Digital Mock-up Deployment Method | Tétouan (Morocco)

Alten Maroc is defined by a deeply collaborative culture, focused on people, trust, and strong team support, with hands-on managers who guide and develop talent.
This environment is enhanced by a strong drive for innovation, encouraging creativity, initiative, and experimentation across projects.
A structured and disciplined organization ensures efficiency, rigor, and quality in engineering delivery.
Performance and ambition are part of the culture as well, supporting collective success while maintaining a positive and caring atmosphere.

"Baselining" activity (setting a reference)

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 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 stage of the baselining process, changes are compared to the initial baseline to assess their impact and compliance with project specifications and requirements.

Baseline update:

When a change is approved and validated, it is integrated into the next baseline to create a new reference. Through this process, the baseline continuously evolves throughout the project.

Traceability and consistency:

The baseline serves as the reference for tracking changes applied to components. It ensures traceability, meaning the ability to track the history of changes over time, and ensures consistency between different parts of the project.

Verification and audit:

Configuration management, including baseline creation, is subject to periodic checks and audits to ensure compliance with standards, regulations, and project requirements.

2. "Change" activity (change management)

Identification of the change request:

The process begins with identifying a change request, which could come from the software development team, users who encountered a problem with their vehicle, or a regulatory compliance audit.

Evaluation of the change request:

Once identified, the request is evaluated based on several criteria: its relevance, its impact on the affected components and systems, and the criticality of the associated risks. This initial analysis determines whether the request is acceptable and can be submitted for approval.

Creation of the change proposal:

If the request is deemed relevant, a technical solution proposal is developed. This must include detailed information about the nature of the modification, its objective, the configurable parameters affected, and the risks associated with its implementation.

Review and approval:

The change proposal is reviewed and evaluated during a decision-making committee. The requestor 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 calibration or configuration files.

Testing and verification:

After implementation, non-regression tests are carried out to verify that the change has been correctly integrated, that it has not generated new malfunctions, and that it meets project requirements.

Validation:

Following successful tests and verifications, the change is validated to confirm that it meets 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.

• Industrial Engineer degree or equivalent
• Experience: 1-4 years in the automotive sector
• Knowledge in mechanics: Solid foundation in mechanical engineering and production, strength of materials, Machine Directive, welded metal parts
• Technical English