IDS TPS_CSS SOW_Draft_SS.pdf

UNCLASSIFIED

STATEMENT OF WORK FOR

IDENTIFICATION SYSTEMS

TECHNICAL PROJECT SUPPORT 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 Identification Systems (IDS) Division, operating under the oLSI® model, has requirements for technical/project management support; budget execution support; material procurement support; data management support; training support; and graphics, media, communications, and clerical support. The projects directly support multiple major defense acquisition programs, other acquisition category designations, and other defense weapons systems including, but not limited to, air, ship, shore, and identification; expeditionary and range control systems; operational control systems; integration, production, installation, and certification; system, mission, and software engineering; and fleet area control and surveillance facility field maintenance.

Applicable Documents.

2.1 Department of Defense (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.1.11 SECNAV M-5216.5 CH-1, Department of the Navy Correspondence Manual, 16 May

2018.

2.1.12 DoDD 7045.14, The Planning, Programming, Budgeting, and Execution (PPBE)

Process, Change 1, 29 Aug 2017.

2.2 DoD Standards.

2.2.1 DoD 7000.14-R, Financial Management Regulations (FMR), Volume 1-16, March

2024.

2.3 Other Government Documents.

2.3.1 NAVAIR Operations Security (OPSEC) Requirements (2013 OPSEC Annex).

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

2.3.3 The Joint Travel Regulations (JTR), 1 Jan 2025.

2.4 Industry Documents.

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

2.5 Other Documents.

2.5.1 IDS Quality Policy Manual Version 6.2.

2.5.2 SOP-CIIDS-B-SEC-002-IDS Division Security.

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 XX). The current operating environment required for this Task Order (TO) includes:

Microsoft Windows 16 or greater

Microsoft Project 2016 or greater

Microsoft Office Professional Plus 2016 or greater

Adobe Reader

Adobe Acrobat Pro

Power BI

Internet access

Flank Speed

Adobe Suite/Creative Cloud

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 IDS Division Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with the IDS

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 87% of work will be performed at Government site and

13% of work to be performed at contractor site. Government site includes NAWCAD WOLF, St.

Inigoes, MD. 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 Contractor Site Requirements. The Contractor shall provide its own support facilities needed to perform the tasking of this TO. The facility shall be within 50 drivable miles of

NAWCAD WOLF in order to satisfy the daily support and administrative operations of this TO.

The Government will not assume responsibility to retain the facilities or take control of the titles after the TO is completed.

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 meetings at the classification levels up to Secret with the capacity to support a minimum of five 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 facility, as required.

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 three 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 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.3.3 The Contractor shall prepare and deliver a Program Management Plan and

Contractor’s Personnel Roster IAW CDRLS A003 and A004.

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.

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

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 and Maintenance

(O&M); Foreign Military Sales (FMS); Research, Development, Test & Evaluation (RDT&E);

Working Capital Fund (WCF); and non-DoD.

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 San Diego, CA; Washington, DC; Key West, FL; Pensacola, FL; Moorestown, NJ; Long Island, NY; Mechanicsburg, PA; Philadelphia, PA; Charleston, SC;

Chesapeake, VA; Dahlgren, VA; and Norfolk, VA. This list is not all inclusive as locations may change over the life of the TO. The Contractor shall submit a Travel Report upon completion of travel and within five days of return. (CDRL A005)

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. Any material and/or Government Furnished Property

(GFP) held by the Contractor shall be reported on a Contractor Acquired Property (CAP)

Report. (CDRL A006)

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

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.

LABOR CATEGORY

LEVEL

DoD SECURITY

CLEARANCE

LEVEL (INTERIM

CLEARANCE

ACCEPTABLE)

REQUIRED BUSINESS DAYS

AFTER ISSUANCE OF TO

Budget Analysts (Financial Analysts) Senior Secret Within 60 business days of award

Business Operations Specialists, All

Other (Project Scheduler)

Journeyman Secret Within 90 business days of award

Data Scientists Apprentice Secret Within 90 business days of award

Data Scientists Basic Secret Within 90 business days of award

Data Scientists Intermediate Secret Within 90 business days of award

Data Scientists Advanced Secret Within 90 business days of award

Database Architects Basic Secret Within 90 business days of award

Database Architects Intermediate Secret Within 90 business days of award

General Clerk I N/A Secret Within 90 business days of award

General Clerk II N/A Secret Within 90 business days of award

General Clerk III N/A Secret Within 90 business days of award

General and Operations Managers Senior Secret Within 60 business days of award

Graphic Artist N/A Secret Within 90 business days of award

Management Analysts Apprentice Secret Within 90 business days of award

Management Analysts Junior Secret Within 90 business days of award

Management Analysts Journeyman Secret Within 90 business days of award

Management Analysts Senior Secret Within 60 business days of award

Procurement Clerks Apprentice Secret Within 90 business days of award

Procurement Clerks Junior Secret Within 90 business days of award

Procurement Clerks Journeyman Secret Within 90 business days of award

Procurement Clerks (Hardware Lead) Senior Secret Within 60 business days of award

Project Management Specialists Junior Secret Within 90 business days of award

Project Management Specialists Journeyman Secret Within 90 business days of award

Project Management Specialists Senior Secret Within 60 business days of award

Technical Writer II N/A Secret Within 90 business days of award

Training and Development Specialists Junior Secret Within 90 business days of award

Training and Development Specialists Journeyman Secret Within 90 business days of award

Training and Development Specialists Senior Secret Within 90 business days of award

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 that facility’s information and security policies.

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: TPS COR, NAWCAD WOLF IDS, 17212

Webster Field Road, B8141, St. Inigoes, MD 20684.

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 the COR, NAWCAD WOLF IDS, 17212 Webster Field Road, B8141, St. Inigoes, MD

20684.

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 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 National

Security Presidential Memorandum 28 (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 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. The

Contractor shall submit an OPSEC Plan IAW CDRL A008.

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.2.7 Cybersecurity.

3.2.7.1 Cybersecurity Plan.

For cybersecurity requirements see the Cybersecurity Plan, Attachment X. Specifically mentioned policies in the Cybersecurity Plan can be accessed via the Cybersecurity Policy Chart at the following link: https://dodiac.dtic.mil/dod-cybersecurity-policy-chart/.

The Contractor shall be required to deliver a Program Cybersecurity Implementation Plan (CSIP) or Annex CSIP to address each of the sections of the Cybersecurity Plan. The Contractor shall demonstrate its understanding of the Cybersecurity Plan and describe how the requirement of each of the sections of the Cybersecurity Plan will be achieved by the Contractor. Sections of the

Cybersecurity Plan that are NOT applicable are required to be addressed.

The Contractor shall describe why a particular section is not applicable. The final Program CSIP shall be in Adobe Acrobat format with a digital signature from the Contractor’s Cognizant

Authority.

If no approved Program CSIP currently exists between the Contractor and the Government, then one must be created and submitted. If an approved Program CSIP already exists and sufficiently satisfies the Cybersecurity Plan requirements for the TO, then no new CSIP delivery is required.

In such cases, the Contractor, in consultation with the Government, shall only submit a Contract

Letter to the Government stating that all Cybersecurity Plan requirements are satisfied by the existing Program CSIP.

If Cybersecurity Plan requirements are NOT adequately addressed by the existing Program

CSIP, then an update to the Program CSIP or a supplemental CSIP document referred to as an

“Annex CSIP” shall be created to satisfy the Cybersecurity Plan requirements. An Annex CSIP shall address unique Cybersecurity Plan Section "G" Assessment and Authorization requirements if a system is being delivered under the TO and unique Section "Q" Software requirements if software is being delivered. These Program CSIP updates or Annex CSIPs shall be submitted

IAW CDRL A009.

3.3 Detailed Support Requirements.

3.3.1 Technical/Project Management Support.

3.3.1(a) Utilize PROC to support technical/project management support efforts for in-production IDS Division systems to include production, modification, retrofitting, and modernization. Applicable to SOW paragraphs 3.3.1.1 - 3.3.1.21.

3.3.1(b) Utilize O&M to support technical/project management support efforts for IDS Division

In-Service Engineering Activities (ISEAs) such as the repair, sustainment, and maintenance of

IDS operational systems. Applicable to SOW paragraphs 3.3.1.1 - 3.3.1.21.

3.3.1(c) Utilize FMS to support technical/project management support efforts for IDS Division systems throughout the project life cycle for international support projects. Applicable to SOW paragraphs 3.3.1.1 - 3.3.1.21.

3.3.1(d) Utilize RDT&E to support technical/project management support efforts for IDS

Division systems in varying stages of research and development to include concept development, design, prototyping, and testing. Applicable to SOW paragraphs 3.3.1.1 - 3.3.1.21.

3.3.1(e) Utilize WCF to support technical/project management support efforts for IDS Division systems throughout the project life cycle. Applicable to SOW paragraphs 3.3.1.1 - 3.3.1.21.

3.3.1(f) Utilize Non-DoD to support technical/project management support efforts for IDS

Division systems in support of Non-DoD IDS Division project and sponsors. Applicable to SOW paragraphs 3.3.1.1 - 3.3.1.21.

3.3.1.1 The Contractor shall provide support for the development and maintenance of Division-directed technical management tools.

3.3.1.2 The Contractor shall provide support with Internal Project Reviews (IPRs) with

Government Project Leads (GPLs) and maintain tracking documentation in the IDS Division

Document Repository System.

3.3.1.3 The Contractor shall provide support for the development and maintenance of detailed project schedules and project cost estimates and by maintaining documentation in the IDS

Division Document Repository System.

3.3.1.4 The Contractor shall provide support by conducting ongoing monitoring of IDS

Division projects by analyzing, planning, and providing status and by maintaining documentation in the IDS Division Document Repository System.

3.3.1.5 The Contractor shall provide support with drafting and analyzing project cost, schedule, and scope risks by utilizing IDS Division-directed project management tools and by maintaining documentation in the IDS Division Document Repository System.

3.3.1.6 The Contractor shall provide technical support to GPLs for design reviews, production reviews, and meetings by preparing documentation such as agendas, meeting minutes, action item assignments, briefs, Plans of Actions & Milestone (POA&M) schedules, presentations, charts, and illustrations and by maintaining documentation in the IDS Division Document

Repository System. (CDRLs A010, A011, and A013)

3.3.1.7 The Contractor shall provide support by supplying inputs to the Government regarding technical and non-technical project risks and by supporting the project’s Risk Management Plan

(RMP) through risk identification, conducting risk analysis, risk mitigation planning, and monitoring risks to closure.

3.3.1.8 The Contractor shall provide support for fiscal status reviews of IDS Division projects by utilizing information provided by the projects to identify where significant deviations between the actual and planned funding profiles exist and by conducting further review to determine the cause of the variance by using processes, guidance, and document analysis within IDS Division-directed Project Performance Documentation tools.

3.3.1.9 The Contractor shall support project reviews related to IDS Division’s portfolio for out-year funding planning and execution feasibility.

3.3.1.10 The Contractor shall provide support for the development and maintenance of the overall IDS Division’s portfolio budget.

3.3.1.11 The Contractor shall provide support by conducting internal Program Management

Reviews (PMRs) with IDS Division leadership.

3.3.1.12 The Contractor shall provide support by collaborating with GPLs and Integrated

Product Teams across IDS Division functional areas to gather key information and forecast metrics.

3.3.1.13 The Contractor shall provide support for IDS Division technical-/non-technical-related data calls, meetings, and project financial execution to include reviewing, maintaining, and providing inputs.

3.3.1.14 The Contractor shall provide support with maintaining and updating a tracking report for post-award IDS Division service contract Navy Enterprise Resource Planning (N-ERP)

Purchase Request (PR) to facilitate timely and accurate IDS Division process workflows in coordination with Government resources to determine list order/priority adjustments and by maintaining documentation in the IDS Division Document Repository System. (CDRL A012)

3.3.1.15 The Contractor shall provide support with routine team meetings to include the preparation of agendas and meeting minutes and by conducting action item tracking. (CDRLs

A011 and A013)

3.3.1.16 The Contractor shall provide financial support to include preparation of N-ERP PRs and by maintaining financial reports derived from N-ERP to track monthly burn rates, commitments, obligations, and expenditures IAW established project plans.

3.3.1.17 The Contractor shall provide support to GPLs by reviewing project expenditures and monitoring contract obligation plans IAW command funding cycles and abide by Procurement

Group Procurement Action Lead Times (PALTs).

3.3.1.18 The Contractor shall provide support to the GPLs by conducting data entry and reviewing project management financial information by utilizing IDS tracking tools and software.

3.3.1.19 The Contractor shall provide support to GPLs by coordinating project schedule timelines to comply with all project milestones.

3.3.1.20 The Contractor shall support the GPLs by obtaining and maintaining knowledge of latest version of the NAWCAD security manual and draft hardware DD-254 documents or modifications when requested.

3.3.1.21 The Contractor shall support IDS Division Security Representative(s).

3.3.1.21.1 The Contractor shall support IDS Security’s maintenance of logbooks, building access lists, and visitor logs.

3.3.1.21.2 The Contractor shall support IDS Security by processing classified and unclassified visit requests, checking visitor identification, verifying visitor security clearances, and issuing and maintaining visitor badges.

3.3.1.21.3 The Contractor shall support IDS Security by coordinating end-of-day facility checks and maintaining records for end-of-day security checks.

3.3.1.21.4 The Contractor shall support IDS Security’s administration of controlled access and restricted spaces and maintain proper and correct documentation and records for IDS-controlled access spaces, including CAC/pin encoding for building and lab access.

3.3.1.21.5 The Contractor shall support IDS Security by maintaining access to Defense

Information System for Security (DISS) and other security data access systems to input and process visit requests.

3.3.2 Budget Execution Support.

3.3.2(a) Utilize PROC to support budget execution support for in-production IDS Division systems to include production, modification, retrofitting, and modernization. Applicable to SOW paragraphs 3.3.2.1 - 3.3.2.13.

3.3.2(b) Utilize O&M to support budget execution for IDS Division ISEAs such as the repair, sustainment, and maintenance of IDS operational systems. Applicable to SOW paragraphs

3.3.2.1 - 3.3.2.13.

3.3.2(c) Utilize FMS to support budget execution for IDS Division systems throughout the project life cycle for international support projects. Applicable to SOW paragraphs 3.3.2.1 -

3.3.2.13.

3.3.2(d) Utilize RDT&E to support budget execution for IDS Division systems in varying stages of research and development to include concept development, design, prototyping, and testing.

Applicable to SOW paragraphs 3.3.2.1 - 3.3.2.13.

3.3.2(e) Utilize WCF to support budget execution for IDS Division systems throughout the project life cycle. Applicable to SOW paragraphs 3.3.2.1 - 3.3.2.13.

3.3.2(f) Utilize Non-DoD to support budget execution for IDS Division systems in support of

Non-DoD IDS Division project and sponsors. Applicable to SOW paragraphs 3.3.2.1 - 3.3.2.13.

3.3.2.1 The Contractor shall support by providing the IDS Division GPLs with financial analytics, to include obligation and expenditure planning, throughout project life cycle IAW

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

3.3.2.2 The Contractor shall support the execution of Planning, Programming, Budgeting, and

Execution (PPBE) processes IAW DoDD 7045.14, The Planning, Programming, Budgeting, and

Execution (PPBE) Process by identifying funding allocations for project and IDS Division operations.

3.3.2.3 The Contractor shall support receiving, processing, monitoring, and executing incoming and outgoing funding throughout a project’s life cycle.

3.3.2.4 The Contractor shall provide support with tracking and reviewing N-ERP spend plans, expenditures, reconciliations, and closeouts.

3.3.2.5 The Contractor shall support the preparation of weekly reports by identifying data for all funding received, committed, obligated, and expended by project and appropriation type to be incorporated into IDS Division project management tools and by conducting risk identification to present options for resolution.

3.3.2.6 The Contractor shall provide support with the preparation of outgoing funding documents while meeting the accuracy and timeliness as defined by the IDS Division Business

Financial Managers (BFMs).

3.3.2.7 The Contractor shall provide support by reviewing and reporting the status of

Unliquidated Obligations (ULOs) and by determining the best path toward the reconciliation of these ULOs to meet fiscal year requirements IAW Division timelines.

3.3.2.8 The Contractor shall provide support to GPLs for the planning and execution of N-ERP project Work Breakdown Structures (WBSs).

3.3.2.9 The Contractor shall provide support for the development and maintenance of project structures in N-ERP.

3.3.2.10 The Contractor shall provide support by reviewing actual obligations in comparison to obligation plans and identifying discrepancies.

3.3.2.11 The Contractor shall provide support by reviewing actual expenditures in comparison to expenditure plans and identifying discrepancies.

3.3.2.12 The Contractor shall provide support by creating reports and tracking funding from acceptance through final billing in N-ERP.

3.3.2.13 The Contractor shall provide support with drafting PRs within N-ERP for post-award service contract requirements as required IAW IDS Division workflows and by providing the required documentation for each action.

3.3.3 Material Procurement Support.

3.3.3(a) Utilize PROC to provide material procurement support for in-production IDS Division systems to include production, modification, retrofitting, and modernization. Applicable to SOW paragraphs 3.3.3.1 - 3.3.3.8.

3.3.3(b) Utilize O&M to provide material procurement support for IDS Division ISEAs such as the repair, sustainment, and maintenance of IDS operational systems. Applicable to SOW paragraphs 3.3.3.1 - 3.3.3.8.

3.3.3(c) Utilize FMS to provide material procurement support for IDS Division systems throughout the project life cycle for international support projects. Applicable to SOW paragraphs 3.3.3.1 - 3.3.3.8.

3.3.3(d) Utilize RDT&E to provide material procurement support for IDS Division systems in varying stages of research and development to include concept development, design, prototyping, and testing. Applicable to SOW paragraphs 3.3.3.1 - 3.3.3.8.

3.3.3(e) Utilize WCF to provide material procurement support IDS Division systems throughout the project life cycle. Applicable to SOW paragraphs 3.3.3.1 - 3.3.3.8.

3.3.3(f) Utilize Non-DoD to provide material procurement support for IDS Division systems in support of Non-DoD IDS Division project and sponsors. Applicable to SOW paragraphs 3.3.3.1 -

3.3.3.8.

3.3.3.1 The Contractor shall provide support by drafting PRs within N-ERP for hardware/material procurements and by developing documentation IAW DoD, Command, and

Contracting Activity formats and standards for new procurements and modifications to include procurement submissions in applicable Command Tools.

3.3.3.2 The Contractor shall provide support by tracking IDS Division upcoming and in-process hardware/material procurement requirements from planning, award, receipt, inspection, and acceptance.

3.3.3.3 The Contractor shall provide support by reviewing hardware technical requirements for acquisition and preparing hardware procurement packages (e.g., SOWs and CDRLs) IAW DoD policies, Command, and Contracting Activity formats and standards.

3.3.3.4 The Contractor shall provide support to the GPLs in the review of project requirements to acquire hardware, software, and other material including documenting market research;

evaluating whether commercial items or non-developmental items are available; and providing the required acquisition documentation, submission, tracking, and reporting based on the type of strategy determined.

3.3.3.5 The Contractor shall provide support for the monitoring and tracking of material/equipment both within N-ERP and via IDS Division tracking tools during stages of the procurement process spanning from procurement planning to delivery of the final product to the

Government.

3.3.3.6 The Contractor shall support tracking hardware packages during the review cycle using data received from Government sources and by providing status updates, conducting procurement tracking, and maintaining tracking documentation in the IDS Division Document

Repository System.

3.3.3.7 The Contractor shall provide support with initiating and tracking Government Purchase

Card (GPC) requests IAW IDS Division workflows, DoD policies, and Command formats and standards.

3.3.3.8 The Contractor shall provide support for the monitoring of all procurement actions from initiation through closeout. (CDRL A014)

3.3.4 Data Management Support.

3.3.4(a) Utilize PROC to provide data management support for in-production IDS Division systems to include production, modification, retrofitting, and modernization. Applicable to SOW paragraphs 3.3.4.1 - 3.3.4.10.

3.3.4(b) Utilize O&M to provide data management support for IDS Division ISEAs such as the repair, sustainment, and maintenance of IDS operational systems. Applicable to SOW paragraphs

3.3.4.1 - 3.3.4.10.

3.3.4(c) Utilize FMS to provide data management support for IDS Division systems throughout the project life cycle for international support projects. Applicable to SOW paragraphs 3.3.4.1 -

3.3.4.10.

3.3.4(d) Utilize RDT&E to provide data management support for IDS Division systems in varying stages of research and development to include concept development, design, prototyping, and testing. Applicable to SOW paragraphs 3.3.4.1 - 3.3.4.10.

3.3.4(e) Utilize WCF to provide data management support IDS Division systems throughout the project life cycle. Applicable to SOW paragraphs 3.3.4.1 - 3.3.4.10.

3.3.4(f) Utilize Non-DoD to provide data management support for IDS Division systems in support of Non-DoD IDS Division project and sponsors. Applicable to SOW paragraphs 3.3.4.1 -

3.3.4.10.

3.3.4.1 The Contractor shall provide support for IDS Division Document Repository System management by arranging online data storage to combine Industry best practices with

Government-mandated processes to create and maintain an organized, practical, and intuitive structure.

3.3.4.2 The Contractor shall provide support by developing, upgrading, and/or enhancing the arrangement, structure, methodology, layout, tools, and access procedures of the IDS Division

Document Repository System for IDS Division data storage.

3.3.4.3 The Contractor shall provide support for IDS Division data management including systematic arrangements, methodology, and structuring for ease of access, review, and retrieval.

3.3.4.4 The Contractor shall support the development, monitoring, and periodic upgrades of structure, categorization, naming conventions, retrieval, and disposition of IDS Division data.

3.3.4.5 The Contractor shall provide support for project database reporting for the IDS

Division to insure interoperability of data reporting from project level to IDS Division and

Command levels.

3.3.4.6 The Contractor shall support the development and management of automated project reporting including processes, collection, validation, and maintenance of accuracy.

3.3.4.7 The Contractor shall support creation and maintenance of an automated process for project reporting that is interoperable with the Command project database tools for technical management and engineering analysis support including schedules, financial tracking, Systems

Engineering Technical Review (SETR) events, project milestones, and test and delivery dates.

3.3.4.8 The Contractor shall support the development and maintenance of automated financial tracking tools for monitoring project, branch, and IDS Division funds.

3.3.4.9 The Contractor shall support the development of automated financial tracking tools that support interoperability with N-ERP and by providing automated tracking for estimates, spend plans, obligations, and expenditures.

3.3.4.10 The Contractor shall support the development and maintenance of the IDS Division

Document Repository System or web-based tools for the optimization of IDS Division processes including civilian travel planning and approvals, leave calendars, overtime and compensatory time approvals, telework tracking and approvals, and other analytics driven automation tools for business operations.

3.3.5 Training.

3.3.5(a) Utilize PROC to support development and execution of technical project management training for in-production IDS Division systems to include production, modification, retrofitting, and modernization. Applicable to SOW paragraphs 3.3.5.1 - 3.3.5.5.

3.3.5(b) Utilize O&M to support development and execution of technical project management training for IDS Division ISEAs such as the repair, sustainment, and maintenance of IDS operational systems…