Gainesville Regional Utilities' existing outage management system, purchased in 2007, remained usable but no longer met the utility's expectations during storms and major events. GRU moved from those capability limitations through a five-proposal RFP, cross-department evaluation and scoring, Utility Advisory Board review, and City Commission authorization to negotiate and purchase a replacement from Open Systems International.
-
Utility: Gainesville Regional Utilities
Utility type: Municipal utility
Technology / purchase: Outage Management System (OMS) replacement
Buying motion: Failure- or performance-driven replacement / remediation
Stages visible in the record: Problem Definition → Solution Exploration → Vendor Evaluation → Purchase Decision
Stakeholders explicitly visible: GRU Purchasing; cross-department evaluation group; Utility Advisory Board; City Commission; General Manager
Evidence / information explicitly mentioned: OMS RFP; five vendor proposals; evaluation criteria; proposal scoring tabulation; referrals as an evaluation criterion
Outcome: Open Systems International ranked highest; the Utility Advisory Board reviewed the recommendation; the City Commission authorized negotiation and purchase, with the General Manager authorized to negotiate and execute agreements and issue a purchase order. Completed contract execution and implementation are not established in the current source set.
Source basis: Primary City of Gainesville / GRU staff recommendation, supplemented by a primary City public meeting transcript / record
What triggered the purchase
GRU had operated its existing OMS since 2007. The available record does not describe a catastrophic system failure. Instead, the system still worked but no longer performed adequately during storms and major events.
The documented limitations included processing delays that affected restoration and customer service, along with an inability to provide the outage information GRU wanted to deliver to customers and other stakeholders quickly enough. The replacement process was therefore framed around a capability gap between the installed system and the utility's current operating expectation
How the utility defined what it needed
GRU defined the replacement need around major-event performance, productivity, reporting, user experience, system integration, and the quality and timeliness of outage information available to customers and other stakeholders. Support and implementation requirements were also part of the documented evaluation framework.
The supplemental public meeting record indicates that GRU considered improving the existing situation but found that path costly and insufficient. The record therefore shows the utility evaluating whether to continue with the incumbent approach before proceeding with a full OMS replacemen
How vendors or options were evaluated
GRU Purchasing issued an OMS RFP and received five proposals. A cross-department group evaluated the responses.
The public record lists a broad set of evaluation considerations, including qualifications, approach, software, cost, differentiators, referrals, functionality, ease of use, integration, user experience, support and implementation. The record does not establish that any one of those criteria was decisive.
A proposal scoring tabulation was then used in the evaluation record. Open Systems International was identified as the highest-evaluated proposer, and the staff recommendation advanced for governance review.
The Utility Advisory Board reviewed the recommendation. The City Commission then authorized negotiation and purchase. These were separate steps from the cross-department proposal evaluation; the record does not treat the advisory-board review or City Commission action as additional vendor scoring rounds.
Evidence and information explicitly mentioned
OMS RFP and proposal evaluation
GRU's procurement record documents an OMS RFP, five responses and a cross-department evaluation process. The listed criteria covered vendor qualifications and approach as well as software, cost, differentiators, referrals, functionality, ease of use, integration, user experience, support and implementation.
Proposal scoring tabulation
The staff record reports a proposal scoring tabulation and identifies Open Systems International as the highest-evaluated proposal. The tabulation supported the recommendation in the public record, but the source does not establish that the tabulation alone, or any single criterion within it, determined the recommendation.
Outcome
Open Systems International ranked highest in GRU's evaluation. The Utility Advisory Board subsequently reviewed the recommendation, and the City Commission authorized negotiation and purchase. The General Manager was authorized to negotiate and execute agreements with Open Systems International and issue a purchase order; the current source set does not separately establish that those actions were completed.
The approved package included implementation, support and software licensing. The current source set does not establish that implementation was completed. For that reason, the visible buying journey in this case stops at Purchase Decision rather than treating Adoption & Implementation as an observed stage. No expansion or advocacy activity is documented in the available record.
Why this case matters for vendors
Replacement began with a capability gap, not a catastrophic failure
GRU's incumbent OMS was still usable, but its performance during storms and major events no longer met the utility's expectations. This case shows a replacement cycle beginning when an operating system falls behind changed requirements and service expectations, even though the record does not describe an outright system failure.
Proposal evaluation, advisory review and purchase authorization were separate steps
The cross-department group evaluated and scored five proposals, after which the recommendation moved to Utility Advisory Board review and then City Commission authorization. For vendors, the case documents a municipal buying process in which being the highest-evaluated proposer and receiving final governing-body authorization were distinct events.
-
City of Gainesville / Gainesville Regional Utilities staff recommendation
Public link: https://gainesville.legistar.com/View.ashx?GUID=E1E42D70-18C2-4900-8357-F0B1BEBE8E33&ID=573208&M=A
Source provenance: Primary City of Gainesville / GRU staff record. Key case evidence is located on PDF p. 4, including the staff-recommendation paragraph beginning "GRU Purchasing issued" and the following paragraph describing the scoring tabulation and highest-evaluated proposal.City of Gainesville public meeting transcript / record
Public link: https://gainesville.granicus.com/TranscriptViewer.php?clip_id=3099&view_id=9
Source provenance: Primary City of Gainesville public meeting transcript / record, used as a supplemental source to S038. Relevant locator: item 170545, passage beginning "The current system that we have was purchased in 2007..." and continuing through the storm-performance limitations, attempted improvement of the incumbent situation, RFP, five proposals and cross-department review.Evidence limitations: The source set documents the capability gap, consideration of the incumbent situation, formal RFP, five proposals, cross-department evaluation, scoring, recommendation, Utility Advisory Board review and City Commission authorization. It does not establish that any single proposal criterion, including referrals, or scoring component caused the selection. It also does not establish completed contract execution, completed OMS implementation, later expansion or advocacy.
More Buying Cases
NEW CASES + ANALYSIS
Get new Utility Buying Cases when they’re published, plus analysis of how utilities buy. Subscribe to CONDUCTOR below
