Production planning
- Commandes
- Readiness refresh
- Material reservation
- Release signoff
Chaîne d approvisionnement et opérations
Production
Manufacturing control for production orders, work orders, material issue, output completion, variance, and audit close.
Implémenté
Evidence-first module page
Primary users
Production manager
Planner
Shop-floor supervisor
Cost reviewer
Visuel derive de l application
Production execution workspace
Release
Signoff gated
Variance
High-risk flagged
Matières
Inventory linked
| Domaine | Statut | Preuve |
|---|---|---|
| Commandes | Readiness checked | Release proof |
| Work orders | Execution tracked | Shop-floor log |
| Audit close | Evidence packed | Close package |
Workflows clés
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
Plan production orders and check release readiness
Step 2
Reserve and issue materials from inventory
Step 3
Run work orders and record output completion
Step 4
Review variance, quality handoffs, and audit-close evidence
Feature checklist
Capabilities grouped the way operators look for them.
Shop-floor execution
- Work orders
- Start/pause/resume
- Quality inspection
- Output completion
Cost and close
- Variance review
- Accounting handoff
- Audit close
- Evidence packs
Carte des modules connectes
How this module exchanges business context with the rest of ERPStack.
| Module | Relation |
|---|---|
| Stock | Material reservation, issue, and completed output |
| Qualité | Inspection, disposition, and release gating |
| Comptabilité | Cost variance and manufacturing handoff evidence |
| BI | Throughput, variance, downtime, and readiness analytics |
Governance and reporting
Controls and management visibility expected from a serious ERP module.
Gouvernance
- Release signoff controls
- High-variance SIEM events
- Audit-close evidence
- Material issue traceability
Rapports
- Production readiness
- Work order status
- Variance
- Audit close
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: Production 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.