Transcript Communications - UW Staff Web Server

UW IT strategy framework
19 June 2007
C&C EC meeting
teg
1
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
Background/Context

TBD
Strategy Development
Methodology

Preparation





Discovery and Discussion




Define framework, definitions, deliverables
Identify general themes for initial focus
Write whitepapers on key issues & trends
Define process, engagement roadmap, milestones
PIs, administrators, SysAds, committees, ...
Listen, facilitate, respond, discuss, decide
Documentation and vetting recommendations
Development of implementation plans & priorities
IT Strategic Plan Deliverables

To be determined
IT Strategic Plan Milestones

To be determined
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.
7
IT/IS/IM Objectives & Strategies

Increase personal productivity
and group effectiveness




Increase institutional efficiency




by providing anytime/anywhere access to great tools
by enabling collaboration without boundaries
by discovering and mitigating IT annoyances
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
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
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)
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
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
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
Some Key IT Service Themes


eScience
Mobility



Collaboration & Breaking down barriers



Anytime/anywhere/any-device access
(laptop initiative, storage svcs, etc.)
Traditional provisioning silos
Organizational boundaries
Dis-intermediation


Avoiding the middle-man for getting info or services
Avoiding the middle-man for sharing rich content
More themes

Managing business risk better





Security, compliance, biz continuity
Energy efficiency –Green computing
SOA
Reducing duplicative efforts
Teaching/Learning technology
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
Funding categories

Services





Infrastructure
Risk mitigation




New service investment
Minimal support for existing services
Deferred mtce and upgrades
Compliance
Security
Business Continuity
Internal tools



MIS
Operational support systems
Project tracking & management
Funding Sources





Core funding
Service fees (recharge)
Indirect cost allocation
FTE tax
Explicit project funding
Framework
Discipline-Specific
eScience
Core
Personal
Productivity
&
Collaboration
Tools
Teaching
Clinical
INFRASTRUCTURE
Admin
Systems
and
Info Mgt
Infrastructure Services








Networking & communications
Storage
Backup
Security
Access control and identity management
Managed servers & Colo
Business continuity
Software development environments
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
Personal Platforms

Computers




Phones




Desktop
Laptop
PDAs
Desktop hard-phone
Soft-phone
Mobile/Smart phones
Operating environments

Windows, Mac, Linux, Symbian, Palm, Blackberry
eScience Platforms

Data clusters
Compute clusters
Visualization clusters

Dominant operating environments




Linux, Unix
Windows
tbd...




Engagement results
Conclusions
Recommendations
Appendices
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”?
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