跳到内容
ERPStack

供应链与运营

质量

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/quality
App-derived visual
Quality management console
Open app route
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.

3 capability groups

Inspection control

  • Quality plans
  • Inspections
  • Provider results
  • Certificate evidence

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.