STATEMENT OF WORK FOR

TECHNICAL ENGINEERING SERVICES

Scope.

As the organic Lead Systems Integrator® (oLSI®) for the Naval Air Warfare Center Aircraft Division (NAWCAD), Webster Outlying Field (WOLF) operates under a product-based business model whereby NAWCAD WOLF civilians lead and manage the execution of the requirements for defense weapon systems programs with combined Government-Industry teams. Using this oLSI® approach, the Government maintains control of intellectual property and data rights, enabling WOLF to rapidly adapt solutions to the dynamic needs of the warfighter.

The NAWCAD WOLF Ship & Air Integrated Warfare (SAIW) Division, operating under the oLSI® model, provides technical and engineering services to support the advanced research and development, systems engineering, and life cycle support of electronics, communications, and information systems in response to tasking from the Department of Defense (DoD) and other U.S. Government organizations. These projects directly support multiple major defense acquisition programs, other acquisition category designations, and other defense weapons systems to include, but not be limited to, Command, Control, Communications, Computers, Combat Systems, Cyber, Intelligence, Surveillance, and Reconnaissance (C6ISR) systems, subsystems, and components of strategic and tactical airborne, land-based, mobile, sea-based surface, and sub-surface platforms.

This Statement of Work (SOW) will provide concept and technology development support, system development and design support, system integration and life cycle sustainment, analysis, and technical assessments; technical management support; and cybersecurity support to projects within the SAIW portfolio. The scope of this effort encompasses rapidly-developed engineering designs for end products intended for immediate warfighter operational use.

Applicable Documents.

The documents and document versions applicable to tasking will be the most current published document at the time of this contract award.

2.1 DoD Specifications.

2.1.1 DoD National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulation Part 117, NISPOM Rule.

2.1.2 DoDM 5200.01 Vol. 2, Marking of Classified Information, Change 4, 28 Jul 2020.

2.1.3 SECNAVINST 5510.36B, Department of the Navy Information Security Program, 12 Jul 2019.

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

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

2.1.6 DoDI 5230.24, Distribution Statements on Technical Information, 10 Jan 2023.

2.1.7 SECNAVINST 5510.30C, Department of the Navy Personnel Security Program, 24 Jan 2020.

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

2014.

2.1.9 SECNAVINST 5239.20A, Department of the Navy Cyberspace Information Technology and Cybersecurity Workforce Management and Qualification, 10 Feb 2016.

2.1.10 DoDD 8140.01, Cyberspace Workforce Management, 5 Oct 2020.

2.2 DoD Standards.

2.2.1 MIL-STD-31000B, Technical Data Packages.

2.2.2 DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT) 19 July 2022.

2.2.3 DoDI 8500.01 Cybersecurity Implementation 07 October 2019.

2.3 Other Government Documents.

2.3.1 National Security Decision Directive 298, dated 22 January 1988 Public Law 100-235, Section 3(d)(4).

2.3.2 SAIW Division Operations Manual.

2.3.3 SAIW Division Project Realization Standard Operating Procedure (SOP).

2.3.4 Director of National Intelligence Memorandum 5 May 2017, Access to NATO Information by Intelligence Community (IC) Personnel and Naval Intelligence Security Policy Directive 17-008 Revision.

2.4 Industry Documents.

2.4.1 ANSI/ASQ ISO 9001:2015, American National Standards Institute/American Society for Quality.

2.4.2 Capability Maturity Model Integration (CMMI) Model.

2.4.3 Certified Information Systems Security Professional (CISSP) Common Body of Knowledge (CBK) 15 April 2024.

2.4.4 ISO/IEC/IEEE 15288:2023, Systems and Software Engineering – System Life Cycle Processes 16 May 2023.

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 Secret as specified on the DD Form 254, Contract Security Classification Specification Form (Attachment 03). The current operating environment required for this Task Order (TO) includes:

Microsoft Windows 11 or greater Microsoft Project 2016 or greater Microsoft Office Professional Plus 2016 or greater Adobe Reader Adobe Acrobat Internet access

Flank Speed

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 ensure that all media are virus free when delivered. The Contractor shall be capable of internet and Local Area Network (LAN) communications with the SAIW Division. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with the SAIW Division during working hours whether at contractor work site or on travel.

3.1.2 Work Location, Facilities, and Telework/Remote Work.

3.1.2.1 Work Location. Approximately 26% of work will be performed at Government site and 74% of work to be performed at the contractor site. Government sites include Marine Corps Air Station (MCAS), Yuma, AZ; Marine Corps Base, Oahu, HI; Patuxent River Naval Air Station, Patuxent River, MD; WOLF, St. Inigoes, MD; and MCAS, Cherry Point, NC.

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

3.1.2.1.1.1 Test Beds. The Government will provide test bed facilities, which are equipped and furnished to support C6ISR systems, subsystems, and components of strategic and tactical airborne, land-based, mobile, sea-based surface, and sub-surface platforms.

3.1.2.1.1.2 Sensitive Compartmented Information (SCI) Facility (SCIF). The Government will provide access to a SCIF designed to protect sensitive data from unauthorized access and interception at each respective Government site.

3.1.2.1.2 Contractor Site Requirements. The Contractor shall provide its own support facilities within 50 drivable miles of WOLF, St. Inigoes, MD in order to satisfy the daily support and administrative operations of this TO. The Government will not assume responsibility to retain the facility or take control of the title after the TO is completed. The Contractor shall have occupancy of these facilities by the base year Period of Performance (PoP) start date specified in Section F.

3.1.2.2 Meeting Support. In support of the tasking outlined in this SOW, the Contractor shall have the capability to host and conduct meetings at the classification levels up to Secret with the capacity to support a minimum of 10 persons. The meeting space shall have contractor-furnished telephone and Video Teleconference (VTC) capability as well as sufficient equipment to conduct meetings with presentations including compatible software as required in section 3.1.1. This support shall be provided at the contractor support facilities required in section 3.1.2.1.2, located within 50 drivable miles of WOLF, St. Inigoes, MD.

3.1.2.3 Telework/Remote Work.

The Contractor may allow contractor employees to telework and/or work remotely in accordance with (IAW) the information in section 3.4. The Contractor may utilize alternate worksites/locations to telework and/or work from a remote location to support continued performance of SOW tasks IAW company policy. When using telework and/or remote work, the Contractor remains responsible for TO performance and compliance with any applicable cost accounting standards and contract cost principles/procedures.

Telework is defined as an alternative workplace arrangement under which a position performs the duties and responsibilities of the assigned position and other authorized activities from an approved alternative worksite, but is required to report to the agency’s worksite on a regular and recurring basis. Telework can be either routine or situational. Routine telework is performed from an alternative worksite on regularly scheduled telework day(s), whereas situational telework is authorized on a case-by-case basis as the need arises or when opting for unscheduled telework and may be authorized for routine teleworkers in such circumstances on regularly scheduled in-office days.

Telework eligible positions require routine on-site performance of two days per week. On-site performance may be required outside of routine on-site performance days, and shall be provided when requested by the Contracting Officer’s Representative (COR).

Remote work is an alternative work arrangement that allows for a position to perform official duties at an approved alternative worksite away from an agency worksite, without regularly returning to the agency worksite during each pay period. Remote work can be either local or distant.

Local remote work is defined as a position that does not require regular and recurring on-site performance but includes enough required on-site performance that the position is required to be staffed within 50 drivable miles of NAWCAD WOLF, St. Inigoes, MD.

Distant remote work is defined as a position that does not require regular and recurring on-site performance and is not required to be staffed within 50 drivable miles of NAWCAD WOLF, St.

Inigoes, MD but shall be staffed within the contiguous United States.

In the event that telework tools become unavailable while working off-site, the Contractor shall require positions defined as telework and local remote work to report on-site in order to access the tools required for performance of this TO.

At any time during TO performance, the COR may determine that a position is no longer eligible for telework and/or local remote work by providing a notice 30 calendar days in advance and/or for distant remote telework positions by providing a notice 90 calendar days in advance so the Contractor can address changes needed to support mission requirements.

3.1.2.4 Industrial Space. The Contractor shall provide sufficient industrial support 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 6,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 drivable miles of NAWCAD WOLF, St.

Inigoes, MD. The Government will not have desk occupancy at the location and will not take possession of the facility at TO termination.

3.1.3 TO 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 Requirements 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. (CDRLs A001 and A002)

3.1.3.2 Organizational Conflicts of Interest (OCI) and Non-Disclosure Agreement (NDA) Status Certification. The Contractor shall report OCI Mitigation Plan compliance and compliance status changes. (CDRL A003)

3.1.4 Work schedule to include Compressed Work Schedule (CWS), 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 8.5 hours each day (including a 30-minute lunch break), from 0730 to 1600 each Monday through Friday (except on the legal holidays as 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. Core working hours are from 0900 to 1430 on standard workdays.

3.1.4.1.1 CWS. CWS is an alternative work schedule to the traditional 5 8.5-hour workdays (which includes a 30-minute lunch break) worked per week. Under a CWS schedule, an employee completes the following schedule within a 2-week period of time: 8 weekdays are worked at 9.5 hours each day (which includes a 30-minute lunch break), 1 weekday is alternately worked at 8.5 hours (which includes a 30-minute lunch break), and 1 weekday is not worked by the employee. The result is 80 hours worked every 2 weeks, with 44 work hours 1 week and 36 work hours the other.

The Contractor may allow its employees to work a CWS schedule provided the requirements of this SOW are met. If the Contractor chooses to allow its employees to work a CWS schedule in support of this TO, any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this TO 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 Contracting Officer’s Representative (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). Procurement (PROC); Operations & Maintenance (O&M);

Research, Development, Test & Evaluation (RDT&E); Non-Department of Defense (Non-DoD);

Foreign Military Sales (FMS); and Working Capital Fund (WCF).

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. If required, temporary travel locations include Continental United States (CONUS) and Outside the Continental United States (OCONUS) locations. This list is not all inclusive as locations may change over the life of the TO.

3.1.5.1.1 CONUS. CONUS locations may include travel to: Huntsville, AL; Mobile, AL; Yuma, AZ; Camp Pendleton, CA; Coronado, CA; Fullerton, CA; San Diego, CA; Littleton, CO;

Washington, D.C.; Jacksonville, FL; Mayport, FL; Tampa, FL;; Andrews AFB, MD; St. Louis, MO; Camp Lejeune, NC; Cherry Point (MCAS), NC; Jacksonville, NC; Morehead City, NC;

Buffalo, NY; Dayton, OH; Hood River, OR; Middletown, PA; Dallas, TX; Fort Bliss, TX;

Alexandria, VA; Arlington, VA; Chesapeake, VA; Fairfax, VA; Fredericksburg, VA; Little Creek, VA; Norfolk, VA; Quantico, VA; and Bingen, WA.

3.1.5.1.2 OCONUS. OCONUS locations may include travel to: Manama, Bahrain; Rijeka, Croatia; Stuttgart, Germany; Honolulu, HI; Kaneohe Bay, HI; Al Asad Airbase, Iraq; Baghdad, Iraq; Camp Taij, Iraq; Taranto Province, Italy; Kanoya Air Base, Japan; Sasebo, Japan;

Yokosuka, Japan; Dugm, Oman; Salalah, Oman; Philippines (Manila, Zamboanga and/or Camp Navarro); Krakow, Poland; Baledogle Air Field (Mogadishu), Somalia; and Thailand (Bangkok, Jordan, Pattaya, and/or Phuket); Dubai, UAE; and other countries in Europe, Asia, the Middle East, and Africa in performance of this TO.

The Contractor shall complete travel request(s) IAW CTXT.232-9509, Travel Approval and Reimbursement Procedures (NAVAIR) (OCT 2013). Upon completion of travel, the contractor employee shall complete a trip/travel report. The COR shall approve all travel performed in support of this TO prior to the commencement of the travel and travel shall result in a trip report.

(CDRL A004)

3.1.5.1.3 Synchronized Pre-Deployment & Operational Tracker (SPOT). The Contractor may travel to locations that require the use of SPOT. IAW DFARS clause 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 LOAs.

3.1.5.1.4 LOA. The KO will provide a LOA for official travel OCONUS, when applicable, supporting the TO. The LOA will identify local authorizations, privileges, etc. as specified by DoD requirements. All defense contractors working under this TO shall carry an LOA, when applicable, with them at all times while deployed OCONUS.

3.1.5.2 Material. Incidental material will be required in the performance of this TO, and all incidental material purchases shall be IAW CTXT-242.9520, Procedures and Approvals Required Prior to Incurring Direct Material Costs. All materials not depleted during the performance of this TO shall become Government property upon completion of this TO. The Contractor shall transfer all materials not depleted to the COR by way of a DD Form 250, Material Inspection and Receiving Report. Material costs may include general and administrative expenses but shall not include profit/fee. (CDRL A005)

3.1.6 Subcontractors. Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this TO. All provisions of this SOW shall flow down to subcontractors providing support under this TO. The Contractor shall submit a Small Business Participation Commitment Document (SBPCD). (CDRL A006)

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 actions that give the perception of personal services.

3.1.8 Transition-Out Plan.

The Contractor’s overall transition-out plan shall be built around maintaining the mission of the Division with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. Prior to the termination or expiration of the TO, 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 A007.

̶ 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 TO 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 TO will be given through issuance of written TDLs. TDLs will not, in any manner, alter the scope of the TO. For further direction see HTXT.242-9502, Technical Direction (Variation) in Section H of the TO. The Contractor shall prepare and deliver a COR Management Report for TDLs IAW CDRL A001.

3.1.10 Quality Management. The Contractor shall develop, implement, document, audit and maintain a Quality Management System (QMS) to ensure conformance with contractual requirements and the specific quality and performance requirements issued under this contractual document. At a minimum, the QMS should meet the intent of the American National Standards Institute/American Society for Quality (ANSI/ASQ) ISO 9001:2015 or Society of Automotive Engineers and the European Association of Aerospace Industries AS9100 and/or equivalent governing body. Regardless of the standards that are applied, the Contractor’s quality approach should be clearly defined and recognize the need to focus on quality management principles including customer focus, process approach, improvement, evidence-based decision making and relationship management. Registered QMS (to the International Organization for Standardization (ISO) standards or equivalent governing body) and QMS required internal audit results verifying Contractor’s compliance with the documented processes and procedures, established to execute the Contractor’s work efforts and product delivery, shall be made available to the Government.

(CDRLs A008 and A009)

3.1.11 Process Documentation. These written procedures and work instructions shall be made available to the contractor employees required to perform the specific task. All procedures and work instructions shall be consistent with the Contractor’s QMS. (CDRL A009)

3.1.12 Government Furnished Property (GFP)/Government Furnished Information (GFI). Any GFI listed in this TO will be provided to the Contractor within five days of TO award. Additional GFI such as training and documentation requiring Contractor review, analysis, and updating will be provided throughout the TO PoP. Disposition of GFI will be made at TO completion. The Contractor shall have an approved Property Management System.

3.2 Security.

3.2.1 Citizenship Requirements. Only U.S. citizens may perform under this TO, unless waived by the Government. 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 on the TO.

3.2.2 Investigative Requirements.

Unclassified: All contractor personnel must be eligible to perform Non-Critical Sensitive work as defined by SECNAVINST 5510.30C, Department of the Navy Personnel Security Program.

All contractor personnel are required to have a favorably adjudicated Tier-3 investigation from the 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 TO.

Classified: All contractor personnel shall maintain security clearance eligibility commensurate with the level of classification of the work performed as annotated in the TO's DD Form 254, Contract Security Classification Specification Form. Contractor personnel shall require access to classified information in performance of this TO up to and including Top Secret (TS) facility level, with a safeguarding level of Secret. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated IAW National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulation Part 117, NISPOM Rule. 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 TO.

It is anticipated that approximately 11 Full Time Equivalent (FTE) performing the work defined in the SOW will need to possess TS/SCI access immediately upon the commencement of performance in an appropriately cleared facility. The contract deliverables (including reports, software, and hardware) will not be classified at the SCI level. SCI will be utilized and accessed as part of routine work only.

All Department of the Navy (DON) contractor employees with SCI access must be briefed into North Atlantic Treaty Organization (NATO) Secret access, IAW the Director of National Intelligence Memorandum 5 May 2017, Access to NATO Information by Intelligence Community (IC) Personnel and Naval Intelligence Security Policy Directive 17-008 Revision mandate for NATO information by IC Personnel.

3.2.2.1 Contractor Personnel Labor Category Security Requirements. All personnel shall have the appropriate DoD Security Clearance Level or Interim Clearance IAW the chart below. All personnel not listed in the table below shall have the ability to obtain a Secret DoD Security Clearance or Interim Clearance within 60 business days of Government request.

LABOR CATEGORY

DoD SECURITY

CLEARANCE

LEVEL (INTERIM

CLEARANCE

ACCEPTABLE)

REQUIRED BUSINESS DAYS

AFTER ISSUANCE OF TASK

ORDER

Computer Occupations, All Other (Subject Matter Expert), Journeyman

TS/SCI (1), TS (2),

Secret (All Others) 120 (1), 90 (2), 60 (All Others)

Computer Occupations, All Other (Subject Matter Expert), Senior TS 90

Electrical Engineers, Journeyman Secret 60 Engineers, All Other (Systems Engineer), Junior Secret 60

Engineers, All Other (Systems Engineer), Journeyman

TS (1), Secret (All Others) 90 (1), 60 (All Others)

Engineers, All Other (Systems Engineer), Senior

TS (1), Secret (All Others) 90 (1), 60 (All Others)

Engineers, All Other (Systems Engineer), Senior (Key) TS 90

General and Operations Managers (Program Manager), Senior (Key) TS 90

General and Operations Managers (Project Manager), Journeyman Secret 60

General and Operations Managers (Project Manager), Senior

TS (1), Secret (All Others) 90 (1), 60 (All Others)

General and Operations Managers (Project Manager), Senior (Key) TS/SCI 120

Logisticians, Junior Secret 60

Logisticians, Journeyman Secret 60

Management Analysts (Configuration Management Analyst), Junior Secret 60

Management Analysts (Configuration Management Analyst), Journeyman Secret 60

Management Analysts (Configuration Management Analyst), Senior Secret 60

Mechanical Engineers, Junior Secret 60

Mechanical Engineers, Journeyman Secret 60

Mechanical Engineers, Senior Secret 60

Project Management Specialists, Journeyman TS (1), Secret (3) 90 (1), 60 (3)

Project Management Specialists, Senior TS/SCI (1), TS (1) 120 (1), 90 (1)

Training and Development Specialists, Junior Secret 60

Training and Development Specialists, Journeyman

TS (2), Secret (All Others) 90 (2), 60 (All Others)

Training and Development Specialists, Senior

TS (1), Secret (All

Computer Network Architects, Basic Secret 60

Computer Network Architects, Intermediate

TS/SCI (1), TS (All Others) 120, (1), 90 (All Others)

Computer Network Architects, Advanced (Key and Non-Key) TS 90

Computer Systems Analysts, Basic TS 90

Computer Systems Analysts, Intermediate TS/SCI (3), TS (All Others) 120 (3), 90 (All Others)

Computer Systems Analysts, Advanced (Non-Key)

TS/SCI (1), TS (All Others) 120 (1), 90 (All Others)

Computer Systems Analysts, Advanced (Key) TS/SCI (1) 120 (1), 90 (1)

Information Security Analysts, Basic Secret 60

Information Security Analysts, Intermediate TS 90

Information Security Analysts, Advanced (Non-Key)

TS/SCI (1), TS (All Others) 120 (1), 90 (All Others)

Information Security Analysts, Advanced (Key) TS/SCI 120

Network and Computer Systems Administrators, Basic Secret 60

Network and Computer Systems Administrators, Intermediate (All Locations)

TS 120

Network and Computer Systems Administrators, Advanced TS 120

Software Developers, Basic Secret 60

Software Developers, Intermediate TS 120

Software Developers, Advanced TS 120

Software Quality Assurance Analysts and Testers, Basic Secret 60

Software Quality Assurance Analysts and Testers, Intermediate

TS (1), Secret (All Others) 90 (1), 60 (All Others)

Software Quality Assurance Analysts and Testers, Advanced

TS (1), Secret (All

Electronics Technician Maintenance I (SCA) Secret 60

Electronics Technician Maintenance II (SCA) Secret 60

Electronics Technician Maintenance III (SCA) Secret 60

Technical Writer III (SCA) Secret (1) 60 (1)

The Contractor employees may be granted access to Joint Worldwide Intelligence Communications Systems (JWICS) and Secret Internet Protocol Network (SIPRNet) in order to establish and maintain accounts. Such access shall be authorized at Government facilities only in support of tasking as required within this SOW. The Contractor shall not access, download, or further disseminate any information or data that falls outside of the scope and execution of the defined TO requirements. In the event that any additional access is required, the Technical Point of Contact (TPOC)/COR must modify the requirements via a DD Form 254 revision. The Contractor shall prepare and submit all required documentation as required by Command policy prior to receiving access.

3.2.3 Common Access Card (CAC)/Public Key Infrastructure (PKI) and System Authorization Access Request (SAAR).

3.2.3.1 SAAR. All contractor personnel requiring access to Government IT systems shall have an approved DD Form 2875, System Authorization Access Request (SAAR) form on file and complete required Annual Information Awareness Training. New employees must submit their SAAR forms within 30 business days of their first day of work. SAAR forms shall be submitted to the COR, Government TPOC, or to the assigned Government Mission Partner Identity, Credential, and Access Management (MP ICAM) Trusted Associate (TA).

3.2.3.2 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. All CACs and identification badges issued to contractor employees shall be returned to the TA following completion of the TO, relocation or termination of an employee, or upon request from the COR/Procuring Contracting Officer (PCO). The Government will provide the Contractor access to Government facilities, as required, for performance of tasks under this TO.

3.2.3.3 DD Form 254. The Contractor shall comply with security requirements specified in the DD Form 254 attached to this TO. Information or data that the Contractor accesses shall be handled at the appropriate classification level. Unclassified information shall be handled IAW the appropriate designation (Controlled Unclassified Information (CUI); Legacy For Official Use Only (FOUO); Covered Defense Information (CDI)). Distribution is authorized to the Requiring Office’s Organization and supported Activity only. Other requests for deliverables under this TO shall be referred to the TPOC/COR of this TO for approval.

The Contractor will require access to:

– Communications Security (COMSEC) Information. National Intelligence Information, Non-Sensitive Compartmented Information (Non-SCI), and SCI

– NATO Information

– Foreign Government Information

– CUI

– SIPRNet (authorized at Government facility only)

In performing this TO, 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

– Require a COMSEC account.

– Have Operations Security (OPSEC) requirements.

– Be authorized to use Defense Courier Service (DCS).

– 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 National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulations Part 117, NISPOM Rule and SECNAVINST 5510.36B, Department of the Navy Information Security Program. If the work is performed at the Government's facility, the Contractor shall comply with facility security procedures and controls.

All contractor facilities shall provide an appropriate means of storage for CUI and materials. All CUI including legacy FOUO and CDI (meeting the definition DFARS Clause 252.204–7012, Safeguarding Covered Defense Information and Cyber Incident Reporting) generated and/or provided under this TO 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 Information and have this statement displayed per DoDI 5230.24, Enclosures 3 and 4.

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

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

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

Distribution Statement (Insert Appropriate Letter and Authorization Title), (Insert Appropriate Reason Category) (dated – (Date of Distribution Authorization)). Other requests shall be referred to: Commander, Naval Air Systems Command, Attn: TES COR, 17134 Webster Field Road, Building 8225, St. Inigoes, MD 20684-4009.

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

Classified information shall be marked IAW DoDM 5200.01, Vol 2, Marking of Classified Information. CUI, including legacy FOUO information generated and/or provided under this TO, shall be marked IAW DoDI 5200.48, Controlled Unclassified Information (CUI). Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings IAW DoDI 5230.24, Distribution Statements on Technical Information and program Security Classification Guidance.

3.2.4.2 Public Release. Any CUI pertaining to this TO shall not be released for public dissemination, including posting to any social media sites such as Facebook or X (formerly known as 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 Public Affair Office (PAO) via the COR identified in GTXT.201- 9501, Designation of Contracting Officer’s Representative.

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 72 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 TO. 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 Naval Air Systems Command (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 A010)

3.2.6 Antiterrorism Force Protection and Emergency Management. The work performed on this TO is not Emergency Essential IAW OPNAVINST 3440.17A, Navy Installation Emergency

Management Program 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.3 Detailed Support Requirements.

3.3.1 Concept and Technology Development Support.

3.3.1(a) (PROC) Provide concept and technology development support for SAIW programs and projects throughout the procurement and production phases of the program’s life cycle.

Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.9.

3.3.1(b) (O&M) Provide concept and technology development support for SAIW programs and projects throughout the O&M phases of the program’s life cycle. Applicable to SOW paragraphs

3.3.1.1 – 3.3.1.9.

3.3.1(c) (RDT&E) Provide concept and technology development support for SAIW programs and projects throughout the research and development phases of the program’s life cycle.

Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.9.

3.3.1(d) (Non-DoD) Provide concept and technology development support for SAIW programs and projects supporting non-DoD customers. Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.9.

3.3.1(e) (FMS) Provide concept and technology development support for SAIW programs and projects intended as FMS. Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.9.

3.3.1(f) (WCF) Provide concept and technology development support for SAIW programs and projects associated with WCF efforts. Applicable to SOW paragraphs 3.3.1.1 – 3.3.1.9.

3.3.1.1 The Contractor shall assist with analyzing the needs of and defining the operational requirements for new systems and/or capabilities to address deficiencies with existing systems and new mission requirements and to identify opportunities for improvements afforded by new technologies. (CDRL A011)

3.3.1.2 The Contractor shall assist with providing technical support for the research and evaluation necessary to transform operational needs and requirements into defined operational objectives and system technical performance objectives in order to guide the development of new or improved system capabilities. (CDRL A011)

3.3.1.3 The Contractor shall support the development of baselines and conceptual architectures and designs necessary to satisfy the operational objectives and technical features of proposed systems. (CDRL A011)

3.3.1.3.1 The Contractor shall assist with the assessment of external and internal interoperability and interface issues. (CDRL A011)

3.3.1.4 The Contractor shall assist with the process of researching, analyzing, identifying, evaluating, and documenting findings in order to perform an Analysis of Alternatives (AoA).

Considerations shall include Government-Off-the-Shelf (GOTS), Commercial-Off-the-Shelf

(COTS), and Non-Developmental Item (NDI) solutions whenever feasible and include issues specific to these solutions such as data rights, supportability, licensing agreements, and copyrights as part of the evaluation. (CDRL A011)

3.3.1.5 The Contractor shall assist with ensuring traceability between system operational requirements and associated hardware and software implementation by documenting and providing information in a format that clearly demonstrates a logical flow and validates that system components are necessary and sufficient to meet system requirements. (CDRL A011)

3.3.1.6 The Contractor shall assist by providing technical support for engineering and technical tests and evaluations to support systems engineering and programmatic decisions of new and existing C6ISR systems. Support shall include assisting with feasibility studies, trade studies, work force studies, cost-benefit analysis, and system total-operating-cost analysis. (CDRL A011)

3.3.1.7 The Contractor shall assist with the analysis and evaluations of new systems by recommending test procedures and protocols for new systems and their components. (CDRLs A012 and A013)

3.3.1.8 The Contractor shall assist with the technical analysis for the development of Test & Evaluation (T&E) documentation necessary to validate and verify the operational and technical parameters of a system. Documentation shall include functions such as participating in planning meetings, assisting in identifying and coordinating required testing and facilities, and assisting with the development of test schedules. (CDRL A012)

3.3.1.9 The Contractor shall assist with the assessment of final test result report analyzing requirements, shortfall, and approaches related to warfighter survivability and vulnerability when utilizing fixed and mobile systems. (CDRL A014)

3.3.1.9.1 The Contractor shall assist with analyzing new equipment against test plans in order to assess their interoperability capabilities and their survivability effectiveness. (CDRLs A013 and A014)

3.3.1.9.2 The Contractor shall assist with the development of analytic and technical reports for test planning and functions to include test requirements analysis, confirmation of requirements met, test procedures, test data analyses, and system safety evaluation testing gaps and shortfalls.

(CDRL A014)

3.3.2 System Design Support.

3.3.2(a) (PROC) Provide system design support for SAIW programs and projects throughout the procurement and production phases of the program’s life cycle. Applicable to SOW paragraphs

3.3.2.1 – 3.3.2.12.

3.3.2(b) (O&M) Provide system design support for SAIW programs and projects throughout the O&M phases of the program’s life cycle. Applicable to SOW paragraphs 3.3.2.1 – 3.3.2.12.

3.3.2(c) (RDT&E) Provide system design support for SAIW programs and projects throughout the research and development phases of the program’s life cycle. Applicable to SOW paragraphs

3.3.2.1 – 3.3.2.12.

3.3.2(d) (Non-DoD) Provide system design support for SAIW programs and projects supporting non-DoD customers. Applicable to SOW paragraphs 3.3.2.1 – 3.3.2.12.

3.3.2(e) (FMS) Provide system design support for SAIW programs and projects intended as FMS. Applicable to SOW paragraphs 3.3.2.1 – 3.3.2.12.

3.3.2(f) (WCF) Provide system design support for SAIW programs and projects associated with WCF efforts. Applicable to SOW paragraphs 3.3.2.1 – 3.3.2.12.

3.3.2.1 The Contractor shall assist by assessing the feasibility and suitability of proposed design solutions. (CDRL A011)

3.3.2.1.1 The Contractor shall assist by providing support for appropriate risk mitigation efforts, such as modeling and simulation, when unproven technologies, unique concepts, or high-risk approaches are proposed.

3.3.2.2 The Contractor shall assist with conducting system design research to define and provide recommendations of the subsystems and the components that compose a system design.

(CDRL A011)

3.3.2.2.1 The Contractor shall assist with identifying and recommending assignments of functions, as appropriate, and by documenting and maintaining an allocated baseline. (CDRL A011)

3.3.2.2.2 The Contractor shall assist with identifying and recommending assignments of specific hardware and software items required to accomplish system functions and to document and maintain a product baseline. Typical products for these efforts include engineering drawings and technical documentation, prototype systems, and evaluation test reports. (CDRL A011)

3.3.2.3 The Contractor shall assist with the research and evaluation of system-related technical documentation such as technical manuals, interface control drawings, and design specifications for completeness and accuracy. (CDRL A011)

3.3.2.3.1 The Contractor shall assist with identifying deficiencies and providing recommendations for corrections or modifications. (CDRL A011)

3.3.2.4 The Contractor shall assist with providing research, design, test, and evaluation support for the overall design of proposed systems. (CDRLs A011, A015, A016)

3.3.2.4.1 The Contractor shall assist with developing, updating, and maintaining detailed engineering drawings and documentation associated with the design of hardware and software systems IAW MIL-STD-31000B, Technical Data Packages. Drawings and documentation must address all aspects of the system and provide the details necessary to integrate, install, and maintain the subject system. (CDRLs A011, A015, A016)

3.3.2.4.2 The Contractor shall assist with the development of installation drawings, procurement drawings, and technical documentation for such items. (CDRLs A015, A017, A018, A019)

3.3.2.4.3 The Contractor shall assist with researching, developing, and conducting technical analyses for system configuration-control processes. (CDRL A020)

3.3.2.4.4 The Contractor shall assist with developing, revising, and updating configuration-control documentation for hardware and software components to include the creation of drawings, work plans, Configuration Management Plans, audit summaries, product drawings, models, and validation reports. (CDRLs A020 and A021)

3.3.2.4.5 The Contractor shall assist with the technical analyses of engineering and design practices that enhance development, modernization, compatibility, and cost efficiency.

3.3.2.4.6 The Contractor shall assist with the development of installation drawings, procurement drawings, and technical documentation for such items. (CDRLs A015, A018, A019, A021)

3.3.2.5 The Contractor shall assist with providing technical support for the development of test and evaluation documentation necessary to validate and verify the operational and technical parameters of systems. (CDRLs A011, A012, A013, A014, A015)

3.3.2.5.1 The Contractor shall assist with providing technical support for test planning and coordination by performing functions such as participating in planning meetings, identifying and coordinating required test resources and facilities, and developing test schedules. (CDRLs A011, A012, A013, A022)

3.3.2.6 The Contractor shall assist with providing technical support for the performance of developmental and operational system tests and evaluations.