Draft PWS.rtf

PERFORMACE BASED WORK STATEMENT

FOR

Chairman Joint Chiefs of Staff (CJCS) Nuclear Command and Control (NC2) / Joint Staff Assessment Visit and Nuclear Procedures Inspection (JSAV/NPI) Program Support

INTRODUCTION: The Chairman of the Joint Chiefs of Staff (CJCS) Nuclear Command and Control (NC2) Joint Staff Assessment Visit (JSAV) Program and Nuclear Procedures Inspection (NPI) provide support to the Joint Staff J36 Nuclear Operations Division.

BACKROUND: The Joint Staff J36 Nuclear Operations Division (NOD) has responsibility for ensuring that National Nuclear Command and Control (NC2) assets, personnel, and procedures provide national military and civilian leadership with the ability and means to manage and direct appropriate forces, support, and Command & Control (C2) elements, to respond to all threats and employ forces appropriately. The NOD promulgates and maintains the Emergency Action Procedures (EAP) for the CJCS (EAP CJCS) which define and assign key roles and responsibilities within the Department of Defense’s (DOD’s) national NC2 system and establish an elaborate and detailed set of procedures directing numerous aspects of the system and its required capabilities. NPI is the principle means used by the Joint Staff to assess and certify the performance and adequacy of national NC2 components for meeting its objectives.

SCOPE: The NC2 NPI program includes the supporting Command Assistance Visit (JSAV) program and related procedural reviews and assessments. The NPI consists of a series of scenario based operational evaluations, procedural reviews and related command visits and evaluations conducted sequentially at all National Military Command System (NMCS) and Combatant Command (CCMD) centers worldwide. The NPI effort is currently authorized and described in the CJCS Instruction 3262.01(series) This program is designed to support specific Combatant Command Center training needs for its NMCS responsibilities. The objective of this requirement is to support the execution of the CJCS NC2 NPI program through development of scenarios in accordance with Joint Staff objectives and guidance. This includes producing associated scenario background, assessment implementation materials, and providing real time assessment execution support for the Joint Staff J36 NOD and its responsibilities to this program. The scope of this requirement is to provide services and support to the Government for scenario development through an iterative process to meet the annual NPI/JSAV schedule. Scenarios consist of background, starting conditions, simulation material, and assessment implementation material. This requirement also provides support to the Joint Staff for execution of each assessment with real time subject matter expertise, role playing, and simulation management. Assessment types are broken out into three different tasks to accommodate National Military Command Center- Eligible (NMCC-E) NPIs, Non- NMCC-E NPIs, and the JSAV program.

The following list outlines a high-level overview of the NPI Support Process/Phases:

Phase One: Planning:

Develop objectives with Joint Staff

Develop potential threat situations Review current guidance Review intelligence products Develop background framework Identify and develop candidate exercise mission streams Identify candidate planning tasks Identify and coordinate (with USSTRATCOM J7) the development of attack warning simulations (CJCS-EAP Vol IV only)

Phase Two: Baseline Product Development:

Develop rough draft Background (Starter) Packages

Develop rough draft Scripts Phase Three: Initial Review Process:

Conduct initial Script reviews and incorporate feedback Refine/revise Background (Starter) Packages Finalize attack warning simulations (CJCS-EAP Vol IV only) Build supporting message traffic Build Nuclear Planning and Execution System (NPES) inputs (CJCS-EAP Vol IV only) Phase Four: Final Products:

“Dry Run” final script reviews Deliver Background (Starter) Packages Deliver Scripts Deliver attack warning simulations Deliver supporting message traffic Deliver NPES inputs (CJCS-EAP Vol IV only) Phase Five: NPI Execution:

Prepare answers for pre-assessment Requests for Information (RFI) from command Prepare and produce final documentation Coordinate attack warning simulation presentation (CJCS-EAP Vol IV only) Support Joint Staff on location as needed (CJCS-EAP Vol IV only) Serve as role players Assist Joint Staff in drafting of After-Action Report Assist Joint Staff in performance observation Assist Joint Staff with NPES support and analysis (CJCS-EAP Vol IV only)

APPLICABLE DOCUMENTS: CJCS-EAPS and CJCSIs as necessary, within security clearance authorization and “need to know”, to accomplish scenario development and execution.

DELIVERABLES: All deliverables become the property of the United States Government. Unless otherwise stated, all deliverables shall be submitted in both hardcopy and electronic media in Microsoft Word, PowerPoint, Excel, Access, Visio, or Project format. A letter of transmittal shall accompany all deliverables. The Contractor shall support the Joint Staff to produce distinct scenarios for each assessed location. These shall be based on one of several sets of common background situations and events. The scenarios can be further distinguished according to the type of command and/or facility being assessed and depending on the role and location of the facility, as well as the purpose of the Joint Staff visit. The most involved NPI scenarios are produced and administered at NMCC-Es. Non-NMCC-E commands (those without specific delineated responsibilities in EAP CJCS Volume IV) have more limited NC2 roles and their NPIs reflect this. JSAV scenarios are individually specified based on required needs and are typically focused on a narrower subset of the EAP CJCS procedures. The Joint Staff conducts and administers the NPI/JSAV program on an annual calendar year cycle with assessments beginning in January through June. JSAVs for the CCMD can be scheduled at any time during the calendar year. The NPI development cycle begins in July of each year. The Contractor shall adhere to the annual NPI calendar cycle. The Government may require surge support during the base or any option period. Surge modifications will be within the scope of the Contract and provide increased support for the defined Tasks of this PWS. Surge support over the life of the Contract will not exceed 15% of the Contractor’s total proposed cost/price for the base and all option periods, excluding any six-month extension of services pursuant to FAR 52.217-8.

6.0: REQUIREMENTS

Task 1 – Contract Management. The Contractor shall integrate and coordinate all activities needed to execute, in an effective and efficient manner, all requirements in this PWS. The Contractor shall manage the timeliness, completeness, and quality of the requirements herein. The Contractor shall ensure that support is provided to match the tasks and required outcomes of this PWS. The Contractor shall maintain optimal levels of organizational resources, staffing, and utilize management controls to meet task quality and schedule requirements throughout the duration of this Contract.

The Contractor shall develop a rolling 90-day Action Plan, which shall provide quality assurance and progress/status reporting on a monthly basis to the COR(s), in coordination with any Government team/project/portfolio leads. The Contractor shall address schedule and performance in the 90-Day Action Plan, noting any problems, risks, and alternative courses of action (COA), recommending solutions, and identifying tasks requiring Government decision or interaction. The Contractor shall proactively identify and prioritize risks and alternative COAs sufficiently in advance to permit Government feedback, intervention and/or action before a risk becomes an issue. The 90-Day Action Plan shall cover the 30-days preceding the period and the 90 days following the period, for a total of 120 days. For the preceding 30 days, the Contractor shall also include: (1) the number of tasks and deliverables not performed or delivered on time; (2) number of tasks and deliverables that required re-work. The Government will determine, after discussions with the Contractor, whether any rework was due to circumstance beyond the Contractor’s control. Any task or deliverable requiring rework, determined by the Government to be beyond the Contractor’s control, will be reduced from the numbers initially presented by the Contractor.

The Contractor shall provide a monthly status report (MSR) no later than the tenth calendar day from the previous month. The MSR shall describe the activities performed, issues needing resolution, and activities planned for the next reporting cycle. The MSR should include a brief description of activities and deliverables during the current month, identification of personnel reassignments (including personnel added or removed), quality assurance measures, estimated date of funds depletion, and the status of invoicing. The monthly progress/status report shall include a Contractor submitted personnel roster that clearly indicates staffing levels on a monthly basis. The MSR shall include specific identification and tracking of any Government Furnished Property (GFP).

6.1 Deliverables

PWS Reference Title Format (See PWS Section 6.11 for additional details) Due Date Distribution/Delivery Method Frequency and Remarks 6.1 90-day Action Plan Contractor 1st Business Day of Each Month Email to COR Monthly 6.1

MSR

Contractor 10th Calendar Day of Each Month Email to COR Monthly

Task 2 – NMCC-E NPI Support. The Contractor shall produce assessment enabling materials (described in the Subtasks listed below) to support the Joint Staff in conducting NPI assessments of NMCC-Es at applicable NMCS nodes. When referencing NMCC-Es, note that each OT at the NMCC-Pentagon (NMCC-PNT) will be individually assessed. Additionally, each NAOC Team will be considered in the same fashion. While the task and deliverable descriptions that follow are unclassified, the actual deliverables to be produced by the Contractor shall be classified up to the TOP SECRET level. The Contractor personnel shall access and process ACCM, FRD, SCI, COSMIC TOP SECRET, NATO SECRET, NC2-ESI, and communications associated with this task.

The Contractor shall gathering and articulating Joint Staff objectives for the upcoming year based on the following milestones:

Milestone 1: Receive the Joint Staff approval for further developing the Candidate Assessment Scenarios (as described in section 6.1.3).

Milestone 2: The Contractor shall deliver to the COR the Strawman Packages, along with accompanying Conferencing Scripts. The Joint Staff reviews these scripts and approves the proposed assessment scenarios for modification and application for each NMCC-PNT Operations Team & NMCC-E to be assessed.

Milestone 3: Candidate Assessment Scenario variants are delivered to the COR, who delivers the product to the Joint Staff for each location being assessed.

The Contractor shall support gather and articulate Joint Staff objectives for the upcoming year. This information shall be used to develop overarching proposals incorporating the objectives into a scenario-based assessment framework. The Contractor shall refine the Joint Staff objectives into a series of assessment-based scenario proposals through a course of meetings with, and input from, the Joint Staff NPI coordinator and members of the Joint Staff NOD Nuclear Strike Branch.

The Contractor shall tailor each of the approved assessment backgrounds and Start of Exercise (STARTEX) postures, assessment timelines, conferencing scripts, and real-time assessment events and message injects, to the locations being assessed, responsive to Joint Staff directions and requirements. The Contractor shall provide one unique scenario-based assessment for each NMCC-E primary and designated contingency command platform (7) and for each NMCC (5) and National Airborne Operations Center (NAOC) Operations Team (3). Additionally, the Contractor shall provide a single JSAV template for the Joint Staff to administer to CCMD battle staffs. These products will be delivered in accordance with the delivery schedule located in Section 11.

The COR shall provide specific deliverable dates based on the cyclical annual NPI schedule. Deliverable dates are subject to change. These dates are agreed to between the Joint Staff and the assessed commands.

The Contractor shall provide up to two technical staff to accompany and support the Joint Staff NPI team implementing all assessments for which NPI packages were developed. At these locations, the Contractor shall provide to the Joint Staff the injection of assessment message inputs using the Nuclear Planning and Execution System (NPES) and/or using other means specific to systems used at the assessed NMCS locations. During assessments, the Contractor shall prepare responses to battle staff pre-start and real time assessment Requests for Information (RFIs), shall act as conferencing role players (as needed), and shall support the Joint Staff Evaluators by developing briefing slides from Evaluator assessment observations and critiques for use in out-briefs.

Task 2 – Subtask 1 - Candidate Scenario Briefing Package. The Contractor shall develop a Candidate Scenario Briefing Package. This deliverable shall first be submitted in draft. After review, the deliverable shall be finalized within 30 days from approval of the NOD NPI objectives message (normally published in June or July of each year). The Candidate Scenario Briefing Package shall consist of at least one but no more than ten generic scenario backgrounds and proposed series of scenario assessment events. This shall include sufficient assessment scenario variation among assessed locations and teams, and include military and political build up, actions, and/or attacks by other nations and/or groups, as well as the United States (US) and other national, political, and military actions and/or responses. The background scenarios shall place battle staff personnel into situations where they can be observed performing required NC2 operational functions to demonstrate proficiency. The scenarios must specifically address assessment focus areas highlighted in the annual Joint Staff NPI objectives message. The Contractor shall provide the Candidate Scenario Briefing Packages and an assessment proposal for each NMCC-E candidate to be assessed with scenario variants for each. Joint Staff Concurrence on the Candidate Scenario Briefing Package satisfies the first deliverable and will result in the COR’s acceptance of that deliverable.

Task 2 – Subtask 2 – Deliverable Schedule. Once the Joint Staff has established the NPI assessment schedule for the upcoming year, the Contractor shall support the COR to develop a Deliverable Schedule for the remaining deliverables in this task. Deliverable dates shall allow the Joint Staff sufficient time to review, revise, and approve deliverables by the agreed to date. The Deliverable Schedule will include generic deliverable dates based on the NPI assessment schedule and/or any special considerations throughout the year. Examples of deliverable dates are as follows: The Contractor shall deliver the appropriate Starter Packages (see deliverable 6.2.6) two weeks in advance of each scheduled NPI and shall deliver Exercise Packages one week in advance of each corresponding NPI.

The delivery schedule is published in the October – November timeframe. Since each NPI is a unique product and is based on current events, the actual delivery will be predicated upon the most current published schedule. These dates will change for each participant and may change after publication of the schedule; therefore, delivery times must be fluid to meet requirements.

Task 2 – Subtask 3 - Strawman Assessment Package. Once the Joint Staff reviews and approves the Candidate Scenario Briefing package, the Contractor shall support the COR with refining and adding detail to the approved background scenario(s), further tailoring the assessment portions for each location and adding detail to events and expected US responses. In addition to this, the Contractor shall develop and present representative Conferencing Scripts for each major scenario variant as an attachment to the Strawman Assessment Package. These will be further refined after Joint Staff approval (further discussed in PWS 6.2.5). The date for completion of the Strawman Assessment Package is NLT 31 October of each calendar year, or ASAP thereafter as coordinated through COR and Joint Staff. Strawman will include draft conferencing scripts to follow by the end of the month in which the Strawman has been submitted. The Strawman Assessment Package shall include more detailed breakouts of the proposed background scenario(s) and assessment proposals for each location. The background scenario(s) shall clearly highlight all of the key events that build up to the STARTEX assessment position and provide greater detail regarding proposed US force generation and NMCS and CCMD status as appropriate. The proposal shall include a detailed rationalization regarding command devolution to the assessed platform/location (as needed). It shall clearly differentiate among scenario variants for each location, adding necessary detail to permit evaluation for accomplishing objectives. The Contractor shall develop common scenario background elements and utilize common scenario events for each NPI. Sufficient variation shall be incorporated to realistically simulate expected roles at each assessed location, as well as to provide differences in assessments. This is done to lessen any intelligence value that later assessed locations might be able to achieve from monitoring prior assessment communications or through other means.

Task 2 – Subtask 4 – SIMSCENE Coordination Package. Once the Joint Staff reviews and approves the Strawman Assessment Package, the Contractor shall begin developing the Simulated Scenario Nuclear Events (SIM-SCENE) Coordination Package and begin refining the necessary EAP CJCS Vol VI Conferencing Scripts. To accomplish the requirements for this task, the Contractor input must possess a detailed understanding of US nuclear options (including option structure, force composition, delivery systems and capabilities, rules of engagement, timing and employment strategy and philosophy). The Contractor shall work closely with the Joint Staff and with the Joint Staff NPES support personnel to develop appropriately detailed enemy attack scenarios and US responses. It is vital for NPI scenario development that the Contractor possess a working ability to interpret and extract useful information from the NPES system, in addition to the ability to build messages to produce the eventual NPI Exercise Packages.

The Contractor shall produce a top-level checklist and comprehensive data file of all proposed Processing and Display SIMSCENEs for all scenario events at each NPI location, which are incorporated into the SIMSCENE Request Worksheets. After approval by the Joint Staff, the Contractor shall prepare SIMSCENE Request Worksheets and deliver these electronically to the USSTRATCOM J7 (trusted agent) one month prior to the first exercise scenario script review. This completes the second delivery milestone of Joint Staff approval of the Strawman Assessment Package. This package consists of proposed conferencing scripts, SIMSCENEs, and major scenario variants. Once the Joint Staff completes scenario script reviews of each proposed strawman scenario in the package, as well as approves them as sufficient to serve as baseline for all subsequent NPI assessments for the upcoming calendar year cycle, the Contractor shall commence work on the specific Assessment Conferencing Scripts, Starter Packages, and Exercise Packages for each assessment.

Task 2 – Subtask 5 – NMCC-E Assessment Conferencing Scripts. Once the Joint Staff approves the Strawman Package, the Contractor shall begin refining the Conferencing Scripts. The goal is for each NMCC-E being assessed to have a unique NPI Assessment Package, (consisting of a Starter and Exercise Package) based on one or more base scenarios and/or scenario variants. Each script shall carefully follow EAP CJCS Vol VI format and content guidelines. The content must meet strict criteria to ensure no ambiguity of Joint Staff assessment intent or expectations for the OTs and battle staffs. These scripts require close Joint Staff coordination and review; several iterations may be required to bring the scripts to final form. Once each script is finalized, the Contractor shall incorporate it into the appropriate NPI Exercise Package for each location and/or OT being assessed.

Task 2 – Subtask 6 – NMCC-E Starter Packages. The Contractor shall produce a unique Starter Package and Scenario Update Package (a separate annex to the standard Starter Package) for each NPI as required by the Joint Staff. Starter Packages shall be provided to the Joint Staff two weeks in advance of each NPI. Scenario Update Packages, if required, shall be provided one week in advance of the Joint Staff travel date for each NPI.

Starter Packages shall include the full background scenario incorporating force, leadership, C3, and option status information, in addition to relevance, content, timing, and other appropriate identifying designation for pre-start messages, force planning actions, and force and COCOM readiness and generation. The Contractor shall produce the Scenario Update Package, if required, which is delivered to the assessed location to cover events for the period from end of Starter Package timeline until STARTEX. In most cases, locations receiving a Scenario Update Package shall receive tasking to perform actions prior to STARTEX, such as alert condition (“LERTCON”) changes, adaptive planning, command handover, and/or message processing. The Contractor shall include these elements in the Scenario Update Package, if it has been requested and/or needed.

Task 2 – Subtask 7 – NMCC-E Exercise Packages. The Contractor shall produce a unique Exercise Package for each NMCC-E. Exercise Packages shall contain a Time-Events List of all situational and message injects expected for the NPI summarizing their content, linkages to major assessment events, and expected inject timing in relation to STARTEX. Additionally, each Exercise Package shall include copies of assessment injects and messages to be injected by the Joint Staff assessment team. The Contractor shall develop message injects using NPES for all locations possessing this capability. These messages shall appear in the Exercise Package, as well as in a separate NPES file as part of the Exercise Package.

The Joint Staff uses NPES files produced by the Contractor in order to directly inject messages into assessed location’s NPES system during their NPI. To facilitate the assessment, the Contractor shall produce a variety of messages to include: Global Summary Messages (GSMs), Situation Reports (SITREPS), Nuclear Employment Reporting (NEREP) messages, INTEL reports, plan availability messages, and a variety of Emergency Action Messages (EAMs) relating to CCMD readiness, force status, and force execution. Additionally, the assessment scenario shall prompt the assessed battle staffs and OTs to develop and generate messages of their own.

The Contractor shall provide additional message traffic relating to Survivable Mobile Command Center (SMCC) functions for those applicable platforms. The Contractor shall include a final copy of all Assessment Conferencing Scripts as an annex to the Exercise Packages. The Exercise Package shall produce events, messages, and injects that enables Joint Staff assessors to observe and assess CCMD and Operations Team performance related to all CJCS Mission Essential Functions (MEFs). This includes the following:

Continuous connectivity with and amongst the President, Secretary of Defense, and Joint Commands.

Situation Monitoring, to include Attack Warning and Characterization;

Decision making;

Force Direction, specifically nuclear force execution and termination;

Force management, including day-to-day and trans/post attack; and Planning, including deliberate and time sensitive.

The Contractor shall relate the assessment events, injects, and messages to criteria established in the various EAP CJCS and implementation instructions with specific emphasis on performance standards specified within the CJCSI 6810.04- NC3 Personnel Performance Objectives and Assessment Criteria.

Task 2 – Subtask 8 – Real Time Assessment Support. The Contractor shall provide up to two personnel to travel with the Joint Staff Assessment Team to all seven NMCC-E NPI locations where assessments are performed. Multiple assessments typically occur within a single trip. The Contractor shall support the Joint Staff for NMCC-PNT OT NPIs conducted at the Pentagon; however, this may occur at alternate locations within the National Capital Region. During these NPIs, the Contractor shall support the Joint Staff by injecting message traffic electronically using NPES where appropriate. The Contractor shall also support the Joint Staff by responding to battle staff RFIs. The Contractor shall also perform additional duties, such as role-playing during assessments and/or data collection and observation summarization for out briefing preparations.

Task 2 – Subtask 9 – NMCC-E JSAV Template. The Joint Staff administers JSAVs at NMCC-Es to promulgate new EAP CJCS based procedures and to ensure that CCMDs are interpreting these procedures and implementing instructions properly. JSAVs may be requested by the CCMD, or at the direction of the Joint Staff depending on perceived need. The Contractor shall develop a single JSAV Template for Joint Staff use in conducting JSAVs at NMCC-Es. The JSAV Template shall resemble NPI Packages, to include Starter Packages (with corresponding Scenario Updates) and an Exercise Package (to include appropriate conferencing scripts and message injects). The JSAV Template will incorporate a scenario background and scenario assessment, based upon prior NPI products, which shall be modified to satisfy current Joint Staff JSAV objectives. The JSAV Template shall be delivered by October 31 of each NPI cycle.

6.2 Task 2 Deliverables

PWS Reference Title Format (See PWS Section 11 for additional details) Due Date Distribution/Delivery Method Frequency and Remarks 6.2.1 Candidate Scenario Briefing Contractor Draft due 30 calendar days after requested. Final due 30 calendar days after Joint Staff approval of draft.

Notify COR via email of delivery. Specific products can remain in house and retrieved from Joint Staff as required.

Annually 6.2.2 Deliverable Schedule Contractor Not later than (NLT) November 30 of each Calendar Year Notify COR via email of delivery. Specific products can remain in house and retrieved from Joint Staff as required.

Annually 6.2.3 Strawman Assessment Package Contractor NLT October 31 of each Calendar Year or ASAP thereafter as coordinated through COR and Joint Staff.

Notify COR via email of delivery. Specific products can remain in house and retrieved from Joint Staff as required.

Annually 6.2.3 Draft Conferencing Scripts Government NMCC OT specific due NLT November 30 each Calendar Year. All others IAW Joint Staff calendar.

Notify COR via email of delivery. Specific products can remain in house and retrieved from Joint Staff as required.

Annually: One for each NMCC-E; approximately seven in total each Calendar Year 6.2.4 SIMSCENE Coordination Package Government IAW Deliverable Schedule (From Deliverable for PWS 6.2.2) Notify COR via email of delivery. Specific products can remain in house and retrieved from Joint Staff as required.

6.2.4 SIMSCENE Request Worksheets Contractor IAW Deliverable Schedule (From Deliverable for PWS 6.2.2) USSTRATCOM J7 (trusted agent)

6.2.5 NOCC Assessment Conferencing Scripts Government IAW Deliverable Schedule (From Deliverable for PWS 6.2.2) Notify COR via email of delivery. Specific products can remain in house and retrieved from Joint Staff as required.

6.2.6 Starter Package Contractor NLT two weeks prior to each assessment start date Notify COR via email of delivery. Specific products can remain in house and retrieved from Joint Staff as required.

One for each assessment 6.2.6 Scenario Update Package (Annex to Starter Package) Contractor If required, one week prior to Joint Staff travel date for each assessment Notify COR via email of delivery. Specific products can remain in house and retrieved from Joint Staff as required.

One for each assessment except for NMCC-PNT OTs 6.2.7 NOCC Exercise Packages Government IAW Deliverable Schedule Notify COR via email of delivery. Specific products can remain in house and retrieved from Joint Staff as required.

One for each assessment 6.2.8 Real Time Assessment Support (e.g., SIMSCENE support, Role Playing, and OT RFI Reponses) Contractor IAW Assessment Schedule Live support Every assessment 6.2.9 NOCC CAV Template Contractor NLT October 31 each Calendar Year Notify COR via email of delivery. Specific products can remain in house and retrieved from Joint Staff as required.

Once Annually

Task 3 – Non-NMCC-E Combatant Command JSAV Support. The Contractor shall provide support and documentation for NPI assessments of and at Non-NMCC-Es. While the task and deliverable descriptions that follow are unclassified, the actual deliverables to be produced by the Contractor shall be classified up to the TOP SECRET level. The Contractor personnel shall access and process ACCM, FRD, SCI, COSMIC TOP SECRET, NATO SECRET, NC2-ESI, and communications associated with this task.

Similar to the support described in 6.2 (Task 2), the Contractor shall gather and articulate Joint Staff objectives for the upcoming calendar year for Non-NMCC-E NPIs. This information shall be used to develop overarching proposals incorporating the objectives into a scenario-based assessment framework. The Contractor shall refine the Joint Staff objectives into an assessment scenario proposal through a course of meetings with, and input from, the Joint Staff NPI coordinator and members of the Joint Staff NOD Nuclear Strike Branch.

The Contractor shall tailor the assessment backgrounds and STARTEX posture information, assessment timelines, conferencing scripts, real-time assessment events, and message injects to the locations being assessed, responsive to the COR guidance and Joint Staff direction. The Contractor shall produce one unique scenario-based assessment for each of the seven primary Non-NMCC-E command centers. Non-NMCC JSAV are normally scheduled to occur from December to June each calendar year.

Each Contractor produced NPI assessment scenario shall support assessment of each Non-NMCC-E battle staff against performance criteria derived from the EAP CJCS associated CJCSI, and in accordance with the annual assessment objectives provided by the Joint Staff. Non-NMCC-Es must demonstrate the ability to participate in conferences; properly request and implement force readiness actions; transmit, receive, and correctly decipher and process EAMs; and demonstrate proper situational awareness and internal informational processing and notification functionality. Due to the limited set of performance expectations for Non-NMCC-Es, their NPIs shall be comparatively less involved than a typical NMCC NPI (as described in 6.2 Task 2). Non-NMCC-E NPIs shall use a common background and assessment scenario with variance to account for different geographical and situational variability. Geographic Non-NMCC-E CCMDs are required to respond to events within their Area of Responsibility (AOR) and are expected to demonstrate the ability to manage and communicate additional readiness actions. US Central Command (USCENTCOM) and US European Command (USEUCOM) NPIs may also require customization to reflect certain CCMD unique circumstances. The Joint Staff’s focus for Non NMCC-E NPIs is to ensure that the CCMDs understand and can meet performance expectations; administration of the NPI scenario itself does not result in certification or decertification decisions as it does with other NPIs.

Task 3 – Subtask 1 - Candidate Scenario Briefing. The Contractor shall develop and provide a Candidate Scenario Briefing for non-NMCC NPIs that is finalized within one month from receipt of the NOD NPI objectives message (normally published in June or July). The Candidate Scenario Briefing shall generally consist of one to two generic scenario backgrounds and proposed scenario assessment events for each CCMD location requiring variation from the base scenario. It ensures that CCMD personnel at assessed locations are placed into situations where the Joint Staff can observe them performing required operational functions and demonstrate proficiency called for by EAP CJCS and other implementing CJCSIs. The scenarios must specifically address assessment of focus areas highlighted in the annual Joint Staff NPI objectives message.

Task 3 – Subtask 2 – Deliverable Schedule. Once the Joint Staff has established the Non-NMCC-E NPI assessment schedule for the upcoming calendar year, the Contractor shall support the COR to develop a Deliverable Schedule for the remaining deliverables in this task. Deliverable dates shall allow the Joint Staff sufficient time to review, revise, and approve.

Task 3 – Subtask 3 – Non-NMCC NPI Starter Package. The Starter Package shall include the background scenario timeline, key events, relevant starter posture information (e.g., Defense Conditions), and status of any force generation and Emergency Action Message (EAM) status. The Starter Package shall be delivered NLT two weeks prior to scheduled NPI execution.

Task 3 – Subtask 4 – Non-NOCC NPI Exercise Package. The Exercise Package shall include a complete Time-Events List of all events to occur during the NPI, all injects that shall be provided to the CCMD during the NPI, and the sequence and proposed timing of these events and injects. The Exercise Package shall also include all EAP CJCS Vol VI conferencing scripts and properly formatted and completed messages for presentation and inject during the assessment. The Contractor shall work with the COR and the Joint Staff to develop conferencing scripts and messages in this package. The initial NMCC-E NPI Exercise Package shall be delivered NLT two weeks prior to the first Non-NMCC-NPI of the assessment cycle. All ensuing Exercise Packages shall be delivered NLT one week prior to the corresponding NPI and prior to Joint Staff team travel to the assessed locations.

6.3 Task 3 Deliverables

PWS Reference Title Format (See PWS Section 11 for additional details) Due Date Distribution/Delivery Method Frequency and Remarks 6.3.1 Non NMMCC-E Candidate Scenario Briefing Contractor Final due NLT 30 Calendar Days upon receipt of NOD NPI Objective Message (normally published in June or July) Notify COR via email of delivery. Specific products can remain in house and retrieved from Joint Staff as required.

Annually 6.3.2 Deliverable Schedule Contractor NLT November 30 of each Calendar Year Notify COR via email of delivery. Specific products can remain in house and retrieved from Joint Staff as required.

Annually 6.3.3 Non-NMCC-NPI Starter Package Contractor NLT two weeks prior to each assessment start date Notify COR via email of delivery. Specific products can remain in house and retrieved from Joint Staff as required.

One for each assessment 6.3.4 NonNMCC-E NPI Exercise Package Government Initial due NLT two weeks prior to Joint Staff travel to assessed location; All others NLT one week prior to Joint Staff travel to assessed location Notify COR via email of delivery. Specific products can remain in house and retrieved from Joint Staff as required.

One for each assessment

Performance Standards.

Performance Standard Quality Level (AQL) Methods of Calculation/Surveillance

6.1 90-day Action Plan 95% of submissions delivered on schedule 100% routine inspection

6.1 Monthly Status Report

95% of submissions delivered on schedule 100% routine inspection

6.2.1 Candidate Scenario Briefing

100% Joint Staff approval. Draft submittal with no more than two resubmissions. Deliverable timeline must be met 100%.

100% routine inspection of deliverable for approval.

6.2.2 Deliverable Schedule

100% Joint Staff approval 100% inspection, review and approval.

6.2.3 Strawman Assessment Package

90% approval by Joint Staff with no more than one resubmission 100% inspection, review and approval. 100% inspection, review and approval.

6.2.3 Draft Conferencing Scripts

Approval must be received in time to meet deliverable schedule 95% of the time 100% inspection, review and approval.

6.2.4 SIMSCENE Coordination Package

Approval must be received in time to meet deliverable schedule 95% of the time 100% inspection, review and approval.

6.2.4 SIMSCENE Request Worksheets

95% of submission delivered on schedule 100% inspection, review and approval.

6.2.5 NMCC-E/NMCS OT Assessment Conferencing Scripts

Approval must be received in time to meet deliverable schedule 95% of the time 100% inspection, review and approval.

6.2.6 Starter Package

Approval must be received in time to meet deliverable schedule 95% of the time 100% inspection, review and approval.

6.2.6 Scenario Update Package (Annex to Starter Pack-age)

Approval must be received in time to meet deliverable schedule 95% of the time 100% inspection, review and approval.

6.2.7 NMCC-E/NMCS OT Exercise Packages

Approval must be received in time to meet deliverable schedule 95% of the time 100% inspection, review and approval.

6.2.8 Real Time Assessment Support (e.g., Role Playing, SIM SCENE support, and OT RFI Reponses) Volume and location of support 100% coordinated with Joint Staff Assessment Team.

100% routine inspection

6.2.9 NMCC-E JSAV Template

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

100% inspection, review and approval.

6.3.1 Non-NMCC-E Candidate Scenario Briefing

100% Joint Staff approval. Draft submittal with no more than two resubmissions.

100% inspection, review and approval.

6.3.2 Deliverable Schedule

100% Joint Staff approval 100% inspection, review and approval.

6.3.3 Non-NMCC-E NPI Starter Package

Approval must be received in time to meet deliverable schedule 95% of the time 100% inspection, review and approval.

6.3.4 Non-NMCC-E NPI Exercise Package

Approval must be received in time to meet deliverable schedule 95% of the time 100% inspection, review and approval.

7.0 ALTERNATE PLACE OF PERFORMANCE (CONTINGENCIES ONLY)

As determined by the COR, contractor personnel may be required to work at an alternate location (e.g., home, contractor facility, or other approved activity) during unforeseen contingencies such as pandemic conditions, exercises, or Government closure. Non-emergency contractors should not report to a closed Government facility. The Contractor shall use best efforts to maintain the same level of support as specified in this PWS. If services are impacted, the Contracting Officer or Contractor may request an equitable adjustment pursuant to the Changes clause.

8.0 Place of Performance: The primary place of performance will be located at the Pentagon CJCS/J36, 3000 Joint Staff, Pentagon, Washington DC; The alternate will be Site R/Rm 3D32B, 450 Harbaugh Valley Rd, Fairfield, PA 17320.

9.0 Travel: Travel in and around the primary place of performance may be required throughout the period of performance. Additional travel within the Continental United States (CONUS) and Outside the Continental United States (OCONUS) may be required to support the requirements of this PWS. All Contractor travel in support of this PWS which falls outside the primary place of performance region must be authorized in advance by the COR. The Contractor’s lead analysts may be required to complete “physiological training/assessment” for military flight qualification to enable participation in NAOC and Looking Glass NPIs. The Contractor must plan for Temporary Duty (TDY) in support of NPI implementation. Currently, for Task 2 (PWS 6.2), a total of five overnight Contractor travel trips are anticipated to support the Joint Staff at COCOM and NAOC NPIs. The Contractor should plan to provide up to two people for up to one week each per trip.

The Contractor shall participate in meetings and gather information for NPI development in the primary place of performance region. Locations for these activities are anticipated to include the Pentagon, other DoD or Government offices in northern Virginia, the District of Columbia, and other Contractor locations in Maryland and Virginia.

The Contractor shall seek prior written authorization by the COR for all travel before any travel costs are incurred. Travel expenses shall be reimbursed consistent with FAR 31.205-46, the substantive provisions of the Federal Travel Regulation (FTR), and the limitation of funds specified in this Contract. The Contractor shall not be reimbursed for the following travel expenses: transportation expenses for assigned personnel for local commuting between their place of residence and their place of work or for local travel of personnel assigned to the Contractor’s sites unless specifically authorized by the COR in writing, in advance. The Contractor shall not be reimbursed for moving or relocation expenses for the Contractor or Contractor employees, and/or subcontractors. There may be other travel expenses or other situations where travel expenses will not be reimbursed. Note: Local travel is defined as travel within 50 miles of the contractor employee’s primary performance site. Local travel will not be reimbursed.

Federal Travel Regulations may be located and downloaded from www.gpoaccess.gov/cfr or www.gsa.gov/federaltravelregulation. For work at OCONUS locations, per-diem rate maximums, as defined by the U.S. Department of State’s Bureau of Administration, Office of Allowances, which may be found at: http://www.state.gov/m/a/als/. For the purposes of ODC travel reimbursement only, “CONUS” is defined as the 48 contiguous states and the District of Columbia, all other locations are considered to be “OCONUS”.

10.0 PERIOD OF PERFORMANCE

The period of performance shall be a one-year base period with four one-year option periods:

Base period is from 09/02/2026 to 09/1/2027 OY1 is from 09/02/2027 to 09/1/2028 OY2 is from 09/02/2028 to 09/1/2029 OY3 is from 09/02/2029 to 09/1/2030 OY4 is from 09/02/2030 to 09/1/2031

11.0 DELIVERABLE FORMAT AND SCHEDULE CONDITIONS

. The Contractor shall prepare all deliverables in accordance with formats provided by the Joint Staff in the form of prior year NPI documents. Additionally, all documents should comply with Joint Staff document criteria including security markings provided in the Joint Staff security classification guides.

Unless otherwise specified, all document graphics shall be completed using a Microsoft Office for Windows compatible format. Clipart shall be based on the standard clipart used by the Joint Staff J36 NOD. Briefings shall be produced and delivered using Microsoft Power Point format using the most current version. Any exceptions shall require coordination with the COR.

The Contractor shall provide the starter packages, exercise packages and injects, and all other delivered text based items electronically in the Word for Windows format using the most current version. The Contractor shall deliver directly to the NOD after review and notify COR following approval. All documents shall be housed on the appropriate classified system and network Automated Data Processing (ADP) system used by the Joint Staff and can be made readily available at the request of the COR if needed. The Contractor shall ensure that any electronic versions of deliverables can be read and accessed by the Government.

12. Security Requirements. Performance for this requirement shall be performed at the TOP SECRET level at two identified Government locations (See PWS Section 8). All personnel performing on this contract will be U.S. citizens. The personnel security requirements for this contract/order cover the individuals supporting the Task Areas delineated in the table below. Contractor personnel must possess the interim or final security clearance eligibility delineated in the table below when performance starts.

PWS Task / Subtask Clearance Level Level of Classified Access Justification for Access to Classified 6.2

TOP SECRET

ACCM, FRD, SCI, COSMIC TOP SECRET, NATO SECRET, NC2-ESI, JWICS, SIPRNET, DCIN TS-GOLD, VIPER In order for the work assigned in section 6 of the SOW to be completed, the clearance level identified is required.

6.3

TOP SECRET

ACCM, FRD, SCI, COSMIC TOP SECRET, NATO SECRET, NC2-ESI, JWICS, SIPRNET, DCIN TS-GOLD, VIPER In order for the work assigned in section 6 of the SOW to be completed, the clearance level identified is required.

12.1 Facility Security Clearance. The work to be performed under this contract is up to the TOP SECRET level and requires Sensitive Compartmented Information (SCI) access eligibility for some personnel. Therefore the company must have a final Top Secret Facility Clearance (FCL) from the Defense Security Service (DSS) Facility Clearance Branch (FCB).

12.2 Security Clearance . Individuals supporting PWS Tasks / Subtasks that require(s) an interim or a final Top Secret security clearance will, immediately upon hire, require Sensitive Compartmented Information (SCI) access eligibility adjudicated by the Department of Defense Consolidated Adjudication Facility or other federal adjudications facility to perform their duties. SCI processing for SCI eligibility will be coordinated with the supporting Government Security Manager and will begin immediately upon start of duty performance under this contract/order. All SCI work under this contract/order will be monitored by the COR/ACOR. The COR/ACOR must be indoctrinated into SCI to monitor the work.

12.3 Investigation Requirements. All personnel requiring Top Secret and SCI access under this contract/order shall undergo a favorably adjudicated Tier 5 (T5) investigation (formerly known as a Single Scope Background Investigation (SSBI)) as a minimum requirement. The T5 will be maintained current within 6-years and requests for Tier 5 reinvestigation (T5R formerly known as Single Scope Background Period Reinvestigation (SBPR) or Phased Periodic Reinvestigation (PPR)) will be initiated prior to the 6-year anniversary date of the previous Tier 5.

12.3.1 All personnel requiring Secret access under this contract/order shall undergo a favorably adjudicated Tier 3 (T3) Investigation formerly known as a National Agency Check, Local Agency Check and Credit Check or Access National Agency Check and Inquiries as a minimum investigation. The Tier 3 Investigation will be maintained current within 10-years and requests for Secret Periodic Reinvestigations will be initiated by submitting a Tier 3R investigation prior to the 10-year anniversary date of the previous Tier 3 Investigation.

12.3.2 The contractor is required to have personnel cleared with an interim or final Top Secret at contract start date. If contractor personnel is replaced during performance of the contract, replacement personnel should also have interim or final Top Secret clearance.

12.4 Visit Authorization Letters (VALs). Visit requests shall be processed and verified through the Defense Information System for Security (DISS) to SMO DKABAA10. A complete list of DISA DISS SMO codes can be found at https://disa.deps.mil/ORG/MP6/mp61/industrialsecurity/Shared%20Documents/Forms/AllItems.aspx). DISS visits for contracts/orders are identified as “Other” or “TAD/TDY” and will include the Contract/Order Number of the contract/order in the Additional Information section. Contractors that do not have access to DISS may submit visit authorizations by e-mail in a password protected .pdf to the COR/ACOR specified in PWS/SOW Section 1.0.

If DISS is not available, the VAL must contain the following information on company letterhead Company name, address, telephone number, facility security clearance

CAGE Code Contract Number Name, SSN, date and place of birth, and citizenship of the employee intending to visit

12.5 Security Contacts:

Joint Staff J3 Security Personnel: (703)-693-0023 Pentagon, Arlington VA, ATTN: J3 Military Secretariat 3000 Joint Staff, Pentagon Washington, DC 20318 Directorate/Center Security Manager:

js.pentagon.j3.list.milsec-all1@mail.mil

12.6 Information Security and Other Miscellaneous Requirements. Contractor personnel shall comply with all local security requirements including entry and exit control for personnel and property at the government facility.

12.6.1 Contractor employees shall be required to comply with all Government security regulations and requirements. Initial and periodic safety and security training and briefings will be provided by Government security personnel. Failure to comply with Government security regulations and requirements shall require the company to provide the Government with a written remediation/corrective action plan; furthermore, failure to comply with such requirements can be cause for removal and the contractor will not be able to provide service on this contract/order.

12.6.2 Contractor employees with an incident report in DISS who have had their access to classified suspended will not be permitted to fill positions requiring access to classified information on a DISA contract/order.

12.6.3 The Contractor shall not divulge any information, classified or unclassified, about DoD files, data processing activities or functions,…