Family of Special Operations Vehicles Open Topic

The automotive digital cliff is fast approaching. With the acceleration of increased vehicle computing complexity will come a corresponding reduction in Non-Standard Commercial Vehicles (NSCV) capabilities. In the NSCV’s current form, the Original Equipment Manufacturer (OEM) Armorer is forced to solve significant engineering hurdles to maintain the functionality of the NSCV each year. These engineering hurdles are exacerbated due to the limited access to the OEM Engine Control Unit (ECU) and Vehicle Electronic Architecture (VEA). Today, operators require more control over NSCV systems. Raglan’s ‘Open’ VEA solution for SOCOM is key to overcoming the cascading control issues stemming from SOCOM’s lack of influence over Toyota’s engineering decisions. Following a successful Phase II, the VEA technology solution developed by Raglan will be nested inside the SOCOM programmatic office to enable greater vehicular control and seamless future integrations/modifications. However today, should SOCOM choose to augment the NSCV systems, the OEM Armorer is often forced to ‘hack’ the VEA or develop inelegant engineering solutions. These, in turn, create operational and security risks for the warfighter. Operational risks are related to the inability to effectively control existing systems on the NSCVs and to integrate new technologies into the NSCVs, while the latter is related to SOCOM’s lack of control over the onboard vehicle hardware/software. Raglan will solve these various problems by developing a tested, proven, installed, and sustainable control solution, which could become the new standard for the Family of Special Operations Vehicles (FOSOV).