662
edits
Changes
Jump to navigation
Jump to search
Line 61:
Line 61: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
GC Enterprise IT Portfolio FAQs (view source)
Revision as of 14:57, 19 November 2019
, 14:57, 19 November 2019no edit summary
'''Schedule 7 – Notes:''' Annotated notes that departments wish to provide by individual Schedules 1 to 4 or an itemized list (for example One-time expenses; Special events e.g. Winter Olympics, G8 Summit; Ever greening etc.) of notes.
'''Schedule 7 – Notes:''' Annotated notes that departments wish to provide by individual Schedules 1 to 4 or an itemized list (for example One-time expenses; Special events e.g. Winter Olympics, G8 Summit; Ever greening etc.) of notes.
*Include any pertinent information that would inform TBS regarding your OPEX/CAPEX decisions. For example, if your department does not have a Capital Vote, and therefore did not report capitalized expenditures separately, this should be noted.
*Include any pertinent information that would inform TBS regarding your OPEX/CAPEX decisions. For example, if your department does not have a Capital Vote, and therefore did not report capitalized expenditures separately, this should be noted.
</div>
<div style="padding:5px; border:1px solid #bd5e01; width:100%; margin-top:20px;">
<div style="color:#00000; font-size:medium; background-color:#f9d6b8; padding:10px;">'''Question: Can you describe important changes to the report?'''</div>
<span style="color:#bd5e01; font-size:medium;">'''Answer:'''</span>
*The report has been split into Operational cost (OPEX) and Capitalization cost (CAPEX) sections, with respective tabs for each.
*The External Services expenditure category was broken apart on all schedules to allow cloud service-related expenses to be identified as separate from other professional services.
*In the model file, the amount of error checking has been increased, in order to improve reporting quality by departments.
'''Note: It is important that no structural changes are made to the worksheets, e.g. addition or deletion of rows or columns, as it will impact the functioning of formulas and error checking.'''
</div>
<div style="padding:5px; border:1px solid #bd5e01; width:100%; margin-top:20px;">
<div style="color:#00000; font-size:medium; background-color:#f9d6b8; padding:10px;">'''Question: Does my department need to report both Operational (OPEX) and Capitalization (CAPEX) expenses?'''</div>
<span style="color:#bd5e01; font-size:medium;">'''Answer:'''</span>
You must report CAPEX costs if:
*your department capitalizes IT expenses, and
*your department has a capital vote.
You may report CAPEX costs (but are not obligated to) if:
*your department capitalizes IT expenses, and
*your department does not have a capital vote.
In this case, if you choose not to report CAPEX costs, these costs should be included on your OPEX tabs. You should not leave these costs out.
If your department does not capitalize IT expenses:
*you would report all expenses on the OPEX tabs.
</div>
</div>
<div style="padding:5px; border:1px solid #bd5e01; width:100%; margin-top:20px;">
<div style="color:#00000; font-size:medium; background-color:#f9d6b8; padding:10px;">'''Question: Does my department have to report on DCE Services (Schedule 4, previously Schedule 2)?'''</div>
<span style="color:#bd5e01; font-size:medium;">'''Answer:''' There was an error made in the training deck that was presented for the 2015/16 IT Expenditure report. For that year, TBS allowed departments to group their DCE Services (Schedule 2 at the time) expenses under a total column, instead of breaking it down into separate service lines. The change was somewhat late-breaking in nature, therefore the IT Expenditure Guide, and the FAQ page were not updated to match the altered version of the IT Expenditure Model, which was posted on GCconnex. This led some departments to believe that they did not need to report on Schedule 2 at all, since both the original and modified templates were available.
The following year, the error was not caught, and TBS reverted back to the original model. Therefore, departments who had mistakenly used the original model and not reported on Schedule 2 were not made aware of the error. Additionally, some departments continued to use the amended model, and this was also not caught, though reporting in a grouped manner was no longer supported.
To clarify, reporting on DCE Services (Schedule 4) is '''''mandatory'''''. Please use the most current model, [https://gcconnex.gc.ca/file/group/12263474/all#41160858 version 1.4.] All previous models have been deprecated, and will not be accepted by TBS.</span>
