Utility Network Migration And Implementation Services

Location:	Florida
Posted:	May 15, 2026
Due:	Jun 12, 2026
Agency:	Kissimmee Utility Authority
Type of Government:	State & Local
Category:	D - Automatic Data Processing and Telecommunication Services
Solicitation No:	RFP 26-028-SH
Publication URL:	To access bid details, please log in.

Main

Agency
Kissimmee Utility Authority

Status
Active

Fiscal Year
2026

Primary Contact
Sheila Hernandez

Title
Utility Network Migration And Implementation Services

Secondary Contact
Jennifer Grieves

Number
RFP 26-028-SH

Tertiary Contact

Type
Request for Proposal

Department
Operations

Online Submissions
Yes

Project Estimate

Piggyback Solicitation
No

Insurance Required
Yes

Bid Bond Required
No

Bid Bond Amount

Performance Bond Required
No

Performance Bond Amount

Construction Bond Required
No

Construction Bond Amount

Scope of Services
The Kissimmee Utility Authority (KUA) is seeking qualified and experienced firms to provide comprehensive Utility Network Migration and Implementation Services. The selected Contractor shall be responsible for planning, designing, configuring, migrating, and implementing KUA’s utility network system into a modernized platform.
Services shall include, but are not limited to:

Assessment of KUA’s existing network, data, and system architecture

Development of a detailed migration and implementation plan, including timelines, risk mitigation, and resource allocation

Data conversion, validation, and migration from legacy systems to the new utility network environment

System configuration, integration, and customization to meet KUA’s operational requirements

Testing, quality assurance, and performance validation of the implemented system

Training of KUA staff and provision of documentation for system use and maintenance

Post-implementation support, troubleshooting, and knowledge transfer
The Contractor shall ensure minimal disruption to ongoing operations, maintain data integrity and security, and deliver a fully functional, scalable, and compliant utility network solution aligned with industry best practices.

Dates(All times are listed as EST )

Broadcast Date
4/21/2026 12:00 PM EST

Question End Date
5/8/2026 2:00 PM EST

Sample Due Date

Due Date
6/12/2026 2:00 PM EST

Bid Opening Date

Question End Date Reminder Notification
1 Day(s)

Sample Due Date Reminder Notification
0 Day(s)

Due Date Reminder Notification
1 Day(s)

Pre-Bid Meetings

Total: 0 (All times are listed as EST )

Date

Time

Mandatory

Location

Shortlist Meeting

Total: 0 (All times are listed as EST )

Date

Time

Location

Documents

Total: 4

Type	Name	Description	File Type
Solicitation Document	RFP 26-028-SH UN Migration Solicitation Documents.pdf	RFP 26-028-SH Full Solicitation Document Package	PDF
Addendum	Addendum No. 1.pdf	Addendum No. 1	PDF
Addendum	Addendum No. 2.pdf	Addendum No. 2	PDF
Addendum	Addendum No. 3.pdf	Addendum No. 3	PDF

Quote/Bid

Zones
Total: 0

Zone

Groups
Total: 0

Group

Quote/Bid Items

Total: 0

Required

Group

Make

Model

Description

Quantity

Unit of Measure

Price/ Percent

Type

Additional Quote/Bid Items Fields

Display Options Spreadsheet Section	No	Display Image and Specifications Hyperlink Fields	No
Display Build Sheet File Upload Field	No	Display Options File Upload Field	No
Require Build Sheet File to be Uploaded	No	Require Options File to be Uploaded	No
Display Lead Time Field	No	Display Standard Packaging Field	No

Delivery Date
None

Required Files to be Uploaded by the Vendor
RFP Response
Pricing Sheet (Excel)

Shipping
FOB Destination

Terms and Conditions
See KUA`s Terms and Conditions
Provide Supplier`s Terms and Conditions

Include Shipping in Price of Items
No

Display Bid Tabulation to Vendors
No

Display Vendor Submissions to Vendors
No

View Vendor Submissions while Bid Solicitation is Active
No

Allow Options File to be Updated after Due Date
No

Allow Post Due Date Submission
No

Questions & Answers

Total: 34

Question	Date Asked	Answer	Date Answered
Good afternoon, Can the 100% performance bond be reduced or removed or replaced with payment retainage? Thank you, Garrett Hopkins Proposal Manager WSP Inc.	4/29/2026 2:17:53 PM	No, KUA will not reduce, remove, or replace the 100% performance bond requirement.	5/1/2026 1:30:10 PM
Good afternoon, Can the 100% performance bond be reduced or removed or replaced with payment retainage? Thank you, Garrett Hopkins Proposal Manager WSP Inc.	4/29/2026 3:23:00 PM	See Addendum No. 1	5/1/2026 1:30:29 PM
Of the listed Web Maps, Web Mapping Applications, Feature Services, and Dashboards, how many of these items is KUA looking for support in migrating to Experience Builder and/or the UN?	5/1/2026 2:54:56 PM	KUA’s inventory of web maps, applications, feature services, and dashboards represents the current state of the ArcGIS Enterprise environment. KUA does not expect a one-to-one migration of all items to Experience Builder or the Utility Network. As outlined in Section 3.1.3, the vendor shall develop and execute a Web & Mobile Enablement Plan that includes assessing the existing inventory, identifying redundant or obsolete items, and recommending consolidation, retirement, reconfiguration, or rebuild approaches as appropriate. Based on this assessment, a subset of prioritized web applications will be selected by KUA for migration or rebuild under this scope. KUA reserves the right to negotiate additional services or scope related to migration, rebuild, and/or support efforts as needed during implementation into the contract’s SOW. In this context, “support” for migrating legacy Web Upbuilded applications includes a collaborative approach between the vendor and KUA staff. KUA staff may lead or independently rebuild lower complexity applications using vendor provided standards and guidance, while the vendor is expected to support and/or lead more complex efforts, including advanced configuration, custom development, integrations, and alignment with Utility Network workflows. Support also includes technical guidance, standards development, and knowledge transfer.	5/13/2026 2:18:27 PM
What does KUA consider "support" for moving legacy Web App Builder apps to Experience Builder?	5/1/2026 2:55:16 PM	Please see previous answer.	5/13/2026 2:19:34 PM
What mobile apps is KUA utilizing, and how many need to be reconfigured for the UN?	5/1/2026 2:56:45 PM	KUA currently utilizes ArcGIS Field Maps and Survey123 to support mobile data collection, inspection workflows, etc. The number of mobile applications requiring reconfiguration for the Utility Network has not been pre-determined, as mobile workflows are dependent on underlying web maps, feature services, and data model changes. KUA reserves the right to add additional services or scope related to migration, rebuild, and/or support efforts as needed during implementation.	5/13/2026 2:20:01 PM
Is KUA expecting the Attribute Assistant and Google Street View add-ins to be migrated to the UN platform?	5/1/2026 2:56:58 PM	KUA requires that functionality currently implemented through Attribute Assistant, such as auto-numbering and attribute population rules, be re-implemented as part of the Utility Network migration. The vendor shall include an equivalent solution within the scope of work using ArcGIS Pro attribute rules or other appropriate, supported methods subject to KUA approval and aligned with Utility Network best practices. The Google Street View add-in is not expected to be migrated as part of this effort.	5/13/2026 2:20:19 PM
To clarify: integrations to IKE Pole Foreman and PLS-CADD are not required, but KUA would like them considered in the design for potential future integrations?	5/1/2026 2:57:14 PM	KUA confirms that integrations with IKE PoleForeman and PLS-CADD are not included in the current scope of work. The vendor shall provide recommendations for data modeling, configuration, and overall system design to support potential future integration with these and similar engineering tools. These recommendations are intended to inform KUA’s future decisions; implementation of such integrations is not required as part of this effort.	5/13/2026 2:20:35 PM
Is an integration between the UN and Service Link required? Or does the ServiceLink integration pertain to AUD?	5/1/2026 2:57:30 PM	KUA confirms that integration with ServiceLink is not included in the current scope of work.	5/13/2026 2:21:01 PM
For the DNV Synergi integration, does KUA prefer the UN system implementer manage DNV directly (similar to Pendulum Media) or does KUA want to directly contract DNV?	5/1/2026 2:57:46 PM	KUA confirms that integration with DNV Synergi is not included in the current scope of work. As outlined in the RFP, Synergi is a future integration to be completed under a separate scope of work. The expectation for this project is that the proposed solution and Utility Network implementation will be designed to support future integration with Synergi, including appropriate consideration of data model, connectivity, and system architecture requirements.	5/13/2026 2:21:29 PM
For the Infinity CIS Integration: Is it KUA`s intention that this remain as a flat file import? The assumption is that this flat file will still need to be processed to create/update/delete meter data in the GIS database.	5/1/2026 2:58:08 PM	KUA intends to maintain the current integration approach with CIS Infinity as a flat file–based process. At present, CIS data is made available to GIS via a database view that is refreshed on a scheduled basis and joined to existing GIS layers (e.g., customer-related features). This integration is used for reference and does not create, update, or delete features within the GIS database. KUA does not require a transactional or bi-directional integration for CIS as part of this project. Vendors may propose alternative approaches if beneficial; however, a flat file–based integration is acceptable.	5/13/2026 2:21:59 PM
Are there two working environments or three working environments (see Section 4.5 "Environment Deployment & Recovery Guide," page 81 and A.1 "GIS Platform and Environment," page 112)?	5/1/2026 2:58:31 PM	KUA confirms that the intended deployment model includes two environments: Test/QA and Production. The reference to “dev/test/prod” in Section 3.5.1a is a general expectation regarding deployment documentation and recovery procedures. Vendors should ensure that environment deployment and recovery processes are well documented and repeatable for the environments in scope. A dedicated development environment is not currently required but may be proposed if recommended by the vendor.	5/13/2026 2:22:28 PM
Is the vendor expected to solution installation of a failover environment (see 3.1.2 "System Assessment," 3.4 "Migration and Integration Considerations," 4.4 "Migration and Integration Planning Deliverables," and A.7 "Current Licensing Detail")?	5/1/2026 2:58:55 PM	KUA is not requiring the implementation of an expanded failover environment as part of the base scope of work. However, existing failover capabilities are expected to be deployed under this scope of work. As reflected in the RFP, KUA currently utilizes license server failover to support business continuity, and the vendor shall ensure this functionality is maintained within the upgraded ArcGIS Enterprise and Utility Network environment. Additionally, vendors should evaluate the existing environment and provide recommendations for enhanced failover and resiliency strategies. KUA may consider implementation of such recommendations separately.	5/13/2026 2:22:50 PM
Please confirm whether KUA intends for all Pendulum Media implementation services, software licensing, and ongoing support to flow through the selected prime vendor`s contract, or whether KUA reserves the right to enter into a separate task order or direct agreement with Pendulum Media for any portion of the Pendulum-related scope (for example, software licensing or post-implementation support during the duration of contract term).	5/3/2026 7:51:25 PM	KUA has requested separate line item pricing for the Pendulum Media Scope of Work. KUA reserves the right to include or exclude this portion of the work based on project needs, funding availability, and negotiations. Prime vendor scope for this line item should include implementation/integration services, standard initial term software licensing costs, and any support costs required by the Prime Vendor for the initial implementation/integration services. Any ongoing support services or licensing costs post-implementation project acceptance may be directly contracted between KUA and Pendulum Media for the Pendulum Media component of the project. KUA reserves the right to negotiate an alternate contracting approach for Pendulum Media-related services, including implementation, software licensing, and ongoing support. Should Pendulum Media be included as part of the project scope, implementation responsibilities during the project shall be addressed by the selected vendor as part of the overall SOW. Vendors should assume coordination with Pendulum Media as part of the implementation effort. Post-implementation support, licensing arrangements, and any ongoing services beyond project completion will be at KUA’s discretion and may be addressed through separate agreements or contracting arrangements. Vendors shall clearly identify any assumptions regarding Pendulum-related scope in their proposals.	5/13/2026 2:24:57 PM
With all the expected report deliverables, is it the desire of KUA to have a review and update cycle for each report? We ask because these review cycles could add extensive time to the project.	5/4/2026 9:56:57 AM	KUA has requested separate line item pricing for the Pendulum Media Scope of Work. KUA reserves the right to include or exclude this portion of the work based on project needs, funding availability, and negotiations. Prime vendor scope for this line item should include implementation/integration services, standard initial term software licensing costs, and any support costs required by the Prime Vendor for the initial implementation/integration services. Any ongoing support services or licensing costs post-implementation project acceptance may be directly contracted between KUA and Pendulum Media for the Pendulum Media component of the project. KUA reserves the right to negotiate an alternate contracting approach for Pendulum Media-related services, including implementation, software licensing, and ongoing support. Should Pendulum Media be included as part of the project scope, implementation responsibilities during the project shall be addressed by the selected vendor as part of the overall SOW. Vendors should assume coordination with Pendulum Media as part of the implementation effort. Post-implementation support, licensing arrangements, and any ongoing services beyond project completion will be at KUA’s discretion and may be addressed through separate agreements or contracting arrangements. Vendors shall clearly identify any assumptions regarding Pendulum-related scope in their proposals.	5/13/2026 2:25:17 PM
With all the expected report deliverables, is it the desire of KUA to have a review and update cycle for each report? We ask because these review cycles could add extensive time to the project.	5/4/2026 9:58:13 AM	Duplicate; please see previous answer.	5/13/2026 2:26:15 PM
With all the expected report deliverables, is it the desire of KUA to have a review and update cycle for each report? We ask because these review cycles could add extensive time to the project.	5/4/2026 9:59:51 AM	Duplicate; please see previous answer.	5/13/2026 2:26:58 PM
Good afternoon, Here is our list of questions, thank you in advance: - Can KUA identify which enterprise integrations are considered operationally critical for Day 1 go-live versus those that could be phased post-go-live? - Beyond the integrations identified in the RFP, what level of existing enterprise integration documentation, interface standards, and operational support documentation currently exists to support implementation planning and testing activities? - Should vendors assume existing integrations will primarily be enhanced/reconnected, or is substantial redesign and redevelopment anticipated? - What level of GIS data quality assessment or remediation has already been completed, and are there known data quality concerns vendors should account for during migration planning? - Has KUA already established Utility Network governance standards such as subnetwork strategy, feeder modeling approach, and operational tracing requirements, or should those activities be included within the implementation scope? - Does KUA anticipate a phased operational transition from ArcFM Designer to AUD, or is the expectation a full production cutover to AUD workflows at go-live? - Are current Compatible Unit (CU) libraries, engineering standards, and design workflows considered production-ready, or should vendors account for refinement, normalization, and validation activities during implementation? - Are Dev, Test, Training, and Production environments already provisioned, or should vendors include environment build and configuration activities within their implementation approach? - What level of vendor involvement does KUA expect for SIT/UAT planning, test script development, coordinated testing activities, and operational validation across integrated systems? - Are there operational constraints, outage windows, storm response considerations, procurement dependencies, or other schedule drivers vendors should account for when developing implementation sequencing and go-live planning? - Does KUA anticipate maintaining parallel ArcFM and Utility Network editing activities during the migration period, and if so, what expectations exist around delta synchronization, edit reconciliation, and cutover coordination? - What level of involvement is expected from Esri Professional Services, SBS/AUD, and other third-party vendors during architecture validation, integration testing, deployment, and production cutover activities? - Are there any known performance, scalability, or versioning challenges within the current ArcGIS Enterprise or geodatabase environment that vendors should account for as part of implementation planning? - Does KUA expect vendors to include post-go-live HyperCare and operational stabilization support as part of the base implementation scope, and if so, what duration and support expectations should be assumed?	5/7/2026 3:43:01 PM	1. KUA expects our GIS, OMS, and AUD to be fully functional and operational on go live; all critical integrations required to support these systems should be in place. Any non-critical remaining integrations are expected to be phased based on operational priorities, system readiness, and implementation sequencing. 2. KUA maintains documentation for several existing enterprise integrations; however, the level of detail, standardization, and completeness varies by system. Vendors should anticipate engaging in a discovery and validation process to fully define interface requirements, operational behaviors, and testing needs. 3. KUA anticipates a combination of integration approaches depending on the system. Some integrations may be enhanced or reconnected, while others may require redesign or redevelopment to align with the Utility Network architecture and modern integration standards. Final determination will be made during detailed design. 4. A foundational level of data assessment has been completed; however, vendors should anticipate performing a comprehensive Utility Network readiness assessment. Data quality, completeness, and structural alignment remediation activities are expected to be part of the implementation effort. 5. KUA has established existing electric network modeling practices within its current ArcFM environment, including feeder definitions and operational tracing behaviors. However, Utility Network governance standards (including subnetwork strategy, feeder modeling alignment to the Utility Network, and formal tracing rules) have not yet been fully defined for the target environment. The selected vendor is expected to lead and support the refinement, validation, and formalization of these standards as part of the Utility Network implementation planning and design phase, leveraging existing ArcFM configurations where appropriate. 6. KUA does not have a predetermined preference for either a phased transition or a full production cutover from ArcFM Designer to Automated Utility Design (AUD). The selected vendor is expected to evaluate system readiness, integration dependencies, and operational risk, and to recommend an appropriate transition strategy as part of the implementation planning phase. The final approach will be based on balancing operational continuity, cost, and system readiness considerations. 7. Current Compatible Unit libraries and design workflows exist and are currently used for successful operation by existing systems. Regardless, this RFP will require the deployment of new systems for KUA. Deployment of new systems are expected to require review, validation, and refinement of existing standards and processes as part of the implementation. Engineering standards may exist in varying forms and levels of maturity and are also expected to be assessed and aligned during implementation. Vendors should anticipate supporting normalization, validation, and alignment activities to ensure consistency with AUD, Utility Network, and enterprise integration requirements. 8. KUA will provide underlying hardware and platform infrastructure (Windows, VMware, and SQL Server). However, the ArcGIS Enterprise environments (Development/Sandbox and Production) are expected to be established, configured, and optimized by the selected vendor in accordance with the RFP requirements. 9. The selected vendor is expected to lead the planning and coordination of SIT and UAT activities, including test strategy development, test script support, execution coordination, and validation across integrated systems in collaboration with KUA and third-party vendors. 10. Vendors should account for operational constraints including outage management requirements, storm response conditions, system availability windows, and coordination with enterprise stakeholders. These factors should be incorporated into implementation sequencing and cutover planning. 11. KUA anticipates that some level of parallel operations may be required during migration. Vendors should plan for appropriate synchronization, reconciliation, and cutover strategies to support a controlled transition from ArcFM-based workflows to the Utility Network environment. 12. KUA expects the selected vendor to coordinate with Esri, SBS/AUD, Pendulum Media, Schneider Electric, and other relevant third-party vendors throughout the implementation lifecycle as needed. The level and timing of third-party involvement will depend on the implementation approach, integration requirements, issue resolution needs, and vendor recommendations identified during planning and execution phases. 13. KUA is not currently aware of specific performance or scalability constraints that would preclude implementation; however, vendors should perform their own detailed assessment of the ArcGIS Enterprise environment and identify any optimization, upgrade, or configuration requirements during the planning phase. 14. Yes. KUA expects vendors to include post-go-live HyperCare and operational stabilization support as part of the base implementation scope. As outlined in Sections 3.1.11, 3.2.9, and 5.6 of the RFP, vendors should assume support activities including cutover coordination, troubleshooting, configuration adjustments, workflow stabilization, knowledge transfer, and transition to steady-state operations. KUA anticipates HyperCare support in the range of approximately 2–6 weeks post go-live, with the specific duration and support structure proposed by the vendor based on implementation approach and operational needs.	5/13/2026 2:27:53 PM
	5/7/2026 3:48:46 PM	See Addendum No. 2	5/13/2026 2:28:14 PM
Could KUA share Appendix B System Architecture and Infrastructure information?	5/7/2026 11:14:28 PM	Please refer to Appendix B for requesting instructions.	5/13/2026 2:28:32 PM
Does the Transmission dataset contain a Geometric Network currently?	5/7/2026 11:14:53 PM	KUA confirms that the Transmission dataset is not currently part of the Geometric Network environment.	5/13/2026 2:28:47 PM
Does KUA peform any tracing on the Transmission dataset currently?	5/7/2026 11:15:11 PM	No, KUA does not currently perform tracing on the Transmission dataset.	5/13/2026 2:29:08 PM
Does the Fiber dataset contain a Geometric Network currently?	5/7/2026 11:15:19 PM	KUA confirms that the Fiber dataset is not currently part of the Geometric Network environment.	5/13/2026 2:29:49 PM
Does KUA peform any tracing on the Fiber dataset currently?	5/7/2026 11:15:27 PM	No, KUA does not currently perform tracing on the Fiber dataset.	5/13/2026 2:30:09 PM
Will KUA need to perform advanced tracing (next protective device or isolation, etc) or simple tracing (Connected, Upstream, Downstream, etc) on the Transmission dataset in the new environment?	5/7/2026 11:15:34 PM	KUA does not currently require advanced or simple Utility Network tracing capabilities for the Transmission dataset as part of this phase of the project. As outlined in Section 3.1.4, transmission assets will be migrated using a lift-and-shift approach and are not planned to be fully modeled within the Utility Network at this time.	5/13/2026 2:31:33 PM
Will KUA need to perform advanced tracing (next protective device or isolation, etc) or simple tracing (Connected, Upstream, Downstream, etc) on the Fiber dataset in the new environment?	5/7/2026 11:15:43 PM	KUA does not currently require advanced or simple Utility Network tracing capabilities for the Fiber dataset as part of this phase of the project. As outlined in Section 3.1.4, fiber assets will be migrated using a lift-and-shift approach and are not planned to be fully modeled within the Utility Network at this time.	5/13/2026 2:33:25 PM
Is ArcFM Fiber Manager used currently, or other fiber management application currently? Please provide application name if applicable.	5/7/2026 11:16:01 PM	KUA is not currently utilizing Schneider Electric's Fiber Manager or another dedicated fiber management application. Fiber assets are currently maintained within GIS at a general asset level, while more detailed strand-level documentation is maintained separately outside of GIS. As outlined in the RFP, fiber assets are planned for lift-and-shift migration only and are not intended to be fully modeled within the Utility Network as part of this phase of the project.	5/13/2026 2:36:37 PM
Does Electric Distribution use feature linked annotation currently and or be required in future state?	5/7/2026 11:16:10 PM	KUA does not currently utilize feature-linked annotation for electric distribution workflows and primarily relies on dynamic labeling. Feature-linked annotation is not currently required as part of the future-state Utility Network environment.	5/13/2026 2:37:01 PM
Will any editors of Transmission or Fiber continue to use ArcMap or will all editors move to ArcGIS Pro or web-based maps for editing?	5/7/2026 11:16:53 PM	KUA’s intended future-state workflow is for editing of Transmission and Fiber assets to occur within ArcGIS Pro and/or web-based applications. KUA does not anticipate continued ArcMap-based editing workflows following implementation.	5/13/2026 2:37:49 PM
Will KUA allow use of an existing Master Professional Services Contract to serve as the basis of this engagement, subject to review of both parties?	5/7/2026 11:17:00 PM	KUA intends to utilize the agreement included within the solicitation documents as the basis for this engagement. Any requested modifications, exceptions, alternative terms, or existing service agreements should be identified by the vendor within their proposal for KUA review and consideration.	5/13/2026 2:38:19 PM
The vendor is responsible for enabling the "GIS-side integration readiness" between the Utility Network and Schneider Electric’s EcoStruxure Grid Operation OMS. Does KUA have an existing systems integrator working on the OMS side that the vendor will coordinate with, or is the OMS deployment happening at a later, undefined date?	5/7/2026 11:17:13 PM	KUA is currently working with Schneider Electric as the primary implementer of EcoStruxure Grid Operation OMS. In addition to OMS, KUA maintains a set of OMS-dependent integrations that support outage management workflows, including customer notification systems (e.g., TextPower), IVR/voice response systems, AMI-related systems, and outage mapping. The selected vendor should anticipate coordination with Schneider Electric as well as other system vendors supporting OMS-related integrations as necessary. The scope of this effort remains focused on GIS-side integration readiness within this broader OMS-driven environment.	5/13/2026 2:38:48 PM
Does KUA plan on this being a full three-year implementation effort as stated in the RFP, or is the three-year term intended primarily as a contracting mechanism?	5/7/2026 11:17:22 PM	KUA does not intend for this to be a full three-year implementation effort. The three-year term is primarily a contracting mechanism to support implementation, stabilization, and potential post-go-live support. KUA anticipates the core Utility Network migration and implementation will be completed within a shorter timeframe, with the remaining contract period available for support and potential enhancements as needed.	5/13/2026 2:39:27 PM
Does KUA envision a phased deployment approach (e.g., electric distribution first, transmission later, OMS integrations later), or a single enterprise cutover?	5/7/2026 11:17:29 PM	KUA anticipates a phased, risk-managed deployment approach rather than a single enterprise cutover. The Utility Network implementation will focus on electric distribution as the core deployment, with transmission and fiber handled as lift-and-shift datasets and integrated as part of the broader deployment plan. OMS and other enterprise integrations will be coordinated in alignment with system readiness and implementation sequencing. Final deployment phasing and sequencing will be refined in collaboration with the selected vendor during the design and implementation planning phases.	5/13/2026 2:39:58 PM
Can you describe the expected integration pattern between AUD/UDH, Pendulum Media, Cogsdale, and GIS?	5/7/2026 11:17:37 PM	KUA envisions an integrated workflow in which design and engineering activities originate in AUD/UDH and are coordinated with Pendulum Media to support compatible unit management, asset position data, and work order estimation processes. Pendulum Media serves as the integration and workflow bridge between GIS and Cogsdale, facilitating the transfer of work order estimates, compatible units, and asset position information between systems. Cogsdale functions as the enterprise financial and work management system, while GIS serves as the primary system of record for electric network and asset data. In the event that the Pendulum Media component is not selected for implementation, then AUD/UDH will tie directly to Cogsdale. The selected vendor shall be responsible for defining the detailed integration architecture, data exchange patterns, and synchronization approach between these systems in coordination with Pendulum Media and other relevant stakeholders during the design and implementation phases.	5/13/2026 2:23:53 PM
Will KUA consider proposal responses that address a defined subset of the overall scope? For example, the Automated Utility Design (AUD) implementation and graphic work design component, rather than requiring a single vendor to respond to all three workstreams in their entirety. If yes, then would a proposal structure encompassing the full scope be required, or would it be sufficient to clearly state our exclusions to the scope in the Statement of Compliance and Exceptions?	5/8/2026 12:43:15 PM	KUA is seeking a single prime vendor to deliver the full scope of services defined in this RFP. Partial proposals that address only a subset of the overall scope (e.g., individual workstreams in isolation) will not be considered. Vendors may utilize subcontractors to support specific components of the scope; however, the prime vendor must demonstrate the capability and responsibility to deliver the complete solution.	5/13/2026 2:23:15 PM

Commodity Codes

Total: 8

Code	Description
[206-54]	Geographic Information Systems (GIS)
[209-49]	Geographic Information System (GIS) Software
[920-40]	Programming Services, Computer
[920-37]	Networking Services (Including Installation, Security, and Maintenance)
[920-45]	Software Maintenance/Support
[920-33]	Mapping Services, Digitized, Cartography (See 962-52 for Standard Mapping Services)
[918-30]	Computer Network Consulting
[917-55]	Information Distribution Services

Publications

Total: 0

Publication

Date

Utility Network Migration And Implementation Services

See also