May 25, 2022 Hood County Special Called Workshop Tyler Odyssey

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

Hood County held a special called workshop on May 25, 2022, to address Justice of the Peace clerk concerns regarding the Tyler Odyssey case management system implementation. Participants discussed whether Tyler Odyssey's one-size-fits-all design was appropriate for Hood County's varied court sizes, with Justice of the Peace offices and county staff expressing concerns about inadequate training, support responsiveness, configuration burdens, data integrity issues, and lack of judicial consultation in the decision-making process. The workshop also examined the original server replacement necessity that prompted the transition, staffing and workload challenges during implementation, and differing perspectives on system viability and cost-benefit trade-offs. Judges requested that commissioners court reconsider the decision based on ground-level office experience, while commissioners discussed their authority to consolidate systems and move forward with the implementation.

• Meeting opening and participant introductionsThe workshop was called to order with participants introducing themselves to establish identity and roles.
• Workshop purpose and agendaThis public workshop was convened to discuss Justice of the Peace clerk concerns regarding Tyler Odyssey implementation.
• Judge Gillam opening statement on Tyler Odyssey concernsJudge Gillam emphasized that clerks are the "front-line soldiers" and stated the timing was appropriate to evaluate whether Tyler Odyssey is working after several months of implementation.
• One-size-fits-all system critiqueJudge Gillam and other speakers noted that Tyler Odyssey's one-size-fits-all approach does not fit all court sizes and types.
• Configuration and customization burdenJudge Gillam cited examples from Pope County, Liberty County, and Chambers County to support concerns and invoked a metaphor about Lockheed fighter jets to justify reevaluation.
• Judge Griggs' perspective on Tyler Odyssey acceptanceJudge Griggs indicated her office is working through the Tyler system and spending significant time learning it daily.
• Ashley's account of forms issues and Tyler support interactionAn official noted that Financials software, implemented in 2012, took about a year to become comfortable with but eventually delivered value.
• County Clerk's office statement against Tyler OdysseyKatie (County Clerk) criticized Tyler Odyssey's design, terminology, and navigation efficiency compared to NetD.
• Tyler Odyssey training and support concerns from JP1JP1 clerk outlined deficiencies in training delivery, support responsiveness, and system usability compared to prior expectations.
• Tyler system process issues with civil cases and case numberingJP1 documented multiple workflow problems including alcohol awareness orders, case number formatting, and forced weekend work.
• Data integrity and litigation concerns with Tyler in other countiesJP1 raised concerns about Tyler's track record with case management, including lawsuits from other counties and closed-case data discrepancies.
• Lack of OCA mapping participation and workshop format criticismsJP1 expressed unwillingness to perform certain tasks and criticized training delivery format.
• Understaffing and workload challenges in JP1JP1 judge described severe time constraints managing civil caseload with limited staff and competing responsibilities.
• District Attorney perspective on Tyler challenges and staffingDA acknowledged common system implementation stressors and raised concerns about vacation and comp time policy impact on SME retention.
• Consensus summary on labor shortage and workload issuesFacilitator identified labor shortage and time constraints as cross-cutting consensus issue.
• JP2 staffing and Tyler system viability assessmentJP2 judge stated office would function adequately with current staff if not implementing Tyler system.
• Monthly reports and discussion of vacation/comp time policy mechanicsJP2 judge referenced monthly performance reports and commissioners court discussion clarified comp time accumulation and usage rules.
• Comp time policy rationale and Tyler implementation concernsDiscussion explained comp time use policy logic and flagged broader Tyler mandates as source of stress.
• Commissioner's court decision history and system consolidation rationaleCounty official explained prior commissioners court decisions to consolidate from two software systems to one Tyler system.
• Judge Massengill reassurance to JP regarding system choiceJP recalled being directly assured of option to remain on NetD system.
• JP3 system neutralityJP3 expressed satisfaction with either system option.
• Commissioner vote and committee review process backgroundCommissioner discussed prior vote against Tyler transition and committee report that formed basis of current decision.
• Committee composition and judge participation in review processCommittee structure and participation levels described, with some judges excluded from report receipt.
• Judge's interpretation of committee report findings on system suitabilityJudge re-read report and distinguished findings on system operation for JPs from overall cost and security concerns.
• Current request to reevaluate and defer to office expertiseJudges requested commissioners court reconsider decision based on ground-level office experience.
• Samuelson committee recommendations and system comparison analysisCommittee member Samuelson explained ranking and comparison methodology used to assess NetD versus Tyler.
• Software maturity model scoring and NetD assessment gapsSamuelson described industry-standard evaluation metrics applied to vendor comparison.
• Icon vs. constable program differences and JP system priorityCompared Icon and constable program development to explain why JP system was prioritized.
• Tyler adoption in other Texas countiesSamuelson noted widespread Tyler adoption across Texas counties.
• Hood County unique circumstances versus other Tyler jurisdictionsSpeaker noted Hood County's issues may be different from other counties successfully using Tyler.
• Denise's individual effort and office workload realityCommissioner acknowledged individual JP2 clerk's exceptional performance amid systemic constraints.
• Small office comparison: staffing and Tyler feasibilityJP3 compared conditions to other small counties encountering similar overwhelm.
• Office staffing choice and Tyler transition trade-offsJP3 clarified office declined additional staffing offers and identified Taylor as source of workload pressure, not staffing.
• Governance meetings and Tyler progress reportingJP3 described governance structure for Tyler implementation oversight.
• Tyler conversion costs and staged implementation optionsDiscussion of the three conversion options evaluated, their costs, and the least and most expensive pathways forward.
• Staffing concerns and unsupported implementationJPs expressed that Tyler conversion demands staff support and time that county is not providing compensation for.
• Net Data cloud migration and vendor strategic planningDiscussion of Net Data's parent company I3 Verticals' plans to migrate to Amazon Web Services and potential forced cloud conversion.
• Lack of judicial input in decision-making processJPs stated that county commissioners never consulted them about the Tyler transition despite making the decision on their behalf.
• "One size fits all" system mandate concernsJPs objected to forcing a single software solution across all offices when different systems work for different departments.
• Forced adoption despite satisfaction with existing systemCommissioners expressed frustration that JPs appear satisfied with Net Data but are being forced to switch anyway.
• Original driver: server replacement necessityContext provided that the Tyler transition decision stemmed from need to replace an aging server.
• Vehicle analogy for incompatible system impositionCommissioner used transportation analogy to characterize the mismatch between system and user needs.
• Forms conversion burden across multiple systemsDiscussion of the ongoing, repetitive work required to upload and configure forms in Tyler Odyssey.
• Token configuration and repetitive form workDetailed explanation of the technical requirements and time burden of adding form tokens.
• Delayed and contradictory form instructions from TylerTimeline of unclear, changing guidance on who is responsible for form configuration work.
• Mismatch between Tyler promises and actual form supportAssertion that Tyler promised to handle form migration but instead shifted responsibility to JPs.
• Form deletion and J-HUG assignment confusionDiscussion of how forms were deleted based on misunderstanding about task assignments.
• Shifting support model for go-live assistanceTyler repeatedly changed its commitment for on-site support during system launch.
• Communication breakdown and workload confusionMultiple instances of conflicting instructions creating wasted effort and overwhelming email volume.
• Tyler staff knowledge gapsConcern that some Tyler personnel lack understanding of full JP office operations and needs.
• Proposed single-office pilot optionQuestion raised about whether current vote allows for one JP office (Gwen's) to pilot Tyler while delaying others.
• Government code and records integrity concernsJPs cited their statutory duty to protect records and expressed concerns about Tyler system reliability based on litigation history.
• Warrant record issues discovered in conversionTechnical problems identified where closed warrants were reopened during Tyler implementation.
• Responsive problem-solving on conversion issuesAcknowledgment that Tyler staff member Andrew has been responsive to reported problems.
• Data conversion challenges and industry-wide issuesDiscussion that Tyler has limited experience converting from Icon to Tyler and similar quirks appear across the state.
• Standardization challenges despite similar JP functionsComment that while JP work across the state is broadly similar, full standardization has not been achieved.
• Attorney General opinion on forced software adoptionReference to AG Jim Maddox opinion stating commissioners cannot force elected officials to use specific software.
• Commissioner authority to protect county interestsCounterargument that commissioners have duty to defend the county and may override statutory concerns.
• Custodian authority and discretion over records systemsJP asserted inherent authority to refuse a system that poses records integrity risk.
• Frustration over lack of collaborative problem-solvingCommissioners asked whether anyone present has proposed solutions rather than just objections.
• Tyler operational documentation and process guidesOffer of compiled documentation on Tyler Odyssey processes for commissioner review.
• System complexity and workflow comparisonDiscussion of interface differences between Tyler Odyssey and Icon systems.
• Four JP consensus and retention preferenceAll four JPs agree on same preferences: keep Kathy (county clerk) on Tyler and keep other JPs on Net Data.
• Vehicle durability analogy for system selectionCommissioner shared personal experience to illustrate value of letting systems prove themselves over time.
• Disadvantage of staggered adoption during rolloutNote that staggered implementation means multiple offices managing conversion simultaneously.
• Overwhelmed staff concerns during transitionComment recognizing the intense demands on JP staff during Tyler implementation.