WSISS V Draft SOW.pdf

N68936-20-R-0102

DISTRIBUTION STATEMENT A: PAO APPROVAL NOT ESTABLISHED TO DATE. Requests shall be referred to the Naval Air Warfare Center, Weapons Division, Code 418400D, China Lake, CA 93555-6100.

STATEMENT OF WORK (SOW)

FOR

WEAPONS AND SYSTEMS INTEGRATION SUPPORT SERVICES (WSISS) V

CLIN 0001 -- Labor CLIN for Weapons and Systems Integration Support Services CLIN 0002 – Other Direct Costs CLIN 0003 – Not Separately Priced CLIN in support of the Contract Data Requirements List

DISTRIBUTION STATEMENT A: PAO APPROVAL NOT ESTABLISHED TO DATE. Requests shall be referred to the Naval Air

1.0 SCOPE

1.1 Background

The Naval Air Warfare Center Weapons Division (NAWCWD) is the weapons systems integration and software support activity for several aircraft Integrated Product Teams (IPTs). IPTs and Program Support Offices currently operating at the NAWCWD include the F/A-18 & EA-18G, AV-8B, AH-1, F-35, and Unmanned Systems. In addition to the aircraft named above, the contract may support any other aircraft that may be assigned to the NAWCWD in the future, any system carried by or supporting aircraft IPTs assigned to the NAWCWD, and interoperability initiatives involving supported aircraft. The mission of each IPT and Program Support Office is to provide research, development, test, evaluation, systems integration, and programmatic support for weapons systems and associated tactical computer systems embedded within or carried on their aircraft, including related systems, support equipment, and interoperability initiatives. The efforts of NAWCWD’s Aircraft IPTs and Weapons Program Support Offices are integral to the Navy’s ability to achieve Integrated & Interoperable (I&I) Warfighting Capabilities (platforms, sensors and weapons operating seamlessly in a Systems of Systems (SoS) environment) that produce an immediate and sustainable increase in warfighting effectiveness and battlespace dominance.

The term "aircraft weapon system,” in the context of this Statement of Work (SOW), is defined as weapons/trainers/sensors and targeting/mission computer/avionics systems and software, including electronic warfare (EW) systems, integrated into NAWCWD IPT supported aircraft, as well as associated pre- and post-flight support systems, and/or support equipment hardware and software for any of the above.

1.2 General Scope of Work

The contractor shall provide the following services and may purchase materials in support of: Modification of aircraft components, technical support services (including full systems integration) to all NAWCWD aircraft IPTs and their associated aircraft weapons and support systems (including foreign military sales (FMS) versions of each aircraft or system), and technical support services (including full systems integration) to other related and/or interfacing systems (including related test laboratories and equipment). The scope of the contract includes performing related technical functions necessary to satisfactorily complete primary tasking, such as:

(a) Integration of weapons, avionics, sensors, targeting systems, system hardware, and software (including system analysis, research, development, engineering, testing, test equipment design/fabrication/maintenance, mission simulation, and interoperability assurance);

(b) Software engineering/development for aircraft computers, avionics, sensors, targeting systems, weapons systems, test laboratories, simulators, mission and system support equipment (including Software Quality Assurance (SQA), Software Configuration Management (SCM), and Verification and Validation (V&V));

(c) IPT program technical services (including special technical research, studies, Quality Assurance (QA), Configuration Management (CM), Data Management (DM), communications management, equipment management, and maintenance of support systems);

(d) Design, fabrication, integration, and purchase of materials supporting operation of test and simulation equipment, flight and system trainers and/or simulator equipment (including mission and interoperability simulations);

(e) Aircraft modifications, aircraft test instrumentation, and telemetry systems design, development, installation, maintenance, service, setup, and operation (including ground-based telemetry systems);

(f) Training in areas where the contractor has special knowledge or expertise (such as legacy systems, etc) and in the use and/or maintenance of software and/or systems designed by the contractor.

(g) Training and the purchase of materials and personnel in the use of agile principles and applications in support the IPT’s identified in this SOW.

2.0 Applicable Documents

Standard requirements documents (Government and Industry Specifications and Standards), reference texts, specific design requirements, and other references will be defined by individual Task Orders. The Government will apply commercial specifications and standards to the greatest extent reasonably possible. The Government will provide all necessary reference documents not generally available to the contractor. The following list of general requirements documents and reference texts is a sampling of those that have been imposed by Task Orders in the past.

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. The list is provided here for contractor reference only.

DISTRIBUTION STATEMENT A: PAO APPROVAL NOT ESTABLISHED TO DATE. Requests shall be referred to the Naval Air

2.1 Department of Defense (DoD) Specifications

DoD-5000 Series Defense Acquisition DoD Manual 4500.36 Acquisition, Management, and Use of Non-

DoD Non-Tactical Vehicles

2.2 Reserved

2.3 Other Government Documents

MIL-STD-1533 Aircraft Internal Time Division MIL-STD-1760 Aircraft/Store Electrical Interconnection System MIL-STD-2217 Requirements for Memory Loader/Verifier

Multiplex Bus Interface with Avionics Systems NAVAIR 01-1A-505 Aircraft Electrical and Electronic Wiring NAVAIRINST 3710.1G Contractor’s Flight and Ground Operations VNAVAIRINST 4355.19 Systems Engineering Technical Review (SETR) NAVAIRINST 5239.2 Naval Air Systems Command Information

Systems Security Program NAVAIRINST 8012 Non-Nuclear Ordnance Non- Combat

Expenditures Requirements/Allocations NAVAIRINST 13034 series Flight Test Requirements NAVSO Pamphlet 3627 Earned Value System NAWCWPNCENINST 7320.1 NAWCWPNS Equipment Management Manual

(series) NAWCWPNS WDPS NAWCWPNS Plant Property System NAWCWPNSINST 3960.4 Project Test Plans for Test of Air Vehicles, Weapons, and Installed Systems OPNAV 43P6 Metrology Automated System for Uniform

Recall and Reporting (MEASURE) User’s Manual

OPNAVINST 4790 series Naval Aircraft Maintenance Program OPNAVINST 5000.42D T&E Policy and Procedures, Encl. (13) OPNAV 5100.23C Safety Ashore Manual OPNAVINST 5239.1A Department of Navy ADP Security Manual

2.4 Reserved

3.0 Requirements

3.1 General Requirements

3.1.1. System Software / Application Compliance

All Information Technology Systems or software/application development, modification or support shall be performed in accordance with Defense Business Transformation guidance (formerly Business Management Modernization Program (BMMP)), Department of the Navy (DON)/Naval Air Systems Command (NAVAIR) Functional Area Manager (FAM) Policies and Guidance, Network and Server Registration, and Web Enablement mandates.

3.1.1.1 Web Sites, Web Enablement and Application / System Development, Modification, and Maintenance Support Services:

All Information Technology systems, software, and website development, modification or support shall be performed in accordance with all applicable Federal, DoD, DON, and NAVAIR policy, guidance, standards, and

DISTRIBUTION STATEMENT A: PAO APPROVAL NOT ESTABLISHED TO DATE. Requests shall be referred to the Naval Air strategies, and should be integrated within the NAVAIR Enterprise portal and collaboration environment whenever possible. Any Web sites/servers hosted/located in contractor facilities, or outside NAVAIR enclave, will transition to NAVAIR architecture and infrastructure in accordance with Legacy Shutdown guidance. Policies include, but are not limited to:

a. Office of Management and Budget Management of Federal Information Resources, OMB CIRCULAR

NO. A-

130 Revised. https://www.whitehouse.gov/omb/information-for-agencies/circulars/

b. OMB Policies for Federal Agency Public Websites, OMB M-05-04.

https://www.whitehouse.gov/search/?s=+memoranda+fym05+04

c. Section 508 Amendments to the Rehabilitation Act of 1973.

https://search.usa.gov/search?query=Rehabilitation-Act&op=Search&affiliate=gsa-section508-accessibility

d. Department of Defense Web Policies and Guidelines. http://www.defense.gov/webmasters

e. Navy Information Operations Command (NIOC) Norfolk Web Risk Assessment Team Website.

https://www.public.navy.mil/fltfor/nnwc/SitePages/WRA.aspx

f. DON Policy for Content of Publicly Accessible World Wide Web Sites SECNAVINST 5720.47B.

http://www.navy.mil/navydata/internet/secnav5720-47b.pdf

g. NAVAIR CIO Website (NAVAIR specific policy and guidelines). To request this policy contact the

NAVAIR

CIO office – 7.2.2 Applications Integration team – Web Manager: Shane Malamphy at 301- 342-1825.

h. Defense Information Systems Agency (DISA) Hosting of All Navy Websites (NAVADMIN 061/08).

https://navadmin.dodreads.com/2018/03/02/defense-information-systems-agency-disa-hosting-of-all-navy-websites/

i. Consolidation of Navy Web Sites - Reduction of IM/IT Footprint NAVADMIN 145/07.

https://www.public.navy.mil/bupers-npc/reference/messages/Documents3/NAV2007/NAV07145.txt

j. DON Web Presence Policy: The Registration, Compliance of, and Investment in, All Unclassified Web Sites and Uniform Resource Locators. http://www.doncio.navy.mil/ContentView.aspx?ID=577

k. Policy and Procedures for Web Risk Assessment (WRA) of Publicly Accessible Navy Sites (ALCOM 129/09).

http://www.public.navy.mil/fcc-c10f/niocnorfolk/Documents/NTD-08-09.txt

3.1.1.2 Enterprise Architecture:

Contractor Networks and connections. Contractor-owned and operated networks are prohibited on any Naval Air Systems Command (NAVAIR) facility or site in support of this contract. The contractor may access non- Government, external IP space via the NAVAIR-provided VPN Outreach service or NAVAIR CIO approved Internet Protocol (IP) service.

Architecture Compliance. The contractor shall ensure all IT solutions, including database solutions, comply with the appropriate NAE Enterprise Architecture, and are verified by the NAVAIR Enterprise Architect (AIR-7.2.3) prior to build out.

Disclosure of pre-existing networks, circuits or connections. Any and all networks, circuits or connections between the contractor and any NAVAIR site related to previous contracts shall be identified in the MOA. Failure to comply and subsequent discovery of an unregistered network, circuit or connection shall be grounds for immediate disconnection.

3.1.1.3 Software Process Improvement Initiative (SPII):

The Contractor shall follow the Software Development Plan (SDP) that they develop and submit in accordance

DISTRIBUTION STATEMENT A: PAO APPROVAL NOT ESTABLISHED TO DATE. Requests shall be referred to the Naval Air with CDRL A00D. The SDP will follow the framework of Institute of Electrical & Electronics Engineers (IEEE)/Electronics Industries Association (EIA) IEEE/EIA Std 12207 regarding subject content, level of detail, and completeness. The SDP shall serve during contract performance as the benchmark for the contractor’s software development effort and shall be periodically evaluated and updated as specified in the CDRL, as a part of continuous process improvement subject to Government review and approval.

3.1.2 Work Location & Facilities

3.1.2.1 Contract Work Environment

The majority of the contractor’s work force shall be physically located in Government-provided work spaces at China Lake, CA; Point Mugu, CA; Yuma, AZ, Cherry point, NC; and Eglin AFB, FL where contractor tasking shall be performed. Total Government workspaces to be provided are estimated to be 330. Contractor personnel shall adhere to existing IPT work processes referenced within each task order. The Contractor shall propose improvements to work processes that result in cost or time savings to the Government. The contractor’s consistent and skillful application of these work processes is critical to the NAWCWD process improvement initiative described in Sections 3.1.9.1 and 3.3.6.

3.1.2.2 Program Milestone and Meeting Support –

The contractor shall support program milestones and meetings; including preparation of technical and milestone documents, preparation for and documentation of meetings, preparation and presentation of presentation materials, and active participation in program meetings.

(CDRLs A00N, A00Z and A010)

3.1.3 Contractor Program Management, Reporting, and General Performance Requirements

3.1.3.1 Tracking & Oversight

The contractor shall maintain a cost accounting system that shall track, report, and invoice on actual expenditures for each Task Order. Additionally, the contractor’s cost accounting system shall be capable of tracking, reporting, and invoicing at the Work Breakdown Structure (WBS) level 3 within each Task Order, when specifically required by the Task Order. The Surveillance Activity Checklist will be used for monitoring contractor performance and is provided in Section J for informational purposes only. The contractor shall manage material and consumable supplies at levels to meet mission requirements. The contractor shall obtain prior approval from the COR for any purchases valued over $500. All COR-approved purchases shall be submitted to the Contracting Officer for post action review within 3-5 business days. The contractor must obtain prior approval from the Contracting Officer for any purchases valued over $3,000. To receive approval for the purchases, the contractor shall submit a consent package providing a description, price, evidence of adequate price competition, or if unavailable, a justification for use of a single source and a determination that the price is fair and reasonable. These requirements apply to all contractor purchases.

3.1.3.2 Periodic Contract Status Reporting

The specific content, periodicity, delivery, and format (if applicable) requirements of each report listed below are defined in Exhibit A. The general report descriptions provided below may be superseded by the requirements specified in Exhibit A.

3.1.3.2.1 Monthly Task Order Progress/Status Report (MSR) (See Exhibit A, CDRL A001)

3.1.3.2.2 Weekly Task Order Expense Status Report (See Exhibit A, CDRL A002)

3.1.3.2.3 Quarterly Contractor Personnel Reports (See Exhibit A, CDRLs A003 and A004)

3.1.3.2.4 Monthly Contract/Task Order Summary Report (See Exhibit A, CDRL A005)

3.1.3.2.5 Contractor Performance Self Evaluation (See Exhibit A, CDRL A006)

3.1.3.2.6 Semiannual Cumulative Contract Report (See Exhibit A, CDRL A007)

DISTRIBUTION STATEMENT A: PAO APPROVAL NOT ESTABLISHED TO DATE. Requests shall be referred to the Naval Air

3.1.3.2.7 Annual Contract Data Product Summary (See Exhibit A, CDRL A008)

3.1.4 Work Schedule

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 0700 to 1700 Mon-Thurs (all weeks) and 0700 to 1600 on working Fridays. Work hours for these days are 9 hours a day, generally observing a 1 hour lunch break. On the working Fridays 8 hours, and 1 hour lunch. (except on the legal holidays specified in paragraph 3.1.4.1.2).

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 of time: 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 PWS/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 ACOR/COR.

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.

DISTRIBUTION STATEMENT A: PAO APPROVAL NOT ESTABLISHED TO DATE. Requests shall be referred to the Naval Air

3.1.4.1.4 Overtime: Overtime cannot be charged directly to the contract unless first approved in writing by the Chief of the Contracting Office.

3.1.4.1.5 Reserved

3.1.5 Other Direct Costs

3.1.5.1 Travel: Travel may include general and administrative expenses, but shall not include profit. Temporary travel to other locations in support of program tasking is / not required. If required, temporary travel locations include (list location(s)). This list is not all inclusive as locations may change over the life of the contract.

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 but shall not include profit/fee.

3.1.6 Subcontractors and Consultants:

Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this contract. All provisions of this PWS/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

3.1.8 Transition out strategy

3.1.8.1 Contract Phase-Out

The contractor shall prepare and submit a Contract Phase-Out Plan describing the completion or transition of work in progress and the professional and orderly transition of contract responsibilities at the end of the contract’s period of performance. (See Exhibit A, CDRL A00C)

3.1.9 Program Unique Requirements

3.1.9.1 Training and Improvement Initiatives

3.1.9.2 Contractor Training

The contractor shall provide a work force properly trained (and certified, if required) to perform all tasking defined within the Task Order Statements of Work (SOW)s or Performance Work Statements (PWS). If tasking requires certification and/or periodic recertification (examples: soldering and certain tasking related to computer system operation/administration), the contractor is responsible for the costs of certification and, if required, periodic recertification. Some technology areas supported by this SOW are continually evolving. The contractor shall attend advanced technology training as required at the task order level.

The contractor shall complete all applicable training required at the task order level. The Government may provide (on a space-available basis) special training to the contractor in the areas of military systems (ex. UAV), training mandated for all personnel working at the NAWCWD (ex. Combatting Trafficking in Persons) or accessing Government systems, and other Government-required training.

The contractor shall provide and/ or attend training to both Government and other contractor personnel in subject areas within the scope of this SOW (ie. Agile training); however, these requirements are anticipated to be in subject areas where the contractor has special knowledge or expertise and in the use and/or maintenance of software and/or systems designed by the contractor. The contractor shall develop presentation and training materials appropriate to particular training assignments.

DISTRIBUTION STATEMENT A: PAO APPROVAL NOT ESTABLISHED TO DATE. Requests shall be referred to the Naval Air

3.1.9.5 Process Improvement Initiatives & Innovations

The contractor shall provide personnel who are knowledgeable regarding the established work process definition documents under each Task Order and shall work cooperatively to establish, maintain, and continuously improve the NAWCWD work environment and ongoing process improvement initiatives. The contractor shall participate in Government process improvement programs/initiatives associated with supported programs and systems (i.e. Agile, SecDevOps, etc.) The contractor shall conduct and report on process improvement studies, including evaluations and evaluation criteria for new products or systems suitable for use in improving system engineering and software development processes.

3.1.9.6 Systems Engineering and Software Process Improvement Initiative (SPII) The contractor shall provide Systems Engineering and Software Process Improvement recommendations for NAWCWD’s active program to improve its processes to a higher maturity level in accordance with the Capability Maturity Model, Integrated (CMMI) principles developed by the Software Engineering Institute (SEI) (Levels 1 - 5).

Some NAWCWD groups have already been certified at Level 5. Other NAWCWD customer Code groups will be striving to attain certification at maturity levels 3-5 within the period of performance of this contract. The contractor shall participate in this program. While the Government is the “process owner,” the contributions of process users are vital to the success of this program. It is the overall collection of process users that achieves the CMMI certification.

The Contractor shall follow the Software Development Plan (SDP) which it developed and submitted in accordance with CDRL A00D.The SDP shall serve during contract performance as the benchmark for the contractor’s software development effort and shall be periodically evaluated and updated as specified in the CDRL, as a part of continuous process improvement subject to Government review and approval. The SDP will follow the framework of Institute of Electrical & Electronics Engineers (IEEE)/Electronics Industries Association (EIA) IEEE/EIA Std 12207 regarding subject content, level of detail, and completeness.

3.1.9.7 Contractor and NAWCWD-Provided Facilities

The contractor shall establish a facility within the general commuting area of the NAWCWD China Lake main gate that meets the security requirements as outlined in the attached DD Form 254. The contractor shall provide workspaces within the contractor facility for approximately 5% of the contractor’s technical staff. Contractor personnel working from the contractor facility may require frequent access to the lab and test facilities at the NAWCWD and frequent interface with Government and other contractor personnel at the NAWCWD. Costs for travel between the contractor's facility and the NAWCWD shall not be directly charged to the contract. NAWCWD work-spaces will be provided for the remaining 95% of the contractor’s technical staff located at China Lake and Pt.

Mugu and other remote locations. Government-provided work-spaces include, as necessary, desks/cubicles, computer equipment, and telephones necessary for performance

3.1.9.8 Contractor’s Ground Operating Procedures.

The contractor shall prepare and submit Ground Operating Procedures (GOPs) (See Exhibit A, CDRL A009) for review and approval by the Government Ground Flight Representative (GGFR) as required by DFARS 252.228-7001 Ground and Flight Risk, and in accordance with NAVAIRINST 3710.1G Contractor’s Flight and Ground Operations, and in accordance with Section J, Attachment 1 AVMI Ground Operating Procedure Template and Guidance

3.1.9.9 Transportation and Vehicle Requirements

The contractor shall provide all vehicles required for the performance of this contract. Under limited circumstances, shared access of Government Owned Government Operated (GOGO) vehicles may be provided to contractor personnel. These are not Interagency Fleet Management System (IFMS) vehicles but are DON owned vehicles managed through the Transportation Office, NAVFAC Southwest, Code 270,and are available under the following conditions: Contracting Officer’s Representative (COR) concurrence with the contractor’s need to use GOGO vehicle(s); COR oversight to ensure compliance with DOD Manual 4500.36; clause 5252.228-9501, LIABILITY INSURANCE included in this contract applies to the use of GOGO vehicles; the contractor shall meet all training and licensing requirements to operate the GOGO vehicles as defined in NAVFAC P-300; the contractor need for GOGO vehicles will not interfere with Government use of those vehicles; and use of GOGO vehicles is for work on a Government site and is for official use only for specific Task Order requirements. The vehicle costs (including vehicle lease costs when all other options are exhausted) directly (and proportionally, if applicable) related to the

DISTRIBUTION STATEMENT A: PAO APPROVAL NOT ESTABLISHED TO DATE. Requests shall be referred to the Naval Air transportation needed to support contractor performance requirements shall be invoiced against the task order(s) defining the tasking needing transportation. PCO approval is required before entering into any leasing or purchase agreement that will result in a direct charge to the contract. The Government may provide contractor access to Government fuel pumps for refueling (at Government expense) of Government vehicles performing transportation in response to the requirements of this contract. If provided, Government fuel pump access will be specified at the Task Order level.

3.1.9.10 General Transportation Requirements:

Contractor performance is required in a number of locations, many of which are accessible by paved roads, but some of which require effective and reliable off-road transportation. Worksites can be remote and/or limited in the number and type of vehicles that they can accommodate. The contactor may be responsible for moving hardware and test equipment; and for towing loads including but not limited to equipment trailers, weapons, and test modules on an as-needed basis. The contractor shall ensure that the transportation vehicles used in contract performance meet all relevant Navy standards specified at the Task Order level. The contractor shall ensure that contractor personnel who drive vehicles on Base shall have a valid driver's license and vehicle insurance coverage, per FAR 52.228-7, and shall meet any other Government requirements that may be imposed upon drivers operating vehicles on Base.

3.1.9.11 Special Flight Line Transportation and Training Requirements:

The contractor shall provide and operate vehicles on the flight line when required at the task order level. The contractor shall coordinate with the Naval Air Weapons Station (NAWS) Air Operations Manager to ensure that special vehicle requirements (such as marking, communications radio, and operator training for airfield ramp operations) are met, prior to operating vehicles on the flight line. Training and licensing will be provided to contractor personnel on an as-needed basis at the Government’s discretion to perform the following restricted special vehicle activities: operation of any vehicle within the flight line area, operation of flight line test support equipment, and for in-cockpit aircraft avionics and systems testing under-ground support power. Contractor personnel operating vehicles on the flight line shall pass all relevant Navy required training, as evidenced by receipt of a Navy Flight Ramp Vehicle License.

3.1.9.12 Riding in Vehicles

For the purpose of performing the contract, Contractor employees may be allowed to ride in vehicles provided by the Government or driven by Government employees. Additionally, when Contractor employees are driving vehicles for the specific purpose of performing the contract requirements, Government employees may ride in those vehicles.

Contractor employees will not be used as chauffeurs or drivers, and shared rides will only be for transportation between locations that both Contractor employees and Government employees need to go. The decision to carpool is solely at the discretion of the driver.

3.2 Security and Classified Data

3.2.1 Citizenship Requirements

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 Investigation Requirements

3.2.3 CAC/PKI/SAAR

DISTRIBUTION STATEMENT A: PAO APPROVAL NOT ESTABLISHED TO DATE. Requests shall be referred to the Naval Air

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 OPNAVINST 5530.14D or Local Installation policy. All CACs and identification badges issued to Contractor employees shall be returned to the Government Security Department at the Government site in accordance with DoDM 1000.13M Vol 1 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 DoDM 1000.13M Vol 1

3.2.4 NAVAIR Security Process: During performance under this contract, the contractor shall comply with the contractual Form DD-254 and applicable NAVAIR security processes. Additional Task Order specific information, if any, will be provided within the Task Orders.

3.2.2 Special Classified Data and Information (see contractual Form DD-254): Contractor performance related to certain IPT-supported aircraft equipment, avionics, sensors, etc. may involve access to: (1) classified information up to the TOP SECRET level, (2) cryptographic keys and data, (3) restricted and formerly restricted data, (4) foreign-nation weapons and sensors intelligence data requiring INTEL and NOFORN clearances, (5) NATO information, and (6) SIPRNET (7) storage of SCI, unescorted access to SCI areas, contract product(s) and/or deliverable(s) will contain SCI” etc.. Contractor personnel performing tasks that require access to cryptographic keys and data, and foreign-nation weapons and sensors intelligence data, shall have the appropriate security clearances to receive/handle such information, and shall satisfactorily complete the relevant Government-provided security training, including COMSEC certification training. U.S. cryptographic equipment inventory information, as well as the systems and manner in which each particular equipment is used, is for official use only. Publication or release of any related COMSEC information by any means, by the contractor, without prior written approval of the contracting officer is prohibited. The contractor must be a U.S. citizen, have a final Government security clearance with the appropriate personnel security background investigation for the level of classification involved, have strict need-to know, have the appropriate COMSEC briefing before access is granted, and granted access only in conformance with procedures established for the particular type of COMSEC information involved. The contractor shall adhere to the DD Form 254 COMSEC security requirements, facility COMSEC material control and operating procedures, and all applicable COMSEC regulations, instructions, and policies. Prior approval from the Government Contracting Activity is required in order for a prime contractor to grant COMSEC access to a subcontractor.

For Official Use Only information generated and/or provided under this contract shall be marked and safeguarded as specified in DoDM 5200.01, Information Security Program Manual (Volume 4) available at http://www.dtic.mil/whs/directives/corres/pdf/520001_vol4.pdf. Contractor shall not store or transmit CUI on personal information technology systems or via personal e-mail. Unclassified e-mail containing any DoD CUI shall be encrypted. Prior to sending CUI to any non-Navy Marine Corps Internet (NMCI) addressees, the sender must first positively verify all recipients are authorized access to CUI and have need-to-know. Non-NMCI recipients must have a DoD compliant Private Key Infrastructure (PKI) certificate that enables electronic transmission via unclassified networks while protecting the CUI with a digital signature and encryption.

Public Release:Disclosure of information is covered by DFARS 252.204-7000 Disclosure of Information, incorporated in Section I of the contract. Concerning subsection (a)(2), “information otherwise in the public domain” is information officially released into the public domain, e.g. via Distribution Statement A, and does not include information in the

DISTRIBUTION STATEMENT A: PAO APPROVAL NOT ESTABLISHED TO DATE. Requests shall be referred to the Naval Air public domain that has not been officially released. For disclosure of unclassified information that has not been officially released, the contractor must seek specific approval from the Contracting Officer, with approval from the NAWCWD Public Affairs Office (PAO).

3.2.3 Foreign Military Sales (FMS):

Contractor personnel working in support of FMS tasking shall interface or work with foreign-nation personnel as required, with Government oversight as required. Those contractor personnel shall satisfactorily complete special Government-provided security training in this area when such training is required.

3.2.4 Security Responsibilities:

The contractor shall comply with DD Form 254 and NAWCWD Security requirements, policies, practices, and procedures. Special Security requirements may be defined at the task order level.

3.2.5 Special Access Information:

The contractor may be granted access to SPECIAL ACCESS INFORMATION for some tasking within this Statement of Work. When this is applicable, it will be identified in the Task Order level form DD-254. When access to SPECIAL ACCESS INFORMATION is granted, it will be for access to information only at another contractor's facility or a Government activity.

3.2.6 Platform-Specific Security Requirements:

The Contractor shall establish a Cyber Security (CS) Program in accordance with the Program Executive Office Tactical (PEO(T)) Cyber Security Plan identified SOW 2.4. All data requested, provided and/or generated during performance of this requirement is considered Covered Defense Information (CDI), and should be treated in accordance with DFARS 252.204-7012. The Contractor shall develop a Cyber Security Implementation Plan (CSIP) addressing the requirements of the CS Plan for the F/A-18 (ALL SERIES) and EA-18G Aircraft/Systems in accordance with CDRL A00E. The Contractor shall review the CSIP at least annually and update it as required, based on revised information provided by the Government, or as a result of changes in the Contractor’s procedures with CDRL A00E.

3.2.7 Personnel Security:

Contractor shall provide personnel with the appropriate security clearance levels for the work to be performed. Access to TOP SECRET information is required in the performance of this contract and shall be in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM) and applicable DoD Personnel Security regulations. The contractor will require access to non-substantial Sensitive Compartmented Information (SCI) at the task order level. Access to SCI requires a final U.S. Government Top Secret Clearance and SCI indoctrination. Non-substantial SCI security requirements will be addressed at the task order level. The contractor shall maintain sufficiently cleared personnel to perform the tasks required by this SOW IAW the DD Form 254, and the Contract. All Contractor personnel shall possess a clearance and need-to-know commensurate with the requirements of their positions.

3.2.8 Information Security:

Direct Support contractor personnel working under the purview of a DoN Commanding Officer/Commander shall comply with the local security provisions and the requirements of SECNAV M-5510.36 (series). 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

3.2.9 Operations Security (OPSEC): The contractor shall comply with the OPSEC requirements outlined within the DD Form 254.The contractor shall develop, implement, and maintain an OPSEC program to protect critical information to include 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. The OPSEC program shall be in accordance with National Security Decision Directive (NSDD) 298, and at a minimum shall include:

DISTRIBUTION STATEMENT A: PAO APPROVAL NOT ESTABLISHED TO DATE. Requests shall be referred to the Naval Air

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.

The contractor shall prepare an Operations Security Plan for government review in accordance with (Exhibit A, CDRL A00B).

The contractor shall deliver a Software Development Plan (SDP) in accordance with SOW Paragraph 3.1.1.3 (see Exhibit A, CDRL A00D).

3.2.10 Cybersecurity:

The contractor shall conduct investigation and analysis of acquisition program artifacts such as but not limited to Initial Capabilities Document (ICD), Capability Description Document (CDD), Capability Production Document (CPD), Navy urgent operational need (UON) and Marine Corps urgent universal need statement (UUNS), joint urgent operational needs (JUONs), threat assessments and acquisition strategies (AS). Knowledge gained from this analysis shall be used when developing the Cyber Security Strategy (CSS) needed to steer and inform the program’s development of a Security Plan (SP) in accordance with DoDI 8510.01, of 12 March 2014.

As a minimum, hardware, firmware, software, documentation (data deliverables) and/or Information Technology (IT) services delivered by this contract shall be in compliance with the following References:

a. DoDI 8500.01 Cyber Security, 7 October 2019

b. DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), 28 July 2017,

c. Committee on National Security Systems Instruction 1253, “Security Categorization and Control

Selection for National Security Systems,” March 27, 2014, as amended.

d. DoDD 8140.01, Cyberspace Workforce Management, 31 July 2017.

e. DoD 8570.01-M Information Assurance Workforce Improvement Program, 101 November 2015, Certified Current as of 10 November 2015.

The contractor shall conduct investigation and perform analysis including; criticality analysis, threat assessment and vulnerability assessments. All findings and recommendations shall be reported to the government in technical reviews and submitted as written reports or documents as listed in Contract Data Requirements Lists. The contractor shall support government efforts needed for Information systems (IS) (enclaves or major applications), Platform Information Technology (PIT) or PIT systems to successfully categorize the system, achieve favorable assessment for selection, implementation and testing of security controls and authorization (approval to operate) before use or interconnection in an operating environment in accordance with references (a), (b) and (c). This includes IT that is standalone and IT that is connected to other systems, networks or enclaves. Information systems (IS) (enclaves or major applications), Platform Information Technology (PIT) or PIT systems delivered prior to award of this contract but included in the performance of this contract may have been delivered in compliance with Department of Defense Information Assurance Certification and Accreditation Process (DIACAP) and as such shall require transition to Risk Management Framework Cyber Security compliance. Transition planning proposed or performed under this contract shall be in compliance with reference (b) Enclosure 8, Figure 2 and all hardware, firmware and software deliverables shall be capable of receiving Authorization to Operate in accordance with reference (b).

Information technology services shall only be performed by personnel who are qualified and certified in accordance with reference (d) Cyberspace Workforce management above. Personnel proposed and/or used in the performance of this contract as certified personnel shall be limited to those whose specifically assigned duties and responsibilities require certification.

All Cybersecurity shall be in compliance with the following listed instructions:

DISTRIBUTION STATEMENT A: PAO APPROVAL NOT ESTABLISHED TO DATE. Requests shall be referred to the Naval Air

a. DoDI 8582.01, Security Of Unclassified DoD Information On Non-DoD Information Systems, 09 December 2019

b. Chairman of the Joint Chiefs of Staff Instruction CJCSI 5123.01H (series), Charter of the Joint Requirements Oversight Council (JROC) and Implementation of the Joint Capabilities Integration and Development Systems (JCIDS), 31 August 2018

c. CJCSI 6211.02D, Defense Information System Network (DISN): Policy and Responsibilities, 24 Jan 2012

d. CJCSI 6251.01D, Narrowband Satellite Communications Requirements, 30 Nov 2012.

e. CJCSI 6510.01F, Information Assurance (IA) and Support to Computer Network Defense (CND), 09 Feb

f. Chairman of the Joint Chiefs of Staff Manual CJCSM 6510.01B – Cyber Incident Handling Program, 10

July 2012

g. Navy Ports Protocols, and Services (NPPS) Manual, Version 1.5, 16 November 2010.

h. Defense Acquisition Guidebook – Chapter 7, Acquiring Information Technology, Including National

Security Systems, Section 7.5, Information Assurance (IA).

i. DoD 5220.22-M, National Industrial Security Program Operating Manual, 1 August 2018 (NISPOM)

j. DoD 8570.01-M, Information Assurance Workforce Improvement Program, 10 Nov 2015, (Incorporating

Change 3, 24 Jan 2012).

k. DoDD 8000.01, Management of the Department of Defense Information Enterprise, 27 July 2017.

l. DoDD 8100.02, Use of Commercial Wireless Devices, Services, and Technologies in the Department of

Defense (DoD) Global Information Grid (GIG), 14 April 2004, Certified Current, 23 April 2007.

m. DoDD 8140.01, Cyberspace Workforce Management, 31 July 2017.

n. DoDI 8330.01, Procedures for Interoperability and Supportability of Information Technology (IT) and

National Security Systems (NSS), 11 December 2019.

o. DoDI8500.01, Cybersecurity, 7 October 2019.

p. DoDI 8520.02, Public Key Infrastructure (PKI) and Public Key (PK) Enabling, 24 May 2011.

q. DoDI 8551.01, Ports, Protocols, and Services Management (PPSM), 27 July 2017.

r. DoDI 8580.1, Information Assurance (IA) in the Defense Acquisition System, 9 July 2004.

s. DoDI 8581.01, Information Assurance (IA) Policy for Space Systems Used by the Department of Defense, 8 June 2010.

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

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

v. Federal Information Processing Standards Publications (FIPS PUB)-199, February 2004.

w. Committee on National Security Systems Policy CNSSP No. 11, 10 June 2013.

x. Office of the Chief of Naval Operations OPNAV INST 5239.1C, Navy Information Assurance (IA)

Program, 20 Aug 08.

y. SECNAV M-5239.1, Department of the Navy Information Assurance Program; Information Assurance

Manual, 1 November 2005.

z. SECNAVINST 5230.15, Information Management/Information Technology Policy for Fielding of

Commercial Off the Shelf Software, 10 April 2009.

aa. SECNAVINST 5239.3C, Department of the Navy Cybersecurity Policy, 2 May 2016.

bb. SECNAVINST 5239.19A, Department of the Navy Computer Network Incident Response and Reporting

Requirements, 4 September 2019.

cc. The National Security Act of 1947.

dd. Title 40/Clinger-Cohen Act.

ee. Title 44/ Federal Information Security Management Act.

ff. National Institute of Standards and Technology Special Publication 800-53, Security and Privacy Controls for Federal Information Systems and Organizations, Revision 4, April 2013 (Updated 22 Jan 2015).

3.3 DETAILED REQUIREMENTS

DISTRIBUTION STATEMENT A: PAO APPROVAL NOT ESTABLISHED TO DATE. Requests shall be referred to the Naval Air

3.3.1 Technical Performance Requirements

Individual Task Orders will specify specific products and services to be delivered. The sections below provide additional definition of the range and types of tasking that the contractor may receive via Task Orders. Each Task Order will include a Statement of Work (SOW), related DD Form 1423, and Contract Data Requirements List (CDRL) for data deliverables. The CDRLs will define the required format, delivery requirements, periodicity, and other requirements for all data deliverables. Task order requirements may require contractor non-local travel (both domestic and foreign, including aboard Government ships-at-sea, aboard Government aircraft). The Government to will not require the contractor to perform as both the requirements developer and acceptance tester for any product.

3.3.2 Systems Integration

The contractor shall perform system integration relative to NAWCWD aircraft…