ConEd queue records

A queue field needs an explicit definition before it can inform a site assessment. Establish which projects it counts, whether it reports an amount of power or a project count, and whether it belongs to a feeder, a substation or another area. Repeated fields across records do not prove which upstream equipment they describe.

Generation queues and customer load answer different questions

Con Edison's hosting-capacity materials include distributed-generation information. A generation queue should not be interpreted as pending customer demand without documentation identifying it as such. Storage charging, generation exports and general customer load also require distinct interpretations.

In this site's capacity taxonomy, Con Edison is EV hosting capacity (ev_hosting_capacity), MW; not comparable to load-serving headroom. Con Edison substation records have no utility-reported source date. A queue field is separate from that capacity metric and needs its own documented scope and date. No per-record queue or capacity values are reproduced here.

Check the denominator before making a ratio

A queue-to-capacity ratio requires compatible asset coverage, resource type, period and units on both sides. A shared queue figure cannot be divided among feeders merely because it repeats in their rows. Nor can a sum of feeder estimates establish an upstream capacity limit.

Where the field's scope is undocumented, retain the uncertainty and ask the utility to explain it. The appropriate output is a qualified research question, not a claim about congestion at a named substation.