# Glossary — BMW Supplier Development Terms > Audience: vendor engineers (Adesso) and new team members without prior BMW Supplier > Development context. Explains domain-specific abbreviations and German-language > concepts used throughout the codebase, database schema, and documentation. --- ## LSC — Lean Shop-floor Cycle The primary measurement workflow in SupplierDev. An LSC visit is a structured on-site engagement at a supplier manufacturing plant where BMW engineers measure cycle times at individual workstations (stations), record shift outputs, and capture improvement actions. The LSC module (`MO-LSC/`, `lib/lsc-workshop/`) covers the digital tooling for this process: stopwatch measurements, shift tracking, OEE recording, and workshop action management. ## KAP / Kapazitäts-Workshop "Kapazitätsanalyse-Prozess" — a capacity analysis process. A KAP-Workshop is a structured event at a supplier facility to analyse production capacity against BMW demand. It is one of the selectable `Auftragstypen` (order types) in the project creation form. Results feed into the Yamazumi chart and bottleneck analysis in the management dashboard. ## KIFAG "KI-gestützte Fabrik-Analyse und -Gesamtbewertung" — the AI-assisted factory analysis and overall assessment methodology. In the codebase, a KIFAG project type activates the `Fabrikanalyse` tab on the project detail page (`app/project/[id]/analyse/`), which links to a QAF-based assessment workflow covering the supplier's entire manufacturing system rather than individual process steps. ## OEE — Overall Equipment Effectiveness A standard manufacturing KPI expressed as a percentage: OEE = Availability × Performance × Quality. In SupplierDev, OEE values are recorded per shift (`MO-OEE/oee-phase1.sql`, `lib/oee/`). The OEE module stores loss categories (`oee_loss_categories`) and provides a Verlustanalyse (loss analysis) view to identify the dominant source of downtime or quality loss at a station or line. ## MO-23 — Planning Module Internal module designation for "Einsatzplanung" (consultant deployment planning). Contains the database tables `consultants`, `appointment_types`, `planning_projects`, and `assignments` (`MO-23/planning-tables.sql`). These tables model which BMW consultant is assigned to which supplier visit on which day. The UI lives in `app/kalender/` (calendar view) and uses the planning board to drag-and-drop assignments. ## MO-24 — Project Form / Assessment Phase 1 Internal module designation covering the project creation form extensions and the first phase of the supplier assessment module. `MO-24/project-form-phase1.sql` adds `project_responsibilities` and `project_statuses` lookup tables. `MO-24/assessment-phase1.sql` introduces the `assessment_categories` and `assessment_questions` tables used by the QAF module. ## MO-25 — Repository / Document Module Internal module designation for the document repository ("Dokumentenablage"). Covers `document_metadata`, `document_departments`, `document_suppliers`, and related link tables (`MO-25/repository-phase-arch.sql`). The UI is in `app/repository/`. Suppliers can attach QAF documents, photos, and measurement sheets; BMW engineers can compare current vs. reference QAF documents side by side. ## MO-26 — Wertstrom / Value-Stream-Map Module Internal module designation for the Wertstrom-Karte (value-stream map) feature (`MO-26/wertstrom-schema.sql`). A Wertstrom is a visual representation of the material and information flow through a production system, from raw material to finished goods. The VSM editor in SupplierDev allows engineers to draw and annotate the map digitally during a plant visit. ## MO-27 — Cross-Module Assignments Link Internal module designation for the `assignments.origin_project_id` foreign key that links planning assignments to their originating project (`MO-27/assignments-origin-project.sql`). This enables bidirectional traceability: from a project you can see which consultants were assigned, and from a planning-board assignment you can navigate to the project. ## Einsatzplanung German for "deployment planning" or "resource scheduling". In SupplierDev it refers specifically to the calendar-based module (`app/kalender/`, `MO-23/`) where BMW team leads plan which engineer visits which supplier on which date. The planning board uses a drag-and-drop interface built on `@dnd-kit`. Offline capability for this module is architecturally designed but not yet fully wired (see `docs/TECHNICAL_DEBT.md` O1). ## Auftragstyp German for "order type" or "project type". Each SupplierDev project has one or more Auftragstypen that determine which feature tabs are visible and which assessment templates apply. Standard values include `lsc_workshop`, `kap_workshop`, `invest_workshop`, `fabrikanalyse`, and `lieferantenbefaehigung`. The lookup table is `master_data_types` / `master_data_values`; project assignments are stored in `project_type_assignments`. ## QAF — Qualitäts-Anforderungs-Formular "Quality Requirements Form" — a BMW-internal checklist document used to assess whether a supplier's manufacturing process meets BMW quality standards. In SupplierDev, QAF documents can be uploaded per project, versioned, and compared side-by-side (current vs. reference). The QAF module (`lib/qaf/`, `app/project/[id]/qaf/`) supports PDF upload, status tracking, and comment capture. ## Wertstrom See "MO-26 — Wertstrom / Value-Stream-Map Module" above. The term literally means "value stream" in German and refers to the complete sequence of activities (both value-adding and non-value-adding) required to deliver a product from raw material to customer. Synonymous with VSM (Value Stream Map). ## Takt / Kundentakt "Takt" is German for beat or rhythm. In lean manufacturing, Takt time (Kundentakt = customer takt) is the rate at which products must be completed to meet customer demand. It is calculated as: Takt = Available production time ÷ Customer demand per period. In SupplierDev, the customer takt is entered per project (`projects.customer_takt_time_sec`) and used as the reference line in Yamazumi diagrams to visualise which stations exceed takt (bottlenecks). ## Bottleneck / Engpass The workstation or process step whose cycle time exceeds the customer Takt time, thereby limiting the throughput of the entire production line. SupplierDev automatically identifies the bottleneck station in the Yamazumi chart based on the recorded cycle measurements. Engineers use this information to prioritise improvement actions. ## Fabrikanalyse / Assessment A factory-wide assessment (as opposed to a single-process LSC measurement). The assessment module (`lib/assessment/`, `app/lsc-workshop/[id]/assessment/`) presents a structured questionnaire across assessment categories (sourced from `assessment_categories` and `assessment_questions`). Responses are scored and aggregated into a radar chart for the management dashboard. The KIFAG project type triggers the full factory assessment scope.