Edit Idea
View Ideas
Idea Date:
Idea Title:
Idea Description:
<p class="MsoNormal">Index:</p> <p class="MsoListParagraphCxSpFirst" style="text-indent: -.25in; mso-list: l4 level1 lfo20;">A. Objective</p> <p class="MsoListParagraphCxSpMiddle" style="text-indent: -.25in; mso-list: l4 level1 lfo20;">B. Priorities Supported</p> <p class="MsoListParagraphCxSpMiddle" style="text-indent: -.25in; mso-list: l4 level1 lfo20;">C. How this strategy inline with GM/Business Unit goals</p> <p class="MsoListParagraphCxSpLast" style="text-indent: -.25in; mso-list: l4 level1 lfo20;">D. Assumptions</p> <p class="MsoNormal" style="text-indent: .25in;">E. Major Milestones</p> <p class="MsoNormal">1. Key Milestones & Timeline</p> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l10 level1 lfo1; tab-stops: list .5in;">Resource Planning</li> <li class="MsoNormal" style="mso-list: l10 level1 lfo1; tab-stops: list .5in;">2024 (Actions taken):</li> <ul style="margin-top: 0in;" type="circle"> <li class="MsoNormal" style="mso-list: l10 level2 lfo1; tab-stops: list 1.0in;">SDV Leadership</li> <li class="MsoNormal" style="mso-list: l10 level2 lfo1; tab-stops: list 1.0in;">SWIL Training</li> <li class="MsoNormal" style="mso-list: l10 level2 lfo1; tab-stops: list 1.0in;">Automated Nightly Builds and demos</li> <li class="MsoNormal" style="mso-list: l10 level2 lfo1; tab-stops: list 1.0in;">MCU1, SE, and MCU3 Build Support</li> <li class="MsoNormal" style="mso-list: l10 level2 lfo1; tab-stops: list 1.0in;">SWIM organization</li> </ul> </ul> <p class="MsoListParagraphCxSpFirst" style="text-indent: -.25in; mso-list: l10 level1 lfo1; tab-stops: list .5in;">· 2025</p> <p class="MsoListParagraphCxSpLast" style="margin-left: 1.0in; mso-add-space: auto; text-indent: -.25in; mso-list: l10 level2 lfo1; tab-stops: list 1.0in;">o MCU1 & SE Build Management</p> <ul style="margin-top: 0in;" type="disc"> <ul style="margin-top: 0in;" type="circle"> <li class="MsoNormal" style="mso-list: l10 level2 lfo1; tab-stops: list 1.0in;">MCU3 Build Management:</li> </ul> </ul> <p class="MsoListParagraph" style="margin-left: 1.0in; mso-add-space: auto; text-indent: -.25in; mso-list: l10 level2 lfo1; tab-stops: list 1.0in;">o CoSIM builds</p> <p class="MsoNormal" style="margin-left: 1.0in; text-indent: -.25in; mso-list: l15 level1 lfo6; tab-stops: list 1.0in;">o 2025 Executive Build Initiatives</p> <p class="MsoNormal" style="margin-left: 1.0in; text-indent: -.25in; mso-list: l15 level1 lfo6; tab-stops: list .5in 1.0in;">o SWIM organization</p> <p class="MsoNormal">2. Responsibilities & Escalation Management</p> <p class="MsoNormal">3. Cadence MCU Builds & NATS Support</p> <p class="MsoNormal">4. Automation Activities</p> <p class="MsoNormal">5. SDV Swimlane Strategy & Complexity-Based Planning</p> <p class="MsoNormal">6. Training & Development</p> <p class="MsoNormal">7. Risk Management & Continuous Improvement</p> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l5 level1 lfo16; tab-stops: list .5in;">Potential Risks</li> <li class="MsoNormal" style="mso-list: l5 level1 lfo16; tab-stops: list .5in;">Mitigation Strategies</li> </ul> <p class="MsoNormal" style="margin-left: .25in;">F. Outcome:</p> <p class="MsoNormal"> </p> <p class="MsoNormal"> </p> <p class="MsoNormal"> </p> <p class="MsoNormal"> </p> <p class="MsoListParagraph" style="margin-left: 1.0in; mso-add-space: auto;"> </p> <p class="MsoNormal"> </p> <p class="MsoListParagraph" style="text-indent: -.25in; mso-list: l11 level1 lfo21;">A. Objective:</p> <p class="MsoNormal">Ensure VMECs smooth execution of the SDV strategy by efficiently leading SWIL resources, managing automated nightly builds, planning swimlanes, and transitioning build responsibilities for MCU3, MCU2 (SE) and MCU1 (MCU0 after May 2025) builds throughout executive initiatives, while eliminating inefficiencies in software branch management. Expand support and leadership to rest of the VMEC resources starting with CTE, CIE, NATS and SQA resources, define a overarching process and ensure quality of the final product: tested build.</p> <p class="MsoNormal"> </p> <p class="MsoListParagraph" style="text-indent: -.25in; mso-list: l11 level1 lfo21;">B. Priorities Supported:</p> <p class="MsoNormal">SDV Build Factory Workload with a focus on SWIL resources (to be rolled out to other resources as well), SDV nightly builds, Executive Initiatives (30x30, Labor Day, NYE, Valentines Day, St. Patrick’s Day, 25% PAR, 50% PAR, 65%, 90%...), MCU1/0/SE SWIL transition, CI build improvement, vECU development</p> <p class="MsoNormal"> </p> <p class="MsoListParagraph" style="text-indent: -.25in; mso-list: l11 level1 lfo21;">C. How this strategy inline with GM/Business Unit goals:</p> <p class="MsoNormal">Supporting the overall GM SDV strategy including high level PMO milestones which aims to be prepared for SDV vehicle launches (lead by L233 program) with all the tools and processes necessary ahead of the official production SDV builds.</p> <p class="MsoNormal">Supporting different levels of CoSIM and bench testing with and without real HW.</p> <p class="MsoNormal"> </p> <p class="MsoListParagraph" style="text-indent: -.25in; mso-list: l11 level1 lfo21;">D. Assumptions:</p> <p class="MsoNormal">MCU3 Architecture is new and demands its own core domain to tackle the challenges.</p> <p class="MsoNormal">NA Engine domain transition and set up the MCU3 domain.</p> <p class="MsoNormal">MCU2 (SE Devices), MCU1/0 will be lead by respective domains as part of the current SWIL structure:</p> <p class="MsoListParagraphCxSpFirst">ECU_MCU2_BE01 (BECM) - Battery Domain</p> <p class="MsoListParagraphCxSpMiddle">ECU_MCU2_TPIM_IM (DMC_R1) - Electrification Domain</p> <p class="MsoListParagraphCxSpMiddle">ECU_MCU1_AGGE_CLSS (LF) - Chassis Domain</p> <p class="MsoListParagraphCxSpMiddle">ECU_MCU1_AGGE_CLSFR (RC) - Chassis Domain</p> <p class="MsoListParagraphCxSpLast">ECU_MCU1_SED_AUTH - Chassis Domain</p> <p class="MsoNormal">MCU2/1/0 architecture/build is identical to VIP builds.</p> <p class="MsoNormal">All the SWIL resources are trained on both MCU3 and other SDV builds and new members will be trained on the same as well.</p> <p class="MsoNormal">Work priorities will be identified by SWIMs and future resource needs will be provided with the SWIMLANE and complexity metrics.</p> <p class="MsoNormal">SWILs will focus on DPLY, PA, ECU, vECU and BOOT builds for 25% PAR milestone.</p> <p class="MsoNormal">Other build types will be planned separately and SWIL activities will be planned with NATS and SWIM support.</p> <p class="MsoNormal">Automation will be covering DPLY and ECU build types with an option to investigate PA, vECU builds.</p> <p class="MsoNormal">VIP work takes priority over this project when *PRTS and other show stoppers are present and resources are shared (i.e. MCU2/1/0 shared resources).</p> <p class="MsoNormal">SDV domain is dedicated for MCU3 projects and may expand its support to other SDV builds when needed.</p> <p class="MsoNormal">Escalation path follows the regular VMEC escalation path: SWIM/EGM/Director/Executive Director.</p> <p class="MsoNormal">VMEC structure including SWIMs are established and build requests don’t directly come to the SWILs such as it is a common practice with other groups (i.e. Infrastructure). SWIM encapsulate the SWIL and CTE/CIE work and allows support groups to focus on the task at hand.</p> <p class="MsoNormal">HW is provided by HW DREs and Infrastructure group when applicable. Respective benches are shared with Infrastructure groups till 50% PAR and then VMEC will have separate benches and HW to implement/execute APP development.</p> <p class="MsoNormal"> </p> <p class="MsoListParagraphCxSpFirst" style="text-indent: -.25in; mso-list: l11 level1 lfo21;">E. Major Milestones:</p> <p class="MsoListParagraphCxSpMiddle" style="text-indent: -.25in; mso-list: l17 level1 lfo17;">1- 30x30 (5/30/2024)</p> <p class="MsoListParagraphCxSpMiddle">Initial builds are provided, content and the builds required for this milestone revised to represent the entire SDV landscape while making it feasible to complete the work. Lessons learned performed, missing components like SWIM role to be established.</p> <p class="MsoListParagraphCxSpLast" style="text-indent: -.25in; mso-list: l17 level1 lfo17;">2- Labor Day Push (9/6/2024)</p> <p class="MsoNormal" style="margin-left: .5in;">Installed Steve H. as SWIM. All SDV builds with VMEC content delivered on time.</p> <p class="MsoListParagraphCxSpFirst" style="text-indent: -.25in; mso-list: l17 level1 lfo17;">3- NYE Push (1/3/2025)</p> <p class="MsoListParagraphCxSpMiddle">EEM_EV and BECM is the focus for VMEC. VMEC builds delivered on time.</p> <p class="MsoListParagraphCxSpMiddle" style="text-indent: -.25in; mso-list: l17 level1 lfo17;">4- Valentines’ Day Push (2/14/2025)</p> <p class="MsoListParagraphCxSpMiddle">179.4p0 builds delivered to CoSIM</p> <p class="MsoListParagraphCxSpMiddle" style="text-indent: -.25in; mso-list: l17 level1 lfo17;">5- St. Patrick’s Day Push (3/21/2025)</p> <p class="MsoListParagraphCxSpMiddle">180.0p0 based ECU and CoSIM builds are delivered on time.</p> <p class="MsoListParagraphCxSpLast" style="text-indent: -.25in; mso-list: l17 level1 lfo17;">6- April Fools’ Day Push (4/1/2025)</p> <p class="MsoNormal" style="margin-left: .5in;">This initiative merged with 25% PAR support.</p> <p class="MsoListParagraphCxSpFirst" style="text-indent: -.25in; mso-list: l17 level1 lfo17;">7- 25% PAR (4/25/2025)</p> <p class="MsoListParagraphCxSpMiddle">Currently working on the MCU3 and MCU2 Builds that has VMEC content.</p> <p class="MsoListParagraphCxSpMiddle">MCU3_FARM_BDY (Steven H. / Cheng X. / Jonathan H.)</p> <p class="MsoListParagraphCxSpMiddle">MCU3_FARM_BDY_BC (Steven H. / Cheng X. / Jonathan H.)</p> <p class="MsoListParagraphCxSpMiddle">MCU3_FARM_EEM_EV (Sumit S. / Sue Z. / Jonathan H.)</p> <p class="MsoListParagraphCxSpMiddle">MCU3_FARM_VMC_EEM_BC (Steven H. / Manohar K. / Jonathan H.)</p> <p class="MsoListParagraphCxSpMiddle">MCU3_FARM_VMC_EV (Steven H. / Manohar K. / Jonathan H.)</p> <p class="MsoListParagraphCxSpMiddle">ECU_MCU2_BE01 (BECM) (Sumit S. / John J. & Gouthami K. / Bo X.)</p> <p class="MsoListParagraphCxSpMiddle">ECU_MCU2_TPIM_IM (DMC_R1) (Guru R. / Namith K. / Jim S.)</p> <p class="MsoListParagraphCxSpMiddle">ECU_MCU1_AGGE_CLSS (LF) (Renuka R / Tagore K. / David W.)</p> <p class="MsoListParagraphCxSpMiddle">ECU_MCU1_AGGE_CLSFR (RC) (Renuka R / Tagore K. / David W.)</p> <p class="MsoListParagraphCxSpMiddle">ECU_MCU1_SED_AUTH (Renuka R / Tagore K. / David W.)</p> <p class="MsoListParagraphCxSpMiddle"> </p> <p class="MsoListParagraphCxSpMiddle"> </p> <p class="MsoListParagraphCxSpMiddle" style="text-indent: -.25in; mso-list: l17 level1 lfo17;">8- 50% PAR (8/29/2025)</p> <p class="MsoListParagraphCxSpLast">TBD</p> <p class="MsoNormal"> </p> <p class="MsoNormal"> </p> <p class="MsoNormal">1. Key Milestones & Timeline</p> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l10 level1 lfo1; tab-stops: list .5in;">Resource Planning</li> </ul> <p class="MsoNormal" style="margin-left: .5in;">Start with TS (David W.) and Engine Domain SWILs and add SWILs from other domains as needed:</p> <p class="MsoNormal" style="margin-left: .5in;"> </p> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l10 level1 lfo1; tab-stops: list .5in;">2024 (Actions taken):</li> <ul style="margin-top: 0in;" type="circle"> <li class="MsoNormal" style="mso-list: l10 level2 lfo1; tab-stops: list 1.0in;">SDV Leadership:</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l10 level3 lfo1; tab-stops: list 1.5in;">SDV leadership is established after 30x30 initiative to ensure successful execution of SDV builds and consists of following team members:</li> <ul style="margin-top: 0in;" type="square"> <li class="MsoNormal" style="mso-list: l10 level4 lfo1; tab-stops: list 2.0in;">Jayden B. – SWIL EGM</li> <li class="MsoNormal" style="mso-list: l10 level4 lfo1; tab-stops: list 2.0in;">Steve H. – SWIM Leader</li> <li class="MsoNormal" style="mso-list: l10 level4 lfo1; tab-stops: list 2.0in;">David W. – SWIL TS</li> <li class="MsoNormal" style="mso-list: l10 level4 lfo1; tab-stops: list 2.0in;">Ryan B. – SWIL CM</li> <li class="MsoNormal" style="mso-list: l10 level4 lfo1; tab-stops: list 2.0in;">Jonathan H. – NATS – MCU3 responsible</li> <li class="MsoNormal" style="mso-list: l10 level4 lfo1; tab-stops: list 2.0in;">Jim S. – NATS – MCU1/SE responsible</li> </ul> <li class="MsoNormal" style="mso-list: l10 level3 lfo1; tab-stops: list 1.5in;">Leadership team meets bi-weekly on Wednesdays. Emergency meetings are scheduled asynchronously.</li> <li class="MsoNormal" style="mso-list: l10 level3 lfo1; tab-stops: list 1.5in;"> </li> </ul> <li class="MsoNormal" style="mso-list: l10 level2 lfo1; tab-stops: list 1.0in;">SWIL Training:</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l10 level3 lfo1; tab-stops: list 1.5in;">Entire NA SWIL team is trained on the MCU3 builds.</li> <ul style="margin-top: 0in;" type="square"> <li class="MsoNormal" style="mso-list: l10 level4 lfo1; tab-stops: list 2.0in;">90% of the builds are matching what we have now in VIP builds.</li> <li class="MsoNormal" style="mso-list: l10 level4 lfo1; tab-stops: list 2.0in;">COMR, Autoscheduler, ethernet and new SWIL configurations could be the pain points for SWILs moving forward.</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l10 level5 lfo1; tab-stops: list 2.5in;">SDV leadership is working on these issues and debugging as needed.</li> </ul> </ul> <li class="MsoNormal" style="mso-list: l10 level3 lfo1; tab-stops: list 1.5in;">They are already familiar with MCU1 and SE devices.</li> <li class="MsoNormal" style="mso-list: l10 level3 lfo1; tab-stops: list 1.5in;">Ethernet and other new technologies are being learned by hands on experience.</li> </ul> </ul> </ul> <p class="MsoNormal" style="margin-left: 1.5in;"> </p> <ul style="margin-top: 0in;" type="disc"> <ul style="margin-top: 0in;" type="circle"> <li class="MsoNormal" style="mso-list: l10 level2 lfo1; tab-stops: list 1.0in;">Automated Nightly Builds and demos:</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l10 level3 lfo1; tab-stops: list 1.5in;">The NA team is already supporting automated nightly builds.</li> <li class="MsoNormal" style="mso-list: l10 level3 lfo1; tab-stops: list 1.5in;">Continue improving and streamlining the automated build processes, ensuring any issues are promptly addressed.</li> <li class="MsoNormal" style="mso-list: l10 level3 lfo1; tab-stops: list 1.5in;">Till Cadence 181 (August2025) SWILs will continue to support nightly builds at current levels. Dashboard data will be shared with upper management and any issues will be immediately followed up and escalated (after stable cadence builds are achieved).</li> <li class="MsoNormal" style="mso-list: l10 level3 lfo1; tab-stops: list 1.5in;">Sumit Shrestha - SWIM BECM/EEM/ EEM BC</li> <li class="MsoNormal" style="mso-list: l10 level3 lfo1; tab-stops: list 1.5in;">Gurudutt Rao - SWIM DMC</li> <li class="MsoNormal" style="mso-list: l10 level3 lfo1; tab-stops: list 1.5in;">Steve Hatch - SWIM all other projects.</li> <li class="MsoNormal" style="mso-list: l10 level3 lfo1; tab-stops: list 1.5in;">Jonathan Hyland (assigned to our team with 75% availability) took the responsibility of automating the builds.</li> <ul style="margin-top: 0in;" type="square"> <li class="MsoNormal" style="mso-list: l10 level4 lfo1; tab-stops: list 2.0in;">Currently ensuring the nightly builds are passing along with SWIMs help .</li> </ul> </ul> </ul> </ul> <p class="MsoNormal"> </p> <ul style="margin-top: 0in;" type="circle"> <li class="MsoNormal" style="mso-list: l2 level1 lfo2; tab-stops: list .5in;">MCU1, SE, and MCU3 Build Support:</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l2 level2 lfo2; tab-stops: list 1.0in;">Head Count Planning:</li> <ul style="margin-top: 0in;" type="square"> <li class="MsoNormal" style="mso-list: l2 level3 lfo2; tab-stops: list 1.5in;">List of VMEC SDV builds are identified.</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l2 level4 lfo2; tab-stops: list 2.0in;">To be reviewed quarterly.</li> </ul> <li class="MsoNormal" style="mso-list: l2 level3 lfo2; tab-stops: list 1.5in;">Complexity level is assigned to each build/swimlane throughout 2025.</li> <li class="MsoNormal" style="mso-list: l2 level3 lfo2; tab-stops: list 1.5in;">Resource need is established with SDV leadership input.</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l2 level4 lfo2; tab-stops: list 2.0in;">Related projects (such as BDY, BDY_BC) are assigned to same</li> </ul> <li class="MsoNormal" style="mso-list: l2 level3 lfo2; tab-stops: list 1.5in;">20% overhead is accounted for nightly build triage.</li> <li class="MsoNormal" style="mso-list: l2 level3 lfo2; tab-stops: list 1.5in;">Plan to be reviewed monthly and resources are further managed by priorities. </li> </ul> <li class="MsoNormal" style="mso-list: l2 level2 lfo2; tab-stops: list 1.0in;">MCU1 and SE Builds:</li> <ul style="margin-top: 0in;" type="square"> <li class="MsoNormal" style="mso-list: l2 level3 lfo2; tab-stops: list 1.5in;">Gradually take over responsibility from NATS and Infrastructure groups to support MCU1 and SE builds throughout 2024, with a full transition by Q3 2025.</li> </ul> <li class="MsoNormal" style="mso-list: l2 level2 lfo2; tab-stops: list 1.0in;">MCU3 Builds:</li> <ul style="margin-top: 0in;" type="square"> <li class="MsoNormal" style="mso-list: l2 level3 lfo2; tab-stops: list 1.5in;">The newly established SDV domain will handle MCU3 builds. Coordination and proper handover between existing teams and the SDV domain is established as part of the transition.</li> <li class="MsoNormal" style="mso-list: l2 level3 lfo2; tab-stops: list 1.5in;">SDV domain members are approved by TS and SDV leadership.</li> </ul> </ul> <li class="MsoNormal" style="mso-list: l2 level1 lfo2; tab-stops: list .5in;">SWIM organization:</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l2 level2 lfo2; tab-stops: list 1.0in;">Currently Steve H. is organizing the bulk of the SDV builds. A SWIM from Battery and another from Electrification domain is supporting him with a very limited capacity.</li> <ul style="margin-top: 0in;" type="square"> <li class="MsoNormal" style="mso-list: l2 level3 lfo2; tab-stops: list 1.5in;">Sumit Shrestha - SWIM BECM/EEM/ EEM BC</li> <li class="MsoNormal" style="mso-list: l2 level3 lfo2; tab-stops: list 1.5in;">Gurudutt Rao - SWIM DMC</li> <li class="MsoNormal" style="mso-list: l2 level3 lfo2; tab-stops: list 1.5in;">Steve Hatch - SWIM all other projects.</li> </ul> </ul> </ul> <p class="MsoNormal" style="margin-left: 1.0in;"> </p> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l1 level1 lfo3; tab-stops: list .5in;">2025:</li> <ul style="margin-top: 0in;" type="circle"> <li class="MsoNormal" style="mso-list: l1 level2 lfo3; tab-stops: list 1.0in;">MCU1 & SE Build Management:</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l1 level3 lfo3; tab-stops: list 1.5in;">MCU1 and SE builds will be fully managed by their respective domains, ensuring a smooth transition.</li> <li class="MsoNormal" style="mso-list: l1 level3 lfo3; tab-stops: list 1.5in;">Transition started with Tagore getting trained by infrastructure team members (March 2025).</li> <li class="MsoNormal" style="mso-list: l1 level3 lfo3; tab-stops: list 1.5in;">Bench setup is being discussed with Steven S.</li> </ul> <li class="MsoNormal" style="mso-list: l1 level2 lfo3; tab-stops: list 1.0in;">MCU3 Build Management:</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l1 level3 lfo3; tab-stops: list 1.5in;">SDV domain will be fully responsible for MCU3 builds by 2025, with all necessary swimlane support in place.</li> </ul> <li class="MsoNormal" style="mso-list: l1 level2 lfo3; tab-stops: list 1.0in;">CoSIM builds:</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l1 level3 lfo3; tab-stops: list 1.5in;">After completing the DPLY builds, SWILs are expected to provide the CoSIM builds to the SIL team for pulling ahead the testing. As the validation proceeds the SWIL will be asked to provide the ECU build.</li> </ul> </ul> </ul> <p class="MsoNormal" style="margin-left: 1.5in; text-indent: -.25in; mso-list: l3 level1 lfo4; tab-stops: list .5in 1.5in;">· There are some road blocks here.</p> <p class="MsoNormal" style="margin-left: 1.5in; text-indent: -.25in; mso-list: l3 level1 lfo4; tab-stops: list .5in 1.5in;">· Most of them needs to be taken care by CoSIM team.</p> <p class="MsoNormal" style="margin-left: 2.0in; text-indent: -.25in; mso-list: l3 level2 lfo4; tab-stops: list 1.0in 2.0in;">§ We are supporting CoSIM team on topics like linker updates weekly.</p> <p class="MsoNormal" style="margin-left: 1.25in; text-indent: -.25in; mso-list: l20 level1 lfo5; tab-stops: list .5in 1.25in;">o Nightly builds and demos:</p> <p class="MsoNormal" style="margin-left: 1.75in; text-indent: -.25in; mso-list: l20 level2 lfo5; tab-stops: list 1.0in 1.75in;">· It is expected that nightly build and demo support will continue during 2025.</p> <p class="MsoListParagraphCxSpFirst" style="margin-left: 1.25in; mso-add-space: auto; text-indent: -.25in; mso-list: l20 level1 lfo5; tab-stops: list 1.25in;">o 2025 Executive Build Initiatives</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.5in; mso-add-space: auto; text-indent: -.25in; mso-list: l9 level3 lfo18; tab-stops: list 1.5in;">· NY Push (1/3/2025):</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.5in; mso-add-space: auto;">(EEM_EV and BECM is the focus for VMEC. VMEC builds delivered on time.)</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.5in; mso-add-space: auto;"> </p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 2.0in; mso-add-space: auto; text-indent: -.25in; mso-list: l9 level4 lfo18; tab-stops: list 2.0in;">§ Tagore to help BECM weekly sprints until Q2 2025 as we are not responsible till 2025.</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 2.0in; mso-add-space: auto; text-indent: -.25in; mso-list: l9 level4 lfo18; tab-stops: list 2.0in;">§ Tagore/Bo to train to Ruomei in December 2024 for 2025 Support.</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 2.0in; mso-add-space: auto; text-indent: -.25in; mso-list: l9 level4 lfo18; tab-stops: list 2.0in;">§ Namith to support Jim S. on DMC.</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 2.0in; mso-add-space: auto; text-indent: -.25in; mso-list: l9 level4 lfo18; tab-stops: list 2.0in;">§ Transition will take place by Q3 of 2025.</p> <p class="MsoListParagraphCxSpLast" style="margin-left: 2.0in; mso-add-space: auto; text-indent: -.25in; mso-list: l9 level4 lfo18; tab-stops: list 2.0in;">§ ECU builds are being added to our plate as we need to support ITCG testing.</p> <p class="MsoNormal"> </p> <p class="MsoListParagraphCxSpFirst" style="margin-left: 1.5in; mso-add-space: auto; text-indent: -.25in; mso-list: l9 level3 lfo18; tab-stops: list 1.5in;">· Valentines’ Day Push (2/14/2025)</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.0in; mso-add-space: auto; text-indent: .5in;">(179.4p0 builds delivered to CoSIM)</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.25in; mso-add-space: auto; text-indent: -.25in; mso-list: l13 level1 lfo19; tab-stops: list 1.25in;">· St. Patrick’s Day Push (3/21/2025)</p> <p class="MsoListParagraphCxSpMiddle" style="text-indent: .5in;">(180.0p0 based ECU and CoSIM builds are delivered on time.)</p> <p class="MsoListParagraphCxSpLast" style="margin-left: 1.25in; mso-add-space: auto; text-indent: -.25in; mso-list: l13 level1 lfo19; tab-stops: list 1.25in;">· April Fools’ Day Push (4/1/2025)</p> <p class="MsoNormal" style="margin-left: .5in; text-indent: .5in;">(This initiative merged with 25% PAR support.)</p> <p class="MsoListParagraphCxSpFirst" style="margin-left: 1.25in; mso-add-space: auto; text-indent: -.25in; mso-list: l13 level1 lfo19; tab-stops: list 1.25in;">· 25% PAR (4/25/2025)</p> <p class="MsoListParagraphCxSpMiddle" style="text-indent: .5in;">(Currently working on the MCU3 and MCU2 Builds that has VMEC content.)</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.0in; mso-add-space: auto;">MCU3_FARM_BDY (Steven H. / Cheng X. / Jonathan H.)</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.0in; mso-add-space: auto;">MCU3_FARM_BDY_BC (Steven H. / Cheng X. / Jonathan H.)</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.0in; mso-add-space: auto;">MCU3_FARM_EEM_EV (Sumit S. / Sue Z. / Jonathan H.)</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.0in; mso-add-space: auto;">MCU3_FARM_VMC_EEM_BC (Steven H. / Manohar K. / Jonathan H.)</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.0in; mso-add-space: auto;">MCU3_FARM_VMC_EV (Steven H. / Manohar K. / Jonathan H.)</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.0in; mso-add-space: auto;">ECU_MCU2_BE01 (BECM) (Sumit S. / John J. & Gouthami K. / Bo X.)</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.0in; mso-add-space: auto;">ECU_MCU2_TPIM_IM (DMC_R1) (Guru R. / Namith K. / Jim S.)</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.0in; mso-add-space: auto;">ECU_MCU1_AGGE_CLSS (LF) (Renuka R / Tagore K. / David W.)</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.0in; mso-add-space: auto;">ECU_MCU1_AGGE_CLSFR (RC) (Renuka R / Tagore K. / David W.)</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.0in; mso-add-space: auto;">ECU_MCU1_SED_AUTH (Renuka R / Tagore K. / David W.)</p> <p class="MsoListParagraphCxSpMiddle" style="margin-left: 1.25in; mso-add-space: auto; text-indent: -.25in; mso-list: l13 level1 lfo19; tab-stops: list 1.25in;">· 50% PAR (8/29/2025)</p> <p class="MsoListParagraphCxSpLast" style="text-indent: .5in;">TBD</p> <p class="MsoNormal"> </p> <p class="MsoNormal" style="margin-left: 1.0in; text-indent: -.25in; mso-list: l15 level1 lfo6; tab-stops: list .5in 1.0in;">o SWIM organization:</p> <p class="MsoNormal" style="margin-left: 1.5in; text-indent: -.25in; mso-list: l15 level2 lfo6; tab-stops: list 1.0in 1.5in;">· We expect to see a new SWIM organization supporting SDV work and create WTs for SWILs.</p> <p class="MsoNormal" style="margin-left: 1.5in; text-indent: -.25in; mso-list: l15 level2 lfo6; tab-stops: list 1.0in 1.5in;">· Current structure:</p> <p class="MsoNormal" style="margin-left: 2.0in; text-indent: -.25in; mso-list: l15 level3 lfo6; tab-stops: list 1.5in 2.0in;">§ Sumit Shrestha - SWIM BECM/EEM/ EEM BC</p> <p class="MsoNormal" style="margin-left: 2.0in; text-indent: -.25in; mso-list: l15 level3 lfo6; tab-stops: list 1.5in 2.0in;">§ Gurudutt Rao - SWIM DMC</p> <p class="MsoNormal" style="margin-left: 2.0in; text-indent: -.25in; mso-list: l15 level3 lfo6; tab-stops: list 1.5in 2.0in;">§ Steve Hatch - SWIM all other projects.</p> <p class="MsoNormal" style="margin-left: 1.5in; text-indent: -.25in; mso-list: l15 level2 lfo6; tab-stops: list 1.5in;">· Daily 8:00AM meetings with upper management ensures the work needs to be done coordinated through SWIMs properly.</p> <p class="MsoNormal" style="margin-left: 1.5in; text-indent: -.25in; mso-list: l15 level2 lfo6; tab-stops: list 1.5in;">· Daily 12:00PM Status/Planning meeting is where we sync beyond VMEC groups.</p> <p class="MsoNormal" style="margin-left: 1.5in; text-indent: -.25in; mso-list: l15 level2 lfo6; tab-stops: list 1.0in 1.5in;">· Daily DSU meeting is held by SWIMs and supports the execution and prioritization.</p> <p class="MsoNormal"> </p> <p class="MsoNormal">2. Responsibilities & Escalation Management</p> <p class="MsoListParagraph" style="text-indent: -.25in; mso-list: l12 level1 lfo7; tab-stops: list .5in;">· Escalation path follows the regular VMEC escalation path: SWIM/EGM/Director/Executive Director.</p> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l12 level1 lfo7; tab-stops: list .5in;">Upstream work that needs to be done before SWIL build:</li> </ul> <p class="MsoNormal" style="margin-left: 1.0in;">Sprint Closure and APP and infrastructure SW release</p> <p class="MsoNormal" style="margin-left: 1.0in;">BSW SW release</p> <p class="MsoNormal" style="margin-left: 1.0in;">HWIO release</p> <p class="MsoNormal" style="margin-left: 1.0in;">ARXML/ODX/MACT/MGAL release</p> <p class="MsoNormal" style="margin-left: 1.0in;">COMR/NPCR CFG release</p> <p class="MsoNormal" style="margin-left: 1.0in;">ENTR CFG</p> <p class="MsoNormal" style="margin-left: 1.5in; text-indent: -.25in; mso-list: l7 level1 lfo8; tab-stops: list 1.5in;">· SWIL Builds</p> <p class="MsoNormal" style="margin-left: 1.0in;">DPLY Build</p> <p class="MsoNormal" style="margin-left: 1.0in;">ECU Build</p> <p class="MsoNormal" style="margin-left: 1.5in; text-indent: -.25in; mso-list: l14 level1 lfo9; tab-stops: list 1.5in;">· Downstream work</p> <p class="MsoNormal" style="margin-left: 1.0in;">Infra Cals Ready</p> <p class="MsoNormal" style="margin-left: 1.0in;">CIE Smoke Test</p> <p class="MsoNormal" style="margin-left: 1.0in;">ECU SW Build ID for JSON updates</p> <p class="MsoNormal" style="margin-left: 1.0in;">TFRP Plan</p> <p class="MsoNormal" style="margin-left: 1.0in;">TW3 Cosim Build</p> <p class="MsoNormal" style="margin-left: 1.0in;">L3 Build</p> <p class="MsoNormal" style="margin-left: 1.0in;">L4 Build</p> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l16 level1 lfo10; tab-stops: list .5in;">SWIM Role:</li> <ul style="margin-top: 0in;" type="circle"> <li class="MsoNormal" style="mso-list: l16 level2 lfo10; tab-stops: list 1.0in;">Steve H. will continue to plan SDV work and manage daily issues, following up in daily calls. Sumit Shrestha and Gurudutt Rao take on the SWIM responsibilities for the initial Battery and Electrification builds.</li> <li class="MsoNormal" style="mso-list: l16 level2 lfo10; tab-stops: list 1.0in;">Establish a process for identifying, tracking, and addressing high-priority issues during daily calls.</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l16 level3 lfo10; tab-stops: list 1.5in;">Steve to inform Jayden after daily calls so that respective people can be made available and give a status update at 12:00PM meetings.</li> </ul> </ul> <li class="MsoNormal" style="mso-list: l16 level1 lfo10; tab-stops: list .5in;">Escalation Process:</li> <ul style="margin-top: 0in;" type="circle"> <li class="MsoNormal" style="mso-list: l16 level2 lfo10; tab-stops: list 1.0in;">Jayden B. will continue to escalate any pressing issues to respective team members.</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l16 level3 lfo10; tab-stops: list 1.5in;">The SDV team identifies the issue and the party causing the issue during daily status calls first thing in the morning.</li> <li class="MsoNormal" style="mso-list: l16 level3 lfo10; tab-stops: list 1.5in;">Steve H. informs Jayden and provides what needs to be done.</li> <li class="MsoNormal" style="mso-list: l16 level3 lfo10; tab-stops: list 1.5in;">Jayden follows up with the issue owner and escalates as necessary.</li> <ul style="margin-top: 0in;" type="square"> <li class="MsoNormal" style="mso-list: l16 level4 lfo10; tab-stops: list 2.0in;">Issue owner is brought in the 12:00PM call and provides an update.</li> <li class="MsoNormal" style="mso-list: l16 level4 lfo10; tab-stops: list 2.0in;">The team decides what is next for the issue and provides help as needed.</li> </ul> </ul> </ul> </ul> <p class="MsoNormal"> </p> <p class="MsoNormal">3. Cadence MCU Builds & NATS Support</p> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l8 level1 lfo11; tab-stops: list .5in;">Cadence 177/178/179/180++ Builds:</li> <ul style="margin-top: 0in;" type="circle"> <li class="MsoNormal" style="mso-list: l8 level2 lfo11; tab-stops: list 1.0in;">Continue supporting the Cadence MCU builds as the primary ongoing task.</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l8 level3 lfo11; tab-stops: list 1.5in;">This is the highest priority for the SDV team.</li> <li class="MsoNormal" style="mso-list: l8 level3 lfo11; tab-stops: list 1.5in;">As needed basis we may bring in other SWILs or ask help from infrastructure team to meet the deadlines.</li> </ul> <li class="MsoNormal" style="mso-list: l8 level2 lfo11; tab-stops: list 1.0in;">SDV leadership team ensures documentation and best practices are in place to streamline these builds and avoid any potential blockers.</li> </ul> <li class="MsoNormal" style="mso-list: l8 level1 lfo11; tab-stops: list .5in;">Cadence Builds there on:</li> <ul style="margin-top: 0in;" type="circle"> <li class="MsoNormal" style="mso-list: l8 level2 lfo11; tab-stops: list 1.0in;">Follow the workorder stated in Cadence 177 builds.</li> </ul> </ul> <p class="MsoNormal"> </p> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l0 level1 lfo12; tab-stops: list .5in;">NATS Support for SE and MCU1 Builds:</li> <ul style="margin-top: 0in;" type="circle"> <li class="MsoNormal" style="mso-list: l0 level2 lfo12; tab-stops: list 1.0in;">Gradually transition SE and MCU1 builds from NATS to the NA SWIL team/domains by Q3 of 2025.</li> <li class="MsoNormal" style="mso-list: l0 level2 lfo12; tab-stops: list 1.0in;">Set up a phased approach for taking over these responsibilities, ensuring proper knowledge transfer and reducing dependency on external teams.</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l0 level3 lfo12; tab-stops: list 1.5in;">Sergio A. started transitioning the BECM project and Namith K. is starting with the TPIM IM.</li> </ul> <li class="MsoNormal" style="mso-list: l0 level2 lfo12; tab-stops: list 1.0in;">Projects currently supported by other groups will be transitioned from respective owners by the end of Q3 2025 as well.</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l0 level3 lfo12; tab-stops: list 1.5in;">Project transition will be handled by the MCU1/SE responsible (David W. / Jim S.).</li> <li class="MsoNormal" style="mso-list: l0 level3 lfo12; tab-stops: list 1.5in;">After the initial setup is in place the SWIL team will take over ensuring all the configurations are set up properly.</li> </ul> </ul> </ul> <p class="MsoNormal"> </p> <p class="MsoNormal">4. Automation Activities:</p> <p class="MsoNormal"> Nightly Automated run aims to build DPLY and ECU builds each time on selected cadence (18x.xp10) and after the run an email compiled and distributed to the subscribers.</p> <p class="MsoNormal"> Changes to the memory mapping, signals and other configurations are causing automation to fail and constantly followed up. By SWILs.</p> <p class="MsoNormal"> Jonathan H. assigned to the SWIL team with 75% capacity to lead the automation activities. Up until 25% Jonathan will try to understand the overall how parts getting together in the new SDV architecture and identify areas the automation could add value. Automation may start as partial automation and go towards a full system automation.</p> <p class="MsoNormal"> Pod promotion strategy where the components are breaking the builds are rejected will be implemented as part of the automation process yet the final product needs to include the scope elements and resulting build may not be accepted by the receiving stakeholders.</p> <p class="MsoNormal"> Following are the areas that needs to be change managed/coordinated to accomplish DPLY and ECU build automation.</p> <p class="MsoNormal"> </p> <p class="MsoNormal" style="text-indent: .5in;">PA and other types of builds are beyond the scope at this point.</p> <p class="MsoNormal"> </p> <p class="MsoNormal">5. SDV Swimlane Strategy & Complexity-Based Planning</p> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l6 level1 lfo13; tab-stops: list .5in;">Headcount (HC) Planning:</li> <ul style="margin-top: 0in;" type="circle"> <li class="MsoNormal" style="mso-list: l6 level2 lfo13; tab-stops: list 1.0in;">Headcount planning for 2024 and 2025 has been completed by assigning complexity levels to each SDV swimlane.</li> <li class="MsoNormal" style="mso-list: l6 level2 lfo13; tab-stops: list 1.0in;">Ensure that team allocations align with these complexity levels and that resources are utilized efficiently for swimlane support.</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l6 level3 lfo13; tab-stops: list 1.5in;">SWILs from similar background/domain could be assigned to the respective MCU3 builds.</li> <li class="MsoNormal" style="mso-list: l6 level3 lfo13; tab-stops: list 1.5in;">Cohort build and respective BC build can be assigned to same person until the workload increases with additional builds on the same swimlane such as Boot builds.</li> <li class="MsoNormal" style="mso-list: l6 level3 lfo13; tab-stops: list 1.5in;">Experienced SWILs could take on most comprehensive build and have trial builds ahead of schedule as partial builds to sort of issues.</li> </ul> </ul> <li class="MsoNormal" style="mso-list: l6 level1 lfo13; tab-stops: list .5in;">Swimlane Strategy Definition:</li> <ul style="margin-top: 0in;" type="circle"> <li class="MsoNormal" style="mso-list: l6 level2 lfo13; tab-stops: list 1.0in;">Ryan’s Work with SW Architects:</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l6 level3 lfo13; tab-stops: list 1.5in;">Ryan is currently working with SW architects to define a broader swimlane strategy, aimed at eliminating unnecessary software branches in the future.</li> <li class="MsoNormal" style="mso-list: l6 level3 lfo13; tab-stops: list 1.5in;">SDV leadership to support Ryan and the SW architects in ensuring that swimlane definitions are clear, effective, and minimize redundant or extra branches.</li> <li class="MsoNormal" style="mso-list: l6 level3 lfo13; tab-stops: list 1.5in;">This strategy should help in simplifying build management and improving the overall efficiency of the SDV builds.</li> <li class="MsoNormal" style="mso-list: l6 level3 lfo13; tab-stops: list 1.5in;">Ryan is leading the new swimlane strategy discussions:</li> </ul> </ul> </ul> <p class="MsoNormal"> </p> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l18 level1 lfo14; tab-stops: list .5in;">Anil is being added to the list.</li> <ul style="margin-top: 0in;" type="square"> <li class="MsoNormal" style="mso-list: l18 level2 lfo14; tab-stops: list 1.0in;">OUTPUT is the new SDV architecture strategy and rules of engagement</li> </ul> </ul> <p class="MsoNormal"> </p> <p class="MsoNormal"> </p> <p class="MsoNormal">6. Training & Development</p> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l19 level1 lfo15; tab-stops: list .5in;">Training:</li> <ul style="margin-top: 0in;" type="circle"> <li class="MsoNormal" style="mso-list: l19 level2 lfo15; tab-stops: list 1.0in;">Training for the SWIL team has already been completed.</li> <li class="MsoNormal" style="mso-list: l19 level2 lfo15; tab-stops: list 1.0in;">Ongoing training sessions are scheduled and hands on experience builds are being rolled out for any new team members who may require additional support, especially as new tools or processes are introduced.</li> <li class="MsoNormal" style="mso-list: l19 level2 lfo15; tab-stops: list 1.0in;">Limited bench setup is available for SWILs.</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l19 level3 lfo15; tab-stops: list 1.5in;">Debugging needs need to be identified.</li> <li class="MsoNormal" style="mso-list: l19 level3 lfo15; tab-stops: list 1.5in;">Advanced Trace32 training may be required. </li> </ul> </ul> </ul> <p class="MsoNormal"> </p> <p class="MsoNormal">7. Risk Management & Continuous Improvement</p> <p class="MsoNormal"> </p> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l5 level1 lfo16; tab-stops: list .5in;">Potential Risks:</li> <ul style="margin-top: 0in;" type="circle"> <li class="MsoNormal" style="mso-list: l5 level2 lfo16; tab-stops: list 1.0in;">SWIL experience</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l5 level3 lfo16; tab-stops: list 1.5in;">Mitigated – currently 7 level SWILs are assigned to the SDV domain. MCU1 and SE builds will be handled by respective domains under the supervision of DL.</li> <ul style="margin-top: 0in;" type="square"> <li class="MsoNormal" style="mso-list: l5 level4 lfo16; tab-stops: list 2.0in;">SDV leadership is also there to help.</li> </ul> </ul> <li class="MsoNormal" style="mso-list: l5 level2 lfo16; tab-stops: list 1.0in;">Delays in transition for MCU1, SE, or MCU3 builds.</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l5 level3 lfo16; tab-stops: list 1.5in;">Accepted – Nightly builds are already covering most of the builds needs to be taken over.</li> <ul style="margin-top: 0in;" type="square"> <li class="MsoNormal" style="mso-list: l5 level4 lfo16; tab-stops: list 2.0in;">If there is any delays the team members will support available SDV builds or lend out to other domains to support any excess work.</li> </ul> </ul> <li class="MsoNormal" style="mso-list: l5 level2 lfo16; tab-stops: list 1.0in;">Early transition request for MCU1, SE, or MCU3 builds.</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l5 level3 lfo16; tab-stops: list 1.5in;">Mitigated – SDV leadership will take on the builds and assign to relative SWILs earlier.</li> </ul> <li class="MsoNormal" style="mso-list: l5 level2 lfo16; tab-stops: list 1.0in;">Inconsistent handling of escalated issues or swimlane strategy inefficiencies.</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l5 level3 lfo16; tab-stops: list 1.5in;">Mitigated – SDV leadership is handling these requests.</li> </ul> <li class="MsoNormal" style="mso-list: l5 level2 lfo16; tab-stops: list 1.0in;">MC1 to MCU0 transition</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l5 level3 lfo16; tab-stops: list 1.5in;">Mitigated – SDV leadership is handling these requests.</li> <li class="MsoNormal" style="mso-list: l5 level3 lfo16; tab-stops: list 1.5in;">Cost cutting measures impacting the MCU1 projects.</li> <li class="MsoNormal" style="mso-list: l5 level3 lfo16; tab-stops: list 1.5in;">May 2025 MCU0 projects will replace MCU1 projects.</li> <li class="MsoNormal" style="mso-list: l5 level3 lfo16; tab-stops: list 1.5in;">By August 2025 empty APP MCU0 builds are needed by the suppliers.</li> </ul> </ul> </ul> <p class="MsoNormal" style="margin-left: 1.25in;"> </p> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l5 level1 lfo16; tab-stops: list .5in;">Mitigation Strategies:</li> <ul style="margin-top: 0in;" type="circle"> <li class="MsoNormal" style="mso-list: l5 level2 lfo16; tab-stops: list 1.0in;">Regular Reviews: Conduct weekly or bi-weekly reviews to monitor the progress of transition timelines, especially for MCU1, SE, and MCU3 builds.</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l5 level3 lfo16; tab-stops: list 1.5in;">Bi-weekly SDV leadership review meetings are in place.</li> </ul> <li class="MsoNormal" style="mso-list: l5 level2 lfo16; tab-stops: list 1.0in;">Escalation Tracking: Implement a formal tracking system for escalated issues, ensuring that any major blockers are promptly addressed.</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l5 level3 lfo16; tab-stops: list 1.5in;">Daily 12:00PM calls are in place for following up with escalations.</li> <ul style="margin-top: 0in;" type="square"> <li class="MsoNormal" style="mso-list: l5 level4 lfo16; tab-stops: list 2.0in;">Daily escalations are supported by Jayden, Steve.</li> </ul> </ul> <li class="MsoNormal" style="mso-list: l5 level2 lfo16; tab-stops: list 1.0in;">Continuous Process Improvement: As swimlane strategies evolve, regularly review and refine them to minimize unnecessary branches and improve overall software development efficiency.</li> <ul style="margin-top: 0in;" type="disc"> <li class="MsoNormal" style="mso-list: l5 level3 lfo16; tab-stops: list 1.5in;">SDV leadership is handing the continuous proves improvement. These improvements are rolled out by SWIL TS.</li> </ul> </ul> </ul> <p class="MsoNormal"> </p> <p class="MsoListParagraph" style="text-indent: -.25in; mso-list: l11 level1 lfo21;">F. Outcome:</p> <p class="MsoNormal">By Q3 of 2025, the SDV strategy will be fully implemented, with smooth transitions of MCU1, SE, and MCU3 build responsibilities, optimized swimlane management, and reduced inefficiencies in software branch management. The NA team will continue supporting automated nightly builds, with resources aligned to handle complexity-based swimlanes effectively.</p> <p class="MsoNormal"> </p>
Idea Notes:
<p style="color: #000000; margin: 0in; font-family: Calibri; font-size: 11.0pt;">Build Master Schedule</p> <p style="color: #000000; margin: 0in; margin-left: .375in; font-family: Calibri; font-size: 11.0pt;">Solution in context Integrated ECU build</p> <ul style="direction: ltr; unicode-bidi: embed; margin-top: 0in; margin-bottom: 0in;" type="disc"> <li style="margin-top: 0; margin-bottom: 0; vertical-align: middle;">VMEC APP</li> <ul style="direction: ltr; unicode-bidi: embed; margin-top: 0in; margin-bottom: 0in;" type="circle"> <li style="margin-top: 0; margin-bottom: 0; vertical-align: middle;">API Definitions (RSMT)</li> <li style="margin-top: 0; margin-bottom: 0; vertical-align: middle;">Users of API (DSC)</li> </ul> <li style="margin-top: 0; margin-bottom: 0; vertical-align: middle;">BSW SW</li> <li style="margin-top: 0; margin-bottom: 0; vertical-align: middle;">ARXML/ODX/MACT/MGAL</li> <ul style="direction: ltr; unicode-bidi: embed; margin-top: 0in; margin-bottom: 0in;" type="circle"> <li style="margin-top: 0; margin-bottom: 0; vertical-align: middle;">RSMT (Regenerates ARXML every 2 hours)</li> <ul style="direction: ltr; unicode-bidi: embed; margin-top: 0in; margin-bottom: 0in;" type="disc"> <li style="margin-top: 0; margin-bottom: 0; vertical-align: middle;">BOM</li> <li style="margin-top: 0; margin-bottom: 0; vertical-align: middle;">API Definitions</li> </ul> </ul> <li style="margin-top: 0; margin-bottom: 0; vertical-align: middle;">ENTR_CFG</li> <ul style="direction: ltr; unicode-bidi: embed; margin-top: 0in; margin-bottom: 0in;" type="circle"> <li style="margin-top: 0; margin-bottom: 0; vertical-align: middle;">Prevision (requires ARXML)</li> </ul> <li style="margin-top: 0; margin-bottom: 0; vertical-align: middle;">COMR_CFG/NPCR_CFG</li> <ul style="direction: ltr; unicode-bidi: embed; margin-top: 0in; margin-bottom: 0in;" type="circle"> <li style="margin-top: 0; margin-bottom: 0; vertical-align: middle;">BCT Tool Generation</li> </ul> <li style="margin-top: 0; margin-bottom: 0; vertical-align: middle;">VMEC APP</li> <ul style="direction: ltr; unicode-bidi: embed; margin-top: 0in; margin-bottom: 0in;" type="circle"> <li style="margin-top: 0; margin-bottom: 0; vertical-align: middle;">Algo (DSC)</li> </ul> <li style="margin-top: 0; margin-bottom: 0; vertical-align: middle;">Integrate ECU</li> </ul> <p style="margin: 0in; margin-left: .375in;"> </p>
Update Idea