IT STRATEGY

BOARD

May 13, 2016

AGENDA

> Call to Order

> Research Computing

—Network 20/20 Vision Update

—Cloud

—Consulting

—Identity and Tier

> Major Projects Review

—HR/Payroll Modernization Update

—UW Medicine EPIC Migration Project

> IT Project Portfolio Executive Review

> Wrap up

2

Research Computing

3

Kelli TrosvigVice President, UW-IT and Chief Information Officer

Network 20/20 Vision

Update

4

David MortonDirector, NDT Mobile Communications, UW-IT

Since We Last Met

˃ Technology BIG leaps and small steps

— Gigabit Passive Optical Network (GPON)

— Fiber to the desk

— Wi-Fi everywhere

— Wi-Fi only

— Cellular/Wi-Ficonvergence

— Routing center consolidation

— Micro-power savings – devices

sleep between packets

˃ Infrastructure and Standards

— Cabling Cat6a

— Number of cables pulled

— Optimize comm closet size

— Emergency power options

— Outdoor hybrid fiber/power cable

Evaluated Options

5

Partners and Next Steps

˃ Consulted During Evaluation Phase

— Housing & Food Services

— Capital Planning and Development

— UW Bothell

— Computer Science & Engineering

— UW Medical Center

— WSU, Penn State, Princeton, Ohio State, WWU, Texas A&M, others

6

˃ Next Steps

— Complete Draft Findings presentation— Present to campus partners and solicit feedback

> CPD, UWMed, HFS, CSE, ARTSI, UWB, UWT> Other recommended partnerships/groups?

— Adjust based on feedback— Complete draft report/updated presentation— Report findings here in fall

7

Questionsor

Suggestions?

Cloud

8

Rob FatlandDirector of Cloud and Data Solutions, UW-IT

Research premise ~ cloud value

> Research should not be compute-limited

> Data management, collaboration should be simple

> Research computing is…

—Perfunctory work, exploratory work, iteration

> Wall-clock time is the primary resource

—Lemma 1: Time cost/benefit and adoption barriers

—Lemma 2: What about what we don’t know about?

9

The Molecules of Cloud Computing

10

Eichler Lab

Genetic Architecture of Autism

Baker Lab

Peptide-based Therapeutics

AA

x 25 = 1 Peptide protein

Noble Lab

Genome-wide Association Studies

Cells (100)

Proteins(200)

$20k, 4 days (not 32 days)__________

500to

5000 etc.

Left-handed complements…

Three Examples from Today

Cloud Adoption

Cloud is an element of research computing. Early adopters provide start-up effort; and they cut their costs and get the time back on their wall clock. And they get to ask and answer bigger questions.

Cloud is part of the direction of research computing. Therefore we want to harmonize what we do ‘cloud’ with the rest of research computing.

> Jupyter notebooks

> API access to data

> databases not spreadsheets

> Frameworks not scratch software

Hence: Consulting is the central idea for propelling

UW research computing forward. 11

> Three pennies gets you… (1 Hr / 1 GB-month)> Code “0—2%” (just the good bits)> Tim: Acceleration ‘89 to 1’> Gaurav: Right-handed scaffolding> Tychele: Future impossible

today

5 years

10 years

Yes but what about…

> Cost

> Security

> Reliability

> Speed

> Services

12

Research Computing Directions

1. Institutionalize scientific consulting at UW– ROI: ‘reverse consult’ story harvest > metrics

2. UW IT return to supporting research, starting with ‘cloud-capable’– Double the staff of UW IT cloud computing for research

3. Democratize cloud access across the student population

4. Cloud adoption incentive programs:– Hardware retirement for reciprocal cloud credit in lieu of ‘buy more servers’

– Proposal support, moderation of cloud research credit programs from vendors

5. Socialize cloud awareness – Deans conduct a ‘survey & exhort’ campaign

– From each school or department: Cloud standard bearers

– Existence-of and Practical training

– Support cycle of participatory events: Cloud COP, hackathons, courses, incubators, …

6. IOT Grand Challenge

7. Implement Student-to-Research labor exchange with cloud certification

8. Growth model: UW campuses, medical; and partner universities

13

Next topicNext topic

QUESTIONS

14

Consulting

15

Bill HoweAssociate Director, eScience Institute

Rob FatlandDirector of Cloud and Data Solutions, UW-IT

2005 - 2008

16

“All across our campus, the process of discovery will increasingly rely on researchers’ ability to extract knowledge from vast amounts of data… In order to remain at the forefront, UW must be a leader in advancing these techniques and technologies, and in making [them] accessible to researchers in the broadest imaginable range of fields.”

In other words:

> Data-intensive science will be ubiquitous

> It’s about intellectual infrastructure and software infrastructure, not only computational infrastructure

http://escience.washington.edu

Long Tail of Research Data

[src: Carol Goble]

PDB

GenBank

UniProt

Pfam

Spreadsheets, NotebooksLocal, Lost

CATH, SCOP(Protein Structure Classification)

ChemSpider

17

Where Do You Store Your Data?

18

src: Conversations with Research Leaders (2008)

src: Faculty Technology Survey (2011)

5%

6%

12%

27%

41%

66%

87%

0% 20% 40% 60% 80% 100%

Other

Department-managed data center

External (non-UW) data center

Server managed by research group

Department-managed server

External device (hard drive, thumb drive)

My computer

Lewis et al 2011

How Much Data Do You Work With?

19

Wright 2013

z Technical staff

David Beck

Jeff Gardner Bill Howe

Erik Lundberg Chance Reschke

eScience Research Consulting circa 2010…

~2 FTE

20

eScience Research Consulting 2016

~8.5 FTE

Dave BeckDirector of Research,

Life SciencesPh.D. Medicinal

Chemistry, Biomolecular

Structure & Design

Jake VanderPlasDirector of Research,

Physical SciencesPh.D., Astronomy

Valentina StanevaData ScientistPh.D., Applied Mathematics and Statistics

Ariel RokemData ScientistPh.D., Neuroscience

Andrew GartlandResearch ScientistPh.D., Biostatistics

Bryna HazeltonResearch ScientistPh.D., Physics

Bernease HermanData ScientistBS, Statswas SE at Amazon

Vaughn IversonResearch ScientistPh.D., Oceanography

Rob FatlandDirector of Cloud and Data SolutionsSenior Data Science FellowPhD Geophysics

Joe HellersteinSenior Data Science FellowIBM Research, Microsoft Research,

Google (ret.)

Data Scientists (fully supported)

Research Scientists (partial support)

Research Faculty Research IT

Brittany Fiore-GartlandEthnographerPh.D Communication

Dir. Ethnography

21

WRF Data Science Studio

22

Building a Research Consulting

Portfolio

> 2010: Embedded

> 2011: Ad hoc lab visits and 1-hour meetings

> 2012: Tutorials, events, user groups

> 2014: Incubator

> 2015: Office hours

> 2015: Data Science for Social Good

> 2016: Rob Fatland

23

Duration of Engagement

# of engagements

go to them

come to us

Office Hours2015-present50+ annually

Door-to-Door; Lab Visits2011-present 25-30

annually

Incubator; DSSG2014-present 1-2annually

Embedded2010-present0-2annually

JointResearch2010-present

0-2annually

per FTE:

24

Duration of Engagement

# of engagements

Office Hours2015-present

go to them

come to us

Incubator; DSSG2014-present

Embedded2010-present

JointResearch2010-present

Door-to-Door; Lab Visits2011-present

25

26

Duration of Engagement

# of engagements

Embedded2010-present

JointResearch2010-present

Office Hours2015-present

go to them

come to us

Door-to-Door; Lab Visits2011-present

Incubator; DSSG2014-present

27

5/9/2016 Bill Howe, UW 28

Data Science Kickoff Session:137 posters from 30+ departments and units

28

Duration of Engagement

# of engagements

Embedded2010-present

JointResearch2010-present

Incubator; DSSG2014-present

Door-to-Door; Lab Visits2011-present

Office Hours2015-present

go to them

come to us

29

Incubation Program Overview

> Quarter-long, in-Studio projects,

engagement two days per week— 4-6 concurrent teams: Network effects among cohort beyond 1:1

interactions

— Each team is ~50% project lead + ~50% eScience FTE

— Structured, time-bounded engagement ensures progress (and an exit strategy)

— Feels like a course: “I have incubator today, so I can’t go do XXX”

> Two-page proposals describing a shovel-ready problem, the science, and how a solution can generalize to other groups

> Participation from faculty, grad students, masters students, and staff

30http://escience.washington.edu/get-involved/incubator-programs/

31

32

Assessing Community Well-BeingThird-Place Technologies

Optimization of King County Metro ParatransitComputer Science & Engineering

Predictors of Permanent Housing for Homeless FamiliesBill and Melinda Gates Foundation

Open Sidewalk Graph for Accessible Trip PlanningElectrical Engineering

33

Duration of Engagement

# of engagements

Embedded2010-present

JointResearch2010-present

Incubator; DSSG2014-present

Door-to-Door; Lab Visits2011-present

go to them

come to us

Office Hours2015-present

34

Office Hours

35

Duration of Engagement

# of engagements

go to them

come to us

Office Hours2015-present50+ annually

Door-to-Door; Lab Visits2011-present 25-30

annually

Incubator; DSSG2014-present 1-2annually

Embedded2010-present0-2annually

JointResearch2010-present

0-2annually

per FTE:

36

Lessons Learned

> Staff

—Science background is important

—Autonomy is important

> Program

—Physical shared studio space is important

—Continuous program evaluation is important

—Diversity in the “menu” is important

—Pipelines are important

—The focus must be the research

37

Going Forward

> Building the “pyramid” has been more about experiments with external dollars than sustainable processes

> UW-IT has an opportunity to institutionalize these programs through eScience and provide national leadership in “intellectual infrastructure”

> This is the direction all of university IT is heading: the pendulum is swinging back to research after 30 years of back office focus

38

QUESTIONS

39

Identity and Tier

40

Nathan DorsAssistant Director, Identity and Access Management,Computing Infrastructure, UW-IT

Overview

41

Trust & Identity

> Trust is “choosing to make something you value vulnerable to another person’s actions”(Charles Feltman)

> Identity is about individual uniqueness, who we are, and how we prove it (identification, authentication)

> Identity is also about the things we say about ourselves and about others – our attributes

42

Trust & Identity

> Together, trust and identity enable scalable collaboration and sharing, with accountability

> It’s how we’re making scholarly identity more secure and portable online – through federation

> Federation is the trusted exchange of identity data (attributes) between parties

43

Research

> Research is local and global – collaborative and federated by nature, often crossing institutional boundaries

> Virtual organizations (VOs) – form to coordinate research activities and access to shared resources

> Institutions like UW must comply with recordkeeping and reporting needs of funders, while identifying research achievements and overall impact

44

Research

> Strategy: Enable small and large-scale cross-organizational research activities, locally and globally, today and into the future

> Objective: Promote open, interoperable solutions to technical and policy problems in trust and identity, in the research and education community, and beyond

> Why: Because research projects will come; we don’t know which ones, but we’ll be ready

45

Initiatives

> So… what are we doing with trust and identity to support research, today and into the future?

46

eduroam

> What: eduroam is a secure roaming network access service developed for the international research and education community, available in 76 territories

> Status: In 2013, UW enabled eduroam for UW members traveling elsewhere, and for researchers visiting the UW Seattle campus

47

ORCID

> What: An open, non-profit community-driven registry of unique researcher identifiers that can be linked to research activities and outputs (publications, data sets, etc.)

> Status: At the UW, mostly individual efforts to integrate into grant and manuscript submission, if required by sponsor or publisher

48

InCommon

> What: InCommon is the identity trust federation operated by Internet2 for the U.S. research and education community

> Status: UW joined as an initial charter member in 2004, as an identity provider; in 2013, UW added support for the Research & Scholarship (R&S) tag, releasing basic identity data to R&S services

> Also subscribed to Certificate Service in 2011

49

eduGAIN

> What: eduGAIN interconnects national identity trust federations like InCommon across the global research and education community

> Status: In March 2016, InCommon joined eduGAIN, which includes 38 other national federations; UW extended support to the global R&S tag

50

Internet2 TIER

> What: The Internet2 “Trust and Identity in Education and Research” (TIER) program

> Objective: Develop a common, sustainable approach to identity and access management

> Why? To simplify campus processes and advance inter-institutional collaboration and research

51

Internet2 TIER

> Status: In 2014, Kelli and others formed the investor council for TIER; then joined forces with Internet2

> Now, UW is one of 49 investor schools helping Internet2 launch the program

> TIER Release One shipped in April, laying groundwork for containerization and deployment mechanisms

52

QUESTIONS

53

Major IT Projects

Review

54

Kelli TrosvigVice President, UW-IT and Chief Information Officer

HR/Payroll Modernization

Update

55

Aubrey FulmerExecutive Program DirectorHR/P Modernization Program

PROGRESS SINCE FEBRUARY

> Lack of a cohesive design and key foundational strategies

> Incomplete or missing documentation of future state design

> End-to-End testing identified gaps and sections of the design that did not fit together

Progress: “Capsule” work produced key concepts and a number of future state process designs; “Mission Control” produced early strategies

Progress: All key concepts and early strategies documented; future state business process design work has begun (10 of 50 complete)

Progress: First cycle of parallel payroll testing completed successfully; Design Integrity Validation (DIVe) sessions planned for July-August; completed Foundations.

56

PROGRESS SINCE FEBRUARY

> Lacked future state operating model that would support the new integrated system and associated processes

> Could not complete Integrated Change Management activities across campus due to design issues

> Challenges with labor relations that were putting the program at risk

Progress: The program works closely with the labor relations team, which has updated Collective Bargaining Units on the program and will continue to do so; outside counsel has been engaged on labor relations issues.

Progress: Initial detailed design for Integrated Service Center completed and approved by Executive Sponsors and business owners

Progress: Integrated Change Management designed and executed “Foundations,” an intensive week-long orientation to new key concepts and strategies for 130 staff, business owners and stakeholders; Campus Foundations planned for summer. Supervisory Org labs also began this week.

57

BUILDING A COHESIVE DESIGN

Prep FoundationsCampus

EngagementDesign Integrity Validation (DIVe)Business Owner

Validation

58

What the ISC isn’t:

> Nice to have/optional

> A traditional “shared services” center designed to reduce costs and eliminate positions

> Not a centralization of HR work from campus departments

THE ISC: WHAT IT IS AND ISN’T

What the ISC is:

> Required for this to be successful

> Designed to cushion the impact of modernization, new systems and processes, not a cost cutting effort

> A centralization of high-exposure transactional services from central business units, not departments

> A single point of service for the campus community

> An integration of process, policy and technology expertise to support business processes in a post-Workday world

59

ONGOING REGRESSION TESTING

USER ACCEPTANCE TESTING

DEPLOY / GO-LIVE

PAYROLL PARALLEL TESTING CYCLES

BUILDING A COHESIVE DESIGN

GO-LIVE ASSESSMENTS

STABILIZATION

INTEGRATED CHANGE MANAGEMENT STEPS 2-6

DEPLOYBUILDDESIGN

PROPOSED HRPM-PROGRAM TIMELINE

INTEGRATED SERVICE CENTER

CAMPUS FOUNDATIONS

APR MAY JUNE JULY AUG SEPT OCT NOV DEC JAN FEB MAR APR MAY JUNE JULY AUG SEPT

2016 2017

60

QUESTIONS

61

UW Medicine EPIC

Migration Project

62

James FineChief Information Officer, UW Medicine

QUESTIONS

63

IT Project Portfolio

Executive Review

64

Kelli TrosvigVice President, UW-IT and Chief Information Officer

QUESTIONS AND

DISCUSSION

65