By Eugene le Roux, FSAIRAC, and Eamonn Ryan
Navigating ambiguity in acquisition. This is Part 1 of a two-part series.
In the complex world of large-scale acquisitions, particularly for sophisticated equipment like vehicles, a seemingly innocuous phrase often appears in requirements: ‘fitted for, but not with’.
This seemingly straightforward directive, whether referring to an air conditioning system, chemical warfare protection or specialised communication gear, implies a future capability without immediate integration. However, beneath its surface lies a labyrinth of engineering, logistical and financial complexities that, if not meticulously managed, can lead to significant cost overruns, delays, and even project failure.
At its core ‘fitted for, but not with’ means that while the primary artifact (such as a vehicle) should be designed to accommodate a specific subsystem, that subsystem will not be included at the time of initial delivery. This approach is often driven by budget constraints, a desire for future flexibility, or uncertainty regarding the ultimate need for a particular capability.
Decoding the options: a spectrum of readiness
When faced with such a requirement, various interpretations can emerge, each carrying distinct implications for readiness and cost:
- Option A: Complete vehicle development, estimate space for undeveloped aircon. This is the riskiest and most shortsighted approach. It defers all the complex integration work, leaving a mere placeholder. The “estimated space” often proves insufficient, leading to costly redesigns and compromises later.
- Option B: Complete aircon development and qualify it in the vehicle, but not for reliability and producibility. This is a step forward, ensuring technical compatibility and functional performance within the vehicle’s environment. However, by omitting reliability and mass producibility qualification, it still leaves significant hurdles for future large-scale deployment.
- Option C: As in B but also qualify for reliability and mass producibility. Develop logistic support and personnel requirements, but don’t produce log items. This is a robust approach. It ensures the subsystem is fully engineered, tested, and ready for efficient mass production. Crucially, it anticipates the entire support ecosystem, from maintenance procedures to training needs. While physical spare parts and documents aren’t produced, their specifications and requirements are defined, significantly de-risking future integration.
- Option D: Like C and produce a certain number of aircons with logistic support, ready when requested. This is the highest level of readiness, providing immediate availability of the subsystem and its support. While incurring upfront costs for production and inventory, it eliminates lead times and ensures immediate operational capability upon demand.