Joseph Zubor

This program was built using a new vehicle network design called FNV2 and included about 100 new or updated software features and 15 new ECUs. It was the first to use the Agile Hybrid method for developing ECU requirements and software models, which were part of suppliers' engineering SOWs. We used Jira to manage the software development process and modify GPDS milestone deliverables. We also conducted early EBB testing for the first time.

Managing this program had its challenges. I needed to teach different teams about changes to the GPDS deliverables and timelines and how to use Jira to manage their tasks. Many software features were still in the R&D stage and for consideration in planning. Additionally, much of the software for EBB testing was not ready for functional testing.

By increasing issue awareness and engaging management, I guided teams in delivering software for vehicle prototype builds and starting integration testing on the MVP. Keeping teams updated on software deliveries during testing helped us achieve approved software to meet J1 production requirements.

I managed a team of general contractors and specialists to build and renovate several switching facilities—specifically in Vernon Hills, Illinois; Kentwood, Michigan; and Des Moines and Davenport, Iowa—from initial architecture and engineering through facility signoff.

I developed strategic project plans to facilitate the installation and integration of mobile switching center subsystems, which included HVAC, fire suppression, DC power plants, and wireless communications equipment. These efforts were aligned with customer requirements and Bellcore facility specifications.

Additionally, I staffed and led a team of network engineers, software developers, integrators, and radio frequency drive testers to create, deploy, and calibrate customer-specific software applications within the cellular network, ensuring they met all customer specifications.

This program was developed using 90% carry-over, software-enabled features and did not require any new ECUs, only minor modifications to existing software. Due to its reduced complexity, it was an ideal candidate for piloting a development EBB. This approach provided ECU functional owners and suppliers with a collaborative space to develop more robust software that could meet aggressive timelines, ultimately expediting the program by eliminating one year of development time.

I worked in a small cross-functional team to identify and deliver the necessary software and ECU hardware, modify the network identifiers and message list, and prepare all associated wiring harnesses to build the breadboard in time to begin functional software development. Managing the program with the bench setup proved to be very beneficial, as we were able to identify bugs early while integrating the module configuration into the network. This also improved suppliers' software delivery, as they could perform more thorough product validation.