How to insert a KPI by comparing two columns

Question

I want to compare the date value under "Start" column and date value under "BL1 Start" column and if they are same I want to use an Indicator in another field and if not same, then another indicator should be displayed in the same field.
Kindly let me know how to do it.
Regards

Answer 1

it is true that you cannot use any 2 parameters (user defined and P6 standard fields alike for that matter) on both sides of the "is" operator in the "if" section of the global change as a condition.
and since the use-case is there, personally i see no good reason why this cannot be so. if any-to-any field comparisons are allowed, any meaningless comparisons of different data types should simply return 0 as their truth value (condition not met) or generate global change report errors
or, more elegant solutions could include more complex "sentences" used as conditions, with more than one operator
e.g. if param_1 < param_2 - param_3,
where param_n is any field (user defined or standard)
also the choice of any parameter as well as operators from dropdown lists should be limited based on the data type of the previously selected parameter(s)
to answer your initial question, the only workaround i can think of is for you to:
*1.* create a user defined field: my_kpi
*2.* use global_change_1 to calculate the value of my_kpi, based any other n number of standard fields, udf's, and/or custom values including PS, CD, current_date_time, substring(), etc to meet your requirements.
use as many "then" lines as needed. no "if" lines required.
e.g.
my_kpi = param_1 + param_2
my_kpi = my_kpi * param_3
my_kpi = my_kpi - some_other_udf
my_kpi = my_kpi / {custom value} division by 0 should be avoided because it will generate errors
this is the equivalent of
my_kpi = ((param_1 + param_2)*param_3 - some_other_udf) / {custom value}
you will probably need one ore two lines with simple divisions or substractions to calculate some relevant value for my_kpi.
e.g.
my_kpi = CD - Planned Finish
my_kpi = my_kpi - {contingency}
*3.* create another udf: my_indicator
*4.* use global_change_2 to assign colour-coded values to my_indicator
if my_kpi < minumum threshold, then my_indicator = red, else my_indicator = green
if you want a 3-colour scale you will need an extra global change to introduce the yellow flag.
the major downside to this is that P6 does not provide (not even v7) solutions for scheduled (jobs), action-triggered or even conditional running of a global change as defined.
it would be nice to have global change batches and have global_change_n triggered by the completion of global_change_n-1, or even to embed one global change (a reference to its definition) within "then" or "else" lines of another global change.
this could significantly enhance (or totally screw up :) the business logic of P6
regards
Edited by: [email protected] on Oct 7, 2009 7:08 PM
Edited by: [email protected] on Oct 7, 2009 7:12 PM