MRP needs a usable material date

The receipt is only one milestone

A purchase order arrives on Monday, exactly as promised. Material requirements planning, or MRP, removes the shortage and production schedules the batch for Tuesday. The warehouse has received the material, but sampling, testing and review are still in progress. The physical delivery is successful while the production plan is already late.

This mismatch occurs when the planning system uses receipt as a substitute for usability. The remedy is to model the interval between those events and preserve the actual material status independently. An expected release date helps planning; it cannot authorise consumption.

The distinction matters especially where an active pharmaceutical ingredient, or API, drives a formulation schedule. A planner may see adequate total stock while none of the required quantity is eligible for the intended batch. More purchasing can increase inventory without resolving the immediate laboratory or review constraint.

Break the lead time into controllable stages

Start at the production need date and work backwards through the actual workflow. Include supplier preparation and transport where relevant, but do not stop at goods receipt. Map receipt verification, sampling availability, sample transfer, test execution, review and the authorised disposition event.

Not every stage is purely sequential. Some document checks can proceed while testing is underway; other tasks depend on an earlier result. Represent these dependencies accurately before summing durations. Adding every average together may overstate the interval, while assuming all activities run in parallel may understate it.

For API operations, ICH Q7 distinguishes received materials under quarantine from materials released after appropriate examination or testing. Apply that source within its API scope; the site's approved procedures determine the actual workflow and authority for each material. FDA ICH Q7 guidance.

Worked example from Monday receipt to Thursday usability

Consider an illustrative material receipt at 09:00 on Monday. Sampling is completed that afternoon. Testing finishes on Wednesday, and review and disposition are expected by 09:00 Thursday. Assume no unresolved issue arises and all required work is included in those estimates.

The planning interval from receipt to expected usability is three calendar days. A production requirement for Wednesday at 09:00 is therefore one day earlier than the expected usable date. The receipt-only model reports no shortage; the usable-date model reports a timing gap that needs a decision.

There are several possible responses. Procurement may find an earlier eligible lot already available. Production may move the batch if downstream commitments permit. QC may assess whether resources can be reassigned without disrupting more critical work. None of these actions implies that testing or review can be skipped to preserve the schedule.

If the next delivery has the same workflow and production genuinely needs material on Wednesday, the planner can propose a Sunday receipt in a calendar calculation. But if receiving or sampling does not operate on Sunday, that answer is infeasible. The correct backward plan must use the relevant departmental calendars, not a simple subtraction of three days.

This is why lead-time fields need both units and calendar rules. “Three days” could mean elapsed days, working days or three laboratory shifts. Record the definition and test it across weekends and holidays before using it to promise a batch start.

Estimate comparable work rather than a universal average

Build release histories from actual events: receipt, sample availability, test completion, review completion and disposition. Group records only where the work is reasonably comparable. Supplier, material family, test package and site may all affect the interval. Do not create so many groups that each estimate rests on one observation.

Keep unusual cases visible. A lengthy investigation is not the same process as routine queueing, but deleting it from history can make future plans overconfident. Maintain a routine estimate and a separate view of exceptions, with an explanation of what each is intended to predict.

For a simple illustrative history of five comparable lots with intervals of two, three, three, four and eight days, the median is three days and the mean is four. Neither figure alone explains the eight-day event. If it resulted from a missing supplier document, the response may be stronger pre-arrival checking rather than an extra day added to every order.

Use an interval or scenario where the decision is sensitive to uncertainty. A production promise that fails whenever release takes four instead of three days is fragile even if three is the historical median. The planner should see that exposure and choose a buffer or alternative deliberately.

Connect laboratory priorities to business consequences

An urgent flag on every sample provides no prioritisation. Give QC the affected production requirement, quantity, need date and available alternative. QC can then assess the queue with operational context while retaining control of the laboratory workflow.

Do not let sales priority automatically reorder regulated work. Some tasks cannot be interrupted safely or efficiently, and a newly urgent sample may require an instrument or analyst that is unavailable. The laboratory sample workflow guide explains how to expose these dependencies without reducing the laboratory to a promised finish date.

Track priority changes as events. If a sample is repeatedly advanced and delayed, the final turnaround time does not reveal the disruption imposed on other work. A useful queue review shows which requests changed priority, who requested the change and which other commitments moved as a result.

Handle partial quantities and changing status

MRP commonly works with product-level balances, but usability may depend on lot, container or quantity. If 600 kilograms arrive and only 400 are eligible under the authorised disposition, the model must not make the remaining 200 available because the receipt header appears complete.

Represent reservations against the usable quantity and release date applicable to the planned requirement. When a quality hold is introduced after planning, affected reservations and production proposals should be recalculated. Preserve the earlier plan for explanation, but clearly mark it as superseded.

Retest and expiry conditions also need explicit treatment. A lot that is currently usable may not remain eligible at the intended consumption date. The planning engine should evaluate the site's approved rules at that future date and refer unresolved questions to the responsible quality function. A date extension cannot be inferred from a convenient production slot.

These situations connect to material-shortage procurement and production scheduling. Keep the responsibilities distinct: procurement creates options, planning compares timing, and authorised quality decisions determine material eligibility.

Validate the planning behaviour before rollout

Test at least one ordinary receipt, a late sample, a review delay, a partial quantity and a material hold introduced after reservation. Include a failed interface. If the quality system cannot be reached, the MRP screen should show stale or unknown information rather than infer release from elapsed time.

Check time zones and event order where sites or suppliers operate in different locations. A release message arriving before an older receipt correction should not cause the integration to restore an obsolete status. Preserve source identifiers and timestamps so reconciliation can identify the actual sequence.

During the pilot, measure how often a planned batch waits for material that was already physically present. Separate the reasons: missing sampling capacity, instrument queue, review workload, documentation or an investigation. This identifies where an improvement would change the usable date instead of merely making a dashboard look faster.

NextEdge Labs can connect these milestones and build a planning view around them. The acceptance condition should be concrete: a planner can explain why a quantity is expected to be usable on a particular date and can see when that expectation changes.

Summary and next actions

MRP becomes more credible when it plans against material usability while retaining the authorised release state as a separate control. The most useful improvement is a visible chain of milestones, calendars and owners that explains the gap between receipt and production readiness.

• Map receipt, sampling, testing, review and disposition for one production-critical material family.
• Recalculate a recent shortage using usable dates and the correct departmental calendars.
• Build comparable release histories and inspect exceptions before choosing planning buffers.
• Test partial quantities, changed status and stale interfaces before relying on the new dates for production promises.