Skip to main content

Hi,

Obstructive maintenance load is hereunder displayed entirely in “Machine Operations Scheduling” area, but not in column chart “Machine Load” when no manufacturing load is scheduled.

  • An obstructive work task of 24 hours is scheduled hereunder
  • Only 9 hours are displayed in machine load on 02/09/2021, and the remaining 15 hours are not on 01/09/2021

From a business perspective, I won’t reschedule anything on 01/09/2021 on PR250 because the machine is in maintenance. The workload should be displayed in any circumstances then, whether manufacturing load is scheduled the same day.

 

The problem was first reported in LCS case G2156460 (Machine obstructive time not correctly reflected in manufacturing visualizer) related to manufacturing visualizer in IFS Applications 10 IEE client.

Detailed explanations received from Saman are reminded in attachment. I thought all problems described in the case would have been solved in IFS Cloud, but it seems not to be.

@Saman K Could you explore this feedback please ?

Visual Shop Orders Planning has shop orders as the underlying data, so typically only dates or weeks when the searched shop orders is loading a resource are included.

Does it make any difference if you set Load Dates = Search Interval? That feature was introduced in IFS Cloud to fetch load for all dates in interval rather than just shop order dates

Also try to use Visual Capacity Requirements page instead. That is built to fetch load for a searched number of resources of a period of time rather than certain shop orders.

@Björn Hultgren Understood. Option Search interval works fine. It’s the title “Load dates” that is confusing, because this option is not only related to date range, but also to the kinds of workload that are displayed. Why not using a more explicit title like “Data Source” with the values “All workloads in the search interval” and “Searched object” or something shorter ?

Glad it resolved the problem!

Yes tricky to find a good name for that parameter, could probably been named better. Anyway I hope the documentation should clarify its purpose.

 

Terms & ConditionsCookie settings