B01.03 HITS-UIII Performance Work Statement DRAFT 2025.03.06.pdf
PDF 2 MB Posted
- Attached to
- Request for Information - USACE-HPCMP HITS-UIII Federal contract opportunity
- Solicitation number
- PANERD25P0000_001596
About this file
This Performance Work Statement (PWS) details the requirements for the High Performance Computing Modernization Program (HPCMP) Integrated Technical Services - Unrestricted III (HITS-U III) contract. The contract will support four Department of Defense Supercomputing Resource Centers (DSRCs) located at Air Force Research Laboratory, Army Research Laboratory, Army Corps of Engineers Engineer Research and Development Center, and Navy Stennis Space Center, with a five-year ordering period. Key objectives include operating DSRCs, delivering unclassified and classified high-performance computing (HPC) capabilities, assisting HPC users, and providing cross-centers/enterprise support.
The primary mission encompasses operating computing centers 24/7, maintaining cybersecurity, delivering HPC capabilities across classified and unclassified environments, and providing technical support services. Contractor personnel will be required to have security clearances ranging from Secret to Top Secret, with specific certification and training requirements. The contract will involve system administration, network engineering, application management, user support, and enterprise-level coordination across multiple military service sites. The contractor will be responsible for continuous system operations, help desk support, technology assessments, software development, and maintaining robust cybersecurity protocols in compliance with Department of Defense information technology standards.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| HITS-UIII Performance Work Statement DRAFT 2025.03.06.pdf | ||
| ProjNet Inquiry Responses_2025.04.18.pdf | ||
| HITS-UIII RFI_2025.04.18 Updated.pdf | ||
| AFRL Sample Tasks RFI_Posted 2025.04.16.pdf | ||
| Navy HITSU III Sample Tasks RFI_Posted 2025.04.16.pdf | ||
| ARL HITSU III Sample Tasks RFI_Posted 2025.04.16.pdf | ||
| ERDC HITS-U III Sample Tasks RFI_Posted 2025.04.16.pdf | ||
| Cross Centers HITSU III Sample Tasks RFI_Posted 2025.04.16.pdf | ||
| B01.03.03 HITS-UIII RFI_2025.04.10_Updated.pdf | ||
| B01.03.02 HITS-UIII RFI_2025.04.07_Updated Paragraph 4(b).pdf | ||
| B01.03 HITS-UIII RFI_2025.03.19_Revised Response Date.pdf | ||
| B01.03 HITS-UIII RFI_2025.03.06.pdf |
Show all 12
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
pg. 1
Performance Work Statement
(PWS)
High Performance Computing Modernization Program Integrated
Technical Services – Unrestricted III
(HITS-U III)
6 March 2025
DRAFT
pg. 2
CONTENTS
Contents
1.0 GENERAL INFORMATION
1.1 INTRODUCTION
1.2 BACKGROUND
1.3 SCOPE
1.4 ACRONYMS
1.5 GENERAL REQUIREMENTS
1.5.1 Contractor Program Manager and Deputy
1.5.2 Key Personnel
1.5.3 Administrative, Managerial, and Supervisory
1.5.4 Security Investigation and clearance
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 Period
1.5.19 Transition activities
1.5.20 Monthly assessment report (CDRL A004)
2.0 PERIOD OF PERFORMANCE (POP)
3.0 GENERAL SCOPE OF REQUIREMENTS
3.1 OPERATE DSRCS
3.2 DELIVER UNCLASSIFIED HPC CAPABILITIES
3.3 DELIVER CLASSIFIED HPC CAPABILITIES
3.4 DELIVER SPECIALIZED HPC CAPABILITIES
3.5 ASSIST HPC USERS
3.6 CROSS-CENTERS/ENTERPRISE SUPPORT
3.7 OVERALL SECURITY
pg. 3
4.0 QUALITY ASSURANCE
5.0 DELIVERABLES
5.1 METHOD OF DELIVERY
5.2 REPORTS/PLANS
5.2.1 Program Management Plan (CDRL A010)
5.2.2 Weekly Situational Awareness Report (CDRL A003)
5.2.3 Monthly Assessment Report (CDRL A004)
5.2.4 Transition Support
5.2.5 Phase-in Plan (CDRL A011)
5.2.6 Phase-Out Plan (CDRL A012)
5.2.7 Initial Business and Technical Meeting (KICK-OFF) (CDRL A014). 52
5.2.8 Monthly Financial Summary Report (CDRL A015)
5.2.9 Enterprise Contractor Manpower Reporting application (eCMRA)
(CDRL A006)
5.2.10 Abbreviated Accident Prevention Plan (AAPP)
5.2.11 Other Reports
5.2.12 Monthly Accrual Forecast (CDRL A015)
5.2.13 Integrated Master Schedule (CDRL A016)
5.2.14 Hardware/Software maintenance report (CDRL A007)
5.2.15 monthly inventory report (CDRL A017)
5.2.16 system integration project plan (CDRL A005)
5.2.17 Monthly Cybersecurity Status Report (CDRL A008)
5.2.18 MONTHLY 8140 NON-COMPLIANCE Report (CDRL A019)
5.3 INSPECTION AND ACCEPTANCE
5.3.1 Scope of Inspection
5.3.2 Basis of Acceptance
5.3.3 Non-Conforming Products or Services
5.3.4 Problem Resolution
5.3.5 Notice of Late Delivery
5.3.6 Draft Deliverables
6.0 CONTRACT ADMINSTRATION
7.0 PAST PERFORMANCE INFORMATION
8.0 APPLICABLE DOCUMENTS
9.0 GOVERNMENT FURNISHED EQUIPMENT (GFE)
9.1 GFE /GFP
9.2 SOFTWARE MADE AVAILABLE FOR CONTRACTOR’S USE
10.0 REIMBURSABLE COSTS
pg. 4
10.1 TRAVEL
10.2 PRIOR APPROVAL
10.3 MATERIALS, EQUIPMENT AND OTHER SERVICES
10.3.1 IT Equipment/Software Solutions
10.3.2 Mail Services
10.3.3 Miscellaneous Supplies and Materials
11.0 PRIVACY ACT
12.0 PERSONNEL SECURITY
12.1 DD-254
12.2 SECURITY MANAGEMENT
12.3 TERMINATION
12.4 EMPLOYMENT ELIGIBILITY
12.5 CONTINUED ELIGIBILITY
12.6 SUITABILITY DETERMINATION
12.7 INFORMATION TECHNOLOGY SECURITY TRAINING AND OVERSIGHT.
13.0 NON-PERSONAL SERVICES
14.0 CONTRACT FUNDING
14.1 INCREMENTAL FUNDING
15.0 CONTRACT ADMINISTRATION DATA
15.1 CONTRACT COMPLETION
16.0 ANTITERRORISM (AT) AND OPERATIONS SECURITY (OPSEC)
16.1 ACCESS AND GENERAL PROTECTION/SECURITY POLICY AND
PROCEDURES
16.2 SUSPICIOUS ACTIVITY REPORTING TRAINING
16.3. CONTRACTOR EMPLOYEES WHO REQUIRE ACCESS TO
GOVERNMENT INFORMATION SYSTEMS
16.4 OPSEC STANDING OPERATING PROCEDURE/PLAN
16.5 OPSEC TRAINING
16.6 INFORMATION ASSURANCE (IA)/INFORMATION TECHNOLOGY (IT)
TRAINING
16.7 FOR INFORMATION ASSURANCE (IA)/INFORMATION TECHNOLOGY (IT)
CERTIFICATION
16.8 FOR CONTRACTS THAT REQUIRE HANDLING OR ACCESS TO
CLASSIFIED INFORMATION
pg. 5
16.9 WILL BE ESCORTED IN AREAS WHERE THEY MAY BE EXPOSED TO
CLASSIFIED AND/OR SENSITIVE MATERIALS AND/OR SENSITIVE OR
RESTRICTED AREAS
16.10 CONTRACTOR COMPANY TO OBTAIN A FACILITY CLEARANCE AND
INDIVIDUAL CLEARANCES AT THE APPROPRIATE LEVEL
16.11 THREAT AWARENESS REPORTING PROGRAM
16.12 PRE-SCREEN CANDIDATES USING E-VERIFY PROGRAM:
APPENDIX A: PURCHASE REQUEST PROCESS AND TEMPLATE
pg. 6
1.0 GENERAL INFORMATION
1.1 INTRODUCTION. Work performed under this contract is for direct support to the Centers component of the Department of Defense (DoD) High Performance Computing Modernization Program (HPCMP) managed by the U.S. Army Corps of Engineers, Army Engineer and Research Center (ERDC), Vicksburg, MS. The Centers component provides funding, strategic direction, and operational guidance for five DoD 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 DoD HPCMP mission is to provide DoD'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 DoD-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’ five DSRC names and locations are identified below:
• The Air Force Research Laboratory (AFRL) DSRC, Wright-Patterson Air Force
Base, OH
• The Army Research Laboratory (ARL) DSRC, Aberdeen Proving Ground, MD
pg. 7
• The Army Corps of Engineers, Engineer Research and Development Center (ERDC) DSRC, Vicksburg, MS
• The Navy DSRC, Stennis Space Center, MS
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 DoD 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 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), 12 hours per day (0800-2000 Eastern Time), excluding federal holidays, to over 5,000 HPC users and HPCMP staff members (approximately 2,500 considered active users).
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 four of the five DSRCs (AFRL, ARL, ERDC, 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. Requirements will be defined by individual tasks from the four supported DSRCs and Cross-Centers. The tasks may include work requested and funded by HPCMP components other than Centers and/or customers of the HPCMP.
1.4 ACRONYMS. The following table is a key of acronyms used within this PWS.
pg. 8
ACRONYMS DEFINITIONS
AFRL Air Force Research Laboratory ARL Army Research Laboratory ATO Authority to Operate CDRL Contract Data Requirements List COTR Contracting Officer’s Technical Representative COR Contracting Officer’s Representative CREATE Computational Research & Engineering Acquisition
Tools and Environments DAAC Data Analysis and Assessment Center DHPI Dedicated HPCMP Investment DoD Department of Defense DPM Deputy Program Manager DREN Defense Research and Engineering Network DSRC DoD Supercomputing Resource Center ERDC Engineer Research Development Center ESMT Enterprise Software Management Team 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 KO Contracting Officer 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
pg. 9
1.5 GENERAL REQUIREMENTS
1.5.1 CONTRACTOR PROGRAM MANAGER AND DEPUTY. 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 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 IT organizational support management experience similar to the size and scope reflected in this PWS. The experience can be Federal or private industry. For candidates with advance degrees (e.g. Masters or PhD) or recognized industry certifications (e.g. PMI’s PMP) may substitute up to 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 Contracting Officer (KO), HPCMP Program Manager (PM) or Contracting Officer's Representative (COR) within two (2) hours of notification.
1.5.2 KEY PERSONNEL. The Government has determined that certain personnel are key to successful completion of the contract. These Key Personnel will be designated in the individual tasks 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 considered to be 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 KO or 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 Tasks Program Manager PWS Paragraph 3.6.1 Deputy Program Manager PWS Paragraph 3.6.1 Site Lead – AFRL DSRC Per AFRL DSRC Tasks Site Lead – ARL DSRC Per ARL DSRC Tasks Site Lead – ERDC DSRC Per ERDC DSRC Tasks Site Lead – Navy DSRC Per Navy DSRC Tasks Lead – Cross-Centers Per Cross-Centers Tasks ISSO Lead – AFRL DSRC PWS Paragraph 3.7.10.1 ISSO Lead – ARL DSRC PWS Paragraph 3.7.10.1 ISSO Lead – ERDC DSRC PWS Paragraph 3.7.10.1 ISSO Lead – Navy DSRC PWS Paragraph 3.7.10.1 ISSO Lead – Cross-Centers PWS Paragraph 3.7.10.1
pg. 10
Program Manager/Deputy Program Manager responsibilities include, but are not limited to:
• The Program Manager/Deputy Program Manager will serve as the main point of contact for the Contracting Officer (CO), Contracting Officer Representative (COR) and, the HPCMP Associate Director 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
• 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.
pg. 11
• 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
• A 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
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 DoD and HPCMPO security regulations by coordination of activities by the established timeline from the ISSMs.
Further ISSO responsibilities and qualifications are identified in PWS paragraph 3.7.10.1.
1.5.3 ADMINISTRATIVE, MANAGERIAL, AND SUPERVISORY. The Contractor shall provide qualified personnel with administrative, managerial, and supervisory capabilities to assure the effective performance of the contract.
1.5.4 SECURITY INVESTIGATION AND CLEARANCE. 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 in accordance with DoD 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 Associate Director 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).
pg. 12
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.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.
All new positions added during the performance of this contract must be staffed within 45 calendar days, and all replacement positions must be staffed within 28 calendar days. The KO/COR/COTRs must be notified if vacancies have not been filled in allotted time period and approve any exceptions to this staffing requirement.
1.5.6 QUALIFICATIONS. The Contractor shall maintain a qualified staff at all times. The Government restricts access or work hereunder to United States citizens only.
All cybersecurity risk management-related positions must have baseline certifications as designated in DoD Approved 8570 Baseline Certifications (DoD 8570.01M) or DoDM
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 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 (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
pg. 13 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 in accordance with 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 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
pg. 14 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 days (Monday-Friday) 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 will identify any exceptions where contractor support may be required during holidays, administrative leave, facility closure, and facility reduced 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
pg. 15 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 concurrence from COR and in accordance with local telework policies.
1.5.15 TRAVEL. Travel shall be in accordance with the Federal Travel Regulations and can only be conducted upon prior approval by 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 actually 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. In the event adequate space is not available at a Government facility to house the personnel required 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, as discussed in paragraph 1.5.14.
1.5.18 TRANSITION 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
pg. 16 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 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 (CDRL A004). The Contractor shall prepare and submit a monthly assessment report describing accomplishments during the past month, the progress achieved via milestones during the past month, plans for the forthcoming month, any anticipated problems. Monthly Assessment Reports shall include staffing numbers, to include number of employees and number of FTEs of the month assessed, staffing changes, vacancies, and extended dollar expenditures.
The Contractor is required to submit the Monthly Assessment Report by the tenth (10th) calendar day of the following month, allowing government customers to review contractor performance in a timely manner without delaying prompt payment of invoices.
2.0 PERIOD OF PERFORMANCE (POP)
The period of performance for the overall base contract will consist of a five (5) year ordering period. Tasks will be issued during the five-year ordering period and will specify a period of performance for each task.
3.0 GENERAL SCOPE OF REQUIREMENTS
This section identifies the baseline 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 and any 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
pg. 17 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 baseline scope of effort needed to minimally support the Centers’ mission. Individual tasks will provide more specifics to the baseline requirements and determine level of effort needed.
3.1 OPERATE DSRCs
This PWS element includes all minimal 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.
Baseline 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, and non-HPC systems 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
• Hardware and software maintenance agreements are up to date
• Configurations are managed effectively
3.1.1 Operations Monitoring
The Contractor shall provide support to monitor the DSRC facilities, infrastructure elements, and HPC systems for 24x7 operations. This includes all unclassified areas in the baseline, and classified areas will be identified by the DSRCs in separate tasks.
3.1.2 Facilities Engineering Support
The Contractor shall provide support to DSRC efforts related but not limited to minor building alterations, environmental monitoring, electrical power and backup subsystems, and mechanical support systems. Services include planning through engineering designs and assessments, as well as other functions needed to execute facility projects.
pg. 18
3.1.3 Cybersecurity Support for DSRC Operations
The baseline operational DREN, SDREN and/or Above-Secret network enclaves in each DSRC require authorization to operate and connect to the wide-area networks.
The Contractor shall assist the government cybersecurity staff in attaining and sustaining the appropriate authorizations to operate. 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 tasks.
3.1.4 System Administration
For baseline DSRC operations, there are a number of non-HPC devices such as workstations, servers, repositories, and virtual communication equipment. The Contractor shall provide system administration support in keeping these systems operating reliably and securely. Each DSRC has different numbers and types of non- HPC systems to administer, and individual tasks will be used to further specify this requirement per DSRC.
3.1.5 Network Engineering and Administration
For baseline 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 tasks.
3.1.6 Database Administration
Each DSRC maintains databases for baseline 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
The Contractor shall provide support for DSRC hardware and software maintenance agreements related to facility equipment and supporting infrastructure (networks, non- HPC servers, etc) used in routine operations.
pg. 19
3.1.9 Inventory Management Support
The Contractor shall assist the government in identifying and documenting equipment inventory for asset management. This contract does not handle GFP however, the Contractor shall provide support to the DSRCs in identifying and documenting equipment inventory for asset management.
3.1.10 Configuration and Change Management
Various system and subsystem configurations often change within a DSRC and effective 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
Each DSRC has the ability to purchase various items needed to support routine operations. This includes, but is not limited to, office supplies and equipment, facility infrastructure items, and HPC infrastructure equipment as well as, hardware/software maintenance. The Contractor shall provide procurement/purchasing support for any local unique DSRC requirements per task.
3.1.12 Continuity of Operations
Technical support is required to reconstitute critical operations, defined by the government, of a DSRC at alternative location(s) in the event of a disaster that would shut down the primary DSRC location. 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
DSRCs regularly execute studies and projects related but not limited to facility upgrades, infrastructure changes, HPC capacity increases, and HPC system installation and integration. The Contractor shall provide technical support to DSRC studies and projects whether local or enterprise level. The support shall include technology planning and assessments and engineering support during project execution.
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 baseline 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
pg. 20 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 tied to delivering unclassified HPC capabilities. This includes but is not limited to HPC data movement and storage systems, portals, servers, routers, and switches that have direct relationships/connections to HPC systems. This does not include those systems or devices that are part of the DSRC baseline operations identified in paragraph 3.1 and associated subparagraphs.
3.2.2 Unclassified HPC System Installation and Integration
This requirement includes preparation of the DSRC facilities for installing, integrating, accepting, and operating unclassified HPC systems. The Contractor shall provide engineering support for connecting the unclassified HPC systems to the DSRC infrastructure, both facilities-related and HPC-delivery-related.
3.2.3 Application Management Support for Unclassified HPC
The HPC original equipment manufacturers (OEMs) typically provide levels of support, maintenance, and warranties for hardware and software delivered with an operational HPC system. For those software components that are to be installed and/or modified to support HPCMP workloads/use cases, the Contractor shall install, modify, and manage those applications for unclassified HPC system utility. This includes but is not limited to job schedulers, reservation/dedicated partition services, data management/movement services, data visualizers, HPC applications, and user interfaces/portals.
3.2.4 Cybersecurity Support for Unclassified HPC Systems
This requirement is related to cybersecurity support for unclassified HPC needed in addition to, DSRC operations cybersecurity identified in paragraph 3.1.3. The Contractor shall provide this additional cybersecurity support to include but not be limited to HPC infrastructure and HPC systems. This additional cybersecurity support shall be identified within individual DSRC tasks. Cybersecurity requirements related to Unclassified HPC systems are identified in section 3.7.
3.2.5 Unclassified HPC System Support
HPC systems may be managed and administered by OEMs, third-party entities, government personnel, or the Contractor. Requirements in this area will be identified by task.
3.2.6 Additional unclassified HPC requirements
pg. 21
As defined per task.
3.3 DELIVER CLASSIFIED HPC CAPABILITIES
integrating, and operating HPC systems for the HPCMP. The baseline scope in this PWS section includes allocated, shared classified HPC systems as well as shared special-purpose classified or systems. This PWS element also includes the HPC-related infrastructure that ties directly to delivering classified HPC capabilities, such as data movement, data storage (mid-tier and archive), and user interfaces/portals to classified HPC systems. All DSRCs have SDREN enclaves; however, not all DSRCs host HPC systems in those enclaves. Some DSRCs have above-secret level enclaves where HPC systems and infrastructure exist. Individual DSRC tasks will describe the specific classified HPC requirements.
3.3.1 Infrastructure Support for Classified 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 tied to delivering classified HPC capabilities. This includes but is not limited to HPC data movement and storage systems, portals, servers, routers, and switches that have direct relationships/connections to HPC systems. This does not include those systems or devices that are part of the DSRC baseline operations identified in paragraph 3.1 and associated subparagraphs.
3.3.2 Classified HPC System Installation and Integration
This requirement includes preparation of the DSRC facilities for installing, integrating, accepting, and operating classified HPC systems. The Contractor shall provide engineering support for connecting the classified HPC systems to the DSRC infrastructure, both facilities-related and HPC-delivery-related.
3.3.3 Application Management Support for Classified HPC
The HPC original equipment manufacturers (OEMs) typically provide levels of support, maintenance, and warranties for hardware and software delivered with an operational HPC system. For those software components that are to be installed and/or modified to support HPCMP workloads/use cases, the Contractor shall install, modify, and manage those applications for classified HPC system utility. This includes but is not limited to job schedulers, reservation/dedicated partition services, data management/movement services, data visualizers, HPC applications, and user interfaces/portals.
3.3.4 Cybersecurity Support for Classified HPC Systems
pg. 22
This requirement is related to cybersecurity support for classified HPC needed in addition to, DSRC operations cybersecurity in paragraph 3.1.3. The Contractor shall provide this additional cybersecurity support to include but not be limited to HPC infrastructure and HPC systems. This additional cybersecurity support shall be identified within individual DSRC tasks. Cybersecurity requirements related to Classified HPC systems are identified in section 3.7.
3.3.5 Classified HPC System Support
HPC systems may be managed and administered by OEMs, third-party entities, government personnel, or the Contractor. Requirements in this area will be identified by task.
3.3.6 Additional classified HPC requirements
As defined per task.
3.4 DELIVER SPECIALIZED HPC CAPABILITIES
integrating, and operating HPC systems for the HPCMP. The baseline scope in this PWS section includes specialized HPC systems used to explore new technologies, alternative service delivery models, or emerging non-traditional workloads/use cases.
These systems are typically not shared or allocated the same as the systems in PWS paragraphs 3.2 and 3.3, and can be hosted in various environments (unclassified, classified, isolated, standalone). This PWS element also includes the HPC-related infrastructure that ties directly to delivering specialized HPC capabilities, such as data movement, data storage (mid-tier and archive), and user interfaces/portals to specialized HPC systems. Each DSRC has unique requirements for specialized HPC which will be addressed in individual DSRC tasks.
3.4.1 Infrastructure Support for Specialized 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 tied to delivering specialized HPC capabilities. This includes but is not limited to HPC data movement and storage systems, portals, servers, routers, and switches that have direct relationships/connections to HPC systems. This does not include those systems or devices that are part of the DSRC baseline operations identified in paragraph 3.1 and associated subparagraphs.
3.4.2 Specialized HPC System Installation and Integration
This requirement includes preparation of the DSRC facilities for installing, integrating, accepting, and operating specialized HPC systems. The Contractor shall provide
pg. 23 engineering support for connecting the specialized HPC systems to the DSRC infrastructure, both facilities-related and HPC-delivery-related.
3.4.3 Application Management Support for Specialized HPC
The HPC original equipment manufacturers (OEMs) typically provide levels of support, maintenance, and warranties for hardware and software delivered with an operational HPC system. For those software components that are to be installed and/or modified to support HPCMP workloads/use cases, the Contractor shall install, modify, and manage those applications for specialized HPC system utility. This includes but is not limited to job schedulers, reservation/dedicated partition services, data management/movement services, data visualizers, HPC applications, and user interfaces/portals.
3.4.4 Cybersecurity Support for Specialized HPC Systems
This requirement is related to cybersecurity support for specialized HPC needed in addition to, DSRC operations cybersecurity in paragraph 3.1.3. The Contractor shall provide this additional cybersecurity support to include but not be limited to HPC infrastructure and HPC systems. This additional cybersecurity support shall be identified within individual DSRC tasks. Cybersecurity requirements related to Specialized HPC systems are identified in section 3.7.
3.4.5 Specialized HPC System Support
HPC systems may be managed and administered by OEMs, third-party entities, government personnel, or the Contractor. Requirements in this area will be identified by task.
3.4.6 Additional specialized HPC requirements
As identified per task.
3.5 ASSIST HPC USERS
This PWS element includes all baseline support required for assisting HPC users. The requirements relate to an enterprise HPC Help Desk basic function hosted by a single DSRC and higher levels of more involved support from experts at the DSRCs. Also included is an enterprise data analysis and visualization requirement hosted by one or more DSRCs to assist HPC users and HPCMP staff in generating graphical representations of HPC results. Another requirement is included to support the development and maintenance of user account authentication methods for secure access to HPC systems.
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 .