Clarity

  • 1.  Overall Status Calculation

    Posted May 15, 2018 01:54 PM

    Up to now we have been using the standard Overall Status calculation based on Scope, Schedule and Effort dropdown selections (we don't look at cost).  We are now moving to two Overall Status indicators.  One will use the dropdown selections and the ask for the other is to use the dropdown selection for Scope, the system calculated Schedule Variance and the system calculate effort variance.  I created another calculated attribute and I have tried using various calculations, but keep getting invalid expression error. Has anyone combined something like these?  The two calculated attributes information is below:

     

    System Schedule Var %

    Referenced Item's Object Type Project

    Referenced Attribute: Schedule to Baseline

    Current Expression: DateDiff(baseline_finish,schedule_finish,"Day")

    Color

    Description

    From

    To

    White

    Default Bucket

     

     

    Green

    Ahead of Schedule

    -100,000

    0

    Green

    On Schedule

    0

    1

    Yellow

    Between 1 and 10 Days Late

    1

    11

    Red

    More than 10 Days Late

    11

    100,000

    System Effort Var %

    Referenced Item's Object Type: Project

    Referenced Attribute: Projected Effort Variance %

    Current Expression: ((ttl_effort-baseline_usage)/baseline_usage)*100

    Color

    Description

    From

    To

    White

    Default Bucket

     

     

    Green

    Less Than Baseline

    -100,000

    0

    Green

    No Variance to Baseline

    0

    1

    Yellow

    Between 1 and 10% Over Baseline

    1

    11

    Red

    More than 10% Over Baseline

    11

    100,000

     

     

    Thanks in advance,

    Art



  • 2.  Re: Overall Status Calculation

    Posted May 16, 2018 01:44 AM

    Projected Effort Variance % is already defined as you have indicated.

    Schedule Variance % could be configered, all you have to do is complete the Display Mappings.

     

    From the Object Status Report, you can the create two New Virtural attributes using the two required attributes on the Project.

     

    The Overall Status (which is a calculated number attribute) can then use these two new Virtual Attributes as part of its forumula.  

     

    But saying all this, good luck with getting the required results you are after as you will be trying to determine the Overall Score based on two percentages and a 'rating' which can be a value 10,20,30.  In addition, even if you were to correctly use these values, the Overall Status would change as the project progresses as the '%' fields will automatically change over time.  You may want to consider a process that will be pick up the attributes when the user creates the Status Report, and to store them as values of 10, 20, 30 (which is how the Scope attibute is stored), and then use these now 'fixed' attributes to calculate Overall Status.



  • 3.  Re: Overall Status Calculation

    Posted May 16, 2018 09:10 AM

    Hi Art,

     

    I reckon the DateDiff() function should be defined as:

     

    DateDiff(day, baseline_finish, schedule_finish)

     

    Suhail.