Solicitation Addendum 1.docx

SOLICITATION ADDENDUM ONE

REMOVAL AND REPLACMENT OF ALL REFERENCES TO NDEE, QUESTIONS AND ANSWERS, REVISED SECTION V.D, REVISED SECTION V.D.2.a, REVISED SECTION V.F, REVISED SECTION VI.A.2, REVISED COST PROPOSAL

SOLICITATION NUMBER: 121442 O5

DWEE IIS Modernization Opening Date: July 29, 2025, 2:00 PM CST Addendum Effective Date: July 11, 2025

Removal and Replacement of all References to NDEE

Effective July 1, 2025, the Nebraska Department of Natural Resources and the Nebraska Department of Environment and Energy merged to create the Nebraska Department of Water, Energy, and Environment (DWEE). All references to “Nebraska Department of Environment and Energy” or “NDEE” within the solicitation and all related attachments shall be removed and replaced with “Nebraska Department of Water, Energy, and Environment” and “DWEE” respectively.

Questions and Answers

Following are the questions submitted and answers provided for the above-mentioned solicitation. The questions and answers are to be considered as part of the solicitation. It is the responsibility of bidders to check the State Purchasing Bureau website for all addenda or amendments.

Scrutinized company means:

(a) Any company organized under the laws of a foreign adversary or having its principal place of business within a foreign adversary, and any subsidiary of any such company; or

(b) Any company owned in whole or in part or operated by the government of a foreign adversary, an entity controlled by the government of a foreign adversary, or any subsidiary or parent of any such company; or 1

(c) Any company that sells to a public entity a final technology-related product or service that originates with a company described in (a) or (b) above, without incorporating that product or service into another final product or service.

For example:

- Number of tables in the DB2 database.

- Number of records in each table (or number of records in the largest tables).

- Number of stored procedures, functions, triggers, and views in the DB2 database.

- Number of lines of RPG code.

Note: we understand from the pre-solicitation conference that this may be difficult. We suggest taking samples of the ~400 RPG programs to be converted. For example, you might select 10 small programs, 10 medium programs, and 10 large programs and provide an average lines of code (LOC) for the small, medium, and large RPG programs.

Due to the nature and structure of the existing system, an accurate estimate of the total lines of source code is not feasible at this stage. This is because the code base may include D specs, commented lines, blank lines, and cross-program dependencies are not necessary that make a precise line count impractical without a detailed code inventory and analysis.

It has been determined that the largest amount of lines of source code is almost 5000 and the smallest could be approximately 300. Again, either one of the programs could include several to hundreds of lines of code that are not required to be converted.

Please refer to the answer to Question #21 above.

1. Average response time for key business transactions

2. Concurrent user load handling (scalability)

3. System throughput for critical processes

4. Network latency and impact on distributed components

5. End-user satisfaction through usability testing

We will work with stakeholders to identify a representative set of high-volume and high-importance transactions in the legacy system and establish baseline measurements for them.

The modernized solution will be tested under comparable workloads to ensure equal or improved response times, improved scalability under peak load, and better overall maintainability.

It has been determined that the largest amount of lines of source code is almost 5000 and the smallest could be approximately 300. Again, either one of the programs could include several to hundreds of lines of code that are not required to be converted.

in the Solicitation Conference Call (new budget constraints, etc.) If true:

a. what has changed, and

b. what is the percentage likelihood that an award will ultimately be made, and if so,

c. what criteria would need to be met, including any new parameters?

The Department reviews its fiscal standing each year, and has to adhere to State budget constraints. The percentage of likelihood to award will depend on the submitted project costs.

(potentially due to budget constraints, as mentioned), which may necessitate postponing the project for several years, we would like to understand the procurement process moving forward. Specifically:

a. would any future award for this project, once budget becomes available, be based on the results and vendor selections from the current RFP process, or would the State initiate an entirely new RFP process at that time?

b. we seek clarification on whether the successful bidders of this current RFP would maintain their status for a future award under such circumstances, or if the entire bidding process would be restarted.

If the State withdraws this Solicitation with no awarded bidder, the State would be required to release a new solicitation.

projects typically necessitate changes to CLs for proper functionality (e.g., calling new PHP programs instead of existing RPG programs), are vendors expected to:

a. include CL modification as part of their proposed solution(s)? If so,

b. will the RFP be amended to clearly outline these expectations for all vendors?

During the creation of Attachment B, it was determined that converting CLPs is not necessary, so were not included in the spreadsheet. But Appendix A was not modified to reflect this change.

REVISED SECTION V.D

Section V.D. of the Solicitation will be updated as follows:

D. SCOPE OF WORK

The Vendor will be responsible for the following tasks. Tasks 1 - 3 must be completed successfully in order for the Vendor to be considered for performance of Tasks 4 – 12. DWEE reserves the right to move forward with or discontinue the project following performance of Tasks 1 – 3.

REVISED SECTION V.D.2.a

Section V.D.2.a of the Solicitation will be updated as follows:

a. Conduct a thorough analysis and discovery of all display screens, CLP, RPG-ILE, free-form RPG programs and modules. Provide within the analysis and discovery report the number of lines of source code for each program and identify the lines of code that will require conversion for modernization.

REVISED SECTION V.F

Section V.F of the Solicitation will be updated as follows:

F. DELIVERABLES

The Selected Vendor will provide the following deliverables. Deliverable 1 must be provided successfully in order for the Vendor to be considered for delivery of Deliverables 2-6. Costs for Deliverables 2-6 may be negotiated between DWEE and the awarded Vendor upon successful delivery of Deliverable 1. DWEE reserves the right to move forward with or discontinue the project following delivery of Deliverable 1.

REVISED SECTION VI.A.2

Section VI.A.2 of the Solicitation will be updated as follows:

TECHNICAL RESPONSE

The Technical Response section of the solicitation response should consist of the following subsections:

Understanding of the Project Requirements Demonstrate understanding of project requirements as listed in Section V, subsection B C.

Project Timeline Provide a detailed project timeline for satisfying each task tasks 1 – 3, described in Section V, subsection C D and presenting each deliverable 1 listed in Section V, subsection E F.

Proposed Development Approach and Workplan Describe the approach for assessing, modernizing, and migrating RPG-ILE and RPG Free Format programs to a language supported by Zend Server. performance of Tasks 1 – 3 and composition of a report detailing findings from performance of Tasks 1 – 3.

Equipment and Software Description Provide details on equipment and software needed to complete the tasks 1 – 3 and present the deliverables deliverable 1 as listed in Section V, subsection E F.

Training Plan Provide a plan and approach to training DWEE personnel on usage of the final product

Quality Assurance and Post- Project Support Commitment Provide and detail commitment for post-deployment support and maintenance

REVISED COST PROPOSAL

NDWEE IIS Modernization Cost Proposal will be updated as follows:

NDEE DWEE IIS Modernization Cost Proposal

Request for Proposal Number 121442 O5

Bidder Name: ____________________________________

Bidder must provide a fixed cost for each Deliverable 1 listed below. Deliverable 1 is comprised of Tasks 1-3 as identified in Section V.D.1-3 in Solicitation 121442 O5 and must be completed successfully for the Vendor to be considered for performance of the remainder of the project.

Costs for Deliverables 2-6 may be negotiated between DWEE and the Vendor upon successful delivery of Deliverable 1. DWEE reserves the right to move forward with or discontinue the project following delivery of Deliverable 1.

All prices, costs, and terms and conditions submitted in the proposal shall remain fixed and valid commencing on the opening date of the proposal until the contract terminates or expires.

A completed Cost Proposal must be submitted with the proposal response.

4: Comprehensive technical documentation for the newly developed system, including all business logic and processes, system features, operating procedures, and regular user maintenance protocols. Conduct Training sessions for both developers and end-users.

Optional/Value-Added Services Bidder may list optional and/or value-added services within the chart below or in bidder’s preferred format along with corresponding prices and/or rates. Prices and/or rates submitted as part of this section will not be evaluated, but will be considered binding upon Contract Award. Bidder may add more rows to the chart below if needed.

This addendum will be incorporated into the solicitation.

SPB Form 26 Last Revised 4-17-2025