Scheduling Laboratory and Scientific Instrument Manufacturing

A scientific instrument plant is rarely constrained by assembly. It is constrained by calibration benches, burn-in chambers, and the technicians certified to sign the record. EDGEBIC by User Solutions models those as finite capacity, carries burn-in as real elapsed time across nights and weekends, and keeps a per-unit routing snapshot so the as-built record survives every schedule change.

Machining, wiring, and mechanical assembly are all schedulable in the ordinary way. Test, calibration, and burn-in are where an instrument builder loses its promise dates, and they are usually the resources whose real capacity nobody has modeled.

Burn-In Is Elapsed Time, Not Worked Time

A 48-hour burn-in does not pause at the end of second shift. It runs through the night and through the weekend, and any plan that clips it to worked hours will be wrong by days on every unit.

Model each chamber as its own work center with a real capacity, and carry the cycle as elapsed time. A soak started Thursday at 2 PM finishes Saturday at 2 PM, and final test is placed on the first shift that is genuinely staffed. If you have three chambers, the plan cannot promise four units into them at once, which is exactly the promise a spreadsheet makes every quarter. The general principle is covered in finite vs infinite capacity scheduling.

Where chambers are interchangeable, put them into a work center group and bind the burn-in step to the group rather than to a named chamber. At schedule time the engine expands the group and places each unit on whichever chamber frees up first against live load. See how a work center group shops a pool of machines.

Calibration Is a Certified Person, Not a Bench

Calibration and final verification are usually the operations that decide whether an instrument ships, and they are done by a small number of certified people against a small number of reference benches. Modeling the bench without the person gets you a plan that is confidently wrong.

Record each technician's certifications, put them on the shift roster, and require the matching skill on the calibration and verification operations. The schedule then books that work only where a certified technician genuinely has hours, so a batch does not get promised into a week when the one person certified on that instrument family is on leave. See how operator skills constrain a schedule and how the shift operator roster works.

That model also makes the certification gap visible ahead of time rather than at the moment it hurts. Run the quarter with one more certified technician on the roster and compare the finish dates, which turns a training budget request into a number of days. See how skills data targets cross-training spend.

Configure to Order Means Quoting Against Live Load

If every unit is configured differently, a standard lead time is a guess dressed as a commitment. Build the configuration's routing, then run it as a what-if against the current schedule and let the result be the promise date.

Because the simulation runs against live load, the answer already accounts for the units in front of it, the chambers that are already full, and the technicians who are already booked. Change one option and rerun to see what that option costs in days, which is the conversation that wins configured orders instead of over-promising them. See how a quote simulation produces a realistic date and how EDGEBIC turns a quote into a promise date.

Outside Processing and Long Lead Parts

Boards go to an assembly house, enclosures go to a coater, and certain sensors have lead times measured in months. None of that belongs in a planner's head.

Put the outside step on the routing with its real transit time, and set whether transit counts calendar days or working days. A five-day turn that starts on a Thursday lands very differently under each convention, and getting that wrong is a recurring source of quiet lateness. Purchase order, receipt, and open-order data from your ERP comes in through flexible Excel, CSV, and database import masks rather than through a native connector, so the dates you schedule against are the ones your buyers are actually working to. See EDGEBIC ERP integration.

Keeping the As-Built Record

Instruments come back. A unit returned from a lab two years after shipment needs a build history that reflects how it was actually built, not how the current master routing reads.

Each job carries its own routing snapshot, so the operations and work centers that unit went through are preserved with the job. Completed operations are never moved by a reschedule, so the record stays intact through every replan and every routing revision. See what is a routing snapshot.

A Worked Unit

A configured benchtop analyzer with a customer-specified detector option and a fixed installation date, scheduled backward from that date.

Burn-in was placed to run over the weekend rather than through Monday and Tuesday of week 5, which pulled calibration forward two days at no cost. Calibration was booked against a specific certified technician's available hours, not against an assumption that any bench would do. The board assembly transit was counted in working days, so the Thursday start returned the following Tuesday rather than the previous weekend.

When a Build Runs Long

Technicians log start, stop, and quantity at a floor station, so a bring-up that took two extra days pushes only the work that has not started. Completed operations stay put through the replan. Over a few quarters those logged times become the evidence your standard times need, which matters most on bring-up and calibration where the routing numbers were estimated from a configuration that no longer ships. See how a reschedule uses last night's actuals.

Heritage in Instrument and Electronics Manufacturing

User Solutions has built finite capacity scheduling since 1991, more than 35 years, for operations where a scarce certified skill and a slow shared resource set the pace: US Navy, GE, BAE Systems, and Cummins across 33 locations. In that same lineage, Instruments For Industry, a manufacturer of solid state and traveling wave tube amplifiers, used Resource Manager DB to combine lean methods with the procurement discipline of a traditional MRP approach rather than choosing one and losing the other. A high-mix instrument builder trying to hold honest dates across configured orders is that same problem.

Where to Start

Enter your burn-in chambers, reference benches, and verification stations as work centers with real capacities and calendars. Carry burn-in as elapsed time. Record your technicians' certifications and put them on the roster. Put outside processing on the routings with real transit days and the right calendar convention. Then quote your next configured order as a simulation against live load and compare it to the standard lead time you would have given.

For fundamentals, what is production scheduling covers the basics and job shop scheduling challenges covers the high-mix problem. A neighboring sector with the same configure-to-order shape is industrial equipment make-to-order scheduling. The industry fit guide maps the rest and EDGEBIC is the product hub. Want to know what your burn-in capacity really allows per month? Contact US for a demo.