Google Apps for CSE
U-T
UTTAC
March 16, 2009
g p
pps
pp
What is Google Ap ?
email
calendar (individual, sha
ared, public, resources)
docs (word proc, spread
dsheets, presentations)
collaborative tools (wiki; li co-editing; also off-line)
(wiki live diti l ff li )
talk (plus: reader, blogge , video, sketch...)
(p , gger, , )
omain
all "branded" with our do (not "gmail.com")
oh, and... search
h d
Demo
//
http://cs.washington.edu
• we control...
o appearance (branding)
)
o accounts
o passwords (held by UW not Google)
W,
o
o we own the data !
Issues - Tactical
ve
• An iterative, collaborativ approach
• URL naming - to accommod multiple vendors
date
• passwords - for browser ac
ccess & for Outlook/Thunderbird
("thick clients")
g
• guidelines for users
• from others - EDUCAUSE C discussions
CIO
Issues - Strategic
• Deployment
• Operations
• Exit strategy r;
- multi-vendor interop!
on
• processes/communicatio
• compliance
• future ce,
- multi-vendor, eScienc education, storage,
hosted apps, HIPAA...
Scope
faculty & staff
• student, f ff
• no "classified" research
• initially...
o no "classified" users g g y
segregate by use
o single provider multiple providers
Approach
• phased
1.Team Edition users
1T Editi
2."non-legacy" users - currrent year new undergrads
undergrads, s, faculty
3.legacy - undergrads grads faculty, staff
1.volunteers
2.bulk - self-migrate? bulk-migr
rate?
IMAP
Exchange
POP (email is not kept on any server!)
y
Timeline
Qtr
• Contract signed - late Wi Q
• Beta cohort - early Sp Qtr
ion
Early adoptors include Team Editi users + a few Au08 incoming CSE
undergrads ~30 + 20 users
• "New" users - early Sp Qtr
Incoming CSE undergrads (Au08 - Sp09) ~200 users
Legacy users (Beta) - l
• L Sp l S Q
(B ) late S - early Sm Qtr
o Volunteers - undergrads, grads, staff, faculty, visitors
o IMAP, Exchange, POP3 (self-storage e)
• Legacy users - Sm Qtr
Remaining users ~1000 users
In-house Service sunset - tbd
• I h S i t
End of an era.
Collaboration
O
• MOU
o CSE
o UW Technology
o UW Administration (CISO, RM, Registrar, AGO)
• issues (SSO or not; password distinctions; naming; etc.)
id li
• guidelines (operational, financial, etc.)
p procedures
• process & p
• lessons
Lessons
for omains
• f other departmental do
(e.g., ischool.washington.edu)
n
• for campus-wide domain
Questions? u
Discussion?