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)

PF1 ↔ Picaso Interfaces

Find more about the Picaso→SAP Production Schedule Upload Interface (Runs → Planned Orders)

Find out more about the Forecast → allocation & PIR interface (work in progress)

Find more about the SAP→Picaso Master Data Interface.

Find more about the SAP→Picaso Transactional Data Interface (Sales orders, Purchase Orders) (work in progress).

Find technical info about the Picaso ↔ SAP interfaces

Find more about the Interfaces filters

WP1 ↔ Picaso Interfaces

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
• and of course, SAP.

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

The Grid

The grids are visual alert monitors, that give you a general feel of the projected inventory per product/package/location.

more about Supply / Demand Monitoring (aka, the grids)

Product / Location  specific supply / demand data

(aka: SKU Details)

A right click on a product/location takes you to the detailed screen that lets you analyze the situation of said product / location.

Plot

A graphical view of the projected inventory.

Summary

A monthly breakdown of the in- and outwards movements, with resulting EoM inventory and Days of Sale.

Lots

On hand inventory, broken down by lot.

Inbound and Outbound orders

Forecast Overview

Production Schedule Overview

Inventory Target

Find more information about how Inventory Targets are calculated here

TargetPlot

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.

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)

How Inventory targeting works in Picaso

Extracting Inventory Target with Excel

More about Inventory Targeting by Jaide.

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

SAP

SAP is the key application for many departments in our company. The Planning group also uses a few SAP modules. Find training material for some of the most interesting ones.

Interfaces

Interfaces filters

PF1→ Picaso

WP1 → Picaso

Picaso→SAP Production Schedule Upload Interface

The Picaso production schedule is uploaded into SAP every night (US late evening).

(Note that On-demand upload is also supported. Security must be given to a user to be allowed to upload the schedule. When running on-demand, runs on lines/locations that the user is allowed for are uploaded into SAP. More about this here.)

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 to SAP Interface

The DRP order upload runs only at 7 AM, noon, and 5:20 PM

No uploads are sent on Saturdays.  Any orders flagged on Saturday will be sent at 5:20 PM on Sunday.

I also added some messaging to the title of the grid extender to indicate when the next upload will be sent to SAP or if the last upload of the day has already been sent: