The automotive software development industry is undergoing a major shift as more and more OEMs are adopting a Software Defined Vehicle (SDV) architecture. Many high-tech companies, OEMs, suppliers, IT services, government agencies, contract houses, etc., have invested billions of dollars into SDV and features. As a result, automotive software is becoming more complex, and OEMs are looking at non-traditional suppliers such as startups and Silicon Valley as sources for new applications. This has led to a need for improved interaction between electronic control units (ECUs) and the increased use of domain controllers. Centralizing features such as EPS and Braking to a High-Performance Computer (HPC) in this new environment presents numerous new challenges and hurdles. EPS/SbW software is an example of an existing actuator application that can be controlled from a domain controller in the vehicle. EPS/SbW software executed from a domain controller can provide the same level of performance as the same algorithm residing in the EPS/SbW actuator itself while allowing for greater interaction with other applications that may reside on the HPC. This presents challenges with lag times in communication and processing between the HPC and the EPS/SbW unit. Also, when systems are provided by different suppliers within vehicles, it becomes difficult to exchange information across ownership silos. This paper takes a deeper dive into the challenges and potential solutions of providing an algorithm such as EPS/SbW on a domain controller in a SDV in the form of software as a product as well as solving these challenges while accounting for the OEMs’ desire to execute software functions from an HPC. We present our own solutions in the context of what is currently being considered in the industry.