Agile manufacturing is the ability to respond to changing production needs while maintaining the requirements of the product and process. At cell level, a useful starting point is one bounded decision: when a machine, material or inspection resource becomes unavailable, which approved alternative can complete the work, and what evidence permits the change?
From networked machines to usable feedback
Sandia's work in the 1990s explored manufacturing equipment coordinated through software. The laboratory's August 1996 report, A CORBA-based manufacturing environment, describes its Agile Manufacturing Testbed, including common software interfaces, manual and automated operations, two-way information flow and a dynamic task sequencer.
The durable idea is that a manufacturing device can expose meaningful capabilities and state to the rest of the system. Shared information can support a change of plan. It still takes an explicit decision rule to determine whether the alternative is suitable for a particular job.
NIST's 2020 research on disruption and dynamic scheduling identifies integration and interpretation of diverse enterprise data as a central challenge. A connection becomes useful when its records describe the same jobs, resources and constraints consistently.
Establish the state that a decision needs
Give each job an identifier, quantity, released revision, route and completion requirement. Record which operations are complete, which are active and which are held. Distinguish a machine that is communicating from one available and qualified for the next operation.
On a narrow screen, scroll the table horizontally. Keyboard users can focus it and use the arrow keys.
| Constraint | Evidence | Consequence of a gap |
|---|---|---|
| Process capability | Released program, tooling and qualified route for this product | Engineering review before scheduling the route |
| Resources | Machine, operator, material, fixture and transport availability | Revise the predicted start or hold the proposal |
| Quality | Inspection capacity and unresolved product holds | Keep release gated by the actual requirement |
| Current state | Timestamps, job position and acknowledged commitments | Reconcile stale or conflicting information |
Set a review horizon and identify work already committed to equipment or operators. Preserve those commitments unless the responsible owner authorizes a change. A proposed schedule should state the assumptions that make it feasible.
Compare the whole remaining route
Fictional decision at 09:00: ten parts can wait 60 minutes for route A, then take six minutes each. Machining finishes after 60 + 10 × 6 = 120 minutes, at 11:00.
An already-qualified route B needs 25 minutes of setup and eight minutes per part: 25 + 10 × 8 = 105 minutes, at 10:45. Assume no other queues or interruptions in either machining calculation.
If required inspection becomes available at 11:15, both lots still await that resource at 11:15. B advances machining completion by 15 minutes, but this evidence alone establishes no earlier inspection release or shipment. Check inspection duration and all remaining work before changing the customer commitment.
Compare alternatives using accepted output and due-date performance, alongside setup effort and effects on other jobs. Include a feasible unchanged-plan option so the cost of rescheduling is visible.
Release one controlled change and learn from it
Record the selected schedule version, approval and acknowledgment at affected stations. Keep product holds and equipment protection within their authorized controls. A scheduling recommendation does not itself authorize a new machining recipe or override a machine interlock.
Rehearse delayed status messages, an unavailable alternative and a failure after partial completion. Define how work is located and reconciled during recovery. A simulation can help test the logic; compare its behavior with actual cell observations as described in virtual assembly lines.
After the change, compare predicted and observed start, completion and release times. Correct the assumptions that caused the difference and retain the evidence. Start with this manageable loop before extending coordination across additional cells.
Use the working record
Download the editable agile cell replanning record. Save a copy, complete the actual requirements and evidence fields, and review open issues with the responsible owner. The plain-text record includes instructions, units where needed, the fictional example, and source references.