IT‑IS‑Networking

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.

72 entries placed under 29 capabilities, named as they would be named now. A capability's bar runs from its earliest piece of evidence to its latest, so it is derived from the rows beneath it rather than asserted. Color is the year the capability first appears, on the same ramp as the technology charts. A bar that stops has a cap; the rest are still in use. 5 of these are straight renames of a period term, and the old name is shown under the new one — the practice did not change when the vocabulary did.
1997200020032006200920122015201820212024

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.

Application Portfolio Management & Rationalizationwas “application rationalization” · Application RationalizationApplication Portfolio Management & Rationalization, 2006 onward

Technology Business Management & FinOpsCost transparency, unit economics and showback — the discipline that was called chargeback before it had a framework and an acronym.

Budget Ownership & Public Accountability for SpendEnterprise Technology Budget ProgramBudget Ownership & Public Accountability for Spend, 2011 to 2024
Service Unit Economics & Internal Service PricingData Center Estate and Colocation ProgramService Unit Economics & Internal Service Pricing, 2015 to 2024

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.

Enterprise Performance Management & Published MetricsComprehensive Performance Management — JaxOps, JaxAnalytics, JaxScoreEnterprise Performance Management & Published Metrics, 2013 to 2016

Risk, Security & Compliance GovernanceRisk appetite, control ownership and the regulator on the other side of the table.

Security Governance & Regulator LiaisonSecurity Posture, Incidents and Federal LiaisonSecurity Governance & Regulator Liaison, 2012 to 2024
Third-Party & Venue Risk AssuranceNFL Stadium Cybersecurity ReviewThird-Party & Venue Risk Assurance, 2022 to 2023
Cryptographic Governance & Crypto-AgilityPost-Quantum Cryptography ProgramCryptographic Governance & Crypto-Agility, 2025 to 2026

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.

Reliability & Availability AssuranceReliability Engineering PracticeReliability & Availability Assurance, 2000 to 2023
AI Governance & Readiness AssessmentEnterprise AI Readiness AssessmentAI Governance & Readiness Assessment, 2022 to 2024

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 RationalizationDeepReducing a portfolio assembled independently over decades — platform consolidation, technology lifecycle planning and technical debt reduction.
  • Architect DevelopmentDeepBuilding 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 GovernanceSpecialistReview boards, charters and the design of decision-making bodies — including one written so its chair could be outvoted.
  • Business Intelligence & Performance AnalyticsWorkingArchitecture direction and standards over an enterprise analytics platform, held separately from the group that built the reports on it.
  • Capability RoadmappingDeepCurrent, interim and target-state design, multi-year capability roadmaps, and enterprise architecture assessments across a federated estate.
  • Design DocumentationSpecialistThe 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 ArchitectureSpecialistThe 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 ProgramProposed December 2025 · accepted January 2026 · began February 2026A 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 Build2024–2026An 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 BoardFrom November 2021The 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 Capability2012–2016Architecture 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 Influence2010–2024A 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 Them2010–2024A 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 Program2009–2024The 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 Program2009–2012The 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 Committee2008–2021The 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 Called2007–2022The 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 CharterWhite paper · 2010The 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 RFP2024–2025An 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 Study2023–2024A 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 Pilot2023–2024ShotSpotter acoustic detection tied to Bosch camera estates and Genetec video management, tested against a seconds-not-minutes requirement.
  • Holographic Display EvaluationClosed November 2023Emerging display technology assessed on a borrow-before-buy basis, closed as a zero-dollar equipment evaluation award.
  • Enterprise AI Readiness Assessment2022–2024Two 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 Assessment2022–2023How 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 Review2022–2023A 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 Rollout2019–2023A 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 Pilot2018–2022Whether a building could move to PoE lighting without stranding the legacy lighting already installed.
  • Nine Years to an Integration Platform2014–2023A 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 Position2011–2023A 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 Program2007–2016Nine 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 Assessment2002–2003Estate-wide survey establishing what could be connected, what it would cost, and what had to be built first.
  • Reliability Engineering Practice2000–2023A 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 & ChargebackSpecialistA 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 & CommercialSpecialistA $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 AutomotivePursuit March–April 2025 · headquarters session May 2025 · relationship carried forwardCisco 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 Program2024–2026Seven 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 Program2015–2024Six 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 System2012–2024A 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 Program2012–2021Taking the City of Jacksonville's IT cost modeling, chargeback and allocation approach to peer jurisdictions across multiple conference years.
  • Enterprise Technology Budget Program2011–2024A $48M to $62M annual technology budget, built and defended in public across thirteen cycles for a consolidated city-county government.
  • The Capital Project Evaluation MatrixMethod authored March 2008 · the quadrant workbook created 18 March 2009 · last recorded use 17 May 2023The 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

Public Safety & Emergency Operations

Continuity, activation and the systems that have to hold on the day everything else does not.

Discipline

  • Continuity of OperationsSpecialistA two-hundred-page all-hazards plan whose first instruction is to skip the plan and go straight to the appendices.
  • Deployable InfrastructureDeepKits built for reproducibility — because a capability has to work in the hands of whoever draws it, not only the person who built it.
  • Disaster RecoverySpecialistRecovery architecture across multiple data centers, with out-of-region standby and a formal separation between backup and archive.
  • Emergency OperationsSpecialistSeven hurricane activations as Emergency Coordination Officer, each producing an after-action review that fed back into the architecture.
  • Public Emergency Information PlatformsWorkingThe 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

Documents

  • ITD Continuity of Operations PlanDesign document · 2009Two 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 & RetentionSpecialistClassification schemes that had to survive a court rather than an audit.
  • Public Records LawSpecialistThe workflow by which a citizen's request becomes produced records under Florida statute — designed to make production repeatable rather than heroic.

Programs and engagements

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 ManagementSpecialistA process designed from first principles, proven, and only then fitted with a commercial product — which is the right order.
  • Orchestration & AutomationDeepItential, webMethods, Terraform and Kubernetes — governed on the principle that automation multiplies the blast radius of a mistake.

Programs and engagements

  • Infrastructure and Integration Automation2018–2024Recurring infrastructure and integration work automated on orchestration platforms, governed on the principle that automation multiplies the blast radius of a mistake.
  • JEA Change Management System2000–2003A web-based change management process and system designed from first principles, later carried to the City as the enterprise standard.
  • Enterprise Change Management Standard1999–2012A 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.