Attachment 1 SOW DRAFT.pdf

STATEMENT OF WORK FOR

CRISIS RESPONSE AND INTEROPERABLE COMMAND, CONTROL,

COMMUNICATIONS, COMPUTERS, COMBAT ELECTRONIC SYSTEMS

Scope.

The Naval Air Warfare Center Aircraft Division (NAWCAD) Webster Outlying Field (WOLF)

Special Communications Mission Solutions (SCMS) Division provides full spectrum Command, Control, Communications, Computers, Combat Systems, Intelligence, Surveillance, and

Reconnaissance (C5ISR) systems engineering solutions to the warfighter. From requirements definition through sustainment (cradle-to-grave), SCMS Division solutions provide critical interoperability, supportability, and connectivity among communication systems, subsystems, components, and equipment. The SCMS Division leads diverse customer-driven projects that are rapid in nature and vary in duration. Multiple projects are concurrently deployed and new projects are continuously added. The SCMS Division, as the organic Lead Systems Integrator, (oLSI) receives funds as a Working Capital Fund (WCF) organization from a broad range of

Department of Defense (DoD) and non-DoD customers to provide best value C5ISR solutions to on-the-ground end users, including joint forces commands and disaster recovery/first responders.

Projects generally follow the SCMS Systems Engineering (SE) and Project Management (PM) framework Standard Work Packages (SWPs) (Section J, Attachments X and Y) and are tailored based on unique project requirements.

The purpose of this Statement of Work (SOW) is to develop and provide a full range of Crisis

Response and Interoperable Command, Control, Communications, Computers, Combat

Electronic Systems (CRIC-ES) solutions and products to facilitate communications and knowledge transfer at crisis locations worldwide. This includes supporting the operational requirements of the current CRIC-ES developed systems, modifications and enhancements for these systems, and developing and maintaining solutions and products for multiple customers; to include, Naval Air Systems Command (NAVAIR) and Non-NAVAIR.

Applicable documents.

The following documents and document sources are provided for reference. The SCMS Division requirement to provide C5ISR interoperability among U.S. military and U.S. civilians may dictate an adherence to a wide variety of specifications and standards. DoD systems shall adhere to the Joint Technical Architecture (JTA) 2.0 Standards. Non-DoD systems may be governed by numerous commercial, national, or international standards. The documents listed below are presented only as representative sources of the technological interface details that may be required during contract performance. Likewise, the documentation listed is not all-inclusive but represents the types of information that may be necessary to perform the work. Each Task Order

(TO) will provide additional details if necessary. The document version applicable to tasking will be the most current published document at the time of TO award.

2.1 Department of Defense (DoD) specifications.

2.1.1 DoDM 5220.22, National Industrial Security Program Operating Manual (NISPOM), 18 May 2016.

2.1.2 SECNAV M-5510.36B, Department of the Navy, Information Security Program, 12 Jul

2019.

2.1.3 DoDI 5200.48 Controlled Unclassified Information (CUI), 6 Mar 2020.

2.1.4 DoDD 5400.07, DoD Freedom of Information Act (FOIA) Program, 5 Apr 2019.

2.1.5 DoDI 5230.24, Distribution Statements on Technical Documents, Change 3, 15 Oct

2018.

2.1.6 SECNAV M-5510.30C, Department of the Navy Personnel Security Program, 24 Jan

2020.

2.1.7 OPNAVINST 3440.17A, Navy Installation Emergency Management Program, 1 Aug

2014.

2.2 Other Government documents.

2.2.1 SCMS Division Research, Development, Test, & Evaluation Network (RDT&E)

Standard Operating Procedures (SOP).

2.2.2 National Institute of Standards and Technology (NIST) Special Publication (SP), 800-

XX.

2.2.3 National Security Decision Directive 298, Public Law 100-235, Section 3(d)(4).

2.2.4 Project Management (PM) framework Standard Work Packages (SWP)

2.2.5 SCMS Systems Engineering Management Plan (SEMP)

2.3 Industry documents.

2.3.1 Department of Defense Joint Technical Architecture (JTA).

2.3.2 International Traffic and Arms Regulations (ITAR).

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 of Top Secret as specified on DD-254 (Attachment X). The current operating environment required for this Contract includes:

Microsoft Windows 2016 or greater

Microsoft Project 2016 or greater

Microsoft Office Professional Plus 2016 or greater

Adobe Acrobat XI (Reader)

Internet access

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 Local Area Network (LAN) communications with the SCMS

Division. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with the SCMS Division during working hours whether at

Contractor work site or on travel.

3.1.2 Work location, facilities, and telework.

3.1.2.1 Work location. Approximately 28% of work will be performed at Government site and

72% of work to be performed at contractor site. Government site includes WOLF St. Inigoes, MD.

3.1.2.1.1 Government site requirements. Contractors performing support on Government site will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, and network access including web servers and applicable databases or other applications necessary to carry out assigned tasks.

3.1.2.1.2 Contractor site requirements. The Contractor shall provide sufficient industrial space, for the receipt, storage, inventory and shipment of equipment associated with assigned projects.

Historically, the space required to meet SOW requirements has been no less than 30,000 square feet. Additionally, the space shall be equipped with heating, ventilation and air conditioning

(HVAC) systems capable of sustaining a controlled environment consistent with the storage, assembly and operation of electronic equipment. The space shall be configured to meet requirements for receiving, material receipt inspection, storage awaiting build up, integration and testing and storage of completed systems. The space shall be equipped to protect Government

Property and shall be located within 50 driving miles of Naval Air Warfare Center – Aircraft

Division (NAWCAD) Webster Outlying Field (WOLF), St. Inigoes, MD. The Government will not have desk occupancy at the location and will not take possession of the facility at contract termination.

3.1.2.2 Reserved.

3.1.2.3 Telework. The Contractor, upon notification to, and concurrence from, the Contracting

Officer's Representative (COR) that the employees' work tasking is eligible for telework, may utilize alternate worksites/locations and telework to support continued performance of its contract In Accordance With (IAW) company policy. Contractor discretion is required when making alternate worksite and telework decisions based upon the nature of support provided by the employees. In the event telework is utilized, the Contractor remains responsible for performance, and compliance with any applicable cost accounting standards and contract cost principles / procedures.

3.1.3 Contract Status Reporting. The Contractor shall provide the following documentation.

3.1.3.1 Monthly progress and financial status report. The Contractor shall provide a progress and financial status report IAW the Contract Data Requirement List (CDRL). The report shall include work accomplished since submittal of the last report, both monthly and cumulative work hour labor costs expended by labor category and material and travel costs. (CDRL A001)

3.1.3.2 Financial Progress Report. (CDRL A002)

3.1.3.3 Contractor’s Personnel Roster/Workforce Report. (CDRL A003)

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

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 eight and a half (8.5) hours (including a thirty-minute lunch break), from 0730 to 1600 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 and end as late as 1800 Monday – Friday.

3.1.4.1.1 CWS. CWS is an alternative work schedule to the traditional five (5) eight and a half

(8.5) hour workdays (which includes a thirty-minute lunch break) worked per week. Under a

CWS schedule, an employee completes the following schedule within a two-week period of time: eight (8) weekdays are worked at nine and a half (9.5) hours each (which includes a thirty-minute lunch break), one (1) weekday is alternately worked as eight and a half (8.5) hours

(which includes a thirty-minute lunch break), and one (1) weekday is not worked by the employee. The result is eighty (80) hours worked every two (2) weeks, with forty-four (44) work hours one (1) week and thirty-six (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 COR/Alternate Contracting Officer’s Representative (ACOR).

3.1.4.1.2 Holidays. The Government observes the federal holidays identified on the Office of

Personnel Management (OPM) website: https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/#url=Overview. With the exception of the events in section 3.1.4.1.3 below, the Contractor is permitted to observe federal holidays IAW 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 (KO) must concur with any determination that work being performed by contractor personnel is mission essential.

3.1.5 Other Direct Costs (ODCs). Operations and Maintenance (O&M); Procurement

(PROC); WCF; Research, Development, Testing & Evaluation (RDT&E); Non-DoD; and

Foreign Military Sales (FMS).

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 required. Temporary travel locations include CONUS and OCONUS locations to include: Alaska, Bahrain, Canada, Germany, Guam, Hawaii, Japan, Puerto Rico, U.S. Territories, United Kingdom, and South

Korea. Possible travel locations include those that are within the United Stated Central

Command (USCENTCOM) Area of Responsibility (AOR). This list is not all inclusive as locations may change over the life of the Contract.

https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/#url=Overview https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/#url=Overview

3.1.5.1.1 The COR/ACOR shall approve all travel performed in support of this Contract prior to the commencement of the travel and shall result in a trip report. (CDRL A004)

3.1.5.1.2 Synchronized Pre-Deployment and Operational Tracker (SPOT). The Contractor may travel in USCENTCOM AOR locations. IAW Clauses 252.225-7040 and 5152.225-5908, SPOT enables the validation of Contractors Authorized to Accompany the Force (CAAF), their authorization and eligibility for access to specific DoD facilities, and their eligibility for specific

Government-Furnished Support (GFS). The Contractor shall initiate a Letter of Authorization

(LOA) for each prospective traveler. The Contractor shall use the SPOT link

(https://spot.dmdc.mil/privacy.aspx) to enter and maintain data with respect to traveling/deployed personnel and to generate LOA.

3.1.5.1.3 LOA. The Contracting Officer will provide the LOA for official travel OCONUS, when applicable, supporting the Contract. The LOA will identify local authorizations, privileges, etc.

as specified by DoD requirements. All defense contractors working under this Contract shall carry an LOA, when applicable, with them at all times while deployed OCONUS.

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 a Material Inspection and Receiving Report (DD

Form 250). Material costs may include general and administrative expenses but shall not include profit/fee. (CDRL A005)

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

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.

The Contractor’s overall transition-out strategy shall be built around maintaining the mission of the SCMS Division with minimal impact, not only in terms of timeliness of performance but also 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 IAW CDRL A006.

̶ Work turnover. The Contractor shall provide a plan of action to effectively transfer tasked work that is in process at the expiration or termination of the Contract to the successor company and establish and maintain effective communication with the incoming Contractor or Government personnel for the period of transition via weekly status meetings.

̶ Quality Assurance (QA). The Contractor shall provide a plan of action to ensure continuation of quality review processes during the transition period to the successor company.

̶ Risk mitigation strategies. The Contractor shall provide a plan of action to mitigate contract performance risks (quality and schedule) encountered during the transition period.

̶ 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 Technical Direction Letters (TDLs). When necessary, technical direction or clarification concerning the details of specific tasks set forth in the Contract and the TOs will be given through issuance of written TDLs. TDLs will not, in any manner, alter the scope of the

Contract or TO. For further direction see NAVAIR Clause 5252.242-9502 Technical Direction

(Variation) in Section H of the Contract. The Contractor shall prepare and deliver a COR

Management Report for TDLs IAW CDRL A001.

3.1.10 Vehicles. The Contractor may be required to transport Government-owned systems/subsystems on a daily basis. Contractor personnel may also be required to operate

Government-owned and/or Government-leased vehicles in the performance of this Contract.

3.1.10.1 Contractor-provided vehicles. The Contractor shall be responsible for transportation of equipment in support of this Contract. The cost of material transport vehicles supporting SOW requirements for the Contractor will not be considered as an allowable direct cost in the performance of the Contract.

3.1.10.2 Government-provided vehicles. The Contractor shall be required, as defined at the TO level, to operate Government-owned or leased vehicles in performance of the Contract.

Government-owned or leased vehicles that the Contractor may use includes, but is not limited to, general purpose passenger carrying vehicles, special-purpose (tactical) vehicles, and SCMS

Division authorized vehicles. All vehicles shall be operated IAW NAVAIR and site-specific processes and requirements. In general, there is no need for specialized licenses; however, if a requirement is identified in a specific TO, there will be time allotted for individuals to obtain the necessary licensing. The Contractor shall report any damage observed on the vehicle/equipment, and shall notify the Government Project Lead (GPL) and COR of any need for service or repair of the Government-owned or leased vehicles. When operating these vehicles, the Contractor shall ensure: possession of a current and valid operator’s license for all vehicles; compliance with all state, federal, and host nation laws pertaining to operating motor vehicles; compliance with NAVAIR policies when operating a vehicle (e.g., no cell phone use, stopping at runway crossings, etc.); use of the most cost-effective means to fuel vehicles; and operation of the vehicles in a safe manner and IAW the vehicle/equipment user/operator manual.

3.1.10.3 If the Contractor is involved in an accident while operating a Government-owned or leased vehicle, they shall notify the GPL, the Procuring Contracting Officer (PCO), and the COR with a verbal report within twenty-four (24) hours and shall provide an accident report within forty-eight (48) hours. (CDRL A007)

3.1.10.4 When operating the vehicle, the Contractor shall be responsible for any costs associated with violations such as speeding tickets, parking tickets, reckless driving, and any damage caused to the vehicle.

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.

Unclassified: All contractor personnel must be eligible to perform Non-Critical Sensitive work as defined by SECNAV M-5510.30C. All contractor personnel are required to have a favorably adjudicated Tier-3 investigation from the Office of Personnel Management (OPM). The

Contractor shall submit a request for personnel security investigation to the Government Security

Office. The Government Security Office shall initiate the contractor employee's Electronic

Questionnaire for Investigations Processing (eQIP) and shall perform a preliminary screening of the contractor employee'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 employee access to Government facilities and information and may prohibit the contractor employee from performance of sensitive duties for failure to provide requested information or when derogatory or adverse information is present on the contractor employee'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 (CUI) and to control distribution of CUI IAW DoDM 5220.22, National Industrial Security Program Operating Manual

(NISPOM) codifying 32 Code of Federal Regulations Part 117, NISPOM Rule and SECNAV M-

5510.36B, Department of the Navy, Information Security Program. All contractor facilities shall provide an appropriate means of storage for CUI and materials. All CUI shall be appropriately identified and marked IAW DoD Instruction 5200.48, Controlled Unclassified Information

(CUI).

CUI including legacy For Official Use Only (FOUO) information and Covered Defense

Information (CDI) (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 DoD Instruction

5200.48, Controlled Unclassified Information (CUI) available at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF.

Any product containing CDI 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.

All controlled unclassified technical information shall be appropriately identified and marked with the following distribution statement(s):

Distribution Statement B–F (as appropriate): Distribution authorized to the Department of

Defense and U.S. DoD contractors only (Critical Technology) (Date). Other requests shall be referred to: Commander, Naval Air Systems Command, Attn: SCMS Division, B8185 Unit 11, 17100 Webster Field Road, St. Inigoes, MD 20684-4009.

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 Top Secret facility level, with a safeguarding level of Top Secret.

The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated IAW DoDM 5220.22, National Industrial Security Program

Operating Manual (NISPOM). 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 IAW the appropriate designation

(CUI; legacy FOUO; CDI). Distribution is authorized to the Requiring Office's Organization and supported Activity only. Other requests for deliverables under this Contract shall be referred to the COR of this Contract for approval.

CUI including legacy FOUO and CDI (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

DoD Instruction 5200.48, Controlled Unclassified Information (CUI) available at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF.

Any product containing CDI 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.1 All personnel shall have the appropriate DoD Security Clearance Level or Interim

Clearance IAW the chart below.

LABOR CATEGORY

DoD SECURITY

CLEARANCE LEVEL

(INTERIM CLEARANCE

ACCEPTABLE)

REQUIRED DAYS AFTER

ISSUANCE OF TO

Computer Network Support Specialists, Journeyman Secret Ninety (90) Days

Computer Network Support Specialists, Senior Secret Ninety (90) Days

Computer Systems Analysts, Journeyman Secret Ninety (90) Days

Drafter/CAD Operator II (SCA) Secret Ninety (90) Days

Drafter/CAD Operator III (SCA) Secret Ninety (90) Days

Drafter/CAD Operator IV (SCA) Secret Ninety (90) Days

Electrical Engineers, Journeyman Secret Ninety (90) Days

Electrician (SCA) Secret Ninety (90) Days

LABOR CATEGORY

DoD SECURITY

CLEARANCE LEVEL

(INTERIM CLEARANCE

ACCEPTABLE)

REQUIRED DAYS AFTER

ISSUANCE OF TO

Engineering Technician I (SCA) Secret Ninety (90) Days

Engineering Technician II (SCA) Secret Ninety (90) Days

Engineering Technician III (SCA) Secret Ninety (90) Days

Engineering Technician IV (SCA) Secret Ninety (90) Days

Financial Specialist, Journeyman Secret Ninety (90) Days

First-Line Supervisors of Mechanics, Installers, and Repairers, Journeyman

(KEY)

Top Secret

Ninety (90) Days (Secret acceptable for eighteen (18) months after issuance pending final Top Secret clearance)

First-Line Supervisors of Mechanics, Installers, and Repairers, Journeyman Secret Ninety (90) Days

General and Operations Managers, Journeyman (Project Manager) Secret Ninety (90) Days

General and Operations Managers, Journeyman (Project Manager) (KEY) Top Secret

Ninety (90) Days (Secret acceptable for eighteen (18) months after issuance pending final Top Secret clearance)

General and Operations Managers, Senior

(Program Manager) (KEY) Top Secret

Ninety (90) Days (Secret acceptable for eighteen (18) months after issuance pending final Top Secret clearance)

General Clerk II (SCA) Secret Ninety (90) Days

Logisticians, Journeyman Secret Ninety (90) Days

Management Analysts, Junior None Ninety (90) Days

Management Analysts, Journeyman Secret Ninety (90) Days

Management Analysts, Senior Secret Ninety (90) Days

Material Handling Laborer (SCA) Secret Ninety (90) Days

Mechanical Engineers, Journeyman Secret Ninety (90) Days

Sheet-Metal Worker, Maintenance (SCA) Secret Ninety (90) Days

Stock Clerk (SCA) Secret Ninety (90) Days

Supply Technician (SCA) Secret Ninety (90) Days

Technical Writer II (SCA) Secret Ninety (90) Days

Telecommunications Equipment Installers and Repairers, Except Line Installers, Junior

Secret Ninety (90) Days

Telecommunications Equipment Installers and Repairers, Except Line Installers, Journeyman

Secret Ninety (90) Days

Telecommunications Equipment Installers and Repairers, Except Line Installers, Senior

Secret Ninety (90) Days

DoD SECURITY

CLEARANCE LEVEL

(INTERIM CLEARANCE

ACCEPTABLE)

REQUIRED DAYS AFTER

ISSUANCE OF TO

Telecommunications Mechanic I (SCA) Secret Ninety (90) Days

Telecommunications Mechanic II (SCA) Secret Ninety (90) Days

Training and Development Specialists, Journeyman Secret Ninety (90) Days

Warehouse Specialist (SCA) Secret Ninety (90) Days

Word Processor II (SCA) Secret Ninety (90) Days

Word Processor III (SCA) Secret Ninety (90) Days

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

Authorization Access Request Navy (SAAR-N).

3.2.3.1 SAAR-N. All contractor personnel requiring access to Government IT systems shall have an approved SAAR-N Form OPNAV 5239/14 Rev Sep 2011 on file and complete required

Annual Information Awareness Training. New employees must submit their SAAR-N forms within thirty (30) days of their first day of work. Instructions for processing the SAAR-N forms are available at:

https://www.cnic.navy.mil/content/dam/cnic/hq/pdfs/Homepage/Command%20and%20Staff/OP

NAV_5239_14_Rev_9_2011.pdf. SAAR-N forms shall be submitted to the COR, Government

TPOC, or to the assigned Government Trusted Associate Sponsorship System (TASS) Trusted

Associate.

3.2.3.2 CACs/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 facility guidance. All CACs and identification badges issued to contractor employees shall be returned to the Government Trusted Agent (TA) following completion of the Contract, relocation, or termination of an employee, or upon request from COR/PCO. 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 facility guidance.

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 legacy FOUO or

CUI. Distribution is authorized to the Requiring Office's Organization and supported Activity only. Other requests for deliverables under this Contract shall be referred to the COR of this

Contract for approval.

3.2.3.3.1 The Contractor will require access to:

‒ Communications Security (COMSEC) Information, Restricted data, Non-Sensitive

Compartmented Information (Non-SCI), North Atlantic Treaty Organization (NATO)

Information, Alternative Compensatory Control Measures (ACCM) Information, CUI, Secret

Internet Protocol Router Network (SIPRNet), Secure Terminal Equipment (STE), and Secure

Fax Access.

3.2.3.3.2 In performing this Contract, the Contractor will:

‒ Receive, store, and generate classified information or material; fabricate, modify, or store classified hardware; have access to U.S. classified information outside the U.S., Puerto Rico, U.S. possessions and trust territories (Contractor authorized access to Classified Information at: Kadena Air Base, Okinawa, Japan; United States Pacific Command (USPACOM) AOR;

United States European Command (USEUCOM) AOR; USCENTCOM AOR; U.S. Army

Panzer Kaserne, Stuttgart, Germany; U.S. Army Kleber Kaserne and Kaiserslautern, Germany); be authorized to use the services of Defense Technical Information Center

(DTIC) or other secondary distribution center; require a COMSEC account; have a Tempest requirement (not releasable to Contractor employees who have not received a final security clearance at the appropriate level); have Operations Security (OPSEC) requirements; be authorized to use Defense Courier Service; and, receive, store, or generate CUI.

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 CUI and to control distribution of CUI

IAW DoDM 5220.22, National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulations Part 117, NISPOM Rule and SECNAV M-5510.36B, Department of the Navy, Information Security Program. If the work is performed at the

Government's facility, the Contractor shall comply with that facility’s security procedures and controls.

3.2.4.1 Marking. All information generated by the Contractor shall be properly marked.

Legacy FOUO information generated and/or provided under this Contract shall be marked IAW

DoDI 5200.48. Technical information shall also be marked with appropriate Distribution

Statements and Export Control warnings IAW DoDI 5230.24 and program Security

Classification Guidance.

3.2.4.2 Public Release. Any CUI pertaining to this Contract shall not be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by appropriate U.S. Government authority. Proposed public releases shall be submitted for approval prior to release through: NAWCAD WOLF (SCMS)

Div., 17100 Webster Field Road, B8185, St. Inigoes, MD 20684-4009, Attn: COR.

3.2.4.3 Loss, compromise, and/or electronic spillage of classified information or CUI. All instances of loss, compromise, and electronic spillage of classified information or CUI shall be reported to the COR, TPOC, and Government Security Office within twenty-four (24) hours of the incident occurring.

3.2.5 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 (IA) and COMSEC. The

OPSEC program shall be IAW 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; and protect sensitive unclassified information and activities that could compromise classified information or operations or degrade the planning and execution of operations performed by the Requirements

Owner and Contractor in support of the mission. (CDRL A008)

3.2.6 Antiterrorism Force Protection and Emergency Management. The work performed on this Contract is not Emergency Essential IAW 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 One) and Active Shooter training.

3.2.7 IT access. All Contractor personnel with access to unclassified information systems, including email, shall have, at a minimum, a favorable National Agency Check (NAC). The

Contractor shall coordinate all IT network or website access requirements after award of the

Contract with the COR and shall be IAW the latest DoD policies and the SCMS Division RDT&E

Network SOP. (Attachment 14)

3.2.7.1 Contractor facility IT access. Employees requiring access to various DoD IT network or network resources from a Contractor facility are mandated by DoD policy to use Government-approved PKIs along with an appropriate hard key (i.e., Smart Card). Defense Information

Systems Agency (DISA) will be the primary source for these certificates.

3.2.7.2 Government facility IT access. Contractor-owned equipment will be permitted connection to NAVAIR/DoD networks in order to carry out the performance of this Contract.

Upon Contract award, the Contractor shall provide all Government site employees with laptop/desktop computers to conduct daily work that meet all of the hardware, software, and standard architecture set forth in the SCMS Division RDT&E Network SOP. Computers shall have sufficient memory, hard disk space, a network interface card, CAC readers, and the capability of running a full range of standard software including current versions of Microsoft

Windows Operating System and Microsoft Office Professional. Technical support from the manufacturer of contractor-owned hardware and software must be available. All contractor-owned desktop and laptop computers provided for Government facility access will be submitted for re-imaging and validation scanning prior to allowing connection to the SCMS RDT&E LAN.

Approval is required by COR and SCMS Network Information Site Security Officer prior to connection. All connected desktops and laptops will be subject to continuous monitoring.

3.2.7.3 Navy Marine Corps Intranet (NMCI). Access to NMCI is not anticipated for this

Contract. If determined to be necessary, the Government will provide all NMCI services, to include hardware, software, and IT support necessary for the performance of this Contract.

Coordination of these services is to be conducted through the COR.

3.3 Detailed Support Requirements.

3.3.1 Production, Fabrication, and Integration Services.

3.3.1(a) (O&M) Provide production, fabrication, and integration services support to include preliminary and detailed design efforts, project plan development, program planning, and site surveys for CRIC-ES related technologies and systems during the O&M phase of the project life cycle. Applicable to paragraphs 3.3.1.1 – 3.3.1.11.

3.3.1(b) (PROC) Provide production, fabrication, and integration services support to include preliminary and detailed design efforts, project plan development, program planning, and site surveys for CRIC-ES related technologies and systems in the production and modernization phases of the project life cycle. Applicable to paragraphs 3.3.1.1 – 3.3.1.11.

3.3.1(c) (WCF) Provide production, fabrication, and integration services support to include preliminary and detailed design efforts, project plan development, program planning, and site surveys for CRIC-ES related technologies and systems throughout all phases of the project life cycle. Applicable to paragraphs 3.3.1.1 – 3.3.1.11.

3.3.1(d) (RDT&E) Provide production, fabrication, and integration services support to include preliminary and detailed design efforts, project plan development, program planning, and site surveys for CRIC-ES related technologies and systems within the RDT&E phase of the project life cycle. Applicable to paragraphs 3.3.1.1 – 3.3.1.11.

3.3.1(e) (Non-DoD) Provide production, fabrication, and integration services support to include preliminary and detailed design efforts, project plan development, program planning, and site surveys for CRIC-ES related technologies and systems throughout all phases of the project life cycle. Applicable to paragraphs 3.3.1.1 – 3.3.1.11.

3.3.1(f) (FMS) Provide production, fabrication, and integration services support to include preliminary and detailed design efforts, project plan development, program planning, and site surveys for CRIC-ES related technologies and systems throughout all phases of the project life cycle to support FMS customers. Applicable to paragraphs 3.3.1.1 – 3.3.1.11.

3.3.1.1 The Contractor shall support the fabrication of cables and electronic system (ES) equipment into required enclosures and housing including equipment racks, cabinets, supporting fixtures, and bases.

3.3.1.2 The Contractor shall assist in soldering, wrapping, harnessing, and wiring to complete the fabrication of cable assemblies, peripherals, interfaces, and components.

3.3.1.3 The Contractor shall support the preparation of Material Equipment Lists (MELs) identifying all equipment required for specific production, fabrication, and integration requirements. (CDRL A011)

3.3.1.4 The Contractor shall support the completion and delivery of completed ES systems, subsystems, and components and associated specifications. (CDRL A012)

3.3.1.5 The Contractor shall support the review and fabrication of ES enclosures and housing structures considering layouts, space, structure, power, security, and the physical and environmental considerations of required installation sites by surveying operational requirements and documenting conceptual, design, and integration alternatives. (CDRL A020)

3.3.1.6 The Contractor shall support the design, integration, and testing of the physical and electrical security of both the ES and the enclosures and housing.

3.3.1.7 The Contractor shall assist in fabrication of electrical and mechanical connection for the production of breadboards, mock-ups, and limited prototype systems.

3.3.1.8 The Contractor shall support the development, production, and manufacturing of ES, systems, subsystems, components, peripherals, and equipment.

3.3.1.9 The Contractor shall support the development of production reports to document procurement, fabrication, and assemblies of all ES and enclosure and housing.

3.3.1.10 The Contractor shall support the preparation of drawings ranging from guidance sketches to detailed electrical and mechanical assemblies. (CDRL A020)

3.3.1.11 The Contractor shall support multimedia and Computer Aided Design (CAD) development efforts to include, but not be limited to, film production/editing, graphics, media

(analog or digital) management/duplication/storage, internet services, general audio-visual production, three-dimensional (3-D) concept visualization, and digital photography. (CDRL

A020)

3.3.2 Logistics and Sustainment Services.

3.3.2(a) (O&M) Provide logistics and sustainment services support to include preliminary and detailed design efforts, project plan development, program planning, and site surveys for CRIC-

ES related technologies and systems during the O&M phase of the project life cycle. Applicable to paragraphs 3.3.2.1 – 3.3.2.15

3.3.2(b) (PROC) Provide logistics and sustainment services support to include preliminary and detailed design efforts, project plan development, program planning, and site surveys for CRIC-

ES related technologies and systems in the production and modernization phases of the project life cycle. Applicable to paragraphs 3.3.2.1 – 3.3.2.15.

3.3.2(c) (WCF) Provide logistics and sustainment services support to include preliminary and detailed design efforts, project plan development, program planning, and site surveys for CRIC-

ES related technologies and systems throughout all phases of the project life cycle. Applicable to paragraphs 3.3.2.1 – 3.3.2.15.

3.3.2(d) (RDT&E) Provide logistics and sustainment services support to include preliminary and detailed design efforts, project plan development, program planning, and site surveys for

CRIC-ES related technologies and systems within the RDT&E phase of the project life cycle.

Applicable to paragraphs 3.3.2.1 – 3.3.2.15.

3.3.2(e) (Non-DoD) Provide logistics and sustainment services support to include preliminary and detailed design efforts, project plan development, program planning, and site surveys for

CRIC-ES related technologies and systems throughout all phases of the project life cycle.

Applicable to paragraphs 3.3.2.1 – 3.3.2.15.

3.3.2(f) (FMS) Provide production, fabrication, and integration services support to include preliminary and detailed design efforts, project plan development, program planning, and site surveys for CRIC-ES related technologies and systems throughout all phases of the project life cycle to support FMS customers. Applicable to paragraphs 3.3.2.1 – 3.3.2.15.

3.3.2.1.1 The Contractor shall provide support by assisting with technical recommendations for possible services, equipment, material, and potential sources for systems specific requirements.

(CDRL A011)

3.3.2.1.2 The Contractor shall assist in maintaining a list of required parts and equipment items that are to be procured and support the preparation of procurement documentation. (CDRL

A011)

3.3.2.2 The Contractor shall support configuration management and baselines of products, hardware, software, drawings, and documentation. (CDRL A017)

3.3.2.3 The Contractor shall assist with providing on-site training of operators at both CONUS and OCONUS locations, supporting training documentation development or updates, and conduct formal classroom training. (CDRL A018)

3.3.2.4 The Contractor shall assist in documenting Engineering Change Proposals (ECPs) in the Government-provided configuration management system and by participating in

Configuration Control Boards (CCBs), Systems Change Requests (SCRs), and Engineering

Review Boards (ERBs). (CDRL A019)

3.3.2.5 The Contractor shall support planning for performance based Integrated Logistics

Support (ILS) of new, existing, or modified ES, including but not limited to, reliability, maintainability, and availability as applied to the following: maintenance planning, supply support, support equipment, trend analysis, technical data, stakeholders, computer resources, training, packing, handling, shipping, transportation, and facilities. (CDRL A021)

3.3.2.6 The Contractor shall support technical assists by developing, reviewing, analyzing or updating service maintenance support plans that identify provisioning parts lists of spare and repair parts considering geography, supportability, interoperability, availability, procurement lead times, inventorying, and stocking requirements. (CDRL A022)

3.3.2.7 The Contractor shall support the development, review, analysis, and updating of operational and maintenance manuals, operator training manuals, and curricula. (CDRL A023)

3.3.2.8 The Contractor shall support the development of ECPs based on changes recognized by users, lessons learned, field experience, and technology refreshment. (CDRL A024)

3.3.2.9 The Contractor shall assist in documenting audits of configurations including verification and validation (VER/VAL) and Physical Configuration Audits (PCAs). (CDRL

A025)

3.3.2.10 The Contractor shall perform corrective action maintenance, installation, configuration, and routine preventative maintenance; troubleshoot problems; and expedite repair of fielded ES by collecting failed customer equipment and managing its transportation to Government maintenance/repair facilities or back to the manufacturer as appropriate.

3.3.2.11 The Contractor shall support risk mitigation by monitoring, replacing, and documenting

Reliability, Availability, and Maintainability (RAM) data and Diminishing Manufacturer

Sources and Material Shortages (DMSMS); analyzing failures to determine root causes; and documenting corrective actions. (CDRL A026)

3.3.2.12 The Contractor shall provide remote and local troubleshooting and repair of fielded ES including system operation, capabilities, functions, limitation, and interfaces.

3.3.2.13 The Contractor shall assist with the activities related to material and equipment procurement and control.

3.3.2.13.1 The Contractor shall support the establishment and maintenance of a system for tracking, inventorying, temporarily storing, and managing parts and equipment required for integration, test, upgrade, and repair of systems.

3.3.2.13.2 The Contractor shall assist with entering, updating, and printing requisition data from the SCMS RDT&E LAN applications and tracking contractor procured status from procurement initiation to delivery.

3.3.2.13.3 The Contractor shall support the utilization of the SCMS RDT&E LAN applications to maintain contractor purchased project material tracking reports, identify delinquent material deliveries, and notify the GPL of discrepancies between schedules and delivery.

3.3.2.13.4 The Contractor shall support the establishment and maintenance system for tracking, inventorying, temporarily storing, and managing parts and equipment.

3.3.2.13.5 Contractor shall assist with storing material and equipment and establish and maintain a system for inventorying.

3.3.2.14 The Contractor shall support the analyses, information gathering, and recommendations concerning use and integration of National Stock Numbers (NSNs) and non-NSN hardware materials for contractor ODC purchases. (CDRL A011)

3.3.2.15 The Contractor shall support shipping of equipment, systems, subsystems, and components and comply with all Government regulations for shipments within the U.S. and abroad IAW with Government provided schedules, including providing a documented process for exporting COMSEC equipment IAW the ITAR. (CDRL A017)

3.3.3 Design and Analysis.

3.3.3(a) (O&M) Provide design and analysis support to include preliminary and detailed design efforts, project plan development, program planning, and site surveys for CRIC-ES related technologies and systems during the O&M phase of the project life cycle. Applicable to paragraphs 3.3.3.1 – 3.3.3.17.

3.3.3(b) (PROC) Provide design and analysis support to include preliminary and detailed design efforts, project plan development, program planning, and site surveys for CRIC-ES related technologies and systems in the production and modernization phases of the project life cycle.

Applicable to paragraphs 3.3.3.1 – 3.3.3.17.

3.3.3(c) (WCF) Provide design and analysis support to include preliminary and detailed design efforts, project plan development, program planning, and site surveys for CRIC-ES related technologies and systems…