Statement_of_Objectives_ASSB.docx

Statement of Objectives

1.Overall Program Objectives

· Multi-Phased Program

· Multi-Program

· Multi-Contractor

2. Place of Performance

· Lab space APG – Government Owned

· Contractor facilities

· Administrative space APG – Onsite and Offsite

3. Contract Objectives

· Provide Post Deployment Software Support and Post Production Software Support maintenance, and sustainment of multiple programs of record/software systems using systems engineering methodologies.

· Systems include the following:

· GRCS

· EMARSS-S

· EMARSS G, V, M

· OGS SIPR Baseline

· TSP

· ARL-E

· STARlite

· System Descriptions can be found in Attachment 1.

4. Program Management Objectives

· The management objectives are to allow the offeror the maximum flexibility to innovatively manage the projected schedule, performance, risks, warranties, subcontracts, and data to provide the goods or services that satisfies the government’s performance requirements.

· Monthly Cost Reports – Reports will include breakout by CLIN/WBS based upon G4 priorities by system

· Monthly Performance Reports – provides detailed performance on CLINS/WBS

· Trip Reports

· Travel approval

· Mandatory Training

· Plan, prepare, validate, conduct, witness, analyze, review, provide technical support and/or evaluate software tests and demonstrations.

· conduct Safety tasks and develop Safety Plans and Reports

· Plan, participate, conduct, brief, provide technical expertise and recommendations, and record minutes at meetings and program reviews

5. Engineering Objectives

· Design, develop, and implement software

· Design, develop, and implement software changes

· Validate Software Problem Reports

· Develop/Maintain System Security Plan(s) (SSPs) for our development & test, certification and accreditation, and fielded systems.

· Maintain ATOs under RMF, following all required NSA guidelines. This includes maintaining all NSA databases and websites needed to track ATOs and IAVAs.

· Maintain continuous monitoring under RMF

· Perform Configuration Management for operational software, support software, utilities, data, documentation, and computer resources

· Support software release packages

· Conduct software engineering assessments and technical evaluation of software code for completeness, accuracy, clarity, maintainability, supportability, modifiability, portability, reusability and performance.

6. Test Support Objectives

· Perform and support Formal Qualification Test

· Perform and support Independent Verification & Validation testing

· Develop Test cases, test plans, and test reports

· Configure and test commercially available hardware or software tools required for PPSS/PDSS

7. Logistics Objectives

· Maintain, develop, and update documentation and training packages for the SEC ASSB Branch portfolio of systems.

· Conduct Instructor and Key Personnel (I&KP) Training

· Develop transition plans and schedules to transition systems from acquisition development to sustainment

9. Facilities Management

· Support and maintain SEC ASSB Branch Software Environments, Facilities, and Information Technology Infrastructure

· Integrate new hardware/software components and ensure that the support environment is maintained in a functional condition at all times

· Semi-Annual status of GFM/GFE/CAP

· Provide recommendations for Information Technology contingency planning and operate and maintain the Continuity Of Operations Plan (COOP) Capability

10. Deliverables (See Attachment 2 – Schedule of Deliverables)

· Monthly IAVA

· Quarterly IAVA, only required in PPSS

· Quarterly STIGS, only required in PPSS

· Software Releases (Quarterly updates and Annual Major Release)

· Tech Bulletins

· Version Design Descriptions

For all non-IAVM software deliveries, the following documentation will be provided to the government:

· SOFTWARE REQUIREMENTS SPECIFICATION (SRS)

· SOFTWARE TRANSITION PLAN

· SYSTEM/SUBSYSTEM SPECIFICATION (SSS)

· SYSTEM/SUBSYSTEM DESIGN DESCRIPTION (SSDD)

· SOFTWARE DESIGN DESCRIPTION (SDD)

· SOFTWARE TEST PLAN

· SOFTWARE TEST REPORT

· SOFTWARE VERSION DESCRIPTION (SVD)

· SOFTWARE USER MANUAL (SUM)

· System Administration Manual (SAM)

· INTERFACE CONTROL DOCUMENT (ICD)

· Integrated Master Schedule (IMS)

· VULNERABILITY SCAN COMPLIANCE (VSC) REPORT

· Requirements Tractability Matrix

· Tactics, Techniques, Procedures (TTP)

· Technical Analysis

· Technical Bulletin (TB)

· Training Support Package (TSP)

· SYSTEM SAFETY HAZARD ANALYSIS REPORT (SSHAR)

· Test Plans

· Test Reports

· PO&AM Metrics

· OPSEC Plan

· CMRA reporting

· Government-Furnished Equipment reporting

· Configuration Management Plan

· Measurement and Analysis Plan

· Quality Assurance Plan

Attachment 1: System Descriptions

ENHANCED MEDIUM ALTITUDE RECONNAISSANCE AND SURVEILLANCE SYSTEM (EMARSS) – SIGINT (S) DESCRIPTION

System Name: Enhanced Medium Altitude Reconnaissance And Surveillance System (EMARSS)

System Manager: Program Manager Sensors - Aerial Intelligence (PM S-AI), under the direction of the Program Executive Office Intelligence Electronic Warfare and Sensors (PEO IEW&S).

System Proponent: Intelligence and Security Command (INSCOM), Army Training And Doctrine Command (TRADOC), United States Army Intelligence Center & School (USAICS), TRADOC System Manager (TSM) Unmanned Aerial Vehicle (UAV), Fort Huachuca, AZ

System Deployed: 224th MI BN, Savannah Ga, 15th MI BN, 116th MI BN

System Overview: EMARSS is a multi-intelligence (multi-INT) AIEW&S system dedicated specifically to directly support the tactical commander. It is intended to enhance BCT effectiveness by defining and assessing the environment and providing targeting support and surveillance. EMARSS aircraft will be located within Aerial Exploitation Battalions (AEB), which are assigned to the U.S. Army Intelligence and Security Command (INSCOM). INSCOM maintains a maximum forward-deployed EMARSS capability using the Capabilities-Based Rotation (CBR). There will be an AEB Forward (FWD) element supporting missions in the target area and an AEB Rear element. When deployed, EMARSS assets are either in direct support of or attached to tactical ground maneuver forces, normally a Brigade Combat Team (BCT).

The original EMARSS also known as EMARSS–S system consist of manned aircraft equipped with an Electro-optic/Infrared (EO/IR) full motion videos (FMV) sensor, four COMINT sensors, a BI Sensor, line-of-sight and beyond line-of-sight (LOS/BLOS) communications suites, and a self-protection suite. This system transitioned to sustainment in FY 17.

EMARSS G, M, and V represent PM SAI system airborne platform configurations which are being added to the EMARSS Program of Record and which will be transitioning to sustainment in FY 18. These platform variants are three distinct designs/capabilities that will result from the conversion of Quick Reaction Capability (QRC) programs into the EMARSS program of record (POR) family. There are unique requirements necessary to sustain the additional platforms and sensors. Additional Platforms include the Liberty, TACOP, Constant Hawk, and VADER. Additional Sensors include the VADER RADAR, Wide Area Surveillance RADAR, Light Imaging and Ranging RADAR, Santa Fe COMINT sensor, and the Pennant Race COMINT Sensor.

EMARSS-G is the common baseline that represents the conversion from the Constant Hawk and TACOP aircraft to a common “Geo-Location” POR platform. Three primary sensor packages are used on EMARSS-G for role-specific tasking. These include: the Wide Area Motion Imagery (WAMI), Light Detection and Ranging (LIDAR), and High Definition (HD) Full Motion Video (FMV). EMARSS-G is capable of changing the onboard sensor depending on mission requirements; AWAPSS or LIDAR. Depending on the sensor used, EMARSS-G can provide Intelligence Preparation of the Battlefield (IPB), High-Value Target (HVT) Location and Identification, Mission Over-watch (MO), Situation Development (SD), and Persistent Area Assessment (PAA) in support of Brigade Combat Teams (BCT). The CH-A and TACOP aircraft have distinctly different starting points prior to this EMARSS variant effort but will have a common configuration at the conclusion of conversion.

EMARSS-M is the common baseline that represents the conversion from the Liberty and MARSS aircraft to a “Multi-Intelligence” POR platform. The platform will perform EO/IR and Aerial Precision Guidance (BI) primary and EO/IR and COMINT secondary on-board missions. In addition, EMARSS-M will leverage the Operational Intelligence Ground Station (OGS) and workstations for all COMINT control, processing and exploitation.

EMARSS-V is the common baseline that represents the conversion of the Vehicle and Dismount Exploitation Radar (VaDER) aircraft to an EMARSS POR platform. The platform will perform SAR/MTI and EO/IR as primary and COMINT and BI as secondary on-board missions. EMARSS-V will function as an Aerial ISR (AISR) asset providing Imagery Intelligence (IMINT) and VADER support of Aerial Exploitation Battalions (AEB) in tasked Areas of Responsibility (AOR).

EMARSS and all its variants will operate as a single platform in support of tactical missions. Mission altitude and flight tracks are chosen to optimize sensor data collection on the target area of interest while avoiding known threats. The mission altitude and flight tracks may be selected to strike a balance among the capabilities of the multiple sensors, or to optimize collection from individual sensors based upon the specific mission collection tasking dictated by the tactical commanders Priority Intelligence Requirements (PIRs) and Commanders Critical Information Requirements (CCIR). EMARSS will provide rapid response to Combat Forces IEW&S tasking with centralized Processing, Exploitation & Dissemination (PED) of IEW&S data at the DCGS-A, while the onboard IMINT and APG operators are simultaneously collecting and analyzing selected information and transmitting critical FMV and intelligence reports to engaged tactical forces directly from the EMARSS aircraft.

The EMARSS aircraft-based system will be located within Aerial Exploitation Battalions (AEB), which are part of the Military Intelligence (MI) Brigades that support theater Army as part of U.S. Army Intelligence and Security Command (INSCOM). The EMARSS ground-based sys-tem will include ground-based software that consists of DCGS-A, BFT, and some COMINT components, as well as the DSIL and EMV. The EMARSS system will consist of a manned air-craft, equipped with Electro-Optic/Infrared (EO/IR) FMV sensor, a COMINT collection system, a BIG IRON system, Line-of-Sight tactical and Beyond Line-of-Sight (LOS/BLOS) communications suites, plus a self-protection suite.

The EMARSS Maintenance Vehicle (EMV) is a “step van” vehicle that facilitates the check-out and maintenance of various sensor and data dissemination systems used on the EMARSS airborne system. The main purpose of the EMV is to support EMARSS aircraft in the field through their pre-mission, post-mission, and maintenance activities throughout the day. The EMARSS Maintenance Laptop will perform a similar role, and is able to perform preflight operations without the use of the EMV.

System Interoperates With: DCGS-A, NSANET, SIPRNET, PRC 117, ARC-231, Blue Force Tracker, DEDICATED LAND LINE, SECURE FAX, NON-ARMY IEW ABN SENSORS, CGS, TENCAP, ONE ROOF, ROVER 5/6, SATCOM, ENT, VORTEX, COMINT (1202 DRT, GEN 5/Adder, PRISM, and BAE SIGINT Payload) ASE- AN/APR-39’S, AN/APR-44’S, Theater Net-centric Geo-location (TNG)

Other Systems Dependent On: DCGS-A, and national intelligence assets (details classified).

Software Application Description:

The IMINT sub-system consists of a Wescam MX-15HDi Electro-Optic / Infra-Red (EO/IR) im-aging sensor, Haivision Makito Encoders, the IMINT workstation hardware and exploitation software, digital video recording system, and analog video switch. Digital video (1080p, HD-SDI) is generated by the Wescam MX-15 turret and sent via dedicated, hard-wired connections to the Haivision Makito Encoders. KLV format meta-data is supplied to the encoders in the vertical blanking of the video and over Ethernet from the Orion software run-ning in the IMINT workstation. The Makito Encoders combine the video and meta-data into an MISP compliant MPEG-2 transport stream, which is multi-cast to the IMINT workstation MIS-screener software and to the PICT-E recording system. One channel of digital video is split prior to encoding by the Makito Encoders and converted to HDMI format and then sent directly to the IMINT workstation displays. NTSC analog composite video is sent from the MX-15 to the Kramer Composite Video Switch over direct hard-wired video connections. The Kramer video switch is controlled over an RS-232 connection from the IMINT workstation. The video switch routes the analog video to the Vortex and Mini-TCDL radios, to the cockpit SAD, and to the IMINT workstation displays. The MX-15 is controlled by the MX-15 hand-controllers (direct RS-422 connections) and by the Orion software over Ethernet. The MX-15 also sends KLV meta-data over Ethernet to the Orion software and the Orion soft-ware sends certain additional pieces of meta-data back to the MX-15 over the RS-422 Moving Map interface. The MX-15 HDi, Encoders, analog video switch and router contain embedded firmware while the IMINT workstation hardware runs all of the IMINT-related software.

The COMINT subsystem comprises of both an air- and a ground-based elements. The COMINT subsystems located on the EMARSS aircraft are designed to perform electronic surveillance on a subset of modern commercial signals. As new exploitation software and firmware become available for more modern signals, each COMINT subsystem may be upgraded in the field to provide new interception and collection capabilities. Current capabilities include, but are not limited to, data collection, signal exploitation, TOA, LOB, DF, and GEO. Individual COMINT subsystems are capable of collecting data on a subset of Signals Of Interest (SOIs) for the EMARSS program. As data is collected on the EMARSS aircraft, it is processed and passed to one of four DCGS-A provided COMINT ground workstations.

Each COMINT ground workstation located within the DCGS-A provides an interface from the SDR operator located on the ground to the air-based SDR. The interface allows the operator to supply each SDR with mission tasking, command and control, health and status reports, data re-ports, and audio output through dedicated ground-based software. In addition to producing various reports, the COMINT ground workstation allows the operator access to Audio, DF, and Geo.

The following table below describes the software applications within the EMARSS System by platform and Subsystem. Software Application Type column identifies the software maintenance requirements that the Contractor will be required to be performed on this task. All software whether it is COTS, GOTS, or PDSS/PPSS will be tracked via the CCB and Project Forge.

Sensors

ELMA and Workstations (On Board aircrafts)

EMARSS Maintenance Vehicle and laptop

Ground EMARSS COMINT Applications on NSA net

Note – Sharing of test environment is required between multiple PM SAI and PM DCGS-A programs.

Available For Use at Government Facilities and support all SIGINT Sensors GGB/OGS NSA Rack

GGB/OGS NSA domain Workstations

GRCS Air to Ground Network Equipment

Trilogy MIU

Router 3845

FTX1526AJG7

PM DCGS-A and SEC are completing the transition plan for the next version of the DCGS-A OGS SIPRNET software baseline. This version includes newer versions of PM SAI QRC ground software and also DCGS-A V 3.1.7 software. It is expected that this version will transition to SEC in FY 19. It is expected that SEC will be only be supporting one SIPRNET software version at a one time. SEC will not need to be supporting the older version once the newer version is transitioned to sustainment.

GUARDRAIL COMMON SENSOR SYSTEMS (GRCS)

A. NOMENCLATURE AND SYSTEM NAME: AN/USD -9B/C/D/E AN/TYQ-224B GUARDRAIL COMMON SENSOR SYSTEMS (GRCS)

B. MDEP: AMLC

C. NSN: 5895-01-365-5599, 5895-01-264-9757; 5895-01-264-9757; 5895-01-365-5597; 5895-01-414-9805 D. SYSTEM PROPONENT: INSCOM, TRADOC, USAICS, TSM UAV, Ft Huachuca AZ E. SYSTEM MANAGER: PM Sensors Aerial Intelligence (SAI), POC Mark O’Neill Tel 443 861 2000 F. DEPOT MAINTENANCE PPSS LEAD: SEC Intelligence, Electronic Warfare & Sensors (IEW&S) Directorate, Aerial & Terrestrial Sensors / Sensors and Mission Equipment (SME) Division, POC: Gary Bissett. Tel.: 443-861-3831.

G. DESCRIPTION: GUARDRAIL COMMON SENSOR (GRCS) Systems are airborne communications and electronic intelligence (COMINT & ELINT) assets available to Corps and Theater commanders and national intelligence-gathering efforts, providing computer-assisted intercept, identification, precision location, and analysis of hostile communications networks and electronic signals and reporting of the intelligence product to unit commanders and the intelligence community via a multitude of tactical and national networks including Joint Worldwide Intelligence Communications System (JWICS), Secret Internet Protocol Router Network (SIPRNET), and National Security Agency (NSA) net. GRCS provides the Corps Commander with a critical "deep look" into the battlefield to facilitate both tactical and strategic decision making. These systems provide Army commanders with tactical communications and electronics intelligence during daily missions and provide support to the national intelligence-gathering effort. They support split-based operations through a satellite relay which allows most mission functions to be conducted via remote operational control from anywhere in the world using only a minimal forward Operational Intelligence Ground System (OGS) S280 shelter and necessary datalink and Satellite Communication (SATCOM) equipment. The datalink equipment maintains line-of-sight communications with the airborne sensor assets and the SATCOM equipment provides reach back to the GRCS Army Exploitation Battalions (AEBs).

GRCS has a common ground software baseline for all Guardrail Systems, known as the Tactical SIGINT Baseline (TSB). This was developed to enhance interoperability among the four systems and with other intelligence systems, decrease the logistical footprint of the ground segment for quick and rapid deployment, increase system reliability, and provided a common baseline for integration into an OGS shelter.

The number of GRCS subsystems has been increased by PM SAI as part of a GRCS Modernization effort to accurately identify and locate new emerging signals of interests. Major Subsystems recently added as part of the GRCS Modernization include an ELINT subsystem, X-MIDAS and High Band COMINT (HBC) Subsystems for other than traditional signals, Communications High Accuracy Location System-Compact (CHALS-C) for COMINT Time difference of arrival, and Enhanced Situational Awareness (ESA) which provides for traditional Direction Finding and audio for traditional signals. All of these subsystems have both ground and air components. The ground components are being added to Tactical SIGINT Baseline (TSB).

H. SYSTEM INTEROPERATES WITH: NSA NET, JTT, JWICS, SIPRNET, ONE ROOF, DCGS-A, ASE/ACS - AN/APR-39’S, AN/APR-44’S I. OTHER SYSTEMS DEPENDENT ON: : ABCS, DCGS-A, NATIONAL INTELLIGENCE SYSTEMS (details classified).

J. SYSTEM(S) DEPLOYED: 15th MI BN, III Corps; 116th MI BDE, 205th MI BDE; 224th MI BN, 525th MI BDE; Split base operations CONUS and OIF/OEF AOR; 3rd MI BN, 501th MI BN, Eight USA, Korea, Fourteen systems were converted to the GRCS Modernization Configuration and will remain deployed for the foreseeable future.

K. OTHER FACTORS INFLUENCING SUSTAINMENT REQUIREMENTS:

Legacy aircraft have been de-fielded across the fleet leaving the new GRCS X models as the sole model. All PM SAI COMINT applications across PM SAI Systems are being integrated into the GRCS Tactical SIGINT Baseline (TSB) software. Requirements for these new applications are being tracked in the other PM SAI COMINT Systems POM lines, but those systems are leveraging common GRCS infrastructure pieces.

II. RESOURCE REQUIREMENTS

SEC creates one major release per year and is able to get critical fixes and upgrade during quarterly patches. High Priority new features and fixes involve being able to intercept and collect new emitters, exchange information with NSA, and meet new reporting requirements. Other critical requirements involve meeting new INSCOM operational and infrastructure changes network.

Operational Intelligence Ground System (OGS)

A. NOMENCLATURE AND SYSTEM NAME: AN-TYQ-224(B) Operational Intelligence Ground System (OGS)

B. MDEP: AMLC

C. NSN: 5895-01-580-6434

D. SYSTEM PROPONENT: INSCOM, TRADOC, USAICS, TCM Intel Sensors, Ft Huachuca AZ

E. SYSTEM MANAGER: Program Manager, Distributed Common Ground System – Army (PM DCGS-A)

F. DEPOT MAINTENANCE PPSS LEAD: SEC Intelligence, Electronic Warfare & Sensors Directorate, Sensors and Mission Equipment (SME) Division.

G. DESCRIPTION: OPERATIONAL INTELLIGENCE GROUND SYSTEM (OGS) integrates existing DCGS-A Program of Record (POR) systems into a single readily deployable S-280 Shelter and provides a common multi-INT Processing, Exploitation, and Dissemination (PED) that supports current and future Army Airborne Intelligence, Electronic Warfare and Sensors (IEW&S) platforms. It provides the soldier at the Corps-level and Army Exploitation Battalions (AEBs) an increased integrated capability with access to five networks (NSA, JWICS, SIPR, NIPR & Coalition) using common software baselines which include Guardrail Common Sensor (GRCS) ground and DCGS-A software. The OGS Shelters are replacing the GRCS Guardrail Ground Baseline (GGB) shelters and the Tactical Exploitation System (TES) Forward Shelters and will provide a common PED for future Airborne IEW&S platforms such as Enhanced Medium Altitude Reconnaissance and Surveillance System (EMARSS). OGS Advanced Miniaturized Data Acquisition System (AMDAS) software baseline involves the integration of multiple technologies and equipment to produce a system which is used to receive tactical Multi-Intelligence (Multi-INT) information for the OGS System.

The OGS will provide the Corps Commander with a critical "deep look" into the battlefield to facilitate both tactical and strategic decision making. Being the common PED for Army IEW&S platforms, the OGS will provide Army commanders with tactical communications and electronics intelligence during daily missions and provide support to the national intelligence-gathering effort. They support split-based operations through a satellite relay which allows most mission functions to be conducted via remote operational control from anywhere in the world using only a minimal forward OGS S-280 shelter and necessary datalink and Satellite Communication (SATCOM) equipment. The datalink equipment maintains line-of-sight communications with the airborne sensor assets and the SATCOM equipment provides reach back to the AEBs.

H. SYSTEM INTEROPERATES WITH: OGS interoperates with the following: GRCS, EMARSS, NSA NET, JTT, JWICS, SIPRNET, ONE ROOF, DCGS-A, EPDS exchanges information with SATCOM, MILSATCOM, and TACSAT. SCS exchanges information with U2 – IADL2/DDL2, Global Hawk, TACSAT, Guardrail, ARL, Apache, Hunter, LAMPS, P-3, ASTOR, SHARP, MP-CDL/

I. OTHER SYSTEMS DEPENDENT ON: The following system rely on OGS to perform their mission: Joint Tactical Terminal (JTT), Army Battle Command System (ABCS), DCGS-A, NATIONAL INTELLIGENCE SYSTEMS

J. SYSTEM(S) DEPLOYED: OGS is deployed at the following locations: 224TH MI Battalion, Hunter Army Airfield, Savannah, GA (XVIII ABN Corps); 15th MI Battalion, Ft Hood, TX, (III Corps); 3rd MI Bn, Republic of Korea (Eighth USA); 1st MI Battalion, Wiesbaden, GE (V Corps); 18TH ABC, Ft. Bragg, NC; III Corps, Ft. Hood, TX; I Corps, JBLM, WA Projected OGS Fielding: 8 Systems total for AEB (2 per AEB), 3 Systems total for Corps.

K. OTHER FACTORS INFLUENCING SUSTAINMENT REQUIREMENTS:

The OGS is combination of systems which reside in one shelter and also in the INSCOM Military Intelligence Brigade garrison locations. There are three (3) different networks in an OGS shelter which are JWICS, SIPRNET, and NSAnet. All NSAnet infrastructure requirements and common applications are tracked under the Guardrail. All sensors specific software are tracked under GRCS or EMARSS.

Small Tactical Radar - Lightweight (Common Name: STARLite)

1. System Name: Small Tactical Radar - Lightweight (STARLite)

2. System Manager: Program Manager Sensors - Aerial Intelligence (PM S-AI), under the direction of the Program Executive Office Intelligence Electronic Warfare and Sensors (PEO IEW&S).

3. System Proponent: TRADOC Capability Manager Aerial (TCM-A)

4. System Deployed: The current STARLite radar is being fielded in support of Operation Freedom’s Sentinel and selected training and garrison sites Continental United States (CONUS)/Outside Continental United States (OCONUS). Areas of responsibility include:

(including spares)

5. System Overview: STARLite is a small, lightweight SAR/MTI (Synthetic Aperture Radar/Moving Target Indicator) used for supporting tactical operations by providing precise battlefield intelligence in numerous types of weather and battlefield obscurants, day and night. The MTI mode detects moving targets, to include man-sized detection, and provides classification and location information and performs cross-cue with the Electro-Optic/Infrared (EO/IR) sensors. STARLite significantly improves battlefield situational awareness and optimizes force maneuver and engagement for mission success through its capability to deliver real-time intelligence imagery to users. SEC sustainment efforts include maintain the software in the embedded sensor and the ground control software, and related accreditations.

6. System Interoperates With: Gray Eagle and Universal Ground Control Stations (UGCS).

7. Other Systems Dependent On: None.

8. Software Application Description:

The STARLite radar system, also referred to as STARLite, consists of a Synthetic Aperture Radar (SAR) / Moving Target Indicator (MTI) radar system, referenced from here on as “the radar system”. The radar system consists of the radar payload subsystem, Ground Control Station – Element subsystem (GCS-E), and transit containers. The radar payload has multiple subassemblies, including the antenna, electronics assembly, power supply, INS/GPS, A-kit, and OFP software. This document applies to radar system performance as delivered with Operational Flight Program (OFP) and GCS-E software configuration version 0400. Figure 1.1-1 shows the system family tree.

Figure 1.11 - Radar System Requirement Levels

The SAR/GMTI System provides a multi-mode radar capability to the U.S. Army’s Extended Range Multi-Purpose (ERMP) Gray Eagle unmanned aircraft system (UAS). The SAR/GMTI radar payload, while functioning aboard the UAS, provides battlefield commanders increased situational awareness through wide area surveillance, imaging of stationary targets, and detection of moving targets. The SAR/GMTI payload is capable of on-board processing and transmission of near-real-time imagery and vehicle detection data to the UAS universal ground control station (UGCS) via a digital data link.

The following software must be installed on the target system in order for the GCS-E software to function properly:

· Microsoft redistributable runtime DLLs VS2013 (x86) (12.0.30501)

· Microsoft .NET Framework 4.5.2 Version 4.5.51209

· FalconView 4.2.1

In addition, the exploitation tool, AiTD Process requires the following software be installed in order to function properly:

· Microsoft redistributable runtime DLLs VS2008 SP1 (x86) (9.0)

The following port numbers will need to be unblocked for the GCS-E to function properly.

Table A1 – GCS-E Port Numbers

A. NOMENCLATURE AND SYSTEM NAME: Target Acquisition System, AN/ZPY-1A, Small Tactical Radar - Lightweight (Common Name: STARLite)

B. MDEP: AMLC

C. NSN: 5864-01-603-3028

SYSTEM PROPONENT: TRADOC Capability Manager Intel Sensors (TCM-IS) E. SYSTEM MANAGER Program Manager (PM), Sensors-Aerial Intelligence (SAI), Product Manager (PdM), Sensors-Unmanned & Rotary Wing (SURW), LTC Xaviera-Chevonne Williams, 443-861-2290 F. DEPOT MAINTENANCE PPSS LEAD: SEC, Terrestrial Sensors Branch, Intelligence, Electronic Warfare & Sensors Directorate (IEW&S) POC: John Gantert. Tel: 443-861-2300 G. DESCRIPTION: STARLite is a small, lightweight SAR/MTI (Synthetic Aperture Radar/Moving Target Indicator) used for supporting tactical operations by providing precise battlefield intelligence in numerous types of weather and battlefield obscurants, day and night. The MTI mode detects moving targets, to include man-sized detection, and provides classification and location information and performs cross-cue with the Electro-Optic/Infrared (EO/IR) sensors. STARLite significantly improves battlefield situational awareness and optimizes force maneuver and engagement for mission success through its capability to deliver real-time intelligence imagery to users. SEC sustainment efforts include maintain the software in the embedded sensor and the ground control software, and related accreditations.

H. SYSTEM INTEROPERATES WITH: The STARLite radar interoperates with the Gray Eagle and Universal Ground Control Stations (UGCS).

I. OTHER SYSTEMS DEPENDENT ON: None J. SYSTEM(S) DEPLOYED: The current STARLite radar is being fielded in support of Operation Freedom’s Sentinel and selected training and garrison sites Continental United States (CONUS)/Outside Continental United States (OCONUS). Areas of responsibility include:

(including spares)

K. OTHER FACTORS INFLUENCING SUSTAINMENT REQUIREMENTS: Currently no data rights for the embedded software.

Tactical Signals Intelligence (SIGINT) Payload (TSP) A. NOMENCLATURE AND SYSTEM NAME: AN/DSC-1(v)1

B. MDEP: AMLC

C. NSN:

SYSTEM PROPONENT: TRADOC Capabilities Manager (TCM) Intel Sensors

E. SYSTEM MANAGER: PEO-IEW&S, PM SAI

F. DEPOT MAINTENANCE PPSS LEAD: SEC IEW&S Directorate, Sensors and Mission Equipment Division

G. DESCRIPTION: The Tactical Signals Intelligence (SIGINT) Payload (TSP) is a radio signal detection, identification, and geo-location system designed to fly aboard an MQ-1C “Gray Eagle” Unmanned Aircraft System (UAS). A TSP-configured MQ-1C UAS will provide Joint Direct-Support Aerial IEW&S (JDSAIEW&S) support to the Division and below commander.

TSP’s broad capabilities support the Persistent Area Assessment (PAA), Situational Development (SID) and Mission Over watch (MO) functional areas of the Integrated Sensor Coverage Area (ISCA) construct by providing a dedicated, dynamically responsive asset with the ability to cover the battle space in depth and to penetrate to collect, locate, and otherwise operate against emitters of interest to develop the electronic operational environment.

TSP will conduct SIGINT missions to answer Division and below commanders’ priority intelligence requirements (PIR) and assists in the capability to cross cue other Intelligence and Electronic Warfare (IEW) and non-IEW sensors, such as Electro-Optics and Infra-Red (EO/IR), Moving Target Indicators (MTI), and /or Synthetic Aperture Radar (SAR). TSP targets Radio Frequency (RF) emitters that operate within multiple frequency bands. TSP is a complementary system to the aerial and terrestrial IEW&S layers through interface with DCGS-A, and the Defense Intelligence Information Enterprise (DI2E). It supports Manned / Unmanned (MUM) teaming with ground SIGINT Terminal Guidance (STG) teams. TSP improves situational awareness and shortens the targeting cycle by detecting, identifying and locating emitters associated with High Value Targets (HVT).

Although each TSP payload may operate as an independent entity, a single ground workstation may control up to three payloads simultaneously, acting in concert or independently. Additionally, the TSP system will be adaptable to other manned and unmanned aerial platforms. The Airborne TSP POD is to be installed on the Gray Eagle MQ-1C UAS wing and will be remotely tasked and controlled from the Ground Workstation.

The TSP has both software and hardware configuration items (CIs). The TSP software is comprised of four CSCIs:

The TSP hardware consists of an airborne module, the pod – carried aboard the MQ-1C, a Maintenance Laptop computer, and a Ground Workstation (GWS). Eventually, the pod will relay its data to a Distributed Common Ground System – Army (DCGS-A) in lieu of the GWS, while serving as a surrogate until the DCGS-A is ready for use.

H. SYSTEM INTEROPERATES WITH: DCGS-A, NSANET, MQ-1C UAS

Interfaces from TSP to the host platform are minimal, consisting only of power, network communication to a Tactical Common Data Link (TCDL) terminal, and RF connections to antennas hard mounted on the platform. The TSP software contains interfaces between 4 CSCIs.

The TSP hardware is composed of several modules with RF, power, and data links connecting them together. The Ground Workstation (GWS) interfaces to a TCDL on one side to receive data from the airborne portion of TSP. This interface is through an encrypted data. Software will be uploaded to the TSP pod and data will be received through the same link encrypted.

The GWS will also interface to a USG SCI network to share intelligence data collected by the TSP.

SIPRNET, PRC 117, ARC-231, Blue Force Tracker, DEDICATED LAND LINE, SECURE FAX, NON-ARMY IEW ABN SENSORS, CGS, TENCAP, ONE ROOF, ROVER 5/6, SATCOM, ENT, VORTEX I. OTHER SYSTEMS DEPENDENT ON: DCGS-A, and national intelligence assets (details classified).

J. SYSTEM(S) DEPLOYED: INSCOM 116th Military Intelligence Brigade and 224th MI Battalion (Bn).

K. OTHER FACTORS INFLUENCING SUSTAINMENT REQUIREMENTS: The TSP sensors operate on NSA net. The TSP is controlled from the ground and leverage Guardrail Infrastructure components and a common COMINT ground software baseline. The costs for TSP specific ground requirements and identified under TSP.

AIRBORNE RECONNAISSANCE LOW-ENHANCED (ARL-E)

NOMENCLATURE AND SYSTEM NAME: AN/ASQ-223A AIRBORNE RECONNAISSANCE LOW-ENHANCED (ARL-E)

B. MDEP: AMLC

C. NSN: TBD

SYSTEM PROPONENT: INSCOM, TRADOC Capabilities Manager (TCM) Intel Sensors, Ft Huachuca AZ E. SYSTEM MANAGER: PM Sensors Aerial Intelligence (SAI) F. DEPOT MAINTENANCE PPSS LEAD: SEC Intelligence, Electronic Warfare & Sensors (IEW&S) Directorate, Aerial & Terrestrial Sensors / Sensors and Mission Equipment Division

G. DESCRIPTION:

The Airborne Reconnaissance Low - Enhanced (ARL-E) systems are manned Army Airborne Intelligence, Surveillance and Reconnaissance (ISR) systems designed to fill critical operational gaps identified in the Joint Direct Support Airborne ISR (JDSAISR) Initial Capabilities Document (ICD), the Counter-Concealment Sensing (C-CS) ICD, and the Training and Doctrine Command (TRADOC) - led Aerial Reconnaissance and Surveillance (R&S) assessment. Headquarters Department of the Army (HQDA) G-3/5/7 issued an ARL Validation and Direction memorandum, dated 25 April 2011, which revalidated the requirement for ARL, and base lined the current capabilities.

The ARL-E system utilizes the DHC-8-300 series aircraft. The ARL-E system will include; dual high-definition Electro-Optical/Infrared (EO/IR) FMV sensors, Synthetic Aperture Radar/Ground Moving Target Indicator (SAR/GMTI) radar, and a communications intelligence (COMINT) sensor with Big Iron capability. ARL-E uses Beyond Line-of-Sight wideband satellite communications and the Common Data Link (CDL) Line of Sight for wide-band dissemination of sensor data to Distributed Common Ground System-Army (DCGS-A) elements.

ARL-E will be assigned to Aerial Exploitation Battalions (AEB) within the Intelligence and Security Command (INSCOM), who will provide command and control, mission planning, sustainment support, and tailor ARL-E deployment packages in support of worldwide missions in accordance with standard Joint and Army tasking processes. ARL-E is able to support the collection requirement of Brigade Combat Teams and higher echelons across the full Range of Military Operations (ROMO) including coalition support.

H. SYSTEM INTEROPERATES WITH: Distributed Common Ground System-Army (DCGS-A), NSANET, JWICS, SIPRNET, ONE ROOF, Operational-Intelligence Ground System (OGS).

I. OTHER SYSTEMS DEPENDENT ON: DCGS-A, and national intelligence assets (details classified).

J. SYSTEM(S) DEPLOYED: Proposed to be deployed to INSCOM AEBs 116th MI Bn, 224th MI Bn, and 3rd MI Bn

K. OTHER FACTORS INFLUENCING SUSTAINMENT REQUIREMENTS:

ARL-E will leverage Guardrail, Enhanced Medium Altitude Reconnaissance and Surveillance System (EMARSS), and DCGS-A software and leverage DCGS-A enterprise license agreements. SEC will be working with PM SAI and PM DCGS-A to maintain common software baselines where possible.

image1.wmf