SUPPLY CHAIN PLANNING RELEASE CONTENT DOCUMENT

Release 11i10 Oracle Production Scheduling and Oracle Strategic Network Optimization Integration v2 to Oracle E-Business Suite

Prepared by the Supply Chain Planning Product Management Team

Last Updated: Version:

May 6, 2009 1.0

Copyright 2009 Oracle Corporation All Rights Reserved

Table of Contents

1. 2.
2.1.

Disclaimer Introduction
Purpose of Document

1 2
2

3.
3.1. 3.2.

Supply Chain Planning

Overview Oracle Strategic Network Optimization
3.2.1. New Features 3.2.1.1. Supply Chain Risk Management 3.2.1.2. Alerts 3.2.1.3. Key Performance Indicators 3.2.1.4. SNO Integration Enhancements 3.2.1.5. SNO Usability Enhancements

3
3 4
4 4 4 6 9 12

3.3.

Oracle Production Scheduling

14

3.3.1. New Features 14 3.3.1.1. Ability to Specify a Unit of Measure on Items 14 3.3.1.2. Enhanced Alerts 14 3.3.1.3. Work Order Centric KPI Comparisons 15 3.3.1.4. Ability to Open Operation and Routings from Operation Instances 16 3.3.1.5. Ability to Auto Create Work Orders Directly from Demands in the Supply and Demand Editor 16 3.3.1.6. Find Functionality for Model Objects 17 3.3.1.7. Provide an Indication that a Demand is Partially Fulfilled by both Starting Inventory and Production 17 3.3.1.8. Automatic Reconciliation of Schedule Backlog 18 3.3.1.9. Batchable Resources 19 3.3.1.10. Consistent Resource Assignment within a User-defined Group of Operations within a Routing 20 3.3.1.11. Resource-specific User Definable Cycle Times for Campaign Run Optimization 22 3.3.1.12. Address Infeasibilities for Firmed Work Order Operations Outside of the Fixed Timefence 22 3.3.1.13. Disable Units of Effort for Setup and Cleanup Operations on Work Orders 24 3.3.1.14. Resource All of Sets 25 3.3.1.15. Hard Links between Work Orders 28 3.3.1.16. Dynamic Throughput Rates on Resources 30 3.3.1.17. Production Scheduling Data Connector Port to Sun, HP, and AIX 32 3.3.1.18. Ability to Export Selected Model Data during Schedule Publish 32 3.3.1.19. PS XML Model Unique Extension 33 3.3.1.20. Enhancements to Auto-generated Routings 33 3.3.1.21. Selective Work Order Release to Production 34

Supply Chain Planning Release Content Document

ii

1.

Disclaimer
This Release Content Document (RCD) describes product features that are proposed for the specified release of the Oracle Production Scheduling and Strategic Network Optimization new features. This document describes new or changed functionality only. Existing functionality from prior point releases is not described. It is intended solely to help you assess the business benefits of upgrading to this release. This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement, which has been executed and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle. Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking significant destabilization of the code.

Supply Chain Planning Release Content Document

Advanced Planning

2.

Introduction
2.1. Purpose of Document
This document describes the new features that are available with Oracle Production Scheduling and Oracle Strategic Network Optimization Integration v2 to Oracle EBusiness Suite. Oracle Production Scheduling and Oracle Strategic Network Optimization are available for both JD Edwards EnterpriseOne ERP and Oracle EBusiness Suite customers. The integration flows are different, but the core product capabilities for Production Scheduling and Strategic Netowrk Optimization are the same. Integration v2 incorporates the latest versions of Production Scheduling and Strategic Network Optimizaton which are 11i10 for E-Business Suite customers and 8.12.1 for JD Edwards customers.

Supply Chain Planning Release Content Document

Advanced Planning

3.

Supply Chain Planning

3.1. Overview
The major themes for the 11i10 releases of Oracle Production Scheduling and Oracle Strategic Network Optimization are: Usability ERP installed base customers expect that additional products associated with the ERP system will not require substantial implementation and maintenance costs. It is important that the SCP products solve their intended problems efficiently from a customer perspective. They should be easy to use and not impose a significant amount of investment for new users. Oracle E-Business Suite Integration A large focus of the SNO and PS releases is to further tighten the integration of these modules to Oracle EBS to support Version 2 of the standard SCP integration. A large focus will be to better generalize our generic integration solution and make it more flexible, removing the many vanilla modeling assumptions originally imposed.

Supply Chain Planning Release Content Document

Advanced Planning

3.2.

Oracle Strategic Network Optimization

3.2.1. New Features
3.2.1.1. Supply Chain Risk Management Due to the dynamic nature of the global business environment, companies are searching for ways to improve their supply chains in order to absorb disruptions that occur unexpectedly. While providing other substantial benefits, Just-in-time, and Lean Manufacturing initiatives have hindered many businesss ability to absorb the impact of unexpected events. Slack in the supply chain - usually in the form of inventory - is no longer an acceptable hedging strategy and a sudden change such as a missed supply, can have an immediate impact on a companies operations. As an example, recent hurricanes have proved disastrous and exposed many weaknesses and companies existing supply chain. Less sensational events, such as an unexpected line shutdown can also have a material impact to the business. The ability to run simulations for these unexpected events is necessary for companies to manage risk and these capabilities are now available in Oracle Strategic Network Optimization. While most advanced planning software packages have simulation capabilities, considering the unexpected nature of an event is absent. As an example, the simulation of an unexpected plant shutdown in the future will trigger inventory pre-build in anticipation of this event in most software packages. Since this event occurs unexpectedly, this is not a realistic hedging strategy. Strategic Network Optimization will simulate the surprise nature of this event and will present realistic options should such and event occur. These simulations can also be run proactively to determine the potential exposure, or risk, that your company faces. The following enhancement will allow planners to analyze and mitigate risk by: The Ability to consider unplanned, and planned events and its impact on the supply chain Easily compare scenarios using various Key Performance Indicators Ability to consider multiple demand series and safety stock plans

Vital to this enhancement is the concept of unplanned events. In order to simulate the unpredictable nature of such events, the element of surprise needs to be reflected in the solution. For example, if a plant is unexpectedly shut down due to a natural disaster the solver should not pre-build inventory in anticipation of this event. This requirement will be a key differentiator for the Strategic Network Optimization and strengthen its position in the marketplace as the leader in Supply Chain Risk Management decision support systems. 3.2.1.2. Alerts Alerts are used to assist the planner with identifying and resolving exceptions after solving the model. The current mechanism to view and manage alerts in SNO is by using the Over and Under User Sets. While this is useful, the generic Over/Under categorization makes it difficult for users to quickly identify exceptions of a certain type. Reports (Smart graphs) are typically created to supplement the Sets and present the

Supply Chain Planning Release Content Document

information in a more useful format. Reports require set up beforehand and multiple reports are needed to identify exceptions of different types. Introducing an alert framework in SNO alleviates the need to use both Sets and reports to manage and review exceptions in the model. It will also provide a familiar alert workflow that is typical in many planning applications. Because of it flexibility, SNO is often used to solve non-traditional supply chain problems. This enhancement focuses on the traditional strategic and tactical manufacturing & distribution use of the application. Consideration for a more flexible framework to support non-traditional uses will be considered in the future. Alerts are categorized based on the business area. Within each category, the type of alert violation will be identified. This provides the planner with the ability to quickly identify and focus on the area of interest. The ability to drill-down and easily navigate to the node or arc of interest is also an important requirement that is addressed. Alerts will provide the following benefits: Alerts provide an immediate visual representation of exceptions, which are faster and more informative than using sets to identify exception. You can drill-down to the exact location of the exception within a node or arc. Alert categorization is more specific than Over and Under User Sets categorization. Little set up is required to use alerts.

This image shows the new Alerts area at the bottom of the Strategic Network Optimization main user interface:

The number and type of alerts is displayed in the Model Workspace area. In the Model Workspace tree, at the root level of Alerts, the number of alerts is displayed in brackets

Supply Chain Planning Release Content Document

and the word Alerts is displayed in bold font. If no exceptions are found in the model, Alerts has no number in brackets next to it and the font is not bolded. In the example above, total of (68) exceptions were found when the model was solved. Within Alerts, there are six different alert categories. The number of exception found within each type of alert is displayed next to the alert category in the Model Workspace area. In the example above, (42) Demand alerts, (22) Inventory alerts, and (4) Transportation alerts were found for a total of (68). Within each alert category, there are several specific types of exceptions. If an exception is found, a red exclamation mark is displayed next to the exception type and if no exceptions are found, a green checkmark is displayed next to the exception type, as seen in the example above. The Alerts section can be displayed across the bottom of the main user interface, as seen in the example above. This section can be shown, expanded, or collapsed, using the up and down arrows at the top of the section. If you double-click an Alerts folder in the Model Workspace tree, the Alerts section at the bottom of the main user interface expands. Single-clicking on an item in the Alerts section of the Model Workspace tree displays the alert in the Alerts section at the bottom of the main user interface. The six tabs; Demand, Inventory, Manufacturing, Transportation, Supply, and Other reflect the alerts results and match the Alerts section in the Model Workspace tree. When using alerts, each node or arc that you want to be alerted about is assigned an alert category. To assign an alert category, a new Category drop-down list was added to nodes and arcs:

3.2.1.3. Key Performance Indicators After running a scenario, Key Performance Indicators (KPIs) can help you make detailed scenario comparisons. They provide you with graphical representation of various metrics in a model. KPIs can show you which scenario is most efficient at filling demand, minimizing inventory costs, or providing the highest percentage of machine utilization. Costs are categorized based on the types of costs in the nodes and arcs and are summed across the whole planning horizon, not by period. KPIs are only visible in Key Performance Indicators view.

Supply Chain Planning Release Content Document

An example of the Key Performance Indicators View Strategic Network Optimization has nine different KPIs: Total Cost - The sum of all costs in the model. Transportation Cost - The sum of all costs for any node or arc in the model where Category is set to Transportation. Production Cost - The sum of all costs for any node or arc in the model where Category is set to Manufacturing. Supply Cost - The sum of all costs for any node or arc in the model where Category is set to Supply. Inventory Cost - The sum of all costs for any node or arc in the model where Category is set to Inventory. Other Cost - The sum of all costs for any node or arc in the model where Category is null. Labor Utilization % - Labor utilization expressed as a percentage. Machine Utilization % - Machine utilization expressed as a percentage. Demand Fill Rate % - Demand Fill Rate expressed as a percentage.

By default, Key Performance Indicator data is displayed in bar chart format. However, the data can also be displayed in pie chart format or polar format by clicking the Pie or Polar tabs. A polar chart displays points in a graph based on data in the scenario. An example of a polar chart can be seen here below:

Supply Chain Planning Release Content Document

= Polar chart By default, each scenario defined in the Model Workspace appears in the Key Performance Indicators view. However, you can use the KPI Selection Dialog to choose which key performance indicators scenarios are displayed.

KPI Selection Dialog

The concept of scenarios was introduced in previous versions of Strategic Network Optimization. However, scenarios are now created and run from the Model Workspace tree as seen below:

Supply Chain Planning Release Content Document

Scenarios & Events in the Model Workspace Tree The concept of events is new to this version of Strategic Network Optimization. Events are individual occurrences which impact the supply chain. Events are created and then added to scenarios. They specify the find and replace functions which are performed within the model. Each scenario should have at least one event assigned to it. If you run a scenario with no events in it, the model baseline solves. Several events can be added to the same scenario. There are two kinds of events: Unplanned Planned

Unplanned events have been added to support Supply Chain Risk Management, they are complete surprises. They are used when there is no warning that the event will occur. A sudden change such as a missed supply can have an immediate impact on a companys operations. Unplanned events allow you to incorporate the concept of surprise into your models solution. Examples of unplanned events which can massively interrupt supply chain operations include natural disasters such as hurricanes and floods. Planned events are not surprises and there is at least some react time involved. With this advance warning, there is at least some time to make other supply arrangements and activate contingency plans. Examples of planned events include seasonal supply chain interruptions, anticipated shortages, and increases in demand caused by promotions. 3.2.1.4. SNO Integration Enhancements When Strategic Network Optimization is sold to EnterpriseOne or Strategic Network Optimization channels, customers expect integration out-of-the box. This is a challenge in SNO because of its flexibility and ability to solve the same problem many different ways. While SNOs flexibility presents a challenge for generic integration it has proved to be beneficial as SNO can be used to solve unconventional business problems. Modeling requirements in the SNO data connector are based on modeling best practices and will build on the existing connector requirements. This enhancement provides the following new functionality in the SNO connector:

Supply Chain Planning Release Content Document

Support of multiple time units of measure for resource commodities Resource Time commodities should be able to accommodate the following time units of measure Seconds Minutes Hours

The appropriate conversion between the different units are made using standard commodity UOM functionality in SNO. Out-of-the box reports included with the SNO connector model Standard reports will be included in a model that is generated by the connector since the structure is known. The illustrated reports are included:

Ability to model customers, in addition to internal organizations and suppliers Customer level demand is to be included in the connector model. Previously, all customer level demand was aggregated and placed on the DCs. Customer lanes, including shipping method, costs, and constraints will also be generated. The customer is represented in the map view by a new map shape of a cloud. The following depicts the generic structure for a customer.

Support of global suppliers and supplier capacity constraints

Supply Chain Planning Release Content Document

10

The previous connector modeled suppliers at the Supplier-Item-Destination Branch level. Aggregate supplier capacities could not be modeled because of this. The supplier structure will be changed to model suppliers at the Supplier-Item level, independent of the destination branch. Support of one-time supplies from broker suppliers Supplies from suppliers that are not a part of the standard Approved Supplier List are common in many industries where supply shortages are prevalent. One-off supplies for qualified parts can often be made to alternative suppliers or brokers. In this case, a purchase order might be present without the supplier being listed on the Approved Supplier List. This enhancement supports this business scenario. Support of manufacturing lot sizes (batch node) Manufacturing lot size will be represented with a batch node in SNO. This modeling will be configurable and there will be a new mgr file option. manufactureBatch=[TRUE|FALSE] (Default of FALSE). Support of manufacturing wait time Manufacturing wait time will be represented with a delay node. . Since SNO can model routings, it needs to model separation time between steps. This node is created at all times Support of All-of-Sets Resource representation changes are being made which will effect how manufacturing routings are represented in SNO. Replacement groups or All-of-Sets are groups of resources that can be alternates of one another (i.e. Crew 1 can run Machine 1 but if an alternate machine is chosen in the operation, it must use Crew 2). This is consistent with a Production Scheduling enhancement. Modeling of fixed production Represent the work order quantity or planned production orders that are present within the time fence. A Controller Single Node will represent planned production and should appear immediately after the routing process node. This node should be created at all times. End-item Product substitution End item product substitution will be available at the global and item-branch level. Ability to input multiple demand and safety stock series For scenario analysis, SNO will be able to import up to three safety stock and demand profiles. New mgr file options will be introduced to specify mapping from the data files to the SNO fields.

Supply Chain Planning Release Content Document

11

3.2.1.5. SNO Usability Enhancements The investment in usability continues with this release. In addition to the Alerts, and KPI view the following enhancements have been incorporated to improve the overall user experience: Improved Find and Replace Find, Replace, and Find Export are essential tools required by consultants, pre-sales, and customers. The purpose for initiating any of these utilities are many from model creation, navigation, and data editing to name a few. While each function serves a distinct purpose, there is some overlap and the fact that they each have similar, yet different dialogs is confusing. The usability suffers further as the number of modal dialogs that pop up can be many. For example, a simple Find query with an ensuing replace opens up to seven dialog boxes which must than be closed. This enhancement provides the following in SNO: Combined dialog boxes for Find, Replace, and Find Export Ability to access the dialog boxes with shortcuts versus the multi-nested menus Improved usability with a more intuitive graphical user interface

Quick access to common functions in the toolbar Commonly used functions have been added to the toolbar for easy access. These include: Find & Replace Hide Nodes Hide Arcs Fat Arcs Align Nodes in Columns Align Nodes in Rows Select Adjacent nodes Show/hide map legend

Improved Map Legend The map legend has been improved to provide the ability to move the legend outside of the map view to prevent the legend from covering up key areas of the map. The ability to specify a shape and color has also been added in this release. Overall Look and Feel Node icons have replaced the dated node symbols to make the nodes easier to identify. The node color has also been changed to match the color of the application and block images have been updated in the sample models.

Supply Chain Planning Release Content Document

12

Supply Chain Planning Release Content Document

13

3.3.

Oracle Production Scheduling

3.3.1. New Features
3.3.1.1. Ability to Specify a Unit of Measure on Items A Unit of Measure has been added as an explicit attribute of every item. This enhancement provides improved visualization throughout the model and schedule views. A global Unit of Measure tab has been added to the scenario properties where users can visualize / define units of measure. Integration processes automatically populate this list when PS is run in an integrated manner

3.3.1.2. Enhanced Alerts In PS, Alerts have been broken down into four distinct categories (Work Order, Demand, Inventory and Resource) and various types within each. These alert categories and types are added to the Model Workspace in the form of a tree control for easier navigation and summary data visualization

Supply Chain Planning Release Content Document

14

The alert view is now tab based and summarized by category / type and is context sensitive to selection within the Model Workspace for easier navigation
Demand Alerts Inventory Alerts Work Order Alerts Resource Alerts

3.3.1.3. Work Order Centric KPI Comparisons The KPI comparison view can now be viewed as either Demand centric or Work Order Centric. Via a new dropdown option, you can now understand the impact on the work order schedule when comparing scenarios.

Supply Chain Planning Release Content Document

15

New dropdown list contains both Demand and Work Order options

D l k s

Content in the bottom of the view changes based on whether it is set to be Demand or Work Order Centric

3.3.1.4. Ability to Open Operation and Routings from Operation Instances This usability enhancement allows the user to perform a right click on a given operation in any of the schedule Gantt charts and easily drill down to the operation and/or routing diagrams. This avoids the user having to navigate back through to the model workspace or the where used properties of a resource to in order to be open an operation.

3.3.1.5. Ability to Auto Create Work Orders Directly from Demands in the Supply and Demand Editor For schedule prototyping purposes, scenario simulation purposes and/or product demonstrations, users sometimes create Work Orders directly in the PS in Work Order Editor using standard functionality. (i.e. Right click | Add Production Work Order). Once the work order is created, users usually peg these back to a given sales order.

Supply Chain Planning Release Content Document

16

This works well, but if there are many sales orders and the user wishes to create a work order for each demand / line item combination this could potentially take quite a bit of time. A new feature has been added to PS that allows users to automatically create Work Orders for a given sales order without even navigating to the Work Order Editor. A simple right click on a demand or a folder or a subset / mixture of folders and demands (via multi-select) allows users to automatically create a work order per demand. 3.3.1.6. Find Functionality for Model Objects Find functionality is now available in PS using CTRL-F via the PS toolbar by selecting Edit | Find. This will launch a Find dialog box which provides text based searching in the PS model and the ability to drilldown to the found objects. You can limit the search to the following (by chosen scenario): All (will search all model objects listed below and their description fields as well) Supplies and Demands only Work Orders only All Resources Crews only Machines only Tools only Items only Operations only Routings only

Selecting and double clicking the result (or selecting the Open button) will drilldown to the selected object. For example, double clicking the operation code will open the operation diagram.

3.3.1.7. Provide an Indication that a Demand is Partially Fulfilled by both Starting Inventory and Production In previous versions of PS, if an order was fulfilled from both production and either starting inventory or a supply event, the starting inventory was not simultaneously displayed in the Production Pegging view (only the Production). This release addresses this by explicitly detailing each of the pegging relationships.

Supply Chain Planning Release Content Document

17

This applies to both materials, WIP and finished goods. The demand for Item A shows a green diamond at the start of horizon indicating some of the order is taken from inventory. The production below it indicates the remaining quantity is from manufacturing activities. Material 1 is consumed in operation A and pegged to both an on-hand quantity and a purchase recommendation. Material 2 is pegged to starting inventory and an incoming purchase order, each represented with a diamond representing incoming supply. 3.3.1.8. Automatic Reconciliation of Schedule Backlog It is common to see shop floor backlog in the schedule views to notify the scheduler that the shop floor is behind and action should be taken to reconcile the situation. There are a variety of different scenarios which cause backlog in the schedule for example: Work order operations having a Firm Start Date, Firm End Date, or Firm Date Range in the past, >1 work order operations having an Active Status on the work order routing operation step which conflicts with another work order >1 work order operations with a firm status with overlapping date ranges

For example, in the screen capture below, the area shaded in yellow indicates a point in time that occurs prior to the horizon start.

While this provides excellent feedback to users, it also introduces another issue the operations can not actually be run in the past. Prior to this release of PS, reconciling the schedule was primarily performed by using Cut | Paste in the Resource Gantt. While this method worked well, it could potentially be somewhat cumbersome to do when there are many operations running behind and/or many resources in the model. This release of PS provides the user with a right click menu item Enforce Horizon Start on resources. Enabling this flag (or setting it in the data model) and performing a repair solve will push forward all operations on that resource to the start of the horizon while maintaining operation sequence and at the same time respecting upstream / downstream precedence constraints. Enabling this flag (or setting it in the data model)

Supply Chain Planning Release Content Document

18

and performing a coldsolve will accomplish the same thing without user intervention (i.e. Auto-reconciliation).

For example, in the diagram below, the operations running on Die Bonder 2 are running behind. The user selects Die Bonder 2, performs a right click, selects Enforce Horizon Start and performs a repair solve (or cold solve). (Users are also able to multi-select and enable this flag for all highlighted resources). The operations on the applicable resource are pushed forward, maintaining the original sequence. This can also be persisted in the data model for a given resource as well.

Operations running in the past will be pushed to start at the beginning of the horizon. The sequence of operations on the resource will not be changed. In many cases, the operations running behind will be one of several operations that are contained within a routing. Since routings have precedence constraints between operations, moving operations from the past to horizon start may have consequences on other operations in the routing. Any upstream or downstream pegged operations of this operation will be pushed forward (if precedence constraints dictate). 3.3.1.9. Batchable Resources A Batchable resource can be described as a machine / oven / kiln (or similar) that can process one or more items simultaneously, but only if they share 1 or more similar Attributes (such as Temperature, Colour, Duration etc) and Attribute Value such as 1 Hour @ 400 Degrees. Typically, these resources have several spots or something equivalent in them. Items when processes within these resources consume 1 or more of these spots. This enhancement to PS enables the following behaviour: Allows users to explicitly define a given resource as Batchable along with a minimum and maximum spot capacity Define a pull forward window to allow a resource to be filled to its minimum spot capacity Allow users to explicitly associate 1 or more user defined attributes and attribute values to an item. T Automatic grouping of operations on a batchable resource by attribute If this is 1 attribute (such as temperature), all operations will be grouped together of the same temperature up to the max capacity of the resource.

Supply Chain Planning Release Content Document

19

If the user groups by more than 1 attribute (for example temperature and duration), this implies that all operations sharing the same duration and temperature will be run together to the max capacity of the resource. Manually move operations between batches if desired or manually move an entire batch. For example, if a sequence on a resource is scheduled to be 10 Hours at 500 Degrees followed by 12 Hours at 400 Degrees, the user can switch the order (via cut/paste, drag/drop, re-sequence in the resource gantt).

For example, the Resource Gantt below illustrates several ovens (CC4101 -> CC4105). Each of these ovens constrains a variety of operations which are running at the same time and grouped by temperature and duration. The summary colour at the oven level indicates spot utilization. Bubble help indicates the attributes of the batch and one can utilize an option in the Toolbar which allows you to highlight only certain batches if you wish (in orange).

Batches are of course applicable to regular manual scheduling activities. You can cut, paste entire batches between ovens, move operations from batch to another, resequence batches and even manually move operations into another batch which does not share the same attributes (you will be provided with a warning). 3.3.1.10. Consistent Resource Assignment within a User-defined Group of Operations within a Routing Alternate resources in a given manufacturing operation are very common amongst most Production Scheduling customer models. These alternate resources are modeled via the use of resource sets. In many cases, this resource set recurs in an upstream or downstream operation(s). In many cases, it is imperative that once a resource is chosen in an upstream operation, it must also be chosen in a downstream operation. This works well in PS and previously was a routing wide configurable option known as Consistent Resource Assignment. Users expressed the desire to be able to perform consistent resource assignment within only a selected group of operations within this routing - for example, operation steps 10, 20 and 30 must run on the same resource but steps 40,50 and 60 even though share a common resource with their preceding operations can run on the alternate. This enhancement in PS allows users to be able to configure PS to do just this.
Supply Chain Planning Release Content Document 20

Consider the following manufacturing routing. To make item A, it must through a setup, run and cleanup operation where it is then cooled. The item passes through a recursive process - Setup(2), Run(2), and Cleanup(2). With the exception of the Cooling operation, all operations run on either M1 or M2, as illustrated for the first Run operation.

When the first setup operation occurs on either M1 or M2, resource assignment must be the same for the following 2 operation steps. If M1 is chosen in the setup operation, it must also be chosen in the run and cleanup. (You dont want to cleanup a machine that you didnt run on). The cooling process occurs in a staging area. However, after the cooling operation takes place, the same logic occurs for the next recurrence of the setup, run and cleanup operations, but a different alternate can be chosen. The first three steps must run on the same machine and the last three steps must also run on the same machine.

The user opens up the properties of the routing and creates 2 distinct group and assigns the first 3 operations to the first group and the last 3 operations to the second group as illustrated. The user performs a solve. The first three operations are run on M1. After the cooling operation, the remaining three operations are run on M2. This could of course all be on M1 or all of M2 or in reverse order. The point is the operations in the groups share the same resource.

If operations are not assigned to groups, they are permitted to be run on any given resource.

Supply Chain Planning Release Content Document

21

If the user is using All of Sets (i.e. >1 Resource such as a Machine1 and Tool1 OR a Machine2 and Tool2), consistent resource assignment applies to the group. i.e. The group must be the same. When migrating a model from previous versions, the import will detect if a routing has consistent resource assignment selected and auto-create a group and assign all operations to it.

3.3.1.11. Resource-specific User Definable Cycle Times for Campaign Run Optimization PS provides the ability to define: Minimum cycle times in various bucket sizes. In a previous release of PS, cycle size was either a Shift, Day or a Week. Cycle sizes are now flexible. For example, a cycle can be 2 weeks, 4 days etc.

If the resource specific cycle size checkbox is selected, planners can enable this flag by CRO resource. Therefore, different lines in the plant can be on their own cycle times rather than having to adhere to global cycle.

3.3.1.12. Address Infeasibilities for Firmed Work Order Operations Outside of the Fixed Timefence As Production Scheduling is a finite capacity scheduling application, some situations can occur which would result in an infeasible production schedule. These situations are always being monitored and resolved through improved data validation, alerting and solver handling of problematic and has drastically improved throughout the past several

Supply Chain Planning Release Content Document

22

releases. This release continues to improve on this theme. For example, it is quite common and sometimes unavoidable to have: >1 work order operation firmed on a same single capacity resource with overlapping date / times. A firm date range on a work order operation which is shorter than total operation run / elapsed time

In prior versions of PS: If the dates fell within the fixed timefence, PS would reconcile the infeasibility and alert the planner that shop floor backlog exists If these work order operations were outside of the fixed time fence this resulted in an infeasible schedule. In this release there is an added capability for the solver to resolve this conflict types outside of the fixed timefence if necessary to avoid this situation.

For example, take the following 2 work orders which are both firmed at the same time outside of the FTF:

Solved in a previous version the schedule was infeasible and the planner was provided with an error message indicative of such. In this release, the schedule is feasible. The highest priority work order is moved to start earlier in the horizon.

Supporting alerts are also provided to the user to indicate the firm date violation.

Supply Chain Planning Release Content Document

23

3.3.1.13. Disable Units of Effort for Setup and Cleanup Operations on Work Orders PS has a differentiating feature introduced several releases ago which provides the ability to schedule Work Orders according to their individual unit of effort. This feature cross references the routing template to break down work order operations into the lot multiples specified on the routing. The feature can be enabled as either a global option applying to all routings, or the user can specify the feature for specific routings. For example, if this feature is leveraged, a work order is scheduled to release inventory according to every lot multiple. In the example below, inventory is moved between operations in 25 unit increments the work order has only 3 operations listed on it, but PS will break it down according to the routing lot multiple.

Inventory Production and Consumption is accurate Makespan is accurate Resource usage is accurate

In some cases, it is quite possible that the first operation may be a setup operation and the last operation may be a cleanup operation.

In this case, the setup & cleanup operations only need to be executed once as opposed to three times. This release of PS has the ability to specify an operation of type Setup, Production or Cleanup.

Supply Chain Planning Release Content Document

24

Setup and Cleanup operations will not be broken down to their units of effort.

3.3.1.14. Resource All of Sets PS provides excellent resource offloading functionality within an operation (e.g. Machine 1 can be substituted for Machine 2, Crew 1 for Crew 2, etc.) via the use of Resource Sets. This type of set can be referred to as a one of type of set, meaning one of the resources within the set must be used. This release adds a new set type on operations that support resource replacement groups within PS ( an All of type of set). This means that resource exclusivity relationships can now be defined directly within a given operation as opposed to having to use Operation Sets. For example, Operator 1 can only run Line 1 and Line 3. Operator 2 can only run Line 3 and Line 2. The new operation structure within PS is depicted below.

Supply Chain Planning Release Content Document

25

The work order editor has a new column to indicate the name of the all of set. This is where manual overrides can be made to which set is attached to the work order. If an alternate set has a different number of resources, rows will be added / subtracted as appropriate.

Paste targets in the Gantt charts are consistent with previous versions of PS. Offloading to an alternate set will show the target in orange. Pasting to a different time on the same set will be highlighted in light blue.

A 1 of resource set can contain a mixture of All of sets, plus single resources.

Supply Chain Planning Release Content Document

26

The All of Setsare shown in the Production Pegging View. The operations on the solver selected All of Set is summarized on the set name, so the user will have visibility into which All of set has been chosen without expanding all of the sets.

From an offloading perspective, the overall approach is virtually the same as previous versions of PS, but the offloading calculation must be applied to all members of the set. If any one of the resources within an All of set have their threshold violated, all resources will be offloaded. If any one of the resources in the target All of set have their offload thresholds violated prior to the offloading taking place, the operation will not be offloaded to that set. At this point, an additional alternate will be evaluated; if no alternates have available capacity, no offloading should take place. If the primary is significantly overloaded, offloading will still occur to less loaded (but still overloaded) alternates. This effectively spreads the load and will help get orders met as quickly as possible. The PS Consistent Resource Assignment feature is also impacted by this enhancement. Prior to this release, Consistent Resource Assignment across routing steps was based on a single resource. If Line 1 was chosen in Step 1 of a routing, it must also be chosen in a subsequent step. In this release, Consistent Resource Assignment applies to members of the all of set.

Supply Chain Planning Release Content Document

27

3.3.1.15. Hard Links between Work Orders This enhancement allows a many to many relationship amongst Work Orders along with the ability for the user to specify precedence constraints between these Work Orders. This is handy if a specific sequence is required between several work orders. The business requirements for this enhancement are best explained with a simple example. Assume the following manufacturing process. To make Item A, the following routing steps take place. The lot multiple across the manufacturing routing is 25 units. Item A is produced by Operation C.

Operation A consumes an inventory Material A.

Material A is a subassembly also manufactured in the plant as per the following process. The lot multiple across this routing is also 25 units. The material is produced by Operation C1.

Assume the user creates a work order for the finished good and the material (50 units each).

These Work Orders are related through inventory, so will generally schedule JIT and have some degree of overlap as illustrated below.

Supply Chain Planning Release Content Document

28

If the user wishes to explicitly relate these Work Orders to one another (for example for lot control, quality reasons etc), they can specify the relationship in the work order editor in the new Related Work Orders tab. Precedence relationships (to facilitate a cooling process, inspection etc) can also be specified, along with min / max separation constraints.

Assume the user populates Starts After End with a minimum separation time of 5 Hours. When Units of Effort is used, the 5 hour minimum separation is applied to the pegged work order routing instances. In this case, the Work Orders are for 50 units each (remember, the routing has a lot multiple of 25 units), therefore there are 2 routing instances and separation is applied twice.

The relationships between the Work Orders can be many to many. A given work order can be linked to many next work orders A given work order can have many previous work orders.

Supply Chain Planning Release Content Document

29

Manual Scheduling within PS will have all appropriate precedence relationships respected.

3.3.1.16. Dynamic Throughput Rates on Resources Some customers vary their production rates fairly dynamically and frequently. For example, the speed of a line can change daily or weekly based on available labor. The net effect of dynamic rate changes is simple they make a given manufacturing operation take more or less time to complete in a given time interval. There are various reasons why the speed of a production line may change which may include (but by no means are limited to) areas such as: trial manufacturing process changes line improvements labour constraints new product development temperature / humidity variations

This release of PS provides the user with the ability to specify dynamic rates on a resource (crew, machine, tool). For example, Packing Line #1 produces items, A, B, C and D. At normal speeds, it produces product at a rate of 100 units per hour. In this example, Item D is produced in runs of 1700 units per week.

Assume due to a labour constraint, the packer now runs at the following throughput rates:

80% in the 1st week 100% in the 2nd week 150% in the 3rd week

The user navigates to the Packer resource properties to the Throughput tab and defines the appropriate dynamic percentages.

Supply Chain Planning Release Content Document

30

The speed at which the items are produced can clearly be seen in Gantt chart by the operation length as well as by looking at the steepness of the slope of the item graph for a given item.

If >1 resource on the operation also has a dynamic throughput range, the lowest value for a given time interval wins. For example, if an operation requires both Packer 1 and Tool 1 and they have competing dynamic throughput rates and effective ranges.

Supply Chain Planning Release Content Document

31

In a resource set, resources can have different throughput rates for different date ranges. If production is offloaded to an alternate resource with a different throughput, the operation duration on the alternate resource will reflect the new throughput. If an operation is moved to a timeslot via manual scheduling (Cut | Paste, Resequencing, Remove Idle etc) that has a different throughput rate defined, the operation duration should change according to the throughput in effect. If the user offloads an operation manually to a different resource with a different rate, the operation duration will change according to the throughput in effect. If the user changes the rate on a resource and runs a repair solve, the repair solve will recognize and change the duration of the operation accordingly.

3.3.1.17. Production Scheduling Data Connector Port to Sun, HP, and AIX The PS SCBM / Oracle EBS data connector now runs on the following platforms: Windows (previously supported) Linux (previously supported) Sun (New) HP (New) AIX (New)

This allows for the PS connector to be deployed on a central server apart from PS if desired. All command syntaxes stays the same. 3.3.1.18. Ability to Export Selected Model Data during Schedule Publish As part of the File | Publish process, users now have the ability to publish the PS model or chosen objects of the data model in XML format. (i.e. changeover rules, groups, crews, machines, tools, operations etc). This is useful if PS is to be the system of record for any data that is not available within the ERP system. The next time a model is imported into PS, integration processes could be extended to reference the various data model elements exported from the previous scheduling session which could amend to the new model prior to import

A new tab in the Publish Profiles allows users to define which data objects to publish. Whenever the Publish Process is called (whether in batch or interactively), the chosen data will be exported to a user named XML file. Interactively, the published model is based off of the approved schedule. Since the schedule publish process batch file points to a named scenario, you can export the model from any given scenario which may or may not be the approved schedule.

Aspects of the model can be output to a user defined filename any object within the model can be output to this specific file.

Supply Chain Planning Release Content Document

32

3.3.1.19. PS XML Model Unique Extension The PS XML data files which can be imported and exported now have an additional extension available. The PS XML non compressed file can be the standard .xml extension or uniquely to PS as an .ops. The .ops file is still standard XML format, but will launch PS directly upon being double clicked. The PS XML compressed file can be the standard .xml.gz extension or uniquely to PS as an .opz. The .opz file is still standard compressed XML format, but will launch PS directly upon being double clicked. The icon for either is the PS standard icon.

3.3.1.20. Enhancements to Auto-generated Routings Auto-generated routings now read resource set definitions and precedence constraints from the original routing. The list below outlines a few typical scenarios that cause Auto-Generation of Operations and Routing templates based on work order structure within Production Scheduling: Work orders which were generated in a Configurator program. Essentially, Work Orders are dynamically created and passed to PS. No corresponding routing exists in PS. Non-standard crews, machines or tools included on the work order bill of resource. Contrary to the above, sometimes the work order would be missing crews, machines or tools on work order operations. Non-standard items included on the work order bill of material. Missing items on the work order bill of material Additional operations included on the work order routing. Missing operations on the work order routing (for example, Oracle EBS does not pass Closed work order operations to PS).
33

Supply Chain Planning Release Content Document

Operation Sets specified on the work order routing

In a previous release of PS, a new feature was added to PS which removed the PS dependency on having a routing template pre-created in the model for every work order in the application. For those scenarios outlined, PS dynamically cross references the work order routing against the routing template during the import process. If a work order meets on of the problematic scenarios outlined earlier, one can expect to see a newly created routing which directly corresponds to the work order in question. If operations differ from their standard templates, a newly created operation will be present in the routing as well. When PS was generating this routing and operation templates, it was not reading the precedence constraints on the work order routing between the operations, nor were the resource sets being constructed. This release of PS has enhanced logic in the import process which addresses these 2 issues. When generating the precedence constraints for the auto-generated routing, the import now looks at the operation codes and cross references the precedence constraints on the routing. If the work order has different precedence constraints than the routing template, the precedence constraints as specified on the work order routing will be used when the auto-generated routing is created. Similarly for resource sets - the operation template is reference to reconstruct the resource sets. 3.3.1.21. Selective Work Order Release to Production After a user approves a schedule within PS, the general business process is to publish the schedule back to ERP. The publish process within PS uses a Release timefence to filter out work orders from the release process. If a work order starts before the end of this timefence, it will be included in the release. If the user wishes to include / exclude individual work orders from this process (regardless of start time), this was not possible prior to this release. This new release provides a new mechanism for the user to be able to individually select which work orders are released back to ERP. For example, after analyzing the schedule, the user approves the schedule he/she is happy with. The user then performs a right click on the scenario name and selects a new option Edit Work Order Release.

This launches a new dialog view which lists all work orders and their various attributes. The Publish Profile selected has a Release Horizon. Any Work Orders starting within this release horizon will be auto-selected. The user can override this if desired.
Supply Chain Planning Release Content Document 34

Supply Chain Planning Release Content Document

35