Picaso Production Schedule - Classic
Open a schedule
In Picaso, hit this icon: . It opens a list of Schedules:
Use the search to find the one you need.
Once you find the one you were looking for, hit:
You may also create a schedule (hit: ) and/or understand how a grid works by looking at its properties ()
Schedule properties
The schedule properties, beside its name and description, is mostly its a list of lines.
Use the icon to open the inventory of lines; and use the arrow keys to update the list of lines.
All lines show next to each other, in a sequence that is determined by the equipment "Unit Position"
Navigation
Navigation buttons
| jumps to today | |
| zoom in - horizontal | |
| zoom out - horizontal | |
| zoom in - vertical | |
| zoom out - vertical |
Color schemes
TBC
Linking runs together
| Key | Function |
|---|---|
| Select two runs, then hit this key. Runs are now linked in a predecessor / successor relationship. See Predecessor/Successor. | |
| To cancel the relationship. |
Candidate runs
Picaso generated runs. Resulting from imbalance between demand and supply
Run details
Inserting a run on the schedule
From scratch
Position your cursor on the production line / existing run on that line. Right click:
and select "".
You may insert a run after or before an existing run:
It opens a window as below:
Product / Formula
In that window, populate either the SKU, or the Picaso material & package code. Picaso will pull in complementary data.
The default formula auto-populates. You may pick another valid formula if necessary. Valid means: within validity date & formula assigned to the relevant production line via production standard effectivity.
For this product/package/line, there is only one production standard effectivity:
Would there be more than one, the one with the default check mark would be selected automatically by default (duh!).
Start Date/Time
As per previous run (+transition), the new run can start Nov 27 at 7:15 am the earliest.
You may also anchor the new run to a given date/time (here, we indicate that we want the new run to start no earlier than Nov 30 at 8:15 am)
Quantity/Duration
Enter a quantity below:
It results in the duration of the run being recalculated as per rate (here, 0.4 MT/h), Up Time from the line (or Op, here = 80%), and yield (here = 100 %)
Duration = 10 MT / (0.4 MT/h) = 25 h.
However, a 80 % Up Time affects negatively the duration: 25 h / 0.8 = 31.25 h. Or 1 day, 7h, and 15 min.
The yield is 100 %, therefore it does not affect the run duration.
If the yield was set to 80% (you can modify it in the run, and it will only affect that run), it would result in both:
- longer run duration: 31.25 h / 0.8 = 39.06 h. Or 1day, 15h, and 4 min
- increased Gross Production: 10 MT / 0.8 = 12.5 MT
- the net production (i.e. what is seen on the grid and affects projected inventory) remains at 10 MT
- increased component consumption (see Effect of yield on components quantity).
The standard rate is pulled from the production standard efficiency (through the formula picked for that run).
The rate can be modified in the run itself. It will only affect that run and its duration.
Hit to revert to the standard rate.
Alternative units of measure
As long as they have been defined, other units of measure can be used
Package
Picking package let you enter quantity in multiple of a the material package code. Here, 25 kg bags. The 25 kg is defined in the packages table of ADM
15 kg bags will therefore translate in a 380 kg run.
Lot size
Going with Lots let you enter quantity in multiple of one lot size. Here, 1 MT. The lot size comes from the Production Standard for this material on this line.
This default lot size can be modified in the run itself (and for the sake of this example, we will do just that). Lot size is now 0.35 MT per lot. Only valid for this run.
It is now much easier when thinking in lots: just enter the number of lots to be produced (here: 250 lots); Picaso will calculate how it translates in MT: 87.50 MT.
The lot size comes from the Production Standard for this material on this line:
Run references
Field | Description |
|---|---|
The Run Reference # | is a Picaso internal reference number that is automatically generated once the run is saved. |
| Customer Order | Once a run has been uploaded to SAP and a Planned order/Process order as been created in SAP, the SAP number populates the Customer Order field. Find more about the Picaso Schedule upload to SAP here. |
| Lot Number | If an output lot number is assigned to a Process order in SAP, it will also show here. |
| Exportable | The Exportable checkbox is inherited from the equipment. It can also be checked on or off by hand. If active, that run is selected for upload to SAP. |
| Output Reported | tbc |
| Completed | tbc |
| Type | tbc |
Formula
The formula tab of a run shows the components of said run. Here, only one component.
Hit the button to insert more components.
Highlight the component and hit the button to display/modify the component's
- consumption rate (100%)
- resulting quantity (-10 MT)
- usage (consumption, since this is a component)
- type (continuous)
- lag (0 days, i.e. no lag)
These values are auto-populated from the standard formula details:
Effect of yield on components quantity
Using the example above: 80% yield results in an increased component consumption:
- increased : -10 MT / 0.8 = -12.5 MT
Contrary to output gross production, the effect of a yield is visible on the component's grid.
Predecessor / Successor
By default, a predecessor / successor relationship links together two consecutive runs on the same production line.
When inserting a run, the action decides what is going on with the relationship.
However, a link can be setup between a run and any other run of any other line. Select two runs (keep the shift key down), then hit the key.
The Link Properties dialog box lets you adjust the details.
Once saved, the runs are linked. In this example, the PVDF 6006/0001 CZ run on XCOMPOUND is the predecessor and the PVDF 6010/1001 CZ is the successor.
Now that these runs are linked together, moving one run results in the other run moving too to comply with the link properties. Any other run in the way will be pushed down.
Hit the key to cancel the relationship.
Notes
Free text. A yellow icon in the run header signals that there is something there:
Copy from another run
Copying multiple runs
Modifying a run
Moving a run
Deleting one/multiple runs
Inserting a downtime
Units of measure and lot sizing
Transitions
Working Calendars
Saving a schedule
to Master Schedule
as a Scenario
Production Schedule upload to SAP
The production schedule is uploaded once a day into SAP. For more on this, read the corresponding note.
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.)
Dynamic Scheduling
Dynamic Scheduling is an add-on to standard Picaso. It enables the generation of a production schedule with more sophisticated which, contrary to the standard, can account for the production wheel, production cycle, and other constraints that can be programmed.












































