This is a presentation for districts considering implementing Google Apps for Education. My district went live with Google Apps in January 2010! Not only did we save our district money, but innovation/productivity increased!
Benefits of TLS/SSL TLS/SSL provides numerous benefits to clients and servers over other methods of authentication, including:Strong authentication, message privacy, and integrityInteroperabilityAlgorithm flexibilityEase of deploymentEase of useCustom spam and inbound mail filtering tools, powered by Postini. ArchivingCapture and index all of email and attachments in a centralized repositoryStore email in redundant and secure Google data centers, creating a reliable, offsite backupSearch your archive using parameters such as date range, sender, recipient, subject and contentReduced price for education
Integrated communicationsGoogle Apps Education Edition combines email, chat, documents and scheduling.Switch from email to IM, voice, or video chat right in your inbox. Reply to time-sensitive email quickly via chat.Share calendars to quickly create and view class and exam schedules, group meetings, and events.Add calendar entries while composing or reading emails.Receive mail from different email addresses with mail fetcher.
If you have trouble with Bandwidth now – it will be worse after you implement!
Sign up- verify you own your domain – get test site going!
Why we chose Google Apps for EDU<br />$ERVER Problem$<br />
Why we chose Google Apps for EDU<br />Direct Costs Savings (email alone)<br />Spam/Virus Filtering - $2000<br />Gaggle email for Students -$2200<br />Antivirus/email maintenance -$1500<br />Soft Costs<br />Large Amounts Storage <br />Offsite Backup<br />and…<br />Endpoint independent, no maintenance, no updates = Decreased IT support (aka ME) – PRICELESS!<br />
Why we chose Google Apps for EDU<br />Google Apps allows centralized control & administration of content.<br />
Why we chose Google Apps for EDU<br />2009 Horizon report – Cloud computingTime to adopt – 1 year or less<br />Flickr, Facebook, Google Apps, Youtube are all examples of cloud based computing. Everything is done via the browser vs. installing licensed software on machines.<br />Flickr Photo by Seven Morris<br />
Why we chose Google Apps for EDU<br />2009 Horizon report – Mobile ComputingTIME TO ADOPT – 1 Year or less<br />"Over the past few years, mobiles have undergone a continual transformation, becoming ever more capable and flexible with each new release. The ability to record audio and video turned them into portable multimedia devices; as storage capacity increased, they became keepers of our family photos, phone books, and calendars; and now, geolocation, web browsing, and email have brought much of the functionality of a laptop to the pocket-sized devices." (2009 Horizon Report) .<br />
Why we chose Google Apps for EDU<br />Security<br />Flickr Photo by Darwin Bell<br />
Security free (for now)<br />Google Message Security is included free for K-12 schools who sign-up by July 2010.<br />
Why we chose Google Apps for EDU<br />Google Support<br />24/7 <br />Email<br />Search/Forums<br />Built in support system<br />Phone<br />
Why we chose Google Apps for EDU<br />Google Apps Education Edition supports open industry standards, meaning it's easy to integrate into your existing IT systems.<br />
Why we chose Google Apps for EDU<br />Voted 2nd most Innovative Company<br />“Our goal is great ideas are going to come from everywhere and great computer scientists are in all parts of the world.” Dave Girouard, President, Enterprise of Google.<br />http://images.businessweek.com/ss/09/04/0409_most_innovative_cos/2.htm<br />
What have we learned?<br />Gmail – Powerful SEARCH, Labs, tasks<br />Google Docs - BlueRibbon/GSH Forms<br />Google Talk- IM/video save history<br />Google Calendar – IEP meetings,Subs, Labs<br />Google Sites - Math, ePortfolio<br />Mobility = LOVE:)<br />
What have we learned?<br />Increased Collaboration <br />Data Tracking<br />Communications streamlined<br />Timely Feedback<br />First system integration where morale increased!<br />
Our Future Plans<br />Staff First (Jan 2010)<br />Uploaded accounts via CSV<br />Open all labs and apps<br />Allowed to share/IM outside domain<br />Students (may 2010)<br />Will implement via Google Apps Directory Sync (Active Directory)<br />Will not turn on Google Talk (IM)<br />Separate ES/MS?<br />Add grades – 4, 5, 6<br />Moodleintegration<br />
Brainstorm…<br />Will your bandwidth support Google Apps?<br />Decide your audience? Teachers, HS, MS, ES?<br />Will you separate your staff/student domains?<br />Will you implement all apps? <br />How is it going to be supported?<br />Communication plan – Email, Wiki, Website?<br />Does your current policy support collaborative work? Inside/outside domain<br />Username convention? (What is easiest?)<br />Will students have access to the outside email?<br />How will it be monitored?<br />