How to Handle Preventive Maintenance for a Machine in EDGEBIC

EDGEBIC by User Solutions holds no maintenance interval, no last-service date, and no PM-due banner at the shop floor terminal. There is nothing to configure on the work center for a service reminder, because tracking the cadence is not what this system does. What it does is turn an agreed service window into hours the scheduler will not book, which is the part that protects your delivery dates.

If you arrived looking for the interval field, this page saves you the search and covers the workflow that genuinely keeps maintenance and the plan in step.

Before You Start

• You know the machine's service cadence from wherever you track it: a maintenance system, a shared calendar, or a spreadsheet.
• The work center exists (how to add a work center).
• You know roughly how long the service takes, because you enter hours rather than a checkbox.

Step 1: Keep the Cadence Where It Lives

Service intervals, hours-since-service, condition monitoring, and work orders belong to your maintenance process. EDGEBIC does not duplicate them, and the work center editor has no field that would.

That division is worth defending rather than working around. Deciding when a machine actually comes out of production depends on the queue in front of it, the maintenance crew's availability, and how badly this week needs the capacity. That is a conversation, not a countdown, and a scheduler that unilaterally blocked a constraint because a counter rolled over would be overridden within a week and then distrusted.

Step 2: Pick the Day From the Load

An interval is a window, not a deadline to the hour. A machine due on the fourteenth on a 90-day cycle is usually just as well served on the twenty-first, and one of those days is cheaper than the other.

Look at the machine's load before you commit. Moving a teardown a week to land it on a genuinely quiet day costs nothing on a quarterly cycle and can save you a late job. How to run the work center utilization report is the quickest way to see where the slack is.

Step 3: Enter the Window as a Per-Day Capacity Override

This is the step that changes the plan. Open the Workcenter tab, select the machine, open its per-day capacity dialog, choose the shift, and find the date.

Enter the hours the machine can genuinely offer that day:

Add a reason such as "quarterly teardown" so the entry explains itself to whoever reads it next month. The full procedure is in how to block a machine for a maintenance day.

The detail that catches people out is that overrides are per day and per shift. A machine running days and nights needs the entry on both, or the plan will quietly book night work onto a machine that is in pieces.

Step 4: Reschedule

Nothing moves until a scheduling run reads the new calendar. Run the schedule and the work that was sitting on those hours is placed elsewhere. Operations already started keep their logged actuals exactly where they were recorded.

Step 5: Reset After the Service

When the machine is back, reset the override so the normal shift formula applies again.

This is the step that gets skipped, and skipping it is expensive in the quiet way. A reduced or zero entry left in place keeps a healthy machine partly out of the plan, and nobody notices until the load looks strange a month later. Treat the reset as part of closing out the work, in the same way you would file the work order.

What Changes When You Save

How to Check It Worked

1. Reopen the per-day capacity dialog and confirm the date shows your number with its reason.
2. Run the schedule and confirm no bars sit inside the protected hours on that machine.
3. After the reset, confirm the day returns to its normal capacity on the next run.

Common Mistakes

• Hunting for an interval field. It does not exist, and there is no terminal banner. The cadence lives in your maintenance process.
• Entering the window on one shift only. A two-shift machine needs the entry on both, or half the day stays bookable.
• Putting the service on the due date by reflex. Pick the cheapest day inside the window the interval allows.
• Forgetting to reschedule. The override is read at planning time, so the plan only respects it after a run.
• Leaving the override in place afterward. A stale entry silently starves a machine that is back in service.

Next

For the wider picture of hours lost inside a working day, read downtime explained, and for how the capacity chain resolves, how EDGEBIC calculates work center capacity. A full worked month is in planning a month of preventive maintenance. More single-task recipes are in the EDGEBIC how-to hub, and the platform overview is at EDGEBIC.