N2C3 PWS (Effective 02.06.2026).pdf

Performance Work Statement Global Command and Control

And Nuclear Command, Control, and Communications Policy and Governance Support

1 BACKGROUND

The National & Nuclear Command, Control, and Communications Division (N2C3), Deputy Directorate for Nuclear and Homeland Defense Operations (DDNHDO), J36 on behalf of the Director of Operations, J3 (DJ3), is the Office of Primary Responsibility (OPR) for Command and Control (C2) systems and Chairman of the Joint Chiefs of Staff (CJCS) operational policy. N2C3 supports day to day military operations, long term system and policy development, and implementation for the Joint Staff (JS), Combatant Commands (CCMDs), Joint Task Forces (JTFs), and Services.

Key portfolio responsibilities include:

Global Command and Control System – Joint (GCCS J) Interactive Broadcast Service (IBS) Deployable Joint C2 (DJC2) Joint Planning and Execution System (JPES) C2 of the Information Environment (C2IE) Defense Readiness Reporting System (DRRS) Joint All Domain C2 (JADC2) and Nuclear Governance

N2C3 integrates and coordinates all C2 systems, leads the C2 Council of Colonels, co-chairs the C2 Executive Steering Council (C2ௗESC), and provides oversight for the National Military Command System (NMCS), Nuclear Command, Control, and Communications (NC3), and the National Leadership Command Capability (NLCC). Additionally, this Division includes the JS Directorate of Operations, J3, Digital and Artificial Intelligence Steward who is responsible for the data-centric transformation of the J3 along with leading DoD wide effort to establish and maintain information sharing globally.

2 PURPOSE

The purpose of this requirement is to acquire administrative, technical, analytical, and CJCS policy support for the Joint Staff J3 Directorate in support of:

Nuclear and Global Joint Command & Control (C2) Common Operational Picture (COP) and National Military Command Center (NMCC) missions

Development, alignment, and implementation of C2 policies, procedures, and modernization initiatives across the strategic and operational spectrum

The Contractor shall provide support for C2 policy, system development, NMCS/NC3 integration and related initiatives.

Additionally, the contractor shall provide systems-engineering expertise and technical assistance while participating in a limited set of procurement-sensitive meetings (e.g., requirements-definition workshops, interface-control briefings, and technical-risk-assessment sessions).

3 REQUIREMENTS

3.1 Global Joint C2 (GJC2) Branch

3.1.1 The GJC2 Branch acts as the secretariat for the General Officer Hosted C2 Executive Steering Council (C2 ESC) and supports N2C3s role as the co-chair for the C2 Council of Colonels. As such, the Contractor shall provide critical support to the C2 governance structure forums and activities. The Contractor shall stay abreast and engaged in all facets of C2 programs, initiatives, policy and system development that fall under the JC2 CDD and the C2 ESC umbrella to include the annual C2 Operational Priorities.

The GJC2 Branch is also the operational sponsor for various C2 systems to include the Global Command and Control System-Joint (GCCS-J) to include modernization efforts, Deployable Joint C2 (DJC2), and the Interactive Broadcast Service (IBS) in addition to being the lead proponent for all joint situational awareness-based systems and initiatives. Support to the branch covers a wide range of C2 and IT-related topics to include but not limited to:

CJADC2

Joint Warfighting Concept Global Information Dominance Experiment series (GIDE) Unit Reference Number (URN) Management Common Operational Picture/Common Intelligence Picture Reporting Requirements and data sharing Global Common Operational Picture Management Communications Security and Cryptologic Modernization Tactical Data Links Joint Data Networks

Globally Integrated Operations and Exercises Global Force Management Near Real Time Operational and Intelligence data dissemination Friendly Force Tracking

SATCOM

Cybersecurity

3.1.2 The Contractor shall support the customer in all these facets by proactively researching and coordinating with C2 community stakeholders to stay abreast of programs, initiatives, and trends that impact C2 and situational awareness to ensure that the operational warfighter’s interests are represented and that efforts are integrated and de-conflicted to provide needed capability to the field. The Contractor shall also remain engaged with interagency, intergovernmental and partner nation initiatives and needs at all classification levels to maintain and improve interoperability.

3.1.3 To support GJC2’s role as the operational sponsor for GCCS-J, one of the Contractor’s key duties is to ensure warfighter/user needs are heard, validated, prioritized and met by the developer for both the current system and modernization efforts. The Contractor shall attend, host and prepare GJC2 reps for a myriad of coordination meetings between CCMD user representatives, Joint Staff capability developers, OSD and DISA to validate and prioritize problem reports and capability needs as well as coordinate JCIDS documentation, CONOPS, and user preferences for new concepts or development items. The Contractor shall participate in operational testing events and forums, research operational impacts of opened Problem Reports, and monitors delivery and fielding schedules. The Contractor shall also research and recommend responses or courses of action regarding operational testing results, fielding decision reviews and operational endorsement of new capabilities, or deliveries. Specifically for modernization, the Contractor shall support the GJC2 Branch as one of the business process owners for the new system and is constantly engaged with stakeholders to scope and mold development efforts during myriad modernization meetings.

3.1.4 GJC2 also leads coordination for the Common Operational Picture (COP) Staff Assistance Visit (SAV) Program. The Contractor shall maintain the Chairman of the Joint Chiefs of Staff Instruction (CJCSI) which covers the SAV program, and the supplement used to guide the conduct of each CCMDs SAV. The Contractor shall provide logistical support, preparation material, coordination with the CCMD to be visited, and the team performing the SAV. The Contractor is responsible for putting together all in-brief and out-brief materials to include preparing the after-action report to be signed by the DDNHDO J36 and sent to the CCMD J3.

Following each SAV the Contractor shall update and track action items to closure.

3.1.5 COP Technical Support. The Contractor provides technical expertise with various COP and SA tools to include GCCS-J, Agile Client, SAGE, A/EISS, RAPIDS, WASABI, C2IE and others. The experts provide technical assistance and training for users on the NMCC watch floor, leads capability demonstrations to various agencies, offices, and partners, and liaisons with program management offices to ensure issues at critical sites are resolved.

3.1.6 C2 Ancillary System Support. The Contractor shall act as the primary user representative for several ancillary systems and databases (DB) to include the Unit Reference Number (URN) DB and the Unique Identifier (UID) DB. The Contractor shall coordinate directly with the developer for establishment, testing and user registrations and assists users with troubleshooting, block assignments, and problem reports. The Contractor shall also assist with the Nickname, Codewords and Exercise Terms (NICKA) system oversight, recommending operational courses of action when questions or concerns arise from authorized users.

3.1.7 Meeting Support: The Contractor shall maintain the SharePoint database for C2 Governance Forums. Research and provides background and recommended talking points to leadership for all C2-related meetings and forums. Prepare briefing material for GJC2 and/or N2C3 presentations. Participate in various C2 governance forums. Handle all logistics for GJC2 and N2C3 hosted forums and workgroups to include the C2 ESC, the annual COP WG and the UNCLAS COP WG, and various smaller meetings and demonstrations. Draft, coordinate, and publish meeting invitations, agendas, briefing materials, read-aheads, and minutes for the community. The Contractor personnel shall remain available to escort non-badged persons within the NMCC for N2C3 meetings, seminars, and conferences. This also includes computer hardware and network personnel required to update and or perform maintenance of individual’s workstations. Escort authorization is annotated on contractor badges.

3.1.8 C2 Policy Support. The Contractor SMEs shall be intimately involved with all C2 Policy documentation. The Contractor shall maintain numerous J36 OPR policy documents and reviews and develops recommended responses for non-J36 OPR documents according to CJCS directives. These documents include:

CJCSI 3115.01 Common Tactical Picture Reporting Requirements CJCSI 3151.01C Global Command and Control System Common Operational Picture Reporting Requirements CJCSI 3151.02 Common Operational Picture/Shared Situational Awareness Staff Assistance Visit

CJCSI 3155.01B, “GCCS-J Operational Framework Policy” CJCSI 3156.01A Management of Joint Unit Reference Numbers CJCSI 3265.01, C2 Management and Governance

CJCSI 3265.02, Joint C2– Training Management CJCSI 3910.01B, Friendly Force Tracking Operations Guidance CJCSM 3115.01D, Vol 1, Joint Data Network Operations CJCSM 3115.02, Vol 2, Common Tactical Picture Data Management CJCSM 3115.03 Joint Data Network (JDN) Operations: Volume III Joint Interface Control Officer CJCSM 3150.29E, Code Word, Nicknames, and Exercise Term (NICKA) System CJCSM 3265.01, C2 Capability Development/Requirements Manual DRAFT CJCSI 3152.01 – USSASE Reporting Requirements

3.1.8.1 Deployable Joint Command and Control (DJC2) Concept of Operations (CONOPS) Global C2 COP CONOPS

3.1.8.2 Unclassified Shared Situational Awareness CONOPS Tactical Information Security Classification Guide (TISCG)

DRAFT IBS CONOPS

3.1.8.3 CJCSI 6731.01 GCCS-J Security Policy

3.2 Systems Branch

3.2.1 The contractor shall support the N2C3, Systems Branch in three main areas: operations and requirements, engineering and architecture, and integration and policy. The magnitude of support required within each of these areas will vary depending on operational needs. Support in all areas will require working across the Joint Staff, Office of the Secretary of Defense, Combatant Commands, Services, NC3 Enterprise Center, Defense Information Systems Agency, and other organizations. The contractor shall support a wide range of subject areas including, but not limited to:

National Leadership Command Capability (NLCC) National Military Command System (NMCS) NC3 policy, processes and procedures DoD Digital Modernization Zero Trust Data Accuracy and Devolution Mission Engineering Cloud Integration Denied, Degraded, Intermittent, and Low-Bandwidth (DDIL) operations Security Policy Joint Capabilities Integration and Development System (JCIDS) process Mission Partner Environment Combined Joint All Domain C2 Capstone Concept for Joint Operations

3.2.2 Operations & Requirements. Serves as operational sponsor and warfighter advocate, monitoring day-to-day activities, and ensuring direct immediate support from the Joins Staff Support Center, DISA Program Executive Office, and other C3 enablers to maintain and sustain C2 systems during current operation and crisis action planning and execution. Develops and monitors the overall health of the NMCS. Plans, develops, and supports NMCS operations and modernization activities to ensure communications interoperability, data and information integration, configuration management, and shared user-defined situational awareness with Military Department-managed systems are aligned with strategic and operational priorities. Ensures NMCS C3 information is obtained from applicable program managers and/or subject matter experts, to include acquisition, sustainment, modernization, and O&M information. Ensures compliance with DoD cybersecurity policies.

3.2.3 The contractor shall monitor systems and programs to ensure that they meet operational requirements and published service level agreements. Develop and monitor trend data to provide recommendations for further analysis. Oversee solutions to mitigate or resolve conflicts between systems in the NMCS. Review, analyze, and make recommendations on system architectures, documentation and configuration controls to determine compliance with applicable standards. Analyze and make recommendations on proposed future system/applications to ensure compatibility and interoperability with existing systems. Document key operational activities, information and data exchanges, system components, functions, interfaces, infrastructure and communications. Ensure cybersecurity requirements are properly documented and included in all system architectural designs. Consult with program managers and users to resolve user identified issues and requirements in the system design. Additionally, the Contractor shall support various NC3 programs, exercises and activities.

3.2.4 Architecture and Engineering. Plans, develops, and supports NMCS operations and modernization activities to ensure communications interoperability, data and information integration, configuration management, and shared user-defined situational awareness with Military Department- managed systems are aligned with strategic and operational priorities. Ensures NMCS C3 information is obtained from applicable program managers and/or subject matter experts, to include acquisition, sustainment, modernization, and O&M information.

3.2.4.1 The contractor shall review engineering and architecture priorities for applications, systems, networks, and transmission systems in the NMCS.

3.2.4.2 Plan, monitor, and coordinate life cycle replacements. Coordinate with OUSD(A&S) to maintain visibility on programs that might have an impact on NC3 requirements, so issues are elevated to the CJCS on a timely manner to address. Ensure that all current and future system architectures designs are aligned to mission objectives and goals. Review and recommend architectural solutions to mitigate or resolve conflicts between systems in the NMCS.

3.2.5 Integration and Policy. Ensures integration and interoperability between all NC3 and NMCS policies, processes, systems, and nodes as part of the Nuclear Command and Control System (NCCS) and National Leadership Command Capability (NLCC). Perform and provide oversight of national strategic and theater communications operational assessments. Orchestrate the assessment of NC3 systems and procedures; correlate data and identify trends/gaps. This section represents and advocates for CJCS operational equities in NC3 systems-related efforts that affect NC3 policy and procedures. The branch chairs or participates in various forums such as the NC3 Capability Portfolio Management Review, NC3 Integrated Acquisition Portfolio Review, NC3 Assessments Working Group (WG), NC3 Readiness Reporting WG, and NC3 Policy, Guidance, and Directives WG. Additionally, it supports and prepares Flag Officer/General Officer-level principals for forums such as the NLCC Senior Steering Group (SSG), Operations Deputies (OPSDEPS), Council on Oversight of the National Leadership C3 System, the Deputy’s Management Action Group (DMAG), and the

TANK.

3.2.6 The contractor shall lead coordination and staffing for numerous policy documents and staffing packages originating from or tasked to the division or branch. Additionally, the contractor shall conduct research and develop recommended courses of action, responses, documentation, policy, and briefing materials. Documents include, but are not limited to:

NC3 Portfolio Definition Polo Hat 5-yr Schedule Security Classification Guidance Nuclear Posture Review supporting documents CJCSI 3264.01, NC3 Operational Assessment Programs CJCSI 3280.01 National Military Command System (NMCS) CJCSI 5119.01 Charter for the Centralized Direction, Management, Operation, and Technical Support of the Nuclear

Command, Control, and Communications System CJCSI 6810.04 Nuclear Command, Control, and Communications Personnel Performance Objectives and Assessment

Criteria CJCSI 6811.03 Defense Injection/reception emergency action message (EAM) C2 Terminal (DIRECT) CJCSM 6254.01 MILSTAR Network Operating Procedures AP-CJCS Vol I, IV, VI, VII, VII Annex Emergency Action Procedures

3.3 Systems-Engineering expertise and Technical Assistance (SETA) Support

3.3.1 DSSWG Support

3.3.1.1 Review and update direct-template artifacts (e.g., data-exchange schemas, interface control documents)

3.3.1.2 Evaluate software patches and releases for compliance with NC³ architecture standards.

3.3.1.3 Produce a DSSWG Technical Brief summarizing findings and recommended actions.

3.3.2 A&S Lead Forum Support

3.3.2.1 Participate in Nuclear C2 Working Group sessions.

3.3.2.2 Provide portfolio-status updates (capability gaps, risk assessments, schedule health).

3.3.2.3 Deliver Recommendations Memoranda that outline technical options for future NC3 capability development.

3.3.3 Global C2 Stakeholder Meeting Support

3.3.3.1 Coordinate with DISA representatives to align C2 requirements with DISA’s enterprise C2 roadmap.

3.3.3.2 Capture and document inter-agency requirements, integration points, and compliance gaps.

3.3.3.3 Produce a Stakeholder-Alignment Report for the GCCS-J Program Office.

3.4 Kick-Off Meeting

3.4.1 The sContractor shall schedule and conduct a joint Government, contractor kick-off meeting to review PWS requirements.

The kick-off meeting may be conducted via several methods and will be determined by the Government. The kick-off meeting will be scheduled O/A 10 days after the contract is awarded.

3.5 Project Schedule

3.5.1 The Contractor shall deliver and maintain an integrated project schedule. This schedule shall be delivered OA the 1st of the Month outlining the projects for each upcoming month.

3.6 Monthly Progress Report

3.6.1 The Contractor shall submit monthly contract summary reports NLT the 15th of the following month.

3.6.2 All reports resulting from this contract shall contain the following disclaimer statement on the report cover, “The views, opinions and findings, contained in this report are those of the author(s) and should not be construed as an official Department of Defense (DoD) position, policy, or decision, unless so designated by other official documentation."

3.6.3 All deliverables shall result in Contractor prepared technical reports as required by the COR. All deliverables become the property of the United States Government. Unless otherwise stated, all deliverables will be submitted in both hard copy and electronic media in Microsoft Word/Power/Excel/Access/Visio/Project format.

3.6.4 The Contractor shall report monthly burn rates on the travel funding for each month.

3.7 Administrative

3.7.1 The staffing functions provided by the Contractors in each branch also include providing significant activities for the Weekly Activity Report (WAR), General Officer / Flag Officer (GO/FO) 5x8s, position papers and fact sheets concerning current C2 topics.

The contractor shall develop position papers and documentation that supports furtherance N2C3 and C2 mission sets supporting the warfighter mission needs.

3.7.2 The contractor shall draft reports, executive summaries, formal briefings, JSAP’s and supporting graphical material in written or oral format.

3.7.3 The Contractor shall conduct issue research, information acquisition, analysis, prepare qualitative assessments and maintain the direct and supporting documents relating to C2 and coordinates summary results with Commands / Services / Agencies (C/S/As).

3.7.4 The contractor shall produce trip reports from TDY’s; minutes from written summary notes from all meetings / teleconferences and research results to support senior leadership request for information.

4 DELIVERABLES

4.1 The Contractor shall prepare meeting documentation as described below:

4.1.1 GJC2, NC3, and NSB Meeting and Working Group support to include developing schedules, coordinating with principals for agenda, coordinating and facilitating clearance requirements and access, assisting with badging, registration, general admin etc., coordinating meeting location, VTC requirements and presentations, taking notes, and publishing minutes. This may involve traveling to sites of meetings. All deliverables become the property of the United States Government.

4.1.2 Unless otherwise stated, all deliverables will be submitted in both hardcopy and electronic media in either Microsoft Word/PowerPoint/Excel/Access/Visio/or Project Format.

Deliverable Frequency

Weekly Activity Report Weekly

Meeting Notes Same duty day unless otherwise extended by the government lead

Integrated Project Schedule Monthly – on or about the 1st

Monthly Progress Reports NLT the 15th of the following month

Comment Resolution Matrix

Dependent upon on Joint Staff Action Process tasks, estimated at 2-4 per week

DSSWG Technical Brief As needed

Nuclear C2 portfolio updates & Recommendations Memoranda

As needed

Global C2 Stakeholder – Alignment Report As needed

4.1.3 Additional Topics for focus by the Contractor SMEs to monitor, support, analyze, and assess for current operational support:

Global Command and Control System - Joint (GCCS-J) (v6.0 and modernization) Data Accuracy Un-classified Shared Situational Awareness Cloud integration Denied, Degraded, Intermittent, and Low-Bandwidth (DDIL) Security Policy Revising of Global C2 IT testing procedures Mission Partner Environment Joint All Domain C2 Capstone Concept for Joint Operations Mission Partner COP initiatives (Department of State, Customs and Border Protection, FVEY, Coalition Partners) Five Eye (Security Marking) (FVEY) COP C2 Training Requirements Annual C2 Operation priorities NC3 policy, processes and procedures National Leadership Command Capability (NLCC) National Military Command System (NMCS) NC3 Enterprise Review (NER)

5 SECURITY

5.1 Clearance Level TS/SCI

5.1.1 All (on-site/off-site) contractor personnel shall possess a final Top Secret (TS) Clearance based on a Single Scope Background Investigation (SSBI), SBPR, or PPR completed within the last 5 years (in-scope) with Sensitive Compartmented Information (SCI) eligibility and been in SCI access within two (2) years prior to reporting to any assignment within Joint Staff to meet contractual security requirements.

5.1.2 The clearance shall be fully adjudicated at the SCI level and will have an indication of “determined eligibility of DCID 6/4” in JPAS. Personnel security clearances (PCLs) shall be verifiable in the Joint Personnel Adjudication System (JPAS).

5.1.3 Foreign Nationals are prohibited from working on classified and unclassified portions of this contract. To help prevent critical work stoppage at the end of the Base year or any option year exercise, The Contractor may request badge and or/CAC card extensions ten working days prior to the end of the period of performance.

5.1.4 The Government will issue new credentials on notification from the Contracting Officer that the Option Period will be exercised to prevent any gaps in contractor support.

5.1.5 NC2: This contract requires that specified contractor employees be granted access to Nuclear Command and Control - Extremely Sensitive Information (NC2-ESI).

5.2 Facility Clearance

5.2.1 The Contractor shall possess a TOP SECRET facility clearance granted from the Defense Security Service as verified within the Industrial Security Facilities Database (ISFD) at the time of contract award.

5.2.2 The Contractor’s employees performing work in support of this contract shall have been granted a TOP SECRET Security Clearance from the Defense Industrial Security Clearance Office or DoD CAF (Central Adjudication Facility), with Sensitive Compartmented Information (SCI) eligibility. Facility security clearances (FCLs) shall be verifiable in the Industrial Security Facilities Database (ISFD).

5.3 Physical Security

5.3.1 The Contractor shall be responsible for safeguarding all Government information or property provided for Contractor use. At the end of each work period, Government information, facilities, equipment and materials shall be secured as specified by DoD security policy and regulations.

5.3.2 The Contractor will also follow and adhere to government site specific security policy and directives, which includes the Joint Staff Security Office policies for the Joint Staff.

5.3.3 The Government will coordinate with site security offices as required to ensure The Contractor has or can access all applicable security regulations and directives upon award.

5.4 NC2

5.4.1.1 NC2-ESI material remains under US Government control at all times. Access to NC2-ESI by contractor personnel will be limited to US Government facilities.

5.4.1.2 Individuals accessed to NC2 shall have a Top-Secret clearance based on a favorable investigation as noted above completed within 5 years to the date of the last investigation.

5.4.1.3 To continue in NC2 access the individual shall have a new investigation (SSBI, SBPR, or PPR) initiated prior to five years from the date the last investigation closed, and no later.

5.4.1.3.1 No waivers will be considered.

5.4.1.3.2 The Contractor’s Facility Security Officer (FSO) shall ensure that the SSBI, SBPR, or PPR is initiated within that five-year period to allow continued access by contractor personnel to NC2 information. Individuals requiring NC2-ESI access will be processed in accordance with the procedures on the Contract DD254.

5.5 Identification of Contract Employees

5.5.1 All contractor personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials.

5.5.2 They shall also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

5.5.3 The Contractor shall be required to wear required Pentagon security badges (indicating contractor status) daily.

5.5.3.1 Pentagon access badges will be requested on JS Contractor In-Processing form 8C (or its replacement) for access to the

NMCC.

5.5.3.2 “NMCC Badge w/Escort” will be checked allowing a visual badge authorization to escort personnel w/in the NMCC supporting escort requirements outlined in Section 2.1.6, “Meeting Support”.

5.6 ACCMs, FGI, & SAP

5.6.1 Contractor staff in direct support of this contract will require access to information protected by Alternative Compensatory Control Measures (ACCMs) and the Nuclear Command and Control-Extremely Sensitive Information (NC2-ESI) access control program.

5.6.2 Additionally, contractor staff in direct support of this contract will require access to Foreign Government Information (FGI).

Some aspects of this effort will require select contractor personnel to be indoctrinated into Special Access Programs (SAP) based on Joint Staff J-36 operational requirements.

5.7 Negligent Discharge of Classified Information (NDCI)

5.7.1 When information is placed on or processed on an information system with insufficient security controls to appropriately protect it (e.g., classified data on an unclassified system) there is a potential for an unauthorized disclosure. Such actions will be classified as a security violation, specifically a negligent discharge of classified information or NDCI. Contractors that cause NDCIs during the course of the contract shall be held financially liable for all actual accumulated restoration costs incurred, as described below, but not less than $5,000 per incident. Such costs will be deducted from the contract price and are not reimbursable.

5.7.2 Restoration costs above $5,000 will be itemized. DISA has developed a Classified Message Incident Standard Operating Procedures (SOP) that will be followed in the event of an NDCI by the Contractor. Personally Identifiable Information (PII) incidents fall under this category. This is not an exclusive remedy (e.g., in the case of PII spillage, identity theft or other insurance may be needed to protect the individuals).

5.7.3 NDCI Cleanup actions may include the following actions:

Server destruction Hard drive wipe and destruction Containment actions

5.7.4 Applicable Documents:

Department of Defense (DOD) Manual Number 5200.01 Volume 3 “DOD Information Security Program: Protection of Classified Information” dated 24 February 2012 JCS Office of the CIO “Joint Staff Information Assurance (IA) Security Incident Response Standard Operating Procedures” dated October 2009 Director of the Joint Staff Memorandum “Remedial Actions for Security Incidents Related to Use of Joint Staff Information Technology or Cyber Systems” dated TBD DoD 5220.22-M, "National Industrial Security Program Operating Manual," February 28, 2006, DoD 5220.22-R, "Industrial Security Regulation," December 4, 1985.

6 Additional Performance Details

6.1 Hours of Operation

6.1.1 The Contractor is responsible to perform between the core hours of 0800 and 1700 Monday thru Friday, except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings.

6.1.2 The Contractor shall at all times maintain an adequate work force for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons.

6.1.3 When hiring personnel, The Contractor shall keep in mind that the stability and continuity of the work force are essential.

6.2 Place of Performance

The primary place of performance for this effort is the Joint Staff, Room MA924, The Pentagon, Washington, D.C.

6.3 Period of Performance

Base Period: 28 March 2026 – 27 March 2027 Option Period I: 28 March 2027 – 27 March 2028 Option Period II: 28 March 2028 – 27 March 2029 Option Period III: 28 March 2029 – 27 March 2030 Option Period IV: 28 March 2030 – 27 March 2031

6.4 Recognized Holidays

The federal Government recognizes the following holidays. Generally, federal facilities are closed. Other than those instances where contractor support might be required. The Contractor is not required to perform on the following holidays’ corresponding calendar days:

New Year’s Day Birthday of Martin Luther King, Jr.

Washington’s Birthday Memorial Day Juneteenth National Independence Day Independence Day Labor Day Columbus Day Veterans Day Thanksgiving Day Christmas Day

6.5 Travel

6.5.1 Requirements

6.5.1.1 The Contractor shall perform travel, when necessary, in accordance with FAR 31.205-46 “Travel Costs,” and the Joint Travel Regulations (JTR). All travel shall be pre-approved by the COR. Below is an estimate of required travel.

6.5.1.2 Location / Duration (days) / Number of Trips / Number of Persons / Per Year: Staff Assistance Visit (SAV) Location Duration Number of Trips Number of Persons

UCOP WG PACOM / Honolulu, HI / 5 / 1 / 2 PACOM / USFK / 12 / 3 / 1 / Not greater than a maximum of 3 people NORTHCOM / Colorado Springs, CO / 3 / 2 / 2 UCOP WG SOUTHCOM / Miami, FL / 5 / 1 / 2 CENTCOM/ SOCOM / SOUTHCOM Miami / Tampa, FL / 6 / 2 / 2 STRATCOM / Omaha, NE / 3 / 2 / 2 TRANSCOM / O'Fallon, IL / 3 / 1 / 2 Raven Rock, PA / 1 / 7 / 5 JS J6CCD / Norfolk, VA / 2 / 6 / 2 AFRICOM / EUCOM / Stuttgart, GE / 7 / 2 / 2 COP WG NORTHCOM / Colorado Springs, CO / 6 / 1 / 4 DISA HQ / FT Meade, MD / 1 / 6 / 2 Key West, FL / 4 / 2 / 1 Waltham, MA / 3 / 2 / 2 Omaha, NE / 4 / 2 / 1 Laurel, MD / 2 / 4 / 2 Warren AFB, WY / 3 / 2 / 2

6.5.2 Reimbursement

6.5.2.1 Travel

6.5.2.1.1 Area of Travel. Performance under this contract may require travel by contractor personnel. If travel, domestic or overseas, is required, the contractor is responsible for making all needed arrangements for his personnel. This includes but is not limited to the following:

Medical Examinations Immunization Passports, visas, etc.

Security Clearances

6.5.2.1.1.1 All contractor personnel required to perform work on any U.S. Navy vessel will have to obtain boarding authorization from the Commanding Officer of the vessel prior to boarding.

6.5.2.2 Travel Policy. The Government will reimburse the contractor for allowable travel costs incurred by the contractor in performance of the contract and determined to be in accordance with FAR subpart 31.2, subject to the following provisions:

6.5.2.2.1 Travel required for tasks assigned under this contract shall be governed in accordance with rules set forth for temporary duty travel in FAR 31.205-46.

6.5.2.3 Travel. Travel, subsistence, and associated labor charges for travel time are authorized, whenever a task assignment requires work to be accomplished at a temporary alternate worksite.

6.5.2.3.1 Travel performed for personal convenience and daily travel to and from work at contractor’s facility will not be reimbursed.

6.5.2.4 Per Diem. Per diem for travel on work assigned under this contract will be reimbursed to employees consistent with company policy, but not to exceed the amount authorized in the Department of Defense Joint Travel Regulations.

6.5.2.5 Shipboard Stays. Whenever work assignments require temporary duty aboard a government ship, the contractor will be reimbursed at the per diem rates identified in paragraphs C8101.2C or C81181.3B(6) of the DOD Joint Travel Regulations, Volume 2.

6.5.2.6 Air/Rail Travel. In rendering the services, the contractor shall be reimbursed for the actual costs of transportation incurred by its personnel not to exceed the cost of tourist class rail, or plane fare, to the extent that such transportation is necessary for the performance of the services hereunder and is authorized by the Ordering Officer. Such authorization by the Ordering Officer shall be indicated in the order or in some other suitable written form.

6.5.2.6.1 NOTE: To the maximum extent practicable without the impairment of the effectiveness of the mission, transportation shall be tourist class. In the event that only first-class travel is available, it will be allowed, provided justification therefore is fully documented and warranted.

6.5.2.7 Private Automobile. The use of privately owned conveyance within the continental United States by the traveler will be reimbursed to the contractor at the mileage rate allowed by Joint Travel Regulations. Authorization for the use of privately owned conveyance shall be indicated on the order. Distances traveled between points shall be shown in standard highway mileage guides.

Any deviations from distance shown in such standard mileage guides shall be explained by the traveler on his expense sheet.

6.5.2.8 Car Rental. The contractor shall be entitled to reimbursement for car rental, exclusive of mileage charges, as authorized by each order, when the services are required to be performed outside the normal commuting distance from the contractor’s facilities. Car rental for TDY teams will be limited to a rate of one car for every four (4) persons on TDY at one site.

7 Contracting Officer’s Representative (COR) & Subject Matter Expert (SME) Contracting Officer’s Representative (COR):

LTC Mark Trapp mark.e.trapp.mil@mail.mil & Phone 703-983-0157

Global Joint C2 Subject Matter Expert:

Mr. Key Watkins (GS-15) oakley.k.watkins2.civ@mail.mil & Phone 703-693-9676

NC3 Systems Subject Matter Expert:

Mr. Tim Price timothy.m.price.civ@mail.mil & Phone 703-693-7536

8 Contractor Personnel Minimum Requirements

8.1 Project Manager (Policy and Planning)

Serves as the National Military Command Systems (NMCS) Exercise Officer to support national-level nuclear decision makers, the Joint Staff, and Combatant Commanders in the operational and threat environments expected during the full spectrum of crisis, to include nuclear war. The Exercise Officer will inform senior Joint Staff military and government civil servants on NC3 system trends derived from assessment data and, when appropriate, provide recommendation to improve NC3 system performance and preserve NC3 system capability.

Provides means to the NMCS leadership to examine assets and procedures to provide end-to-end connectivity from warning sensors to national decisionmakers to executing forces through the NMCS. Identifies NC3 system deficiencies, isolates their causes, assigns appropriate corrective actions, and monitors problem resolution.

This position establishes assessment and exercise requirements, objectives, schedules and participation levels. Develops format of final operational and technical reports. Monitors results to assess the effectiveness of applicable emergency action and operational procedures. Supports Joint Staff leadership by providing feedback on the effectiveness, reliability, and responsiveness of the NC3 system and personnel proficiency. Assigns distributes, and monitors action items for resulting discrepancies. Provides trend analysis for NC3 community use. Develops data collection requirements for assessments, compliance standards, exercises, outage reports, inspections, testing, and service reports to enable operational risk assessment across the NMCS.

Education and Experience: A Bachelor’s degree from an accredited college or university is required. Contractor must possess an understanding of the standard methods, procedures and techniques of research and analysis in the subject matter field; ability to acquire subject matter information about the field and related fields; and knowledge of literature resources in the field. Five (5) years qualifying experience without a degree.

8.2 Nuclear Assessment Exercise Officer (Policy and Planning) Serves as a National Military Command System (NMCS) Project Manager enabling effective configuration management using organic technical expertise in systems architecture, integration, and cybersecurity. The NMCS Project Manager will develop and maintain enterprise architectures and document key operational activities, information and data exchanges, system components, functions, interfaces, infrastructure and communications assets into the NC3 operations within the NMCS.

Provides an information technology specialty to develop NMCS operational and architectural requirements on behalf of the Joint Staff to operate the NMCS. Submit Joint Staff NC3 requirements to the NC3 Enterprise Lead and the NC3 Enterprise Center who will develop, engineer, and integrate enterprise solutions for the Department.

This position develops and maintains architectural system views of the NMCS. Ensure NMCS system information is obtained from applicable program managers and/or subject matter experts, to include acquisition, sustainment, modernization, and O&M information. Consults with program managers and users to resolve user identified issues and requirements in the architectural design.

Communicate technical needs, opportunities and constraints to program managers and senior leadership. Liaise with NC3 systems architects to resolve communications and information systems integration problems.

Education and Experience: A Bachelor’s degree from an accredited college or university is required. Project Management Professional (PMP) Certification desired. Information Technology Infrastructure Library (ITIL) Foundations, equivalent, or higher certification desired. Contractor must possess an understanding of the standard methods, procedures and techniques of research and analysis in the subject matter field; ability to acquire subject matter information about the field and related fields; and knowledge of literature resources in the field. Five (5) years program management experience is required without degree or PMP certification.

8.3 Cyber Policy Officer (Policy and Planning)

Provides security analysis, planning, design and direction of major technology projects with National Military Command System (NMCS) impact. Represents and assists the J36 in overall planning, direction and management of cybersecurity requirements efforts of the NMCS. Communicates complex technical requirements to nontechnical personnel.

Participates in the NMCC Configuration Management Board (CMB) and the NMCS CMB (when established). Reviews proposed new systems, networks, and software designs for potential security risks; recommends mitigation strategies.

Maintains relationships with internal and external mission partners to ensure expedited and timely resolution of problems in support of the greater mission success. Applies expertise and broad professional knowledge of information security/ information assurance policy, standards and practices to all components of the enterprise.

Education and Experience: A Bachelor’s degree from an accredited college or university in a STEM field is required. Certified Information System Security Professional (CISSP) Certification is desired. Contractor must possess an understanding of the standard methods, procedures and techniques of cyber defense, cybersecurity analysis in the subject matter field; ability to acquire subject matter information about the field and related fields; and knowledge of literature resources in the field. Five (5) years of cyber/information system experience is required without degree or CISSP certification.

8.4 NC3 System Architect (Enterprise Architecture)

Provides analysis, planning, design and direction of major technology projects with the National Military Command System (NMCS) impact. Represents and assists the J36 in overall planning, direction and management of architectural requirements efforts of the NMCS. Communicates complex technical requirements to nontechnical personnel.

This position assesses communications and information systems for architectural compliance in order to meet technical requirements to ensure current NMCS and solutions adhere to the Nuclear Command and Control Technical Performance Criteria as defined in CJCSI 6811.01. Provides architecture modeling/analysis knowledge to identify and develop solutions to complex enterprise problems.

Determines the gaps in the current architecture and develops plans for resolution. Ensures technical integration is achieved by participating in test planning, validation, and reviews.

Coordinates with other organizations in the NMCS to maintain accurate data, to include DISA, Combatant Commands, service components, and other mission partners. Responsible for establishing configuration control requirements and procedures by providing guidance and direction to all mission partners to assure compliance with established procedures and guidelines. Responsible for the maintaining the local repository of reference models and information repository. Develops and support architectural change control processes to support technical systems integration and interoperability design. Establishes the documentation required for system baselines. Reviews and determines the adequacy and accuracy of the system baselines. Participates in the NMCC Configuration Management Board (CMB) and the NMCS CMB (when established). Reviews proposed new systems, networks, and software designs for potential security risks; recommends mitigation strategies, and resolves integration issues related to the implementation of new systems within the existing infrastructure.

Maintains relationships with internal and external mission partners to ensure expedited and timely resolution of problems in support of the greater mission success. Applies expertise and broad professional knowledge of information security/ information assurance policy, standards and practices to all components of the enterprise architecture.

Education and Experience: A Bachelor’s degree from an accredited college or university is required. Four (4) years of successful and pertinent experience of such nature and level as to provide a knowledge of the basic principles, theories, practices, techniques, terminology and expressions of Nuclear Command and Control/Nuclear Command and Control Communications. Contractor must have experience with the DoD Architecture Framework. Contractor must possess an understanding of the standard methods, procedures and techniques of research and analysis in the subject matter field; ability to acquire subject matter information about the field and related fields; and knowledge of literature resources in the field. Ten (10) years qualifying experience without a degree.

8.5 NC3 Configuration Manager (Data Management)

Provides analysis, planning, design and direction of major technology projects with National Military Command System (NMCS) impact. Represents and assists the J36 in overall planning, direction and management of architectural requirements efforts of the NMCS. Communicates complex technical requirements to nontechnical personnel.

This position assesses communications and information systems for architectural compliance in order to meet technical requirements to ensure current NMCS and solutions adhere to the Nuclear Command and Control Technical Performance Criteria as defined in CJCSI 6811.01. Provides architecture modeling/analysis knowledge to identify and develop solutions to complex enterprise problems.

Determines the gaps between the current and target architecture and develops plans for transition to target architecture.

Coordinates with other organizations in the NMCS to maintain accurate data, to include DISA, Combatant Commands, service components, and other mission partners. Responsible for establishing configuration control requirements and procedures by providing guidance and direction to all mission partners to assure compliance with established procedures and guidelines. Responsible for the maintaining the local repository of reference models and information repository. Develops and support architectural change control processes to support technical systems integration and interoperability design. Establishes the documentation required for system baselines. Reviews and determines the adequacy and accuracy of the system baselines. Participates in the NMCC Configuration Management Board (CMB) and the NMCS CMB (when established). Reviews proposed new systems, networks, and software designs for potential security risks; recommends mitigation strategies, and resolves integration issues related to the implementation of new systems within the existing infrastructure.

Maintains relationships with internal and external mission partners to ensure expedited and timely resolution of problems in support of the greater mission success. Applies expertise and broad professional knowledge of information security/ information assurance policy, standards and practices to all components of the enterprise architecture.

Education and Experience: A Bachelor’s degree from an accredited college or university is required. Four (4) years of successful and pertinent experience of such nature and level as to provide a knowledge of the basic principles, theories, practices, techniques, terminology and expressions of Nuclear Command and Control/Nuclear Command and Control Communications. Contractor must have experience with the DoD Architecture Framework. Contractor must possess an understanding of the standard methods, procedures and techniques of research and analysis in the subject matter field; ability to acquire subject matter information about the field and related fields; and knowledge of literature resources in the field. Ten (10) years qualifying experience without a degree.

8.6 NC3 Network Engineer (Enterprise Architecture)

Provides monitoring, planning, design and direction of major technology projects with the NMCS impact. Represents and assists the J36 in overall planning, direction and management of Configuration Management (CM) requirements efforts of the NMCS.

Communicates complex technical requirements to nontechnical personnel. Provides knowledge to identify and develop solutions to change management and control problems. Determines the gaps in the current documentation and develops plans for resolution.

Ensures technical integration is achieved by participating in test planning, validation, and reviews.

Coordinates with other organizations in the NMCS to maintain accurate data, to include DISA, Combatant Commands, service components, and other mission partners. Responsible for establishing configuration control requirements and procedures by providing guidance and direction to all mission partners to assure compliance with established procedures and guidelines. Responsible for the maintaining the local repository of CM artifacts and information repository. Establishes the documentation required for CM baselines.

Reviews and determines the adequacy and accuracy of the CM baselines.

Maintains relationships with internal and external mission partners to ensure expedited and timely resolution of problems in support of the greater mission success. Applies expertise and broad professional knowledge of information security/ information assurance policy, standards and practices to all components of the CM.

Education and Experience: A Bachelor’s degree from an accredited college or university is required. Four (4) years of successful and pertinent experience of such nature and level as to provide a knowledge of the basic principles, theories, practices, techniques, terminology and expressions of Nuclear Command and Control/Nuclear Command and Control Communications. Information Technology Infrastructure Library (ITIL) Foundations, equivalent, or higher.

8.7 NC3 Policy Officer (Policy and Planning)

Leads and directs all policy activities in support of the J36 priorities for the sustainment and modernization of future NMCS operational requirements. Oversees the policies of all N2C3 system and capability activities from development through implementation. Represents and assists the J36 in overall planning, direction and management of policy requirements efforts of the NMCS.