Defense Compliance

What it is for

Defense Compliance (Savunma Uyum) runs the quality and security compliance work of an organization serving the defense industry in one place. The same engine carries different frameworks (quality standards, document and permit programs, customer specifications): frameworks and their versions are defined, the organization collects answers and evidence for each requirement, reviewers decide, gaps become findings and actions, and finally an audit package is prepared.

It belongs to the separately licensed Defense package and does not appear in the menu without it. Defense Security is a separate product; if both are licensed, the dashboard and the war room can show each other’s counts. Readiness percentages on screen are the organization’s own indicators, not an official score, level or document status; official results are recorded separately.

Who uses it

Quality and compliance officers, evidence-owning units, reviewers, auditors and management. The page opens for anyone who can see at least one Defense Compliance section; each tab depends on its own section permission, and a tab without permission is not shown at all.

Screens

• Dashboard (Pano): the first tab.
• Frameworks (Çerçeveler): set up frameworks, enter requirements, publish versions.
• Evidence vault (Kanıt kasası): attach evidence and link it to requirements.
• Assessments (Değerlendirmeler): assess against a published version and assign items to owners.
• Findings and actions (Bulgu ve eylemler): gaps become findings and actions.
• Audits (Denetimler): plan and run audits, including mock audits.
• Capability inventory (Yetkinlik envanteri): competencies.
• Contract quality requirements (Sözleşme kalite şartları): customer quality clauses.
• Import (İçe aktarma): bring in an existing readiness workbook.
• War room (Harp Odası): follows readiness.
• Reports (Raporlar): produces output.
• Audit package (Denetim paketi): the file set handed to the auditor.

Typical workflow

1. Set up the framework (from a shell, a package or by hand), enter its requirements and publish the version.
2. Open an assessment against the published version and assign items to owners.
3. Owners write answers and add evidence, which is verified by an independent person.
4. Reviewers decide on items; gaps become findings and actions, which are verified.
5. Plan and run audits, then follow readiness on the dashboard and war room and prepare reports and the audit package.

Related modules

• Defense Security

Step-by-step screen guides are currently available in Turkish; the links above open them.