IDOS-IT PWS Full V1.docx
DOCX document 168 KB Posted
- Solicitation number
- FA8204-26-R-NIIT
About this file
This Performance Work Statement (PWS) details comprehensive Information Technology (IT) support services for the Air Force Nuclear Weapons Center's (AFNWC) Intercontinental Ballistic Missile (ICBM) Directorate and Air Force Global Strike Command (AFGSC). The contract encompasses IT service desk support, documentation and training services, project management, software license management, equipment custodial services, audio-visual support, hardware procurement, data storage and transfer, cybersecurity, system administration, and configuration lifecycle management across multiple ICBM system divisions including Minuteman III Systems, Sentinel Systems, and ICBM Futures.
Key performance requirements include maintaining consolidated IT service support, developing documentation and training materials, managing IT projects, tracking software licenses, managing IT asset lifecycles, providing technical support, ensuring cybersecurity, administering systems, and managing configuration processes. The contract requires strict security protocols, with personnel potentially needing access to classified information including Special Access Program (SAP), Sensitive Compartmented Information (SCI), and collateral information up to Top Secret level. The PWS emphasizes comprehensive support for the ICBM enterprise, focusing on maintaining operational readiness, reliability, and technical integration of critical nuclear weapon system infrastructure.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| IDOS-IT RFI.docx | DOCX document | |
| LCATS and LEVELS.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
IDOS-IT PWS
PERFORMANCE WORK STATEMENT (PWS)
FOR
INTERCONTINENTAL BALLISTIC MISSILE (ICBM) DEVELOPMENT, OPERATIONS, AND SUSTAINMENT (IDOS) Information Technology (IT) Services
In Support Of
AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)
Program Executive Office for ICBM 15 Dec 2025
| 1. Introduction | 6 | |
| 1.1 | Directorate and Key Partner | 6 |
| 1.2 | Program Overview | 6 |
| 1.3 | Purpose | 7 |
| 2. Scope | 8 | |
| 2.1. General Scope and Authority | 8 | |
| 3. Performance Requirements | 9 | |
| 3.1 Consolidated IT Service Desk Support | 9 | |
| 3.1.2. Documentation and Training Services | 9 | |
| 3.1.3. IT Project Management Services | 10 | |
| 3.1.4. Unit Software License Management | 10 | |
| 3.1.5. Equipment Custodial | 11 | |
| 3.1.6. Audio-Visual (AV) Support Services | 11 | |
| 3.1.7. Hardware Procurement | 12 | |
| 3.1.8. Data Storage and Transfer | 12 | |
| 3.2 Additional Requirements | 13 | |
| 3.2.1 Cybersecurity | 13 | |
| 3.2.2 System Administration | 13 | |
| 3.2.3 Configuration and Life Cycle Management | 14 | |
| 4. General Requirements | 14 | |
| 4.1. Terms and Definitions | 14 | |
| 4.2. Teleworking | 17 | |
| 4.3. Non-Personal Services | 17 | |
| 4.4. Inherently Governmental Functions | 17 | |
| 4.5. Hours of Operation | 17 | |
| 4.6. Holidays and Observances | 18 | |
| 4.7. Professional Conduct | 18 | |
| 4.8. Business Relations | 19 | |
| 4.9. Ethics | 20 | |
| 4.10. Organizational Conflicts of Interest (OCIs) | 20 | |
| 4.11. Mission Essential Services | 21 | |
| 4.12. Travel/Temporary Duty (TDY) | 21 | |
| 4.13. Government Vehicle Use | 22 | |
| 5. Contract Management | 22 | |
| 5.2. Organizational Structure and Key Personnel | 22 | |
| 5.3. Subcontract Management | 23 | |
| 5.4. Surge Support | 23 | |
| 5.5. Staffing | 23 | |
| 5.6. Labor Categories Description | 23 | |
| 5.7. Labor Quantity Workbook | 24 | |
| 5.8. Non-Disclosure Agreements (NDAs) | 24 | |
| 5.9. Associate Contractor Agreements (ACAs) | 24 | |
| 5.10. Other Contracted Support | 25 | |
| 6. Deliverables and Reporting Requirements | 25 | |
| 6.1. Monthly Status Reporting | 25 | |
| 6.2. Quarterly Progress Reviews | 26 | |
| 6.3. Financial Reporting | 26 | |
| 6.4. Task Monitoring and Application Tracking | 27 | |
| 6.5. Labor Hour Tracking | 27 | |
| 6.6. Records Management | 28 | |
| 6.7. Contractor Training Requirements | 28 | |
| 6.8. Access to Contractor Facilities | 28 | |
| 6.9. Quality Assurance | 28 | |
| 6.10. Rehabilitation Act Compliance (Section 508) | 29 | |
| 7. Data Rights | 29 | |
| 8. Security | 30 | |
| 8.1. Security Requirement | 30 | |
| 8.2. DD Form 254, Contract Security Classification Specification | 30 | |
| 8.3. Data Security and Controlled Unclassified Information (CUI) Handling | 30 | |
| 8.4. Scientific and Technical Information (STINFO) Marking | 30 | |
| 8.5. Personnel Security Clearances and Access | 31 | |
| 8.6. Collateral Access: | 31 | |
| 8.7. Special Access Program (SAP) Access: | 31 | |
| 8.8. Sensitive Compartmented Information (SCI) Access | 32 | |
| 8.9. Foreign Government Information (FGI) | 32 | |
| 8.10. Security Incident Reporting | 32 | |
| 8.11. Security Classification Guides (SCGs) | 32 | |
| 8.12. JADE Access | 32 | |
| 8.13. Computer Security Requirements | 32 | |
| 8.14. Operations Security (OPSEC) | 33 | |
| 8.15. Common Access Card (CAC) | 33 | |
| 8.16. Base or Area Badges and Access to Facilities | 34 | |
| 9. Government Facilities | 34 | |
| 10. Installation Requirements | 34 | |
| 11. Safety | 37 | |
| 12. Government Furnished Property, Equipment, Materials and Information | 37 | |
| 12.1. GFP Management | 37 | |
| 12.2. GFP Transition - Phase-In | 37 | |
| 12.3. Nuclear Weapons Related Material (NWRM) | 38 | |
| 12.4. Use of Personal Equipment | 38 | |
| 12.5. GFE in Alternate Work Sites | 38 | |
| 12.6. Protection from Loss | 38 | |
| 12.7. Safeguarding Government Property | 38 | |
| 13. Transition Planning | 38 | |
| 13.1. Transition Onboarding Plan | 38 | |
| 13.1.1. Knowledge Transfer | 39 | |
| 13.1.2. Data Access and Migration | 39 | |
| 13.1.3. Personnel Integration | 39 | |
| 13.1.4. System Access and Security | 39 | |
| 13.1.5. Training | 39 | |
| 13.1.6. Deliverable Schedule | 39 | |
| 13.1.7. Compliance with GTRD | 39 | |
| 13.2. Transition Off-Ramp Plan | 39 | |
| 13.2.1. Data Delivery | 40 | |
| 13.2.2. Knowledge Transfer | 40 | |
| 13.2.3. System Decommissioning (if applicable) | 40 | |
| 13.2.4. Personnel Transition | 40 | |
| 13.2.5. Intellectual Property | 40 | |
| 13.2.6. Security | 40 | |
| 13.2.7. Deliverable Schedule | 40 | |
| 13.2.8. Compliance with GTRD | 40 |
1. Introduction
1.1 Directorate and Key Partner
The Air Force Nuclear Weapons Center (AFNWC) Intercontinental Ballistic Missile (ICBM) Directorate (NI) is responsible for the inception-to-retirement integrated life cycle management of the nation's land-based ICBM force. This Performance Work Statement (PWS) establishes the requirements for comprehensive Information Technology (IT) and Communications Security (COMSEC) support services to the directorate and its primary operational partner, Air Force Global Strike Command (AFGSC). These services provide essential support for the reliable, secure, and effective operation of the ICBM force
1.2 Program Overview
1.2.1. The ICBM Directorate consists of multiple divisions, each with a distinct mission focus. This contract will provide IT support across these organizations as required. The primary divisions and their missions are summarized below:
| Organization |
| Full Name |
| Primary Mission Focus |
| NI |
| ICBM Directorate |
| Provides overall directorate leadership and executes enterprise-wide strategic tasks through front-office entities like the Director's Action Group (DAG). |
| NIM |
| Minuteman III (MMIII) Systems Division |
| Ensures the continued operational readiness, availability, and reliability of the Minuteman III weapon system through integrated sustainment and modernization until its end-of-life. |
| NIX |
| Sentinel Systems Division |
| Leading the total system recapitalization of the MMIII ICBM, including the acquisition and deployment of new missile, command & launch, and infrastructure systems. |
| NIY |
| ICBM Futures Division |
| Guides future technology development and integration to proactively address emerging threats and transition new capabilities to programs of record. |
1.2.2. The Directorate also includes specialized support divisions that provide functional expertise across the enterprise, including but not limited to:
1.2.2.1. NIE (Enterprise Engineering Division): Serves as the central technical authority, managing enterprise-wide digital engineering, specialty engineering, and common technical standards.
1.2.2.2. NIT (Test and Support Division): Provides enterprise-wide Test & Evaluation (T&E) expertise, manages test infrastructure, and leads integration with all DoD test agencies.
1.2.2.3. NIZ (Warhead and Logistics Division): Manages the sustainment and development of ICBM nuclear warheads, leading integration efforts between the Department of Defense (DoD) and the Department of Energy (DOE) to ensure warhead and missile compatibility.
1.2.3. Key Operational Stakeholder
In addition to the internal directorate divisions, this PWS may require the contractor to provide direct and indirect IT support to the primary operational user of the ICBM weapon system:
| Organization |
| Full Name |
| Primary Mission Focus |
| AFGSC |
| Air Force Global Strike Command |
| Serves as the operational user and maintainer of the nation's land-based ICBM force. Responsible for organizing, training, and equipping forces to conduct global strike operations. |
1.3 Purpose
The purpose of this PWS is to acquire comprehensive IT and COMSEC support services that enable the successful operation, sustainment, and security of the ICBM enterprise The Contractor shall utilize only government-owned networks for the performance of authorized government work. The Government shall determine and direct the specific tasks, projects, or activities that are to be conducted on government-owned networks, and the Contractor shall adhere to these directions. Any use of government networks for non-governmental purposes, or for any activity not explicitly authorized by the Government, is strictly prohibited. The Contractor is responsible for ensuring that all personnel accessing government networks are aware of and comply with this restriction.
The Contractor acknowledges that all requirements and specifications outlined in this Performance Work Statement (PWS)– apply to any and all networks, systems, and tasks as directed by the Government. The Government reserves the right to assign, add, or remove networks, systems, and tasks within the scope of this PWS, and the Contractor shall provide services accordingly. The Contractor's responsibilities extend to all IT-related functions, activities, and support services as required by the Government, even if not explicitly detailed within a specific section of this PWS.
For the purposes of this Performance Work Statement (PWS), performance terms such as 'excellent,' 'timely,' 'efficient,' 'prompt,' 'effective,' and other similar qualitative descriptors shall be quantitatively defined within individual Service Level Agreements (SLAs) for each relevant process. These SLAs will provide specific, measurable, achievable, relevant, and time-bound (SMART) targets for performance, ensuring clear expectations and objective evaluation criteria for all contracted services. The SLAs will be incorporated as an integral part of this PWS and will be subject to regular review and adjustment as needed to meet evolving requirements and optimize service delivery
2. Scope
2.1. General Scope and Authority
This Performance Work Statement (PWS) establishes the requirements for a contractor to provide comprehensive IT support services to the ICBM Systems Directorate (ICBMSD) and Air Force Global Strike Command (AFGSC). All work shall be performed in coordination and cooperation with pertinent overseeing Government personnel. The contractor provides comprehensive IT support across various domains, including service desk, documentation, project management, software licensing, hardware lifecycle, AV, procurement, data storage, and security, ensuring efficient operations, compliance, and continuous improvement. This support encompasses both proactive and reactive measures to maintain systems, protect data, and support user needs throughout the IT lifecycle.
2.1.1 Consolidated IT Service Desk Support: Establishes a central point of contact for all IT issues, focusing on efficient incident resolution, service request fulfillment, knowledge base management, customer service, and performance reporting.
2.1.2 Documentation and Training Services: Focuses on developing and maintaining high-quality, accessible documentation and training materials for both users and IT staff, continuously improving based on feedback and metrics.
2.1.3 IT Project Management Services: Ensures successful planning, execution, and closure of IT projects, adhering to budget, schedule, and quality standards, with alignment to government IT strategy.
2.1.4 Unit Software License Management: Manages software assets, ensuring compliance with licensing agreements, optimizing utilization, and minimizing risks of violations.
2.1.5 Equipment Custodial: Manages the physical lifecycle of IT assets, maintaining accountability, security, and efficient utilization.
2.1.6 Audio-Visual (AV) Support Services: Provides reliable operation and maintenance of AV equipment and systems, offering timely troubleshooting, maintenance, and user support.
2.1.7 Hardware Procurement: Manages the hardware procurement process, ensuring that the government has all necessary information for informed and compliant purchasing decisions.
2.1.8 Data Storage and Transfer: Ensures data availability, integrity, and confidentiality while optimizing storage utilization, performance, and secure data transfer.
2.1.9 Cybersecurity: Provides proactive and reactive measures to protect information and maintain a strong security posture, including risk assessments, incident response, training, and security architecture design.
2.1.10 System Administration: Provides proactive and reactive services to maintain system availability, optimize performance, and ensure compliance with security policies, including server maintenance, performance tuning, and security management.
2.1.11 Configuration and Life Cycle Management: Manages the installation process to maintain standardized configurations, minimize security vulnerabilities, and optimize item performance throughout their lifecycle.
3. Performance Requirements
3.1 Consolidated IT Service Desk Support
The contractor shall provide comprehensive and integrated IT service desk support, ensuring effective resolution of user issues and efficient fulfillment of service requests. The Contractor shall execute these tasks using qualified IT support personnel to establish, manage, and mature the user support model, ensuring IT services are effectively delivered and sustained throughout their entire lifecycle, meeting all user support requirements from initial deployment through end-of-life. The IT Service Desk shall serve as the single point of contact for all IT-related incidents, service requests, and inquiries, ensuring minimal disruption to business operations and maximizing user productivity.
3.1.1.1. The contractor shall manage IT incidents, from initial reporting to resolution or escalation, logging all actions and utilizing a ticketing system, while providing timely status updates to users.
3.1.1.2. The contractor shall manage service requests, fulfilling standard requests efficiently and escalating non-standard requests as needed, while maintaining a service catalog.
3.1.1.3. The contractor shall create, maintain, and utilize a comprehensive knowledge base to improve incident resolution and service request fulfillment efficiency, and contribute to its continuous improvement.
3.1.1.4. The contractor shall deliver excellent customer service in all interactions, ensuring a positive and professional experience for all users.
3.1.1.5. The contractor shall generate regular performance reports, identify trends, and participate in training and IT projects to proactively improve IT service delivery.
3.1.2. Documentation and Training Services
The contractor shall develop, maintain, and deliver high-quality documentation and training materials that are accurate, current, and accessible.
3.1.2.1. The contractor shall develop and maintain clear, accurate, and up-to-date user and technical documentation, utilizing standardized templates and incorporating user feedback.
3.1.2.2. The contractor shall develop and deliver engaging and effective training programs for both users and IT staff, tailoring content to specific needs and employing diverse training methods.
3.1.2.3. The contractor shall establish and maintain a central, easily accessible, and government directed repository for all documentation and training materials, implementing version control and promoting self-service knowledge acquisition.
3.1.2.4. The contractor shall track training attendance and completion rates and solicit user feedback to assess the effectiveness of documentation and training efforts.
3.1.2.5. The contractor shall use feedback and key metrics to continuously improve documentation and training materials, staying current with industry trends and best practices.
3.1.3. IT Project Management Services
The contractor shall ensure the successful planning, execution, monitoring, and closure of IT projects on networks and systems as directed by the Government. The Contractor shall provide qualified Project Management Professionals (PMPs) or equivalent personnel who will manage projects to achieve defined objectives, within budget, on schedule, and to the required quality standards.
3.1.3.1. The contractor shall collaborate with stakeholders to define project scope, objectives, and deliverables, ensuring alignment with Government IT strategy and priorities.
3.1.3.2. The contractor shall develop comprehensive project management plans, including detailed scope, schedule, budget, resource allocation, risk management, and communication strategies.
3.1.3.3. The contractor shall manage project execution according to the project management plan, tracking progress, managing resources, and conducting regular status meetings to keep stakeholders informed.
3.1.3.4. The contractor shall proactively manage project risks and issues by identifying, assessing, and mitigating potential problems, and effectively resolving escalated issues.
3.1.3.5. The contractor shall ensure project success by completing all deliverables, conducting project closure meetings, documenting lessons learned, and adhering to all Government project management methodologies, regulations, and policies.
3.1.4. Unit Software License Management
The contractor shall ensure the proper management, accountability, and compliance of all software assets within assigned units of [Organization Name] on networks and systems as directed by the Government. The Contractor shall provide trained and qualified personnel to serve as USLMs, responsible for effectively managing the software lifecycle, optimizing software utilization, and minimizing the risk of software licensing violations.
3.1.4.1. The contractor shall Maintain a comprehensive software inventory, accurately documenting licenses and proof of purchase across all environments, and track software usage to identify optimization opportunities.
3.1.4.2. The contractor shall Securely manage and distribute license keys; proactively monitor deployments to prevent unauthorized installations and licensing violations.
3.1.4.3. The contractor shall Ensure software licensing compliance, adhering to license agreements and staying updated on software licensing regulations.
3.1.4.4. The contractor shall Support software audits and inventories; resolve licensing issues.
3.1.4.5. The contractor shall Manage software requests, ensuring required approvals and proper license allocation; track unit software acquisitions.
3.1.4.6. The contractor shall Dispose of software according to agreements and regulations.
3.1.4.5. The contractor shall Act as a liaison, communicating licensing policies and ensuring unit personnel understand their licensing responsibilities.
3.1.4.5. The contractor shall Fulfill software-related service requests across all environments.
3.1.4.5. The contractor shall Maintain accountability for assigned software assets and provide accurate, timely reports on software asset management and compliance.
3.1.5. Equipment Custodial
The contractor shall manage the physical lifecycle of IT assets, ensuring accountability, security, and efficient utilization.
3.1.5.1. The contractor shall maintain auditable records and ensure accountability for all physical IT assets throughout their lifecycle, from receipt to disposition, minimizing loss, theft, or damage.
3.1.5.2. The contractor shall manage the inventory of physical IT assets, conducting and documenting regular inventories, reconciling counts with records, resolving discrepancies, and providing reports to the Government.
3.1.5.3. The contractor shall manage the receipt, distribution, transfer, disposal, or donation of physical IT assets, ensuring proper documentation and compliance with procedures.
3.1.5.4. The contractor shall maintain an adequate supply of ready-to-deploy physical IT hardware, ensure assets are labeled, document hardware-related problem resolutions, and provide priority IT service as directed.
3.1.5.5. The contractor shall comply with all IT asset management policies and regulations, ensure proper out-processing procedures are followed, and be held responsible for negligence leading to lost or damaged assets.
3.1.6. Audio-Visual (AV) Support Services
The contractor's engineering staff ensure the reliable operation and maintenance of existing AV equipment and systems. The Contractor shall provide timely and effective troubleshooting, maintenance, and user support services to maximize the availability and usability of AV resources for meetings, presentations, training, and other events.
3.1.6.1. The contractor shall deliver respond to user requests for AV support in a timely manner; diagnose and troubleshoot AV equipment malfunctions; repair or replace faulty AV equipment components; escalate complex AV issues as needed, and document all activities in a ticketing system.
3.1.6.2. The contractor shall perform scheduled preventative maintenance on AV equipment; identify and address potential problems; maintain a maintenance schedule; and keep accurate maintenance records.
3.1.6.3. The contractor shall provide user support and training on AV equipment operation, create and maintain user documentation, respond to user questions, provide on-site support for events, and guide proper AV asset use.
3.1.6.4. The contractor shall monitor AV system performance to identify and resolve issues, optimize configurations, track usage, and maintain detailed asset information.
3.1.6.5. The contractor shall maintain an accurate inventory of AV equipment, track equipment movement, and recommend replacement of obsolete equipment.
3.1.6.6 The contractor shall coordinate with other IT and facilities teams to resolve AV issues and ensure proper installation and maintenance; and work with external vendors for repairs and upgrades.
3.1.7. Hardware Procurement
The contractor shall manage the preparation process, from requirements gathering to documentation completion, ensuring the Government has all necessary information to make informed and compliant purchasing decisions.
3.1.7.1. The contractor shall coordinate with stakeholders to elicit and document hardware requirements; validate those requirements; obtain necessary approvals; research hardware options; develop recommendations; prepare all order documentation; ensure documentation complies with policies; maintain accurate preparation activity records; generate preparation activity reports; and track estimated costs for proposed hardware purchases.
3.1.8. Data Storage and Transfer
The contractor shall ensure data availability, integrity, and confidentiality while optimizing storage utilization and performance, including efficient and secure data transfer capabilities on government-directed environments, and will maintain the storage as directed by the government.
3.1.8.1. The contractor shall maintain storage resources, optimizing capacity, ensuring sufficient bandwidth for data transfer, implement storage management policies, implement and maintain a data backup and recovery strategy ensuring secure storage, test procedures, implement and maintain a data archiving and retention strategy, implement and maintain robust security measures to protect data, monitor storage systems for security vulnerabilities, and comply with security regulations.
3.1.8.2. The contractor shall implement and enforce access control policies, encrypt sensitive data in transit and at rest, monitor storage performance and capacity utilization, generate reports on performance, security, and data transfer, and provide timely alerts of storage-related issues.
3.1.8.3 plan and execute data migrations, minimizing downtime and data loss, with optimized data transfer speeds and data integrity
3.2 Additional Requirements
3.2.1 Cybersecurity
The contractor shall provide proactive and reactive cybersecurity measures to ensure the confidentiality, integrity, and availability of information, and to maintain a strong security posture in accordance with applicable regulations and policies.
3.2.1.1. The contractor shall conduct risk and vulnerability assessments, including scanning and penetration testing, and prioritize vulnerabilities based on risk.
3.2.1.2. The contractor shall prepare and deliver detailed test documentation, including Data Requirements, Detailed Test Plans, and Test Procedures for each test event.
3.2.1.3. The contractor shall monitor security logs and alerts, investigate incidents, and contain, eradicate, and recover from security incidents, providing 24/7 support.
3.2.1.4. The contractor shall develop and maintain incident response plans, security configuration standards, and security policies and procedures.
3.2.1.5. The contractor shall develop and deliver security awareness training, conduct phishing simulations, and track training completion rates.
3.2.1.6. The contractor shall design and implement secure IT architectures, evaluate new technologies, assess their security implications, monitor systems for configuration drift, automate configuration management, ensure compliance, conduct security audits, generate reports, and provide support for regulatory audits.
3.2.2 System Administration
The contractor shall provide proactive and reactive system administration services to maintain system availability, optimize performance, and ensure compliance with security policies
3.2.2.1. The contractor shall maintain core system infrastructure, including installing, configuring, maintaining, and monitoring servers and operating systems, and managing server resources.
3.2.2.2. The contractor shall proactively ensure system performance and stability by tuning systems, troubleshooting incidents, and implementing security best practices.
3.2.2.3. The contractor shall secure systems and data by implementing and maintaining security controls, managing user accounts, monitoring for vulnerabilities, and responding to security incidents.
3.2.2.4. The contractor shall improve system efficiency and compliance by automating routine tasks, managing patch deployments, and adhering to government policies and regulations.
3.2.3 Configuration and Life Cycle Management
The contractor shall manage the installation process to maintain standardized configurations, minimize security vulnerabilities, and optimize item performance throughout their lifecycle on the designated networks and systems.
3.2.3.1. The contractor shall install standardized configurations on all new and existing items, automate the configuration installation process whenever possible to minimize manual effort and reduce the risk of errors, document the configuration installation process and provide training to IT staff.
3.2.3.2. The contractor shall deploy configuration updates and patches in a timely manner to address security vulnerabilities and improve performance, test updates and patches in a controlled environment before deploying them to production items, track the status of updates and patches and report on compliance.
3.2.3.3. The contractor shall monitor items to ensure compliance with standardized configurations and security policies, identify and remediate configuration drift, generate regular reports on configuration compliance and security posture, report any security breaches or incidents immediately.
3.2.3.4. The contractor shall support the lifecycle processes, ensuring that they are properly configured and integrated into the organization's IT environment, support the end-of-life processes, ensuring that data is securely handled and that items are properly disposed of, maintain an accurate inventory of all items and their configurations.
4. General Requirements
4.1. Terms and Definitions
This section provides definitions for acronyms, abbreviations, and terms used throughout this Performance Work Statement (PWS) to ensure a common understanding between the Government and the Contractor.
| Acronym / Term |
| Definition |
| AFGSC |
| Air Force Global Strike Command; the operational user of the ICBM weapon system. |
| AFNWC |
| Air Force Nuclear Weapons Center. |
| CDD |
| Capability Development Document. |
| CDRL |
| Contract Data Requirements List; a list of authorized data requirements for a specific procurement. |
| CM |
| Configuration Management; the discipline of managing the technical baseline of the system. |
| CUI |
| Controlled Unclassified Information. |
| DAFI |
| Department of the Air Force Instruction. |
| DMSMS |
| Diminishing Manufacturing Sources and Material Shortages; a supply chain and obsolescence issue. |
| DoD |
| Department of Defense. |
| DOE |
| Department of Energy. |
| ECP |
| Engineering Change Proposal; a formal document used to propose a change to the system's baseline. |
| FMECA |
| Failure Modes, Effects, and Criticality Analysis; a reliability engineering analysis method. |
| FOC |
| Full Operating Capability; the state achieved when a system is fully deployed and operational. |
| ICBM |
| Intercontinental Ballistic Missile. |
| ICBMSD |
| Intercontinental Ballistic Missile Systems Directorate (also referred to as NI). |
| ICD |
| Interface Control Document; a document that specifies the detailed design of an interface. |
| ILSP |
| Integrated Logistics Support Plan; a key planning document for system sustainment. |
| IOC |
| Initial Operating Capability; the first attainment of the capability to effectively employ a system. |
| KPP |
| Key Performance Parameter; a critical system attribute that must be met. |
| KSA |
| Key System Attribute; a system attribute considered important but not as critical as a KPP. |
| LORA |
| Level of Repair Analysis; an analysis to determine the most cost-effective maintenance strategy. |
| LPO |
| Lead Project Office. |
| MBSE |
| Model-Based Systems Engineering; the practice of using digital models to support systems engineering. |
| MMIII |
| Minuteman III; the legacy ICBM weapon system. |
| NH&S |
| Nuclear Hardness & Survivability; the discipline of ensuring a system can withstand hostile environments. |
| PDR |
| Preliminary Design Review; a formal technical review. |
| CDR |
| Critical Design Review; a formal technical review. |
| PLM |
| Product Lifecycle Management; the process of managing the entire lifecycle of a product from inception. |
| PWS |
| Performance Work Statement; this document. |
| RF |
| Radio Frequency. |
| R&M |
| Reliability and Maintainability. |
| RMF |
| Risk Management Framework; the DoD process for managing cybersecurity risk. |
| RTVM |
| Requirements Traceability and Verification Matrix; a table linking requirements to their verification. |
| SE&I |
| Systems Engineering and Integration. |
| SEMP |
| Systems Engineering Management Plan; a key planning document for technical efforts. |
| SIPRNET |
| Secret Internet Protocol Router Network. |
| SPO |
| System Program Office. |
| STINFO |
| Scientific and Technical Information. |
| STPA |
| Systems-Theoretic Process Analysis; a modern hazard analysis technique. |
| TEMP |
| Test and Evaluation Master Plan; the overarching planning document for all T&E activities. |
| UAF |
| Unified Architecture Framework; a standard framework for architectural models. |
| WSER |
| Weapon System Effectiveness Report; a key deliverable from the T&E process. |
4.2. Teleworking
4.2.1. Telecommuting/telework is defined as authorization for an employee that works at the United States Government (USG) location, to work at an alternate location, i.e., at the employee’s home or Contractor location, either routinely or situationally. Contractor-designated location is defined as a contractor-identified place of performance for specific employees, i.e., not at the USG location.
4.2.2. Authorization for telework will be considered on a case-by-case basis.
4.2.3. Teleworking is not authorized for classified work. Authorized telework locations do not abrogate the Contractor’s requirement for complying with the protection of information IAW DoD and USAF regulations, Security and Protection of Information sections of this PWS, contract clauses or DD Form 254.
4.3. Non-Personal Services
4.3.1. The Government shall not supervise Contractor personnel. Supervision of employees in a non-personal services contract is the sole responsibility of the Contractor and establishes the employer-employee relationship it has with its employees. Supervision includes continuous employee management of recruitment, hiring, termination, compensation, benefits, career development, human resources management infrastructure, security clearance management, work location, contract assignment and evaluations of Contractor employees. Government personnel are authorized to regularly assign work tasks and provide guidance on the completion of work products or services and maintain the right to reject the finished product or results.
4.3.2. The Contractor shall manage its employees and guard against any actions that are of the nature of personal services or give the perception of personal services. If the Contractor believes that any actions constitute or are perceived to constitute personal services, or are outside the scope of this task order, the Contractor shall notify the IDOS CO or COR immediately.
4.3.3. See Section 8.1, Organizational Structure and Key Personnel, for more information.
4.4. Inherently Governmental Functions
4.4.1. The Contractor shall not perform any inherently governmental functions as defined by Federal Acquisition Regulation (FAR) Subpart 7.5. All program decisions shall be the sole responsibility of the Government.
4.4.2. The Contractor shall not counsel, mentor, make judgments and/or discretionary decisions or perform any other activities related to supervision of Government personnel.
4.4.3. If the Contractor believes that any actions constitute or are perceived to constitute inherently governmental functions, the Contractor shall notify the IDOS CO immediately.
4.5. Hours of Operation
Hours of operations at all locations are an eight-to-nine-hour shift reflected in a normal industry standard eight hours a day 40 hour a week schedule. Nine-hour shifts, i.e., Hill AFB, are reflected in the standard two-week period of “5/4/9” creating an 80-hour standard period (a five-day week and a four-day week at nine hours each day with every other Friday off with the working Friday being an eight-hour day equaling a two-week total of 80 hours). Nine-hour shifts shall be coordinated through the COR. All locations may have varying start times between 0600 - 1730. Core hours of work are from 0900 to 1500 daily. “Core” reflects a portion of any workers day that overlaps within that range. Employees are expected to be available during some portion of core hours. Regardless, this effort will not exceed a 40-hour work week without COR notification.
4.6. Holidays and Observances
4.6.1. The Contractor shall be aware of and account for the following holidays when scheduling personnel and planning work activities. The Government observes the following holidays:
| Holiday |
| Date |
| New Year's Day |
| 1 January* |
| Martin Luther King Jr.'s Birthday |
| Third Monday in January |
| President's Day |
| Third Monday in February |
| Memorial Day |
| Last Monday in May |
| Juneteenth |
| 19 June* |
| Independence Day |
| 4 July* |
| Labor Day |
| First Monday in September |
| Columbus Day |
| Second Monday in October |
| Veteran's Day |
| 11 November* |
| Thanksgiving Day |
| Fourth Thursday in November |
| Christmas Day |
| 25 December* |
* If the date falls on a weekend, the holiday will be observed on the closest weekday.
4.6.2. The Government may also observe any day designated by federal statute, executive order, or proclamation by the President of the United States. The Contractor will be notified of these additional observances as soon as the Government is aware.
4.6.3. Notwithstanding holidays and Government closures, the Contractor shall perform IAW the terms established in this task order. The Contractor is responsible for planning and managing its resources to ensure that required services are delivered despite these closures, unless otherwise directed by the IDOS CO in writing.
4.6.4. If the duty location is closed, no contractor services shall be provided unless authorized by the IDOS CO in writing. The Contractor shall be responsible for notifying its employees of installation closures. Contractor personnel shall be permitted access to Government facilities only if Government personnel are present.
4.7. Professional Conduct
4.7.1. Contractor personnel shall act as responsible agents and representatives of the ICBM Organization, the United States Air Force (AF), the DoD, and the Federal Government, IAW governing laws and regulations.
4.7.2. Contractor behavior shall be professional and reflect positively on the Government.
4.7.3. The Contractor shall present an unblemished appearance in regards to ethics, discretion, protection of information, etc.
4.7.4. The Contractor shall foster and maintain good working relationships with internal and external stakeholders.
4.7.5. The Contractor shall collaborate with internal and external stakeholders as needed to accomplish requirements and tasks.
4.7.6. The Contractor shall follow all applicable USAF policies, instructions, manuals, and guidelines with respect to usage of electronic mail and Internet. Every authorized user accessing IT that stores or processes Air Force information will operate the device within the guidelines provided in the annual cyber awareness training and any supplemental training provided. The Contractor shall report unusual behavior in accordance with the local communications focal point's standard operating procedures or appropriate help desk.
4.7.7. In addition to the above, the Contractor shall:
4.7.7.1. Ensure that all Contractor personnel receive training on ethics, security, and data privacy upon commencement of work under this contract and periodically thereafter, as directed by the Government.
4.7.7.2. Establish and maintain a system for reporting and investigating allegations of misconduct or unethical behavior by Contractor personnel.
4.7.7.3. Cooperate fully with Government investigations into any alleged misconduct or unethical behavior.
4.7.7.4. Take appropriate disciplinary action against Contractor personnel who violate the standards of professional conduct and ethics outlined in this section.
4.8. Business Relations
4.8.1. The Contractor shall successfully integrate and coordinate all activities needed to execute the requirements. The Contractor shall manage the timeliness, completeness, and quality of problem identification. The Contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of subcontractors. The Contractor shall seek to ensure customer satisfaction and professional and ethical behavior of all Contractor personnel.
4.8.2. In alignment with OMB Circular A-11's performance efficiency guidance and the DoD's commitment to operational efficiency and sustainability, the Contractor is expected to:
4.8.2.1. Identify and implement cost-saving measures throughout the performance of this contract. This includes, but is not limited to, process improvements, technological innovations, and optimization of resource utilization.
4.8.2.2. Propose alternative solutions or approaches that could result in reduced costs, improved performance, or enhanced efficiency without compromising quality or compliance with requirements.
4.8.2.3. Utilize best practices and industry standards to streamline operations and eliminate redundancies.
4.8.2.4. Leverage existing Government resources and infrastructure where feasible to minimize duplication and maximize efficiency.
4.8.2.5. Explore opportunities for shared services and collaborative partnerships to achieve economies of scale.
4.8.2.6. Implement sustainable practices that reduce environmental impact and contribute to long-term cost savings.
4.8.2.7. Regularly report on cost-saving initiatives implemented and their associated impact, as agreed upon with the Contracting Officer and/or Contracting Officer's Representative.
4.8.2.8. The Government will consider and evaluate all Contractor-proposed efficiency initiatives and, where appropriate, will work collaboratively with the Contractor to implement them. Approved cost-saving initiatives may be incorporated into contract modifications, as appropriate.
4.9. Ethics
The Contractor shall maintain the highest ethical standards and exercise impeccable discretion in all activities related to the ICBM mission. Given the sensitive nature of ICBM modernization, sustainment, and strategic nuclear deterrence, the Contractor's conduct must be beyond reproach. This includes strict adherence to all applicable regulations and guidelines regarding the protection of information, including but not limited to those governing electronic mail use (AFI 33-119) and internet use (AFI 33-129 AFOSISUP). The Contractor's actions will directly impact the perception and effectiveness of the ICBM Directorate; therefore, any ethical lapse will be unacceptable.
4.10. Organizational Conflicts of Interest (OCIs)
4.10.1. Contractor personnel performing work under this contract may receive, have access to, or participate in development of proprietary or Source Selection Information (SSI) (e.g. cost or pricing information, budget information or analyses, specifications or work statements, etc.), or perform evaluation services which may create a current or subsequent OCI as defined in FAR 9.5.
4.10.2. As such, this contract includes a specific, special OCI H-clause with restrictions on the contractor. The purpose of OCI restrictions is to assure the objectivity of all contractor recommendations to the Government and create a cooperative relationship for the integration of SSC and other contract efforts.
4.10.3. The Contractor shall notify the Government PCO immediately should they become aware that any access or participation may result in an actual, potential, or perceived OCI.
4.10.4. The Contractor shall promptly submit a plan to the PCO to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be accepted solely at the discretion of the Government PCO. In the event the PCO unilaterally determines that an OCI cannot be satisfactorily avoided or mitigated, the PCO may affect other remedies as deemed necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.
4.10.5. OCI restrictions apply to all team members (Primes, Subcontractors, Joint Venture Members, etc.).
4.11. Mission Essential Services
During crisis situations, some technical and engineering support services may be necessary to sustain mission essential services and travel. The contractor shall provide a written plan, to be incorporated into the contract, that ensures the continuation of these services during crisis situations.
4.12. Travel/Temporary Duty (TDY)
4.12.1. Travel Policies and Procedures
4.12.1.1. Contractor travel policies and procedures must adhere to best business practices in accordance with FAR 31.205-46 and the Federal Travel Regulation (FTR) as a guide regarding air fares, per diem, allowances, and reimbursement of travel expenses. First-class air travel is not authorized. The Government reserves the right to disallow unreasonable travel costs. All travel costs incurred must be in accordance with FAR 31.205-46.
4.12.1.2. The Contractor shall obtain written approval for travel requirements prior to costs being incurred, from the designated Government program/effort lead. The Government is under no obligation to reimburse the Contractor for any travel in which prior written approval has not been received.
4.12.1.3. At the Government’s request, the Contractor shall prepare and submit to the Contracting Officer Representative (COR) or Government designee, a Travel Approval Request (TAR) for Continental United States (US) (CONUS)/Outside the CONUS (OCONUS) travel prior to traveling.
4.12.1.4. A Letter of Authorization (LOA) is required in addition to a TAR for Contractor employees to travel on military aircraft.
4.12.2. Travel Locations
Travel locations specific to this effort may include, but are not limited to:
4.12.2.1. United States Air Force Bases: Hill, FE Warren, Kirtland, Malmstrom, Minot, Offutt, Peterson, Vandenberg, and Wright-Patterson.
4.12.2.2. Other Locations: Huntsville, AL; Joint Base San Antonio, TX; Laurel, MD; Livermore, CA; Los Angeles, CA; Promontory, UT; Washington, D.C.; and other locations as identified by the Government.
4.12.3. Travel Requirements
Travel and temporary duty (TDY) requirements specific to this contract include, but are not limited to: Working Groups, meetings, and Integrated Product Team (IPT), technical interchanges at contractor facilities and vicinity; technical meetings and conferences relevant to the program.
4.13. Government Vehicle Use
4.13.1. The contractor shall obtain and maintain forklift certification through Hill AFB's training courses and adhere to established procedures, with recertification completed IAW government-specified timelines and channels.
4.13.2. The contractor shall operate government-provided vehicles to transport equipment between facilities and attend meetings, IAW government-directed procedures and authorized usage guidelines.
4.13.3. The contractor shall ensure employees assigned to operate either government-owned/leased equipment in performance of their duties will be certified. Government-owned vehicles being provided is not a term of this contract, but a current capability provided which could be ended at any time due to vehicle non-availability or reduction in the government vehicle fleet.
4.13.4. The contractor shall assist with receiving government assets and unloading delivery trucks to receive new IT assets in the IT Depot. The contractor shall be able to operate a government vehicle for delivery and pickup of IT assets, as available. The contractor shall comply with operating and safety requirements to prevent damage to government property or injury to self or others. The contractor shall ensure assets are safely and securely stored and the warehouse remains a clean and safe environment through constant attention to order, refuse, recycling, and disposal, etc.
5. Contract Management
5.1. The following sections specify requirements for contract management and are to be applied to this Task Order (TO). The Contractor shall establish and maintain a robust contract management system with clear organizational lines of authority and responsibility to ensure effective and efficient performance of all requirements under this PWS. The Contractor must maintain continuity between the support operations at various performance locations and the Contractor's corporate offices.
5.2. Organizational Structure and Key Personnel
5.2.1. The Contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to the requirement. These organizational lines of authority must be broken down to a work package level and align with or have the ability to adjust with the government program's needs and organization should the government organizational structure change.
5.2.2. Within 90 days of contract award, the Contractor shall provide the Government with an organizational chart that clearly depicts the lines of authority and responsibility for all personnel involved in performing this contract down to the work package level.
5.2.3. The Contractor shall designate a single point of contact (POC), the Contract Manager, who shall be responsible for the overall management and performance of this contract. The Contract Manager shall have full authority to act on behalf of the Contractor in all matters related to this contract.
5.2.4. The Contractor shall also designate Technical Points of Contact (TPOCs) who will be the primary interface with Government technical personnel. These should be identified down to the work package level.
5.3. Subcontract Management
5.3.1. The Contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance on this requirement.
5.3.2. The contractor is responsible for ensuring all subcontractors adhere to the standards and requirements outlined in this document.
5.4. Surge Support
5.4.1. Surge support requirement is defined as short-term work to support mission activities in order to meet urgent customer needs. This type of support is typically needed because of schedule changes, system requirements updates, adverse test results, and other unforeseen or unplanned events. As such, surge support is usually needed “at the last minute”. Oftentimes, the need for surge support is satisfied by allowing Contractor personnel to simply work more than the normal forty hours per week.
5.4.2. The Contractor shall have the flexibility to adjust work schedules and staffing levels to accommodate surge requirements and ensure timely completion of mission-critical tasks. The Contractor shall coordinate with the Government Program Manager to communicate any significant changes in resource allocation.
5.5. Staffing
5.5.1. Contractor Personnel, Disciplines, and Specialties
5.5.1.1. The Contractor shall accomplish the assigned work by employing and utilizing qualified personnel with appropriate combinations of education, training, and experience directly relevant to the ICBM enterprise and specifically aligned with the required System Engineering and Integration (SEI) activities. The Contractor will ensure personnel skills are precisely matched to the work/task, minimizing both underutilization and over-qualification of resources. The labor categories, labor rates, and man-hours utilized in the performance of this TO will be the minimum necessary to accomplish the task efficiently and effectively while maintaining the highest standards of quality and compliance relevant to the ICBM mission. The Contractor shall provide the necessary resources and infrastructure to manage and administer this TO.
5.6. Labor Categories Description
5.6.1. A Labor Categories Description (LCD) is attached as Addendum 1 to this Task Order. The LCD details the minimum expected education, experience, and required certifications (if applicable) for each labor category utilized under this TO. The Contractor shall ensure that all personnel assigned to this Task Order meet or exceed the qualifications outlined in the LCD. Submissions of resumes for personnel that do not meet the minimum education and experience outlined in the LCD may be rejected.
5.7. Labor Quantity Workbook
5.7.1. A Labor Quantity Workbook (LQW) is attached as Addendum 2 to this Task Order. The LQW details the positions, areas within the program that are supported, clearance, and location the position is required for each labor position supporting the program. Adjustments of labor positions and amounts can be made through modifications to this addendum.
5.8. Non-Disclosure Agreements (NDAs)
5.8.1. The Contractor may need to access other companies' proprietary information in order to perform the requirements of this contract. Also, contractors and major subcontractors must effectively share information concerning the status of programs and technical issues in order to competently and conscientiously support the ICBM Organization. NDAs are required to facilitate this open communication and appropriately protect information. Violation of an NDA is considered a major security violation.
5.8.2. The Contractor shall obtain and maintain NDAs with all applicable Government, corporate, supplier, and sub-tier vendors with proprietary, restricted, competition sensitive, or any other restricted…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .