EWIRDRAFTPWSW911W518R0003.pdf

Performance Work Statement (PWS) for

Electronic Warfare Integrated Reprogramming (EWIR)

Analysis, Production and Process Support

30 January 2018

1. SCOPE

This Performance Work Statement (PWS) describes a wholly self-contained, end-to-end, Electronic Warfare

Integrated Reprogramming (EWIR) Intelligence Mission Data (IMD) production process. Under this contract, Contractor personnel shall provide expertise, analysis, production, research, development, and process support to the

Technical Electronic Intelligence (TechELINT)/EWIR Branch (IANG-STS-TE) of the U.S. Army National Ground

Intelligence Center (NGIC) in every aspect of EWIR IMD and EWIR Database (EWIRDB) production. The

Contractor shall perform specific tasks in the areas of information gathering, data reduction, signals analysis, engineering assessment, product preparation and production process enhancement that shall support NGIC's efforts to accomplish nationally mandated EWIR production and enable NGIC's TechELINT Branch to realize significant improvements in production quantity, quality and efficiency.

2. BACKGROUND

The EWIRDB is the primary Department of Defense (DoD) approved source for technical parametric and performance data on non-communications electronic emitters and associated weapon systems, and the only DoD-validated source of emitter intelligence. The combined EWIRDB merges the all-source radar engineering assessments produced by NGIC and the other Service Intelligence Centers (SICs) with the observed radar signal data housed in National Security Agency's (NSA) Combined Emitter Database (CED) and in the Observed ELINT

Engineering Model (OEEM). CED and OEEM comprise the parametric descriptions of associated emitter signals that are derived from observed TechELINT data by NGIC and other signals intelligence (SIGINT) producer agencies.

NGIC is generally tasked for EWIR production by the Department of Defense Intelligence Analysis Program

(DIAP) for ground-based and heliborne emitters. NGIC is responsible for DIAP production on all foreign air defense artillery (ADA) radars, air defense target acquisition radars, ground surveillance radars, artillery-locating radars, artillery-associated meteorological radars and radiosondes, radiofrequency (RF) fuzed artillery munitions, jammers and electronic attack (EA) systems, heliborne avionics, and similar battlefield sensors and systems. In addition, NGIC is annually tasked for the production of specific emitter models by the Defense Intelligence Agency (DIA) on behalf of the Joint Chiefs of Staff and the EWIRDB user community through formal Community On-Line

Intelligence System for End Users and Managers (COLISEUM) production requirements. NGIC is operationally tasked by Joint Chiefs of Staff instruction to provide threat analyses and EWIR model updates in support of electronic warfare (EW) reprogramming operations within each theater command. Within NGIC, the TechELINT

Branch of the Signatures Division is responsible for EWIRDB, OEEM, and CED production under the oversight of

NGIC's EWIR Production Coordinator and Contracting Officer's Representative (COR).

Up until 2010, the EWIRDB user community relied on a text-based file format designed to accommodate EW systems originating in the Cold War era. The flat-file architecture and content limitations of the thirty-year-old

Legacy EWIR and Kilting databases were made obsolete by the complexity of today's modern radars and the demand for interoperability with other on-line intelligence and military databases. In response to Congressionally

Directed Actions (CDA) which mandated modernization of national EW capabilities, two concurrent developments were undertaken: NSA's CED, which has replaced both the Kilting and the ELINT Parameter Limits (EPL) Listing databases, and DIA's Next-Generation EWIR System (formerly called “NGES”), which has replaced the Legacy

EWIRDB. The modernized EWIRDB also contains the OEEM, which will link to CED, but will provide much more robust signal definitions for use by EWIR Community customers. Modernized EWIR and OEEM/CED will significantly enhance our ability to produce more highly detailed technical descriptions of the complex signals and advanced capabilities of current and future generations of sophisticated radar systems and to present that data to a broader and much more demanding community of users.

The modernized EWIRDB represents a paradigm shift in the way radar and signals analysts assemble raw intelligence information and produce highly technical and detailed, system-of-systems descriptions of entire weapon and sensor systems. EWIR and OEEM/CED will become focal points around which analysts are to build and manage a complete understanding of a radar and its signal by linking supporting reference documents, new and archived intelligence, uncorroborated information, photographs, graphics, modeling and simulation (M&S) programs, and finished intelligence products. EWIR will be significantly more challenging for the analyst than the legacy EWIRDB has been, in that the analyst will be required to create and maintain a coherent hardware-and-signal representation of the behavior and capabilities of each threat system. NGIC’s EWIR production methodology has evolved to include these new concepts:

-- The relational nature of the EWIR and OEEM/CED databases places new internal demands upon analyst-entered data in that the hardware components being modeled must logically fit with all other components, and, taking those components collectively, the system representation must be capable of generating all of the threat system's described signal characteristics across all of the system's modes of operation.

-- The Modernized EWIR database places new external demands upon the analyst in that threat system information must directly correlate to the observed signal data in OEEM/CED. Additionally, EWIR information must be congruent with and provide data to other relational databases such as the Modernized Integrated Database (MIDB), the Military Equipment Parametrics and Engineering Database (MEPED), and NGIC's System Parametric

Information Relational Intelligence Tool (SPIRIT) database. This interoperability requires that an on-going comparison of EWIR data with a variety of other data sources be established and maintained.

-- The Modernized EWIRDB requires a much higher-order description of the operating characteristics of a radar system than the Legacy EWIRDB could provide by requiring a definition of the system-level command architecture which directs the operation of the radar and its associated sensors and weapons, as well as descriptions of the parametric characteristics of the radar's mode-to-mode transitions.

-- The Modernized EWIRDB uses a system-of-systems approach to accurately describe the operational characteristics of advanced, integrated weapon systems. Analysts must not only be able to accurately capture the behavioral characteristics of a threat’s radars, optics, and other sensor systems, but also be able to model how each of the sensor and weapon components works together to perform the threat’s intended mission. Whereas a Legacy

EWIRDB analyst might be responsible for describing the behavior and parametrics of a single emitter, a modern

EWIRDB analyst must be able to accurately portray radar systems, electro-optical systems, communication systems, associated gun, missile, and artillery systems, and any and all associated vehicles and support equipment.

Comprehensive EWIR analysis of modern threat systems involves expanding the weapon system representation by requiring detailed characterizations of all associated communications and sensor devices (infrared, television, laser rangefinder, optics, passive sensors, datalinks, etc.), as well as descriptions of all functional interactions among the components comprising the communications, radar and sensor suites associated with that weapons platform.

-- The Modernized EWIRDB features the ability to fully replicate and simulate, in near real time, an emitter’s waveforms, behaviors, and reactivity to external stimulus. This level of functionality is often referred to as “Tier I.”

EWIR analysts must be able to effectively combine intelligence analytic tradecraft, radar engineering, algorithm coding and computer science, and modeling and simulation, in order to provide realistic EWIR-driven “hardware in the loop” capabilities for some of the DoD’s most sophisticated electronic warfare customers.

-- The Modernized EWIRDB features the ability to provide detailed power, pattern, and polarization (P-cubed) representations of complex emitter radiation behavior. This level of fidelity is also included in the so-called “Tier I” level of EWIRDB production. EWIR analysts must be able to provide detailed P-cubed representations and simulations of target emitters in the EWIRDB by fusing a diverse array of intelligence sources and analytic disciplines.

-- The Modernized EWIRDB includes a suite of tools for both users and producers. The proper use of these tools and execution of the production process for Modernized EWIRDB production requires unique and specific training.

NGIC does not possess, nor will be available to provide, EWIRDB producer training to the Contractor. The

Contractor must be able to provide a wholly self-contained production process to include all aspects of research, EWIRDB production, software administration, and quality control.

For the purposes of this contract, the terms “NGES” and “EWIR” or “EWIRDB” will be used interchangeably when referring to Modernized EWIRDB products using the Standard EWIR Reference Format (SERF) and the Knowledge

Prepositioning System (KPS) architecture. The terms “Legacy EWIR” or “Legacy EWIRDB” will be used when referring to EWIRDB products using the Technical ELINT Reference File (TERF) format. The terms "EWIRDB model" and "EWIRDB system object" (ESO) refer to the various data models that comprise the modernized EWIR database. A group of interrelated ESOs and their associated Mountings, Configurations, and Designators Models make up a complete threat system. While NGIC has transitioned to 100% production in the modernized, SERF-format EWIRDB production, there may be a limited number of Legacy TERF-based EWIRDB files that must be produced for the purpose of retiring or superseding a Legacy EWIRDB file with a modernized EWIRDB model. For this reason, the Contractor must retain the necessary tools, expertise, and analytic capability for ad hoc Legacy

EWIR production in limited quantities.

3. PRIMARY TASK: EWIR PRODUCTION

The EWIR production task is comprised of ten subtasks that fall under four production process functional areas: data management, system assessment, signal characterization, and project management. Each work directive will specify the work to be accomplished under one or more of the EWIR production subtasks, but a work directive need not exercise all ten subtasks. For every work directive, there will be an EWIR Tasking List (ETL) which will identify the specific systems to be worked under each subtask for which services are being ordered. Since the ETL will be classified, it will be provided as a separate contract document to the Contractor through secure means.

A. DATA MANAGEMENT

Data management is that functional area which ensures that relevant source information is being incorporated into the EWIR production process. Data management functions include research, collaboration with government analysts, data mining, data screening, intelligence validation, data dissemination, data archiving, data transfer, and classification and marking review. Data management support provided under this contract is described under

Subtask 1 (All-Source Intelligence Research) and Subtask 2 (Data Transfer and Administration) below.

(1) SUBTASK 1: ALL-SOURCE INTELLIGENCE RESEARCH

All-source intelligence describes all classified and open-source information (other than unminimized ELINT data) and the ELINT intercept report records that pertain to NGIC's threat systems and their associated signals, sensors and weapon systems. All-source intelligence provides the source documents that are necessary to perform EWIRDB analysis and that are required as references for each parametric value entered in the EWIRDB. All Source

Intelligence Research may involve formal activities, such as the systematic periodic screening of national databases, as well as informal activities, such as desk side collaboration with government analysts. All Source Intelligence

Research also includes the screening and archiving of customer feedback, such as EWIRDB Problem Reports/Data

Quality Feedback, Threat Change Verification Requests, Requests for Information, and informal feedback, such as telephone conversations and emails.

All-Source Intelligence Research Tasking List

Each work directive ETL shall specifically list the systems for which work under this subtask will be performed. No new systems shall be added to this subtask during the performance period of a work directive except in the case of threat system family-member splits. The Contractor can expect some systems to be listed only under this subtask and nowhere else on a work directive, e.g., to enable the accumulation of source data in advance of an order for a

EWIRDB System Initialization. However, every system tasked anywhere else on a work directive, under any other subtask, will typically be concurrently tasked under this subtask so that other tasks will be supported with a source data acquisition capability.

Keyword List

For each system on the tasking list, the Contractor shall research, develop, and maintain, a list of keywords which are to be used as search terms in locating and identifying sources of information about that system. Since the use of a robust set of keywords when conducting a search ensures that all pertinent information shall be retrieved while acquisition of irrelevant information will be minimized, any analyst or reviewer who discovers a new term which might be useful as a keyword, or who recognizes the need to refine or correct an existing keyword, shall update the keyword list and advise the COR immediately. In addition, the COR may coordinate with the Contractor to add, delete, or correct keywords at any time during the performance period. The Contractor shall maintain an up-to-date keyword listing. The initial Contractor-developed keyword list, and any COR-coordinated updates thereto, constitutes the Government-approved keyword list.

Data-mining

Search engines available for data-mining include applications such as Pathfinder/Trax, Distributed Common Ground

System – Army (DCGS-A), Think, Analyze, Connect (TAC), Record Message Traffic (RMT), Next Generation

Trident (NGT), and Palantir. The Contractor shall create and maintain an individual search engine query record for each system tasked under this task using the most suitable application according to the Contractor’s expert evaluation. The Contractor’s data-mining process shall be able to effectively retrieve all relevant messages that are streamed through DIA's message traffic system or that have already been stored in DIA's databases. The Contractor shall be responsible for keeping the relevant query strings updated with the most up to date keywords for that system. As relevant new items of intelligence are discovered, they shall be incorporated into the New Information section of that system's EWIR model and supporting documentation. "New Information" is considered to be that information that was discovered since that system's preceding All Source Review Date (ASRD). Research on a system shall go as far back into the system's history as necessary to fully characterize the system for representation in the EWIRDB. In the event that the data-mining application being used is replaced by another, similar query tool, the contractor shall transfer, create, or maintain query records sufficient to satisfy the requirements of this subtask using the new query tool.

Screening, Validation, and Dissemination

The Contractor shall compare the information in each new document against the data in the EWIRDB and

OEEM/CED models, as appropriate, of the system to which the document refers. If the document appears to contain potentially new or possibly conflicting information, the Contractor shall validate the document by ensuring that the document bears the correct classification and downgrading markings, that there are no missing sections or pages, and that relevant enclosures or attachments are present or have been requested. If the document is in hardcopy format, the Contractor shall attempt to acquire a digital softcopy through Intelink retrieval or from the originator; if the document is not readily available in softcopy format, the Contractor shall scan and save the document using the appropriate file format. If the document or information is classified at a higher level than can be used in EWIRDB products, the Contractor shall take the appropriate steps to have the document or portions thereof downgraded by the originating agency. The Contractor shall then incorporate the new information into the "New Information" section of that system's EWIR model and supporting documentation, and add the document to that system's reference file folder. The Contractor shall also compare the document against the system's keyword list and update the system's keyword list accordingly.

Archiving

The Contractor shall create and maintain an individual query tool record for each tasked system as a repository of validated source documents about that system so that the archived knowledge about that system is readily available to the EWIR and government analysts. Whenever a correction or cancellation notification is received, the Contractor shall locate the affected document in the system's supporting documentation and effect the indicated changes.

The Contractor shall also archive any other source materials gathered in support of the performance of any task or subtask in this contract that pertains to a system, including hardcopy documents scanned into PDF files and materials obtained from searches conducted on Intelink or the internet.

A significant amount of additional information about the system or its source documents are generated through e-mail, discussion papers, spreadsheets, and the like. When such material is provided, the Contractor shall ensure that those materials are properly archived in the system's reference folder and Analyst’s Log (see section 4).

Performance Considerations

-- Workload: Query models for tasked systems shall continuously deliver any new records from message traffic and other data sources into the appropriate repository. Historical workload from this program indicates that a total of

10,000 to 20,000 messages per year must be processed and evaluated for NGIC’s total EWIR production portfolio of approximately 200 systems.

-- Timeliness: New information queries shall be screened regularly by the Contractor for new messages so that new information can be validated and disseminated to the Contractor's responsible analysts. The Contractor shall screen, and, where warranted, validate, disseminate and archive, any message received for any system tasked under this subtask within a maximum of five (5) business days.

-- Contingencies: Family-member splits, consolidation of system and/or signal files, changes in system designators or signal notations have profound impacts on the execution of this subtask. Family-member splits shall often require the creation of new keyword lists, search query records, and EWIR supporting documentation for the new variants, and the modification of the keyword lists, search query records, and EWIR supporting documentation associated with the original threat systems. Emitter mergers and designator changes shall also require modifications of keyword lists, search query records, and EWIR supporting documentation. However, because the response to each of these circumstances shall be highly dependent on the emitter involved, the Contractor will provide recommendations to the COR on the actions that need to be taken by the screening analyst for each event in order to meet the search query record requirements. The Contractor shall complete all actions as required within five (5) business days.

Work Directive Item Deliverables for Subtask 1

Keyword List Create/modify as necessary during the performance period

Search Engine Query Record Create/modify as necessary during the performance period

Message Traffic Application Create/modify as necessary during the performance period

EWIRDB Analyst’s Log Create/modify as necessary during the performance

Bookmarked References Create/modify as necessary during the performance

CED Summary File Create/maintain whenever a CED record exists

(2) SUBTASK 2: DATA TRANSFER AND ADMINISTRATION

The Contractor is responsible for ensuring that all data transfer activities between the Government and the

Contractor's facility are conducted in accordance with national and local security and information assurance regulations. The Government intends to sponsor the Contractor to obtain SIPRNET network capability over which a majority of this activity shall take place; however, a great deal of administrative effort is also required to transfer data between the Government’s on-site Joint Worldwide Intelligence Communications System (JWICS) network and Secret internet Protocol Router Network SIPRNet network, and to package any hardcopy or media for transportation between the Government's and the Contractor's locations.

Data Packages

The Contractor is responsible for preparing data packages which shall be used in accomplishing EWIRDB updates under subtasks on each work directive. The data package shall include all data necessary to update or initialize the

EWIRDB System in accordance with the work directive. The data package must also include digital copies of all relevant hardcopy source materials contained in the NGIC historical system and signal folders for that system. The

Contractor shall ensure that the source documents in the data package have been archived in the system's search engine query record.

Data Manager

The Contractor shall identify a Data Manager who shall oversee all data-handling and data-transfer services provided by the Contractor. The Data Manager shall ensure that deliverables, reference documents and administrative communications bear correct classification markings and that data packaging and transfers are handled in accordance with national and local security and information assurance regulations. The Data Manager shall create and maintain a Classified Data Transfer Log that shall record all data transfer actions between the

Government and the Contractor throughout the duration of the contract period of performance. The Data Manager is also responsible for the archiving, organization, administration, and eventual destruction of all contract-related classified material. The Data Manager will serve as an authorized and accredited Data Transfer Agent, and is responsible for obtaining and maintaining currency requirements for that role.

Data Transfer and Administration Tasking List

Each work directive ETL shall specifically list the systems for which work under this subtask shall be performed.

Data Transfer and Administration Performance Considerations

This subtask shall be performed continuously throughout the duration of the performance period of the associated work directive.

Work Directive Item Deliverables Package for Subtask 2

Classified Data Transfer Log Create/maintain during the performance period

B. SYSTEM ASSESSMENT

System assessment is the creation of an all-inclusive, technical description of a threat system that details, for weapon system engineers, modeling experts, operational planners and tactical users, that system's hardware design, signal characteristics, function, operating behavior, performance metrics, potential capabilities, deployment platforms, manufacture, proliferation, and associated radars, sensors, communications and weapon systems. System assessments are created by supplementing incomplete intelligence and open-source information with expert engineering estimates and are maintained in the validated and authoritative EWIRDB database. This section describes the four types of EWIR efforts (Subtask 3 through Subtask 6) which shall be tasked for support under this contract.

Under NGIC's EWIR production scheme, tasked systems shall undergo Initialization (Subtask 3) or Comprehensive

Update (Subtask 4) as deemed appropriate by the COR. Once the EWIRDB model has successfully undergone an

Initialization or Comprehensive Update, it shall be considered "baselined" and its currency shall be maintained through a continuous review and updating process (Subtask 5).

(1) SUBTASK 3: EWIRDB SYSTEM INITIALIZATION

For each work directive item under this subtask, the Contractor shall be required to create a new set of EWIRDB models for a specific threat system.

EWIRDB System Initialization Tasking List

Each work directive ETL shall specify, as individual work directive items, those systems for which work under this subtask is to be performed. Each work directive item shall state whether TERF production is required and shall specify which ESOs are to be produced. The EWIRDB System Initialization Tasking List can also identify additional systems as optional or contingency tasks, which may be added or substituted for another system of equal complexity already on the list (with COR coordination) at any time during the work directive performance period.

Each system tasked for EWIRDB System Initialization will typically appear as a work directive item under Subtask

1 (All-Source Intelligence Research) and under Subtask 5 (Continuous Lifecycle EWIRDB System Production).

EWIRDB System Initialization Specifications

For each work directive item, the Contractor shall assemble, review, and analyze available all-source intelligence material to ensure that as many attributes, characteristics, and operational modes as possible can be identified for that EWIRDB model. The Contractor shall prepare data packages, which shall include the retrieval of new information and the digitization of applicable hardcopy references and source materials available in NGIC historical system and signal folders, for delivery to the Contractor's responsible systems analyst. From this analysis, the analyst shall create new EWIRDB models, to include specified ESOs and appropriate Transition Logic Maps

(TLM), a new Legacy EWIRDB file, or both, according to the production requirements specified in the EWIRDB

System Initialization Tasking List for that work directive item. Special emphasis shall be given to ensuring that

EWIRDB radar models are able to dynamically simulate and incorporate external stimulus via the appropriate operands and external data and configuration inputs. The model must also contain detailed power, pattern, and polarization models for all relevant assessed modes. The analyst shall also compare the EWIRDB/NGES file against the system's keyword list and nominate any new keywords or corrections to existing keywords for incorporation into the system's keyword list. The analyst will incorporate any necessary changes based on user data quality feedback.

Once all deliverables for a work directive item have successfully passed the Contractor's Quality Control (QC) process and have been found to be fully acceptable to the Government, the Contractor shall be directed to commence

Continuous Lifecycle EWIRDB System Production (Subtask 5) for that system as specified in the EWIRDB System

Initialization Tasking List production requirements for that work directive item.

Performance Considerations

The preparation of data packages shall be accomplished on-site at NGIC; all other functions comprising this subtask must be performed at the Contractor's secure facility until such time that NGIC is able to host a fully functioning

EWIRDB production enterprise.

-- Workload: Based on historical workload data, as many as thirty (30) threat systems, each comprising up to 20 individual EWIRDB models, may be tasked under this subtask per year.

-- Contingencies: Occasionally, the Contractor analyst will discover during analysis that the system specified by the work directive item is actually identical to, or a closely related variant of, another system for which EWIRDB models have already been published. In such circumstances, the Contractor shall request that the COR coordinate with the Contracting Officer regarding instructions on how further production, if any, shall proceed for that work directive item.

Work Directive Item Deliverables Package for Subtask 3

Keyword List Create/update as necessary

EWIRDB Analyst’s Log Create/update as necessary

Bookmarked References Create/modify as required during the performance period

EWIRDB Model(s) (SERF Format) As specified by work directive

Legacy EWIRDB File(s) (TERF Format) As specified by work directive

(2) SUBTASK 4: COMPREHENSIVE EWIRDB SYSTEM UPDATE

For each work directive item under this subtask, the Contractor shall be required to conduct a comprehensive review and update of existing EWIRDB models for a specific threat system. The objective of a comprehensive review is to produce a high-quality, fully detailed set of EWIRDB models that can be indefinitely maintained in an up-to-date condition through Continuous Lifecycle EWIRDB production (Subtask 5).

Comprehensive EWIRDB System Update Tasking List

Each work directive ETL shall specify those systems for which work under this subtask is to be performed. Each work directive item shall state whether TERF production is required and shall specify which ESOs are to be produced. The Comprehensive EWIRDB System Tasking List can also identify additional systems as optional or contingency work directive items, which may be added or substituted for another system of equal complexity already on the list (with COR coordination) at any time during the work directive performance period. Each system tasked for Comprehensive EWIRDB System Update will typically appear as a work directive item under Subtask 1

(All-Source Intelligence Research) and Subtask 5 (Continuous Lifecycle EWIRDB System Production).

Comprehensive Review Specifications

For each work directive item, the Contractor shall assemble, review, and analyze available all-source intelligence material to ensure that as many attributes, characteristics, and operational modes as possible can be identified for each EWIRDB model. Special emphasis shall be given to ensuring that EWIRDB radar models are able to dynamically simulate and incorporate external stimulus via the appropriate operands and external data and configuration inputs. The model must also contain detailed power, pattern, and polarization models for all relevant assessed modes. The Contractor shall prepare data packages, which shall include the retrieval of new information and the digitization of suitable hardcopy references and source materials for delivery to the responsible systems analyst.

The Contractor’s responsible systems analyst shall evaluate available source material to ensure that existing and new attributes, characteristics, and operational modes have been assessed with the highest-confidence, least-restrictive data possible. The analyst shall review all existing attribute lines to check the validity of the entered data, the confidence level, classification and releasability, and the cited references and comments. When verified data is available, the analyst shall replace estimated values with data reported by source documents. The responsible systems analyst shall add new data or assessments based on new information gathered during research, review

ESOs, verify that all operating modes and TLMs are accurately represented, and conduct a comparative

EWIRDB/OEEM/CED review. The analyst shall also compare the EWIRDB models against the keyword list and nominate any new keywords or corrections to existing keywords for incorporation into the keyword list. All substantive changes made to the EWIRDB system shall be recorded in the EWIRDB Analyst's Log (see section 4), and all classified versions of the EWIRDB model(s) shall be updated as necessary at the same time. The analyst will incorporate any necessary changes based on user data quality feedback.

A comprehensive review exceeds the EWIRDB community's requirements for the all-source review of an EWIRDB model. The Contractor’s systems analyst shall change the EWIRDB model’s ASRD to the intelligence cutoff date of the entire body of information considered during the comprehensive review.

Once all deliverables for a work directive item have successfully passed the Contractor's QC process and have been found to be fully acceptable to the Government, the Contractor shall continue production for that system under

Subtask 5 (Continuous Lifecycle EWIRDB System Production) if tasked to do so in the ETL.

Performance Considerations

The preparation of data packages shall be accomplished on-site at NGIC; all other functions comprising this subtask must be performed at the Contractor's secure facility until such time that NGIC is able to host a fully functioning

EWIRDB production enterprise.

-- Workload: Based on historical workload data, as many as thirty (30) threat systems, each comprising up to 20 individual EWIRDB models, may be tasked under this subtask per year.

-- Contingencies: Any family-member split, consolidation of system models, or change in signal notation can profoundly impact how work on a system tasked under this subtask shall be accomplished. If work has already begun on a comprehensive review of an EWIRDB system file when such an event occurs, the Contractor shall request that the COR coordinate with the Contracting Officer regarding instructions on how further production, if any, shall proceed for that work directive item.

Work Directive Item Deliverables Package for Subtask 4

Keyword List Update as necessary

EWIRDB Analyst’s Log Update as necessary

Bookmarked References Create/modify as required during the performance period

(3) SUBTASK 5: CONTINUOUS LIFECYCLE EWIRDB SYSTEM PRODUCTION

For each work directive item under this subtask, the Contractor will be required to continuously review new information gathered for a system, and, whenever warranted, produce incremental updates of existing EWIRDB models and/or Legacy EWIRDB files.

Continuous Lifecycle EWIRDB System Production Tasking List

Each work directive ETL shall specify those systems for which work under this subtask is to be performed. Each system tasked for Continuous Lifecycle Production will typically appear as a work directive item under Subtask 1

(All-Source Intelligence Research) and Subtask 5 (Continuous Lifecycle EWIRDB System Production)).

Continuous Lifecycle EWIRDB System Production Specifications

For each work directive item, the Contractor shall review, on an on-going basis, all new source data that pertains to a particular threat system. If new research reveals information that should be added to, or be used to modify, the threat system description, the Contractor shall incorporate that new data by performing incremental updates of the threat system's EWIRDB models [and concurrent updates of Legacy EWIRDB files, if tasked]. During the incremental update, the responsible systems analyst shall effect the necessary, data-driven changes, and then review any other attributes or comments which are related to those that had been added or revised, to ensure that the consequences of the new data have been fully represented in the revised EWIRDB models. The analyst shall record all changes made in the EWIRDB models, and revise any other deliverables as necessary. The analyst shall compare the changes made in EWIR products against the system's CED/OEEM files, and record all discrepancies in the EWIRDB and

EWIRDB Analyst's Log. The Contractor's QC process shall review the changes made by the analyst and ensure that all related ESOs, TLMs and attributes affected by the new data were also updated.

Since all new information obtained for a threat system is being evaluated upon receipt, every incremental update accomplished for that threat system under NGIC's Continuous Lifecycle EWIRDB System Production regimen constitutes a comprehensive, all-source review. Therefore, the responsible systems analyst shall change the ASRD for the system's EWIRDB or Legacy EWIRDB files to the publication date of the most recently published source document used in the incremental update. If no new information has been received which has prompted an EWIR product update for a full calendar year from the last ASRD, then the primary analyst shall record a statement to that effect in the relevant EWIRDB models, update the ASRD, and submit the work directive item package for acceptance as an annual review.

Performance Considerations

This subtask shall be performed continuously throughout the duration of the performance period of the associated work directive. This subtask shall be accomplished either on-site at NGIC or at the Contractor's secure facility.

-- Workload: Since NGIC will use this subtask to maintain the threat system descriptions of each initialized or comprehensively reviewed EWIRDB model in an up-to-date condition, the number of systems tasked for continuous concurrent production will steadily increase as work directive items are successfully completed under Subtask 3 and

Subtask 4. Based on historical workload data, as many as two hundred (200) threat systems, each comprising up to

20 individual EWIRDB models, may be tasked under this subtask per year.

Continuous EWIR production has been designed to accommodate relatively-limited, incremental updates to established system files. Occasionally, new source information will be received that will necessitate an extensive revision of a system's EWIRDB models. The Contractor may choose to finish any or all such exceptional updates under this continuous production subtask; however, in the event that new source data will require an excessive effort to complete, the Contractor may elect to ask the COR to coordinate with the Contracting Officer regarding re-tasking the update for that work directive item as a Comprehensive EWIRDB System Update.

-- Contingencies: Any family-member split, consolidation of EWIRDB models, or change in signal notation which involves a system tasked under this subtask may require the COR to coordinate the re-tasking of that system, and the

COR will coordinate instructions on how further production, if any, shall proceed for that work directive item. Any new data which prompts an extensive revision of the EWIRDB or Legacy EWIRDB files may be identified by the

Contractor as an exceptional update which may be re-tasked, through coordination with the COR, as a comprehensive update under Subtask 4.

Work Directive Item Deliverables Package for Subtask 5

Keyword List Update as necessary

EWIRDB Analyst’s Log Update as necessary

Bookmarked References Create/modify as required during the performance period

(4) SUBTASK 6: RESEARCH, DEVELOPMENT, TESTING AND EVALUATION (RDT&E) FOR

ACQUISITION PROGRAMS

For each work directive item under this subtask, the Contractor shall be required to conduct RDT&E of scientific and software principles and solutions to solve emerging requirements of defense acquisition programs.

Acquisition programs increasingly feature advanced EW capabilities which levy new EWIR requirements on the

Government. The next generation of weapon systems require vastly increased quality, quantity, and fidelity of intelligence mission data in order to meet their advanced electronic warfare requirements. These requirements often tax the limits of what is possible in the EWIRDB.

The Contractor shall be responsible for monitoring the evolving requirements of particular acquisition programs as assigned during the routine execution of Subtask 1 (All Source Intelligence Research). The COR, the Contractor, and the Acquisition, Intelligence, and Requirements (AIR) communities will work closely together to develop solutions to any unique program requirements.

Research, Development, Testing, and Evaluation (RDT&E) for Acquisition Programs Specifications

Under this task, the Contractor will work closely with the individual program offices to conduct RDT&E in order to research ways to make the current EWIR toolset produce the “colorized” intelligence mission data needed by individual weapon systems and to meet unique acquisition program EWIR requirements. The Contractor shall conduct RDT&E to develop new algorithms, collection methodologies, software solutions, etc. of EWIRDB models and associated toolsets independent of the framework outlined in Subtasks 3, 4, and 5. The result of Subtask 6 efforts may result in anything from a report to an EWIRDB model.

Performance Considerations

This subtask shall be performed as necessary throughout the duration of the performance period of the associated work directive. This subtask can be accomplished on-site at NGIC or at the Contractor's secure facility.

-- Workload: RDT&E for this Subtask could take many hundreds of hours. The Government anticipates no more than ten events during a 12-month period.

Work Directive Item Deliverables Package for Subtask 6

Contractor's research, testing, and/or evaluation report Create as required during the performance period

EWIRDB model and associated toolsets Create as required during the performance period

C. SIGNAL CHARACTERIZATION

Signal characterization is the extraction of parametric data from the measurement of the observed characteristics of a system's radiated signals. Parametric signal data can be used to uniquely identify a system and can be interpreted by signals analysts to reveal that system's function, operating modes, system hardware design, performance capabilities, and interaction with other radars, sensors and weapon systems. TechELINT analysis is conducted on collected pulse-level and signal-level datasets, and on the intercept records reported by ELINT collectors, to derive the signal characteristics of a system. Both processed and unminimized TechELINT data is analyzed using the appropriate

SIGINT community tools. This section describes the three types of signal characterization efforts: Subtask 7

(Parametric Review), Subtask 8 (Directed Signals Analysis), and Subtask 9 (ELINT Database Maintenance) that shall be tasked to provide TechELINT analysis support to EWIR production under this contract. The two production objectives for signal characterization are: (1) to exploit ELINT data in direct support of EWIR production and publish analytical findings in serialized, SIGINT reports which can be used as references in EWIR products; and, (2) to produce OEEM and CED signal definitions which correlate to, and corroborate, systems assessments so that a single, integrated, and coherent system description is presented to EWIR customers.

In order to promote an effective fusion of systems and signals data, this contract requires the responsible EWIRDB analyst to carry out the Contractor's QC procedures for each signal characterization deliverable that has been produced for that system. This systems-analyst/signals-analyst corroboration shall ensure that TechELINT analytical findings are consistent with, or shall be incorporated into, the existing EWIRDB assessment.

The production standards for signals analysis and reporting are detailed in published security regulations and production guidance for EWIRDB and SIGINT reporting.

(1) SUBTASK 7: PARAMETRIC REVIEW

For each work directive item under this subtask, the Contractor shall be required to conduct a parametric review of

ELINT intercept data in order to produce the appropriate serialized SIGINT reports for a specific system.

Parametric Review Tasking List

Each work directive ETL will specify those emitter signals for which work under this subtask is to be performed.

The ETL can also include additional work directive items as optional or contingency tasks, which may be added or substituted at any time during the work directive performance period. The tasking list will also specify the production requirements which must be completed for each work directive item. Each emitter tasked for parametric review will also typically appear as a work directive item under Subtask 1 (All-Source Intelligence Research).

Parametric Review Specifications

For each work directive item, the signals analyst shall obtain all available serialized SIGINT reports published for that emitter and retrieve all of the emitter's ELINT intercept records from a suitable authoritative source (such as

Wrangler, or equivalent). Then, using the appropriate analysis tools, the signals analyst shall perform signal-level and pulse-level analysis on the intercept records, omitting those records the analyst determines to be invalid. The signals analyst will extract statistical data for as many parameters as possible, giving special emphasis to those which shall complete the Wartime Reserve Modes (WARM) and parametric fields required for EWIR production.

The signals analyst shall draft a serialized SIGINT report as specified for the work directive. The signals analyst shall also create any informal documentation necessary for the timely and accurate updating of EWIRDB products.

During the Contractor's QC review, the systems analyst and the signals analyst shall ensure that the TechELINT findings are representative of the body of reported data and consistent with the established parametric description for that signal; if significant differences exist, the analysts' rationale justifying such changes shall be recorded in the

SIGINT report, in the updated OEEM/CED entries, and in the emitter's associated EWIRDB Analyst's Log as appropriate. If the emitter is also listed as a work directive item under a continuous production subtask (Subtask 5), the systems analyst shall begin an EWIRDB update, based on the agreed upon changes, as soon as the Subtask 7 work directive item package has been accepted by the government. If the subject emitter is concurrently tasked under Subtask 9 (ELINT Database Maintenance), the Contractor's TechELINT analyst can begin execution of

Subtask 9 once the serialized SIGINT report has been accepted by the government.

Performance Considerations

-- Workload: Based on historical workload data, NGIC might order as few as three (3) to as many as thirty (30) parametric reviews per year.

-- Contingencies: Any family-member split, consolidation of emitter files, or change in signal notation which involves an emitter tasked under this subtask will usually require the COR to coordinate re-tasking that emitter. If work has already begun on a parametric review when such an event occurs, the COR will coordinate with the contracting officer on providing instructions on how production shall proceed for that work directive item.

Work Directive Item Deliverables Package for Subtask 7

EWIRDB Analyst’s Log Update as necessary

Draft Serialized SIGINT Report Create/update as required during the performance

(2) SUBTASK 8: DIRECTED SIGNAL ANALYSIS

For each work directive item under this subtask, the Contractor shall be required to conduct a comprehensive, in-depth analysis of ELINT intercept and pulse-level data in order to produce a complete characterization of the parametric and modal behaviors of a tasked emitter.

The complex nature of the EWIRDB Radar Models necessitates a thorough understanding of the operation, modes, and transitions of threat emitters. Subtask 8 is intended to promote in-depth research and analysis of specific behaviors and intelligence gaps necessary to fully characterize the operation of threat systems.

Directed Signal Analysis Tasking List

Each work directive ETL will specify those systems for which work under this subtask is to be performed. The

Directed Signal Analysis Tasking List can also include additional work directive items as optional or contingency tasks, which may be added or substituted at any time during the work directive performance period. The tasking list will also specify the production requirements which must be completed for each work directive item. Each system tasked for Directed Signal Analysis will also typically appear as a work directive item under Subtask 1 (All-Source

Intelligence Research).

Directed Signal Analysis Specifications

Directed signal analysis will be ordered primarily to satisfy EWIRDB-specific intelligence through exploitation of

TechELINT data. Each work directive item under this subtask will specify the intelligence objectives to be achieved through analysis and will specify the production requirements the signals analyst must satisfy in order to complete the task. Directed signal analysis tasks will generally address more complicated analytical problems whose resolution might require persistent, long-term efforts. The signals analyst might be tasked to characterize a sophisticated operating mode or a complex scan, for example, or to refine the parametric descriptions of two or more emitters whose identifying signal characteristics are mutually ambiguous.

Most ELINT analytical tasks will require the signals analyst to extract the necessary data from digitized samples of intercepted signals collected in pulse-level datasets by making parametric measurements using the appropriate

ELINT community software. Once the specified intelligence objectives have been achieved, the signals analyst shall report all findings as specified in the ETL. Specifications for the work directive item could include a research paper, whitepaper, or other informal report, or a draft serialized SIGINT report, as specified for the work directive item.

During the Contractor's QC review, the system analyst and the signals analyst shall ensure that the TechELINT findings are representative of the body of reported data and consistent with the established parametric description for that signal; if significant differences exist, the analysts' rationale…