- Home
- Blog
- Shop Floor Execution
- Skill Expiry and Recertification in EDGEBIC
In EDGEBIC by User Solutions, an operator certification can carry an expiry date, and when it lapses the scheduling engine stops counting that person as qualified for the skill. Certifications are not permanent by default: a welder certified for a demanding alloy, an inspector qualified on a coordinate measuring machine, a machinist signed off on a setup, all can be given an expiry so the schedule reflects reality when a qualification runs out. This keeps the labor constraint honest over time, which is the whole point of tracking operator skills in the first place.
A schedule that assigns a lapsed welder to a certified job is fiction before the first arc strikes. Expiry tracking is how EDGEBIC refuses to build that fiction.
The Certification Record
A certification is the link that says "this operator holds this skill." It carries a few fields beyond the operator and the skill themselves.
| Field | Meaning |
|---|---|
| Certified on | When the qualification was earned, informational |
| Expires on | When it lapses. Empty means it never expires |
| Level | An optional site-defined proficiency, informational in this version |
| Active | Whether the certification currently counts |
Two of these control whether the operator counts as qualified: the expiry date and the active flag. The certified-on date and the level are for your own records and reporting.
How Expiry Reaches the Schedule
The scheduling engine does not query the database mid-run. Before each scheduling run, EDGEBIC loads everything the engine needs into one structure, and that load is where expiry is enforced. A certification whose expiry date has passed as of the run is simply not included. The operator drops out of the qualified pool for that skill on the next scheduling run, quietly and automatically.
The consequence is clean. A step that requires the skill is staffed only from operators whose certification is still valid. If the lapsed operator was the only qualified person, the step slides to a shift where a valid operator is staffed, exactly as it would if that person were on time-off or simply not rostered. The engine never assigns work to a certification it cannot honor.
One important detail: expiry is evaluated as of the run. A certification that has expired is treated as expired for the whole run, not switched off partway through the plan. So if a cert lapses next week, the operator is excluded from every day of the next scheduling run, not just from next week onward. Renewing before the run puts them back in play for the entire plan.
A Worked Example
Take a plant with one Inconel-certified welder, Joe, and a queue of Inconel jobs. Joe's certification expired last Friday. Nobody else holds the skill yet.
- The engine loads its data for tonight's run and filters out Joe's expired certification. The qualified pool for the Inconel skill is now empty.
- Every Inconel job needs that skill, so none can be staffed. They slide until a valid operator exists, which right now is never, so they park.
- The Gantt shows the slide plainly. That is the honest answer: the work cannot run without a certified welder.
Renew Joe's certification with a future expiry, or certify a second welder, and reschedule. The pool has valid hours again, and the jobs pull back to where they can be staffed. The slide was never a bug; it was the constraint telling you the truth.
Recertifying an Operator
Bringing an operator back into the pool is a two-minute task. Open the operator's Skills tab and either extend the certification's expiry date to a future date or add a fresh certification for the skill. At the next scheduling run the certification is unexpired, the operator rejoins the qualified pool, and steps that needed the skill can be staffed by them again. Because operator availability is read at run time, nothing changes on the plan until a reschedule runs, so you can update several certifications and then run once.
Recertification is also where the certified-on date and the optional level earn their keep. Recording when the qualification was renewed and at what proficiency gives you a running history of who is signed off on what, useful for planning cross-training and spotting a skill held by only one person.
Suspend Without Losing History
Sometimes you need to pull a certification without expiring it, for example while an operator waits on a re-test. Deactivate the certification rather than deleting it. An inactive certification drops out of the engine feed just like an expired one, so the operator stops counting as qualified, but the record stays with its certified-on date intact. When the re-test passes, reactivate it. Deleting would erase the history of what the person once held, which you do not want; deactivation gives the same scheduling effect while preserving the trail.
The same principle protects the skill itself. A skill still required by any routing step cannot be hard-deleted. EDGEBIC refuses with a friendly count and points you to deactivate instead, so you never orphan a step's requirement by accident.
Why This Matters
Certification tracking is a small feature with an outsized payoff for trust. A plant that schedules a lapsed welder onto a certified job discovers the problem on the floor, or worse, at the customer. EDGEBIC moves that discovery to the plan, where you can act on it: renew the cert, cross-train a second operator, or accept the slide with eyes open. It is the same discipline that took User Solutions customers like GE Railcar from 30% to 90% on-time delivery, which is planning against reality rather than against a hopeful assumption.
Expiry composes with everything else in the labor model. A valid certification still has to be rostered on the shift and free of time-off to count, and the attend fraction still decides how much of that person a run consumes. Expiry simply governs the first question: is this person qualified at all, right now.
The Bottom Line
Skill expiry keeps your qualified pool honest. A certification can carry an expiry date, and once it lapses the operator drops out of the engine feed on the next scheduling run, so steps needing the skill are staffed only by valid, unexpired operators. Recertify by extending the date or adding a fresh certification, and deactivate rather than delete when you need to suspend without losing history. The result is a schedule that never promises work a certification cannot cover. See how the pieces fit in the shop floor execution guide, and explore the platform at EDGEBIC.
Expert Q&A: Deep Dive
Q: My only Inconel welder's certification expired last Friday and now all my Inconel jobs slid a week. Is that the system misbehaving?
A: No, that is the constraint working. An expired certification is dropped from the engine feed, so your welder no longer counts as qualified for that skill, and the jobs that needed it cannot be staffed until someone valid is available. The slide is the honest picture: the work genuinely cannot run without a certified person. Renew the certification with a future expiry date and reschedule, and the jobs pull back to where the welder can cover them.
Q: I want to suspend a certification pending a re-test without losing its history. What is the right move?
A: Deactivate the certification rather than deleting it. An inactive certification drops out of the engine feed just like an expired one, so the operator stops counting as qualified, but the record and its certified-on date stay for history. When the re-test passes, reactivate it or add a new certification. Deleting is the wrong tool here: deactivation gives you the same scheduling effect while preserving the audit trail of what the person once held.
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 Schedule Reconciliation Report in EDGEBIC, Explained
Eight parameter checks over two exception grids. See how EDGEBIC reconciles the plan against the plant and shows only the rows that disagree.
Why a Dependent-Parallel Child Is Exempt From the Over-Booked Check
Three synchronized drills book 24 hours on an 8 hour day. That is real plant behavior, not a capacity breach, and flagging it would make the whole check useless.
Confirming a Sub-Assembly Versus the End Product in EDGEBIC
One dialog, two mechanisms. See why confirming an end product reduces the build directly while confirming a sub-assembly works through ordinary stock netting.
