How to Log Actual Hours for a Day Outside the Planned Window in EDGEBIC

The Log Actuals grid in EDGEBIC by User Solutions extends past an operation's planned window: go to a day earlier than the scheduled start or later than the scheduled end, enter the hours, and a daily row is created for that date. Work starts early and runs late, and the record is only useful when it can say so. This is how to log the day that really happened.

For everyday entry inside the planned window, see how to log actual hours and pieces. Every task in this library is mapped on the EDGEBIC how-to hub.

Before You Start

• The operation has an actual start recorded, so the grid opens on day rows rather than the dates dialog.
• The job is not marked complete, since a completed job locks actuals entry until it is reopened. If it is, start with how to reopen a completed operation.
• You know the real dates, not just the real hours. Both matter, and they are stored separately.

Step 1: Open the Grid for the Operation

Right-click the operation's bar on the Schedule View Gantt and choose Log Actuals, or use the Log Actual header button on the Job View tab and pick the work center. On the routing diagram in the live monitoring view, double-clicking the step's card opens the same flow.

The grid arrives with one row per calendar day of the operation's window, showing the scheduled hours and pieces beside the actual columns.

Step 2: Go to the Day You Need

Move to the date the work really happened, even when it sits before the first row or after the last. The window extends to reach it, and the day is added as a new daily row.

Two directions, one behavior:

A row with actual hours and no scheduled hours is not an error. It is the plan and the shop disagreeing, recorded honestly.

Step 3: Enter the Work

Type the hours or the pieces. With Auto Calc Hours ticked, the other side derives from the operation's rate, so you only enter the side your shop counts. Untick it when you want both numbers to stand as measured.

Click Save.

• If you changed values that had been reported before, the dialog asks for a reason. It is stored in the logging history with the old value, the new value, and your name, and an empty reason cancels the save.
• If earlier days of the same operation are still empty, a prompt says so. Fill them if they should be filled, or continue if the gap is real.

Step 4: Make the Dates Agree

Hours on a day and the operation's actual start and end are separate records. Logging Saturday hours on an operation whose actual start says Monday leaves the bar drawing in one place and the hours sitting in another.

Use Log Actual Dates inside the dialog to set the actual start to the real first day, and the actual end to the real last day where the operation is finished. The validator refuses an end that is not after the start, which is always a data-entry error rather than a real situation.

Step 5: Reschedule

Press Re-Schedule for the job, or run the full schedule where several jobs were corrected. The engine plans remaining work forward from where the job really is, so a job that gained a Saturday should now show its downstream steps pulled earlier, and a job that ran into an extra day should show them pushed later.

What Changes When You Save

How to Check It Worked

Reopen the grid and confirm the out-of-window day is there with your hours. Then look at the Job View header: actual hours should include the day you added. Finally check the Gantt bar, which draws from the actual start once actuals exist, so a corrected start should have moved it.

Common Mistakes

• Logging the day and leaving the dates. The bar and the hours then disagree, and the reschedule resumes from the wrong point.
• Assuming a health check will catch a wrong day. The checks catch an end before a start. Which calendar day you logged on is your judgment.
• Logging out of order. Fill earlier days first and the prompts about empty earlier days stop firing.
• Accepting an auto-filled day and never revisiting it. Days the system filled from plan wear a badge for exactly that reason, and editing one clears the badge.
• Batching a week of entry. Rescheduling resumes from your last logged position, so late logging plans the plant around stale reality.

See how logged reality drives the next plan on the EDGEBIC product page.