search cancel

Resource 'Availability' Grand Total amount shows 374,480 hours


Article ID: 237598


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


In the Modern UX, when looking at the 'Availability' field for a Resource in the Staffing Workspace and using the 'Grand Total' View Option, you see a really large number: 374,480 hours. 
Is this the maximum number of hours for a resource and why is it so large? 
Another issue, is that if this field is used in Classic UX, the amount is also shown as a really large number. 


Release : Any


Resource Object, 'Availability' Field:

  • In Studio, on the Resource Object, the definition of the 'Availability' field is identified as a 'Time-varying' Data Type. 
  • This field was created and introduced for use in the Modern UX Only. 
  • This is an aggregation of the Resource's Availability Rate using either the Standard Calendar or the Resource's Calendar based on the Working Days and Shifts for the Unit of Measurement and the configuration of the views in Modern UX. 
  • Without any date constraints this field will display a really large number based on the information below. 

Modern UX:

  • All Time Slice Curve data within Clarity have minimum and maximum date boundaries of Jan. 1, 1900 to Jun. 3, 2079. 
  • The Grand Total 'Availability' hours for a Resource using the default, stock Standard Calendar without the Hire or Termination date will have a maximum number of hours = 374,480.  This is because the 'Availability' curve will have a (minimum) start date of Jan. 1, 1900 and a (maximum) end date of Jun. 3, 2079.  This equates to approximately 179 years. 
    • 374,480 total hours / 8 hours per day = 46,810 working days
    • 46,810 days / approximately 261 working days per year = approximately 179 years
  • If you enter a Date of Hire and/or a Date of Termination, the Grand Total Availability will be adjusted upon update of time slices. 
  • If you set up calendar shifts to alter the daily 'Availability Rate' and alter the calendar working days and non-working days, the Grand Total Availability will be adjusted upon update of time slices. 
  • When viewing 'Sum of Periods' the Resource 'Availability' will be bound by the date range selected within the View Options. 

Classic UX: 

  • In Classic UX, as with any other 'Time-varying' field, if it is not configured correctly on a grid, the amount will show a large value. 
  • Configuring a 'Time-varying' field as a 'regular', single field will provide a sum total amount.
  • Configuring a 'Time-varying' field as a Time-Scaled field will provide the amounts bound by the date ranges of the time periods. 
  • The Resource 'Availability' field is stored in the database in the unit of measurement of 'Seconds'.
  • With the Resource 'Availability' field, there is a Known Issue and therefore it is not recommended to use this field in Classic UX.
    • When displaying this field in Classic, it is NOT getting converted into Hours, Days or FTE 
    • The amounts shown is the total number of seconds stored in the slice without applying the unit of measurement conversion and without applying the standard or resource calendar. 
    • There are no plans to 'fix' this field in Classic.  It was introduced and intended for use in Modern UX Only. 
    • Configuration Recommendation: 
      • To avoid having users place this field in the Classic, Resource List View, the Administrator can do the following configuration through Studio on the Resource Object, Views:
        • Place the field on a Secured Properties Subpage for each Resource Type (Labor, Expense, Material, Equipment). 
        • Set the Resource List Column [Options] for the 'Attribute Value Protection'. 


Additional Information