Edit Idea
View Ideas
Idea Date:
Idea Title:
Idea Description:
<p>Engine, Transmission, Chassis Integration Team is responsible for integrating SW components to release vehicle level SW to downstream to calibrators and test engineers. My team consists of SWILs (Software Integration Leaders), CIEs (Controller Integration Engineers) and NATS (New Architecture Specialists). We are responsible for the Engine, Transmission and Chassis domains. Within Chassis Domain we also have the SDV projects. SDV projects are new and they are called MCU0 projects, we are responsible for SEAT, Closure and Auth modules. SWILs and CIEs could be 6 or 7th level within the organization hierarchy and NATS are 8th level as they are the highest level an engineer can get. We are also getting SWIL support from TCS team which is a contract company that works directly with us. They are mainly focusing on the legacy Engine and Transmission projects. From our local team we still support them with CIEs and NATS.</p> <p>Our specific group gets the work from SWIMs (SW Integration Manager) in terms of Jira tickets and SWILs in my team builds, sanity checks and releases the SW as per the ticket. After the release the issues found mostly on the bench is debugged again the CIE members of the team. NATS are there to handle any request that is beyond the SWILs and CIEs as they are trying to get the operational status of controllers achieved at all times. We are a systems team and although we supposed to get cadence builds and requests in relation we also get pull ahead build requests where the new component have to be build with the old baseline of software in situations like when it is too risky to move to the latest software. Similarly the issues can pop up at any point which requires attention from CIEs or NATS.</p> <p>I am setting up this team starting September 2025. Previously I was managing the SWIL team for all domains and we went through a reorganization and I ended up bringing the part of the SWIL team working on the Engine, Transmission, Chassis areas including MCU0s. On top I received same domain CIEs and NATS which was not part of my previous team. I don't have any SWIMs coordinating the work within and that role is provided by the larger organization. My goal is to create a performing team now kind of vertical including the integration with SWILs and issue resolution and support with CIEs and NATS.</p> <p>Here is the roles and responsibilities for each role within my team as well as mission and primary customers:</p> <p>Role 1: SWIL: Software Integration Leader (SWIL)<br>Mission: Build Integrated Vehicle Motion Control Software that exceeds customer expectations and business requirements.<br>Primary Customers: Calibration Community, Platform Teams<br>ROLES/RESPONSIBILITIES<br>• Integrate and build software for controller system releases and interim software builds<br>• Single point contact with controller supplier for software<br>• Assist in development of software content and software anomaly corrections as required<br>• Integration and verification testing of an integrated software build <br>• Prepare software for production release<br>• Manage controller resources for given ECU<br>• Oversee bench and instrumentation issue resolution<br>• Provide, communicate, and support common best practices among SWIL community</p> <p>DELIVERABLES<br>• Software release including build products and instrumentation files<br>• Release notification communicated to team<br>• Changes from previous release<br>• main/secondary/boot/BSP compatibilities<br>• part numbers<br>• ARXML (Global B and GEM programs)<br>• Supplier software issue resolution<br>• Coordination of Software impact analysis of Controller Supplier exceptions and outstanding PCE’s with SME (For example, NATS, SWIM, TRB, Safety).<br>• Support for SWIM in Supplier software CR task scheduling for new GM CTRS requirements and BSP anomalies.<br>• Scheduling of and/or participation in BSP Controller Supplier software design and verification reviews.<br>• Mentoring to software team members<br>• Software review<br>• Communication of common anomaly corrections with SWIM & SWILs for other ECUs<br>• SW tested per SWIL checklist and procedures<br>• First-pass verification<br>• Compiler/linker/locator logs<br>• C Source Code Parser log<br>• Second-pass verification<br>• Bench/vehicle testing<br>• Software and calibration parts configuration managed<br>• Support for system calibration development<br>• Software released and posted according to process and SWET requirements<br>• Resolution of ROM, RAM, and Throughput constraint issues<br>• Resolution of software build proliferation issues<br>• Support for resolution of issues identified by calibration and platform teams<br>• Expedient resolution of bench problems<br>• Documentation (CRs) of requested process and tool updates<br>• Usage of common tools (e.g., tool catalog and make files)<br>• Active participation in SWILs Meeting </p> <p>Role 2: CIE<br>Controller Integration Engineer (CIE)</p> <p>Mission Statement: First responder to troubleshoot vehicle or bench level VMEC specific integration issues and recommend solutions.<br>Primary Customers: SWILs, SWIMs, Software Development Teams (ARTs / Value Streams), Software Execution Teams (SWET), Controller Integration Teams, Calibration and Vehicle teams, Test Environment providers</p> <p>ROLES/RESPONSIBILITIES<br>• This role is responsible for vehicle embedded control system engineering with a primary focus on forming and leading cross-functional teams to troubleshoot issues through all the different life cycle stages (early development through launch and through end of production) on the full range of GM vehicles.<br>• Lead efforts to work closely with internal development teams including manufacturing, controls development, software, calibration, and testing activities, as well as other cross functional teams in tackling a wide variety of issues as they arise and plotting the best path towards resolution.<br>• Focus on vehicle system level integration issues including hardware, software, calibration, and vehicle wiring issues (including development activities, in-vehicle build events, buy-off rides, test trips, general fleet usage, durability, VeSCoM Checkout, etc.)<br>• Lead efforts and develop strategies to best support:<br>• Test Engineers when facing issues on bench or vehicle for testing (KBT, Milestone, etc.)<br>• Software support for calibration teams and development trips<br>• Assembly plant and field problem resolution.<br>• Test Environment Engineers in troubleshooting and commissioning HIL/SIL/SOLE systems for executing tests and developing operating scenarios to emulate vehicle functions.<br>• Controls development (SWAT, VIP, SDV, Infrastructure teams) as required.<br>• Basic Software Development team during emergency builds and testing (e.g., compliance updates) <br>• Prototype shop and dynos/durability cars / test & development fleets<br>• Evaluating controller field returns <br>• Controller rework/reflash (at Pre-PPO and PPO facilities)/Red X activities<br>• Vehicle software updates if users need help flashing software or investigating and resolving implementation issues.<br>• Analyze in-house software by applying debugging tools in troubleshooting issues in the ECU memory management, infrastructure operation and applications code.<br>• Respond to issues from PRTS, Defect Tracking, etc. and actively participate or lead the appropriate stakeholder priority discussion forums.<br>• Work on both internal SW testing issues and/or with suppliers in outsourced programs.<br>• Confirm resolution of CIE documented hardware and software anomalies.<br>• Act as point contact with Issue Resolution Teams and Technicians at PPO and Plants to implement processes that enable rapid problem resolution.<br>• Educate/train/support/mentor new and less experienced Controls Integration Engineers (CIE) and others learning about the tools and methods employed in this role.<br>• Develop new tools and processes supporting troubleshooting.<br>• Integrate and apply applicable Agile SAFe methods in CIE tasks.</p> <p>DELIVERABLES<br>• Document hardware and software anomalies using JIRA (or similar database) and PRTS as appropriate.<br>• Root cause analyze and propose potential solutions to issues. <br>• Review and update PRTS status for issues according to priority established through RPN values and stakeholder discussions. <br>• Lead updates on controller integration issue status to appropriate system issue owners (by providing timely responses to stakeholders)<br>• Debug and identify root causes issues on the bench.<br>• Timely Bench & Vehicle Testing. Appropriate feedback to the ARTs and Software Factory<br>• “Quick turn” tests of software corrections and non-production controller/software for demos, mules, dynos, etc.<br>• Preparing for test and debugging controller (s/w, calibration issues) on the appropriate environment (vehicle, HIL, SIL, etc.)<br>• Document and publish CIE related best practices, lessons learned, and develop web or Sharepoint or other information sharing pages for CIEs.<br>• Execution of PRC designee role in assigned PRTS</p> <p>Role 3: NATS - New Architecture Technical Specialist (NATS)</p> <p>Mission Statement: To define requirements and achieve operational status of new controller architectures<br>Primary Customers: Software development teams, Calibration teams, Vehicle teams, ARTs, Value Streams</p> <p>ROLES/RESPONSIBILITIES<br>• Works with SWILs and CIEs to integrate application code and HWIO with the EDU or initial prototype controller to get a new controller up and running.<br>• Interacts with instrumentation supplier and the controller supplier (HWIO) to get the bench operational and to debug and resolve issues for the initial New Architecture Program<br>• Acts as Software Manager on the initial New Architecture Program and/or coordinate these SW activities:<br>• Primary interface to controller supplier for software<br>• Lead initial controller validation efforts.<br>• Controller interface to development teams (ARTs, Value Streams)<br>• Schedules and participates in HWIO Controller Supplier software reviews.<br>• Generates technical solutions for new and major architectures.<br>• Provides technical leadership for advanced cross functional technology development.<br>• Develops and evaluates engineering designs including complex design analysis.<br>• Creates and balances requirements across systems.<br>• Initiates and evaluates cost studies, product suggestions and value analyses.<br>• Leads overall communication, coordination, and consultation with engineering departments and customers.<br>• Stays abreast of new technology and competitive products.<br>• Trains, develops, mentors, and evaluates technical capability of team members</p> <p>DELIVERABLES<br>• Operational development environment - Coordinated efforts of controls tools group, controller supplier, instrumentation supplier and tools vendors to ensure controller teams are functional using Software Bench, Debuggers, Compilers and Instrumentation<br>• Prioritize CIE/CTE and SWIL activities, for initial controller deployment.<br>• Support CSIL and SWIL to manage HWIO delivery and validation, for initial controller deployment.<br>• Impact Analysis of controller supplier software exceptions<br>• Coordinated development and resolution of supplier software and LLIO issues.<br>• Coordinated software development activity across teams.<br>• Negotiated controller software release schedule and content on initial builds with hand-off to production SWIM.<br>• Review of supplier software<br>• Technical solutions which can be implemented in a secure, standard, cost-effective manner.<br>• Recommendations of future controller and CPU architectures to leverage available technologies.<br>• Product suggestions</p>
Idea Notes:
Update Idea