Attachment 2 - Performance Work Statement.pdf

PERFORMANCE WORK STATEMENT (PWS)

TO PROVIDE

NUCLEAR WEAPONS AND ICBM MAINTENANCE/LOGISTICS SOFTWARE

APPLICATION DEVELOPMENT AND SUSTAINMENT

FOR

AIR FORCE GLOBAL STRIKE COMMAND

As of January 2026

Table of Contents

EXECUTIVE SUMMARY

1. PURPOSE

2. SCOPE

3. REQUIREMENT(S)/DESCRIPTION OF SERVICE(S)

3.1 Requirements/Duties:

3.2 Additional Requirements and Options

3.3 Personnel Qualifications

3.4 Transition Periods

4. CERTIFICATION REQUIREMENTS

4.1 Information Assurance (IA)

5. CONTRACTUAL REQUIREMENTS

5.1 Place of Performance

5.2 Travel

5.3 Business Hours / Normal Hours of Operation

5.4 Federal Holidays

5.5 Government Support Services

5.6 Non-Personal Services

5.7 Contractor Identification

5.8 Contract Manager

5.9 Documentation and Data Management

5.10 Security

5.11 Training

5.12 Software Support and Data Rights

5.13 Continuation of Essential Contractor Services During Crisis Declared by the President of the United States, the Secretary of Defense, or Overseas Combatant Commander

5.14 Associate Contractors

5.15 Use of Non-Compete Clause

5.16 Contractor Full-Time Equivalent Reporting

6. SERVICES SUMMARY (SS)

6.1 Quality Control

6.2 Quality Assurance

7. CONTRACT DATA REQUIREMENTS LIST (CDRL)

8. APPLICABLE STANDARDS AND REFERENCES

APPENDIX 1: DEFINITIONS USED IN THE PWS

APPENDIX 2: YEARLY AVERAGE HISTORICAL WORK (2014-2025)

APPENDIX 3: ACRONYMS

APPENDIX 4: PUBLICATIONS

EXECUTIVE SUMMARY

Air Force Global Strike Command (AFGSC) and the Air Force Nuclear Weapons Center (AFNWC), in accordance with Air Force Manual (AFI) 21-200, Munitions and Missile Maintenance, must advocate for sustainment of Nuclear Munitions Command and Control (NMC2) in order to maintain standardization of the Air Force nuclear weapons, cruise missile, and Intercontinental Ballistic Missile (ICBM) maintenance management, sustainment, and status reporting. The Air Force seeks to modernize NMC2 through a base year and four (4) option year contracts.

A high level of Air Force nuclear weapons, cruise missile, and ICBM maintenance and sustainment knowledge and expertise is required in order to simultaneously balance user requirements and ensure, to the greatest extent possible, that appropriate site configuration, and application product deployments avoid inherent classification compromises caused by improper data aggregation. Primary requirements are for comprehensive software application lifecycle support, to include requirements development and design, application implementation, data analysis and storage architecture, unit and usability testing, permission architecture and management, user training and onboarding support, and continuous support and sustainment. In addition, as needed, develop enhancements and change requests based of usage analysis, recurring maintenance, and daily contact with users to ensure a seamless user experience. It should be noted that the NMC2 hosting environment and server management is provided by Enterprise Information Services (EIS) and is not a part of this effort, but the contractor will have to work with EIS to ensure server configuration changes/updates are accounted for in the user experience.

1. PURPOSE

At the direction of Headquarters Air Force (HAF) nuclear weapons, Missiles and Munitions Division (A4LW) NMC2 was developed to standardize nuclear weapons, cruise missile and ICBM maintenance command and control application for control of daily maintenance, scheduling, and reporting activities. Use of NMC2 for the nuclear enterprise is mandatory and provides credentialed and authorized users the ability to collaborate on information and obtain near real-time updates, retrieval, and sharing of data from any location, at any time.

The NMC2 site collection consists of 150+ sites, 25+ applications/analytic dashboards, with over 28,000 users across 500 distinctly purposed permission groups. These sites are focused primarily on organizations that have a need for daily command and control (C2) collaboration of nuclear enterprise related maintenance and logistic activities. Data contained within the sites and applications are structured around the needs of each major command (MAJCOM) -- AFGSC, United States Air Forces Europe (USAFE), and Air Force Materiel Command (AFMC). The resounding success of the current site collection is directly attributed to the use of SMEs as the architects and day to day administrators.

Use of the NMC2 site collection, and all it contains, is utilized by all entities of the Air Force nuclear enterprise and United States Strategic Command (USSTRATCOM), users include Headquarters Air Force (HAF) to the lowest field level units. Primary personnel utilizing NMC2 encompass personnel stationed in all four time zones in the 48 contiguous states and across two time zones in Europe.

Stakeholders are nuclear deterrence decision planners, their associated wing/group/squadron commanders, all 21M3N and 13NXX assigned to the aforementioned locations, 2M0XX/2W0XX/2W1XX/2W2XX Air Force Specialty Code (AFSC) Career Field and MAJCOM Functional Managers, all maintenance personnel, as well as thousands of AF civilians supporting the Air Force nuclear enterprise. Career Field Managers for the above-mentioned AFSCs also accomplish developmental team actions for all Technical Sergeants and above using NMC2 as well as coordinate with the Air Force Personnel Center (AFPC) using NMC2. Also, per AFI 20-110, Nuclear Weapons Related Materiel Management, NMC2 is the host of the official Air Force Nuclear Weapons Related Materiel (NWRM) listing and NWRM discrepancy reporting and analysis tool; the NWRM applications are utilized by maintenance and supply personnel from across the Air Force.

NMC2 administrators (contractor employees) require vast experience and a complete familiarity of the daily Intercontinental Ballistic Missile (ICBM), cruise missile, nuclear bomber and fighter, as well as North Atlantic Treaty Organization (NATO) nuclear weapons maintenance and logistics activities. NMC2 administrators must be thoroughly familiar with the roles, responsibilities, and missions of all entities represented in the site collection; understanding the relationships between Air Force organizations within the nuclear enterprise is critical. Administrators must also have an in-dept knowledge and understanding of deployed applications within NMC2 in order to support day-to-day logistics, personnel management, and leadership reporting needs.

2. SCOPE

The Air Force requires this contract to support over 28,000 users across 500 distinctly purposed and managed permission groups, which must remain intact to ensure data confidentiality, integrity, and availability. The contractor shall be thoroughly familiar with the roles, responsibilities and missions of all NMC2 nuclear enterprise entities, and their respective permission groups and hierarchies, in order to properly execute user permission group, change requests, or data display change requests while also preventing these requests from inherently resulting in classification compromises caused by improper data aggregation (classification through compilation).

3. REQUIREMENT(S)/DESCRIPTION OF SERVICE(S)

Factor Data

Average daily unique users 1000+

Application age Approximately 16 years

Life expectancy N/A – Determined by EIS

Platform M365 government cloud

COTS SharePoint Framework (SPFx) compatible Languages HTML, TypeScript/JavaScript, and CSS

Avg. transactions per day 10,000-20,000 clicks or queries including application usage

NMC2 request volume 20 per day directly relating to application usage/functions, data configuration, and access requirements

Access Controls Current implementation has ~500 distinct groups across all applications and data storage

3.1 Requirements/Duties:

At all times, the contractor shall utilize their Air Force nuclear weapons, cruise missile, and ICBM maintenance expertise to properly manage and oversee all NMC2 applications and dashboards to include data storage configurations and reports to prevent potential Classified Messaging Incidents (CMIs), which may occur by improper data classification or data aggregation (classification through compilation). While the contractor is not expected to monitor all user input for CMI potential, the contractor must ensure the aforementioned applications and dashboards products presented to the user do not inherently prompt for or report data fields which would result in potential CMIs. The contractor shall manage the composition and usage of ~500 Nuclear Enterprise permission groups comprised of over 28,000 individual users. All requirements below shall be accomplished using COTS features. Contractor duties fall into five areas of responsibility.

3.1.1 Application and Data Storage Administration

NMC2 administration requires in depth knowledge in the areas of Air Force nuclear weapons, cruise missile, and ICBM maintenance practices, nuclear capable unit mission roles, depot support units, training organizations, as well as unit personnel certifications, qualifications and functions. This knowledge will be used to build, improve, and maintain tools that save user’s time, drive improved/more efficient process, and to draw insights not readily obvious from raw data. The contractor will also use their knowledge of the Air Force nuclear enterprise to quickly ascertain whether user-requested enhancements to applications and data storage configurations will result in a potential CMI and offer alternative solutions where potential exists. Specifically, the contractor shall perform the following:

3.1.1.1 Maintain standardization across the nuclear enterprise for nuclear weapons, cruise missile, and ICBM maintenance and logistics processes, to the maximum extent possible, across the entire site collection for similar mission areas (CDRL A001)

3.1.1.2 Identify, coordinate, and aggregate best practices across units into standardized applications

(CDRL A001)

3.1.1.3 Adapt current and future application, dashboards, data storage, and user permission groups and hierarchies to Air Force nuclear enterprise organizational changes (CDRL A001, A002)

3.1.1.4 Provide a means for user support requests (CDRL A001, A002, A003). Approximation based on historical data is 400-450 user requests per month

3.1.1.5 Assist nuclear units with Nuclear Maintenance Certification Tool (NMCT) data analysis, user issues, AF Form 2435 maintenance to include corrections and transcriptions, certification task template management, in-processing and out-processing individuals, and user access requirements based on their functional roles IAW AFI 21-204, Nuclear Weapons Maintenance. Define requirements for enhancements and solutions to NMCT that address user issues, data analysis requests, new feature requests and 2435 maintenance issues (CDRL A001, A002)

3.1.1.6 If requested provide on-location NMC2 site visits as detailed in paragraph 5.2. Take user inputs as potential action items. Assess ad hoc home-grown data tools and translate into meaningful, intuitive, standardized data applications to be used where applicable across the Air Force Nuclear Enterprise. Track and coordinate action items through appropriate configuration manager(s) and Contracting Officer’s Representative (COR) (CDRL A001, A002)

3.1.1.7 Monitor and provide change management, process adoption and refinement support for the following NMC2 applications (CDRL A001, A002):

3.1.1.7.1 ICBM: VES tracking, Site Log, Equipment Tracker, Daily Status, Maintenance Schedule, RS/RV Configuration Control, AVDO, ETAR, MAR 1067 dashboard, MEEL dashboard, ORP/SPF dashboard

3.1.1.7.2 B61-12 TKA: ETAR, MAR, DR, FTE, GFE, CFE, FTA, and TYPE Trainers and SATS

3.1.1.7.3 NWRM Discrepancy Reporting Analytics

3.1.1.7.4 NEMT database

3.1.1.7.5 USAFE Equipment Tracking and WS3 Equipment Analytics dashboard

3.1.1.7.6 NCP UR analytics dashboard and Nuclear Weapons Container and Bolster dashboard

3.1.1.7.7 NMCT

3.1.1.7.8 All new application developed and deployed under this contract

3.1.1.8 Provide user support (on-location as detailed in paragraph 5.2, through email, and over the phone) for the following existing applications as well as all new application/dashboards developed under this contract:

3.1.1.8.1 ICBM VES tracking application - This support will include assistance with bar code generation, backend permission configuration, Integrated Maintenance Data System (IMDS) vehicle and equipment integration, vehicle and equipment build requests, recovery and lost tool management (CDRL A001, A002)

3.1.1.8.2 ICBM Site Log application - This support will include backend permission configuration, external application data storage maintenance, managing checklist entries, and fault repeat/recur analysis (CDRL A001, A002)

3.1.1.8.3 ICBM Equipment tracking application for Missile Guidance Set (MGS) and Boosters - This support will include permission configuration, external application data storage maintenance, and entry/deletion assistance as needed (CDRL A001, A002)

3.1.1.8.4 ICBM Daily Status Dashboard. This support will include permission configuration, external application data storage maintenance for MEEL and ORP/SPF, and ICBM Status conditions (CDRL A001, A002)

3.1.1.8.5 ICBM Maintenance Schedule dashboard. This support will include permission configuration, external application data storage maintenance for (unit daily, weekly, and quarterly schedule) (CDRL A001, A002)

3.1.1.8.6 ICBM RS and RV Configuration Control database and lookup tool. This support will include permission configuration, external application data storage maintenance and assistance with individual weapon system form maintenance and updates (CDRL A001, A002)

3.1.1.8.7 ICBM AVDO Reporting application. This support will include permission configuration, external application data storage maintenance, and support for each type of ICBMAVDO report per DAFI 21-103 (CDRL A001, A002)

3.1.1.8.8 ICBM ETAR application. This support will include permission configuration, external application data storage maintenance, alert management, search tool assistance, data analysis, and Artificial Intelligence (AI) generated request comparisons (CDRL A001, A002)

3.1.1.8.9 ICBM MAR application. This support will include permission configuration, external application data storage maintenance, alert management, search tool assistance, and data analysis (CDRL A001, A002)

3.1.1.8.10 ICBM 1067 Staffing dashboard. This support will include permission configuration and external application data storage maintenance (CDRL A001, A002)

3.1.1.8.11 ICBM MEEL and ORP/SPF item dashboard. This support will include permission configuration, external application data storage maintenance, compatibility with the ICBM Status Dashboard, updates to data points in storage configurations, and assistance with sorting and filtering all data (CDRL A001, A002)

3.1.1.8.12 TKA ETAR application. This support will include permission configuration, external application data storage maintenance, alert management, search tool assistance, and data analysis (CDRL A001, A002)

3.1.1.8.13 TKA MAR application. This support will include permission configuration, external application data storage maintenance, alert management, search tool assistance, and data analysis (CDRL A001, A002)

3.1.1.8.14 TKA DR application. This support will include permission configuration, external application data storage maintenance, alert management, search tool assistance, and data analysis (CDRL A001, A002)

3.1.1.8.15 TKA FTE & GFE/CFE application. This support will include permission configuration, external application data storage maintenance, alert management, search tool assistance, and data analysis (CDRL A001, A002)

3.1.1.8.16 TKA FTA application. This support will include permission configuration, external application data storage maintenance, alert management, search tool assistance, data analysis, flight hour usage displays, and maintenance record storage (CDRL A001, A002)

3.1.1.8.17 TKA TYPE Trainers SATS application. This support will include permission configuration, external application data storage maintenance, alert management, search tool assistance, data analysis, approval workflow, and adjustments to account for new item procurement (CDRL A001, A002)

3.1.1.8.18 NWRM Discrepancy Reporting Analytics dashboard. This support will include permission configuration, external application data storage maintenance, search tool assistance, and data analysis (CDRL A001, A002)

3.1.1.8.19 NEMT database. This support will include permission configuration, external application data storage maintenance, search tool assistance, and data analysis (CDRL A001, A002)

3.1.1.8.20 USAFE Equipment Tracking and WS3 Equipment Analytics dashboard. This support will include permission configuration, external application data storage maintenance, alert management, search tool assistance, data analysis, and adjustments to account for new unit and equipment additions (CDRL A001, A002)

3.1.1.8.21 NCP UR analytics dashboard. This support will include permission configuration, external application data storage maintenance, search tool assistance, data analysis, and metric export and modifications (CDRL A001, A002)

3.1.1.8.22 Air Force Nuclear Weapons Container and Bolster dashboard. This support will include permission configuration, external application data storage maintenance, search tool assistance, data analysis, and adjustments to account for new unit and equipment additions

(CDRL A001, A002)

3.1.1.9 Coordinate with Air Force Enterprise Information Management personnel on scheduled server maintenance, site storage space allocation, and planned upgrades, as required (CDRL A001, A002, A003)

3.1.1.10 Work with server host administrators to help diagnose and resolve host hardware- and software-induced issues (CDRL A002, A003)

3.1.2 Application Permission Management

NMC2 application permission configurations across all applications and ~500 distinct permission groups necessitate strong Air Force nuclear enterprise expertise; not only to permit authorized users to requested data and application functions, but to also prevent unit data modification or access through unauthorized user privileges. Specifically, the contractor shall perform the following:

3.1.2.1 Configure backend permission hierarchies and access for over 1000 unique data storage configurations based on mission requirements, to ensure users’ need-to-know access is met

(CDRL A001)

3.1.2.2. Work with the ICBM Operations community to ensure all ICBM missile launch officer and their leadership’s permission groups have appropriate access to the ICBM Daily Status, ICBM Maintenance Schedule, and ICBM Site Log application for their respective units (CDRL A001)

3.1.2.3 Work with the ICBM System Program Office (SPO) to ensure all applicable engineering, program manager, system manager, and equipment specialist permission groups have access to the ICBM ETAR and MAR applications, ICBM Site Log application, and the Periodic Depot Maintenance (PDM) application (CDRL A002)

3.1.2.4 Work with the AFGSC Supply community, fuels managers, and helicopter operators to ensure the appropriate permission groups have access to the ICBM Helicopter Refueling tracking applications (CDRL A002)

3.1.2.5 Work with AFGSC vehicle manager to ensure the appropriate permission groups have access to the AFGSC armored vehicle management site (CDRL A002)

3.1.2.6. Work with the TKA SPO to ensure all applicable engineers, program manager, system managers, and equipment specialists permission groups have access to applicable applications (TKA DR, ETAR, MAR, FTA, TYPE Trainers/SATS, etc.) (CDRL A002)

3.1.2.8 Work with permission managers at all levels to ensure they have the appropriate access to add and delete users into their specific unit/functional permission groups and assist if necessary

(CDRL A002)

3.1.3 Application and Data Storage Enhancement and Development

NMC2 application development, sustainment, and modification require unwavering Air Force nuclear maintenance and data classification diligence. Specifically, the contractor shall perform the following:

3.1.3.1 Provide users the capability to aggregate information into algorithms and reports, develop data visualizations, and enforce and expedite standard processes and business logic using built SPFx applications that cannot be provided by standard M365 government cloud functionality

(CDRL A002)

3.1.3.2 Create web forms and application models that enforce Air Force business logic and processes, based on requirements from the nuclear enterprise maintenance and logistics processes

(CDRL A002)

3.1.3.3 Develop new tools, data analysis workspaces, dashboards, and applications as requested by users, after such requests are approved by the COR (CDRL A001, A002, A003) (Historical workload for new site development is approximately 20 sites and 4-5 applications annually)

3.1.3.4 Provide comprehensive maintenance and sustainment support for all currently deployed applications (CDRL A002)

3.2.1.5 Provide updates to existing web service interfaces and data storage schemas supporting all applications as required

3.1.3.6 Design, Implement/Enhance, and Sustain the below applications (CDRL A001, A002, A003)

3.1.3.6.1. Develop and sustain a “Help Desk” type application that answers user questions and connects them to relevant resources by searching a knowledge base and site's data fields. Leverage existing data and advanced search capabilities, to provide seamless and efficient user experience while reducing the burden on staff (CDRL A001, A002, A003) (2026)

3.1.3.6.2. Enhance/modify the Minimum Essential Equipment Listing to include:

3.1.3.6.2.1. Additional columns to display Defense Property Accountability System authorizations and levels (CDRL A001, A002, A003) (2026)

3.1.3.6.2.2 Display metrics to show a visual breakdown of equipment levels (CDRL A001, A002, A003) (2026)

3.1.3.6.3 Create field training detachment tracker application to:

3.1.3.6.3.1 Document training deviations such as, wing, class, hours, reason, etc. to provide real time data (CDRL A001, A002, A003) (2027)

3.1.3.6.3.2 Present real time metrics to be presented to leadership (CDRL A001, A002, A003) (2027)

3.1.3.6.4 Create an application to build, route, and track field training detachment pre-requisite class requirements (CDRL A001, A002, A003) (2027)

3.1.4 Contract Management

The requirements in the area of contract management are administrative duties associated with continuity of operations. These duties do not define overall contract management responsibilities of the contractor or Government. Specifically, the contractor shall perform the following:

3.1.4.1 Provide a staffing plan detailing how contractor will minimize disruption of services and support when planned/unplanned absences longer than 6 business days occur (CDRL A001, A002, A004, A005, A006)

3.1.4.2 Develop continuity plans for phase-out period as specified in 3.5.2. (CDRL A001)

3.1.4.3 Provide site collection access to COR equal to that of contractor personnel (CDRL A001)

3.1.4.4 Submit contract data requirement list (CDRL) items in accordance with timeframes noted in Section 7, CDRL, of this PWS

3.2 Additional Requirements and Options

For the requirements and options listed below, specific CDRLs are required as listed in section 7 of this PWS (CDRL AXXX)

***Tasks listed in this section will come from section 3.1.3 after the AFGSC COR determines application priorities for the Base Year and each OY.

3.3 Personnel Qualifications

This effort involves application of extensive Air Force nuclear maintenance and logistics experience and proven capabilities in SPFx application development. The following qualifications are minimum qualifications necessary to perform the services described in sections 3.1.1, 3.1.2, and 3.1.3.

3.3.1 Nuclear Weapons Maintenance Expertise:

In order to ensure personnel responsible for nuclear weapons, cruise missile, and Intercontinental Ballistic Missile (ICBM) maintenance data management can quickly and accurately manage numerous applications, application permission configurations, and also identify actual/potential classification and security violations that would render the NMC2 environment inaccessible due to a CMI, contractor personnel shall have the following expertise:

3.3.1.1 A minimum of 20 years of experience in planning Air Force nuclear weapon, cruise missile, and ICBM maintenance activities at the USAF squadron level through center, Numbered Air Force (NAF), or other higher headquarters staff levels

3.3.1.2 A thorough understanding of Air Force Nuclear Weapons Security Classification Policy; CG- W-5, Joint DOE/DoD Nuclear Weapon Classification Policy Guide; TCG-WPMU-2, Joint DOE/DoD Topical Classification Guide for Weapon Production and Military Use; and GG-2, Joint DOE/DoD General Guidance for UCNI

3.3.1.3 Understanding of all nuclear-related deficiency management systems (i.e. deficiency reports, unsatisfactory reports, safety reports, nuclear flag-word reports) as detailed in 21-series and 91-series Air Force Instructions, as well as the Joint Nuclear Weapons Publication System

(JNWPS)

3.3.1.4 Understanding of the Air Force ICBM ETAR, STR, and SOR request process to include the staffing and routing

3.3.1.5 Understanding of Air Force and Department of Energy supply chain management as it relates to nuclear weapons, cruise missile, and ICBM maintenance

3.3.1.6 Thorough understanding of the Air Force NWRM discrepancy reporting and identification process as defined in DAFMAN 20-110, Nuclear Weapons Related Materiel Management

3.3.1.7 Thorough understanding of the Air Force Missile and Munitions management defined in

DAFMAN 21-200, Munitions and Missile Maintenance Management

3.3.1.8 Thorough understanding of the Air Force ICBM and Cruise Missile management defined in

AFMAN 21-202, Missile Maintenance Management

3.3.1.9 Thorough understanding of the Air Force Nuclear Maintenance Certification and Qualification program defined in AFMAN 21-204, Nuclear Weapons Maintenance

3.3.1.10 Thorough understating of the ICBM AVDO process defined in DAFI 21-103, Equipment

Inventory, Status and Utilization Reporting

3.3.1.11 Ability to obtain and retain, at a minimum, a SECRET/Critical Nuclear Weapon Design

Information (CNWDI) security clearance level

3.3.2 Air Force Nuclear Munitions Command and Control (NMC2) Expertise

3.3.2.1 Ten or more years of demonstrable experience with sustainment, development, migration, and/or optimization of NMC2 applications and data storage

3.3.2.2 Knowledge of the relationship of all permission groups to every application within NMC2

3.3.2.3 Knowledge of the stakeholders and their roles with regards to the data and applications within

NMC2

3.3.2.4 In depth knowledge of the NMC2 schema and the ability to assist users with locating required information relevant to their level of responsibility

3.3.2.5 Ability to assist users with understanding the relationships and interactions between all data applications; primary sources, feeder sources, and look-up sources

3.3.2.6 In-dept knowledge of all applications deployed in NMC2

3.3.2.7 Thorough understanding of the following:

ICBM Maintenance Processes

GMR Codes MOSR Codes

HHQ Directed Maintenance processes AVDO Reporting

Mission Essential Equipment List Operational Readiness Parts

Single Point Failure Parts Launch Facility Operations

Missile Alert Facility Operations Missile Field Helicopter Refueling Data

VES Tool Tracking Application LF and MAF Site Logs

FOT&E processes STR process

SORTS reporting requirements Site Logs

Weapons Storage Areas

Line Number Reporting RS/RV Configuration Mgmt. and Reporting

Pylon/ Launcher Status Reporting Dull Sword Reporting

Nuclear UR Reporting MS/BS Requirements

NMCT Operation Container/ Bolster Status and Reporting

H1616 Operations Nuclear Weapons Reportable T&H Equipment

DOE Equipment and Defect Tracking Req Explosive Operation Requirements

Nuclear Weapon System Specific Test Set Operations and Fault Reporting

Nuclear T&H Equipment ROs

TKA SPO

ETAR and MAR Staffing and Routing Deficiency Reporting

Nuclear Weapon System Sustainment Processes FTA Management

TYPE Trainers GFE, CFE, and FTE

3.3.3 Software Engineer and Development Experience

3.3.3.1 A minimum of 15 years designing and developing applications in a DoD or Air Force environment using SPFx compatible languages

3.3.3.2 A degree in Software or Computer Engineering

3.3.4 Key Personnel

The contractor shall notify the contracting officer in writing prior to the departure of any personnel that are fulfilling the nuclear weapons maintenance expertise function and identify the proposed substitution. Any proposed personnel substitution shall meet the expertise requirements of section 3.3.1, 3.3.2, and/or 3.3.2 and shall not assume the position until experience is validated by the Government.

3.4 Transition Periods

3.4.1 Phase-in Period

The contractor shall ensure a smooth transition from the previous contractor through a transition period which shall begin 7 calendar days prior to the start of the period of performance. The phase-in contractor shall be allowed access to the facility to familiarize personnel with equipment, facilities, and requirements. However, such access shall not interfere with the performance efforts of phase-out personnel. Arrangements for access to government facilities during this period shall be made with the

COR.

3.4.1.1 The contractor shall identify to the government a Transition Manager with the authority to accomplish all work necessary to successfully facilitate contract transition. This authority need not include the authority to bind the company contractually

3.4.1.2 The contractor and the government shall mutually agree on a time and date for a Pre- Performance Conference

3.4.1.3 The contractor shall be prepared to assume contract requirements upon completion of phase-in period

3.4.2 Phase-out Period

3.4.2.1 During the last 14 calendar days of the period of performance, the contractor shall provide, if applicable, transition assistance to another contractor or to the government. All work associated with the phase-out shall be part of the contractor’s regularly priced work and no additional hours/funding shall be authorized. During this period, the contractor shall be fully responsible for NMC2 operations.

3.4.2.2 During transition assistance, if applicable, the contractor shall provide system familiarity training and orientation to another contractor or designated government representatives. Such training and orientation will include, but is not limited to:

3.4.2.2.1 Granting another contractor or government representatives system permissions equal to those of the outgoing administrators

3.4.2.2.2 Training on NMC2 user permission management, application operation, data storage configuration modifications, or any other NMC2 feature which requires administrator (‘back-end’) access to accomplish

4. CERTIFICATION REQUIREMENTS

4.1 Information Assurance (IA)

Personnel performing IA activities are required to obtain, and remain current with, technical and/or management certifications to ensure compliance with DoD 8570.01-M, Information Assurance Workforce Improvement Program, 19 December 2005 (with all current changes), and as stipulated in DFARS 252.239-7001, Information Assurance Contractor Training and Certification.

5. CONTRACTUAL REQUIREMENTS

5.1 Place of Performance

Place of performance shall be determined by the contractor and remote access into NMC2 is permitted. Contractor employee(s) should expect to travel to prime NMC2 operating locations as directed by the Government. Travel requirements may include visits to Barksdale AFB, LA and visits to prime NMC2 operating locations: Malmstrom AFB, MT; FE Warren AFB, WY; Minot AFB, ND; Whiteman AFB, MO; Kirtland AFB, NM; Ellsworth AFB, SD; Spangdahlem AB, Germany (and its associated Munitions Support Squadron sites at Buechel, Germany; Volkel, The Netherlands; Ghedi, Italy; and Klein-Brogel, Belgium); Ramstein AB, Germany; Aviano AB, Italy;

Lakenheath AB, United Kingdom; and Incirlik AB, Turkey.

5.2 Travel

The contractor may be required to perform periodic travel both within and outside the Continental United States. Passports and VISAs will be required. The contractor shall coordinate specific travel arrangements with the CO or COR to obtain advance, written approval for the travel to be conducted.

The contractor’s written request for travel shall contain the dates, locations, and estimated costs of the travel. If any travel arrangements cause additional costs that exceed those previously approved, written approval by COR is required prior to undertaking such travel. Allowable travel costs are described in the Federal Acquisition Regulation (FAR) 31.205-46. The Joint Travel Regulation (JTR) does not apply to contractors; however, may be used to aid the CO and/or COR in making individual decisions regarding travel rules. The contractor shall be responsible for obtaining all passports/visas, passenger transportation, lodging, and subsistence, both domestic and overseas. The contractor shall travel using the lower cost mode transportation commensurate with the mission requirements. When necessary to use air travel, the contractor shall use tourist class, economy class, or similar accommodations. Travel shall be on an actual accrual basis; no profit or fee will be paid.

5.3 Business Hours / Normal Hours of Operation

The work week is 40 hours and overtime is not authorized. The average workday is 8 hours and the window in which those 8 hours are scheduled shall be during normal business hours which are 7:00 AM to 6:00 PM Central time zone, Monday through Friday, except federal holidays.

5.4 Federal Holidays

New Year’s Day January 1st Martin Luther King Day 3rd Monday in January Washington’s Birthday 3rd Monday in February Memorial Day Last Monday in May Juneteenth National Independence Day June 19th Independence Day July 4th Labor Day 1st Monday in September Columbus Day 2nd Monday in October Veterans’ Day November 11th Thanksgiving Day 4th Thursday in November Christmas Day December 25th

5.5 Government Support Services

If the contractor proposes on-site presence, the Government will furnish or make available working space, computer, network access, and telephone line access for contract personnel. The Government will provide the contractor with access to all facilities, as required, to perform in accordance with this PWS. The contractor shall be subject to all military rules and regulations while working on or visiting a military installation. The contractor shall coordinate with the COR to prepare for and send visit requests to the intended site’s point of contact with sufficient time for the site to process the contractor’s permission to obtain access to the Government facility.

5.6 Non-Personal Services

The Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the Government assign tasks to or prepare work schedules for individual contractor employees. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services or give the perception of personal services. If the contractor feels that any actions constitute, or are perceived to constitute personal services, it shall be the contractor’s responsibility to notify the CO immediately. These services shall not be used to perform work of a policy/decision making or management nature, i.e., inherently Governmental functions. All decisions related to programs supported by the contractor shall be the sole responsibility of the Government.

5.7 Contractor Identification

All contractor personnel shall be required to distinguish themselves from Government employees in accordance with AFFARS Clause 5352.242-9000, Contractor Access to Air Force Installations.

Contractor personnel are required to wear or prominently display installation identification badges or contractor-furnished, contractor identification badges while visiting or performing work on the installation. When conversing with Government personnel during business meetings, over the telephone or via electronic mail, contractor personnel shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify company affiliation.

Contractor personnel co-located with Government employees should identify their workspace area with their name and company affiliation.

5.8 Contract Manager

No later than 30 days after contract award, the contractor shall notify the CO in writing of a Contract Manager and an alternate who shall be the primary representative(s) responsible for the successful performance of this contract, including participation in Program Management Reviews and ensuring all contract standards are adhered to. The Contract Manager shall have full authority to act for the contractor on all contract matters relating to daily operations of this task order. The Contract Manager shall be available immediately during normal business hours to discuss problem areas.

After normal duty hours, the Program Manager shall be available within 3 hours. The contractor shall support stakeholder meetings, staff meetings, engineering meetings, and other program meetings, as required. The contractor shall provide the CO with written notice of any changes in the Contractor Manager and/or alternate no later than the effective date of the change.

5.9 Documentation and Data Management

The contractor shall establish, maintain, and administer an integrated data management system for collection, control, publishing, and delivery of all documents within NMC2. The data management system shall include but not be limited to the following types of documents: CDRLs, White Papers, Status Reports, Audit Reports, Agendas, Presentation Materials, Minutes, and Contract Letters. The contractor shall provide the Government with electronic access to this data, including access to printable reports.

5.9.1 Records, Files, Documents

All physical records, files, documents, and work papers, provided and/or generated by the Government and/or generated for the Government in performance of this PWS, maintained by the contractor which are to be transferred or released to the Government or successor contractor, shall become and remain Government property and shall be maintained and disposed of IAW AFI 33-322, Records Management and Information Governance Program; the Federal Acquisition Regulation, and/or the Defense Federal Acquisition Regulation Supplement, as applicable. Nothing in this section alters the rights of the Government or the contractor with respect to patents, data rights, copyrights, or any other intellectual property or proprietary information as set forth in any other part of this PWS.

5.10 Security

The contractor shall comply with applicable program security requirements. This effort requires contractor security to the SECRET/CNWDI level with access to NATO information. Contractors will handle, mark, and disseminate UCNI information in accordance with 32 CFR Part 223. 32

CFR 223.2 details the applicability of this federal regulation to contractors and consultants of the Department of Defense.

Contractor employees shall be able to obtain adequate security clearances prior to performing services. The Contract Security Classification Specification (DD Form 254) will encompass all security requirements. All contractor employees located on military installations shall also comply with Operations Security (OPSEC) requirements as set forth in DoD Directive 5205.02E, Operations Security Program, AFI 10-701, Operations Security, DoD directive 5230.25, Withholding of Unclassified Technical Data from Public Disclosure, and the International Traffic in Arms Regulation (ITAR). In accordance with DoD 5200.2-R, Personnel Security Program (Jan 87), DoD military, civilian, consultants, and contractor personnel using unclassified automated information systems, including e-mail, shall have at a minimum, a completed favorable National Agency Check Plus Written Inquiries (NACI). The contractor may be required to have all employees, prime and subcontracted, sign a non-disclosure agreement (NDA) prior to obtaining access to DoD or Air Force data. The original NDAs shall be submitted to the CO.

The types of Personnel Security Investigations (PSI) required for the contractor vary in scope of investigative effort depending upon requirements of the Government and/or conditions of the contract. In cases where access to systems is as a condition of the contract/task order, application/cost for the appropriate PSI shall be the responsibility of the contractor. In such instances, the contractor shall diligently pursue obtaining the appropriate PSI for its employees prior to assigning them to work any active task order.

5.10.1 Transmission of Classified Material

The contractor shall transmit and deliver any classified material/reports IAW the National Industrial Security Program Operating Manual (DoD 5220.22-M).

5.10.2 Protection of System Data

The contractor shall protect system design related documents and operational data whether in written form or in electronic form in accordance with all applicable policies and procedures for such data, including DOD Regulations 5400.7-R and 5200.1-R to include latest changes, and applicable service/agency/ combatant command policies and procedures.

5.10.3 System and Network Authorization Access Requests

For Contractor personnel who require access to DoD, DISA, or Air Force computing equipment or networks, the Contractor shall have the employee, prime or subcontracted, sign and submit a System Authorization Access Report (SAAR), DD Form 2875.

5.11 Training

Contractor personnel are required to possess the skills necessary to support their company’s minimum requirements of the labor category under which they are performing. Training necessary to meet minimum requirements will not be paid for by the Government or charged to the contract.

5.11.1 Government-Provided Training

The contractor’s employees may participate in other Government provided training, on a non-discriminatory basis as among contractors, under the following circumstances:

a. The contractor employees’ participation is on a space-available basis,

b. The contractor employees’ participation does not negatively impact performance of this task order, and

c. The Government incurs no additional cost in providing the training due to the contractor employees’ participation

5.11.2 Contracting Officer Representative Training

The Government requires COR training from the contractor at the beginning of the period of performance, and whenever COR personnel change, for carrying out emergency functions such as, but not limited to, globally denying access to the NMC2 environment in the case of a CMI when that CMI occurs outside of contractor business hours.

5.12 Software Support and Data Rights

The contractor shall fully support all COTS software provided to support integrated solutions in this contract. The contractor shall be able to utilize and support all software revisions. The Government’s data rights with regards to module coding within the NMC2 environment are specified in Defense Federal Acquisition and Regulation Supplement (DFARS) Clause 252.227-7015, Technical Data Commercial Items.

5.13 Continuation of Essential Contractor Services During Crisis Declared by the President of the United States, the Secretary of Defense, or Overseas Combatant Commander

The Requiring Activity has determined that this requirement is Mission Essential (M-E) in accordance with DoDI 1100.22.

The performance of these services is considered mission essential during time of crisis. Should a crisis be declared by the Secretary of Defense, the CO or COR will verbally advise the contractor of revised requirements, followed by written direction. When a crisis is declared, the operation of the NMC2 is considered a critical service during a crisis; other services relating to development, refinement, and creation of applications, reports, workflows, and similar functions are not considered essential functions. The contractor shall continue providing service in this capacity to AFGSC until the crisis is over. The contractor shall ensure enough skilled personnel are available during a crisis for any operational emergency. A crisis management plan shall be submitted IAW A-TE-3, A04, which states that the Contractor shall Submit an essential personnel list within 10 days after the contract start date. The list shall contain the employee’s name, address, home phone number, cell phone number (or beeper number), DOD ID number, security clearance, and duty title. This list shall be updated annually or as changes occur.

5.14 Associate Contractors

The contractor performing service under this PWS shall interface with associate contractors as may be necessary for performance. The contractor may be required to negotiate a Non-Disclosure Agreement (NDA) to facilitate the free and open exchange of information with other contractors.

5.15 Use of Non-Compete Clause

The contractor shall not limit the employment of employees by another contractor beyond the period of performance identified in contract (to include exercised Option Periods) for which employees provide services

5.16 Contractor Full-Time Equivalent Reporting

IAW the implementation of the FY 11 NDAA Section 8101, Contractor Inventory, the contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for NMC2 data management service via a secure data collection site. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

Reporting inputs shall be for the labor executed during the period of performance for each government Fiscal Year (FY), which runs 1 October through 30 September. While inputs may be reported at any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the CMRA help desk.

6. SERVICES SUMMARY (SS)

The contractor’s performance will be assessed monthly by a process that measures success towards achieving defined performance objectives. The Services Summary will be in accordance with DAFI 63-101, Integrated Life Cycle Management, DAFI 63-138, Acquisition of Services, DAFI 10-601, Operational Capability Requirements Documentation and Validation and FAR Subpart 37.6, Performance-Based Acquisition.

SS No.

PERFORMANCE

OBJECTIVE

PWS

REFERENCE

PERFORMANCE THRESHOLD

SS-1

Schedule Effectiveness – Milestones and tasks are delivered on or before original schedule dates.

3.1 – 3.1.4 Milestones/tasks are completed IAW original baseline dates 95% of the time.

SS-2

CDRL Timeliness –

CDRLs submitted to the Government for review are delivered as originally scheduled.

3.1 – 3.1.4 CDRLs delivered on time.

SS-3

CDRL Accuracy

CDRLs do not require content revisions.

3.1 – 3.1.4 Submissions are considered accurate if

Government revisions are editorial only. Content revisions result in an inaccurate rating.

SS-4

User Management – User and group permission requests are completed within timeframes annotated

3.1.2

100% of user administration requests completed within 3 business days of contractor notification, whether notified by NMC2 request form, email, or telephone

SS-5

Functionality/Site Creation

Contractor develops functionality and applications required by users

3.1.3

100% completion of customer-requested intelligence tools/dashboards/applications, as prioritized and approved by COR, to the timeframe agreed upon between

COR and the contractor.

SS-6

Contractor Employee

Qualifications 3.3

All contractor personnel shall possess appropriate knowledge and experience for the technologies required.

6.1 Quality Control

The Contractor shall develop and maintain a quality control program acceptable to the Government covering the services under this contract within 30 days after contract award. Complete records of all inspection work performed by the Contractor shall be maintained and made available to the Government during contract performance and for as long afterwards as the contract requires. The contractor shall utilize its own internal quality control processes in the performance of this contract.

In order to supplement the contractor’s quality control program, government personnel will verify contractor compliance with performance requirements.

No later than 90 calendar days from contract award, contractor shall integrate existing and emerging processes with an AFGSC electronic staffing solution to effectively create, coordinate, submit, approve and archive all applicable AFGSC staff actions. Solution must be documented and be flexible and tailored to account for staffing process variances that are dependent on the wide array of staff action categories. Keys to accomplishment must include, at a minimum, flexible and dynamic workflows, integration of existing automated orders generation capability, common templates, functional look and feel, and ease of navigation. Solution must be able to sustain and support the current NMC3 hosting environment, be flexible to utilize active users or NMC2 users and be scalable to allow non-domain users permissions to use the tool.

6.2 Quality Assurance

The Government will continuously monitor and evaluate the contractor's performance under this contract. The COR will evaluate the contractor's performance through intermittent inspections of the contractor's quality control program, contract surveillance and receipt of validated complaints from contract customers. The Government will record all routine surveillance observations using the Performance Assessment Report (PAR).