Plan Analysis: Late Demand Diagnosis

Overview

You can use Rapid Planning late demand diagnosis to identify:

As it plans to satisfy a demand, the planning solver also searches these paths:

It finds these constraint failure conditions and reports them when it cannot wholly satisfy a demand due to any of these conditions:

You can simulate solutions and finds the best responses.

Constraints

In this example:

the picture is described in the document text

Intermediate Level Reporting

The planning solver reports the root or leaf cause of a delay

x

the picture is described in the document text

Partial Quantity Shortage Constraints

If the planning solver plans to satisfy partial quantities of a demand from multiple organizations, it reports failure constraints from all organizations involved.

In this example:

the picture is described in the document text

Material Constraint Caused by Resource Constraint

Sometimes, the report of a lead time material constraint is actually caused by resource unavailability. For example:

the picture is described in the document text

Process

The late demand diagnosis process is:

If you accept the latensses, continue analysis and release recommendations.

If you don't accept the latenesses, do this as many times as you need to accept the lateness. You can use more than one simulation plan and compare among them to choose the best solution:

You can see the late demand information in any planning mode, but the information is most relevant in mode Constrained – Enforce capacity constraints

Viewing

You see late demand information in the view Constraint Details.

Troubleshooting

Since the planning solver calculates constraints on all paths, it makes run times longer when you use it.

The planning solver exhausts all possibilities for solving a late demand only on the primary path.

To find all upstream constraints along the primary path, use view Constraints Detail, do a query-by-example and filter by search path Primary.