SeaQueen
Posts: 1451
Joined: 4/14/2007 From: Washington D.C. Status: offline
|
quote:
ORIGINAL: p1t1o How long does a scenario have to be before "Surge" Air Ops starts to become unrealistic? It depends? What is the context of the scenario? People ask these questions like there's a single obvious answer and there isn't one. When you're talking about "surge" ops you're really talking about maintenance and turn around times. Those can be constrained by everything from the availability of parts, to the maintainers being fatigued. The "sweet spot" for CMO is the 12-24 hour time frame, so in a 12-24 hour snap shot of an ongoing conflict, a lot of stuff is beyond the scope of the scenario. Things like a given tail being flown so much that its engines are in need of an overhaul, but the engine that was supposed to arrive in a C-130 flight didn't get there because it had to turn around thanks to a bunch of J-20s flying through its route, aren't handled easily by CMO. What I do, given the 12-24 hour snapshot, is just randomize which aircraft are in maintenance and which aren't, based on a reasonable probability of being mission capable (I use data publicly available in Air Force magazine, typically, and if I don't have data, I use an average of the type (e.g. fighters) ). So... given that, when to use "surge" versus "sustained" ops? It depends on what you're trying to capture in the scenario. Sustained ops will radically cut your sortie rate, and in my mind reflects almost a peacetime or maybe a very protracted conflict, where manpower, budgets, parts, fuel and resources are constrained or at least tightly controlled and conserved. It's less a difference in any physical constraint, in some ways, and more a difference in mindset. I would imagine both peace and wartime scenarios using both "surge" and "sustained" settings. Does that help?
|