Performance Work Statement.pdf

Performance Work Statement (PWS) Maritime Operations Center (MOC) / Ballistic Missile Defense (BMD) /

Type Command (TYCOM) Naval Information Forces (NAVIFOR) N83

1.0 INTRODUCTION

1.1 Navy Maritime Operations Centers (MOCs) were developed as an Operational-level of War (OLW) Navy component commander (NCC) and numbered fleet commander (NFC) warfighting capability to be organized, trained, manned, and equipped to support commander’s decision-making and set conditions for operational command and control (C2) of naval, joint, and combined forces. The Chief of Naval Operations (CNO) established the MOC Standard to deliver fully interoperable MOCs that can execute common missions, functions, and tasks (MFTs) in support of combatant commanders.

1.2 In collaboration with Commander, U.S. Pacific Fleet (CPF), AN is assigned authority to develop and set the MOC Standard, to include MFTs, procedures, organization, training, manning, and equipping requirements. Additionally, USFFC and CPF have responsibilities to develop MOC policy and submit program and budget requirements necessary to maintain the MOC Standard and ensure the warfighting readiness of the MOCs.

2.0 BACKGROUND

2.1 USFF and CPF established the Fleet MOC Standardization Council (FMSC) at the primary forum for implementing the MOC Standard; prioritizing OLW/MOC warfighting gaps; approving solution to OLW/MOC issues and deficiencies; providing recommendations on requested non-standard support; and providing prioritized recommendations to the appropriate OPNAV sponsor for resourcing.

2.1.1 The FMSC represents all NCC/NFCs and consists of an executive steering committee (ESC), executive working group (EWG), and four standing working groups. The ESC membership includes all NCC/NFC Deputy Commanders and is chaired by the USFF Deputy Commander. The EWG is the FMSC’s primary collaborative forum for referring fleet OLW/MOC issues to the ESC. The EWG membership includes all NCC/NFC MOC Directors and the leads of the four standing working groups – Manpower/Manning WG; Training WG; Materiel WG; and the Requirements WG.

2.1.2 The FMSC Requirements WG is chaired by USFF N83, MOC Capabilities Branch Lead, and functions at the OLW/MOC warfare improvement program (WIP). The Requirement WG:

2.1.2.1 Operates in accordance with COMFLTFORCOM/COMPACFLTINST 7101.3, Warfare Improvement Programs and Fleet Collaborative Teams in Support of Integrated Fleet Capabilities Requirements, for capturing, vetting, and prioritizing fleet OLW/MOC capability needs to improve readiness and optimize resources.

2.1.2.2 Coordinates the conduct of the Fall and Spring WIP workshops and the production of the Integrated Prioritized Capabilities List, which serves as the authoritative source of input to the OPNAV planning and programming process and the primary fleet MOC standardization POM deliverable.

2.1.3 To fulfill FMSC Requirements WG responsibilities, NAVIFOR N83 performs the following in support of OLW/MOC:

2.1.3.1 Coordinates Fleet assessment of OLW/MOC capabilities and warfighting gaps in support of the Navy Planning, Programming, Budgeting, and Execution (PPBE) process and provides recommendations for development and transition of new OLW/MOC capabilities.

2.1.3.2 Develops the annual OLW/MOC Integrated Prioritized Capabilities List (IPCL) to articulate these capability requirements, gaps and recommendations.

2.1.3.3 Develops the bi-annual Baseline Configuration Change Plan (BCCP) for MOCs and conducts assessment of OLW/MOC capabilities in support of the Force Development Systems Wholeness Assessments (SWA) and Capability and Capacity Assessments (C/CA).

2.1.3.4 Collaborates with stakeholders such as NCCs, NFCs, NWDC, NWC, PEO-C4I, NAVIFOR, OPNAV N2/N6, and SMWDC to provide recommendations for the integration of OLW/MOC DOTMLPF-P solutions.

2.1.3.5 Participates in the development of new Concepts of Operations (CONOPS) related to MOC warfighting capabilities.

3.0 OBJECTIVE

3.1 The primary objective of this requirement is to provide a broad range of technical services to support force development and address warfighting capability and systems wholeness gaps across the spectrum of OLW/MOC functional areas by coordinating and tracking OLW/MOC stakeholder efforts and provide expert recommendations to advance future OLW/MOC warfare capabilities. This performance-based requirement includes the full spectrum of support tasks required for the rigorous assessments and analyses of issues vital to fleet commander C2 of distributed maritime operations. These tasks include the overall management of FMSC Requirements WG activities - to include development of objectives, agendas, conference planning, scheduling, facilitation, and recorded summary of key findings, recommendations, and decisions; production of the OLW/MOC IPCL, from initial development to signature; and development of gap solutions, in coordination with MOC stakeholders, for POM submission. Contractor support will provide the depth of understanding required to conduct root cause analysis, analyze alternatives, and develop necessary documentation to advocate for solutions.

4.0 SCOPE OF WORK

4.1 The scope of this PWS encompasses support required to execute the core functions of the NAVIFOR Operational Level of War / Maritime Operations Center (OLW/MOC) Requirements Branch.

4.1.1 Contract support shall fill both a capacity and capability gap in MOC C4I and Manpower, Personnel, Training, & Education (MPT&E) necessary to address fleet OLW C2 warfighting capability gaps articulated in MOC Certification Reports (MCRs) and the OLW/MOC IPCL and serve as the primary interface to external stakeholders on MPT&E and C4I issues at the MOC’s. Specifically, contract support will:

4.1.1.1 Lead MOC C4I and MPT&E sub-working groups to conduct root cause analysis of warfighting capabilities gaps identified in the MCRs.

4.1.1.2 Author the MOC C4I and MPT&E sections of the OLW/MOC IPCL.

4.1.1.3 Develop the MOC BCCP in concert with MOC stakeholders, and coordinate all staffing to ensure timely delivery to the USFFC Force Development Division.

4.1.1.4 Identify MOC C4I and MPT&E issues for Force Development SWA and C/CA consideration and develop supporting documentation from inception to final adjudication.

4.1.1.5 Review doctrine and CONOPS for MOC C4I and MPT&E equities and provide recommendations for modifications and identify potential impacts on future MOC capability requirements.

4.1.2 Contract support shall fill both a capacity and capability gap in maritime fires and BMD C2, planning, integration, assessment and maritime fires necessary to address specific areas articulated in MCRs and the OLW/MOC IPCL and serve as the primary interface to external stakeholders on maritime fires and BMD C2, planning, integration, assessment and integrated maritime fires issues at the MOCs.

Specifically, contract support will:

4.1.2.1 Lead MOC maritime fires and BMD C2 sub-working groups to conduct root cause analysis of warfighting capabilities gaps identified in the MCRs.

4.1.2.2 Author the MOC maritime fires and BMD C2 sections of the OLW/MOC IPCL.

4.1.2.3 Identify MOC maritime fires and BMD C2 issues for Force Development SWA and C/CA consideration and develop supporting documentation from inception to final adjudication.

4.1.2.4 Review doctrine and CONOPS for MOC maritime fires and BMD C2 equities and provide recommendations for modifications and identify potential impacts on future MOC capability requirements.

5.0 MOC C4I and MPT&E TASKS

5.1 Function as the MOC C4I and MPT&E SME in support of NAVIFOR responsibilities to lead the FMSC Requirements WG and the lead for fleet articulation of OLW/MOC warfighting gaps and capability requirements. Specifically:

5.1.1 Provide briefs, Point Papers and other written documents as required to support and defend guidance, structure and manning principles that rationalize the manning of Fleet staffs and MOCs.

5.1.2 Attend weekly Branch meetings and provide weekly verbal and written status report updates to USFF N8/N9 OLW/MOC Branch Director, which will include a summary of relevant tasks, discussions, or products completed that week.

5.1.3 Provide trip reports to NAVIFOR N84 OLW/MOC Branch Lead and the COR in accordance with NAVIFOR standard trip report format.

5.1.4 Produce Issue Papers, White Papers, Analysis reports, PowerPoint Briefs, Comment Resolution inputs, and other written documents as required by the tasks described herein. Provide MOC MPT&E products, to include organizational assessments in support of training and operations.

5.1.5 Use Joint Professional Military Education (JPME) level techniques and analytical skills, as well as an in-depth knowledge of NTTP 3-32.1 and OPNAVINST 3500.42 in the identification, substantiation and advocacy of OLW/MOC MPT&E requirements to provide defined training and education pipelines and associated documentation that supports decisions within the PPBE process.

5.1.6 Coordinate with MOC stakeholders, to include OPNAV, NAVIFOR, PEO C4I, and NCC/NFCs to produce the MOC BCCP on a semi-annual basis.

5.1.7 Develop OLW/MOC SWA and C/CA issues for inclusion in the USFF N94 Force Development submission in support of the annual POM process.

5.1.8 Use Defense Readiness Reporting System-Strategic (DRRS-S) and knowledge of the OPNAV PPBE process to provide written periodic status reports documenting end-to-end tracking of MOC MPT&E requirement identification through solution implementation in accordance with the current POM

OLW/MOC IPCL.

5.1.9 Provide recommended MPT&E-related changes to doctrine, education and training requirements in writing via Comment Resolution Matrix, email or other written format to enhance MOC operations in support of Commander’s decision cycle and battle rhythm.

5.1.10 Participate in the annual development cycle of the OLW/MOC IPCL, with general focus on MOC C4I and MPT&E requirements and a specific focus on the IPCL Manpower and Training and MOC C4I System Architecture capability areas.

5.1.11 Provide written periodic status reports documenting end-to-end tracking of MOC requirement identification through solution implementation in accordance with the current POM OLW/MOC IPCL

5.1.12 Ensure efficient management, oversight and administration of all tasking by the OLW/MOC contractor workforce

5.1.13 Conduct root cause analysis, analysis of alternatives, and necessary documentation to advocate for solutions to address capability gaps across the DOTMLPF-P spectrum.

6.0 INTEGRATED MARITIME FIRES / BMD C2 TASKS

6.1 Function as the MOC maritime fires and BMD C2 SME in support of NAVIFOR N84 responsibilities to lead the FMSC Requirements WG and the lead for fleet articulation of OLW/MOC warfighting gaps and capability requirements. Specifically:

6.1.1 Serve as the primary interface and provide expertise for NAVIFOR N84 OLW/MOC Branch to external stakeholders on BMD C2, planning, integration, assessment and integrated maritime fires issues at the MOCs. Coordinate the identification, analysis, articulation and justification of Fleet MOC BMD requirements at the OLW and provides decision support to senior leadership on BMD C2, planning, integration and assessment as it relates to OLW.

6.1.2 Lead solutions development and analysis efforts to define MOC operational capability needs and requirements in the area of BMD C2, planning, integration, assessment and integrated maritime fires and properly scope the issues in order to identify and propose potential solutions across the DOTMLPF-P spectrum. This effort will require coordination with other area expertise and solution providers.

6.1.3 Attend weekly Branch meetings and provide verbal and written status report updates to NAVIFOR N84 OLW/MOC Branch Lead, which will include a summary of relevant tasks, discussions or products completed that week.

6.1.4 Research relevant operational level guidance and doctrine needed to provide verbal or written recommendations as required for focused engagement with solution providers and other key stakeholders to enact modifications required to address the BMD C2 and maritime fires gaps detailed in the current

POM OLW/MOC IPCL.

6.1.5 Coordinate, under the guidance of the NAVIFOR N84 OLW/MOC Branch Lead, the annual development cycle for the OLW/MOC IPCL. Participate in the development of the OLW/MOC IPCL, with a specific focus on the MOC C2 of BMD and Integrated Fires capability areas.

6.1.6 Use JPME level techniques and analytical skills, as well as an in-depth knowledge of NTTP 3-32.1 and OPNAVINST 3500.42 in the identification, substantiation, and advocacy of OLW/MOC BMD C2, planning & assessment, and integrated maritime fires requirements to present Point Papers and other written documents, reports and briefs as required to document the recommended DOTMLPF-P solutions related to BMD C2, planning, integration, assessment and integrated maritime fires as articulated in the current POM OLW/MOC IPCL and support leadership decisions via the PPBE process.

6.1.7 Provide recommended revisions to MOC doctrine and documents, including NTTP 3-32.1 and OPNAVINST 3500.42, via Comment Resolution Matrix, email or other written means to reflect alignment of MOC BMD and integrated fires elements and processes to facilitate information exchanges with Joint headquarters and subordinate CTFs.

6.1.8 Provide recommendations to develop new or modify existing tools to better facilitate the integration of BMD C2 and integrated fires capabilities. This effort will require knowledge of the following programs/systems: Command & Control Battle Management Communications (C2BMC); Global Command and Control System – Maritime (GCCS-M); Joint Automated Deep Operations Coordination System (JADOCS); Maritime IAMD Planning System (MIPS); AEGIS Mission Planner (AMP); MOC System of Systems; Theater Battle Management Core System (TBMCS); Air Defense System Integrator (ADSI); and Link Monitoring and Management Tool (LMMT).

6.1.9 Provide guidance and expertise in the identification and development of an education and training plan to establish core fleet capabilities to develop target lists and desired effects for non-kinetic weapons.

6.1.10 Use knowledge of the OPNAV PPBE process to provide end-to-end tracking of identification through solution implementation for BMD C2, planning, integration, assessment and maritime fires requirements articulated in the current POM OLW/MOC IPCL.

6.1.11 Provide written and verbal recommendations to the development of a Navy integrated fires and effects synchronization documents, including CONOPS and TTPs.

6.1.12 Coordinate the planning and management of the FMSC Requirements Working Group activities; to include agenda development, scheduling of media resources, briefing material, meeting facilitation, and written summaries provide written periodic status reports documenting end-to-end tracking of MOC requirement identification through solution implementation in accordance with the current POM

OLW/MOC IPCL

6.1.13 The contractor shall identify, substantiation and advocacy of OLW/MOC requirements to provide defined training and education pipelines and associated documentation that supports decisions within the PPBE process.

6.2 Function as the secretariat of the FMSC Requirements Working Group and coordinate all activities required to meet deliverables as identified in the Fleet MOC Standardization Council Instruction.

Specifically:

6.2.1 Maintain a current list of FMSC Requirements WG membership.

6.2.2 At the beginning of each POM cycle, develop a plan for the execution of FMSC Requirements WG activities, to include the Fall Workshop, to ensure the timely delivery of the OLW/MOC IPCL.

6.2.3 Make all arrangements for meeting facilities and media required to execute FMSC Requirements WG activities.

6.2.4 Coordinate development and distribution presentation materials.

6.2.5 Facilitate execution of FMSC Requirements WG meetings.

6.2.6 Produce and distribute summary of FMSC Requirements WG sessions, with specific emphasis on identifying any decisions or recommended follow-on activities that we identified.

7.0 PERSONNEL REQUIREMENTS – Experience/Functional Requirements.

7.1 Personnel Qualifications. Contractors may qualify in more than one knowledge area as outlined above. A Bachelor’s degree or equivalent experience is required for all positions. Equivalent experience to a Bachelor’s degree is two (2) additional years beyond eight (8) years of experience required. Example:

Program Manager (8 years of experience required) – No degree + equivalent (2) years additional experience = total 10 years of experience required.

7.2 C4I/MPT&E Business Support

7.2.1 Responsibilities / Requirements:

7.2.1.1 Serve as the OLW/MOC C4I and MPT&E subject matter expert

7.2.1.2 Attend meetings related to OLW/MOC

7.2.1.3 Serve as the subject matter expert for the advancement of OLW/MOC capabilities.

7.2.1.4 Prepare products for adjudication by NAVIFOR N84 OLW/MOC staffs to include coordination with FCC, OPNAV, TYCOMS, Fleet Commanders, NWDC, WDCs, PEO-C4I, PEO-EIS, PEO-IWS, ONR and other Programs and Commands.

7.2.1.5 Prepare products for review and approval up to the Flag Officer/Senior Executive Service level.

7.2.1.6 Prepare briefs, staffing packages and provide information to update CTS items related to the advancement of Fleet Design.

7.2.1.7 Serve as the single point of contact to the government for all contractor-to-contractor teaming work arrangements and execution responsible for all aspects of contract support to ensure a balance of efficient and effective operations.

7.2.2 Education: A Bachelor’s degree or equivalent experience is required.

7.2.3 Qualifications:

7.2.3.1 Five (5) years cumulative and relevant experience within the last ten (10) years as an action officer on a CCDR, NFC, NCC, Joint, service, or Echelon III or above flag staff required.

7.2.3.2 Three (3) or more years as a Program Analyst on an NFC, NCC, CCMD, or joint staff in an OLW/MOC MPT&E requirements related position.

7.2.3.3 Three (3) or more years as a Program Analyst on an NFC, NCC, CCMD, or joint staff in an OLW/MOC C4I requirements related position.

7.2.3.4 Three (3) years of experience working issues related to the following programs: Fleet Training Management and Planning System (FLTMPS), Navy Training Management and Planning System (NTMPS), Defense Readiness Reporting System (DRRS), and the Training Requirements Module (TRM) of the Corporate Enterprise Training Activity and Resource Systems (CeTARS) is required.

7.2.3.5 JPME Phase I or Joint Experience (desired)

7.2.3.6 Demonstrated knowledge and experience with the OPNAV PPBE process and IPCL development.

7.2.3.7 Demonstrated knowledge and experience with MOC C4I systems and associated manpower and training requirements.

7.2.3.8 Possess analytical skills to support identification, substantiation and advocacy of OLW/MOC MPT&E requirements.

7.2.3.9 Experience determining program objectives, organizing requirements, scheduling projects and developing standards and guidelines.

7.2.3.10 Experience managing multiple projects/tasks simultaneously.

7.2.3.11 Experience managing large complex projects/deliverables with numerous stakeholders.

7.2.3.12 Experience managing relationships across business and customer organizations, and other stakeholders throughout the project cycle.

7.2.3.13 Experience managing multiple priorities and interruptions with minimal impact on productivity/deliverables.

7.2.3.14 Experience ensuring consistency of quality in services across multiple functional areas/commands.

7.2.3.15 Experience employing independent judgment and initiative to manage personnel and resources.

7.2.3.16 Experience leveraging best practices and problem solving.

7.2.4 Security clearance: Top Secret/SCI

7.3 Integrated Maritime Fires/BMD C2 Subject Matter Expert.

7.3.1 Responsibilities / Requirements:

7.3.1.1 Serve as the Integrated Maritime Fires and BMD C2 subject matter expert across the OLW/MOC domain

7.3.1.2 Attend meetings related to OLW/MOC.

7.3.1.3 Prepare products for adjudication by USFF/CPF/CNE staff to include coordination with FCC, OPNAV, TYCOMS, Fleet Commanders, NWDC, WDCs, PEO-C4I, PEO-EIS, PEO-IWS, ONR and other Programs and Commands.

7.3.1.4 Prepare products for review and approval up to the Flag Officer/Senior Executive Service level.

7.3.1.5 Prepare briefs, staffing packages and provide information to update CTS items related to the advancement of OLW/MOC.

7.3.2 Education: Bachelor’s degree

7.3.3 Qualifications:

7.3.3.1 Five (5) years relevant experience within the last ten (10) years as a BMD and/or Fires action officer on a CCDR, NFC, NCC, Joint, service, or Echelon III or above flag staff required.

7.3.3.2 Three (3) or more years experience as a Program Analyst on an NFC, NCC, CCMD, or joint staff in an OLW/MOC BMD C2, planning & assessment, and integrated fires requirements related position required.

7.3.3.3 Three (3) years of experience working issues related to all the following programs: Command & Control, Battle Management Communications (C2BMC); Global Command and Control System – Maritime (GCCS-M); Joint Automated Deep Operations Coordination System (JADOCS); Maritime IAMD Planning System (MIPS); AEGIS Mission Planner, MOC System of Systems, Theater Battle Management Core System (TBMCS); Air Defense Systems Integrator (ADSI); and Link Monitoring and Management Tool (LMMT) required.

7.3.3.4 JPME Phase I or higher (desired)

7.3.3.5 Demonstrated knowledge and experience with the OPNAV PPBE process and IPCL development.

7.3.3.6 Possess analytical skills to support identification, substantiation and advocacy of OLW/MOC BMD C2, planning & assessment, maritime integrated fires requirements.

7.3.3.7 Experience handling multiple priorities and interruptions with minimal impact on productivity/deliverables.

7.3.3.8 Experience with advanced naval technology products and deliverables.

7.3.3.9 Experience as Team or project leader.

7.3.4 Security Clearance: Top Secret/SCI

7.4 Contractor Personnel.

7.4.1 As an umbrella program, it is expected that each contractor employee’s primary role be defined and secondary skills be applied to promote efficiency and flexibility across the effort. It is envisioned that the contractor will effectively manage its workforce across the program including shifting resources to accommodate changes in schedules or high tempo requirements.

7.4.2 The Government requires all contractor personnel proffered for this work to be fully qualified, as per the requirements of the PWS, at time of contract award.

7.4.3 The contractor shall perform all duties in a professional manner. The contractor shall be responsible for establishing and maintaining a favorable relationship with end users and other customer team members to enhance the customer service reputation and quality within NAVIFOR.

8.0 SECURUITY REQUIREMENTS

8.1 OPSEC

8.1.1 IAW DODM 5205.02M, contractor shall protect information listed in the Critical Information List (CIL) and any other sensitive, but unclassified information that may be useful to our adversaries.

Contractor shall abide by OPSEC policies and procedures, as detailed in DODM 5205.02M, COMUSFLTFORCOMINST 3432.1A, and/or as directed by the OPSEC Manager/Officer or an OPSEC Coordinator. Contractor shall accomplish USFF initial OPSEC training within 90 days of in-processing and complete refresher OPSEC training annually. Contractor shall notify their OPSEC Coordinator or the OPSEC Manager/Officer of recommendations for the OPSEC program or potential OPSEC concerns.

POC: USFF OPSEC Program Manager, phone 757-836-4462. The critical information list can be found in COMUSFLTFORCOMSTAFFNOTE 3070 (CRITICAL INFORMATION LIST).

8.2 Security Clearances

8.2.1 Contractor personnel supporting this effort are required to obtain and possess a Top secret / SCI security clearance under this effort. It is the Contractor’s responsibility to obtain and maintain the appropriate security clearances for its personnel prior to the start and during the performance of work in accordance with the requisite DD254.

8.2.2 The Contractor Facility Security Office (FSO) must abide by the National Industrial Security Program Operating Manual (NISPOM) guideline to ensure new hires receive an initial security and insider threat briefing and defensive security overview of the classification system. In addition, FSO’s must ensure contractors receive and comply with annual security refresher training, participate in periodic and continuous security clearance review and evaluation processes. The FSO must promptly report to the COR all contractor-related security incidents and incidents that may affect the contractor’s trustworthiness or the contractor’s clearance.

8.2.3 The Contractor employee fulfilling this contract must obtain a DoD Common Access Card (CAC).

The CAC is a multi-functional “smart” card. It is the official DoD identification card for military, civil service and Contractor personnel. It is also the DoD Geneva Convention identification card for all military, civil service and Contractors accompanying military personnel in hostile areas. It is used to grant access to DoD installations and some buildings. It is also used to access DoD networks and secure websites. The COR will connect the contractor personnel with the Trusted Agent (TA). The FSO via the COR will submit the contractors Trusted Associate Sponsorship System (TASS) i.e. CAC application to the Trusted Agent who will review, verify, reject and/or approve the application. If rejected, the system notifies the Contractor and records the rejection. If approved, the system will update Defense Enrollment Eligibility Reporting System (DEERS) with the Contractor information and direct the Contractor, by e-mail, to proceed to a military facility/installation that has a Real-time Automated Personnel Identification System (RAPIDS) workstation for CAC issuance.

8.2.4 Contractor personnel shall be required to wear a Contractor identification badge and government supplied badge and/or CAC at all times while on Government property. The Contractor shall take appropriate precautions to prevent security violations, ensure possible compromises are reported in a timely manner, and promote a high level of security awareness among personnel assigned to the contract.

8.2.5 The primary place of performance shall be on-site/off-site at the locations listed (12.4/12.4.1 refers), which dictates that all personnel performing on-site must possess U.S. Citizenship and at a minimum an active DoD clearance at the Secret Level. Contractors may be subject to a Government Security Investigation and must meet eligibility for access to classified information. The positions require the proposed personnel to be trained and certified to DoD requirements in order to perform the duties.

8.2.6 The contractor shall abide by established processes and procedures for the issuance and collection of government furnished Common Access Cards (CACs) for all contractor personnel when there is a new hire, resignation or termination. All CACs contain personal identifiable information (PII) that shall be controlled in accordance with government directives. Upon termination or resignation all CACs are to be returned immediately to the contractor’s respective government appointed Technical Assistant reporting to the COR. The Technical Assistant will ensure the CAC is returned to the COR for proper deactivation and destruction by the USFF Trusted Agent.

8.2.7 Any unauthorized possession of an official identification card, (i.e. CAC) can be prosecuted criminally under section 701 of title 18, United States Code (U.S.C) which prohibits photographing or otherwise reproducing or possessing DoD identification cards in an unauthorized manner, under penalty of fine, imprisonment or both. The Contractor shall have procedures in place to ensure the retrieval and return of the government furnished equipment (CACs) from contractor personnel who are no longer supporting the contract.

8.2.8 The CAC is the property of the U.S. Government and shall not be retained by the cardholder upon expiration, replacement or when the DoD affiliation of the contracted personnel has been terminated.

8.2.9 The contractor is responsible for complying with government facility security requirements.

9.1 DD254

9.1.1 The DD254 provides further details as to the security requirements of this contract. Contractor shall comply with all security instructions and references included in the DD254 throughout the life of this contract and beyond if required. Contractor shall comply with the COMUSFLTFORCOMSTAFFINST

5531.1A (INDUSTRIAL SECURITY PROGRAM).

9.2 Base Access

9.2.1 The Contractor is responsible for and shall obtain CACs for all contractor personnel and vehicle passes for vehicles requiring entry onboard Government installations. The Contractor shall complete and submit the requisite documentation to the COR.

9.3 Physical Security

9.3.1 The Contractor shall be responsible for safeguarding all Government property provided for Contractor use. At the close of each work period, Government facilities, equipment, and materials shall be secured. The Contractor shall follow established Government security procedures for the facility for which they are assigned and/or supporting. Contractor shall comply with the COMUSFLTFORCOMSTAFFINST 5530.2A (PHYSICAL SECURITY PLAN) at all times during the performance of this effort.

9.4 Key Control

9.4.1 The Contractor shall establish and implement methods of making sure all keys and key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons.

NOTE: All references to keys include key cards, CAC, and individual security identification badges. No keys issued to the Contractor by the Government shall be duplicated.

9.4.2 The Contractor shall adhere to the methods/procedures included in their proposed/accepted QCP covering key control. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas.

9.4.3 The Contractor shall immediately report any occurrences of lost or duplicate keys and key cards to the COR and local security official.

9.4.4 In the event keys other than master keys are lost or duplicated the Contractor shall upon direction of the Contracting Officer re-key or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the Government the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due the Contractor. In the event a master key is lost or duplicated all locks and keys for that system shall be replaced by the Government and the total cost deducted from the monthly payment due the Contractor.

9.4.5 The Contractor shall prohibit the use by any persons other than the Contractor’s employees of Government keys and key cards issued to members of that Contractor’s team.

9.4.6 The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas or those personnel authorized entrance by the Government (usually through the use of facility-or event-specific identification badges).

9.5 Lock Combinations

9.5.1 The Contractor shall ensure that all lock combinations are not revealed to unauthorized persons.

9.6 Information Technology System Access:

9.6.1 The Government will furnish designated contractor personnel with appropriate access to the appropriate Navy unclassified and/or classified systems, consistent with security clearances required.

9.7 Contactor Identification.

9.7.1 Personnel shall clearly identify themselves as contractor personnel as follows:

9.7.2 Meetings. Contractor personnel shall identify themselves as and/or be introduced as “contractor personnel” and display distinguishing badges or other visible identification for meetings with government personnel.

9.7.3 Written Correspondence. Contractor personnel shall identify themselves as contractor personnel in all formal and informal written correspondence with government personnel.

9.7.4 Telephone Correspondence. Contractor personnel shall identify themselves as contractors during the initial greeting when participating (initiating or receiving) in telephone conversations with government personnel.

9.8 Contractor Mandatory Required Training:

9.8.1 The contractor is responsible to ensure its employees (and subcontractors) supporting this contract complete and stay up to date on all training required by USFLTFORCOM and supported activities for individuals working on Government installations. Some examples of required training and their requisite course numbers/references are listed below. The required training is subject to change throughout the life of this contract; however, the contractor should assume at least a total of eight (8) hours for all required training courses annually per contractor/subcontractor employee. The contractor shall provide documentation (copies of training certificates) to the contracting officer’s representative confirming that contractor employees have completed the required training within five (5) days of the specific training due date. Required courses are:

Program Course Reference Cyber Awareness DOD-IAA-V12.0 or DOD-IC-IAA-V12.O SECNAVINST 5239.3B, para. 7(a)

(4) Privacy Act & PII DOD-PII-V2.0 SECNAVINST 5211.5E, para.

18(d)(2) Antiterrorism Awareness Level I CENSECFOR-AT-010.1.0 DoDI 2000.16, para. E3.25.1.5 supported by E2.11; E3.18.6 OPSEC NIOC-USOPSEC-2.0 OPNAVINST 3432.1A, para. 3 & para. 4c(3) and

COMUSFLTFORCOMINST

3432.1, para. 8a(7)

Suicide Prevention CPPD-GMT-SAP-1.0 OPNAVINST 1720.4A, para. 5a(1) Records Management DOR-RM-010 Counterintelligence Awareness NCIS Face-to-Face SECNAVINST M-5510.30, chapter 4; employee (to include contractor) is defined in Appendix A

Security Awareness Local Brief/Seminar SECNAVINST M-5510.30, chapter 4 & para. 102; employee (to include contractor) is defined in Appendix A.

Active Shooter CNIC-TRTAS-1.1 USFF Commander directed.

10.0 TRAVEL/ OTHER DIRECT COSTS (ODCs)

10.1 Travel expenses shall be reimbursed on the basis of actual costs in accordance with the Joint Travel Regulations. All travel requests shall be submitted to the COR per USFF travel processes and procedures utilizing the travel authorization request form. All travel shall be approved in advance by the COR.

Advance booking and/or discount rates shall be utilized, whenever possible, if military/government travel is available it should be used.

Description Base Period Option I Option II Option III Option IV FAR 52.217-8 Travel $6,064.00 $5,814.00 $5,864.00 $5,764.00 $4,656.00 $4,656.00

10.2 Non-reimbursable Travel costs.

10.2.1 Travel costs incurred in the replacement of contractor personnel, for any reason, will not be reimbursed by the Government.

10.2.2 No travel or subsistence costs will be reimbursed for work performed within a 50-mile radius of the place of performance where services are being provided.

10.2.3 Relocation cost and travel costs incident to relocation of Government facilities will not be reimbursed.

10.2.4 Relocation cost and travel cost incident to the relocation of contractor/subcontractor employees will not be reimbursed.

10.2.5 Reimbursement of privately owned vehicle mileage from residence to place of primary work assignment, facility/military command, installation or pier on the day of departure or return when travel is expected to commence as a result of embarking a vessel or any other Government furnished transportation in the same general location as primary place of work is not allowed.

11.0 DELIVERABLES/REPORTS

11.1 Deliverables/reports shall meet professional standards and requirements. Deliverables/reports shall be transmitted by electronic means using PDF format according to the identified delivery date per Table 1: Deliverables/Reports. Non-rigid physical media (e.g. compact disk) shall be packaged in a rigid package designated for shipping or mailing. Flexible envelopes shall not be used.

11.2 Monthly Status Report (MSR).

11.2.1 The contractor shall provide a MSR consistent with the invoice period, by the 5th workday of the month, to the COR and technical assistant (TA). The reports shall include the following information:

11.2.1.1 Activities of the past month. A summary of the action taken and progress made on outstanding tasks for the past month, including travel, problems, issues and technical assistance log (as applicable).

11.2.1.2 Activities of the next month. A review of the work planning for the next month to meet task requirements, including projected travel, anticipated risk, and/or issues.

11.2.1.3 Management synergies and efficiencies for the past month. (Table 1, deliverable A001)

11.3 Monthly Financial Status Report (MFSR).

11.3.1 The contractor shall provide a MFSR consistent with the invoice period, by the 10th workday of the month, to the COR. The reports shall include the following information:

11.3.1.1 Hours and travel expended identified by individual, functional role (as applicable), and labor category.

11.4 Trip Report.

11.4.1 The contractor shall submit a post travel trip report to the COR, and applicable Tas within five (5) working days following the conclusion of the trip. The report shall include a summary of timetables, accomplishments, significant discussions, events, contacts and action items. (Table 1, deliverable A004)

11.5 Travel Plan.

11.5.1 Provide a plan for contractor travel prior to each contract year and update as required through the year. Plan should provide number of travelers per trip and planned expenses. (Table 1, deliverable A005)

11.6 Deliverable Table.

Table 1: Deliverables/Reports

NOTE: In addition to the reports/deliverables listed above, additional reports, documents, studies, spreadsheets, products, plans or other emergent requirements requested by USFF shall be provided. The Fleet Design team deliverable matrix below identifies specific deliverables necessary for the successful management and accomplishment of the tasks and the PWS requirements.

Report Description Deliverable Due Date Format

Administrative Deliverables

Monthly Status Report

See PWS Reports (Section 11.2)

A001

Submitted to the COR and ACOR no later than the 10th working day of each month. Not to exceed 5 pages, 10 font with 1 inch margins.

MS Word

Monthly Financial Status Report

See PWS Reports (Section 11.3)

A002

Submitted to the COR and ACOR no later than the 10th of each month.

MS Word / Excel

End of Contract Final Report

See PWS Section 12.7.2, 12.9

A003 Submitted to the COR no later than the 15 days prior to the end of contract performance.

MS Word

Trip Report See PWS Section 11.4

A004 Submitted to the TA no later than 5 working days after the conclusion of the trip. Not to exceed 1 page, pitch 10 font with 1 inch margins

Travel Plan See PWS Section 11.5

A005 Submitted to the COR/TA prior to each contract year and update as required through the year

MS Word

Phase-out Plan The Contractor’s transition management plan (Section 12.8, 12.9)

A006 Submitted to the COR and ACOR no later than the 5 days after start of contract performance.

Technical Deliverables

MOC BCCP

See PWS Section 5.1.6

A010

Semi-annually.

Submitted to USFF N83 prior suspense date set by USFF Force Development Division Officer.

MS Excel

SWA & C/CA See PWS Section 5.1.7

A011 Annually. Submitted to USFF N83 prior suspense date set by USFF Force Development Division Officer.

MS PowerPoint

OLW/MOC IPCL See PWS Section 6.3.6

A012 Annually. Submitted to USFF N83 prior to suspense date set by N83 at the beginning of the POM cycle

12.0 GENERAL INFORMATION

12.1 Period of Performance.

12.1.1 The contract will consist of a twelve (12) month base period, four (4) twelve (12) month option periods/Option Years (OY), and the option to extend services for up to six (6) months pursuant to FAR 52.217-8.

12.2 Recognized Holidays.

12.2.1 Below are the traditional Federal holidays in which Government facilities will be closed. With the exception of responsibilities, such as 24-hour operations to support training events/exercises and real world events, where prior approval has been granted by the COR to perform on-site at the Government installation, Contractor shall follow their corporate policy for work on recognized Federal holidays where on-site performance cannot be conducted:

New Year’s Day Memorial Day

Labor Day Thanksgiving Day

Martin Luther King Jr.’s Birthday Juneteenth Columbus Day Christmas Day President’s Day Independence Day Veteran’s Day

12.3 Hours of Operation.

12.3.1 As required in the accomplishment of this contract and in keeping with a non-personal services contract the Contractor shall be responsible for managing their labor hours. This includes defining core hours during the work week as well as managing the labor hours beyond their defined normal workday and during weekends and federal holidays as well as when the Government facility is closed due to local or national emergencies, administrative closings or other Government directed facility closings.

12.4 Place of Performance.

12.4.1 Work shall be accomplished on-site at Naval Information Forces, 115 Lake View Parkway, Suffolk, VA 23435

12.5 Post-Award Conference, Kickoff and Periodic Progress Meetings.

12.5.1 The Contractor shall attend any post-award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5.

12.5.2 The COR, ACOR, TA, and other Government personnel may also meet periodically with the Contractor to review the Contractor's performance. At times, these meetings may include the Contracting Officer, who will apprise the Contractor of how the Government views the Contractor's performance.

12.5.3 The Contractor shall apprise the Government of any problems being experienced. Appropriate action shall be taken to resolve outstanding issues.

12.6 Phased Transition (Phase-Out).

12.6.1 The Contractor shall develop, submit and maintain a “Phased Transition Plan.” This plan shall be submitted to the COR and ACOR no later than the five (5) days after start of contract performance.

12.6.2 The Plan consists of a Phase-Out (end of contract final report) of incumbent/new contractor teams.

The Phase-Out periods each shall be no more than 30 calendar days from the beginning of contract performance and prior to the end of contract performance. The level of detail for the plan must be sufficient for each of the parties (Government/Contractor) to understand and be able to execute. The plan shall address the ramp up of the contract and the process to ensure that the impact to other programs within NAVIFOR or other Government sites is mitigated.

12.7 Phase-out.

12.7.1 Phase-Out of the contract shall address the transition to the next Contractor team at the end of this contract.

12.7.3 During transition, the Contractor shall provide the following:

12.7.3.1 Conduct indoctrination/orientation for new contractor personnel.

12.7.3.2 Provide training to contractor personnel on specific applications unique to NAVIFOR functional areas.

12.7.3.3 Account for and transfer Government property.

12.7.3.4 Exchange program-related corporate knowledge with incumbent.

12.7.3.5 Observe and participate in exercises and support events in process.

12.7.3.6 Develop administrative and operating processes in coordination with NAVIFOR.

12.7.3.7 Provide end of contract final report that includes final status and financial report (Table 1, deliverable A003 / A006).

13.0 GOVERNMENT FURNISHED AND CONTRACTOR ACQUIRED RESOURCES

13.1 Government Furnished Information (GFI).

13.1.1 The Government will provide operational information and documentation required to meet objectives and tasks identified within this PWS. Initial delivery of required GFI shall be provided within 30 working days from the date of contract award. Subsequent required GFI may necessitate a GFI request by the contractor. Request shall be submitted on official company letterhead or by company electronic mail directed to the COR with an info-copy to the TA. If determined by the COR and/or TA to be a valid request, the COR shall coordinate with the TA to deliver GFI within ten (10) working days (upon receiving the request) and shall notify the contractor in writing or by electronic mail should additional time be required. The contractor shall coordinate all requests for additional technical and contractual information with the COR. The contractor shall acknowledge receipt of all GFI in writing or by electronic mail to the COR within five (5) working days after receipt. All GFI shall be returned to the forwarding government agency when the effort is completed, or if directed by the COR, destroyed using applicable procedures.

13.1.2 The Government will furnish the contractor with necessary software, including public key infrastructure certificates, common access cards to enable contractors to access applications and information systems on NMCI NIPRNET and SIPRNET.

13.1.3 The Government will furnish equipment or facilities needed by the contractor personnel to accomplish objectives and tasks identified in this PWS. The Government will provide the workspace, workstations (desk, chair and personal computer) and local area network (LAN) computer connections necessary to access and use the administrative network used by the Government in the accomplishment of the Contractor-assigned tasks. These networks are for administrative and operations support by the Government and Contractor personnel. The Government will provide access to operations and tactical systems, analytic hardware and software required to support the specific missions. When the Contractor is located at a Government facility, the Government will provide utilities, heating and air conditioning, telephone service, and office supplies for use during the period of the respective contract award. While the Government does not determine or control the number of contractors required for task accomplishment, the Government may limit the number of contractors it can accommodate at the Government facility. Additionally, the Government will approve the location of those contractors working at Government facilities. The Government will make adjustments in the number of workstations and other Government-provided support if changes in numbers of Contractor personnel are required.

13.1.4 Regardless of the place of performance all products and deliverables generated at Government expense become the property of the Government.

13.2 Access to DoD IT Systems

13.2.1 In accordance with SECNAVINST 5510.30, contractor employees who require access to DoN or DoD networks are categorized as IT-I, IT-II, or IT-III. The IT-II level, defined in detail in SECNAVINST 5510.30, includes positions which require access to information protected under the Privacy Act, to include Protected Health Information (PHI). All contractor employees under this contract who require access to Privacy Act protected information are therefore categorized no lower than IT-II. IT Levels are determined by the requiring activity’s Command Information Assurance Manager.

13.2.2 Contractor employees requiring privileged or IT-I level access, (when specified by the terms of the contract) require a Single Scope Background Investigation (SSBI) or T5 or T5R equivalent investigation, which is a higher level investigation than the National Agency Check with Law and Credit (NACLC)/T3/T3R described below. Due to the privileged system access, an investigation suitable for High Risk national security positions is required. Individuals who have access to system control, monitoring, or administration functions (e.g. system administrator, database administrator) require training and certification to Information Assurance Technical Level 1, and must be trained and certified on the Operating System or Computing Environment they are required to maintain.

13.2.3 Access to sensitive IT systems is contingent upon a favorably adjudicated background investigation. When access to IT systems is required for performance of the contractor employee’s duties, such employees shall in-process with the Navy Command’s Security Manager and Information Assurance Manager upon arrival to the Navy command and shall out-process prior to their departure at the completion of the individual’s performance under the contract. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The decision to authorize access to a government IT system/network is inherently governmental. The contractor supervisor is not authorized to sign the SAAR-N; therefore, the government employee with knowledge of the system/network access required or the COR shall sign the SAAR-N as the “supervisor.”

13.2.4 The SAAR-N shall be forwarded to the Command’s Security Manager at least 30 days prior to the individual’s start date. Failure to provide the required documentation at least 30 days prior to the individual’s start date may result in delaying the individual’s start date.

13.2.5 When required to maintain access to required IT systems or networks, the contractor shall ensure that all employees requiring access complete annual Information Assurance (IA) training, and maintain a current requisite background investigation. The Contractor’s Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.

14.0 CONFERENCES AND MEETINGS

14.1 The following requirements are set forth regarding conferences and meetings:

14.1.1 All conferences and meetings shall be chaired by the Government and assisted by the contractor as required.

14.1.2 Face-to-face meetings between the Government and contractor personnel shall require authorization from the COR. Once approved, the COR and contractor shall bi-laterally agree upon the specific location, date, and duration of the conference or meeting.