How to Mark a Job as Started in EDGEBIC

To mark a job as started in EDGEBIC by User Solutions, right-click the order row in the Orders grid and choose Start Order, which sets its Status to In Progress. The control lives on the Drive Schedule tab, in the Orders grid. It is a planning flag, not an actuals entry: it tells the plan the job is live without stamping an actual start time on any operation.

The distinction matters more than it looks. A status flag and a logged actual do two different jobs, and reaching for the wrong one is the most common reason a plan and a shop floor drift apart. This page covers the flag. For the shop-floor record that drives rescheduling, see the sibling recipe on the kiosk linked at the end.

Before You Start

• The job is already scheduled. Start Order changes a status; it does not create a plan.
• You understand this is a flag, not actuals. It does not write an actual start onto any operation.
• You know your reschedule mode. Only some modes leave an In Progress job alone.

Step 1: Open the Orders Grid

Open the Drive Schedule tab. The Orders grid lists every manufacturing order with its Product, Quantity, Due Date, Priority, and Status.

Find the row for the job you want to mark started. Click it once to select it.

Step 2: Choose Start Order

Right-click the selected row and choose Start Order from the context menu.

The Status column changes to In Progress. No dialog, no date picker: this action is deliberately lightweight because it records a state, not a time.

Step 3: Log Actuals Separately If You Need Them

If the plan needs to know where the operation actually stands, this is where the kiosk comes in. An operator confirming a real step writes an actual start time onto that operation row, and that is the information a reschedule uses to resume the job from the shop floor rather than replanning it from the top.

Marking the order In Progress and logging an actual are two separate acts. Do the first for a quick planning signal. Do the second when the shop floor has real progress to report.

What Changes When You Save

How to Check It Worked

1. Confirm the Status column on the Orders grid reads In Progress for that row.
2. If you expected actuals, open the operation detail and check that an actual start is present. If it is blank, you set the flag but did not log the actual, which is fine as long as that was your intent.
3. Before an end-of-day rerun, confirm your Scheduling Mode. Choose Incremental All or Smart Incremental if you want started jobs left alone.

Common Mistakes

Expecting Start Order to record actuals. It sets the Status only. If a report or a reschedule seems to ignore the fact that work has begun, it is because no actual start was logged. Use the kiosk for that.

Assuming the flag survives every mode. Full Reschedule and Reschedule replan the job regardless of the In Progress flag. Only Incremental All and Smart Incremental preserve it.

Confusing In Progress with On Hold. In Progress says work has started. On Hold suspends a job. They are different states with different downstream effects. Do not use one to mean the other.

Next

Start Order is the fast way to flag a live job on the Orders grid, and it pairs with the kiosk path when the shop floor has real progress to report. To record that progress, read how to start a job on the kiosk. To see how modes decide what a rerun touches, read how to run the scheduler, and to keep a job out of the plan entirely, how to put a job on hold. More single-task recipes are in the EDGEBIC how-to hub, and the platform overview is at /edgebic.