DRAFT_PWS_FOR_SOURCES_SOUGHT_PURPOSES_1.pdf

HYDROLOGICAL DATABASE (HDB) SUPPORT SERVICES IDIQ

DRAFT PERFORMANCE WORK STATEMENT

1. SCOPE:

1.1. OBJECTIVE:

The objective of this performance-based contract is to maintain, support, and further develop the Bureau of Reclamation's Hydrological Database (HDB) through the Contractor's provision of services for on-call technical support, troubleshooting of HDB malfunctions, development of modifications to HDB, support of HDB enhancements, and the development, documentation, and distribution of software applications that interface with

HDB.

1.2. BACKGROUND:

HDB is currently used in production in the Upper Colorado Basin Region, in all four of its area offices, in the Lower Colorado Basin Region in the Boulder Canyon Operations Area and Yuma Area Offices, in the Missouri Basin and Arkansas-Rio Grande-Texas Gulf Region in the Eastern Colorado Area Office, in the California Great Basin Region in the Lahontan Basin

Area Office and in the Klamath Basin Area Office. Each of these offices support separate instances of HDB for the collection and storage of vital hydrological data within their operational jurisdiction to aid in decision support and reporting for Reclamation facilities managed within each of these offices.

The HDB system is a critical decision support tool for day-to-day operations of many of

Reclamation’s major water storage and distribution facilities throughout the Western

United States. HDB is critical for enabling and supporting ongoing modeling activities that include (but are not limited to) basin inflow forecasting, National Environmental Policy Act

(NEPA) and Endangered Species Act (ESA) compliance processes, long- and mid-term modeling and planning efforts, and day-to-day operational control and management. HDB is also utilized to support Reclamation’s website and other publicly available data portals such as Reclamation Information Sharing Environment (RISE), and public and internal

Application Programming Interfaces (APIs).

The HDB is the foundation for Reclamation's Database of Record. As conceptualized by the

Database of Record defining document, the driving vision for the Hydrologic Database is to:

• Consolidate data previously existing in various systems and personal spreadsheets.

• Assure complete and consistent data collection and storage; documentation of data sources.

• Provide historical information on other existing HDB data versions including information on when the data was either used or available for use.

• Perform as a means of quality control.

• Allow the user access, at any time interval, to the original source data for calculated or summarized data

• Provide for an automated generation of time-aggregated summary data as well as automated computations that compute data parameters based on collected inputs.

Reclamation managers are often interrogated formally or informally regarding the basis for operational decisions - decisions that are usually based on data such as forecasts, flows, available water supply and downstream water and/or energy demands. Reasonable explanation of decisions requires maintaining the exact data considered in the decision and being able to reproduce the overall state of the system and retrieve forecast information available at the time the decision was made. Enhanced capability to document the basis for the past decisions is urgently needed to assist Reclamation's defense in litigation and other processes.

Development of the database of record will facilitate Reclamation's continued ability to rely on and interpret their data in order to make sound operational decisions, provide an indisputable record of data used to make past decisions, and provide a complete record of best available historical and forecast data for research proposed and policy development.

The HDB system is comprised of the Oracle based HDB databases combined with a collection of software applications (computer programs) that are set up to automatically collect and store a variety of operational and hydrologic data from various data sources. Software applications within the system also allow operational staff to access the data for quality control as well as hydrologic modeling studies, water accounting efforts, and day-to-day operations and modeling of dams, reservoirs and related assets and features. Some of these software applications collect and store data in HDB while others allow data to be retrieved from HDB and displayed in ways that assist operations staff and the public to interpret the state of the hydrologic system.

2. REFERENCES:

2.1. Hydrological Database - Bureau of Reclamation

http://hydrodb.net

2.2. National Environmental Policy Act

http://www.epa.gov/nepa

2.3. Endangered Species Action

https://www.law.cornell.edu/wex/endangered_species_act_(esa)

3. DEFINITIONS:

3.1. Qualified Contractor Personnel: means those Contractor employees directly performing work under this contract who collectively possess and maintain all of the following skills, capabilities, and knowledge to provide a high-quality level of technical support services.

Individual personnel assigned to specific tasks must have the relevant qualifications for those tasks; however, the full set of qualifications may be met and maintained by the contractor’s team as a whole throughout the life of the contract. These qualifications http://hydrodb.net/ http://www.epa.gov/nepa https://www.law.cornell.edu/wex/endangered_species_act_(esa) include:

3.1.1. High level of knowledge with regard to the HDB database structure, including database relationships in HDB, including DECODES and the Computational

Processor.

3.1.2. Full understanding of the HDB objectives with respect to time-series data management including, but not limited to: computation management, interval data consistency, model data management, validation and quality assurance, etc.

3.1.3. Expert-level proficiency in Oracle database Operations and Maintenance and programming, as well as other computer programming languages such as JAVA, C, python, C#, Perl, and VB.net.

3.1.4. Ability to develop and support internal and external tools to access and modify data through API and specialized software tools.

3.1.5. Demonstrated ability to develop or support tools in full compliance with federal cybersecurity standards, including adherence to Software Development Life Cycle

(SDLC) and Secure Software Development Framework (SSDF) practices, and working knowledge of NIST and FISMA requirements.

3.1.6. Ability to adapt to emerging technologies and evolving technical requirements over the life of the contract, including acquiring and applying new programming languages, database platforms, data visualization tools, and cybersecurity protocols.

3.1.7. Maintenance of certifications and training necessary to support future IT systems and hydrological data management technologies relevant to HDB operations.

3.2. Call: refers to any request for technical assistance or support initiated by Reclamation personnel through approved communication channels. This includes phone calls, emails, instant messages, and submissions through the designated online issue-reporting tool. A call may involve routine inquiries, troubleshooting requests, or urgent issues requiring immediate attention.

3.3. Urgent Call: means any request for technical assistance that involves system outages, critical data loss, cybersecurity incidents, or issues that significantly impact operational decision-making. Note: While the Minimum Acceptable Quality Level for urgent calls is two

(2) hours, the Contractor shall make every reasonable effort to immediately engage in resolving urgent issues upon receiving the call. Reclamation will flag any urgent calls, messages, or submissions as “urgent”.

3.4. Responded Call: A call is considered responded to when the Contractor initiates direct engagement with the original caller and begins steps toward resolving the reported issue or inquiry.

3.5. Task Order: means a written order issued by the Contracting Officer under this IDIQ contract that authorizes specific work, deliverables, and performance requirements.

4. HOURS OF AVAILABILITY:

Reclamation’s normal operating hours are 8:00 a.m.–5:00 p.m., Monday through Friday, Mountain

Standard Time, excluding Federal Holidays. The Contractor shall be available to provide on-call support during these hours as specified in this Performance Work Statement. For urgent matters, Reclamation may contact the Contractor outside normal business hours, and the Contractor shall provide assistance within the response timeframes defined in the Performance Requirements Summary. The Contractor may perform work at its convenience, provided that all required response and resolution timeframes are met. Only time spent performing authorized work is billable.

5. TASKS:

All tasks described herein, including development, maintenance, compliance, and documentation, shall be performed by qualified Contractor personnel as defined in Section 3.1. The tasks listed in this section define the scope of services that may be ordered under this IDIQ contract. Performance of any task occurs only upon issuance of a Task Order by the CO and shall be carried out as needed consistent with the requirements of the applicable Task Order.

5.1. Provide On-demand Technical Support: Provide on-demand HDB technical support to

Water Resources users. These services shall be provided by qualified Contractor personnel during normal Reclamation business hours and within the performance standards outlined in section 7. Examples of on-demand technical support include but are not limited to the following:

5.1.1. Provide technical support in the installation and configuration of HDB and all supporting applications for instances of HDB.

5.1.2. Consult with Reclamation on identification of problems and solutions, including development of new functional requirements for the database instances.

5.1.3. Provide information to Reclamation by way of informational meetings, and/or developing additional technical documents as requested.

5.1.4. Respond to emails, phone calls, and requests for information and/or assistance in any matters dealing with HDB instances. These requests may include but are not limited to adding new data types, creating or modifying computations, restoring data, decoding GOES satellite data, troubleshooting scripts, etc.

5.1.5. Provide support in relation to HDB connections to RiverWare, or similar modeling platform, through connection packages and procedures as requested.

5.1.6. Provide support for server operating systems (currently Red Hat Enterprise Linux) as requested for instances of HDB.

5.1.7. Provide documentation of the number of hours worked per month by task order.

Provide monthly meetings for technical support team status reports and delineate the work performed on the various HDB instances.

5.1.8. Provide on demand support for other issues that may arise over the lifecycle of the HDB System.

5.2. Database System Maintenance and System Malfunction Resolution Services:

Troubleshoot, diagnose, and solve software and database management problems involving

HDB system malfunctions as expeditiously as possible and within the performance standards outlined in section 7. Examples of database system maintenance and system malfunction resolution services include but are not limited to the following:

5.2.1. Support database strategic planning and assistance to Reclamation with respect to currently available and supported products and versions of the database.

5.2.2. Install and test modifications and regular updates to operational systems and applications to keep functioning and operational both the production and test/development versions of the HDB databases and all installed applications.

5.2.3. Maintain all existing loader programs and applications on database instances, and new loader programs and applications as they are implemented. This will include the open source TSTool software data loaders and all stored procedures and packages for various external loading applications.

5.2.4. Provide system maintenance and system malfunction resolution services for other issues that may arise over the lifecycle of the HDB System.

5.3. HDB Development, Coordination and Documentation: Develop, test, and integrate HDB enhancements; maintain code and documentation; coordinate with stakeholders; support data tools; ensure secure knowledge transfer and consistent operations across all instances.

Examples of HDB development, coordination, and documentation include but are not limited to the following.

5.3.1. Develop enhancements to HDB as requested by Reclamation's HDB Water

Resources Group to be transferable, functional, and available to other instances of

HDB.

5.3.2. Install and test available enhancements and regular updates to production and test/development databases, systems and applications at each HDB instance. All enhancements and modifications prepared by contractor shall be fully tested on a test environment maintained with the Reclamation network. Reclamation will be responsible for maintaining the test environment and access to the contractor for this purpose. Documentation of successful testing shall be submitted to

Reclamation. Only after Reclamation review of testing results and approval by

Reclamation shall contractor install enhancements or modifications onto the HDB production environment.

5.3.3. Integrate HDB enhancements and code modifications into the HDB source code and database scripts baseline.

5.3.4. Maintain and support the HDB source code and the computation processor algorithms for HDB to be consistent as possible with other HDB installations.

5.3.5. Coordinate development of programs/systems used for data acquisition, data logging, feedback control, and configuration (currently OPENDCS) with the other participating entities.

5.3.6. Documentation of new developments shall be provided with new deliverables.

Maintain all other documentation related to HDB, OpenDCS, the Computational

Processor, data loaders, etc.

5.3.7. The contractor shall develop and maintain a comprehensive, transferable knowledge base that includes system architecture documentation, annotated source code, configuration guides, and training materials. This knowledge base shall be structured to support onboarding of future contractor staff or federal personnel and maintained in a secure, centralized location accessible to authorized Reclamation staff.

5.3.8. Provide download capabilities of HDB installation scripts, documentation and application software on the HDB web site.

5.3.9. Attend and participate in conference calls, user groups, team, or other impromptu meetings. This should include the HDB User Group meeting (usually 2 days annually).

5.3.10. Coordinate development of programs/systems used for data loading into HDB

(currently TSTools) with other participating entities.

5.3.11. Coordinate Computational Processor Developments.

5.4. HDB Data Access and Editing Tools: Develop, maintain, and enhance tools for accessing, editing, and sharing HDB data. This includes HDB-POET source code updates, public and internal API development, visualization tools for data communication, and automated scripts for stakeholder data sharing. Examples of HDB data access and editing tools include but are not limited to the following.

5.4.1. HDB-POET

5.4.1.1. As requested by Reclamation, perform development tasks on HDB-POET application source code and provide access to installation scripts for

Reclamation staff.

5.4.1.2. Produce enhancements to the source code to meet new specifications and guidelines requested by and in collaboration with Reclamation staff.

5.4.2. API

5.4.2.1. Public API development and maintenance

5.4.2.2. Internal API development and maintenance

5.4.3. Visualization Support and Development – Provide development and support for visualization and data exploration tools to assist in communication with the public.

5.4.4. Automated Data Sharing – Maintain and modify scripts/applications to allow data sharing with Reclamation stake holders.

5.4.5. Data editing tools - Provide development and support for data editing tools to assist in quality assurance and control of HDB data

5.5. Maintain Compliance with Department of Interior Cybersecurity Requirements: All databases, tools, applications, and data developed or maintained under this contract shall comply with the current Department of Interior cybersecurity policies and applicable federal requirements. Contractor solutions must implement Secure SSDF and SDLC practices as applicable and follow NIST and FISMA standards in effect at the time of performance. Reclamation Cybersecurity personnel shall be consulted on an as-needed basis to confirm applicable standards and requirements.

5.6. Data, Reports, and Deliverables: The contractor shall prepare and submit monthly status reports to all participating Reclamation Offices. These reports shall contain the following information:

5.6.1. Dates and approximate length of time (hours) required by contractor to resolve each incident for which on-demand HDB technical support services rendered by

Contractor to Reclamation under this contract.

5.6.2. Description of the issues involved for each reported incident requiring on-demand

HDB technical support and the actions taken by the contractor to achieve a resolution of the reported incident.

5.6.3. Details for all authorized Contractor travel associated with this contract such as dates, times, locations, specific costs, purposes of travel, and what contributions the Contractor provided as a result of the travel.

5.6.4. For specific tasks described in each task order under this contract, the report should include the task order, a brief description of the overall task, and the status of performance and completion of the task, including a determination by the

Contractor as to whether or not the task will be completed by the deadline specified in the associated task order.

5.6.5. Task orders issued under this contract may include additional reporting requirements beyond those specified within this performance work statement.

6. TASK ORDERS

6.1. The Contractor shall only perform tasks under this contract after the issuance of task orders.

6.2. It is anticipated that all task orders will be firm-fixed price.

6.3. Regions referenced in Section 1.2 above are authorized to use this IDIQ provided the work is in line with the PWS.

6.4. The frequency of task orders are anticipated on a yearly basis but could vary based on need.

6.5. When the Government requires a task order, the Contract Specialist or Contracting Officer will submit a Request for task order Proposal to the Contractor. The Request for task order

Proposal does not constitute an Order or Obligation. The Contractor shall not commence performance of any work or incur any costs related to the requirement until such time that a task order is signed and issued by the Contracting Officer. The Government’s issuance of and the Contractor’s response to a Request for task order Proposal does not guarantee the issuance of a task order.

6.6. Upon receipt of the Contractor's proposal, the Government will evaluate the proposal and negotiate with the Contractor as needed. If the Government determines that negotiations are needed, then the Contractor shall negotiate in good faith to arrive at a mutually agreeable outcome and do so as expeditiously as practical.

6.7. Pricing for “materials” as defined in FAR 16.601. If this includes travel, regardless of whether the task order is Firm-Fixed-Price or Time-and-Materials, travel will be reimbursed at cost and in accordance with FAR 31.205-46 and the Federal Travel Regulation. The amount proposed should be a not-to-exceed estimated amount with supporting documentation with the number of travelers, common carrier fares, local transportation costs (e.g.

Privately-Owned Vehicle reimbursement), rental car expenses, per diem (i.e. lodging and subsistence), and miscellaneous & incidental expenses.

7. PERFORMANCE REQUIREMENTS SUMMARY: The table below specifies the standard for satisfactory performance of the tasks identified in this performance work statement. Inspections and evaluations will be based on these standards and will inform the Government’s Quality

Assurance Surveillance Plan (QASP) and Contractor Performance Assessment Reporting System

(CPARS) ratings.

Task Description Performance Indicator Performance Standard Minimum Acceptable Quality Level (MAQL)

5.1 Provide On-Demand

Technical Support to Reclamation users

Timing of responses (engagement and initiation of resolution) to calls for technical assistance, questions, and support.

75% of all non-urgent calls received after 3:00 p.m. MST or outside normal operating hours must be responded to by qualified Contractor personnel within two (2) hours of the start of the next normal operating period.

50% of all non-urgent calls received before 3:00 pm MST are responded to immediately by qualified Contractor personnel.

25% of all non-urgent calls received before 3:00 pm MST are responded to within two (2) hours by qualified Contractor personnel.

Remaining 25% of non-urgent calls (regardless of when they are received) are responded to within the timeframes defined in the MAQL.

All non-urgent calls must be responded within the next business day.

All urgent calls must be responded to by qualified Contractor personnel within two (2) hours of the call, regardless of when they are received.

5.2 Troubleshoot, diagnose, and

resolve HDB system malfunctions immediately after they occur.

Time to diagnose and resolve reported HDB system malfunctions.

1) 75% of malfunctions diagnosed by qualified Contractor personnel within 24 hours and resolved within 48 hours. 2) 25% of more complex malfunctions diagnosed within 24 hours and resolved within 96 hours.

All reported malfunctions shall be resolved within 4 business days unless extenuating circumstances exist.

5.3 Perform development, coordination, and documentation tasks as specified in task orders.

Completion and delivery of task order-specified deliverables.

Deliverables inspected, accepted, and delivered on time by qualified Contractor personnel.

90% of all task order deliverables delivered on time and in acceptable form.

5.4 Develop and maintain HDB

data access and editing tools, including APIs and visualization tools.

Availability, functionality, and compliance of tools.

Tools updated and maintained per task order; all work performed by qualified Contractor personnel

95% of tasks completed within required timeframe in acceptable form by Reclamation.

5.5 Maintain compliance with

Department of Interior and federal cybersecurity requirements for all contract activities and deliverables.

Documented adherence to SSDF, SDLC, NIST, and FISMA standards.

100% compliance for all deliverables and activities.

Provide evidence of corrective action within 30 days of any finding to prevent escalation to a POA&M.

Remediate or seek Risk Acceptance for any cybersecurity findings that result in a POA&M within 90 days of the published finding.

5.6 Prepare and submit reports

and deliverables.

Timeliness and completeness of reports.

Reports include all required details, are understandable, and submitted on time by qualified Contractor personnel.

90% of reports delivered on time and accepted without revision.