VICTORY_Architecture_A_DistroA_20190402.pdf

VEHICULAR INTEGRATION FOR C4ISR/EW

INTEROPERABILITY (VICTORY) ARCHITECTURE

Version A April 2, 2019

Released by the VICTORY Standards Support Office vsso@victory-standards.org

Distribution Statement A

Approved for public release. Distribution is unlimited.

VICTORY Architecture Version A April 2, 2019 ii

TABLE OF CONTENTS

1. Scope .....................................................................................................................................................1 1

1.1 Acronyms and Abbreviations .......................................................................................................... 2 2

1.2 Architecture Background and Terminology .................................................................................... 5 3

1.3 VICTORY Compliance ................................................................................................................... 8 4

1.3.1 Architecture Compliance and Conformance Concepts ............................................................8 5

1.3.2 Component Type Compliance and Conformance Concepts ....................................................9 6

1.3.3 VICTORY Compliance Statements .......................................................................................10 7

2. Introduction .........................................................................................................................................11 8

2.1 Motivation for a New Architecture ................................................................................................ 11 9

2.2 VICTORY Goals ........................................................................................................................... 11 10

2.3 Overall Approach ........................................................................................................................... 13 11

3. VICTORY Architecture Overview .....................................................................................................15 12

3.1 VICTORY Tenets .......................................................................................................................... 15 13

3.1.1 Data Bus-Centric Design ........................................................................................................15 14

3.1.2 On-the-Wire Network Interfaces ............................................................................................16 15

3.1.3 Shared Hardware Components ...............................................................................................17 16

3.1.4 Standard Open Interfaces and APIs .......................................................................................17 17

3.1.5 Shared PNT Services ..............................................................................................................17 18

3.1.6 Shared Information Assurance Components ..........................................................................18 19

3.2 VICTORY Data Bus Context ........................................................................................................ 19 20

3.3 VICTORY Data Bus Functionality ................................................................................................ 21 21

3.3.1 Transport Data ........................................................................................................................21 22

3.3.2 Provide Information Assurance ..............................................................................................21 23

3.3.3 Provide Shared Hardware Infrastructure ................................................................................22 24

3.3.4 Provide Shared PNT ...............................................................................................................22 25

3.3.5 Enable Integration of Modular Systems .................................................................................22 26

3.3.6 Enable Interfaces to Non-Modular Systems ...........................................................................22 27

4. VICTORY Component Types and Interfaces .....................................................................................24 28

5. Common Functions .............................................................................................................................30 29

5.1 Data Transport ............................................................................................................................... 30 30

5.2 Auto-Discovery .............................................................................................................................. 30 31 iii

5.3 Health Reporting ............................................................................................................................ 31 32

5.4 Common Management Functions .................................................................................................. 31 33

5.5 Activity Marking ............................................................................................................................ 32 34

5.6 Security Logging ............................................................................................................................ 33 35

5.7 Incident Response .......................................................................................................................... 33 36

6. VICTORY Data Bus Architecture ......................................................................................................35 37

6.1 Infrastructure .................................................................................................................................. 35 38

6.1.1 Switch .....................................................................................................................................36 39 Switch Data Transport Interface .................................................................................................... 36 40 Switch Management Interface ....................................................................................................... 36 41

6.1.2 Low Latency Switch ...............................................................................................................36 42 Low Latency Switch Data Transport Interface .............................................................................. 36 43

6.1.3 Generic End Node ..................................................................................................................36 44 Generic End Node Data Transport Interface .................................................................................. 37 45 Generic End Node Management Interface ..................................................................................... 37 46

6.1.4 Shared Processing Unit ..........................................................................................................37 47 Shared Processing Unit Data Transport Interface .......................................................................... 38 48 Shared Processing Unit Management Interface ............................................................................. 38 49 Shared Processing Unit Platform API ............................................................................................ 38 50 Direct Attached Storage Encryption Management Interface ......................................................... 39 51

6.1.5 Network Attached Storage .....................................................................................................39 52 Network Attached Storage Device Interface ................................................................................. 39 53 Network Attached Storage Management Interface ........................................................................ 39 54 Network Attached Storage Encryption Management Interface ..................................................... 39 55

6.2 Shared PNT .................................................................................................................................... 40 56

6.2.1 Time Synchronization Service ...............................................................................................40 57

Time Synchronization Service Data Interface ............................................................................... 40 58 Time Synchronization Service Management Interface .................................................................. 40 59

6.2.2 Position, Orientation, and Direction of Travel Services ........................................................40 60 Position, Orientation, and Direction of Travel Service Data Interfaces ........................................ 41 61 Position, Orientation, and Direction of Travel Service Management Interfaces ........................... 41 62

6.2.3 GPS Receiver Service ............................................................................................................41 63 GPS Receiver Service Device Interface ......................................................................................... 41 64 iv

GPS Receiver Service Management Interface ............................................................................... 41 65

6.3 System Management ...................................................................................................................... 41 66

6.3.1 VDB Management Service .....................................................................................................42 67 VDB System Management Interface ............................................................................................. 42 68

6.3.2 VICTORY System Configuration Description ......................................................................43 69 VDB Configuration Description .................................................................................................... 43 70 Information Assurance Configuration Description ........................................................................ 44 71 C4ISR/EW Systems Configuration Description ............................................................................ 44 72 Platform Systems Configuration Description ................................................................................ 44 73

6.4 Recording and Logging .................................................................................................................. 44 74

6.4.1 Mission Recorder ...................................................................................................................44 75

Mission Recorder Data Interface ................................................................................................... 45 76 Mission Recorder Management Interface ...................................................................................... 45 77

6.4.2 Data Logger ............................................................................................................................45 78 Data Log Retrieval Interface .......................................................................................................... 46 79 Data Logger Management Interface .............................................................................................. 46 80

7. Information Assurance Architecture ...................................................................................................47 81

7.1 Access Control ............................................................................................................................... 47 82

7.1.1 Authentication Service ...........................................................................................................47 83 Authentication Management Interface ........................................................................................... 47 84

7.1.2 Policy Decision Service .........................................................................................................47 85 Policy Decision Management Interface ......................................................................................... 48 86

7.1.3 Policy Enforcement Service ...................................................................................................48 87 Policy Enforcement Management Interface ................................................................................... 48 88

7.1.4 Policy Store Service ...............................................................................................................48 89 Policy Store Management Interface ............................................................................................... 48 90

7.1.5 Attribute Store Service ...........................................................................................................48 91 Attribute Store Management Interface ........................................................................................... 48 92

7.2 Data Integrity and Confidentiality ................................................................................................. 49 93

7.2.1 Data Signing Service ..............................................................................................................49 94

7.2.2 Signed Data Verification Service ...........................................................................................49 95

7.2.3 Data at Rest Encryptor ...........................................................................................................49 96

Data at Rest Encryptor Management Interface .............................................................................. 49 97 v

7.2.4 Inline Network Encryptor .......................................................................................................49 98 Inline Network Encryptor Transport Interface ............................................................................... 49 99 Inline Network Encryptor Management Interface ......................................................................... 50 100

7.3 Host and Network Protection ......................................................................................................... 50 101

7.3.1 Host-Based Antivirus .............................................................................................................50 102

Host-Based Antivirus Management Interface ................................................................................ 50 103

7.3.2 Host-Based Firewall ...............................................................................................................50 104

Host-Based Firewall Management Interface .................................................................................. 51 105

7.3.3 Intrusion Detection and Prevention System ...........................................................................51 106

Intrusion Detection and Prevention System Management Interface .............................................. 51 107

7.3.4 Network Firewall ....................................................................................................................51 108

Network Firewall Management Interface ...................................................................................... 51 109

8. C4ISR/EW Systems Architecture .......................................................................................................53 110

8.1 Audio Communications ................................................................................................................. 53 111

8.1.1 Legacy Intercom System ........................................................................................................53 112

Legacy Intercom System Data Interface ........................................................................................ 53 113 Legacy Intercom System Management Interface ........................................................................... 54 114

8.1.2 Legacy Radio ..........................................................................................................................54 115 Legacy Radio Data Interface .......................................................................................................... 54 116 Legacy Radio Management Interface ............................................................................................ 54 117

8.1.3 Digital Audio Source ..............................................................................................................54 118 Digital Audio Source Data Interface .............................................................................................. 54 119 Digital Audio Source Management Interface ................................................................................ 55 120

8.1.4 Audio Announcement Source ................................................................................................55 121 Audio Announcement Source Data Interface ................................................................................ 55 122 Audio Announcement Source Management Interface ................................................................... 55 123

8.2 Video and Imagery Situational Awareness .................................................................................... 55 124

8.2.1 EO/IR Sensor ..........................................................................................................................56 125

EO/IR Sensor Management Interface ............................................................................................ 56 126

8.2.2 EO/IR Encoder .......................................................................................................................56 127

EO/IR Encoder Data Interface ....................................................................................................... 56 128 EO/IR Encoder Management Interface .......................................................................................... 57 129

8.2.3 Gimbal ....................................................................................................................................57 130 vi

Gimbal Data Interface .................................................................................................................... 57 131 Gimbal Management Interface ....................................................................................................... 57 132

8.3 Off-Vehicle Network Interfacing ................................................................................................... 57 133

8.3.1 Router .....................................................................................................................................57 134

Router Data Interface ..................................................................................................................... 58 135 Router Management Interface ........................................................................................................ 58 136

8.3.2 Network Radio .......................................................................................................................58 137 Network Radio Data Transport Interface ....................................................................................... 58 138 Network Radio Management Interface .......................................................................................... 58 139

8.3.3 Off-Vehicle Network Gateway ..............................................................................................59 140 Off-Vehicle Network Gateway Data Interface .............................................................................. 60 141 Off-Vehicle Network Gateway Management Interface ................................................................. 60 142

8.4 Modular RF Signal Resources ....................................................................................................... 60 143

8.4.1 MORA Overview ...................................................................................................................60 144

MORA Low Latency Bus .............................................................................................................. 61 145 MORA Top-Down Perspective ...................................................................................................... 62 146 MORA Signal Resource ................................................................................................................ 63 147 MORA Processing Resource ......................................................................................................... 64 148 MORA Transitional Implementation ............................................................................................. 64 149

8.4.2 Modular RF Signal Resources Component Types .................................................................65 150

8.4.3 MORA Device ........................................................................................................................66 151

MORA Device Management Interface .......................................................................................... 67 152

8.4.4 MORA Signal Resource Manager ..........................................................................................67 153

MORA Signal Resource Management Interface ........................................................................... 67 154

8.4.5 MORA Signal Port Manager ..................................................................................................67 155

8.5 Radio Frequency Processing .......................................................................................................... 67 156

8.5.1 RF Direction Finding Engine .................................................................................................68 157

RF Direction Finding Engine Data Interface ................................................................................. 69 158 RF Direction Finding Engine Management Interface .................................................................... 69 159

8.5.2 RF Geolocation Engine ..........................................................................................................69 160 RF Geolocation Engine Data Interface .......................................................................................... 69 161 RF Geolocation Engine Management Interface ............................................................................. 70 162

8.5.3 RF Spectrum Sensor ...............................................................................................................70 163 vii

RF Spectrum Sensor Data Interface ............................................................................................... 70 164 RF Spectrum Sensor Management Interface ................................................................................. 70 165

8.5.4 RF Signal Detector .................................................................................................................70 166 RF Signal Detector Data Interface ................................................................................................. 71 167 RF Signal Detector Management Interface .................................................................................... 71 168

8.5.5 RF Signal Generator ...............................................................................................................71 169 RF Signal Generator Data Interface ............................................................................................... 71 170 RF Signal Generator Management Interface ................................................................................. 71 171

8.5.6 Electronic Warfare System .....................................................................................................71 172 Electronic Warfare System Data Interface ..................................................................................... 72 173 Electronic Warfare System Management Interface ....................................................................... 72 174

9. Platform Systems Architecture ............................................................................................................73 175

9.1 Vehicle Systems Interfacing .......................................................................................................... 73 176

9.1.1 Automotive System ................................................................................................................74 177 Automotive System Data Interface ................................................................................................ 74 178 Automotive System Management Interface ................................................................................... 74 179

9.1.2 Power Distribution System .....................................................................................................75 180 Power Distribution System Data Interface .................................................................................... 75 181 Power Distribution System Management Interface ....................................................................... 75 182

9.1.3 Mechanical Articulation Joint ................................................................................................75 183 Mechanical Articulation Joint Data Interface ................................................................................ 76 184 Mechanical Articulation Joint Management Interface ................................................................... 76 185

9.2 Lethality Systems Interfacing ........................................................................................................ 76 186

9.2.1 Weapon System ......................................................................................................................76 187

Weapon System Data Interface ...................................................................................................... 77 188 Weapon System Management Interface ........................................................................................ 78 189

9.2.2 Targeting System ....................................................................................................................78 190 Targeting System Data Interface .................................................................................................... 79 191 Targeting System Management Interface ...................................................................................... 79 192

9.2.3 Remote Weapon Station .........................................................................................................80 193 Remote Weapon Station Data Interface ......................................................................................... 81 194 Remote Weapon Station Management Interface ........................................................................... 81 195

9.3 Protection Systems Interfacing ...................................................................................................... 81 196 viii

9.3.1 Threat Detection System ........................................................................................................81 197 Threat Detection System Data Interface ........................................................................................ 82 198 Threat Detection System Management Interface ........................................................................... 82 199

9.3.2 Active Protection System .......................................................................................................82 200 Active Protection System Data Interface ....................................................................................... 82 201 Active Protection System Management Interface .......................................................................... 82 202

9.4 Logistics Systems Interfacing ........................................................................................................ 83 203

9.4.1 Vehicle Configuration Service ...............................................................................................83 204

Vehicle Configuration Service Management Interface .................................................................. 83 205

9.4.2 Vehicle Health and Usage Monitoring Service ......................................................................84 206

Vehicle Health and Usage Monitoring Service Data Interface ...................................................... 84 207 Vehicle Health and Usage Monitoring Service Management Interface ........................................ 84 208

9.5 Training Systems Interfacing ......................................................................................................... 84 209

9.5.1 Live Training Transformation Adapter ..................................................................................84 210

Live Training Transformation Adapter Data Interface .................................................................. 86 211 Live Training Transformation Adapter Management Interface ..................................................... 86 212

9.5.2 Lasing System ........................................................................................................................86 213 Lasing System Data Interface ........................................................................................................ 87 214 Lasing System Management Interface ........................................................................................... 87 215

9.5.3 Laser Detection System ..........................................................................................................87 216 Laser Detection System Data Interface .......................................................................................... 88 217 Laser Detection System Management Interface ............................................................................ 88 218

10. VICTORY Composition Guidelines ...............................................................................................89 219 220 221 ix

LIST OF FIGURES 222

Figure 1. Illustration of Architecture Compliance and Conformance .......................................................... 9 224 Figure 2. Open Standards Matrix ................................................................................................................ 12 225 Figure 3. VICTORY Data Bus Context ...................................................................................................... 19 226 Figure 4. VICTORY Data Bus Architecture Organization ......................................................................... 26 227 Figure 5. Information Assurance Architecture Organization ...................................................................... 27 228 Figure 6. C4ISR/EW Systems Architecture Organization .......................................................................... 27 229 Figure 7. Platform Systems Architecture Organization .............................................................................. 28 230 Figure 8. VICTORY Configuration Description Organization .................................................................. 28 231 Figure 9. MORA Top-Down Perspective ................................................................................................... 63 232 Figure 10. MORA Transitional RF System Top-Down Perspective .......................................................... 65 233

1. SCOPE 234

This document describes the Vehicular Integration for C4ISR/EW Interoperability (VICTORY) 235 Architecture, which provides a framework for integrating Command, Control, Communications, 236 Computers, Intelligence, Surveillance, and Reconnaissance (C4ISR) and Electronic Warfare 237 (EW) systems on military ground vehicles, and interfacing with the vehicle systems. The scope 238 of the VICTORY Architecture is within the vehicle platform. 239 This document describes the architecture, which consists of a set of system and component types, 241 their interfaces, and architectural patterns through which those system and component types can 242 be composed to create C4ISR/EW system designs on vehicular platforms. The architecture 243 creates a conceptual framework, but does not describe the technical details of the design 244 instantiations, systems, components, or interfaces. The technical details (e.g., specific 245 technologies chosen to implement the types and interfaces) are described in the VICTORY 246 Standard Specifications. In other words, the architecture identifies the conceptual entities 247 (system and component types, interfaces) and how they are integrated (structures and patterns), 248 and the standard specifications identify the technical attributes of some of the entities, namely 249 their interfaces. The standard specifications documentation is developed and matured by a 250 standards body, which consists of government stakeholders, manufacturers of components, 251 systems, vehicles, and system integrators. 252

1.1 Acronyms and Abbreviations 253

Table 1. Acronyms and Abbreviations 254

Acronym Definition

1PPS 1 Pulse Per Second

2D Two-Dimensional

3D Three-Dimensional

ABAC Attribute Based Access Control

ACERT Army Computer Emergency Response Team

ADC Analog-to-Digital Converter

API Application Programming Interface

APS Active Protection System

AS Attribute Store

BIT Built-In Test

C4ISR Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance

CAN Controller Area Network

CBM Condition Based Maintenance

CLOE Common Logistics Operating Environment

CM Configuration Management

CPU Central Processing Unit

CREW

Counter Radio-controlled Electronic Warfare -or- Counter RCIED Electronic Warfare CT Component Type

DAC Digital-to-Analog Converter

DAGR Defense Advanced GPS Receiver

DAR Data at Rest

DDS Data Distribution Service

DF Direction Finding

DFE Direction Finding Engine

DIFCUE Direct Fire/Indirect Fire CUE

DoD Department of Defense

DSP Digital Signal Processor

EO Electro-Optical

Acronym Definition

EO/IR Electro-Optical and Infrared

EPLRS Enhanced Position Location Reporting System

EW Electronic Warfare

FFT Fast Fourier Transform

FPGA Field-Programmable Gate Array

GFE Government Furnished Equipment

GLE Geolocation Engine

GPP General Purpose Processor

GPU Graphics Processing Unit

GPS Global Positioning System

IA Information Assurance

IDPS Intrusion Detection and Prevention System

IMU Inertial Measurement Unit

INE Inline Network Encryptor

INS Inertial Navigation System

IP Internet Protocol

IR Infrared

ITAS Improved Target Acquisition System

IVN In-Vehicle Network

LAN Local Area Network

LCOP Logistics Common Operating Picture

LOB Line of Bearing

LRAS3 Long-Range Advanced Scout Surveillance System

LT2 Live Training Transformation

MAC Media Access Control

MAPS Modular Active Protection System

MDM MORA Data Message

MILES Multiple Integrated Laser Engagement System

ML2B MORA Low Latency Bus

MLRF Micro-Laser Rangefinder

MORA Modular Open RF Architecture

NAS Network Attached Storage

NDA Non-Disclosure Agreement

NTP Network Time Protocol

OS Operating System

OSA Open Systems Architecture

OSI Open System Interconnection

PAN Personal Area Network

PNT Position, Navigation, and Timing

PDS Policy Decision Service

PDU Power Distribution Unit

PES Policy Enforcement Service

PHY Physical Layer

PS Policy Store

PSD Power Spectral Density

PTP Precision Time Protocol

QoS Quality of Service

RCD RF Conditioning and Distribution

RCIED Radio-Controlled Improvised Explosive Device

RCM Reliability Centered Maintenance

RF Radio Frequency

RHD Radiohead

RPG Rocket-Propelled Grenade

RWS Remote Weapon Station

SA Situational Awareness

SDR Software-Defined Radio

SoSE System of Systems Engineering

SPU Shared Processing Unit

STORM Small Tactical Optical Rifle Mounted

SWaP Size, Weight, and Power

SWaP-C Size, Weight, and Power and Cost

TES Tactical Engagement Simulation

TOW Tube-launched Optically-tracked Wire-guided

TPE Theater Provided Equipment

TTL

Transistor-to-Transistor Logic -or- Transistor-Transistor Logic

UI User Interface

USB Universal Serial Bus

VDB VICTORY Data Bus

VCL VICTORY Configuration Language

VCL ID VCL Instance Document

VHUMS Vehicle Health and Usage Monitoring Service

VICTORY Vehicular Integration for C4ISR/EW Interoperability

VISA Video and Imagery Situational Awareness

VoIP Voice over Internet Protocol

VRCU Vehicular Remote Control Unit (VRCU)

VSSO VICTORY Standards Support Office

WAN Wide Area Network

WESS Weapons Effects Simulation System

WMI Warfighter Machine Interface

WPAN Wireless Personal Area Network

1.2 Architecture Background and Terminology 255

Architecture, within the context of this document, is a conceptual framework consisting of a 257 common terminology, a set of modular functional entities that interoperate through interfaces, 258 and common structures, patterns, and rules to follow when instantiating and organizing the 259 modular entities to form system designs. 260 More concisely, an architecture defines a common glossary (well-defined terminology), a type 262 system (modules and interfaces), and system composition guidelines (common structures, 263 patterns, and constraints). 264 The VICTORY Architecture has been developed specifically for integrating electronics systems 266 in U.S. Army ground vehicles, and is therefore specific to the domain of electronics systems on 267 military ground vehicles. The VICTORY Architecture type system consists of a set of 268 component types and interfaces that are relevant to the kinds of electronic systems that are part of 269 or are integrated with these vehicles. 270

Although some of the component types may provide functionality that is commonly 272 implemented in either hardware or software, they should be thought of as conceptual as opposed 273 to tangible items. Their groupings in the architecture description are not meant to imply the same 274 breakdown and allocation of functions to physical and logical elements of a design. In other 275 words, architectural components A and B, with interfaces a, b, and c, may be implemented in 276 firmware on a single physical device in one design, and in software on multiple physical devices 277 in another design. Those systems could be considered functionally equivalent as long as the 278 interfaces are open and correctly implemented. 279 The VICTORY Architecture is not the same as a vehicle design or a vehicle system 281 implementation. A design is an instantiation of the architecture. In a design, technical choices 282 have been made to address the operational, functional, performance, and other types of 283 constraints and requirements for the system being developed. 284 A design is a plan that describes how a system will be constructed to implement a specific set of 286 functional and non-functional requirements. A design includes a set of design elements (physical 287 and logical components with physical and logical interfaces), a system mapping (allocation of 288 functionality to design elements), and a system organization (interrelation and interconnection of 289 design elements). Logical components are usually realized in software or firmware, and 290 implement a set of features defined by the architecture. Note that the features of the VICTORY 291 Architecture correspond to component types, which organize functionality with sets of 292 supporting interfaces. Logical components have logical interfaces to other logical components, 293 and implement a set of architectural interfaces. These support communication and management-294 related functions such as configuration, control, status reporting, or fault management. Physical 295 components and interfaces are hardware devices that can host the logical components and their 296 physical interconnections. In a design, the architectural components and interfaces have been 297 allocated to logical components and interfaces; and the logical components and interfaces have 298 been allocated to physical components and interfaces. In this document, the term component is 299 used to describe either a logical or physical component in the context of a system design or 300 implementation. The term artifact is used to describe a tangible entity implementing one or more 301 logical and/or physical components. 302 A physical design (or hardware design) is the physical view of a design. It includes a set of 304 physical components with their physical interfaces connected. A physical design is analogous to 305 a wiring diagram. In a physical design, the hardware components have been identified, choices 306 have been made about technologies, the interfaces have been chosen, and the connections 307 between interfaces have been defined. 308 A logical design (or software design) is the logical view of a design. It includes a set of logical 310 components (software) with their logical interfaces (messaging paths and application 311 programming interfaces [APIs]) connected. The logical components form applications, which 312 provide the functionality of the system. In a logical design, software components have been 313 identified, functionalities have been decided, and technology choices for implementation of the 314 software components and interfaces have been made. 315

The mapping of logical components to physical components and logical interfaces (messages and 317 APIs) to physical interfaces (wires, connections, and platform resources) is part of the design 318 process, and is called the system allocation. 319 As stated above, within the context of this document, an architecture defines a common glossary, 321 a type system (modules and interfaces), and system composition guidelines (common structures, 322 patterns, and constraints). The modules, which are called component types in VICTORY, 323 describe a set of functionality or behavior, but only in general terms, along with interfaces 324 necessary to support that functionality. The architecture does not define how the functionality is 325 to be implemented, identify the technical details of the interfaces, completely detail the behavior 326 of the components, or constrain how functionality is to be mapped to physical devices or 327 software components. The technical details of the component behaviors and interfaces are 328 defined in part by standard specifications, which leave some options open to be chosen during 329 the design process. The choices of hardware components, software components, performance, 330 and overall system design are defined in the system design specifications. Some technical details 331 are prescribed by the standard specifications, and others are left as choices for the designer of a 332 particular system. The line demarking where the architecture and specifications stop and where 333 the vehicle-specific design starts is important to the success of the architecture. If the component 334 and interface standard specifications are too rigid (over constrained), there is less flexibility in 335 designing systems. If they are too loose (under constrained) subsystems, and components 336 developed independently against the specifications will not interoperate when integrated. The 337 goal is for the standard specifications to be detailed and constraining enough that interoperability 338 between systems and components on the vehicle is achieved in most cases, while allowing for 339 flexibility for designers to support a wide range of system requirements. 340 Note: The VICTORY Architecture document concentrates on the first two elements of an 342 architecture; the common glossary, and the type system. It defines terms and a common lexicon, 343 and defines modular entities called component types, and their interfaces through which they 344 interoperate. Although this architecture document does identify a commonly used architectural 345 structure (the VICTORY Data Bus), and patterns that may be used when developing designs 346 (e.g., the adapter pattern), it does not completely provide the third element of an architecture; the 347 composition guidelines. Properly explaining implementation patterns, and in particular 348 constraints (rules), necessarily requires providing detailed design examples, which the authors of 349 this document determined should be put into a separate document. The VICTORY 350 Implementation Guide document will be a companion to the VICTORY Architecture document. 351 It will explain in detail the VICTORY composition guidelines (the third leg of an architecture), 352 and provide general guidance to designers and implementers for how to use VICTORY 353 Component Types to design and implement systems to meet different types of system 354 requirements. 355 The architecture provides an abstract framework onto which standard specifications can be 357 developed. The goals are for the architecture and standard specifications to be applicable for a 358 large variety of systems, and to reduce the difficulty of integration, reduce the amount of 359 hardware, and to increase interoperability between systems. 360 In order to achieve these goals, it is necessary to have both an architecture and standard 362 specifications. This document provides the definition of the VICTORY Architecture, whereas 363 the standard specifications are provided in “VICTORY Standard Specifications.” 364

1.3 VICTORY Compliance 365

There is no concept of overall VICTORY compliance or conformance. VICTORY defines sets of 366 component types, each of which defines requirements for a set of interfaces. No component or 367 system will implement all of the component types, as not all of them are relevant for a single 368 system. For that reason, a system, design, or architecture cannot be said to be fully compliant or 369 conformant with the VICTORY Architecture or Specifications. 370 Compliance is designed, claimed, tested, and documented at the component type level, based on 372 the component types implemented in a particular system. VICTORY does not define a concept 373 of conformance. The reasoning that VICTORY defines compliance at the component type level 374 and does not define conformance is explained in this section. 375

1.3.1 Architecture Compliance and Conformance Concepts 377

Compliant and conformant are similar concepts, but there are important differences. There are 378 also differences in the meaning when compliant and conformant are applied at the system and 379 component type level. 380 Referring to Figure 1, Architecture Compliance implies that a system implements some, but not 382 necessarily all of the features of an architecture, and that no features defined by the architecture 383 are implemented in a different way. Architecture Conformance implies that a system implements 384 all of the features of an architecture. Architecture Full Conformance means that not only are all 385 features implemented, but no features are implemented that are not defined by the architecture. 386

Figure 1. Illustration of Architecture Compliance and Conformance 389

Note: Used with permission, ©2011 The Open Group. 390

As mentioned above, it is highly unlikely that a system will be implemented to include all of the 392 VICTORY Component Types (CTs). That is why VICTORY does not define a concept of 393 system or architecture level compliance or conformance. 394

1.3.2 Component Type Compliance and Conformance Concepts 396

When the compliance and conformance concepts are applied at a component type level, as 397 opposed to a full system architecture or design level, the differentiation is similar. 398 The VICTORY concept of compliance relates to component type specifications, analogous to an 400 architectural feature, which is the term used in the text of Figure 1. In the VICTORY context, 401 the terms component or artifact mean hardware and/or software that implements the functionality 402 and interfaces of one or more component types. 403

An implemented artifact can be said to be compliant with a VICTORY CT if and only if all of 405 the interfaces and features that are indicated as required in the CT specification are implemented, 406 and pass a compliance test. VICTORY CT interfaces can be optional or recommended. An 407 artifact can be compliant with the VICTORY CT specification if it does not implement the 408 optional or recommended interfaces. However, if the artifact does implement those interfaces, 409 they must also pass a compliance test for the implementation to be compliant with the CT 410 specification. This is similarly true for features that are marked as optional or recommended 411 within the interface specifications. If an artifact implements optional or recommended features, it 412 must pass a compliance test for those features for it to be compliant with the CT. 413 VICTORY does not define CT-level conformance. If it did, saying an artifact is conformant to a 415 CT specification would imply that all options and features were implemented and passed a 416 conformance test, and that no features were implemented that are not defined by the 417 specifications. That concept would be far too inflexible for the ground vehicle domain. 418

1.3.3 VICTORY Compliance Statements 420

To reiterate the most important concept, compliance with VICTORY specifications is stated, 421 tested, and documented at the component type level only. Instead of saying a system is 422 “VICTORY Compliant,” the correct statement is that a system is “compliant with the following 423 VICTORY Component Types: Position Service, etc.” Whenever a compliance claim is made, it 424 must be supported by a compliance test document for each component type for which the claim 425 is made. The compliance test documents describe the tests that were performed and the results 426 generated. 427 The objective is for the U.S. Army to benefit from the interoperability created by adopting the 429 VICTORY Component Type specifications.