# What to sense at SFB, and in what order (2026-11-06)

Research for the Mission Studio plan (`stellarview/docs/plans/mission-studio-interchange-collector.md`, "Also now"). Public sources only. Nobody at the Authority, its board or any vendor was contacted, and no form was submitted. RFP 2027-006 is an open solicitation.


The machine-readable copy is `what-to-sense-2026-11-06.json` beside this file. It has the same 74 items, 124 event types with a class each, the phases and the sources, so MissionSight's catalogue can seed from it.

## What this starts from

- **The pass 3 sensor plan** (`projects/sfb-terminal/04-plan/sensor-plan.json`): 195 points on 15 classes. 73 are already reported, 64 are to confirm at the site tour and 58 need a sensor. It places no camera, gunshot, fire device or transponder positions. The rule it follows is REQ-SFB-040: build no sensor for equipment that already reports.
- **The sensor catalogue** (`sensor-catalogue-2026-10-30.md`): 15 asset classes with makers, buses, collectors and the realities of sourcing (Florida licensing, airside access, FAA equipment rules, federal funds).
- **The VT and BHS research** (`terminal-assets-vt-bhs-2026-11-06.md`): 12 elevators and 6 escalators by the Authority's count, 8 inbound and 3 outbound baggage systems, and who maintains what.
- **The POC screens** "Sensor Catalogue", "Existing Sensors" and "Sensor Gaps (concept)" (`poc/screens.json`). None of the Connect group's screens carries a REQ-SFB tag today.
- **The RFP requirements** (`staging/e2-sanford/requirements.md`): REQ-SFB-017 to 026 name the systems; REQ-SFB-005 lets the Authority set the order of the five asset classes; REQ-SFB-040 to 042 set the sensor rules.

This file adds the domains the pass 3 plan did not cover (water compliance, fire records, IT rooms, restrooms, passenger flow, curb, the airfield beyond lighting, the fuel farm, drones and the environment), a priority on every item, and event types.

## How to read the tables

- **Priority.** P1 safety or compliance. P2 uptime or cost. P3 passenger experience. P4 nice to have. These are ours. The RFP's own P-numbers are its section groups and mean something else.
- **Reports today?** yes: the asset or its controller reports it. likely: usually, often behind a paid option or a contract. partial: some of it. no: nothing reports it. Where it is yes or likely, REQ-SFB-040 applies and no sensor is bought.
- **Phase.** The rollout phase below (0 to 5).
- **Basis.** V: read on a primary page, this session or in the cited research file. S: secondary or a search extract; read the primary before quoting it in the bid. I: our inference.
- **Event types** are named `domain.asset.state`, as the plan's `bhs.conveyor.blocked`. Each has a class for MissionSight: state, alarm, reading, count, fault or document. Records such as inspections are events of class document, so a PDF from "a weird system" lands in the same catalogue.

## The items, by domain

### Vertical transport

| ID | What | Measures | Why it matters | Reports today? (via) | Cheapest way otherwise | Event types | P | Phase | Source | Basis |
|---|---|---|---|---|---|---|---|---|---|---|
| vt-01 | Elevator run state, faults and entrapments | car in service or out, fault codes, a passenger trapped | safety, uptime: A trapped passenger is a safety call. Out-of-service time is the RFP's VT measure (REQ-SFB-020). SFB: 12 elevators per the Authority; 33 of 44 plan points to confirm. | likely (OEM cloud API (Schindler Ahead, KONE 24/7, Otis ONE), often a paid option in the maintenance contract) | The OEM data option, bought at modernisation (Elevator 5 is funded now). Retrofit monitor only where the controller exposes nothing, fitted by the elevator contractor (Fla. Stat. 399) | `vt.elevator.state_changed` (state)<br>`vt.elevator.fault` (fault)<br>`vt.elevator.entrapment` (alarm) | P1 | 1 | S-CAT, S-VT, S-PLAN | V |
| vt-02 | Elevator door cycles, door faults and levelling | door operations, reopen faults, stop accuracy | uptime, safety: Doors cause most call-outs; poor levelling is a trip hazard. | likely (OEM controller and cloud) | OEM data option | `vt.elevator.door_fault` (fault)<br>`vt.elevator.levelling_out_of_band` (alarm) | P2 | 2 | S-CAT, S-PLAN | I |
| vt-03 | Elevator pit water | water present in the pit | uptime, safety: Elevator 5 had water in the pit (2023). Water in a pit takes a car out and damages equipment. | no (nothing standard) | A float or leak sensor in the pit, fitted by the elevator contractor, read by the BMS or a LoRaWAN gateway | `vt.elevator.pit_water` (alarm) | P2 | 3 | S-VT | I |
| vt-04 | Escalator running, stopped and safety trips | run state; comb plate, handrail and step switch trips | safety, experience, uptime: A trip can mean a fall. A stopped escalator at the checkpoint builds a queue (the Escalator 3 example). SFB: 6 escalators, all modernised by Nov 2024. | likely (OEM cloud (Schindler Ahead, KONE 24/7) or the controller) | OEM data option; else a current transducer on the drive gives run or stop | `vt.escalator.stopped` (state)<br>`vt.escalator.safety_trip` (alarm)<br>`vt.escalator.restarted` (state) | P1 | 1 | S-CAT, S-PLAN | V |
| vt-05 | Escalator handrail-step speed, step chain and drive vibration | speed difference, chain elongation, bearing vibration and temperature | uptime, cost: Early warning before a trip or a long repair. | partial (Some OEM packages; often not) | Wireless vibration and temperature on the drive (SKF IMx-1 class) with a gateway in mesh range | `vt.escalator.vibration_high` (alarm)<br>`vt.escalator.handrail_speed_mismatch` (alarm) | P2 | 3 | S-CAT, S-PLAN | V |

### BHS

| ID | What | Measures | Why it matters | Reports today? (via) | Cheapest way otherwise | Event types | P | Phase | Source | Basis |
|---|---|---|---|---|---|---|---|---|---|---|
| bhs-02 | BHS emergency stops | E-stop pulled and reset | safety: An E-stop means a person was at risk or a hand is in the system. | yes (PLC) | Same gateway as bhs-01 | `bhs.estop.activated` (alarm)<br>`bhs.estop.reset` (state) | P1 | 2 | S-PLAN | I |
| bhs-03 | Motor run and fault per section | run, trip, overload | uptime: Faults locate the stopped section for the maintainer. | yes (PLC) | Same gateway | `bhs.motor.fault` (fault)<br>`bhs.motor.state_changed` (state) | P2 | 2 | S-CAT, S-PLAN | V |
| bhs-04 | Claim carousel run and speed | running, stopped, belt or plate speed | experience, uptime: A stopped carousel is seen by every arriving passenger. SFB: 24 of 32 carousel points reported. | yes (PLC) | Same gateway | `bhs.carousel.state_changed` (state) | P2 | 2 | S-PLAN | I |
| bhs-05 | Bag throughput and first and last bag times | bags per hour per line; first and last bag on each carousel | experience: Bag delivery time is a passenger measure and an airline service measure. | likely (PLC counters; a BHS SCADA if fitted) | PLC counter tags through the same gateway; else a photo-eye count | `bhs.throughput.count` (count)<br>`bhs.claim.first_bag` (state)<br>`bhs.claim.last_bag` (state) | P3 | 4 | S-CAT | I |
| bhs-06 | Gearbox and motor vibration and temperature | vibration, temperature on drives | uptime, cost: Condition monitoring before a drive fails; Vanderlande does this at Heathrow. | no (nothing standard on older drives) | Banner QM30VT2 on Modbus to the gateway, or SKF IMx-1; fitted under the Davis Industrial BHS contract | `bhs.drive.vibration_high` (alarm)<br>`bhs.drive.temperature_high` (alarm) | P2 | 3 | S-CAT, VDL-LHR, S-PLAN | V |
| bhs-07 | Inline checked-baggage screening state | screening machine state | safety: TSA equipment. Out of scope: read only what TSA agrees to share, model nothing inside. SFB: Owner of inline screening not confirmed. | unknown (TSA and its contractor) | None by us | none | P4 | 5 | S-CAT | I |

### Boarding bridges and PCA/GPU

| ID | What | Measures | Why it matters | Reports today? (via) | Cheapest way otherwise | Event types | P | Phase | Source | Basis |
|---|---|---|---|---|---|---|---|---|---|---|
| pbb-01 | Bridge faults and drive motor current | fault codes, drive and bogie current | uptime, cost: Jet bridge repairs drove R&M 27% over budget in April 2026. SFB: 16 bridges; 32 of 32 plan points reported. | yes (Allen-Bradley PLC on each bridge; 'Not Connected') | Read-only gateway on the PLC; OPC UA where firmware allows | `pbb.bridge.fault` (fault)<br>`pbb.bridge.state_changed` (state) | P2 | 2 | S-CAT, S-PLAN | V |
| pbb-02 | Auto-level and cab position | auto-level active and faults, cab and rotunda position, docked | safety: An auto-level fault while docked can damage the aircraft door or the bridge. | yes (Bridge PLC) | Same gateway | `pbb.autolevel.fault` (fault)<br>`pbb.bridge.docked` (state)<br>`pbb.bridge.undocked` (state) | P1 | 2 | S-CAT, S-PLAN | I |
| pbb-03 | PCA and GPU state | PCA running and supply air temperature; GPU connected and output | cost, experience: Without both connected the aircraft keeps its APU running (fuel, noise, emissions). | likely (The bridge PLC or the unit's own controller; JBT iOPS covers GPU and PCA) | Read from the bridge PLC; a current transducer where nothing reports | `gate.pca.state_changed` (state)<br>`gate.gpu.connected` (state)<br>`gate.gpu.disconnected` (state) | P2 | 2 | JBT-IOPS, S-CAT | S |
| pbb-04 | Bridge hours and docking counts | hours in use, dockings | cost: Use-based maintenance in place of calendar maintenance. | yes (Bridge PLC) | Same gateway | `pbb.usage.count` (count) | P3 | 2 | S-CAT | I |

### HVAC

| ID | What | Measures | Why it matters | Reports today? (via) | Cheapest way otherwise | Event types | P | Phase | Source | Basis |
|---|---|---|---|---|---|---|---|---|---|---|
| hvac-01 | AHU temperatures, fan state and alarms | supply, return and mixed air; fan and VFD state; alarms | uptime, experience: Comfort and uptime in a Florida terminal. The BMS stays the control system (REQ-SFB-017). | yes (Schneider EcoStruxure BMS (BACnet; MQTT publish from V3.2)) | Read EcoStruxure; no new sensor | `hvac.ahu.alarm` (alarm)<br>`hvac.ahu.reading` (reading) | P2 | 2 | S-CAT, S-PLAN, RFP | V |
| hvac-02 | AHU filter pressure drop | differential pressure across filters | cost, experience: Filters changed on condition; Florida humidity loads coils and filters. | partial (BMS where fitted) | A BACnet or Modbus differential pressure transmitter bound in EcoStruxure | `hvac.ahu.filter_dirty` (alarm) | P2 | 3 | S-CAT, S-PLAN | S |
| hvac-03 | Chiller status, chilled water and kW | state, supply and return temperature, flow, kW, alarms | uptime, cost: Five chillers carry the terminal. Energy is the largest controllable cost. | likely (Chiller controller (BACnet or Modbus card or activation key) and EcoStruxure) | Confirm each chiller's comms option; add a BTU meter where missing | `hvac.chiller.alarm` (alarm)<br>`hvac.chiller.reading` (reading) | P2 | 2 | S-CAT | V |
| hvac-04 | Refrigerant leak in the chiller plant room | refrigerant concentration | safety: A leak in an enclosed plant room is a life-safety hazard to the person who walks in. | partial (A detector may exist in the plant; to confirm) | A Modbus refrigerant detector (Bacharach MGS-400 class) read by the BMS | `hvac.plant.refrigerant_leak` (alarm) | P1 | 1 | S-CAT | S |
| hvac-05 | Cooling tower water treatment | conductivity, biocide feed, controller alarms | safety, compliance: A cooling tower calls for a Legionella water management program under ASHRAE 188. SFB: Cooling tower is a guessed row in the asset list. | likely (The water treatment controller) | Read the treatment controller; log the program's checks as documents | `hvac.cooling_tower.treatment_alarm` (alarm)<br>`hvac.cooling_tower.check_recorded` (document) | P1 | 2 | ASHRAE-188, S-LIST | S |
| hvac-06 | Space temperature, humidity and CO2 in holdrooms | room conditions | experience: Comfort and air quality where passengers wait. | partial (BMS room sensors where fitted) | Schneider SpaceLogic SLP class on BACnet (non-stock, lead time) | `hvac.space.out_of_band` (alarm) | P3 | 4 | S-CAT | V |
| hvac-07 | Mechanical room temperature and humidity | room conditions | uptime: Overheating plant rooms shorten equipment life. SFB: 8 plan points need a sensor. | no (nothing named) | A BACnet or LoRaWAN room sensor | `facility.room.temperature_high` (alarm) | P2 | 3 | S-PLAN | I |

### Power and generators

| ID | What | Measures | Why it matters | Reports today? (via) | Cheapest way otherwise | Event types | P | Phase | Source | Basis |
|---|---|---|---|---|---|---|---|---|---|---|
| pwr-01 | Generator run state, fuel, battery and alarms | running, fuel level, battery voltage, coolant, oil pressure, alarms | safety, compliance: Emergency power for life safety. A failed start is found in a test or in an outage. SFB: New sets from the Generator Replacement project (Sept 2026). | yes (Generator controller (Cat EMCP 4.4 or Kohler APM603 class: Modbus, BACnet on Kohler); 'Not Connected') | Read-only edge gateway; never the control path | `power.generator.state_changed` (state)<br>`power.generator.alarm` (alarm)<br>`power.generator.fuel_low` (alarm) | P1 | 1 | S-CAT, S-PLAN | V |
| pwr-02 | Transfer switch position | normal or emergency source | safety: Shows when the terminal is on generator. | yes (ATS controller (ASCO 7000 class, Modbus)) | Same gateway | `power.ats.transferred` (state)<br>`power.ats.returned` (state) | P1 | 1 | S-CAT, S-PLAN | V |
| pwr-03 | Monthly generator exercise record | each test run, duration and load | compliance: NFPA 110 asks for a monthly exercise of at least 30 minutes under load. The record proves it. | yes (Derived from pwr-01 run state and kW) | No new sensor; the Collector derives the record and files it to the CMMS | `power.generator.test_completed` (document) | P1 | 1 | NFPA-110 | S |
| pwr-04 | Main electrical metering | kW, kWh, power quality at the service | cost: Energy cost and demand charges. | likely (Switchgear meters or the utility's interval data) | Read existing meters; add a Modbus meter only where none | `power.meter.reading` (reading)<br>`power.demand.peak` (reading) | P2 | 2 | RFP | I |
| pwr-05 | Electrical room temperature | room temperature | uptime, safety: Hot switchgear rooms fail equipment. SFB: 2 plan points need a sensor. | no (nothing named) | Room sensor; thermal survey optional | `facility.room.temperature_high` (alarm) | P2 | 3 | S-PLAN | I |

### Water, leaks and backflow

| ID | What | Measures | Why it matters | Reports today? (via) | Cheapest way otherwise | Event types | P | Phase | Source | Basis |
|---|---|---|---|---|---|---|---|---|---|---|
| wtr-01 | Water service flow | flow and totals at the service | cost, uptime: Night flow above a baseline means a leak somewhere. SFB: 1 plan point needs a sensor. | no (the utility meter, read monthly) | A pulse or ultrasonic meter on the service; the utility's AMI data if offered | `water.service.flow` (reading)<br>`water.leak.suspected` (alarm) | P2 | 3 | S-PLAN | I |
| wtr-02 | Floor leak detection | water on the floor in plant rooms, IT rooms, above the BHS | uptime, cost: Water over a conveyor or in an IDF stops operations. SFB: 4 plan points in mech rooms. | no (nothing named) | Leak sensors on LoRaWAN or wired to the BMS | `water.leak.detected` (alarm) | P2 | 3 | S-PLAN | I |
| wtr-03 | Backflow preventer test status | annual test date and result per device | compliance: Florida's cross-connection rule; utilities require an annual test. A record, not a sensor. | no (the tester's report, perhaps in the CMMS) | File the test report as a document event through the Collector | `water.backflow.test_recorded` (document)<br>`water.backflow.test_due` (document) | P1 | 0 | FAC-62-555.360 | S |
| wtr-04 | Pump and lift station run, fault and high level | pump state, wet well level | uptime, compliance: A failed lift station overflows sewage. SFB: pump-station row in the asset list. | likely (A panel alarm dialler or SCADA) | Read the panel; add a level switch output | `water.pump.fault` (fault)<br>`water.wetwell.high_level` (alarm) | P2 | 2 | S-LIST | I |

### Fire and life safety (systems only)

| ID | What | Measures | Why it matters | Reports today? (via) | Cheapest way otherwise | Event types | P | Phase | Source | Basis |
|---|---|---|---|---|---|---|---|---|---|---|
| fire-01 | Fire alarm panel alarm, trouble and supervisory | panel states per device | safety, compliance: The core life-safety system. The twin reads it, never writes (Fla. Stat. 633.3482 licensing). SFB: Panel make not confirmed. | yes (The FACP, through a UL-listed BACnet gateway (Notifier BACNET-GW-3, Simplex BACpac class)) | Read the listed gateway; no new device | `fire.panel.alarm` (alarm)<br>`fire.panel.trouble` (alarm)<br>`fire.panel.supervisory` (alarm) | P1 | 1 | S-CAT | V |
| fire-02 | Sprinkler flow, tamper and fire pump | flow switch, valve tamper, pump running | safety: A closed valve or a running pump is an impairment or a fire. | yes (FACP supervisory points) | Same gateway | `fire.sprinkler.flow` (alarm)<br>`fire.valve.tamper` (alarm)<br>`fire.pump.running` (alarm) | P1 | 1 | S-CAT | V |
| fire-03 | Inspection and test records | fire alarm and sprinkler inspections | compliance: Proof that tests happened. A record, not a sensor. | no (the contractor's reports) | Document events through the Collector | `fire.inspection.recorded` (document)<br>`fire.inspection.due` (document) | P1 | 0 | S-CAT | I |

### IT and network rooms

| ID | What | Measures | Why it matters | Reports today? (via) | Cheapest way otherwise | Event types | P | Phase | Source | Basis |
|---|---|---|---|---|---|---|---|---|---|---|
| it-01 | IDF and MDF temperature | inlet or room temperature and humidity | uptime: Network rooms hold every other system's data path. ASHRAE TC 9.9 recommends 18 to 27 C inlet. SFB: 4 IT rooms; 4 plan points need a sensor. | no (nothing named) | An SNMP or BACnet room sensor | `it.room.temperature_high` (alarm) | P2 | 3 | ASHRAE-TC99, S-PLAN | S |
| it-02 | UPS status | on battery, battery health, load | uptime: A UPS on battery means the room has minutes left. SFB: 4 plan points to confirm. | likely (UPS network card (SNMP)) | Read the card | `it.ups.on_battery` (alarm)<br>`it.ups.battery_fault` (fault) | P2 | 2 | S-PLAN | I |
| it-03 | Wi-Fi access point and switch health | AP up or down; clients per AP | uptime, experience: AP client counts also give occupancy (pax-02) with no new sensor. SFB: 165 APs are a guessed row. | yes (The wireless controller or network manager) | Read the controller | `it.ap.down` (alarm)<br>`it.ap.clients` (count) | P2 | 2 | S-LIST | I |

### Restrooms and cleaning

| ID | What | Measures | Why it matters | Reports today? (via) | Cheapest way otherwise | Event types | P | Phase | Source | Basis |
|---|---|---|---|---|---|---|---|---|---|---|
| rr-01 | Restroom usage counts | people in per restroom | experience, cost: Clean on use, not on a clock. Washroom cleanliness is an ACI ASQ measure. | no (nothing named) | A door people counter on LoRaWAN; usage thresholds raise a clean task (CVG, Syracuse) | `restroom.usage.count` (count)<br>`restroom.clean.due` (state) | P3 | 4 | ACI-ASQ, TRAX-SYR, CVG-WC | S |
| rr-03 | Fixture leaks and overflows | water under fixtures | cost: Floods spread to rooms below. | no (nothing named) | Leak sensor | `water.leak.detected` (alarm) | P3 | 4 | none | I |
| rr-04 | Consumables and odour | soap, paper, ammonia | experience: Nice to have once usage counts work. | no (nothing named) | Dispenser level sensors; odour sensors | `restroom.supply.low` (alarm)<br>`restroom.odour.high` (alarm) | P4 | 5 | CVG-WC | S |

### Passenger flow and queues

| ID | What | Measures | Why it matters | Reports today? (via) | Cheapest way otherwise | Event types | P | Phase | Source | Basis |
|---|---|---|---|---|---|---|---|---|---|---|
| pax-01 | Checkpoint queue wait | minutes from queue entry to the checkpoint | experience: IATA rates each subsystem on space and maximum waiting time. TSA publishes national totals only. | no (nothing public per airport) | Measured outside the checkpoint, with TSA's agreement, by camera analytics inside the VMS boundary or by device travel time (Schiphol). Never model the checkpoint inside | `pax.queue.wait_time` (reading) | P3 | 4 | IATA-LOS, TSA-VOL, SCHIPHOL | S |
| pax-02 | Holdroom and claim hall occupancy | people present per space | experience: Crowding and seating; cleaning and staffing by load. SFB: 6 plan points to confirm. | partial (Wi-Fi client counts (it-03)) | Wi-Fi counts first; camera counts in the VMS second | `pax.space.occupancy` (count) | P3 | 4 | S-PLAN, SCHIPHOL | I |
| pax-03 | Ticket counter queues | queue length | experience: Airline and Authority staffing. | no (nothing named) | Camera analytics in the VMS | `pax.queue.length` (reading) | P4 | 5 | IATA-LOS | I |
| pax-04 | Flight status | scheduled, estimated and actual times; gate; carousel | experience, uptime: The context for every other event (which bags, which bridge, which holdroom). | yes (FIDS and the airlines' feeds) | Read the FIDS feed | `flight.status_changed` (state) | P2 | 2 | RFP | I |

### Parking and curb

| ID | What | Measures | Why it matters | Reports today? (via) | Cheapest way otherwise | Event types | P | Phase | Source | Basis |
|---|---|---|---|---|---|---|---|---|---|---|
| park-01 | Parking occupancy by zone | spaces free per zone; entries and exits | experience, cost: Revenue and the passenger's first minutes. | yes (Skidata PARCS (SKIDATA Connect partner API)) | Read SKIDATA Connect | `parking.zone.occupancy` (count)<br>`parking.gate.fault` (fault) | P3 | 4 | S-CAT | V |
| park-02 | Per-space sensors in the new remote lot | space occupied | experience: Cheaper while the lot is built (about 800 spaces, due Nov or Dec 2026) than cut in later. SFB: Time-boxed: decide before paving. | no (nothing) | LoRaWAN per-space sensors or conduit only, specified now | `parking.space.occupied` (state) | P3 | 4 | S-CAT | V |
| park-03 | Curb dwell | vehicle dwell at the curb | experience, safety: Double parking and congestion at the terminal front. | no (nothing) | Camera analytics inside the VMS | `curb.vehicle.dwell_exceeded` (alarm) | P3 | 4 | S-CAT | S |

### Airfield

| ID | What | Measures | Why it matters | Reports today? (via) | Cheapest way otherwise | Event types | P | Phase | Source | Basis |
|---|---|---|---|---|---|---|---|---|---|---|
| af-01 | Lighting circuit faults | regulator step and output current, insulation resistance, vault alarms | safety, compliance: Part 139 lighting must work. Maintenance follows AC 150/5340-26C. SFB: 8 runway plan points. | yes (The ALCMS and its regulators; closed network (AC 150/5345-56B)) | A one-way export agreed with the ALCMS maker | `airfield.lighting.circuit_fault` (fault)<br>`airfield.lighting.step_changed` (state) | P1 | 1 | S-CAT, FAA-5340-26C, FAA-5345-56B | V |
| af-02 | Individual lamp outages | lamps out per circuit | safety, compliance: The regulator cannot see single lamps. SFB: Mission already drafted in MissionSight. | no (lamp-level monitoring is an add-on (ADB SAFEGATE LINC 360)) | The nightly drone pass (MissionSight edge-lights mission) and the self-inspection record | `airfield.light.out` (alarm) | P1 | 3 | S-CAT, MS-EVENTS | V |
| af-03 | Self-inspection records | daily Part 139 inspection results | compliance: Required daily; records kept 12 months. Held in Simplify i3. | yes (Simplify i3) | Read i3; no sensor | `airfield.inspection.recorded` (document)<br>`airfield.discrepancy.opened` (alarm) | P1 | 0 | CFR-139.327, RFP | S |
| af-04 | FOD found | object, place, time | safety, compliance: FOD guidance updated in AC 150/5210-24A; CertAlert 24-03. | partial (self-inspection records) | Records first; drone sweeps; fixed FOD radar (AC 150/5220-24) only after a business case | `airfield.fod.found` (alarm)<br>`airfield.fod.removed` (state) | P1 | 0 | FAA-5210-24A, FAA-CA-24-03, FAA-5220-24 | S |
| af-05 | Standing water and ponding | water on pavement after rain | safety: Florida rain; braking. Pooling is better found by survey than by one embedded sensor. | no (nothing) | Lidar or drone survey after heavy rain; a Vaisala DRS511 class sensor only at a known spot | `airfield.surface.water_film` (reading)<br>`airfield.ponding.found` (alarm) | P1 | 3 | S-CAT | V |
| af-06 | Pavement condition | distress, PCI | cost, safety: FDOT inspects on about a three-year cycle; AC 150/5380-6C covers distress and repair. | partial (FDOT's pavement reports) | Drone or lidar survey between FDOT cycles | `pavement.distress.found` (document)<br>`pavement.pci.updated` (reading) | P2 | 3 | S-CAT, FAA-5380-6C | V |
| af-07 | Wildlife sightings and strikes | species, count, place; strikes | safety, compliance: SFB runs wildlife projects (Phase 1 on Twy B/B7; Phase II at $2M). AC 150/5200-33C covers attractants. | partial (the wildlife log and strike reports) | A phone report into the Collector; avian radar only after a business case | `airfield.wildlife.sighting` (reading)<br>`airfield.wildlife.strike` (alarm) | P1 | 0 | FAA-5200-33C, S-LOCK | S |
| af-08 | Weather | wind, visibility, ceiling, precipitation | safety: Operations and ramp safety. SFB: asos row in the asset list. | yes (The ASOS on the field (public observations)) | Read the public observation feed | `weather.observation` (reading) | P1 | 0 | FAA-5220-16E, S-LIST | I |
| af-09 | Lightning near the ramp | strikes within a radius | safety: Ramp crews stop work when lightning is close. Florida has frequent storms. SFB: Ask who calls ramp closures today. | no (nothing named) | A commercial lightning data feed, no hardware | `weather.lightning.within_radius` (alarm)<br>`weather.lightning.all_clear` (state) | P1 | 1 | none | I |
| af-10 | Vehicle position on the movement area | position, speed, identity | safety: Runway incursions. VMAT funded (FAA grant Aug 2026). | no (the VMAT transponders, once fitted) | An ADS-B receiver the Authority owns | `airfield.vehicle.position` (reading)<br>`airfield.vehicle.out_of_bounds` (alarm) | P1 | 3 | S-CAT, FAA-5220-26 | V |
| af-11 | PAPI, beacon and wind cones | lit and aligned | safety, compliance: Visual aids on the self-inspection list. SFB: 28 PAPI and 5 wind cone rows. | partial (ALCMS for some; inspection for others) | Self-inspection record; drone night pass | `airfield.visual_aid.fault` (fault) | P1 | 1 | FAA-5340-26C, S-LIST | I |

### Fuel farm

| ID | What | Measures | Why it matters | Reports today? (via) | Cheapest way otherwise | Event types | P | Phase | Source | Basis |
|---|---|---|---|---|---|---|---|---|---|---|
| fuel-01 | Tank level and high-level alarm | level, volume, high and high-high alarms | safety, compliance: Overfill is a fire and spill risk; EPA's 2024 alert targets failed overfill prevention. SFB: Fuel farm is security-sensitive in the GIS; operator not confirmed. | likely (The tank gauge at the farm, run by the fuel operator) | Read the operator's tank gauge; no new device | `fuel.tank.level` (reading)<br>`fuel.tank.high_level` (alarm) | P1 | 1 | EPA-OVERFILL, S-GIS | S |
| fuel-02 | Leak and release detection | interstitial or sump sensors; monthly release detection | compliance, safety: USTs need release detection under 40 CFR 280; ASTs fall under SPCC. | likely (The tank gauge or leak panel) | Same as fuel-01 | `fuel.tank.leak_detected` (alarm)<br>`fuel.release_check.recorded` (document) | P1 | 1 | CFR-280, EPA-OVERFILL | S |
| fuel-03 | Fuel quality and fire safety checks | daily quality checks, fire safety training, inspections | compliance: 14 CFR 139.321 and AC 150/5230-4C. A record, not a sensor. | no (the operator's logs) | Document events through the Collector | `fuel.quality_check.recorded` (document)<br>`fuel.inspection.recorded` (document) | P1 | 0 | FAA-5230-4C | S |

### Drones

| ID | What | Measures | Why it matters | Reports today? (via) | Cheapest way otherwise | Event types | P | Phase | Source | Basis |
|---|---|---|---|---|---|---|---|---|---|---|
| drn-01 | Our drone fleet and stations | sortie landed, segments stored, station state | uptime: Drones are sensors; their own health is the first thing to watch. | yes (MissionSight events and the Tender) | Already in MissionSight's contracts | `sortie.landed` (state)<br>`segment.stored` (state) | P2 | 2 | MS-EVENTS | V |
| drn-02 | Findings from drone passes | a lens finding on an enrolled subject | safety, uptime: One pass checks many assets: edge lights, claim devices, floors. | yes (MissionSight finding.raised) | Already in MissionSight's contracts | `finding.raised` (alarm)<br>`coverage.indexed` (document) | P1 | 3 | MS-EVENTS | V |
| drn-03 | Unauthorised drones near the airport | UAS detected | safety: The FAA cannot confirm the legality of any UAS detection system and asks for coordination first. | no (nothing) | Only after FAA coordination; a detection vendor's feed | `airspace.uas.detected` (alarm) | P4 | 5 | FAA-UAS | S |
| drn-04 | Drones for wildlife dispersal | dispersal flights | safety: FAA CertAlert 23-08 sets considerations. | no (nothing) | Later, under the wildlife plan | `airfield.wildlife.dispersal_flown` (document) | P4 | 5 | FAA-CA-23-08, S-OPEN | V |

### Environmental

| ID | What | Measures | Why it matters | Reports today? (via) | Cheapest way otherwise | Event types | P | Phase | Source | Basis |
|---|---|---|---|---|---|---|---|---|---|---|
| env-01 | Stormwater ponds and flooding | pond level; ponding on landside roads | safety, compliance, cost: Stormwater Pond Improvements are bidding; the Board asked for better stormwater data. | no (nothing) | Ultrasonic level sensors on LoRaWAN at outfalls and ponds | `env.pond.level_high` (alarm)<br>`env.flood.ponding` (alarm) | P2 | 3 | S-LOCK | I |
| env-02 | Stormwater sampling | benchmark samples where the permit asks | compliance: MSGP Sector S; sampling thresholds are tied to deicing chemical use, likely not met in Florida. | no (the permit's records) | Document events | `env.stormwater.sample_recorded` (document) | P2 | 0 | EPA-MSGP-S | S |
| env-03 | Aircraft noise | noise events by place and time | compliance, experience: SFB has a noise abatement committee (SANAC). Part 150 sets the measures. | no (nothing found) | Noise monitors only if a Part 150 study or the committee asks | `env.noise.event` (reading) | P4 | 5 | S-LOCK | S |
| env-04 | Outdoor air quality | PM2.5, NOx at the ramp and curb | experience: Community and staff exposure; no rule found that requires it at SFB. | no (nothing) | Low-cost air quality sensors | `env.air.reading` (reading) | P4 | 5 | none | I |

### Terminal (other)

| ID | What | Measures | Why it matters | Reports today? (via) | Cheapest way otherwise | Event types | P | Phase | Source | Basis |
|---|---|---|---|---|---|---|---|---|---|---|
| ter-01 | Automatic doors | door faults, stuck open | uptime, safety: A stuck door at the curb is an accessibility and climate problem. Access control is out of scope. SFB: 12 doors in the asset list. | partial (Door operators' fault outputs) | Fault contact to the BMS | `facility.door.fault` (fault) | P3 | 4 | S-LIST | I |
| ter-02 | Terminal lighting zones | on, off, dim, energy | cost: Energy; Acuity SensorSwitch is 'Not Connected'. | partial (nLight ECLYPSE with optional BACnet) | Read the nECY if networked | `facility.lighting.zone_state` (state) | P4 | 5 | S-CAT | S |
| ter-03 | Digital signs and FIDS screens | screen up or down | experience: A blank sign misleads passengers. SFB: 4 digital sign rows. | likely (the signage player's manager) | Read the content manager | `facility.sign.down` (alarm) | P3 | 4 | S-LIST | I |

## The first fifteen, in order

Ordered by priority, then by how little it costs to get. A P1 item that already reports comes before a P1 item that needs hardware.

| Order | ID | What | Why this place |
|---|---|---|---|
| 1 | fire-01, fire-02 | Fire alarm panel: alarm, trouble, supervisory, sprinkler flow and tamper | Life safety. The panel already monitors every device; a listed gateway reads it. No new device. |
| 2 | vt-01 | Elevator faults and entrapments | A trapped passenger is the most urgent VT event. Usually in the OEM cloud; Elevator 5's funded modernisation is the moment to buy the data option. |
| 3 | vt-04 | Escalator stops and safety trips | Safety, and the checkpoint queue. The Escalator 3 story in the Exploder already shows it. |
| 4 | pwr-01, pwr-02, pwr-03 | Generators, transfer switches and the monthly test record | Emergency power. The new controllers speak Modbus. The NFPA 110 record falls out of the run state. |
| 5 | af-01 | Airfield lighting circuit faults | Part 139 lighting. The ALCMS measures it; only a one-way export is needed. |
| 6 | af-03, af-04, af-07 | Self-inspection, FOD and wildlife records | Compliance records that already exist in i3 or in logs. Phase 0, no hardware. |
| 7 | af-08, af-09 | Weather and lightning | The ASOS is public; lightning is a data feed. Ramp safety. |
| 8 | fuel-01, fuel-02 | Fuel farm tank level, overfill and leak detection | Fire and spill. A tank gauge usually exists; it belongs to the fuel operator. |
| 9 | hvac-04 | Refrigerant leak in the chiller plant | Life safety for the person entering the plant room. |
| 11 | pbb-02, pbb-01 | Bridge auto-level faults, then bridge faults | Aircraft and bridge damage; the cost that put R&M 27% over budget. PLC tags. |
| 12 | af-02 | Lamp outages from the nightly drone pass | The regulator cannot see single lamps. The MissionSight mission is drafted. |
| 13 | hvac-05 | Cooling tower water treatment | Legionella risk under ASHRAE 188. Read the treatment controller. |
| 14 | wtr-02, vt-03 | Water on the floor in plant and IT rooms, and in elevator pits | Cheap sensors. Elevator 5 had water in its pit. |
| 15 | it-01, it-02 | IDF temperature and UPS state | Every other feed runs through these rooms. |

Next after these: the BMS feed (hvac-01, hvac-03), PCA and GPU (pbb-03), bag throughput (bhs-05) and occupancy from Wi-Fi (pax-02).

## The rollout, in phases

| Phase | Name | What | Gate before the next |
|---|---|---|---|
| 0 | Records first, no hardware | Register every source. Read Simplify i3 and file the records that prove compliance: self-inspection, FOD, wildlife, backflow, fire inspections, fuel checks, stormwater. Read the public weather feed. Load the owner's asset list. (8 items) | Each source has an owner, an interface and a freshness. Every record type classifies in the catalogue. |
| 1 | Life safety and compliance feeds, read only | Fire panel through its listed gateway, generators and transfer switches, the ALCMS export, the fuel farm tank gauge, elevator entrapment and escalator trips from the OEM, refrigerant detection, lightning feed. (13 items) | Each feed is read only, tested end to end, and its alarm reaches a person. |
| 2 | Uptime and cost from systems already there | EcoStruxure (AHUs, chillers, cooling tower treatment), the bridge and BHS PLCs through one read-only gateway, full VT OEM data, PCA and GPU, UPS, Wi-Fi controller, metering, flight status. In the class order the Authority sets (REQ-SFB-005). (18 items) | The five RFP classes show availability, alarms and open work in one view (REQ-SFB-024). |
| 3 | Cheap gap sensors and drone passes | Leak sensors, IT and mechanical room temperature, elevator pit water, filter pressure, gearbox vibration, water service flow, pond level; the nightly edge-light drone pass, ponding and pavement surveys; VMAT receiver once transponders arrive. (15 items) | Each new point has an asset ID in i3, a supplier who proved conformance, and a battery or calibration duty. |
| 4 | Passenger experience | Occupancy from Wi-Fi counts, restroom usage and cleaning taps, queue time measured outside the checkpoint with TSA's agreement, parking by zone, curb dwell, doors and signs, bag delivery times. (12 items) | Each measure has a definition and a before value (REQ-SFB-058). |
| 5 | Nice to have, after a business case | Noise monitors, outdoor air quality, fixed FOD radar, UAS detection after FAA coordination, drone wildlife dispersal, consumables and odour, terminal lighting zones. (8 items) | A business case the Authority accepts. |

Two exceptions:

- **Time-boxed.** The remote parking lot (park-02) is P3, but sensors or conduit must be specified before it is paved (due November or December 2026). It is raised in phase 0 as a decision.
- **Out of scope.** Cameras and their positions, gunshot detection, access control, checkpoint internals and inline baggage screening stay with their owners. We read their panels through the owner and model no device position.

Phase 2 follows the class order the Authority sets at initiation (REQ-SFB-005). Until then, our proposal is VT, then BHS, then bridges, then HVAC, because that is the order of the P1 items inside each.

## What the counts say

- 74 items. 27 are P1, 26 are P2, 13 are P3 and 8 are P4.
- 34 items report today or are likely to (yes or likely). For those, REQ-SFB-040 says read, and build nothing.
- 5 items are records only, with no sensor at all (wtr-03, fire-03, af-03, fuel-03, env-02). 11 items raise document events. All of them need the Collector's document path and no hardware.
- The pass 3 plan's 58 "needs sensor" points sit almost entirely in phase 3.

## Open questions for a site tour

Additions to the seventeen questions in `sensor-catalogue-2026-10-30.md`. Ask only when the solicitation rules allow contact.

**Life safety and compliance**
1. Is there a refrigerant detector in the chiller plant room, and what does it report to?
2. Who runs the fuel farm, and does its tank gauge have a network or serial output the operator would share read-only?
3. Who calls a ramp closure for lightning today, and from what data?
4. Where do the self-inspection, FOD and wildlife records live: i3, paper or another system?
5. Is the cooling tower under a water management program, and who holds its treatment controller?
6. Where are backflow test reports filed?

**Feeds that may already exist**
7. Do the UPS units in the IDFs and MDF have network cards, and who watches them?
8. Can the wireless controller export client counts per access point for occupancy?
9. Does the pump or lift station panel report anywhere, or only dial out?
10. Is there a FIDS feed the Authority controls?

**Places to look at**
11. Which rooms have had water on the floor: plant rooms, IDFs, under restrooms, over the BHS?
12. Where does water pond on the landside roads and the apron after heavy rain?
13. Which restrooms draw the most complaints, and how are cleaning rounds recorded today?
14. Where does the checkpoint queue start, and would TSA accept a wait-time measure taken outside the checkpoint?

## Sources

Local files are in the sanford-twin repository. External sources were looked up on 2026-11-06; those tagged S on an item were read as search extracts and need the primary read before they are quoted.

- **S-CAT**: sanford-twin docs/research/sensor-catalogue-2026-10-30.md
- **S-VT**: sanford-twin docs/research/terminal-assets-vt-bhs-2026-11-06.md
- **S-PLAN**: sanford-twin projects/sfb-terminal/04-plan/sensor-plan.json (pass 3, 195 points)
- **S-LIST**: sanford-twin projects/sfb-terminal/build/latest asset list (3,943 rows, first cut)
- **S-LOCK**: sanford-twin docs/research/flysfb-lockstep-2026-10-30.md
- **S-OPEN**: sanford-twin docs/research/open-checks-2026-10-30.md
- **S-GIS**: sanford-twin docs/research/saa-gis-2026-10-30.md
- **RFP**: sanford-twin staging/e2-sanford/requirements.md (REQ-SFB-001 to 070)
- **FAA-5340-26C**: FAA AC 150/5340-26C, Maintenance of Airport Visual Aid Facilities (2014-06-20, active) <https://www.faa.gov/airports/resources/advisory_circulars/index.cfm/go/document.current/documentNumber/150_5340-26>
- **FAA-5345-56B**: FAA AC 150/5345-56B, ALCMS (cited in S-CAT: the ALCMS network is for the ALCMS only)
- **FAA-5380-6C**: FAA AC 150/5380-6C, Guidelines and Procedures for Maintenance of Airport Pavements (2014-10-10) <https://www.faa.gov/documentLibrary/media/Advisory_Circular/150-5380-6C.pdf>
- **FAA-5210-24A**: FAA AC 150/5210-24A, Airport Foreign Object Debris (FOD) Management (2024-02-08, active) <https://www.faa.gov/airports/resources/advisory_circulars/index.cfm/go/document.current/documentNumber/150_5210-24>
- **FAA-CA-24-03**: FAA Part 139 CertAlert 24-03, FOD management (2024-02-29) <https://www.faa.gov/sites/faa.gov/files/arp-part-139-cert-alert-24-03-FOD-Mgmt.pdf>
- **FAA-5220-24**: FAA AC 150/5220-24, Airport Foreign Object Debris Detection Equipment <https://www.faa.gov/documentLibrary/media/Advisory_Circular/150_5220_24.pdf>
- **FAA-5200-33C**: FAA AC 150/5200-33C, Hazardous Wildlife Attractants on or near Airports (2020-02-21, active) <https://www.faa.gov/documentLibrary/media/Advisory_Circular/150-5200-33C.pdf>
- **FAA-5230-4C**: FAA AC 150/5230-4C, Aircraft Fuel Storage, Handling, Training, and Dispensing on Airports; the accepted means for 14 CFR 139.321 <https://www.faa.gov/airports/resources/advisory_circulars/index.cfm/go/document.current/documentNumber/150_5230-4>
- **FAA-5220-16E**: FAA AC 150/5220-16E Change 1, AWOS for Non-Federal Applications (2019-01-31) <https://www.faa.gov/airports/resources/advisory_circulars/index.cfm/go/document.current/documentNumber/150_5220-16>
- **FAA-5220-26**: FAA AC 150/5220-26 Change 3, vehicle ADS-B (VMAT) (cited in S-CAT) <https://www.faa.gov/documentLibrary/media/Advisory_Circular/150_5220_26_change_3_consolidated.pdf>
- **CFR-139.327**: 14 CFR 139.327 Self-inspection program (daily, and during construction); records kept 12 months <https://www.ecfr.gov/current/title-14/chapter-I/subchapter-G/part-139/subpart-D/section-139.327>
- **FAA-UAS**: FAA, UAS Detection, Mitigation, and Response on Airports; 2019 sponsor letter: the FAA cannot confirm the legality of any UAS detection system <https://www.faa.gov/airports/new_entrants/uas_detection_mitigation_response>
- **FAA-CA-23-08**: FAA CertAlert 23-08, unmanned aircraft in support of wildlife dispersal (cited in S-OPEN)
- **EPA-MSGP-S**: EPA Multi-Sector General Permit, Sector S (air transportation), Florida DEP summary <https://floridadep.gov/sites/default/files/SectorS.pdf>
- **CFR-280**: 40 CFR 280 Subpart D, release detection for underground storage tanks <https://www.ecfr.gov/current/title-40/chapter-I/subchapter-I/part-280/subpart-D>
- **EPA-OVERFILL**: EPA technical alert EPA 540-S-24-001, failure of overfill prevention (SPCC, 40 CFR 112) <https://epa.gov/system/files/documents/2024-08/failure-of-overfill-prevention-at-substantial-harm-oil-facilities-tech-alert_508-compliant_07_23_2024_draft-final.pdf>
- **NFPA-110**: NFPA 110 monthly generator exercise, at least 30 minutes under load (as summarised by the Minnesota Department of Health) <https://www.health.state.mn.us/facilities/regulation/engineering/lscgensets24.pdf>
- **FAC-62-555.360**: Fla. Admin. Code 62-555.360, cross-connection control; annual backflow testing as applied by Florida utilities <https://www.law.cornell.edu/regulations/florida/Fla-Admin-Code-Ann-R-62-555-360>
- **ASHRAE-188**: ANSI/ASHRAE Standard 188, Legionellosis risk management; a cooling tower calls for a water management program (ASHRAE fact sheet) <https://www.ashrae.org/File%20Library/About/Government%20Affairs/Advocacy%20Toolkit/Virtual%20Packet/188-Fact-Sheet-Revisd-09.20.18docx.pdf>
- **ASHRAE-TC99**: ASHRAE TC 9.9 thermal guidelines, recommended inlet 18 to 27 C (trade summary) <https://datacenterfrontier.com/evolving-data-center-cooling-ranges-standards/>
- **IATA-LOS**: IATA Level of Service best practice paper (ADRM): space and maximum waiting time per subsystem <https://www.iata.org/contentassets/d1d4d535bf1c4ba695f43e9beff8294f/iata-level-of-service-paper-best-practice.pdf>
- **ACI-ASQ**: ACI Airport Service Quality KPIs, incl. washroom cleanliness and availability (ACI slides at ICAO, 2018) <https://www2023.icao.int/MID/Documents/2018/Airports%20and%20AN%20Charges%20WS/4.3%20Centric%20Approach%20ACI.pdf>
- **TSA-VOL**: TSA checkpoint travel numbers: daily, national totals only, not per airport <https://www.tsa.gov/travel/passenger-volumes>
- **VDL-LHR**: Vanderlande, predictive maintenance at Heathrow (sensors on critical BHS equipment) <https://www.vanderlande.com/news/introducing-predictive-maintenance-at-heathrow-airport/>
- **JBT-IOPS**: Oshkosh AeroTech (JBT) iOPS: bridges, and the GPU and PCA units on them <https://oshkoshaerotech.com/news-and-events/press-releases/monitoring-gate-and-mobile-aviation-equipment/>
- **TRAX-SYR**: TRAX Analytics at Syracuse Hancock International: restroom usage and cleaning data (vendor case study) <https://www.casestudies.com/company/trax-analytics/case-study/syracuse-hancock-international-airport-customer-case-study>
- **CVG-WC**: CVG pilot: restroom usage thresholds alert housekeeping (vendor case study) <https://www.casestudies.com/company/samsung/case-study/cincinnati-airport-enhances-the-customer-experience-with-wearable-alerts-solution>
- **SCHIPHOL**: Esri ArcUser on Schiphol's digital twin: PLC faults raise work orders; queue times, occupancy and flow <https://www.esri.com/about/newsroom/arcuser/digital-twin-helps-airport-optimize-operations>
- **YVR**: AviationPros on YVR's digital twin (from November 2020, with Vanderlande and BCIT IoT trials) <https://www.aviationpros.com/airport-business/airport-infrastructure-operations/article/21232260/innovating-airport-operations>
- **MS-EVENTS**: missionsight contracts/events (sortie.landed, segment.stored, finding.raised and six more)
