REUSABLE AND REFRESH-ABLE


FIGURE 1


Service- oriented,


architecture- based common mechanisms for sharing data, remotely controlling subsystems, handling faults and securing (cybersecurity) subsystems.


In-vehicle network of multiple networking protocols with open interfaces.


Plug-in approaches for


multiple communication protocols and in-vehicle network.


GCIA uses open standard specifications developed by PEO GCS for integrating C4ISR (command, control, computers, communications and intelligence, surveil- lance and reconnaissance) and electronic warfare (EW) devices. Te specifications are known as VICTORY—Vehicular Integration for C4ISR/EW Interopera- bility. Different vendors can add, modify, replace, remove or support warfighter capabilities through GCIA’s standard- ized interfaces throughout the life cycle of a vehicle platform.


Operational state-aware infrastructure services


and applications with interfaces.


Shared hardware resources (e.g., computing, display and sensors).


Uninterrupted situational awareness and


communication faults handling.


Te reusable artifacts of GCIA, such as government-owned software, specifica- tions and implementation guides, can add value to other Army vehicle programs for developing or enhancing their information technology capabilities with lower-cost and low-risk options.


PRINCIPLES OF OPEN VEHICLE SYSTEMS


PEO GCS’ Common Infrastructure Architecture, the key points of which are shown here, stresses common hardware and software that can be reused across platforms and that make it easier for different combat platforms to communicate. (Graphic by U.S. Army Acquisition Support Center and PEO GCS)


A system is modular when it is decom- posed into multiple components that may be easily rearranged, replaced or inter- changed in various configurations. A loosely coupled system has no or mini- mal dependency on components of other systems to carry out its functions, and changing one system will not impact other systems. A cohesive system carries out a single, well-defined function and


contains only the parts that are required to carry out that single function.


GCIA exhibits all the characteristics of an open systems architecture. It creates a common approach across all combat vehi- cle platforms to support new innovations and technologies, promote competition, decrease costs and shorten integration timelines.


KEY TENETS, BENEFITS AND USES Before GCIA, for combat vehicle programs such as Stryker, Bradley or a tank, each warfighter capability would provide its own specific infrastructure functions with proprietary interfaces for a military vehicle integration. Tese unique functions increase the complexity of integration, and they add a significant amount of integration and testing time to the acquisition program. Tis would impact budgets and schedules for Army acquisition programs. However, GCIA provides common system-level infra- structure capabilities such as shared display and computing resources, data sharing, common fault handling, soft- ware configuration management and a common data-communication network that all the warfighter capabilities can use instead of having their own specific infra- structure capabilities. Te infrastructure is analogous to a robust highway with strategically placed standard services


66


Army AL&T Magazine


October-December 2018


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144