FINAL DRAFT HITSU III Performance Work Statement_V 1.1_21 May 2026.pdf
PDF 1 MB Posted
- Solicitation number
- PANERD25P0000_001596
About this file
This is a Performance Work Statement (PWS) for the High Performance Computing Modernization Program (HPCMP) Integrated Technical Services—Unrestricted III (HITS-U III) contract, issued by the U.S. Army Corps of Engineers, Engineer Research and Development Center (ERDC). The contract is structured as a five-year Indefinite Delivery Indefinite Quantity (IDIQ) base with task orders to be issued during the ordering period.
The PWS outlines comprehensive technical and operational support requirements across four Department of War (DoW) Supercomputing Resource Centers (DSRCs): Air Force Research Laboratory (AFRL) at Wright-Patterson AFB, Army Research Laboratory (ARL) at Aberdeen Proving Ground, ERDC at Vicksburg MS, and Navy DSRC at Stennis Space Center MS. Core responsibilities include 24/7/365 operations and monitoring of DSRC facilities and infrastructure; delivery of high-performance computing capabilities at unclassified, classified, and specialized levels; system administration, network engineering, database administration, and cybersecurity support across Defense Research and Engineering Network (DREN) and Secret DREN (SDREN) enclaves; and enterprise-level user support services including a Help Desk operating Monday-Friday, 8 a.m. to 8 p.m. Eastern Time, supporting approximately 2,500 active users. The contractor must establish key personnel including an Enterprise Program Manager, Deputy Program Manager, Site Leads for each DSRC, and Information System Security Officer (ISSO) Leads. All personnel require a minimum Secret security clearance; those in elevated-privilege or Above-Secret roles require Top Secret clearance. The contractor must achieve and maintain CMMC Level 2 (C3PAO) certification prior to award and throughout performance. Additional requirements encompass emerging technology support (AI/ML, quantum computing, hybrid cloud), enterprise software development and management, procurement support, facilities and engineering support, inventory management, change and configuration management, and continuity of operations planning. Monthly Assessment Reports are due by the 10th of each following month, documenting personnel staffing levels, financial expenditures, risk management, and technical performance.
View the file
Other files
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
Performance Work Statement
(PWS)
For High Performance Computing
Modernization Program (HPCMP) Integrated Technical Services –
Unrestricted III
(HITS-U III)
PANERD-25-0000 001596
USACE/ERDC
HPCMP
DATE: 21 May 2026
VERSION: FINAL DRAFT 1.1
Table of Contents
Table of Contents
1.0 General Information
1.1 Introduction
1.2 Background
1.3 Scope
1.4 Acronyms
1.5 General Requirements
1.5.1 Key Personnel
1.5.2 Administrative, Managerial and Supervisory
1.5.3 Security Investigation and Clearance
1.5.4 Cybersecurity Maturity Model Certification (CMMC)
1.5.5 Substitution or Addition of All Personnel
1.5.6 Qualifications
1.5.7 Meetings and Training:
1.5.8 Quality Control Program:
1.5.9 Quality Assurance
1.5.10 Contract Management
1.5.11 Contract/Task Meetings
1.5.12 Contract Review
1.5.13 Hours of Operations
1.5.14 Observance of Legal Holidays and Administrative Leave
1.5.15 Travel
1.5.16 Conservation of Utilities
1.5.17 Off-Site Space Requirements
1.5.18 Transition-In Period
1.5.19 Transition-Out Activities
1.5.20 Monthly Assessment Report
2.0 Period of Performance
3.0 General Scope of Requirements
3.1 Operate DSRCs
3.1.1 Operations Monitoring
3.1.2 Facilities and Engineering Support
3.1.3 Cybersecurity Support for DSRC Operations
3.1.4 System Administration
3.1.5 Network Engineering and Administration
3.1.6 Database Administration
3.1.7 Software Development
3.1.8 Maintenance Support
3.1.9 Inventory Management Support
3.1.10 Configuration and Change Management
3.1.11 Procurement Support
3.1.12 Continuity of Operations
3.1.13 Technical Project Support
3.2 Deliver Unclassified HPC Capabilities
3.2.1 Infrastructure Support for Unclassified HPC
3.2.2 Unclassified HPC System Installation and Integration
3.2.3 Application Management Support for Unclassified HPC
3.2.4 Cybersecurity Support for Unclassified HPC Systems
3.2.5 Unclassified HPC System Support
3.2.6 Additional Unclassified HPC Requirements
3.3 Deliver Classified HPC Capabilities
3.3.1 Infrastructure Support for Classified HPC
3.3.2 Classified HPC System Installation and Integration
3.3.3 Application Management Support for Classified HPC
3.3.4 Cybersecurity Support for Classified HPC Systems
3.3.5 Classified HPC System Support
3.3.6 Additional Classified HPC Requirements
3.4 Deliver Specialized HPC Capabilities
3.4.1 Infrastructure Support for Specialized HPC
3.4.2 Specialized HPC System Installation and Integration
3.4.3 Application Management Support for Specialized HPC
3.4.4 Cybersecurity Support for Specialized HPC Systems
3.4.5 Specialized HPC System Support
3.4.6 Additional Specialized HPC Requirements
3.4.7 Emerging Technologies
3.5 Assist HPC Users
3.5.1 Basic HPC Help Desk
3.5.2 DSRC Help Desk Liaisons
3.5.3 Higher Level User Support
3.5.4 HPC Application Management and Support
3.5.5 Advanced Visualization Application Development and Maintenance
3.5.6 Advanced Visualization Application Support
3.5.7 User Authentication Services
3.6 Cross-Centers/Enterprise Support
3.6.1 Contract Program and Performance Management
3.6.2 Project Management Support for Projects
3.6.3 Technology Assessment and Advancement Support
3.6.4 Enterprise Cybersecurity Support
3.6.5 Enterprise Outreach Services
3.6.6 Enterprise Software Development and Management
3.6.7 Cross-Centers/Enterprise Architecture Support
3.6.8 Cross-Centers/Enterprise Database Management
3.6.9 Cross-Centers/Enterprise Procurement Support
3.7 Overall Security
3.7.1 Risk Management
3.7.1.1 Cybersecurity Risk Management and Authorization
3.7.1.2 Plan of Action & Milestones (POA&M)
3.7.1.3 Supply Chain Risk Management (SCRM)
3.7.1.4 Cloud
3.7.2 Vulnerability Management
3.7.3 Information Security Continuous Monitoring (ISCM)
3.7.4 Endpoint Security (ESS)
3.7.5 Zero Trust and Comply-to-Connect
3.7.6 Incident Response
3.7.7 User Activity Monitoring (UAM)
3.7.8 Logical Security
3.7.9 Physical Security
3.7.10 Cybersecurity Personnel
3.7.10 Personnel Security and Clearance Requirements
3.7.11 Security Directives & Training
3A AFRL DSRC Annex
3B ARL DSRC Annex
3C ERDC DSRC Annex
3D Navy DSRC Annex
4.0 Quality Assurance
5.0 Deliverables
5.1 Method of Delivery
5.2 CDRL Reports/Plans
5.3 Inspection and Acceptance
6.0 Contract Administration
7.0 Past Performance Information
8.0 Government Furnished Equipment (GFE)
9.0 Reimbursable Costs
10.0 Privacy Act and PII Training
11.0 Personnel Security
12.0 Non-Personal Services
13.0 Contract Funding
14.0 Contract Administration Data
15.0 Antiterrorism (AT) and Operations Security (OPSEC)
Appendix A: Army Mandatory Procurement Process
1. Authority and Purpose
2. Mandatory Source Hierarchy
3. IT-Specific Operational Requirements (CHESS / SWEP)
4. Contractor Procurement Responsibilities (Revolutionary FAR Overhaul (RFO) Aligned)
5. Supply Chain Security & Foreign Sourcing Restrictions
6. Documentation and Invoicing
7. Expiration
Appendix B: Service Contract Reporting (SCR) Process
Appendix C: Engineering Manual 385 1-1 Safey Requirement
Appendix D: Contractor’s Release of Claims
1.0 General Information
1.1 Introduction
Work performed under this contract is for direct support to the Centers component of the Department of War (DoW) High Performance Computing Modernization Program (HPCMP) managed by the U.S. Army Corps of Engineers (USACE), Army Engineer Research and Development Center (ERDC), Vicksburg, MS. The Centers component provides funding, strategic direction, and operational guidance for five DoW Supercomputing Resource Centers (DSRCs) located throughout the country and represented by three military services (Air Force/Space Force, Army, and Navy). Although there are similarities between the DSRCs such as operations and supercomputing capabilities, they have unique processes and procedures due to their diverse customer user base environments. An enterprise approach under Cross-Centers is to generate efficiencies and innovations at two or more of the DSRCs in order to increase the ability for HPCMP to deliver a holistic customer user experience.
In addition, to the DSRCs, the HPCMP includes other components that that provide support to the Centers such as Resource Management (RM) and Computational Research & Engineering Acquisition Tools and Environments (CREATE). The objective of this contract is to maintain the enterprise perspective across the DSRCs while enabling each DSRC to sustain a certain level of autonomy to better serve the mission of the HPCMP and support any unique HPC customer requirements. The federated approach with geographically separated sites, a distributed workforce, and centralized oversight lends itself to an operational model where an overarching Cross-Centers team works with the local DSRC staff. The Cross-Centers team communicates with government staff executive agents and local DSRC staff (both Government and Contractor) on enterprise efforts.
1.2 Background
The DoW HPCMP mission is to provide DoW's scientists and engineers with the resources necessary to solve the most demanding compute-intensive and data-intensive problems through the strategic application of HPC, networking, and subject matter expertise. To accomplish this mission, the program established a number of components related to HPC hardware, application software, networking, resource management, security, and training. The Centers component is focused on operating the DSRCs with associated DoW-wide network connectivity, implementing and managing HPC software applications and support environments, and providing some basic assistance to end users (approximately 2,500 active users at this time). The fundamental mission of Centers then is to: operate the DSRCs, deliver HPC capabilities, and assist users. This mission often includes support to other HPCMP components, specifically in delivery of HPC and user assistance.
The Centers’ four DSRC names and locations are identified below (the fifth DSRC, the Maui High Performance Computing Center (MHPCC), is not within the scope of this contract):
• The Air Force Research Laboratory (AFRL) DSRC, Wright-Patterson Air
Force Base, OH
• The Army Research Laboratory (ARL) DSRC, Aberdeen Proving Ground, MD
• The U. S. Army Corps of Engineers, Engineer Research and Development
Center (ERDC) DSRC, Vicksburg, MS
• The Navy DSRC, Stennis Space Center, MS (operated under the
Commander, Naval Meteorology and Oceanography Command -
CNMOC)
Historically, prior to the establishment of the HPCMP in the mid-1990s, the DSRCs were owned by their respective service agencies vying for funding and supercomputing hours on their own using varied business models until the HPCMP unified the overall mission. The program was intended to take advantage of economies-of-scale by providing shared world-class supercomputing service levels to the DoW science & technology, and now the acquisition, communities. The challenges of keeping the DSRCs operating toward a common mission relate to nuances among the different military service organizations that host them, geographic separation, and enterprise versus local perspectives. Prior contracts leveraged a federated approach of allowing the DSRCs to operate somewhat autonomously while working together through an enterprise team for more efficiencies and effectiveness where appropriate.
1.3 Scope
The scope of this contracted effort includes: (1) essential DSRC infrastructure operations support, including system integration and operation, system administration, network administration, cybersecurity/information assurance, facilities support, database administration, maintenance management and execution for the facility, hardware, and software; (2) delivery of HPC capabilities at unclassified and classified levels including management of workflows and use cases; (3) enterprise and user support requirements, such as HPC Help Desk, data analysis and visualization, application software support, outreach, and support for other HPCMP components; (4) program and project management support, such as financial data and reports and process management, procurement support, and inventory support. Operations support includes all services required for DSRC routine operations, somewhat independent of HPC capabilities being delivered or customers (users of HPC systems) supported. The DSRCs operate 24 hours/day, 7 days/week, even during federal holidays. An enterprise HPC Help Desk provides support 5 days per week (Monday-Friday), extended business hours per day (nominally 0800-2000 Eastern Time to cover typical business hours across the continental US), excluding federal holidays, to over 5,000 HPC users and HPCMP staff members (approximately 2,500 considered active users), although the total number may increase during the performance period of this contract. Cybersecurity is a critical requirement on this contract, where Centers must perform continuous risk assessments and management, as well as sustain the approvals to operate.
This contract will provide services to support the operations and management of the four identified DSRCs (AFRL, ARL, ERDC, and Navy), as well as the Cross- Centers/Enterprise component. NOTE: The scope does not include operations support for the MHPCC DSRC but does include enterprise efforts that impact the MHPCC. This may include purchase of enterprise capability to be implemented at all DSRCs including MHPCC as well as transfer to MHPCC of documents, software, or other artifacts relevant to enterprise efforts developed on this contract. Requirements will be defined by individual task orders from the four supported DSRCs and Cross-Centers. In addition, task orders may include work requested and funded by HPCMP components other than Centers and/or requirements funded by customers of the HPCMP.
The definition of HPC and development of HPC technologies have been evolving since the inception of the HPCMP. Traditional HPC systems were known as “supercomputers” with associated massive numbers of compute processing units, high-speed interconnects, and high-performing file systems. Not long ago, a shift occurred toward more hybrid architectures consisting of different components for compute-intensive and data-intensive workloads with the introduction of general-purpose graphics processing units (GPGPUs). More recently, with the emphasis on artificial intelligence (AI) and machine learning (ML) use cases there has been a rise in the development of exclusive GPGPU-based systems. There has also been focused research on quantum computing, which is drastically different from conventional HPC, as well as hybrid cloud computing environments. The scope of this contract shall include support of HPC emerging technologies such as AI/ML, quantum computing, and cloud-supported architectures, as they become part of the HPCMP’s mission.
1.4 Acronyms
ACRONYMS DEFINITIONS
AD Associate Director AFRL Air Force Research Laboratory ARL Army Research Laboratory ATO Authority to Operate CDRL Contract Data Requirements List CNMOC Commander, Naval Meteorology and Oceanography
Command COTR Contracting Officer’s Technical Representative COR Contracting Officer’s Representative
CREATE Computational Research & Engineering Acquisition Tools and Environments
DAV-C Data Analysis and Visualization Center (DAV-C) DHPI Dedicated HPCMP Investment DoW Department of War DoD Department of Defense DPM Deputy Program Manager DREN Defense Research and Engineering Network DSRC DoW Supercomputing Resource Center ERDC Engineer Research Development Center ESMT Enterprise Software Management Team GFE Government Furnished Equipment GFP Government Furnished Property HPC High Performance Computing HPCMP High Performance Computing Modernization
Program HPCMPO High Performance Computing Modernization
Program Office ISSM Information System Security Manager ISSO Information System Security Officer IT Information Technology KO Contracting Officer MHPCC Maui High Performance Computing Center OEM Original Equipment Manufacturer PgMP Program Management Plan pIE Portal to the Information Environment PM Program or Project Manager PWS Performance Work Statement QAP Quality Assurance Program QASP Quality Assurance Surveillance Plan QCP Quality Control Plan RDT&E Research, Development, Test and Evaluation RM Resource Management RMF Risk Management Framework S&T Science and Technology SDREN Secret Defense Research and Engineering Network STIG Security Technology Implementation Guide SOPs Standard Operating Procedures T&E Test and Evaluation UAG User Advocacy Group
1.5 General Requirements
1.5.1 Key Personnel
The Government has determined that certain personnel are key to successful completion of the contract. These Key Personnel shall be designated in individual task orders and are subject to the provisions and clauses of the contract.
Resumes shall be submitted detailing the qualifications and experience of Key Personnel. The personnel specified below are essential to the work being performed under this contract. Prior to diverting any of the specified individuals to other projects, the Contractor shall notify the Contracting Officer (KO) or Contracting Officer’s Representative (COR) one month in advance and shall submit justification (including proposed substitutions) in sufficient detail to permit evaluation of the impact on the program. No diversion shall be made by the Contractor without the written consent of the KO. Key personnel are identified as follows:
Position PWS Reference Enterprise Program Manager Section 1.5.1 Enterprise Deputy Program Manager Section 1.5.1 Site Lead – AFRL DSRC Section 1.5.1 Site Lead – ARL DSRC Section 1.5.1 Site Lead – ERDC DSRC Section 1.5.1 Site Lead – Navy DSRC Section 1.5.1 Lead – Cross-Centers Section 1.5.1 ISSO Lead – AFRL DSRC Section 1.5.1, 3.7 ISSO Lead – ARL DSRC Section 1.5.1, 3.7 ISSO Lead – ERDC DSRC Section 1.5.1, 3.7 ISSO Lead – Navy DSRC Section 1.5.1, 3.7 ISSO Lead – Cross-Centers Section 1.5.1, 3.7
The Contractor shall provide a Program Manager (PM) and Deputy Program Manager (DPM) who shall be responsible for the performance of the work specified in accordance with (IAW) the terms and conditions of the resulting contract. The PM and DPM shall have full authority to act on behalf of the Contractor for all issues pertaining to contract administration for subject contract.
The PM and DPM will possess at least a bachelor’s degree in finance, business administration, computer science, computer engineering and/or information systems or other related discipline with a minimum of fifteen (15) years program management experience which includes a minimum of ten (10) years Information Technology (IT) organizational support management experience similar to the size and scope reflected in this Performance Work Statement (PWS). The experience can be Federal or private industry. For candidates with advanced degrees (e.g. Masters or PhD) or recognized industry certifications (e.g. PMI’s
PMP) may substitute for up to five (5) years’ experience. Qualifications of the PM and DPM are subject to Government review and concurrence. The PM and DPM shall be available during normal working hours to meet at the HPCMP office in person and/or via teleconference with Government personnel designated by the KO, HPCMP PM or COR within two (2) hours of notification.
Program Manager/Deputy Program Manager responsibilities include, but are not limited to:
• The PM/DPM will serve as the main point of contact for the KO, COR and, the HPCMP Associate Director (AD) of Centers for the overall contract status updates related to the enterprise and DSRC efforts in several areas, including cost management/avoidance, schedule estimation and tracking, contract performance management, risk management, requirements analysis, and quality assurance activities.
• Effectively communicate overall contract cost, schedule, and performance, and provide regular status updates to government leadership at regularly scheduled status meetings or other established methods of communication
• Provide program management for all subtasks areas to include Task Planning, Contractor Personnel Management, Task/Project Management and Cost Reporting, Schedule and Task Performance Oversight, Risk Management, Reporting and Contract Deliverables Management, Strategic Planning and Technical Recommendations across various components of the contract.
• Establish and sustain effective and pro-active, top-down and bottom-up, communications amongst contractor DSRC Site Leads, Cross-Centers Lead and other Government stakeholders.
• Consolidate inputs and provide feedback on all contractor projects included in the Integrated Master Schedule to ensure consistency and coordination of any dependencies that might affect other projects and potentially other DSRCs/Cross-Centers
• Maintain thorough understanding of the technical and performance requirements in the performance work statement.
Site/Cross-Centers Lead responsibilities include, but are not limited to:
• Site/Cross-Centers Lead will be primary point-of-contact to the Government DSRC Directors and DSRC Contracting Officer Technical Representatives (COTRs) for the tracking and reporting of the DSRC/Cross-Centers in several areas local to the DSRCs: cost management, schedule estimation and tracking, contract performance management, risk management, requirements analysis, and quality assurance activities.
• Oversight and management of contractor personnel local to the DSRCs to ensure proactive and effective communication related to project schedules, performance and risk analysis.
• Interfaces with the Site Lead ISSO to provide direction to the site contractor personnel in coordinating activities related to ensuring DSRC enclave’s security posture is maintained.
• Report on a weekly basis, or as needed, the technical and programmatic status of existing projects to local contractor and Government staff.
• Interact with contract PM, DPM, and/or corporate staff to facilitate DSRC/Cross-Centers specific work and ensure business office activities are accelerated in support of the DSRC/Cross-Centers to include procurements
• Maintain thorough understanding of the technical requirements to provide effective communication and recommendations to the DSRCs on risk analysis and technical/business efficiencies.
• Ensure configuration management of assets is maintained
The Information System Security Officer (ISSO) Lead responsibilities include, but are not limited to:
• Primary point-of-contact to the Government DSRC Information System
Security Manager (ISSM) in maintaining the DSRC enclave’s security posture assigned acceptable risk level.
• Interfaces with Site Lead to coordinate activities related to ensuring DSRC enclave’s security posture is maintained.
• Lead and direct other local ISSOs at the DSRCs to ensure continuity of the implementation of DoW and HPCMPO security regulations by coordination of activities by the established timeline from the ISSMs.
Further ISSO responsibilities are identified in Sections 3.7.10.1
1.5.2 Administrative, Managerial and Supervisory
The Contractor shall provide qualified personnel with administrative, financial, managerial, and supervisory capabilities to assure the effective performance of the contract.
1.5.3 Security Investigation and Clearance
The overall contract Contractor personnel shall be required to perform duties requiring a security investigation. At a minimum all contractor personnel are required to have and maintain a Secret clearance. The scope of the investigation required and the forms to be completed shall be IAW DOW personnel security directives and the HPCMP Personnel Security Investigative Memorandum. Most of the contractor personnel require IT Level I (critical sensitive information access) which requires a favorable Special Security Background Investigation (SSBI) (Tier 3/5 Personnel Security Investigation). The Contractor shall be responsible for the preparation and submittal of the required forms to the HPCMP facility Security Office. The Contractor personnel shall not be required, nor permitted to perform work prior to receipt of the required approval unless a temporary waiver is granted by the HPCMP AD for Security.
Contractor personnel performing duties that require system elevated privileges and/or any support of Above-Secret (e.g. Top Secret, Special Access Program – SAP) environments and systems are required to have Top Secret Clearances (Tier 5 Personnel Security Investigation).
The Contractor shall include in the Monthly Assessment Report (CDRL A004) a listing of the names of all contractor personnel who had access to an HPCMP facility, sensitive information and/or resources anytime during the reporting period. Copies shall be submitted to the Government Physical Security Point of Contact and the COR/KO. In furtherance of the above report, the Contractor shall also include any employment changes made during the reporting period to the KO/COR. Examples of such changes are terminations, new hires, and name changes.
1.5.4 Cybersecurity Maturity Model Certification (CMMC)
The Contractor shall comply with the Cybersecurity Maturity Model Certification (CMMC) program requirements as established by the DoW and IAW DFARS Clause 252.204-7021 (Cybersecurity Maturity Model Certification Requirements).
Required Certification Level: The Contractor shall achieve and maintain a CMMC Level 2 (C3PAO) Certification Assessment prior to contract award and throughout the life of the contract.
C3PAO Assessment Requirement: Because this contract requires the handling, processing, or storing of Controlled Unclassified Information (CUI), a Level 2 self-assessment is insufficient. The Contractor’s CMMC Level 2 assessment must be conducted and certified by an authorized CMMC Third-Party Assessment Organization (C3PAO).
Maintenance of Certification: The Contractor must maintain their CMMC Level 2 (C3PAO) Certification for the entire Period of Performance (PoP), including any exercised option periods. The Contractor shall ensure their active C3PAO assessment status is properly documented and verifiable within the DoW Supplier Performance Risk System (SPRS).
Flow-down Requirements: The Contractor shall mandate this requirement for all subcontractors or suppliers at all tiers who will process, store, or transmit CUI in the performance of this contract, ensuring they maintain a CMMC Level 2 (C3PAO) Certification Assessment.
1.5.5 Substitution or Addition of All Personnel
The Contractor shall fill vacancies within 28 calendar days after the vacancies occur. The Contractor shall maintain adequate staffing levels and report number of days vacant for all open positions on Monthly Assessment Report (CDRL A004) to ensure performance and delivery requirements are met.
1.5.6 Qualifications
The Contractor shall maintain a qualified staff at all times. Qualifications relate to education levels, training certifications, and security clearances, as identified throughout the PWS and within individual tasks. The Government restricts access or work to United States citizens only.
All cybersecurity risk management-related positions must have baseline certifications as designated in DoW/DoD Approved 8570 Baseline Certifications (DoW/DoD 8570.01M) or DoW/DoD 8140.03 foundational and resident qualification requirements prior to employment.
1.5.7 Meetings and Training:
Contractor personnel may be required to attend functions such as meetings, seminars, conferences, workshops, educational courses, and training unique to the HPCMP or directed/mandated by the HPCMP. The requirement to attend said functions will be identified in individual requests, approved by the COTR/COR/KO and may include activities such as attendance at a conference to give a technical presentation, attendance at meetings to obtain information necessary to perform tasks included in this PWS, or to present information obtained in performing a task related function. The Contractor, at their own expense, shall provide training of Contractor employees, unless the Government has given prior approval for training to meet special requirements that are particular to its environment and/or operation.
1.5.8 Quality Control Program:
The Contractor shall establish and maintain a complete Quality Control Plan (QCP) (CDRL A020) to ensure the services performed conform to stated requirements. The Contractor shall include an initial QCP with their proposal. The KO will notify the Contractor of acceptance or required modifications to the plan.
The Contractor shall make appropriate modifications at no additional cost to the Government and obtain acceptance of the QCP by the KO before the start of the initial performance period. The Contractor shall submit an updated QCP to the COR/KO for approval six (6) months after contract award, assuming the benefit of lessons learned over the initial six-month period. Thereafter, the plan shall be reviewed, updated, and submitted annually, or as changes occur, for acceptance by the Government. The QCP shall describe the inspection system for the requested services listed in the PWS and shall include the following:
• A description of the contractor's quality control system. The system shall cover all services, specify work to be inspected on either a scheduled or unscheduled basis, frequency, and describe how inspections are to be conducted.
• The name(s) and qualifications of individual(s) responsible for performing quality control inspections, and the extent of their authority.
• A description of the methods used to record the quality control inspection and corrective actions taken.
• A description of the methods used for identifying and preventing defects in the quality of service performed.
• The approach for filling vacancies in a timely manner, providing qualified personnel and documenting and maintaining an ongoing training program to ensure contractor employees acquire the knowledge and skills necessary for new/emerging technology, managing changes in workload requirements and providing timely and accurate invoices. The Contractor shall maintain a file of all scheduled and performed Quality Control inspections, inspection results, and dates and details of corrective actions.
The file shall be made available to the KO and COR upon request.
1.5.9 Quality Assurance
The Government’s quality assurance is not a substitute for Quality Control (QC) by the Contractor. All findings of unsatisfactory or non-performed work will be resolved IAW the Quality Assurance Surveillance Plan (QASP). Failure to agree as to what constitutes defective performance under these clauses shall be handled under the procedures of the disputes clause included in the resulting contract.
1.5.10 Contract Management
The Contractor shall submit a Program Management Plan (PgMP CDRL A010) to the KO and COR for approval within 30 calendar days after start of contract.
Thereafter, the plan shall be reviewed, updated, and submitted annually 30 days after the start of each task, and/or as changes occur, for acceptance by the Government.
1.5.11 Contract/Task Meetings
The Contractor PM and/or DPM shall be required to meet, at the discretion of the KO, with the KO and/or COR during the term of the contract. Meeting minutes shall be documented as designated by the KO. The Contractor may also request a meeting with the COR. The COR will coordinate any such meeting request through the KO.
1.5.12 Contract Review
Twice yearly contract review meetings may be coordinated by the Government to disseminate information and discuss any contract or operational issues, including contract activity. These program reviews, if conducted, will be at a time and location of the Government's choice. The Contractor shall submit any agenda items to the COR and KO no later than five (5) days prior to the scheduled contract review and minutes will be supplied no later than five (5) days after the review (CDRL A002).
1.5.13 Hours of Operations
The hours of operations include all operational support required for DSRC resources and networks to include DSRC operations 24 hours/day, 7 days/week and a Help Desk that provides support 5 business days per week (Monday- Friday), nominal business hours per day (nominally 0800-2000 Eastern Time), excluding Federal Holidays, to over 5,000 users (approximately 2,500 considered active users). The Contractor shall observe the normal work hours of the HPCMP. The HPCMP’s normal work hours, Monday through Friday, are 0600 to 1800 of the respective DSRC time zone. Specific tasks may require variations from this schedule as a result of the type of work performed and shall be approved by the COR or KO. The Contractor shall optimize personnel staffing and manning to match the specific task requirements and performance criteria during the operating hours. In addition, weekend and evening support may be required to accommodate HPCMP activities.
1.5.14 Observance of Legal Holidays and Administrative Leave
Generally, the Contractor shall not be required to work, nor will payment be made by the Government for holidays and administrative leave. The Contractor shall obtain prior approval from the KO and COR before providing support during recognized federal holidays, periods of administrative leave, facility closures, or times of restricted facility access. Generally, computer operators will work 24/7, 365 while other positions will be required to be on-call. The Contractor shall implement the best approach to cover DSRC and Cross-Centers operations.
The following is a list of Federal holidays and other events that might lead to reduced access to the DSRC facilities and/or reduced staffing levels (DSRCs will continue to operate):
a. New Year's Day
b. Martin Luther King Jr Day
c. Washington’s Birthday
d. Memorial Day
e. Juneteenth
f. Independence Day
g. Labor Day
h. Columbus Day
i. Veterans Day
j. Thanksgiving Day
k. Christmas Day
l. Any other day designated by Federal statute, executive order, or presidential proclamation.
There may be local determinations relating to adverse weather conditions, national emergencies, energy conservation, HPCMP and/or DSRC executive order determinations, furloughs, etc., which may require one or more facilities to close or reduce facility access. Since there is 24/7 coverage required for this contract, work may be required at the respective facilities to be determined by the local authority. However, work may also be performed at an alternate location, with prior approval by the KO or COR. Telework may be permitted with approval from the COR and concurrence from the local site COTR and IAW local teleworking policies.
1.5.15 Travel
All Contractor travel shall comply with the Joint Travel Regulations (JTR) and Federal Travel Regulation (FTR). The Contractor shall submit a formal travel request to the COTR/COR/KO at least seven (7) business days prior to the scheduled travel. The Contractor shall not conduct any travel under this contract without explicit written prior authorization from the COTR/COR/KO. If unexpected travel due to an unplanned system outage is required, the Contractor must show due diligence that costs were kept to a minimum and are beholden to supplying all receipts and costs in the Trip Report (CDRL A001).
1.5.16 Conservation of Utilities
The Contractor shall instruct employees in utilities conservation practices. The Contractor shall be responsible for operating under conditions, which preclude the waste of utilities that shall include:
a. Lights shall be used only in areas where, and when, work is being performed.
b. Mechanical equipment controls for heating, ventilation, and air conditioning systems shall not be adjusted by the contractor, or by contractor employees, unless authorized.
c. Water faucets or valves shall be turned off after the required usage has been accomplished.
d. Computer equipment shall be powered down during off hours, unless otherwise coordinated.
1.5.17 Off-Site Space Requirements
For DSRC-related tasks, Contractor staff shall generally perform work on-site at the DSRCs although some off-site work may be permitted under local guidance.
For Cross-Centers/enterprise efforts, Contractor staff generally work from either nearby DSRC sites or more commonly from remote locations. In the event adequate space is not available at a Government facility to house the personnel required to work on-site for specific task(s), the Government shall provide required space including all utilities, telephone, janitorial services, workstations;
associated hardware and software; office equipment/ furnishing(s), telecommunication connectivity, as required for Information systems access, and supplies. However, the Contractor, with the direction and assistance of the Government representative(s), shall provide the appropriate space for Contractor personnel during natural disasters, and unforeseen Government facility closures.
Contractor staff approved for remote work shall be provided Government-furnished IT equipment to perform duties under this contract.
1.5.18 Transition-In Period
It is essential to the Government that services required under this PWS are performed without interruption. Consequently, it is imperative that transition to full contract performance be accomplished in a well-planned, orderly manner. The transition period shall begin at the time of award. Full contract performance is expected within one hundred and twenty (120) calendar days of contract award, or as required by the solicitation. The purpose of this orientation is primarily to:
a. Observe work accomplished by current contractor personnel
b. Complete personnel requirements including the hiring of personnel to ensure satisfactory performance beginning on the contract start date (Note: Soliciting personnel for employment during their duty hours is prohibited. Contractor shall abide by applicable recruitment governance regulations.)
c. Obtain security clearances
d. Accomplish necessary training of contractor employees
e. Establish workstations and other equipment/access necessary
f. Support and close-out current HPCMP System Integrations
g. Transition of maintenance agreements across Cross-Centers and
DSRC sites
1.5.19 Transition-Out Activities
At the conclusion of option periods or extensions, the services provided under this PWS may be awarded to another contractor. The Contractor in place shall be required to assist in the transition activities.
1.5.20 Monthly Assessment Report
The Contractor shall prepare and submit a comprehensive Monthly Assessment Report (CDRL A004) to provide the Government with full visibility into operational progress, schedule adherence, financial expenditures, and risk management.
The Contractor shall submit the Monthly Assessment Report no later than the tenth (10th) calendar day of the following month. Adherence to this timeline is mandatory to allow Government stakeholders to review contractor performance and resolve any discrepancies without delaying the prompt payment of invoices.
The Monthly Assessment Report shall, at a minimum, include the detailed elements outlined in the following table:
Category Description
Personnel & Staffing
Current Levels: Total employee headcount and Total Full-Time Equivalents (FTEs) utilized during the assessed month. Turnover & Changes: Detailed summary of any staffing changes, including onboarding and offboarding personnel. Vacancy Status: List of current vacancies, the duration they have been open, the status of ongoing recruitment efforts, and estimated fill dates. Operational Impact:
Assessment of how any current vacancies or staffing changes are impacting mission performance or schedule.
Financial Expenditures
Monthly Costs: Extended dollar expenditures incurred during the reporting month. Cumulative Tracking: Cumulative cost-to-date compared against the total allocated budget or ceiling. Funding Status:
Current burn rate, remaining funding balance, and notification if funding is projected to fall below critical thresholds.
Risk Management
Anticipated Risks: Identification of new or emerging risks (schedule, technical, financial, or personnel-related). Mitigation Strategies:
Detailed risk mitigation plans and corrective actions proposed or implemented to resolve identified risks before they impact performance.
Technical & Schedule Performance
Accomplishments: Detailed summary of tasks completed and deliverables submitted during the reporting month. Milestone Progress: Status of project milestones (completed, on schedule, or delayed) and adherence to the baseline schedule. Future Planning:
Specific plans, objectives, and scheduled milestones for the forthcoming month. Quality & Performance: Summary of any technical reviews, performance assessments, or Quality Control (QC) inspections conducted, including corrective actions taken.
Part 2.0: Period of Performance The overall Indefinite Delivery Indefinite Quantity (IDIQ) base contract will consist of a five (5) year order period. Task orders will be issued during the five-year ordering period and will specify a period of performance for each order.
Part 3: General Scope of Requirements This section identifies the broad set of requirements for contractor technical services needed to support the mission of the HPCMP Centers component. The three primary focus areas of the mission are to (1) operate the DSRCs, (2) deliver HPC capabilities, and (3) assist users of HPC resources. Although the DSRCs contribute similarly to the mission, they have some unique requirements based on local organization support (or lack of), emphasis on classified or specialized HPC capabilities, and tailored support for expected HPC workflows and use cases. DSRC-specific, Cross-Centers/enterprise related, and any other special requirements will be addressed through individual tasks.
The following sections are organized by the Centers’ mission elements: Operate DSRCs (3.1), Deliver HPC Capabilities (Unclassified 3.2, Classified 3.3, Specialized 3.4), and Assist HPC Users (3.5). There is an additional section (3.6) that identifies the requirements for Cross-Centers or enterprise activities, including overall contract program and performance management. The last section (3.7) addresses the overall security requirements. Altogether, the requirements identified in this PWS for the base contract determine the broad scope of effort needed to fully support the Centers’ mission. Individual tasks will provide more specifics to the basic requirements and determine levels of effort needed.
3.1 Operate DSRCs
This PWS element includes all general support required for basic operations of the DSRCs to be ready to deliver HPC capabilities and assist users. The requirements are somewhat independent of the number of HPC systems operating and HPC users being supported. The requirements are inclusive for a DSRC facility with appropriate operational elements of total electrical power and mechanical cooling capacity (not tied specifically to any HPC systems but representative of overall total capacity), basic DREN and SDREN networking enclaves with various operational workstations and servers, safety and security programs, and business processes such as procurement, asset/inventory control, change management, and configuration management.
Basic operations support will ensure the following:
• Each DSRC operates and delivers HPC capabilities 24 hours/day, 7 days/week, 365 days/year (includes government holidays, although reduced staff expected during government holidays)
• Facilities, support infrastructure, local networks, and non-HPC systems (such as general or dedicated physical or virtual servers and workstations) remain operational and reliable
• Cybersecurity support is continuous and consistent with effective risk assessment and management so that network enclaves maintain appropriate authorities to operate (ATOs)
• Hardware and software maintenance and service agreements are up to date
• Assets and associated configurations are managed effectively
3.1.1 Operations Monitoring
The Contractor shall provide support to monitor the DSRC facilities, infrastructure elements, networks, and both non-HPC and HPC systems for 24x7 operations.
This includes all unclassified areas at a minimum, and classified areas will be identified by the DSRCs in separate tasks.
3.1.2 Facilities and Engineering Support
The Contractor shall provide technical infrastructure and site-readiness support incidental to the beddown, installation, and physical integration of Technology Insertion (TI) systems, to include other HPC and non-HPC systems within the DSRC. This support shall include, but is not limited to, environmental monitoring, electrical power conditioning, backup subsystems, mechanical cooling adjustments, and other related technical tasks specifically required for system integration. Services involve engineering assessments, technical designs, and associated support functions necessary to prepare and maintain the physical environment for successful HPC system deployment.
As IAW FAR 31.205-4, costs of bonding required by the contractor in the general conduct of its business are allowable to the extent that such bonding is IAW sound business practice and the rates and premiums are reasonable under the circumstances.
3.1.3 Cybersecurity Support for DSRC Operations
The basic operational DREN, SDREN and/or Above-Secret network enclaves in each DSRC require authorization to operate (ATO) and connect to the wide-area networks. The Contractor shall assist the government cybersecurity staff in attaining and sustaining the appropriate authorizations to operate (ATOs).
Cybersecurity requirements related to DSRC operations are identified in section
3.7. Cybersecurity support in classified enclaves other than SDREN will be addressed in individual DSRC task order.
3.1.4 System Administration
The Contractor shall provide comprehensive system administration support for non-High-Performance Computing (non-HPC) infrastructure to ensure continuous, reliable, and secure operations. This infrastructure includes, but is not limited to, physical and virtual workstations, servers, data repositories, and virtual communication equipment. Due to the unique configuration of each DSRC, the Contractor shall execute specific administration requirements as defined in individual task orders, which will specify the quantity, system types, and localized security protocols for each site.
3.1.5 Network Engineering and Administration
For basic DSRC operations, the DREN, SDREN and/or Above-Secret enclaves require engineering and system administration support for the various equipment items such as routers and switches. The Contractor shall provide network engineering and system administration for the network devices. Support for network engineering and administration for classified enclaves other than SDREN will be addressed in individual DSRC task order.
3.1.6 Database Administration
Each DSRC maintains databases for basic operations support. This includes but is not limited to environmental monitoring data, service tickets, maintenance logs, etc. The Contractor shall provide database administration support for these systems.
3.1.7 Software Development
The Contractor shall develop, and support execution of specialized software used in DSRC operations. This includes but is not limited to applications to monitor facility environmental controls and automate operational processes.
3.1.8 Maintenance Support
As part of their procurement and lifecycle management requirements, the Contractor shall source, procure, and manage hardware, software, and service agreements necessary for DSRC routine operations. This includes, but is not limited to, maintenance agreements for facility equipment and supporting infrastructure (e.g., networks, non-HPC servers).
The Contractor shall ensure that all renewals, upgrades, and procurements are executed in a timely manner to prevent any lapse or interruption in maintenance coverage or service agreement validity. The Contractor is responsible for tracking all expiration dates and shall initiate procurement actions with sufficient lead time to ensure seamless continuity of support. All procurement actions shall be conducted IAW approved Government purchasing regulations and are subject to prior KO/COR approval as defined in the task order.
3.1.9 Inventory Management Support
The Contractor shall provide technical support to the DSRCs in identifying and documenting equipment inventory for asset management. All inventory and asset management support activities shall be performed on a task order basis, with specific deliverables, locations, and system counts defined in individual task orders.
While this contract does not include Government Furnished Equipment (GFE) or Government Furnished Property (GFP) that is accountable to the Contractor, the Contractor shall assist the Government in the identification, documentation, and tracking of Government-owned assets to ensure comprehensive lifecycle management and audit readiness.
3.1.10 Configuration and Change Management
Various system and subsystem configurations often change within a DSRC and/or at the Cross-Centers/enterprise level and effective local and/or enterprise management processes are executed. The Contractor shall support the configuration and change management processes by assisting in identifying and documenting configurations and associated changes.
3.1.11 Procurement Support
The Contractor shall provide procurement and purchasing support for local, unique DSRC requirements on a task order basis. Procurements executed under this contract shall be strictly limited to items, services, and agreements required for the execution of the requirements under this contract. In addition, all procurements will require COR and/or KO approval.
Allowable purchases to support routine operations include but are not limited to:
office supplies and equipment, facility infrastructure items, HPC infrastructure equipment, services to include installation and integration support, hardware and software maintenance, and the initial procurement and renewal of software agreements.
Contractor procurement documentation for all acquisitions must specify the designated Government Inventory Manager. This individual shall serve as the authorized official to sign for acceptance and assume formal accountability for all property purchased under this contract.
3.1.12 Continuity of Operations
Technical support is required to reconstitute critical operations, defined by the government, for a DSRC at alternative location(s) in the event of a disaster that would shut down the primary DSRC location. This includes Cross-Centers or enterprise services hosted at a DSRC. The Contractor shall assist in establishing continuity of operations and disaster recovery for such events and shall support any exercises/simulations.
3.1.13 Technical Project Support
The DSRCs regularly execute studies and projects related to, but not limited to, facility upgrades, infrastructure changes, HPC capacity increases, and HPC system installation and integration. The Contractor shall provide technical support for these DSRC studies and projects at both the local and enterprise levels, as required by the Government.
Technical support shall include technology planning, feasibility assessments, and engineering support during project execution. At the Government's discretion, specific project support activities and deliverables shall be managed and tracked via formal Work Requests issued under an authorized task order.
3.2 Deliver Unclassified HPC Capabilities
Delivering HPC capabilities includes requirements in direct support of installing, integrating, and operating HPC systems for the HPCMP. The basic scope in this PWS section includes allocated, shared unclassified HPC systems as well as shared special-purpose unclassified systems. This PWS element also includes the HPC-related infrastructure that ties directly to delivering unclassified HPC capabilities, such as data movement, data storage (mid-tier and archive), and user interfaces/portals to unclassified HPC systems.
3.2.1 Infrastructure Support for Unclassified HPC
The Contractor shall provide technical support to include, but not be limited to, system engineering, system integration, system administration, and database administration for HPC-related infrastructure directly…
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 .