Scheduling Certified Operators in Aerospace Manufacturing

In aerospace, the constraint is often a person rather than a machine, and a schedule that cannot say so is fiction before the first arc strikes. EDGEBIC by User Solutions models operators as a second finite resource: routing steps name a required skill, operators hold dated certifications, rosters say who works which shift on which weekday, and a per-person hours ledger makes sure no day ever oversells anyone. For a shop with one Inconel-certified welder and five welding cells, that is the difference between a plan and a wish.

The full model, including the ledger design and the attend fraction, is documented in operator and skill scheduling explained. This post is about the aerospace and defense case.

The Failure This Exists to Kill

A scheduler that sees only machines will happily place five Inconel weldments on five welding cells in the same shift. Every machine is free, so every job fits.

On the floor there is one person certified for that process. Four of those five jobs do not start. Nothing in the plan said so, nothing flagged it, and the slip is discovered when a supervisor walks the aisle. By then the downstream operations, the inspection slots, and the delivery promise have all been built on the fiction.

That silent slip is the failure. It is not a reporting problem, it is a modeling problem: the plan had no way to represent the one thing that actually constrained it.

The Four Objects You Configure

The model is deliberately small, and each piece maps to something an aerospace shop already tracks on paper.

A routing step then names one required skill, and the constraint activates for that step only. Steps with no required skill are unaffected, and a shop that never configures operators schedules exactly as it would without the feature.

Rosters are a weekly pattern rather than per-date rows, mirroring how machine calendars work: a weekly shift definition plus holiday exceptions. Plants roster weekly and record absences as exceptions, so per-date rosters would mean thousands of rows per planning horizon for no additional truth.

Expiry Is Not a Reminder, It Is Capacity

For an AS9100 shop this is the detail that matters most. A certification carries an expiry date, and an expired certification is filtered out when the operator data is assembled for a scheduling run. The person simply stops counting toward the qualified pool.

That converts certification currency from an administrative reminder into a scheduling input. If a skilled operation loses capacity between two runs and nobody changed the roster, check expiry dates first. It also means recertification has a visible schedule consequence, which is usually the argument that gets it prioritized.

The same applies to deactivation: an inactive operator, an inactive certification, or an inactive roster row drops out of the feed and keeps its history for reporting.

The Qualified Pool, Worked

Two welding cells, one instance each, an eight-hour day shift Monday to Friday. One skill. One certified welder rostered Monday to Friday with no leave. Two jobs, each needing eight hours on a different cell, both requiring that skill at full attendance.

Without an operator model, both schedule Monday 08:00 to 16:00 in parallel. One welder, two simultaneous machines.

With the model:

1. The first job schedules. Monday's qualified pool is 8 hours, the machine needs 8, the pool affords 8. It is allocated Monday 08:00 to 16:00 and the welder is booked for 8 hours.
2. The second job asks about Monday. The pool is now 8 minus 8, which is zero, so Monday is never offered. The diagnostic log records the work center, the date, the shift, and the skill that could not be staffed. The day walk continues and Tuesday's pool is 8 hours, so the second cell runs Tuesday.

Certify and roster a second welder and both jobs run Monday, one on each cell. The plan now matches how a supervisor would staff it, which is the whole point.

Why Hours Rather Than Presence or Pools

Three simpler models were considered and each fails in a specific way worth knowing, because you will be tempted by them.

Presence only ("is somebody qualified rostered?") passes all five Inconel jobs. It is the original failure wearing a checkbox.

Per-skill pools ("eight hours of weld capacity, eight hours of inspection capacity") double-counts anyone multi-skilled. A person certified in two skills sells eight hours into each, and the plan believes in sixteen hours of one person. In aerospace, where cross-certification is the norm, this fails immediately.

Wall-clock intervals ("book this person 08:00 to 12:00 on this machine") doubles the state and exceeds the fidelity the machine side itself carries, since machine allocations are hour quantities per shift window rather than exact intervals.

What ships is a per-person hours ledger keyed by person, date, and shift. Joe has eight hours on Monday's day shift regardless of how many certifications he holds. Two of his bookings on different machines may overlap within a shift, exactly as machine allocations do, but no day can ever oversell his hours.

Pinning a Named Person

Sometimes the requirement is not "somebody certified" but "this person." A first article witnessed by a specific inspector, a weld on a customer-approved operator's stamp, a training assignment.

Pinning a routing step to an operator narrows the qualified pool to exactly that person in every calculation. The rest of the pool is never used as a fallback.

The consequence is the point of the feature. Take a step pinned to a welder who is on leave Monday through Wednesday, with a second certified welder available all week. Unpinned, the step runs Monday staffed by the second welder. Pinned, the pools for Monday to Wednesday are zero and the step slides to Thursday, that person's first day back.

A named person's absence becomes visible schedule movement rather than a silent substitution nobody approved. In a regulated shop, that is not a cost, it is the requirement.

Two guardrails come with it. A pin requires a skill on the step, and a pinned person who is inactive or not certified for that skill fails immediately with a message naming the problem rather than scheduling around it quietly. And a pin is cleared only when the skill is removed from the step, never on a skill change, so changing a step's skill leaves the pin in place and surfaces the mismatch on the next run rather than quietly dropping the assignment.

Multi-Shift Work and Why the Gate Is Binary

One behavior looks odd until you see the alternative. The check that asks whether a shift is usable receives the full remaining requirement for the step, not the slice that shift would take.

A twelve-hour operation asked about Monday, where the staffed pool is eight hours, would fail a strict comparison. So would Tuesday, and every other day, because every shift is smaller than twelve hours. The operation becomes unschedulable despite forty staffed hours in the week.

So the gate is binary: a shift with any staffed hours passes, and a separate clamp bounds the quantity when hours are actually allocated. Monday takes eight, Tuesday takes four, the operator is booked eight and four, no day is oversold, and the job finishes Tuesday at noon.

What the Supervisor Sees

Three surfaces carry the model into daily use. A read-only dispatch list groups planned work by operator and date with hour totals, which is what a supervisor prints. The Gantt marks skill-required operations and can show lanes by operator rather than by machine, with the crew for each bar in the tooltip. And the operator calendar shows availability against booked hours per person and per skill pool over time.

One clarification worth stating: planned operator assignments are plan data, regenerated wholesale on every reschedule. They answer "who is planned to work this," not "who worked it." Actual labor comes from the shop floor tracking surfaces, and the two should not be confused when building reports.

Composing With Machines and Constraints

The skill dimension composes with the machine dimension rather than replacing it. A step can name a machine pool and a required skill, and the pool's member selection is staffing-aware, so a machine whose shifts cannot be staffed for that skill loses to one that can rather than winning on machine capacity and then sliding. See machine pool scheduling for the machine half.

Do not model certifications as a machine pool. A pool answers "which interchangeable machine"; the skill layer answers "which qualified person, for how many hours." They are different questions with different data.

For the category background, aerospace and defense scheduling covers the fundamentals, AS9100 scheduling requirements covers the quality-system angle, and the defense and aerospace manufacturing scheduling page is the shorter evaluation read. If your delivery risk is a long routing rather than a certification, protecting delivery dates on long aerospace routings is the companion. The industry fit guide maps the rest, and EDGEBIC is the product hub.

Ready to put your cert list into the schedule? Contact US for a demo and bring the qualification matrix you keep in a spreadsheet.