I will try and explain this as simple as I can.
First off, these programs are designed to mitigate delays and congestion in the two places that they can happen. Either Enroute or actually at the airports themselves.
The airports themselves will generate whats called ground delay programs or EDCTs. These are those times that usually given to u during your clearance if a program was alreaaalready in effect. These times are funneled through the command center and will either be a +/- 5 program or a time with a call for release 15 min prior to that time.
Then there is the standard Call for Release programs that affect aircraft within a cetain radius of busy airports or airspace. We have several "static " release Airports that never change like ATL IAD ORD etc. Sometimes we'll get releases for airports that due to wx or other reasons require a call for release. To pilots. ...we have to call when u taxi or have a firm idea as to when we can get u airborne. We are hitting an airborne time ie when u tag up on radar, time for the center. We have a window of only a.min or.2 thus the reason for being exact.
One other thing ... in the summer months or during thunderstorm season. The center(s) that are impacted by weather to where certain routes are cuttoff will generate EDCTs that are almost always +/- 5 min. These programs are called AFPs or airspace flow programs. This is why u might sometimes see an EDCT to a small airport like ROA RDU or OMA
Excellent post and thanks for the insight. I hate to keep asking what I think is the same question, but is the time to "call" for the release up to the controllers discretion? You say you can call when you can get a "firm idea" of when we can get airborne. Is that not what you get when a Pilot calls you and gives an estimated wheels up time? In my experience, some controllers will call with the time I give them and others wait until a 5 prior to push call or actually taxiing. All scenarios under the same call for release to ATL.