ID05150001_SOW_(FBO).doc

U.S. General Service Administration Statement of Work

Establishment of

Blanket Purchase Agreement (BPA) Statement of Work (SOW)

Intelligence Mission Data (IMD) Support: EWIRDB, Characteristics & Performance (C&P), Signatures, Order of Battle (OOB) & EWIRDB Support for Foreign Military Sales (FMS)

For

National Air and Space Intelligence Center (NASIC) Wright-Patterson Air Force Base, Ohio

OCTOBER 17, 2014

1.0 Requiring Agency

National Air and Space Intelligence Center

Electronic Analysis Squadron 4180 Watson Way

Wright-Patterson AFB, Ohio 45433-5648

National Air and Space Intelligence Center

Client Representative (CR): Patricia Schuerman Office Symbol: NASIC/XPQ

Phone: 937-522-4889 Fax: 937-656-0655

E-mail: patricia.schuerman@us.af.mil National Air and Space Intelligence Center

Primary Technical Representative: Donald S. Chrapko Office Symbol: NASIC/ACLA

Phone: 937-522-4875 Fax: 937-656-0313 E-mail: donald.chrapko@us.af.mil National Air and Space Intelligence Center

FMS Technical Representative: Rodney W. Stark Office Symbol: NASIC/ACLA

Phone: 937-522-4872 Fax: 937-656-0313 E-Mail: rodney.stark@us.af.mil GSA Contracting Officer Representative (COR)

Benny Reyes

Phone: 937-431-5530

Fax: 937-427-3970

E-mail: benny.reyers@gsa.gov GSA Contracting Officer (CO)

Cassandra Hannah-Boyd

Phone: 312-886-7499 Fax: 312-886-3827 E-mail: cassandra.hannahboyd@gsa.gov

(X) New Task

(X) Fixed Price

(X) Time & Materials

(X) On-Site

(X) Off-site

2.0 INTRODUCTION/BACKGROUND

This Blanket Purchase Agreement renews the ongoing work accomplished under the existing BPA 5TP57100200: Electronic Warfare Integrated Reprogramming Database (EWIRDB) and Next Generation EWIRDB System (NGES) U.S. Foreign Military Sales (FMS) Production and Training Support dated October 2009. As a major stakeholder directly supporting the Department of Defense Directive Number 5250.01 (January 22, 2013), Management of Intelligence Mission Data (IMD) in DoD Acquisition, the National Air and Space Intelligence Center (NASIC) creates integrated, predictive intelligence products in four of the five IMD primary functional areas: EWIR, Characteristics & Performance (C&P), Signatures, and to a lesser extent, Order of Battle (OOB).

In addition to the IMD support, NASIC functions as the Executive Agent for both the U.S. and FMS EWIRDB and as such, hosts and disseminates each, as well as, participates in the file creation of those specialized products. Finally, the analysis and production efforts performed under this BPA directly feed or influence data required for other complementary databases such as, but not limited to, the Air Force Mission Support System/Combat Support Database (AFMSS/CSDB), and Military Equipment Parametric and Engineering Database, (MEPED) mission requirements.

3.0 SCOPE OF WORK /OBJECTIVE

The scope of the work involves all aspects of IMD and FMS support to include (but not limited to) data research and acquisition, critical analysis, expert assessment, and subsequent system file creation. In addition to the analysis aspects, support for training, mentoring and collaborating with analysts from NASIC and other production center partners and users across the IMD and FMS communities to ensure consistency of standards and production methodology to the extent possible remains a critical requirement.

Therefore, the contractor shall make their expertise available to Missile & Space Intelligence Center (MSIC), National Air and Space Intelligence Center (NASIC), National Ground Intelligence Center (NGIC), and Office of Naval Intelligence (ONI) and other user/producers/analysts (as directed by the U.S. government) who are generating similar products in-house for both IMD and EWIRDB FMS missions. Support during technical meetings and familiarization sessions may also be required.

4.0 CONTRACTOR REQUIREMENTS

At a minimum, the contractor shall possess analysis expertise in all IMD functional areas: EWIR, C&P, Signatures, and OOB. In addition, the contractor shall possess expertise in peripheral functional areas such as AFMSS/CSDB and MEPED and in particular all Tech ELINT related activities as they support EWIRDB end-to-end processing.

Furthermore, the contractor shall possess Information Technology (IT) expertise for both modeling and tool development that extends into and interacts with NASIC’s SAVANT infrastructure, NASIC’s Opana frameworks, the 453 Electronic Warfare Squadron (EWS) United States Relational Electromagnetic Systems database/Relational Parametrics (USRELMS/RELPARA) architecture and other functionally related infrastructures across the IMD community as they pertain to collaborative production activities.

The contractor shall provide a program manager cognizant of the overarching relationships of NASIC’s IMD commitments and engagement across the user/producer community. The program manager shall provide total task management and shall supervise contractor personnel. The contractor program manager shall serve as the primary point of contact to the government Client Representative (CR) for all technical aspects of the required work. No personal services shall be performed under this contract.

5.0 APPLICABLE DOCUMENTS

Applicable documents will be determined on an individual Task Order basis (TO).

6.0 STATEMENT OF WORK (SOW) REQUIREMENTS

6.1 Task 1 - Project Management

The contractor shall provide all labor, facilities, and non-Government Furnished Equipment (non-GFE) to successfully complete all operations and maintenance (O&M -CLIN0001) and research and development ( R&D -CLIN0001A) tasks that support the management of EWIRDB, Technical ELINT, C&P, Signatures, OOB, CSDB, MEPED, and FMS activities to include the following:

6.1.1 Create and maintain a Project Management Plan. The Project Management Plan shall describe, as a minimum, the resources necessary to accomplish the SOW. The Project Management Plan shall be completed and certified by the contractor, the CR, and the GSA Contracting Officer (CO) within 30 calendar days after award of Task Order. (Ref: Table 7.8 - deliverable 1.)

6.1.2 The contractor shall provide up-to-date status, individually for each Task Order with an active period of performance, through Monthly Status/Financial Reports. Monthly Status/Financial Reports shall be unclassified and shall include details on the following items for each previous time period: (1) Best up-to-date estimate of hours worked and therefore expected charges, including those of subcontractors; (2) status of work performance; (3) any problems or concerns encountered that may impact cost or schedule; (4) status of open items from previous reports; (5) any suggested solutions; (6) personnel changes; (7) proposed government actions; (8) a summary chart of the current financial status on all CLINs (labor, ODCs/travel, material). (Ref: Table 7.8 – deliverables 2.)

6.1.3 The contractor shall provide up-to-date status, individually for each Task Order with an active period of performance, through quarterly Program Management Reviews (PMRs). The contractor’s program manager shall be required to present oral program reviews as requested by the NASIC CR or Technical Monitor (TM). (Ref: Table 7.8 – deliverables 3.)

6.1.4 Prepare written documentation on the results of tasking to include verbal and written comments, informational memorandums and letters, meeting minutes, specialized technical reports and papers, as well as final report and studies as defined in individual Task Orders. Present briefings on government selected studies, models, or analyses associated with task efforts to various intelligence organizations, committees, or panels as defined in the individual Task Orders by the government. The contractor shall prepare and present the briefings to the government appointed experts prior to the actual presentation, to ensure content accuracy and that security considerations are properly addressed and followed. (Ref: Table 7.8 – deliverables 4 and 5.)

6.1.5 Maintain a complete listing of classified material issued by the government and maintained at the contractor’s facility in performance of this contract to include, the title of the material; the origination date; the overall classification; the type of material (i.e. report, electronic media, etc.); the number of copies held; and any other information necessary to identify the inventory. Further, the contractor shall obtain written approval by the CR prior to the release of any classified material. The contractor shall provide the CR with a destruction certificate for all classified material that is destroyed. (Ref: Table 7.2 – deliverable 6.)

6.2. Task 2 – The contractor shall provide the necessary resources to plan, implement, and manage the tasks set forth below either on-site or off-site as required in each individual Task Order to the extent provided by the available man-hours. Activities under this task require support to include O&M (CLIN0002) and/or R&D (CLIN0002A) tasks in the subsections to follow. (Ref: Table 7.2 – deliverables 4, 5, 7, 8, and 9.)

6.2.1 O&M Support. The contractor shall provide mentoring, technical expertise, and analytic support for standardized product generation by NASIC analysts.

6.2.2 O&M Production. The contractor shall perform research, data acquisition, and technical analysis to provide SAVANT compliant product initialization and/or updates on specified systems as directed by the government technical representative or Technical Monitor (TM). The contractor shall maintain thorough knowledge of the primary tools anticipated for usage under this task (i.e. Systematic Architecture for Virtual Analytic Netcentric Information (SAVANT), MARTES, Combined Emitter Database (CED), Knowledge Pre-positioning System (KPS), JADE, and the Opana suite of tools). (Ref: Table 7.8 – deliverable 7 and 9.)

6.2.3 O&M Training and Familiarization. The contractor shall provide functional area training and/or familiarization, to both U.S. and/or foreign partners, as it pertains to design considerations and efficient SAVANT compliant software usage for both producers and users of the selected functional area data. (Ref: Table 7.8 – deliverable 8.)

6.2.3.1 US Participants. The contractor shall provide Producer and/or User training and mentoring on an ad hoc basis using the following guidelines:

a. Class format shall be determined based on anticipated student participation.

b. The primary location of the classes shall be in the Dayton, OH locality and may involve both government and contractor facilities.

c. The contractor shall provide a task leader to oversee total task management and supervise contractor personnel. The task leader shall serve as the primary point of contact to the government Client Representative (CR) for all technical aspects of the required work.

d. Training which requires travel shall be coordinated with the EWIRDB Executive Agent prior to making travel arrangements.

6.2.3.2 Foreign Participants. The contractor shall provide familiarization for foreign customers consistent with the Arms Export Control Act (22 USC); and International Traffic in Arms Regulation (ITAR) (22 CFR 120-130).

a. The requirement and funding for this task shall be specified by the appropriate Technical Monitor (TM) or if in the case of FMS support, the FMS EWIRDB Program Manager (FMS Technical Representative).

b. Class format shall be coordinated with the appropriate Technical Representative or TM prior to performance of this task.

c. In all cases, the contractor shall submit a rough order of magnitude (ROM) to the government indicating expected costs of presenting the functional familiarization.

d. The location of the classes shall be coordinated with the appropriate technical representative or TM. Location may involve both government and contractor facilities and may include travel.

e. The contractor shall provide a task leader to oversee total task management and supervise contractor personnel. The task leader shall serve as the primary point of contact to the CR and FMS technical representative for all technical aspects of the required work.

6.2.4 O&M Analytic Tools and Utilities: Maintenance and Upgrades. The contractor shall review, report defects, recommend and create enhancements to existing applicable SAVANT compliant software tools and utilities as directed by the appropriate government technical representative or TM. The contractor shall accompany all recommended enhancements with an appropriate white paper write-up and a ROM cost estimate to the appropriate government TM. No software development shall initiate prior to government acceptance. Software upgrades shall be fully SAVANT compliant with sufficient regression testing to ensure continued compatibility across functional areas. (Ref: Table 7.8 – deliverable 5 and 9.)

6.2.5 R&D Utility Development. The contractor shall develop and/or test applicable SAVANT compliant software tools and utilities as directed by the appropriate government technical representative or TM. The contractor shall accompany all recommended enhancements with an appropriate white paper write-up and a ROM cost estimate to the appropriate government technical representative. No software development shall initiate prior to government acceptance. (Ref: Table 7.8 – deliverable 9.)

6.2.6 Foreign Military Sales Analysis Production and Support. The contractor shall perform technical analysis on selected EWIRDB emitter systems as requested by the FMS technical representative or TM. The analysis shall be used as the basis for updates and/or initializations to casework associated with the Foreign Military Sales EWIRDB “Direct” and/or “Indirect” customers. (Ref: Table 7.8 – deliverable 7.)

6.2.6.1 Direct Database Customers. Data initializations and/or updates for direct customers shall comply with the formatting and standards established within the existing Foreign Military Sales Direct Database (FMS-DDB). The specific countries supported shall be delineated via subsequent Task Orders (TOs).

6.2.6.2 Indirect Database Customers. Data initializations and/or updates for indirect customers shall comply with the Standard EWIR Reference Format (SERF) XML-based EWIRDB.

6.2.6.3 Funding Provided by FMS Cases. The contractor shall track and report funding expenditures (provided through FMS cases) based on country lists provided by the government via subsequent Task Orders (TOs).

7.0 DELIVERABLES/SCHEDULE

7.1 Deliverables Acceptance Criteria: - Deliverables (to include technical reports and briefings) issued under this contract shall contain the following acknowledgments: "This research was supported and monitored by the National Air and Space Intelligence Center (NASIC) under Contract “(insert contract number here).” Further, it shall have a disclaimer to the effect that the report is the contractor's opinion based on information furnished to them and does not necessarily represent the opinion of any government agency.

7.1.1 Inspection Point - NASIC/XPQ will be the point for final inspection and acceptance by the government for all special tasks, data, and reports called for during the contract period. For each task levied on the contractor, the designated CR or Technical Monitor shall be responsible for the evaluation and acceptance of all products resulting from an assigned task.

7.1.2 Review - All work shall be subject to review by the designated NASIC Technical Monitor. The work will be in accordance with NASIC policy as identified in Task Orders, regulations, instructions, or subsequent superseding documentation; or as conveyed to contractor personnel by the NASIC CR or their designee(s) through the contractor's Program Manager.

7.1.3 Report Delivery - The contractor shall deliver the draft/final reports to the Technical Monitor in one hardcopy and one softcopy format (determined in each Task Order) in the NASIC currently installed versions of Microsoft Office. If another format is required, it will be specified in each individual Task Order.

7.1.4 Review Constraints - The Technical Monitor will have 10 calendar days to review the draft deliverables and make comments. The contractor shall then have five (5) calendar days to make all recommended corrections/changes. The final report shall be delivered to the Technical Monitor and/or CR who shall have five (5) calendar days for final review prior to acceptance or provide documented reasons for non-acceptance. When the government fails to complete the review within the time specified the deliverable shall become acceptable by default.

7.1.5 Rejections - The CR shall have the right to reject or require correction of any deficiencies found in the deliverables that are contrary to the information contained in the contractor's accepted proposal. In the event of rejection of any deliverable, the contractor shall be notified in writing by the CR of the specific reasons why the deliverable is being rejected. The contractor shall have five (5) calendar days to correct the rejected deliverable and return it.

7.1.6 Product Format Requirements. Contractors working in a government facility will have daily contact with government analysts and shall adhere to local analysis practice as directed at the time of performance activities. Analysis products created in a non-government facility and delivered under this BPA shall conform to the following guidelines unless otherwise directed by the task Technical Monitor either through the specific Task Order (TO) or by verbal agreement. If changes are made verbally, the contractor shall provide their written understanding of requirements for government review and approval prior to departing from the formatting standards that follow. The typical CD/DVD shall contain a top-level summary of the data content contained on the delivered media, table of contents, virtual system folders as required, analyst’s notes & issues, and references used.

7.1.7 Delivery of Reports: - All unclassified written deliverables (reports, monthly status reports, etc.) shall be emailed to the CR and TM. All classified deliverables shall be forwarded to CR (or their appointed representative) as follows:

7.1.7.1 Collateral Reports: All reports classified SECRET or below shall be hand-delivered to NASIC or forwarded via registered mail, postage affixed, directly to:

Outside wrapper markings:

NASIC/XPQ

ATTN: Contract Nr/Task Number 4180 Watson Way

Wright-Patterson AFB, OH 45433-5648

7.1.7.2 SCI Reports: All SCI reports submitted under this contract shall be forwarded via the Defense Courier Service to:

Outer wrapper markings:

DEFENSE COURIER SERVICE

DODDAC: HKL266

Wright-Patterson AFB, OH 45433-5648

Inside wrapper markings:

TO BE OPENED BY APPROPRIATE CONTROL OFFICER

ATTN: Contract Nr/Task Number

NASIC/XPQ

Wright-Patterson AFB, OH 45433-5648

7.2 Engineering and Analysis for SERF-based EWIRDB Production. The contractor shall ensure their analysis practice meets the following guidelines unless otherwise directed in subsequent Task Assignment Guides:

7.2.1 General Requirements. The contractor shall ensure the virtual file folders include the following items:

a. Administrative Section: This section shall include a Table of Contents for the folder, plus File Administrative Data including remarks, keywords for data searches, data gaps, issues, and telecoms with NASIC analysts.

b. File Section: This section shall contain the actual EWIRDB file(s).Technical ELINT Reference File (TERF) based files shall be of standard EWIRDB format for airborne systems and CROSSBOW format for ground based systems. SERF-based XML system files shall be Knowledge Pre-positioning Systems (KPS) Internal format, complete with multimedia attachments.

c. AMBER Files: The section shall contain *.mdl and *.ant AMBER files per direction of the government for NASIC ground based systems. This section shall be marked N/A for NASIC airborne systems.

d. EWIRDB Spreadsheet: This section shall contain the analyst's EWIRDB spreadsheet file, which shall show calculated parameters.

e. Reference Section: The contractor shall use this section to hold any digitized references or other miscellaneous materials (text files, pdf files, html files, etc.) that could be relevant to the subject analysis. A summary document of references cited in the actual system/emitter file shall also be included.

Note: When performing analysis at non-government facilities, and where applicable, the contractor shall convert new intelligence documents used to produce system files into a digital format following the guidelines that follow:

1. Each document shall exist as a stand-alone file.

2. Photos, graphs, tables, and other graphics may be stored within the main document or accessed via an external link. The method shall be consistent among all documents and approved by the government.

3. The contractor shall receive approval from the government prior to digitizing non-NASIC Finished Intelligence documents, which are more than 25 pages in length, or NASIC Finished Intelligence documents more than 5 pages in length.

7.2.2 Analysis Requirements. The contractor shall perform technical analysis to provide updates and/or initializations to specified emitter systems as requested by the EWIRDB Executive Agent.

a. Following standard operating procedures, the contractor shall research and consult additional reference material for clarification and completeness of analysis; however, for select systems, the government may direct a minimal amount of research be accomplished. The primary source of information for creating file initializations will be the legacy TERF-based EWIRDB file and its associated source references.

b. The contractor shall select the most appropriate and efficient means available to aid the transition from legacy TERF-based EWIRDB files to new SERF-based EWIRDB files.

c. The contractor shall make use of any EWIR Community shared migration and analysis aids provided as necessary.

d. The contractor shall ensure the EWIRDB TERF is accurate and complete. For those files where problems exist, the contractor shall take steps to ensure deficiencies are not propagated to the new file(s).

e. The contractor shall make use of the Joint Analytic Data Editor (JADE) and TERF-to-SERF migration software as appropriate.

f. The contractor shall complete basic State View representations for each radar system as appropriate.

g. The contractor shall ensure each radar system also has the associated KPS Core data (designators, User countries etc.) and one or more associated antenna models (as required).

h. All EWIRDB production work shall undergo a rigorous quality control assessment utilizing all available software tools to aid in assuring system files meet established EWIRDB standards. Any standards not met shall be documented (with the reason why) in the administrative section of the virtual file folder. Therefore, the contractor shall perform a technical quality control assessment for each radar threat model (RTM) created. In addition to the accepted EWIRDB community standards, unless otherwise noted, each RTM shall include successful performance within the following applications:

1. STRIKE FORCE+

2. StateView

3. ModalView

4. Keystone

5. Topaz

6. ScanVisualization

7. Multimedia Review Tool

8. TechQC Tool

i. Results that do not conform to normal standards require specific comments within the admin section of the virtual folder. An example would be non-compliance of a specific recently approved EWIRDB standard or “holes” within the ModalView results.

j. As part of the QC procedures, the contractor shall have a senior radar analyst review each instantiated radar system to ensure accuracy, completeness, and conformity with sound engineering and analytic practice.

k. The contractor shall ensure all necessary fields are populated to support a MEPED export.

7.3 Engineering and Analysis for TERF-based EWIRDB Production. The contractor shall ensure their analysis practice meets the following guidelines unless otherwise directed in subsequent Task Assignment Guides:

7.3.1 General Requirements. The contractor shall ensure the virtual file folders include the following items:

a. Administrative Section: This section shall include a Table of Contents for the folder, plus File Administrative Data including remarks, keywords for data searches, data gaps, issues, and telecoms with NASIC analysts.

b. File Section: This section shall contain the actual EWIRDB file(s).TERF-based files shall be of standard EWIRDB format for airborne systems and CROSSBOW format for ground based systems. SERF-based XML system files shall be KPS Internal format, complete with multimedia attachments.

c. AMBER files: The section shall contain *.mdl and *.ant AMBER files per direction of the government for NASIC ground based systems. This section shall be marked N/A for NASIC airborne systems.

d. EWIRDB Spreadsheet: This section shall contain the analyst's EWIRDB spreadsheet file, which shall show calculated parameters.

e. Reference Section: The contractor shall use this section to hold any digitized references or other miscellaneous materials (text files, pdf files, html files, etc.) that could be relevant to the subject analysis. A summary document of references cited in the actual system/emitter file shall also be included.

Note: When performing analysis at non-government facilities, and where applicable, the contractor shall convert new intelligence documents used to produce system files into a digital format following the guidelines that follow:

1. Each document shall exist as a stand-alone file.

2. Photos, graphs, tables, and other graphics may be stored within the main document or accessed via an external link. The method shall be consistent among all documents and approved by the government.

3. The contractor shall receive approval from the government prior to digitizing non-NASIC Finished Intelligence documents, which are more than 25 pages in length, or NASIC Finished Intelligence documents more than 5 pages in length.

7.3.2 Analysis Requirements. The contractor shall perform technical analysis to provide parametric updates and/or initializations to selected legacy TERF-based EWIRDB radar files as directed by the EWIRDB Executive Agent or FMS EWIRDB Program Manager.

a. Following standard operating procedures, the contractor shall research and consult additional reference material for clarification and completeness of analysis for each radar system and then update/initialize file parametric attributes based on the best available intelligence data.

b. The contractor shall enter mode-coded data and update the suffix table associated with any legacy TERF-based EWIRDB file.

c. The contractor shall enter required FMS codes and related FMS information into the EWIRDB file as required.

d. The contractor shall ensure all necessary fields are populated to support a MEPED export.

e. All EWIRDB production work shall undergo a rigorous quality control assessment utilizing all available software tools to aid in assuring system files meet established EWIRDB standards. Any standards not met shall be documented (with the reason why) in the administrative section of the virtual file folder. Therefore, the contractor shall perform a technical quality control assessment for each radar system created.

f. As part of the QC procedures, the contractor shall have a senior radar analyst review each instantiated radar system to ensure accuracy, completeness, and conformity with sound engineering and analytic practice.

7.4 Engineering and Analysis for AFMSS/CSDB Production. The contractor shall ensure their analysis practice meets the following guidelines unless otherwise directed in subsequent Task Assignment Guides:

7.4.1 General Requirements. The contractor shall ensure the virtual file folders include the following items:

a. Administrative Section: This section shall include a Table of Contents for the folder, plus File Administrative Data including remarks, keywords for data searches, data gaps, and telecoms with NASIC analysts.

b. File Section: This section shall contain the actual TERF file, and a formatted printout of the file. The file shall be normal EWIRDB format for airborne systems and CSDB TERF format for ground based systems.

c. AMBER files: The section shall contain *.mdl and *.ant AMBER files per direction of the government for NASIC ground based systems. This section shall be marked N/A for NASIC airborne systems.

d. Modeling of the threat radar's maximum detection range (MDR). The contractor shall use AMBER as the baseline comparison tool for determining the assessed range performance in the Threats on the fly (TOTF) and counter Low Observable Auto Router (CLOAR) models. All significant modes shall be coded into the AFMSS CSDB file.

e. AFMSS/CSDB Spreadsheet: This section shall contain the analyst's AFMSS/CSDB spreadsheet file, which shall show calculated parameters.

f. Reference Section: The contractor shall use this section to hold any digitized references or other miscellaneous materials (text files, pdf files, html files, etc.) that could be relevant to the subject analysis. A summary document of references cited in the actual TERF file shall also be included.

Note: When performing analysis at non-government facilities, and where applicable, the contractor shall convert new intelligence documents used to produce system files into a digital format following the guidelines that follow:

1. Each document shall exist as a stand-alone file.

2. Photos, graphs, tables, and other graphics may be stored within the main document or accessed via an external link. The method shall be consistent among all documents and approved by the government.

3. The contractor shall receive approval from the government prior to digitizing non-NASIC Finished Intelligence documents, which are more than 25 pages in length, or NASIC Finished Intelligence documents more than 5 pages in length.

7.4.2 Analysis Requirements. The contractor shall perform technical analysis to provide parametric updates to selected AFMSS/CSDB radar files, as directed by the NASIC CSDB Program Manager.

a. Following standard operating procedures, the contractor shall research and consult additional reference material for clarification and completeness of analysis for each radar system and then update/initialize file parametric attributes based on the best available intelligence data.

b. The contractor shall enter mode-coded data and update the suffix table associated with any AFMSS/CSDB file.

c. The contractor shall enter required FMS codes and related FMS information into the AFMSS/CSDB file as needed.

d. All CSDB production work shall undergo a rigorous quality control assessment utilizing all available software tools to aid in assuring system files meet established CSDB standards. Any standards not met shall be documented (with the reason why) in the administrative section of the virtual file folder. Therefore, the contractor shall perform a technical quality control assessment for each radar system created following established procedures called out by the Program Manager, CSDB Producer’s Manual and the 453rd EWS.

e. As part of the QC procedures, the contractor shall have a senior radar analyst review each instantiated radar system to ensure accuracy, completeness, and conformity with sound engineering and analytic practice.

7.5 Engineering and Analysis for Observed ELINT Data Production. The contractor shall provide observed ELINT data production on-site at the National Air & Space Intelligence Center.

7.5.1 General Requirements. The contractor shall provide EW Signal Model production for both the ELINT Intercept Model (EIM) and the Observed ELINT Engineering Model (OEEM) as directed by NASIC/GXS Signals Analysis Squadron technical representative or Technical Monitor (TM). The government shall direct which systems and models will be targeted for production and will provide all required data necessary for model instantiation. Additional system research to support production is not anticipated; however, may be accomplished if requested by the government technical representative or TM.

7.5.2 Personnel Qualifications. In addition to any previously mentioned personnel qualifications, the selected technical analysts shall possess a full understanding and working knowledge of KILTING, EWIR/EWIRDB, Knowledge Pre-Positioning System (KPS), Joint Analytic Data Editor (JADE), OEEM, EIM, ORCA, Data Assessment and Selection Services (DASS) and the Combined Emitter Database (CED).

7.5.3 Product Requirements. The final product for all OEEM models shall complement and contribute toward the all-source assessment for that same system. Note: This requirement implies the OEEM system work shall be fully compatible and ready for use by All Source analysts. Completed signals analysis products (i.e. EIM/OEEM) shall be submitted to the appropriate government technical representative for inclusion in the master EIM/OEEM repository.

7.6 Engineering and Analysis for Combat/Combat Support Aircraft Production. The contractor shall perform technical information research, provide expert technical assessment, and accomplish documentation on combat/combat support aircraft data in support of baseline IMD requirements. In addition to an IMD baseline, production data under this BPA also supports Air Force Mission Support System/Combat Support Database (AFMSS/CSDB), and Military Equipment Parametric and Engineering Database (MEPED) mission requirements.

7.6.1 General Requirements. The contractor shall employ their technical expertise to ensure relevance and accuracy of the required data gleaned from the researched combat/combat support aircraft technical information. Upon government validation of the contractor’s initial assessments, the contractor shall transfer that data to NASIC’s Fixed Wing Aircraft (FWA) database in support.

7.6.2 Technical Information Research. The contractor shall perform classified and unclassified technical information research on assigned combat/combat support aircraft to find each aircraft’s performance and technical characteristics, propulsion system, avionics fit, and other aircraft-specific data spelled out in the NASIC-provided Manned Aircraft / FWA (Fixed Wing Aircraft) Analysts User Guide. NASIC will provide a partial list of classified and unclassified web sites for the contractor’s use as a start for their research.

7.6.3 Technical Assessment. The contractor shall provide the technical expertise necessary to ensure relevance and accuracy of the required combat/combat support aircraft data gleaned from the researched aircraft technical information.

7.6.4 Documentation of Aircraft Data. The contractor shall document all resultant combat/combat support aircraft data and their sources in NASIC-prescribed Microsoft Excel spreadsheet format.

7.6.5 Government Verification and Validation. The contractor shall submit completed spreadsheets to the government technical monitor (TM) of this task for his/her review, verification, and validation. Once validated by the government, the spreadsheet(s) will be returned to the contractor for their use as the data source for populating the NASIC’s combat/combat support FWA database.

7.6.6 Populating Combat/Combat Support FWA Database. The contractor shall input all required combat/combat support aircraft data from the government-validated aircraft spreadsheets into the NASIC-designated database by following the directions contained in the NASIC-provided Manned Aircraft / FWA Analysts User Guide.

7.7 Software Development. All software shall be NASIC SAVANT compliant; therefore, software that is not compatible with the SAVANT KPS/Virtual Production System (VPS) architecture shall not be considered as a viable submission. Software that is intended to extend the general SAVANT capabilities shall be considered on a case by case basis. Software that falls into this category shall require government approval prior to utilization for all software projects. (Ref: Table 7.8 – deliverable 9.)

7.7.1 Requirements Analysis. Perform analyses of infrastructure, operational, technical, functional, data and interface requirements. Design, develop, compare and evaluate potential technical solutions, concepts or alternatives to meet requirements. Transform statements of requirements into designs that satisfy NASIC needs in a sound technical and cost effective manner. Assess, determine and document the impacts that such solutions or other emerging technologies may have on NASIC mission.

7.7.1.1 Provide system architectural designs, ensuring that all the requirements for the software items are allocated, refined and documented to facilitate detailed design. Designs shall elaborate and/or refine software requirements to form a basis for the development and implementation of the capabilities and shall conform to NASIC and government standards, and best practices. Designs shall also be consistent with unique user, service, command, agency or community oriented policies and procedures. The design process may include Preliminary, Detailed and Critical Design Reviews (PDRs, DDRs and CDRs). (Ref: Table 7.8 – deliverable 9.)

7.7.1.2 Perform software requirements analysis and document the software level requirements describing, at a minimum, the functional capability specifications, performance, interfaces, qualifications requirements, security specifications, human factors engineering, data definition and database requirements, installation and acceptance requirements. Document and present the results. (Ref: Table 7.8 – deliverable 9.)

7.7.2 Use of Non-Developmental Software (NDS). Maintain cognizance of developments in Commercial off the shelf (COTS) and Government off the shelf (GOTS) software. All development shall maximize the use of such software. Evaluate the planning performed for the use of NDS to ensure that all applicable PWS requirements have been met. Upon acquisition, evaluate the software to determine whether it performs as documented and is adequately documented. Ensure that the software will pass NASIC security and/or information assurance testing (e.g., CTO testing) prior to incorporating it into the software being developed.

7.7.2.1 NDS software. For all software/hardware purchased or licensed, arrangements shall be made for licensing and maintenance agreements to transfer to the government upon completion of this effort. All hardware and software must be compliant with NASIC IT architecture and standards.

7.7.3 Develop/Implement/Code. Satisfy requirements by building system enhancements and/or new engineering developments. Perform software coding and testing for each software component/item in accordance with the approved Software Development Plan (SDP).

7.7.4 Modification of existing software and documentation. All software to be developed or enhanced shall utilize the design and coding standards of the existing software. All modifications to existing software shall be documented as updates to the existing documentation. All software and database development must adhere to NASIC-33-108 (NASIC IT Management Concept of Operations (CONOPS)) and its successors and/or addendums. NASIC/SC shall determine which components of NASIC-33-108 will be tailored out on a case-by-case basis. (Ref: Table 7.8 – deliverable 9.) Anticipated documentation includes:

a. Functional Description

b. Data Base Specification

c. User Manual

d. Computer Operation Manual

e. Maintenance Manual

f. System/Subsystem Specification

g. Data Requirements Document

h. Software Unit Specification

i. Implementation Procedures

j. Training Material

7.7.5 System Documentation. Software documentation furnished under this BPA shall be delivered in electronic format compatible with Microsoft Office products. Typical documentation shall provide instruction on how to startup, shutdown and troubleshoot the system and lists of hardware and software used and physical and logical interface diagrams. Software delivered in support of Tech ELINT Opana Frameworks shall be placed into the NASIC Integrated Signals Intelligence SIGINT Lab (ISL) Infocenter on G-FORGE. Where applicable, documentation shall address: (Ref: Table 7.8 – deliverable 9.)

a. Startup/shutdown procedures (to include reboots from unscheduled shutdowns)

b. Key system processes & how to monitor/fix/restart any failed processes or process components

c. Dependencies on other systems and resources

d. Location of all log files pertinent to system resources and applications

e. Rebuild procedures for a failed system including any procedures to rebuild storage or optional peripheral equipment

f. Rack elevations

g. Hardware list

h. Software list with versions

i. System interconnection diagrams

7.7.6 Integration. Increase the functional capability of the NASIC baseline through system engineering process to fully integrate into the software, documentation and programmatic baseline.

7.7.6.1 Perform system integration with other systems. Test the aggregates as they are developed, against their requirements.

7.7.6.2 Perform software integration and testing. Integrate the software units and software components and test as the aggregates are developed. Ensure the requirements for the software are met.

7.7.6.3 Perform software qualification testing for each software item.

7.7.6.4 Conduct in-plant testing in accordance with the government-approved test plans. The approved test plans shall include properly formatted documentation necessary to obtain a CTO and other security and/or information assurance approvals. Document the results in the Test Report. (Ref: Table 7.8 – deliverable 9.)

7.7.6.5 Upon successful completion of in-plant testing, install and test at NASIC in accordance with government-approved test plans. Prior to installation into the NASIC production environment, all approvals for installation and all CTO/security and/or information assurance approvals must have been granted by the government. Document the results in the Test Report. (Ref: Table 7.8 – deliverable 9.)

7.7.7 Configuration Management. Manage a CM and software maintenance process for assigned NASIC systems, activities, applications, databases and infrastructures; prepare and/or analyze BCRs and SPRs; provide implementation strategies in the form of WPs for effort directed at single or multiple BCRs and/or SPRs or combinations of BCRs and SPRs as identified by the government; and implement software changes associated with BCRs and SPRs. Submit initial WPs and submit updates to WPs as requested by the government due to scheduling, requirements, or other changes.

7.7.8 Software Problem Reports. Upon receipt of a Software Problem Report (SPR) from the government, investigate the problem to determine probable causes, potential resolutions, effort required, characterizations of various approaches, advantages and disadvantages of approaches, schedule, risks and cost of alternative courses of action to resolve, work around or mitigate the effects of the problem. Present results to the government via a WP for review, discussion, disposition, coordination and approval. Each WP shall contain testable performance requirements, deliverable items, delivery schedule, and cost. Perform the effort in accordance with the government-approved WP to close the SPR keeping the government cognizant of the status of the effort to achieve its goal of resolution within budget, performance and schedule. Participate in meetings to inform the government as to progress and/or need for approval to change the budget, scope, schedule or deliverables required as the situation may warrant. Deliver materials in compliance with NASIC configuration management, testing, installation practices and guidelines.

7.7.9 Baseline Change Requests. Upon receipt of a Baseline Change Request (BCR) from the government, perform a requirements analysis to define possible and recommended approaches, effort required, relationships to other ongoing effort, advantages and disadvantages of approaches, schedule, risks and cost of alternatives. Present results via a WP to the government for review, discussion, coordination and approval. Each WP shall contain testable performance requirements, deliverable items, delivery schedule, and cost. Perform the effort in accordance with the government-approved WP to develop the baseline change keeping the appropriate government representatives cognizant of the status of the effort towards achieving the objective within budget, performance and schedule. Participate in meetings to inform the government as to progress and/or need for approval to change the budget, scope, schedule or deliverables required as the situation may warrant. Deliver materials in compliance with NASIC configuration management, testing, installation practices and guidelines.

7.7.10 Certification and Fielding. Provide full documentation, functionality, and support to meet all testing, security, documentation and functional elements to transition the new or enhanced NASIC baseline capability to the field with full approval to operate at the NASIC and customer locations. Provide technical support for the installation, familiarization, certification and operation that will be maintained for each baseline and targeted customer. (Ref: Table 7.8 – deliverable 9.)

7.7.10.1 Perform and support all certification and security activities required to acquire security certification and approval to field. Provide all security and program documentation, support the program security testing, and comply with the NASIC approval processes for fielding the SAVANT baseline(s) within NASIC. Provide familiarization training for system capabilities.

7.7.11 Distribute and install the developed baseline within the user environment, integrate and configure all required components required for site acceptance and operations.

7.8 Schedule - The contractor shall submit reports and other deliverables in accordance with the requirements set forth in Table 7.8.

TABLE 7.8

8.0 MEETING ATTENDANCE/TRAVEL

8.1 Meeting Attendance - The contractor shall participate in regular team meetings, technical interchange meetings, threat coordination meetings, FMS customer meetings and working group meetings as required. Meetings may be held at Wright Patterson AFB, OH, the prime contractor facilities, or at other locations as requested by the government.

8.1.1 The contractor shall prepare and present briefings to the government when requested on the results of efforts undertaken for this SOW. The schedule will be as mutually agreed to between the contractor and the Technical Monitor. Briefings shall be conducted in appropriately cleared areas and IAW security rules and regulations.

8.2 Travel Requirements. Contract personnel will be required to travel to perform some of the efforts required in the SOW (both CONUS and/or OCONUS). All travel must be approved prior to occurrence. Failure to obtain pre-approved travel will result in non-payment by the government. Funding for travel shall be obligated at the Task Order level.

8.2.1 Travel between Wright-Patterson AFB, OH and the local contractor's office, and vice versa, is not a reimbursable cost under this contract.

8.2.2 All estimated travel (including the total number of trips, the beginning and duration of each trip, and the number of all contract personnel making the trip, location and associated costs) shall be subject to the advance approval of the CR. Professional personnel under this contract shall travel both inside and outside the continental United States as required. All requests for travel shall be submitted to the government CR via electronic email. Further, all travel preparations (air fare, hotel, rental car) shall be made by the contractor. The contractor shall adhere to Joint Travel Regulations policy and claims for reimbursement of expenses.

8.2.3 CONUS Travel Requirements: The contractor shall adhere to the requirements listed above and shall submit all requests for travel via electronic email to the CR a minimum of 15 calendar days prior to the anticipated travel start date.

8.2.4 OCONUS Travel Requirements: The contractor shall adhere to the requirements listed in 8.2.2, and when travel is required outside the continental United States, the contractor shall be responsible for all additional preparations to include, passports, inoculations, and transportation expenses. All clearance requests must be sent to the CR a minimum of 30 calendar days before the anticipated travel start date. Exceptions due to State Department regulations must also be taken into consideration for OCONUS travel.

9.0 PERSONNEL/REQUIREMENTS

9.1 Service

9.1.1. Services required interpretation of high level organizational engineering performance requirements such as projects, systems, missions, etc., and the objectives and approaches to their achievement.