SW Eng Dept Draft SOW.pdf

DRAFT

STATEMENT OF WORK (SOW) for

THE SOFTWARE ENGINEERING DEPARTMENT SERVICES

FOLLOW-ON CONTRACT

1.0 Scope:

This Statement of Work (SOW) defines the scope required in support of Software Engineering

Department and Naval Air Systems Command (NAVAIR) Program Management Administration

(PMA) for the following activities: Software Systems Engineering, Systems and Software

Integration and Software Development, Test, Software Acquisition, Integration and Laboratory

Engineering, Systems/Subsystems Integration, Avionics/Software/Air Vehicle Technology

Insertion, Platform Simulation, Configuration Management, and Program Performance

Assessment Analysis and Planning. This includes direct Software systems engineering support services throughout the full life cycle of a weapon system from concept development through disposal, and applied to Naval Aircraft weapons and support systems. This effort shall apply to

U.S. domestic military programs and Foreign Military Sales (FMS) programs.

This SOW further defines the requirement for the development and integration of aircraft systems, mission systems, and support systems including Software and mission system and laboratory hardware. The scope will include Software program generation and Software and hardware integration, along with the development of test devices and systems which support system test and integration such as weapon system simulators and trainers. Such test devices and systems may include non-intrusive hardware/interface monitoring devices and the

Software/systems that analyze the data extracted/generated.

This SOW addresses all functional areas for the development of operational systems requirements and integration, which includes conducting operational and functional systems testing and fleet introduction. The overarching areas of support consist of product development that includes hardware, firmware, trade analysis documentation, cost reporting, financial tracking, test plans, test procedure documentation, test report documentation, training materials including computer-based training as well as training documentation, operator user guides and operational concept documentation.

This effort includes Software test and evaluation to determine specification compliance, performance compliance, operational effectiveness, and for the suitability of Software and hardware for fleet introduction, as well as, the ability of that Software to be inter-operable with other Navy platforms. In addition, the government requires recommendations for hardware design where such design affects the human-machine interface of the system. Required reporting and analysis support services will include trade-off analysis reports, analysis reports of system design, test procedures to validate specification compliance and performance compliance, operational usability reports, interoperability reports to include conducting actual operational analysis in the laboratory or aircraft environment.

The fleet introduction, as defined in this contract, supports the initial introduction of a new system or system program configuration. This effort shall include training the test community, the training community, providing initial fleet orientation, as well as providing training materials to these communities.

Support services required for continuous operation of the Software Support Activity (SSA)

Software production facilities (SPF). SSA SPF’s provides complete lifecycle services for the

Navy platforms. In addition to supporting the development of future mission critical Software programs, these facilities provide Software sustainment and development environments offering specialized tools, archival processes, full back up capability, and disaster recovery. Services provided shall include hardware analysis, engineering, mission Software programming, Simulation/Stimulation programming, web application development and website maintenance, documentation configuration management, Software configuration management and library services.

Support Services under this SOW are required for the Program Executive Offices (PEOs), NAVAIR, Mission Aligned Organizations (MAOs), and other agencies listed below:

PEO(T) TACTICAL AIRCRAFT PROGRAMS

PEO(A) AIR ASW, ASSAULT, and SPECIAL MISSION PROGRAMS

PEO(U&W) UNMANNED AVAITION and STRIKE WEAPONS

PEO(JSF) JOINT STRIKE FIGHTER

PEO(CS), COMMON SYSTEMS

AIRCRAFT SYSTEMS GROUP

DAiTA GROUP

MISSION SYSTEMS GROUP

FOREIGN MILITARY SERVICES

OTHER U.S. GOVERNMENT AGENCIES (FEDERAL)

2.0 Applicable documents:

The Government will provide the Contractor copies of, or access to, any relevant DoD

Instructions, directives, policies, procedures and guidelines, as well as, Software Engineering

Standard Work Packages (SWPs) necessary to perform tasking during contract performance in support of individual task orders.

A comprehensive list of Navy regulatory documents can be found at the Department of the Navy

(DON) Chief Information Officer (CIO) Information Technology (IT) Policy and Guidance website, http://www.doncio.navy.mil/. Throughout the life of this contract, if any policy, instruction, or regulation is replaced or superseded, the replacement or superseding version shall apply. The Contractor is responsible for adhering to all regulations applicable under this contract and resulting awarded task orders. A list of applicable documents are listed below, but are not limited to:

2.1 Department of Defense specifications:

Updated DoD Cybersecurity Policies are available in the following link:

https://www.csiac.org/resources/the-dod-cybersecurity-policy-chart/

2.1.1 DoD 5220.22-M, National Industrial Security Program Operating Manual, (NISPOM) 28

Feb 2006

2.1.2 DON letter 5239 NAVAIR 726/2322 of 18 Feb 09, NAVAIR Data at Rest Policy

2.1.3 DoDM 5200.01 (DoD Information Security Program: Controlled Unclassified Information

(CUI)) Vol. 4 (enclosure 3 pages 11-18) 24 Feb 2012

2.1.4 DoD 5400.7-R, Freedom of Information Program Chapter 3 (pages 31-42) Sep 1998

2.1.5 DoDD 5230.24 Distribution Statements on Technical Documents, Change 1, Effective 28

Apr 2016

2.1.6 DoD Directive Number 8500.01E Information Assurance (IA)

2.1.7 DoD 8570.01-M, Information Assurance Workforce Improvement Program, 19 Dec 2005

(Incorporating Change 3, 24 Jan 2012)

2.1.8 DoD Contract Security Classification Specification, DD Form 254

2.1.9 SECNAV M-5510.30 Personnel Security Program Jun 2006

2.1.10 SECNAVINST 5239.3B DON Information Assurance Policy, 17 JUN 2009

2.1.11 SECNAV M-5239.1, DON Information Assurance Manual

2.1.12 SECNAVINST 5510.36A DoN Information Security Program Instruction

2.1.13 SECNAVINST 5720.42F DoN Freedom of Information Act (FOIA) Program

2.1.14 OPNAVINST 3440.17A Navy Installation Emergency Management Program, 1 Aug 2014

2.1.15 OPNAVINST 3140.24F Adverse and Severe Weather Warnings and Conditions of

Readiness

2.1.16 OPNAVINST 3432.1A Operations Security

2.1.17 NASPAXRIVINST 3140.6P Destructive Weather Preparedness and Response Plan

2.1.18 NASPAXRIVINST 12610.7H Employee Reporting Procedures During Emergency

Situations (December 2016)

2.1.19 Procedures, Guidance and Information (PGI), DFARS PGI 204.73, Safeguarding Covered

Defense Information and Cyber Incident Reporting, December 1, 2017

2.1.20 DON CIO Memo 02-10, "Department of the Navy Chief Information Officer

Memorandum 02-10 Information Assurance Policy Update for Platform Information

Technology," 26 April 2010

2.1.21 DoDI 8500.2, "Information Assurance Implementation," February 6, 2003

2.1.22 DoDI 8510.01, "DoD Information Assurance Certification and Accreditation Process

(DIACAP)," November 28, 2007

2.1.23 DoDI 8520.2, "Public Key Infrastructure (PKI) and Public Key (PK) Enabling, April 1,

2.1.24 DoDI 8551.1, "Ports, Protocols, and Services Management (PPSM)," August 13, 2004

2.1.25 DoDI 8580.1, "Information Assurance in the Defense Acquisition System," July 9, 2004

2.1.26 DoDI 8581.01, "Information Assurance (IA) Policy for Space Systems Used by the

Department of Defense," June 8, 2010

2.1.27 SECNAVINST 5239.19, "Department of the Navy Computer Network Incident Response and Reporting Requirements," 18 March 2008

2.1.28 The National Security Act of 1947

2.1.29 Title 40/Clinger-Cohen Act2.1.35 Section 508 Amendment to the Rehabilitation Act of

1973 http://www.section508.gov/ https://www.csiac.org/resources/the-dod-cybersecurity-policy-chart/ http://www.section508.gov/

2.1.30 48 CFR 252.204-7012 - Safeguarding covered defense information and cyber incident reporting.

2.2 Department of Defense standards: Not Applicable (N/A)

2.3 Other Government documents: (e.g. NAVAIR Documents):

2.3.1 NAWC Software Engineering SWPs (29; SWP#s including but not limited to: SWP-4940-

001 through SWP-4940-0029)

2.4 Industry documents: Not Applicable (N/A)

2.5 Others if needed: Not Applicable (N/A)

3.0 Requirements

3.1 General Requirements

3.1.1 Compatibility. The Contractor shall maintain the capability to prepare documents and

Software packages compatible with the Government Information Technology (IT) environment through the security classification, specified in the Department of Defense Contract Security

Classification (DD-254), of up to Top Secret. The current operating environment required for this contract includes:

Microsoft Windows 10

Microsoft Project 2016

Microsoft Office Suite 2016 (i.e. Word, Excel, Access, Project and PowerPoint)

Adobe Acrobat XI (reader)

Internet access with Internet Explorer, Google and Firefox web browsers

The Contractor shall maintain the ability to interface with and transfer data to and from requiring office software applications and their upgraded versions. The Contractor shall maintain state-of the-art antivirus software and ensure that all media are virus free when delivered. The

Contractor shall be capable of Internet and LAN communications with the Naval Air Systems

Command (NAVAIR) Software Engineering and Acquisition Management Division. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with NAVAIR Software Engineering and Acquisition Management Division during working hours whether at Contractor work site or on travel.

The contractor shall utilize software tools in generating contracted deliverable items. Delivery tools to include but not limited to: Navy CM suite of tools such as Jenkins, GIT, CM Synergy, ClearCase, ClearQuest, Concurrent Version System (CVS), Change, Synergy and, Programmable

Acoustic Processor Simulator (PAPS).

3.1.2 Work Location and Facilities

3.1.2.1 Work location. The primary place of performance under this contract is Naval Air

Station, Patuxent River, MD (approximately 90%) with a limited amount of support at other enterprise-wide facility locations (approximately 10%), to include but not limited to: North

Island San Diego, CA; Indianapolis, IN; Jacksonville, FL; Whidbey Island, WA; Lakehurst, NJ and Horsham, PA. Approximately 90 percent of work will be performed at the Government site and 10 percent of work to be performed at the Contractor site. Specific performance locations will be included in individual task orders. Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, and network access including web servers and applicable databases or other applications necessary to carry out assigned tasks. Government facilities may be required for the performance of a task order and will be identified in specific orders.

The Contractor shall provide necessary workspaces for proposed off-site support personnel. The

Contractor’s facility shall meet the requirements of the DD Form 254 applicable to this contract.

Additional facility requirements may be addressed in individual task orders.

*On-site work is considered work performed at a Government owned/rented space. Off-site work is work performed at the Contractor’s facility.

3.1.2.2 Meeting support. In support of the tasking outlined in this SOW, the Contractor shall have the capability to host and conduct Unclassified meetings, the capacity minimum of support will be determined at the contract Task Order (TO) level.

3.1.3. Deliverables.

The following CDRL list (DD Form 1423) are required in support of the overarching IDIQ contract and will be deliverable under a specified task order.

Operation Security Plan (OPSEC) – A003

Phase-Out Transition Plan– A007

Non-Disclosure Agreement – Company– A009

Non-Disclosure Agreement – Individual – A010

The following CDRL list (DD Form 1423) to support individual Task Orders. CDRL requirements will be determined at the Task Order level:

Monthly Progress and Financial Status Report A001

Technical Report – A002

Contracting Officer’s Management Report– A004

Presentation Material – A005

Information Technology Personnel Security Report for COR – A006

Training Program Structure Document – A008

The following provides additional details associated to CDRLS A001 through A011 outlined above.

3.1.3.1 Monthly Progress and Financial Status Report. The contractor shall provide a progress and financial status report in accordance with the Contract Data Requirement List

(CDRL) A001, Exhibit A. This report shall include the following information for each applicable

Task Order under this IDIQ contract:

The report shall include work accomplished since submittal of the last report and existing or potential problem areas.

Utilization summary (total number of dollars and hours contracted and expensed monthly and cumulatively)

Labor category hours’ expenditures

Funding summary with percent remaining

Material and travel costs, both monthly and cumulative expenditures

Personnel roster, the contract labor category and number of hours worked for each, the contract labor rate, start and end dates of employment, and other applicable personnel comments/notations deemed necessary.

CDRL deliverables provided during reporting period, and identify and provide status of delinquent CDRL data items.

3.1.3.2 Technical Reports. The Contractor shall deliver technical reports as needed in accordance with CDRL A002, Exhibit A. The report shall include companion executive summary report and briefing. These reports may apply to any section of the SOW requirements in section 3.3.

3.1.3.3 Operations Security Plan. The contractor shall provide an Operations Security

(OPSEC) Plan in accordance with the CDRL A003, Exhibit A. This plan shall address the contractor’s OPSEC activities during the performance of the contract and include: description of the OPSEC environment to include identification of critical information, OPSEC threat and vulnerabilities an adversary might exploit to acquire critical information, document the OPSEC risk analysis, identify proposed and actual OPSEC measures, and define and assign specific

OPSEC responsibilities that are tied to the contractor’s corporate OPSEC Program. The

OPSEC Plan shall serve as a repository of the OPSEC history of the contract.

3.1.3.4 Contracting Officer’s Management Report. In order to support invoice reviews conducted as part of proper surveillance, the contractor shall report incurred cost and progress in accordance with NAVAIR clause 5252.232-9529, “Incurred Cost and Progress Reporting for services,” in CDRL A004, Exhibit A, and the Incurred Cost Reporting Instructions incorporated as Attachment (4).

3.1.3.5 Presentation Material. The contractor shall prepare presentation materials for quarterly program review meetings that shall be used to assess the overall status of the contractual effort.

Reports shall be prepared in accordance with CDRL A005, Exhibit A.

3.1.3.6 Information Technology Personnel Security Report for COR.

The contractor shall provide an Information Technology Personnel Security Report to the COR in accordance with CDRL A006, Exhibit A. The report submitted to the COR shall be sanitized to not contain Social Security information. The report shall show that all contractor personnel meet the requirements for obtaining access to Government IT Systems, and that all requirements are verified and validated thereafter on an annual basis. All prime, subcontractor, consultants, and temporary employees shall be included in the reports. Revised reports shall be submitted when gains and/or losses of employees occur to ensure that all employees comply with these requirements prior to accessing Government IT Systems.

3.1.3.7 Phase-Out Transition Plan.

The contractor shall provide a Phase-Out Transition Plan in accordance with the CDRL A007, Exhibit A and SOW paragraph 3.1.8.

3.1.3.8 Training Program Structure Document.

The contractor shall provide a Training Program Structure Document in accordance with CDRL

A008, Exhibit A. This document shall provide training planning data and training course control data. This information is relative to long-range training program resource requirements, for personnel and equipment, and their implementation. This document details the configuration baseline of a training course.

3.1.3.9 Non-Disclosure Agreement (NDA).

The contractor shall provide Non-Disclosure Agreement in accordance with CDRL A009 and

A010, Exhibit A. Provided when a confidential relationship exists between the parties to protect any type of classified, confidential, or sensitive Government information or data. Provide a signed NDA before disclosure of classified, confidential, or sensitive information or data that is owned or possessed by the Government. This CDRL is applicable when a Government organizational unit enters into a contract, interagency agreement, or other formal relationship where certain information must be disclosed to Contractors for the purpose of this requirement contract.

3.1.3.10 Other Reporting:

The Contractor may be required to provide additional reporting, documentation, and schedules in accordance with deliverable requirements CDRLs incorporated at the task order level.

Reporting shall be in sufficient detail and quality to meet the requirement established in individual task orders, and shall comply with the standards and guidelines in Section 3.0. Other reporting requirements may include, but are not limited to:

Software source code and executables.

Manufacturing drawings, data, lists, procedures, and schematics.

Maintenance requirements, guidelines, schedules, procedures, instructions, and corrective actions.

Agendas, minutes and presentation materials for meetings, presentations, and conferences.

3.1.4 Work Schedule to include Compressed Work Schedule (CWS), overtime, holidays, installation closure, and telework.

3.1.4.1 Work Schedule:

The contractor shall provide the required services and staffing coverage during normal working hours. Normal working hours are usually 8.5 hours (including a 30-minute lunch break), from

0800 to 1630 each Monday through Friday (except on the legal holidays specified in paragraph

3.1.4.1.2). Some supported Government offices have flexibility to start as early as 0600/0630 and end as late as 1800, Monday –Friday.

3.1.4.1.1 Compressed Work Schedule (CWS):

CWS is an alternative work schedule to the traditional five 8.5-hour workdays (which includes a

30-minute lunch) worked per week. Under a CWS schedule, an employee completes the following schedule within a two-week period: eight weekdays are worked at 9.5 hours each

(which includes a 30-minute lunch), one weekday is alternately worked as 8.5 hours (which includes a 30-minute lunch), and one weekday is not worked by the employee. The result is 80 hours worked every two weeks, with 44 work hours one week and 36 work hours the other.

The contractor may allow its employees to work a CWS schedule provided the requirements of this SOW are met. If the contractor chooses to allow its employees to work a CWS schedule in support of this contract, any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this contract and will not be reimbursed by the Government. Additionally, the CWS schedule shall not prevent contractor employees from providing necessary staffing and services coverage as required by the

Government to the contract Task Order (TO) Technical Point of Contact (TPOC). The contract

TO TPOC shall determine if the labor category and associated duties are eligible to utilize the

CWS schedule.

3.1.4.1.2 Holidays:

The Government observes the following holidays:

New Year’s Day, January 1

Martin Luther King’s Birthday, the third Monday in January

President’s Birthday, the third Monday in February

Memorial Day, the last Monday in May

Independence Day, July 4

Labor Day, the first Monday in September

Columbus Day, the second Monday in October

Veteran’s Day, November 11

Thanksgiving Day, the fourth Thursday in November

Christmas Day, December 25

With the exception of the events in section 3.1.4.1.3 below, the contractor is permitted to observe the above Holidays in accordance with its corporate policy.

3.1.4.1.3 Installation Closure:

When Federal facilities are closed by the Government, or when Federal employees are officially excused from work due to a holiday or a special event, severe weather, a security threat, or any other Government facility related problem that prevents Federal personnel from working at the

Government facility, contractor personnel assigned to work at that facility in support of such

Federal employees shall follow their parent company’s policies.

While generally, contractor personnel may not perform work on-site at a Government facility without oversight from Federal personnel, in very limited circumstances, work being performed by contractor personnel may be deemed mission essential and performance of such mission essential work may be authorized to continue at the Government facility despite the facility being otherwise closed for normal operations. The circumstances permitting work being performed by contractor personnel to be deemed mission essential are extremely limited and generally only apply to performance of efforts related to public health, safety, or matters related to national security. The cognizant Contracting Officer must concur with any determination that work being performed by contractor personnel is mission essential. Any mission essential services to be provided will be identified at the Task Order level, if applicable.

3.1.4.1.4 Teleworking:

Telework under this contract may be authorized; however, the contractor must provide their

Telework policy detailing the roles, responsibilities, security, safety, and requirements, for the contractor’s adherence, in coordination with the TPOC and COR. The contractor shall notify the

TPOC and COR for any position for which the contractor proposes a teleworking situation. The contractor notification shall identify the individual’s name, labor category, principal location where telework will occur, communication methods available to reach the contractor during telework hours (email, cell phone, house phone, etc.), the working hours the person shall be in a telework status and available for correspondence, and in-person meetings as needed. The TPOC and COR will determine if the labor category and associated duties can be completed via telework. The Government is not responsible for any operating costs associated with telework by the contractor up to and including maintenance, insurance and/or liabilities.

3.1.4.1.5 Overtime:

Overtime is not authorized on this contract. Overtime cannot be charged directly to the contract unless first approved in writing by the Chief of the Contracting Office in accordance with FAR

22.103 NMCARS 5222.103.

3.1.5 Other Direct Costs (ODCs):

3.1.5.1 Travel:

Travel will be allowable only when it is essential to the performance of the tasks detailed in individual Task Orders. Reimbursement for travel performed shall be in accordance with the

Department of Defense Joint Travel Regulation (JTR)

(http://www.defensetravel.dod.mil/site/travelreg.cfm). The COR shall approve all travel performed in support of this contract. In accordance with NAVAIR Clause 5252.232-9509

Travel Approval and Reimbursement Procedures, travel within a 50-mile radius of the

Contractor’s regular worksite is considered the Contractor’s official station and therefore not subject to reimbursement. Travel may include general and administrative expenses as appropriate, but shall not include profit. Temporary travel to other locations in support of program tasking may be required. Temporary travel locations include CONUS & OCONUS locations, which will be identified in individual task orders. Locations to include but not limited to: Jacksonville, FL; Melbourne, FL; Dallas, TX; Richardson, TX; Ft. Worth, TX; Waco, TX;

Anaheim, CA; Miramar, CA; San Diego, CA; Woodland Hills, CA; Pt. Mugu, CA; Horsham, PA; Seattle, WA; Whidbey Island, WA; Kaneohe Bay, HI; Seattle, WA; Norfolk, VA; Manassas, VA; Long Island, NY; Owego, NY; Greenville, SC; Oklahoma City, OK; United Kingdom;

Atsugi, Japan; Misawa, Japan; El Salvador; Signorelli, Sicily; Egypt; Bahrain; and Djibouti.

http://www.defensetravel.dod.mil/site/travelreg.cfm

Travel authorization requests shall be submitted for TPOC approval 30 days in advance of required travel, when possible, but no less than 15 business days prior to travel, TPOC approvals shall be routed to the COR for approval prior to traveling. Contractor required access to

Government-owned facilities will be authorized with the proper clearances and visit requests.

The contractor shall provide all necessary information, as required, to support such clearances and visit requests.

3.1.5.1.1 OCONUS Passports, Visas and Customs: The contractor shall be responsible for obtaining all passports, visas, or other documents necessary to enter and/or exit any areas(s) identified by the contracting officer for contractor employees. All contractor employees shall be subject to the customs, processing procedures, laws, agreements, and duties of the country to which they are deploying, and subject to the procedures, laws, and duties of the United States upon re-entry. Contractors are required to register all personnel with the appropriate U.S.

Embassy or Consulate.

3.1.5.2 Material:

All materials not depleted during the performance of this contract shall become Government property upon completion of this contract. The contractor shall transfer all materials not depleted to the COR by way of Material Inspection and Receiving Report (DD Form 250).

Material costs may include general and administrative expenses as appropriate, but shall not include profit/fee.

The contractor shall provide material integral and /or incidental to the performance of task orders awarded under this contract. Material will be identified within each task order, representative examples include but not limited to: software products and licenses, laboratory related hardware, advanced computers, tablets, iPads, and various digital/information technology equipment, materials, and products (cables, connectors, splitters, antennas); shipping, training delivery, and course materials. In accordance with NAVAIR Clause 5252.242-9515 anticipated material purchases shall be listed by specialized part, components, material, and equipment, and must be submitted to the contracting officer and TPOC with a copy to COR for approval prior to purchasing. The contractor shall track, manage, and otherwise account for purchases made on behalf of the Government under the authority of this contract with an approved purchase system.

The contractor’s purchasing system must have been reviewed and approved in accordance with

Part 44 of the Federal Acquisition Regulation (FAR). The Government reserves the right to review the contractor’s purchasing system as set forth in FAR Subpart 44.3.

Note: When buying certain IT items, an ITPR is required. Requirement owners will make the determination as to whether an IT Approval is required and complete the requisite information in the

Purchase Requisition.

The costs of general purpose business expenses required for the conduct of the Contractor’s normal business operations are not an allowable direct cost in the performance of this contract.

General purpose business expenses include, but are not limited to, the cost for items such as telephones and telephone charges, reproduction machines, word processing equipment, personal computers and other office equipment and office supplies.

3.1.6 Subcontractors:

Provisions stated herein shall be, clearly, and effectively communicated to all subcontractors providing support under this contract. All provisions of this SOW shall flow down to subcontractors providing support under this contract.

3.1.7 Management of Contractor Personnel:

The Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances will the Government assign tasks to, or prepare work schedules for, individual contractor employees. The contractor shall manage its employees and guard against any actions that are of the nature of personal services, or give the perception of personal services for Government employees.

3.1.8 Transition out Strategy:

The Contractor’s overall transition out strategy shall be built around maintaining the mission of the program/division with minimal impact, in terms of timeliness of performance, and to ensure that critical data and knowledge transfer occurs. Upon termination or expiration of the contract, the contractor shall ensure an orderly transition of responsibilities, while minimizing impact to the operation. The contractor shall submit a transition out plan, to include the minimum elements listed below in accordance with CDRL A007.

3.1.8.1 Work Turnover. The contractor shall provide a plan of action effectively transferring tasked work that is in process at the expiration or termination of the contract to the successor company. Establish and maintain effective communication with the incoming contractor or

Government personnel for the period of transition via weekly status meetings.

3.1.8.2 Quality Assurance. The contractor shall provide a plan of action to ensure continuation of quality review processes during the transition period to the successor company.

3.1.8.3 Risk Mitigation Strategies. The contractor shall provide a plan of action to mitigate contract performance risks (quality and schedule) encountered during the transition period.

3.1.8.4 Data/Information Transfer. The contractor shall provide a plan of action for the efficient inventory and transfer of program data to the successor company.

3.1.9 Quality Surveillance and Performance Standards:

The Government will conduct quality surveillance via various methods including formal and informal meetings, review of technical reports, review of monthly progress reports, and review of deliverables as provided in the Contract Surveillance Plan (CSP) Attachment X.

The Contractor shall maintain an effective quality control program to ensure services are performed in accordance with the SOW and the Surveillance Activity Checklist (SAC)

(Attachment to the CSP). The Contractor shall implement procedures to identify, prevent, and ensure non-recurrence of defective services.

3.1.10 Government Furnished Property (GFP)/Government Furnished Information (GFI):

Any GFP/GFI listed in this contract or resulting Task Orders will be provided to the Contractor within 30 days after award. Additional GFP/GFI such as training, and documentation requiring

Contractor review, analysis, and updating will be provided throughout the contract period of performance. Disposition of GFP/GFI will be made at contract completion. Contractor must have an approved Property Management System.

3.2 Security

3.2.1 Citizenship Requirements:

Only U.S. citizens may perform under this contract. If the Contractor cannot find qualified U.S.

citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. The waiver request should include:

a. The individual's name, date and place of birth, position title, and current citizenship.

b. A statement that a qualified U.S. citizen cannot be hired in sufficient time to meet the contractual requirements.

c. A statement of the unusual expertise possessed by the applicant.

d. A statement that access will be limited to a specific government contract (specify contract number).

e. A statement that the Contractor has obtained an export license for the information required to perform the contract.

3.2.2 Investigative Requirements:

3.2.2.1 Unclassified:

All Contractor personnel must be eligible to perform Non-Critical Sensitive work as defined by

SECNAV M-5510.30. All Contractor personnel are required to have a favorably adjudicated

Tier-3 investigation from the Office of Personnel Management. The Contractor shall submit a request for personnel security investigation to the Government Security Office. The Government

Security Office shall initiate the Contractor's Electronic Questionnaire for Investigations

Processing (eQIP)), shall do a preliminary screening of the Contractor's eQIP for suitability and derogatory information. The Contractor employee shall provide all requested information pursuant to the Privacy Act of 1974. The Government Security Office may deny the Contractor access to Government facilities and information and may prohibit the Contractor from performance of sensitive duties for failure to provide requested information or when derogatory or adverse information is present on the Contractor's eQIP, in such cases, the Contractor employee may not perform on the Contract.

The Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified information and to control distribution of controlled unclassified information in accordance with DoD 5220.22-M, National Industrial

Security Program Operating Manual (NISPOM), and SECNAV M-5510.36. All Contractor facilities shall provide an appropriate means of storage for controlled unclassified information and materials. All controlled unclassified information shall be appropriately identified and marked as For Official Use Only in accordance with DoDM 5200.01, Information Security

Program: Controlled Unclassified Information (CUI) Volume 4 (enclosure 3).

Controlled Unclassified Information including For Official Use Only and Covered Defense

Information (meeting the definition of 48 CFR 252.204–7012(a)) generated and/or 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 pages 11-18) available at http://www.dtic.mil/whs/directives/corres/pdf/520001_vol4.pdf. Any product containing Covered Defense Information shall be assigned a distribution statement

(distribution statements B through F) using the criteria set forth in DoDI 5230.24 (Distribution

Statements on Technical Documents); and have this statement displayed per DoDI 5230.24, Enclosure 3.

3.2.2.2 Classified:

All Contractor personnel shall maintain security clearance eligibility commensurate with the level of classification of the work performed as annotated in the Contract's DD-254, Contract

Security Classification Specification Form.

Contractor personnel shall require access to classified information in performance of this contract up to and including Secret /Top Secret / SCI, as determined by the task order, with a safeguarding level of Secret /Top Secret / SCI, as determined by the task order. The Contractor is responsible for ensuring that all personnel receive the requisite investigation, and are favorably adjudicated in accordance with DoD 5220.22-M, National Industrial Security Program Operating

Manual. Contractor employees who fail to meet security clearance requirements may not access classified information or perform sensitive duties. In such cases, the Contractor employee may not perform on the contract.

The contractor shall comply with security requirements specified in the DD-254 attached to this contract. Information or data that the contractor accesses shall be handled at the appropriate classification level. Unclassified information shall be handled in accordance with the appropriate designation (Controlled Unclassified Information; For Official Use Only; Covered

Defense Information). Distribution is authorized to the Requiring Office's Organization and its supported Activity(s) only. Other requests for deliverables under this contract shall be referred to the TPOC/COR of this contract for approval.

Controlled Unclassified Information including For Official Use Only and Covered Defense

Information (meeting the definition of 48 CFR 252.204–7012(a)) generated and/or 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 pages 11-18) available at http://www.dtic.mil/whs/directives/corres/pdf/520001_vol4.pdf. Any product containing Covered Defense Information shall be assigned a distribution statement

(distribution statements B through F) using the criteria set forth in DoDI 5230.24 (Distribution

Statements on Technical Documents); and have this statement displayed per DoDI 5230.24, Enclosure 3.

3.2.2.3 Sensitive Compartmented Information (SCI):

Some programs under this IDIQ contract may require personnel to have access to Sensitive

Compartmented Information (SCI), SCI is an access determination based on need to access intelligence information in which classified national intelligence information concerning or derived from intelligence sources, methods, or analytical processes are required to be handled within formal access control systems established by the Director of National

Intelligence (DNI). Under DoD Instructions 5200.01 “DoD Information Security Program and

Protection of Sensitive Compartmented Information”. Personnel requiring access to SCI will be identified at the Task Order level, if applicable.

The SCI designation is an add-on, not a special clearance level at a Secret level or Top Secret level. The government also supports access to SCI in which access is determined by need-to-know. These accesses require increased investigative requirements before access is granted and therefore increased lead times may be experienced during the SCI investigative process.

Individuals with a security clearance may be “read into” SCI as a part of their job requirement and receive explicit permission to access an SCI control system(s). This process may include a polygraph or other approved investigative or adjudicative action. Once it is determined, a person should have access to an SCI control system(s), they sign a nondisclosure agreement, are "read in" or indoctrinated and is recorded in a local access register or in a computer database. Upon termination from a particular SCI control system, the employee is “read out” or debriefed and again signs the nondisclosure agreement.

3.2.3 Common Access Card (CAC)/Public Key Infrastructure (PKI), System Authorization

Access Request (SAAR-N).

3.2.3.1 SAAR-N:

All contractor personnel requiring access to Government Information Technology (IT) systems shall have an approved System Authorization Access Request (SAAR-N) Form OPNAV

5239/14 (Rev Sep 2011) on file, and complete required Annual Information Awareness Training.

New employees must submit their SAAR forms within thirty (30) days of their first day of work.

Instructions for processing the SAAR-N forms are available at:

http://www.cnrc.navy.mil/publications/Forms/OPNAV_5239_14_SAAR_N.pdf.

SAAR-N forms shall be submitted to the Contracting Officer’s Representative (COR), Government Technical Point of Contact (TPOC), or to the assigned government Trusted

Associate Sponsorship System (TASS) Trusted Associate.

3.2.3.2 Command Access Cards (CAC) / Local Badges:

Contractor CACs and facility specific identification badges will be issued by the Government to on-site contractor personnel and shall be visible at all times while personnel are at the

Government site. The contractor shall furnish all requested information required to facilitate issuance of identification badges and shall conform to local installation badge policy and guidance. All CACs and identification badges issued to Contractor employees shall be returned to the Government Security Department at the Government site in accordance with local installation badge policy and guidance following completion of the contract, relocation or termination of an employee, or upon request from the Contracting Officer’s Representative. The

Government will provide the contractor access to Government facilities, as required, for performance of tasks under this contract. Contractor personnel shall comply with local installation badge policy and guidance.

https://www.clearancejobs.com/jobs/intelligence http://www.cnrc.navy.mil/publications/Forms/OPNAV_5239_14_SAAR_N.pdf

3.2.3.3 DD-254:

The contractor shall comply with security requirements specified in the DD-254 attached to this contract. Information or data that the contractor accesses shall be handled at the appropriate classification level, unclassified information shall be handled as “For Official Use Only”.

Distribution is authorized to the Requiring Office’s Organization and its supported Activity only.

Other requests for deliverables under this contract shall be referred to the TPOC/COR of this contract for approval.

3.2.4 Information Security:

If the work is performed at the Contractor's facility, the Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and controlled unclassified information (CUI) and to control distribution of CUI in accordance with

DoD 5220.22-M (NISPOM), and SECNAV M-5510.36. If the work is performed at the

Government's facility, the Contractor shall comply with the local Security Policy and Procedures.

3.2.4.1 Marking:

All information generated by the Contractor shall be properly marked. For Official Use Only information generated and/or provided under this contract shall be marked in accordance with

DoDM 5200.01. Technical information shall also be marked with appropriate Distribution

Statements and Export Control warnings in accordance with DoDD 5230.24 and program

Security Classification Guidance.

3.2.4.2 Public Release for Classified and Unclassified Information:

No information pertaining to this contract shall be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved in writing for public release by the appropriate U.S. Government authority. Proposed public releases shall be submitted for approval prior to release through the Procurement Contracting

Officer (PCO).

3.2.4.3 Loss, Compromise and/or Electronic Spillage of Classified or Controlled

Unclassified Information:

All instances of loss, compromise and electronic spillage of classified or controlled unclassified information shall be reported to the COR, TPOC and Government Security Office within 24 hours of the incident occurring.

3.2.5 Operations Security (OPSEC):

The Contractor shall develop, implement, and maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the Contractor and any subcontractor during performance of the contract. The Contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. This program may include Information Assurance and Communications Security (COMSEC). The OPSEC program shall be in accordance with National Security Decision Directive (NSDD) 298, and at a minimum shall include:

1) Assignment of responsibility for OPSEC direction and implementation.

2) Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.

3) Establishment of OPSEC education and awareness training.

4) Provisions for management, annual review, and evaluation of OPSEC programs.

5) Flow down of OPSEC requirements to subcontractors when applicable.

While performing aboard NAVAIR or NAVAIR sites, the contractor shall comply with facility

OPSEC program instructions and contribute to organization-level OPSEC efforts. Include

OPSEC as part of its ongoing security awareness program and take all required Agency training.

Be responsive to the Supporting OPSEC Manager on a non-interference basis. Protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by the RO and contractor in support of the mission.

The Contractor shall prepare and deliver an OPSEC Plan in accordance with CDRL A003

3.2.6 Anti-Terrorism Force Protection and Emergency Management: The work performed on this contract is not Emergency Essential in accordance with OPNAVINST 3440.17A and

Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans.

Contractor personnel shall comply with all Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans and directives. Contractor personnel shall not report for work at Government facilities upon declaration of Force Protection Condition CHARLIE or in any event or emergency where Government officials’ direct curtailment of operations to

“Mission Essential Only”. All Contractor personnel assigned to a government facility shall complete annual Antiterrorism (Level I) and Active Shooter training.

3.2.7 Program Unique Requirements:

3.2.7.1 Data Handling:

In accordance with OCI Clause 5252.209-9510(e)(5) and as appropriate, this contract provides for the contractor to provide technical evaluation and/or advisory and assistance services in support of acquisition planning and execution of NAVAIR programs. The contractor will have access to system performance, program / business sensitive, company proprietary and pre-decisional material / data, which shall not be disclosed to any entity, Government or otherwise, outside of the NAWCAD unless specifically indicated by a designated Government point of contact or authorized in writing by the Contracting Officer. The Contractor shall not use for purposes other than performance under this contract; nor shall the contractor release, reproduce, distribute, or publish any data or analysis that is provided as GFI or produced in the performance of this contract; nor shall the contractor authorize others to do so, without written permission of the Contracting Officer. Further, the contractor shall, within 15 days after the effective date of this contract, obtain and provide to the COR signed Non-Disclosure Agreements (NDAs) signed by a duly authorized representative of the prime contractor, each subcontractor, and each consultant (provided as CDRLs A009 and A010), and shall obtain and provide to the COR signed individual NDAs with all contractor, subcontractor, and consulting personnel that performs work under this contract. Additionally, the contractor agrees to place in each subcontract affected by these provisions the necessary language to bind the subcontractor by these terms and conditions. IMPORTANT: Executing these non-disclosure agreements attached to this solicitation does not alleviate the contractual duties and obligations the Contractor has pursuant to NAVAIR Clause 5252.209-9510(e)(5) including agreeing to execute agreements with companies furnishing proprietary data in connection with work performed under this contract.

3.3 Detailed Support:

Appropriations. Task Orders under this IDIQ contract will includes the following types of funding: Navy Working Capital Funds (NWCF), Research, Development, Test and Evaluation

(RDT&E), Operation and Maintenance, Navy (O&MN), Aircraft Procurement, Navy (APN), Foreign Military Sales (FMS)

Software engineering is a continuing capability that must be continuously developed, deployed and improved throughout its lifecycle. Contractor support requirements listed in sections 3.3.1 through 3.3.16.3 shall include all phases of Software Systems Engineering from software systems acquisition through sustainment phases of a project. Support efforts include the development, preparation, test, and updates to new and current equipment and capabilities.

3.3.1 Mission Analysis Support: The contractor shall review and comment on Mission

Analysis documents that will define requirements for platforms and systems during the acquisition and/or sustainment phases of the program using Government provided data. The contractor shall evaluate the impact of new equipment capabilities and/or the impact of updated hardware and software on meeting the requirements and the mission performance against projected or current threat capabilities.

3.3.1.1 Hardware and Software Technical Plans. The contractor shall review and comment on the technical plans of hardware and software by writing or updating hardware and software technical plans based NAVAIR/NAWCAD provided information. The technical plans shall incorporate trade-off studies, engineering approach analyses, system implementation analyses, and comments for the technical development. These hardware and software technical plans shall include the following Sow sections 3.3.1.2 through 3.3.1.7:

3.3.1.2 Project Master Plan. The contractor shall develop and update Project Master Plans by creating schedules, monitoring milestones, and identifying manpower requirements. The plan shall include the following information for the concept development, detailed design, pre-production, and sustainment phases of the project:

a. Schedule – The schedule shall be organized by subsystem. The major events and event durations for the required activities must be defined.

b. Milestones – For each major activity, project milestones shall be included which correspond to tangible products or achievement levels.

c. Manpower – For each major area, manpower required to achieve the final and intermediate milestones associated with that activity shall be identified.