13
Wednesday • Great discussions • Rich set of issues and considerations raise • Service edges explored, but few specific service offerings defined • How to avoid going home with the stigma…

Wednesday Great discussions Rich set of issues and considerations raise Service edges explored, but few specific service offerings defined How to avoid

Embed Size (px)

Citation preview

Page 1: Wednesday Great discussions Rich set of issues and considerations raise Service edges explored, but few specific service offerings defined How to avoid

Wednesday

• Great discussions

• Rich set of issues and considerations raise

• Service edges explored, but few specific service offerings defined

• How to avoid going home with the stigma…

Page 2: Wednesday Great discussions Rich set of issues and considerations raise Service edges explored, but few specific service offerings defined How to avoid
Page 3: Wednesday Great discussions Rich set of issues and considerations raise Service edges explored, but few specific service offerings defined How to avoid

Wednesday Evening

• Shared services brokering discussion– is there a marketplace?

• Semi-random table (or not)… who would be willing to buy/sell services, at what price and under what conditions?– Assume 3yr for most services; 10yrs for some

(data center)

Page 4: Wednesday Great discussions Rich set of issues and considerations raise Service edges explored, but few specific service offerings defined How to avoid

Many Potential Service Providers

Page 5: Wednesday Great discussions Rich set of issues and considerations raise Service edges explored, but few specific service offerings defined How to avoid

Business Continuity Tool

• Service: Wizard-based tool (hosted app) to help school/dept/unit create/maintain BC plan

• Audience: Risk Management organization• Cost: $10K/year• Provider: Berkeley, ???• Availability: now• “Buyers”/Market: ???

Page 6: Wednesday Great discussions Rich set of issues and considerations raise Service edges explored, but few specific service offerings defined How to avoid

Remedy

• Service: Trouble ticketing and routing; other services TBD ( ITIL suite, knowledge management, etc)

• Cost: TBN ($10K-$50K/year… or more or less, depending on scope… plus license xfer)

• Provider: Stanford, ???• Availability: Summer/fall 2009• “Buyers”/Market: ???

Page 7: Wednesday Great discussions Rich set of issues and considerations raise Service edges explored, but few specific service offerings defined How to avoid

Cyrus

• Service: IMAP accounts via Cyrus• Requirements: ≤10Gb quotas• Cost: $10/account/year• Provider: Berkeley, ???• Availability: now• “Buyers”/Market: ???

Page 8: Wednesday Great discussions Rich set of issues and considerations raise Service edges explored, but few specific service offerings defined How to avoid

Calendar

• Service: Define requirements for higher ed to be positioned for hard core negotiation with Google re our requirements to adopt Gcal en masse

• Providers (discussion leaders): Stanford, UCSD, UC-Davis, Minnesota, UT-Austin, ???

• Availability: now• “Buyers”/Market: ???

Page 9: Wednesday Great discussions Rich set of issues and considerations raise Service edges explored, but few specific service offerings defined How to avoid

Backup/Storage

• Service: Backup & storage services on /TB basis• Requirements: May require dedicated bandwidth• Monthly Cost: Backup@$0.30/Gb (setup fee in

some cases & minimums); Storage@$0.15-0.25/Gb (tiered & minimums)

• Provider: Stanford, Berkeley, ???• Availability: now• “Buyers”/Market: ???

Page 10: Wednesday Great discussions Rich set of issues and considerations raise Service edges explored, but few specific service offerings defined How to avoid

Mobile Apps

• Service: Build on Breakout group model…. collaborative sharing of apps, engine for new innovation, +“commoditization” of polished (common) tool sets

• Provider: universities as innovation engines + MIT architecture + TerriblyClever as (one possible) commercialization engine

• Availability: now• “Buyers”/Market: ???

Page 11: Wednesday Great discussions Rich set of issues and considerations raise Service edges explored, but few specific service offerings defined How to avoid

Exchange

• Service: Faculty & Staff email accounts• Requirements: ≥ 2Gb quotas (+ others as

defined by breakout group• Cost: $20/account/year (plus license xfer)• Potential Providers: Indiana, Duke• Availability: Summer 2010• “Buyers”/Market: ???

Page 12: Wednesday Great discussions Rich set of issues and considerations raise Service edges explored, but few specific service offerings defined How to avoid

Hosting

• Service: Identify four geographically diverse locations for (4) 25,000sf, 10MW data center facilities (Columbia River, NC, Iowa, Texas)

• Requirements: 10 year anchor tenant contracts Dedicated bandwidth

• Cost: $100M/10MW “units” capital; ≤$0.05/MW power cost + ops

• Provider: ???• Availability: 2 years?• “Buyers”/Market: ???

Page 13: Wednesday Great discussions Rich set of issues and considerations raise Service edges explored, but few specific service offerings defined How to avoid

Next Steps (this afternoon)

• Call to join in the effort to more fully define these shared service offerings (but not study to death)

• Request to identify other tangible shared service offerings– Service scope– Providers/leaders