FLynx
I've been involved with a couple of support contracts in the past based on "hole in the wall" and "avaliability" requirements. In theory it is beautiful, with a single availability requirement you throw the entire risk over the fence to industry and have a fixed price for support as far as the eye can see.
What happens in practice is the contract is is signed before the aircraft is fielded. Meanwhile a new defence initiative is announced, oh the number of operating bases has changed, kerrching - contract amendment. Oh you want to fight a war, that was not in your SOIU, you are supposed to be doing 25% training flights in nice flat level circuits only operating some of the kit. You want to operate all the fleet in baking hot temperatures, fly them 15 hours a day with max loads, fitted with a stack of UORs that industry does not recognise; kerching - contract amendment. What do you mean you want to sustain the surge requirement for 5 years, kerching - contract amendment. Now the support budget is not big enough because it has been trimmed to fit the availability requirement.
The beautiful theory is beloved by accountants and only works in theory because no-one has a crystal ball good enough to cover a 10 year contract.
regards
retard