BEYOND A COMMON OPERATING ENVIRONMENT
Tis architecture goes a long way in facilitating
system interoperability.
However, proper integration of advanced C4ISR/EW devices requires additional VICTORY specification. For example, the
VICTORY standard must be
modified to include an RF bus as well as a precision timing distribution capability. VICTORY is currently limited to intra- vehicle data exchange, and it needs to be extended to inter-vehicle networking so that it can support collaboration, coordination and distributed processing across multiple
vehicles LOOKING AHEAD AT THE COE
The premise of the COE is a common set of IT standards and architecture that will support the Army’s modernization of network and other capabilities for Soldiers on the battlefield. Here, a Soldier pulls security during a patrol Dec. 2, 2012, near Forward Operating Base Shank in Logar province, Afghanistan. (U.S. Army photo by SPC Alex Kirk Amen, 115th Mobile Public Affairs Detachment)
in support
of C4ISR/EW capabilities. Tis will de-conflict missions and reduce the SWAP-C of
each vehicle. VICTORY
addresses tactical vehicles, but the COE addresses all tactical platforms; standards must be developed for networking on dismounts as well as airborne and fixed platforms.
hardware components also need to
be specified, such as digital interfaces for RF receivers, transmitters, sensors and amplifiers.
SHARING COMPONENTS Te
Communications – Electronics
Research, Development and Engineer- ing Center (CERDEC) of the U.S. Army Research, Development and Engineer- ing Command is working on sharing components among C4ISR/EW systems.
CERDEC is demonstrating several capabilities with common components across EW and communications systems, as well as working with Project Manager (PM) Electronic Warfare of Program Executive Office Intelligence, Electronic Warfare and Sensors (PEO IEW&S) on open architectures
ing architecture for EW. Concurrently, CERDEC supports PEO Command, Control and Communications – Tactical
74 Army AL&T Magazine April–June 2013
(PEO C3T) in communication systems architectures.
Te current COE effort began with the Vehicle Integration for C4ISR/EW Interoperability (VICTORY) initiative, whereby specifications are part of the real- time, safety-critical CE; they define data bus architecture and services to enable the networking of C4ISR/EW equip- ment onboard a vehicle. CERDEC leads several efforts in VICTORY standards and is actively investigating and develop- ing modifications that support sharing of RF components.
CERDEC is also leveraging two Army programs of
and network-
Tier Networking Vehicular Radio and PEO IEW&S’ Multi-Function Electronic Warfare—to demonstrate a SWAP-C reduction for both systems by sharing amplifiers and antennas.
record—PEO C3T’s Mid-
Beyond C4ISR/EW interoperability for vehicles, CERDEC is researching common software architectures and devel- opment environments for communication and EW waveforms using a common set of hardware. (See Figure 2.)
Software architectures also offer many options. A top option for C4ISR/EW capabilities is
cations Architecture (SCA), developed through the Joint Tactical Radio System program to provide an open framework that describes the hardware and software interfaces for software-defined radios.
Specifications support only communi- cation requirements; however, today’s operational environment requires the simultaneous usage of EW, communi- cation and other C4ISR systems. Many C4ISR/EW systems have been designed under a proprietary architecture; design- ing a nonproprietary, open architecture that supports simultaneous usage of these
the Software Communi-
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 |
Page 145 |
Page 146 |
Page 147 |
Page 148 |
Page 149 |
Page 150 |
Page 151 |
Page 152 |
Page 153 |
Page 154 |
Page 155 |
Page 156 |
Page 157 |
Page 158 |
Page 159 |
Page 160 |
Page 161 |
Page 162 |
Page 163 |
Page 164 |
Page 165 |
Page 166 |
Page 167 |
Page 168
