How Does a Defense Project Come to Life? 17 Stages from Need to Inventory

A defense project is a multi-year process conducted under the coordination of the SSB, which begins with the emergence of an operational need and goes through successive stages such as defining the need, selecting the procurement model, contracting, design, prototyping, testing, acceptance, mass production, and entry into inventory. This process does not progress in the same order and duration for every project; the stages may be shortened, combined, or repeated depending on the procurement model, technological maturity, and scale of the project.
Why 17 Stages?
The following framework of 17 stages summarizes the general process accepted in defense procurement literature, adapted to Turkey’s institutional structure (SSB, user authority, contractor company). The aim is to answer the question “how does a product come into existence” with a concrete roadmap extending from need to inventory.
| # | Stage | Summary |
|---|---|---|
| 1 | Emergence of operational need | Change in threat, expiration of the old system, new mission requirement, technological advancement, or desire to reduce external dependency |
| 2 | Definition of need | The user authority defines the job description, performance expectations, quantity, and delivery needs |
| 3 | Pre-assessment and feasibility | Domestic capability, ready product options, estimated cost and timeline, technological risk are analyzed |
| 4 | Determination of procurement model | One of the models such as domestic development, ready purchase, joint production, or production under license is selected |
| 5 | Decision on the project | Authorized mechanisms clarify scope, priority, financing, and timeline |
| 6 | Proposal and contractor selection | Call for proposals, evaluation of technical/administrative/financial proposals, localization and risk analysis are conducted |
| 7 | Contract | Technical specifications, timeline, milestones, payment plan, test-acceptance conditions are finalized |
| 8 | Conceptual design | Mission needs are transformed into engineering requirements, initial architecture is established |
| 9 | Preliminary design | System architecture, subsystems, weight-power-volume balances are modeled |
| 10 | Critical design | Design approaches production, interfaces are finalized, technical risks are reduced |
| 11 | Prototype production | The first prototype is produced, ground tests and integration are performed |
| 12 | Testing and qualification | Unit, system, environmental, durability, flight/shooting/marine 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 infrastructure, distribution to units |
| 16 | Life cycle support | Maintenance, repair, modernization, software updates, obsolescence management |
| 17 | Export and new variants | Export permits, country-specific configuration, technology transfer, new users |
How Does Need Arise?

The initial spark of a project often comes from the field: the changing threat environment expressed by the user authority (military command, police, gendarmerie, coast guard), the completion of the lifespan of a system in the inventory, or the emergence of a new operational concept. At this point, the SSB (Defense Industry Agency) steps in: it clarifies the need together with the user authority and determines what performance and quantity are expected. Operational requirement details that are not publicly available 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 conditions. If there is no capability in this area domestically and there is time pressure, ready procurement may be preferred; if there is a long-term national capability goal, domestic development or joint production may be chosen. While projects like KAAN and ALTAY are carried out with a unique domestic development model, production under license or joint development models may be used in some subsystems. Therefore, it is incorrect to generalize that “every project in Turkey is carried out in the same way.”
From Prototype to Mass Production: Why Is There No Direct Transition?

A prototype is the first concrete form of the design; however, for mass production to commence, the prototype must pass unit, system, environmental, and durability tests, address identified deficiencies, and complete the qualification process. If this step is skipped, unexpected malfunctions, security risks, or costly recalls may arise in field conditions. A prototype that fails testing returns to design; this is not a failure of the project but a normal and necessary part of the process.
Is Acceptance and Entry into Inventory the Same Thing?

No. The “acceptance” of a product means that it has been confirmed to meet the contract conditions and technical requirements. After this, the product is delivered to the user authority; however, additional steps such as training, logistics support infrastructure, and acceptance at the unit level may be required for it to fully enter operational use. Therefore, news of “delivered” does not always indicate the same moment as news of “operational.”
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 progress in a different order depending on the project’s procurement model, scale, and technological maturity.
Incorrect: If the prototype is successful, it immediately goes into mass production.
Correct: There are testing, qualification, and acceptance processes between the prototype and mass production; these steps are not skipped.
Incorrect: Delivery means the product is fully operational.
Correct: After delivery, processes such as training, logistical preparation, and unit acceptance may continue.
Frequently Asked Questions
How many years does a defense project typically take?
It varies depending on the scale of the project and the procurement model; domestic development projects generally take longer than off-the-shelf purchases.
Is there a difference between the prototype and the mass production product?
Yes, the prototype is revised based on deficiencies identified during testing; the mass production product includes these revisions.
Who conducts the acceptance test?
Acceptance processes are carried out in coordination with the SSB, relevant user authorities, and the contractor.
Does every project go into mass production?
No; some projects may stop at the testing phase, change scope, or be canceled.
Does a product that enters inventory never change?
No; it continues to be developed through modernization and software updates throughout its life cycle.
Related Content
- What is the Presidency of Defense Industries, What Does It Do?
- Why is the SSB Necessary? What is the SSB Good for if Companies are Producing?
References
- 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

