You can simulate unanticipated events in the business environment and respond to them. By comparing multiple simulation plans with the baseline plan, you can make the best decision for execution.
You can do simulations by modeling changes in business conditions, for example, new demands, changes to supplies, and engineering change orders. The planning solver analyzes the impacts of these changes.
Use simulations if you:
Have frequent, unanticipated supply chain changes that occur in the near term
Want to do what-if scenario analysis, simulate responses, and compare scenarios before deciding on responses to these changes
Plan inputs: For example, items, bills of material and resources, to simulate, for example, engineering change orders, machine downtime
Plan data: Forecasts and supplies to simulate situations, for example, hot demand and late supplies.
You make these changes either:
Individually
Mass update: Multiple changes with one transaction
Change:
Plan inputs using simulation sets
Plan data using the views
This table compares the editing methods.
| Simulation Sets | Views |
|---|---|
| Changes apply to collected data | Changes apply to plan data |
| You can use the changes in multiple plans | You can use the changes in the changed plan only |
| You cannot edit supply and demand entities | You can edit supply and demand entities |
| Used to update key properties without updating ERP | Used for interactive simulation using a plan |
| See changes in the Plan Inputs tab | See changes in the views |
This table shows the entities that you can update.
| Entity Type | Create Rows | Duplicate Rows | Update Rows | Delete Rows |
|---|---|---|---|---|
| Items | No | No | Yes | No |
| Resources | No | Yes | Yes | No |
| Bill of Materials | No | Yes | Yes | No |
| Resource Availability | No | Yes | Yes | Yes |
| Resource Requirements | No | No | No | No |
| Calendar | No | Yes | Yes | No |
| Calendar Associations | Yes | Yes | Yes | No |
| Supplier | No | Yes | Yes | No |
| Processes | No | Yes | Yes | No |
| Supply and Demand | No | No | No | No |
This table shows the attributes that you can update.
| Entity | Attributes |
|---|---|
| Item | Maximum Order Quantity, Minimum Order Quantity, Fixed Lot Multiple, Fixed Order Quantity, Variable Lead Time, Fixed Lead Time, Preprocessing Lead Time, Processing Lead Time, Post-processing Lead Time |
| Resources | Units, Bottleneck Flag, Effective Date, Disable Date |
| Bill of Material | Assembly Quantity, Effective Date, Disable Date, Component, Substitute Component Item, Component Usage Quantity, Component Yield, Substitute Priority, Substitute Quantity, Substitute Item UOM |
| Resource Availability | Shift, Shift Date, Assigned Units, Start Time, End Time |
| Calendar | Status |
| Calendar Associations | Association Type |
| Supplier | Processing Lead Time, Last Change Date / Time, Changed by, Minimum Order Quantity, From Date, To Date, Capacity, FLM |
| Processes | Effective Date, Disable Date, Operation Effective Date, Operation Disable Date, Resource, Alternate Routing, Replacement Group, Alternate Resource, Assigned Units, Rate or Amount, Operation Yield |
After the collected data arrives, you can use it unchanged to run through a plan
You can change it using either:
Direct changes
Simulation sets
You can change data as changes in your manufacturing environment occur by individually updating or mass updating a plan or a copy of a plan. You do not have to make the changes in the source system and re-collect them.
You can use these changes to visualize your supply and demand picture:
Before: A current plan
After: A simulation plan that includes the simulated data. This can be a copy of the current plan
Edit plan data in order to evaluate their impact on the plan.
To make direct edit changes:
Navigate to a data area tab
Do not enter a simulation set name in the view's Search Area
Type over the data that you want to change or use a mass update. See Mass Update.
You do not need to make direct updates for a plan run to use your changes. You can update data in the Rapid Planning views and store your changes in a simulation set. If you make individual updates and mass updates to a simulation set and run a plan with the simulation set, the planning solver uses the changes from your simulation set. The changes are not permanently in the plan, they are in the simulation set. See Editing Plan Input (Collected) Data – Simulation Sets.
If you make individual updates and mass updates to a plan and run it, the planning solver uses your changes. The edits only apply to that plan and are permanently in the plan, unless you manually undo each one. They are neither in a simulation set nor saved to the database.
This table shows the edits that you can make in the Supply & Demand view.
| Order Type | Editable Field | Default Value |
|---|---|---|
| Planned Order | Firm Status | Firm |
| Firm Date | Value from field Sugg Due Date | |
| Firm Quantity | Value from field Quantity | |
| Alternate BOM | ||
| Alternate Routing | ||
| Source Organization | ||
| Source Supplier | ||
| Source Supplier Site | ||
| Purchase Order / Purchase Requisition | Firm Status | Firm |
| Firm Date | Value from field Sugg Due Date | |
| Firm Quantity | Value from field Quantity | |
| Source Organization | ||
| Source Supplier | ||
| Source Supplier Site | ||
| Work Order | Firm Status | Firm |
| Firm Date | Value from field Sugg Due Date | |
| Firm Quantity | Value from field Quantity | |
| Alternate BOM | ||
| Alternate Routing | ||
| Forecast | Firm Status | Firm |
| Firm Date | Value from field Sugg Due Date | |
| Firm Quantity | Value from field Quantity | |
| Order Priority | ||
| Sales Order | Firm Status | Firm |
| Firm Date | Value from field Sugg Due Date | |
| Firm Quantity | Value from field Quantity | |
| Order Priority |
After you edit plan data, you can re-run a plan without refreshing snapshot data. When you start plan action Launch Plan, select Launch Plan, do not refresh snapshot.
Use simulation sets to modify plan inputs and evaluate their impact on the plan. You can use one simulation set can be given as input to a particular plan. One simulation set can include changes to multiple entities.
You do not need to store your changes in a simulation set for a plan run to use them. You can update data in the Rapid Planning views and not name a simulation set (direct updates). If you make direct individual updates and mass updates to a plan and run it, the planning solver uses your changes. The changes are permanently in the plan. See Editing Plan Input (Collected) Data – Direct Change.
If you save plan changes in a simulation set, they are separate from the collected data and do not change the collected data. You can apply them again later to that plan or to another plan. Plan runs start with the collected data and write over it with the data in their simulation set.
You can begin to work with simulation sets by navigating to a data area tab.
Simulation Set Exists for the View
If the view already has changes into a simulation set, you see:
There is an entry in tab Plan Inputs, Manage Simulation Sets
The column Simulation Set has value Collected Data. If the tab has changed rows that you saved in a simulation set, that column shows the simulation set name.
Simulation Set is a criterion in the search area. All of the rows of the tab display and the simulation set rows are in blue highlight.
You can continue to make changes into the simulation set.
Starting with a New Simulation Set
If you are making changes into a simulation set for the first time, you:
Make a simulation set
Make changes into it
Simulation Set Operations
To make a simulation set:
Click Manage Simulation Sets
In window Manage Simulation Sets, click icon Add New
In the new blank row, enter the new simulation set name
To make changes into a simulation set:
Verify that there is a simulation set name in the view's Search Area
Type over the data that you want to change or use a mass update. See Mass Update.
To rename a simulation set:
Click Manage Simulation Sets
In window Manage Simulation Sets, select the row with the name of the simulation set to rename
Type the new name in the same row
To make a copy of a simulation set:
Click Manage Simulation Sets
In window Manage Simulation Sets, select the row with the name of the simulation set to make a copy of
Click icon Duplicate
The copied simulation set appears with name Duplicate of <original simulation set name>. You can rename it.
You can set a simulation set as a default. Every time you make a mass change, the Update Data window:
Applies the default simulation set to the data
Fills field Simulation Set with the default simulation set name. The mass update changes will go to the default simulation set unless you select another simulation set name before you OK the mass change
When you add or duplicate a row in a tab and want to store it in a simulation set, select the simulation set that you want as the value for column Simulation Set.
You can perform a mass update that includes rows from the simulation set:
If you want to save these latest changes in a simulation set, when you are in window Update Data for the mass change, click button Manage Simulation Sets
Changed data appears in new rows
You can change changed data in an individual update but not in another mass update
You can delete rows from a simulation set just as you can from the collected data.
You may save changes in a simulation set, recollect the data, and then apply the simulation set to the recollected data. There can be changes in the simulation set that changed a row from the previous collection, but that row is not in the current collection. The tab displays these simulation set changes as deleted rows (red text with strikethrough and a red flag.
To delete a new simulation set:
Click Manage Simulation Sets
In window Manage Simulation Sets, select the row with the name of the simulation set to delete
Click icon Delete
Applying Simulation Sets
You can apply one simulation set to a plan for each run.
When you want to apply a simulation set to a plan, enter its name in plan option Simulation Set.
The planning solver applies all the simulation set changes to the plan data before it begins solving supply and demand.
When the plan finishes, you can see the simulation set entities in the data area tabs as new rows.
Use incremental planning for hot demands. Incremental planning does not re-snapshot planning data.
The incremental plan freezes all:
Supplies
Planned orders
Resource capacity consumption
Supplier capacity consumption
Pegging relationships
The planning solver only changes plan output to:
Create and reshuffle supplies to meet the hot demand and determine when you can meet it
Recalculate all exception messages
If there are multiple hot demands, the planning solver plans by:
Highest demand priority
Then by earliest due date
Then by lowest quantity
See Define Incremental Replan Scope.
If the incremental plan output is not satisfactory, run a replan; do not run multiple incremental planning runs.
Run plan launch either with or without snapshot.
When you re-run with snapshot, the planning solver starts over with the collected data. However, the planning solver does not write snapshot data over your manual changes in the simulation set.
Use multi-planner collaboration if:
Your business has multiple planners
They work independently on different parts of the plan
They each want to easily save their changes either together or separately
This is how Oracle Rapid Planning processes data when more than one planner is working on the same plan:
Their saved changes are visible to one another
A save or undo of changes by one planner saves or undoes the changes of all the planners
A re-plan run by one planner locks out all planners from making changes to that plan
If two planners are changing the same entity, the last one's change holds
When one planner releases planned orders, the planned order information may not include unsaved changes by another planner. For example, a planner has mass-edited supplier capacity but not saved the changes. When another planner then releases planned orders, they are based on the previous supplier capacity.
Saving to Simulation Sets
Each planner can save their changes to a simulation set.
If you don't select any changed records, all your changes go into the simulation set. If you select changed records, only those changes go into the simulation set.
Use view action Save to Set or menu Plan Actions > Save to Simulation Set:
You can perform all the simulation set actions.
If you can update an entity in the views, you can save the entity to a simulation set.
If you change a field in a record, the save process saves the entire records, not just the field that changed. When the plan runs and applies the simulation set, it applies to all fields from the last chronological update of the record.
When two planners update the same record at different times, the second updater's view may not display the field updates of the first updater. If so, the planning solver loses the first updater's field changes when it applies the second updater's record.
Simulation Set Configuration
All planners can save their changes to one simulation set. If multiple planners change the same information, the planning solver uses the last chronological change. Use this method if you want to consolidate all changes to apply to the next run of the plan.
Each planner can save their changes to different simulation sets. Use this method if each planner wants to run independent simulation on their part of the plan.
Planners can save changes from multiple plans to the same simulation set. Use this method if planners are working with copies of the base plan but want to save changes to apply in the next run of the base plans.
Multi-planner Example
This table shows a collected engineering change order cut-over in tab Plan Inputs
| Simulation Set | End Item | Component | Effective Start | Effective End |
|---|---|---|---|---|
| Collected Data | AS66311 | CM66331 | - | Jan 7 |
| Collected Data | AS66311 | CM66331New | Jan 8 | - |
The planner does some simulations, decides that a later cut-over is better, and enters that decision in the Bill of Materials view. The planner saves the changes to simulation set MySimSet. The data in tab Plan Inputs changes.
| Simulation Set | End Item | Component | Effective Start | Effective End | Last Updated By | Last Updated Date and Time |
|---|---|---|---|---|---|---|
| Collected Data | AS66311 | CM66331 | - | Jan 7 | Planner 1 | 09/12/08 00:00 |
| Collected Data | AS66311 | CM66331New | Jan 8 | - | Planner 1 | 09/12/08 00:00 |
| Collected Data | AS66311 | CM11222 | - | Jan 15 | Planner 1 | 09/12/08 00:00 |
| Collected Data | AS66311 | CM11222 | Jan 16 | - | Planner 1 | 09/12/08 00:00 |
| MySimSet | AS66311 | CM66331 | - | Jan 31 | Planner 1 | 09/12/08 00:10 |
| MySimSet | AS66311 | CM66331New | Feb 1 | - | Planner 1 | 09/12/08 00:10 |
Another planner can save changes to the same simulation set.
| Simulation Set | End Item | Component | Effective Start | Effective End | Last Updated By | Last Updated Date and Time |
|---|---|---|---|---|---|---|
| Collected Data | AS66311 | CM66331 | - | Jan 7 | Planner 1 | 09/12/08 00:00 |
| Collected Data | AS66311 | CM66331New | Jan 8 | - | Planner 1 | 09/12/08 00:00 |
| Collected Data | AS66311 | CM11222 | - | Jan 15 | Planner 1 | 09/12/08 00:00 |
| Collected Data | AS66311 | CM11222 | Jan 16 | - | Planner 1 | 09/12/08 00:00 |
| MySimSet | AS66311 | CM66331 | - | Jan 31 | Planner 1 | 09/12/08 00:10 |
| MySimSet | AS66311 | CM66331New | Feb 1 | - | Planner 1 | 09/12/08 00:10 |
| MySimSet | AS66311 | CM11222 | - | Feb 14 | Planner 2 | 09/12/08 00:20 |
| MySimSet | AS66311 | CM11222New | Feb 15 | - | Planner 2 | 09/12/08 00:10 |
However, if the other planner saves changes to the same data that the original planner saved changes to, the simulation set only keeps the changes from the other planner
| Simulation Set | End Item | Component | Effective Start | Effective End | Last Updated By | Last Updated Date and Time |
|---|---|---|---|---|---|---|
| Collected Data | AS66311 | CM66331 | - | Jan 7 | Planner 1 | 09/12/08 00:00 |
| Collected Data | AS66311 | CM66331New | Jan 8 | - | Planner 1 | 09/12/08 00:00 |
| Collected Data | AS66311 | CM11222 | - | Jan 15 | Planner 1 | 09/12/08 00:00 |
| Collected Data | AS66311 | CM11222 | Jan 16 | - | Planner 1 | 09/12/08 00:00 |
| MySimSet | AS66311 | CM66331 | - | Jan 25 | Planner 2 | 09/12/08 00:10 |
| MySimSet | AS66311 | CM66331New | Jan 26 | - | Planner 2 | 09/12/08 00:10 |
Use this if you have changing demand priorities that do not conform to consistent rules and you receive hot demands. You can mass update demand priorities without rerunning the planning solver snapshot.
You can use this functionality in unconstrained and constrained plans.
If you do have consistent demand priorities and do not receive hot demands, either:
Set them on sales orders in the execution (source) system and collect them
Use demand priority rules
Process
Use an original plan--a new plan or one launched with refresh Snapshot.
Make a copy (destination plan). Use concurrent request Copy Simulation Plan.
Extract demands from the copy plan. Your business must write a query to extract the demand IDs and attributes that you want into a spreadsheet.
Update demand priorities. You must upload them to the Planning Data Store:
This table has columns – Plan ID, Demand ID, Firm Date, and Order Priority.
Both Plan ID and Demand ID: need foreign key references to their corresponding columns in table msc_demands.
You can only load priorities for demands that are in the plan. Plan ID-Demand ID of the updated demand must match Plan ID-Demand ID of a demand in the plan.
The table does not keep history.
Launch the copy plan:
Select option Use Mass Updated Demand Priorities.
Do not refresh snapshot. Select either Incremental Replan or Launch Plan, do not refresh snapshot. If you select Incremental Plan, use incremental replan scopes: Freeze selected Supplies / Replan all demand or Freeze all except selected supplies, Replan all demands.
If you need to refresh snapshot, use concurrent process Launch Simulation Planner. See Launch Plan, Schedule a Plan Run. For both parameters Launch Snapshot and Use Mass updated Demand Priorities, use their default values Yes. For Launch Snapshot, if you select No, you must have run the plan with snapshot at least once before.
Analyzing and Viewing
After the copy plan launch finishes, compare the original and the copy plan.
In view Supply/Demand, you can see, the new priority information in columns Order Priority and Firm Date.
The process updates Suggested Due Date based on the new demand priorities. It keeps the original Suggested Due Date (from the first refresh snapshot run) in column Original Due Date. If you've run a plan without snapshot, Original Due Date does not change, even if you change Firm Date.
If you want to adjust some of the demand priorities in the completed copy plan, you can in view Supply/Demand both by direct update and mass update.
You use Oracle Advanced Supply Chain Planning and Oracle Rapid Planning together to respond to unanticipated events between Advanced Supply Chain Planning runs. Use Rapid Planning to simulate prospective changes that address these unanticipated issues. Choose a solution, then release it to the execution system and feed it back to Advanced Supply Chain Planning.
Simulate Advanced Supply Chain Planning plans in Rapid Planning if you:
Use Advanced Supply Chain Planning
Have frequent, unanticipated supply chain changes that occur between Advanced Supply Chain Planning plan runs
Want to do what-if scenario analysis, simulate responses, and compare scenarios before deciding on responses to these changes
Typically, businesses run Advanced Supply Chain Planning plan as a nightly job. The next morning, the planner validates the plan output, takes corrective action, and releases orders to the execution system.
During the day, if any dynamic changes occur, for example, to demands, supplies, resources, bills of material, and routings, the planner can see the effects of these changes. Simulate these changes using Rapid Planning plans.
See also Rapid Planning and Advanced Supply Chain Planning.
This table describes the simulation process.
| Oracle Advanced Supply Chain Planning | Oracle Rapid Planning |
|---|---|
| Enable simulations | |
| Run plan | - |
| Edit and firm order dates | -- |
| Release orders to execution | -- |
| There are unanticipated events that cause production issues before the next plan run. . . | -- |
| Copy Advanced Supply Chain Planning plan as Rapid Planning baseline plan (once, either from Advanced Supply Chain Planning or Rapid Planning) | Copy Advanced Supply Chain Planning plan as Rapid Planning baseline plan (once, either from Advanced Supply Chain Planning or Rapid Planning) |
| -- | Do this as many times as you need to simulate potential solutions and select a solution: |
| -- | - Copy the baseline plan to a simulation plan |
| -- | - Make changes to the simulation plan |
| -- | - Firm a portion of the simulation plan |
| -- | - Run the simulation plan |
| -- | - Compare the baseline and the simulation results |
| -- | Release orders |
| -- | Firm orders |
| Run the plan and specify the Rapid Planning simulation plan that you used to solve the issue and released orders from. | -- |
See Oracle Advanced Supply Chain Planning Implementation and User's Guide.
See Oracle Advanced Supply Chain Planning Implementation and User's Guide.
See Oracle Advanced Supply Chain Planning Implementation and User's Guide.
Navigate to Copy Plan.
In Copy From, select Plan Type ASCP
In Copy To, select Plan Type Rapid Planning. If it is a new plan, enter Description, Simulation Horizon (Days), and Category Set.
If the plan exists, you receive a warning.
You can create the baseline Rapid Planning plan from an Advanced Supply Chain Planning plan using these methods:
In Advanced Supply Chain Planning: Menu, Open Simulation
In Rapid Planning: Process, Copy Plan
Supplies inside the simulation horizon that peg to demands outside the simulation horizon disappear from the baseline plan.
Baseline Entities
The baseline creation process replicates the Advanced Supply Chain Planning plan with these entities.
End demands
Supplies: Dates and quantities. However, it does not copy orders made by Global Order Promising.
Details for planned orders and their dependent demands
Make: Bill of material, routing, resources, operation start and end dates, resource requirement start and end dates, components, and component requirement dates
Buy: Supplier, supplier site, and ship method
Transfer: Source organization and ship method
Details for scheduled receipts and their dependent demands:
Work orders: Bill of material, routing, resources, operation start and end dates, resource requirement start and end dates, components, and component requirement dates
External purchase orders and purchase requisitions: Supplier, supplier site, and ship method
Internal purchase orders and purchase requisitions: Source organization and ship method
Safety stock
It depends on how you select the Advanced Supply Chain Planning organization-level plan options Plan Safety Stock
You check it for at least one organization: The process sets Rapid Planning plan option Safety stock lead time method to Safety Stock Quantity and uses the safety stock quantities from the Advanced Supply Chain Planning plan.
You clear it for all organizations: The process sets Rapid Planning plan option Safety stock lead time method to Do not compute safety stock.
For setting Advanced Supply Chain Planning plan option Plan Safety Stock, Oracle recommends that you either select it for all organizations or clear it for all organizations.
Copy plan options and set defaults for some non-Advanced Supply Chain Planning plan Options that are not present in ASCP
Run the Rapid Planning snapshot process to load the static data.
Load all end demands and supplies—scheduled receipts and planned orders--within the simulation horizon. If you have supplies within the Rapid Planning planning horizon that peg to demands outside the Rapid Planning planning horizon, the supplies disappear. Oracle recommends that you set your Rapid Planning planning horizon to:
At least 30 days after your last supply order due date
A length where you can see the information that you need, but where you can ignore the plan results of the final 30 to 45 days, in case orders disappear.
Set the firm flag on all the supplies to Yes. The planning solver does not change order dates.
Set all planning time fences to the end of the Rapid Planning planning horizon. The planning solver does not create supply.
Run the planning solver to:
Make resource and material requirements the orders
Peg demands to supplies
Issue exceptions
Calculate Exceptions/KPIs
Unfirm the artificially firmed supplies and reset all artificially set planning time fences.
The Rapid Planning plan shows the name of the Advanced Supply Chain Planning plan.
In tab Main, you can change these plan options:
ATP Enabled
Category Set
Use for S&OP
Plan Security Attributes
In tab Organizations, the sections show the organizations and global demand, demand, and supply schedules from the Advanced Supply Chain Planning plan.
Tab Advanced shows the profile option values from the Advanced Supply Chain Planning plan.
This is how process Create Baseline Plans sets supply order attributes and what you can do with the supply orders in Rapid Planning.
For firm supplies, the process makes dependent component requirements and resource requirements firm as well.
| Oracle Advanced Supply Chain Planning Supply | Oracle Rapid Planning Supply |
|---|---|
| Scheduled receipt – No change recommended | It inherits firm status from Advanced Supply Chain Planning and has Action = None. You can plan it in a Rapid Planning simulation and release its recommendation. |
| Scheduled receipt – Change recommended and not released | It inherits Firm = No and Action = Release. You can either: - Release the Advanced Supply Chain Planning recommendation straightaway - Plan it in a Rapid Planning simulation and release its recommendation |
| Scheduled receipt – Change recommended and released | It inherits Implement Firm, Action = None, and Suggested Due Date = Implement Date You can either: - Leave it alone - Unfirm it, plan it in a Rapid Planning simulation, and release its recommendation |
| Planned order – Unreleased and unfirm | It inherits Firm = No and Action = Release. You can either: - Release the Advanced Supply Chain Planning recommendation straightaway - Replace it by planning it in a Rapid Planning simulation |
| Planned order – Unreleased and firm | It inherits Firm = Yes and Action = Release. You can either: - Leave it alone - Release it straightaway - Unfirm it, plan it in a Rapid Planning simulation, and release its recommendation |
| Planned order – Released | Inherits Firm = Yes, Suggested Due Date = Implement Date, and Action = None. You can modify the firm flag. When you plan a simulation, Rapid Planning removes it, unless it is part of the simulation scope. Oracle recommends that you do not do this--if you rerun the plan, it plans another, you might accidentally release it, and you order double production. |
You can't run the snapshot for these plans
You must replan in either of these modes:
Incremental Replan
Launch Plan, do not refresh snapshot
See Define Incremental Replan Scope.
Use the Analytics view to compare supply orders between the baseline plan and the simulation plans.
Navigate to tab Metrics. Attend to these metrics:
Total Supply Quantity
Planned Order Quantity
Make Planned Order Quantity
Transfer Planned Order Quantity
Buy Planned Order Quantity
Work Order Quantity
Purchase Orders / Requisition Quant
Internal Purchase Orders / Requisition Quantity
Total Demand Quantity
Forecast Quantity
Sales Order Quantity
See Base Metrics.
Navigate to tab Order Comparison, subtab Supply Order Comparison. You can see comparison between purchase orders, purchase requisitions, and work orders. It reports are:
Action changes: For example, cancelled orders vs non-cancelled orders, rescheduled orders vs non-rescheduled orders, and have an action vs do not have an action.
Due date changes (Available Date + [Equal To, Less Than, or Greater Than]): Supply Due Dates between scheduled receipts are outside the range. For example, Available Date + greater than 10 = all supply order pairs with Supply Due Dates more than ten days apart.
It does not report planned orders.
In the simulation plan that you use to solve the issue, release orders to the execution system.
In the simulation plan that you use to solve the issue, firm the planned orders that you released.
They become firm planned orders when you pass them to the next Advanced Supply Chain Planning run.
Feed back the results of your Rapid Planning simulation decision to the next Advanced Supply Chain Planning plan run.
See Oracle Advanced Supply Chain Planning Implementation and User's Guide.
You can purge Advanced Supply Planning plans that have baseline and simulation Rapid Planning plans.
The Rapid Planning plans remain but don't have reference to a baseline plan and don't have any of the restrictions of a baseline plan.
Advanced Supply Chan Planning can plan to the minute level. It can model detailed shop floor constraints such as sequence dependent setups, hard links.
Rapid Planning plans at the day level. You use it to get a rapid response to changes in plan inputs and data without needing to respect all of the detailed constraints.
In constrained plans, Rapid Planning always plans in Enforce capacity constraints mode. If you will compare Rapid Planning and Advanced Supply Chain Planning output, run the Advanced Supply Chan Planning plan as Constrained – Enforce capacity constraints.
Rapid Planning has a global parameter to control safety stock. Advanced Supply Chain Planning has organization-level control. If you will compare Rapid Planning and Advanced Supply Chan Planning output, set the Advanced Supply Chain Planning plan safety stock parameter in each plan organization to be the same as the Rapid Planning parameter.
If you use any of these modeling constructs and constraints in the Advanced Supply Chain Planning plan, the Rapid Planning and Advanced Supply Chan Planning output will be very different:
Process manufacturing organizations
Project manufacturing organizations
Flow routings
Batchable resources
Transportation capacity
Fixed days supply order modifier
Percentage based sourcing splits
Product family level planning
Bill of resources planning
Phantom items
Copying a plan from ASCP to RP loads only the demand and supply within the simulation horizon. Keep the simulation horizon large enough to minimize end-of-horizon effects. For example, if you want to simulate for 30 days and cumulative lead-time is 15 days, Oracle recommends that you set the horizon to 45 days. The demands within the simulation horizon will use supplies up to 30 days; otherwise the planning solver may drop them.
This is a possible scenario for processing a hot demand.
You have a production plan.
You receive information on a hot demand.
Copy your production plan to a new plan named Hot Demand.
View the Supply Chain Bill for the demanded item.
Navigate to the Material Plan view. Note the supply, demand, and projected available balance.
Navigate to the Supply/Demand view, enter the hot demand, and assign it a high priority.
Re-navigate to the Material Plan view and notice the impact of the hot demand, including the negative projected available balance.
Save the Hot Demand plan.
Run plan Hot Demand without changing current orders.
Note that the planned date for the hot demand is unacceptably late.
Re-run plan Hot Demand with the ability to change current orders.
Review key performance indicators, favorites, and order comparison information between the production plan and the Hot Demand plan.
If the Hot Demand plan is the more acceptable plan, release planned orders from it.
This is a possible scenario for processing an engineering change order cut-in.
You have a production plan.
You receive information on a phase out-phase in bill of material change
Copy your production plan to a new plan named ECO Change 1.
Navigate to the Bill of Material view and modify the bill of material by changing the effectivity dates.
Run plan ECO Change 1.
Navigate to the Horizontal Plan screen and review the projected available balance for the two components. Check for a large final projected available balance on the phase-out component.
Compare key metrics, for example, excess inventory monetary value and late days, between the production plan and plan ECO Change 1.
If there is, for example, unacceptable excess inventory monetary value, copy your plan ECO Change 1 to a new plan named ECO Change 2.
Re-navigate to the Bill of Material Edit/Update screen and modify the bill of material with a new cut-in date.
Run plan ECO Change 2.
Navigate to the Material Plan view and review the projected available balance for the two components.
Compare key metrics, for example, excess inventory monetary value and late days, between the plan ECP Change 1 and plan ECO Change 2
Release planned orders from the more acceptable ECO Change plan.
This is a possible scenario for processing a yield bust.
You have a production plan.
You receive information on a reduction in inventory by 100 pieces due to a yield bust.
Copy your production plan to a new plan named Supply Change
Navigate to the Supply/Demand view and lower the inventory by 100 pieces.
Navigate to the Material Plan view and note the projected available balance change.
Run plan Supply Change.
Compare key metrics between the production plan and plan Supply Change.
If you find that the results from the Supply Change plan are unacceptable, check alternate components and find one with supplier capacity of 100 per day.
Negotiate with your supplier for supply of an alternate component.
Re-run plan Supply Change.
Re-compare key metrics between the production plan and plan Supply Change.
If the Supply Change plan is the more acceptable plan, release planned orders from it.
This is a possible scenario for processing a resource downtime.
You have a production plan.
You receive information on a down bottleneck resource for all of next week.
Copy your production plan to a new plan named Resource Downtime.
Navigate to the Resource Availability view and decrease the resource availability for next week to zero.
Run plan Resource Downtime
Compare key metrics between the production plan and plan Resource Downtime.
If you find that the results from the Resource Downtime plan are unacceptable, check alternate resources.
Negotiate for overtime on an alternate resource for next week.
Re-navigate to the Resource Capacity view and increase the alternate resource availability for next week by 20%.
Re-run plan Resource Downtime.
Re-compare key metrics between the production plan and plan Resource Downtime
If the Resource Downtime plan is the more acceptable plan, release planned orders from it.