ISR as a Service.

What it is

The government defines the intelligence requirement. The contractor supplies everything needed to meet it — aircraft, sensors, crews, maintenance, ground station, communications, analysts — and is paid against coverage delivered rather than equipment supplied.

Why governments choose it

Speed, mostly. A service contract can put an aircraft over a corridor in a fraction of the time an acquisition takes, without requiring the government to first build an aviation organization it does not have. It also converts a large capital requirement into an operating expense, which some ministries can approve far more easily than a capital program — and which ministry can approve which is frequently the real reason a model is chosen.

What it actually costs

Pricing is normally per flight hour or per month of guaranteed coverage, all-inclusive. The number is higher than the marginal cost of flying an aircraft you already own, because it includes the contractor’s capital, risk, sustainment and margin.

The comparison that matters is not service cost against fuel cost. It is service cost against the fully-loaded cost of acquiring the aircraft, building the maintenance organization, training the crews and carrying the airworthiness burden yourself, amortized across the years you will actually operate it. Run honestly over a three-year horizon, service usually wins. Run over twelve, it usually does not. Which horizon applies is a question about the threat, not about the aircraft.

What “guaranteed coverage” means in a contract

This is the clause that decides whether the arrangement is a good one, and it is the clause most often skimmed.

Coverage hours promised are not coverage hours flown. Weather closes airfields. Aircraft go unserviceable. Airspace gets restricted at short notice, sometimes by the customer’s own government. A contract has to say what happens in each case, and the honest ones distinguish between causes:

• Contractor-caused shortfall — unserviceability, crew availability — should carry a credit or a make-good obligation.
• Customer-caused shortfall — airspace denied, basing withdrawn, tasking not issued — normally does not, because the contractor stood the capability up regardless.
• Neither party — weather, a volcanic ash advisory, a regional closure — is negotiated, and the fair answer is usually shared.

A contract that promises a flat number of hours with no such breakdown is either priced with a large risk margin you are paying for, or is going to produce a dispute in month four.

What the government still has to supply

A service contract does not outsource the whole problem, and the parts that stay with the customer are the ones that make it work:

Tasking. Somebody has to decide what the aircraft looks at, daily, with authority. Programs where tasking is unclear produce sorties flown against yesterday’s priority.

Somebody to receive the product. If nothing downstream can act on the intelligence, the coverage is an expense with no output. This is where processing, exploitation and dissemination belongs in the conversation — whether the contractor supplies the analysts or the ministry does, they have to exist.

Basing and airspace. A ramp, fuel, security, and the authority to fly where the mission requires. Foreign-registered aircraft operating in national airspace is a diplomatic question before it is an aviation one.

Legal authority. Persistent aerial surveillance touches domestic law in most countries. Settling what may be collected, retained and shared is the customer’s to do, and doing it after the aircraft arrives is doing it late.

The risks worth naming

• Dependency. A service contract that runs for years without a transfer plan leaves the government no more capable than at the start.
• Data ownership. Who holds the collected imagery, who may access it, and what happens to the archive at contract end should be settled in the contract, not assumed.
• Exit. If the relationship ends badly, what continues to work? For most service arrangements the honest answer is nothing, which is why the transfer question belongs in the first conversation rather than the last.

How to structure one so it ends well

Decide at the outset which column you are buying. ISR as a service is COCO — the fastest model, the lowest capital, and the one that leaves nothing behind unless you deliberately build transfer into it.

If the intent is eventually to own the capability, three things belong in the original agreement rather than a later amendment: partner-nation personnel embedded alongside the contractor crews from the start, a defined transfer milestone with competency criteria attached, and customer ownership of the data and the archive throughout. Bolted on in year three, each of these is a renegotiation. Written in at award, they cost very little.

If the intent is genuinely to rent a capability for a defined period and then stop — which is a legitimate answer — say so, and price the exit rather than discovering it.