victory:an open system architecturefor military … integrity engineering rethinking systems...

MooreIntegrityEngineering RethinkingSystemsEngineeringThroughModularity,Interoperability&OpenArchitecture

VICTORY: AnOpenSystemArchitecture forMilitaryGroundVehicleElectronicsACaseStudyforModularity&Interoperability

2017GroundRoboticsCapabilitiesCapabilitiesConference&ExhibitionInteroperabilityPanel

MichaelS.Moore,Ph.D.MooreIntegrityEngineeringVICTORYChiefArchitectmsmooreinsa@gmail.com

22March2017


MilitaryGroundVehicleProblemSpace

AutomotiveBus

Targeting

ComputerDisplay2xGPSRX /Ant

CREW System

GPSRX/AntComputer(s)Wiring DVE System

Display/KB/UIDevice/Wiring

(Legacy) Voice CommIntercom

LegacyWiring,Antennas,AmplifiersUIDevices

GPSRX

GPSRX/Ant,ComputerDisplay/KB/UIDevices,Wiring

Battle Command

ComputerDisplay,WiringUIDevice

Weapon Station

New Radios

EachwithGPSRX/Ant

• Duplicatedfunctionality• SizeWeightandPowerClaims• ManySoldierInterfaces• SystemsDoNotInteroperate• Nocommonsecurityapproach• Logistics,MaintenanceDifficult

Future Systems?SA Video, Intel,Protection, A-PNTNo Path Forward

RootCause:Systemsareprocuredseparately,withoutknowledgeofacommonvehiclearchitecturethatcouldprovideservicesandsupportinteroperability


VehicularIntegrationforC4ISR/EWInteroperability(VICTORY)Approach§ IncludeanEthernetIn-VehicleNetwork(IVN)aspartofvehicle(infrastructure)

– IntegrateC4ISR/EWsystems,interfacewithotherelectronicsystems– Providetheplumbingforsystemsandcomponentstointeroperate

VICTORYisnotaboutnewtechnology.Itisaboutaddingin-vehiclenetworkstoplatforms,andagreeinguponopenspecificationsforinterfaces.

§ Provide shared hardware, services, and security protections as part of IVN

– Shared transport, processing resources, user interface devices

– Position, orientation, direction of travel– Management mechanisms: config,

control, data logging, health reporting– Access control, data protection, etc.

§ Define modules: “Component Types” interoperate via network-based messaging interfaces – C4ISR, EW, Vehicle Platform, Weapons Systems CTs interoperate on IVN with open standards

DISTRIBUTIONSTATEMENTA:Approvedforpublicrelease,27June2013


WhatDrovetheVICTORYApproachDISTRIBUTIONSTATEMENTA:Approvedforpublicrelease,27June2013

• Vehicleprogramscannotlevyrequirementsforspecificsoftwaremiddlewareondevices• DefinemessaginginterfacesallowedVICTORYtonotaffectinternaldesigndetails• Loosely-coupled,federatedarchitecture,requiringonly“onthewire”protocols• Commonsemantic: format,encoding,encapsulation,transport,andsecuritycontrols

• Messages,dataelements,operations,parameters,protocols


WhatDrovetheVICTORYApproachDISTRIBUTIONSTATEMENTA:Approvedforpublicrelease,27June2013

• VDB(In-VehicleNetwork)infrastructureprovidescapabilitiesaspartofthevehicle• SharedtransportwithQoS,Sharedprocessingtohostsoftwareapplications• InformationAssurancecontrolsbuilt-in(accesscontrol,dataprotection,etc.)• Sharedservices:Position,Navigation,Timing(PNT)• Supportforsystemmanagement;configuration,control,health


VICTORYFrameworkProducts§ Architecture:definescommonterminology,structures,component(types),andinterfaces

§ StandardSpecifications:providetechnicalspecificationsfortheitemsidentifiedinthearchitecture

§ ComplianceTestSuite (CTS):provides[foreachcomponenttype]the“goldenstandard”testplan,reporttemplateandtesttoolforcompliancetesting

§ ReferenceDesigns:providesamplesonhowtousethestandardspecification

§ ValidationArtifacts:resultsoftheinitialimplementationofthestandardspecifications

§ ReferenceSoftwareLibrary:reusablesoftwaretojumpstartimplementation,thathasbeenverifiedwiththeuseofComplianceTestTool(CTT)

6

DISTRIBUTIONSTATEMENTA:Approvedforpublicrelease,27June2013

The architecture documents the scope of interest, system structure, boundaries, “component types”, their functions, and their interfaces. It

does not identify a specific design or set of HW/SW components.The CTT includes the specifications with browsing capability.


VICTORYImplementation&Status§ VICTORYStandardsSupportOffice(VSSO)

– InProgramExecutiveOfficeforGroundCombatSystems(PEO-GCS)– Managesarchitectureandstandards,ledbyanExecutiveSteeringGroup(ESG)– VehicleandproductprogrammanagersstaffESG,andfundtheVSSO

§ Stablearchitectureandstandards,withsupportingtoolsandreferenceSW– VICTORYArchitecture,Version:A3,23May2014– VICTORYStandardSpecifications,Versio:1.6.2,March31,2015– EngineeringChangeProposals(ECPs)beingexecutedasneeded

§ Beingimplementedinprogramsofrecord– Vehicleandproductprograms(acrossthegamut)– Governmentlaboratoriesdevelopingcommonproducts– Multiplevendorproducts(HW/SW)

§ FutureextensionofVICTORYscope –willnotchangecurrentbaseline– ModularOpenRadioFrequencyArch(MORA)– fromArmyS&TCommunity– ExtendmodularityintoRFsystemssucharadios,intelligence,&EW– MakelargeSWaP componentssharable

• Antennas, amplifiers, signal conditioning, Signal processing, common applications


Take-Aways§ VICTORY:anexampleModularOpenSystemsApproach(MOSA)

– Developedtocreatemodularity/interoperability– Developedforthemilitarygroundvehiclebusinessmodel– Hasalong-termsupportstrategy,andisbeingimplemented

§ Technicalapproachdeterminedbybusinessmodel– Defines“onthewire”messageformatsfirst,asopposedtoanAPI– Entitiesprocuredarelargely“Boxes”,notsoftwaremodules– Cannotassumeallendpointscanrunamiddlewareorevensoftware

§ OSAbestpracticesandcommonsharedartifactsarebadlyneeded– E.g.RoboticsInteroperability:effortsdonotsharedatamodel– Conceptsarere-createdfromscratch- beitamiddleware(APIs),

messagedefinitions,orsoftwareframeworkeffort– Technology/notationdistractfromrealjob:commonsemantic– Currentopportunity:developcommonsharedartifactsforrobotics!

MooreIntegrityEngineering RethinkingSystemsEngineeringThroughModularity,Interoperability&OpenArchitecture 9

Questions?Discussion?

• Formoreinformation• VICTORY:www.victory-standards.org

[email protected] withquestions.

victory:an open system architecturefor military … integrity engineering rethinking systems...

Documents