PWS CNAF_CPRG N8_SUPPORT_Final_30JAN2026.docx

Performance Work Statement to Support Commander, Naval Air Forces (N8/N01M) and Commander, Patrol and Reconnaissance Group (N8) Support Services

1.0 Introduction

This Performance Work Statement (PWS) provides for contractor support services to Commander, Naval Air Forces Pacific, (CNAP) San Diego, CA; Commander, Naval Air Forces Atlantic (CNAL), Norfolk, VA; Commander, Patrol and Reconnaissance Group (CPRG), Norfolk, VA.

2.0 Background

CNAP and CNAL are Echelon 3 commands, and CPRG is an Echelon 4 command, responsible for providing manned, trained and equipped aviation units and aircraft carriers to combatant commanders. Naval Aviation forces are forward, engaged and ready every day. It is a national priority to sustain, resource, and ultimately expand these capabilities to maintain our competitive advantage against all external threats. Consequently, many communities in naval aviation will be in some phase of transition to a new Type/Model/Series (T/M/S) aircraft at any given time and a new class of aircraft carrier will set sail during this contract’s period of performance. As the single voice of aviation requirements for the fleet, CNAP N8 is responsible for ensuring the operational requirements necessary to maintain current readiness of our existing forces (via The Chief of Naval Operations Staff (OPNAV N98/N2N6/N83) and to introduce future aircraft, aircraft carriers, and weapons systems (via OPNAV N98/N2N6) are properly represented.

CNAP N01M is responsible for planning all Navy Aviation transitions to new aircraft, capability upgrades and sundown of legacy capabilities, sundown of legacy platforms, permanent duty station (PDS) and home port changes (HPC), along with establishment and disestablishment of units while maintaining combat readiness in support of the Global Force Management (GFM), the Chief of Naval Operations (CNO) Optimized Fleet Response Plan (OFRP), and any Requests for Forces (RFFs) via the Master Aviation Plan (MAP). CNAP N01M is also responsible for the transition costs associated with all aspects of the transitions and introduction of aircraft and support requirements.

To develop and execute the MAP and the Navy’s Strategic Goals CNAP N01M requires contract support with proficiency in the “man/train/equip” functions of these Echelon 3 and 4 commands, as well as OPNAV’s Planning, Programming, Budgeting, and Execution (PPBE) process. Contractor must have significant experience and proficiency in the Navy’s transition processes, force structure, T/M/S training systems, permanent duty station changes, homeport changes, Immediate Superior in Charge (ISIC) changes, Prepare To Deploy Order (PTDO) requirements, the Navy’s organizational, manpower and manning system, aircrew and maintenance training, National Environmental Policy Act (NEPA) requirements, site evaluation and facilities requirements, basing and infrastructure requirements, Navy finance and budgeting system, operational aviation to include aviation squadrons, air wings and aircraft carriers acquisition, operation, tactics and maintenance. At the Echelon 4 level, contractor support is also required to support continuing transitions to the P-8A Poseidon and MQ-4C Triton Unmanned Aerial System (UAS). In addition, experience with the OPNAV PPBE process, an understanding of the Maritime Patrol and Reconnaissance Aircraft (MPRA) operational mission areas and UAS technologies, and experience with the Navy's manpower at the staff level is required.

3.0 Scope and Objective

Contractor will focus on successful squadron, air wing, and aircraft carrier transition processes, and Type Commander (TYCOM) PPBE processes for manning, basing, facilities, the Flying Hour Program (FHP) account and other accounts associated with the manning, training and equipping of the Naval Air Enterprise (NAE). Contractor reports (analysis and recommendations) will be complex, and the contractor shall offer multiple well-supported recommendations with the express purpose to allow the government decision-maker a meaningful opportunity to make an informed decision in the government’s best interest.

4.0 Task Descriptions

4.1 CNAP N01M T/M/S Transition Support and MAP Development (CNAP HQ, San Diego CA)

4.1.1 Contractor shall provide recommendations into the CNAF MAP, and on manpower, manning and impacts to maintenance/materiel as required.

4.1.2 Review, analyze, and recommend requirements for introduction of new platforms and transitioning aviation communities from legacy to new aircraft and the sundowning of communities. Analysis shall include a determination of requirements for home port/permanent duty station changes, to include manpower and manning implications required to meet these transitions, identification of any shortfalls or excesses in the requirements, with the goal of enabling transitions to occur on the approved timeline. Contractor shall provide recommendations, and alternate recommendations with up-to-date data and data-analysis. Contractor shall prepare, professional presentations that outline processes to be deployed, likely outcomes and alternative outcomes – and shall outline the varying data/information to develop the recommendations. Intended audience: OPNAV resource sponsors, Navy Personnel Command (NPC), Naval Air Systems Command (NAVAIR) leadership, Center for Naval Aviation Technical Training (CNATT), Commander, Navy Installations Command (CNIC), Navy regional commanders, CNAL and CNAP PXO/PCO and PAIMDO training courses, Aviation Flag Officer Training Symposium (AVFOTS) and Aviation Warfighting Commander’s Conference (AIRWARCOM). (CDRL 01, 06)

4.1.3 Analyze the costs of executing the MAP and associated changes. Provide a tatus report outlining costs – with up-to-date cost figures and requirements as requested by the client. (CDRL 06)

4.1.4 Determine outstanding transition requirements for those communities transitioning to new aircraft and sundowning. (CDRL 06)

4.1.5 Provide recommendations, and support with up-to-date data, on changes that will identify the manpower, manning and phasing requirements necessary to ensure squadron, wing and aircraft carrier manpower requirements are planned and programmed to enable execution of the MAP. Analysis should occur in conjunction with MAP development and recommendations shared via the most appropriate means, for example, face to face, telcon, email, up to and including Flag level briefings.

4.1.6 Draft MAP planning documentation for the annual MAP conference to include naval messages announcing the conference, conference agenda and briefing templates, conference scheduling and location, and summary of conference results and future required actions. Coordinate RSVPs and VAR requests with the hosting facility and provide regular updates to the MAP Director and help resolve issues as they are identified. (CDRL 05, 06)

4.1.7 Analyze MAP requirements, transition requirements and sundown requirements for current and future manpower, manning and budget PPBE requirements implications and make recommendations to CNAF N8, OPNAV N98, Performance to Plan (P2P), Naval Sustainment System (NSS) T/M/S Transition Executive Steering Committees (ESC), Fleet Integration Teams, and Project Focus Groups to ensure T/M/S transitions, sundowns, and changes are executed on timeline and within programmed budget. In the development of this analysis, participate in meetings, visits, etc. to provide written feedback on any outstanding requirements.

4.1.8 Semi-annually (spring and fall) develop and present a MAP product, in conjunction with CNAP N01M/CNAL N40 for CNAP/L approval. The information presented within the MAP shall be based upon CNAP/L N40, OPNAV N98, and other Echelon 2 and 3 evaluation of transition plans, deployment schedules and other operational factors. (CDRL 03)

4.1.9 Provide updates to the CNAL/CNAP Safe for Flight (SFF) instruction as required. Provide guidance to CNAF N01M and squadrons when questions or waiver requests are submitted by squadrons which are transitioning to a new Type Model Series (TMS) aircraft or squadrons that are standing up a completely new TMS. Liaison with CNAL and CNAP N codes as required to assist in answering waiver request as required.

4.1.10 Analyze changes in the MAP and provide recommendations to the OPNAV N51 Strategic Laydown and Dispersal (SLD) process during the Design Phase. (Weekly)

4.1.11 Attend the SLD Assessment Phase working group meetings and provide inputs and recommendations regarding shore installation requirements in support of the MAP. (Weekly)

4.2 CPRG Maritime Patrol Reconnaissance Force (MPRF) Transition, MILCON, and NEPA Planning Support (CPRG HQ, Norfolk, VA)

4.2.1 Prepare briefing materials for presentation to MPRF and higher echelon staffs outlining progress, processes, and recommendations for tasks outlined below. Attend periodic stakeholder requirements and transition progress reviews, held at varying intervals, from weekly to quarterly, to obtain up to date goals, objectives, issues, and problem areas highlighted by Department of Navy personnel. Notes shall be prepared as required outlining goals, objectives, issues and problem areas to be integrated into problem solutions outlined in the planning documentation. (CDRL 06)

4.2.2 Review, analyze, and recommend requirements for the MPRF Family of Systems (FoS) Transition and sustainment, to include: P-8A, MQ-4C Triton Multi-Int, advanced airborne sensor (AAS), and P-8 quick reaction capability (QRC). Analysis will include determination of manpower, aircraft, facilities and equipment requirements to introduce and operationally deploy all CPRG FoS capabilities/aircraft in accordance with the timeline specified in the MAP.

4.2.3 Recommend well-researched, data-driven alternatives to the MPRF leadership for the most cost-effective and operationally efficient courses of action to introduce and operationally deploy the FoS capabilities depicted on the MAP. Recommendations should focus on cost-savings without sacrificing mission-essential operations and shared via the most appropriate means, for example, face to face, telcon, email, up to and including Flag level briefings.

4.2.4 Record infrastructure related goals, objectives, issues and problem areas highlighted during stakeholder requirements and transition progress reviews, held at various intervals. Data collected shall be clearly presented to the government in a contractor-determined format. (CDRL 06)

4.2.5 Analyze cost and schedule execution of infrastructure related MPRF FoS capabilities and draft reports in accordance with paragraph 5.0 when requested by the government.

4.2.6 Provide infrastructure inputs to the Maritime Patrol and Reconnaissance Force (MPRF) transition roadmap depicting detailed airframe delivery and assignment, modifications, training, deployment, transition, testing, manpower based on known budgetary realities, and contingency plans for pending budgetary decisions. The roadmap shall include P-8A, VPU MQ-4C, QRC, TOC/MTOC, AAS. (Quarterly)

4.2.7 Evaluate all facility construction project planning documents for P-8A, MQ-4C, and TOC/MTOC at CONUS and OCONUS locations, including attending DD1391 cost estimate and design reviews. Ensure local plans and designs meet Unified Facility Criteria (UFC), program facilities requirements documents (FRD), and other documented requirements and directives. Make recommendations, if the document is not in compliance, for changes, improvements. Update facility construction plans with approved changes, improvements. (Daily)

4.2.8 Coordinate, track, and support all Sensitive Compartmented Information Facility (SCIF) Concept Approval Requests (CAR), Construction Security Plans (CSP), and accreditation efforts for SCIF and Special Access Program (SAP) facilities between cognizant administrative commands, program offices, NAVFAC, and Army Corps organizations. (Daily)

4.2.9 Provide information and requested data for MPRF MILCON or special projects during annual Shore Mission Integration (SMIG) and POM cycle reviews (Annual).

4.2.10 Participate in NEPA stakeholder engagement meetings to obtain data relating to MPRF FoS transitions impacting MPRF air operations; and, to obtain information about mission changes, force structure changes, basing, and construction. Utilize that information to provide recommendations for changes to NEPA documentation, subject of this task.

4.2.11 Track historical MPRF-related NEPA planning documents, specifically highlighting previous Navy statements concerning NEPA planning, BRAC planning and Congressional engagement. Provide a report to CPRG as determined by the government. (CDRL 06)

4.3 CNAP N8C Readiness Requirements Support (CNAP HQ, San Diego, CA)

4.3.1 Analyze readiness requirements. Attend OPNAV N8/83 and other stakeholder readiness requirements reviews and record CNAF (CNAL & CNAP) inputs to the readiness requirements PPBE process. (Bi-monthly)

4.3.2 Provide budgetary analysis for the CNAF Flying Hour Program and related readiness accounts (flying hours, TAD dollars, Projected Related Engineering (PRE)/Projected Related Logistics (PRL) support, depot level maintenance, etc.) for squadrons, air wings and aircraft carriers, required to support the Optimized Fleet Readiness Training Plan (OFRTP) across the Fiscal Year Defense Plan (FYDP). Conduct this analysis annually and report results, based upon current PPBE status, real-time programming and budgeting uncertainty. Make recommendations for the development of requirements and budgeting models for all naval aviation readiness accounts to improve fidelity and the ability to rapidly determine requirements and assess impacts of programming or budgeting decisions affecting the accounts. (CDRL 04, 06)

4.3.3 Support planning and programming of the CNAF Flight Hour Flight Hour Other (1A1A/1A2A) programs for development of POM submissions. Research and prepare briefing material in support of the PPBE process. (CDRL 04)

4.3.4 Provide continuity of the PPBE cycle knowledge and PBIS support to the Flying Hour Program Manager. Serve as the CNAF POC for Cost Adjustment and Visibility Tracking System (CAVTS) validation during the PPBE process. Require PBIS, DataVis, and CAVTS access accounts. (CDRL 04)

4.3.5 Assist N8C in the analysis and interpretation of Carrier Operations and Maintenance budgetary policies, practices, and programmatic changes to include the impact of potential and realized Carrier Operations and Maintenance budgetary shortfalls to support plans, programs and activities. Submit requirement for Ship Operating Account (1B1B) for CNAF annually through both Fleet Forces and COMPACFLT.

4.3.6 Act as the CNAF N8 Requirements Directorate liaison for all matters pertaining to the tracking and analysis of the Aircraft Intermediate Maintenance Depot (AIMD), Air Traffic Control Systems, Aircraft Support Equipment, Aircraft Systems Support and Aviation Depot budgets (Aviation Readiness Accounts 1A4N and 1A5A) throughout the PPBE cycle.

4.3.7 Have access and knowledge to operate both Flying Hour Resource Model (FHRM), Flying Hour Projection System (FHPS), and OPNAV Ship OPS Budget Model.

4.3.8 Comply with all the requirements for CNAP N8C as per the CNAFINST 7300.1 (Flying Hour Program) to include submitting, tracking approval, and monitoring the funding of Flying Hour Other inputs to the budget process (Annual).

4.3.9 Maintain the Unfunded Priority List (UPL) for the current execution year, validating the inputs and coordinating with the CNAP Comptrollers on the requested amounts (Monthly).

4.3.10 Supports TYCOM equities and preparations required for OPNAV N83’s annual Flying Hour Program (FHP) planning conference. Prepares materials, summarizes key issues, priorities, action items, and lessons learned to be incorporated into the following year’s event when feasible. (Annually)

4.3.11 Attend annual Council of Captains (CoC) Conference in the Norfolk/Virginia Beach, VA area. Prepare briefs, issue papers, and respond to questions that may arise as pertaining to the readiness accounts. (CDRL 05)

4.3.12 Attend annual OPNAV Program Requirement Review (PRR) in Pentagon, Washington, D.C. Assist N8C in preparing brief to N98 on next POM cycle’s fleet requirement.

4.4 CNAL N82 Aircraft Carrier Requirements Support (CNAL HQ, Norfolk, VA)

4.4.1 Analyze ship and ship/air integration requirements, draft briefings and make written recommendations to the CVN-78 Class Integrated Transition Team (ITT) and the six Project Focus Groups (Manpower & Manning, Training and Certification, Doctrine & Operations, Maintenance, Logistics, Facilities & Infrastructure) to support the on-time introduction and deployment of CVN-78 Class aircraft carriers in accordance with the MAP. Recommendations shall be data-driven and should include alternatives and associated risks and impacts. (Daily)

4.4.2 Draft briefings for the CVN-78 ITT ESC identifying the risks and risk mitigations for the on-time introduction and deployment of CVN-78 and follow-on ships in class. Make recommendations for the most effective courses of action to meet the deployment schedule considering cost, schedule, and warfighting capability. Review manpower requirements for CVN 78 Class to include onboard underway assessment of workload. (Semi-annually) (CDRL 06)

4.4.3 Facilitate the PFG VI Working Group (Facilities and Infrastructure) by coordinating quarterly meetings on designs, updates, budgetary reviews and progressions for all areas of CVN 78 class support. (Quarterly)

4.4.4 Review and analyze plans for and results of CVN-68 & CVN-78 Class aircraft carriers and related shipboard systems operational tests and evaluations and identify potential risks and mitigations to introduction and deployment schedules. (Quarterly)

4.4.5 Assess impact to transition progress and recommend risk mitigation strategies to the government for problems and issues identified during periodic CVN 78 Class transition progress reviews. (Monthly)

4.4.6 Analyze issues and make recommendations to CNAL N82 on the applicability of new technology to the CVN- 68 and CVN-78 aircraft carrier classes. (Monthly)

4.4.7 Draft CVN Navy Aviation Requirements Group (NARG) planning documentation for the annual CVN NARG conference to include naval messages and/or email announcing the conference, drafting conference agenda and briefing templates for review and approval, conference scheduling and location, disseminating approved messages and materials. Following the conference, the contractor shall prepare a summary of key issues, priorities, action items, and lessons learned to be incorporated into the following year’s event when feasible. (CDRL 05)

4.5 CNAL N83 Infrastructure Requirements Support (CNAL HQ, Norfolk, VA)

4.5.1 Collect and analyze requirements for CNAF Military Construction (MILCON), and facilities sustainment, restoration, and modernization (FSRM) integrated priority lists (IPLs) to support the PPBE process and the introduction of new aircraft and aircraft carriers in accordance with the MAP, and maintain the capability of existing facilities to maintain, train and equip existing squadrons, type wings and aircraft carriers. (Daily)

4.5.2 Brief government-approved CNAF MILCON and FSRM priorities to the region mission integration group (RMIG) and shore mission integration group (SMIG) and input those priorities into the Internet Naval Facilities Assets Data Store (iNFADS) IPL module. (Quarterly)

4.5.3 Provide analysis and make recommendations for CNAP/L inputs to the Unified Facility Criteria (UFC), and Basic Facility Requirement (BFR) development and review processes. (Monthly)

4.5.4 Draft assessment documents for and participate in, CNAP/L facilities assessments that evaluate the condition of naval aviation facilities and then draft recommendations for the government addressing the most effective programming of resources to sustain, renovate, and modernize facilities. Draft recommendations should include alternatives for infrastructure improvements and associated risks. (Quarterly)

4.5.5 Analyze and document operational requirements for basing new aircraft and nuclear-powered aircraft carriers (CVN), draft basing strategies and plans, and make recommendations for the strategic basing of CNAF operational forces consistent with previous basing decisions, national environmental policy act (NEPA) documentation, and policy. (Monthly)

4.5.6 Analyze changes in the MAP and provide recommendations to the OPNAV N52 Strategic Laydown and Dispersal (SLD) process during the Design Phase. (Weekly)

4.5.7 Attend the SLD Assessment Phase working group meetings and provide inputs and recommendations regarding shore installation requirements in support of the MAP. (Weekly)

4.5.8 Maintain continuous tracking of shore installation issues that affect current readiness of CNAP and CNAL subordinate commands. Aggregate and deliver relevant information to validate allocation of execution year TYCOM Operations and Maintenance, Navy (O&MN) resources for aviation shore facility property. (Daily)

4.5.9 Record issues affecting basing, infrastructure, and facilities presented during stakeholder requirements and squadron and aircraft carrier transition progress reviews. Draft recommendations regarding assessed impact of these issues and associated risks to the government, including data-driven alternatives. (CDRL 06) (Monthly)

4.5.10 Review naval aviation related NEPA documentation and ensure operational data inputs to NEPA and Air Installation Compatibility Use Zone (AICUZ) study documents generated by U. S. Fleet Forces (USFF) Shore Readiness Directorate (N46) are accurate and realistic. (Quarterly)

4.5.11 The contractor shall provide logistical support for the annual CNAF Infrastructure Enabling Navy Aviation Requirements Group (ENARG) for approximately 60 attendees, with a facility in the Chesapeake/Virginia Beach, VA area, certified to support up to Secret classified briefings and materials. This support may include drafting naval messages and/or emails announcing the conference, drafting conference agenda and briefing templates for review and approval; and disseminating approved messages and materials. Following the conference, the contractor shall prepare a summary of key issues, priorities, action items, and lessons learned to be incorporated into the following year’s event when feasible. (CDRL 05). (Annually)

4.5.12 The contractor shall provide support for the annual Council of Captains (CoC) meeting. This is an annual, single event for approximately 60 attendees in the Norfolk/Virginia Beach, VA area. Support may include drafting naval messages and/or email announcing the conference, drafting conference agenda, and briefing templates for review and approval; and disseminating approved messages and materials. (CDRL 05) (Annually)

4.5.13 The contractor shall provide logistical support for the annual CNAF N8 Offsite. This is an annual single event for approximately 20 attendees in the Chesapeake, VA area. Support will include coordination with the venue, assisting with security clearance verification, and disseminating approved messages and materials. (CDRL 05) (Annually)

4.6 CNAP N83 Infrastructure Requirements Support (CNAP HQ, San Diego CA)

4.6.1 Assist CNAL N83 in collecting and analyze requirements for CNAF Military Construction (MILCON), and facilities sustainment, restoration, and modernization (FSRM) integrated priority lists (IPLs) to support the PPBE process and the introduction of new aircraft and aircraft carriers in accordance with the MAP, and maintain the capability of existing facilities to maintain, train and equip existing squadrons, type wings and aircraft carriers focusing on the west coast and INDOPACOM theater. (Daily)

4.6.2 Assist CNAL N83 in briefing government-approved CNAF MILCON and FSRM priorities to the region mission integration group (RMIG) and shore mission integration group (SMIG) and input those priorities into the Internet Naval Facilities Assets Data Store (iNFADS) IPL module focusing on the west coast and INDOPACOM theater. (Quarterly)

4.6.3 Provide assessment to CNAP N8 on the condition of west coast naval aviation facilities, basing, and construction requirements and make recommendations for the most effective method of programming for required resourcing. Liaise with OPNAV N98 as required and keep the CNAF N83 Infrastructure Requirements Lead informed of programmatic/budget/PPBE status. (Quarterly)

4.6.4 Provide assessment and recommend inputs to CNAP N8 for the Naval Aviation west coast Regional Mission Integration Group (RMIG) and Shore Mission Integration Group (SMIG) development and review processes. (Quarterly)

4.6.5 Actively participate within the Navy Region Southwest RMIG process by attending meetings and providing analysis and recommendations to the CNAP representative. (Quarterly)

4.6.6 Attend OPNAV’s Strategic Laydown Dispersal (SLD) cycle process and provide analysis, assessment and recommendations to CNAP N8 staff on aviation areas of concern per OPNAVINST 3111.17 (series).

4.7 Staff Requirements Officer Training

4.7.1 The contractor shall develop a training course outline consisting of 8 to 12 hours of instruction in DoN Acquisition, Department of War (DoW) Joint Capabilities Integration and Development System (JCIDS), DoN Requirements, and PPBE. The contractor shall provide three annual training courses for up to 20 CNAL, CNAP and CPRG attendees: two courses at CNAL HQ, Norfolk, VA and one at CNAP HQ, San Diego, CA.

5.0 Contract Data Requirements Lists (CDRL).

Deliverables will vary depending upon the CNAP/CNAL or CPRG division being supported and will be determined by the primary Assistant Chief of Staff. However, the minimum requirements will include the following:

5.1.1 (CDRL 01) Monthly Financial & Status Report (Tasks 4.0 – 4.5): The contractor shall document the efforts performed in the completion of each task in a detailed Monthly Status Report due to the COR and TPOC on or before the tenth of each month. contractor format is acceptable. Minimum report requirements are as follows:

(a) Summaries of the efforts expended on each primary task of the work statement

(b) Notable achievements

(c) Issues or obstacles impeding progress and recommended solutions

(d) Topics or issues identified by the COR with contractor comment and/or mitigation plans

(e) Hours expended by labor category, for reporting period and cumulative total

(f) Cost by labor category, for reporting period and cumulative total

(g) Whether on or off glide slope for annual hours and, if off, by how much and primary rationale

5.1.2 (CDRL 02) Trip Reports (Tasks 4.0 – 4.5): The contractor shall document all travel completed in support of tasks 4.0 – 4.6 in a detailed report and submit to the COR and TPOC within five (5) working days of completed travel. Contractor format is acceptable. Minimum report requirements are as follows:

(a) Dates of and reason for travel

(b) Contacts/meeting attendees

(c) Summary/description of events

(d) Problem Areas/Action Items/Recommendations/Follow-up

5.1.3 (CDRL 03) Master Air Plan (MAP) (Task 4.1.2 and 4.1.3) (Semi- Annually): The contractor shall document results of analysis and recommendations for inclusion into/development of the MAP twice yearly to include all transition costs that are associated with the MAP. Contractor format is acceptable. At a minimum, report will identify man, train and equipment related phasing requirements by squadron, wing and aircraft carrier that are available and associated with the MAP development over a 6-month period. The report shall be submitted to CNAL N40, CNAP N01M, CNAP N40, the COR and TPOC NLT 30 June and 31 December each calendar year.

5.1.4 (CDRL 04) Budget Documents (Task 4.3.2 – 4.3.5) (Annually): During the annual budget cycle (01OCT-15DEC) the contractor shall prepare budget documents for review and submittal by CNAP N8. government format required.

5.1.5 (CDRL 05) Conference Support Summary (Tasks, , 4.4.7, 4.5.11, 4.5.12): Following the CNAF Manpower ENARG, Infrastructure ENARG, CVN NARG, and TPP conferences; the contractor shall prepare a summary in contractor format of key issues, priorities, action items, and lessons learned to be incorporated into the following year’s event when feasible. The summary shall be submitted to the COR NLT 30 calendar days following conference end date.

5.1.6 (CDRL 06) Reports/Briefings (Tasks 4.1-4.5): The contractor shall prepare reports and PowerPoint presentations, and information papers analyzing issues identified as specified in the PWS. Contractor shall provide issue analysis and multiple recommendations, with support for analysis and recommendations provided. No less than quarterly, except where otherwise set forth in the PWS.

5.1.7 (CDRL 07) Staff Requirements Officer Training (Task 47.1) (Annually): The contractor shall submit the course outline for the Staff Requirements Officer Training once annually.

6.0 Travel

This contract will require routine travel to CNAP headquarters in San Diego, CA; CNAL headquarters in Norfolk, VA; OPNAV and other Washington DC sites; Naval Air Systems Command in Patuxent River, MD and OCONUS locations as required. Other less routine travel may be required as determined by the CNAP/CNAL/CPRG N8 and MAP POC’s. All travel must have COR written approval prior to accomplishment.

Contractor personnel shall be authorized travel expenses consistent with the provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified for this contract. The contractor will only invoice and be reimbursed for actual travel expenses incurred.

7.0 Labor Categories and Key Personnel

A single labor category, Principal Analyst, is anticipated. The contractor shall provide only fully qualified and competent personnel to perform the scope of effort set forth herein. The levels of skills, education and experience of the different classifications of personnel provided for contract performance must meet the minimum requirements set forth below.

7.1 Principal Analyst: Minimum of ten years of experience in supporting studies, analyses, surveys and reporting in support of organizational business improvement projects. Demonstrated ability in analysis; working cross-functionally in analyzing, designing and developing business solutions. Proven ability to lead, provide vision, set goals, analyze needs, and define processes at the enterprise level on major programs. Understands customer needs and communicates effectively. Requires a bachelor’s degree in business, finance, engineering, science, mathematics or equivalent and work experience related to systems design analysis, functional requirement analysis, and implementation or transition planning for government or commercial systems and processes. An advanced degree in such a field is highly desirable. Additionally, prior work experience within the last five years directly related to Naval Aviation and the programs/tasks addressed in this work statement is highly desirable.

7.1.1 In addition to the knowledge, skills and experience addressed in 7.1, Task 4.1 requires practical experience in navy aviation squadron, air wing, aviation maintenance, and aircraft carrier introduction and transition processes, the CNAF Master Aviation Plan (MAP), and manpower and transition budget PPBE processes, as well as experience in public speaking to provide regular flag level briefings. Located in San Diego.

7.1.2 In addition to the knowledge, skills and experience addressed in 7.1, Task 4.2 requires experience in the MPRA community and demonstrated depth of knowledge in operational mission areas and deployment cycles. Contractor shall have experience analyzing and planning transition infrastructure basing and NEPA requirements for the P-8 Poseidon, MQ-4C, Advanced Airborne Sensor (AAS), Quick Reaction Capability (QRC), Tactical Operations Center (TOC) and Mobile Tactical Operations Center (MTOC) systems. Contractor shall possess the experience and technical knowledge to prepare and deliver Flag-level presentations on manpower, aircraft, facilities and equipment requirements to facilitate informed decision making. Located in Norfolk.

7.1.3 In addition to the knowledge, skills and experience addressed in 7.1, Task 4.3 requires practical experience in the CNAF Flying Hour Program, Aircraft Depot Maintenance, Weapons Depot Maintenance, Ship Depot Maintenance, and other budgetary accounts associated with squadron, air wing and aircraft carrier readiness accounts, strategic laydown of Naval Aviation units, the DoW PPBE process, Program Budget Information System (PBIS), Flight Hour Resource Model (FHRM), and naval aviation force structure and facilities requirements. Located in San Diego.

7.1.4 In addition to the knowledge, skills and experience addressed in 7.1, Task 4.4 requires demonstrated knowledge of nuclear-powered aircraft carrier operations, engineering, propulsion, ship self-defense, combat systems, and maintenance. Contractor shall demonstrate practical knowledge of Navy aircraft carrier requirements definition process, the aircraft carrier introduction and transition processes, the CNAF MAP, and the PPBE process. Located in Norfolk.

7.1.5 In addition to the knowledge, skills and experience addressed in 7.1, Task 4.5 and Task 4.6 requires a demonstrated understanding of strategic basing initiatives for aircraft and aircraft carriers, with demonstrated knowledge of the Navy’s justification and explanation of the current and known future force laydown. Experience in military construction (MILCON), facility sustainment, restoration and modernization (FSRM) and special project requirements determination and prioritization processes, National Environmental Policy Act requirements as they relate to naval aviation basing and facilities requirements, naval aviation aircraft and aircraft carrier introduction and transition processes, the MAP, Commander, Naval Installations Command (CNIC) Air Operations Program funding, DoN facilities evaluation criteria, and the PPBE process. One located in Norfolk and one in San Diego.

7.2 Key Personnel:

7.2.1 Certain skilled experienced professional and/or technical personnel are essential for completing the work to be performed under this contract. The contractor shall provide resumes for all Key Personnel. No substitutions shall be made of accepted key personnel except for sudden illness, death, or termination of employment, without prior written approval from the COR/KO. Substitutions shall only be accepted if in compliance with paragraph 7.2.2 Substitution of Key Personnel.

7.2.2 Substitution of Key Personnel: All contractor requests for approval of substitutions shall be submitted in writing to the KO and the COR within thirty (30) calendar days in advance of the effective date, whenever possible, and shall provide a detailed explanation of the circumstances necessitating the proposed substitution, a complete resume for the proposed substitute, and any other information requested by the KO necessary to approve or disapprove the proposed substitution.. The KO, the COR, and CNAP N8 Assistant Chief of Staff (ACOS) will evaluate such requests and promptly notify the contractor of approval or disapproval in writing. In certain cases, a period of apprenticeship (with both the existing and incoming contractors working together) may be required to avoid a gap in capability.

7.2.3 Personnel satisfying the labor category listed above in paragraphs 7.1 are considered key personnel.

8.0 Security Requirements

8.1 A Secret security clearance is required for all contract support under this Performance Work Statement except as noted in paragraphs 8.3.

8.2 NMCI/NIPR access is required for all contractors assigned to support this contract. Additionally, contractor personnel assigned to support tasks 4.1, 4.2 and 4.4 require SIPR access.

8.3 As outlined in the DD-254, contractor personnel providing services in support of task 4.1, 4.2 and 4.4 require a Top Secret security clearance, and access to "Sensitive Compartmented Information" (SCI) and "Special Access Programs (SAP)”. Additionally, contractor personnel providing services in support of task 4.4 require access to Restricted Data.

8.4 Contractor facilities must be certified to receive, hold and produce classified materials and support meetings and conferences up to SECRET level.

8.5 The contractor facility security officer (FSO) is responsible for processing investigations for clearance eligibility on all assigned contractor employees. Contractor employees with temporary (interim) access will not be issued a common access card (CAC) until proof of a favorable return of fingerprints or the investigation is completed, and a final clearance determination is rendered.

8.5.1 The contractor FSO shall submit a visit request via the Defense Information for Security System (DISS) to SMO Code N570254 (CNAP) for key personnel assigned to support task 4.1, 4.3 and 4.6; SMO code N570126 (CNAL) for key personnel assigned to support task 4.4 and 4.5; and SMO code N39555 (CPRG) for key personnel assigned to support task 4.2.

8.5.2 The contractor shall coordinate with the Mission Partner Identity, Credential, Access Management (MP ICAM) Sponsor to obtain access credentials for each employee performing services. A Common Access Card (CAC) will be initiated by a MP ICAM Sponsor to gain physical access to DOW installations and logical access to DOW information assurance resources. This access will include Sensitive but Unclassified (SBU) and Personally Identifiable Information (PII). When the CAC is no longer required, the contractor or program manager will recover the CAC from the contractor employee and return the CAC to the MP ICAM Sponsor.

8.5.3 The contractor shall comply with all applicable DOW security regulations, policies and procedures during the performance of this task order. The contractor shall not disclose and must safeguard classified information, procurement sensitive information, computer systems (hardware) and data, Privacy Act data, Sensitive but Unclassified (SBU) information and all other government work obtained or generated in the performance of this contract. Contractor personnel on site will participate in all government activity security awareness training. The contractor FSO shall refer to and follow the National Industrial Security Program Operating Manual (NISPOM) DOD 5220.22-M and applicable government security policies for security guidance.

· DOD 5200.1R Information Security Program

· DOD 5200.2-R Personnel Security Program

8.5.4 The COMNAVAIRPAC Security Manager is Mr. Chris Bruebaker; Email address: christopher.l.bruebaker.civ@us.navy.mil; telephone: 619-767-1534.

8.5.5 The MP ICAM Sponsor for this contract is Frank Nelson, Email address: frank.r.nelson3.civ@us.navy.mil; telephone: 619-545-5370

8.6 Contractor personnel with access to NMCI must comply with current DOW mandated Information Technology (IT) training requirements. The current training requirements are provided in the following table:

Privacy and Personally Identifiable Information (PII) Awareness Training (DOD-PII-(Series))

Annual Navy Knowledge Online, https://wwwa.nko.navy.mil/

Records Management in the DON: Everyone’s Responsibility (DOR- RM-010-(Series))

Annual Navy Knowledge Online, https://wwwa.nko.navy.mil/

8.7 All information or data developed under this contract belongs to and is the property of the U.S. Government and shall be marked and handled as controlled unclassified information (CUI). The contractor shall comply with all applicable DOW security regulations and procedures during the performance of this task order. Contractor shall not disclose and must safeguard procurement sensitive information, computer systems and data, privacy act data, and government personnel work products, which are obtained or generated in the performance of this task order. The Trustworthiness clause is applicable to this task order. Contract security requirements are defined in the contract DD254, Contract Security Classification Specification. The contractor shall comply with all applicable DOW security regulations and procedures during performance of this task order. The contractor shall not disclose and must safeguard sensitive information, computer systems and data, privacy act data and government work products obtained or generated in performance of this task order. Contractor facility and all contractual personnel providing services under this contract must have clearances at time of start date.

8.7.1 Disclosure of Information: Information made available to the contractor by the government for the performance or administration of this effort shall be used only for those purposes and shall not be used in any other way without the express prior written agreement of the KO. The contractor agrees to assume responsibility for protecting the confidentiality of government records, which are not public information. Each employee of the contractor to whom information may be made available or disclosed shall be notified in writing by the contractor that such information may be disclosed only for a purpose and to the extent authorized herein. contractor personnel will be required to execute a Non-Disclosure Agreement (NDA).

8.7.2 Limited Use of Data: Performance of this effort may require the contractor to access and use data and information proprietary to a government agency or government contractor that is of such a nature that its dissemination or use, other than in performance of this effort, would be adverse to the interests of the government and/or others. Contractor and/or contractor personnel shall not divulge or release data or information developed or obtained in performance of this effort, until made public by the government, except to authorized government personnel or upon written approval of the KO.

The contractor shall not use, disclose, or reproduce proprietary data that bears a restrictive legend, other than as required in the performance of this effort. Nothing herein shall preclude the use of any data independently acquired by the contractor without such limitations or prohibit an agreement at no cost to the government between the contractor and the data owner that provides for greater rights to the contractor.

The government shall retain ownership of all government owned data provided to the contractor for use during contract performance. Any data provided to the contractor for use is provided “as is”.

All contract generated deliverables are government property in accordance with DFARS 252.227-7013 (JAN 2025).

9.0 Place of Performance

9.1 Support shall be required on-site to support the CNAP/CNAL and CPRG staffs in Norfolk and San Diego, as necessary. The government will provide office space and administrative support, to include NMCI NIPR and SIPR access, as well as supporting documentation, briefing materials, and information access as required to meet the objectives and required deliverables.

9.2 In the event there is a facility or health issue creating an unsafe environment, contractor employees may telework on a situational basis if authorized by the COR or PCO. The contractor shall maintain a telework agreement with all employees who telework detailing their responsibilities to maintain performance and safeguard government furnished equipment. The contractor will be required to provide a copy to the contracting officer and the COR. The government will provide employees with a CAC Reader to enable access to NMCI email through employee's personal computer, or a NMCI laptop/power cord/computer bag if resources are available. All other equipment/resources (Internet, desk, monitors, chairs etc.) is not the government’s responsibility and is between the contractor and its employees.

10.0 QUALITY ASSURANCE SURVEILLANCE PLAN:

In accordance with the Contract Administration Plan, the COR, with the assistance of the TPOC will measure and evaluate the contractor’s performance based upon the following terms:

Marginal to unsatisfactory performance rating if requirements met less than 80% of the time or less.

Marginal to unsatisfactory performance rating if requirements met 84% of the time or less

Marginal to unsatisfactory performance rating if costs exceed awarded value.

Marginal to unsatisfactory if responsive less than 80% of the time.

Marginal to unsatisfactory rating if contractor unresponsive to government staffing concerns.

Marginal to unsatisfactory rating for a large number of complaints and/or unresolved complaints

PERFORMANCE REQUIREMENTS SUMMARY

11.0 Hours of Operation

Work is generally performed during the government’s core business hours, which are Monday through Friday between the hours of 7:30 AM and 4:00 PM, except federal holidays. The contractor is not required to provide services on federal holidays. The federal holidays are Columbus Day, Veterans Day, Thanksgiving Day, Christmas Day, New Year’s Day, Martin Luther King, Jr. Day, Presidents’ Day, Spring Holiday, Memorial Day, Juneteenth National Independence Day, Independence Day, and Labor Day. Contractor personnel are not permitted in government spaces when no government employee is present.

12.0 Government Points of Contact:

12.1 Contracting Officer’s Representative: CNAP N8 Deputy ACOS, Mr. Brian Martinez, brian.a.martinez5.civ@us.navy.mil, (619) 545-8142

12.2 Technical Point of Contact: CNAP N8 ACOS, CAPT Devon Hockaday, devon.m.hockaday.mil@us.navy.mil, (619) 545-5414