Setting up the production output location

This new functionality is available with KB 2995954 and will be included in Microsoft Dynamics AX2012 R3 CU8. To find the HF you can use LCS Issue Search.

What’s new?

To support an efficient process for putting away produced products, it is now possible to define an output location specific for a production or a batch order. This will enable the warehouse worker to exactly know where to go, to pick up the goods for put away.

The illustrations below shows the difference between the R3 and the CU8 implementation. The first illustration shows the R3 implementation where it was only possible to define one output location per warehouse:

The second illustration shows the CU8 implementation. In this implementation it is possible to set up an output location per production or batch order. This will give the warehouse worker a better overview of where to pick the finished products for final put away

This blog will explain how this new capability is enabled by using the official demo data released for Microsoft Dynamics AX 2012 R3 CU8 Virtual Machine (VM).

In the company USPI there is a formula for making Pellets. This formula will be used for showing how this feature is enabled and used.

The illustration below shows the Pellets production:

The item numbers for the ingredients (or raw materials) as MW4004 – Polypropylene and MW4005 – Rubber are pre-fixed with MW and the four end items are pre-fixed with PW. PW4000 – Pellets is the formula item, and PW4001 – Chips and PW4002 – Blocks are co-products. PW4003 – Slag is a by-product

Let us take a closer look how to enable this feature. First we need to set up the production output location. Looking at the route for the Pellets formula operation 40 DryFilling is the last operation:

An applicable output location for this operation is found through the Resource requirements for the operation. In the Resource requirements, criteria for finding an applicable resource or resource group during scheduling, is set up:

The output location is specified on the resource group, as it can be seen in the illustration below:

In case no output location is defined on the resource group, then a default production output location is used as a fallback location. This default output location is set up on the warehouse:

In the diagram below the defaulting hierarchy is shown. The diagram shows the rule that applies for finding the production output location when reporting as finished for a production or batch order:

Example

To see how this works, let us report as finished a quantity of the formula item PW4000 – Pellets. The batch order is in status Started and is ready to be reported as finished:

Reporting as finished is done from the mobile device:

Batch order number, Item number, quantity and license plate is entered:

And the process is completed and put away work is generated:

Taking a closer look at the put away work, the pick location for this work is FILL-01. This location is the output location that was set up on the resource group that is applicable for the last operation DryFilling

Let us try to remove the output location from the resource group and then report as finished one of the co-products from the batch order

We report as finished a co-product PW4002 – Blocks and put away work is generated

The put away work will in this case have the default output location OUTPUT. This location is the fallback location set up in the warehouse

The defaulting of the output location is enabled for all the places where the reporting as finished process can be performed. This includes

Using the report as finished function from the batch order
Using the report as finished journal
Reporting as finished from the job or route card journal. This is possible when user reports on last operation and marks the field Report as finished on the journal line
Report as finished from list page Current operations. This is possible when reporting as finished the last operation
Reporting as finished from the Job registration form in the manufacturing execution module (MES). This is possible when the user reports as finished the last operation

Summary

In CU8 it is now possible to set up an output location for the last operation in a production route. This supports a more efficient process for putting away produced products from the shop floor to the warehouse. The output location is set up on the resource group that is applicable for the route operation. A fallback output location set up on the warehouse is used in case no output location is defined on the resource group. Using the output location defined for the last operation in the production route is applicable for all the places where the report as finished process can be performed.

Working with Overlap in Microsoft Dynamics AX

Conducting Dynamics AX Manufacturing training for a class in Malaysia, it became clear that the current documentation on Overlap in Dynamics AX was not telling the full story.
Therefore, I decided to write this blog.

So, what is Transfer batch and Overlap quantity?

In Dynamics AX ‘Transfer batch’ is the field used to control an overlapped schedule. Apics define ‘Overlapped schedule’ as “A manufacturing schedule that overlaps successive operations. Overlapping occurs when the completed portion of an order at one work center is processed at one or more succeeding work centers before the pieces left behind are finished at the preceding work centers.”

Overlapped schedule is also known as lap phasing, operation overlapping, telescoping or send ahead.

‘Overlap quantity’ is a calculated field on the production order – ensuring that we avoid gaps in the schedule, when the successor operation to the operation with a Transfer batch value, has a shorter process time.
The ‘Overlap quantity’ determines the first transfer batch size for the operation; the following transfers to the next operation will use the ‘Transfer batch’ value.

Overlap quantity example

Say you have a production order for 10 pcs and it has two operations 10 and 20, each operation taking 2 minutes per pcs:

Without overlap:

Normally operation 20 will start when the entire quantity (10 pcs) has been processed on operation 10

With overlap:

When you have specified something in ‘Transfer batch’ field, let us say 2 pcs, it means the next operation (in our case 20) can already start when only 2 pcs has been processed on the operation 10. The value from ‘Transfer batch’ is by default copied to the ‘Overlap quantity’, on the production order.

Why does the Overlap quantity sometimes change when I estimate a production order?

The ‘Overlap quantity’ parameter on the production order route is calculated by the system. This is done during the estimation (or scheduling) of the production order, to prevent gaps in situations where a later operation have a shorter process time than the current operation. The fact that the successor would be waiting for the delivery from the predecessor would be causing a gap.
So, the calculation of an optimal ‘Overlap quantity’ is done based on the ‘Transfer batch’ and the operation process durations on the route.

Overlap example with gaps (two operations):

Say you have a production order for 10 pcs and it has two operations 10 and 20, this time the first operation takes more time than the second does:
Opr 10: 20 min per pcs
Opr 20: 10 min per pcs
Again, we have a Production order for 10 pcs and Transfer batch quantity set to 2 pcs

Without any change during Estimation the jobs on the route would have a gapped schedule and look like this:

However, as the first operation in total will take 200 min to complete and the second will take 100 min you will get the following information when estimating:

With the change from 2 to 6 we ensure that there are no gaps between the jobs in the second operation.

Overlap example with gaps (three operations):

Now let us spice it up a bit and add another operation – Opr. 30 with a run time of 5 min per pcs. We will also set a ‘Transfer batch’ = 4 on operation 20

In this case, you get the following information during estimation:

Now the schedule will look like this:

Therefore, by updating the ‘Overlap quantity’ on the production order during the Estimation Dynamics AX ensures that production on the following operation can happen without any gaps – avoiding a gapped schedule.

Christian Rytt, Senior Program Manager at Microsoft Development Center Copenhagen

AX2012 process manufacturing integrates to manufacturing execution

In previous versions it was not possible to collect data on shop floor for process manufactured products. Many customers use both process and discrete manufacturing capabilities in Dynamics AX in their environments regardless of whether they are generally dealing with process manufactured products or with assembled products. Therefore in AX2012 it was made possible to do data collection on products that were manufactured using formulae and batch orders. This post describes the context in which some decisions were made and also lists a number of enhancements to process manufacturing in AX2012 that make this possible.

Synchronous updates
Manufacturing execution in AX2012 is changed so that progress updates made on job registration are instantly updated in the production module. It is now possible to track the production progress within production module by viewing jobs and quantity form from production orders as soon as the progress entry is made. This is also extended to batch orders.

Job registration form
On the job registration form it is now possible to see operations or jobs depending on whether operation or job scheduling was run on batch orders. The setup required for this is described in the documentation here.
Since batch orders can produce multiple outputs, it is now possible to see these multiple outputs by shop floor worker on their terminal. This is made possible by allowing access to co-by products form from job registration form. It is possible to configure job registration form so the co-by products button appears here. Setup of action pane that is needed to set this up is described here.
It is now made possible to set up the action pane on job registration form so that linked quality orders to the batch order in progress can be seen from within the job registration form. This capability enables either shop floor worker or supervisor to easily access and see the status of quality orders for the batch order on which they are still recording progress.
It is now made possible to set up the action pane on job registration form so that linked non-conformances to the batch order in progress can be seen from within the job registration form. This capability enables either shop floor worker or supervisor see the associated non-conformances

Production status list page
This page is intended as an overview for shop floor supervisor. In previous versions it was not possible to see batch order jobs on this page.

In process manufacturing AX2012 it is possible to do the following.

View the batch order jobs,
View the formula connected to the batch order for which jobs are being displayed
View the non-conformances connected to the jobs being displayed
View the consolidated orders form, this form will show consolidated orders, bulk or pack orders that are related to the batch order that is currently in focus on production jobs list page
"Cancel finished report" button will cancel the quantity reported as finished against the batch order, just like in the case of production order

Report as finish
In AX2012 it is possible to report as finish multiple outputs through manufacturing execution. This is achieved by simply making it mandatory for the user to open up report as finish form while reporting quantity as finish. The report as finish form that opens up is standard form that is used for reporting against a batch order. So, all the capability of adding co-by products and reporting against already available multiple co-by products is possible just like through the production module.

Edit job lists form
This is a new form in AX2012 where it is possible to re-prioritize individual jobs. This allows greater flexibility on shop floor. None of the changes are synchronized with master planning and scheduling. Based on our research users wanted some capability to do this without the changes going through master planning and scheduling. Shop floor supervisors often change the resources or get asked to prioritize certain jobs and there wasn’t a way to capture such changes without running master planning. Running MRP is huge overhead, not in control of a single supervisor since it impacts larger site/organization and usually decisions of such an immediate timeframe should not be run through master planning. Therefore, this capability was added in AX2012 in Manufacturing execution module. This job prioritization can be done for individual jobs or multiple jobs. Jobs can be moved from one position to another in the queue. Resources allocated for a job can be also manually changed here if the allocated resource is not available for a short period for whatever reason. This capability is now also available for jobs originating from batch orders.

Inventory Picking
While picking for a batch order from manufacturing execution module, AX2012 ensures that picking is done in FEFO order is this is setup for the item being picked

Catch weight and production module
A number of new fields have been added to many forms. All forms that are used to process products and those that are used to show progress of products through shop floor have new fields to handle products that have dual unit of measure defined.

Forms that have been modified

Production journals
Route jobs form
Route form
Materials form

Grid setup for catch weight products
CW started quantity, CW start quantity and CW requested quantity are three new fields that can now be setup on the grid in the job registration form.

Catch weight and manufacturing execution module
Catch weight fields are now available on several forms so that products with dual unit of measure defined can be processed using the manufacturing execution module.

Forms that have been modified are:

Edit jobs list form
Change feedback form
Raw registrations form
Posted registrations form
Quantity reports form
Approve form

Hopefully this post introduces you to the changes made to allow shop floor workers to record progress against products that are being manufactured using batch orders and formulae.