Skip to main content
Solved

Visualizer Labor Load

  • Oct 28, 2021 9:50 PM UTC
  • 2 replies
  • 345 views
Curious_User
Sidekick (Customer)
Forum|alt.badge.img+8

Community,

I have been wondering if the Visualizer has been working properly for everyone that uses it. 

I am on (IFS APPS 10 UPD 11).

When grouping the Labor Class graph to a weekly view, it does not update the actual capacity in the tooltip, it still shows daily capacity which is misleading. (See picture)

In addition since it is a weekly view and aggregated, should it not also show that we are not overloaded if we look at capacity from a week by week standpoint? 

Where as the Labor Load in Standard Hours - Labor Class shows this accurately.

Looking forward to some replies :). 

Best answer by Saman K

Hi, 

This should work  .

I tested in UPD14 - APP10. I got expected results.

  1. I have a shop order with machine run factor 1 and Labor run factor 9
  2. I have done capacity calculation so capacity is visible in labor and machine classes
  3.  When I see labor class load - its overloaded as 9/8 hrs loaded on one day
  4. then I go to weekly basis , it is shown as partially loaded 9/48 hrs ( shown correctly in the label)

Hope this helps.

Saman

 

View original
    This topic has been closed for replies.

    2 replies

    Saman K
    Hero (Employee)
    Forum|alt.badge.img+9
    • Saman K
    • Hero (Employee)
    • Answer
    • Dec 16, 2021 8:21 AM UTC

    Hi, 

    This should work  .

    I tested in UPD14 - APP10. I got expected results.

    1. I have a shop order with machine run factor 1 and Labor run factor 9
    2. I have done capacity calculation so capacity is visible in labor and machine classes
    3.  When I see labor class load - its overloaded as 9/8 hrs loaded on one day
    4. then I go to weekly basis , it is shown as partially loaded 9/48 hrs ( shown correctly in the label)

    Hope this helps.

    Saman

     

    Saman K
      Curious_User
      Sidekick (Customer)
      Forum|alt.badge.img+8

      Thank you @Saman K, this sounds like our system has a bug that needs to be addressed which might have been fixed in UPD14 already.

      Terms & ConditionsAccessibility statement