cleanup
This commit is contained in:
281
ROADMAP.md
281
ROADMAP.md
@@ -3,193 +3,83 @@
|
||||
## Documentation maintenance
|
||||
|
||||
- Keep [CHANGELOG.md](D:/CODING/mrp-codex/CHANGELOG.md) updated alongside roadmap-driving feature completion, priority shifts, and notable delivery milestones.
|
||||
- Keep [SHIPPED.md](D:/CODING/mrp-codex/SHIPPED.md) updated when roadmap items move from planned to delivered.
|
||||
- When roadmap changes affect implementation guidance or deployment expectations, update the companion docs in [README.md](D:/CODING/mrp-codex/README.md), [INSTRUCTIONS.md](D:/CODING/mrp-codex/INSTRUCTIONS.md), [STRUCTURE.md](D:/CODING/mrp-codex/STRUCTURE.md), and [UNRAID.md](D:/CODING/mrp-codex/UNRAID.md) in the same change set.
|
||||
|
||||
## Product direction
|
||||
|
||||
MRP Codex is being built as a streamlined, modular manufacturing resource planning platform with strong branding controls, fast operational workflows, and a single-container deployment model that is simple to back up and upgrade.
|
||||
|
||||
## Current status
|
||||
This file tracks work that still needs to be completed. Shipped phase history and completed slices now live in [SHIPPED.md](D:/CODING/mrp-codex/SHIPPED.md).
|
||||
|
||||
### Completed: Foundation release
|
||||
## Near-term priority order
|
||||
|
||||
- Monorepo-style workspace with `client`, `server`, and `shared`
|
||||
- React + Vite + Tailwind frontend shell
|
||||
- Express + TypeScript backend shell
|
||||
- Prisma + SQLite schema foundation with committed initial migration
|
||||
- Local authentication with JWT-based session flow plus persisted session visibility and revocation
|
||||
- RBAC permission model and protected routes
|
||||
- Central Company Settings with runtime branding controls
|
||||
- Light and dark mode theme system
|
||||
- Local file attachment storage under `/app/data/uploads`
|
||||
- Puppeteer PDF service foundation with branded company-profile preview
|
||||
- CRM reference entities for customers and vendors
|
||||
- CRM customer and vendor create/edit/detail workflows
|
||||
- CRM search, filters, and persisted status tagging
|
||||
- CRM contact-history timeline with authored notes, calls, emails, and meetings
|
||||
- CRM shared file attachments on customer and vendor records, including delete support
|
||||
- CRM reseller hierarchy, parent-child customer structure, and reseller discount support
|
||||
- CRM multi-contact records, commercial terms, lifecycle stages, operational flags, and activity rollups
|
||||
- Inventory item master, BOM, warehouse, and stock-location foundation
|
||||
- Inventory transactions, on-hand tracking, and item attachments
|
||||
- Inventory transfers, reservations, available-stock visibility, and work-order-driven material reservation automation
|
||||
- Sales quotes and sales orders with commercial totals logic
|
||||
- Purchase orders with vendor lookup, item lines, totals, and quick status actions
|
||||
- Purchase-order line selection restricted to inventory items flagged as purchasable
|
||||
- Purchase receiving foundation with warehouse/location posting, receipt history, and per-line received quantity tracking
|
||||
- Branded sales quote, sales order, and purchase-order PDF templates through the shared Puppeteer pipeline
|
||||
- Shipping shipment records linked to sales orders
|
||||
- Packing-slip, shipping-label, and bill-of-lading PDF rendering for shipments
|
||||
- Logistics attachments directly on shipment records
|
||||
- Projects foundation with customer, quote, sales-order, shipment, owner, due-date, notes, and attachment linkage
|
||||
- Project list/detail/create/edit workflows and dashboard program widgets
|
||||
- Manufacturing foundation with work orders, project linkage, material issue posting, completion posting, and work-order attachments
|
||||
- Manufacturing stations, item routing templates, and automatic work-order operation planning for gantt scheduling
|
||||
- Vendor invoice/supporting-document attachments directly on purchase orders
|
||||
- Vendor-detail purchasing visibility with recent purchase-order activity
|
||||
- Audit trail coverage across core settings, inventory, purchasing, project, sales, and manufacturing write flows
|
||||
- Admin diagnostics screen with runtime footprint, record counts, storage-path visibility, and recent audit activity
|
||||
- Dedicated user-management screen for account creation, activation, role assignment, and role-permission editing
|
||||
- CRM customer/vendor changes and shipping mutations covered by the shared audit trail
|
||||
- Startup validation during server boot with checks for storage paths, writable directories, database connectivity, client bundle readiness, Chromium availability, and risky production defaults
|
||||
- Backup/restore guidance and exportable support bundles surfaced through the admin diagnostics workflow
|
||||
- Backup verification checklist and restore-drill runbook surfaced through the admin diagnostics workflow
|
||||
- Support-log viewing for startup warnings, HTTP failures, and server errors surfaced through the admin diagnostics workflow
|
||||
- Route-level frontend code-splitting and vendor chunking to keep the initial client payload lighter
|
||||
- SKU-searchable BOM component selection for inventory-scale datasets
|
||||
- Theme persistence fixes and denser responsive workspace layouts
|
||||
- Full-site density normalization pass across active CRM, inventory, settings, dashboard, and login screens
|
||||
- Live planning gantt timelines driven by project and manufacturing data
|
||||
- Sales-order demand planning with multi-level BOM explosion, stock/open-supply netting, and build/buy recommendations
|
||||
- Multi-stage Docker packaging and migration-aware entrypoint
|
||||
- Docker image validated locally with successful app startup and login flow
|
||||
- Core project documentation in `README.md`, `INSTRUCTIONS.md`, and `STRUCTURE.md`
|
||||
1. Support-log filtering, retention controls, and broader support-package polish
|
||||
2. Revision comparison UX for changed sales and purchasing documents
|
||||
3. Project milestones, project rollups, and deeper project-side execution visibility
|
||||
4. Manufacturing routing/work-center depth, labor capture, and capacity-aware execution views
|
||||
5. Dashboard KPI, alert, recent-activity, and exception-widget expansion
|
||||
|
||||
### Current known gaps in the foundation
|
||||
## Active roadmap
|
||||
|
||||
- Prisma migration execution is committed and documented, but local Windows Node 24 schema-engine behavior remains inconsistent; use Node 22 or Docker for migration execution
|
||||
- CRM reporting is now functional, but broader account-role depth and downstream document rollups can still evolve later
|
||||
- The current sales/purchasing/shipping foundation now includes sales approvals and revision history, but still needs vendor exception handling, deeper carrier integration, and richer document comparison tooling
|
||||
- The dashboard is now live-data driven, but still needs richer KPI widgets, alerts, recent-activity queues, and exception reporting as more transactional depth is added
|
||||
- The new projects domain is foundational but still needs milestones, project rollups, and deeper inventory/purchasing/manufacturing tie-ins
|
||||
- The new manufacturing domain is foundational but still needs routings, labor capture, work-center views, and capacity-aware planning tie-ins
|
||||
- Auth sessions are now persisted and revocable, but the admin surface still needs richer filtering, history retention, and unusual-access review tooling
|
||||
### Platform and operational docs
|
||||
|
||||
## Dashboard Plan
|
||||
- Keep the Windows Prisma migration workflow clearer and less fragile for local contributors
|
||||
- Continue tightening backup, restore, and support-runbook guidance as operations maturity grows
|
||||
- Preserve the single-container deployment path while improving diagnostics and supportability
|
||||
|
||||
- Keep `Dashboard` as the primary landing surface for operators
|
||||
- Expand it by modular panels rather than redesigning it for each new feature phase
|
||||
- Prefer metric cards, exception queues, action shortcuts, and status summaries over static descriptive content
|
||||
- Add future widgets for purchasing, shipping exceptions, inventory shortages, planning readiness, and audit/system health
|
||||
- Continue expanding the new project widgets into milestone, blockage, and shipment-readiness views instead of creating a separate landing area
|
||||
- Continue expanding the new manufacturing widgets into shortage, routing, and bottleneck views instead of creating a separate landing area
|
||||
- Treat dashboard modules as upgradeable blocks that can be reordered or expanded without disturbing the shell
|
||||
### Dashboard
|
||||
|
||||
## Planned feature phases
|
||||
- Expand `Dashboard` by modular panels rather than redesigning it into a different shell
|
||||
- Add richer KPI widgets, alerts, recent-activity queues, and exception reporting
|
||||
- Add deeper project, manufacturing, purchasing, shipping, and audit/system-health widgets
|
||||
|
||||
### Phase 1: CRM and master data hardening
|
||||
### CRM and master data
|
||||
|
||||
- Better seed/bootstrap strategy for non-development environments
|
||||
- Additional CRM account-role depth if later sales/purchasing workflows need it
|
||||
- More derived CRM rollups once quotes, orders, and purchasing documents exist
|
||||
|
||||
QOL subfeatures:
|
||||
|
||||
- More derived CRM rollups once downstream quote/order/purchasing/shipping data grows further
|
||||
- Saved CRM filters and quick views
|
||||
- Better hierarchy navigation between reseller parents and child accounts
|
||||
- One-click contact actions for email and phone workflows
|
||||
- Duplicate-account detection and merge workflow
|
||||
- Cleaner attachment previews and richer record timelines
|
||||
- More compact table controls for heavy CRM data-entry users
|
||||
- CRM document rollups and broader account-role depth that were deferred until downstream modules matured
|
||||
|
||||
### Phase 2: Inventory and manufacturing core
|
||||
### Inventory
|
||||
|
||||
- Item master and SKU structure foundation
|
||||
- Warehouse and stock location foundation
|
||||
- Inventory transactions and on-hand tracking foundation
|
||||
- Bills of materials and custom assemblies foundation
|
||||
- File attachments for BOM drawings and manufacturing support docs foundation
|
||||
|
||||
QOL subfeatures:
|
||||
|
||||
- Item master enrichment: categories, alternate part numbers, revisions, preferred vendor data, and reorder settings
|
||||
- Stock transfers between warehouses and locations
|
||||
- Reservation and allocation visibility against demand
|
||||
- Faster SKU search and keyboard-heavy item/BOM entry flows refinement
|
||||
- Better warehouse dashboards for on-hand, shortages, and recent movement
|
||||
- Item master enrichment: categories, alternate part numbers, revisions, reorder settings, and broader sourcing metadata
|
||||
- Faster keyboard-heavy item/BOM entry refinement beyond the current searchable pickers
|
||||
- Better warehouse dashboards for on-hand, shortages, reservations, and recent movement
|
||||
- BOM revision support and clearer where-used visibility
|
||||
- Bulk item import/export and mass-update utilities
|
||||
|
||||
### Phase 3: Sales and purchasing documents
|
||||
|
||||
- Quotes, sales orders, and purchase orders
|
||||
- Reusable line-item and totals model
|
||||
- Purchase receiving flow tied to purchase-order lines and inventory receipts foundation
|
||||
- Document states, approvals, and revision history
|
||||
- Branded PDF templates rendered through Puppeteer
|
||||
- Attachments for vendor invoices and supporting documents
|
||||
|
||||
Foundation slice shipped:
|
||||
|
||||
- Sales approval stamps and automatic revision history on quotes and sales orders
|
||||
- Purchase-order supporting documents through the shared attachment pipeline
|
||||
- Vendor-detail purchasing visibility for recent purchase-order activity
|
||||
|
||||
QOL subfeatures:
|
||||
### Sales and purchasing
|
||||
|
||||
- Vendor exception handling for acknowledgements, invoice matching, receipt discrepancies, and related inbound follow-up
|
||||
- Deeper carrier/commercial defaults where they improve order-entry speed
|
||||
- Revision comparison UX for changed customer-facing and purchasing documents
|
||||
- Line duplication, drag ordering, and keyboard-first line editing
|
||||
- Saved customer defaults for tax, freight, and commercial terms
|
||||
- Inline stock visibility while building quotes and orders
|
||||
- Restrict purchase-order item entry to purchasable inventory only
|
||||
- Richer dashboard widgets for recent quotes, open orders, purchasing queues, and shipping exceptions
|
||||
- Better totals breakdown visibility on list pages and detail pages
|
||||
- Revision comparison view for changed customer-facing documents
|
||||
- Faster document cloning and quote-to-order style conversions across document types
|
||||
|
||||
### Phase 4: Shipping and logistics
|
||||
### Shipping and logistics
|
||||
|
||||
- Shipment records linked to sales orders
|
||||
- Bills of lading, packing slips, and shipping BOM PDFs
|
||||
- Carrier, package, and tracking data
|
||||
- Outbound shipment status workflow
|
||||
- Scanned logistics-document attachment handling
|
||||
|
||||
QOL subfeatures:
|
||||
|
||||
- Printer-friendly reprint and history actions for logistics documents
|
||||
- Partial shipment workflow and split-shipment visibility
|
||||
- Better tracking-link UX and carrier-specific shortcuts
|
||||
- Packing verification and ship-confirm checkpoints
|
||||
- Shipment search by order, tracking, customer, and carrier from one screen
|
||||
- Reprint and history actions for generated logistics PDFs
|
||||
- Printer-friendly reprint/history actions for logistics documents
|
||||
|
||||
### Phase 5: Projects and program management
|
||||
|
||||
Foundation slice shipped:
|
||||
|
||||
- Project records with customer linkage, status, owner, priority, due dates, and notes
|
||||
- Project-to-quote, sales-order, and shipment linkage for delivery context
|
||||
- Project attachments through the shared file pipeline
|
||||
- Project list/detail/create/edit flows and dashboard visibility
|
||||
### Projects and program management
|
||||
|
||||
- Project document hub for drawings, support files, correspondence, and revision references
|
||||
- Milestones, checkpoints, and non-manufacturing work packages for long-running execution tracking
|
||||
- Project-level commercial, material, schedule, and delivery rollups
|
||||
- Cross-functional visibility for engineering, purchasing, manufacturing, shipping, and customer communication
|
||||
|
||||
Module interactions:
|
||||
|
||||
- CRM: projects link to customer accounts, reseller-owned end customers, contacts, and account notes
|
||||
- Sales: quotes and sales orders can spawn or attach to projects; project status should reflect commercial state where relevant
|
||||
- Inventory: projects reference item/BOM scope, expose shortage/reservation pressure, and later roll up material readiness
|
||||
- Purchasing: projects surface buyout demand and vendor receipts tied to project material needs
|
||||
- Shipping: shipments should be visible from the project record when a project drives deliverables
|
||||
- Dashboard: projects add live widgets for active programs, overdue milestones, shortages, and blocked delivery
|
||||
- Manufacturing: manufacturing orders and shop execution should link back to projects, but remain their own subsystem
|
||||
- Gantt/planning: project milestones and execution dates should feed planning views without collapsing projects into scheduling alone
|
||||
|
||||
QOL subfeatures:
|
||||
|
||||
- Project templates for repeatable build types
|
||||
- Project-specific attachment bundles and revision snapshots
|
||||
- One-screen project cockpit with commercial, material, schedule, and shipping summary
|
||||
@@ -197,34 +87,13 @@ QOL subfeatures:
|
||||
- Project filtering by customer, owner, status, due date, and risk
|
||||
- Project activity timeline and audit-friendly milestone history
|
||||
|
||||
### Phase 6: Manufacturing execution
|
||||
### Manufacturing execution
|
||||
|
||||
Foundation slice shipped:
|
||||
|
||||
- Work orders tied to manufactured or assembly items, with optional project linkage
|
||||
- BOM-based material requirement visibility from the work-order record
|
||||
- Material issue posting that creates real inventory issue transactions
|
||||
- Production completion posting that creates finished-goods receipt transactions
|
||||
- Work-order list/detail/create/edit flows, attachments, and dashboard visibility
|
||||
|
||||
- Work orders tied to projects, sales demand, or internal build demand
|
||||
- Routing/work-center structure for manufacturing steps and handoffs
|
||||
- Material issue, consumption, completion, and WIP tracking
|
||||
- Work orders tied more explicitly to sales demand or internal build demand where appropriate
|
||||
- Routing/work-center structure for manufacturing steps and handoffs beyond the current station templates
|
||||
- Material consumption depth, WIP tracking, and execution traceability
|
||||
- Labor and machine-time capture for production execution
|
||||
- Manufacturing status workflow from release through completion
|
||||
- Manufacturing rollups for open work, blockers, shortages, and throughput
|
||||
|
||||
Module interactions:
|
||||
|
||||
- Projects: manufacturing orders can be attached to projects, but projects remain the higher-level long-running record
|
||||
- Inventory: manufacturing consumes components and produces finished/semi-finished stock
|
||||
- Purchasing: shortages and buyout demand should be visible from manufacturing execution
|
||||
- Shipping: completed manufacturing should feed shipment readiness, but shipping remains separate
|
||||
- Dashboard: manufacturing adds live queues for open jobs, blocked work, overdue orders, and completion throughput
|
||||
- Planning: manufacturing orders and routings become a major input into capacity and gantt scheduling
|
||||
|
||||
QOL subfeatures:
|
||||
|
||||
- Traveler/job packet output
|
||||
- Partial completions and split-order execution visibility
|
||||
- Better shortage and substitute-part handling
|
||||
@@ -232,22 +101,12 @@ QOL subfeatures:
|
||||
- Rework / hold / scrap tracking
|
||||
- Work-center dashboards and operator-focused queues
|
||||
|
||||
### Phase 7: Planning and scheduling
|
||||
### Planning and scheduling
|
||||
|
||||
Foundation slice shipped:
|
||||
|
||||
- Live gantt schedule backed by active projects and open manufacturing work orders
|
||||
- Project due-date milestones, manufacturing sequencing links, and standalone work-queue visibility
|
||||
- Planning exception queue for overdue or at-risk project/manufacturing schedule items
|
||||
|
||||
- Live project-backed SVAR gantt timelines
|
||||
- Task dependencies, milestones, and progress updates
|
||||
- Manufacturing calendar views and bottleneck visibility
|
||||
- Labor and machine scheduling support
|
||||
- Theme-compliant gantt customization for light/dark mode
|
||||
|
||||
QOL subfeatures:
|
||||
|
||||
- Collapsible schedule groupings and saved planner views
|
||||
- Drag-and-drop rescheduling improvements
|
||||
- Critical-path and overdue highlighting
|
||||
@@ -255,68 +114,20 @@ QOL subfeatures:
|
||||
- Better mobile and tablet behavior for shop-floor lookups
|
||||
- Faster filtering by project, customer, work center, and status
|
||||
|
||||
### Phase 8: Demand planning and supply generation
|
||||
### Demand planning and supply generation
|
||||
|
||||
Foundation slice shipped:
|
||||
|
||||
- Sales-order demand planning from approved or active demand records
|
||||
- Multi-level BOM explosion from sales-order lines through manufactured and assembly children
|
||||
- Netting against available stock, active reservations, open work orders, and open purchase orders
|
||||
- Build and buy recommendations surfaced directly from the sales-order workflow
|
||||
- Prefilled work-order and purchase-order draft generation launched from demand-planning recommendations
|
||||
- Shared shortage and readiness rollups surfaced across dashboard, planning, project, purchasing, and manufacturing views
|
||||
- Preferred-vendor sourcing on inventory items for buy-side planning defaults
|
||||
- Pegged work-order and purchase-order supply links back to originating sales demand
|
||||
- Planning recommendations now reduce against already-linked draft/open supply to avoid duplicate WO/PO generation
|
||||
|
||||
- Shared MRP demand engine across sales, inventory, purchasing, manufacturing, projects, and planning
|
||||
- Planned work-order and purchase-order recommendation generation
|
||||
- Coverage, shortage, and lateness rollups from customer demand down through supply layers
|
||||
- Cross-module shortage visibility on sales orders, projects, work orders, purchasing, and dashboard widgets
|
||||
|
||||
QOL subfeatures:
|
||||
|
||||
- One-click conversion of planning recommendations into work orders and purchase orders
|
||||
- Deeper planner drilldowns from demand source to buy/build action without re-keying data
|
||||
- Better shortage and substitute-part guidance during planning review
|
||||
- Saved planning views by customer, project, item family, and shortage state
|
||||
- Planner-focused drilldowns from demand source to buy/build action without re-keying data
|
||||
- Time-phased supply recommendations with vendor lead times and build timing
|
||||
|
||||
### Phase 9: Security, audit, and operations maturity
|
||||
### Security, audit, and operations maturity
|
||||
|
||||
Foundation slice shipped:
|
||||
|
||||
- Audit trail coverage across core write flows for settings, inventory, sales, purchasing, projects, and manufacturing
|
||||
- Admin diagnostics screen for runtime footprint, storage visibility, key record counts, and recent audit activity
|
||||
- Expanded role-management UI with account creation, activation, role assignment, and permission administration
|
||||
- Persisted auth-session tracking with admin visibility into active, expired, and revoked sign-ins
|
||||
- Server-side logout and admin session revocation for JWT-backed access
|
||||
- Shared destructive-action confirmation and recovery messaging for admin, sales, purchasing, shipping, inventory, manufacturing, and attachment workflows
|
||||
- CRM customer/vendor changes and shipping mutations covered by the shared audit trail
|
||||
- Startup validation during server boot with checks for storage paths, writable directories, database connectivity, client bundle readiness, Chromium availability, and risky production defaults
|
||||
- Backup/restore guidance, support-bundle exports, and support-log viewing surfaced through the admin diagnostics workflow
|
||||
|
||||
- Expanded role management UI
|
||||
- Permission assignment administration
|
||||
- Audit trail coverage across critical records
|
||||
- Backup/restore workflow documentation and scripts
|
||||
- Health checks, startup diagnostics, and production readiness cleanup
|
||||
|
||||
QOL subfeatures:
|
||||
|
||||
- Admin diagnostics screen for permissions, migrations, storage, and PDF health
|
||||
- Better session filtering, review history, and unusual-access cues for operational admins
|
||||
- Extend destructive-action safety coverage into remaining project and form-edit removal workflows
|
||||
- More explicit environment validation on startup
|
||||
- Support-log filtering, retention controls, and broader support-package polish
|
||||
- Backup verification checklist and restore drill guidance
|
||||
|
||||
## Revisit / Deferred Items
|
||||
|
||||
- Local Windows Prisma migration reliability still needs a cleaner documented workflow or tooling wrapper
|
||||
- CRM document rollups and broader account-role depth were deferred until more downstream modules exist
|
||||
- Some generated document and workflow screens still need additional polish for dense, keyboard-efficient operational use
|
||||
- Dashboard cards now use live data, but richer recent-activity widgets and exception queues are still deferred
|
||||
- Admin diagnostics depth for permissions, migrations, storage, and PDF health
|
||||
- Longer-term session history and audit depth beyond the current review filtering and retention cleanup
|
||||
- More explicit environment validation on startup
|
||||
- Backup verification and restore-drill guidance should keep expanding as the system grows
|
||||
|
||||
## Cross-cutting improvements
|
||||
|
||||
@@ -327,7 +138,7 @@ QOL subfeatures:
|
||||
- Consistent document-template system shared by sales, purchasing, and shipping
|
||||
- Clear upgrade path for future module additions without refactoring the app shell
|
||||
|
||||
## Near-term priority order
|
||||
## Revisit / Deferred Items
|
||||
|
||||
1. Better session filtering, review history, and unusual-access cues for operational admins
|
||||
2. Extend destructive-action safety coverage into remaining project and form-edit removal workflows
|
||||
- Local Windows Prisma migration reliability still needs a cleaner documented workflow or tooling wrapper
|
||||
- Some generated document and workflow screens still need additional polish for dense, keyboard-efficient operational use
|
||||
|
||||
Reference in New Issue
Block a user