With the release of DELMIA Ortems 2022 level Refresh 5 (from Fix 2222), in the Planning application a new type of link: “Maximum waiting time” is available to model the maximum duration between two operations and highlight when it’s not respected.
Introduction
In the Planning application, you can create links between two phases of the same WO, or between two phases of distinct WOs. In order to model maximum duration between two operations without performance impact or difficulties to modify the Planning, a new type of link was created. A good overview of this functionality is offered in a Demo video included in this post.
New "Maximum waiting time exceeded" operation color
"Maximum waiting time exceeded" is the name for this new color:
With this color selection, operation tags get the following background colors:
This color indicates that no waiting time is use on this operation
This color indicates that the waiting time comply
This color indicates that the waiting time does not comply
Note: if an operation is the target of several links of this type, when one of these links exceeds its waiting time the target operation is colored with the "waiting time" not compliant color .
New criterion "Maximum waiting time exceeded" available on filter
If you want the criterion to return only the operations that exceed their maximum waiting time, set it as equal to Yes.
Conversely, if you want the criterion to return all the operations except those that exceed their maximum waiting time, set it to No. If you want the criterion to return only the operations that do not have a maximum waiting time, set it as equal to N/A.
New KPI to view & monitor the total number of downstream operations that exceed their maximum waiting time
This indicator returns the number of target operations concerned by not compliant links in the plan.
Of course it is possible to set a maximum value to warn the users when the number exceeds its maximum value (Performance > Monitoring view > Configure):
If this KPI is set to be always visible in the plan (by checking its "Active" column from Performance > Monitoring view > Configure), it looks like this:
New highlighting mode available to display the upstream operations of the noncompliant links.
Caution: In a backward-sequenced plan, planning is in the reverse order. Therefore, when the application cannot comply with a maximum waiting time, it highlights the upstream operation of the link instead of the downstream operation.
To determine which operation to highlight, the application relies exclusively on the active sequencing feature, and ignores any machine grouping or WO specificities.
So, on a backward-sequenced grouping in an otherwise forward-sequenced plan, the application highlights the downstream operations of the noncompliant links.
Conversely, for a forward-sequenced WO in a backward-sequenced plan, the application highlights the upstream operations of the noncompliant links.
Based on that information, you can then bring changes to the plan if applicable.
Demo video
Implementation directly on the Planning
For the new link with a maximum waiting time, you can choose among:
- Start-Start
- End-End
- End-Start
- Start-End
Whatever the type, you must enter the Maximum Time between the two dates.
For example, for a start-start link, this is the maximum acceptable time between the start of the upstream operation and the start of the downstream operation of the link. Specify this value in the current time unit of the plan.
The application verifies whether it can create the link. If it can, then the new link appears as a colored line between the two operations.
If creation is not possible, a message informs you — provided you have enabled the message display — and the application cancels the action.
If applicable, the dates of the operations change to meet the constraints of the new link.
The two operations can take place either on the same machine, or on different machines.
The total precedence constraint between the two operations always applies. Conversely, the maximum waiting time may not. In fact, if the application cannot comply with it, it plans the downstream operation of the link beyond that maximum time.
This type of link therefore allows you to model total precedence constraints in more detail, while retaining some planning flexibility for the operations concerned. As such, it can offer a convenient alternative to synchronization links, for example, for production processes where the maximum waiting time is more of a recommendation than an imperative.
Database modification:
Following the new constraint, modification has been made to the structure of the database:
- A new value for B_PREN was added: BT_TYPEPREC = 'H'
H = Maximum waiting time
- BT_PROPPREC include ('FF','DF','DD','FD')
FF = Maximum lead time, end-end / Maximum waiting time, end-end
DF = Maximum lead time, start-end / Maximum waiting time, start-end
DD = Maximum lead time, start-start / Start-start availability / Maximum waiting time, start-start
FD = Maximum lead time, end-start / End-start availability / Maximum waiting time, end-start
