EWIR PWS Draft.pdf

UNCLASSIFIED

Performance Work Statement (PWS) for the

Electronic Warfare Integrated Reprogramming (EWIR) Analysis, Production and Process Support

Indefinite Delivery/Indefinite Quantity (IDIQ) Contract

PART 1: GENERAL INFORMATION

1. General. This is a non-personal services indefinite delivery/indefinite quantity (IDIQ) contract to obtain Electronic Warfare Integrated Reprogramming (EWIR) analysis, production, and process support. The U.S. Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the contractor who, in turn is responsible to the government.

1.1. Description of Services/Introduction. The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform EWIR analysis, production, and process support as defined in this Performance Work Statement except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.

1.2. Background.

1.2.1. The EWIR Database (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 repository of all-source emitter intelligence. The combined EWIRDB merges the all-source radar engineering assessments produced by National Ground Intelligence Center (NGIC) and the other Service Intelligence Centers (SICs) with observed emitter signal data housed in the National Security Agency's (NSA) databases. The current NSA database (i.e., the Combined Emitter Database (CED)) is scheduled to be succeeded as part of the TechSIGINT Revitalization (TSR) Program with a new database that will utilize EWIRDB-compatible Emitter Intercept Models (EIMs) and Emitter Engineering Models (EEMs). EIMs and EEMs comprise the parametric descriptions of associated emitter signals that are derived from observed Technical Electronic Intelligence (TechELINT) data by NGIC and other signals intelligence (SIGINT) producer agencies.

1.2.2. NGIC is generally tasked for EWIR production by the 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, radio frequency (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 EWIR models by the Defense Intelligence Agency (DIA) on behalf of the Joint Chiefs of Staff and the EWIRDB user community through the Intelligence Mission Data (IMD) Prioritization and Risk Management Framework (PRMF) process and 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 TechSIGINT Branch of the Signatures Division is responsible for EWIRDB, CED, EIM, and EEM production under the oversight of NGIC's EWIR Team Lead and Contracting Officer's Representative (COR).

1.2.3. The 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. The EWIRDB is the focal point around which analysts 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 analysts are 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 concepts.

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

1.2.3.2. The EWIRDB places external demands upon the analyst in that threat system information shall directly correlate to observed signal data in CED/EIM/EEM. Additionally, EWIRDB information shall be congruent with and provide data to other relational databases such as the Machine-Assisted Analytic Rapid-Repository System (MARS), 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.

1.2.3.3. The EWIRDB necessitates a high-order description of the operating characteristics of a radar system 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.

1.2.3.4. The EWIRDB uses a system-of-systems approach to accurately describe the operational characteristics of advanced, integrated weapon systems. Analysts shall accurately capture the behavioral characteristics of a threat’s radars, optics, and other sensor systems; additionally, the analysts shall model how each of the sensor and weapon components works together to perform the threat’s intended mission.

An EWIRDB analyst shall 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.

1.2.3.5. The 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 referred to as a “Tier I” Product Status. EWIR analysts shall 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.

1.2.3.6. The EWIRDB features the ability to provide detailed power, pattern, and polarization (P-cubed) representations of complex emitter radiation behavior. EWIR analysts shall provide detailed P-cubed representations and simulations of target emitters in the EWIRDB by fusing a diverse array of intelligence sources and analytic disciplines.

1.2.3.7. The EWIRDB includes a suite of tools for both users and producers. The proper use of these tools and execution of the production process for 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 shall provide a wholly self-contained production process to include all aspects of research, EWIRDB production, software administration, data management, and quality control.

1.2.3.8. 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). 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.

1.3. Objectives. The contractor shall perform information gathering, data reduction, signals analysis, engineering assessment, product preparation and production process enhancement in support of NGIC's efforts to accomplish nationally mandated EWIR production while enabling improvements in production quantity, quality and efficiency.

1.4. Scope. This PWS describes a wholly self-contained, end-to-end, EWIR Intelligence Mission Data (IMD) production process. Under this contract, contractor personnel shall provide expertise, analysis, production, research, development, and process support to the TechSIGINT Branch (IANG-STS-TE) of the U.S. Army NGIC in every aspect of EWIR IMD and 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 TechSIGINT Branch to realize significant improvements in production quantity, quality and efficiency.

1.5. Period of Performance. The ordering period of performance shall be 60 months. FAR 52.217-8, Option to Extend Services, also applies. Each task order shall specify the period of performance for the task order.

1.6. General Information.

1.6.1. Quality Control: The contractor shall develop and maintain an effective Quality Control Program (QCP) to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s QCP is the means by which they assure that work complies with the requirement of the contract. The contractor shall deliver a Quality Control Plan (QCP) applicable to all task orders issued on the IDIQ within 30 days after contract award. Changes to the QCP shall be submitted to the Contracting Officer (KO) and COR within 5 working days when changes are made thereafter. After acceptance of the quality control plan the contractor shall receive the KO’s acceptance in writing of any proposed change to its Quality Control (QC) system. If required, individual task order deviations from the IDIQ QCP shall be submitted with the contractor’s task order proposal. If accepted, the applicable deviation(s) shall be reflected in the individual task order PWS.

The contractor shall submit all deliverables in "ready for publication" condition, that is, products which are in the proper format, are correctly linked, and bear the appropriate classification and control markings.

The contractor shall not rely on the government to act as the contractor's final QC appraiser, but shall ensure that interpretive quality control (IQC), technical quality control (TQC) and production quality control (PQC) procedures are integral and effective components of the contractor's own EWIR production process. The contractor's overall QC process shall ensure that all deliverables have been produced in compliance with all EWIR and TechELINT community production requirements and standards. All errors discovered during the contractor's QC process shall be corrected by the contractor before task order item packages are submitted to the COR for approval.

1.6.1.1. Interpretive Quality Control (IQC)

1.6.1.1.1. Prior to its submission for government acceptance, the contractor shall subject each deliverable to an interpretive quality control review which tests the reasonableness of the product taken as a whole.

Unwarranted or illogical claims, whether intentional or inadvertent, made by the systems analyst, can have significant ramifications on the threat evaluation of the radar, especially in regard to weapons system acquisition programs, order-of-battle production, operational SIGINT support, intelligence planning for military operations, and the conduct of electronic warfare operations. Gross misrepresentations of system capabilities in critical products will cause those deliverables to be rejected by the COR.

1.6.1.1.2. An effective IQC process ensures that the system being depicted by the primary analyst in the EWIR model (or by the signals analyst in the CED/EIM/EEM entry or a serialized SIGINT report) realistically portrays the radar and its weapons systems and accurately characterizes its signal. The system's operational capabilities and performance assessments shall be plausible when the radar's vintage, manufacturer, function, employment and proliferation are taken into account. Each capability being attributed to a system shall be recognizable by the IQC analyst as an element of a logically developed model of a radar system that has consistently evolved through reasoned interpretation of credible evidence. The analyst's rationale for significant changes to an existing description or for rejecting community-held views for that system shall be sufficiently documented by the primary analyst to support the contractor's IQC review. The final product shall be a valid, viable and coherent system or signal characterization that has been derived through accepted analytical procedures, that is representative of the body of reported data, and that is consistent with community standards and good engineering principles.

1.6.1.2. Technical Quality Control (TQC)

1.6.1.2.1. The contractor is responsible for implementing technical quality control procedures that can ensure the veracity of the information presented in each product being submitted as a deliverable to the government. TQC procedures shall be effective in detecting mistakes from the two principal causes of analyst-produced errors: reaching erroneous analytical findings, and inaccurately conveying analytical findings into the finished product. When the analyst presupposes exaggerated or underrated capabilities for a system, fails to authenticate information reported in source documents, misunderstands or misinterprets source data, makes calculation errors, or misapplies or incorrectly deviates from standard engineering formulas and estimations, then the assessed design and performance capabilities of that radar are misrepresented and the parametric characteristics by which that radar's signal is identified are distorted. TQC shall also determine whether the model is able to correctly dynamically react to its environment using external stimuli, and execute properly in the necessary suite of EWIRDB and other simulation tools. Gross technical errors discovered in critical products will cause those deliverables to be rejected by the COR.

1.6.1.2.2. Even if the analytical findings accurately define a system and its signal, significant errors can be created when the analyst incorporates that information into the EWIRDB. The parametric sets and sequences which encompass multiple, interdependent parametric fields in describing the operating modes of a system are often inaccurately represented in the EWIRDB. Other data-entry mistakes (e.g., using data with the wrong units of measure, entering a value for the lower limit of a parametric range that is higher than the high limit value, or making typographical mistakes when entering data) are easier to comprehend, but are no less destructive to the veracity of the system description.

1.6.1.2.3. Such data-entry mistakes are damaging enough when taken at face value: if a system uses a transmitter that can produce 1,000 watts of power, entering "1,000" instead of "1.0" for the Transmitter Peak Power field (which requires power to be expressed in kilowatts) profoundly changes that radar's assessed capabilities. However, because so many parametric fields are interrelated, even a simple data-entry error can propagate its detrimental effects throughout an EWIR model. Inattention to the interaction of multiple data fields can also produce inconsistencies in the system description, especially when the analyst fails to update amplifying information in a comment concurrently with the changes being made to the parametric lines to which that comment had referred. As a safeguard, each update shall be compared against the existing EWIRDB, EIM, EEM, and CED entries for that system to ensure that inconsistencies have been eliminated, that analytical continuity has been upheld, and that all intended changes in the system description have been identified and explained.

1.6.1.2.4. The contractor's TQC process can utilize a combination of both manual and computer checking but shall ensure that the system being described is a viable system and that the descriptions of system components and operating modes are accurately represented, fully explained, understandable, coherent, and absent any incongruities. The TQC process shall critically review EWIRDB models and updates and serialized SIGINT reports to ensure that all community and contract technical standards and requirements have been met, and that all required parametric fields have been completed either with data correctly drawn from appropriate source documents or with assessments properly estimated in accordance with community standards and accepted engineering practices. In performing TQC checks for a serialized SIGINT report or EIM/EEM/CED update, the draft report or update shall also be compared with the associated EWIRDB model to ensure that the TechELINT analytical findings are consistent with, or shall be incorporated into, the current EWIRDB assessment. TQC checks shall also be performed concurrently for each Foreign Military Sales (FMS) and alternately classified version of each EWIRDB file produced.

1.6.1.3. Production Quality Control (PQC)

1.6.1.3.1. The contractor is required to submit each task order item as a complete, "ready for publication" package. An effective production quality control process shall ensure that all security and production standards and requirements levied by the community and the contract have been met for each deliverable, that file formats have been checked, that intelligence community tradecraft directives have been complied with, that data files have been properly classified and products correctly marked, that all NGIC issues have been addressed, and that all links and bookmarks refer to the correct document file locations. A task order item cannot be accepted until all deliverables associated with that package have been submitted to the COR.

1.6.2. Quality Assurance. The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan. This plan is primarily focused on what the government shall do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6.3. Recognized Holidays. The contractor is not required to perform services on the following Federal holidays:

New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Juneteenth Christmas Day Independence Day

1.6.4. Hours of Operation. The contractor is responsible for conducting business, between the hours of 9:00 a.m. to 3:00 p.m. Monday thru Friday except Federal holidays or when the government facility is closed due to local or national emergencies, administrative closings, or similar government directed facility closings. For other than firm fixed price contracts, the contractor will not be reimbursed when the government facility is closed for the above reasons. The contractor shall at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the government facility is not closed for the above reasons. When hiring personnel, the contractor shall keep in mind that the stability and continuity of the workforce are essential.

1.6.5. Place of Performance. The work under this contract will be performed on site at NGIC (Charlottesville, VA) and off site at the contractor’s facility (City TBD, VA). In order to facilitate rapid responses to quick-turn customer requirements, as well as to facilitate efficient quality assurance in the EWIR development environment, the contractor’s facility shall be located within a thirty-minute drive of NGIC in Charlottesville, VA.

1.6.6. Type of Contract. Task orders issued against this IDIQ shall be the cost-plus-fixed-fee (CPFF), term form.

1.6.7. Security Requirements. The security requirements are in accordance with the contract DD254, Department of Defense Contract Security Requirement List.

1.6.7.1. Personnel Security.

1.6.7.1.1 All on-site individuals being proposed to work under this contract require TOP SECRET/ Sensitive Compartmented Information (SCI) clearances based on a Single Scope Background Investigation. Contractor personnel performing work under this contract shall have a TOP SECRET/SCI clearance at time of the proposal submission, and shall maintain the level of security required for the life of the contract. In addition, TechELINT analysts being proposed to work under this contract who do not have a valid counter-intelligence polygraph examination on file shall consent to an examination/re-examination in order to gain access to SIGINT data.

1.6.7.1.2 All off-site individuals being proposed to work under this contract require SECRET clearances.

1.6.7.2. Physical Security. The contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.

1.6.7.3. The contractor shall possess and maintain a SECRET level of safeguarding from the Defense Security Service (DSS) for their off-site facility.

1.6.8. Special Qualifications.

1.6.8.1. Training. The contractor is required to ensure that all employees comply with the Mandatory Intelligence Training requirements for contractor personnel in accordance with Army Regulation (AR) 381-10. The contractor shall provide documentation to the COR that training has occurred for each employee. The training is mandatory for all personnel in the Intelligence environment.

16.8.2 Contractor employees shall be fully trained and capable of performing services required on this contract; however, task orders also may provide for government-furnished training to contractor employees in the event the government determines such training is (1) indispensable to adequate contract performance and (2) such training can only be provided by the government.

1.6.8.2.1. Online Training. Mandatory online training includes 1) Anti-Terrorism Force Protection, 2) Combating Trafficking in Person, 3) Information Assurance/DoD Cyber Awareness Challenge Training,

4) Intelligence Oversight Awareness Training, 5) Annual Security Refresher Training, 6) Operation Security (OPSEC) Annual Training, 7) DNI Unauthorized Disclosures of Classified Information Training, and 8) DoD Controlled Unclassified Information (CUI) Awareness Training. Additional training may be mandated by the government as necessary.

1.6.8.2.2. Classroom Training. Mandatory classroom training includes 1) Classification Marking, 2) OPSEC Initial Training, and 3) The Threat Awareness and Reporting Program (TARP). Additional training may be mandated by the government as necessary.

1.6.9. Post Award Conference/Periodic Progress Meetings. The contractor shall attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The KO, COR, and other government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the KO will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be attended at no additional cost to the government.

1.6.10. Contracting Officer Representative (COR). The COR will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration The COR is authorized to perform the following functions: assure that the contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance;

maintain written and oral communications with the contractor concerning technical aspects of the contract; issue written interpretations of technical requirements, including government drawings, designs, specifications; monitor contractor's performance and notifies both the KO and contractor of any deficiencies; review and approve contractor travel requests; coordinate availability of government furnished property, and provide site entry of contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.6.11. Personnel.

1.6.11.1. Key Personnel.

1.6.11.1.1. The following personnel are considered key personnel by the government: Senior Systems Analyst, Senior Signals Analyst, Project Manager, and Data Manager. Key personnel shall be nominated by the contractor and accepted by the government. The contractor shall provide sample resumes for each position upon the commencement of each task order.

1.6.11.1.2. The contractor shall provide a project manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the contractor when the manager is absent shall be designated in writing to the KO. The project manager or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract. The project manager or alternate shall be available between 8:00 a.m. to 4:30 p.m., Monday thru Friday except Federal holidays or when the government facility is closed for administrative reasons.

1.6.11.1.3. The contractor shall inform the KO and COR within 48 hours of realized or pending changes in key personnel. The contractor shall have 15 business days to replace any key personnel vacancies that occur due to attrition or dismissal.

1.6.11.1.4. Qualifications of Key Personnel. See Appendix 01 for mandatory qualifications of key personnel.

1.6.11.2. Qualifications of Non-Key Personnel. See Appendix 01 for the government’s anticipated non-key personnel labor categories. Cited education and experience qualifications are suggested but not mandatory. All labor categories shall be submitted for review and approval by the government. Additional labor categories beyond those identified in Appendix 01 maybe submitted for approval by the government and subsequent inclusion in a revised appendix.

1.6.12. Identification of Contractor Employees. All contract personnel attending meetings, answering government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are government officials. They shall also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed. Contractor personnel performing work at NGIC will be required to obtain and wear badges in the performance of this service.

1.6.13. Contractor Travel. The contractor may be required to travel in the Continental United States (CONUS) and within the NCR during the performance of this contract to attend meetings, conferences, forums, and working groups. All travel requires government approval/authorization and notification to the COR. Authorized travel expenses will be reimbursed in accordance with FAR 31.205-46 and the limitation of funds specified in each task order. The contractor will be authorized to share transportation in government owned or operated vehicles (e.g., MIL-AIR) as deemed appropriate by the KO or COR.

1.6.14. Other Direct Costs (ODCs). The contractor is required to obtain, maintain, and administer the required software, hardware, licenses, training, credentials, and accreditation necessary to implement a fully self-contained EWIRDB production enterprise. All ODCs require government approval/authorization and notification to the COR.

PART 2: DEFINITIONS & ACRONYMS

2. DEFINITIONS AND ACRONYMS:

2.1. Definitions.

2.1.1. CONTRACTOR. A supplier or vendor having a contract to provide specific supplies or service to the government. The term used in this contract refers to the prime.

2.1.2. CONTRACTING OFFICER. A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.1.3. CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the KO to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.4. DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.5. DELIVERABLE. Anything that can be physically delivered but may include non-physical things such as meeting minutes.

2.1.6. KEY PERSONNEL. Contractor personnel who are considered essential to the successful performance of the work hereunder and are identified in the PWS as key personnel.

2.1.7. PHYSICAL SECURITY. Actions that prevent the loss or damage of government property.

2.1.8. QUALITY ASSURANCE (QA). The government procedures to verify that services being performed by the contractor are performed according to acceptable standards.

2.1.9. QUALITY ASSURANCE Surveillance Plan (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.10. QUALITY CONTROL. All necessary measures taken by the contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.11. SUBCONTRACTOR. One that enters into a contract with a prime contractor. The government does not have privity of contract with the subcontractor.

2.1.12. WORK DAY. The number of hours per day the contractor provides services in accordance with the contract.

2.1.12. WORK WEEK. Is defined as Monday through Friday, unless specified otherwise.

2.2. Acronyms.

ADA Air Defense Artillery AIR Acquisition, Intelligence, and Requirements AIS Automated Information System APGTE A Practical Guide to EWIRDB API Application Program Interface AR Army Regulation ASA Assigned Signal Analyst ASAP Air & Space Analysis & Planning ASRD All Source Review Date CAPCO Controlled Access Program Coordination Office CATS Consolidated Analysis Tools Station CD Compact Disk CDA Congressionally Directed Actions CED Combined Emitter Database CMR Contractor Manpower Reporting COLISEUM Community On-Line Intelligence System for End Users and Managers CONOP Concept of Operation CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer Representative COTR Contracting Officer's Technical Representative CSSM Central Security Service Classification Manual CUI Controlled Unclassified Information DCGS-A Distributed Common Ground System – Army DD254 Department of Defense Contract Security Requirement List DIA Defense Intelligence Analysis DIAP Defense Intelligence Analysis Program DMAS Data management Access Service DOC Document (Microsoft Word) DoD Department of Defense DSSC Director of Central Intelligence Special Security Center DVD Digital Video EA Electronic Attack ELINT Electronic Intelligence EO Electro-Optic EPL ELINT Parameter Limits ESO EWIRDB system object ESP ELINT Screening Position ETL EWIR Tasking List EWIR Electronic Warfare Integrated Reprogramming EWIRDB Electronic Warfare Integrated Reprogramming Database EW Electronic Warfare FMS Foreign Military Sales FSC Federal Service Code FVEY Five Eyes GALE Generic Area Limitation Environment HTML Hyper-Text Markup Language IANG-STS-TE NGIC TechSIGINT Branch ICD Interface Control Documents

ICD Intelligence Community Directive IM&S Information Management and Storage IMD Intelligence Mission Data IQC Interpretive Quality Control IR Infrared IT Information Technology JADE Joint Analytic Data Editor JTR Joint Travel Regulation JWICS Joint Worldwide Intelligence Communications System KO Contracting Officer KPS Knowledge Prepositioning System M&S Modeling and Simulation MATLAB Matrix Laboratory MEPED Military Equipment Parametrics and Engineering Database MIDB Modernized Integrated Database NAIC National Air Intelligence Center NGES Next-Generation EWIR System NGIC National Ground Intelligence Center NGT Next Generation Trident NISPOM National Industrial Security Program Operating Manual NOFORN Not Releasable to Foreign Nationals NSA National Security Agency ODC Other Direct Costs OEEM Observed Electronic Intelligence (ELINT) Engineering Model OPSEC Operation Security P-cubed Power, Pattern, and Polarization PDF Portable Document Format PPM Production Process Management PQC Production Quality Control PRS Performance Requirements Summary PWS Performance Work Statement QA Quality Assurance QAP Quality Assurance Program QASP Quality Assurance Surveillance Plan QC Quality Control QCP Quality Control Plan QCP Quality Control Program RDT&E Research, Development, Testing, and Evaluation RF Radio Frequency RMT Record Message Traffic SAVANT Synchronized and scalable Audio Video content Across NeTworks SCI Sensitive Compartmented Information SERF Standard EWIR Reference Format SIC Service Intelligence Center SIGINT Signals Intelligence SIPRNET Secure Internet Protocol Router Network SPIRIT System Parametric Information Relational Intelligence Tool SQL Structured Query Language TAC Think, Analyze, Connect

TARP Threat Awareness and Reporting Program TechELINT Technical Electronic Intelligence TERF Technical ELINT Reference File TLM Transition Logic Map TQC Technical Quality Control UIC Unit Identification Code USSID United States Signals Intelligence Directive WARM Wartime Reserve Modes XML Extensible Markup Language XSL eXtensible Stylesheet Language

PART 3: GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3. GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1. Services. NGIC will seek to sponsor Secure Internet Protocol Router Network (SIPRNET) connectivity to the contractor's facility. If the installation is approved, NGIC will pay the initial connection fees and annual usage fees; however, the contractor shall be responsible for providing any necessary computer or networking hardware or software required to establish SIPRNET access within the contractor's facility.

3.2. Facilities. The government will provide a minimum of eight individual work areas, eight computer workstations having Joint Worldwide Intelligence Communications System (JWICS) access, and one scanner-equipped computer workstation with SIPRNET access, and five ELINT analysis workstations for use by on-site contractor personnel; floating access will also be provided to unoccupied government workstations. NGIC computer workstations will be equipped with all software necessary for the completion of tasks described in this PWS. All government-furnished equipment will remain the property of NGIC.

3.3. Utilities. The government will provide all utilities in the facility for the contractor’s use in performance of tasks outlined in this PWS. The contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions that preclude the waste of utilities, such as turning off the water faucets or valves after using the required amount.

3.4. Information/Data.

3.4.1. The government will provide electronic access to appropriate intelligence community electronic data resources through on-site NSANET, JWICS, SIPRNET and unclassified internet workstations.

Additionally, NGIC will provide the contractor with applicable hard-copy intelligence source documents, published security regulations and production guidance, and pertinent reference materials as determined jointly by the COR and contractor personnel. NGIC will also provide a listing of assigned government analysts for each threat system for which NGIC is responsible.

3.4.2. While appropriate access to data will be provided to contractor personnel on-site at ngic, this contract shall not require or sanction the transfer of sci data or materials off-site to the contractor's own secure facility. Digital data files containing classified material at the collateral level may be supplied to the contractor by the appropriate approved means of secure transfer. Classified hardcopy documents, compact disks (cds) and digital videos (dvds) may be delivered to the contractor by courier or secure mail.

The contractor shall be responsible for safeguarding all classified information and unclassified material subject to distribution restrictions, throughout the duration of this contract. Contractor personnel responsible for data management will be required to maintain courier and data transfer agent credentials for the term of the contract.

PART 4: CONTRACTOR FURNISHED ITEMS AND SERVICES

4.1. General. The contractor shall furnish all supplies, equipment, facilities and services required to perform work under this contract that are not listed under Section 3 of this PWS.

4.2. NGIC does not currently have an operational installation of Joint Analytic Data Editor (JADE), Synchronized and scalable Audio Video content Across NeTworks (SAVANT), or any other EWIRDB production enterprise software onsite at NGIC. All EWIRDB models shall be produced off-site at the contractor's facility using the contractor’s wholly self-contained EWIR production process, and delivered to NGIC for stand-alone, read-only review and acceptance, until such time as a validated, fully functioning EWIRDB production enterprise can be established at NGIC.

4.3. In order to accomplish the work being tasked, the contractor shall possess a fully functional EWIR/JADE/SAVANT or equivalent installation that is operating on a SECRET-level platform and/or network at the contractor's facility. The contractor shall designate a workstation within the contractor's local production facility that can be used by the COR to review deliverables being submitted for acceptance.

4.4. The contractor will be completely responsible for obtaining, maintaining, and administering the required software, hardware, licenses, training, credentials, and accreditation necessary to implement a fully self-contained EWIRDB production enterprise. The government intends the contractor to commence EWIRDB production immediately upon award of the contract, and possesses neither the resources nor technical expertise to provide any technical assistance or training to the contractor concerning EWIRDB tools, production software, databasing, accreditation, or any other software, infrastructure, or analytic process concerns.

PART 5: SPECIFIC TASKS

5.0. Specific Tasks:

5.1. 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 task order will specify the work to be accomplished under one or more of the EWIR production subtasks, but a task order need not exercise all ten subtasks. For every task order, 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.

5.1.1. 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.

5.1.1.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.

5.1.1.1.1. All-Source Intelligence Research Tasking List

Each task order 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 task order 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 task order, 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 task order, 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.

5.1.1.1.2. 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.

5.1.1.1.3. Data-mining

Search engines available for data-mining include applications including (but not limited to) 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 enable effective retrieval of all relevant messages that are streamed through DIA's message traffic system or that have already been stored in DIA or other Intelligence Community 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.

5.1.1.1.4. Screening, Validation, and Dissemination

The contractor shall compare the information in each new document against the data in the EWIRDB and CED/EIM/EEM 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.

5.1.1.1.5 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 portable document format (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).

5.1.1.1.6. Performance Considerations

5.1.1.1.6.1. 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 shall be processed and evaluated for NGIC’s total EWIR production portfolio of approximately 200 systems.

5.1.1.1.6.2. 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.

5.1.1.1.6.3. 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.