- Home
- Blog
- Glossary (EDGEBIC)
- What Is an End-Product Actuals Roll-Up in Manufact…
What Is an End-Product Actuals Roll-Up in Manufacturing? EDGEBIC Definition
An end-product actuals roll-up is a read-only summary that aggregates a job's operational actuals against the manufacturing order's single end product. It reports actual start and end, hours, pieces, planned hours, percent complete, and an all-steps-done flag for the job's end item, and it deliberately excludes sub-assembly rollup rows and component splits so nothing double-counts. It is the canonical answer to the question every manager eventually asks: how far along is this job's end item?
This entry is part of the EDGEBIC by User Solutions glossary series; for the broader vocabulary of planning, see the manufacturing glossary. For the per-step measure it aggregates, see what is percent complete.
How an End-Product Actuals Roll-Up Works
A manufacturing order builds one end product, but the routing that makes it can be layered: sub-assemblies feed the end item, and some steps split into components. Actuals get logged all through that structure, step by step, as the floor does the work.
If you simply summed every actual on the job, you would double-count. A sub-assembly's hours already flow up into the end product's operations, and a component split represents the same physical work seen from a different angle. Adding the sub-assembly rollup rows and the component splits on top of the end-product operations would make the job look busier than it is.
The end-product actuals roll-up avoids that by aggregating only what belongs to the single end product, excluding the sub-assembly rollup rows and the component splits. What remains is a clean picture of the end item: when it actually started and ended, how many hours and pieces are logged, how many hours were planned, what percent is complete, and whether every step is done. Because it is a projection over the step-level actuals rather than a stored record, it always reflects the latest logged data.
A Concrete Example
Job 42 builds one finished product through a routing that includes two sub-assemblies. As the floor logs actuals, hours accumulate on the sub-assembly steps and on the end product's own operations.
A manager asks how far along Job 42 is. Summing every row would over-count, because the sub-assembly hours are already reflected in the end product's operations. The end-product actuals roll-up instead reports on the end item alone: 62 percent complete, with 48 of 78 planned hours logged. That single figure is the honest progress of the finished product, not an inflated total.
When the last step finally closes, the roll-up's all-steps-done flag flips true. The manager no longer has to judge whether 98 percent means finished; the flag says it plainly. The roll-up gave a trustworthy running answer throughout and a definitive one at the end.
How EDGEBIC Uses It
The end-product actuals roll-up is a read-only projection over a job's logged actuals:
- It aggregates against the single end product, reporting actual start and end, hours, pieces, planned hours, and percent complete for the job's end item.
- It excludes sub-assembly rollup rows and component splits so shared work is not counted twice, keeping the figures honest.
- It carries an all-steps-done flag that turns true only when every step is complete, giving a definitive finished signal beyond a high percentage.
The roll-up is the job-wide sibling of step-level percent complete: one summarizes a step, the other the whole end item. To feed it, log actuals on the steps with how to log actual hours and pieces, and read the roll-up for the clean end-item answer.
An end-product actuals roll-up is a read-only summary that aggregates all of a job's operational actuals against the manufacturing order's single end product. In EDGEBIC it reports actual start and end, hours, pieces, planned hours, percent complete, and an all-steps-done flag for the job's end item. It deliberately excludes sub-assembly rollup rows and component splits so nothing double-counts, which makes it the canonical answer to how far along is this job's end item.
Because including them would count the same work twice. A job's end item is made from sub-assemblies and components, and their hours already flow up into the end product's operations. If the roll-up summed the sub-assembly rollup rows and the component splits on top of the end-product operations, a job would appear to have more hours logged than it really did. Excluding those rows keeps the percent-complete and hours figures honest, reflecting the end item's true progress.
It is read-only, a projection rather than a stored record you change. It reflects the operational actuals that have been logged on the job's steps, aggregated for the end product. You log actuals on the individual steps as usual, and the roll-up recomputes its summary from them. That separation keeps a single source of truth: the step-level actuals are the data, and the roll-up is a clean view over them.
Expert Q&A: Deep Dive
Q: A manager asks how far along Job 42 is. Which number do I give them?
A: Give them the end-product actuals roll-up figure, for example 62 percent complete with 48 of 78 planned hours logged. That is the canonical how-far-along answer for the job's end item, because it aggregates the operational actuals against the single end product and leaves out sub-assembly and component rows that would otherwise inflate the total. Any per-step percentage answers a narrower question; the roll-up is the one that speaks to the whole job's end item in one clean number.
Q: How do I know when the whole job is really done?
A: The roll-up carries an all-steps-done flag that is only true once every step is complete, so it is a reliable signal that the end item is finished rather than merely well along. A high percent complete tells you the job is close, but the all-steps-done flag is the definitive marker. Watching that flag, rather than eyeballing a percentage, tells you the end item has actually crossed the finish line.
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.
