How to Include Sub-Assemblies in the Schedule in EDGEBIC

To include sub-assemblies in the schedule in EDGEBIC, open Settings, go to the Schedule tab, and tick "Include sub-assemblies in schedule" under the Sub-Assemblies group, then click Save. When the box is on, multi-level routings explode and schedule with their parent job. When it is off, only the top-level routing is planned. The setting is on by default.

Many products in EDGEBIC by User Solutions are built in levels: a finished item made from fabricated sub-assemblies, each with its own routing. This policy controls whether the scheduler reaches down into those lower levels and plans them alongside the parent, or stops at the top and plans only the final routing. It is a single site-wide switch, and it changes what gets planned for every multi-level product on the next run.

Before You Start

• You have at least one multi-level product. The setting has no visible effect on a single-level routing. If a sub-assembly is part of a routing, review how to add a sub-assembly to a routing.
• You can reach the Settings tab. The Settings navigation tab is permission controlled.
• You know how your lower levels are sourced. Turn the policy off only if sub-assemblies are planned or bought outside EDGEBIC.
• You can run the scheduler. The change applies on the next Drive Schedule run.

Step 1: Open the Schedule Policy Screen

Open the Settings tab, then select the Schedule tab. This is the site-wide scheduling policy screen, read fresh by the engine on every run.

Step 2: Find the Sub-Assemblies Group

Scroll to the Sub-Assemblies group. It holds a single checkbox.

Step 3: Choose On or Off

Leave it on if your shop fabricates every level of a product and you want the whole tree planned, so lower-level capacity and lead time feed the parent's dates. Turn it off only when the sub-assemblies are handled by another system and you want the plan to reflect final assembly alone.

Step 4: Save and Re-Run

Click Save. The status line confirms it. Then run Drive Schedule: the new policy is read on that run.

What Changes When You Save

How to Check It Worked

1. Pick a product whose routing you know contains a sub-assembly.
2. Run Drive Schedule for a job on that product.
3. Open the job in Job View. With the policy on, the sub-assembly steps appear in the schedule, sequenced ahead of the parent's final steps. With it off, only the top-level routing steps are present.
4. Cross-check on the Work Center Progress report: the sub-assembly steps show as scheduled operations when the policy is on, and are absent when it is off.

Common Mistakes

Blaming a missing routing when the policy is off. If sub-assembly steps vanish from every multi-level job at once, the culprit is usually this global switch, not the individual routing.

Turning it off to drop one purchased sub-assembly. The switch is all or nothing across the whole site. To exclude a single bought item, model that item so it carries no capacity-consuming steps rather than disabling sub-assembly scheduling for everything.

Editing and not re-running. Policy is read at the next scheduling run. Save, then run Drive Schedule.

Assuming it changes stored data. The setting only changes what the next run plans. It writes nothing to your routings.

Next Steps

This policy decides how deep the scheduler reaches into a multi-level product. Set the tree up correctly first with how to add a sub-assembly to a routing, then confirm the whole plan with a fresh run using how to reschedule everything from scratch. For the wider picture of what the engine plans, read what is production scheduling. More single-task recipes live in the EDGEBIC how-to hub, and the platform overview is at /edgebic.