Defence production where every unit can be proven

One data environment for engineering, the line, and finance: specifications, production tasks, warehouse, serial numbers, and contract documents — in your perimeter, on Creatio. You deploy the system in your own environment; we provide the evidence base you use for security authorization under Resolution No. 712.

What Creatio certificates cover and what remains your responsibility

You are under scrutiny from four sides at once

A state contract is not an order. It is a promise, signed, and someone will come to check that you kept it. The customer asks about one delivery date and what has already shipped. The military representative will not sign the act until he has seen the test protocol and the batch documents. A licence audit looks at qualifications, equipment, calibration and whether the documentation in use is current. An export raises the end-user question: who they are, what confirms the intended use, and which licence covers it.

The answers exist in the plant. The problem is where they live: the military representative's folder, an engineer's mailbox, the planner's spreadsheet, the certificate file at the warehouse. Assembling them takes weeks, and sometimes a shipment that does not leave.

Syntech Manufacturing does not add one more folder. It keeps the answers where they are created: in receiving, in the operation, in the inspection, in the act, in the issue document.

The six threads they pull on

State contracts and delivery dates

a contract is flagged as a state contract: defence order code, the customer's military unit, the military representation, the advance offset percentage. Then stages, specification, delivery schedule and production orders behind each delivery. The panel forecasts every delivery as on track, at risk or late, with the reason and the float.

Military acceptance and the act archive

an act covers a batch, a delivery or a list of serial numbers: acceptance type (military representative, customer, internal QC), decision, remarks, both signatures, printed form. Every serial knows its act, and a shipment without one is stopped or flagged.

NATO codification

the product card carries a 13-digit NSN, the NIIN is derived automatically and the NCAGE is validated. A separate list holds codes by supplier and manufacturer, and the NSN goes onto the label.

Export control

export classification on the product, licences with usage charged by quantity and value, end users with their screening status, end-use certificates. The check runs before the issue is written: denied parties and destinations are always blocked, the rest warn or block as you decide.

Traceability, recall and the electronic dossier

from a serial number down to component batches and supplier certificates, and up to the customer, the contract and the act. Everything affected is held or recalled in one action; the dossier prints as a page or downloads as an archive.

Staff reservation and qualifications

military registration data on the employee, reservation lists with candidate selection, the quota gauge against the critical-enterprise decision, a daily warning before deferments lapse, history with reasons. Beside it, the qualification matrix checked at operation start.

The requirement matrix: what is met and what is not

We scored release 2.1.0 against the Ukrainian defence-manufacturing requirement matrix. Of its 37 functions, eight are platform-level — record-level rights, audit logs, backup, isolated deployment — and come from Creatio, so we left them out. That leaves 29 business requirements, scored strictly: "met" means the whole requirement can be completed in the product today, with no manual assembly and no external system. "Partial" means part of it works, "not met" means it is not there. All 29 rows are below.

25 met · 2 partial · 2 not met — out of 29 business requirements

Licensing of development and manufacture of military equipment

Records of the qualified composition of personnel

Met

Qualifications sections, qualifications required on operations, check at operation start

Licensing of development and manufacture of military equipment

Records of equipment

Met

Equipment register: passports, preventive maintenance, repair orders, calibrated measuring instruments

Licensing of development and manufacture of military equipment

Technological documentation kept under version control

Met

BOM/routing revisions with change notices; tech maps versioned, operator sees current version

Licensing of development and manufacture of military equipment

Produce the evidence pack for a licence audit within an hour

Partial

Product dossier (PDF/ZIP) per batch or serial; no single licence-audit pack

Special permit for access to state secrets (business part)

Nomenclature of positions and register of clearances

Not met

No clearance register; job titles come from the Creatio contact record only

NATO standardisation and codification

Item master with NATO codes and "our part number ↔ NSN"

Met

NATO codification tab: NSN, NIIN, NCAGE, codes per supplier, search by NSN

NATO standardisation and codification

Product configuration

Partial

Revision effectivity by date and serial, as-built composition; no variants, no as-designed comparison

NATO standardisation and codification

Versioned bill of materials with change history

Met

Revisions tab with side-by-side comparison; engineering change notices with approval

Export control

Met

Export licences section: items, quantity and value usage, statuses, expiry job

Export control

Met

End-user flag and screening (cleared / watch / denied) with audit trail on the account

Export control

Met

End-use certificates section (EUC, IIC, DV), linked to licence and end user

Export control

Automatic shipment block when no valid licence exists

Met

Check runs before Issue; denied parties always blocked, licence block is a setting