![]() GCIA’s complete hardware and software ecosystem definition represents a paradigm shift on how to establish a vehicle architecture by defining an overall integrated solution. Going forward, ground-combat vehicle solutions will need to support GCIA, which has the needed specificity while leveraging SOSA and CMOSS. The ability to move applications and functions, using distributed network resources, to any spot in the vehicle will provide an unprecedented new level of fault resiliency compared to today’s vehicle architectures, where there is very little redundancy built in. Capabilities can be hosted anywhere on the platform because all of the resources will be networked, so solutions developed for GCIA-based applications will be transportable between different hardware elements, not just within the platform, but platform to platform, from compute instance to compute instance. System designers can use the specified building blocks and develop their software on the very same hardware platform that all other GCIA-compliant suppliers are using GCIA defines the internal vehicle network (IVN). ![]() The GCIA network can accommodate very-low-latency paths while providing determinism. Each box also has its own software that must be qualified and communicate with the next layer of software on the vehicle network: All of this adds time and program risk. New functions often arrive in their own boxes that host their own computers and need space on an already crowded vehicle. This stricture forces designers to build from a much smaller set of building blocks from the beginning in order to deliver the benefits of greatly reduced time to field new technology and tech refreshes for ground combat vehicles that GCIA promises. While GCIA looks to SOSA for system profile definitions and VITA hardware standards, it limits the approved use to only a handful of SOSA profiles and narrow subset of hardware standards. smart), security (multilevel security boxes vs. In addition, GCIA directs the use of Intel hardware and Linux software and defines the types of displays (dumb vs. For example, GCIA defines a version of Ethernet that supports TSN (time-sensitive network) standards for safety-critical data movement on the standard core network. Most importantly, GCIA is concerned with how the network moves and shares data to support all the resources needed to host the different functions on a ground-combat vehicle. While CMFF focuses on the C4ISR piece of the vehicle infrastructure (communications and mission management), GCIA focuses on the requirements to enable a core compute networked infrastructure that will enable a system designer to simply “plug in” all the desired capabilities. ![]() The Army has developed two new standards – the PEO Aviation and PEO [Ground Combat Systems) GCS’s CMFF (CMOSS Mounted Form Factor) and the PEO GCS’s GCS Common Infrastructure Architecture (GCIA) – to define a detailed and comprehensive architecture for the desired interoperability, adaptability, and technology movement. ![]() While it makes use of many of the same standards as the CMOSS standards, such as OpenVPX, it became clear that these standards didn’t go far enough to satisfy the Army’s vision for combat vehicles. When the SOSA Technical Standard effort began, it focused initially on airborne sensor systems. The next step was CMOSS, which – in its effort to define the suite of standards for building the desired infrastructure and network – embraced the VICTORY, MORA, and OpenVPX standards. That reality resulted in hardware/software convergence which explored what such a solution set might look like, such as standardizing on 3U OpenVPX, as a way of driving a modular enough solution that could have a significant impact on interoperability. While the VICTORY standard helped make some progress and created some excitement, the need to converge on a more focused solution set soon became apparent. Army has long pursued a standardized infrastructure and architecture for ground-combat vehicle hardware and networking. ![]() 1/3 Save Starter Kit image: Curtiss-Wright ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |