BOR status buckets are the Products dashboard's stable three-value classification of every product's routing state: Has BOR, No BOR, or Multiple BORs (Legacy). In EDGEBIC by User Solutions, they answer one question at a glance: which products can actually be scheduled? A product with a bill of routing has a recipe the engine can plan against, one with no routing cannot be scheduled at all, and one carrying several routings is flagged for cleanup. EDGEBIC shows the split as a pie so the gap is impossible to miss.
This entry is part of the EDGEBIC glossary series. For the broader vocabulary, see the manufacturing glossary. BOR status buckets are one of several dashboard classifications; a related trust indicator is the data quality chip, which marks how fresh a number is rather than whether a product can be scheduled.
How BOR Status Buckets Work
A bill of routing is a product's manufacturing recipe: the ordered steps, the work center for each step, and the time each takes. It is what turns "we need 100 of these" into an actual schedule. So the first thing a planner needs to know about the product catalog is coverage: how many products have a routing and how many do not.
BOR status buckets answer that by placing every product in exactly one of three states:
- Has BOR: the product has a routing and can be scheduled.
- No BOR: the product has no routing, so nothing about it can be planned yet.
- Multiple BORs (Legacy): the product carries more than one routing, usually older data that needs consolidating.
The classification is stable, meaning it always resolves to one of these three, so the pie always adds up and never leaves a product uncounted. The value is in the No BOR and Multiple slices. No BOR is a direct to-do list of products that will silently fail to schedule until someone builds their routing. Multiple BORs is a warning that a product could schedule against the wrong recipe if the duplication is not cleaned up.
A Concrete Example
Open the Products dashboard for a catalog of 80 products and the pie might read:
| Bucket | Count |
|---|---|
| Has BOR | 63 |
| No BOR | 12 |
| Multiple BORs (Legacy) | 5 |
The 63 Has BOR products are ready: any manufacturing order for them will turn into a plan. The 12 No BOR products are the problem, because a job for any of them has no steps or times to schedule against and will simply not appear in the plan. If those 12 include something you are counting on shipping, that demand is currently invisible to the schedule.
The 5 Multiple BORs products need review. Each carries more than one routing, and unless the selection is unambiguous, a job could schedule against a version you did not intend. Consolidating them to a single correct routing moves them into Has BOR and removes the ambiguity.
How EDGEBIC Uses BOR Status Buckets
The buckets live on the Products dashboard as a pie chart, giving planners a coverage read on the whole catalog in one glance. They sit alongside the other dashboards EDGEBIC ships, described in EDGEBIC dashboards explained, each turning a table of records into a picture a planner can act on.
The practical workflow is to clear the No BOR slice first, since those products cannot be scheduled until they have a routing, then review the Multiple BORs slice to retire duplicate recipes. As routings are built and cleaned up, products migrate into Has BOR and the pie fills with schedulable products. That direct link between a dashboard slice and a concrete planning gap is what makes BOR status buckets more than a chart: they are a queue of the master-data work that has to happen before the schedule can be trusted.
Expert Q&A: Deep Dive
Q: The Products dashboard shows 12 products in the No BOR slice. What is the practical impact?
A: Those 12 products cannot be scheduled at all until each gets a bill of routing. A manufacturing order for a No BOR product has no steps, work centers, or times to plan against, so it simply will not turn into a schedule. The pie slice is a to-do list: build a routing for each of the 12, and they move into the Has BOR bucket and become schedulable. Until then, any demand for them is invisible to the plan.
Q: A product I expected to schedule sits in Multiple BORs (Legacy). Should I worry?
A: Worth a look, yes. Multiple routings on one product means there is more than one recipe on file, and unless the selection is unambiguous, a job could schedule against a version you did not intend. The safest move is to review that product's routings, keep the correct one, and retire the rest so it lands cleanly in Has BOR. The bucket exists precisely to make that legacy duplication visible before it produces a surprising plan.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.
User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
The EDGEBIC Scheduling Glossary Index
A themed index to the EDGEBIC glossary: scheduling engine, capacity and calendars, materials and planning, shop floor, reporting, quoting, and data import terms, defined in plain language.
What Is the Critical Chain in Manufacturing Scheduling?
The critical chain is the longest dependent path through a plan once shared machine contention is counted, not just step precedence. Here is how it differs from the critical path.
What Does Finite Capacity Mean in EDGEBIC?
Finite capacity means the scheduler refuses to book more hours on a machine than that machine actually has. See exactly how EDGEBIC enforces it, day by day and shift by shift.