SLO Guide

Service Level
Optimization
Installation and User’s Guide

version 3.0
© 2008-2010 SmartOps Corporation, All Rights Reserved.
SmartOps® Service Level Optimization (SLO) Installation and User’s Guide
This manual, as well as the software described herein, is furnished under license and may be used or copied only within the
terms of such license. The content of this manual is furnished for informational use only, is subject to change without notice,
and should not be construed as a commitment by SmartOps Corporation. SmartOps assumes no responsibility or liability for
any errors or inaccuracies that may appear in this documentation. Except as permitted by license, no part of this document
may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical,
recorded, or otherwise, without the prior written permission of SmartOps.
SmartOps®, the SmartOps logo, and SmartOps product names and slogans are registered trademarks or other proprietary
marks owned by SmartOps Corporation. Other trademarks contained in this software or related materials may be registered
trademarks or proprietary marks of their respective owners. The software and/or databases provided by SmartOps
Corporation and its licensors are protected by U.S. and international copyright, patent and other intellectual property rights.
No part of the software or database may be used, reproduced or transmitted in any form or by any means, electronic or
mechanical, for any purpose except as expressly provided in writing by SmartOps Corporation.
Reverse engineering, decompiling, or disassembling the software or its database objects is prohibited. Any intellectual
property infringement or other violation of any of the above terms will be prosecuted to the maximum extent of the law.
This product includes software developed by:
- the Apache Software Foundation (http://www.apache.org/ and http://poi.apache.org/)
- Sun (http://java.sun.com/ and http://java.sun.com/products/javamail/)
SmartOps Corporation, One North Shore Center, Suite 400, Pittsburgh, PA 15212
Table of contents
Introduction
About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Contacting support services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Service Level Optimization Overview

Sample business problem addressed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
SmartOps approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Fit within EIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Installing and configuring SLO

SLO licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
SLO installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
SLO global configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
SLO module settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
User account privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Configuring SLO privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
User Account preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Assigning SLO preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1
Service Level Optimization Installation and User’s Guide
SLO data set configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Assigning SLO Copy Output processor settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Assigning automatic MIPO scenario access settings . . . . . . . . . . . . . . . . . . . . . . . . . 22
Running SLO
Starting SLO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Importing MIPO scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Editing SLO Input data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Stocking point static input data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Stocking point time varying input data (single period). . . . . . . . . . . . . . . . . . . . . . . . 31
Stocking point time varying input data (single node) . . . . . . . . . . . . . . . . . . . . . . . . . 32
Stocking point time varying input data (single property) . . . . . . . . . . . . . . . . . . . . . . 34
Auditing data changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Filtering audit records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Selecting a specific audit transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Adjusting date periods for specific audit transaction . . . . . . . . . . . . . . . . . . . . . . . . . 38
Analyzing and managing scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Preparing the SLO scenario for optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Optimizing the SLO scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Duplicating SLO scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Managing scenario access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Deleting a SLO scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Deleting multiple scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Running SLO reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Stocking Point Static Inputs Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Stocking Point Time Varying Inputs Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Master Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Assigning the STAGE attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Inventory Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Stocking Point Static Outputs Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Stocking Point Time Varying Outputs Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
2
Table of contents
Demand Stream Static Outputs Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Editing SLO Output data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Stocking point static output data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Exporting SLO data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Managing SLO alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Appendix:
Alert Definitions
SLO alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Index
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
3
4
Introduction
W
ith the SmartOps® Service Level Optimization (SLO) application, you can optimize your
supply chain target service level for each stocking-point with external demand forecast so as
to guarantee the overall global target service level. It takes as input the key drivers of
inventory such as demand forecasts and forecast error, lead times, replenishment frequencies,
inventory costs, margins, and batch sizes. It outputs individual item-location target service levels
which together satisfy the desired global target fill rates and yet minimize inventory investment and/or
cost of lost sales over the planning horizon.
The SLO application workflow process consists of the following steps:
1. The user creates and optimizes a MIPO scenario containing the stocking point data
needed for SLO analysis
2. The user imports the MIPO scenario into the SLO application via the SmartOps Portal
3. The user optimizes the SLO scenario to identify the global target service level
4. The SLO application calculates solution outputs and produces its results in the form of
reports
5. The user exports the SLO optimized service level inputs back to the MIPO
scenario
6. The user re-optimizes the MIPO scenario with the SLO service level inputs to
achieve the desired target service level
5
About this guide

The SmartOps Service Level Optimization Installation and User’s Guide describes the configuration settings
needed to enable SLO to work as a stand-alone application, along with detailed instructions for the
workflow process as described previously. This guide contains the following chapters:
• Chapter 1: SLO Overview
• Chapter 2: Installing and configuring SLO
• Chapter 3: Running SLO
• Appendix: SLO Alerts
Intended audience
This book is intended for users of SmartOps applications and customer Information Technology (IT)
staff.
The primary audience for this guide is supply chain planners and operations research engineers who
use SmartOps’ applications, such as Multistage Inventory Planning & Optimization (MIPO™).
The secondary audience for this guide is IT personnel at customer sites. Their focus is installing,
configuring, and maintaining the third-party software used to interface with the SmartOps SLO
application.
Notation conventions
This section describes notation and formatting conventions used throughout SmartOps
documentation. These conventions have been defined and are used to provide consistency and clarity
as well as to aid visual recall of information.
Convention Example
Any item that appears literally on the computer screen such as a text • click Go
field label, a menu name, or a button label is printed in boldface. • click LOGOUT
Information that should be entered exactly as shown is also printed in • Type 2 in the Factor by text
boldface. box.
Keyboard keys are indicated by the text of the key face displayed in • ALT
upper case and small caps.
• SHIFT
Key combinations include multiple keys. A plus sign connects names of • CTRL+ALT+DELETE
keys that should be pressed simultaneously.
• SHIFT+S
Table 1: Notation conventions used in this document
6
Introduction
Convention Example
Information you enter that is specific to your own circumstances, such • Type User Name and press
as your user name or a specific unit cost, is designated by an italic ENTER.
variable name. • lead time, also called total lead

time
Italic text is also used to indicate a new term or concept.
This symbol indicates information that emphasizes or supplements
important points of the main text.
This symbol indicates a note of caution. Items that warrant a note of

caution include warnings that could protect against a loss of data or
other undesired behavior.
Table 1: Notation conventions used in this document
Contacting support services

SmartOps Support Services provides technical and application support via telephone and email.
To reach the Support Services department by telephone:
1. Dial (412) 231-0115.
2. When prompted, press 4 to be directed to SmartOps Support Services.
To reach the Support Services department by email:
Email SupportServices@SmartOps.com
For more information about SmartOps, visit our Web site:
www.SmartOps.com
7
8
Chapter 1:
Service Level
Optimization Overview
T
he Service Level Optimization (SLO) module provides a means by which a company can
determine its most cost-efficient set of service levels across all items with external demand,
given an overall service level target.
The SmartOps MIPO application calculates an overall inventory cost for a given product line. If a
company has a target service level, in terms of fill rate, and wishes to minimize the total inventory cost,
it will run SLO to optimize the individual service levels at each customer facing stocking point such
that the global service level is maintained but the overall inventory cost is minimized.
This chapter provides a high-level overview of SLO.
Sample business problem addressed

A company has a diverse portfolio of over 300 products that sell through various channels to a large
set of customers. In order to maintain its position in the market and the satisfaction of its customers,
the company needs to achieve a 98.5% overall service level across all orders. To set inventory targets,
the planners need to identify the specific service level objective for each item, location, and customer
combination. Should the planners set all the combinations to 98.5%, use some type of ABC
stratification, or is there a better way?
9
SmartOps approach
The SmartOps Service Level Optimization (SLO) module is the ideal tool for the difficult problem of
finding the right balance between service and cost. SLO provides optimal service levels for each
demand point while respecting targets global service levels or service cost-revenue tradeoffs.
Figure 1-1 Service Level Changes vs. Gross Profit Margins

As shown in Figure 1-1, SLO identifies the optimal service target for each demand point while
achieving an aggregate 98.5% service level as well as maintaining a minimum service level of 90% for
each item. Many of the demand points have optimal service levels below 98.5% and other require
service levels above the global objective. It is not surprising that items with higher gross margins will
typically dictate higher service levels. Many other factors also impact the optimal service levels
including lead times, batch sizes, and forecast error. As shown in Figure 1-2, SLO tends to set higher
service levels at demand points with lower forecast error, leveraging these items to achieve the global
objective.
Figure 1-2 Service Level Changes vs. Forecast Error
10
Chapter 1: SLO Overview
Traditional Service Decision

SmartOps Service Level Optimization
Approach
Sets specific service levels for each item-location Optimizes specific service levels for each item-location
in the supply chain to meet global service level in the supply chain to ensure global service level target
target, but fails to recognize differences between by including calculations to minimize inventory and lost
service-cost relationships in calculations revenues
Classifies items into ABC but can only do so Models all relevant drivers of inventory requirements
through simple relationships between demand such as
volumes and margins
• lead time and lead time variability
• replenishment frequency
• forecast and forecast error
• frozen window
Utilizes simple search mechanisms Embeds sophisticated search algorithms within

enterprise inventory optimization
Table 1-1 Service Level Approach Comparisions (Traditional vs. SmartOps)
Fit within EIO

SmartOps Service Level Optimization (SLO) is a key component of the SmartOps Enterprise
Inventory Optimization (EIO) solution. SLO runs in conjunction with SmartOps Multistage
Inventory Planning & Optimization (MIPO) to optimize item-specific service levels given the optimal
inventory placement generated by MIPO. SLO only requires a few additional data elements in
addition to supply chain data required for inventory optimization.
SLO Inputs SLO Outputs
• Global target service level per item • Optimal service levels for each SKU-
groups (optional) location
• Lost sales percentage (when • Inventory requirements
applicable)
• Expected lost revenues
• Desired service level range (min/
• Product availability statistics
max)
• Margins (when incorporating lost
revenues)
Table 1-2 SLO Inputs and Outputs
11
Global target service level and lost sales percentage are optional inputs. When the objective is to
minimize the total inventory cost, a global target is needed to ensure reasonable service. If the desired
objective is to minimize inventory costs plus revenue loss, the impact of lost sales plays the role of the
global target service level, and SLO can find the best mix of service levels that minimize the total cost.
As shown in Figure 3, a company using the SLO module was able to determine the optimal global
service level target by analyzing the tradeoffs between inventory cost and lost revenues. In this case,
targeting a global service level of 98% was the right mix between cost and service for this company.
Figure 1-3 Total Cost vs. Target Global Service Level
Benefits
Based on analysis of customer data, utilizing SLO will provide a 5%-7% additional reduction in
inventory compared to setting uniform service level targets across all items or even ABC type
stratification schemes. Additionally SLO provides a quantitative, systematic, and integrated method to
establish and manage service level targets.
12
Chapter 2:
Installing and
configuring SLO
T
his chapter describes the procedure for installing and configuring the Service Level
Optimization (SLO) application, and prerequisites for using SLO. Designed to run in the
SmartOps Portal, the SLO installation and configuration includes the following:
• SLO licensing
• SLO installation
• SLO module settings
• SLO user account settings
SLO licensing
The Service Level Optimization application requires a licensing agreement with SmartOps in order to
be installed and configured to run in a network environment. Please contact SmartOps Support
Services with any questions related to your software licensing agreement.
13
SLO installation
SLO installation takes place during the MIPO installation process. For more information on the
MIPO installation process, see the MIPO Installation and Upgrade Guide.
SLO global configuration

After you have successfully installed MIPO, you can use the SmartOps portal to set up the global
settings for the SLO application.
SLO module settings

The SmartOps Manage Module Settings feature includes a separate module for SLO. You can
configure SLO by logging on to SLO and selecting Module Settings under the Settings menu.
The SLO module contains the configuration settings used by the SLO application for various
functions. You can access this module by doing the following:
1. Log on to the SLO application.
2. Select Module Settings under the Settings menu.
3. Select Service Level Optimization from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate SLO parameters. A list of
the parameters and their functions is provided below.
Delta threshold
Parameter: Delta threshold
Required: Yes
Behavior: The percentage change on the value of the global target objective between two
consecutive iterations is evaluated by SLO in each iteration. If the corresponding value is
smaller than the predefined threshold, the default being 1e-6, the SLO computation will
stop.
Default: 1e-6
Gamma Delta Service Level
Parameter: Delta Service Level
Required: No
Behavior: When gamma distribution is used to model demand for the MIPO scenario,
SLO performs a service level conversion based on the value defined in this parameter.
Default: 0.00001
Initial Omega
Parameter: Initial Omega
Required: Yes
Behavior: The initial value of the predefined threshold used by SLO to determine the its
14
Chapter 2: Installing and Configuring SLO
searching step sizes.

Default: 1024
Initial Solution Search Factor
Parameter: Initial Solution Search Factor
Required: No
Behavior: The scale factor used to determine the step size in search of the first feasible
solution.
Default: 0.5
Initial Solution Search Iterations
Parameter: Initial Solution Search Iterations
Required: No
Behavior: The number of iterations for which to apply the initial solution search scale fac-
tor to determine step size in search of the first feasible solution. Once this limit is
reached, a scale factor of 1 is applied.
Default: 4
Maximum Alerts
Parameter: Maximum Alerts
Required: No
Behavior: Consolidate alerts of a specific type upon reaching this limit.
Default: 500
Maximum Iterations
Parameter: Maximum Iterations
Required: No
Behavior: The maximum number of MIPO iterations to compute by SLO.
Default: 200
Note: If a SLO scenario contains less than 20 customer facing nodes, the SLO module will
automatically run 5.000 iterations regardless of this setting value.
Normal Delta Service Level
Parameter: Normal Delta Service Level
Required: No
Behavior: The small perturbation on the fill rate.
Default: 0.0001
Omega Scale Factor
Parameter: Omega Scale Factor
Required: No
Behavior: The scale factor used by SLO to reduce searching step sizes.
Default: 2
Omega threshold
Parameter: Omega threshold
Required: No
15
Behavior: The threshold that is used to determine the SLO searching step sizes.
Default: 1e-6
Percentage Change
Parameter: Percentage Change
Required: No
Behavior: Percentage change.
Default: 1e-8
Validation Threads
Parameter: Validation Threads
Required: No
Behavior: Number of threads that will be doing validations. Typically it should be set to
the number of CPUs the database computer is running. If empty it will use as many
threads as CPUs are available on the application server.
Default: None
When you are finished with your configuration, click OK.
If you decide not to implement the changes you made, click Cancel.
User account privileges

If you have administrative privileges in SLO, you can assign privileges to a user account to enable or
prevent a user from performing specific SLO tasks. The following SLO privileges can be set through
the SmartOps Portal administrator settings:
• Access the SLO module
• SLO alert configuration
Configuring SLO privileges

To set or change SLO privileges to a user account:
1. Click Settings > User Settings to open the User Settings window. By default, the User
Info tab is selected and contains information for the current user.
2. Click User Privileges to open the User Privileges tab, shown in Figure 2-1.
16
Figure 2-1 User Privileges tab in the User Settings window

3. Select a user account to modify by clicking the Browse (...) button to open the User
Selector.
a. Select All or User Name from the Search by drop-down menu.
b. If you select All, a list of all users is displayed. Click the desired user name and click
OK to close the User Selector.
c. If you select User Name, the User Name field is displayed.
d. Enter the first few letters of the name and click Show. The Users list is populated
with user names that start with the text you entered. If there are many users, you can
page through the list.
e. Click the desired user name and click OK to close the User Selector.
4. Select Service Level Optimization from the Select Module drop-down menu.
5. Check or uncheck the check boxes for each privilege, to grant or deny the privilege,
respectively.
Note: Privileges in SLO are hierarchical. For example, a user must

have the privilege to Access SLO module before any subsequent
privileges you select, such as View SLO Alerts or Email SLO Alerts,
take effect. The different levels of the hierarchy are denoted by level of
indentation. Also note that assigning a high level, or base, privilege
does not mean that subsequent privileges are automatically selected
and assigned. Each privilege must be assigned individually.
17
6. Click OK to save your changes. The User Settings window is reloaded and displays a
status message indicating that the changes to the user account were saved successfully.
Note: Although the changes you make to a user account are effective
immediately, if the user whose account you modified is signed in to
SLO at the time you saved the changes, he or she cannot view the
privileges you changed in the User Privileges tab until he or she logs
out and signs in again.
SLO privilege definitions
parameter definition notes

Access SLO module Enables the SLO functionality of the Parent setting
SLO module. This optional feature only
available through SmartOps license
agreement.
Access SLO module alerts Enables the SLO alert delivery and Parent setting
generation options.
Table 2-1 SLO privilege definitions
User Account preferences

If you have administrative privileges in SLO, you can assign preferences that enable or prevent users
access to certain SLO tasks.
Assigning SLO preferences

To assign SLO preferences to a user account:
1. Click Settings > User Settings to open the User Settings window. By default, the User
Info tab is selected and contains information for the current user.
2. Click User Preferences to open the User Preferences tab, shown in Figure 2-2.
18
Figure 2-2 User Preferences tab in the User Settings window

3. Select a user account to modify by clicking the Browse (...) button to open the User
Selector.
b. If you select All, a list of all users is displayed. Click the desired user name and click
4. Select the Service Level Optimization module from the Select Module drop-down
menu.
5. Check or uncheck preferences you want to set or enter new values as appropriate.
Note: Click the check box next to the column heading labeled
Preference to select or deselect all of the available preferences for the
selected module.
19
6. Click OK to save your changes. The User Settings window is reloaded and displays a
status message indicating that the changes to the user account were saved successfully.
Note: Although the changes you make to a user account are effective
immediately, if the user whose account you modified is signed in to
SLO at the time you saved the changes, he or she cannot view the
preferences you changed in the User Preferences tab until he or she
logs out and signs in again.
SLO preference definitions

View Global Service Objective Lets user see Global Service Objective
Out of Range alerts Out of Range alerts in the View Alerts
window.
View Stocking Point Lost Sales Lets user see Stocking Point Lost Sales
Percentage Null or Negative alerts Percentage Null or Negative alerts in
the View Alerts window.
View Invalid Customer-facing Lets user see Invalid Customer-facing

Stocking Point Unit Cost alerts Stocking Point Unit Cost alerts in the
View Alerts window.
View Customer-facing Stocking Lets user see Customer-facing Stocking

Point Inventory Unit Cost Out of Point Inventory Unit Cost Out of
Range alerts Range alerts in the View Alerts window.
View Max Service Level < Global Lets user see Max Service Level <
Service Objective alerts Global Service Objective alerts in the
View Alerts window.
View Min Service Level > Global Lets user see Min Service Level >
Service Objective alerts Global Service Objective alerts in the
View Alerts window.
View Customer-facing Stocking Lets user see Customer-facing Stocking

Point is Non-stocking Node alerts Point is Non-stocking Node alerts in
the View Alerts window.
Email Global Service Objective Lets user receive an email notification

Out of Range alerts when Global Service Objective Out of
Range alerts occur.
Table 2-2 SLO preference definitions
20

Email Stocking Point Lost Sales Lets user receive an email notification
Percentage Null or Negative alerts when Stocking Point Lost Sales
Percentage Null or Negative alerts
occur.
Email Invalid Customer-facing Lets user receive an email notification

Stocking Point Unit Cost alerts when Invalid Customer-facing Stocking
Point Unit Cost alerts occur.
Email Customer-facing Stocking Lets user receive an email notification

Point Inventory Unit Cost Out of when Customer-facing Stocking Point
Range alerts Inventory Unit Cost Out of Range
alerts occur.
Email Max Service Level < Global Lets user receive an email notification
Service Objective alerts when Max Service Level < Global
Service Objective alerts occur.
Email Min Service Level > Global Lets user receive an email notification
Service Objective alerts when Min Service Level > Global
Service Objective alerts occur.
Email Customer-facing Stocking Lets user receive an email notification

Point is Non-stocking Node alerts when Customer-facing Stocking Point
is Non-stocking Node alerts occur.
Table 2-2 SLO preference definitions
SLO data set configuration

The SLO workflow design allows for weekly data updates to MIPO to include SLO scenario outputs
as the service level inputs for MIPO optimization. The SLO Output Copy processor can be invoked
during the data loading process to automatically copy this data. This processor can be configured in
the PSS.DAT file for the data set
The SLO scenario can also be configured to automatically inherit the scenario access iinfomration
associated with its source MIPO scenario.
Note: The processor settings file for your organization can be named something other
than PSS.dat. A processor settings file will always contain the text “PSS” in the first
field of the header line.
21
Assigning SLO Copy Output processor settings

To configure SLO Output Copy procesor properties on a per-loadset basis (in PSS.DAT):
1. Identify and unzip the loadset where you want to change processor settings.
2. Locate the PSS.dat file and open it in a text editor. If PSS.dat has already been configured
for the SLO Output Copy processor, the file will resemble the following:
PSS||PSS_PROCESSOR_NAME|PSS_PROPERTY|PSS_VALUE
ADD||SloOutputCopyProcessor|Is Active|true
ADD||SloOutputCopyProcessor|Processing Phase|Preprocessing
ADD||SloOutputCopyProcessor|Execution Order|1
ADD||SloOutputCopyProcessor|SourceScenarioName|EnterSLOSupplyChainName
Here
END_OF_SET||||
3. In PSS.dat, add or modify the properties associated with the SLO Output Copy
processor.
4. Save and close the PSS.DAT file.
5. Update and close the .zip archive.
Note: SDLT users can also enter these settings using the Processor Settings tab.
For Data Gateway users, these settings can be entered through the Processor Settings
tab in the SGLT.
Assigning automatic MIPO scenario access settings

To configure a SLO scenario to automatically inherit the MIPO scenario access settings (in PSS.DAT):
1. Identify and unzip the loadset where you want to change processor settings.
2. Locate the PSS.dat file and open it in a text editor. If PSS.dat has already been configured
for SLO, the file will resemble the following:
PSS||PSS_PROCESSOR_NAME|PSS_PROPERTY|PSS_VALUE
ADD||ScenarioTransformationProcessor|Is Active|True
ADD||ScenarioTransformationProcessor|Processing Phase|Preprocessing
ADD||ScenarioTransformationProcessor|Execution Order|1
ADD||ScenarioTransformationProcessor|TargetScenarioName|5Items-SLO
ADD||ScenarioTransformationProcessor|TargetScenarioModuleName|SLO
ADD||ScenarioTransformationProcessor|ImportTransition|True
ADD||ScenarioTransformationProcessor|InheritScenarioUserAccess|True
ADD||ScenarioAssociationProcessor|Processing Phase|Preloading
22
ADD||ScenarioAssociationProcessor|Execution Order|1
ADD||ScenarioAssociationProcessor|Is Active|true
ADD||ScenarioAssociationProcessor|User|<InsertUserNameHere>
END_OF_SET||||
3. In PSS.dat, add the property InheritScenarioUserAccess and set it to True.
4. Add the Scenario Association Processor properties, setting the User property to the name
of the user assigned to the MIPO scenario.
5. Save and close the PSS.DAT file.
6. Update and close the .zip archive.
Note: SDLT users can also enter these settings using the Processor Settings tab.
For Data Gateway users, these settings can be entered through the Processor Settings
tab in the SGLT.
23
24
Chapter 3:
Running SLO
T
his section provides instructions for running the SLO application. It describes how to start
the SLO application and import a MIPO user scenario. When the SLO application finishes
its optimization process, it will produce output results that can be viewed as reports and
exported back into the associated MIPO user scenario. This MIPO scenario can then be re-
optimized with the new SLO service level inputs to determine appropriate safety stock for each
inventory item will satisfiy the global service level defined in SLO.
Note: This feature relies on a software license agreement with SmartOps in order to be
activated.
This chapter discusses:

• Starting SLO
• Importing MIPO scenario
• Editing SLO input data
• Managing SLO scenarios
• Running SLO reports
• Exporting SLO data to MIPO
• Managing SLO alerts
25
Starting SLO
You can start the SLO module from the SmartOps Portal sign-in screen. Just enter your user name
and password in the appropriate field. Then click the dropdown list associated with the various
SmartOps modules to select SLO.
Click Sign In to start the SLO module.
Figure 3-1 Starting SLO
Note: You can also switch over to the SLO module any time while logged on to
another SmartOps module by clicking on Portal > SLO - Service Level
Optimization.
26
Chapter 3: Running SLO
Importing MIPO scenarios

The Import Scenario window allows you to load a MIPO user scenario into SLO. If you wish to
export the SLO-generated service levels back to MIPO, you must import a MIPO user scenario rather
than the base scenario, as any MIPO base scenario cannot be edited once it has been loaded into
MIPO. See the MIPO User Guide for more information about scenarios.
Figure 3-2 The Import Scenario window

As a reference, the Import Scenario window also provides a history of MIPO scenarios imported
into SLO. The history information includes the following information:
• MIPO scenario name
• SLO scenario name
• Loading Start and End date/time
• Status
27
The Import History is not limited to manual imports, but includes all unattended loads as well.
The Import History list defaults to 50 records. This default value can be changed in the
ImportConfigResources.properties file.
To import a MIPO scenario:
1. Click Data Set > Import Data Set to open the Import Scenario window.
Note: You must have privileges to access the Import Scenario

window.
2. From the list of MIPO scenarios, click the radio button associated with the scenario you
wish to import into SLO.
3. Click OK. You will be required to confirm your request.
4. From the Confirmation dialog box, click OK. The Manage Scenarios window appears.
5. Use the Manage Scenarios window to name the scenario and set configuration
parameters used by the SLO Import Processor.
6. Click OK. The scenario will be loaded into the SLO module. When completed, you will
see a message stating "Imported Scenario successfully."
The Scenario Import History table is updated to include information based on the
selected MIPO scenario, including the status of the import process.
Once the selected MIPO scenario is successfully imported into SLO, you will see the
status change to “Completed” in the Data Set Import History table. Additionally, the
Model and Scenario Selectors are refreshed to include the names of the data model/
scenario specified in the file you imported.
Note: If you have trouble importing the MIPO scenario, use the View Alerts feature to
determine if any alerts were generated during the Import process. See the section
entitled "Managing SLO Alerts" for more information on SLO alerts.
Editing SLO Input data

You can view and edit both Input and Output data in SLO. SLO allows you to make changes to both
static and time varying data for the stocking point inputs through the Edit menu.
In the MIPO application, a supply chain is modeled as a network of nodes where each node represents
an item-location pair. A node is also referred to as a stocking point for a specific item. Each node can
have upstream nodes, downstream nodes, or both. Each node is connected to its upstream and
28
downstream nodes by paths. SLO uses MIPO stocking point data to calculate service levels for each
item-location in the supply chain in order to achieve a global service level.
Stocking point static input data

Data that does not vary with time is considered to be static data in MIPO. Examples of static stocking
point data include target service level, holding cost percent, and unit cost. You can edit static inputs
for one or multiple stocking points in MIPO.
To edit static data for stocking points:
1. Use the scenario selector to choose the SLO user scenario you wish to edit.
2. Click Edit > Input Data > Stocking Point Data > Static to open the Edit Stocking
Point Data - Static window, shown in Figure 3-3.
Figure 3-3 Edit Stocking Point Data - Static window

3. Click the Browse (...) button to open the Node Selector. Use the Node Selector to
choose stocking points to edit.
4. Click OK to close the Node Selector.
29
5. The Edit Stocking Point Data - Static window is reloaded and contains the stocking
point or stocking points you selected on the left and all of the editable properties on the
right.
6. If numerous stocking points are returned, you can page through them by clicking the
arrows in the lower left corner of the window, or by entering a number in the Page field
and pressing ENTER.
7. Select the stocking points that you want to edit:
• Click an individual radio button to edit an individual stocking point.
• Click the All Stocking Points on all pages radio button to edit all stocking points.
8. Choose the method you want to use to specify your changes by clicking the one of the
following radio buttons:
• Click =x to assign a new value.
• Click +x or -x to increase or decrease by a specific value.
• Click +x% or -x% to increase or decrease a value by percentage.
Note: When editing values that have a predefined valid range (such as,
.50 to .999 for Target Service Level, 0 to 1 for Holding Cost
Percentage, and -1 to 1 for Schedule Attainment Loss Percentage)
and you attempt to enter an absolute value (=x) outside of that range, a
status message indicates that the value you entered is invalid and you
are prompted to enter a different value.
However, if you specify a relative change (+x or -x) or a percentage
change (+x% or -x%) that results in a value outside the valid range, the
value is automatically rounded up or down to the closest valid value.
For example, if the valid range is 0-1, the current value is .75, and you
increase it by 200%, the resultant value exceeds the valid range. In this
case, the new value that is saved for this property and displayed in the
user interface is one (1).
9. Identify the stocking point properties that you want to edit and enter new values in the
fields at the bottom of the appropriate columns.
Note: Viewing costs is a user privilege in MIPO. If you are not

authorized to view cost information, the Unit Cost property is not
displayed. As a result, you cannot edit this property.
Note: If the Initialization mode for this scenario is set to

Automatic in the Scenario Management window, you cannot
edit the value for On Hand Inventory.
30
10. Click OK to save your changes. The Edit Stocking Point Data - Static window is
reloaded and displays a status message indicating that the data was updated successfully.
The columns on the right reflect the changes you made.
Stocking point time varying input data (single period)

Data that varies with time is considered to be time varying data in MIPO. For nodes, examples of time
varying data include forecast demand mean, forecast demand standard deviation, and minimum stock.
To edit time varying data for stocking points for a single period:
2. Use the Period Selector to choose the period for which you want to edit data.
3. Click Edit > Input Data > Stocking Point Data > Time Varying to open the Edit
Stocking Point Data - Time Varying (Single Period) window, shown in Figure 3-4.
Figure 3-4 Edit Stocking Point Data - Time Varying (Single Period) window
6. The Edit Stocking Point Data - Time Varying (Single Period) window is reloaded. It
contains the stocking point or stocking points you selected on the left and all of the
editable properties on the right. Note that the stocking point and property names are
hyperlinks.
and pressing ENTER.
31

Note: You can edit Forecast Demand Mean and Forecast Demand
Standard Deviation for Customer Facing Stocking Points only. Also, if
you select more than one Node Type (for example, a combination of
Internal and Customer Facing nodes), the Forecast Demand Mean and
Forecast Demand Standard Deviation fields are not editable.
11. Click OK to save your changes. The Edit Stocking Point Data - Static (Single Period)
window is reloaded and displays a status message indicating that the data was updated
successfully. The columns on the right reflect the changes you made for the nodes you
selected.
Stocking point time varying input data (single node)

To edit multiple properties for a single node for all selected periods:
Stocking Point Data - Time Varying (Single Period) window.
hyperlinks.
32
and pressing ENTER.
8. To edit time-varying data for a single node for multiple periods, click on a stocking point
name.
9. The Edit Stocking Point Data - Time Varying (Single Node) window, shown in
Figure 3-5, opens. It contains the time-varying properties on the left and each of the
periods in the display horizon on the right. Note that the name of the node you are
editing is listed in the Choose Nodes to Edit field near the top of the window.
Figure 3-5 Edit Stocking Point Data - Time Varying (Single Node) window
11. Specify the length of time for which you want to apply your changes by specifying values
for the Edit Period From and Edit Period To fields. To do so, click the Browse (...)
button and use the Period Selector.
12. Identify the properties that you want to edit and enter new values in the fields to the right
of the appropriate rows. Note that your changes are applied for all periods you specified.
33
13. Click OK to save your changes. The Edit Stocking Point Data - Time Varying (Single
Node) window is reloaded and displays a status message indicating that the data was
updated successfully. The window reflects the change you made for the nodes and all
properties and periods you specified.
Note: You can change the stocking point for which you editing time-
varying properties by clicking the Browse (...) button next to the
Choose Stocking Points to Edit field. Use the Node Selector to
choose a different node or group of nodes to edit.
Stocking point time varying input data (single property)

To edit a single property for multiple nodes and periods:
Stocking Point Data - Time Varying (Single Period) window.
hyperlinks.
and pressing ENTER.
8. To edit a single property for single or multiple nodes and periods, click on a property
name.
9. The Edit Stocking Point Data - Time Varying (Single Property) window, shown in
Figure 3-6, opens. It contains the nodes on the left and each of the periods in the display
34
horizon on the right. Note that the name of the property you selected is listed in the
Choose Time Varying Properties drop-down menu near the top of the window.
Figure 3-6 Edit Stocking Point Data - Time Varying (Single Property) window
• Click the All Stocking Points on all pages radio button to edit all paths.
12. Identify the periods that you want to edit and enter new values in the fields at the bottom
of the appropriate columns or enter the same value for all periods by entering it in the
field in the first column.
35
13. Click OK to save your changes. The Edit Stocking Point Data - Time Varying (Single
Property) window is reloaded and displays a status message indicating that the data was
updated successfully. The window reflects the change you made for the property, nodes,
and periods you specified.
Note: You can change the stocking point for which you editing time-
varying properties by clicking the Browse (...) button next to the
Choose Stocking Points to Edit field. Use the Node Selector to
choose a different node or group of nodes to edit.
Auditing data changes

The Audit Data Changes feature lets you see what changes were made to specific scenario data, who
made specific changes, and when these changes were made. The Audit Data Changes window can
display all changes to input data for specific scenarios. You can also filter the display to narrow the list
of audit information.
To view the audit history, click Edit > Audit Data Changes. You will see the Audit Data Changes
window, which defaults to the last audit transaction, if any exists.
36
Figure 3-7 Audit Data Changes window
From the Audit Data Changes window, you can do the following:
• Set filters
• Select a specific audit transaction, including associated component if necessary
• Compare original data record to modified data record
Filtering audit records

When setting filters to display audit data, You can use the following categories:
• Data Type: Defaults to All data. You can select Input data or Output data.
• Audit Date: The default value is Today. You can select Last Five Days, Last Ten Days,
Last Thirty Days. You can also use the Calendar button to select a Date Range.
37
• Screen: Use dropdown list to view data changes associated with a specific SLO screen.
• User: Use dropdown list to view data changes associated with a specific SLO account.
Click any dropdown list to change the filter, and then click Refresh.
Note: When filtering audit records by date, Today means the last 24 hours. For
example, if you are filtering audit records from Today, and today is July 15 at 2:30pm,
you can see audit records that were generated on July 14 at 5pm, because it’s within the
24-hour window. The same applies to the settings for Last five days, Last ten days,
Last thirty days. However, when choosing a specific date (such as July 15, 2003 to July
15, 2003), you see audit records for only those dates.
Note: When you set specific filter options and click Refresh, SLO automatically saves
those filter options as a preference for you.
Selecting a specific audit transaction

The Audit Data Changes window lists transaction information, including:
• Date and time when the change was made
• Account name of user who made the change
• Type of change that was made
• Specific SLO screen used to make the change
To select a specific audit transaction, click its associated radio button.
Note: Certain audit transactions may involve multiple components. This is indicated by
an activated Component dropdown list. Click the Component dropdown list to select
specific component.
The associated records involved with the change appear at the bottom of the screen. You will see two
sets of records, the original and the modified record (yellow background). You can identify the change
by comparing the data in the original record to the modified record.
Adjusting date periods for specific audit transaction

You can further filter out unnecessary information by adjusting the start and end periods.
1. Click the [...] button. The Period selector appears.
2. Scroll through the list of periods and click which one you wish to view.
3. Click OK.
38
Analyzing and managing scenarios

The Manage Scenarios window lets you optimize SLO scenarios, create new SLO scenarios based
on existing SLO data., and delete existing SLO scenarios.
Figure 3-8 Manage Scenario window

When you apply changes to a SLO scenario, validate, optimize it, and view the new results (or
outputs), you are analyzing a scenario. You manage scenarios by duplicating and deleting them in SLO.
Note: The ability to analyze and manage scenarios is a user privilege in SLO. If you are
not authorized to analyze or manage scenarios, the Analyze > Manage Scenarios
menu item is disabled. In addition, you cannot view any scenario-related alerts.
39
Note: Scenario Access Control privileges are dynamically generated when a scenario is
created. If a you create a scenario and want other users to be able to access it, use the
Manage Scenario Access feature to add users.
Preparing the SLO scenario for optimization

If you select a SLO scenario, you can define certain data fields on the Manage Scenarios window that
will be used by SLO during the optimization process.
• Initialization - determines if the user specifies values for On Hand or if the value is
inferred by the application
• Minimization Objective - determines how SLO calculates cost minimizing as part of
the objective of achieving the defined global service level
• Global Service Objective - identifies whether or not SLO enforces the global target
service level constraint during optimization
• Global Service Level - defines the global target used by SLO during optimization
• Global Service Scope - specifies whether or not only demand streams with optimized
service levels contribute to the global service level constraint.
• Service Level Measure - identifies whether to calculate service level as a function of
cost or inventory quantity
• Start Period - the period from which calculation must begin for the selected scenario. All
horizons are measured relative to this period, which must be equal to Base Period for
base scenarios and greater than or equal to the value specified for user scenarios.
• Analysis Horizon - the number of periods beyond the start period (in other words, in
the future) for which accurate results are desired
• Data Horizon - the number of periods of data available for computation (optimization)
in SLO
• Historical Data Horizon - the amount of historical data available for creating a timeline
in SLO
• Distribution Type - indicates whether SLO uses a normal distribution algorithm or a
gamma distribution algorithm when calculating inventory targets
• Adjust Safety Stock for Bias - indicates whether SLO will adjust safety stock
requirements by the positive forecast bias determined by DIM.
• Demand Timing Uncertainty - indicates whether SLO applies advanced logic to
calculate safety stock requirements for intermittent SKUs as determined by DIM.
• BA Inputs Stop Severity - signals SLO to halt the validation process whenever an Input
business alert of the selected severity is generated.
40
• BA Outputs Stop Severity - signals SLO to halt the validation process whenever an
Output business alert of the selected severity is generated.
Perform the following steps to edit information about the SLO scenario:
1. Use the Supply Chain Selector to select the supply chain for which you want to create a
user scenario.
2. Click Analyze > Create User Scenario to open the Manage Scenarios window. The
Supply Chain Name field contains the name of the supply chain you selected.
3. Enter the name of the user scenario you are creating in the Scenario Name field.
Note: The following special characters are not supported for use
in scenario names: single quote (‘), double quote (”), backslash (\),
angle brackets (>,<), ampersand (&), and pipe (|).
4. Enter a brief description of the scenario in the Description field, if desired.

5. Select the desired Initialization option from the drop-down menu:
• If you select User-specified, you must enter a value for On Hand Inventory when
creating or editing a stocking point. Failing to enter a value for On Hand Inventory
causes a Missing On Hand alert to be generated during validation. In addition,
entering a value for Planned Receipts for each supply path is optional.
• If you select Automatic, the system calculates a value for On Hand Inventory for
each stocking point and Planned Receipts for each supply path. You cannot enter
or edit these values for On Hand Inventory or Planned Receipts when creating or
editing stocking points or supply paths.
Note: If you change the Initialization option of a supply chain

(Base scenario, not upgraded) or user scenario, it must be
re-validated and re-optimized. In addition, if you change the
Initialization option from Automatic to User-specified, you
must enter On Hand Inventory values for stocking points to
avoid a validation alert.
6. Select the Minimization Objective option from the drop-down menu:

• If you select Sum of Safety Stock Holding Cost and Lost Margin, SLO will
generate its global service level based on minimizing the total holding cost for all
safety stock and all lost sales associated with not meeting demand.
• If you select Total Safety Stock Holding Cost, SLO will generate its global service
level based on minimizing the total holding cost for safety stock only. Note: When
this option is selected, the Global Service Objective option will be disabled.
41
7. If available, select the Global Service Objective from the drop-down menu. Yes
indicates that SLO enforces the global target service level constraint. No indicates that
the constraint need not be enforced during optimization.
8. Enter a Global Service Level to be used by SLO as the global target during
optimization.
9. Select the Service Level Measure from the drop-down menu; either Units or Dollars.
10. Select an Owner of the supply chain. If it is a different user, click the Browse (...) button
to open the User Selector:
b. If you select All, a list of all users is displayed; click the desired user name and click
11. Note that the Period Length of the scenario cannot be edited; it specified when the
supply chain is created.
12. Click the Browse (...) button to open the Period Selector. Use the Period Selector to
specify a Start Period for the scenario.
Note: For user scenarios, the value you enter for the Start Period
must be greater than or equal to the value entered for the Base
Period.
13. Enter a value in the Analysis Horizon field. The analysis horizon is the number of periods
beyond the start period (in other words, in the future) for which accurate results are
desired.
14. Enter a value in the Data Horizon field. The data horizon is the number of periods of
data available for computation (optimization) in MIPO. The value entered for data
horizon must be greater than or equal to the value entered for the analysis horizon.
15. Enter a value in the Historical Data Horizon field.
16. Note that the Service Level of the scenario cannot be edited; it is specified as Fill Rate,
indicating that the service level will be calculated as a ratio of the total number of units
over a given period
17. Select the Distribution Type to use for optimization. The default is Normal, but
Gamma distribution can be used to improve the accuracy of inventory target for items
42
with demand error distributions with long tails (e.g., items with lumpy demand, items
with intermittent demand, or slow-moving items).
18. Select the dropdown list for Use DIM Outputs? to the desired setting. This parameter
indicates whether or not SLO should use the output values from the DIM module when
optimizing the scenario.
19. Select the Business Alerts Stop Severity for both Inputs and Outputs by clicking the
corresponding dropdown list. This signals SLO to halt the validation process whenever a
business alert of the selected severity is generated. See the section entitled “Business Alert
Settings” in the MIPO Installation and Upgrade Guide for more information about Business
Alerts.
20. Click OK to save your changes.
Note: Processes invoked when you create a scenario can take

some time to execute. During this time, you can continue using the
SLO application. To determine the status of a scenario-related
process, click Analyze > Manage Scenarios to open the
Manage Scenarios window. Then click REFRESH to view the
Scenario Status.
The Manage Scenarios window is refreshed, and contains a status message indicating whether the
user scenario was saved successfully. If the scenario was saved successfully, and you are the owner, the
Scenario Selector displays the name of the user scenario you created. In addition, the following fields
contain updated information:
• Scenario Status - indicates the status of the scenario; if the user scenario was created
successfully, this field reads “Created, not validated.”
• Base scenario modified? - indicates whether or not changes have been made to the
base scenario
• Last Modified (GMT) - the date and time (in Greenwich Mean Time) that the
supply chain was last changed
• Modified By - the user name of the person who last modified the supply chain
• Base Period - the latest recognized date in the database when historical data
transitions to forecast data
• Calculation Horizon - represents the number of periods forward that MIPO
provides calculations. If the start period is the same as the base period, this number
will be equal to the data horizon. If the start period is after the base period (e.g., 3
periods), then the calculation horizon will be less than the data horizon (e.g., data
horizon - 3).
• End Horizon - the last period deemed as having reliable output data throughout the
supply chain
43
• Audit History Exists? - identifies if input or output data had been updated in the
scenario via a check box indicator. You can review the specific data changes for the
scenario by clicking Edit > Audit Data Changes.
21. The Scenario Audit Information panel is displayed in the Manage Scenarios window.
It displays information about tasks performed on the selected scenario, including when
the scenario was created, the Scenario Status of validation and optimization, and the
Date and Time (GMT) that the tasks occurred.
Optimizing the SLO scenario

Before you can view the results (or outputs) of the changes you make to a SLO scenario, it must be
validated and optimized. Validation ensures that the scenario is structurally and logically consistent
with the algorithms used to calculate outputs in SLO. When you optimize a scenario, the data it
contains is used by SmartOps algorithms to calculate new results based on the changes you made.
Note: The ability to optimize a user scenario is a user privilege in SLO. If you are not
authorized to optimize a scenario, the TASKS > Optimize Scenario menu item is
disabled in the Manage Scenarios window.
Perform the following steps to optimize a scenario:

1. Use the Supply Chain Selector to select the SLO scenario you want to optimize.
2. Click Analyze > Manage Scenarios to open the Manage Scenarios window.
Note: If you select a scenario for optimization that has not yet been validated, it will be
validated automatically before the optimization process begins.
3. Click TASKS > Optimize Scenario. The Manage Scenarios window is refreshed and
displays a status message indicating that the scenario is being optimized. In addition, the
Scenario Audit Information is updated to reflect the status of the optimization process.
Note: The amount of time it takes to optimize a scenario depends on the quantity of data
it contains. While a scenario is being optimized, the Manage Scenarios window is peri-
odically reloaded. To annually reload the Manage Scenarios window during optimiza-
tion, click REFRESH. To cancel optimization, click TASKS > Cancel Optimization.
4. When optimization of the scenario is complete, the Manage Scenarios window displays
a status message indicating that optimization is complete. In addition, the Scenario
Audit Information indicates that optimization is complete, and whether or not the
scenario was optimized successfully:
Note: If the scenario contains validation errors that prevent it from being optimized suc-
cessfully, you must correct them before continuing. To determine the origin of errors,
click Alerts > View Alerts to view the alerts associated with the scenario. For specific
information about the incorrect data, identify the specific alert and view the alert details.
44
Duplicating SLO scenarios

If there is an existing SLO scenario to which you want to make small changes, duplicating it and
making changes to the copy can save time and decrease the likelihood that you will introduce errors.
To duplicate a SLO scenario:
1. Use the Supply Chain Selector to select the SLO scenario you want to duplicate..
3. Click TASKS > Duplicate Scenario. A dialog box opens and prompts you to enter a
name for the copy of the scenario.
4. Enter a name in the Enter the new scenario name field and click OK.
Note: The following special characters are not supported for use
in scenario names: single quote (‘), double quote (”), backslash (\),
angle brackets (>,<), ampersand (&), and pipe (|).
Note: Processes invoked when you duplicate a scenario can take

MIPO application. To determine the status of a scenario-related
Scenario Status.
5. The Manage Scenarios window is reloaded and displays a status message indicating that
scenario copy was created successfully. The name you entered for the copy of the
scenario is displayed in the Supply Chain Selector.
6. Enter a brief description of the scenario in the Description field, if desired.
7. Select the desired Initialization option from the drop-down menu:
• If you select User-specified, you must enter a value for On Hand Inventory when
creating or editing a stocking point. Failing to enter a value for On Hand Inventory
causes a Missing On Hand alert to be generated during validation. In addition,
entering a value for Planned Receipts for each supply path is optional.
• If you select Automatic, the system calculates a value for On Hand Inventory for
each stocking point and Planned Receipts for each supply path. You cannot enter
45
or edit these values for On Hand Inventory or Planned Receipts when creating or
editing stocking points or supply paths.
Note: If you change the Initialization option of a supply chain

(Base scenario, not upgraded) or user scenario, it must be
re-validated and re-optimized. In addition, if you change the
Initialization option from Automatic to User-specified, you
must enter On Hand Inventory values for stocking points to
avoid a validation alert.
8. Select the Minimization Objective option from the drop-down menu:

• If you select Sum of Safety Stock Holding Cost and Lost Margin, SLO will
generate its global service level based on minimizing the total holding cost for all
safety stock and all lost sales associated with not meeting demand.
• If you select Total Safety Stock Holding Cost, SLO will generate its global service
level based on minimizing the total holding cost for safety stock only. Note: When
this option is selected, the Global Service Objective option will be disabled.
9. If available, select the Global Service Objective from the drop-down menu. Yes
indicates that SLO enforces the global target service level constraint. No indicates that
the constraint need not be enforced during optimization.
10. Enter a Global Service Level to be used by SLO as the global target during
optimization.
11. Select the Service Level measure from the drop-down menu; either Units or Dollars.
12. Select an Owner of the supply chain. If it is a different user, click the Browse (...) button
to open the User Selector:
b. If you select All, a list of all users is displayed; click the desired user name and click
11. Note that the Period Length of the scenario cannot be edited; it specified when the
supply chain is created.
46
12. Click the Browse (...) button to open the Period Selector. Use the Period Selector to
specify a Start Period for the scenario.
Note: For user scenarios, the value you enter for the Start Period
must be greater than or equal to the value entered for the Base
Period.
13. Enter a value in the Analysis Horizon field. The analysis horizon is the number of periods
beyond the start period (in other words, in the future) for which accurate results are
desired.
14. Enter a value in the Data Horizon field. The data horizon is the number of periods of
data available for computation (optimization) in MIPO. The value entered for data
horizon must be greater than or equal to the value entered for the analysis horizon.
15. Enter a value in the Historical Data Horizon field.
16. Note that the Service Level of the scenario cannot be edited; it specified; it is specified
as Fill Rate, indicating that the service level will be calculated as a ratio of the total
number of units over a given periodSelect the Distribution Type to use for
optimization. The default is Normal, but Gamma distribution can be used to improve the
accuracy of inventory target for items with demand error distributions with long tails
(e.g., items with lumpy demand, items with intermittent demand, or slow-moving items).
17. Select the dropdown list for Use DIM Outputs? to the desired setting. This parameter
indicates whether or not SLO should use the output values from the DIM module when
optimizing the scenario.
18. Select the Business Alerts Stop Severity for both Inputs and Outputs by clicking the
corresponding dropdown list. This signals SLO to halt the validation process whenever a
business alert of the selected severity is generated. See the section entitled “Business Alert
Settings” in the MIPO Installation and Upgrade Guide for more information about Business
Alerts.
19. Click OK to save your changes.
Note: Processes invoked when you create a scenario can take

Scenario Status.
The Manage Scenarios window is refreshed, and contains a status message indicating whether the
user scenario was saved successfully. If the scenario was saved successfully, and you are the owner, the
Scenario Selector displays the name of the user scenario you created. In addition, the following fields
contain updated information:
47
• Scenario Status - indicates the status of the scenario; if the user scenario was created
successfully, this field reads “Created, not validated.”
• Base scenario modified? - indicates whether or not changes have been made to the
base scenario
• Last Modified (GMT) - the date and time (in Greenwich Mean Time) that the
supply chain was last changed
• Modified By - the user name of the person who last modified the supply chain
• Base Period - the latest recognized date in the database when historical data
transitions to forecast data
• Calculation Horizon - represents the number of periods forward that MIPO
provides calculations. If the start period is the same as the base period, this number
will be equal to the data horizon. If the start period is after the base period (e.g., 3
periods), then the calculation horizon will be less than the data horizon (e.g., data
horizon - 3).
• End Horizon - the last period deemed as having reliable output data throughout the
supply chain
• Audit History Exists? - identifies if input or output data had been updated in the
scenario via a check box indicator. You can review the specific data changes for the
scenario by clicking Edit > Audit Data Changes.
20. The Scenario Audit Information panel is displayed in the Manage Scenarios window.
It displays information about tasks performed on the selected scenario, including when
the scenario was created, the Scenario Status of validation and optimization, and the
Date and Time (GMT) that the tasks occurred.
Managing scenario access

This feature lets the owners of specific user scenarios to provide access privileges to other SmartOps
application user accounts.
Perform the following steps to provide scenario access to another user account:
1. Use the Supply Chain Selector to select the SLO user scenario for which you want to
provide access.
2. Click Analyze > Manage Scenario Access to open the Manage Scenario Access
screen.
3. If the user account hasn't been assigned access privileges, click the account name listed
under the Unassigned Users window. To assign Read-Only privileges, click the [>]
arrow next to the Read-Only Users window. The account name will move from the
Unassigned Users window to the Read-Only window. Similarly, you can assign Full-
Access privileges the same way.
48
Note: You must be assigned as the owner of the selected supply chain or user scenario to
use this feature. The blue user account indicates the scenario owner.
4. If you want to change access privileges for a user account, click the user account and use
the arrow keys to change access to either Read-Only, Unassigned or Full-Access.
5. Click OK. You will see a message indicating that the scenario access privileges have been
saved.
Deleting a SLO scenario
Note: The ability to delete data models and base scenarios are user privileges in SLO. If
you are not authorized to delete data models and base scenarios, the TASKS > Delete
menu item is disabled.
To delete a scenario:
1. Use the Supply Chain Selector to select the SLO scenario you want to delete.
3. Choose TASKS > Delete Scenario.
4. A confirmation dialog opens and prompts you confirm the deletion.
Note: Processes invoked when you delete a SLO scenario can take
Manage Scenarios window. Then check Scenario Audit
Information for the latest status.
5. Click OK to delete the SLO scenario. The Manage Scenarios window is reloaded and it
displays a status message indicating that the scenario has been deleted.
Deleting multiple scenarios
Note: The ability to delete SLO scenarios are user privileges in SLO. If you are not
authorized to delete data models and base scenarios, the Analyze > Delete Scenarios
menu item is disabled.
To delete multiple scenarios at the same time:

1. Click Analyze > Delete Scenarios to open the Delete Scenarios window.
2. Click the check box associated with each scenario you wish to delete. Click Select All to
delete all scenario data from SLO.
49
3. Click Delete.
A confirmation dialog opens and prompts you confirm the deletion.
Note: Processes invoked when you delete a data model and base
scenario can take some time to execute. During this time, you can
continue using the SLO application. To determine the status of a
scenario-related process, select the supply chain and scenario of
interest in the selection, click Analyze > Manage Scenarios to
open the Manage Scenarios window. Then check Scenario
Audit Information for the latest status.
4. Click OK to delete the selected scenarios. The Delete Scenarios window is reloaded and
it displays a status message indicating that the selected scenarios have been successfully
deleted.
Running SLO reports

The SLO module includes reports based on both input and output data. You can generate the
following reports:
• Stocking Point Static Inputs
• Stocking Point Time Varying Inputs
• Master Summary
• Inventory Summary
• Stocking Point Static Outputs
• Stocking Point Time Varying Outputs
50
Stocking Point Static Inputs Report

The Stocking Point Static Inputs Report, shown in Figure 3-9, displays inputs for stocking points. The
report results are non-interactive and can be viewed only in a table.
Figure 3-9 Stocking Point Static Inputs report results
Note: Viewing report contents that are expressed as a dollar amount (cost) is a user
privilege in MIPO. If you are not authorized to view dollar amounts, you can only view
the sections of this report that are expressed in unit amounts.
For the Stocking Point Static Inputs Report, information listed in Table 3-1 is displayed.
Result Description
Target Service Level The minimum acceptable service level that a company feels they must
achieve.
Input Mechanism Specifies if the service level on the stocking point was calculated by
SLO or is a MIPO input. Valid values are either Input or Optimized.
Service Time The number of periods between the time an order is placed and the
time it must be shipped before a stockout is considered to have
occurred.
Holding Cost Percentage The cost associated with holding inventory at a stocking location. It is
expressed as a percentage of unit cost.
Table 3-1 Stocking point static inputs
51
Result Description
Unit Cost Represents the dollar value of one unit of inventory (expressed in the
specified unit of measure) for a given time at a given stocking location.
This cost may include partial processing (for example, assembly or
painting) cost on the raw material or components.
Unit Purchase Cost The inbound acquisition cost or transfer price for each item-location.
Unit Transfer Price The price at which a stocking point sells a unit of a product to its
downstream stocking point (its customer).
On Hand Inventory All inventory that is physically available to fill demand, which is all types
of stock except pipeline. Specifically, on hand inventory includes cycle,
safety, merchandising, and prebuild (if applicable) stock.
Unusable On Hand Inventory Unusable On Hand inventory is the portion of On Hand inventory that
should not be considered when calculating inventory targets as it
cannot be used to satisfy demand.
UOM Name The standard unit in which the quantity of an item is managed.
Examples of units of measure include inches, pounds, gallons, and
pallets.
Periods Between Reviews (PBR) The value of periods between review for a given item at a given location
is the frequency at which shipments of that item are received from
upstream locations. In other words, it is an average order period.
Periods Since Last Review (PSLR) For a given item at a given location is the number of periods since
placing a replenishment order or determining (based on inventory) to
not place an order.
Pooling Factor A heuristic adjustment made to the safety stock computation based on
the perceived correlation of demand across customer-facing nodes.
Maximum Ship Life The maximum number of periods an item can remain at a given node
before it becomes unusable.
Coverage Duration The number of periods over which Weeks of Stock is averaged to
determine the Average Safety Stock Coverage.
Schedule Attainment Loss The percentage of scheduled production that is expected to be missed.
Percentage
Schedule Attainment CV The coefficient of variation of the loss percentage.
For example, if the loss percentage is 0.2 and the coefficient of

variation is 0.5, then actual production can expect to be short 20% +/-
10% of the scheduled production.
52
Result Description
Minimum Service Level An optional field used by the SmartOps Service Level Optimization
(SLO) module to define the lower limit on the individual target fill rate
at the associated customer-facing stocking point.
Maximum Service Level An optional field used by the SmartOps Service Level Optimization
(SLO) module to define the upper limit on the individual target fill rate
at the associated customer-facing stocking point.
Lost Sales Percentage An optional field used by the SmartOps Service Level Optimization
(SLO) module to define the acceptable lost sales percentage to be
applied at the minimum service level at the associated customer-facing
stocking point.
Processing Cost The per unit cost of manufacturing and assembly for each item-
location.
Transportation Cost The cost of moving an item from an upstream node to an immediate
downstream node for a given inventory stocking location.
Order Administration Cost The per unit cost of administering an order for each item-location.
Handling Cost The cost of material movements within the warehouse, which may
include unloading costs, breakdown costs, labor costs, and machinery
costs
Other Cost Miscellaneous expenses, including taxes and insurance, related to

keeping inventory.
To create a Stocking Point Static Inputs report:

1. Use the Supply Chain Selector to select the supply chain for which you want to
generate the report.
2. Use the Scenario Selector to select the base or user scenario for which you want to
3. Click Reports > Input Reports > Stocking Points > Static Data to open the
Stocking Point Static Inputs Report window. By default, the window displays results
for all customer facing stocking points.
select a different set of nodes for which to generate the report, if desired. Click OK to
close the Node Selector.
53
5. Click Refresh. The Stocking Point Static Inputs Report window is reloaded
containing the new results in table format. You cannot view this report in a chart.
Note: You can change the Period for which you are generating
this report. To do so, use the Period Selector to select a different
period. You are prompted to refresh the contents of the report.
Click OK. The contents of the report are updated using the new
period you selected.
Stocking Point Time Varying Inputs Report

The Stocking Point Time Varying Inputs Report, shown in Figure 3-10, displays time-varying inputs
for stocking points. The report results are interactive, but can be viewed only in table format.
Figure 3-10 Stocking Point Time Varying Inputs report result for a single period
For the Stocking Point Time Varying Inputs Report, information listed in Table 3-2 is displayed.
Result Description
Input Forecast Demand Mean An estimate of the mean demand for the product at that stocking
location during a given period
Table 3-2 Stocking point time varying inputs
54
Result Description
Input Forecast Demand Standard Characterizes the difference between forecasted and actual demand. It
Deviation is a statistical measure of forecast accuracy and can be used to estimate
the variability of the underlying demand.
Minimum Required Stock Minimum inventory kept in a retail or customer-facing location. It may
be used for showroom or demonstration purposes, but is typically
included in inventory available to meet demand. In addition, this report
displays information about any custom properties created for your
supply chain.
Table 3-2 Stocking point time varying inputs
To create a Stocking Point Time Varying Inputs Report for a single period:
1. Use the Supply Chain Selector to select the supply chain for which you want to
2. Use the Scenario Selector to select the base or user scenario for which you want to
3. Click Reports > Input Reports > Stocking Points > Time Varying Data to open the
Stocking Points Time Varying Inputs Report (Single Period) window. By default,
the window displays results for all customer facing stocking points.
4. To select a different set of nodes for which to generate the report, click the Browse (...)
button to open the Node Selector. Select the nodes and click OK to close the Node
Selector.
5. Click Refresh. The Stocking Point Time Varying Inputs Report (Single Period)
window is reloaded containing the new results in table format. Note that the node names
and time-varying properties are hypertext links.
Note: The default period on which this report is based is determined by the values of
the Base Period and Data Horizon for the scenario.
55
Stocking Point Time Varying Inputs - Single Property

The Stocking Point Time Varying Inputs Report is an interactive report. To view an individual
property for all nodes for all periods, as shown in Figure 3-11, click the name of the desired property
in the top row of the report table.
Figure 3-11 Stocking Point Time Varying Inputs report results for a single property
The results are displayed in the Stocking Point Time Varying Inputs Report (Single Property)
window for all periods. The property you selected is displayed in the Time Varying Properties field.
You can change the Stocking Points for Report, the Start and End periods, and the Time Varying
Properties for the report by clicking the Browse (...) button next to each field, respectively.
56
Stocking Point Time Varying Inputs - Single Node

The Stocking Point Time Varying Inputs Report is an interactive report. To view all properties for an
individual node for all periods, as shown in Figure 3-12, click the name of the desired node in the first
column of the report table.
Figure 3-12 Stocking Point Time Varying Inputs report results for a single node
The results are displayed in the Stocking Point Time Varying Inputs Report (Single Node)
window for all periods. The name of the node you selected is displayed in the Stocking Points for
Report field. You can change the Stocking Points for Report and the Start and End periods for the
report by clicking the Browse (...) button next to each field, respectively.
Master Summary Report

The Master Summary Report, shown in Figure 3-13, is a read-only, non-interactive report that displays
the overall revenue, supply chain cost, and the inventory investment by attribute and by target
inventory position (TIP) component. Results are generated for customer-facing stocking points and
internal stocking points for the chosen supply chain and scenario for the specified period.
The service level calculations used to generate the Master Summary Report include the following
options:
• Straight Average - displays average service levels based on a average of the service level
from all customer facing stocking points.
• Forecasted Unit Volume Weighted - displays unit service levels based on weighted
averaging for units.
• Forecasted Inventory Cost Weighted - displays dollar service levels based on weighted
averaging for cost.
These options can be found using the Preferences button on the report.
57
The following sections describe the results included in the Master Summary Report in more detail.
Figure 3-13 Master Summary report results
privilege in MIPO. If you are not authorized to view dollar amounts, you are not
authorized to create a Master Summary report.
58
Revenue
In the Master Summary Report, the overall revenue results include information about the outputs
listed in Table 3-3.
Result Description
Average Customer Target Service Service level is a metric that refers to the probability that demand is met
Level from stock. Average customer target service level is determined by
calculating the end-customer service level using the Forecast Mean
weighted average of service levels for all customer-facing stocking
points.
Average Customer Service Time Average customer service time is determined by calculating the average
(not weighted) service time for all customer-facing stocking points.
Service time is the number of periods between the time an order is
placed and the time it must be shipped before a stockout is considered
to have occurred.
Unit Sales The unit sales per period is determined by calculating the sum of
forecast mean for all customer facing stocking points. The sum of unit
sales is obtained and then averaged, resulting in a unit sales average for
all periods.
Average Unit Sales Price Average unit sales price is the average price at which a unit of inventory
is sold at customer facing stocking points. It is determined by dividing
the total estimated revenue by unit sales.
Total Forecasted Revenue The total forecasted revenue is determined as the sum of revenue for
each customer facing stocking point by multiplying the forecast mean
and the unit transfer price for all periods.
Total Lost Margin The total lost margin is determined as the sum of lost sales for each
customer facing stocking point over all periods.
Table 3-3 Revenue results for the Master Summary report
Supply Chain Cost

In the Master Summary Report, the supply chain cost results include information about the outputs
listed in Table 3-4.
Result Description
Material Cost Material cost is determined by multiplying the forecast mean and
component cost for all stocking points. The sum of the results is
obtained for each period, resulting in an average component cost for all
periods.
Table 3-4 Supply chain cost results for the Master Summary report
59
Result Description
Transportation Cost Material transportation cost is determined by multiplying the forecast
mean and transportation cost for all stocking points. The sum of the
results is obtained for each period, resulting in an average component
transport cost for all periods.
Processing Cost Processing cost is the per unit cost of manufacturing and assembly for
each item-location. For this report, it is determined by multiplying the
forecast mean and processing cost for all stocking points. The sum of
the results is obtained for each period, resulting in an average
processing cost for all periods.
Inventory Holding Cost Inventory holding cost is the cost associated with holding inventory at a
stocking location. For this report, inventory holding cost is determined
by calculating the total chain inventory investment, which is the sum of
average pipeline stock, average safety stock, average cycle stock, average
prebuild stock, and average merchandising stock. The total chain
inventory investment, holding cost percentage, and unit cost totals are
then multiplied for each period for all stocking points. The sum of the
results is obtained for each period, resulting in an average inventory
holding cost for all periods.
Order Administration Cost Order administration cost is the per unit cost of administering an order
for each item-location. For this report, it is determined by multiplying
the forecast mean and order administration cost for all stocking points.
The sum of the results is obtained for each period, resulting in an
average order administration cost for all periods.
Handling Cost Handling cost is the cost of material movements within the warehouse,
which may include unloading costs, breakdown costs, labor costs, and
machinery costs. For this report, handling cost is determined by
multiplying the forecast mean and handling cost for all stocking points.
The sum of the results is obtained for each period, resulting in an
average handling cost for all periods.
Other Cost Other costs are miscellaneous expenses, including taxes and insurance,
related to keeping inventory. For this report, other costs are determined
by multiplying the forecast mean and other costs for all stocking points.
The sum of the results is obtained for each period, resulting in an other
costs average for all periods.
Total Estimated Cost Sum of Supply Chain Costs.
Table 3-4 Supply chain cost results for the Master Summary report
60
Inventory Investment
In the Master Summary Report, the inventory investment by attribute and by TIP component includes
information about the outputs listed in Table 3-5.
Result Description
Average Safety Stock Average safety stock is a buffer added to inventory to counteract
stockouts when demand and lead times are uncertain. The amount of
safety stock is typically determined based on a specified service level
and the associated variability in demand and lead times. For this report,
average safety stock is determined by multiplying the safety stock and
the unit cost for all stocking points. The sum of the results is obtained
for each period, resulting in an average safety stock average for all
periods.
Average Cycle Stock Average cycle stock is a component of the average inventory position at
a stocking location for a specified item and a specified period. It
corresponds to the portion of average on hand inventory that exists to
cover demand between shipments (replenishments). For this report,
average cycle stock is calculated by doubling the cycle stock, subtracting
from it the forecast mean, dividing that number in half, and multiplying
it with the unit cost for all stocking points. The sum of the results is
obtained for each period, resulting in an average cycle stock average for
all periods.
Average Prebuild Stock Prebuild stock is inventory built due to capacity constraints in
anticipation of future demand. For this report, average prebuild stock is
determined by multiplying the prebuild stock and the unit cost for all
stocking points. The sum of the results is obtained for each period,
resulting in an average prebuild stock average for all periods.
Average Merchandising Stock Merchandising stock is the minimum inventory kept in a retail or
customer-facing location. It may be used for showroom or
demonstration purposes, but is typically included in inventory available
to meet demand. It is also known as minimum stock, showroom
inventory, or display stock. Note that merchandising stock is different
than safety stock. It is an additional component of inventory over and
above the safety stock needed to accommodate supply and demand
uncertainties. For this report, average merchandising stock is
determined by multiplying the merchandising stock and the unit cost
for all stocking points. The sum of the results is obtained for each
period, resulting in an average merchandising stock average for all
periods.
Table 3-5 Inventory investment results for the Master Summary report
61
Result Description
Average Pipeline Stock Average pipeline stock represents all inventory for which a
replenishment order has been placed but not yet received. For this
report, average pipeline stock is determined by multiplying the average
physical pipeline stock and the unit cost for all stocking points. The
sum of the results is obtained for each period, resulting in an average
pipeline stock average for all periods.
Total Chain Inventory Sum of Inventory Investments.

Investment
Table 3-5 Inventory investment results for the Master Summary report
Turns
In the Master Summary Report, the number of turns is determined by dividing the annualized cost of
goods sold (COGS) by the average on hand inventory. An inventory turn is the number of times that a
company’s inventory cycles over per year (or per a specified time period). Lower inventories result in
higher inventory turns.
Result Description
Turns Annualized Cost of Goods Sold (COGS) / Average on hand inventory.
Table 3-6 Turn results for the Master Summary report
Note: Results for the Master Summary Report can contain an entry called Unassigned.
This entry is displayed when one or more stocking points is not assigned an attribute
value. The sum of relevant data for all such stocking points is displayed under this
heading.
To generate a Master Summary Report:
1. Use the Supply Chain Selector to select the SLO scenario for which you want to
Note: The scenario you select must be optimized before you can
view the Master Summary Report.
2. Click Reports > Output Reports > Master Summary to open the Master Summary
Report window.
62
3. Click Refresh. The Master Summary Report window opens containing the report
results in a table. You cannot view this report in a chart.
4. To change the period for which you are creating the report, specify different Start and
End periods. If you select starting and ending periods that are the same, the results of the
report will be based on a single period. The contents of the report are updated using the
new period you selected.
Note: The default period on which this report is based is

determined by the values of the Start Period and End Horizon
for the scenario.
5. To change the preference for service level calculation, click Preferences, then click the
associated radio button for the preference you prefer, then click OK to regenerate the
report. There are three service level calculations that can be used for the report:
• Straight Average - displays average service levels based on a average of the service
level from all customer facing stocking points.
• Forecasted Unit Volume Weighted - displays unit service levels based on weighted
averaging for units.
• Forecasted Inventory Cost Weighted - displays dollar service levels based on
weighted averaging for cost.
Assigning the STAGE attribute

The STAGE attribute is a node attribute used to group stocking points into different levels in a supply
chain in MIPO. It is the default method of displaying inventory quantities in the Master Summary and
Inventory Summary output reports. The number and names of stages in a supply chain are specific to
your supply chain. The number of stages and their names are defined by your organization and must
be created using the MIPO interface, uploaded from a .zip file, or loaded through the Data Gateway
and are then assigned to each node as appropriate.
For example, the stages in a supply chain could resemble the following:
• Suppliers
• Manufacturing
• Assembly
• Dealers
For the Master Summary and Inventory Summary reports results to be meaningful and accurate, each
stocking point in your supply chain must be assigned a STAGE attribute value. If a stocking point is
not assigned a STAGE attribute value, the results for the Master Summary and Inventory Summary
reports contain a column called Unassigned. The sum of relevant data for stocking points not
associated with a STAGE is displayed under this heading.
63
Sorting STAGES
STAGE attribute values in MIPO are sorted alphabetically. To guarantee that stages are sorted
according to the order that they occur in the supply chain, you must enter STAGE attribute values as
names preceded by a two-digit number value. For example, for the following stages to be sorted
according to the order they occur in a supply chain, they must be named as follows:
• 01 - Suppliers
• 02 - Manufacturing
• 03 - Assembly
• 04 - Dealers
Note: A zero must precede a one-digit number for the stages to be ordered correctly.
For example, if you use the numbers 1, 2, 10, 11, and 21 preceding the names of stages,
they would be returned as 1, 10, 11, 2, and 2.
Using a Node Attribute other than STAGE

You can group stocking point inventories in the Master Summary and Inventory Summary reports
using a node attribute other than the STAGE attribute. To do so, you must change the value of the
following setting in the ReportConfigResources.properties file:
report.STAGE_ATTRIBUTE_NAME=STAGE
For example, if you wanted to group stocking points according to the node attribute “COUNTRY”
the entry in the ReportConfigResources.properties file would be:
report.STAGE_ATTRIBUTE_NAME=COUNTRY
Note: The value of the report.STAGE_ATTRIBUTE_NAME setting is case-sensitive. An

attribute named “COUNTRY” is a different attribute than one named “Country”.
Ensure that you name and assign attributes consistently.
In addition, you would need to create attribute values similar to the following, and assign them to each
stocking point appropriately. Note that it's not necessary to ensure that the names coincide with an
particular order in the physical supply chain:
• United States
• Canada
• Mexico
• France
• Germany
• Brazil
64
Inventory Summary Report

The Inventory Summary Report, shown in Figure 3-14, is an interactive report that summarizes the
TIP or average inventory position (AIP) and its components, as a cost, averaged for the selected
periods as totals by attribute. The results of the report can be based on an entire supply chain or on a
selected group of nodes and can be viewed as a table or in a chart. For this report, AIP is determined
by adding the average cycle stock, average prebuild stock, average safety stock, average pipeline stock,
and average merchandising stock. The average inventory position on hand is determined by
subtracting the average pipeline stock from the average inventory position total.
Figure 3-14 Inventory Summary report results
privilege in MIPO. If you are not authorized to view dollar amounts, you cannot view
this report.
Note: Results for the Inventory Summary Report can contain a column called
Unassigned. This entry is displayed when one or more stocking points is not assigned
an attribute value. The sum of relevant data for all such stocking points is displayed
under this heading.
To create an Inventory Summary Report:
65
view the Inventory Summary Report.
2. Click Reports > Output Reports > Inventory Summary to open the Inventory
Summary Report window. By default, the window displays results for all stocking
points.
3. If you want to select a different set of stocking points, click the Browse (...) button next
to the Stocking Points for Report field to open the Node Selector. Use the Node
Selector to select a different set of stocking points for which to generate the report. Click
OK to close the Node Selector.
4. To change the period for which you are creating the report, specify different Start and
End periods. If you select starting and ending periods that are the same, the results of the
report will be based on a single period.

for the scenario.
5. Click Refresh. The Inventory Summary Report window is refreshed and contains the
report results in a table. Note that the text entries displayed in the first row (STAGES, by
default) are hypertext links.
6. The Inventory Summary report is an interactive report. You can view the results for the
nodes in each stage, as shown in Figure 3-15, by clicking the hypertext link for the desired
stage. For example, if a set of nodes in your supply chain are assigned the attribute value
“Supplier,” the Inventory Summary report contains a stage named “Supplier” in the first
row. If you click this link, you see inventory summary results for all supplier nodes only.
66
Figure 3-15 Inventory Summary report results according to attribute

7. To return to the main Inventory Summary Report window, click BACK.
8. Click SHOW CHART to view the results in a chart, as shown in Figure 3-16. The
Inventory Summary report opens in a separate window, in chart format.
67
Figure 3-16 Inventory Summary report results in a chart
68
Stocking Point Static Outputs Report

The Stocking Point Static Outputs Report, shown in Figure 3-17, displays static outputs for stocking
points. The report results are non-interactive and can be viewed only in a table.
Figure 3-17 Stocking Point Static Outputs Report window

For the Stocking Point Static Outputs Report, information listed in Table 3-7 is displayed.
Result Description
Calculated Service Level Service level is a metric that refers to the probability that demand is met
from stock. Calculated service level is the service level calculated by
MIPO. MIPO determines optimal service level for each inventory
stocking location by using the maximum of the calculated service level
and the user-specified service level.
Non-stockout Probability The probability that the item will be available at the customer-facing
stocking point.
Table 3-7 Results for the Stocking Point static output report
69
Result Description
Average Safety Stock Coverage Safety stock is a buffer added to inventory to counteract stockouts
when demand and lead times are uncertain.
Average Safety Stock Coverage is determined by averaging Weeks of

Stock over a number of periods, called the Coverage Duration. Weeks
of Stock is the number of periods of forward expected demand that can
be met by the current inventory.
Effective Lead Time Effective lead time represents the first initial periods during which no
changes can be made to the planned receipts for a given stocking point.
These periods can be considered a “frozen” horizon. Effective lead
time is calculated based on lead time, lead time standard deviation, and
reliability inputs for all the incoming supply paths of a stocking point.
End Horizon The end horizon is the last period deemed as having reliable output
data throughout the supply chain.
Implied Initial On Hand The implied initial on hand value for each forecast period.
Modified Service Time Modified Service Time is an output calculated on each supply path (and
displayed on that path's upstream node in MIPO) that shows the
Customer Service Time input adjusted and propagated upstream.
First Reliable Output Period This value identifies which period is the first with valid safety stock for
the associated stocking point.
Average Lost Demand An optional field used by the SmartOps Service Level Optimization
(SLO) module to define an average lost sales value for each customer-
facing stocking point (averaged over good periods).
Average Forecast Mean An optional field used by the SmartOps Service Level Optimization
(SLO) module to define an average forecast value for each customer-
Average Forecast CV An optional field used by the SmartOps Service Level Optimization
(SLO) module to define an average forecast error CV value for each
customerfacing stocking point (averaged over good periods).
Average Safety Stock An optional field used by the SmartOps Service Level Optimization
(SLO) module to define an average safety stock value for each
customer-facing stocking point (averaged over good periods).
Table 3-7 Results for the Stocking Point static output report
To create a Stocking Point Static Output Report:
70
view the Stocking Point Time Static Outputs Report.
2. Click Reports > Output Reports > Stocking Points > Static Data to open the
Stocking Point Static Outputs Report window.
4. Click Refresh. The Stocking Point Static Output Reports window is reloaded

for the scenario.
71
Stocking Point Time Varying Outputs Report

The Stocking Point Time Varying Outputs Report, shown in Figure 3-18, is an interactive report that
displays outputs for stocking points. The results displayed are time-varying outputs, and can be viewed
only in table format.
Figure 3-18 Stocking Point Time Varying Outputs report results for a single period
For the Stocking Point Time Varying Outputs Report, information listed in Table 3-8 is displayed.
Result Description
Forecast Demand Mean An estimate of the mean demand for the product at that stocking
location during a given period.
Forecast Demand Standard The difference between forecasted and actual demand.
Deviation
Safety Stock Buffer added to inventory to counteract stockouts when demand and
lead times are uncertain.
Cycle Stock One component of the average inventory position at a stocking

location for a specified item and a specified period. It corresponds to
the portion of average on hand inventory that exists to cover demand
between shipments (replenishments).
Prebuild Stock Inventory built due to capacity constraints in anticipation of future

demand.
Table 3-8 Results for the Stocking Point time varying output report
72
Result Description
Merchandising Stock The minimum inventory kept in a retail or customer-facing location. It
may be used for showroom or demonstration purposes, but is typically
included in inventory available to meet demand.
Expected On Hand Stock Expected inventory that is physically available to fill demand, which is
all types of stock except pipeline.
Physical Pipeline Stock A subset of total pipeline stock and includes all inventory in the supply
chain that is currently being moved from one location to another.
Total Pipeline Stock Component of target inventory position and is based on the total lead
time and includes all orders from the time that they are created until the
time they are actually received by the location that has ordered them.
Target Iinventory Position Target inventory position (TIP) is the SmartOps-calculated optimal
replenishment policy parameter defined for each stocking point for
each review period. A TIP replenishment policy calls for a stocking
point to periodically (every PBR periods) compare its TIP to its
inventory position and place enough orders (in multiples of the batch
size) to bring its inventory position up to or above its TIP.
Rounded TIP Value produced by the TIP Rounding processor, which takes the real
TIP number produced by MIPO optimization and rounds the TIP
number to an integer value. This process ensures that dealers will
receive targets composed of complete units of inventory.
On Hand Stock (Periods) On hand stock includes all inventory that is physically available to fill
demand, which is all types of stock except pipeline. Specifically, on
hand inventory includes cycle, safety, merchandising, and prebuild (if
applicable) stock.
Planned Receipts Shipment quantities on a path for a given period, that are expected at
the end stocking point in that period, assuming deterministic lead times
and service times in response to planned orders.
Safety Stock (Periods) Buffer added to inventory to hedge against stockouts when demand
and lead time are uncertain. The amount of safety stock is typically
determined based on a specified service level and the associated
variability in demand and lead times.
Unshifted Safety Stock The amount of unshifted safety stock units associated with specific
stocking point data.
Unshifted Merchandise Stock The amount of unshifted merchandise stock units associated with
specific stocking point data.
Backlog Safety Stock Backlog safety stock associated with specific stocking point data.
73
Result Description
Lost Sales Represents any lost sales associated with a stocking point for each
period of the data horizon.
Additional Required Capacity For this report, additional required capacity is aggregated for all
incoming supply paths to all selected stocking points.
Production Quantity The amount of a given item to be produced over a specific time period.
Reorder Point A calculated threshold used in consumption-based production planning

to trigger replenishment of the associated item whenever the total
amount of onhand stock and outstanding planned receipts drops below
the reorder point.
To create a Stocking Point Time Varying Output Report for a single period:
view the Stocking Point Time Varying Outputs Report.
2. Click Reports > Output Reports > Stocking Points > Time Varying to open the
Stocking Point Time Varying Outputs Report (Single Period) window.
4. Click Refresh. The Stocking Point Time Varying Output Reports (Single Period)
window is reloaded containing the new results in table format. You cannot view this
report in a chart. Note that the node names and time-varying properties are hypertext
links.
74

for the scenario.
Stocking Point Time Varying Outputs - Single Property

The Stocking Point Time Varying Outputs Report is an interactive report. To view an individual
property for all nodes for all periods, as shown in Figure 3-19, click the name of the desired property
in the top row of the report table.
Figure 3-19 Stocking Point Time Varying Outputs report results for a single property
The results are displayed in the Stocking Point Time Varying Outputs Report (Single Property)
window for all periods. The property you selected is displayed in the Time Varying Properties field.
You can change the Stocking Points for Report, the Start and End periods, and the Time Varying
Properties for the report by clicking the Browse (...) button next to each field, respectively.
75
Stocking Point Time Varying Outputs - Single Node

The Stocking Point Time Varying Outputs Report is an interactive report. To view all properties for
an individual node for all periods, as shown in Figure 3-20, click the name of the desired node in the
first column of the report table.
Figure 3-20 Stocking Point Time Varying Outputs report results for a single node
The results are displayed in the Stocking Point Time Varying Outputs Report (Single Node)
window for all periods. The name of the node you selected is displayed in the Stocking Points for
Report field. You can change the Stocking Points for Report and the Start and End periods for the
report by clicking the Browse (...) button next to each field, respectively.
76
Demand Stream Static Outputs Report

The Demand Stream Static Outputs Report, shown in Figure 3-21, displays static outputs for stocking
points. The report results are non-interactive and can be viewed only in a table.
Figure 3-21 Demand Stream Static Outputs Report window

For the Demand Stream Static Outputs Report, information listed in Table 3-9 is displayed.
Result Description
Calculated Service Level Service level is a metric that refers to the probability that demand is met
from stock. Calculated service level is the service level calculated by
MIPO. MIPO determines optimal service level for each inventory
stocking location by using the maximum of the calculated service level
and the user-specified service level.
Table 3-9 Results for the Demand Stream Static Output report
77
Result Description
Calculation Mechanism A demand stream specific output that specifies how the service level on
the demand stream was calculated. Valid values are either Input or
Optimized.
Non-stockout Probability The probability that the item will be available at the customer-facing
stocking point.
Average Lost Demand An optional field used by the SmartOps Service Level Optimization
(SLO) module to define an average lost sales value for each customer-
Average Forecast Mean An optional field used by the SmartOps Service Level Optimization
(SLO) module to define an average forecast value for each customer-
Average Forecast CV An optional field used by the SmartOps Service Level Optimization
(SLO) module to define an average forecast error CV value for each
customerfacing stocking point (averaged over good periods).
Effective Lost Sales Percentage Defines the acceptable lost sales percentage to be applied at the
minimum service level at the associated customer-facing stocking point.
Table 3-9 Results for the Demand Stream Static Output report
To create a Stocking Point Static Output Report:

view the Stocking Point Time Static Outputs Report.
2. Click Reports > Output Reports > Demand Streams to open the Demand Stream
Static Outputs Report window.
to the Demand Streams for Report field to open the Node Selector. Use the Node
Selector to select a different set of demand streams for which to generate the report.
Click OK to close the Node Selector.
4. Click Refresh. The Demand Stream Static Output Reports window is reloaded
78
Editing SLO Output data

If necessary, SLO allows you to make changes to the service level outputs for the stocking points
through the Edit menu.
Note: Even though SLO allows you to edit both static and time-varying stocking point
outputs, MIPO only uses the service level data from the static stocking point output
when it performs its optimization process after you export the SLO outputs back to the
MIPO user scenario.
Stocking point static output data

Data that does not vary with time is considered to be static data in MIPO. Examples of static stocking
point data include calculated service level, average safety stock coverage, and implied initial on hand.
You can edit static Outputs for one or multiple stocking points in MIPO.
To edit the calculated service level for stocking point outputs:
79
2. Click Edit > Output Data > Stocking Point Data > Static to open the Edit Stocking
Point Output Data - Static window, shown in Figure 3-22.
Figure 3-22 Edit Stocking Point Output Data - Static window

5. The Edit Stocking Point Output Data - Static window is reloaded and contains the
stocking point or stocking points you selected on the left and all of the editable properties
on the right.
and pressing ENTER.
80
Note: When editing values that have a predefined valid range (such as,
.50 to 1.0 for Calculated Service Level, and you attempt to enter an
absolute value (=x) outside of that range, a status message indicates
that the value you entered is invalid and you are prompted to enter a
different value.
However, if you specify a relative change (+x or -x) or a percentage
change (+x% or -x%) that results in a value outside the valid range, the
value is automatically rounded up or down to the closest valid value.
For example, if the valid range is 0-1, the current value is .75, and you
increase it by 200%, the resultant value exceeds the valid range. In this
case, the new value that is saved for this property and displayed in the
user interface is one (1).
10. Click OK to save your changes. The Edit Stocking Point Output Data - Static window
is reloaded and displays a status message indicating that the data was updated
successfully. The columns on the right reflect the changes you made.
Exporting SLO data

The Export Data Set screen allows you to export an optimized SLO usser scenario back to the MIPO
source user scenario in order to re-optimize the MIPO scenario with the SLO target service levels.
81
Figure 3-23 Export Scenario window
Note: Exporting SLO scenarios is a user privilege in SLO. You must have privileges
both to export data models and to view and modify the specific data models you want
to export.
Note: To export a SLO scenario to its MIPO source:

1. Use the Supply Chain Selector to choose the SLO scenario you want to export.
2. Click Data Set > Export Data Set to open the Export Scenario window.
3. Select the associated MIPO user scenario by clicking its radio button.
4. Click OK. You will be required to confirm your request.
82
5. From the Confirmation dialog box, click OK. The scenario’s service level data will be
exported back to MIPO user scenario.
The Scenario Export History table is updated to include information based on the
selected MIPO scenario, including the status of the export process.
Once the selected SLO scenario is successfully exported to MIPO, you will see the status
change to “Finished” in the Scenario Export History table. You can now open the
MIPO application and re-optimize the user scenario so it includes the SLO target service
levels.
Note: If you have trouble exporting the SLO scenario, use the View Alerts feature to
determine if any alerts were generated during the Export process. See the section
entitled "Managing SLO Alerts" for more information on SLO alerts.
Managing SLO alerts

The Alerts menu lets you view and manage alerts generated by the SmartOps portal applications,
including the SLO module. See the chapter on Managing Alerts in the MIPO User’s Guide for more
information on this feature.
Refer to the Appendix for details on the alerts associated with the SLO module.
83
84
Appendix:
Alert Definitions
T
his section describes the alerts generated by the SLO module. The table below lists definitions
and troubleshooting strategies, where available, for the SLO alerts.
Note: Key to Alert Severities

Informational alerts are generated upon request to provide a summary progress of
processing for informational purposes. The generation of informational alerts can be
enabled or disabled, by default, depending on context.
Warning alerts inform the user that a condition has occurred that could cause the
software to behave differently from its normal mode. Warnings can include
initializations of missing initial values, unsolicited changes to user preferences, and
exceeding suggested limits.
Error alerts denote a condition that may or may not require user attention. An alert
with error severity is recoverable within the context of the software module in use, so
that processing may proceed, at least partially.
Fatal errors cause the procedure or computation in progress to terminate and roll the
persistent state of the installation to a consistent state. In general, fatal errors do not
cause the server software or the user session to terminate, unless the error occurred in
an infrastructural area necessitating such termination.
85
SLO alerts
Refer to the table below for details on the alerts associated with the SLO module.
Alert Name Description Severity

Max Service Level Less Than SLO generates this alert whenever it detects that the Error
Global Service Objective maximum service level is less than global service
objective for a customer-facing stocking point.
Min Service Level Greater Than SLO generates this alert whenever it detects that the Error
Global Service Objective minimum service level is greater than global service
objective for a customer-facing stocking point.
Customer-facing Stocking Point SLO generates this alert whenever it detects that the Error
is Non-stocking Node customer-facing stocking point has the type "non-
stocking node."
Stocking Point Lost Sales SLO generates this alert whenever it detects that the Error
Percentage Null or Negative lost sales percentage is null or negative for a customer-
facing stocking point where a value greater than or
equal to zero is required.
Global Service Objective Out of SLO generates this alert whenever it detects that the Error
Range the value for the global service objective is out of
range.
Initial Feasible Solution Not SLO generates this alert when infeasibility is detected Error
Found during optimization.
Table A-4: SLO alert descriptions
86
Index
A Demand Stream Static Outputs Report. . . . 77

alerts duplicating SLO scenario . . . . . . . . . . . . . . . 45
managing SLO. . . . . . . . . . . . . . . . . . . . 83
SLO definitions . . . . . . . . . . . . . . . . . . . 86 E
analyze SLO scenario . . . . . . . . . . . . . . . . . . 39 editing SLO data
attribute auditing changes. . . . . . . . . . . . . . . . . . . 36
STAGE . . . . . . . . . . . . . . . . . . . . . . 63, 65 MIPO inputs . . . . . . . . . . . . . . . . . . . . . 28
audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 SLO outputs. . . . . . . . . . . . . . . . . . . . . . 79
auditing SLO data changes . . . . . . . . . . . . . 36 exporting SLO data. . . . . . . . . . . . . . . . . . . . 81
C I
contacting Support Services . . . . . . . . . . . . . 7 Input Reports
conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Stocking Point Static Inputs . . . . . . . . . 51
creating Stocking Point Time Varying Inputs. . . 54
Demand Stream Static Outputs Report 77 installing SLO
Inventory Summary Report . . . . . . . . . 65 module settings . . . . . . . . . . . . . . . . 13, 14
Stocking Point Static Inputs Report . . . 51 user account preferences . . . . . . . . . . . . 18
Stocking Point Static Outputs Report . 69 user account privileges. . . . . . . . . . . . . . 16
Stocking Point Time Varying Inputs Report Inventory Investment . . . . . . . . . . . . . . . . . . 61
54
Stocking Point Time Varying Outputs M
Report . . . . . . . . . . . . . . . . . . . 72 Master Summary Report
Inventory Investment . . . . . . . . . . . . . . 61
D Revenue . . . . . . . . . . . . . . . . . . . . . . . . . 59
deleting Supply Chain Cost . . . . . . . . . . . . . . . . . 59
multiple scenarios . . . . . . . . . . . . . . . . . 49 Turns . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
single scenario . . . . . . . . . . . . . . . . . . . . 49 MIPO
87
exporting SLO data back to . . . . . . . . . 81 deleting multiple. . . . . . . . . . . . . . . . . . . 49

importing scenario into SLO . . . . . . . . 27 deleting single. . . . . . . . . . . . . . . . . . . . . 49
duplicating . . . . . . . . . . . . . . . . . . . . . . . 45
O SLO
optimization alert definitions . . . . . . . . . . . . . . . . . . . 85
optimize SLO scenario . . . . . . . . . . . . . 44 alert management. . . . . . . . . . . . . . . . . . 83
preparing SLO scenario . . . . . . . . . . . . 40 analyzing scenarios. . . . . . . . . . . . . . . . . 39
Output Reports editing input data . . . . . . . . . . . . . . . . . . 28
Demand Stream Static Outputs . . . . . . 77 editing outputs . . . . . . . . . . . . . . . . . . . . 79
Inventory Investment . . . . . . . . . . . . . . 61 exporting data . . . . . . . . . . . . . . . . . . . . 81
Inventory Summary . . . . . . . . . . . . . . . 65 importing MIPO scenarios . . . . . . . . . . 27
Revenue . . . . . . . . . . . . . . . . . . . . . . . . . 59 optimizing scenarios . . . . . . . . . . . . . . . 44
Stocking Point Static Outputs. . . . . . . . 69 overview . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Stocking Point Time Varying Outputs . 72 privileges. . . . . . . . . . . . . . . . . . . . . . . . . 16
Supply Chain Cost. . . . . . . . . . . . . . . . . 59 running reports . . . . . . . . . . . . . . . . . . . 50
Turns . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 starting SmartOps Portal . . . . . . . . . . . . 26
overview SLO alert definitions . . . . . . . . . . . . . . . . . . 86
SLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 SLO module settings . . . . . . . . . . . . . . . 13, 14
SmartOps Portal
P starting SLO . . . . . . . . . . . . . . . . . . . . . . 26
preferences STAGE attribute. . . . . . . . . . . . . . . . . . . 63, 65
SLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Stocking Point Static Outputs Report . . . . . 69
privileges Stocking Point Time Varying Outputs Report72
SLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Supply Chain Cost . . . . . . . . . . . . . . . . . . . . 59
Support Services
contact information . . . . . . . . . . . . . . . . . 7
R
Reports
Demand Stream Static Outputs . . . . . . 77 T
Inventory Investment . . . . . . . . . . . . . . 61 Turns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Inventory Summary . . . . . . . . . . . . . . . 65
Master Summary . . . . . . . . . . . . . . . . . . 57 U
Revenue . . . . . . . . . . . . . . . . . . . . . . . . . 59 User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Stocking Point Static Inputs . . . . . . . . . 51 user account privileges . . . . . . . . . . . . . . . . . 16
Stocking Point Static Outputs. . . . . . . . 69
Stocking Point Time Varying Inputs . . 54
Stocking Point Time Varying Outputs . 72
Supply Chain Cost. . . . . . . . . . . . . . . . . 59
Turns . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Revenue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
S
scenario access . . . . . . . . . . . . . . . . . . . . . . . 48
scenarios
88
SmartOps Corporation
One North Shore Center
Suite 400
Pittsburgh, PA 15212
Made and printed in the USA.

30_09132010

SLO Guide

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

SLO Guide

Enviado por

Direitos autorais:

Formatos disponíveis

Service Level

Installation and User’s Guide

SmartOps® Service Level Optimization (SLO) Installation and User’s Guide

This product includes software developed by:

- the Apache Software Foundation (http://www.apache.org/ and http://poi.apache.org/)

- Sun (http://java.sun.com/ and http://java.sun.com/products/javamail/)

Service Level Optimization Overview

Installing and configuring SLO

SLO data set configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Demand Stream Static Outputs Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

About this guide

Table 1: Notation conventions used in this document

variable name. • lead time, also called total lead

This symbol indicates a note of caution. Items that warrant a note of

Table 1: Notation conventions used in this document

Contacting support services

Sample business problem addressed

Figure 1-1 Service Level Changes vs. Gross Profit Margins

Figure 1-2 Service Level Changes vs. Forecast Error

Traditional Service Decision

Utilizes simple search mechanisms Embeds sophisticated search algorithms within

Table 1-1 Service Level Approach Comparisions (Traditional vs. SmartOps)

Fit within EIO

SLO Inputs SLO Outputs

Table 1-2 SLO Inputs and Outputs

Figure 1-3 Total Cost vs. Target Global Service Level

SLO global configuration

SLO module settings

searching step sizes.

User account privileges

Configuring SLO privileges

Figure 2-1 User Privileges tab in the User Settings window

Note: Privileges in SLO are hierarchical. For example, a user must

SLO privilege definitions

parameter definition notes

Table 2-1 SLO privilege definitions

User Account preferences

Assigning SLO preferences

Figure 2-2 User Preferences tab in the User Settings window

SLO preference definitions

parameter definition notes

View Invalid Customer-facing Lets user see Invalid Customer-facing

View Customer-facing Stocking Lets user see Customer-facing Stocking

View Customer-facing Stocking Lets user see Customer-facing Stocking

Email Global Service Objective Lets user receive an email notification

Table 2-2 SLO preference definitions

parameter definition notes

Email Invalid Customer-facing Lets user receive an email notification

Email Customer-facing Stocking Lets user receive an email notification

Email Customer-facing Stocking Lets user receive an email notification

Table 2-2 SLO preference definitions

SLO data set configuration

Assigning SLO Copy Output processor settings

Assigning automatic MIPO scenario access settings

This chapter discusses:

Click Sign In to start the SLO module.

Figure 3-1 Starting SLO

Importing MIPO scenarios

Figure 3-2 The Import Scenario window

Note: You must have privileges to access the Import Scenario

Editing SLO Input data

Stocking point static input data