# Modelling Scenario: Resource Running Modes and Durable BOM

**URL:** <https://community.criticalmanufacturing.com/t/modelling-scenario-resource-running-modes-and-durable-bom/839>\
**Category:** Modelling & Configuration\
**Tags:** semiconductor, v11.3\
**Created:** [September 9, 2026, 8:38am UTC](https://community.criticalmanufacturing.com/t/modelling-scenario-resource-running-modes-and-durable-bom/839 "2026-09-09T08:38:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Filipe\_Serra](https://avatars.discourse-cdn.com/v4/letter/f/da6949/32.png) [@Filipe\_Serra](https://community.criticalmanufacturing.com/u/Filipe_Serra)\
**Post date:** [September 9, 2026, 8:38am UTC](https://community.criticalmanufacturing.com/t/modelling-scenario-resource-running-modes-and-durable-bom/839/1 "2026-09-09T08:38:58Z")

</div>

Hi All,

I’m looking for your help in the following Use Case, where we aim at using Material Durables and Resource RunningModes together to tackle a scenario where MES needs to control the way of the resource is operating with the correct durables.  
So, I have a resource operating in two different steps that can do 2 different processes. Each process has a specific running mode. However, there is a 3rd running mode that means that the resource can do both processes simultaneously (on different materials).

Each running mode ends up requiring a different set of durables.

Scenario details:

- Resource using Running Mode:
  - Running Mode A - used when the equipment is performing a specific function only, like Load - StepName: LOADSTEP
  - Running Mode B - Unload (for example) - StepName: UNLOADSTEP
  - Running Mode C - Mixed - when the resource can simultaneously be loading and unloading containers (different materials)

- Step configurations:
  - 
    - StepName: LOADSTEP -

    - Can use Running Mode Load - if only doing Load

    - Can use Running Mode Exchange if also processing material in an Unload step

  - 
    - StepName: UNLOADSTEP:

    - Can use Running Mode Unload - if only doing Unload

    - Can use Running Mode Exchange, if also processing material in a Load step

- Important Notes:
  - Each Running mode, because of the specific hardware used, requires a specific Durable BOM
    - Load Step has a Durable Load BOM (if doing only Load)
    - Unload Step has a Durable Unload BOM (if doing only Unload)
    - How about the Exchange mode?
      - EXCHANGE Running Mode requires part of the LoadBOM and part of the UnloadBOM
      - Any ideas on how to model this scenario, and control which BOM is being used for a given product? Is Running Mode even advised here?

Let me know if you have any suggestion or ping me and we can talk about this!

---

<div class="post-metadata">

**Author:** ![Miguel\_Torres](https://avatars.discourse-cdn.com/v4/letter/m/a9adbd/32.png) [@Miguel\_Torres](https://community.criticalmanufacturing.com/u/Miguel_Torres)\
**Post date:** [September 9, 2026, 3:13pm UTC](https://community.criticalmanufacturing.com/t/modelling-scenario-resource-running-modes-and-durable-bom/839/2 "2026-09-09T15:13:26Z")

</div>

Hi,

**MaterialDurablesContext Smart Table** does not allow you to define **BOM** s per **Resource Running Mode**.

However, it does allow you to define a **BOM** using a **Recipe** as key.

So my suggestion to tackle this using pure modelling would be to tie a **Recipe** to each specific **Running Mode** in **Recipe Context Smart Table** , and then configure **MaterialDurablesContext** with the correct combinations such as:

- **Step:** Load, **Recipe:** Load, **BOM:** LoadDurablesBOM
- **Step** : Load, **Recipe** : Exchange, **BOM** : ExchangeDurablesBOM

In theory, you could have a generic **BOM** for the Load **Step** , and then a specific one for when **Recipe** is Exchange, using the ability of defining broader and more specific settings for each.

Hope this helps!

Best regards,  
Miguel Torres

---

<div class="post-metadata">

**Author:** ![system](https://yyz2.discourse-cdn.com/flex050/user_avatar/community.criticalmanufacturing.com/system/32/23_2.png) [@system](https://community.criticalmanufacturing.com/u/system)\
**Post date:** [September 18, 2026, 1:02pm UTC](https://community.criticalmanufacturing.com/t/modelling-scenario-resource-running-modes-and-durable-bom/839/3 "2026-09-18T13:02:16Z")

</div>

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![Filipe\_Serra](https://avatars.discourse-cdn.com/v4/letter/f/da6949/32.png) [@Filipe\_Serra](https://community.criticalmanufacturing.com/u/Filipe_Serra)\
**Post date:** [September 18, 2026, 1:33pm UTC](https://community.criticalmanufacturing.com/t/modelling-scenario-resource-running-modes-and-durable-bom/839/4 "2026-09-18T13:33:10Z")

</div>

Thanks Miguel,

That indeed helps to follow an OoB approach. Will keep this in mind when discussing this topic further. Small caveat, using Recipe/recipeContext may not be feasible in this specific project context.