Overview
Simplified IT Ecosystem
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.
Interfaces (zoom in on Picaso & EP)
Find more about the Picaso→SAP Production Schedule Upload Interface
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
Picaso Modules
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
Open a grid
In Picaso, hit this icon: . It opens a list of Grids:
Use the search to find the one you need.
Once you find the one you were looking for, hit: 
The grids are sorted alphabetically.
Each grid's name starts with a number. Find the meaning of these numbers here
You may also create a grid (hit: 
) and/or understand how a grid works by looking at its properties (
)
Grids properties:
The grid properties, beside its name and description, is mostly its filters.
You may add, modify, or delete filters, which are really just selection criteria.
In this example, modifying the first filter (Product Name), shows how it works: this grid selects all products with a 'Product Name' name starting with PVDC. the '%' is a wildcard. (the other filter looks at another product property: product group = 'PREMIX').
Notice the 
checkbox; if activated 
it lets you fill in the value of that filter every time you open the grid:
Color coding
Sorting
Stats
Months
Hammer settings
Change your horizon
related grid
att MTO / STK
Summary
Equivalent
TargetPlot
Plot
On-hand Inventory
Inbound and Outbound orders
Ignore
Status:
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
- 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
More about the Picaso Production Schedule module.
Conventions in Picaso
Started as conventions, gradually morphed into guidelines.
| Grids | First Digit | Convention |
|---|
| 0 | Aro US |
| 1 | Aro EU |
| 2 | Japan |
| 3 | Greater China |
| 4 | India |
| 5 | Korea |
| 6 | Plastomers, PVDC, PVDF |
| 7 | Fluids |
| 8 |
|
| 9 | Tecnoflon |
Other Applications:
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)
PicReport (Picaso Reporting)
PicReport is the reporting environment. We wanted to create our own ad-hoc custom reports.
It gives us access to all database in Picaso.
It is a read-only systems.
More about PicReport here
Management Dashboard
Interfaces
Picaso→SAP Production Schedule Upload Interface
The Picaso production schedule is uploaded into SAP every night (US late evening).
The interface creates one SAP Planned order for each Picaso run.
The production version of the SAP Planned order is either always 0001 or it is determined by the formula used for the run. Table Schedule Upload Unit Parameters drives what the interface works with (fixed PVersion or formula-driven).
The screencopy below is that of a Picaso run.
Its attributes:
- Product: PVDC PV910
- Package: BB5
- the two above determine the SAP Material code (table SKU Code)
- Line: SUSP PKG
- Formula 80 (from possible formulas for that line, determined by Production Standard and Production Standard Effectivity)
- the formula determines the SAP Production version (see above)
- Quantity 176 MT
- Start Date: Dec 02 2022
- End Date: Dec 04 2022 - 12:00 (determined by quantity and rate. Rate from Production Standard Effectivity)
- Customer Order: SAP Planned Order number. This Run has already been interfaced with SAP.
The corresponding SAP Planned order:
- Planned order 1079453469
- Material 161835
- Production Version V01
- Quantity 176 MT
- Start Date: Dec 02 2022
- End Date: Dec 04 2022
- Note that the GR Processing time (2 days) is pulled from SAP Master Data. Nothing to do with the Picaso interface.
The end date of the SAP Planned order is actually driven by multiple factors: the QC Lag, the Schedule upload Lag Adjustment, and the SAP Goods Receipt Processing Time also affect the Planned order. Read the corresponding note to know more about it.
Best Practices
Daily Schedule Update Routine
DRP