Appendix - Technology Roadmaps
Title: FASmail: Faculty and Staff email | Manager: Liza Jose | Date: | ||
---|---|---|---|---|
Overall direction description The UBC Faculty & Staff E-mail service is a UBC-funded and in-house hosted enterprise e-mail service for staff, faculty and student employees of the University of British Columbia. FASmail will support 15K to 20K users. Current technology consists of Exchange 2010 servers and data stores running on a virtual environment that offers High Availability(HA) and Vmotion capabilities. Database Availability Group (DAG) will be implemented to add HA at the application level. Incremental increase in user mailbox storage as well Archiving will be a big consideration in the next 3 years. The service will deploy the next version upgrade of Exchange after the release of service pack 1. | ||||
Year | Milestone | Dependencies | ||
1 | Complete migration of all mercury-Exchange 2007 accounts to FASmail FY 2011 | |||
2 | Complete migration of all Interchange Faculty and Staff email to FASmail FY 2011 | |||
3 | Complete Student Email refresh FY 2011 | Student Email Strategy | ||
4 | Implement DAG Phase 1 by June 30, 2011 | Infrastructure setup at Life Sciences | ||
5 | Increase FASmail mailbox size by 2012-2013 | Storage purchase/upgrade | ||
6 | Upgrade FASmail to next version of Exchange | New Exchange version SP1 |
Title: myUBC | Manager: Liza Jose | Date: |
---|---|---|
Overall direction description myUBC is running on a very old version of uPortal, which is no longer supported by the vendor. The system has not been patched for a long time. It runs on four physical Sun Servers that need to be retired – two servers fall directly under the myUBC portal service while two other servers are shared with the CWL service and are owned by the CWL service. The service has not matured due to the absence of a business owner. With the new and growing demand from business units, a replacement portal is in consideration. UBC IT will develop a service framework and engage stakeholders in implementing a new portal (also referred to as "Communication Hub") that will serve the global needs of the community. | ||
Year | Milestone | Dependencies |
1 | Identify Stakeholders and business owner(s); gather high level needs -FY 2011 | |
2 | Develop service framework -FY 2011 | |
3 | Investigate next generation portal options -FY 2011 | |
4 | Run Pilot – FY 2011 | Product Selection |
6 | Implement Communication hub – FY 2012 | Successful Pilot |
7 | Integrate with Unified Communications – FY 2012 | Unified Communications implementation |
8 | Decommission legacy uPortal – FY 2013 |
Title: Voice / Unified Communications | Manager: Liza Jose | Date: |
---|---|---|
Overall direction description The goal of the Voice Service is to provide an integrated, highly reliable communications and collaboration infrastructure for the University. The UBC IT Voice Service, as it exists today, is isolated from other technologies provided by UBC IT. A higher degree of integration between voice and other collaboration infrastructure, such as email, is required to facilitate real-time and asynchronous communications. At the same time, a movement towards an application-based unified communications environment will enable UBC IT to leverage common platforms for services – providing for the more effective use of resources. Along with the move to a more integrated communication and collaboration environment, legacy systems are being refreshed with new technology. TDM capability is retained to continue supporting mission-critical services such as the hospital, 911/emergency phones, alarms, etc. VOIP strategy is renewed to accommodate service expansion as well as to support cost-effective alternatives. | ||
Year | Milestone | Dependencies |
1 | Deploy Unified Messaging as replacement for legacy Voice mail Octel; Migrate all Octel accounts by June 30, 2011 | Exchange 2010 deployment |
2 | Upgrade Cisco CUCM/CUPM by Aug 31, 2011 | |
3 | Implement new CS1K –TDM/VOIP switch (successor to Nortel) by July 1, 2011 | |
4 | Implement new enterprise Contact Centre service FY 2012 | |
5 | Implement VoIP/UC strategy FY 2012 | |
6 | Implement Low-cost Tier with Unified Communications offering FY 2013 | Unified Communications Pilot |
7 | Decommission legacy systems FY 2014 |
Title: FMS | Manager: Lyla Crighton | Date: Nov 18/2010 |
---|---|---|
Overall direction summary: Continuity of current functionality (reliable, responsive and cost-effective), provide a campus wide budget system, integrated reporting | ||
Year-QX | Milestone | Dependencies |
1. 2011-Q3 | Integrated Reporting Inventory Management | |
2. 2011-Q4 | Infrastructure Upgrades | |
3. 2012 | IAM Travel & Expenses Image Now Integrated Reporting | |
4. 2013 | eProcurement Vendor EFT | |
5. 2014 | eProcurement | |
6. 2015 | Integrated Reporting – expanded analytics FMS Upgrade (Fusion) |
Title: HRMS | Manager: Greg Lakowski | Date: Nov 18/2010 |
---|---|---|
Overall direction summary: Continuity of current functionality (reliable, responsive and cost-effective), addition of new functionality as specified by Functional Owner (e.g. Absence Management, Talent Management), implement common workflow | ||
Year-QX | Milestone | Dependencies |
1. 2011-Q3 | Common Workflow Model Faculty eRecruit | |
2. 2011-Q4 | PD Funds IAM | |
3. 2012 | HRMS 9.1 begins Timesheet eForm Integrated Reporting | |
4. 2013 | HRMS 9.1 ends eBenefits begins IAM | |
5. 2014 | eBenefits ends Absence Management begins | |
6. 2015 | Absence Management ends Career Path and Planning |
Title: Business Information Systems (BIS) – Applications | Manager: Kevin Labadie | Date: 1/26/11 |
---|---|---|
Over the next 5 years, BIS will focus on ensuring stable, effective and cohesive delivery of application services across the various clients we support. These applications should be consolidated where possible to meet operational efficiency targets while enabling our clients to meet their individual business needs. Additionally, BIS will start the process of migrating applications off aging development platforms (i.e. ColdFusion) to more scalable languages, namely J2EE with IAM integration. We will also begin to develop mobile applications to allow our clients increased accessibility to their customers. | ||
Year | Milestone | Dependencies |
1 | Utility Management System, Key Lock System and DSX MDB migrations to new platforms. | Change Management, Virtual Servers and Storage |
2 | FME replacement | Virtual Servers and Storage, Application Integration needs |
3 | IAM integration for required applications | Identity and Access Management Services, Change Management |
4 | Retire ColdFusion as a development platform | Change Management |
5 | Offer mobile applications (Bookstore, Parking) | Identity and Access Management Services, Various Business Drivers. |
Title: Business Information Systems (BIS) - Infrastructure | Manager: Kevin Labadie | Date: 1/26/11 |
---|---|---|
Over the next 5 years, we will focus on virtualizing (centralizing where virtualization isn't possible) all BIS infrastructure across the portfolio. Our initial focus will be on lifecycle management, centralized services and building a more robust and scalable infrastructure layer as a strong foundation for our current and future application needs. | ||
Year | Milestone | Dependencies |
1 | Centralized services (monitoring, syslog, WSUS, antivirus and proxy services) | Change Management |
2 | Database upgrade and migrations to Linux | Demand Management, Virtual Servers and Storage |
3 | Standardized workstation environment | Virtual Desktops, IT Service Management |
4 | Server virtualization | Virtual Servers and Storage, Demand Management, Change Management |
5 | Consolidated Server Rooms | Virtual Servers and Storage, Change Management |
Internal Business Application Services
Solutions and Integration Strategy
Network Service
Title: Roadmap Name Enterprise Storage | Manager: Responsible Manager Lois Cumming | Date: Completed February 10/11 |
---|---|---|
Overall direction summary: Continue to scale up the storage capacity and add Storage Management tools to offer more Tiers of SAN Services. Highlight overall direction of roadmap: Continue to expand capacity at UBCV and at an off-site location and add management tools to achieve efficiencies. | ||
Year-QX | Milestone | Dependencies |
1. 2011-Q1,2,3 | Decommission Vancouver/Burnaby and Richmond filers (5 years old and off support as of March 2011) Decommission the IBM Tape Library | Other milestones on this roadmap Other milestones on other roadmaps: -virtualise legacy servers such as Oracle4, Finance and HR database servers |
2. 2011- Q1,2.3 | Build archive SAN solution off-site, out of earthquake zone Install Storage Resource Management tools | |
3. 2011 Q1,2,3,4 | Implement the new Secure File Service | |
4. 2012 Q1,2,3,4 | Service Level Monitoring | |
5.2013 Q1,2,3,4 | Install 100 GgE FCOE equipment |
Title: Roadmap Name Virtual Server Service | Manager: Responsible Manager Lois Cumming | Date: Completed February 10, 2011 |
---|---|---|
Overall direction summary: Continue to scale up and out to meet the demand for cloud computing. Highlight overall direction of roadmap: The Virtual Server Service is "hardware agnostic" so we continue to scale to meet the increasing demand for compute resources, higher availability and keep pace with the latest technology revisions. | ||
Year-QX | Milestone | Dependencies |
1. 2011-2012 Q2,3,4 | Continue to scale up (increase) chassis and blades infrastructure with capacity for 2000 virtual servers | Other milestones on this roadmap Other milestones on other roadmaps: Build GRID03 |
2. 2012 Q1,2,3 | Retire chassis and blades on GRID01 | |
3. 2012 Q1,2,3 | Expand chassis and blades on GRID03 to off-site location | Other milestones on other roadmaps: Build GRID04,GRID05 |
4.2013 Q1,2,3 | Continue to scale up (increase) chassis and blades infrastructure with capacity for 3000 virtual servers | |
5.2013 | Highly available environment built at the off-site location (UBC-O?) |
Reporting / Business Intelligence
Title: Data Centre | Manager: Bob Macdonald | Date: 02/08/11 |
---|---|---|
Overall direction summary: The completion of the new Data Centre will allow for the transition of Research computing and IT services consolidation away from the Dept Server Rooms to the new facility. With this new facility and with offsite Data Centre Space the Klink Facility can be gradually depopulated over the next 5 years. Departmental Server Rooms decommissioning will be ongoing as Research consolidates and as services are centralised. Life Cycle Maintenance will be ongoing and budgeted accordingly. | ||
Year | Milestone | Dependencies |
1. 2011 | Construction of new Data Centre | No Dependencies |
2.2012 | Commissioning of new Data Centre Begin Decommissioning of Dept Server Rooms | Network Roadmap (New Router Pair based on NEXUS 7K) |
3.2013 | Decommissioning of Server Rooms CONT. Off Site Data Centre Capacity on line. | VSS, SAN, VDI, Exchange Roadmaps |
4.2014 | Begin Depopulation of Klink Off Site Hosting of Admin systems Decommissioning of Server Rooms CONT. | VSS, SAN, VDI, Exchange Roadmaps |
5.2015 | Complete Klink Depopulation Decommissioning of Server Rooms CONT. | VSS, SAN, VDI, Exchange Roadmaps |
Title: IT Service Centre | Manager: Rose Chan | Date: Jan 31, 2011 |
---|---|---|
Overall direction summary: The IT Service Centre becomes a customer-focused single point of contact for campus services managed by UBC IT and its partners as required. The unit provides information, monitoring services, technical support, and escalation for all enterprise IT services. The IT Service Centre will:
| ||
Year-QX | Milestone | Dependencies (other milestones on this roadmap) |
2011-Q1 | Implementation of webchat as additional means of support mechanisms. This enables UBC Campus community have the choice to select the preferred channels to access UBC IT Service Centre. | |
2011 – Q2 | Develop a knowledge management model at ITSC with a set of best practices which enhances our ability to share knowledge and information. | The hiring of the Knowledge Analyst position for the ITSC |
2011 – Q2 | Service transition or onboarding process introduced to facilitate any changes or new services for better and more efficient support at ITSC – Phase 1 (new services) | |
2011 – Q3 | A common incident handling tool and process to be used by all groups at UBC IT in handling incidents. This will increase the efficiency and productivity of staff and thus enhance our service levels. | The selection of a common tool. |
2012 – Q1 | Reduce the number of contact points to UBC IT – Phase I (collapsing some phone numbers or re-routing calls) | |
2012 – Q2 | Service Transition or upgrading of existing services – Transition Process introduced to facilitate any changes or new services for better and more efficient support at ITSC – Phase 2 (existing services) | |
2012 – Q4 | Integrated workflows across IT Service Providers | Successful tool implementation |
2013 – Q1 | A standardized Incident Management Process Framework implemented across all groups at UBC IT. | |
2013 – Q2 | Reduce the number of contact points to UBC IT – Phase 2 | |
2014 – Q1 | Contact Centre (Telephony tools) upgrade | New Contact Centre Application Platform (Aspect Contact Centre) |
2015- Q1 | Full implementation of IT Service Management for all groups at UBC IT for standardization and consistency purpose. | |
2015 – Q1 | UBC IT becomes a single point of contact (SPOC) |
Title: Database Service Strategy | Manager: Brock Smith | Date: Completed |
---|---|---|
Overall direction summary: The 5-Year end state for the Database Administration unit is to provide to the Campus Community an enhanced Database Service that enables the Campus Community to implement the systems, technologies, and services desired in a robust, efficient and reliable manner. This will be done by providing a centralized database service that is available to the organizations/groups/individuals that require database services. It will do so by taking advantage of the Virtual Systems service, related infrastructure and the evolved growth and sophistication of the other UBC IT units such as the IT Service Centre. The services provided under the umbrella Database management service will be robust (in that it will be able to maintain uptime in the face of maintenance windows) but also highly available, when desired, in that multiple instances of the same Database server will be concurrently available to accommodate load or failure of a particular component in the service stream. Database services will be also be available using three different technologies lines with enterprise level expertise. There will be sophisticated service level monitoring and enhanced Tier 2 support via the ITSC (OC) and the service will be available 24*7, 365 days a year. With the implementation of succession planning, ongoing training and the deployment of a Microsoft SQL/MySQL server team, the Database Administration unit will have expertise in the three technology areas offered and will be able to offer this to the campus community where required. The Database Administration unit during the period under consideration will also explore technical alternatives and related technologies to identify and deploy, where possible, credible competing technologies with the potential to improve existing services and/or replace existing technologies. The enhancement of the knowledge in the DBA unit lends itself to providing a superior level of support and enable UBC IT to meet its overall objectives. Database Services will be constructed to enable application teams and similar to perform their work more efficiently and become more effective in their use of database services by the use of self provisioning and also by gaining an enabler to rapidly test and deploy updated applications via the ability to quickly deploy production instances of databases in test environments. The expertise present in the application teams will be further enhanced via the development of an application DBA training program that will enable application teams to knowledgeably use database services to the extend desired. | ||
Year-QX | Milestone | Dependencies |
1H2011 | Training Oracle 11g Migration to VSS MS SQL DB Service App/System DBA planning 2-Tier DB Hosting Planning | Staffing to execute projects Funds to execute projects |
2H2011 | Migration to VSS MS SQL DB Service App/Sys DBA Training/Implementation 2-Tier Oracle DB Hosting Roll-out IAM Integration ITSM Integration | Technology Funding exists to provide enhanced availability for DB services |
2012 | Life Cycles – Oracle 12g Oracle Tier 1 hosting rollout Research/Plan "cloud" based DB Provision Dynamic DB deployment planning/Web-site creation Plan 2-Tier MSSQL/MySQL Hosting Enhance App/Sys DBA Program | Oracle deploys 12G in this timeframe |
2013 | Life Cycles Expand "cloud" based provisioning to include MSSQL/MySQL Business Continuity App DBA Training/Certificate program | Cloud technologies exist that will permit this level of deployment |
2014 | Life Cycles Review Oracle use, RFP for DB platform Oracle 13g training 2-Tier DB hosting for MSSQL/MySQL | Oracle deploys 13G in this timeframe |
2015 | 2015 Life Cycles Deploy/test alternative DB platforms Update App/Sys DBA program 2-Tier DB hosting for MSSQL/MySQL |
Title: UBC Events | Manager: Liza Jose | Date: |
---|---|---|
Overall direction description UBC Events was launched in September 2008. It is a centralized online public events calendar system that serves the entire UBC community: Students, Faculty, Staff, Alumni, and Visitors. UBC Public Affairs, UBC IT, and Student Development collaborated to implement a common solution that addresses event scheduling and publishing needs of the community. UBC Events incorporated over two hundred and forty separate event providers into its calendaring system in its inaugural year on campus, bringing UBC closer to its vision of a "connected community." The application has become so popular and has matured as a service. A growing demand for additional and enhanced functionality has called for major service upgrades. New features will be released in the next couple of years. In addition, a major backend system refresh will be planned for. | ||
Year | Milestone | Dependencies |
1 | Feature Enhancement FY 2010 | |
2 | Investigate other backend products FY 2011 | |
3 | Feature enhancement or System Refresh FY 2011 | UBC Events Strategy |
4 | Develop mobile strategy FY 2011 | |
5 | Integration with other systems FY 2012 | System Refresh |
Title: IT Service Management | Manager: Laura Cutshall | Date: 02/2011 |
---|---|---|
Overall direction summary: This roadmaps outlines the continued implementation of a standard service management practice that includes process development and tool suite implementation to support the core service management practices (Service Desk including Self-Service, Service Catalogue including actionable Request Fulfillment, and CMDB to support incident, problem and change management) for IT and non-IT services. It is envisioned that the technology implemented and the processes developed within this program will support a campus-wide model to manage services in a customer-centric and cost-effective way. The objectives of the program and supporting roadmap are:
| ||
Year-QX | Milestone | Dependencies |
2011 start | ITSM Tool Suite Selection | |
2011 Q1 | ITSM Tool Suite - IAM integration | ITSM Tool Suite Selection, Identity Management |
2011 Q1 | Incident Management (IM) Process and Tool to UBC IT – all departments | |
2011 Q2 | Onboard ITSM Partner groups for IM Process and Tool | |
2011 Q2 | Initial Request Fulfillment (RF) to UBC IT departments – continues to roll out to 2012. | IAM Entitlement Engine |
2011 Q3/4 | Onboard ITSM Partner groups for RF – RF continues to roll out to 2012. | |
2011 Q2/3 | Problem, Knowledge, Service Level Management to UBC IT and ITSM Partner Groups - continues to roll out to 2012. | |
2011 Q2 | Change Management (ChM) and initial Configuration Mgmt Database (CMDB) to UBC IT departments – continues to roll out to 2012. | |
2011 2H | Onboard ITSM Partner groups for ChM and initial CMDB – continues to roll out to 2012. | |
2011 2H | Self Service & Service Catalogue to customers and end users | |
2012 2H | Program Transition to Operational Governance Model | |
2013-15 | Continue to onboard IT and non-IT Service Departments via ITSM Governance Group | |
2013-15 | Continued Process Improvement via Operational via ITSM Governance Group |
UBC Directory Service
Title: Digital Signage | Manager: Liza Jose | Date: |
---|---|---|
Overall direction description A number of new and existing buildings are using or planning to use digital signage (LCD/Plasma TV's) to convey information to occupants and visitors. As the use of digital signage proliferates, standards will need to be developed to use this resource effectively and efficiently. A common platform, with signs linked via the UBC computer network, will allow for visual creativity with standards to help create a common visitor experience. Further, an integrated network facilitates a consistent and reliable posting of emergency information. | ||
Year | Milestone | Dependencies |
1 | Full Production Service Availability by April 1, 2011 | |
2 | New Clients on boarded FY 2011 | |
3 | Emergency Broadcast Functionality FY 2011 | Trigger machine and workflow |
4 | Seamless Integration with UBC Events FY 2012 | |
5 | Disaster recovery and 24-7 emergency support |