Addendum_No._5.pdf

P a g e 1 | 4

TO: All Proposers FROM: Sheila Hernandez, CPPB, FCCM, Senior Buyer DATE: June 8, 2026 RE: RFP 26-028-SH Utility Network Migration And Implementation Services

ADDENDUM #5

Bidders are hereby notified that this addendum shall be made a part of the above-named Request for Proposal and agreement documents. The items listed below are issued to add, modify, and/or clarify the solicitation document and agreement documents. The items shall have the same force and effect as the original bidding and agreement documents, and cost involved shall be included in the bid pricing. Bids, to be submitted, shall confirm with the addition and revision listed herein. Return this sheet with your bid response.

I. QUESTIONS

Q1. In Appendix C, E. Contract Labor Rates section, are we able to add to or modify the roles listed? If so, is it acceptable to add them in a separate excel spreadsheet or word doc attachment?

A1. Vendors must provide rates for the labor categories identified in the solicitation. Vendors may also propose additional labor categories, if applicable, and may include those rates as a separate attachment to their proposal.

Q2. Section 1 of 5.1.1 notes the following: "Engage Esri (as a subcontractor, if applicable) to perform system architecture design and performance assessment." Does this mean Esri engagement is optional, or Esri`s involvement a requirement?

A2. Engagement of Esri Professional Services is optional. References to Esri as a subcontractor are intended to recognize that some vendors may elect to leverage Esri resources for architecture assessment, performance optimization, ArcGIS Monitor implementation, or related activities.

The selected vendor remains responsible for delivering all required services and outcomes identified in the RFP, regardless of whether Esri Professional Services is engaged. Vendors may propose the approach they believe is most appropriate based on their qualifications, experience, and implementation methodology.

Q3. In Section 1 of 5.1.1, the section also notes "Engage Esri (as a subcontractor, if applicable) to stand up ArcGIS Monitor for system performance tracking." Does this mean Esri engagement is optional, or Esri`s involvement a requirement?

A3. Engagement of Esri Professional Services is optional. The same guidance provided in Question 2 applies to ArcGIS Monitor implementation and configuration activities.

Q4. Does KUA anticipate our project team members will access a KUA jump box / virtual machine to utilize the required software or does KUA expect equipment to have all required software installed locally?

A4. KUA can create a variety of connection solutions to accommodate remote vendor access. Provision of a jump box, if required, would be the responsibility of the vendor.

P a g e 2 | 4

Q5. What method of VPN connectivity does KUA plan to allow (for example: web-based TLS VPN like F5 Remote Access, desktop VPN client like Cisco AnyConnect, or other)?

A5. KUA can accommodate remote vendor access through industry standard VPN solutions or configure a site-to-site connection depending on the scope of the work required. Specific equipment, brand names, configurations or processes are confidential and would be made available to the successful bidder of the contract.

Q6. Will KUA provide a split-tunnel or full-tunnel VPN?

A6. KUA can accommodate remote vendor access through industry standard VPN solutions or configure a site-to-site connection depending on the scope of the work required. Specific equipment, brand names, configurations or processes are confidential and would be made available to the successful bidder of the contract.

Q7. Is transmission currently managed in the same Geometric Network as distribution?

A7. No. KUA's transmission assets are not currently modeled within the Geometric Network and are maintained separately from the electric distribution Geometric Network.

As described in the RFP, transmission assets will be migrated to the new GIS environment using a lift-and-shift approach and will remain outside of the Utility Network as part of this phase of the project.

Q8. Is fiber represented as network features today or simple GIS assets?

A8. Fiber is currently maintained as simple GIS assets and is not modeled as a network within the Geometric Network.

Q9. Does KUA anticipate migrating transmission or fiber to UN within the next 3-5 years?

A9. KUA has not established plans to migrate transmission or fiber assets into the Utility Network within a specific 3-to-5-year timeframe. While KUA may evaluate future enhancements to transmission or fiber asset management, no decision has been made regarding Utility Network implementation for either dataset.

Future transmission or fiber Utility Network modeling is not included in the current scope and should not be assumed.

Q10. Will future systems (ADMS, OMS, SCADA, telecom management systems) require a common network model to utilize fiber and transmission assets?

A10. KUA has not established specific requirements regarding the use of a common network model by future systems such as ADMS, OMS, SCADA, or telecommunications management platforms.

As part of the implementation, KUA expects the selected vendor to provide recommendations regarding system architecture, data modeling, and configuration approaches that preserve future flexibility and support potential integration requirements. Vendors may identify opportunities to support future flexibility and interoperability where practical; however, no specific common network model requirements have been defined as part of the current scope.

Q11. Are transmission and fiber features edited by the same GIS users?

A11. Yes. Transmission and fiber features are currently edited and maintained by the same GIS users.

Q12. Section 3.2.4 states "Ensure interoperability with other operational Tools / Systems."

Please describe the operational tools KUA is desiring AUD to integrate with other than GIS and

EAM.

A12. In addition to GIS (Utility Network) and Cogsdale FMS, KUA may elect to include Pendulum Media as the primary integration platform supporting compatible units, asset

P a g e 3 | 4 positions, and design-to-workflow data exchange. If included, the selected vendor shall support integration and coordination activities associated with the Pendulum Media solution.

AUD is also expected to support field mobility applications such as ArcGIS Field Maps and Survey123.

Q13. In Section 3.2.5, what is KUA asking for when they say: "Modernizing outdated CUs and templates where appropriate"?

A13. KUA is requesting that the vendor evaluate existing compatible units (CUs), favorites, composite favorites, templates, and related design configuration elements during migration to

AUD.

The intent is not to redesign KUA's engineering or construction standards, but rather to ensure that CUs and design resources are organized and configured in a manner that promotes efficient use within AUD.

Where appropriate, the vendor may recommend improvements to favorites structures, composite favorites, templates, design libraries, and related configuration elements to improve usability, consistency, maintainability, and alignment with AUD workflows. Decisions regarding changes to KUA's engineering standards, construction practices, or underlying compatible unit definitions will remain subject to KUA review and approval.

Q14. In Section 3.2.5, please elaborate what KUA is asking for in the following statement:

"KUA’s historical and operational design standards are accurately represented in AUD"?

A14. KUA's intent is that existing operationally relevant design standards, workflows, and practices be reasonably represented within AUD where supported by the platform and where it is practical to do so.

KUA generally prefers to align AUD with current business processes and design practices where feasible; however, KUA recognizes that some workflows, configurations, or standards may need to be modified to align with AUD capabilities, Utility Network requirements, or implementation best practices.

Q15. In Section 3.2.4, please elaborate on what KUA is asking for when you ask: "Document details of integrations with GIS (Utility Network), Cogsdale FMS, and Pendulum Media CU/asset position interface. Include only non-standard configuration, data mapping, workflows, testing, and validation details."

A15. KUA is requesting detailed implementation-level documentation of all integrations between AUD, the Utility Network, Cogsdale FMS, and Pendulum Media to support long-term maintainability and in-house support of the solution.

This includes documentation of only non-standard or solution-specific elements such as custom configuration, data mappings, transformation logic, workflow rules, integration endpoints, and exception handling procedures.

For each integration, vendors shall also document:

* Data flow direction and frequency

* Field-level mapping between systems

* Any custom rules, scripts, or middleware transformations

* Workflow triggers and automation logic

* Testing scenarios and validation procedures, including end-to-end integration testing

The intent is to ensure KUA has sufficient technical and operational documentation to independently support, maintain, and extend integrations following project completion.

P a g e 4 | 4

Q16. In Section 3.2.6, is the intention that the bidder would conduct comparisons between Field Maps and other Field As-Builting tools?

A16. KUA’s intent is for the selected vendor to evaluate and recommend a field mobility solution that supports as-built capture, redlining, design review, and field data collection workflows.

Esri Field Maps is anticipated as a primary baseline solution; however, vendors may propose alternative third-party tools where they provide clear functional, operational, or integration advantages.

The expectation is not a formal market comparison of all available tools, but rather a solution-focused assessment to ensure the selected approach meets KUA’s workflow, data capture, and integration requirements in the most effective manner.

Q17. Section 3.3.1: Asset position is mentioned several times throughout the RFP, not just section 3.3.1. Is KUA storing the x, y, z geographical location of assets? If so, where is it stored?

A17. KUA maintains asset spatial location (x, y, and where applicable z coordinates) within the GIS environment as the system of record for geospatial asset data.

Other enterprise systems may receive and store asset position information to support work management, and other operational workflows. However, these systems do not serve as the authoritative source for spatial asset geometry.

Q18. What file formats do Pendulum accept? Is there a pre-defined message schema for Pendulum?

A18. Please contact Pendulum Media for response to these questions.

Q19. Is there an expectation to write against Pendulum APIs? Or provide a message queue or file location for messages to be picked up?

A19. Please contact Pendulum Media for response to these questions.

Bidder(s) must acknowledge receipt of this addendum by signing this form below and returning it with your bid response.

Acknowledgment is hereby made of Addendum #5 to project RFP 26-028-SH Utility Network Migration And Implementation Services

Bidder Signature Date

Bidder Printed Name Company Name

This addendum is issued to provide additional information, clarification, corrections, additions, deletions and/or to answers questions concerning the above referenced solicitation. All information provided in this addendum is incorporated into the solicitation document as if set forth therein. All other parts of the solicitation have been maintained as originally distributed. This addendum supersedes any verbal or other instructions given to any proposer qualified to respond pursuant to the requirements set forth in the solicitation document.