IT Strategic Plan

Goal #2 - Modernize and Consolidate Applications and Infrastructure

Initiative #1 - Modernize Instructional Technology

Expected Outcomes:  Though discipline-specific variations will continue to exist across colleges and departments, CMU's classroom experience and core instructional technology will be essentially consistent.  OIT staff will be better able to support activities in ANY college and support will be provided by multiple people and teams.  Software will be documented in the Knowledgebase.  OIT has defined research support services and strong working relationships with researchers and research organizations.

 

Strategies:

      • Standardize classroom configurations and management
      • Build, implement, and maintain a plan for consolidating software titles where appropriate and for supporting those titles in meaningful ways
      • Develop and extend support for protected research data sets
      • Inventory existing research-related services, identify gaps, and fill them

Planned for FY18

      • Document desired classroom configuration
      • Upgrade PCs to latest Windows (we have some win7 machines now)
      • Review the Tech to Classroom mapping and make changes based on locations
      • Get more support standards on podium computers - administrator access etc. 
      • Get more of the techs consistent physical access to the instructional technology.
      • Provide reports to leadership on the status of lab computing
      • Inventory software titles currently in use.  
      • Build a plan for addressing opportunities for consolidation.
      • Build a plan for the evolution of support for research services

Initiative #2 - Optimize the Applications Environment

Expected Outcomes:  CMU's enterprise applications are mapped to business processes, application lifecycles are developed and monitored, and decisions about which applications to find or review are proactively driven by those plans.

 

Strategies:

      • Implement Application Lifecycle Management
      • Implement Business Process Management

Planned for FY18

      • Begin development of an application inventory and a plan for their evolution
      • Invest in InCommon/Shibboleth as a federation/single sign-on standard
      • Retire "At-Risk" Applications
      • Determine BPM Platform
      • Determine resource requirements
      • Conduct Proof-of-Concept

Initiative #3 - Articulate a Next-Generation ERP Plan

Expected Outcomes: CMU's next generation EPP will support not just the traditional mission-critical business processes, but also emerging ones such as recruitment, retention (advising) and post-graduation engagement.  Additionally, it will be cost effective and supportable from the standpoint of interface management.

 

Strategies

      • Construct a plan for the evolution of CMU's ERP, including optional paths with pros/cons and cost implications.

Planned for FY18

      • Complete assessment of Success Factors, begin planning for FI/CO, and SLCM functions in SAP
      • Complete assessment of CRM

Initiative #4 - Position CMU's Data as an Institutional Asset

Expected Outcomes: CMU has an agreed-upon strategy for the capture, maintenance, and use of data needed to guide its most critical decisions, This strategy includes a data dictionary that describes the use and meaning of CMU data and an application/platform plan for its capture, maintenance and dissemination.  Data architecture will include the models, principles, policies, and standards that govern the methods of data collection, storage, integration, and use.

 

Strategies

      • Develop and implement a data architecture plan that is aligned with master data management and lays a solid foundation for immediate and future needs. 

Planned for FY18

      • Begin short and long-term planning for data architecture. 
      • Document existing data architecture building blocks, including principles, policies, resources, technology. 
      • Begin data collection supporting community engagement

Initiative #5 - Manage the Evolution of CMU's Technical Architecture and Infrastructure

Expected Outcomes: There is a plan in place for infrastructure evolution and replacement, and this plan takes into account all needs of the university - academic, business, and technical (new capabilities needed, announced loss of support, IPv6, etc.).  This plan is actively managed, and appropriate elements of this plan are incorporated into regular maintenance as required.

 

Strategies

      • Develop a map of CMU's critical infrastructure and a plan for its regular update and maintenance
      • Target specific opportunities for service/infrastructure consolidation

Planned for FY18

      • Engage consulting to build the baseline map and plan
      • Form a Technical Architecture Team to manage the map and plan on an on-going basis
      • Conduct Network Maintenance
      • Conduct Server and Storage Maintenance
      • Conduct Mediated Classroom Maintenance
      • Shift VMWare infrastructure and management from CBA to OIT - Phase I (ICE 3.0)