Gasoline Engine Controls Development SME

TheGasoline Engine Controls Development Engineeris responsible for developing new features and enhancing existing algorithms. This role involves working closely with a cross-functional team and utilizing various tools (vehicle, HIL, dyno, virtual environments, rapid prototyping) through the V-model software development process to ensure the quality and robustness of production algorithms.

The controls engineer will interface with systems and calibration teams to fully understand requirements, develop implementation strategies, assess compliance and robustness, ensure ease of calibration, and document impacts against regulatory requirements. Responsibilities include implementing designs efficiently and validating them against requirements in both virtual and physical environments throughout the production process. The controls engineer is also expected to provide technical guidance, training, and act as an expert in their field of specialization.

Controls algorithm development typically begins as an advanced effort but must ultimately meet program timelines and conform to high-level functional requirements.

The successful candidate will ensure projects remain on track by developing plans, tracking progress, and presenting technical reports to management and project chiefs. They will also actively participate in decision-making regarding control strategy design to achieve functional objectives.

The candidate willbe responsible fordeveloping andimplementinga set ofcontrolsfeatures, controlling determined actuators, reading values fromsensorsor estimatingengineering quantities,in eachphysical architecture.

Specific Responsibilities include but are not limited to:

• Reading, understanding and approval of the requirements that are defined in the CFTS (Controls Function Technical Specification)documents defined by the Controls Features team.

• Development of the architecture and definition of the interfaces of the Software Components (SWC).

• Creation of interface files(arxml)that are compliant with theAutosarspecifications.

• Integration of theAutosarcomposition files, making sure that there are no unconnected interface ports across the Software Components (SWC).

• Analysis of the Controller Area Network (CAN) Database Communication files (DBC), toidentifyand implement any new messages and signals received by or sent from the Engine Control Unit (ECU) to the other nodes.

• Analysis and implementation of the interfaces related to the On-Board Diagnostics (OBD) and Function Inhibition Identifiers (FIDs) that are needed to exchange information across the Engine Controls SWCs.
• Analysis and implementation of the interfaces related to Data Identifiers (DIDs) and Legislative Diagnostics Identifiers (PIDs) to be accessed through a scan tool.
• Analysis and implementation of the interfaces that are needed to store information into Non-Volatile Random Access Memory (NVRAM).

• Definition of the Variant Management implementationthatisneeded to turn on or off a determined feature/functionality,basedon theprogram/engine/vehicleit isappliedto.Thisistooptimizethe resources (CPU bandwidth, RAM, ROM usage) based on the build target.

• Definition of the implementation requirements in the CCDD (CenterofExcellenceControls Design Document).

• Design and Documentation ofControls Algorithms,harmonized across different platforms and architecture variants to drive scalable and common solutions whenever possible.

• Creation of the linksamongthe high-level requirements in the CFTS,the implementation requirements in theCCDDand the implementation model.

• Model In the Loop (MIL)reports generation.

• Automatic codeandAutosarRunTimeEnvironment (RTE)generation usinganintegration pipeline.
• Generation of local prototype software builds, to test the integration and verify the developed functionality in an embedded and integrated environment.

• Write and storethe Design Verification Plans (Controls DVP) andverify them attheHardwareInTheLoop (HIL)simulator,with report generation (DVP&R).

• Update of the artifacts needed for the generation of the ADD (Algorithm Description Document) of thecontrolsalgorithms.

• Explanation of the Controls Algorithms to the other stakeholders/customers, such as the Calibration Teams.

• Tracking ofthe features that are defined as Auxiliary Emissions Control Devices.

• Attend theRequirements Review Boardfor the review and approval of the ControlsAlgorithmchangeswith the Controls Features team and other stakeholders, including justifications of the impacts on Auxiliary Emissions Control Devices.

• Provide Controls Design Review tracking documents, to confirm that changes arecomplete andtestedaccording to theAgileDefinition of Done,and lessons learnedareacknowledged, for the final approvalbefore the implementation scheduling.

• Attendand activelyparticipatinginAgile framework recurring meetings, such as daily standups,Big Room Planning, Sprint Planning Ceremonies.