1 / 26

UW IT strategy framework

19 June 2007 C&C EC meeting teg. UW IT strategy framework. UW IT Strategic Plan Outline. Background and context (incl ref to C&C SP) ‏ Methodology, Deliverables, and Milestones Mission, Objectives, Strategies Trends Key issues Key themes Framework and Definitions Engagement results

lethia
Download Presentation

UW IT strategy framework

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 19 June 2007 C&C EC meeting teg UW IT strategy framework

  2. UW IT Strategic Plan Outline Background and context (incl ref to C&C SP)‏ Methodology, Deliverables, and Milestones Mission, Objectives, Strategies Trends Key issues Key themes Framework and Definitions Engagement results Conclusions Recommendations Appendices

  3. Background/Context TBD

  4. Strategy Development Methodology Preparation Define framework, definitions, deliverables Identify general themes for initial focus Write whitepapers on key issues & trends Define process, engagement roadmap, milestones Discovery and Discussion PIs, administrators, SysAds, committees, ... Listen, facilitate, respond, discuss, decide Documentation and vetting recommendations Development of implementation plans & priorities

  5. IT Strategic Plan Deliverables To be determined

  6. IT Strategic Plan Milestones To be determined

  7. IT organizational mission Support the business(discovery, learning, care)‏ --by providing relevant, reliable, & responsive services. Improve productivity and efficiency --by providing great tools; reducing useless duplication. Foster partnerships --that enable extraordinary achievements by UW students, faculty, staff, and clinicians. Foster innovation --that transforms learning, research and health care. Showcase technology --that illustrates what is possible.

  8. IT/IS/IM Objectives & Strategies Increase personal productivity and group effectiveness by providing anytime/anywhere access to great tools by enabling collaboration without boundaries by discovering and mitigating IT annoyances Increase institutional efficiency by reducing duplication of efforts by leveraging marketplace economies of scale by leveraging advanced tech., stds, good design Reduce institutional risk by improving security by supporting compliance efforts by improving UW's business continuity capability

  9. Trends --technology Welcome advances Wireless Multiple processor cores New emphasis on power efficiency Solid-state storage density Convergence and device integration Video quality and latency Optical network capacity Unwelcome changes Increasing complexity; Worse MTTR and MTTG Increasing protocol diversity

  10. Trends --Marketplace Energy costs -> increasing Compute & Storage costs -> decreasing Commodity IT -> large scale out-task options Content from consumers More proprietary stds and attempts by each major corp to win control over all aspects of customer experience (e.g. cell comm & entertainment)‏

  11. Trends –Research Universities Contract/grant competition: increasing Multi-discipline virtual organizations: increasing Global, 24x7 activities: increasing Dependence on IT services: increasing Off-shoring research risks: increasing Competition for student seats: increasing? State support: ?? Compliance requirements: Increasing Data security risks: increasing

  12. IT = Inevitable Tensions complexity vs. diversity vs. supportability local optimization vs. global optimization security vs. everything convergence vs. risk responding vs. leading consensus-building vs. agility group-think vs. risk-taking Long-term vs. short-term investment one-size-fits-all vs. custom homogeneity vs. species diversity (resilience)‏ monopoly vs. choice

  13. Key IT Governance Issues Central vs. decentral control/autonomy, dupl. Who gets input? Who decides? Heterogeneity: enough, but not too much Funding and re-prioritization (by whom?)‏ Planning vs. agility Balancing investment in new services vs: Future risk mitigation Deferred mtce on current services Infrastructure upkeep & upgrades Management info & operational support systems

  14. Some Key IT Service Themes eScience Mobility Anytime/anywhere/any-device access (laptop initiative, storage svcs, etc.)‏ Collaboration & Breaking down barriers Traditional provisioning silos Organizational boundaries Dis-intermediation Avoiding the middle-man for getting info or services Avoiding the middle-man for sharing rich content

  15. More themes Managing business risk better Security, compliance, biz continuity Energy efficiency –Green computing SOA Reducing duplicative efforts Teaching/Learning technology

  16. People-oriented Services Consulting services, e.g. Security SOA Video System administration Building UW's tech community Campus technology meetings Sponsoring email lists, blogs, wikis Invited speakers

  17. Funding categories Services New service investment Minimal support for existing services Deferred mtce and upgrades Infrastructure Risk mitigation Compliance Security Business Continuity Internal tools MIS Operational support systems Project tracking & management

  18. Funding Sources Core funding Service fees (recharge)‏ Indirect cost allocation FTE tax Explicit project funding

  19. Framework Discipline-Specific Core eScience Personal Productivity & CollaborationTools Admin Systems and Info Mgt Teaching Clinical INFRASTRUCTURE

  20. Infrastructure Services Networking & communications Storage Backup Security Access control and identity management Managed servers & Colo Business continuity Software development environments

  21. Personal & Group Productivity Tools Content creation (docs, audio, video, ppt, drwgs)‏ Math, budget, modeling, simulation, etc Communication (Email, IM, Telephony, Paging)‏ Calendaring (Personal, Group, Public)‏ Contact management & presence management Information Gathering & Sharing Searching, sorting, filtering Content management Wikis, Blogs, “YouTube”, “MySpace” Catalyst-like tools, e.g. Surveys Group file access/sharing DBMS

  22. Personal Platforms Computers Desktop Laptop PDAs Phones Desktop hard-phone Soft-phone Mobile/Smart phones Operating environments Windows, Mac, Linux, Symbian, Palm, Blackberry

  23. eScience Platforms Data clusters Compute clusters Visualization clusters Dominant operating environments Linux, Unix Windows

  24. tbd... Engagement results Conclusions Recommendations Appendices

  25. Engagement ideas Types of engagements One-to-one (Dean, PI, Admin, Techie, Student, etc)‏ Affinity group discussions Arranged talks by outside experts Presentations/organized discussions in existing IT groups (CompDirs, ITRSG, *TACs)‏ Electronic engagement via email lists (TechSupport), wiki, surveys, blogs-with-feedback Next-gen “NW Computer Faire”??what about partnering on another “Innovation Symposium”?

  26. Questions/Next steps Is this on the right track? Suggested changes? Merge with engagement roadmap? What kind of white papers do we need? Relationship to OIM planning efforts? Next steps? How do we decide what to focus on? We don't Delegate EC votes Customer votes (for some value of “customer”)‏ EC “adopt-a-project” plan

More Related