Ten Minutes With the Traffic Engineer
He thinks in corridors, travel times and how fast the fire truck gets through.
The traffic engineer's questions are simple. Will the corridor run on plan at rush hour? Will emergency vehicles get their green? Will the traffic center see every intersection it's supposed to see? Will we be fixing a problem at two in the morning, or answering complaints at nine?
If you have ten minutes with him, talk in those terms. Then show results he can check, in three levels.
| Level | What it shows |
|---|---|
| Found | Devices missing from the inventory. Default and shared logins. Controllers reachable from places they shouldn't be. Contractor and vendor logins nobody owns. Devices talking somewhere new. |
| Saved | Hours your team no longer spends hunting for devices, chasing vendors, driving to cabinets and checking fixes by hand, priced at your own labor rates. |
| Estimated | The disruption you likely avoided, with every assumption shown so your team can change it. |
Keep those three apart. Found is measured. Saved is measured against your own numbers. Estimated is a judgment, and it should look like one.
Then make one small ask. Start with one corridor.
Pick the place where trouble would hurt most. The corridor outside the hospital. The route to the airport. The school zone. One radio network. One contractor's remote login.
The Blind Spot Assessment puts a Findavi appliance on that one part of your signal network and listens. At the end, your team gets five things.
1. A map of the devices in scope and who they talk to.
2. Evidence of each exposure, with an owner named for it.
3. A plan ranked by what breaks if each device fails.
4. The fixes Findavi can make under your approval rules.
5. The security check and service check for every proposed change.
Ask your team: Which single corridor would cause the biggest problem for the public if its signals failed for a day? Start there.