Workforce Scheduling Release 5.0 for Windows Implementation Overview OWS Development Team

Workforce Scheduling Release 5.0 for Windows Implementation Overview

OWS Development Team

CONFIDENTIAL: All capabilities and dates are for planning purposes only and may not be used in any contract

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

Safe Harbor Statement


Objective

• Provide a high level presentation of how the product is configured and implemented


Agenda

• Configuration Overview

• Implementation Overview

• OWS Admin Overview


Summary

• Powerful and Agile Business Model • Large variety of work organizations• Dynamically adjusted when organization changes

• Simple to implement• Easily configured with the OWS Designer tool• No technical knowledge

• Centrally Administrated• OWS Admin: Technical Deployment and Monitoring• Web based Functional Administration role (contracts,

events…)


Agenda





LifecycleCustomer interfaces

Customer OWS Idk+

OWSStatistical Tool

Domain modeling environmentDevelopment environment

InfrastructurePlatform team

Infrastructure Standards

Time Activity PeopleApplications

modeling needs

OptimizationTechniques

Standard Domain configurationApplication developers

Domain specificrequirements

TempoTools +Infra components +

APIs

Consultant

CustomerParameters

setting

OWS Config +

OWS Designer

Customerrequirements

Customer specific configuration


Business Model Overview

Inputs Tasks

1:N1:NN:NN:N

Drivers

ForecastForecast

Activities

N:1N:1

DemandDemand& Schedule& Schedule


Configurable Business Model

• Inputs: historical & forecasted values, distribution profiles, time windows…

• Drivers such as transactions, sales, customers…• Required Tasks (e.g. Item scanning, Credit card transaction…)

• Workload may depend on a driver and a “Labor Standard”

• Activities scheduled (e.g. Cashier, Butcher…)• An activity groups several tasks

• Organizational constraints such as• Presence of a key holder• Activities considered as “management”…

• Optimization engine priorities and fairness• Hierarchy Description• Multiple Store Models:

• Department and team structure• Activity and Organizational Constraints selection


Configurable Employee Model

• HR information options• Employee identifier

• Skills• Skill priority and Individual Proficiency • Special qualification (e.g. First-Aid, Key Holder…)

• Contracts • Contract parameters:

• Absence management• Scheduling rules

• Day compositions constraints• Contract parameters defined through the hierarchy


OWS Designer Tool

• Simple to use• No technical knowledge• Graphical display

• Flexibility• Highly configurable

• Stand Alone tool• Based on a configuration file


Configurable Display

• GUI Components• Display, read-write mode, mandatory fields

• Screens• Display, read-write mode

• Schedule Reports• Order, Departments, Breaks, absences…


OWS Designer Demo


Agenda





Important Statement

• The following slides are based on TempoSoft projects

• Its intent is to help developing future Oracle Methodology for Workforce Scheduling projects


Implementation Methodology

• A step by step approach• Analysis• Pilot• Limited Deployment• Full Deployment

• Objectives :• Master cost and time line• Control adequacy with operational needs• Validate change management and support organization• Size suitably the architecture



• Analyze gaps with the standard• Design the model (store templates) • Configure screens & reports by adjustment of the standard

• First level prototype designed and tested (CRP)

• Functional and operational managers involved

Analysis Pilot LimitedDeployment

Full Deployment



• Pilot the application on 2/3 stores in order to:• Validate benefits will be reached• Identify required adjustments

• Full configuration required for the targeted stores• Complete set of test data collected by the customer

• Initial data load but no live interface with external systems• Coaching of pilot users• Feedbacks analyzed

• Quality of the Schedules• Ease of use

LimitedDeployment

Full DeploymentAnalysis Pilot



• Deploy over 10/15 stores in order to• Check needs of all store types are covered• Validate production architecture • Validate interfaces• Train the trainers and validate change

management tools• Prepare support organization

Full DeploymentAnalysis Pilot Limited

Deployment



• Complete company-wide deployment• End User training• Initial data load & logical deployment (define

users, stores…) • Implement architecture support• Dedicated local first line and second line user

support in place• TempoSoft never covered change management &

end user training ( done by partners )

Analysis Pilot LimitedDeployment

Full Deployment


Keys to success

• Keep it simple• One or two positions per department• Uniform model for all store types• If no simple mathematical formula exist, step back and/or rely

on users’ pragmatic knowledge

• Work as a single team in a timely manner• Limited time to validate a deliverable• Check ASAP all possible consequence of design choices (IT,

HR, Operations,..)


Agenda





OWSAdmin

• Web Application• Simple user interface• Install and deploy OWS Applications on all tiers

• Presentation servers• Synchronous and asynchronous business severs• Integration servers

• Maintaining OWS Applications• Versions management• Monitoring • Logs management


OWSAdmin

• OWS database schemas management• Customization & Production database schemas• Creation• Back up and restore• Schema Upgrades• Configuration Updates


OWS Admin Demo

Documents

Workforce Scheduling Release 5.0 for Windows Implementation Overview OWS Development Team