- Home
- Blog
- EDGEBIC How-To
- How to See a Job's Step-by-Step Schedule in EDGEBI…
To see a job's step-by-step schedule in EDGEBIC by User Solutions, open the Schedule Job BOR view and pick the job number. It lists one row per operation with the work center it was assigned to, its planned start and end, its actual start and end if any, and the utilization used. This is the operation-level view that the job's overall start and end dates on the Orders grid cannot give you.
Two questions look the same but are not. "When does this job start and finish?" is answered on the Orders grid. "Which machine is each operation on, and when?" needs the step view. This page covers the second.
Before You Start
- The job has been scheduled. An unscheduled order has no operation rows to show.
- You have the job number or can find it in the dropdown.
- You understand this reads the saved plan, not unsaved Gantt edits.
Step 1: Open the Schedule Job BOR View
Under the Schedule area, open the Schedule Job BOR sub-tab. This view is built specifically to show operation-level detail for one job at a time.
Step 2: Select the Job
Choose the job number from the dropdown at the top of the view. The grid loads every operation for that job.
Each row shows the operation's work center, its planned start and end, its actual start and end when they exist, its utilization, and the routing step it came from. Read it top to bottom and you have the full path of the part through the plant.
Step 3: Read the Columns
Work through the rows in sequence:
- The work center column tells you where each operation landed. If a step has an alternate or a pool behind it, this is where you learn which resource actually took the work.
- The planned dates are what the engine computed.
- The actual dates, if present, are what the shop floor reported. A blank actual means the step has not been confirmed yet.
- Utilization shows how much of the shift the step used. A material or component line reads zero because it consumes no machine time.
What Changes When You Save
Nothing. This is a read-only view. Opening it, selecting a job, and reading the rows changes no data. It is a lens onto the committed plan, which is exactly why it is safe to hand to anyone who needs to answer a per-operation question.
How to Check It Worked
- Confirm the grid shows one row per operation in the routing, in sequence.
- Confirm each work center operation names a real machine and carries planned dates.
- If the job has been running, confirm the completed operations carry actual dates and the not-yet-started ones do not.
- If a number looks wrong, cross-check the Gantt. If the two disagree, you are looking at unsaved Gantt edits, which do not reach this view until you save them.
Common Mistakes
Expecting unsaved Gantt drags to appear. The step view reads the saved plan. Save the Gantt first, then reopen the view.
Reading a material step's zero utilization as a fault. Material and component steps consume no capacity and schedule instantly. Zero is correct for them.
Confusing job-level dates with step-level dates. The job's overall start and end come from the earliest and latest of its operations. They are not the same as any single step's dates. Use the step view when you need the machine-by-machine picture.
Next
The Schedule Job BOR view is the answer to "which operation is on which machine, and when." To carry that operation list out of the Job View into a spreadsheet for a job packet, read how to export one job's operation list to Excel. For the job's overall dates instead, read how to find a job's scheduled dates. To see live progress against the plan, read how to check a job's progress, and to understand how the engine placed each step in the first place, what production scheduling is. More single-task recipes are in the EDGEBIC how-to hub, and the platform overview is at /edgebic.
Expert Q&A: Deep Dive
Q: A customer wants to know exactly which machine their part is on this week. Where do I look?
A: Open the Schedule Job BOR view and select their job number. Each operation row names the work center it landed on plus its planned start and end, so you can tell them the part is on, for example, Mill-2 Tuesday through Wednesday and then Deburr on Thursday. The Orders grid only gives the job's overall start and end dates, which is not enough to answer a per-operation question. The step view is the one built for that.
Q: The step view shows an operation on a work center I did not expect. How did it get there?
A: The most likely reason is that the step has a true alternate configured and the scheduler routed it to the alternate because the primary was busy, or a machine pool resolved to a different member. The step view tells you where the work landed; to see why, check whether the routing step has alternates. If the operation also shows an actual start, remember that in-progress work is locked to the machine it started on and will not be moved to a faster alternate on a reschedule.
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
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.
