manufacturing
This commit is contained in:
29
README.md
29
README.md
@@ -21,6 +21,7 @@ Current foundation scope includes:
|
||||
- branded quote, sales-order, and purchase-order PDFs through the shared backend document pipeline
|
||||
- shipping shipments linked to sales orders with packing slips, shipping labels, bills of lading, and logistics attachments
|
||||
- projects with customer/commercial/shipment linkage, owners, due dates, notes, and attachments
|
||||
- manufacturing work orders with project linkage, material issue posting, completion posting, and work-order attachments
|
||||
- file storage and PDF rendering
|
||||
|
||||
## Product Map
|
||||
@@ -33,20 +34,20 @@ Current completed foundation areas:
|
||||
- sales and purchasing foundation
|
||||
- shipping foundation
|
||||
- projects foundation
|
||||
- manufacturing foundation
|
||||
- branding, attachments, auth/RBAC, and PDF infrastructure
|
||||
|
||||
Planned cross-module execution areas:
|
||||
|
||||
- manufacturing execution
|
||||
- planning and gantt scheduling
|
||||
|
||||
Near-term priorities:
|
||||
|
||||
1. Manufacturing execution
|
||||
2. Vendor invoice/supporting-document attachments and broader vendor-facing operational depth
|
||||
3. Sales approvals and revision history
|
||||
4. Planning and gantt scheduling with live project/manufacturing data
|
||||
5. Inventory transfers, reservations, and deeper stock controls
|
||||
1. Vendor invoice/supporting-document attachments and broader vendor-facing operational depth
|
||||
2. Sales approvals and revision history
|
||||
3. Planning and gantt scheduling with live project/manufacturing data
|
||||
4. Inventory transfers, reservations, and deeper stock controls
|
||||
5. Broader audit-trail coverage and operational diagnostics
|
||||
|
||||
Revisit / deferred items:
|
||||
|
||||
@@ -64,6 +65,7 @@ Dashboard direction:
|
||||
- future additions should emphasize relevant metrics, next actions, alerts, and workflow shortcuts
|
||||
- richer recent-activity widgets and exception queues are a planned QOL follow-up, not a separate landing-page redesign
|
||||
- projects now feed dashboard widgets for active programs, overdue work, and risk
|
||||
- manufacturing now feeds dashboard widgets for released work, overdue orders, and execution load
|
||||
- future project widgets should deepen milestones, shortages, and shipment readiness
|
||||
|
||||
Navigation direction:
|
||||
@@ -92,12 +94,16 @@ Next expansion areas:
|
||||
|
||||
## Manufacturing Direction
|
||||
|
||||
Manufacturing should remain a separate execution subsystem rather than being collapsed into Projects.
|
||||
Manufacturing is now a separate execution subsystem rather than being collapsed into Projects. The current slice ships work-order records with build-item linkage, optional project linkage, warehouse/location output posting, BOM-based material requirement visibility, material issue posting, completion posting, work-order attachments, and dashboard visibility.
|
||||
|
||||
Planned interactions:
|
||||
Current interactions:
|
||||
|
||||
- Projects: manufacturing orders may belong to a project, but projects remain the higher-level long-running record
|
||||
- Inventory: manufacturing consumes components and produces stock
|
||||
- Inventory: manufacturing consumes components and produces stock through real issue/receipt transactions
|
||||
- Dashboard: manufacturing now contributes released/open/overdue load widgets
|
||||
|
||||
Next expansion areas:
|
||||
|
||||
- Purchasing: shortages and buyout demand should surface from manufacturing execution
|
||||
- Shipping: completed manufacturing should feed shipment readiness
|
||||
- Planning: manufacturing orders, routings, and work centers should drive capacity and schedule views
|
||||
@@ -308,15 +314,16 @@ As of March 14, 2026, the latest committed domain migrations include:
|
||||
- sales totals and commercial fields
|
||||
- shipping foundation
|
||||
- projects foundation
|
||||
- manufacturing foundation
|
||||
|
||||
Recent roadmap-driving migrations should always be applied before validating new CRM, inventory, sales, shipping, or purchasing features in a running environment.
|
||||
|
||||
## UI Notes
|
||||
|
||||
- Dark mode persistence is handled through the frontend theme provider and should remain stable across page navigation.
|
||||
- The shell layout is tuned for wider desktop use than the original foundation build, and now exposes Dashboard, CRM, inventory, sales, shipping, projects, settings, and planning modules from the same app shell.
|
||||
- The shell layout is tuned for wider desktop use than the original foundation build, and now exposes Dashboard, CRM, inventory, sales, shipping, projects, manufacturing, settings, and planning modules from the same app shell.
|
||||
- The active module screens now follow a tighter density baseline for forms, tables, and detail cards.
|
||||
- The dashboard should continue evolving as a modular metric board for future purchasing, shipping, manufacturing, and audit data.
|
||||
- The dashboard should continue evolving as a modular metric board for future purchasing, shipping, planning, and audit data.
|
||||
- The client build still emits a Vite chunk-size warning because the app has not been code-split yet.
|
||||
|
||||
## PDF Generation
|
||||
|
||||
Reference in New Issue
Block a user