WHAT'S ON THE HORIZON FOR LYNX?
It always irks me when a company acquires another one and promptly announces that nothing will change. Of course, it will! It is simply a case of when and how much. We just passed the month milestone since our acquisition by OceanSound Partners was announced to the industry and it is exactly one month since Tim Reed was announced as taking the helm.
Given this backdrop, I thought it as good point to share (such that I can do in the public domain) some of the initial observations I have noted. On one hand, nothing has changed. Lynx has focused on delivering operating systems, hypervisors, and software frameworks that simplify the way mission critical systems are developed, certified, and deployed. You will see a more maniacal focus on those use cases going forward.
I see that the “Software Defined Anything” momentum provides opportunities across a diverse set of applications in Military, Aerospace, and Federal sectors. The need to develop resilient, safe, and secure edge software at a fraction of the current cost and lead time is requiring our customers to change their approach. Outside our areas of focus, we continue to read about the impact of systems that are not delivered with a high enough level of quality. Companies' reputations are at risk, and sometimes the consequence of failure is that organizational changes are made at the very top. These pressures are compounded by the well-publicized challenge of the lack of skilled workers facing a range of industries including Defense. Our sense is that the markets where Lynx focusses are going be impacted more significantly than others in this regard. While the prior article focused on supply chain issues causing to delays to the assembly and shipment of existing systems, the same problem exists in the engineering teams that are creating the next great thing. Advances in technology will, we feel, will be critical to driving improvements here.
WHAT DOES THIS MEAN IN PRACTICAL TERMS?
EMBRACING "OPEN"
Lynx focused on POSIX from the get-go. We embrace standards like ARINC and FACE APIs that help our customers avoid lock in. You will see more of this in Lynx’s future.
EMBRACING "NEW" (DEVELOPMENT PATTERNS)
Customers often need to create and test software well ahead of hardware availability. Lynx has started to offer support of virtual platforms such as QEMU but needs to, and will do, more in this area. We see customers embracing digital twin technology to test complex functionality well ahead of first flights of new airframes. This is complemented by more continual development/test methodologies which have been harnessed for some time in some industries but which, we believe, will be key to addressing some of the cost and time pressures our customers are facing.
EMBRACING "GROWTH"
There are signs of growth in all sorts of areas if you are looking for them. The passing of the CHIPS act this month is one recent example. The share of semiconductor manufacturing has, according to the Semiconductor Industry Association, dropped from 37% back in the 1990s down to 12% today. This is much more than new wafer fabs in Ohio and Arizona. We are seeing new “in America, (primarily) for America” development activity. I like this list (it isn’t complete, but it is pretty good) of non-traditional semiconductor companies that was published this month. I am convinced that this list with include companies from the military and aerospace industries inside the next three years. There will all types of accelerators for artificial intelligence and very specific security functionality to avoid reverse engineering and system compromises. Lynx wants to be a critical ecosystem partner that helps this technology be harnessed into secure, connected platforms on land, sea, and air.
Exciting times ahead! I promise to share more over the coming months.