Atch 4 Functional Req. Perf. Spec.pdf

H9240823R0001

SECTION J, ATTACHMENT 4

MQ-1C ER OMSA/C2 FUNCTIONAL REQUIREMENTS PERFORMANCE

SPECIFICATION REFERENCE

1.0 OPEN MISSION SYSTEM (OMSA)

1.1 Voice Relay

The OMSA shall provide voice relay in support of USSOCOM customers.

1.2 Data Translation

The OMSA shall be capable of converting incoming data types to other data types. For example, an incoming message in a Cursor on Target format should be able to be converted to Variable Message Format for transmission over alternate datalinks/networks.

1.3 Link16

The OMSA shall be able to send and receive link 16 messages.

1.4 Remote Zeroize

All OMSA controllers shall be able to remotely clear the OMSA's controlled cryptographic information or communications security information. For example, upon receipt of a "zeroize" command from an authorized controller, the OMSA should command all connected radios to clear controller cryptographic keys.

1.5 Operator Network Configuration

The operator shall be able to remotely configure or re-configure the network configuration of the OMSA to support integration with USSOCOM and Joint Customer networks during any phase of the mission.

1.6 Data Isolation

The OMSA shall be able to encrypt, using National Security Agency (NSA) approved methods, and logically isolate data transmitted over the primary datalink from the baseline aircraft data.

1.7 Data Encryption

The OMSA shall encrypt all data transmitted to controllers using NSA approved cryptographic methods sufficient for the classification level of the data in transport.

1.8 Reliable Timing Source

The OMSA shall provide a timing source capable of maintaining time to within 5 secs over a 48 hour period without reconditioning or retraining. The OMSA may be reconditioned or trained during or prior to pre-flight using external sources (e.g. Global Positioning SO-p Kit/Global Navigation Satellite SO-p Kit).

1.9 Ground Station Data Relay

The OMSA shall send and receive digital data to and from controllers and airborne RF networks.

1.10 Bandwidth Management

The OMSA shall be able to constrain the bandwidth utilization of its data transmitted over the primary datalink to avoid interference with the baseline aircraft data. This shall be configurable both for transmit and receipt of data, asymmetrically.

1.11 Operational Availability - Deployed

The deployed platoon with four aircraft must sustain the capability for two sorties per 24/7 period (one orbit total) with the capability to surge for a third sortie on order for limited periods.

1.12 Power Control

All controllers shall be able to toggle power to individual aircraft subsystems.

1.13 Materiel Availability

The system must maintain a combat operational availability of 80%. This is based on a complete system of systems.

1.14 MISB 0903

Objects identified by the Aided Target Detection and Recognition function shall be encoded In accordance with the Motion Imagery Standards Board (MISB) 0903 (Video Movement Target Indicator (VMTI)) metadata. 0903 metadata shall be added to the transport stream (T).

Metadata shall be encoded as an independent elementary stream (O).

1.15 Aided Target Detection from EO/IR Sensor

The OMSA shall identify points of interest within the motion imagery from the Motion Imagery Sensor to enhance operator and battlefield situational awareness.

1.16 Voice over IP

The OMSA shall send and receive voice data to and from the control station and airborne Radio Frequency (RF) networks. VoIP encoding shall be in accordance with the Unmanned Aircraft Systems Interoperability profiles for Family of Systems Block I.

1.17 Operator Awareness

The OMSA shall notify the control station operator of any detected signals or anomalous behavior that indicates an EMS threat to the OMSA performance.

1.18 Airborne Data Relay

The OMSA shall be able to relay data between airborne RF networks.

1.19 Radio Management

All controllers shall be able to remote configure the SO-p Kit's radios to include waveform, power levels, encryption, modes of operations, and frequencies.

1.20 Distributed Control over alternate datalinks

The OMSA shall enable level control of the MQ-1C ER payloads (T), aircraft (O), and weapons

(O) through on-board communications systems, other than the inherent Line Of Sight (LOS) and Satellite Communication (SATCOM) systems.

1.21 Processing System

The following section details requirements applicable to elements within the system that perform data processing functions (i.e. mission/flight computers).

1.21.1 Volatile storage reserve

[408] The processing system shall have 50% volatile storage reserve, under nominal operating conditions, at delivery.

1.21.2 Processing reserve

[406] The processing system shall have 50% reserve nominal processing at initial delivery

1.21.3 Non-volatile storage reserve

[407] The processing system shall have 50% reserve non-volatile storage at delivery.

2.0 COMMAND AND CONTROL (C2)

2.1 Flight Control Software Compatibility

The system shall be able to operate all modes of the MQ-1C Extended Range aircraft through all phases of operation to include pre-flight, taxi, takeoff, cruise, descent, landing, and post-flight.

The system should use the software released by the Extended Range Multi-Purpose program-of-record to the greatest extent practical, to include the Core UAV Control System (CUCS) and General Atomics Vehicle Specific Module (VSM).

2.2 Multiple Baseline Control

The system shall be able to control the current, and at least two previous baselines of the Extended Range Multi-Purpose system. The intent of this requirement is to enable interoperability between MQ-1C Extended Range Aircraft operating on different program of record fielded baselines. For example, the Command-and-Control system shall be able to interoperate with the 4.3.5revA, 4.3.5rev-, and 4.3.4revB software baselines released from the US Army Unmanned Aircraft System Program Office.

2.3 Emplacement

The system shall be capable of achieving a minimum operational capability (one aircraft), set-up initial launch/recovery/site equipment, plan initial and lost-link way point, emplace necessary safety equipment, and launch one MQ-1C ER), within 8 hours of arriving at a preplanned launch site.

2.4 Displacement

After the operational unit has achieved a minimum operational capability, if given the order to move to a new L/R site or perform split-based operations (O), the system’s minimum operational equipment will be ready for movement in four hours or less (not including unit BII and ancillary equipment) (T), including unit BII and ancillary equipment (O). When moving to a new L/R site, some operations (e.g., maintenance, refuel, rearm, SATCOM) may be limited at the new site based on the availability of personnel, tools, and equipment while transitioning between L/R sites (T).

2.5 Aircraft Maintenance Operations

The system shall be able to conduct aircraft maintenance and diagnostic functions to replicate the functionality of the current Improved Portable Maintenance Aide (IPMA). This includes functionality necessary to conduct all maintenance checks of the system.

2.6 System Maintenance

In the event of a component failure, the mean-time-to-replace (MTTR) shall be 3 hours or less.

The maintenance concept for the system is “reboot, reimage, replace”. “Replace” in this context means to swap the system, subsystem, or component with an equivalent spare part to re-establish operations. “Reimage” in this context means to reload the software baseline on the system with a fresh installation to potentially eliminate any corruption. “Reboot” in this context means to either perform a hard (remove power) or soft restart of the software to clear corruption. There is no expectation of subsystem or component level troubleshooting beyond identification of the failed element.

2.7 Uninterruptable Power

2.7.1 Minimal Configuration

When configured with just the processing unit and peripherals, the system shall be able to operate for no less than 60 minutes without primary power.

2.7.2 Full System

In a full workstation configuration, the system shall be able to operate for no less than 60 minutes without primary power. This includes locally attached datalink equipment for a single datalink.

2.7.3 Dual Workstation

In a full mission configuration (i.e. two workstations) the system shall be able to operate for no less than 30 minutes without primary power. This includes locally attached datalink equipment for a single datalink.

2.8 Datalink Compatibility

The system shall integrate with the current Universal Ground Data Terminal (UGDT), SATCOM Ground Data Terminal (SGDT), and Rover6 modem with Ku directional Antenna.

2.9 Mission Data Archival

The system shall locally archive not less than 72 hours of mission data for the EO/IR sensor and nose-camera. For the purposes of calculations, it shall be assumed that total video bandwidth is 10Mbps.

2.10 Emergency Procedures

The system shall not require modification of existing emergency procedures from the operator’s manual.

2.11 File Sharing

2.11.1 Operator to Operator Manual File Sharing

Operators shall be able to transfer files electronically to other Operator Workstations on the network without requiring other systems as an intermediary. This is intended to pass mission products directly between Aircraft and Payload Operators even when operating without the MSS or other supporting systems.

2.11.2 Operator to Operator Automated File Synchronization

The systems shall be able to synchronize files in designated directories electronically between workstations without operator initiation or action. This is intended to ensure that some data that is regularly shared and used for communication between Aircraft and Payload Operators is kept in sync.

2.11.3 MSS Files Transfers

The system shall be able to transfer files to and from the MSS.

2.12 Voice Communications

2.12.1 Crew communications

The system shall be able to exchange digital voice between Aircraft Operator and Payload Operator workstations to facilitate crew communications.

2.12.2 Tactical Communications Box (TOCBox) Voice Interoperability The system shall be able to exchange digital voice with the TOCBox.

2.12.3 Hand-free Voice

The system shall allow operators to communicate via digital voice without requiring the use of their hands. This requirement may be satisfied with voice activation or by means of an alternate actuator (e.g., foot-pedal) for push-to-talk.

2.13 Motion Imagery

The system shall be able to re-stream motion imagery data from the MQ-1C to a configurable multicast address.

2.14 Operational Availability

The system shall demonstrate an Operational Availability (Ao) such that total Operational Unit Ao does not fall below 80% (T), 90% (O).

2.15 Storage and Processing

2.15.1 Processing Capacity

The system shall have 50% reserve processing power under nominal operating load upon delivery of the initial software baseline.

2.15.2 Non-Volatile Storage Capacity

The system shall have 50% reserve non-volatile storage under nominal operating loads upon delivery of the initial software baseline.

2.15.3 Volatile Storage Capacity

The system shall have 50% reserve volatile storage under nominal operating loads upon delivery of the initial software baseline.