April 30, 2025 Hood County Radio Workshop

Open with transcript & summary →Search this meeting's transcript →

Hood County Commissioners' Court convened a workshop on April 30, 2025, to discuss the Granberry Regional Network radio system, covering technical infrastructure, Harris service offerings, monitoring capabilities, and network resilience. The meeting addressed identified service gaps including the lack of 24/7 security monitoring, proposed proactive service enhancements at additional cost, VPN security risks, and single points of failure in the current network topology. Discussions included the fee structure for radio maintenance, liability considerations for third-party equipment, environmental monitoring needs, and the need for fiber redundancy to improve network stability. The workshop concluded with plans to draft an updated interlocal agreement and schedule presentations to participating entities, with emphasis on balancing security, reliability, and cost-sharing across the regional public safety network.

• Meeting call to order and invocationThe special called workshop of Hood County Commissioners' Court convened in the central jury room at the Ralph H. Walton Junior Justice Center in Granberry, Texas.
• Workshop purpose: Granberry Regional Network radio systemThe workshop was convened to discuss the Granberry Regional Network radio network.
• Summary of meetings and progress on radio network coordinationCampbell provided a recap of multiple meetings held since March 20th involving IT, emergency management, dispatch, commissioners, neighboring counties, and city leadership.
• Overview of Granberry Regional Radio Network infrastructure and acronymsChris Collins, chief information security officer for the city of Granberry, provided technical overview of the GRRN system, including key components and network topology.
• GRRN as dual ecosystem of IT and communication systemsThe Granberry Regional Radio Network operates as an integrated ecosystem of both IT infrastructure and communication stack components.
• VPN licensing, compliance, and Harris technician accessThe radio network is completely separate from the city network, with VPN licensing structured to allow Harris technician access while maintaining security compliance.
• Network monitoring and R&M tool capabilitiesThe R&M tool dispatch uses provides a red-light, green-light, yellow-light system to monitor network status across different operational aspects.
• History of contract and discovery of missing monitoring servicesCollins discovered through reviewing the contract and contact with Harris that critical 24/7 security monitoring and operations monitoring were not being provided despite contract language suggesting they should be.
• Current Harris service offering and maintenance structureHarris provides tiered service including standard Monday-Friday response, preventive annual maintenance, premium technical support, 24/7 remote engineering, and third-party licensing for equipment management.
• Regional issues with third-party renewal and San Antonio's firewall incidentIssues were identified among Texas Harris customers regarding third-party licensing renewal, with San Antonio experiencing a critical incident where a firewall update could not be deployed for four days.
• List of customer concerns and initial response from HarrisCollins and team compiled a list of customer concerns voiced about the network and began addressing them with Harris, starting with the lack of 24/7/365 monitoring.
• Proposed 24/7/365 security monitoring (SOC) service from HarrisHarris quoted security operations center (SOC) services through a third party for 24/7/365 security monitoring with specific caveats regarding non-standard equipment.
• Reactive versus proactive network monitoring approachSOC monitoring would enable proactive intervention by Harris engineers identifying issues before they cause outages, compared to current reactive model.
• Proposed updates to VPN access and security liabilityQuestion two addressed VPN access to GRN; currently dispatch has access, but this creates security risk and requires liability clause in any updated interlocal agreement.
• Addressing intermittent connections and single points of failure through grants and cooperationQuestion three addressed intermittent tower connections due to lack of redundancy; Collins discussed grant funding and multi-entity cost-sharing approaches used by other Texas municipalities.
• Communications gap and service level with Granberry ITCity previously had dedicated radio technician; interlocal agreement requires 10 business days notice for adds, deletes, or changes to radios, though most are typically resolved within couple days.
• UAS as gatekeeper: radio programming and GRN connectivity protocolsThe UAS (Unified Administration System) controls which devices can communicate on the P25 system and requires specific technical data from entities before radios can be programmed and added to the network.
• Rapid response service proposal and cost structureCollins proposes adding rapid response option at approximately $33,000 per year for more proactive service delivery; fee structure will be published as separate schedule rather than embedded in interlocal agreement.
• Incident response and non-Harris equipment liabilityFor network incidents and repairs involving non-standard Harris equipment like Silio microwave links, agreements must exist between the third party and Harris, or liability falls back to the county.
• Harris technician VPN access and yellow-light alertsHarris maintains six VPN accounts into the city core to proactively fix yellow-light alerts and prevent outages; current reactive state lacks this proactive capability because monitoring is not in place.
• Harris equipment maintenance agreement and tariff impactsThe city negotiated core maintenance and upgrades with Harris, who stopped selling certain cores due to tariff concerns affecting long-term pricing.
• Radio service fee structure and maintenance cost recoveryThe $13 per radio monthly fee covers core maintenance costs divided across all devices on the network, with separate per-unit charges for consoles and core access fees.
• Original maintenance contract and year-one billing structureThe original $13 fee was designed to replace Harris maintenance on a 14–15 year contract; year one the city paid maintenance costs without billing participants until systems normalized.
• OTAR licensing and device scaleHarris licenses services based on device count; the city purchased OTAR (Over-The-Air Rekey) capability outright for approximately 900 active radios without charging participants.
• Capital investment versus ongoing maintenance cost structureThe initial 2.1 million dollar city capital investment is distinct from the $13 monthly maintenance fee, which funds Harris service similar to a cell phone provider's monthly charge.
• Interlocal agreement flexibility and fee schedule adjustmentsThe city seeks to reference a fee schedule rather than specify fixed dollar amounts in interlocal agreements to allow flexibility in service offerings without renegotiating contracts.
• Annual maintenance escalation and budget methodologyHarris historically provided a maintenance schedule based on their algorithm; the city now budgets known next-year costs divided by 900 radios and anticipates a budget amendment.
• County 15-year maintenance contract and shared cost concernsThe county operates under a separate 15-year Harris maintenance fee schedule; clarification was sought on whether the county pays both its own and a portion of the city's maintenance fees.
• Core replacement funding and 15-year system lifespanThe $13 fee funds core replacement and system support over 15 years to ensure the radio system remains operational for the full contract duration.
• Fee stability despite radio count changesThough the original agreement projected fees would decrease as more radios joined, the fee remained $13 per radio as additional entities came on board.
• Service enhancement rationale and network stabilityThe city added monitoring and rapid response services to protect the network and provide proactive rather than reactive operations, accepting higher costs for stability.
• GRN operational history and Harris support behaviorThe GRN went live in late 2023 after a planned 2021 timeline; Harris support has provided after-hours assistance during emergencies without documented after-hours charges.
• Harris after-hours support and potential contractual service provisionHarris technician Josh has responded after-hours to ice storms, weather, and equipment failures without documented charges, suggesting possible contractual obligation.
• Original contract language review and attorney perspectiveThe original Harris contract stated they would provide maintenance and response without specified time limits; lawyers in attendance discussed estoppel and waiver implications.
• Harris support during equipment failures and service provision timingThe city experienced time-clock and GPS equipment failures; both were identified and replaced during daytime hours by Harris without documented charges.
• Core environmental monitoring incident and redundancy gapsAn air conditioner and backup air conditioner both failed, causing equipment damage because the city lacked access to monitor the situation in real time.
• Thermostat monitoring and environmental threshold implementationThe city installed a standalone thermostat to monitor temperatures at a 70-degree threshold, separate from the GRN, to provide early warning of equipment stress.
• Knock and sock monitoring equipment integration requirementsKnock and sock services monitor equipment physically connected to and compatible with Harris systems; third-party equipment not connected is not covered.
• Data center management and environmental control backgroundThe city's representative has managed data centers with millions of dollars in equipment and hundreds of thousands of customers, applying that expertise to radio system environmental management.
• Remote site alarm integration and additional infrastructure costsAll alarms tie into the GRN for remote sites, requiring additional wireless network investment; redundancy and fiber infrastructure add ongoing costs.
• Managed service provider and third-party security verificationThe city employs a managed service provider that performs SIEM, vulnerability assessments, and penetration testing, with third-party verification requested to "check the checker."
• Monitoring thermostat integration and cost implicationsThe city pays $83,000 annually for enhanced monitoring yet must add a separate thermostat connection to the Harris system at additional cost.
• Cradle point monitoring infrastructure and cellular costsThe city installed a Cradle Point router for environmental monitoring with a $39 monthly Verizon cellular fee to provide real-time notification of facility issues.
• Knock and sock liability and non-Harris equipment exclusionsKnock and sock services cover Harris equipment; third-party systems like alarm networks and non-standard equipment are explicitly excluded from coverage.
• Monitoring network accessibility versus security lockdown tensionIf the system is locked down for security, field technicians cannot troubleshoot remotely; remote access by vendor support is necessary for rapid diagnosis from home while technicians mobilize.
• Contractual responsibility and technology background in agreement interpretationAgreements must specify contractual liability if a vendor's remote access results in network compromise; this requires both technical and legal expertise to properly translate.
• Organizations' cybersecurity maturity and compliance gapMost government entities lag years behind on security standards; the city implemented two-factor authentication a year and a half ago while CIJ only mandated it in 2025.
• Background in counter-intelligence and cybersecurity incident responseThe representative's background includes counter-intelligence and cyber-criminal investigations, informing current security posture and incident response practices.
• Provider responsibilities and centralized maintenance modelThe network provider described security and redundancy obligations and proposed centralized Harris maintenance contracts to replace individual entity arrangements.
• Individual entity contracts versus unified approachThe speaker explained how separate contracts limit communication about problems across entities and outlined benefits of a unified contract structure.
• Network documentation challenges and current diagram limitationsThe speaker acknowledged significant gaps in documentation and explained the diagram presented may be outdated.
• Single point failures and network topology gapsThe analysis identified multiple single-point failures across the network due to incomplete redundant loops in the topology.
• Fiber as redundancy solution and topography challengesSpeakers discussed fiber connectivity as a more stable alternative to microwave links and identified United Co-op's existing infrastructure.
• United Co-op fiber availability and expansion strategyThe speaker explained United Co-op's fiber expansion goals and how to engage with their engineering team for infrastructure deployment.
• Fiber options explored and costsCounty representatives examined fiber alternatives and found pricing to be expensive across multiple providers.
• Alternative approach: fiber point from dispatch to Stevenville with backfeed through towersParticipant proposed a collaborative approach to create network resilience through strategic fiber placement and backfeeding.
• Chalk Mountain tower failure case studyThe speaker illustrated network vulnerability through a recent windstorm incident affecting critical microwave links.
• Redundancy criticality and limitations of single microwave linksParticipants emphasized that redundancy is essential and discussed why dual microwave links on single tower are insufficient.
• Federal mandate background and regional network purposeSpeaker provided context that the Granberry Regional Radio Network implements a post-9/11 federal mandate delayed from 2015 to 2023.
• Expanding enhanced maintenance and service modelSpeaker outlined cost implications of adding proactive monitoring and maintenance to the regional network service.
• County core package acquisition and contract provisionsParticipant asked whether city would sell its core infrastructure package to county; response indicated need to verify Harris contract terms.
• Engaging fiber providers through engineering relationshipsSpeaker emphasized importance of connecting with engineering teams rather than sales staff to understand network expansion plans.
• Fiber routing strategy for network connectivityParticipants discussed the most practical approach to leveraging existing United Co-op fiber infrastructure on Highway 377.
• Next steps: draft interlocal agreement and entity consultationMeeting concluded with planned review of proposed contract terms and schedule for council presentation.
• Governance model discussion and county responsibility debateParticipant raised fundamental questions about whether current model with city as core host is appropriate for regional public safety network.
• County core ownership scenario and persistent communication challengesSpeaker explained that even if county assumed core infrastructure, it would not resolve fundamental network topology problems.
• Historical context: county opportunity and city initiativeRepresentative explained two decades of failed county efforts and emphasized that city took responsibility when county declined.
• Current redundancy status and equity concernsCity official addressed redundancy asymmetry and noted entities must fund their own resilience measures.
• Network design concerns and ongoing mitigation discussionsCounty representatives indicated concerns about current network structure and committed to collaborative problem-solving on the agreement.
• Safety and life-safety priority in network resilienceCounty official emphasized that communication failures have life-or-death consequences and commitment to network security.
• Single point failure design critique and liability concernsCounty official criticized decisions allowing single-point-of-failure designs and raised liability concerns about inadequate infrastructure.