October 2021

State of Industry

How OEMs Can Better Prepare for Tomorrow’s World of Connected Vehicles

More than 95% of the vehicles would feature connectivity (ethernet, cybersecurity, real-time updates) by the end of 2030. More than 50% of such vehicles would be entirely electric, and more than 60% of the customers would prefer switching OEMs based on the feature-laden autonomy being facilitated.  The likelihood of such a tremendous shift reminds us of the time when wireless consumer electronics became the norm and gave wired devices a run for their money or the time when eCommerce snatched away the liberty of brick-and-mortar stores. But even these cannot come close to the influence that connected vehicle Industry 4.0 will have on the way we go about manufacturing, distribution, and maintenance of automobiles.  In fact, the shift is already happening with the human-machine interface (HMI) becoming the new front end and vehicle control moving to the cloud-based solutions. Considering the relatively acute market differentiation possibilities but equally vaster opportunities to thrive, how can Original Equipment Manufacturers (OEM) prepare for a data-driven era of connected vehicles? Let’s find out.  Software-first Ideology Software, as opposed to the standard design-first philosophy, will embark on its journey as the pivotal market differentiator, and rightly so. The intricate connectivity powered by IoT devices and facilitated by high-grade ethernet will make it essential for the OEMs to manufacture enhanced powertrains capable of striking a balance between the go-to driving philosophy and the changing market.  On the microscopic scale, the OEMs will have to adhere to the following: Burkacky et al., from McKinsey Center for Future Mobility, state that a vertical technology stack could very well be the answer to “customer-facing functions” and will present opportunities for “developers to focus on differentiation” and OEMs to “rely on best-in-class hardware implementations, such as chips for AD.” Integration-first Approach In 2018, Eric Taub, while writing for New York Times, expressed his concerns over the non-integration of carmakers and software giants. He argued that the in-dash navigation systems are not as adept as those on one’s smartphone. Although Taub’s views didn’t necessarily pertain to the case for connected vehicles, they certainly reflected the conundrum that (is and) could trouble the OEMs soon.  In the past, too, OEMs have had to move from their in-built applications to those from service providers. The integration of Apple CarPlay is one such example that demonstrates the vitality of moving forward with an all-inclusive approach.  Actually, there’s no reason why an OEM wouldn’t. Software product manufacturers and cloud giants like Google, Amazon, Microsoft, and Apple have already made their name for user-centric applications. Why not leverage them for good? In fact, their omnipresence is an opportunity to attract and sustain consumers by facilitating an exceptionally improved user experience. To that end, integration-first is a preparation for the OEMs to establish absolute control over the connected vehicles market.  Future-proofing Philosophy Although the OEMs are aware of the market disruption headed their way, they must remain loyal to their own strategy by being future-proof. In other words, OEMs must focus on incorporating better connectivity standards to be able to secure the cloud tokenization of vehicle control logic. Specifically, the OEMs will have to focus on: From the management perspective, OEMs must: Accelerate the design phase in order to make the product suitable for both legacy and new cars/vehicles similarly.  Enterprise-Consumer Balancing Approach OEMs would be wise to consider their readiness in the face of an enterprise-first approach. It would be easier for the OEMs to take the leap if they are already on the right path.  The enterprises’ concerns are different from those of consumers. For example, while consumers would like more power, businesses would want greater flexibility. While consumers would like predictive maintenance of their vehicles, companies would want to get more done with fewer resources.  Likewise, customers and businesses differ a bit in other aspects such as security, reliability, and governance. The data-driven era of connected vehicles will introduce points of convergence between the consumer and enterprise applications, and OEMs will have to be ready to expedite the same. For example:  The Road Ahead In a future-proof strategy for the connected vehicles market, OEMs will have to be cognizant of digital disruption on a global scale and move away from traditional business models. In their efforts towards that end, the car-makers must look at both the automotive industry and adjacent verticals as opportunities to breed stakeholder solutions and create long-lasting customer relationships. 

Education

How Embedded and Software Testing are Different (and Why you Need Embedded Experts for that)

Today almost every product – be it a vehicle or high-tech medical equipment – works on embedded systems. Embedded systems are made up of tightly coupled hardware and software. So, if we take an example of a train with an automatic door, the software controls when the door opens and closes. Trends such as the Internet of Things (IoT), connected devices, and self-driving vehicles have further increased the demand for embedded systems. Almost 90% of processors are a part of embedded systems. The market size of embedded systems is expected to reach $116.2 billion by 2025. Given how critical embedded systems are in today’s world, companies need to invest in embedded testing. Embedded testing enables companies to test the software and hardware of embedded solutions. It helps companies identify and fix bugs in the hardware and software of critical systems and increases their chances of receiving the required certifications. Most importantly, considering that embedded systems are used for life-saving and mission-critical purposes, testing has to be done carefully. A single miss could pose a threat to someone’s life too. Hence, companies must remember that it’s very different from software testing and approach it accordingly. How are Embedded Testing and Software Testing Different? Embedded testing is quite different from software testing. Types of testing To begin with, software testing is limited to the software only. In embedded testing, the testing team needs to test both the software and the hardware of the system. Software testing mainly happens on client-server, web, and mobile-based applications. In software testing, companies do different types of tests such as accessibility, acceptance, integration, automated, black-box, and many more. Embedded testing goes beyond the software. In fact, it is done mainly on hardware. Software testing tests the functionalities of the applications, while embedded testing is focused on the hardware’s behavior. This doesn’t mean that software testing is sidelined or deprioritized in embedded testing. What it means is that the dependency on hardware is more. Product launch In the modern software development model, software testing is done along with development. So, the bugs are identified and fixed at an early stage. It helps the developers to build a better quality and secure product by design. This also helps the companies to launch the product quickly as development and testing happen simultaneously. In some cases of embedded testing, the software cannot be tested until the hardware is ready. Sometimes the custom tools are unavailable. The testers are compelled to wait till the late stages to test the product. The tight coupling of software and hardware might also lead to product launch delays. Bug fixing Another difference is that the bugs can be easily reproduced in software testing to allow testers to identify them and fix them confidently. However, the same method cannot be followed in embedded testing as the events have to be reproduced on the software and hardware level. The testers need to test every defect at a deeper level to find out the exact source. They have to collect more data to analyze the defects and may also have to alter the systems intentionally to fix the bugs. Testing method Unlike software testing, embedded testing relies mainly on manual testing. Considering that in embedded testing, both hardware and software are tested, automation testing could become complicated. However, it does not mean that the testing process cannot be automated. Testers could use modular and extensible testing environments to prevent any changes in the common hardware and software interface. In fact, testers could use specific automated testing tools that support the unique use case of embedded testing. This can help them perform embedded testing more efficiently and reduce the chances of errors that could potentially lead to life-threatening situations         Conclusion It’s clear that embedded testing has to be done differently to ensure that it is secure and functional. The skill sets would differ. Hence, companies need to work with a testing team that has expertise in testing embedded systems and ensuring that they are safe and compliant with the safety guidelines. It’s important to partner with a company that has specialized tools to test embedded systems. They must also follow the protocols and policies strictly. At Intellore, we help companies in designing, developing, and testing embedded products. We also offer independent testing services that are tailor-made to the company’s business needs to ensure their compliance and safety. To know more, contact us.

Scroll to Top