Att 1 Draft SOW SAIW TPMS Rev 01.pdf

UNCLASSIFIED

STATEMENT OF WORK FOR

SHIP AND AIR INTEGRATED WARFARE

TECHNICAL/PROJECT MANAGEMENT SUPPORT

1.0 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 is engaged in the research, development, design, integration, test and evaluation, deployment, training, technical management, and maintenance support for integrated Command, Control, Communications, Computers, Combat Systems, Intelligence, Surveillance, and Reconnaissance (C5ISR) life cycle engineering systems supporting various sponsors to include Naval Air Systems Command

(NAVAIR), Naval Sea Systems Command (NAVSEA), and other Department of Defense (DoD) and Federal organizations. The SAIW Division, operating under the oLSI® model, has requirements for technical project management and operational support to successfully fulfill the

SAIW Divisions mission of provided support services at both the diverse project levels and the over all Division organizational level.

This Task Order (TO) provides support for technical and systems engineering, technical and project management, organizational management, administrative, acquisition, and budget execution for the entire SAIW Division project lifecycle to include support for overarching organizational planning, performance, reporting, and best practices to ensure consistent high levels of success. This requirement is in direct support of projects related to multiple major defense acquisition programs, other acquisition category designations, and/or other defense weapons systems to include, but not be limited to, multiple major defense acquisition programs, other acquisition category designations, and other defense weapons systems with an agile management approach to ensure that solutions are delivered efficiently and effectively.

2.0 Applicable Documents.

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.

DRAFT

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

2.1.9 SECNAV M-5216.5 CH-1, Department of the Navy Correspondence Manual.

2.2 DoD Standards.

2.2.1 DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology

(IT).

2.2.2 DoDD 7045-14, The Planning, Programming, Budgeting, and Execution (PPBE)

Process, Change 1, 29 Aug 2017.

2.2.3 DoD 7000.14-R, Financial Management Regulations (FMR), Volume 1-16, November

2025.

2.3 Other Government Documents.

2.3.1 National Security Presidential Memorandum 28 (NSPM-28).

2.3.2 SAIW Division Operations Manual.

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

2.4 Industry Documents.

2.4.1 International Organization for Standardization (ISO), ISO 9001:2015 Standard.

3.0 Requirements.

3.1 General Requirements.

3.1.1 Compatibility. The Contractor shall maintain the capability to prepare documents and software packages compatible with the Government IT environment through the security classification of none as specified on the DD Form 254, Contract Security Classification Specification Form (Attachment XX). The current operating environment required for this TO includes:

Microsoft Windows 11 or greater Microsoft Project 2016 or greater

Microsoft Office Professional Plus 2016 or greater Adobe Reader Adobe Acrobat Pro

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 86% of work will be performed at Government site and 14% of work to be performed at contractor site. Government site includes NAWCAD WOLF St.

Inigoes, MD.

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.2 Contractor Site Requirements. The Contractor shall provide its own support facilities within 50 drivable miles of NAWCAD 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 Statement of Work (SOW), the Contractor shall have the capability to host and conduct Unclassified meetings 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 contractor support facilities required in section 3.1.2.1.2, located within 50 drivable miles of NAWCAD 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, to include a required day of Wednesday. On-site performance may be required outside of routine on-site performance days, and shall be provided when requested by the 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 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.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. (CDRL A001)

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 A002)

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 1500 EST 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). Working Capital Fund (WCF); Procurement (PROC);

Operations & Maintenance (O&M); Research, Development, Test & Evaluation (RDT&E); Non-

Department of Defense (Non-DoD); and Foreign Military Sales (FMS).

The Contractor shall complete travel request(s) IAW CTXT.232-9509, Travel Approval and Reimbursement Procedures (NAVAIR) (OCT 2013). Upon completion of travel, each 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 A003)

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 San Diego, CA; Washington, D.C;

Mayport, FL; Orlando, FL; Tampa, FL; Marlborough, MA; Columbus, OH; Harrisburg, PA;

Chesapeake, VA; and Norfolk, VA.

3.1.5.1.2 OCONUS. OCONUS location may include travel to Pearl Harbor, HI.

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 A004)

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.

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

̶ 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.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 Secret facility level, with no safeguarding level. 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.

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 TO

Business Operations Specialists, All Other (Organizational

Management), Senior

Secret (One) 60

Business Operations Specialists, All Other (Organizational

Management), Senior, Key

Top Secret 90

Computer Systems Analysts (IT

Specialist), Senior Secret 60

Data Scientists (Data Analytics), Senior, Key Secret 60

Financial Specialists (All Other)

(Financial Analyst), Senior Secret 60

General and Operations

Managers, All Other (Program

Manager), Senior, Key

Top Secret 90

Management Analysts (Services

Acquisition Support), Senior, Key Secret 60

Project Management Specialists, Senior, Key Secret 60

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 Technical Point of Contact (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.

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: SAIW Technical/Project Management Support (TPMS) 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.4.4 Unclassified contractor information systems that generate, process, store, or transmit CUI or Federal Contract Information (FCI) shall, at a minimum, adhere to DFARS Clause

252.204-7021 Cyber Maturity Model Certification (CMMC) Level 2. The Contractor shall implement, maintain, and document cybersecurity controls in accordance with the CMMC requirements applicable to this contract, including all practices and processes required for the designated CMMC level, for the duration of the period of performance.

3.2.5 Operations Security (OPSEC). The Contractor shall develop, implement, and maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the Contractor and any subcontractor during performance of the TO. The Contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. This program may include Information Assurance (IA) and Communications Security (COMSEC). The OPSEC program shall be IAW NSPM-28 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 A006)

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 Technical and Systems Engineering Support.

3.3.1(a) (WCF) Provide technical and systems engineering support for SAIW programs and projects associated with WCF efforts. Applicable to SOW paragraphs 3.3.1.1 - 3.3.1.10.

3.3.1(b) (PROC) Provide technical and systems engineering 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.10.

3.3.1(c) (RDT&E) Provide technical and systems engineering 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.10.

3.3.1(d) (O&M) Provide technical and systems engineering 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.10.

3.3.1(e) (Non-DoD) Provide technical and systems engineering support for SAIW programs and projects supporting Non-DoD customers. Applicable to SOW paragraphs 3.3.1.1 - 3.3.1.10.

3.3.1(f) (FMS) Provide technical and systems engineering support for SAIW programs and projects intended as FMS. Applicable to SOW paragraphs 3.3.1.1 - 3.3.1.10.

3.3.1.1 The Contractor shall provide support with the development of IA documentation.

3.3.1.2 The Contractor shall provide support by documenting engineering requirements for potential projects within the SAIW portfolio.

3.3.1.3 The Contractor shall provide support with tracking and supporting installation and integration schedules for projects within the SAIW portfolio based on inputs from SAIW personnel.

3.3.1.4 The Contractor shall provide support by documenting findings of design evaluations, interoperability studies, and shipyard documentation reviews.

3.3.1.5 The Contractor shall provide support with conducting systems engineering analysis for use in developing or upgrading existing communications and information systems.

3.3.1.6 The Contractor shall provide support with exploring emerging and next generation technologies that can replace existing platform and C5ISR technologies to meet new/existing requirements.

3.3.1.7 The Contractor shall provide support with performing specialized studies and evaluations to be used to provide an assessment of current communications and information systems architecture and to offer recommendations for new technology.

3.3.1.8 The Contractor shall provide support with conducting and documenting findings of engineering reviews for key SAIW Division programs.

3.3.1.9 The Contractor shall provide support by attending and supporting scheduled and ad-hoc information interchange meetings in order to provide project and technical experience in support of the engineering efforts of SAIW projects. (CDRL A007)

3.3.1.10 The Contractor shall provide support with developing SAIW Division Systems Engineering Standards IAW NAVAIR's systems engineering processes.

3.3.2 Technical Project Management Support.

3.3.2(a) (WCF) Provide technical project management support for the SAIW programs and projects associated with WCF efforts. Applicable to SOW paragraphs 3.3.2.1 - 3.3.2.14.

3.3.2(b) (PROC) Provide technical project management 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.14.

3.3.2(c) (RDT&E) Provide technical project management 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.14.

3.3.2(d) (O&M) Provide technical project management 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.14.

3.3.2(e) (Non-DoD) Provide technical project management support for SAIW programs and projects supporting Non-DoD customers. Applicable to SOW paragraphs 3.3.2.1 - 3.3.2.14.

3.3.2(f) (FMS) Provide technical project management support for SAIW programs and projects intended as FMS. Applicable to SOW paragraphs 3.3.2.1 - 3.3.2.14.

3.3.2.1 The Contractor shall provide support to project management processes throughout the project life cycle including initiation, planning, executing, monitoring, controlling, and closeout.

3.3.2.2 The Contractor shall support the development and maintenance of project planning documentation to include, but not be limited to, the following document types: Program

Management Plan (PMP); Responsible, Accountable, Consulted, and Informed (RACI) Matrix;

Project Performance Reports (PPRs); Contract Status Reports (CSRs); Internal Project Reviews

(IPRs); detailed project schedules; project cost estimates; technical reviews; delivery documentation; and project close out reports. (CDRL A008)

3.3.2.3 The Contractor shall provide support by tracking project performance against established baselines documented in project plans and status reports. The type of plans reviewed include, but are not limited to, Work Breakdown Structure (WBS)/Plans of Actions &

Milestones (POA&M)/schedules, requirements managements, change management, risk management, and spend plans. The type of status reports include, but are not limited to, PPRs, IPRs, internal SAIW compliance reviews and audits, accomplishment reports, Earned Value

Management System (EVMS) reports, project briefings, customer/sponsor feedback, and meeting minutes.

3.3.2.4 The Contractor shall provide support with the development of project scheduling documentation to include, but not be limited to, WBSs, POA&Ms, and IMSs.

3.3.2.4.1 The Contractor shall provide support with the development and the functional implementation of detailed project scheduling and change management best practices in planning, updating, and maintaining schedules.

3.3.2.4.2 The Contractor shall support schedule analysis to identify project risks and/or opportunities to support the assessment of resource usage and planning.

3.3.2.4.3 The Contractor shall provide support with schedule analysis to include critical path and near-critical path analysis.

3.3.2.5 The Contractor shall provide support in the development of project review documentation IAW the SAIW Division Project Realization Standard Operating Procedure (SOP). Examples of the documentation include, but are not limited to, Program Management

Reviews (PMRs), System Requirements Reviews (SRRs), Preliminary Design Reviews (PDRs), Critical Design Reviews (CDRs), and Test Readiness Reviews.

3.3.2.6 The Contractor shall provide support to design and production reviews and informal meetings with SAIW sponsors and stakeholders.

3.3.2.6.1 The Contractor shall provide support with the preparation of documentation such as agendas, presentations, charts, illustrations, meeting minutes, and action items lists.

3.3.2.6.2 The Contractor shall provide support for the SAIW Division's SharePoint Online (SPO) repository and ensure that it is maintained with accurate meeting artifacts and records from all sources.

3.3.2.7 The Contractor shall provide support for the development of briefs and reports for conferences and meetings hosted or attended by SAIW personnel. (CDRL A009)

3.3.2.8 The Contractor shall provide support by participating in meetings to provide project and financial management expertise and document any important information and artifacts.

(CDRL A007)

3.3.2.9 The Contractor shall provide support by providing recommendations on the technical and non-technical project risks.

3.3.2.9.1 The Contractor shall provide support towards the development and maintenance of the project's Risk Management Plan (RMP) through the identification, analysis, mitigation planning, and monitoring and controlling of risks to closure IAW DoDI 8510.01, Risk Management

Framework (RMF) for DoD Information Technology (IT).

3.3.2.9.2 The Contractor shall provide support by identifying and documenting risks (consequences and likelihood) within SAIW risk registry or equivalent.

3.3.2.10 The Contractor shall provide support with performing analysis of the financial status of the projects utilizing information provided by project personnel and document status in the PPR.

3.3.2.10.1 The Contractor shall provide support in the research and identification of deviations between planned, actual, and projected financial metrics and document findings in the PPR.

3.3.2.10.2 The Contractor shall provide support with the analysis and identification of the long-term effect of the deviations and document findings in the PPR.

3.3.2.11 The Contractor shall provide support with requirements management for SAIW projects including requirements definition, refinement, tracking, management, and verification.

3.3.2.11.1 The Contractor shall provide support with the tracking of project deliverables and document findings in the PPR.

3.3.2.11.2 The Contractor shall provide support for change control management.

3.3.2.12 The Contractor shall provide support in the development and review of Performance

Work Statements (PWSs), Memorandums of Agreement (MOAs), and Memorandums of Understanding (MOUs) for SAIW projects.

3.3.2.12.1 The Contractor shall provide support with project planning activities to meet the operational objectives of the SAIW project.

3.3.2.13 The Contractor shall provide support of creating, documenting, formatting, and analyzing project dashboards IAW CDRL A010.

3.3.2.14 The Contractor shall provide support by maintaining SAIW Division SPO repository with project data and information IAW SAIW Division Operations Manual.

3.3.3 Organizational Management Support.

3.3.3(a) (WCF) Provide organizational management support for SAIW programs and projects associated with WCF efforts. Applicable to SOW paragraphs 3.3.3.1 - 3.3.3.10.

3.3.3(b) (PROC) Provide organizational management support for SAIW programs and projects throughout the procurement and production phases of the program's life cycle. Applicable to SOW paragraphs 3.3.3.1 - 3.3.3.10.

3.3.3(c) (RDT&E) Provide organizational management support for SAIW programs and projects throughout the research and development phases of the program's life cycle. Applicable to SOW paragraphs 3.3.3.1 - 3.3.3.10.

3.3.3(d) (O&M) Provide organizational management support for SAIW programs and projects throughout the O&M phases of the program's life cycle. Applicable to SOW paragraphs 3.3.3.1 -

3.3.3.10.

3.3.3(e) (Non-DoD) Provide organizational management support for SAIW programs and projects supporting Non-DoD customers. Applicable to SOW paragraphs 3.3.3.1 - 3.3.3.10.

3.3.3(f) (FMS) Provide organizational management support for SAIW programs and projects intended as FMS. Applicable to SOW paragraphs 3.3.3.1 - 3.3.3.10.

3.3.3.1 The Contractor shall provide support with the development of strategic and tactical plans that address current and projected funding requirements, technical resources, IT needs, and material acquisition requirements.

3.3.3.1.1 The Contractor shall support the Government with documenting the feasibility to execute forecasted projects which may include, project financial trends, project financial execution, project processes, tools, and facilities. (CDRL A010)

3.3.3.2 The Contractor shall assist in maintaining floor plans and seating charts for SAIW buildings, utilizing input provided by SAIW personnel.

3.3.3.3 The Contractor shall provide support with the collaboration, development, and maintenance of SAIW SOPs and Standard Work Packages (SWPs) IAW the SAIW Division

Operations Manual.

3.3.3.3.1 The Contractor shall provide support with reviewing those processes to ensure they are compliant with the SAIW Divisions Operations Manual and document any findings.

3.3.3.3.2 The Contractor shall provide support with reviewing those processes to ensure they are compliant with the SAIW Division's International Organization for Standardization (ISO), ISO

9001:2015 Standard certification and document any findings.

3.3.3.3.3 The Contractor shall provide support with performing and documenting findings of internal ISO audits and IPRs to maintain Division readiness for International Organization for

Standardization (ISO), ISO 9001:2015 Standard. (CDRL A007)

3.3.3.3.4 The Contractor shall provide support with technical editing of SAIW SOPs and SWPs.

3.3.3.4 The Contractor shall provide support with the collaboration and documentation of SAIW impacts from FAR, DFARS, NAVAIR, and NAWCAD financial and acquisition

Government driven by policy changes. (CDRLs A009 and A010)

3.3.3.5 The Contractor shall provide support with the documentation of performance metrics established by SAIW directives and project initiatives.

3.3.3.5.1 The Contractor shall provide support by gathering and acquiring key artifacts to support the Government review and assessment of these performance metrics. Key artifacts include, but are not limited to, historical obligation/expenditure data. (CDRL A010)

3.3.3.6 The Contractor shall support with the preparation and analysis of Navy Enterprise

Resource Planning (N-ERP) reports by identifying data for all funding received, committed, obligated and expended, analyzing risk and presenting options for issue resolution against financial benchmarks. (CDRL A010)

3.3.3.7 The Contractor shall provide support by proposing improvements to the budget execution processes, including using the SAIW tools, to report on incoming financial data and execution. Tools include, but are not limited to, Qlik and SPO.

3.3.3.8 The Contractor shall provide support in the development of responses to data calls from internal and external offices.

3.3.3.9 The Contractor shall provide support with creating, documenting, formatting, and analyzing operations dashboards. (CDRL A010)

3.3.3.10 The Contractor shall provide support with Agile Framework implementations (Division, Branch, Project, Command interfaces) and must understand Agile methodologies and principles (Agile, Scrum, Scaling, Kanban) throughout an oLSI® project life cycle. Additional knowledge is required with Agile supporting tools (JIRA, DevSecOps, etc) to ensure project status, blockers, and issues (cost, schedule, performance) are tracked in real-time and captured ensuring transparency across the Command.

3.3.4 Administrative Support.

3.3.4(a) (WCF) Provide administrative support for SAIW programs and projects associated with

WCF efforts. Applicable to SOW paragraphs 3.3.4.1 - 3.3.4.4.

3.3.4(b) (PROC) Provide administrative support for SAIW programs and projects throughout the procurement and production phases of the program's life cycle. Applicable to SOW paragraphs 3.3.4.1 - 3.3.4.4.

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

3.3.4.1 - 3.3.4.4.

3.3.4(d) (O&M) Provide administrative support for SAIW programs and projects throughout the O&M phases of the program's life cycle. Applicable to SOW paragraphs 3.3.4.1 - 3.3.4.4.

3.3.4(e) (Non-DoD) Provide administrative support for SAIW programs and projects supporting

Non-DoD customers. Applicable to SOW paragraphs 3.3.4.1 - 3.3.4.4.

3.3.4(f) (FMS) Provide administrative support for SAIW programs and projects intended as

FMS. Applicable to SOW paragraphs 3.3.4.1 - 3.3.4.4.

3.3.4.1 Administrative Support.

3.3.4.1.1 The Contractor shall provide support with the maintenance of Division directories and new hire packages.

3.3.4.1.2 The Contractor shall support security procedures by maintaining logbooks, checking identification, issuing visitor badges, and coordinating facility end-of-day checks by SAIW personnel.

3.3.4.1.3 The Contractor shall provide support with maintaining conference room schedules by coordinating requests and providing resolution to scheduling conflicts.

3.3.4.1.4 The Contractor shall provide support with the coordination of the pick-up and delivery of mail services.

3.3.4.1.5 The Contractor shall provide support with preparing documentation to order, inventory, and distribute office supplies.

3.3.4.1.6 The Contractor shall support other clerical duties such as photocopying, faxing, scanning, filing, and collating documents as required.

3.3.4.1.7 The Contractor shall provide support with the processing of incoming and outgoing visit requests in support of SAIW personnel, including interfacing with BASICS II and Defense Information System for Security (DISS).

3.3.4.1.8 The Contractor shall support the development and processing of both classified and unclassified correspondence and naval messages to the appropriate personnel IAW SECNAV M-

5216.5 CH-1, Department of the Navy Correspondence Manual.

3.3.4.1.9 The Contractor shall support specialized training for SAIW personnel in the areas of project management, acquisition, cost management, best business rules/practices, software applications, NAVAIR applications, and other topics as needed to support the SAIW strategic and tactical plans. (CDRL A011)

3.3.4.1.10 The Contractor shall support the development of graphics and documentation including, but not limited to, the development of reviews for briefings, technical reports and drawings, system manuals, display materials, brochures, recognition and award material, and electronic publishing. (CDRL A010)

3.3.4.1.11 The Contractor shall provide support with developing meeting minutes and action items for critical Division, branch, and project level meetings. (CDRL A007)

3.3.4.2 Business Operations Support.

3.3.4.2.1 The Contractor shall provide reception support for key SAIW buildings and facilities.

3.3.4.2.2 The Contractor shall support facility visitors by greeting them in person, over the phone, or via video conferencing tools.

3.3.4.2.3 The Contractor shall provide support to SAIW personnel and/or visitors with answering routine personnel or facility questions and/or referring inquiries to SAIW Division leadership.

3.3.4.3 Travel Support.

3.3.4.3.1 The Contractor shall support SAIW Division travel requirements by processing, tracking, and routing of SAIW personnel travel arrangements, order requests and receipts, and travel reimbursement claims utilizing the Defense Travel System (DTS). Information to support the travel orders and reimbursement claims will be provided by the Government traveler.

3.3.4.3.2 The Contractor shall provide assistance by reviewing and documenting internal process changes in support of Government travelers as a result of travel policy changes and impacts with regard to the Joint Travel Regulations (JTR), as well as additional DoD, U.S. Navy, NAVAIR, and local NAWCAD travel directives and guidance

3.3.4.4 Information Technology Support.

3.3.4.4.1 The Contractor shall provide assistance with on-site IT support to SAIW personnel, to include both Government and contractor personnel).

3.3.4.4.2 The Contractor shall support the coordination of Division-wide compliance with IT initiatives related to the Division networks.

3.3.4.4.3 The Contractor shall provide support by reviewing and analyzing computer and information requirements for SAIW personnel.

3.3.4.4.4 The Contractor shall provide support by researching user technology issues and track to resolution.

3.3.4.4.5 The Contractor shall provide support by providing help desk support in troubleshooting issues related to computer systems, software, and hardware.

3.3.4.4.6 The Contractor shall provide support to install, modify, and repair computer software and hardware where permitted.

3.3.5 Acquisition Support.

3.3.5(a) (WCF) Provide acquisition support for SAIW programs and projects associated with WCF efforts. Applicable to SOW paragraphs 3.3.5.l - 3.3.5.2.

3.3.5(b) (PROC) Provide acquisition support for SAIW programs and projects throughout the procurement and production phases of the program's life cycle. Applicable to SOW paragraphs

3.3.5.l - 3.3.5.2.

3.3.5(c) (RDT&E) Provide acquisition support…