BIG-IP LTM and GTM, carried for sixteen years and selected for what it could be programmed to do rather than what it did on the day. The rule language is the reason: redirects, landing pages, analytics logging, source-address handling and access control all lived as rules on the traffic manager rather than as changes to the applications behind it.

Data groups alongside them, so that extending a service to another building was a list entry rather than an edit to a production rule. The application security module went onto the original purchase order because the question asked at design time was whether anything in the path would actually read what crossed it.

Also named on the dispatch platform for XLerator replication and disaster recovery testing, on the solid waste modernization at 12.1.5.2, and in the five-year continuity plan as the global traffic management layer deciding which data center a request reaches.

Where it appears

Declared on each entry rather than listed here, so this page cannot drift from the work it describes. What each entry named is quoted as it stands, with how much of that project rested on it and what stands behind the claim beside it. The first of those drives the height of the surface above.

City of Jacksonville

• Infrastructure and Integration Automation2018–2024BIG-IP / GTM automation on the dispatch paththe project had no deliverable without itdocumented at the time
• Consolidated CAD/911 Dispatch System2016–2024BIG-IP LTM for replication and DR testingthe project had no deliverable without itdocumented at the time
• Solid Waste Systems Modernization2014–2023BIG-IP 12.1.5.2one of the platforms it was built ondocumented at the time
• Enterprise Traffic Management Platform2006–2022BIG-IP LTM and GTM · application security module · iRules · data groupsthe project had no deliverable without itdocumented at the time