Quality Report Intelligence
Product documentation
Every quality document your customer demands, written from your evidence, proven line by line, defensible in an audit. Works with the QMS you already have.
What QRI is
QRI writes the quality documents your customer demands (NCR/CAR, 8D, FRACAS, government QA defect reports, counterfeit-part reports, QA activity plans, FAI/AS9102, PPAP) from evidence you already hold, with every sentence traceable to its source.
It is not a QMS. Your existing QMS stays the system of record. QRI imports the case, drafts and proves the report, gates its release, and returns the package.
Three commitments define the product. Grounding is enforced, not promised: generated text is a ledger of atomic claims; each claim cites a retrievable source. Release is deterministic: preflight is a rule engine, not a model. The obligation ends at acceptance, not export: lifecycle runs draft → review → approval → QMS return → customer/GQAR acceptance.
Core concepts
- Source case: the QMS record a report is written from. Reports are normally created from an imported case; manual creation is an audited exception.
- Source-locked field: a critical value (part number, serial/lot, firmware revision, test temperature) bound to a single authoritative source. Conflicting sources block confirmation until resolved.
- Claim ledger: the compiled draft as atomic claims, each carrying its citation and the model/version/hash that generated it.
- Preflight: deterministic release gates. Blocking rules stop submission; reviewer warnings do not. Every failed row names its owner role and whether retry is safe.
- Role separation: authors hold EDIT_RECORD, reviewers hold APPROVE_REPORT; the author of a version can never approve it. Approval requires an e-signature with stated meaning.
- GQAR lifecycle: for government contracts, submit package → optional witness of RCA/corrective action → acceptance or rejection, per 방위사업 품질관리 규정 별지 제18호 (AQAP 2110 equivalent for NATO-pattern customers).
- Model qualification: no model serves a production task until it passes measured gates (extraction accuracy, retrieval nDCG, unsupported-claim escape ≤1%, terminology accuracy). Weights hash is recorded on every claim.
Screen reference
- Work: Dashboard (open / blocked-by-preflight / ready / past-due, attention list); My Work; Quality Report Work Queue (shared register with saved views, filters, columns).
- Quality Records (QRI-native): Imported Cases (QMS/file ingestion airlock); Evidence Library (immutable evidence with exact provenance).
- Connected QMS (external): Quality Events, CAPA, Actions, Effectiveness, Suppliers, Document Register as read-mirrors, bannered EXTERNAL.
- Knowledge & Standards: Historical Knowledge (hybrid retrieval; similarity is never presented as proof of cause); Templates & Rules (8 types, versioned, clause citations); Terminology (controlled KO/EN register).
- Report form (11 tabs): Overview · Report Sections · Source Case & Sync · Confirmed Fields · Evidence Register · Historical Cases · RCA Assistant · Report Studio · Preflight · Review & Return · Audit Trail.
- Administration: AI Models & Runtime; Import & Onboarding; Workflow Configuration; Users & Access; System Validation (GAMP-5 IQ/OQ/PQ baselines); System Audit; Connected QMS Modules.
Report types
Eight templates ship in demo scope. Report output language is a template property (KDS templates → Korean; AS/AIAG → English), independent of interface language. Technical identifiers are never translated.
- NCR/CAR v3.2KDS 0050-9000 8.7 · 10.2 · KS Q ISO 9001
- 8D v2.1AIAG/VDA · IATF 16949
- FRACAS v1.4MIL-HDBK-2155 · KDS 0050-9000 10.2 · 10.3.1
- GQA-DEFECT v1.0KDS 0050-9000 8.5.5.1 · 별지 제18호 · AQAP 2110
- COUNTERFEIT v1.0KDS 0050-9000 8.1.4 · 8.1.5 · AS9100
- QA-PLAN v1.0KDS 0050-9000 8.1.2 · 8.7.3 · 별지 제18호
- FAI/AS9102 v1.0AS9102C · AS9100D 8.5.1.3
- PPAP v1.0AIAG PPAP 4th Ed. · IATF 16949 8.3.4.4
Deployment & security
On-premise, air-gapped: no external API dependency; local models on customer GPU. RBAC with change-controlled accounts (deactivated, never deleted). Append-only audit trails at record and system level.
E-signatures carry meaning, credential, and acknowledgement. Classification marking schemes are tenant configuration (e.g. US CUI), stamped on exports, never hardcoded.
Connector failure paths (offline / stale / read-only / rejected payload) fail safe: nothing partially written; retry safety is stated.
Roadmap items are not sold as current: HWPX/DOCX/PDF-A export, OCR/HWP/XLSX/instrument-CSV/photo ingestion, redlines and version compare, submission tracking, reporting analytics, customer-specific template packs.
Demo guide
Synthetic data throughout, watermarked. The status bar states that this is not an approved quality record. One-click role entry (Quality Engineer / Quality Reviewer / System Administrator), no credentials.
Suggested path: open RPT-2026-0041 → resolve the firmware source conflict → compare precedents → record RCA (5-Why/fishbone) → compile the draft → repair claims → run preflight → submit → switch to Reviewer → approve with e-signature → return to QMS → record GQAR acceptance.
Failure demos: set the connector offline/stale; try to approve as the author (refused); try to assign an unqualified model (refused). Reset Demo restores the seeded state.
Glossary
Controlled Korean / English pairs
- 부적합
- nonconformance
- 시정조치
- corrective action
- 사전검증
- preflight
- 출처 잠금
- source-locked
- 특채
- concession
- 처분 결정 권한
- disposition authority
- 정부품질보증 대표자
- GQAR
- 입회
- witness
- 인수
- acceptance
- 반송
- rejection/return
- 발행
- release/issue
- 게시
- publish
- 유출점
- escape point
- 적격성 평가 qualification.
FAQ
What is QRI?
QRI (Quality Report Intelligence) is on-premise software for defense and regulated manufacturers that writes customer-required quality documents from the manufacturer's own registered evidence: nonconformance and corrective-action reports (NCR/CAR), 8D problem-solving reports, FRACAS failure reports, first-article inspection reports (AS9102), and PPAP packages. Every generated sentence traces to a retrievable source, and a deterministic preflight check gates release.
How does QRI prevent AI hallucination in quality reports?
QRI separates generation from release. Language models draft; a deterministic rule engine blocks release of any claim that lacks a cited source, any part number without an authorized source, and any causal conclusion without a verification requirement. The measured escape rate of ungrounded assertions into approved reports is the gating metric, reported with numerator, denominator, and method.
Does QRI replace our QMS?
No. QRI connects to the existing QMS (quality events, CAPA, suppliers, document register remain the system of record), imports cases, writes and validates the report package, and returns it. The lifecycle tracks through customer acceptance. For Korean defense contracts, through GQAR (Government Quality Assurance Representative) acceptance under 방위사업 품질관리 규정 별지 제18호.
Can QRI run in an air-gapped network?
Yes. QRI runs entirely on-premise with local language models (7B–32B class), no external API calls, and a model-qualification workflow: a model must pass measured gates (extraction accuracy, retrieval quality, unsupported-claim rate, terminology accuracy) before it may serve any production task.
Which standards does QRI support?
Report templates cite their governing clauses: KDS 0050-9000 (Korean defense QMS requirements), KS Q ISO 9001, AS9102C first-article inspection, AIAG PPAP 4th edition, AIAG/VDA 8D, IATF 16949, MIL-HDBK-2155 FRACAS, and AQAP 2110 for NATO-pattern government quality assurance.
Is QRI available in Korean?
Yes. The interface, controlled terminology register (approved Korean/English quality-term pairs), and report output are fully bilingual. Report output language is set by the template, independent of interface language.