The traffic light system provides information on project progress by evaluating temporal and quantitative progress in Falcon. The traffic light is clearly visible in the project tree, but can also be found elsewhere, e.g. in your dashboard.

In the project tree the left traffic light stands for the effects and the right traffic light for the activity progress.

  • Green: Time (activities) or effects are within the defined optimum.

  • Yellow: Time (activities) or effects are within the defined tolerance range, so they are slightly delayed.

  • Red: Time (activities) or effects have exceeded the specified tolerance limit and are therefore significantly delayed.

Note: The traffic light system is based on a scoring model. Activities are estimated as a function of the delay (in days). If Falcon remains in the default setting, the activity light changes to yellow after 3 days delay and to red after 7 days delay. The effect traffic light changes colour and becomes yellow when less than 90% of the light is reached. A red traffic light is shown at less than 70% achievement.

But every project is different. Therefore, admins and hub owners can determine for each project when a traffic light changes color. If you want to know which limits apply to you, you can ask your project administrator.

Learn below how the logic behind effect and activity traffic lights differ:

Effect Traffic Lights

When the effect traffic light jumps from green to yellow and from yellow to red depends on the degree of achievement of the effects. 

The default setting in Falcon is a 90-70 split. If you reach more than 90% of the planned effect, the traffic light remains green. Between 90% and 70% it is yellow and only when the 70% hurdle is broken the traffic light does turn red.

In addition, you can specify which goal you want to pursue ("more is better", "less is better" or " spot landing"). 

Here we explain how to set the effects traffic lights.

The traffic light stays gray?

To "turn on" the color for the effect traffic light of a tree element (project/package/measure), the following requirements must be met:

  • In the profile of the element, an effect must be selected that is indicated by the traffic light. Select the effect in the Position field. You can find out more about this topic here.

  • Plan and actual values must be entered in at least one period (e.g. week or month) so that a delta can be calculated.

Activity Traffic Lights

Falcon's traffic light logic for activities works according to a simple scoring system and is similar to the Premier League. First, you determine how many days delay an activity has to receive for a yellow or a red traffic light. To stay with the football example, you determine the number of days delay after which an activity is considered undecided (yellow) and lost (red). In the next step, you determine how many points a green, yellow and red traffic light is worth. As default setting, Falon provides here, as in football, 3, 1 and 0 points.

An example: A measure has 3 activities. All are 3 days late. You have set the traffic light for each activity to yellow from a delay of 3 days to 7 days. You have assigned 3 points for a green traffic light, 2 points for a yellow traffic light and 1 point for a red traffic light. A maximum of 9 points was therefore possible (3 activities times 3 points for a green traffic light per activity). In fact, 6 points were achieved and thus just under 67% of the maximum possible number of points. Depending on your selected limit value, the measure is now assessed as red, green or yellow. As default value Falcon assumes 65% as limit value for a red traffic light. In this example, the measure is evaluated as yellow.

You can find out how to set the activity traffic lights here.

This is how the delay tolerance works when checking off an activity.

Did this answer your question?