HC-003: The Ambulances | Hard Calls

1

The Situation

You are a CO at an overseas base, tasked with buying four ambulances: two for off-road recovery, two for patient transport to host nation hospitals on public roads. You have two customers who each own half the requirement. The logistics readiness squadron owns the vehicles themselves, and early on they give you details about the chassis. Medical owns everything that goes inside, and they show up with drawings: air tank holders, specific gurneys, mounting for every piece of equipment they can imagine needing.

Quick vocabulary stop, because this scenario turns on it. The chassis is the truck underneath: frame, engine, drivetrain, axles, suspension. Everything the ambulance is as a vehicle lives there, including the two numbers that decide whether the finished truck actually works: how much weight it can carry, and where that weight sits. The medical box and everything bolted inside it are cargo the chassis has to carry, and every gurney mount and air tank holder moves those numbers.

Medical is engaged, detailed, and loud. They answer emails same day, they iterate the drawings, they know exactly what they want. The logistics squadron gave you their chassis input at the start and went quiet. Your solicitation window is open, the requirement package is nearly complete, and the medical drawings are the most polished requirements document you have ever been handed.

2

The Pressure

Nobody is leaning on you in this one. That is what makes it dangerous. The pressure is quieter: a timeline, a nearly complete package, and one customer who acts like the customer while the other one seems satisfied. Going back to the logistics squadron means reopening a requirement everyone considers settled, admitting the package is not as done as it looks, and slipping the schedule for a question nobody has asked out loud.

And the question itself is easy to miss. The drawings are beautiful. The equipment list is complete. What is not on any page is the integration math: what all of that equipment weighs, where it sits in the box, and what it does to a chassis that someone else specified months ago for a different-looking load. Two halves of the requirement, each individually correct, and no one assigned to the seam where they meet. Except that the seam is exactly where the contracting officer sits.

3

The Authorities

Fewer fiscal law fireworks in this one. The authorities here are about who owns a requirement and what a requirement actually is.

FAR 11.002, describing agency needs. Requirements documents must describe what the government actually needs, stated in terms of functions, performance, and essential physical characteristics. A pile of equipment drawings is not a requirement for a working ambulance. The requirement is a vehicle that carries that equipment and a patient, safely, on the roads and terrain it will actually see. Read it →

FAR Part 10, market research. Research is not only about who can sell you the thing. It is how you learn what the thing has to be, including what a loaded box does to a chassis. The people who knew that math sat in the logistics squadron, one email away. Read it →

FAR 1.102-3 and 1.102-4, the Acquisition Team. The team is everyone with a stake in the outcome, and the customers are part of it. When two customers each hold half of one requirement, somebody has to integrate them. The FAR's team concept assumes it happens. It does not name who does it, which in practice means the CO does, because the CO is the one who signs the package that goes out the door. Read it →

Not a regulation, but load it anyway: the physics. Every vehicle has a maximum loaded weight rating and a center of gravity. Bolt enough equipment high in a tall box and an off-road truck becomes a road hazard. Load a transport past what its suspension was specified for and the shocks stop shocking. No FAR clause protects you from a spec that ignores this. Only the chassis experts do.

4

What's Your Call

One anonymous vote. No login. You see the split after you commit.

Not voting? Skip the vote and show the call. But the vote is the point.

5

The Call

Locked. Make your call above first. This section opens after you vote.

The right answer is B. I picked A. This is the Hard Call where I tell you about the time I got it wrong.

Medical had the louder voice, so I treated them as the customer. They gave me drawings, equipment lists, gurney models, air tank holders, everything laid out clean. I built the package around all of it, on top of the chassis details the logistics squadron had given me at the start, and I never went back to them. I solicited, evaluated, and awarded four ambulances.

Here is what showed up. Two off-road recovery ambulances so top-heavy from equipment mounted high in the box that they could absolutely go off-road, and would tip over on the road. And two patient transport ambulances so overloaded that the shocks did not work. A patient in the back would ping pong around on every host nation pothole between the base and the hospital.

The failure was not the equipment and it was not the chassis. Each half was right on its own. The failure was the seam. All of Medical's equipment added weight the chassis specs had never been asked to carry, and the one organization that could have caught it, the vehicle experts who should have been the main drivers of the requirement, never saw the final load because I never took it back to them. One meeting. That is what B costs. I did not spend it, and the government bought four ambulances that could not do their jobs.

We got lucky on the back end. The vehicles were reconfigured for flightline and base operations, so the money was not a total loss. But do not let the salvage soften the lesson: it was a failure, it was my failure, and it was expensive. The loudest customer is not the requirement owner. Expertise decides who drives, and when two offices each hold half of one requirement, integrating them is not extra credit. It is the job. The CO owns the seam.

And that is the other reason this page exists. You are going to make mistakes with real money on real contracts. Own them by name, salvage what can be salvaged, and turn the rest into a story that keeps the next CO from buying an ambulance that cannot drive to a hospital.

One caveat, and it applies to every Hard Call on this site. In contracting, the target always moves. Option C is a real tool, and on a different requirement a performance spec that pushes integration to industry is exactly right. It depends on the specifics: the market, the expertise on your side of the table, the time you have, and how well you can state the performance envelope. Nothing on this page translates to every requirement, ever. Make the call on the facts in front of you. Some of you will agree with mine and some will not, and that is exactly why this page exists. Take the floor below.

6

The Floor

Disagree with the call? Good. Make your case. Sign in with GitHub to post. Same rule as always: sanitized examples only. No CUI, no PII, no source selection information, no live acquisition details.