Architected disaster recovery across multiple data centers, with a formal backup and retention policy separating backup from archive, and evaluation of AWS, Azure and alternative hosting models against recovery objectives and the cost of meeting them.
The Cecil disaster recovery data center was designed as a facility as well as a network: dual UPS, A and B power paths, diverse carrier entry, and high-availability firewall and IPS pairs with hardware bypass.
Subtopics
- 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.
- Emergency OperationsSeven hurricane activations as Emergency Coordination Officer, each producing an after-action review that fed back into the architecture.
Applied in
- 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.
- 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.
- 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.
- Medical Examiner's Office Enterprise IntegrationNine subsystems federated through one bus across three sites, with the integration layer itself made redundant.
- Cecil Disaster Recovery Data CenterFacility and network design for the recovery site — power, cooling and carrier entry as well as what ran inside.
- 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.
- Enterprise Traffic Management PlatformSixteen years on a platform chosen for what it could be programmed to do rather than what it did on the day — bought as a server proxy in 2006 and ending as continuity infrastructure.
- 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.
- 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.
- 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.
- 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.
- Fort Stewart Mobile Disaster Recovery FleetA fleet of vehicles able to deploy across Georgia during disasters and operate where fixed infrastructure was gone.
- JEA Utility SCADA and Redundant Control SitesSCADA across 24 treatment plant sites on a SONET and ATM core — water and wastewater engineered as separate systems, with the control network separated from the corporate one two decades before the industry had a name for it.
- Emergency Operations Center Wireless NetworkA fault-tolerant Motorola wireless network built specifically for EOC use during natural disasters.
- 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.
Through subtopics
11 further projects reference a subtopic of this entry rather than the entry itself.
- 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.
- 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.
- First Coast Radio SystemRegional shared public safety radio across three system generations — original, retrofit, and full P25 replacement.
- Enterprise GIS PlatformSeventeen years of architecture authority over the City's geospatial estate — and the record of it is a capacity and availability record rather than a mapping one.
- 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.
- Enterprise Audiovisual-over-IP FabricFive sites on one fabric across eighteen years — Council, the Emergency Operations Center, the Ed Ball backup rooms, the Cecil Field backup 911 facility and a youth services agency — so a room stopped being a closed system.
- Fire & Rescue Mobile Gateway and SD-WAN OverlayThree hundred apparatus turned into routed nodes on the enterprise network — dual carriers on private APNs, head-ends behind two providers, and a zero-trust overlay behind a firewall virtual system built for the fleet.
- 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.
- The SHA-2 Migration That Reached DispatchA routine certificate renewal that broke a live estate through its oldest endpoints, stopped station alerting in seventy-plus fire stations, and was resolved by deliberately keeping one service weak.
- Super Bowl XXXIX Surveillance Network and Command CenterThe transport and command center behind the video surveillance estate for the 2005 Super Bowl — evaluated, architected and overseen by the same person, deliberately.
- SOCOM Transportable Wireless KitA two-site voice, video and data package over a point-to-point link where no fixed infrastructure existed.
Career
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.
Attested by
- Emergency Management TrainingNine courses taken in 2006, two years before the Emergency Coordination Officer designation they led to — the Incident Command System sequence through ICS-400, two continuity courses, and the Florida state academy.
See also
Also searched as
- operational resilience
- BCP
- BCDR
- business continuity
- RTO
- RPO
Continuity and recovery filed separately at the time, under the single term the regulated world later settled on.