Repository navigation
Learning B2 Routes and Operation Level BOM
A bill of materials (BOM) identifies required materials; an operation-level BOM identifies where they are consumed. Teaching product P goes through cutting and assembly. Each unit consumes one blank in cutting and two fasteners in assembly. Planning ten units requires knowing that the 20 fasteners are needed at assembly, because their availability can affect when that operation starts.
| Business object | Teaching example | Relationship |
|---|---|---|
| Product | P | product |
| Route | R-P | process_route.product links to P |
| Operations | Cutting 10, assembly 20 | process.route and process.seqno |
| Resources | Cutter WC-C, assembly station WC-A | process_adaptor links operations and work centers |
| Materials | Blank M-1, fastener M-2 | ingredient links an operation to material |
Sequence values 10 and 20 only specify order. Here, one execution of an operation produces one unit. For operations producing several units per execution, record output per execution and the basis of material consumption separately.
Suppose ten blanks are available today and 20 fasteners arrive tomorrow. The business may permit cutting today and assembly tomorrow. Whether intermediate inventory, separated operations and cross-period work can be represented depends on the selected model and enabled constraints. Operation-level data provides the place to examine those questions.
Attaching all materials only to the finished product can hide early-operation requirements. Requiring everything at the first operation can prevent work that could otherwise start. Use the real consumption point.
- Confirm P's route and any candidate routes.
- Check operation order, outputs and eligible work centers.
- Trace each ingredient record to a specific operation and material.
- Check the basis of consumption, including processing cycles or output units.
- Align material availability with the planning time axis.
This exercise assumes each finished unit passes through each operation once, without losses or co-products. Ten units therefore require ten blanks and 20 fasteners. For multi-output, scrap or co-product cases, first confirm that the selected model can represent the process. Then calculate from output per execution and material consumption. Output per execution is distinct from the proportion of good units produced.
Changing fastener consumption from two to three raises the teaching requirement to 30. Update the confirmed operation-material relationship, check availability, then rerun. A larger delivery weight cannot supply the missing ten fasteners.
A route or alternative-resource change also needs an object-level review. Another route may change materials, output per cycle, and processing duration. For continuous processing, also check output per unit time and its units. Replacing a work-center label alone is insufficient.
Add a surface-treatment operation consuming 0.2 liters of fluid per unit. Draw the route, resource and material relationships. Under the no-loss assumption, ten units require two liters.
Explain where the fluid is consumed, its unit, its availability and the eligible resources. This establishes structure and hand calculations. Actual planning results require execution with the corresponding constraints enabled.
Standardized Data Interface · Data Objects and Fields · Data Readiness and Validation · ERP and MES Data Mapping
Worksheets: Worksheet: Scenario and Decision Task
Topic B · Previous: From Business Tables to Computable Objects · Next: Align Time, Capacity and Material Availability
Product Home | DecisioWorks v1.4.0 | English / 中文
- What Is DecisioWorks / DecisioWorks 是什么
- Scenarios and Pain Points / 适用场景与痛点
- Quick Start / 快速开始
- Documentation Map / 文档地图
- Research and Commercial Editions / 研究版与商业版
- Whitepapers / 白皮书
-
Learning Center / 学习中心: 8 topics / 8 个专题
- Design Principles and Differentiation / 设计原则与差异化
- Architecture Overview / 总体架构
- Component Responsibilities / 组件职责
- Standard Actions and Orchestration / 标准动作与能力编排
- Objectives and Rule Control / 目标与规则控制
- Controlled Solving and Engine Adapters / 受控求解与模型适配
- Results, Evidence, and Feedback / 结果、证据与反馈
- Developer Guide Index / 开发手册索引
- Data Objects and Fields / 数据对象与字段
- Actions, Recipes, and Execution / 动作、配方与执行
- Runtime Status, Errors, and Limits / 运行状态、错误与限制