18R0015_Solicitation_Amendment.docx

N6893618R0015

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 11-Jun-2018 04:00 PM to 14-Jun-2018 03:00 PM.

The following have been added by full text:

N68936-18-R-0015 Amendment 2

Offeror Questions and Government Responses

Question 1:

Given the date of the deadline for questions and the desire to submit a fully responsive, compliant proposal, contractor requests the government grant a two week extension to allow adequate time to respond.

Government Response:

The deadline to submit proposals has been extended to 14 June 2018 at 3:00 PM Pacific Time.

Question 2:

Attachment L-2, Instructions Worksheet title is "Instructions to Prime Contractors for completing Attachment L-5 Annual Fully Burdened Labor RFP # N68936-14-R-0108." Confirmation: Please confirm that Attachment L-2 applies to # N68936-18-R0015 and not "Attachment L-5 Annual Fully Burdened Labor RFP # N68936-14-R-0108."

Government Response:

The Government has updated Attachment L-2 to correct the clerical error. The updated attachment is provided with this amendment.

Question 3:

Section 1.4 Small Business (SB) Utilization Strategy. Question: Is there a page limit for communicating the Offeror's Small Business Utilization Strategy? Does this page limit affect other subsections that comprise Volume 1: Technical?

Government Response:

Yes, the page limit is 5 pages. The Table in L-1 Content of Proposals (Services) 26 March 2018 Part A Section 3.0 has been updated to show Technical subfactor 1.4 Small Business Utilization Strategy, with a five page limit. Furthermore, the total technical volume page limit has been increased to 60 total pages to accommodate the Small Business Utilization Strategy and the Transition Plan. (See also, Government Response to question 4)

Question 4:

The Transition Plan is not included the page limit table (Section 3, page 68). Question: Since Sections 1.1 through 1.3 take up all 45 pages of Volume 1, the contractor assumes there is no page limit associated with the Transition Plan. Is this assumption correct?

Government Response:

There is a 10 page limit associated with the transition plan. The Table in clause L-1 Content of Proposals (Services) 26 March 2018 Part A Section 3.0 has been updated to reflect this, and the total page limit increased for the Technical Volume. (See also, Government Response to question 3)

Question 5:

Section 3.0 indicates that Volume 2 should not exceed 25 pages. Question: (a) If forms for principal subcontractors or JVs are added, can the page limit be increased by 5 pages per form? (a) Are consent letters excluded from the page limit?

Government Response:

No, the page limit will not be increased. No, consent letters are included in the limit.

Question 6:

The instructions ask for "Signed SF33 for basic solicitation and acknowledgment of each amendment, including completion of any RFP clause or provision that requires a fill-in or response" in Volume 3. The instructions for Annex 1 also ask for "Offeror shall provide all Fill-Ins required by the solicitation." Question: Can the Government clarify where signed contractual material belongs?

Government Response:

Offerors should submit the signed proposal and amendments, including required offeror fill-ins of the RFP clauses with their completed proposal.

Question 7:

The instructions for Volume 2 Past Performance state: "The primary source of past performance information will be PPIRS. If a Contractor Performance Assessment Report (CPAR) exists for multiple years for the same contract/order ... [it] will be used for evaluation. In the event a CPAR does not exist for a past performance reference, the Offeror shall submit a Contractor Performance Assessment Questionnaire (CPAQ)..." Question: If a CPAR exists for a contract, but it is not in PPIRS, can the contractor submit a copy of the CPAR in their proposal?

Government Response:

Yes.

Question 8:

On page 33, the Government incorporates the Paperless Contracting (NAVAIR) (JUN 2009) clause, which states “terms “written”, ”mailed”, or “physically delivered” appear in other provisions of this contract, these terms are hereby defined to explicitly include electronic commerce, email, or paperless delivery methods.” Page 69 and 70, state offeror shall submit proposals via United States Postal Service or through commercial carrier. Question: Does the paperless clause apply to the proposal? If so, can the proposal be submitted electronically rather than via hard copy and CD-ROM?

Government Response:

No. As stated in L-1 Content of Proposals (Services) 26 March 2018, Part A Section 3.0 table, the Government’s requirements for printed and CD copies of proposals are clearly outlined.

Question 9:

Page 47 and 60, The NAICS Code listed in small business requirements is 541512 Computer Systems Design Services. Question: Would the Government consider adding the following NAICS Code 541712 or 541715 (Research and Development in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology)?

Government Response:

No.

Question 10:

Page 60, The Government includes FAR Clause 52.222-60, Paycheck Transparency (Executive Order 13673) OCT 2016, however, Executive Order 13683 stated Executive order 13673 has no force or effect. The current FAR lists 52.222-60 as Reserved. Question: Would the Government consider removing FAR Clause 52.222-60?

Government Response:

The Government has removed the clause.

Question 11:

There appears to be a discrepancy in the due date for submitting questions to the government.

Page 2 of the RFP states “*Questions pertaining to the RFP shall be submitted no later than 3:00 PM Pacific Time 10 business days after the solicitation is posted. Questions shall be submitted by email to lauryn.hiser@navy.mil <mailto:lauryn.hiser@navy.mil> with the RFP number as the subject line.”

Page 67 of the RFP states “Questions: Offerors may submit questions requesting clarification of solicitation requirements by emailing the contract specialist at lauryn.hiser@navy.mil <mailto:lauryn.hiser@navy.mil> . It is required that all questions be received within 10 calendar days of the date this solicitation is issued.”

Question: Would the government please provide clarification that the questions are due 10 business days after the solicitation is posted?

Government Response:

The RFP was corrected in Amendment 1 to “10 business days” in Section L, and the period for questions was clarified in Section A to state the period for questions ends on 25 May 2018.

Question 12:

Upon review of the above referenced RFP, we have noted that a discrepancy regarding the deadline for submitting questions.

Page 2 of the RFP indicates that questions are due “10 business days” after the solicitation is posted (which was May 10, 2018) and Section L-1 on Page 67 indicates that questions are due “10 calendar days” after the solicitation is issued.

Government Response:

Please see the Government Response to Question 11.

Question 13:

My company would like to request this contract be set aside for Service Disabled Veteran Owned Small Business.

Government Response:

This requirement is for a full and open competition.

Question 14:

Is the draft transition plan included within the page count for Volume 1: Technical, section 1.1 Technical Capabilities and Approach; or is it to be in the appendices, with no associated page limit?

Government Response:

Please see the response to question 4.

Question 15:

Please clarify the last day to submit questions pertaining to the RFP, perhaps specifying a date?

Government Response:

Please see the response to question 11.

Question 16:

Volume 2, Past Performance information shall be submitted 14 days prior to the submission date specified in Block 9 of the SF 33 of the RFP. Please clarify that this requirement is 14 calendar days prior to the 11 June 2018 proposal due date. Noting that this date (Monday, 28 May 2018) is a Government holiday, does that make the effective Past Performance due date Friday, 25 May 2018, or does it extend to Tuesday, 29 May 2018, due to the holiday? We assume the Government will not be available to receive the documentation on that specific date nor will the offeror be able to arrange for delivery on that date.

Government Response:

The due date will be Monday, June 4, 2018 3:00 PM Pacific Time, to account for the federal holiday and extension of the RFP as noted in the Government Response to question 1.

Question 17:

Provide a written narrative of the Offeror’s understanding and proposed capability to perform the requirements of the following Statement of Work (SOW) paragraphs: 3.2.3, 3.3, 3.5, and 3.6. Please confirm that these are the only SOW sections to be addressed the Volume 1, Section 1.1, Technical Capabilities and Approach portion of the proposal response.

Government Response:

Yes.

Question 18:

Does the SB Utilization Strategy count against Tech Volume page counts? Or, does it become an appendix, with no page count limitation? This is not explicitly listed in page count table.

Government Response:

Please see the response to question 3.

Question 19:

Does the Government want just 1 (one) CD overall? Or, are we to split off all price / cost volume information onto a separate CD, which means 2 (two) CDs will be provided in the response package? Or, are we required to provide 4 separate CDs, one for each listed volume?

Government Response:

In accordance with Section L, separate CDs should be furnished for each volume for which they are required.

Question 20:

An alphabetical listing of all US BLS SOC codes can be found here: https://www.bls.gov/soc/2010/soc_alph.htm.

The reference URL doesn't work any longer. Are we using 2010 SOC codes or 2018 SOC codes?

2018: https://www.bls.gov/soc/2018/home.htm 2010: https://www.bls.gov/soc/2010/home.htm

Government Response:

Please use the 2018 version.

Question 21:

Table 3.5.2 row 6 identifies Computer Scientist Journeyman and Table 7.6 row 6 identifies Computer Scientist Junior. What is the correct skill level?

Government Response:

Computer Scientist Journeyman. Please note the tables have been updated.

Question 22:

Table 3.5.2 row 9 identifies Informational Management and Technology Analyst Journeyman and Table 7.6 row 9 identifies Informational Management and Technology Analyst Senior. In addition the SOC codes are different. What is the correct skill level and SOC code?

Government Response:

Informational Management and Technology Analyst Journeyman - 15-1212. Please note the tables have been updated.

Question 23:

Table 3.5.2 row 10 specifies SOC code 15-1212 and Table 7.6 specifies SOC code 15-1221. Which is correct? What is the correct SOC code?

Government Response:

15-1221. Please note the tables have been updated.

Question 24:

Table 3.5.2 row 11 identifies Test Engineer Journeyman and Table 7.6 identifies Test Engineer Senior. What is the correct skill level?

Government Response:

Test Engineer Journeyman. Please note the tables have been updated.

Question 25:

Table 3.5.2 rows 12 and 13 identify Systems Specialist Senior and Financial Manager Senior that are not represented in Table 7.6 Should there be entries for these positions in table 7.6?

Government Response:

The Systems Specialist Senior position has been consolidated to a single category with 57,600 total hours. There are two Financial Manager positions (Senior and Junior). Please note the tables have been updated.

Question 26:

Table 3.5.2 row 16 identifies Data Management Specialist Journeyman and Table 7.6 row 14 identifies Data Management Specialist Junior. What is the correct skill level?

Government Response:

Management Specialist Journeyman. Please note the tables have been updated.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

Statement of Work Avionics, Sensors, & E*Warfare Department Mission Data/Information Division, Tactical Aircraft Electronic Warfare Integrated Product Team, United States Reprogramming Laboratory, FMS Reprogramming Laboratory & Rapid Response Project Office 3/26/2017

1.0 Introduction

1.1 The requirements of this Statement of Work (SOW) describe the project management and engineering support required to provide the Navy and Marine Corps land, sea, and air platforms with a responsive, efficient, and reliable means to collect, detect, assess, identify, exploit, neutralize, and disseminate products to the U.S. and its interests. This requirement is designed to support the execution of systems engineering support to meet current and future Electronic Warfare (EW) Mission Information Engineering (MIE) capabilities and security protection needs for Mission Data/Information Engineering Division, Airborne Electronic Attack (AEA) Integrated Product Team (IPT) , Naval Mission Planning Systems (NavMPS) IPT, Sea Hawk Eye Emitter Library Development (SHEELD), EW Data Systems (EWDS)/ EW Tactical Information and Report Management System (ETIRMS), Tactical Aircraft (TACAIR) EW IPT, United States Reprogramming Laboratory (USRL), and Rapid Response Project Office (RRPO). These programs support manned and unmanned platforms EW MIE and mission information system areas and require continuous improvement and upgrade.

1.1.1 The objective of this effort is to support mission information system technology and information technologies advanced concept development and the analysis, testing, development, and integration of equipment, operations, and training for all aspects of support.

1.2 Scope

The scope of this acquisition is to provide: planning, research, analysis, material, prototyping, proof of concept demonstrations, system and software engineering and integration, system testing and evaluation, system deployment, system security, and system training support to Mission Data/Information Engineering Division, AEA IPT, NavMPS IPT, SHEELD, EWDS/ETIRMS, TACAIR EW IPT, USRL, and RRPO.

1.3 Project Background

Mission Data/Information requirements are received weekly and sometimes daily based on emerging threats and operations. Related tasking rapidly change due to evolving threats and constant changes in mission data needed to respond to threats and regions. Required response time could be days to weeks in addition to regular data/payload shipments. During normal fleet operation, the contractor will follow project schedule, which is published/updated on a regular basis. If it is rapid response work, contractor will be immediately contacted and rapid response work will be given the highest priority. A monthly mission data file release schedule is maintained and revised by the Government as required. It is disseminated through regularly scheduled team meetings and the Government’s project development process. Prioritization on tasking will be governed by program and fleet operations. Due to response time for mission data. the laboratories must be available and updated continuously. Multiple electronic warfare platforms require similar data, but in different formats and interactions.

The Contractor will have access to the Government provided Sensitive Compartment Information Facility (SCIF), as requested, to support projects assembling Information Technology (IT) prototypes. Contractor provided SCIF facilities are not required.

The Contractor will have access to Government laboratories as required.

Contractors shall be required to follow Department of Defense (DoD) and DoD component regulations, instructions, policies and Standard Operating Procedures (SOP) when providing project support.

2.0 Applicable Documents

2.1

2.2

NWP 3-22.5-EA6B (EA-6B Tactical Manual (TACMAN))

Defense Information Infrastructure - Common Operating Environment (DII-COE) Specifications Ver 3.3

Mission Planning User's Manual (Ver 1.0)

Mission Planning On-Line Help (Ver 1.0)

Joint Mission Planning System (JMPS) Developer's Handbook Ver 1.2.4/1.3.5

Mission Planning Functional Requirements Document (Ver 1.0)

Mission Planning Database Design Document (Ver 1.0)

Mission Planning Software Development Plans (SDPs) (Ver 1.0)

Mission Planning System/Segment Specification (SSS) (Ver 1.0)

Mission Planning Software Requirement Specifications (SRS) (Ver 1.0)

Mission Planning Configuration Management Plan (CMP-0601)

AEA SSA's Software Change Procedures Guide (SCPG)

Mission Planning Software Coding Standards (Ver 1.0)

DoD-STD-2167A, Defense System Software Development

MIL-STD-1679A, Software Development

MIL-STD-498, Software Development and Documentation (still valid for legacy systems)

IEEE/EIA-12207, Software Life Cycle Processes

Lockheed Martin System Integration (LMSI) Emitter Definition File (EDF) User’s Manual (264A502-00 Rev 6)

LMSI Baseline Scan Tune (BST) User’s Manual (266A921-04 Rev B)

2.3 Industry Standards

The Government will provide all necessary reference documents not generally available to the contractor as required. Throughout the life of the contract, if any instruction or document is replaced or superseded, the replacement or superseding instruction or document shall be applicable to the requirements defined in this SOW.

3.0 Requirements

All requirements are as directed at the task order level.

3.1 Program Management Support

3.1.1 The Contractor shall provide program management support under this contract. Tasking shall include: management and oversight of all activities performed by Contractor personnel, including subcontractors, to satisfy the requirements identified in this SOW. The Contractor shall identify, by name, a Program Manager (PM). The PM shall provide management, direction, administration, quality control, and leadership of the contractor personnel and contract tasks. Contract tasking will be initiated as a result of the Mission Data/Information that is briefed weekly or daily depending on rapid response needs. Specific tasking will be identified at the order level.

3.1.2 The Contractor shall prepare and deliver a monthly Progress, Status, and Management Report (CDRL A001) and a Funds and Man-Hour Expenditure Report (CDRL A002). The reports shall include the following:

a. Activities performed during the reporting period, by project (include: on-going activities, new activities, activities completed; progress to date on all above mentioned activities). Each section of the report shall begin with a brief description of the project.

b. Problems and corrective actions taken. The report shall also include issues or concerns and proposed resolutions to address them.

c. Personnel gains, losses, and status

d. Government actions required.

e. Schedule (identify major tasks, milestones, and deliverables; planned and actual start and completion dates for each).

f. Summary of trips taken, conferences attended (Trip Reports shall be attached to the report for the current period).

g. Current period and cumulative invoiced cost. Costs shall be segregated at the lowest level of performance, Sub Line Item Number (SLIN), rather than on a total contract basis. Supporting documentation shall include costs by individual labor categories, burdened rates, and hours (both straight time and overtime) as well as a cost breakdown of Other Direct Costs (ODCs), materials, and travel.

h. For other than firm fixed price subcontractors, the Contractor shall provide subcontractor incurred costs relating to labor categories, burdened rates, and hours (both straight time and overtime) invoiced as well as a cost breakdown of ODCs, materials, and travel invoiced.

i. Estimated cost of each CLIN for the current month’s tasking.

3.1.3 The Contractor shall document all support requirements in a Program Management Plan (PMP) (CDRL A008).

The PMP shall:

a. Describe the proposed management approach.

b. Contain detailed SOPs for all tasks.

c. Include milestones, tasks, and subtasks required in this contract.

3.1.3.1 The Contractor shall provide the Government with a draft PMP, on which the Government will make comments. The final PMP shall incorporate the Government’s comments. The PMP shall be updated annually, with implemented changes reported each month in the monthly Progress, Status, and Management Report (CDRL A001). The Contractor shall work from the latest Government-approved version of the PMP. During normal fleet operation, the contractor will follow project schedule, which is published/updated on a regular basis. Rapid response work will be identified through the helpdesk. A Heat Ticket will be issued, and work will be re-prioritized in response to the Heat Ticket.

3.1.4 The Contractor shall prepare trip reports within five (5) days after trip completion (CDRL A004). The Contractor shall keep a summary of all travel including the name of the employee, location of travel, duration of trip, and Point of Contact (POC) at the travel location.

3.1.5 The Contractor shall periodically update the Quality Control Plan (QCP) as changes in program processes are identified (CDRL A00D).

3.1.6 The Contractor shall utilize an overarching Summary Dashboard that provides details about each of the Contractor’s projects to include customer name, customer POC, task name, abbreviated work description, start date, end date, adjusted end date, amount funded, amount invoiced, burn rate, and other pertinent information. This Summary Dashboard shall be available only to Electronic Warfare Integrated Laboratories Division (EWIL), TACAIR EW IPT, USRL, and RRPO and the Contracting Officer (KO) and Contracting Officer’s Representative (COR).

3.1.6.1 In addition, the data that feeds the Summary Dashboard shall be maintained at the project level as Individual Dashboards. Individual Project Dashboards shall be available only to the Project stakeholder, EWIL, TACAIR EW IPT, USRL, and RRPO, and the KO and COR.

3.1.6.2 Deliverables shall be identified in the Summary Dashboard and Individual Project Dashboards for each project. Individual Dashboards shall be updated monthly.

3.1.7 The Contractor shall attend Government-led engineering, test, and technical reviews, meetings, and test events for the purpose of gathering data required to develop and deliver the efforts as stated herein (CDRL A005 and A006).

3.1.8 The Contractor shall provide presentation materials, including viewgraphs, slides, videotape, and printed media in the form of reports, instructions, and other materials. Prepare plans, milestone charts, reviews, analyses, evaluations, and recommendations, which will provide the technical and scientific evidence necessary to facilitate program development decisions. Planning inputs shall allow the Government to make the technical, budgetary, and programmatic decisions necessary for program implementation and fielding of systems and equipment (CDRL A007).

3.2 Project Support

This contract will consist of multiple projects. Each project will require project management support and the development, engineering, and integration of a deliverable, usually in the form of a prototype, involving the collection, process, and exploitation, and dissemination of operational requirements.

3.2.1 The Contractor shall provide project management support for Mission Data Information Engineering Division, AEA IPT, NavMPS IPT, SHEELD, EWDS/ETIRMS, TACAIR EW IPT, USRL, and RRPO customers.

3.2.2 The Contractor shall evaluate and execute customer requirements through a formal project management process. The Contractor shall support project planning by providing analysis related to project specifications, project structures, resource allocation, project forecasting (to include rough orders of magnitude) and project control. The Contractor shall work as part of a Government/Contractor integrated project team.

3.2.2.1 The Contractor shall:

a. Develop an Implementation Plan to be added to the Project Management Plan (CDRL A00C). The format of the plan shall be approved by the Government.

b. Provide support for project closeouts by assisting in conducting formal acceptance tests based on the success criteria defined in the implementation plan for the project. The COR shall sign-off on the acceptance. The format of acceptance tests will be approved by the Government (CDRL A00A).

3.2.3 The Contractor shall develop, engineer, and integrate deliverables to meet project requirements. The Government will use the deliverable for the purpose of collection, processing, exploitation, and dissemination of mission information system data.

The Contractor shall:

a. Implement advanced systems to improve data communication. Integrate information from single or multiple sources with related information to enable the Government or Contractor to evaluate the integrity of the information. Implement advanced information systems to aid quick dissemination of critical information.

b. Update and deliver technical documentation to reflect the modernized equipment configuration. This documentation shall include updating engineering drawings, provisioning documentation, software documentation, and technical instructions. Develop documentation supporting analysis verification and validation.

c. Develop test reports that describe the analysis and evaluation of the test results.

d. Develop the mission information systems to include unique subsystem components that could include devices associated with detection, characterization, and classification of mission information systems using radiation, acoustic, optical, or other types of scientific sensors.

e. Develop multiple rapid reaction technologies Concept of Operations (CONOPS) and technical approaches that will be evaluated by the Government for operational testing (CDRL A00E). CONOPS shall address specific requirements, specifications, Government Furnished Equipment (GFE), Contractor Furnished Equipment (CFE), Government Off-The-Shelf (GOTS) software, Commercial Off-The-Shelf (COTS) software, and locally fabricated integration components.

f. Develop technical performance and evaluation plans to support rapid insertion of one or more capabilities into an operational environment.

g. For each approved CONOPS, the Contractor shall identify, coordinate, and position resources during development and testing to satisfy intelligence requirements. Once data is verified and validated by the Government, the Contractor shall develop and manage a collection plan that integrates requirements with target characteristics.

h. Design and modify sensor data fusion software. All Information Technology (IT) Systems or software/application development, modification or support shall be performed in accordance with Defense Business Transformation guidance (formerly BMMP), NAVAIR FAM Policies and Guidance, Network and Server Registration, and Web Enablement mandates. (CDRL A009). This software is used to create database applications, as well as accommodate computer hardware and operating system changes. The software supports database management software, data analysis software, and database content exchange between systems.

i. The Contractor shall also support the development of a collection plan for use in the development of CONOPS and testing of prototypes, to optimize the effective and efficient use of available, capable, and suitable Government and Contractor collection assets and resources.

j. The Contractor shall provide development, engineering, and integration to enable the Government to transform that data into information that can be readily disseminated and used, transmitted, and exploited by Government and Contractor analysts.

3.3 Research and Analysis Support

3.3.1 The Contractor shall provide research and analysis support to include characterizing, demonstrating, and evaluating emerging mission information system technologies by developing custom identification, collection, interpretation, and evaluation systems necessary to assess systems in areas such as Cloud, Big Data, mobility and processing/exploitation/dissemination. The Contractor shall provide support for performance of assessments to support the identification, development, implementation, and enhancements of mission information systems or sub-systems proposed or in development to improve Navy and Marine Corps mission capabilities and operations. This task shall include research, analysis, design, development, coding, integration, and test.

The Contractor shall:

a. Analyze and provide recommendations on the design and development of IT-based mission information systems.

b. Provide analysis, recommendations, and solutions for Big Data and cloud system technology insertion initiatives, including transfer and transition of existing and emerging technologies to improve EW and mission information system performance.

c. Provide systems engineering and integration on mission information systems and other initiatives, including development of systematic situation analyses, trade-off analyses, problem and potential problem analyses, decision analyses, risk analyses, tactics analyses, mission analyses, and strategy analyses associated with systems engineering and integration.

d. Provide human systems integration analysis and design solutions for mission information systems.

e. Research, analyze, design, develop, fabricate, integrate, test, deliver, and install IT-based test capability software. All Information Technology (IT) Systems or software/application development, modification or support shall be performed in accordance with Defense Business Transformation guidance (formerly BMMP), NAVAIR FAM Policies and Guidance, Network and Server Registration, and Web Enablement mandates Analyze system support requirements and provide a report to the Government that documents that analysis and findings.

f. Provide analysis and recommendations to the Government on COTS and GOTS hardware and software effectiveness.

g. Research and analyze software anomalies and update, integrate, test, and deliver software corrections so that legacy IT-based capabilities are not degraded.

h. Ensure that the current software is capable of functioning with legacy capabilities currently possessed by the Government.

i. Provide research and analysis to execute development of mission information system technologies directly responsive to special warfare related mission information system requirements.

j. Conduct research and analysis of current and future mission information system capabilities, requirements, deployments, and integration; mission information system advanced concepts and technologies; system and subsystem platform integration; application of applied physics; analysis of electrical designs; analysis of mechanical concepts; analysis of acoustic noise and sonar systems; analysis of illumination, detection, characterization, and classification of targets.

k. Conduct research and analysis to develop IT-based mission information system, subsystems, associated equipment, and programs.

l. Conduct data analysis and provide technical recommendations for the enhancement of strategic concept development.

m. Identify, exploit, and manipulate current and emerging technologies, including services oriented architecture, advanced visualization, data science and analytics.

3.3.2 The Contractor shall receive requirements as part of planned product changes resulting from Engineering Change Proposals (ECPs), prioritized System Trouble Reports (STR), and Engineering Review Boards (ERBs).

3.3.3 The Contractor shall create draft Functional Requirements Documents (FRDs) for required projects and route the document to the Government for update and review.

3.3.4 The Contractor shall create a draft Requirements Traceability Matrix (RTM) from the requirements database and FRD. The RTM shall be routed to systems engineers, test lead, and project manager for review.

3.3.5 The Contractor shall perform requirements analysis across systems and projects preparing data flow diagrams depicting the data and information that will be required by project with its source, and documenting the interdependencies between systems. The Contractor shall initiate reviews of the data flow and interdependencies with assigned systems engineers, test leads, and project managers.

3.3.6 The Contractor shall perform trade studies and provide recommendations for requirements tool implementations for use with programs.

3.4 Information Assurance

3.4.1 The Contractor shall support all information assurance officer responsibilities in accordance with JAFAN 6/3 and ICD 503- Intelligence Community Information Technology systems security: Risk management certification and accreditation, and provide Information Assurance (IA) assistance to units involved in classified activities, establish and maintain accreditation for all information systems operating within a classified environment, and develop and maintain system security plans outlining security operating procedures (CDRL A00F).

The Contractor shall:

a. The Contractor shall perform day-to-day monitoring of network security events, monitor, and maintain, security configuration settings and system modifications to ensure compliance with Information Assurance Vulnerability Alert (IAVA) mitigation actions, Security Technical Implementation Guide (STIG) guidance and assist in the transition from DIACAP to Risk Management Framework (DI-MISC-80508B) and (DI-MGMT-80227 and D001) and (DI-IPSC-81442A).

b. Assist the unit information assurance manager in developing sanitation and secure data extraction programs for all media, security incident cleanup plans, system certification testing plans, vulnerability testing, and protection measure procedures.

c. Maintain continuous control and accountability of all IT hardware and software entered into and removed from classified facilities at NAWCWD laboratories and contractor facilities supporting this contract.

d. Perform initial and recurring security training for all personnel afforded access to any information systems in accordance with Government security policy and procedures.

e. Identify requirements related to fielding and supporting encryption and cryptologic equipment/keys for classified networks.

f. Provide day-to-day security management and oversight for classified activities, including sensitive documents, data, and equipment according to Gov SOPs.

g. Manage the use, processing, and disposition of sensitive items. according to Gov SOPs.

h. Operate under applicable DoD cyber security policies and standards.

3.5 Engineering Support

3.5.1 The Contractor shall provide engineering support for fielding, operation, and sustainment of new, existing, and prototype systems for EW mission information engineering including sensor engineering, mission data files, and EW threat analysis, on both manned and unmanned platforms at the Weapons Division including: Airborne Turret Infrared Measurement System (ATIMS); NavMPS core, Joint Mission Planning System (JMPS) Framework, and Unique Planning Components (UPCs); ETIRMS; SHEELD; EWDS; Joint Threat Analysis Common Component (JTACC); Tactical Information System (TIS), and Tactical Aircraft Moving Map Capability (TAMMAC), and the laboratories and infrastructure supporting those projects. Elements of this task shall include:

a. Provide software development to include new requirements, changes to existing requirements, and correction of deficiencies (CDRL A009). The Contractor shall perform design, development, integration, test, evaluation, and documentation of software and firmware for sensor engineering, EW threat analysis, and mission data files development, deployment, and maintenance.

b. Provide sensor engineering to include fusion of EW data from national intel data sources, including Electronic Warfare Integrated Reprogramming (EWIR) Database, and Combined Intelligence Database (CID), into platform-specific sensor format to optimize the mission data libraries.

c. Provide EW threat analysis to include development of threat characteristics and performance, Electronic Intelligence (ELINT), and data fusion parameters

d. Provide mission data files that produce flight plans to include the flight path, the best method to identify and detect EW threats, and application of kinetic or non-kinetic effects.

e. Support exercises, fielding, and test events of new, existing, and prototype systems in required locations for sensor engineering, EW threat analysis, and mission data files development, deployment, and maintenance. Tasking to include operating the system, test preparations, data output analysis and storage, and experiments to assess impact of new systems and the transition of new technologies into current systems

f. Provide continuous performance assessment of operational systems and make recommendations for continued improvements and upgrades for mission information engineering

g. Provide mission information engineering expertise at technical interchange meetings (TIMs) (CDRL A005 and A006).

h. Analyze, evaluate, troubleshoot, recommend, and incorporate corrective actions for identified deficiencies in laboratory and operational systems for sensor engineering, EW threat analysis, and mission data files development, deployment, and maintenance.

i. Provide integration management so that software updates on one system will be updated throughout all affected systems.

j. Install IT prototypes in host platforms. An IT prototype could be installed on a rack, in a building, on an airplane, on a boat, in a motor vehicle, or in a stationary bunker. The Contractor shall be responsible for the Operation and Maintenance (O&M) of the IT prototype as well as the IT prototype host platform.

3.6 Training Support

3.6.1 The Contractor shall coordinate and provide training for demonstrations, exercises, operational systems training and mission training. Operational systems training shall address operator and maintainer interfaces with the system, including normal and degraded modes of operation. Mission training shall include the operating environment, threats, political concerns, and special operating considerations. The Contractor shall develop and present formal and informal training material that describes the functional and operational aspects of the mission planning software as well as key software development capabilities such as compiling of source code, development and testing of mission data files (including those applicable to various EW systems including towed decoys), and support of deployable systems and methods including manned and unmanned platforms (CDRL A00G).

The Contractor shall:

a. Provide systems familiarization training, on a bi-annual basis, in both a classroom environment and field environment that will enable users to operate the hardware and software delivered.

b. Develop and provide applicable manuals related to the training (CDRL A00G).

c. Deliver classroom, on-the-job, and distance learning training both inside the continental United States (CONUS) and outside the continental United States (OCONUS), at both Government and Contractor sites.

3.7 Lab Maintenance and Modernization

3.7.1 The Contractor shall:

a. The contractor shall design, obtain, install, configure, and maintain hardware and software for the IT systems, subsystems and associated equipment to meet contract requirement.

b. The contractor as directed at the task order level shall design, obtain, install, configure, and maintain shielding (preventing Radio Frequencies (RF) and sound from entering and leaving secure areas), security systems, laboratory flooring, laboratory chairs, workbenches, equipment racks, wall coverings, cooling and heating as required to maintain the lab environment.

c. The contractor shall obtain, install, configure, calibrate, and maintain measuring equipment.

4.0 Deliverables

All data deliverables under this contract shall be in accordance with the Attachment DD Form 1423s.

Transition-In Plan (CDRL A00H) Transition-Out Plan (CDRL A00J)

5.0 Government Furnished Items

Currently there is no GFE identified for this contract. The Contractor shall provide a GFE Report for each piece of GFE that is required in support of the contract. Report shall include cover sheet to identify Contract, Task Order, and CDRL number (CDRL A00B).

5.1 Government Furnished Equipment

The Government will furnish access to laboratories and facilities on an as-needed basis during normal operating hours. The Contractor shall provide a list of personnel with the “need to know” for access to Government spaces (CDRL A003). Contractor personnel performing these tasks will require access to classified facilities and must have appropriate clearances on file with the NAWCWD Security Office. The Government reserves the right to control the laboratory and facility schedules and the use of documentation required for performance of this contract.

5.2 Government Furnished Information

The Contractor shall receive and maintain custody of any Government Furnished Information (GFI) provided during the course of the performance of this effort. The Government will provide all applicable technical documentation, procedures, and information as required for completion of the contract.

5.3 Government Furnished Facilities

The Government shall determine facility requirements and locations for meetings and program reviews, as well as suitable infrastructure to manage program requirements to support the scope of activities.

The Contractor will be authorized access to Naval Air Warfare Center Weapons Division (NAWCWD) Navy Marine Corps Intranet (NMCI) owned/Government owned equipment, which shall be utilized during the performance of tasks stated in Section 3.0 of this contract.

6.0 Special Conditions

6.1 Place of Performance

6.1.1 Contractor’s Facility and Government Facilities at Point Mugu, CA; China Lake, CA; San Diego, CA; Owego, NY; Eglin Air Force Base, FL; Jacksonville, FL, Patuxent River, MD; and Whidbey Island, WA.

6.2 Travel

6.2.1 The Contractor may be required to travel throughout the CONUS and to locations OCONUS. If travel, domestic or overseas, is required, the Contractor shall be responsible for making all needed arrangements for personnel. This includes, but is not limited to, medical examinations, immunizations, passports, visas, and security clearances.

6.2.2 All travel shall be in accordance with the Government’s Joint Travel Regulations (JTR). Before undertaking any travel to any site in performance of this contract, the Contractor shall have this travel approved by, and coordinated with, the COR.

6.2.3 The Contractor shall submit a trip report to the COR and technical points of contact for all travel performed, no later than five (5) days after completion of the trip (CDRL A004).

6.3 Security

6.3.1 Performance on this contract will require Contractor employees to have access to classified information up to and including Top Secret (TS)/ Sensitive Compartmented Information (SCI) and Special Access Program (SAP) level. Secret clearances will be required of all personnel within 60 days of contract award. TS clearanes will be identified upon need at the Task Order level. The work to be performed under this contract as delineated in the attached DD Form 254 involves access to, handling of, and generation of classified material up to and including TS/SCI and SAP. The Contractor shall appoint a Security Officer who shall (1) be responsible for all security aspects of the work performed under this contract, (2) assure compliance with all DoD and Service regulations regarding security, and (3) assure compliance with any written instructions from the Security Officers of each Government facility. In the event that any individual tasking requires a higher level of clearance, a separate DD Form 254 will be prepared and issued. The Contractor may be required to have access to live data during the performance of this contract. Any records and data or information the Contractor may have access to may be highly sensitive and confidential. The Contractor must not divulge any information about files, data processing activities or functions, user IDs or passwords or any other knowledge that may be gained to anyone not authorized to have access to such information. It is the Contractor’s responsibility to ensure that all required employees have proper authority. All classified material shall be processed and protected in accordance with the provisions of this contract and all required instructions and directives in effect concerning the processing of classified material.

6.3.2 The Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified and classified information in accordance with the National Industrial Security Program Operating Manual (NISPOM) and DoDM 5200.01, Information Security Program: Controlled Unclassified Information (CUI) Volume 4 (enclosure 3) and DoD 5400.7-R (Freedom of information Act Regulation) (Chapter 3). All Contractor facilities shall provide an appropriate means of storage for controlled unclassified and classified documents, equipment, and materials in accordance with Operations Security (OPSEC) requirements.

6.3.3 For Official Use Only Information generated and provided under this contract shall be marked and safeguarded as specified in DoDM 5200.01 (DoD Information Security Program: Controlled Unclassified Information (CUI) Vol. 4 (enclosure 3 page 11-17) available at:

http://www.dtic.mil/whs/directives/corres/pdf/520001_vol4.pdf

DoD 5400.7-R. Freedom of Information Program Chapter 3 (pages 31-42) available at:

http://www.dtic.mil/whs/directives/corres/pdf/540007r.pdf

6.3.4 Distribution Statement -- All controlled unclassified technical information shall be appropriately identified and marked with the distribution statement identified on the source document.

6.3.5 The Contractor shall not disclose any information provided or developed under this contract outside the Government without prior approval from the Government. Contractor shall provide one (1) copy of each employee-signed Non-Disclosure Statement to the COR prior to performing any work on this contract. The COR will retain one (1) copy for the contract file.

6.3.6 All persons engaged in work while on Government property shall be subject to search of their persons (no bodily search) and vehicles at any time by the Government, and shall report any known or suspected security violations to the NAWCWD Pt. Mugu security department. Assignment, transfer, and reassignment of Contractor personnel shall be at the discretion of the Contractor; however, when the Government directs shall remove from contract performance any person who endangers life, property, or national security through improper conduct. Prior to conducting work under this contract, the Contractor shall provide a list of employees that will be working on site (CDRL A003). The employee list shall contain full names, customer supported, security clearance levels, and labor categories. This list shall be updated within forty-eight (48) hours after changes occur.

6.4 Transition-In

6.4.1 The Contractor shall ensure that there will be minimum service disruption to vital Government business and no service degradation during and after transition. All transition activities and 100% of Contractor support shall be completed within thirty (30) calendar days after the start date of the contract. All key personnel are required at the start of the contract. The Contractor shall submit a draft Transition-In Plan with its proposal and at the Contract Kick-Off Meeting. The draft Transition-in Plan is subject to changes pending Government comments and recommendations after the kick-off meeting. The final Transition-In Plan shall be approved by the COR. (CDRL A00H)

6.4.2 The phase-in activities shall include such functions as:

a. Transfer of knowledge, experience, and lessons learned to the new Contractor.

b. Assist in startup to include identification of incumbent workforce and prioritized onboarding of staff to ensure no service disruption and a smooth transition.

c. Transfer appropriate property, documentation, or personnel, as agreed to between the parties (including but not limited to, devices, equipment, databases, and systems related to this SOW).

d. Attend program reviews and participate in working groups and briefings.

6.4.3 The Transition-In Plan shall, at minimum, address the above phase-in activities. The plan shall also include a training program for Contractor personnel and a date for accepting responsibilities for each division of work described in the Transition-In Plan.