Inspection control
- Quality plans
- Inspections
- Provider results
- Certificate evidence
공급망 및 운영
품질
Quality management for plans, inspections, NCR/CAPA, supplier quality, certificates, overrides, and disposition evidence.
구현됨
Evidence-first module page
Primary users
Quality manager
Inspector
Supplier quality lead
Operations reviewer
App-derived visual
Quality management console
Gates
Override controlled
증거
준비 상태
예외
Worklisted
| 영역 | 상태 | 증거 |
|---|---|---|
| Inspections | Plan driven | Result evidence |
| NCR/CAPA | Workflow managed | Action trail |
| Certificates | Lifecycle tracked | Retention link |
핵심 워크플로
What the module helps operators complete.
Each workflow is written as an operational path, not a marketing claim, so buyers can understand the day-to-day module fit.
Step 1
Define inspection plans and record inspection outcomes
Step 2
Manage NCR, CAPA, supplier audit, and disposition workflows
Step 3
Control quality gate overrides and exception worklists
Step 4
Generate certificate, supplier rating, and compliance evidence
Feature checklist
Capabilities grouped the way operators look for them.
Exception handling
- NCR/CAPA
- 처분
- Exception worklists
- Due-date overrides
Supplier quality
- Supplier audits
- Ratings
- Review workflow
- Financial trace exceptions
Connected module map
How this module exchanges business context with the rest of ERPStack.
| Module | 관계 |
|---|---|
| 재고 | Blocked stock, disposition, and traceability impact |
| 생산 | Inspection and release gate handoffs |
| 구매 | Supplier quality, audit, and rating feedback |
| 문서 | Certificate, evidence, and retention links |
Governance and reporting
Controls and management visibility expected from a serious ERP module.
거버넌스
- Quality gate override controls
- Disposition reconciliation
- Supplier rating workflow
- Evidence retention audit
보고서
- Inspection status
- NCR/CAPA workload
- Supplier quality
- Certificate readiness
AI coverage policy
What ERPStack can honestly claim for this module today.
AI claims are tied to the official Agent Tool Registry, evaluation evidence, safe-mode controls, and scheduled-agent monitor readiness. Roadmap modules only show planned coverage until module-native tools are implemented.
AI L2 ready| Coverage claim | Current AI coverage: Quality L2/L2 ready through the official Agent Tool Registry. |
|---|---|
| Governance evidence | Governance evidence: 2 registered tools, 2 evaluation cases, tenant/RBAC/safe-mode registry controls, and AI log evidence. |
| Scheduled monitor | Scheduled monitor readiness: not in the current proactive-agent monitor wave. |
| L4/L5 boundary | Remaining L4/L5 gap: no autonomous execution or self-optimizing agent behavior is claimed; write paths remain permissioned, previewed, and confirmable. |
Evidence-first standard
Module pages explain value, workflow, control, and proof in one place.
This page structure supports the current public module catalog with app-derived visuals, connected-module evidence, governance proof, and report context that can be compared against real product routes.
Feature clarity
Buyers can see concrete function groups instead of vague capability claims.
Operational fit
Workflows, users, and connected modules show where the module belongs.
Governance proof
RBAC, audit, SIEM, approvals, and reporting are surfaced as first-class concerns.
Review path
Public pages link back to app routes so reviewers can compare page claims to product surfaces.