How does a defense project turn into reality? 17 stages from need to inventory.

The defense project is a multi-year process coordinated by the Defense Industries Authority, starting with the emergence of an operational need and moving through successive stages such as need identification, procurement model selection, contracting, design, modeling, testing, acceptance, mass production, and entry into inventory. This process does not progress in the same order and duration for every project; stages may be shortened, merged, or repeated depending on the procurement model, technology maturity, and project size.
Why 17 Stages?
The following framework consisting of 17 stages summarizes the generally accepted process in defense procurement literature, modified to fit the institutional structure in Turkey (Defense Industries Authority, user authority, contractor company). The aim is to answer the question “how does the product come into existence” with a concrete roadmap extending from need to inventory.
| # | Phase | Summary |
|---|---|---|
| 1 | Emergence of Operational Need | Change in threat, expiration of old system, new mission requirements, technological advancement, or desire to reduce external dependency |
| 2 | Defining the Need | The authority defines the job description, performance expectations, quantity, and delivery needs |
| 3 | Preliminary Assessment and Feasibility | Local capability, off-the-shelf product options, estimated cost and timeline, and technological risks are analyzed |
| 4 | Determining the Procurement Model | One of the models is chosen, such as local development, off-the-shelf purchase, joint production, or licensed production |
| 5 | Decision on the Project | The authorized mechanisms clarify the scope, priorities, funding, and timeline |
| 6 | Proposal and Contractor Selection | Proposals are invited, technical/administrative/financial proposals are evaluated, local analysis and risk analysis are conducted |
| 7 | Contract | Technical specifications, timeline, milestones, payment plan, and testing and acceptance conditions are finalized |
| 8 | Conceptual Design | Mission needs are transformed into engineering requirements, and preliminary engineering is created |
| 9 | Preliminary Design | System engineering, subsystems, weight, power, and size balance are modeled |
| 10 | Critical Design | Design drives production, interfaces are finalized, and technical risks are reduced |
| 11 | Prototype Production | The first prototype is produced, and ground tests and integration are conducted |
| 12 | Testing and Qualification | Unit, system, environmental, durability, flight/shooting/maritime tests and qualification |
| 13 | Acceptance | Factory acceptance, field acceptance, temporary and final acceptance stages |
| 14 | Mass Production | Production line, supply chain, quality assurance, and localization continue |
| 15 | Entry into Inventory | Delivery, training, maintenance structure, distribution to units |
| 16 | Life Cycle Support | Maintenance, repair, updates, software updates, obsolescence management |
| 17 | Export and New Copies | Export permits, country-specific configuration, technology transfer, new users |
How does the need arise?

The initial spark for a project often comes from the field: the changing threat environment expressed by the user authority (military command, police, gendarmerie, coast guard), the end of the life cycle of a system in stock, or the emergence of a new operational concept. At this stage, the Defense Industries Agency (SSB) intervenes: it clarifies the need with the user authority and defines what the expected performance and quantity are. Operational requirements that are not available to the public are not published at this stage; the information reflected to the public generally indicates that the project exists and its general purpose.
Why does the procurement model change from project to project?
Even the same type of need can be met with different procurement models under different circumstances. If there is no capability in this field locally and there is time pressure, ready-made procurement may be preferred; if there is a long-term goal for national capability, local development or joint production may be chosen. While projects like KAAN and ALTAY are implemented with a unique local development model, licensing production or joint development models may be used in some subsystems. Therefore, it is incorrect to generalize that “every project in Turkey is executed in the same way.”
From prototype to mass production: why is there no direct transition?

The prototype is the first tangible form of the design; however, to start mass production, the prototype must undergo unit, system, environmental, and durability tests, address identified defects, and complete the qualification process. If this step is skipped, unexpected failures, security risks, or costly recalls may arise in field conditions. A prototype that fails testing returns to design; this is not a project failure but a natural and necessary part of the process.
Is acceptance and entry into inventory the same thing?

No. The acceptance of the product means that it has been confirmed to meet the contract terms and technical requirements. After that, the product is delivered to the user authority; however, there may be additional steps such as training, logistical support structure, and unit-level acceptance required for its full operational use. Therefore, the news of “delivery” does not always mean the same moment as the news of “operation”.
Common Misconceptions
False: Every defense project goes through the same 17 stages, in the same order and within the same timeframe.
True: Stages can be shortened, combined, or progressed in a different order depending on the project procurement model, its size, and technological maturity.
False: If the prototype is successful, it immediately enters mass production.
True: There are testing, qualification, and acceptance processes between the prototype and mass production; these steps are not skipped.
False: Delivery means that the product is fully operational.
True: After delivery, processes such as training, logistical preparation, and unit acceptance may continue.
Frequently Asked Questions
How many years does a defense project usually take?
This varies depending on the size of the project and the procurement model; domestic development projects generally take longer than off-the-shelf purchases.
Is there a difference between a prototype and a mass production product?
Yes, the prototype is modified based on defects identified during testing; the mass production product includes these modifications.
Who conducts the acceptance testing?
Acceptance processes are carried out in coordination with the SSB, relevant authorities, and the contractor.
Does every project enter mass production?
No; some projects may stop at the testing stage, change their scope, or be canceled.
Does the product that enters inventory never change?
No; it continues to be developed through updates and software upgrades throughout its lifecycle.
Related Content
- What is the Presidency of Defense Industries, and what do they do?
- Why is SSB necessary? What benefits does SSB provide if companies are producing?
References
- The official website of the Presidency of Defense Industries (ssb.gov.tr)
- Law No. 3238 on certain regulations related to the defense industry
- Audit reports of the Presidency of Defense Industries by the Court of Accounts
Last updated: July 25, 2026
