Joint Government Operations and Resilience Committee Meeting - July 21, 2025
STREAMING COPY IN PREPARATION — RECORDING AVAILABLE FROM THE ORIGINAL SOURCE
Joint Government Operations and Resilience Committee Meeting - July 21, 2025
This joint meeting of the Government Operations and Resilience Committees featured two presentations: one on the city's enterprise resource planning (ERP) system contract with SAP and another on hurricane preparedness. The meeting was chaired by Councilmember Carter (Resilience) and co-chaired by Councilmember Flickinger (Government Operations). Councilmembers present included staff from Districts A, C, H, I, and At-Large 1, along with Councilmember Cayman (online) and Councilmember Huffman (online).
Discussion Items
Presentation 1: Enterprise Resource Planning System Contract (SAP)
Stephen David, Chief Strategy and Operations Officer from the Mayor's Office, and Summer Zhao, Deputy Chief Information Officer, presented a request to approve a new SAP contract for the city's ERP systems. The contract covers licensing, maintenance, and cloud migration for existing on-premise systems (ECC) and various cloud solutions (SuccessFactors, Ariba, SAP Analytics Cloud, etc.). The proposed contract amount is $20.5 million for the initial three-year term, with two optional one-year renewals. The MWBE goal is 0% because the contract consists of non-divisible licensing elements. David highlighted the city's strategic IT investments, including the 11-year-old SAP implementation, and emphasized the benefits of moving to the cloud (redundancy, remote access, cybersecurity). Zhao detailed the city's current SAP usage: FY26 budget of $7.3 billion, FY25 payments of $6.6 billion, 2024 payroll of $2.3 billion, and 38,000 employees/retirees managed. She noted that the city is ahead of 80% of peer public sector organizations in cloud ERP adoption. The new contract will fund the replacement of the on-premise backbone (S/4HANA) and add learning and performance management modules. Councilmembers asked about data ownership (confirmed retained), data transfer integrity (confirmed), and internet outage contingency (business continuity plans, offline modes, and redundant fiber lines). David noted that cost savings are expected in out-years through reduced on-premise expenses and license negotiations. No vote was taken; the presentation was for informational purposes.
Presentation 2: Hurricane Preparedness
Brian Mason, Director of the Office of Emergency Management, presented the city's hurricane preparedness timeline and response framework. He explained the use of "H-minus" time designations based on when tropical storm force winds arrive at the coast. Key points included: only 12% of 67 storms that hit within 60 nautical miles of Houston provided 144+ hours notice; most form quickly (48-72 hours). Mason outlined the four principles of preparedness: make a plan, stay informed, build a kit, and get connected. He emphasized the importance of knowing evacuation zones (five Houston zip codes in Zone B) and having a family communication plan. He discussed the difference between voluntary and mandatory evacuations, and the process of sequencing evacuations from the coast inland. During the storm, the EOC monitors 911/211/311 calls, critical infrastructure, and coordinates with partners. Post-storm, rapid needs assessments and FEMA coordination begin. Councilmembers raised questions about electric vehicle charging along evacuation routes (Mason noted state plans for fuel tankers and EV charging challenges), post-disaster communications when cell towers fail (no current solution, but acknowledged as a concern), and the use of digital message boards on freeways (used for mobility, not for specific distribution site details). Councilmember Thomas suggested alternative distribution locations, which Mason requested be emailed for evaluation. The presentation also covered bayou monitoring via Harris County Flood Control District sensors. No vote was taken.
Key Outcomes
- The SAP contract presentation was informational; a formal council action request is expected to be brought forward at a future meeting.
- The hurricane preparedness presentation was informational; no formal decisions were made.
- The next Government Operations Committee meeting is scheduled for Thursday, August 21, 2025.
- The next Resilience Committee meeting is scheduled for Monday, August 25, 2025, at 10:00 a.m.
Meeting Transcript
Welcome to the joint government operations and resilience committee meeting. I'd like to acknowledge my um chair Toyla Carter of the Resilience Committee and invite her to offer any opening remarks. Thank you. Um we're glad to uh host this joint committee today. We hope it's a really good use of everyone's time because we like to consolidate this and look forward to all the presentations. Thank you all for being here and all you do. All right, thank you all so much for being here. Obviously, this is incredibly timey, bate timely based on where we are in the season. So we're excited to hear uh the presentations. I would like to acknowledge our council members that are present. So we have staff from District A, C, H, I, and then Councilmember Cayman's online. And she also has someone here on staff, and then at large one, we have a team member. I'm sorry. Raveras is here. Thank you for being here. And my chair here, um, Councilmember Carter, and then Councilman Alcorn. Okay, perfect. All righty. So today's meeting will feature two presentations, one from Houston's information technology services, and then also the Office of Emergency Management. At this time, I would like to yield to the for the HIITS presentation. Presentation one enterprise resource planning system contract, and the presenter will be Stephen David, who is our operations officer from the mayor's office. And also Summer Zhao. She's a deputy chief information officer as well. Thank you so much to both of you, and thank you for being here. Good afternoon, Council members. I am uh happy to be here in front of y'all. Councilmember get this out of here. It's good to see you, man. Uh thanks for taking the time. Thanks for hosting us. Uh I'm here with uh deputy CIO of the IT department, SummerShow. Um, and really excited to talk about um what we have coming up. Um we're gonna bring it to council soon. This is intended to talk to you a little bit about she's gonna walk you through exactly what the SAP contract is, um, what we are planning to do, what the next few years looks like. I'm here to have uh here to help answer any questions, but also to give sort of an introductory remarks um about the way that the city of Houston comports itself with regard to IT strategy. Uh so as some of y'all may or may not know, uh, prior to coming back to the city of Houston, I had a uh seven-year stint in the private sector, uh six-year stint in the private sector, and I worked uh most of that time with a company called Accenture. It's the uh world's largest IT consulting firm. Um and what I did was a lot of the work that you're about to see, uh transitioning municipalities, county governments, state governments from one system to another system. We call it IT implementation. Uh more importantly, um transitioning from what we would consider tier two, tier three uh systems into a tier one system. SAP, for example, is a tier one system. Uh the home brewed systems that the city of Houston has uh or had uh prior to SAP or any of our other systems would be considered tier two and tier three. With regard to IT strategy, the City of Houston has uh over the course of the the past few decades made a couple of very strategic choices that has set itself up for uh success moving forward in the future. So, for example, and we sort of take this for granted, we are a Microsoft organization. Um we have Outlook, we have PowerPoint and Word, we have all of the licensing infrastructure underneath it. For example, we are what's called an E5 license organization. That's the biggest and best license that you can get. You get really cool things like Power BI baked into your license. But more importantly, what it did was it created a foundation for which we could grow. Um so a great example uh of that is that our 311 platform, while we call it Chris, the uh customer can't remember.
openpublica.com