Business Architecture & Governance
The half of the record that is not an engineering deliverable. Committees and charters, assessments that ended in a recommendation, a technology budget defended in public, continuity plans and emergency operations, the statutory obligations around records, and the gates that controlled change.
Left to right is time. Each row is one of the 8 capability domains the map below files this work under, in the order that map declares rather than alphabetically. A domain the map lists but no dated project evidences has no load to raise and is not drawn, so this chart can carry fewer rows than the map has domains. Height is the governance work running in that domain in that year, weighted by what failure would have cost — life-safety ×3, a statutory obligation ×2.2, the estate itself ×1.5, an evaluation ×1. Same arithmetic, same viewpoint and same color ramp as the technology surface. This one is measured against its own peak rather than the record's, because itis the whole of the governance record and there is nothing above it to compare against: full red means as much as any governance domain here ever carried. The yellow markers are five-year meridians.
Everything here also appears under Technology, Projects or Documents. This is the same record cut a second way — by what the work was rather than by what it ran on. 72 entries across 6 themes.
The capability map
The same entries read in the vocabulary of 2025 and 2026 — operational resilience, technology business management, change enablement, AI governance — rather than in the words each organization used at the time. Nothing is renamed below this chart: the entries keep their own period language, and where a current term is a straight rename of an older one, the chart says which. The question a reader is really asking is whether the capability is here, not whether the word is.
Architecture Governance & Design AuthorityThe decision rights: who sets a standard, who reviews against it, and what happens when the answer is no.
Capability-Based Planning & Portfolio StrategyBusiness architecture proper: what the organization needs to be able to do, and what it owns that does it.
Technology Business Management & FinOpsCost transparency, unit economics and showback — the discipline that was called chargeback before it had a framework and an acronym.
Operational ResilienceThe term the regulated world settled on for what used to be filed separately as business continuity, disaster recovery and emergency management.
Data, Records & Information GovernanceOwnership, retention and disclosure — and the harder modern version, where the number is published and a citizen can dispute it.
Risk, Security & Compliance GovernanceRisk appetite, control ownership and the regulator on the other side of the table.
Change Enablement & Release GovernanceChange management as ITIL 4 renamed it, and the newer problem underneath it: automation multiplies the blast radius of a mistake.
Technology Assurance & EvaluationWork whose deliverable is a judgment: due diligence, feasibility, and the readiness assessments that now carry an AI column.
By theme
The same record again, grouped the way the work was actually organized at the time.
Architecture Governance
The bodies that issued standards nobody could be compelled to follow, the practice of getting them adopted anyway, and the design authority that does the same job inside a services firm.
Discipline
- Application RationalizationReducing a portfolio assembled independently over decades — platform consolidation, technology lifecycle planning and technical debt reduction.
- Architect DevelopmentBuilding an architecture practice of up to fourteen, on a weekly rhythm and a design review gate, and moving engineers into senior and lead roles.
- Architecture GovernanceReview boards, charters and the design of decision-making bodies — including one written so its chair could be outvoted.
- Business Intelligence & Performance AnalyticsArchitecture direction and standards over an enterprise analytics platform, held separately from the group that built the reports on it.
- Capability RoadmappingCurrent, interim and target-state design, multi-year capability roadmaps, and enterprise architecture assessments across a federated estate.
- Design DocumentationThe discipline of writing a design down, revising it under review, and stating its own risk plainly — carried to revision 16, 26 and 35 on the largest programs.
- Enterprise ArchitectureThe discipline of placing technology correctly in a business's data flows, risk posture and cost structure — the through-line of the last two decades.
Programs and engagements
- Post-Quantum Cryptography ProgramA thirty-six-month joint research engagement with the group's parent company, originated rather than assigned — proposed December 2025, accepted January 2026, transacted at CFO level between two companies.
- Enterprise Architecture Practice BuildAn architecture practice of up to fourteen, built and run to a design review gate and a weekly rhythm — so engagements were delivered against one design language rather than individual preference.
- Architecture Review BoardThe successor governance body, and the first with a budget attached — a five-to-ten year capital plan rather than a rolling list of purchases.
- Enterprise Business Intelligence Platform and CapabilityArchitecture authority over the City's analytics platform, held deliberately apart from the group that built the reports — with the capability hired and taught to a published standard.
- Architecture by InfluenceA CIO's instruction — manage by influence rather than by headcount — and the fourteen years of practice built on it, in an estate where nothing could be mandated anyway.
- Proving Products Before Recommending ThemA standing part of the architecture function rather than an occasional exercise — pilot against the estate's own conditions, then hand it over with the operators trained.
- Enterprise Architecture ProgramThe EA practice itself — business, information, technical and solution viewpoints, with strategy, assessments and multi-year capability roadmaps for a platform shared by agencies that answered to different elected officers.
- Enterprise Security Committee and Governance ProgramThe city's enterprise architecture review board, chaired and chartered — and, in the years before the City had a Chief Security Officer, the body where security policy was set.
- Architecture Technology Governance CommitteeThe second governance body, and the one where architecture decisions were actually worked — with the operations and delivery teams in the room rather than only architects.
- Requirements or Findings: When Architecture Gets CalledThe same function with the same authority produces requirements on one capital program and findings on another — and the only variable is whether the project called it before or after the build.
Documents
- Enterprise Security Committee CharterThe charter for the body that served as the city's enterprise architecture review board — written so its chair could be outvoted. Revision 5.0.
Assessment & Advisory
Work whose deliverable was a judgment rather than a build — and which was worth most when it ended in a defensible no.
Programs and engagements
- Municipal Infrastructure Assessment to RFPAn infrastructure assessment for a town government, scoped from the start to become the foundation of its own procurement rather than a proposal for follow-on work.
- Citywide Network Total Cost of Ownership StudyA weighted scoring instrument for a manufacturer standard ahead of a refresh — which earned itself within three weeks, when a reseller's savings claim turned out to be priced against the wrong baseline.
- Gunshot Detection and Active-Shooter Tracking Feasibility PilotShotSpotter acoustic detection tied to Bosch camera estates and Genetec video management, tested against a seconds-not-minutes requirement.
- Holographic Display EvaluationEmerging display technology assessed on a borrow-before-buy basis, closed as a zero-dollar equipment evaluation award.
- Enterprise AI Readiness AssessmentTwo years of technology review and systems analysis on where AI could fit a consolidated city-county government — and, as often, where it could not yet be defended.
- PLC Alarm Notification over Cellular AssessmentHow a controller raises an alarm that reaches a human when the site has no operator in front of it and no network worth the name.
- NFL Stadium Cybersecurity ReviewA league Internal Audit assessment of the city-owned stadium against the Department of Homeland Security's stadium cybersecurity guidelines, reaching the building's control systems as much as its enterprise IT.
- Electronic Paper Tablet Assessment and RolloutA personal device that became a supported city endpoint — after the enterprise web filtering estate I had built turned out to be the thing breaking it.
- Building Automation and PoE Lighting Feasibility PilotWhether a building could move to PoE lighting without stranding the legacy lighting already installed.
- Nine Years to an Integration PlatformA platform question carried across two evaluations and nine years — lost in 2014 to a vendor who could discount faster than a migration could be justified, and answered in 2023 by attaching it to a building.
- The Virtual Desktop PositionA decade of evaluation whose deliverable was a refusal — two platforms piloted and closed by change order, and an objection that held for eight years.
- Automated Asset Tracking ProgramNine years carrying the asset tracking agenda across two titles, argued on billing accuracy rather than loss prevention — and ending in a position and a scoped proof of concept rather than a deployment.
- Florida Rock Facilities Technology AssessmentEstate-wide survey establishing what could be connected, what it would cost, and what had to be built first.
- Reliability Engineering PracticeA reliability toolchain bought for one utility engagement in 2000, carried into a city estate, and still running twenty-three years later — availability as a computed number rather than a drawn assertion.
Cost, Budget & Commercial
A technology budget built, allocated and defended in public, and services costed and sold against commercial alternatives.
Discipline
- IT Cost Modeling & ChargebackA full technology budget allocated across every agency by measured consumption rather than negotiation — designed in 2012, first implemented in 2013, owned for eleven budget cycles.
- Portfolio Planning & CommercialA $48M–$62M annual budget built, allocated and defended in public — plus TCO, ROI, build-versus-buy and vendor management.
Programs and engagements
- Enterprise Agreement Pursuit — Global AutomotiveCisco services subject-matter expert on a bid for a global automotive manufacturer's North American arm — a two-day clarification window, an affiliate's engineering bench as the differentiator, a loss, and a headquarters meeting four weeks later.
- Vendor and Partner ProgramSeven technology and service partners brought in across two years for capability the practice did not have or could not scale, with a formal manufacturer specialization track behind it.
- Data Center Estate and Colocation ProgramSix tiered sites for the city and five external agencies — and a municipal IT department selling colocation against commercial carriers, and winning on engineering.
- CBM Cost Model and Customer Billing SystemA full technology budget allocated across every agency by measured consumption rather than negotiation — designed in 2012, first implemented in 2013, owned for eleven budget cycles.
- FLGISA Cost Model ProgramTaking the City of Jacksonville's IT cost modeling, chargeback and allocation approach to peer jurisdictions across multiple conference years.
- Enterprise Technology Budget ProgramA $48M to $62M annual technology budget, built and defended in public across thirteen cycles for a consolidated city-county government.
- The Capital Project Evaluation MatrixThe weighted scoring instrument behind the City's technology capital funding — and the single workbook built in March 2009 that was still deciding a security product purchase fourteen years later.
Documents
- IT Cost Modeling and Chargeback for Local GovernmentConference presentations to Florida jurisdictions on moving from pooled cost allocated by PC count to consumption-based chargeback.
- Customer Billing System Process DocumentationThe end-to-end process behind the city's IT chargeback platform, spanning sixteen functional lanes and eight systems of record. Co-authored.
Public Safety & Emergency Operations
Continuity, activation and the systems that have to hold on the day everything else does not.
Discipline
- Continuity of OperationsA two-hundred-page all-hazards plan whose first instruction is to skip the plan and go straight to the appendices.
- Deployable InfrastructureKits built for reproducibility — because a capability has to work in the hands of whoever draws it, not only the person who built it.
- Disaster RecoveryRecovery architecture across multiple data centers, with out-of-region standby and a formal separation between backup and archive.
- Emergency OperationsSeven hurricane activations as Emergency Coordination Officer, each producing an after-action review that fed back into the architecture.
- Public Emergency Information PlatformsThe public side of emergency management — where a citizen-facing service is the channel residents are told to use, and its availability stops being a web operations concern.
Programs and engagements
- Ed Ball Hearing Room — Backup Council ChambersA committee room specified to run a City Council meeting if the Chamber were unavailable — which makes it a continuity facility for the legislative body, not a meeting room.
- Disaster Recovery Validation and Application TieringCriticality bound to recovery objectives in an instrument rather than a narrative, and a definition of "tested" that the estate could not yet meet — reported rather than softened.
- Republican National Convention — National Special Security EventCritical Infrastructure Subcommittee for a national special security event relocated to the city eight weeks into planning — first-responder mobility, venue design, carrier redundancy, and federal sensors landed on a municipal estate.
- Consolidated CAD/911 Dispatch SystemTwo agencies with separate commands onto one dispatch platform, cutting response times from five to ten minutes down to one to two.
- Cecil Disaster Recovery Data CenterFacility and network design for the recovery site — power, cooling and carrier entry as well as what ran inside.
- E911 Caller Location and Backup Answering PointMaking the dispatcher see a room instead of a phone number — then building a second answering point so the dispatch center was not a single point of failure.
- JaxReady — Public Emergency Preparedness PlatformThe City's evacuation and flood zone lookup, on mobile and the public web — carried into the emergency public information chain, and tested as critical infrastructure rather than as a website.
- ITD Continuity of Operations PlanA two-hundred-page all-hazards continuity plan whose first instruction is to skip the plan and go straight to the appendices.
- Emergency Operations Center ActivationsSeven activations keeping public-safety and EOC systems available under hurricane conditions — in Logistics from 2006 and as the division's Emergency Coordination Officer from 2008 — with each after-action review fed back into the architecture.
- Fort Stewart Mobile Disaster Recovery FleetA fleet of vehicles able to deploy across Georgia during disasters and operate where fixed infrastructure was gone.
- Florida National Guard Continuity of Operations PlanThe first COOP of the career — the discipline carried forward into the City of Jacksonville plan a decade later.
- First Coast Radio SystemRegional shared public safety radio across three system generations — original, retrofit, and full P25 replacement.
Documents
- ITD Continuity of Operations PlanTwo hundred pages, all-hazards, sole author. Aligned to the county emergency management plan and built on Incident Command System doctrine.
Records, Compliance & Accountability
Where the retention rule is a law rather than a policy, and where the numbers are a public record once published.
Discipline
- Data Classification & RetentionClassification schemes that had to survive a court rather than an audit.
- Public Records LawThe workflow by which a citizen's request becomes produced records under Florida statute — designed to make production repeatable rather than heroic.
Programs and engagements
- Comprehensive Performance Management — JaxOps, JaxAnalytics, JaxScoreThe division's flagship analytics program in three layers, ending in a public dashboard — where disclosed numbers constrain the model underneath rather than the presentation on top.
- Security Posture, Incidents and Federal LiaisonWorking directly with the City's Chief Security Officer on posture, governance, attacks and breaches — and alongside Homeland Security and the FBI when an incident reached that far.
- Public Records Request MethodologyThe workflow by which a citizen's request becomes produced records under Florida statute.
- Records Retention and Disposition StandardsClassification, retention and defensible disposition under Florida public records law, across an estate where criminal justice records, patient information, court records and elections data shared one platform.
Change & Release Governance
The gates. Automation multiplies the blast radius of a mistake, which is an argument for more governance rather than less.
Discipline
- Change ManagementA process designed from first principles, proven, and only then fitted with a commercial product — which is the right order.
- Orchestration & AutomationItential, webMethods, Terraform and Kubernetes — governed on the principle that automation multiplies the blast radius of a mistake.
Programs and engagements
- Infrastructure and Integration AutomationRecurring infrastructure and integration work automated on orchestration platforms, governed on the principle that automation multiplies the blast radius of a mistake.
- JEA Change Management SystemA web-based change management process and system designed from first principles, later carried to the City as the enterprise standard.
- Enterprise Change Management StandardA change process designed for a utility in 1999, carried into the City as its enterprise standard, and handed to operations in 2012 — after which it outlasted both commercial platforms bought to run it.