Recent Updates to the DoD Approach and Strategy …...I n t e g r i t y - S e r v i c e - E x c e l...

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Recent Updates to the DoD Approach and Strategy to Implementing Modularity and

Openness in Weapon Systems

1

J. Kyle HurstAir Force Departmental Standardization Officer

Distribution Statement A: Approved for public release.

Dr. Kelly AlexanderOffice of the Chief Systems Engineer (OCSE), Army ASA(ALT)

Bruce Burnside Engineering Policy, Standards & Industrial Engineering Group (SEA 05S


Air Force Modular Open Systems Approach Implementation Status

1

J. Kyle HurstAir Force Departmental Standardization Officer

Distribution Statement A: Approved for public release. Distribution is unlimited. AF PAIRS Case #2019-0684


Updated AFI63-101 Integrated Lifecycle Management

Included recommendation to use Modular Open System Approaches in Middle Tier of Acquisition policy

USAF Service Acquisition Executive signed memo addressing contractual language/considerations Tie incentive fees or follow on contracts to delivery of

technical data with sufficient right to compete future upgrades or verifiable compliance to open standards

Air ForceAcquisition Policy & Guidance



Air Force Data Rights GuidebookEquip acquisition personnel to handle common IP issues Actionable information vice recitation of the rulesSix key focus areas: lifecycle planning for IP, IP in source

selection, maximizing unlimited rights, SW acquisition, battling vendor lock, integrated data/digital environments

“Smart IP Cadre” to assist program offices with IP issues, keep guidance current, and assist senior leaders with Air Force IP strategic direction

Air ForceIntellectual Property Considerations



Mandated Open Mission Systems/Universal Command and Control (OMS/UCI)

Mandated Universal Armament Interface (UAI)

Endorsed Simulator Common Architecture Requirements and Standards (SCARS)

Developing of other broadly applicable standardsEstablished Open Architecture Management Office (OAMO)Developing a “reference architecture”

Air ForceMandating Specific Standards



Air Force Reference Architecture for Avionics

Tie to AF & DoD enterprise architectureFocus toward program offices, programs of recordEnable early Verification & Validation of requirementsManage open standards and architectures with OAMO

Electronic Warfare

SPEAD - SOSARaging Crow

Big Iron

SensingSOSA

COARPS

CommunicationsSOSA

Open Comms

AutonomyTEAMS

PNTR-EGI

Msn Functions (software services)

• Fusion• Targeting• Etc.

OMS Isolator

Aircraft(safety critical)

Abstract Service Bus (ASB)/Critical Abstraction Layer (CAL) as defined by OMS

Reference Architecture for Avionics

UAIJMPS-Open Mission

System (JOMS)

Weapons (WOSA)

ABMS/OA DCGS

CMCCMIL-STD-1553 - Deterministic



Questions?For additional information:

https://milsuite.mil/wiki/Portal:Air_Force_Engineering_Resource_Center/Standardization_Program


America’s Force of Decisive Action

UNCLASSIFIED

UNCLASSIFIED

Dr. Kelly Alexander Director, Systems Engineering Program Support (SEPS)

Office of the Chief Systems Engineer (OCSE)Assistant Secretary of the Army for Acquisition, Logistics & Technology (ASA(ALT))

Status of Army Modular Open Systems Approach (MOSA)

Implementation

DISTRIBUTION A: Approved for public release / distribution unlimited.

2

UNCLASSIFIED

UNCLASSIFIED

MOSA Enables Army Modernization

Interoperability

Tech Refresh

Competition

Innovation

Cost Competition

Open Standards

Open Architecture

IP/Data Rights Open

Interfaces

Business Strategy

Governance

MOSA Benefits

MOSA Principles

•Open Architecture•Designation of Key Interfaces•Widely supported, common standards for key interfaces•Certify Conformance•Modular and severable designs

Technical Enablers

•MOSA Incentives/RFP•Enterprise investment strategies to maximize re-use

•Transformation of life-cycle sustainment strategies

•Strategic use of data and intellectual property rights

Business Enablers

•Acquisition Strategy•Systems Engineering Plan•Key MOSA Activities throughout the Acquisition Lifecycle

ProgrammaticEnablers

MOSA Enablers

MOSA is a “Warfighting Imperative”

3

UNCLASSIFIED

UNCLASSIFIED

MOSA Implementation Policywill be issued

Implementing MOSA in the Army

• Directs stakeholders to implement MOSA enablers to achieve MOSA benefits

• Assigns responsibilities to stakeholders • Allows MDA to tailor in Acquisition

Strategy

MOSA Implementation Guide

• Guidance for stakeholders to implement the MOSA business and technical enablers throughout the acquisition lifecycle

• Identifies key program events and artifacts for MOSA

• Best Practices

MOSA Enablers

• Database of Mature Standards• Open Architectures• Reuse artifacts/tools etc• Checklist for program self-assessment• MOSA Contracting & Incentive Strategies

4

UNCLASSIFIED

UNCLASSIFIED

Army MOSA Policy Activities

•Enables the necessary intellectual property and data rights to support MOSA implementation

Intellectual Property Policy and Implementation Guidance

(Dec 2018/Feb 2019)

•Update to broaden this section beyond architectures to align with MOSA Statutory/Regulatory Guidance

AR 70-1 “Army Acquisition Policy” Aug 2018

•Provides lifecycle guidance on open systems•Choose specifications and standards adopted by industry standards bodies or de facto standards (set by the market place) for selected system interfaces (functional and physical), products, practices and tools.

DA Pam 70-3 “Army Acquisition Procedures” Sep 2018 – No

changes recommended at this time

In P

roce

ssC

urre

nt

• Directs MDAPS/Non MDAPS & Middle Tier to implement MOSA enablers to achieve MOSA benefits (MDA approves)

• Assigns responsibilities to key stakeholders

Draft MOSA Implementation Policy (Planned for release

Nov 2019)

• MDAP/Non-MDAP and Middle Tier Guidance• Focus on Mature Technical and Business Enablers

Draft MOSA Implantation Guidance (Planned for release in

Nov 2019)

5

UNCLASSIFIED

UNCLASSIFIED

•Organically developed: End to end Infrastructure Architecture for Ground Vehicles

•Common Infrastructure (hardware and software, and in-vehicle network)•Reusable Common Infrastructure Software Framework•Organically developed VICTORY Interface

Ground Common Infrastructure

Architecture (GCIA)

•Identifies Key Interface Standards & Information Exchanges

•Improves Interoperability

Reference Architectures for PNT

•Identified cross cutting capabilities to improve component reuse•Improved Interoperability •Aligned, Integrated and Operationalized PEO assets through Architecture IPT/Roles& Responsibilities

Open System Architectures for

Future Vertical Lift

•System architecture allows several major system components to be incrementally added, removed, or replaced throughout the life cycle

•Data Rights/IP Strategy enables competition

Improved Turbine Engine (ITE) Program

PMs Are Currently Using Domain Specific Strategies To Enable MOSA

Current MOSA Implementation Examples in Army Programs

6

UNCLASSIFIED

UNCLASSIFIED

Status of MOSA Enabling Standards & Architectures

Fully Mature

•Vehicular Integration for C4ISR/EW Interoperability (VICTORY)•Future Airborne Capability Environment (FACE)•C4ISR Open Suite of Standards (CMOSS)•Modular Active Protection Systems Framework (MAF)•Modular Open Radio Frequency Architecture (MORA)•Hardware Open Systems Technologies (HOST)•Integrated Sensor Architecture (ISA)•Robotics and Autonomous Systems, Ground (RAS-G)•Interoperability Profile (IOP)

Expected to reach full maturity

w/in 5 years

• Ordinance Interface Standard (OIS)• Engagement Operations (EO)

Several Domain Specific MOSA Technical Enablers are Mature & In Use

7

UNCLASSIFIED

UNCLASSIFIED

Common Artifacts for

Source Selection

Library of Open System Architectures

(OSA)

Reusable Software and Tools Library

Database of Open

Standards

Technical Enablers for MOSA Applications

Future State Where Artifacts are Shared Across the Acquisition Community

8

UNCLASSIFIED

UNCLASSIFIED

Army MOSA Implementation Lead Point of Contact

Dr. Kelly D. Alexander ([email protected])Director, Systems Engineering Program Support (SEPS) Office of the Chief Systems Engineer (OCSE)Assistant Secretary of the Army (Acquisition, Logistics and Technology (ASA(ALT))703-545-5033 (office)571-344-3166 (mobile)

NDIA 22nd Annual Conference

Department of the Navy (DON)

Modular Open Systems Approach

(MOSA) Status

Bruce Burnside

Engineering Policy, Standards & Industrial Engineering

Group (SEA 05S)

October 21-24, 2019

Distribution Statement A – Approved for public release: distribution unlimited.

1UNCLASSIFIED – DISTRO A

MOSA supports DON by allowing us to:

– Accelerate deployment of updated technology to Fleet

– Reduce cost & cycle time

– Adapt quickly to evolving requirements & threats

– Continuously access current technology in supply base

– Avoid risk from obsolescence

– Promote ease of communication among systems and

platforms in the Naval Operational Architecture

DON MOSA Objectives


Overview & Recommendations

MOSA Implementation Policy• Directs stakeholders to implement MOSA enablers to

achieve MOSA benefits• Assigns responsibilities to stakeholders • Allows Program Office to tailor in Acquisition Strategy

MOSA Implementation Guidance• DON OSA Contracting Guidebook for stakeholders to

implement the MOSA business and technical enablers throughout the acquisition lifecycle

MOSA Best Practices

• Share Lessons Learned & Reuse artifacts• Database of Mature Standards & Technical Manuals• OAAT Tool for program self-assessment (Technical &

Business Categories)• MOSA Contracting Incentive Strategies

Train Workforce • DAU CLE-019 Training Available • Supplement with MBSE/Interface Management• Address Skills Gaps


Management of DON MOSA documents via:

–DoD Acquisition Streamlining & Standardization Information

System (ASSIST) database [DSP Standards]

–DON Naval Systems Data Support Activity (NSDSA)

Technical Data Management Information System (TDMIS)

database [Tech Manuals]

– Future Airborne Capability Environment (FACE) & Sensor

Open System Architecture (SOSA) Consortiums

–DoD High Performance Computing Modernization Program

(HPCMP)

–Naval Enterprise Modeling & Simulation (NEMS)

Environment / Automated Test & Retest Overview (ATRT)

Major DON Tools for MOSA (1 of 2)


Management of DON MOSA documents via:

–Modernized MOSA Development & Delivery (M2D2) Compile-

to-Combat in 24 Hours (C2C24) Environment

–Navy Enterprise Data Center (NEDC) & Component Enterprise

Data Center (CEDC) Hosting Environments

– Combat Management System (CMS) & Virtual Pilot Ship

(VPS) Standardization Platform Interface

– Surface Electronic Warfare Improvement Program (SEWIP)

– Submarine Warfare Federated Tactical Systems (SWFTS)

Environment

–DON Commonality Virtual Shelf Repository

Major DON Tools for MOSA (2 of 2)


Major DON Environments

• Lead programs of record included by Area

• DON Service Bus ties to DoD enterprise architecture and Command & Control

• MOSA success requires early planning by Program Teams

Reference Architecture

DoD/DON Acquisition

ASSISTTDMIS

DON CommonalityVirtual Shelf

Surface WarfareCMS VPS

SEWIP

Undersea WarfareSWFTS

NAVAIRFACE SOSA

OMS/UCI HPCMP

NAVWARC2C24 CANES NEDC CEDC

Command & Control

DON Service Bus

Unmanned SystemsNEMSATRT

HPCMP


Support DoN new programs with MOSA

implementation to achieve benefits

Continue to monitor DON programs with MOSA

assessments

Create solutions by partnering with contractors

Way Forward


Questions

Recent Updates to the DoD Approach and Strategy …...I n t e g r i t y - S e r v i c e - E x c e l...

Documents

Transcript of Recent Updates to the DoD Approach and Strategy …...I n t e g r i t y - S e r v i c e - E x c e l...