Picaso is the Scheduling, Demand Management, and Supply Chain monitoring system of the GBU.

The current name of Picaso is actually TPS (Tactical Planning and Scheduling). Picaso is the historical name of this application.

Simplified IT Ecosystem

Interfaces (zoom in on Picaso & EP)

List of Planning Applications

Picaso Modules

Demand Management
Supply / Demand monitoring (aka the Grids)
- Distribution Requirement Planning (DRP) - automated generation of a distribution plan
Production schedule (hourly buckets) - full manual or automated (Detailed Scheduler)
- (add-on) Dynamic Scheduling - automated generation of a production schedule

Other Apps

ADM: Advanced Data Management
EP: Enterprise Planning
Inventory targeting: calculation of target stock, setting safety stock
WebDP: Web-based Demand Management
PicReport: Access-based reporting system
Management Dashboard

Planning Applications Overview

Demand Management

Customer/product/pack/region (month)
All key figures displayed/modifiable (security depending)
Sales History: shipped orders
Open orders: outstanding orders
Inheritance logic
Sales Rep -> Account Mgr forecast (manual)
Adjusted Forecast -> netting (automated) (find the logic here)
Sales Control goes to SAP for allocation (manual)
Manger -> Planner forecast (manual)
Final forecast goes into Supply/Demand
Real time (no snapshot/frozen period) <-> Supply/Demand

more about Demand Management

Supply / Demand monitoring (daily buckets)

The Grid

Plot

On-hand Inventory

Inbound and Outbound orders

Forecast Overview

From the Picaso forecasting module (real time update)
Forecast = 1 value per month
Inv. projection: forecast broken down into daily buckets

Production Schedule Overview

From the Picaso production schedule module (real time update)
Picaso schedule copied to SAP overnight

Inventory Target

Safety stock and Max Stock setting
Suggested values (driven by forecast error and service level)
real time integration with ADM

Distribution Requirement Planning

automated generation of a distribution plan

Production schedule (hourly buckets) - full manual or automated (Detailed Scheduler)

Finite capacity. One production line = 1 column
Production campaign duration driven by qty (manual) and production rate (from master data)
- Production rate updated in Picaso DB (no SAP interface)
- BOM from SAP (daily interface)

Automatic transition time calculation (optional)
Each line scheduled individually
- shared resource not supported
- multisep production process to be managed by hand
No feedback for in-process (manual update of in process runs)
Daily interface w/SAP (one campaign = one planned order)
One Schedule table used at a time (sharing conflict)
Production Scheduling Scenario (what-if analysis)
Navigation to output- / input product supply/demand balance
Real time update within Picaso ecosystem

Dynamic Scheduling

Automated Schedule builder

embedded in Picaso system (add-on)
No additional interface channel required

Transparent to user: one add’l function in the menu
Result goes into Picaso Schedule Table

No different from a manual schedule
Data flow to SAP goes from there

ADM: Advanced Data Management

Picaso, EP, and WebDP master data are maintained in this central system.

A few other system monitoring, logging, and configurations are also found in ADM.

More about ADM

EP (Enterprise Planning)

Inventory targeting (calculation of target stock, setting safety stock)

WebDP (Web Demand Planning)

Web enabled
Horizon: 12 months(?)
Accounts assigned to Account Mgrs (via Sales Force, manual synchronization[?])
Forecast recorded at product / ship-to / month level
Price: default (statistical), manual override possible
No ‘forecast snapshot’. Picaso modules consider forecast from DP as soon as updated.
Forecast accuracy (Sales Reps forecast of M-2, vs actual ship of M0)