Attachment 1 - Performance Work Statement 377044 - Scheduling Software and Maintenance.pdf
PDF 365 KB Posted
- Solicitation number
- 377044
- Issued by
-
Department of Energy
About this file
This document is a Performance Work Statement (PWS) for a federal contract opportunity to provide scheduling software and implementation support services. The key details are:
The objective is for HMIS Business Management Systems to acquire an asset management software, maintenance, and bar code scanners. The subcontractor is required to provide Scheduling Management software, annual support, and implementation support services. The work includes an on-premises software or FedRAMP Cloud Medium to High solution to handle approximately 351,000 batch jobs per year. The subcontractor must provide qualified personnel with at least 5 years of relevant implementation experience. Deliverables include the software, annual support, an implementation plan, a schedule, and status reporting. Work will be performed off-site at the subcontractor's primary location. The contract is for a base year with 4 option years.
View the file
Other files
Show all 11
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
General Materials or Services- Rev 2 03/28/2023
Performance Work Statement
For
General Materials or Services
Title: Scheduling Software and Maintenance
Date: 9/17/2024
Revision Number: 0
Requisition Number: 00377044
Table of Contents
INTRODUCTION / BACKGROUND
1.1 OBJECTIVE
1.2 DESCRIPTION OF WORK – GENERAL
1.3 DESCRIPTION OF WORK – SPECIFIC
DELIVERABLES/SUBMITTALS
2.1 Deliverables
2.2 Submittals
PLACE OF PERFORMANCE
3.1 Onsite Work Location/Potential Access Requirements
3.2 Site Access and Work Hours
3.3 Badging
REQUIREMENTS
4.1 Engineering Requirements
4.2 Environmental, Safety, and Health Requirements
4.3 Quality Assurance Requirements
ACCEPTANCE CRITERIA
CONFIGURATION MANAGEMENT
6.1 Configuration Management Requirements
6.2 Applicable Standards
6.3 Verification/Hold Points
QUALIFICATIONS
SPECIAL REQUIREMENTS
8.1 Training
8.2 Use of Government Vehicles
Not applicable to this PWS
8.3 Government Property
8.4 Hanford System Access Requirements
8.5 Electrical Components
8.6 Section 508 of Rehabilitation Act Applicability
ACCESS AUTHORIZATION/CLEARANCE REQUIREMENTS
MEETINGS
10.1 Meetings
INTERFACE/NOTIFICATIONS
APPENDICES
INTRODUCTION / BACKGROUND
The Department of Energy, Richland Operations Office, (DOE-RL) manages the Hanford Site working toward protecting the workers, public, and environment by further reducing risk, as well as providing the necessary infrastructure for continued safe and effective cleanup operations, access and use. This is accomplished by work performed by contractors and subcontractors, to ensure the safety of Hanford cleanup.
As a Prime Contractor to the U.S. Department of Energy, Hanford Mission Integration Solutions (HMIS) is responsible for providing direct support to the DOE-RL and its contractors with cost effective infrastructure and site services integral and necessary to accomplish the Hanford Site environmental cleanup mission.
HMIS Business Management Systems is responsible for business software and tools. This is to acquire an asset management software, maintenance and bar code scanners for use in the field to track and account for assets.
1.1 OBJECTIVE
HMIS Business Management Systems requires the services of an experienced subcontractor to provide: Task 1: Scheduling Management Software which meets the requirements, Site License Annual Support, and if needed, Server Support. Base year with 4 option years. Task 2: Implementation Support Services to HMIS for proposed software.
1.2 DESCRIPTION OF WORK – GENERAL
The subcontractor shall provide Scheduling Management software (Task 1) and technically qualified resources (Task 2) that work as a part of a team under the direct oversight of HMIS. Subcontractor resources shall be responsible for independently planning, organizing, and performing a wide variety of non-hazardous specialized administrative/technical duties in support of the successful completion of goals and deliverables. Subcontractor will provide United States citizens resources on United States soil. Additionally, the subcontractor shall furnish all necessary labor, technical and professional services, supervision, materials, tools, equipment, consumables, and payment of any applicable taxes to perform all operations necessary and required to perform the scope as directed by HMIS.
Unless otherwise approved, the subcontractor shall work in accordance with HMIS subcontract requirements, operating policies and procedures and shall be responsible for execution of the work in accordance with the quality standards and requirements specified for assigned project and facility.
Specifically, HMIS requires a subcontractor to provide: Task 1: Scheduling Management Software which meets the requirements, Site License Annual Support, and if needed, Server Support. Base year with 4 Option Years. Task 2: Implementation Support Services to HMIS for proposed software.
1.3 DESCRIPTION OF WORK – SPECIFIC
This Performance Work Statement (PWS) serves as the Master Agreement PWS and defines the overarching scope of the services to be provided and the requirements applicable to the Master Subcontract as well as any associated Subcontract Release(s) issued against
it. The work products and services to be provided, including any specific HMIS standards and requirements, required for the successful completion of this work activity includes Task 1: Scheduling Management Software, Site License Annual Support, and if needed, Server Support if issues arise. This is anticipated to be an on-premises software or must be FedRamp Cloud Medium to High.
The current successful batch job counts for Production is ~351,000 a year with a monthly average of 29,221. See Appendix A for table of Software Specific Requirements. Also see Appendix B for Cybersecurity provisions. The current scheduling system is used to schedule, submit, and track production Information Management batch job processing. The current system which HMIS is looking to replace is used to schedule and process jobs for a multitude of applications including but not limited to focus on applications belonging to Human Resources, Finance, Project Controls and Reporting. The current platform is not granted access to end point systems but acts as scheduling system for jobs. Job execution is performed on end point system by the application or authorized accounts outside of the current platform. Task 2: Implementation Support Services to HMIS for purposed software to include a detail schedule and costs. This will also include expectations of resources needed from HMIS to accomplish implementation.
DELIVERABLES/SUBMITTALS
2.1 Deliverables
Will deliverables be required to be furnished by the Subcontractor: Yes
Task 1 Product Description QTY
1. Scheduling Management Software – Site License and Annual Support (Base plus 4 Option Years) Based on a production count per month of 29,221 – License Key
Task 2 Implementation Plan and Support Services QTY
1. Implementation Plan and Support Services (seeking fast track 6-9 months)
2. Schedule, Milestone and Management Report for Implementation – Description of work performed, hours by staff, costs, plans for next month, Issues, and Accomplishments. Monthly Reporting
3. Weekly Hour Reporting
If deliverables are required, the specific deliverables, dates for completion, reviews, etc., are as follows:
2.2 Submittals
If the PWS requires the submittal of Subcontractor Information, the following apply:
The following items shall be submitted to the submittal e-mail address as indicated on Appendix C, Submittal Register. The Subcontractor shall include the Procurement Specialist and Buyer’s Technical Representative (BTR) on the transmittal
• The Subcontractor submittals identified herein and summarized on the Submittal Register shall be submitted by the Subcontractor using the Contractor Document Submittal Form (CDSF). See Appendix C.
• Subcontractor information shall be submitted in either hard copy or electronic format (If electronic, it must be viewable using either Microsoft® Windows®, Microsoft® Office, or Adobe® Acrobat® software).
• Subcontractor will utilize this CDSF form for delivery of Software authorization documentation only for the deliverables of Task 1 and Task 2. (Note software key for licensing will be emailed to end user and cc to Procurement Specialist).
PLACE OF PERFORMANCE
Will work be performed on the Hanford site: No-Work shall be performed offsite at the primary place of business, or other location as designated by the subcontractor. If no, work shall be performed offsite at subcontractors the primary place of business, or other location as designated by the subcontractor.
3.1 Onsite Work Location/Potential Access Requirements
The primary work location under this subcontract shall be none anticipated for this procurement. This will be completed via Teams meetings and subcontract working on United States soil remotely.
3.2 Site Access and Work Hours
Hanford personnel at the Hanford Site work a standard 4/10 schedule. The standard work week consist of ten (10) hours of work between 6:00 a.m. and 4:30 p.m. with one-half hour designated as an unpaid period for lunch, Monday through Thursday.
Work performed outside normal operating hours shall be coordinated and/or approved through the BTR and/or the Procurement Specialist prior to performing the work.
3.3 Badging
For any on-site work, see On-Site Services Special Provisions for details. The subcontractor shall wear a Buyer issued security badge identifying themselves. A minimum of two (2) working days advance notice is needed for site badging. Subcontractor employees will be required to submit to vehicle searches and not personally carry or transport certain prohibited articles.
Not Applicable
REQUIREMENTS
The requirements listed below are to identify specific standards the subcontractor and subcontractor personnel will be obligated to work to in support of this Performance Work Statement.
4.1 Engineering Requirements
No specific engineering requirements as these are Commercial-off-the-shelf products, therefore not applicable.
Engineering requirements applicable: No
4.2 Environmental, Safety, and Health Requirements
Not Applicable
4.3 Quality Assurance Requirements
The work activities for this Performance Work Statement (PWS) has been designated as a Quality Level F - Q Level 3 - GS. The subcontractor shall be responsible for performing quality workmanship and shall conduct the quality control measures necessary to ensure work conforms to referenced codes and standards, and other requirements defined in this PWS.
ACCEPTANCE CRITERIA
Task 1: License for Schedule Management Software that meets requirements as listed in Appendix A and B.
Task 2: Implementation Plan and Support Services must be accompanied with resumes of proposed individuals who will fulfill the role of subcontractor Project Manager, and suggested number of IT developers/technical engineers who have 5 or more years of experience with implementations of this size and nature who are all U.S. Citizens and live on U.S. Soil. Please include certified signed resumes.
CONFIGURATION MANAGEMENT
6.1 Configuration Management Requirements
Task 1: Meets the requirements listed in Appendix A and B to this PWS.
Task 2: Must be experience in Software management life cycles providing prior working experience satisfactory of a least 5 years.
6.2 Applicable Standards
There are no specific applicable standards identified for this PWS.
6.3 Verification/Hold Points
Not Applicable
QUALIFICATIONS
The Subcontractor shall ensure that its personnel meet and maintain the appropriate training, qualifications, and certification requirements to perform the work as specified in this PWS. The subcontractor is expected to provide appropriately trained and qualified staff to perform the type of work associate with their work at the Hanford site. Additionally, the subcontractor shall perform work in accordance with the specifications, exhibits, and other documents, which made by reference, are a part of the PWS.
In addition to the above, the Subcontractor shall provide qualified personnel throughout the period of performance of the Subcontract.
Subcontractor shall be responsible for ensuring its personnel meet and/or maintain current and valid training requirements, certifications and are fully capable to complete the duties described through the entirety of the Subcontract period of performance and that all personnel shall meet the 5 or more years’ experience implementing awarded scheduling software.
SPECIAL REQUIREMENTS
Not applicable
8.1 Training
The following types of training are required: None are applicable to this PWS.
The subcontractor shall maintain training records for their personnel and ensure all required training is completed prior to work.
8.2 Use of Government Vehicles
Not applicable to this PWS.
8.3 Government Property
Government Property is not anticipated to be furnished to or acquired by Subcontractor under this PWS.
8.4 Hanford System Access Requirements
The following systems shall be utilized to perform the work described. For those systems which HMIS will be responsible for (hereby HMIS Operated System), HMIS will operate, manage, maintain and authorize access for Subcontractor personnel. The Subcontractor shall identify each of its personnel who will require access to the HMIS operated system.
For those systems which the Subcontractor shall be responsible for (hereby Subcontractor Operated System), The Subcontractor shall be responsible for the operation, management, maintenance, and access authorization for these systems.
No system access is required by Subcontractor for either Task 1 or Task 2 for this PWS.
8.5 Electrical Components
Not Applicable
8.6 Section 508 of Rehabilitation Act Applicability
Section 508 of the Rehabilitation Act requires federal agencies to develop, procure, maintain, and use information and communications technology (ICT) that is accessible to people with disabilities - regardless of whether or not they work for the federal government. Section 508 requires federal agencies to make their ICT such as technology, online training, and websites accessible for everyone. This means that personnel with disabilities are able to do their work on the accessible computers, phones and equipment in their offices, take online training or access internal website to locate needed information.
Applicable
ACCESS AUTHORIZATION/CLEARANCE REQUIREMENTS
The scope of work will not require access authorization (security clearance).
MEETINGS
10.1 Meetings
After subcontract award, if a meeting is necessary for support HMIS will issue meeting notices and prepare an agenda and minutes for each meeting addressed in this Section. When applicable, minutes will identify action items, assigned actionees, and due dates.
INTERFACE/NOTIFICATIONS
A. A BTR will be designated for the subcontract/ subcontract release.
B. Designation of BTR
The BTR is responsible for monitoring and providing technical guidance for this subcontract and should be contacted regarding questions or problems of a technical nature. The BTR is also responsible for appropriate surveillance of the subcontractor’s representative while on site. In no event, however, will an understanding or agreement, modification, change order, or any deviation from the terms of this subcontract be effective or binding upon HMIS unless formalized by proper subcontract documents executed by the Procurement Specialist prior to completion of this subcontract. On all matters that pertain to the subcontract terms, the subcontractor shall contact the Procurement Specialist specified within this subcontract.
When in the opinion of the subcontractor, the BTR requests or directs efforts outside the existing scope of the subcontract;
the subcontractor shall promptly notify the Procurement Specialist in writing. The BTR does not possess any explicit, apparent or implied authority to modify the subcontract. No action should be taken until the Procurement Specialist makes a determination and/or modifies the contract.
C. The work will be inspected periodically by the BTR.
D. The subcontractor shall immediately notify the field Contract Release BTR (who will contact HMIS Safety) of any injuries or incidents; to include damage to subcontractor-owned property or equipment. The subcontractor will follow this up within 24 hours with a written explanation to the Procurement Specialist of the occurrence.
E. In the event that there is an abnormal or unusual situation associated with this contract work scope, the subcontractor is to immediately contact the BTR. If, after several attempts, the subcontractor is unable to contact either the BTR or the Procurement Specialist, the Contractor is to contact HMIS Occurrence Notification Center at (509) 376-2900, which is available 24 hours a day, seven days a week, and provide them with: Contract Number, Procurement Specialist’s name, BTR’s name and a short summary of the abnormal or unusual situation. If after making contact with HMIS, the subcontractor is advised to suspend activities, the subcontractor is not to proceed until such direction to proceed has been expressly issued by the Procurement Specialist. If there is an emergency situation, the subcontractor is to make the appropriate immediate emergency call to 911 or 373-0911 for cell phones and then make the notifications to HMIS as set forth herein.
F. Prior to work in the field, subcontractor shall ensure each employee has been cleared by HMIS and verify all training is complete in accordance with this Performance Work Statement.
APPENDICES
Appendix B: Cybersecurity Provisions
Appendix C: Contractor Document Submittal Form (CDSF)
Appendix B - Cybersecurity Provisions
1. The supplier shall provide a completed Compliance with 32 CFR 2004.34 Foreign Ownership Influence and Control, FAR 52.225-1, Buy American-Supplies and Buy American Act 41 USC 8301-8303 Exhibit in the RFP thereby attesting to having no affiliation to a sensitive country.
2. The Supplier shall procure parts from Original Equipment Manufacturer (OEM) or trusted authorized distributor of the OEM and not a drop shipper (e.g. Amazon, eBay, Alibaba).
3. The supplier shall not procure counterfeit asset, component, sub-component, or integrated circuits.
4. The Supplier shall submit security notices when vulnerabilities or flaws are discovered in products they manufacture or procure from vendors.
5. Supplier shall identify long-term service agreements and licensing to facilitate the serviceability duration. All agreements will be acquired separately by the Buyer and submit this listing to the Buyer.
6. The supplier shall inform the Buyer when a product (including software) is phased out no less than 6 months before end-of-service is scheduled.
7. The Supplier shall notify the Buyer when Common Vulnerabilities and Exposures (CVE)
(https://cve.mitre.org) reports a vulnerability or flaw in the system that impacts the Buyer assets.
8. The Supplier should report out via CISA Coordinated Vulnerability Disclosure (CVD) managed by
Department of Homeland Security Cyber Infrastructure Response Team (CISA) any vulnerabilities which the Supplier discovers on their own to facilitate ease of access to disclosure information.
9. The Supplier shall collaborate with the Buyer to manage the threats and vulnerabilities reported by external agencies – especially CISA Emergency Directives, but may also include ICS-CERT, US-CERT, or MITRE organizations.
10. The Buyer may, at will, solicit the Supplier to assist the Buyer in evaluating the impact of vulnerabilities reported by federal agencies and determine whether the remediation or alternate mitigation prescribed by agencies may be incorporated into affected assets within the scope of supply.
11. The Supplier should respond to Buyer lines of inquiring regarding threats and vulnerabilities within 24 hours.
12. The Supplier should make a good will attempt to meet the turnaround time required by the governing agency or shall inform the Buyer when the turnaround time cannot be met within 24 hours.
13. The Supplier shall submit documentation that supports and aligns to the inventoried configuration baseline. The documentation shall include, as applicable:
a. User manuals that document use of asset(s) under scope of supply, user interfaces and features such as login logout, authenticator entry, changing default passwords, configuration setup, account setup instructions.
b. Operations and Maintenance manuals that explains routine maintenance that must be performed to assets(s) under scope of supply, how to restore factory defaults, how to recover from unexpected power loss, error code definitions, applying firmware updates, installing patches, and all other activities that are required to maintain the security of the information system and assets.
c. Tools, appurtenances, and media necessary to maintain the asset(s) in the scope of supply.
14. Binary files for firmware and configuration files installed on asset(s) in scope of supply in the native format and in a state that facilitates disaster recovery objectives.
15. The Supplier shall submit configuration settings in readable format whenever a configuration file cannot be provided.
16. Once the supplier receives approval of baseline artifacts, future The Supplier shall submit change notices to provide traceability to Buyer approved changes. The change notice identifier shall be referenced in revision history of affected artifacts in the configuration baseline documentation and test documents.
17. The supplier shall notify the Buyer when supporting documentation is unavailable or lacks sufficient detail for reaching a determination on compliance to security requirements. The Supplier shall document when vendor furnished documents (e.g., installation manuals, operational manuals) are not available for a digital asset.
18. Suppliers shall not connect Supplier-owned tools or media to any asset on the Buyer premises.
19. Supplier shall service assets at the Hanford site using tools, appurtenances, and media authorized by the
Buyer.
20. Supplier shall conduct surveillance of packages containing products that have been received by the
Government but are stored at supplier facility for two months or greater every two weeks to verify contents have not been breached.
21. The Supplier shall log surveillance results with specific attention to signs for unauthorized access.
22. The Supplier shall collaborate and cooperate in any Buyer or government inspection or audit for as long as the Buyer uses the Supplier’s service.
23. The Supplier Shall furnish require articles when requested from the Buyer.
24. The Supplier shall not obstruct any inspection or audit and shall be fully transparent in all work processes and business conduct as it relates to storage of government owned date.
Appendix C – Contractor Document Submittal Form (CDSF)
| 1 INTRODUCTION / BACKGROUND |
| 1.1 OBJECTIVE |
| 1.2 DESCRIPTION OF WORK – GENERAL |
| 1.3 DESCRIPTION OF WORK – SPECIFIC |
| 2 DELIVERABLES/SUBMITTALS |
| 2.1 Deliverables |
| 2.2 Submittals |
| 3 PLACE OF PERFORMANCE |
| 3.1 Onsite Work Location/Potential Access Requirements |
| 3.2 Site Access and Work Hours |
| 3.3 Badging |
| 4 REQUIREMENTS |
| 4.1 Engineering Requirements |
| 4.2 Environmental, Safety, and Health Requirements |
| 4.3 Quality Assurance Requirements |
| 5 ACCEPTANCE CRITERIA |
| 6 CONFIGURATION MANAGEMENT |
| 6.1 Configuration Management Requirements |
| 6.2 Applicable Standards |
| 6.3 Verification/Hold Points |
| 7 QUALIFICATIONS |
| 8 SPECIAL REQUIREMENTS |
| 8.1 Training |
| 8.2 Use of Government Vehicles |
| Not applicable to this PWS. |
| 8.3 Government Property |
| 8.4 Hanford System Access Requirements |
| 8.5 Electrical Components |
| 8.6 Section 508 of Rehabilitation Act Applicability |
| 9 ACCESS AUTHORIZATION/CLEARANCE REQUIREMENTS |
| 10 MEETINGS |
| 10.1 Meetings |
| 11 INTERFACE/NOTIFICATIONS |
| 12 APPENDICES |
File details come from the government source that posted it. Updated .