MUX_Technical_Requirements_Brief_FBO_04June2018.pdf

Unclassified

MAGTF UAS Expeditionary (MUX) Industry Day Agenda: June 6-7, 2018

Wingate Hotel – Fredericksburg, VA

DAY 1

• 0730-0845: Sign-In

• 0855-0900 Administrative Remarks Marci Spiotta / PMA-266

• 0900-0905 Introduction Col Frey

• 0905-0920 Opening Remarks LtGen Rudder / DCA

• 0920-0935 Opening Remarks LtGen Walsh / MCCDC

• 0935-1005 Marine Corps MUX Concepts & Overview Col Frey / BGen Adams

‒ CONOPS

‒ Requirement

• 1005-1020 MUX Acquisition Overview CAPT Dodge / PMA-266 ‒ Teaming Arrangements / Small Business Opportunities

• 1020-1030 Break

• 1030-1200 Detailed Briefings:

‒ Budget/Schedule Col Frey

• CBA / ICD

‒ Mission Profiles FMID / PMA-266 ‒ Technical Requirements PMA-266

• Aircraft

• Mission Systems

• Control Station / NIOPS

• Systems Engineering Environment

• 1200-1330 LUNCH

• 1330-1630 One-on-One Session 1 – Separately Scheduled Govt./Industry

DAY 2

• 0830-1630 One-on-One Session 2 – Separately Scheduled Govt./Industry

Public Release Number 2018-485

Mission Profiles

LtCol William Collier, FMID

MUX Capability Development

(Background)

Mission Profiles Overview

• Mission Profiles

– Profiles were generated and tailored from ICD

• Supports Pre-AoA and AoA analysis

• Teases out critical design characteristics that may drive cost and schedule

• Expect mission profiles to change as a result of AoA and RFI responses

• Mission profile tiers defined within publicly released MUX RFI dated

8 March 2018

MEU/ARG Early Warning (Tier 1)

Sea-based Hot Day (MIL-STD-3013)

NEO Air Reconnaissance (ISR) (Tier 1)

Advance Force Electronic Warfare (Tier 1)

Communications Relay C4I (Tier 1)

Offensive Air Support (Tier 2)

Aerial Escort (Scout) (Tier 3: Important but may be allocated to other systems)

Cargo Reduced Risk Transport

(Tier 3: Important but may be allocated to other systems)

Capability Requirements

Robert Ernst, PMA-266 Chief Engineer

• Air Vehicle

• Autonomously start-up

• Fly en-route and conduct mission

• Return To Base (RTB)

– Land on L-Class ship

– Land on un-surveyed austere 150’x150’ landing zone

– Operations shall be under supervisory control or (fully) autonomous

• Maneuver / Agility

– High energy, low speed conditions

– Hover Out of Ground Effect (HOGE) at 6,000 feet and 95 degrees

Fahrenheit (6k/95°F) at mission radius

• Air Vehicle cont’d

• Ability to operate in all weather conditions

– Operate, identify and engage threats during:

• Night and Degraded Visual Environment (DVE)

• Moderate icing, marine environments, sand and dust

• Instrument Meteorological Conditions (IMC)

• Instrument Flight Rules (IFR)

– Except most severe weather conditions (e.g. severe thunderstorms, heavy turbulence, heavy icing, etc.)

• Ability to operate in National Air Space (NAS), and International Air Space

– Air vehicle shall incorporate Sense and Avoid (SAA) capability

• Cooperative vs non-cooperative, blue and brown water operations capability in national and international air space

• Support area of operation similar to MQ-9 Reaper

• Air Vehicle cont’d

• Architecture shall support:

– Open architecture concept(s) – for payloads and weapons

– State-of-the-art avionics, anti-jam (GPS), and Alt PNT solutions

– Real-time transmission of high definition Full Motion Video (FMV)

– Full Cooperative Engagement Capability (CEC) support, providing real-time targeting solution to host ship and/or Guided Missile Destroyer (DDG)

– Transmission of sensor data: real-time targeting and Electronic Warfare (EW) data

– Command and Control: C2 or advanced C2, and C4 Naval Inter- Operability Profiles (NIOPS) to support system-of-systems approach

– Communications relay

• Airborne digital interoperability

• Secure communications network bridge

• Capability to seamlessly connect air, sea, and ground networks for C2, C4, CEC, target detection, cueing, tracking and engagement

• Air Vehicle cont’d

• Shipboard Capability

– L-Class (amphibious class ships LHA/LHD, LPD, LX(R), and ESB) ship operations

• Navy Surface combatants

– Blade spreading and folding areas similar to UH-1Y Venom

• Aircraft (spotting) allocation TBD

– C2 will be addressed by the Common Control System (CCS) and integrated in to the ship system(s) by the Government

• Survivability

– Implementation of cyber security measures and design methods to protect flight critical subsystems

– Ballistic Protection of the following aircraft subsystems:

• Fuselage

• Transmission

• Engine

• Fuel system

Performance

• Air Vehicle cont’d

– Survivability cont’d

– Electrical system

– Flight controls

– Minimize Infrared (IR) and acoustic signatures

• Air Vehicle cont’d

– Trade Space

• Cruise speed of 200 to 300 kts (with full mission systems)

• Combat radius of 350 to 700 nm (un-refueled with full mission systems)

• Aerial refueling

– Aerial refueling via standard North Atlantic Treaty Organization (NATO) probe and drogue refueling systems

• Single air vehicle Time on Station (TOS) of 8 to12 hours at 350 nm (radius)

• Cargo Operations

– Internal payload of 3000 lbs (threshold), 6000 lbs (desired)

• With no external payload

– External payload of 3000 to 9000 lbs

• With minimum internal payload of 500 lbs

Mission Systems

• Payloads*:

– Industry feedback is requested to best define mission systems support in each of the following areas:

• Early warning

• Intelligence, Surveillance, and Reconnaissance (ISR)

• Electronic Warfare

• Communication relay

• Offensive air support

• Aerial escort

– Representative Weapons as listed within the table of the MUX RFI dated 8 March 2018

– Space, Weight, and Power estimates provided by the Government and based on today’s state-of-the-art hardware/software

• Payloads should be modular/plug and play to address system requirements

– Providing for easy upgradeability

Representative payloads have been included as part of the RFI process*

EO/IR WAMI RADAR LIDAR

Hypersp ectral SIGINT ES/EA Counter

UAS

MEU/ARG Early Warning - System

T T T T T T D

2 NEO Air Reconnaissance- AV T D D D T T T D

Advance Force Electronic Warfare - System

T D T T T D T T T

Amphibious Assault C4I - System

T D T D T T T D T T

5 Amphibious Raid OAS - AV T D T D D T T T D T T

6 TRAP/CSAR Scout - AV T D D D D T T D T T

7 Recon Resupply - AV T D T T T T

Mission Profile # Mission Profile Desc Early

Warning Radar

Air Reconaissance EW Comm Relay

Surv Package

Cargo

Payload (T : Threshold, D : Desired)

Mission Payloads (Equipment) Capability Requirements

Hellfire (4 or 8) APKWS

Expendable

UAS

AARGM-

HARM AIM-9X

Sm 'd' bomb (2)

AMRAAM Torps Sonobuoys

MEU/ARG Early Warning - System

D D D

2 NEO Air Reconnaissance- AV

Advance Force Electronic Warfare - System

T T D D

Amphibious Assault C4I - System

T D

5 Amphibious Raid OAS - AV T D D

6 TRAP/CSAR Scout - AV T D

7 Recon Resupply - AV

Payload (T : Threshold, D : Desired)

WeaponsMission Profile # Mission Profile Desc

Mission Payload (Weapons) Capability Requirements

Requirement has been updated to a minimum of 8 Hellfire Missiles*

Common Control System / Naval Inter-Operability Profiles (NIOPS)

John Mayer, NIOPS SME

NAVAIR

Why Common Control System

(CCS)?

Cost efficiency through software reuse, concerted technical refresh cycles, and streamlined operator training.

Expedited fielding of new UxS platforms through the development of a mature, scalable control baseline.

Protection of a critical Naval capability through an integrated cybersecurity and flight safety approach.

Proliferation of new UxS capabilities through a build it once, make available to all model.

Provide simultaneous, multi-mission management capabilities enabling a force multiplier in unmanned operations.

Control lifecycle costs through an open architecture model

C om m onality

In te ro pe ra bi lit y

Multi-Domain Mission Management

II

CCS

Interoperable Systems

• Interoperability is critical to the Navy, and the means by which PEO(U&W) UAS programs acquire interoperability is by identifying UAS Interoperable Capabilities (UASIC) that apply to their programs

• PEO(U&W) Common Standards and Interoperability (CSI) produces technical products that vendors leverage to produce systems that provide UASICs

– Generic system models that decompose UASIC from CONOPS through functional and system models and identify critical interfaces that must be standardized

– Naval Interoperability Profiles (NIOPs) that

• Reference the appropriate standard(s) for an interface

• Establish a common implementation of the standard(s) necessary to promote a

UASIC

• Designate the Navy's preference in places where the standards are ambiguous, or where there are multiple options permitted within the standard

• CSI currently has nine NIOPs (next slide) available on their SharePoint site

– https://nserc.navy.mil/navair/csi

– Contact Jennifer DelaCruz (jennifer.m.delacruz.ctr@navy.mil) to request access

Current NIOP Library

• Command and Control (C2)

– Advanced C2 (ADV-C2) version Iv0.5.0, referenced in MQ-25 Interface Control Document (ICD) and Performance Spec, Common Control System (CCS) has implemented earlier version

– Standard C2 (STD-C2) version Iv0.1.0, RQ-21 evaluating for long-term implementation

• ISR Products

– Motion Imagery (MI) version Rv1.4.0, referenced in MQ-25 ICD and Performance Spec

– SAR/ISAR version Iv0.1.0, RQ-21 evaluating for long-term implementation

– MI-Derived Still Imagery (MIDSI) version Tv0.0.5, referenced in MQ-25 ICD

– Tracks - guidance report under development

• Networks

– Network version Iv0.1.0, addresses ADNS, referenced in MQ-25 ICD

• Datalinks

– Standard CDL (STD-CDL) version Rv1.3.0, referenced in MQ-25 ICD and Performance

Spec

– Bandwidth-Efficient CDL (BE-CDL) version Iv0.1.0, RQ-21 intends to implement in near-term

• Motion Imagery (MI) NIOP has a complete technical data package released

– MI Model that contains system engineering elements suitable for incorporation into programs’ system models

– MI NIOP that contains:

• Scope of the interoperable capability that will be achieved

• References to specific MISB, DoD, NGA, and NATO standards that are to be implemented

• Specific, testable requirements suitable for inclusion in programs’ specifications

– Example: “The Precision Time Stamp, as defined in MISB ST 0603, inserted on each frame of Motion Imagery shall be accurate within 10 msec.”

• Additional implementation guidance and notes (non-normative)

• MI NIOP addresses differing requirements based on the intended use of the imagery

– Least stringent for situational awareness

– Higher quality for exploitation

– Highest quality for strike support

Anatomy of a NIOP

Systems Engineering Environment

• Model-Based Systems Engineering (MBSE)

– The Government desires to implement MBSE that requires:

• Digital Interface Control Documents (ICDs)

• The move from paper documents and spreadsheets to models

• Allows Government to become more agile and conform to evolving

DoD and industry standards

– Move away from paper deliverables etc.

– Model-based solutions, evaluations, and certifications

• Intended to:

– Reduce number and size of SETR events

– Allows for rapid upgrades and increased speed to the fleet

– Reduce weapon systems’ Total Ownership Cost (TOC)

– Provide flexibility and agility to adapt to evolving standards and open architecture

Summary

• Path Forward

– NAVAIR to complete an AoA and war game(s) in FY19

– BAA (studies) RFP release in FY19

• Second industry day is anticipated to support BAAs

• Follow-on RFIs may be required to address payloads and system-of-systems approach etc.

• Industry Input

– Seeking industry input concerning acquisition approach as requirements continue to be developed

– Request feedback on current requirements in the following areas:

• Technical and schedule risk

• Technical trade-off (e.g. cruise speed vs combat radius vs payload capability)

• System-of-systems approach

– Single aircraft design vs multiple aircraft system-of-systems approach

Questions

Backup

CCS Architecture

TACTICAL ENTERPRISE

Operating System

Secure Network

DDS Router (RTI)

DDS Bus (RTI) Web Services Application Server

(JBOSS)

Enterpris e

Mule

ESB

Firew all

Vehicle Flight Status Service

M anage Vehicle Plan Service

Vehicle Subsystem C ontrol / Status Service

Vehicle Interface Service

Vehicle Flight C ontrol Service

Vehicle H ealth Service

Vehicle M essenger Service

M anage W

C As Service

H ealth &

M onitoring (H

AM

S) Service

Vehicle R ecovery C ontrol Service

Vehicle Launch C ontrol Service

C om m s C ontrol Service

C om m s Status Service

Field C onfiguration Service

M anage M ission Plan C atalog Service

Legacy TC S

Engineering Test Service

G round Station Status Service

G atew ay

Presentation Layer

Business Logic

Window Comms Foundation

(WCF)

XMPP

Triton Legacy Services

Triton Legacy

C

VN

H eartbeat Service

M C

S Interface Service

UCS Service

Non-UCS Services

AIS Xlator Service

Vehicle C onfiguration Service

AIS Track C orrelation Service

AIS C

apture Processing Service

C om pute R elative W aypoints

G round Subsystem

C ontrol/Status

Legacy

U

IP G

round Service

M ap Point Service

R elative N avigation Validation Service

System Interface Service