System Engineering Support

Product: iBMU – Battery Management Unit for German OEM

Scope: System Engineering support during development (SYS.1, SYS.2, and SYS.3).

Main Responsibilities in the Project:

  • CSR inspection: Supported System Engineer Lead during CSR inspection. Introduced stages of the analysis, proposed distribution of Customer Specific Requirements among development teams (assignments). Proposed metrics and prepared JIRA dashboards for monitoring progress. Suggested various ways forward with pros and cons in situations of weak progress and engagement.
  • Analyzed the CSR assigned to the System team based on the current stage of requirements.
  • CR Implementation: Took over the implementation of CR into the Requirements DB. Developed a CR Implementation Checklist that enabled sharing and delegating work to new engineers in the team. Helped communicate status throughout stages and completion rates. The checklist unified implementation over 2 years and helped discover corner cases early. Led to the creation of two other checklists: CR Incoming Inspection & CR Baseline Checklist.
  • Supported Configuration Management during the introduction of new attributes related to HW and SW versions. Executed the transition from old to New Variant Handling (NVH) in Requirement Data Base for SYS.1, SYS.2, and SYS.3.
  • Analyzed the diagnostic state of features related to heat management from a broad perspective, including freeze frames, countermeasures, and generic diagnostics requirements.
  • Maintained tooling for monitoring traceability of customer requirements (updated filters, added filter criteria to existing filters, and created new ones).
  • Prepared OnePagers for several system features for new colleagues in the System Team and other teams. Prepared technical descriptions of System Functions according to Customer guidelines for customer diagnostics service employees.
  • TPM: Updated Technical Product Description along with new SW and HW Versions.
  • Compared requirements regarding HW versions. Examined requirements versus agreements at the Management Level. Conducted a deep dive into the history of requirements from 2018 to 2022.Described current process practices within the scope of SYS.1, SYS.2, and SYS.3.

What was executed or delivered within the project:

  • Direct changes in Requirements Data Base (Jama).
  • Confluence content, flows, charts, and BPMN, SysML, and UML diagrams.
  • Numerous lists, descriptions, and reviews saved as xlsx, docx, and pptx files.
  • JIRA issues and dashboards.