CMOSS Overview 14SEP23 Dist A 23-1038.pdf

APPROVED FOR PUBLIC RELEASE

23-1038 APPROVED FOR PUBLIC RELEASE

APPROVED FOR PUBLIC RELEASE

U.S. ARMY COMBAT CAPABILITIES

DEVELOPMENT COMMAND

C5ISR CENTER

14 September 2023 1

C5ISR/EW Modular Open Suite of Standards (CMOSS) Overview 13 SEP 2023

JASON DIRNER

23-1038

CMOSS OVERVIEW

• CMOSS is a suite of standards to support the reduction of the size, weight and power of C5ISR and EW systems while increasing the flexibility and adaptability of these systems ‒ Universal A-Kit – Project Managers field capabilities as cards into a common chassis ‒ Pooled radio resources such as antennas and amplifiers for Communications, Electronic Warfare (EW), and Signals Intelligence (SIGINT) systems ‒ Shared processing resources such as computers and displays ‒ Shared data services such as Position, Navigation, and Time (PNT) ‒ Foundation for enhanced interoperability and simultaneity between C5ISR systems ‒ Reduced life cycle cost through increased competition, smaller logistics tails with common sparing, and upgrading to the latest hardware as parts are replaced ‒ Rapid insertion of new technology/capability

CMOSS ArchitectureWhy Converge?

C5ISR/EW Modular Open Suite of Standards (CMOSS)

CMOSS

23-1038

Reduces logistics tails by enabling common sparing. Eliminates the need for “End of Life” buys for a 30+ years sustainment by enabling hardware modernization every 5-10 years.

CMOSS ARCHITECTURE

Reduces the size, weight and power footprint of

C4ISR systems by sharing hardware such as antennas and amplifiers.

Universal A-Kit eliminates the need for platform specific integration. PMs field capabilities as cards in common chassis and antennas/amplifiers that use existing cabling.

Enables rapid technology insertion using best of breed capabilities to address emerging requirements.

Lays the foundation for enhanced interoperability and simultaneity amongst

C4ISR capabilities.

23-1038

CMOSS DEVELOPMENT HISTORY

MORA

V1.1

SEP 14

CMOSS Lab Demo

APR 15

CMOSS Lab Demo

APR 17

CMOSS Vehicle Demo

OCT 17

MORA V2.0

JAN 16

MORA V2.1

JUN 17

CMOSS Profiles in OpenVPX

JUL 17

MORA Input in ANSI/VITA 49.2

JUL 17

SOSA V1.0

Snapshot 1

FEB 18

First POR Uses

CMOSS

SEP 18

MORA in

VICTORY V1.8

APR 19

MORA V2.2

SEP 18

SOSA V1.0

Snapshot 2

JAN 19

C5ISR

Center

Kickoff of

HW/SW

Convergence

OCT 13

Army, Air Force, and Navy Kickoff

SOSA Consortium

NOV 15

SOSA V1.0

Snapshot 3

JUL 20

MORA V2.3

AUG 19

VICTORY V1.9 /

MORA V2.4

APR 21

PM EW&C

CMOSS

Memo

JUN 19

CMFF

A-CDD

Approved

JAN 21

CMOSS/SOSA

in NDAA FY21

HASC

JUL 20

Tri-Service Memo

JAN 19

ASA(ALT)

MOSA

Memo

MAR 20

SOSA

V1.0

SEP 21

CMOSS

IRS V1.1

MAR 22

SOSA V2.0

Snapshot 1

JUN 22

MORA V2.5

DEC 22

CMOSS

IRS V1.2

4Q23

SOSA V2.0

Snapshot 2

4Q23

VICTORY

V1.10 4Q23

23-1038

C5ISR CENTER CMOSS STRATEGY

Contact MMO@army.mil for additional info

Manage

•Manage and mature standards

•Educate community •Application to relevant S&T

•Lab and development architecture

•Transition deliverables •Compliance/performance tools and testsSIL

•Baseline platform architecture

•Compliance/performance tests

•Tech demonstrationsField Experiment

ORGANIZE

SYNCHRONIZE

EXECUTE

• C5ISR Center S&T and CMOSS prototyping efforts

• PEO IEW&S

• PEO C3T

• PEO GCS

• PEO CS&CSS

• PEO Aviation

• N-CFT and APNT/Space CFT

• AFLCMC Open Architecture Management Office

• NAVAIR PMA-209

• Industry Partners

• International Partners

MOSA Management OfficeSOSA Consortium

Open Innovation Lab

Network Modernization Experiment

23-1038

CMOSS INTEROPERABILITY REQUIREMENTS

SPECIFICATION (IRS)

• Managed by the C5ISR Center MOSA Management Office (MMO)

• Includes requirements that can be referenced in contracts by:

̵ Directly citing the document (preferred) ̵ Copying specific requirements relevant to a program

• Identifies sections of open standards that are required by CMOSS ̵ VICTORY component types and applicability ̵ MORA component types and applicability ̵ Allowed OpenVPX plug-in card profiles and form factors ̵ Required software frameworks ̵ Recommended connectors and mounts

• Restricts options to facilitate portability and reuse

• Additional details can be found in the standards themselves

23-1038

STATUTE AND POLICY

Policy Guidance on Implementing Modular Open Systems Approach in Army Acquisition Programs and Middle Tier of Acquisition Efforts

ASA(ALT)

Modular Open Systems Approaches for our Weapon Systems is a Warfighting Imperative

Tri- Service

23-1038

STATUTE AND POLICY

Utilization of Electronic Warfare & Cyber C4ISR/EW Modular Open Suite of

Standards (EW&C CMOSS)

PM

EW&C

CMFF

A-CDD

23-1038

STATUTE AND POLICY

William M. (Mac) Thornberry National Defense Authorization Act for Fiscal Year 2021

Report of the Committee on Armed Services House of Representatives

NDAA

FY21

HASC

23-1038

STATUTE AND POLICY

National Defense Authorization Act for Fiscal Year 2022

Report of the Committee on Armed Services House of Representatives

NDAA

FY22

23-1038

STATUTE AND POLICY

National Defense Authorization Act for Fiscal

Year 2023 Report of the Committee on Armed Services

House of Representatives

NDAA

FY23

23-1038

EW Pod

CEMA System CEMA Card

SIGINT, EW, and Cyber System

SDR Card

CMOSS EFFORTS

APNT Experimentation Crypto Card

Radio Card

Integrated Chassis

Digital Radiohead

Radio & COMSEC Cards

23-1038

CMOSS MOUNTED FORM FACTOR (CMFF)

23-1038

TSOA-ID DEMONSTRATION (2020)

CMOSS

Prototype SOSATM Prototype

Transceiver Plug-In Card Transceiver

Plug-In Card

Single Board Computer

SDR Framework

Rapid tech refresh enabled by standard payload profile

Capability reuse across programs and services enabled by common standards

Independent HW and SW upgrades enabled by RF front end abstraction

23-1038

TSOA-ID DEMONSTRATION (2022)

Electronic Warfare Laptop

GPS

Antenna

Headset

Mission Command Tablet

ML2B

VDB

EW

Antenna

End User Device

Handheld RadioComms

Antenna

Communications Network

NAVAIR

PMA-209

HOST

Chassis

AFLCMC

SOSA

Chassis

• Converged architecture integrates Mission Command, Position Navigation and Timing, Communications, and Electronic Warfare in a single chassis

• Common architecture enables capability reuse and interoperability across services

̶ Same Communications and Mission Command cards in Army, Navy, and Air Force chassis

̶ Common Operational Picture for C2 and SA ̶ SOSA System Management

CMOSS AT HIGH ALTITUDE

23-1038

CMOSS CARDS

Radio Cards

Singe Board Computers

Graphics Processing Units

Switches

PNT Cards Storage Cards

Power Supply Modules

Note: List is not exhaustive or an endorsement. New capabilities are constantly being developed.

23-1038

CMOSS CHASSIS AND RADIOHEADS

Chassis

Radioheads Note: List is not exhaustive or an endorsement. New capabilities are constantly being developed.

23-1038

• The SOSA Consortium is a C5ISR-focused technical and business collaborative effort… ‒ What: Develop a unified technical Open Systems Architecture standard for RADAR, EO/IR, SIGINT, EW, and Communications – and the supporting business models ‒ Why: Improve sub-system, system, and platform affordability, re-configurability, upgradability, and hardware/software/firmware re-use – and to shorten cycle times to counter emerging threats ‒ Who: The Air Force, Navy, Army, other government agencies, industry and academia ‒ How: Developing an OSA via modular decomposition (defining functions and behaviors) and associated interfaces (including physical, protocol, and data structure) between the modules

CMOSS is aligned with the SOSATM Technical Standard

SENSOR OPEN SYSTEMS ARCHITECTURE (SOSATM)

CONSORTIUM

CMOSS OpenVPX profiles included in hardware specification

MORA used for Transmission/

Reception modules

SOSA Taxonomy

VICTORY used for Nav Data Service module

SvcV-1 Top-Level SOSA Services Context Description

23-1038

SOSA CONSORTIUM

SOSA™ Sponsors

• Air Force Life Cycle Management

Center

• Collins Aerospace

• Joint Tactical Networking Center

• Lockheed Martin

• Marine Corps Systems Command, Product Manager EWS

• NAVAIR

• NIWC Atlantic

• U.S. Army DEVCOM C5ISR Center

• U.S. Army PEO Aviation

• U.S. Army PEO C3T

• U.S. Army PM PNT

• U.S. Army Project Manager Electronic

Warfare and Cyber

• U.S. Space Force Space and Missile

Systems Center

SOSA™ Principals

• BAE Systems, Inc.

• Cubic Corporation

• Curtiss-Wright Defense Solutions

• Elbit Systems of America

• FLIR Systems, Inc.

• GE Aviation Systems

• General Dynamic

• Huber+Suhner Astrolab

• Intel Corporation

• L3Harris

• Leonardo DRS

• Mercury Systems

• NASA

• Northrop Grumman

• Raytheon

• Sierra Nevada Corporation

• SR Technologies, Inc.

• SRC Inc.

• VadaTech Inc

SOSA™ Associates

• II-VI Aerospace & Defense, Inc.

• Abaco Systems

• Acromag, Inc.

• Aegis Power Systems

• Aitech

• AirBorn, Inc.

• Amphenol

• Ampro ADLINK Technology, Inc.

• Analog Devices

• Anduril Industries, Inc.

• ANELLO Photonics

• Annapolis Micro Systems, Inc.

• Apogee Semiconductor

• Atrenne

• Ball Aerospace

• Behlman Electronics, Inc.

• CACI International, Inc.

• Chameleon Consulting Group

• Cobham Advanced Electronic

Solutions Inc.

• CodeMettle, LLC

• Comtel Electronics, Inc.

• Concurrent Technologies

• Cornet Technology Inc.

• COTSWORKS, LLC

• CRFS, Inc.

• Critical Frequency Design

• Crossfield Technology

• Crystal Group

• Dawn VME Products

• Delta Information Systems

• DornerWorks

• DRS Signal Solutions

• DRTI

• EIZO Rugged Solutions, Inc.

• Elma Electronic Inc.

• EPI

• Epirus Inc

• Epiq Solutions

• Expeditionary Engineering Inc.

• FiberQA

• Freedom Power Systems, Inc.

• Frontgrade Technologies

• GALT Aerospace

• General Micro Systems, Inc.

• Georgia Tech Research

Institute

• Glenair

• GORE

• Herley Industries, Inc.

• Herrick Technology

Laboratories, Inc.

• HII Mission Technologies

• Hughes Network Systems, LLC

• IDEAS Engineering and

Technology, LLC

• Inertialwave, Inc.

• Innoflight, LLC

• Interface Concept

• iRF Solutions

• ITT Cannon LLC

• ITZ, LLC

• Jacobs

• Jovian Software Consulting

LLC

• Kontron America

• LCR Embedded Systems, Inc.

• Lead Dog Technologies

• Leidos

• LGS Innovations

• Mathtech, Inc.

• Meritec

• Micro Focus (US), Inc.

• Microchip Technology Inc.

• Micropac

• Midwest Microwave Solutions

Inc

• Milpower Source

• Moog Inc.

• Motorola Solutions

• New Wave Design and

Verification, LLC

• NVIDIA Corporation

• North Atlantic Industries, Inc.

• One Stop Systems

• OnTime Networks, LLC.

SOSA™ Consortium - Brings together DoD, industry, and academia under a rigorous consensus based approach for standards development. SOSA leverages CMOSS development. The consortium has 154 members. US Army CMOSS developers serve in many key roles within the consortium.

CMOSS - Standards developed and maintained by the US Army to support Army procurements which respond to program office schedules and needs. CMOSS defines an instantiation of the SOSA reference architecture which provides the necessary specificity to achieve the Army’s reuse and portability goals. We strive to maintain alignment between CMOSS and the SOSATM Technical Standard.

• Orion Technologies, LLC

• Orolia Defense & Security, LLC

• Pacific Defense

• PacStar

• Parry Labs, LLC

• Pentek, Inc.

• Phoenix International

• Pixus Technologies USA Corp.

• Quantic Electronics

• QRC Technologies, LLC

• RADA Technologies, LLC

(RADA USA)

• Rantec Power Systems, Inc.

• Real-Time Innovations

• REDCOM Laboratories Inc.

• Red Hat

• Red Rock Technologies

• Riverside Research

• RTD Embedded Technologies

• Saab, Inc.

• Samtec

• ScioTeq LLC

• Sciens Innovations

• Sealevel Systems, Inc.

• Selex Galileo Inc.

• SI2 Technologies, Inc.

• Skayl LLC

• Smiths Interconnect Americas

• Southwest Research Institute

• StreamDSP LLC

• Systel, Inc.

• TE Connectivity

• Technology Service Corporation

• THE MITRE CORPORATION

• Tektronix, Inc.

• Telephonics

• Tomahawk Robotics

• Tucson Embedded Systems

• University of Dayton Research

Institute

• Variable Software, Inc.

• Viasat, Inc.

• VITA

• W-IE-NE-R Power Electronics

• Wolf Advanced Technology Inc.

23-1038

• Initiated by US Navy’s Naval Air Systems Command (NAVAIR) at Patuxent River, MD in 2014

• Specification methodology for state-of-the-art embedded systems development and acquisition ‒ Compilation of established industry standards such as OpenVPX and IPMI ‒ Flexibility to add new Tier 2 standards for other technologies ‒ Initial focus on airborne mission processing

• Focused on establishing interoperability and interchangeability at the module level

T I E R

T I E R

T I E R

Graphics Card

SBC

Enclosure

Face Plate

Airframe

FACE Developed & Integrated Software-based Capability

(Years) v1.0 v2.0 v3.0 v4.0 v5.0

Host Vision

OpenVPX profiles aligned so CMOSS, SOSA, and HOST can use the same payload modules

HOST chassis management aligned with SOSA out-of-band hardware system management

• Tier 1: Universal requirements that apply to all HOST components

• Tier 2: Technology specific requirements (e.g., OpenVPX)

• Tier 3: Module level requirements used to create component registry

HOST chassis management augments CMOSS network layer interoperability to provide enhanced system management

HARDWARE OPEN SYSTEMS TECHNOLOGIES (HOST)

23-1038

CMOSS

VICTORY

SOSA

VITA

MORA VITA

49.2

OpenVPX

VITA 65

IPMI

VITA 46.11

FACE

REDHAWK

SCA

Photon

SALVAGE

X-Midas

Mounted

CE

SAE

AS6129

AS6169

AS39029

AS6070

OCI

DMTF

OVF

OAI

CMOSS IRS V1.1 AND SOSA TS V2.0 SS1

IEEE

Ethernet

IETF

TCP/IP

W3C

SOAP/

XML

Endeavor to converge the CMOSS and SOSA circles over time

23-1038

CMOSS

VICTORY

SOSA

VITA

MORA VITA

49.2

OpenVPX

VITA 65

IPMI

VITA 46.11

FACE

REDHAWK

SCA

Photon

SALVAGE

X-Midas

Mounted

CE

SAE

AS6129

AS6169

AS39029

AS6070

OCI

DMTF

OVF

OAI

CMOSS IRS V1.2 AND SOSA TS V2.0 SS2 (4Q23)

IEEE

Ethernet

IETF

TCP/IP

W3C

SOAP/

XML

CMOSS

+ SOSA Connectors and Mounts + SOSA System Management

SOSA

+ VICTORY Position, Orientation, and Direction of Travel + SCA (within module)

23-1038

LAYERED STANDARDS

Open Standards

SOSA

CMOSS

CMFF

Card Sizes

Slot Profile Options

Cooling Software Run-Time Environ-ments

System Management

C5ISR

Functional Interfaces

Electrical Connector Standards

Mechanical Interface Standards

Environ-mental Standards

- Same as

SOSA

- VITA 46

- VITA 90

- 91 Profiles

- VITA 65

- VITA 66.x

- VITA 67.x

- SOSA+

- VITA

48.x

- FACE

OSS

- OCI

Container

- OVF VM

- VITA 46.11 - N/A - SAE

AS6129A

- SAE

AS6169A

- NATO

- Subset of

MIL-STD-

810 in VITA 47.1-3

- 3U VPX

- 3U sVPX

- 6U VPX

- VNX+

- 33 Payload

- 12 Switch

- 4 PNT

- 2 PS

- AMPS

- 1.0” CC

- 1.5” AFT

- 1.0” LFT

- FACE

OSS

- OCI

Container

- OVF VM

- SOSA

Config Files

- VITA 46.11

Tier 3 IPMC and ChMC

- SOSA In- Band System Mgmt

- SOSA

EW,

COMMS,

SIGINT,

Radar, EO/IR

- VICTORY

Position, Orientation, DOT

- MORA

- SAE

AS6129A

- SOSA

connectors

- 40 identified

- SAE

AS6169A

- NATO

- Leverages mounting of SAVE but not explicitly

- VITA +

some

ATPD-2404

- 3U VPX

- 6U VPX

- 6 Payload

- 4 Switch

- 1 PNT

- 2 PS

- Reduced

AMPS

- 1.0” CC

- 1.5” AFT

- SCA

- MMC*

- FACE

- Photon

- Redhawk

- SALVAGE

- X-MIDAS

- VICTORY

- MORA

- VITA 46.11

Tier 3 IPMC and ChMC*

- SOSA In- Band System Mgmt*

- VICTORY

- MORA

- Same as

SOSA

- Same as

SOSA

- Same as

SOSA*

- 3U VPX - 2 Payload

- 1 Switch

- 1 PNT

- 1 PS

- Reduced

AMPS

- 1.0” CC - SCA

- FACE

- MMC

- VICTORY

- MORA

- VITA 46.11

Tier 3 IPMC and ChMC

- SOSA In- Band System Mgmt

- VICTORY

- MORA

- Subset of

SOSA

and SAVE

TBD*

- SAVE - SOSA +

ATPD-2404

and AVN

AQP

N ar ro w s Fo cu s

* = Future

23-1038

SPECIFICATIONS AND STANDARDS BODIES

• CMOSS – C5ISR/EW Module Open Suite of Standards

• DMTF – Distributed Management Task Force

• FACE – Future Airborne Capability Environment

• IEEE – Institute of Electrical and Electronics Engineers

• IETF – Internet Engineering Task Force

• IP – Internet Protocol

• IPMI – Intelligent Platform Management Interface

• MORA – Modular Open RF Architecture

• Mounted CE – Mounted Computing Environment / Common Operating Environment

• OAI – OpenAPI Initiative

• OCI – Open Container Initiative

• OVF – Open Virtualization Format

• SAE – Society of Automotive Engineers

• SCA – Software Communications Architecture

• SOAP – Simple Object Access Protocol

• SOSA – Sensor Open Systems Architecture

• TCP – Transmission Control Protocol

• VICTORY – Vehicular Integration for C4ISR/EW Interoperability

• VITA – VMEbus International Trade Association

• W3C – World Wide Web Consortium

• XML – Extensible Markup Language

23-1038

• CMOSS Interoperability Requirements Specification (IRS) V1.2 will be released in 4Q FY23 ̵ Addresses lessons learned and gaps from CMFF prototyping ̵ Increase alignment between CMOSS and SOSA ̵ Reference VICTORY V1.10, MORA V2.5, and SOSA Technical Standard

V2.0 Snapshot 2

• SOSA Technical Standard changes stemming from CMFF ̵ Environmental Specifications on cards ̵ Connectors and IO ̵ Additional Signals of Opportunity pins ̵ MLS support

• CMOSS documentation can be downloaded from:

̵ FY22-C5ISR-CMOSS on SAM.gov

(https://sam.gov/opp/1cc5def015a042c881e5ff7dcb35a87f/view) ̵ Joint Communications Marketplace (https://jtnc.sites.crmforce.mil/)

CMOSS AND SOSA UPDATES SUPPORTING CMFF

SAM.gov

JCM

23-1038

JOINT COMMUNICATIONS MARKETPLACE (JCM)

CMOSS Documentation (https://jtnc.experience.crmforce.mil/JTNC/s/cmoss)

Select Joint Communications Marketplace (https://jtnc.experience.crmforce.mil/JTNC/s/)

Select CMOSS to view and add CMOSS aligned products

23-1038

• CMOSS leverages the compliance process for each of the constituent standards

̵ VICTORY and MORA verify compliance at the component level using a Compliance Test Suite (CTS)

̵ MORA also provides a test client to observe functional behavior and verify interactions between component types

̵ VICTORY and MORA reference software is available on VDL (https://restricted.vdl.afrl.af.mil)

̵ OpenVPX (VITA 65) requires suppliers to provide, on request, a statement of compliance which identifies rules plus verification outcome

̵ FACE has a robust conformance program run by The Open Group ̵ SCA compliance is verified by the Joint Tactical Networking Center (JTNC)

• CMOSS compliance will be augmented by the SOSA Conformance Program when available

• Army is working with NAVAIR to develop a single-slot OpenVPX Conformance Tool (OCT) that can be used to verify OpenVPX compliance in the future

̵ Initially focused on the CMOSS/SOSA payload profile

CMOSS COMPLIANCE OVERVIEW

23-1038

• Objectives:

̵ Provide a robust verification means to support PMs and vendors ̵ Provide guidelines for establishing and accrediting facilities to perform independent compliance verification tests for VICTORY component types

• The CTS provides artifacts for each VICTORY component type, including:

̵ A “golden standard” Compliance Test Plan (CTP), which provides detailed test configuration and methodologies for conducting compliance verification test

̵ A Compliance Test Report (CTR) template, for documenting compliance test results

̵ A Compliance Test Tool (CTT), which provides a mix of capabilities, including automating some compliance tests, providing guidance for non-automated tests, allowing user input for verification results based on inspection and demonstration, and generating/viewing CTRs

VICTORY COMPLIANCE TEST SUITE (CTS)

23-1038

• CMOSS reduces the SWaP of C5ISR equipment and enables rapid technology insertion, while at the same time providing significant cost savings during the procurement and sustainment phases of the life-cycle

• Multiple CMOSS efforts are on-going providing EW, SIGINT, Comms, Mission Command, PNT, and Cyber capabilities

• CMOSS is being aligned with the SOSA Consortium with Army, Air Force, Navy, and USMC participation

• The CMOSS specifications can be obtained from:

̵ FY22-C5ISR-CMOSS on SAM.gov

(https://sam.gov/opp/1cc5def015a042c881e5ff7dcb35a87f/view) ̵ Joint Communications Marketplace (https://jtnc.sites.crmforce.mil/) ̵ AF Virtual Distributed Laboratory (https://restricted.vdl.afrl.af.mil) ̵ OpenVPX (http://www.vita.com) ̵ REDHAWK (https://redhawksdr.github.io/Documentation) ̵ SCA (http://www.public.navy.mil/jtnc) ̵ FACE (http://www.opengroup.org/face) ̵ SOSA (http://www.opengroup.org/sosa) ̵ Open Innovation Lab (https://apntoil.army.mil/)

SUMMARY

SAM.gov

JCM

Please join the SOSA Consortium if you’d like to contribute to these standards!

TECHNICAL OVERVIEW

23-1038

Adds a network data bus to vehicles

• Specifies “on-the-wire” network-based interfaces for discovery, management, health publishing, and data exchange

• Provides shared hardware and user interface hardware

• Provides shared services including time synchronization, position, orientation, and direction of travel

• Supports IA requirements and “defense in depth” security designs

VICTORY leverages the following commercial technologies:

• SOAP-based web services and Simple Network Management

Protocol (SNMP) for management

• Syslog over UDP and SNMP for health publishing

• VICTORY Data Messages (VDMs) for data distribution

‒ XML application layer payload encapsulated in a VDM-specific binary header

‒ Multicast UDP provides a simple publish/subscribe paradigm

• Zero Configuration Networking (Zeroconf) for node and service discovery

Traditional Approach

VICTORY Approach

VICTORY enables interoperability across C4ISR, EW, and platform systems on Army ground vehicles. Technical approach is applicable to air, sea, and subsurface platforms.

VEHICULAR INTEGRATION FOR C4ISR/EW

INTEROPERABILITY (VICTORY)

23-1038

• MORA integrates VICTORY and VITA Radio Transport (VITA 49.2) to standardize access and control of the RF chain

• Decomposes the RF chain into the following signal resources:

‒ Antennas (antenna elements / arrays) ‒ RF Conditioning (e.g., LNAs, filters and HPAs) ‒ RF Distribution (e.g., RF switches) ‒ RF Frequency Translation (e.g., tuners and up converters) ‒ Signal Domain Conversion (e.g., ADCs and DACs)

MODULAR OPEN RF ARCHITECTURE (MORA)

OVERVIEW

23-1038

• Resource management occurs over different physical links than control and data due to performance and security considerations

• Discovery and allocation occur in non real-time (milliseconds or seconds) over the VICTORY Data Bus (VDB) ‒ Leverages SOAP-based web services with MORA defined WSDLs and schemas

‒ Inherits the IA controls and attribute-based access control (ABAC) framework provided by

VICTORY

‒ Priority-based resource reservation restricts control to a single entity at a given time

‒ Data can be subscribed to by multiple entities

‒ Interfaces enable but do not prescribe implementation of the resource manager itself

RESOURCE MANAGEMENT

23-1038

• RF control and data distribution occur in real-time (microseconds) over the MORA Low Latency Bus (ML2B)

• MORA Data Message (MDM) binary header encapsulates VITA 49.2 ‒ Enables ACK-based reliable delivery over

UDP without degrading performance ‒ Data and context messages use multicast for one-to-many distribution ‒ Different Ethernet and IP service classes defined for control and data packets

• MORA necks down VITA 49.2 to ensure interoperability ‒ Limits packet types that are supported ‒ Identifies required fields ‒ Limits field options such as timestamp and data format ‒ Defines the Discrete I/O field to replace discrete signals

Allowed VITA 49.2 Context/Command Indicator Fields (CIF)

CONTROL AND DATA

23-1038

Payload Radial ClockControl/Data Plane Switch Slot Profiles

Example Backplane

RF and Computing

SLT3-PAY-1F1U1S1S1U1U2F1H-14.6.11-0/4

Position, Navigation, and Timing SLT3x-TIM-2S1U22S1U2U1H-14.9.2-1

Supports DoD-specific concerns including:

• Connectivity for the VICTORY Data Bus

(Control Plane) and MORA Low Latency Bus (Real-Time Data Plane)

• Radial clock distribution for phase coherent operation

• Blind-mate optical and coaxial connectors for two-level maintenance

Maximizes interoperability by:

• Specifying a single slot profile for each type of card (e.g., Payload, Radial Clock, etc.)

• Limiting protocols to a single technology family

‒ Ethernet for Control and Data Planes ‒ PCIe for Expansion Plane

• Limiting the use of user-defined pins

SLT3-SWH-6F1U7U-14.4.14

SLT3-SWH-4F1U7U1J-14.8.7-n

CMOSS OPENVPX PROFILES

Refer to SOSATM Technical Standard for additional details

23-1038

I/O Intensive SBC Control/Expansion Plane Switch Slot Profiles

Example Backplane

Platform I/O

SLT3-PAY-1F1F2U1TU1T1U1T-14.2.16

Analog RF Distribution SLT3-SWH-1F1S1S1U1U1K-14.8.8-n

Ethernet and PCIe

SLT3-SWH-6F8U-14.4.15

CMOSS OPENVPX PROFILES

RF Switch

External I/O

Platform Specific I/O

SLT3-PAY-2U2U-14.2.17

Refer to SOSATM Technical Standard for additional details

23-1038

• Control Plane (1 Ultra-Thin Pipe)

– Ethernet

– Routed over backplane in star topology using switch card

– Monitoring/management over the VICTORY Data Bus

• Real-Time (RT) Data Plane (1 Fat Pipe)

– Ethernet

– Routed over backplane in star topology using switch card

– Real-time control over the MORA Low Latency Bus

• Non Real-Time (NRT) Data Plane (1 Ultra-Thin Pipe)

– Ethernet

– Routed over backplane in star topology using switch card

– Non real-time control over the MORA Low Latency Bus

• Expansion Plane (2 Fat Pipes)

– EP00 – EP03: PCIe

– EP04 – EP07: PCIe / User Defined

– Routed over backplane in ring or star topology

– Supports tight coupling of adjacent cards

• Maintenance Port provides console for use during board maintenance

• Radial clocks terminated on plug-in module

– 1 PPS AUX_CLK

– 100 MHz REF_CLK

• Data Plane separated from Control Plane by an unused Ultra-Thin Pipe (GND)

• Only uses 12V, 3.3V_AUX, and VBAT to maximize portability

• VITA 67.3 Module C provides coax and/or fiber over the backplane

– 14 coax connections using SMPM pins

– Coaxial pin assignment is as follows:

– 6 user-defined pins for coherent operation across payloads (e.g., local oscillator distribution)

– 75-Ohm NanoRF option available for video

– Future support for optical interfaces using high density MT ferrules

PAYLOAD SLOT PROFILE

SLT3-PAY-1F1U1S1S1U1U2F1H-14.6.11-4

23-1038

• Enable portability of software applications across hardware platforms

• Appropriate software framework is dependent on mission area ‒ REDHAWK: Free and Open Source Software

(FOSS) Software Defined Radio (SDR) framework

‒ Software Communications Architecture (SCA): Developed by JTNC for Comms applications

‒ Future Airborne Capability Environment (FACE): Developed by NAVAIR PMA-209 for avionics applications

• Software frameworks can be integrated with network layer to maximize reuse and leverage existing capabilities ‒ MORA REDHAWK Device ‒ VICTORY Platform-Specific Services

Segment (PSSS) within FACE

Composition of a SCA System (from SCA Specification V4.1)

REDHAWK IDE (from REDHAWK website)

Architecture Segments Example (from FACE Technical Standard 2.1)

SOFTWARE FRAMEWORKS

BACKUP

23-1038

• Coordinate MOSA usage across C5ISR Center ‒ Review S&T projects and identify cross cutting opportunities to include MOSA ‒ Allocate MOSA implementation funding for labs, experimentation, and matrixed SME support ‒ Provide MOSA training for directorate SME’s ‒ Facilitate technology transition

• Manage and mature standards ‒ Develop and maintain the CMOSS and VICTORY specifications ‒ Develop compliance tools and support compliance verification ‒ C5ISR Center lead for standards bodies such as the SOSATM Consortium ‒ Coordinate with external MOSA activities

• Provide MOSA support to the acquisition community ‒ Consolidate resource requests for MOSA support facilities and staff ‒ Support inclusion of MOSA in policy and programs

• Coordinate/represent MOSA with external partners including USAF, USN, FVEY, and Industry

MOSA MANAGEMENT OFFICE RESPONSIBILITIES

23-1038

• Army has transitioned sustainment of the VICTORY Standard Specifications to the SOSA Consortium

‒ Leverage existing Industry-Government consensus-based standards body ‒ Facilitate alignment between CMOSS and SOSA ‒ Maximize efficiency of individuals developing and using the specifications

• VICTORY Standard Specifications V1.10 (which includes MORA V2.5) will be transitioned and distributed in its entirety by the SOSA Consortium

‒ Future updates will be made within the SOSA Consortium ‒ Initial transfer does not imply applicability to SOSA components (i.e., start as separate standards managed by the same consortium) ‒ Integration with the SOSA Technical Standard will be accomplished via change proposals per the current process

• Army will retain ownership of the VICTORY Compliance Test Suite (CTS) although it is expected that it will be leveraged as part of the SOSA Conformance Program ‒ Currently available for download from the SOSA program on VDL

VICTORY TRANSITION TO SOSA CONSORTIUM

Army remains committed to the use and sustainment of VICTORY

23-1038

THANK YOU.

Jason Dirner MOSA Chief Engineer MOSA Management Office, DEVCOM C5ISR Center MMO@army.mil

14 September 2023 43