State contracts and delivery dates
Defence order code, military unit, representation, delivery schedule, advances, production orders and forecast: on track, at risk or late.
MILTECH / DEFENCE
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.
25
requirements met
2
partial
2
not met
29
business requirements scored
CONTROL
You are under scrutiny from four sides at once
A state contract is not just an order. The customer asks about the delivery date, the military representative needs the test protocol and batch documents, a licence audit checks qualifications, equipment and current documentation, and export raises the end-user and licence question. Syntech Manufacturing keeps the answers where they are created: in receiving, in the operation, in inspection, in the act and in the issue document.
Military acceptance
An act covers a batch, delivery or serial numbers: acceptance type, decision, remarks, signatures, printed form and shipment link.
NATO codification
The product card carries NSN, NIIN, NCAGE and supplier/manufacturer codes; the NSN goes onto the label.
Export control
Product classification, licences with quantity and value usage, end users, end-use certificates and a check before shipment.
Traceability and recall
From a serial number down to component batches and certificates, and up to the customer, contract and act; hold or recall affected items in one action.
Staff reservation and qualifications
Military-registration data, reservation lists, quota, expiry warnings, history and a qualification matrix checked at operation start.
MILTECH / DEFENCE
What the team sees
History of every serialized item
From a serial number down to component batches and supplier certificates; from the serial number up to the customer, contract and act.
Changes reach the line quickly
BOM and routing revisions, ECN and current operator instructions do not get lost in email and paper.
Shipment document packs
Test protocols, acceptance acts, certificates, licences and labels are linked to the batch or serial number.
Inside your perimeter
On-premise or private cloud, roles, SSO, 2FA, change logs and isolation by contract or project.
25 / 29
The requirement matrix: what is met and what is not
We scored the product against the Ukrainian defence-manufacturing requirement matrix. Of 37 functions, eight are platform-level — record-level rights, audit logs, backup and isolated deployment — and come from Creatio. Of 29 business requirements, 25 are met, 2 are partial and 2 are not met.
25
requirements met
2
partial
2
not met
HONEST LIMITS
What we do not do
You should see this list in the first week, not during acceptance.
- No register of state-secret clearances.
- No integration with DOT-Chain Defence or another defence marketplace.
- No bundled qualified e-signature provider; there is a connection point for an external provider.
- End-user screening is manual; the system keeps the audit trail.
- Financial accounting stays in an external accounting system.
Platform certificates are evidence, not automatic compliance
Creatio has ISO/IEC 27001:2022, ISO 9001:2015, SOC 2 Type II and ISO/IEC 27017/27018 for the relevant scopes. But your system’s compliance is assessed by the system owner after deployment and configuration.
In your perimeter
On-premise or private cloud. The manufacturing contour runs without an external service.
Roles, rights and audit
Record- and column-level rights, change logs, SSO and 2FA are used at the platform level.
Isolation by contract
Access to a contract, order or product is controlled by roles, so a neighbouring project stays invisible to teams that do not need it.
Test us on a contract of your own
Bring your state contract and one serial number. In the demo we take them from the delivery schedule to the acceptance act and licence check — and show where the system still has limits.