Kirikkale Software Partner: Enterprise Software for the Defense Supply Chain

Kirikkale software partner for the defense supply chain

For a supplier in Kirikkale, a software investment is less about screens and more about traceability, document discipline and security. When we discuss Kirikkale software needs with manufacturers, they usually describe the same picture: the ERP lives in one place, quality records sit in spreadsheets, drawing revisions are scattered across shared folders, and when a customer audit is announced, someone has a few days to stitch it all together. For companies that supply parts, semi-finished goods or services to defense prime contractors and MKE plants, that fragmentation quickly becomes contractual risk.

This guide is written for owners, quality managers and IT leads at metalworking shops, machinery makers, defense sub-suppliers and service firms around the refinery in Kirikkale, Türkiye. Aksiyon Soft is headquartered in Samsun and has no office or branch in Kirikkale. We deliver remotely and plan on-site visits for critical steps such as discovery workshops, user acceptance or go-live, depending on the project schedule.

In short

• Kirikkale’s industry grew around MKE plants, defense sub-suppliers and the Tüpraş refinery, and its software needs follow that supply chain.
• The usual priorities are lot/serial traceability, document revision control and supplier portals.
• For classified work, the clearance requirements of Law No. 5202 shape hosting and access decisions from day one.
• Data flowing between ERP, quality, e-Waybill (e-İrsaliye) and portals should be governed by a middleware layer.
• Aksiyon Soft is based in Samsun and works with Kirikkale companies remotely, with planned on-site visits when needed.

• • •

How does Kirikkale’s industrial base shape its software needs?

According to the investment catalogue of the Ahiler Development Agency (AHİKA) for the Kirikkale Weapons Industry Specialized OIZ, the sector’s roots go back to 1925, when the Cannon and Ammunition Factory was founded; the growing number of plants was later attached to the Mechanical and Chemical Industry Corporation established in 1950. The same source notes that Kirikkale became a province in 1989 and that the city grew hand in hand with the defense industry. Today the official MKE website lists Weapons, Ammunition, Heavy Weapons, Steel and Brass, and Gunpowder factories with Kirikkale addresses.

Entrepreneurs who invested to supply these plants with intermediate goods and raw materials created a cluster of defense sub-suppliers. The Invest in Kırıkkale site describes the province as “the city that gave its name to a firearm” and says it hosts more than 20 private-sector investors in the field. The Kirikkale Weapons Industry Specialized OIZ, the country’s first and only zone dedicated to the weapons industry, covers 50 hectares and was registered as a legal entity in 2013, according to AHİKA.

Energy is the other pillar. Tüpraş’s Kirikkale Refinery was founded in 1986, and its capacity was registered at 5.4 million tonnes per year in 2019. Tüpraş also states that the refinery has the highest road-tanker loading capacity in Türkiye, which creates a separate digitalization space for local maintenance, contractor and logistics firms.

Local sector	Typical software need	Critical integration
Defense sub-suppliers (machining, forging, tooling)	Lot/serial traceability, nonconformance and corrective action records	ERP, quality management, prime contractor portal
Metal and machinery suppliers	Work order tracking, material certificate archive, capacity planning	ERP, MES or machine data, e-Waybill
Refinery maintenance and service firms	Field work orders, work permits, equipment maintenance history	Customer work order system, mobile field app
Logistics and warehousing	Shipment planning, vehicle and document tracking	e-Waybill, accounting, customer portal

• • •

How do you build traceability and document control for a defense supplier?

The audit question is simple: “Which raw material lot, which machine and which drawing revision was this part made from, and who approved it?” Answering that in minutes requires data to be captured in the right structure at the moment of production. Reports assembled from spreadsheets afterwards cost time and do not inspire confidence.

Lot and serial number chain

At goods receipt the material certificate is matched to a lot; when a work order is opened, that lot is linked to it and inspection results are written to the same record. MKE’s Steel and Brass Factory page lists tests such as XRF, spectrometry and ultrasonic inspection. On the supplier side, storing similar results as queryable data rather than PDFs is what makes traceability real.

Document revision control

Drawings, control plans and work instructions should be managed by revision, and the shop floor should only see the revision in force. An approval workflow writes who released what and when into the audit trail. An enterprise document management platform replaces the scattered folder structure.

Supplier and customer portals

Prime contractors increasingly expect orders, delivery dates and quality documents through portals. Running your own portal, or pushing data automatically to the customer’s portal, ends the habit of moving files by e-mail. Our article on RBAC access model design is a good starting point for the permission model.

• • •

How do security requirements affect the software architecture?

Article 6 of Türkiye’s Defense Industry Security Law No. 5202 requires a Personnel Security Clearance for anyone accessing classified information, documents or projects, and a Facility Security Clearance for the site where the project is carried out. MKE’s factory pages also highlight their facility security certificates. In software terms, this means deciding where each data set lives and who can access it before the contract is signed.

In practice, modules that touch classified data often run on on-premise servers in a network segment closed to the internet, while the customer-facing portal sits in a separate layer and exposes only shareable data. A software vendor’s remote access should be logged and opened only for limited time windows. We cover vendor-side risk in more detail in supplier data breaches and KVKK.

• • •

Middleware and system integration

A typical Kirikkale supplier has at least four systems that must talk to each other: the ERP or accounting package, quality records, machine or production data, and the customer’s portal. On top of that comes the Revenue Administration’s (GİB) e-Waybill application, which General Communiqué No. 509 made mandatory for certain groups of taxpayers. Wiring each system directly to every other one produces a spider’s web that breaks at the first change.

A middleware layer brings those connections into one place. A sample flow: when a work order is closed in the ERP, the middleware captures the event, pulls the inspection result and lot data from the quality module, drafts the e-Waybill and sends a shipment notice to the prime contractor’s portal. If the portal does not respond, the message waits in a queue, is retried, and the same shipment is never sent twice. We explain these patterns in outbox pattern, idempotency and retries, and the overall design in our enterprise integration middleware architecture guide.

For maintenance firms working around the refinery the scenario differs: work permits, equipment numbers and completion photos travel between the customer’s work order system and a mobile field app. In both cases the middleware leaves an audit trail of who sent what and when. We build this with our API and integration service and the API and data integration platform.

The historic Çeşnigir Bridge over the Kızılırmak (Photo: 753okiwiki, CC BY-SA 4.0, Wikimedia Commons)

Central Kirikkale, 2013 (Photo: 71ergun, CC BY-SA 3.0, Wikimedia Commons)

For metal and machinery suppliers, machine data is the shared source of work orders and quality records.

• • •

How should a software project in Kirikkale be phased?

The AHİKA catalogue also lists the province’s industrial zones: Kirikkale 1st OIZ covers about 150 hectares and Keskin OIZ about 153 hectares. Many companies there are mid-sized, family-run and heavily dependent on one large customer. In that setting, a phased roadmap carries far less risk than a program that changes everything at once.

Phase 1: Discovery that works back from an audit question

Pick the question you struggled with most in your last customer audit, and we map together where that data lives today. A few workshops are usually enough to reveal missing tables and approval steps.

Phase 2: An MVP for one product family

Take traceability and document control live for a single product family first. Scaling before operator screens, barcode scanning and inspection entry have been tested on a real shift produces a system the shop floor will not adopt.

Phase 3: Integration and roll-out

Once the MVP is stable, ERP, e-Waybill and customer portal connections are added through the middleware, and other product families follow the same template. Every step has written acceptance criteria and a rollback plan.

• • •

Checklist before choosing a software partner in Kirikkale

Clarifying these points internally before you request proposals lets you compare vendors on scope rather than price alone.

• Is it documented which data is classified and where it will be hosted?
• Have you chosen a sample audit question for the lot, serial and revision chain?
• Is there an inventory of ERP, quality, e-Waybill and customer portal systems?
• Are the vendor’s remote access rules and logging method defined?
• Are acceptance criteria and the post-go-live support period (SLA) defined?
• Does the contract state clearly who owns the source code and documentation?

For the full evaluation framework, see our guide on how to choose a software company.

• • •

How can Aksiyon Soft help?

Through our enterprise software solutions service we build traceability modules, document control, supplier portals and the integration layer that ties them together in one consistent product. Our delivery model has four steps: discovery (process, data and security inventory), an MVP (for example lot traceability for one product family), two-week sprint demos, and hypercare followed by SLA-backed support after go-live.

Our team is based in Samsun and works remotely across Türkiye; we do not claim a branch or representative office in Kirikkale. Its proximity to Ankara often makes it easy to combine discovery or acceptance days into a single trip. To compare neighboring provinces, read our guides for Ankara, Yozgat, Corum, Amasya and Tokat; for how our head office works, see Samsun enterprise software partner.

Frequently asked questions

Do you have an office in Kirikkale?

No. Our head office is in Samsun. We run day-to-day work with Kirikkale companies remotely and plan on-site visits for steps such as discovery, acceptance or go-live.

Is remote delivery possible for classified projects?

Parts that touch classified data are handled in the environment your organization specifies and by authorized staff. We take on the overall architecture, non-classified modules and development with test data, and define access rules in the contract.

Do we need to replace our existing ERP?

Usually not. We add traceability, document control and portal modules alongside your ERP and manage the data flow between them through middleware.

How soon can we see a working version?

It depends on scope. A narrow MVP such as lot traceability for one product family can be demoed within a few sprints; programs with multiple integrations take longer. We share timelines and assumptions in writing after discovery.

Do you handle e-Waybill integration as well?

Yes. Depending on your integration method, we connect e-Waybill creation and status tracking to your ERP and shipment flow.

Who owns the source code?

That is set in the contract. Enterprise projects usually aim to hand over source code and documentation to the client; third-party licenses are listed during discovery.

Let’s talk about your project

Tell us in a few sentences about your traceability, document control or supplier portal needs in Kirikkale, and we will clarify scope, risks and the delivery model together in a discovery session. Reach us through the contact form.

Sources

• Ahiler Development Agency — Kirikkale Weapons Industry Specialized OIZ investment catalogue (accessed October 2026)
• Invest in Kırıkkale — Defense industry (accessed October 2026)
• MKE A.Ş. — Weapons Factory (accessed October 2026)
• MKE A.Ş. — Steel and Brass Factory (accessed October 2026)
• Tüpraş — Kirikkale Refinery (accessed October 2026)
• Turkish Legislation Information System — Defense Industry Security Law No. 5202 (2004)
• Revenue Administration (GİB) — About e-Waybill (accessed October 2026)
• Ahiler Development Agency — Kirikkale Documentry Film, YouTube (2017)