Maak uittrekstaten per productieweek

Data requirements

# Bill of Material **The production planning and reporting environment for DHME modular building projects.** Bill of Material (BOM) is the downstream reporting and planning app in the DHME suite. It consumes the definitions and generated records produced by Manual Import and transforms them into actionable views: aggregated material lists, assembly schedules, weekly production planning, and printable QR stickers. It also supports submitting formal planning requests to the assembly team. --- ## What it does Bill of Material reads from the DHME datasets (modules, elements, objects) and provides: - Aggregated **element and object quantities** filtered by any combination of module types, houses, phases, and categories - A **weekly production planning view** showing which modules are assembled on which days, including cumulative hours and assembly line assignments - An **assembly schedule** with drag-and-drop sequence reordering and inline workload editing - **CSV exports** in five different formats for use in external tools - **QR sticker PDFs** for physical tracking on the production floor - A **planning request flow** to formally submit assembly planning parameters to the project's assembly task --- ## Views ### Elements view Four sub-tabs covering different perspectives on the element data: **Bill of Materials tab** Aggregates element types across all filtered modules, showing total quantities broken down by week. Provides a clear overview of what needs to be produced and when. **Weekly Planning tab** A day-by-day schedule showing which modules are being worked on each day, cumulative work hours, and which assembly line each module is assigned to (when multi-line assembly is configured). Includes ramp-up period indicators. **Module Content tab** A matrix cross-referencing modules against element types — useful for verifying which modules produce which elements. **QR Codes tab** An interface for selecting modules or element types and generating a printable A4 PDF sheet of QR stickers. Each sticker encodes the project info, item ID, and type. Supports bulk selection, search, and multiple copies per sticker. ### Objects view Aggregates object types (materials, components) across all filtered data. Shows dimensions, NLSFB classification, and steel quality. Each row expands to show which element types contain that object. ### Assembly view A module-level schedule showing assembly sequence, workload hours, and phase. Supports: - **Drag-and-drop reordering** of modules to change their assembly sequence - **Inline workload editing** with +/− buttons or direct input --- ## Key features ### Workload-based scheduling engine The core of the planning system. Given a start date and configuration, the engine automatically schedules each module based on its workload (hours) and sequence: - Assigns modules to time slots respecting working hours per day and working days per week - Supports **multi-line assembly**: modules are distributed across N parallel assembly lines, each assigned to the earliest available line - Supports a **ramp-up period**: limits how many new modules can start per week during the first N weeks, simulating production line warm-up - Skips weekends automatically - Computes a precise start date, end date, and assembly line number for every module ### Planning request system Formally request assembly planning through the app by configuring: - **Assembly hall** and hall configuration - **Start date** and start hour - **Work hours per day** and work days per week - **Number of assembly lines** - **Ramp-up settings** (weeks and modules per week during ramp-up) Before submitting, a confirmation dialog shows a full summary of all parameters. After submission, the request is tracked through statuses: Not Requested → Requested → Planned / Rejected. All settings are persisted in the assembly phase task's custom fields. ### Multi-preset filter system Filters work across five dimensions simultaneously: - Module type - House number - Build number - Element category - Object category Multiple filter **presets** can be saved per view and combined at runtime. Within a category, active values are unioned (OR); across categories, filters are intersected (AND). Presets are stored in the database and shared across the project team. ### CSV export (five formats) All views support export to CSV for use in external tools: | Export | Contents | |---|---| | **Bill of Materials** | Element types with weekly quantities | | **Objects report** | Objects with dimensions, NLSFB, and steel quality | | **Assembly schedule** | Module sequence, workload, and phase | | **Weekly planning** | Day-by-day module schedule with cumulative hours and assembly line info | | **Module content matrix** | Module-element cross-reference | ### QR sticker PDF generation Generate printable A4 PDF sheets with QR codes for physical tracking: - Select any subset of modules or element types - QR codes encode project number, item ID, and type - Supports multiple copies per sticker - Search and bulk-select controls for efficient selection ### Detail panel with navigation history Clicking any row opens a context-aware detail panel on the right side: - Module details including computed scheduled start and end times, and assembly line - Element type breakdown showing which modules produce it - Object type properties and usage across elements - A back button navigates through the full history of opened detail items within the session ### Generation status banner If a generation is running in Manual Import (or was recently completed), a banner at the top of the app shows the current status, progress, and any errors. This keeps the BOM team informed about whether the data they are viewing is up to date. ### Assembly view — sequence reorder and workload editing - Drag rows in the assembly table to change the module assembly sequence; the new sequence is saved immediately - Edit assembly workload hours inline with +/− buttons or direct input; changes update the scheduling engine output in real time ### Permission-based access Read access to each DHME table is required to display data. Write access to the modules table is required for sequence reordering and workload editing. Project admins bypass all checks. The app shows a clear no-permission state when access is denied. --- ## Data flow ``` Manual Import (Modules + Elements + Objects) ↓ Bill of Material ↓ ┌───────────────┼───────────────┐ ↓ ↓ ↓ CSV exports QR sticker PDFs Planning request (assembly task) ``` --- ## Supported languages English, Dutch, German --- ## Technical notes - Built with Vue 3, TypeScript, Vuetify 3, Pinia, and UnoCSS - State is managed via a global singleton store pattern (`createGlobalState`) - Scheduling engine lives in `stores/helpers/dateCalculations.ts` — pure, deterministic, tested independently - Real-time generation status updates via WebSocket signals (`jobProgress`) - API calls go through `@antcde/connect-ts` (table CRUD, task API) and `@collaborall/dhme-services` (generation API) - QR PDF generation is entirely client-side using canvas primitives - Filter preset storage uses a dedicated database table (`CFFA_DHME_BOM_FILTER_PRESETS`) - Planning settings are persisted in `CFFA_DHME_BOM_PLANNING_SETTINGS`