SystemContract Manufacturing (CDMO)

Capacity Planning & Scheduling Scenarios

Capacity planning that answers a client's pull-in on the plant's own schedule: agents draw each scenario with its cleanings, crews and QA review time, a challenger attacks it, and two people sign.

See one client's pull-in drawn on the schedule ↓
Watch with transcript →
The problem

A pull-in answered in a spreadsheet moves another client's date unseen

A client asks for its batches sooner, for launch stock in a new market. The planner exports the line schedule into a spreadsheet and moves rows. Then the hard questions go out by email: is the second press approved for this product yet, which cleaning does the new order need, who can staff a weekend, can QA review the extra records.

The plant head gets one option days later and cannot see what it moved. The client's dates are often revised a week on, when a forgotten cleaning or a full review queue surfaces, and the batches pushed back belong to another client nobody told.

Built forPlanning headsProduction plannersPlant headsQA operations managers

The Problem Today

A pull-in replanned by hand misses a cleaning, a crew rule or QA's review queue, and another client's date slips without anyone seeing it.

62%
drug shortages that followed plant or quality problems, FDA published

Asked around the plant by hand

  • Lines
  • Cleanings
  • Crews
  • QA review
  • Another client's order slipsA batch moved for one client pushes a second client past its date
  • The answer waits on emailLine status, crews and QA time are asked one person at a time

The Solution

  1. The live schedule, drawnEach batch a bar on its machine, each cleaning at its matrix length
  2. Each scenario drawn over itMoved batches leave ghosts; new cleanings and weekend shifts appear
  3. Held to the plant's rulesA line still in qualification is blocked, and a challenger tests each draft
  4. Two signatures, then the clientPlanning chooses, QA sizes the review work, the plant head signs second

Built-in controls

  • Only approved lines and validated cleanings
  • Nobody approves the scenario they chose
  • Each client sees only its own orders

What You Get

A client's pull-in answered with a plan the plant can run, and no other client's date moved in silence.

  • Yes to a launch pull-inBatches made sooner with crews and cleanings already planned
  • Dates a client can plan onCommitted in its own portal, with the one condition stated
  • Crews kept inside policyEach operator keeps a full weekend off in three
Features

Capacity planning features, from the client's request to signed dates

A client asks for eight planned batches sooner, and planning, QA operations, the plant head and the account manager each act on one drawn schedule.

demoThe plant, its clients, the people, the orders and every date shown are sample data.

  1. 01Ghost schedule

    Production schedule as a Gantt of each batch and changeover cleaning

    • Each batch a bar on its machine. Granulators, dryers, blenders, presses, the encapsulator and the coaters each get a row, so the planner reads the plan the way the floor runs it.
    • Cleanings at their real length. Changeover cleanings come from the cleaning matrix and are hatched at their length, so the hours a product change costs stay in view.
  2. 02Client request

    Client pull-in request read from its fields, with each batch it touches

    • The request as the client sent it. Product, batches, month asked for and reply deadline come from the portal form's fields, and the line the reader took is marked.
    • Planned batches with their orders. Each planned batch the request touches shows its purchase order, today's make date and disposition date, so nobody searches planned orders by hand.
  3. 03Blocked line

    Equipment qualification status checked before a line is offered as capacity

    • An open change control blocks a line. A press still in qualification is drawn where the batches would run and cannot be chosen, so no client is promised capacity that is not there.
    • An unvalidated cleaning named. A product order whose cleaning has no validation on that line is listed beside the qualification status as a reason it is blocked.
    • The client's approval for a new line. Moving a product to another line also waits on its owner's approval under the quality agreement, and the panel says so before anyone asks.
  4. 04What-if scenario

    What-if scenario analysis drawn on the schedule, with each order it moves

    • Ghosts where the batches were. A moved batch leaves a faint ghost joined to its new bar, so the planning head sees exactly which later weeks the scenario emptied.
    • Cleanings and weekend shifts drawn in. The product changeover cleanings the new order needs appear on the press row, and opened weekend cells show which machines would run.
    • Other clients' orders that move. Down the right runs each other client order whose disposition date moves, by how many working days, and which ones pass their committed date.
  5. 05Scenario challenger

    Scenario challenger that tests each draft, the agents' own first one included

    • First drafts tested like a planner's. A draft the agents drew is tested as hard as a planner's, and the screen says what was fixed in it before planning reads it.
    • The plant head's questions answered first. Why not weekdays only, and whether three weekends in a row keep crews within policy, are answered on the page or sent to the person who decides.
  6. 06Decision

    Scenario chosen by the planning head, with its approval left to another

    • A choice signed with its meaning. The head of production planning signs what the choice means and picks a reason code, and both stay on the decision record.
    • Approval waits for QA's answer. The plant head cannot sign until QA operations has confirmed review time, so no plan is approved while other clients' dates still slide.
  7. 07Release capacity

    QA review capacity requested record by record and answered in overtime shifts

    • The records a scenario adds. Each batch reaching the review desk early is listed with its new packaging date, so QA sizes the extra work from the plan itself.
    • An answer in shifts and records. The QA operations manager picks reviewer overtime shifts and signs, and the projection redraws with the other clients' orders back on their dates.
  8. 08Second sign-off

    Plant head approval only after each part of the scenario has been opened

    • Four parts read before signing. What moves, crews and cost, release dates and the challenger must all be opened before the plant head approves or sends the scenario back.
    • The signed plan frozen as signed. Any later steer or setting starts an unsigned draft, so dates already sent to a client stay true.
  9. 09Client portal

    Committed delivery dates sent after both signatures, accepted in a portal

    • Sent by the account manager. The client account manager reads the notice drafted from the signed plan before sending it, and firm dates stay blocked while a material hold stands.
    • Only the client's own orders. The client's supply planner sees its own batches and committed dates, with the condition they rest on, and nothing of another client's schedule.
    • Answers in fixed fields. Accepting, or declining with a reason from a list, changes the order's status; a typed comment waits for the account manager, unread by agents.

The crew plan reaches the plant head already checked against the weekend rule

Planning builds and chooses, QA operations sizes the extra review work, and the plant head approves a plan someone else chose.

Heads of production planning

Answer client pull-ins and line problems, and own the master schedule

  • Three scenarios drawn in one run
  • Each order a choice moves, client by client
  • A plan only another person can approve
Production planners

Build the weekly sequence, steer the agents and ask what-ifs

  • Cleanings the matrix requires, never guessed
  • Steers such as no Sunday shifts, logged
  • A line-down question answered on the schedule
Plant heads

Approve the schedule second and grant working-time exceptions

  • Crew plans checked against the policy
  • Each part of a scenario opened before approval
  • Settings that change only with their signature
QA operations managers

Run batch record review and disposition, and size review capacity

  • The extra records a scenario adds, listed
  • Overtime answered in shifts and records
  • Release dates that count the growing queue

No date is promised as firm while the material behind it is on QA hold

Request reader

Reads the client's request and the supply agreement, and lists the planned batches it touches.

  • Never reads the client's free text
Routing reader

Reads the approved equipment for each product and step, and any open change control on a line.

  • Never places a batch on equipment not approved for it
Cleaning sequencer

Orders batches on each line, adds the cleaning each product order needs and keeps the wet-granulate hold rule.

  • Never uses a product order whose cleaning is not validated
Calendar and crew checker

Checks shifts, shutdown, frozen zone, weekend crews, training records and the working-time policy.

  • Never names a person for a weekend shift
Release-date projector

Projects the CDMO's disposition dates from packaging and QA review capacity, and lists each order that moves.

  • Never calls a date firm while its material is on hold
  • Never dispositions a batch
Scenario challenger

Plays the plant head, QA, the client and an inspector against each scenario, the agents' own drafts included.

  • Never chooses a scenario
Client notice writer

Drafts the client's new committed dates from the signed plan and reads its fixed-field answer.

  • Sends nothing itself

The agents' first weekend draft made fewer batches than weekdays alone

Weekends that could not finish a batch

Draft A opened weekend shifts on the granulator and press only, so nothing could be dried, blended or coated; it made 0 of 8 in December until the challenger opened the rest of the train.

Three weekends in a row for one crew

The six qualified operators on the product's press would work three weekends running, against the rule of one full weekend off in any three, so scenario A needs the plant head's exception.

One punch set for every December batch

The second punch set is locked in the stopped press under a deviation, so each December compression runs on a single set with no spare; the planner decides how to cover it.

demoSample data, from the working solution.

More screens

On weekdays alone, re-sequenced coatings make room for two of the eight

The weekday option, a line-down question asked in words, the rules the agents plan with, where the product may be made, and who signed.

Weekdays only, coatings re-sequencedWith no weekend shifts, re-sequencing coatings first in, first out makes 2 of 8 in December, and 58 other client orders move, 27 past their committed date.
A press line down, asked in plain wordsAsked what moves if a press line is down for three working days next week, the assistant draws it and lists the 10 client orders that move.
The rules the agents plan withApproved equipment by product and step, each changeover cleaning with its hours and validation status, and the shifts, crews and working-time rule the agents plan with.
Where the product may be made at allAcross four plants the product is approved on one press line; the line in qualification and the plants with no approval are named, and their schedules are not drawn.
The plant head's reading of every part is logged before the approvalQA's answer, the plant head's reading and approval, the drafted and sent notice and the client's answer, newest first, each with its reason, meaning and session.

demoSample data, from the working solution.

The schedule rebuilt from validation reports, cleanings and the review log

Line schedule and planned ordersBatches on each machine and the orders behind them, from the execution and planning systems.
Validation reports and change controlsWhich equipment is approved for each product, and which lines are still in qualification.
Cleaning matrix and batch record hold rulesEach product order's cleaning, its hours and validation, and how long wet granulate may wait.
Calendar, training records and working-time policyShifts, shutdown, qualified operators by step and the weekend rule for each crew.
QA review logThe review rate and queue that set each projected disposition date.
Client portal requests and answersPull-in requests and the client's fixed-field answers to new dates.

Questions planning offices ask about capacity planning for client programs

What is capacity planning at a contract manufacturer?

Capacity planning at a CDMO decides which client batches run on which approved lines and when, with the cleanings, crews and QA review time each one needs. Here agents draw each what-if over the plant's own schedule and list every client order a change moves, and people choose and sign.

What happens when a line is still in qualification?

The scenario on that line is drawn on its own row, marked blocked and cannot be chosen. The panel names the open change control, the stopped qualification batch, any cleaning not yet validated on the line and the client approval a new line needs.

How does QA review time enter a capacity plan?

Batches that reach the review desk sooner put extra work ahead of later batches. The projection shows which client orders move until QA operations confirms review time in fixed fields, and the plant head cannot approve the scenario before that answer.

Who signs a scenario before it becomes the schedule?

The head of production planning chooses it, QA operations confirms the review time, and the plant head reads it through and signs second. A scenario needing a working-time exception also carries the plant head's signed exception.

Does a new schedule release or disposition any batch?

No. The agents project dates and never release, disposition or approve. Disposition of what the plant made stays with the CDMO's QA, and release to market with the client's qualified person.

Bring the pull-in
you could not answer in time.

Send one plant's line schedule, cleaning matrix and a client's request, and we will draw the scenarios over it.