136
edits
Important: The GCConnex decommission will not affect GCCollab or GCWiki. Thank you and happy collaborating!
Changes
Jump to navigation
Jump to search
mLine 337:
Line 337: + + + + + + + + + + + + + + + + + + + + + + +
→Annual Frequency
The lowest frequency that should be entered is 1 divided by the total length of the analytical period (e.g., 1/10 for a 10-year analytical period). Any frequency lower than this will be equivalent to a frequency of 1 divided by the length of the analytical period, since the first cohort will not incur the cost a second time within the analytical period, and in all years after year 1, the same new entrants will incur the cost.
The lowest frequency that should be entered is 1 divided by the total length of the analytical period (e.g., 1/10 for a 10-year analytical period). Any frequency lower than this will be equivalent to a frequency of 1 divided by the length of the analytical period, since the first cohort will not incur the cost a second time within the analytical period, and in all years after year 1, the same new entrants will incur the cost.
'''Labour: Time Spent (hours)'''
'''Labour: Internal or External Overhead'''
'''Labour: Staff Level (hourly wage without overhead)'''
'''Error check:'''
The Error Check column contains a formula that checks for common mistakes and gives you a written explanation of how you could/should fix them. It is simply a series of IF statements joined by the "&" operator. If you accidentally delete this formula then the error check functionality will no longer work. You can resolve this problem by re-downloading the RCC or typing the following formula in the error check column (or a new column entirely if you've deleted the whole thing): "=ErrorCheck". Try to implement the suggested solution before reaching out for further assistance.
Orange-shaded error messages indicate that you may want to change something, but you don't necessarily have to. For instance, you will notice an orange error message if you enter a series of inputs that do not result in any incremental impact, since this may be something that you intended to do for completeness or transparency purposes, or maybe it was a mistake. If you manually enter a custom wage directly in the activities table, an orange message will remind you to ensure that the wage you entered is in the same price year as the one specified on the Initiatives sheet. If you've used a high frequency, an orange message will suggest that you consider modelling it a different way (see the explanation of frequency above).
All other error messages will be shaded in red, indicating that something is wrong and should be resolved before you submit the RCC to TBS.
'''Assumptions/Notes:'''
Be sure to add any assumptions and/or notes that would justify the values you enter for the various input parameters. This will help your future self, your colleagues, and your TBS analyst. An RCC submitted to TBS without notes will delay approvals, since your analyst will have to ask you for an explanation of your assumptions.
<big>'''TO BE CONTINUED . . .'''</big>
<big>'''TO BE CONTINUED . . .'''</big>
