“If NYC shuts down power how long can we run on diesel at the datacenter?”
That was the whole email.
Hurricane Irene was moving toward New York. Transit was stopping, low-lying areas were evacuating, and the city was preparing for conditions most of our normal plans did not cover.
The subway shutdown and evacuation orders made the timeline real. If utility power disappeared, the generator clock would start while the rest of the city was dealing with the same storm.
For the website, the question was fuel.
A generator is reassuring, but it is not an answer measured in time. The useful answer is how long it can carry the actual load with the fuel already available.
That was the distinction behind my one-line message. I was not asking whether the data center had generators. I was asking for the number of hours between a city power shutdown and the next decision.
I left the facility name, fuel level, generator capacity, and contingency sequence out of the note. I wanted the answer, not a long email built on assumptions about backup power.
Outside the data center, Irene was forcing the city to make unusual preparations. Inside the infrastructure plan, I needed one plain constraint.
How long?
The email went out from my iPhone on Saturday morning. It carried no recommendation. It was a request for the fact we needed before anyone could decide what came next.
New York was preparing for the storm. I was asking how much time the backup power could buy.
Until somebody replied with the actual runtime, all I had was the question.