CompanyGraph
A fighter, missile, satellite, or sensor becomes military capability only when its configuration, people, software, parts, authorization, and mission readiness remain connected.
The customer needs a mission result
A government does not ultimately need an aircraft sitting in a hangar. It needs an aircraft that can perform a defined mission with trained crews, usable software, weapons, fuel, maintenance, secure communications, and an authorized operating plan. The same distinction applies to a missile-defense system, satellite, command network, or sensor: hardware is one condition of capability, not the complete result.
Lockheed Martin’s 2025 annual report describes four business areas serving government and allied customers. Their products and contracts differ, but every program must turn a requirement into a configuration that can be produced, tested, operated, maintained, and eventually replaced.
Requirements become a configuration
A military requirement becomes system architecture, software, interfaces, test plans, security controls, manufacturing processes, and training. Classification can protect information and limit access, but it also narrows who can inspect, reproduce, repair, or challenge a design. A cleared workforce and a qualified supplier are not interchangeable with a generic engineering team.
Qualification attaches evidence to a defined design and process. It does not make every later part, update, or field condition identical to the tested case. A production record can establish that a unit was built under approved instructions. It cannot alone show that the unit’s current software, corrosion state, maintenance history, or mission equipment remains suitable.
Long programs share costs and share constraints
Large programs distribute development and production across services, allies, suppliers, bases, and congressional districts. That distribution can lower unit cost and create a durable industrial route. It also means that a design choice, software baseline, or delayed part can affect many users at once. Replacing the program would require a new requirement, procurement, training, infrastructure, suppliers, and years of testing.
The public budget funds more than the factory. It funds engineering, test ranges, secure facilities, depot capacity, spares, software updates, and people who know how to operate and repair the system. Those obligations continue after a production milestone. A program can therefore remain politically and industrially important while the fielded system still has a readiness problem.
The F-35 shows why inventory is not readiness
The F-35 is a useful documented case, not a model for every defense program. The Joint Strike Fighter joins variants for several U.S. services and allied customers, with a long production and sustainment horizon. GAO’s recent review says the program continues to face readiness challenges and that the Department of Defense launched a $13.7 billion strategy in 2025 to improve sustainment by 2030. The report also describes parts, software, management, and incentive problems.
That evidence changes what “success” means. More aircraft, more spare-parts spending, or a larger backlog of work does not automatically produce more aircraft ready for every assigned mission. A part can be in inventory but incompatible, awaiting installation, or unavailable at the location where it is needed. Software can be delivered but not usable in the intended configuration. A contractor can be paid while the operational result remains below the required level.
Maintenance is another production system
Maintenance turns a fielded platform back into a usable configuration. It requires inspections, repair instructions, tools, trained technicians, parts, software, test equipment, facilities, and data rights. GAO has described the difficulty of moving F-35 sustainment responsibilities between contractor and government and the continuing importance of technical data and supply support. The organization that owns the aircraft is not automatically the organization able to repair it.
A maintenance action can correct one aircraft while revealing a fleet-wide design or supplier problem. A readiness metric can show that an aircraft was available for one mission or all assigned missions, but it does not identify every cause of delay. Correction requires a path from the maintainer’s observation to the program office, supplier, designer, contract manager, and budget holder who can change the next configuration.
Money arrives before the prevented failure
Defense capability requires money before its benefit is visible. Secure facilities, cleared workers, test articles, redundancy, spare parts, cybersecurity, and long-lead components must be funded before they prevent a failed sortie or unavailable system. A contract can allocate cost and performance obligations, but a payment record does not prove that the mission result exists.
This creates pressure across the route. A customer may defer a spare or test capability to protect a current budget, while the supplier may preserve cash through a narrower workforce or inventory plan. Those choices can look efficient in an accounting period and still reduce future readiness. Regulation, audit, and contract incentives exist partly because cost and schedule are visible now while the avoided failure is not.
Alternatives are real but slow
A government can modify a platform, buy a different system, use a legacy aircraft, change the mission, or develop a new supplier. None is a frictionless substitute. Clearances, export controls, interfaces, training, facilities, data rights, certification, and appropriations constrain the timing. A second source may be technically possible and still unavailable before the current system must operate.
That is why program lock-in should not be confused with technical superiority. The existing route may be the only one that can deliver a required capability at the required time, even while its cost or readiness is disputed. The alternative becomes real only when the government has the authority, information, people, and money to qualify it.
What Lockheed Martin’s position actually shows
Lockheed Martin operates inside a public defense system that funds specialized capability over decades. Its scale, classified experience, supplier relationships, and program histories can make it difficult to replace quickly. The same structure can leave the government dependent on a small number of primes and make problems hard to observe from outside the secure boundary.
The complete result is neither a contract nor a platform count. It is a mission-capable configuration whose software, parts, people, data, funding, and authority remain connected. When a readiness signal appears, responsibility means reaching the person who can still change the design, supplier, maintenance plan, contract, budget, or mission.