Templates may be integrated with templates setup in ERP or manually setup as described below. They may also be manually uploaded as documented here: Co-Product Template (coproducttemplate.txt)

For Plex ERP customers, Dynamic Multi-Outs need to be setup in order to integrate with DemandCaster.

1. Click "Utilities"
2. Click "Planning Templates"
3. Click "Add New"

There are two planning template options: Batching and Co-Product. To learn about batching, please review the Batching article.

1. Select "Co-Product"
2. Enter the "Name" of the template
3. Then click "Filter" to select the sku's to include in the Co-Product template

1. Click the + icon to add a SKU to the template
2. Enter the multiple of the SKU within the template. The multiple determine how many parts are produced with each production cycle.
3. Determine if the template for the given SKU is its primary template. As a note, if a SKU has not been assigned a primary template it will automatically be assigned as a primary. For example, the third line had been issued to a template previously thus it is not assigned as a primary within this template. If you assign it as a primary, it will be automatically removed as a primary from the other template.
4. Once all SKU's have been assigned, click the back button to save the template.

An asterisks displays which co-product template is the primary for a given SKU.

The rows in a Co-Product template selection page are marked in yellow in one of the following situations:

1. The SKU is already selected in the same template.

2. The SKU is selected in a batching template.

3. The SKU's location is different than the one already selected in this template.

The logic works on a FIFO basis. Upon running a new requirement plan, the first SKU required sets the template to be used based on its primary template. It will then create requirements for all the other SKU's included in the template based on the multiplier value for each part.

If other SKU's in the template have minimums or batch sizes greater than the primary SKU, the quantities will be adjusted accordingly.

Consider the example below. A template has been created where SKU A, B, and C are included and each SKU assigned multiples. Each SKU are produced from the same raw material.

The requirement plan is run and the requirements for each SKU is generated with the following results.

Since Item A is needed first it will set the first order and the other SKU's will be brought forward with the appropriate multiples and their requirements recalculated for each subsequent planning bucket. This does mean the other items will be produced earlier than needed.

The multiplier is reviewed to ensure the output of each is balanced for each period. On September 2^nd, since item B’s requirement increases to 75, item A’s and C’s quantities will also increase by the appropriate multipliers.

The sum of the above will set the requirements for the raw material offset by lead time. Each item will explode its requirements based on its BOM quantity. This is the standard MRP explosion.

The sum of the above sets the raw material requirements

Upon running the requirement plan, the resulting co-product plans will be available in the drop down of the planner action and visible in the Batch column.