Deployment Guide
Translate this page with Google -español -български -中文（中国大陆） -中文（臺灣） -hrvatski -čeština -dansk -Nederlands -suomi -français -Deutsch -Ελληνικά -हिन्दी -italiano -日本語 -한국어 -norsk -polski -português -română -русский -svenska
One Laptop per Child (OLPC) Deployment Guide
|
NOTE: The contents of this page are not set in stone, and are subject to change! This page is a draft in active flux ... |
|
Feel free to make minor corrections/additions in-line.
The OLPC Deployment Team: David Cavallo, Carla Gomez Monroy, Edgar Ceballos
This is a generalized guide to a large-scale deployment of one laptop per child. It is a working document that reflects lessons learned from our initial pilots and deployments. Additional ideas will be incorporated as we learn from each other.
Please also check out the Deployment Guide/Deployment Resources for reports, links, documentation and other resources collated by deployment teams all around the world.
Every deployment includes planning (pre-deployment), execution (deployment), and support (post-deployment). Topics that need to be considered in detail in any deployment include:
- Consultation
- Core Team
- Logistics
- Localization
- Connectivity
- Power Infrastructure
- School Server
- Teacher Preparation/Student Facilitation
- Support
- Service/Repairs
- Internet-safety Training
- End-of-life Planning
Each of these topics is expanded upon in this wiki. Also in the wiki are: (I) some tips based upon our experience in trial deployments around the world; (II) a deployment checklist; (III) a sample deployment deployment schedule; (IV) a sample workshop schedule; (V) a glossary of terms; (VI) a worksheet for planning deployment needs on an individual school basis; and (VII) a guide to imaging, activating, and registering laptops.
A workbook for estimating deployment power consumption and expenses is available, along with the presentations and materials from the Deployment planning workshops held at OLPC's Boston, MA headquarters for visitors who come in to plan their large country-wide rollouts.