IT Capital Planning Process

All IT projects at UBC are governed in accordance with the Capital Projects Policy FM11. This UBC-wide policy applies to both Building Infrastructure Development and Information Technology (IT) projects.

The purpose of the Policy is to ensure there is appropriate oversight of capital expenditures and internal loans commensurate with the value and risk associated with those activities; and to establish a framework for requests, approvals, monitoring and reporting.

The Policy applies to all IT projects regardless of size, originating unit, or availability of funding. The policy provides a definition of what constitutes an IT project, specifies approval thresholds, and identifies what must be included in the costing of an IT project.

Project approvals are governed by Policy FM11, with approval authority commensurate with the project’s Aggregate Estimated Value (AEV). The higher the project AEV the more approvals and at a higher level are required.

Aggregate Estimated Value (AEV) represents the total estimated cost of the investment. It includes both the one-time project cost and the ongoing sustainment cost for the initial term of the investment. In addition to external costs paid to vendors, AEV also includes internal costs (Administrative or Faculty staff, UBC IT staff etc.).

AEV includes:

• Purchase, license, subscription
• Work performed during planning, scoping, configuration, customization, development, implementation, and integration.
• Maintenance, support
• Contingencies, taxes

AEV is first calculated at the Investment Request stage. As the project progresses more detail will become available, the AEV will be revised and become a more accurate representation of the true cost.

The following is a high level overview of the IT Capital Planning process for investments under $5 million AEV. Investments greater than $5 million require additional approvals.
 

--> <?xml version="1.0" encoding="UTF-8"??> /**/ .cls-1 { stroke: #00a7e1; stroke-width: 11.9px; } .cls-1, .cls-2, .cls-3 { fill: none; } .cls-4 { clip-path: url(#clippath-34); } .cls-5 { clip-path: url(#clippath-21); } .cls-6 { clip-path: url(#clippath-6); } .cls-7 { clip-path: url(#clippath-7); } .cls-8 { clip-path: url(#clippath-17); } .cls-9 { clip-path: url(#clippath-31); } .cls-10 { clip-path: url(#clippath-15); } .cls-11 { clip-path: url(#clippath-33); } .cls-12 { clip-path: url(#clippath-18); } .cls-13 { clip-path: url(#clippath-4); } .cls-14 { clip-path: url(#clippath-22); } .cls-15 { clip-path: url(#clippath-23); } .cls-16 { clip-path: url(#clippath-9); } .cls-17 { clip-path: url(#clippath-10); } .cls-18, .cls-19 { fill: #fff; } .cls-20 { clip-path: url(#clippath-25); } .cls-21 { clip-path: url(#clippath-27); } .cls-22 { fill-rule: evenodd; } .cls-22, .cls-23 { fill: #00a7e1; } .cls-24 { clip-path: url(#clippath-11); } .cls-25, .cls-26 { fill: #0c2344; } .cls-27 { clip-path: url(#clippath-36); } .cls-28 { clip-path: url(#clippath-35); } .cls-26 { font-family: Whitney-Light, Whitney; font-size: 31px; font-weight: 300; } .cls-26, .cls-29, .cls-19 { isolation: isolate; } .cls-30 { clip-path: url(#clippath-28); } .cls-31 { clip-path: url(#clippath-1); } .cls-32 { clip-path: url(#clippath-5); } .cls-33 { clip-path: url(#clippath-20); } .cls-34 { clip-path: url(#clippath-8); } .cls-35 { clip-path: url(#clippath-3); } .cls-36 { clip-path: url(#clippath-26); } .cls-37 { clip-path: url(#clippath-12); } .cls-38 { clip-path: url(#clippath-14); } .cls-39 { fill: #002145; } .cls-40 { clip-path: url(#clippath-30); } .cls-41 { clip-path: url(#clippath-19); } .cls-42 { clip-path: url(#clippath-32); } .cls-19 { opacity: 0; } .cls-43 { clip-path: url(#clippath-16); } .cls-44 { clip-path: url(#clippath-2); } .cls-45 { clip-path: url(#clippath-29); } .cls-46 { clip-path: url(#clippath-37); } .cls-47 { clip-path: url(#clippath-13); } .cls-48 { clip-path: url(#clippath-24); } .cls-49 { clip-path: url(#clippath); } .cls-3 { stroke: #002145; stroke-width: 2px; } /**/ M 

Today IT projects come in various forms and a question might come up as to what constitutes an IT project. Policy FM11 provides a definition of what is to be considered an IT project for the purpose of the policy. It includes:

• Acquisition or development of software
• Subscription fees for software-as-service (SaaS) solutions
• Acquisition of information technology hardware
• Upgrades from one major hardware or software version to another
• Associated activities and services, such as: planning, scoping, requirements gathering, installation, development, integration, configuration, and implementation related to IT.

Contact us early. The sooner you engage us, the more we can do to support you to ensure that your project is a success. Your Client Services Manager is the starting point for discussing your specific project needs and they will engage the IT Portfolio Management team and other IT experts as required.

If you do not have a Client Services Manager, or have process related questions, you can contact the IT Portfolio Management team.