http://wiki.laptop.org/mediawiki/api.php?action=feedcontributions&user=Alexandros.Papadopoulos&feedformat=atomOLPC - User contributions [en]2024-03-29T08:32:19ZUser contributionsMediaWiki 1.31.7http://wiki.laptop.org/mediawiki/index.php?title=Talk:Startup_diagnosis&diff=248107Talk:Startup diagnosis2010-10-27T09:17:25Z<p>Alexandros.Papadopoulos: </p>
<hr />
<div>== Diagnosis ==<br />
''' The following suggestions are made as part of the [[Improving the Deployment Toolkit]] project. Please make suggestions and enhancements in this discussion page, which will be incorporated into the page and into the next release of the deployment guide'''<br />
<br />
''Note to be removed before updating the page: This page currently describes what can happen during startup without providing guidance on how to resolve problems. I suggest adding some specific diagnosis instructions along the following lines. Please provide input and ideas in this discussion page so that this diagnosis script can be improved before incorporating into the page itself.''<br />
<br />
=== Diagnosis principles ===<br />
The following basic diagnosis principles will help identify and fix problems:<br />
# Speak with people to understand what is happening from the perspective of the person experiencing the problem<br />
# Speak with people that have already attempted to fix the problem as they may have ideas about where the problem lies and possible solutions, or know what solutions have already been tried and did not work<br />
# Observe what happens yourself<br />
# Use a process of elimination to narrow down where the problem is<br />
## Consider possible causes of the problem<br />
## Start diagnosing the cause with the most likely, by replacing parts or performing tests to confirm whether that is in fact the cause<br />
# Consider what options are available for solving the problem:<br />
## If the solution will take a long time like waiting for a new part, perhaps there is a short term solution that can be used until the new part arrives, like sharing power supplies until a faulty supply is replaced<br />
# Fix the problem<br />
# Follow up later to confirm that the problem really was fixed<br />
# If the problem could not be fixed<br />
## Consider who else may be able to help and consult them<br />
## Consider completely replacing the laptop or part<br />
## Consider whether there is a way of avoiding the problem or working around the problem all together<br />
<br />
=== Diagnosis of laptop power and battery problems ===<br />
''' Note: The [[XO Troubleshooting PowerOn]] page and [[Deployment Guide/Fault Diagnosis#Startup or power problems|other pages]] also discusses how to resolve power problems but makes many assumptions and leaps to conclusions about the nature of the problem. That and this page also duplicate each other to an extent and neither are currently included in the deployment guide section of the wiki. Suggestion: Consider merging these pages and linking to the merged page from the [[Deployment Guide]]'''<br />
<br />
If the laptop fails to turn on when the power button is pressed, the following actions can help diagnose the reason why and help identify a solution:<br />
<br />
# Starting with the laptop switched off, the battery in place, and disconnected from the power, with no lights showing: Press the power button, which is at the bottom right of the screen marked with a circle with a vertical bar, to the right of the on light with the same symbol, and the battery light<br />
# Any of the following conditions could indicate that the battery has insufficient power to operate the laptop and therefore needs recharging or replacing:<br />
## The battery light comes on and is red<br />
## The laptop starts to boot but then switches itself off<br />
## The laptop completes its boot, presents the favourite activities screen, and then switches itself off<br />
## Nothing happens<br />
# If any of these happen, plug the power supply into the mains socket and connect it to the laptop (by plugging it into the socket on the left hand side of the screen at the bottom)<br />
# If the battery light comes on and is amber then this means the battery is charging from the mains<br />
## Press the on button; the power light should light up green and the screen should come on and show icons or messages indicating it is booting<br />
### If the power light fails to come on follow this '''power adapter diagnosis procedure''':<br />
#### Try using another power adapter that is known to work from a different laptop; If this works, the power adapter needs replacing<br />
#### Try using a different mains socket that is known to work; If this works, the original mains socket needs repairing<br />
#### Try removing the battery and running the laptop just from the mains socket; If this works, the battery is faulty and needs replacing<br />
### If the laptop was not working on the battery and then started working when plugged into the mains, try leaving the laptop plugged in until the battery light turns green, indicating it is fully charged<br />
#### If the battery light fails to turn green after 4 hours, unplug the laptop and see how long the battery lasts; the battery may need replacing<br />
#### If, after charging for four hours, the laptop switches off immediately or soon after disconnecting it from the mains, replace the battery (Note that batteries may take longer to charge depending on the quality of the mains power supply and the age of the battery)<br />
# If the battery light does not come on when the laptop is plugged into the mains:<br />
## Follow the above '''power adapter diagnosis procedure''' and if the power adapter is working,<br />
### Remove the battery and replace it with a battery from another laptop that is known to work<br />
### If this new battery works then the original battery is faulty and must be replaced<br />
### If the battery that is known to work does not make the laptop work then the laptop is faulty and needs to be repaired<br />
<br />
[[User:Mark.Burnett|Mark.Burnett]] 07:40, 19 September 2010 (UTC)<br />
<br />
The above look good to me. I suggest cutting down verbosity by using pictures. Happy to provide some when I get an XO.<br />
<br />
[[User:Alexandros.Papadopoulos|Alexandros.Papadopoulos]] 09:17, 27 October 2010 (UTC)</div>Alexandros.Papadopouloshttp://wiki.laptop.org/mediawiki/index.php?title=Talk:Startup_diagnosis&diff=246013Talk:Startup diagnosis2010-09-20T12:48:46Z<p>Alexandros.Papadopoulos: /* Diagnosis */</p>
<hr />
<div>== Diagnosis ==<br />
''' The following suggestions are made as part of the [[Improving the Deployment Toolkit]] project. Please make suggestions and enhancements in this discussion page, which will be incorporated into the page and into the next release of the deployment guide'''<br />
<br />
''Note to be removed before updating the page: This page currently describes what can happen during startup without providing guidance on how to resolve problems. I suggest adding some specific diagnosis instructions along the following lines. Please provide input and ideas in this discussion page so that this diagnosis script can be improved before incorporating into the page itself.''<br />
<br />
=== Diagnosis principles ===<br />
The following basic diagnosis principles will help identify and fix problems:<br />
# Speak with people to understand what is happening from the perspective of the person experiencing the problem<br />
# Speak with people that have already attempted to fix the problem as they may have ideas about where the problem lies and possible solutions, or know what solutions have already been tried and did not work<br />
# Observe what happens yourself<br />
# Use a process of elimination to narrow down where the problem is<br />
## Consider possible causes of the problem<br />
## Start diagnosing the cause with the most likely, by replacing parts or performing tests to confirm whether that is in fact the cause<br />
# Consider what options are available for solving the problem:<br />
## If the solution will take a long time like waiting for a new part, perhaps there is a short term solution that can be used until the new part arrives, like sharing power supplies until a faulty supply is replaced<br />
# Fix the problem<br />
# Follow up later to confirm that the problem really was fixed<br />
# If the problem could not be fixed<br />
## Consider who else may be able to help and consult them<br />
## Consider completely replacing the laptop or part<br />
## Consider whether there is a way of avoiding the problem or working around the problem all together<br />
<br />
=== Diagnosis of laptop power and battery problems ===<br />
''' Note: The [[XO Troubleshooting PowerOn]] page and [[Deployment Guide/Fault Diagnosis#Startup or power problems|other pages]] also discusses how to resolve power problems but makes many assumptions and leaps to conclusions about the nature of the problem. That and this page also duplicate each other to an extent and neither are currently included in the deployment guide section of the wiki. Suggestion: Consider merging these pages and linking to the merged page from the [[Deployment Guide]]'''<br />
<br />
If the laptop fails to turn on when the power button is pressed, the following actions can help diagnose the reason why and help identify a solution:<br />
<br />
# Starting with the laptop switched off, the battery in place, and disconnected from the power, with no lights showing: Press the power button, which is at the bottom right of the screen marked with a circle with a vertical bar, to the right of the on light with the same symbol, and the battery light<br />
# Any of the following conditions could indicate that the battery has insufficient power to operate the laptop and therefore needs recharging or replacing:<br />
## The battery light comes on and is red<br />
## The laptop starts to boot but then switches itself off<br />
## The laptop completes its boot, presents the favourite activities screen, and then switches itself off<br />
## Nothing happens<br />
# If any of these happen, plug the power supply into the mains socket and connect it to the laptop (by plugging it into the socket on the left hand side of the screen at the bottom)<br />
# If the battery light comes on and is amber then this means the battery is charging from the mains<br />
## Press the on button; the power light should light up green and the screen should come on and show icons or messages indicating it is booting<br />
### If the power light fails to come on follow this '''power adapter diagnosis procedure''':<br />
#### Try using another power adapter that is known to work from a different laptop; If this works, the power adapter needs replacing<br />
#### Try using a different mains socket that is known to work; If this works, the original mains socket needs repairing<br />
#### Try removing the battery and running the laptop just from the mains socket; If this works, the battery is faulty and needs replacing<br />
### If the laptop was not working on the battery and then started working when plugged into the mains, try leaving the laptop plugged in until the battery light turns green, indicating it is fully charged<br />
#### If the battery light fails to turn green after 4 hours, unplug the laptop and see how long the battery lasts; the battery may need replacing<br />
#### If, after charging for four hours, the laptop switches off immediately or soon after disconnecting it from the mains, replace the battery (Note that batteries may take longer to charge depending on the quality of the mains power supply and the age of the battery)<br />
# If the battery light does not come on when the laptop is plugged into the mains:<br />
## Follow the above '''power adapter diagnosis procedure''' and if the power adapter is working,<br />
### Remove the battery and replace it with a battery from another laptop that is known to work<br />
### If this new battery works then the original battery is faulty and must be replaced<br />
### If the battery that is known to work does not make the laptop work then the laptop is faulty and needs to be repaired<br />
<br />
[[User:Mark.Burnett|Mark.Burnett]] 07:40, 19 September 2010 (UTC)</div>Alexandros.Papadopouloshttp://wiki.laptop.org/mediawiki/index.php?title=User:Alexandros.Papadopoulos&diff=245477User:Alexandros.Papadopoulos2010-09-09T17:16:20Z<p>Alexandros.Papadopoulos: </p>
<hr />
<div>Welcome to my user page!<br />
<br />
I hope to be useful to this project. I'm based in the UK and have experience with GNU/Linux, teaching, systems administration, documentation, IT security, consulting, project management and a keen interest in education development.<br />
<br />
I'm working on [http://wiki.laptop.org/go/Improving_the_Deployment_Toolkit improving the Deployment Guide & relevant tools].<br />
<br />
Please leave comments/suggestions/ideas on [http://wiki.laptop.org/go/User_talk:Alexandros.Papadopoulos my talk page].<br />
<br />
Looking forward to hearing from you!<br />
<br />
Alex</div>Alexandros.Papadopouloshttp://wiki.laptop.org/mediawiki/index.php?title=User:Alexandros.Papadopoulos&diff=245476User:Alexandros.Papadopoulos2010-09-09T17:14:17Z<p>Alexandros.Papadopoulos: </p>
<hr />
<div>Welcome to my user page!<br />
<br />
I hope to be useful to this project. I'm based in the UK and have experience with GNU/Linux, teaching, systems administration, documentation, IT security, consulting, project management and a keen interest in education development.<br />
<br />
I'm working on [http://wiki.laptop.org/go/Improving_the_Deployment_Toolkit improving the Deployment Guide & relevant tools].<br />
<br />
Please leave comments/suggestions/ideas on [http://wiki.laptop.org/go/User_talk:Alexandros.Papadopoulos my talk page].<br />
<br />
Looking forward to hearing from you!<br />
<br />
Alex<br />
<br />
<br />
--------<br />
<br />
__TOC__<br />
<br />
==Store templates available on the site==<br />
<br />
<br />
==Structure of useful information==<br />
<br />
* Consultation<br />
* Guideline letters of introduction<br />
* [http://wiki.laptop.org/go/One_Laptop_per_Child Documentation to explain the OLPC principles, benefits, responsibilities, implications etc]<br />
* [http://wiki.laptop.org/go/EKindling/Pre_Deployment_Survey Key questions to answer about educating communities cultural issues, feasibilities of the OLPC vision]<br />
* Full deployment lifecycle plan<br />
* Core Team or "Core Tasks"<br />
* [http://en.wikipedia.org/wiki/OLPC_XO-1 Hardware 1]<br />
* [http://laptop.org/en/laptop/hardware/specs.shtml Hardware 2]<br />
* [http://wiki.laptop.org/go/Olpc-update Software 1]<br />
* [http://en.wikipedia.org/wiki/Sugar_(GUI) Software 2]<br />
* [http://wiki.sugarlabs.org/go/Welcome_to_the_Sugar_Labs_wiki Software 3]<br />
* [http://activities.sugarlabs.org/en-US/sugar/browse/type:1/cat:107 Software 4]<br />
* [http://wiki.laptop.org/go/School_server Server / Connectivity / Infrastructure 1]<br />
* [http://wiki.laptop.org/go/XS_Recommended_Hardware Server / Connectivity / Infrastructure 2]<br />
* [http://www.olpcnews.com/internet/access/asynchronous_internet_connectivity.html Server / Connectivity / Infrastructure 3]<br />
* [http://en.wikipedia.org/wiki/OLPC_XO-1 Power Infrastructure]<br />
* Finance<br />
* Logistics<br />
* [http://en.wikipedia.org/wiki/Digitizing Digitisation & Collection of educational content]<br />
* [http://wiki.laptop.org/go/Customization_stick Customisation of the OS 1]<br />
* [http://wiki.laptop.org/go/Activity_pack Customisation of the OS 2]<br />
* [http://wiki.laptop.org/go/OLPC_Keyboard_layouts Keyboard testing and set up]<br />
* [http://en.wikipedia.org/wiki/Sugar_(GUI) SUGAR upgrades 1]<br />
* [http://www.sugarlabs.org/index.php SUGAR upgrades 2]<br />
* Logistics<br />
* Guidelines on laptop leadtimes<br />
* [http://www.customs.co.uk/Classification.html Customs guideline and Technical specs on XO]<br />
* Safety guidelines on power implications<br />
* Laptop stock control requirements<br />
* Spare Parts stock control Requirements<br />
* [http://wiki.laptop.org/go/Activation_and_developer_keys "Activation Key" requirements]<br />
* [http://wiki.laptop.org/go/Feature_roadmap/Activation_lease_security "Activation Lease" status]<br />
* [http://en.wikipedia.org/wiki/Sugar_(desktop_environment)"Imaging" and OS guidelines 1]<br />
* [http://wiki.laptop.org/go/OS_images "Imaging" and OS guidelines 2]<br />
* Localisation<br />
* [http://en.flossmanuals.net/XO/Keyboard[Keyboard selection options]<br />
* Translation and its testing<br />
* [http://wiki.laptop.org/go/Pootle Options around "Pootle" translation options]<br />
* [http://dir.yahoo.com/Reference/Dictionaries/Language/ Dictionaries (also consider wiktionary - AP)]<br />
* [http://en.wikipedia.org/wiki/Speech_synthesis Voice Synthesizer]<br />
* [http://en.wikipedia.org/wiki/Sugar_(desktop_environment) Base System customisation]<br />
* [http://activities.sugarlabs.org//en-US/sugar/ Other local data loads PDF's & other content]<br />
* Core guidelines to integrate localised material into the Core Model<br />
* [http://en.flossmanuals.net/XO/AboutNetworksAndTheInternet Connectivity]<br />
* Guidelines on laptop connectivity options<br />
* Experiences of rurual deployments<br />
* [http://wiki.laptop.org/go/Wireless_Access_Point_Compatibility Wireless mesh network options]<br />
* Power Infrastructure<br />
* Minimum laptop power & server requirements<br />
* [http://wiki.laptop.org/go/Talk:Battery_and_power Solar power options]<br />
* [http://wiki.laptop.org/go/XO_Troubleshooting_Battery Battery storage guidelines 1]<br />
* [http://wiki.laptop.org/go/Talk:Battery_and_power Battery storage guidelines 2]<br />
* [http://www.olpcnews.com/hardware/power_supply/ Other power generation options and relevant guidelines]<br />
* [http://wiki.laptop.org/go/School_server School Server]<br />
* Benefits of the Server<br />
* [http://docs.moodle.org/en/OLPC_XS_installation Guidelines on setting up the server 1]<br />
* [http://wiki.laptop.org/go/XS_Installing_Software Guidelines on setting up the server 2]<br />
* [http://www.olpcnews.com/internet/access/asynchronous_internet_connectivity.html Guidelines on setting up the server 3]<br />
* [http://wiki.laptop.org/go/Deployment_Guide/Teacher_Preparation_Student_Facilitation Teacher Preparation & Student Facilitation]<br />
* [http://wiki.laptop.org/go/Learning_workshops Learning Workshops]<br />
* [http://wiki.laptop.org/go/OLPC_Oceania/Teacher_Training Teacher preparation]<br />
* [http://en.forum.laptop.org/ Community preparation]<br />
* [http://wiki.laptop.org/go/OLPC_Oceania/Evaluation Evaluating techniques of pupils]<br />
* [http://wiki.laptop.org/go/Participate Support]<br />
* [http://wiki.laptop.org/go/Regional_community_groups Details of National Support Teams]<br />
* [http://wiki.laptop.org/go/Support_Gang Details of other possible support teams]<br />
* [http://wiki.laptop.org/go/Repair Service & Repairs]<br />
* [http://en.flossmanuals.net/XO/Repairing Assembly diagrams]<br />
* [http://wiki.laptop.org/go/Disassembly Notes on how to swop components]<br />
* [http://www.kidsmart.org.uk/ Internet Safety Training]<br />
* [http://www.direct.gov.uk/en/Parents/Yourchildshealthandsafety/Internetsafety/index.htm Technology filters 1]<br />
* [http://wiki.laptop.org/go/Ask_OLPC_a_Question_about_Social_Issues#Router-based_content_filtering.2F_parental_controls Technology Filters 2]<br />
* [http://wiki.laptop.org/go/Disassembly End of Life Planning]<br />
* [http://en.wikibooks.org/wiki/One-to-One_Laptop_Schools/Australia Contacts]<br />
<br />
==Options for useful information==<br />
<br />
* Structured around deployment<br />
* Planning for the Laptops<br />
* Initial feasibility<br />
* Local Community support<br />
* State or other statutory guidelines<br />
* Technical things around using the laptops This covers what is described as localisation - Keyboards - Translation - Voice synthesiser options - text to speech - Self Configuration of the wireless network - Other connectivity - VSAT DSL Ethernet cabling - Power suppply differences Solar Wind Human - Battery options - Server options - Internet safety and guidance options - "Sugar" training<br />
* OLPC training material from the OLPC Workshops<br />
* Teacher training<br />
* Practical advice after the laptops are in use - How to service and repair laptops - End of life planning & recycling</div>Alexandros.Papadopouloshttp://wiki.laptop.org/mediawiki/index.php?title=User:Alexandros.Papadopoulos&diff=245226User:Alexandros.Papadopoulos2010-09-08T16:07:21Z<p>Alexandros.Papadopoulos: </p>
<hr />
<div>Welcome to my user page!<br />
<br />
I hope to be useful to this project. I'm based in the UK and have experience with GNU/Linux, teaching, systems administration, documentation, IT security, consulting, project management and a keen interest in education development.<br />
<br />
I'm working on [http://wiki.laptop.org/go/Improving_the_Deployment_Toolkit improving the Deployment Guide & relevant tools].<br />
<br />
Please leave comments/suggestions/ideas on [http://wiki.laptop.org/go/User_talk:Alexandros.Papadopoulos my talk page].<br />
<br />
Looking forward to hearing from you!<br />
<br />
Alex</div>Alexandros.Papadopouloshttp://wiki.laptop.org/mediawiki/index.php?title=User_talk:Alexandros.Papadopoulos&diff=245225User talk:Alexandros.Papadopoulos2010-09-08T16:06:42Z<p>Alexandros.Papadopoulos: Created page with 'Feel free to leave comments/suggestions/ideas in this page. Remember to sign your comments by appending four tildes <nowiki>(~~~~)</nowiki> at the end. Thanks! Alex'</p>
<hr />
<div>Feel free to leave comments/suggestions/ideas in this page. Remember to sign your comments by appending four tildes <nowiki>(~~~~)</nowiki> at the end.<br />
<br />
Thanks!<br />
<br />
Alex</div>Alexandros.Papadopouloshttp://wiki.laptop.org/mediawiki/index.php?title=Improving_the_Deployment_Toolkit&diff=244588Improving the Deployment Toolkit2010-08-27T08:26:29Z<p>Alexandros.Papadopoulos: /* Approach */</p>
<hr />
<div>A place to gather ideas about creating a process to perpetually improve the [[Deployment Guide]] and deployment toolkit.<br />
<br />
If you are not a member of the team that created this page please add your comments to the [[{{TALKPAGENAME}}|Discussion page]].<br />
<br />
{{draft}}<br />
<br />
== Principles ==<br />
# Improvements will be based on real experiences<br />
# Improvements in documents and process will not depend on individuals but will stand alone and naturally support a changing OLPC team<br />
# Documents should be self explanatory (documents should be as easy to pick up and use as possible with no prior experience or training)<br />
# Improvements will be made in a sustainable way (the process by which the improvements are achieved will be documented so as to enable repeated improvement)<br />
<br />
<br />
== Challenges ==<br />
# The people involved in each deployment may be different and have never completed a deployment before<br />
# The technology being deployed evolves with time, ahead of the changes to the deployment guide<br />
# Each location to which laptops are deployed will have different challenges<br />
<br />
<br />
== Resources ==<br />
This section contains links to other sites that may contain useful information<br />
# What can we learn from Sugar Labs, e.g. via their [http://wiki.sugarlabs.org/go/Deployment_Team/Resources wiki]<br />
# "Deployment Meetings"<br />
## [http://wiki.laptop.org/go/Deployment_meetings This wiki's deployment meetings page]<br />
## [http://pipka.org/blog/2009/01/18/olpc-deployment-meetups/ Pipka deployment meeting page]<br />
# [http://wiki.laptop.org/go/OLPC_UK OLPC UK Community Effort]<br />
# [http://www.olpcnews.com/ OLPC News (separate website)]<br />
# [http://www.olpcfriends.org/ OLPC Friends]<br />
<br />
== Deliverables ==<br />
This section shows the deliverables as described in the statement of work for this improvement activity. Each deliverable contains a link to the section in this wiki where the planning for that deliverable can be conducted<br />
# Improved '''[[#Deployment Wiki|Deployment Wiki]]''' ([http://wiki.laptop.org wiki.laptop.org])<br />
## Achieved by following the process in (1) above<br />
## Clearer structure<br />
## Clearer reference to the official Deployment Guide, Deployment Toolkit and Contacts List<br />
## Links to all useful information for Deployments (e.g. sample training guides)<br />
## Additional content to include:<br />
### How to address national & regional education policy (including sponsorship) <br />
### Funding scenarios decision tree<br />
### NGO v Gov v Philanthropist v Charity<br />
### Team set up and deployment management<br />
### Links to related documents such as training guides<br />
### Templates, e.g. training & deployment timetables<br />
### Lessons learned, e.g. Don’t rely on solar power, ...<br />
### A teachers perspective / how to facilitate learning with the XO<br />
# Improved '''[[#Deployment Guide|Deployment Guide]]''' (Google Docs "official release" version)<br />
## Achieved by following the process in (1) above<br />
## Official ‘release’ of the improved Deployment Wiki suitable for printing. The purpose of this is to provide a reference document containing a cleansed and structured form of the content of the wiki.<br />
# '''[[#Process for releasing new Deployment Guide|Process for releasing new Deployment Guide]]''' (Google Doc) - to allow OLPC to continue updating new releases of the ''Deployment Guide'' from the wiki, as the information on the wiki is continually updated<br />
## Refined through delivery of 2,3, & 4 below<br />
## How to create a new release of the [[#Deployment Guide|Deployment Guide]] Google Doc from the [[#Deployment Wiki|Deployment Wiki]]<br />
## How to cleanse and restructure the [[#Deployment Wiki|Deployment Wiki]] to aid continued collaboration and maintain consistency with the [[#Deployment Guide|Deployment Guide]]<br />
## How to update the [[#Deployment Toolkit|Deployment Toolkit]] from the updated [[#Deployment Guide|Deployment Guide]]<br />
### To maintain consistency<br />
### To incorporate any new configurations, technologies or services into the cost model from new developments identified in the [[#Deployment Wiki|Deployment Wiki]]<br />
# Improved '''[[#Deployment Toolkit|Deployment Toolkit]]''' (Currently an Excel Spreadsheet; Convert to Google Docs spreadsheet?)<br />
## Achieved by following the process in (1) above<br />
## Contains a parameterized estimating model for building a laptop and infrastructure order suitable for a specific deployment, including financials and the Economic Template<br />
## Purpose is to encapsulate the knowledge of what is required to deploy one laptop per child in a form suitable for determining the infrastructure and budget requirements for a deployment<br />
## Additional content to include:<br />
### Make consistent with updated deployment guide<br />
### Include further examples of templates filled in by various deployment type (large, medium, small etc.)<br />
### Embed Economic template into same toolkit, and update to deliver a tool for showing the split of costs over time, to allow for incremental budgeting, and a tool to allow for budgeting for ongoing maintenance and laptop replacement<br />
### Include links to useful information on topics covering tax, import, replacing parts etc.<br />
# '''[[#Guideline and Process for Customising Deployment Guide|Guideline and Process for Customising Deployment Guide]]''' (Google Doc) for creating a ''Deployment Plan'' for a specific deployment. The official deployment guide contains all guidance for all kinds of deployment to all kinds of environment. Only certain parts of this guide will be relevant to each specific deployment. The official guide also becomes out of date as new lessons from new deployments are captured in the wiki. This process provides guidance on how to create a specific deployment plan by taking just the relevant material out of the official deployment guide and updating this with any new material from the deployment wiki. The purpose of this activity is to simplify things for the deployment team and make sure they have the latest information.<br />
## Guidance document about how to create a customised Deployment Guide that will be appropriate for YOUR deployment.<br />
## This is to ensure that those preparing for a Deployment complete all necessary documentation to procure the necessary laptops and associated infrastructure and complete all necessary documentation for the deployment team to commence deployment<br />
## It will include major deployment milestones, as well as collaboration and knowledge sharing activities<br />
## Outputs of using this process include:<br />
### A budget plan and order sheet created using the Deployment Toolkit<br />
### A Deployment Plan that has been tailored for this deployment by taking relevant parts of the Deployment Guide, Contacts Database and Deployment Wiki<br />
### Updated deployment tracking wiki<br />
# '''[[#Deployment Tracker|Deployment Tracker]]''' (within the ''Deployment Wiki'')<br />
## Who is at what phase (team contact details, location, nature of deployment)<br />
## What open questions they have<br />
## What problems they've solved<br />
## A copy of their deployment plan<br />
# '''[[#Contacts list|Contacts list]]''' (Google Docs Spreadsheet) - people involved in OLPC deployments across the globe, as well as their role (where known)<br />
# '''[[#Report|Report]]''' containing lessons learned, observations & recommendations<br />
## The report will summarise the changes and provide additional observations and recommendations made during the course of the work<br />
## The purpose of the report is to provide OLPC with additional insights into how people are thinking and how to improve communication, knowledge management, and effectiveness of the deployment process<br />
## To enable this activity to be repeated in the future<br />
## To identify additional improvement areas outside the scope of this piece of work<br />
## The report will include:<br />
### Summary of work done to create the deliverables to enable this activity to be repeated at a future date<br />
### Observations on potential issues that should be addressed or opportunities that could be exploited<br />
### Recommendations for how to increase the use and effectiveness of the deployment guide<br />
<br />
== Approach ==<br />
# Technical Research<br />
## Is there a way to generate a document from a wiki? (AlexP - Manual method: https://secure.wikimedia.org/wikipedia/en/wiki/Wikipedia:Tools/Editing_tools#From_Microsoft_Word )<br />
## Create a wiki editing quick reference<br />
### Technical reference for wiki notation for numbered lists, references etc.<br />
### Organisational standards<br />
#### Place the following text and a link back to this page at the top of any new page that is part of this improvement: ''This page is work in progress as part of the [[Improving the Deployment Toolkit]] activity. Please only edit if you are part of that team otherwise you can contribute ideas or review comments via the [[{{TALKPAGENAME}}|discussion page]]''<br />
### Collect references to other relevant pages like the [[Style guide]] and ensure consistency<br />
#### Prefix each page of the [[Deployment Guide]] with ''Deployment Guide/''<br />
#### Capitalise words in short phrases for page and section titles<br />
## Is there a way to automatically count the number of pages below a given page like the [[Deployment Guide]]<br />
# Create a plan<br />
## Assess the size of the guide (number of pages linked from the [[Deployment Guide]])<br />
## Identify key sections<br />
## Identify candidate pages for merging or differentiating (e.g. similar title/content)<br />
## Prioritise update activity<br />
## Allocate update tasks<br />
# Identify people to contribute or review<br />
## Identify people to interview<br />
## Identify members of the [[Wiki gang]] who could advise or review<br />
## Use the wiki history pages to:<br />
### Identify frequently active users<br />
### Identify main authors/experts for key pages<br />
# Setup interviews and meetings for status updates and reviews<br />
# Create a copy of the [[Deployment Guide]] page as a [[Draft Deployment Guide]]<br />
# Update the [[Draft Deployment Guide]]<br />
## Preparation<br />
### Check sections with the same title as new sections you want to add don't already exist and if they do make a decision about whether to edit that live page directly or to take a copy and publish it by copying it back later as we do with the main [[Deployment Guide]] page<br />
### Review material in the [[ClassActs/Resources]] section<br />
### Identify existing material that could be referred to by or moved into the new sections<br />
## Add new sections<br />
### [[How to align with national & regional education policy]] (including sponsorship)<br />
### [[Planning scenarios decision tree]] (use Policy Questions word doc as basis)<br />
#### Funding<br />
#### Policy<br />
#### NGO<br />
#### Government<br />
#### Philanthropist<br />
#### Charity<br />
### [[Team setup and deployment management]]<br />
### [[Links to related documents]] such as training guides<br />
### [[Templates]], e.g. training & deployment timetables<br />
### [[Lessons learned]], e.g. Don’t rely on solar power, ...<br />
### [[A teachers perspective]] / how to facilitate learning with the XO<br />
### [[How to edit this wiki]]<br />
## Follow all links from the [[Draft Deployment Guide]] according to priorities<br />
### Combine or delete pages where appropriate, updating any references to these at the same time<br />
### Review and update pages to improve clarity, navigation and accuracy<br />
### Split pages into multiple sections or pages where appropriate<br />
### Add cross references between pages where appropriate<br />
## Review structure and flow of the [[Draft Deployment Guide]]<br />
## Add additional navigation / cross references between sections as required<br />
## Add clearer reference to the official Deployment Guide, Deployment Toolkit and Contacts List<br />
## Go through the google doc and add missing material back into the [[Working Deployment Wiki]]<br />
## Use the discussion tab for each wiki page for sharing ideas and review comments<br />
# Review [[Draft Deployment Guide]] with OLPC<br />
# Create google doc from [[Draft Deployment Guide]]<br />
# Review google doc with OLPC<br />
# Agree publishing date and comms with OLPC<br />
# Copy the [[Draft Deployment Guide]] back into the [[Deployment Guide]]<br />
# Announce new [[Deployment Guide]] and google doc<br />
# Use this section as a basis for creating the [[Process for Releasing New Deployment Guide]]<br />
# Create a [[Deployment Toolkit]] (wiki page and excel spreadsheet)<br />
## Obtain latest versions of spreadsheets<br />
## Combine the ''OLPC Deployment Workbook'' Excel spreadsheet (country budget planner) with the ''Economic Template'' Excel spreadsheet<br />
## Simplify<br />
## Improve usability<br />
## Update assumptions if required (contact authors)<br />
## Align the [[Deployment Toolkit]] with the [[Deployment Guide]]<br />
### For each line item in the spreadsheet there should be a corresponding section in the wiki<br />
### For each relevant section in the wiki, the spreadsheet should allow budget planning for it, e.g.<br />
#### Power generation solutions<br />
#### Teacher training options<br />
#### Project support resourcing options<br />
# Create [[Guidelines and Process for Customising the Deployment Guide]]<br />
# Create [[Deployment Tracker]]<br />
## Leverage existing resources such as the google map showing deployments<br />
<br />
== Plan ==<br />
<br />
== Core Team ==<br />
The core team are managing the project described in this page, allocation of tasks, and communication with OLPC and other third party contacts.<br />
<br />
The core team consists of the following people:<br />
# Pippa Thomas<br />
# [[User:Mark.Burnett|Mark Burnett]]<br />
# [[User:Alexandros.Papadopoulos|Alexandros Papadopoulos]]<br />
<br />
== Extended Team ==<br />
The extended team consists of the following people:<br />
# Toyosi Ogedengbe<br />
# Sergio Coury<br />
<br />
This list is maintained by the [[#Core Team|Core Team]]<br />
<br />
== Task Management ==<br />
=== Ideas ===<br />
As Ideas emerge and are discussed they will be added into the deliverables below<br />
<br />
# Identify and document the major [[#Processes|Processes]] in simple to follow steps<br />
# Get a non consultant, non technical author to review our deliverables from a readability perspective<br />
## Early on to help ensure write in simple non consultant English<br />
## Near the end to review the final deliverables<br />
# Include an orientation and induction process<br />
# Find other initiatives similar to OLPC that we can learn from<br />
# Find other kinds of deployment guide that we can learn from<br />
# Who else can we learn from?<br />
# Include a map of the various different resources / web sites and their purposes - list forming under the [[#Resources|Resources]] section<br />
# There seem to be a lot of people enthusiastically sharing their experiences via all sorts of different wikis, and the way some of the entries are written is more like a personal blog - i.e. a stream of consciousness of their lessons learned and experiences. This is no doubt effortless for the individuals by comparison to attempting to edit a wiki by finding the right place to update information. So something to think about is how can we increase the ease of updating the wiki or how can we more effectively harvest the personal experiences without having a team to do it<br />
# Consider how children can pass on knowledge from one generation to the next, so as younger children come into a school and are given a laptop they learn from older children and the older children are challenged to put their knowledge into practice through the questions of the younger children<br />
# Create a facebook page for children with an XO so they can communicate and share ideas with each other<br />
<br />
=== Unallocated tasks ===<br />
This section contains a list of tasks identified by the extended team or collated from discussion pages creates as part of this project. Tasks will be moved from this section into the [[Allocated tasks]] section by the core team as they are allocated.<br />
# Identify duplicate pages and recommend approach to consolidate / delete<br />
=== Allocated tasks ===<br />
This section contains tasks allocated to specific members of the extended team by the core team.<br />
==== [[User:PippaThomas | Pippa Thomas]] ====<br />
# Create a single page FAQ describing what OLPC do and what we are doing on this project<br />
<br />
=== Tasks pending review ===<br />
=== Completed Tasks ===<br />
== Processes ==<br />
<br />
=== Guideline and Process for Customising Deployment Guide ===<br />
# Update the [[#Deployment Tracking Wiki|Deployment Tracking Wiki]] to indicate you are preparing a deployment<br />
# Follow the [[#Readiness Assessment Process|Readiness Assessment Process]] to check you have everything you need to start a deployment and understand the main areas of challenge for your particular location<br />
# Make a copy of the [[#Deployment Guide|Deployment Guide]] and call it "[[#Location Deployment Plan|Location Deployment Plan]]" (replacing the word "Location" with the name of the location you are deploying to<br />
# Remove sections from the document that do not apply to you<br />
# Update the ''Team'' section with roles and responsibilities and contact details for your team<br />
# Update the ''Support Team'' section with roles, areas of expertise and contact details of any people in other teams that have agreed to support your team<br />
# Follow the [[#Deployment Plan|Deployment Plan]]<br />
<br />
=== Solve Problem Process ===<br />
Part of the [[#Deployment Process|Deployment Process]]<br />
# Check to see if the [[#Deployment Guide|Deployment Guide]] says how to solve the problem<br />
# Check to see if the [[#Deployment Wiki|Deployment Wiki]] says how to solve the problem<br />
# Check to see if there are any [[#Open Question|Open Question]]s in the [[#Deployment Wiki|Deployment Wiki]] that are similar to yours; If there are, contact the teams that created those questions to see if they have made progress and work together to solve the problem<br />
# If no solutions can be found, create an [[#Open Question|Open Question]] page so that others can see you are trying to solve this problem<br />
# Check the [[#Deployment Tracker|Deployment Tracker]] to see what other teams are currently working who are at the same or later stage in the [[#Deployment Process|Deployment Process]] as you and consult with them<br />
# Update the [[#Open Question|Open Question]] page when you find a solution<br />
<br />
=== Readiness Assessment Process ===<br />
This process helps you determine whether you are ready to start a deployment by providing a checklist. It also includes a questionnaire to help you determine the major areas of challenge you may have to point you in the right direction for how to overcome these challenges, such as <br />
* by providing links to specific collaboration areas in the [[#Deployment Wiki|Deployment Wiki]] that may be more up to date than the guide as it is used by those involved in deployments right now to collaborate and share ideas<br />
* by pointing you at the most relevant areas in the [[#Dealing with exceptions|Dealing with exceptions]] section of the ''Deployment Guide''<br />
<br />
=== Process for releasing new Deployment Guide ===<br />
<br />
Assumptions:<br />
* The ''Deployment Guide'' will always be available from the same URL<br />
* A draft of the new release will be created in a separate document whilst it is being worked on<br />
* Once the new release is ready for publication, the google doc will be updated and an announcement made on the ''Deployment Wiki''<br />
<br />
Process:<br />
# Identify volunteers from currently active deployment teams to support the process by providing up to date experience and review of changes to the wiki and document<br />
# Create a new page in the [[#Deployment Wiki|Deployment Wiki]] for collaborating on producing the new version of the ''Deployment Guide''<br />
# Update the front page of the wiki to say that a new version of the deployment guide is currently being produced, the expected date by which it will be available, and provide a link to the collaboration page inviting input<br />
# Produce a draft of the new ''Deployment Guide'' by copying the current release into a new google doc<br />
# Review changes made to the [http://wiki.laptop.org wiki.laptop.org Deployment Wiki] since the last release of the ''Deployment Guide'' was created<br />
## Consolidate similar entries in the wiki and add these to the draft deployment guide or replace sections if these entries supercede them and also remove the corresponding superceded sections of the wiki<br />
## Review the [[#Open Question|Open Question]]s section of the [[#Deployment Wiki|Deployment Wiki]]<br />
### Answer the questions if possible, consulting the deployment teams who raised them in the process to validate the answers<br />
### Update the Open Question page and incorporate the answer into the draft deployment guide<br />
# Send the draft to the volunteers and members of the core team who have agreed to review it<br />
# Apply review comments<br />
# Issue the new document by publishing a message on the ''Deployment Wiki''<br />
<br />
== Documents ==<br />
<br />
=== Deployment Guide ===<br />
'''Notes:'''<br />
As well as containing a refinement of the current ''Deployment Guide'', this revised document will also contain the following:<br />
# A process for requesting improvements to the guide<br />
# A process for requesting help when the guide does not contain the expected information (the [[#Solve Problem Process|Solve Problem Process]])<br />
# A FAQ (Frequently Asked Questions) section<br />
# The Anatomy of an OLPC deployment<br />
## A high level overview of the deployment process<br />
## The typical roles and responsibilities of deployment team members<br />
## A list and description of all the typical parts (e.g. laptops, power, connectivity) and associated deployment activities<br />
## A list of alternative parts, pros and cons of each and when you would usually choose one over another (e.g. forms of power)<br />
# Glossary of terms<br />
# A [[#Dealing with exceptions|Dealing with exceptions]] section listing the circumstances that are not dealt with by the standard deployment process either because they are problem situations or exceptional or rare circumstances that would otherwise clutter the process and make it difficult to follow<br />
<br />
'''Sections:'''<br />
==== Dealing with Exceptions ====<br />
<br />
=== Contacts List ===<br />
Containing the following details for each contact:<br />
* Name<br />
* Role<br />
* Location<br />
* Areas of expertise<br />
* Email<br />
* Mobile<br />
* Land line<br />
* Address<br />
* Deployment experience (which locations have they been involved in deploying)<br />
<br />
=== Report ===<br />
Containing the following sections:<br />
# Summary of work done to create the deliverables to enable this activity to be repeated at a future date<br />
# Observations on potential issues that should be addressed or opportunities that could be exploited<br />
# Recommendations for how to increase the use and effectiveness of the deployment guide<br />
<br />
<br />
=== Location Deployment Plan ===<br />
The ''Location Deployment Plan'' provides a plan for a specific deployment.<br />
It is created by the [[#Guideline and Process for Customising Deployment Guide|Guideline and Process for Customising Deployment Guide]] from the [[#Deployment Guide|Deployment Guide]].<br />
<br />
== Templates for ''Deployment Wiki'' Pages ==<br />
<br />
=== Open Question ===<br />
<br />
Contents<br />
# Question title<br />
# Description of the problem<br />
# Solutions considered and discarded and why<br />
# Ideas for how to solve the problem that are currently being explored<br />
# Contact details for the team</div>Alexandros.Papadopouloshttp://wiki.laptop.org/mediawiki/index.php?title=Improving_the_Deployment_Toolkit&diff=244587Improving the Deployment Toolkit2010-08-27T08:23:48Z<p>Alexandros.Papadopoulos: /* User:PippaThomas */</p>
<hr />
<div>A place to gather ideas about creating a process to perpetually improve the [[Deployment Guide]] and deployment toolkit.<br />
<br />
If you are not a member of the team that created this page please add your comments to the [[{{TALKPAGENAME}}|Discussion page]].<br />
<br />
{{draft}}<br />
<br />
== Principles ==<br />
# Improvements will be based on real experiences<br />
# Improvements in documents and process will not depend on individuals but will stand alone and naturally support a changing OLPC team<br />
# Documents should be self explanatory (documents should be as easy to pick up and use as possible with no prior experience or training)<br />
# Improvements will be made in a sustainable way (the process by which the improvements are achieved will be documented so as to enable repeated improvement)<br />
<br />
<br />
== Challenges ==<br />
# The people involved in each deployment may be different and have never completed a deployment before<br />
# The technology being deployed evolves with time, ahead of the changes to the deployment guide<br />
# Each location to which laptops are deployed will have different challenges<br />
<br />
<br />
== Resources ==<br />
This section contains links to other sites that may contain useful information<br />
# What can we learn from Sugar Labs, e.g. via their [http://wiki.sugarlabs.org/go/Deployment_Team/Resources wiki]<br />
# "Deployment Meetings"<br />
## [http://wiki.laptop.org/go/Deployment_meetings This wiki's deployment meetings page]<br />
## [http://pipka.org/blog/2009/01/18/olpc-deployment-meetups/ Pipka deployment meeting page]<br />
# [http://wiki.laptop.org/go/OLPC_UK OLPC UK Community Effort]<br />
# [http://www.olpcnews.com/ OLPC News (separate website)]<br />
# [http://www.olpcfriends.org/ OLPC Friends]<br />
<br />
== Deliverables ==<br />
This section shows the deliverables as described in the statement of work for this improvement activity. Each deliverable contains a link to the section in this wiki where the planning for that deliverable can be conducted<br />
# Improved '''[[#Deployment Wiki|Deployment Wiki]]''' ([http://wiki.laptop.org wiki.laptop.org])<br />
## Achieved by following the process in (1) above<br />
## Clearer structure<br />
## Clearer reference to the official Deployment Guide, Deployment Toolkit and Contacts List<br />
## Links to all useful information for Deployments (e.g. sample training guides)<br />
## Additional content to include:<br />
### How to address national & regional education policy (including sponsorship) <br />
### Funding scenarios decision tree<br />
### NGO v Gov v Philanthropist v Charity<br />
### Team set up and deployment management<br />
### Links to related documents such as training guides<br />
### Templates, e.g. training & deployment timetables<br />
### Lessons learned, e.g. Don’t rely on solar power, ...<br />
### A teachers perspective / how to facilitate learning with the XO<br />
# Improved '''[[#Deployment Guide|Deployment Guide]]''' (Google Docs "official release" version)<br />
## Achieved by following the process in (1) above<br />
## Official ‘release’ of the improved Deployment Wiki suitable for printing. The purpose of this is to provide a reference document containing a cleansed and structured form of the content of the wiki.<br />
# '''[[#Process for releasing new Deployment Guide|Process for releasing new Deployment Guide]]''' (Google Doc) - to allow OLPC to continue updating new releases of the ''Deployment Guide'' from the wiki, as the information on the wiki is continually updated<br />
## Refined through delivery of 2,3, & 4 below<br />
## How to create a new release of the [[#Deployment Guide|Deployment Guide]] Google Doc from the [[#Deployment Wiki|Deployment Wiki]]<br />
## How to cleanse and restructure the [[#Deployment Wiki|Deployment Wiki]] to aid continued collaboration and maintain consistency with the [[#Deployment Guide|Deployment Guide]]<br />
## How to update the [[#Deployment Toolkit|Deployment Toolkit]] from the updated [[#Deployment Guide|Deployment Guide]]<br />
### To maintain consistency<br />
### To incorporate any new configurations, technologies or services into the cost model from new developments identified in the [[#Deployment Wiki|Deployment Wiki]]<br />
# Improved '''[[#Deployment Toolkit|Deployment Toolkit]]''' (Currently an Excel Spreadsheet; Convert to Google Docs spreadsheet?)<br />
## Achieved by following the process in (1) above<br />
## Contains a parameterized estimating model for building a laptop and infrastructure order suitable for a specific deployment, including financials and the Economic Template<br />
## Purpose is to encapsulate the knowledge of what is required to deploy one laptop per child in a form suitable for determining the infrastructure and budget requirements for a deployment<br />
## Additional content to include:<br />
### Make consistent with updated deployment guide<br />
### Include further examples of templates filled in by various deployment type (large, medium, small etc.)<br />
### Embed Economic template into same toolkit, and update to deliver a tool for showing the split of costs over time, to allow for incremental budgeting, and a tool to allow for budgeting for ongoing maintenance and laptop replacement<br />
### Include links to useful information on topics covering tax, import, replacing parts etc.<br />
# '''[[#Guideline and Process for Customising Deployment Guide|Guideline and Process for Customising Deployment Guide]]''' (Google Doc) for creating a ''Deployment Plan'' for a specific deployment. The official deployment guide contains all guidance for all kinds of deployment to all kinds of environment. Only certain parts of this guide will be relevant to each specific deployment. The official guide also becomes out of date as new lessons from new deployments are captured in the wiki. This process provides guidance on how to create a specific deployment plan by taking just the relevant material out of the official deployment guide and updating this with any new material from the deployment wiki. The purpose of this activity is to simplify things for the deployment team and make sure they have the latest information.<br />
## Guidance document about how to create a customised Deployment Guide that will be appropriate for YOUR deployment.<br />
## This is to ensure that those preparing for a Deployment complete all necessary documentation to procure the necessary laptops and associated infrastructure and complete all necessary documentation for the deployment team to commence deployment<br />
## It will include major deployment milestones, as well as collaboration and knowledge sharing activities<br />
## Outputs of using this process include:<br />
### A budget plan and order sheet created using the Deployment Toolkit<br />
### A Deployment Plan that has been tailored for this deployment by taking relevant parts of the Deployment Guide, Contacts Database and Deployment Wiki<br />
### Updated deployment tracking wiki<br />
# '''[[#Deployment Tracker|Deployment Tracker]]''' (within the ''Deployment Wiki'')<br />
## Who is at what phase (team contact details, location, nature of deployment)<br />
## What open questions they have<br />
## What problems they've solved<br />
## A copy of their deployment plan<br />
# '''[[#Contacts list|Contacts list]]''' (Google Docs Spreadsheet) - people involved in OLPC deployments across the globe, as well as their role (where known)<br />
# '''[[#Report|Report]]''' containing lessons learned, observations & recommendations<br />
## The report will summarise the changes and provide additional observations and recommendations made during the course of the work<br />
## The purpose of the report is to provide OLPC with additional insights into how people are thinking and how to improve communication, knowledge management, and effectiveness of the deployment process<br />
## To enable this activity to be repeated in the future<br />
## To identify additional improvement areas outside the scope of this piece of work<br />
## The report will include:<br />
### Summary of work done to create the deliverables to enable this activity to be repeated at a future date<br />
### Observations on potential issues that should be addressed or opportunities that could be exploited<br />
### Recommendations for how to increase the use and effectiveness of the deployment guide<br />
<br />
== Approach ==<br />
# Technical Research<br />
## Is there a way to generate a document from a wiki? (Alex P)<br />
## Create a wiki editing quick reference<br />
### Technical reference for wiki notation for numbered lists, references etc.<br />
### Organisational standards<br />
#### Place the following text and a link back to this page at the top of any new page that is part of this improvement: ''This page is work in progress as part of the [[Improving the Deployment Toolkit]] activity. Please only edit if you are part of that team otherwise you can contribute ideas or review comments via the [[{{TALKPAGENAME}}|discussion page]]''<br />
### Collect references to other relevant pages like the [[Style guide]] and ensure consistency<br />
#### Prefix each page of the [[Deployment Guide]] with ''Deployment Guide/''<br />
#### Capitalise words in short phrases for page and section titles<br />
## Is there a way to automatically count the number of pages below a given page like the [[Deployment Guide]]<br />
# Create a plan<br />
## Assess the size of the guide (number of pages linked from the [[Deployment Guide]])<br />
## Identify key sections<br />
## Identify candidate pages for merging or differentiating (e.g. similar title/content)<br />
## Prioritise update activity<br />
## Allocate update tasks<br />
# Identify people to contribute or review<br />
## Identify people to interview<br />
## Identify members of the [[Wiki gang]] who could advise or review<br />
## Use the wiki history pages to:<br />
### Identify frequently active users<br />
### Identify main authors/experts for key pages<br />
# Setup interviews and meetings for status updates and reviews<br />
# Create a copy of the [[Deployment Guide]] page as a [[Draft Deployment Guide]]<br />
# Update the [[Draft Deployment Guide]]<br />
## Preparation<br />
### Check sections with the same title as new sections you want to add don't already exist and if they do make a decision about whether to edit that live page directly or to take a copy and publish it by copying it back later as we do with the main [[Deployment Guide]] page<br />
### Review material in the [[ClassActs/Resources]] section<br />
### Identify existing material that could be referred to by or moved into the new sections<br />
## Add new sections<br />
### [[How to align with national & regional education policy]] (including sponsorship)<br />
### [[Planning scenarios decision tree]] (use Policy Questions word doc as basis)<br />
#### Funding<br />
#### Policy<br />
#### NGO<br />
#### Government<br />
#### Philanthropist<br />
#### Charity<br />
### [[Team setup and deployment management]]<br />
### [[Links to related documents]] such as training guides<br />
### [[Templates]], e.g. training & deployment timetables<br />
### [[Lessons learned]], e.g. Don’t rely on solar power, ...<br />
### [[A teachers perspective]] / how to facilitate learning with the XO<br />
### [[How to edit this wiki]]<br />
## Follow all links from the [[Draft Deployment Guide]] according to priorities<br />
### Combine or delete pages where appropriate, updating any references to these at the same time<br />
### Review and update pages to improve clarity, navigation and accuracy<br />
### Split pages into multiple sections or pages where appropriate<br />
### Add cross references between pages where appropriate<br />
## Review structure and flow of the [[Draft Deployment Guide]]<br />
## Add additional navigation / cross references between sections as required<br />
## Add clearer reference to the official Deployment Guide, Deployment Toolkit and Contacts List<br />
## Go through the google doc and add missing material back into the [[Working Deployment Wiki]]<br />
## Use the discussion tab for each wiki page for sharing ideas and review comments<br />
# Review [[Draft Deployment Guide]] with OLPC<br />
# Create google doc from [[Draft Deployment Guide]]<br />
# Review google doc with OLPC<br />
# Agree publishing date and comms with OLPC<br />
# Copy the [[Draft Deployment Guide]] back into the [[Deployment Guide]]<br />
# Announce new [[Deployment Guide]] and google doc<br />
# Use this section as a basis for creating the [[Process for Releasing New Deployment Guide]]<br />
# Create a [[Deployment Toolkit]] (wiki page and excel spreadsheet)<br />
## Obtain latest versions of spreadsheets<br />
## Combine the ''OLPC Deployment Workbook'' Excel spreadsheet (country budget planner) with the ''Economic Template'' Excel spreadsheet<br />
## Simplify<br />
## Improve usability<br />
## Update assumptions if required (contact authors)<br />
## Align the [[Deployment Toolkit]] with the [[Deployment Guide]]<br />
### For each line item in the spreadsheet there should be a corresponding section in the wiki<br />
### For each relevant section in the wiki, the spreadsheet should allow budget planning for it, e.g.<br />
#### Power generation solutions<br />
#### Teacher training options<br />
#### Project support resourcing options<br />
# Create [[Guidelines and Process for Customising the Deployment Guide]]<br />
# Create [[Deployment Tracker]]<br />
## Leverage existing resources such as the google map showing deployments<br />
<br />
== Plan ==<br />
<br />
== Core Team ==<br />
The core team are managing the project described in this page, allocation of tasks, and communication with OLPC and other third party contacts.<br />
<br />
The core team consists of the following people:<br />
# Pippa Thomas<br />
# [[User:Mark.Burnett|Mark Burnett]]<br />
# [[User:Alexandros.Papadopoulos|Alexandros Papadopoulos]]<br />
<br />
== Extended Team ==<br />
The extended team consists of the following people:<br />
# Toyosi Ogedengbe<br />
# Sergio Coury<br />
<br />
This list is maintained by the [[#Core Team|Core Team]]<br />
<br />
== Task Management ==<br />
=== Ideas ===<br />
As Ideas emerge and are discussed they will be added into the deliverables below<br />
<br />
# Identify and document the major [[#Processes|Processes]] in simple to follow steps<br />
# Get a non consultant, non technical author to review our deliverables from a readability perspective<br />
## Early on to help ensure write in simple non consultant English<br />
## Near the end to review the final deliverables<br />
# Include an orientation and induction process<br />
# Find other initiatives similar to OLPC that we can learn from<br />
# Find other kinds of deployment guide that we can learn from<br />
# Who else can we learn from?<br />
# Include a map of the various different resources / web sites and their purposes - list forming under the [[#Resources|Resources]] section<br />
# There seem to be a lot of people enthusiastically sharing their experiences via all sorts of different wikis, and the way some of the entries are written is more like a personal blog - i.e. a stream of consciousness of their lessons learned and experiences. This is no doubt effortless for the individuals by comparison to attempting to edit a wiki by finding the right place to update information. So something to think about is how can we increase the ease of updating the wiki or how can we more effectively harvest the personal experiences without having a team to do it<br />
# Consider how children can pass on knowledge from one generation to the next, so as younger children come into a school and are given a laptop they learn from older children and the older children are challenged to put their knowledge into practice through the questions of the younger children<br />
# Create a facebook page for children with an XO so they can communicate and share ideas with each other<br />
<br />
=== Unallocated tasks ===<br />
This section contains a list of tasks identified by the extended team or collated from discussion pages creates as part of this project. Tasks will be moved from this section into the [[Allocated tasks]] section by the core team as they are allocated.<br />
# Identify duplicate pages and recommend approach to consolidate / delete<br />
=== Allocated tasks ===<br />
This section contains tasks allocated to specific members of the extended team by the core team.<br />
==== [[User:PippaThomas | Pippa Thomas]] ====<br />
# Create a single page FAQ describing what OLPC do and what we are doing on this project<br />
<br />
=== Tasks pending review ===<br />
=== Completed Tasks ===<br />
== Processes ==<br />
<br />
=== Guideline and Process for Customising Deployment Guide ===<br />
# Update the [[#Deployment Tracking Wiki|Deployment Tracking Wiki]] to indicate you are preparing a deployment<br />
# Follow the [[#Readiness Assessment Process|Readiness Assessment Process]] to check you have everything you need to start a deployment and understand the main areas of challenge for your particular location<br />
# Make a copy of the [[#Deployment Guide|Deployment Guide]] and call it "[[#Location Deployment Plan|Location Deployment Plan]]" (replacing the word "Location" with the name of the location you are deploying to<br />
# Remove sections from the document that do not apply to you<br />
# Update the ''Team'' section with roles and responsibilities and contact details for your team<br />
# Update the ''Support Team'' section with roles, areas of expertise and contact details of any people in other teams that have agreed to support your team<br />
# Follow the [[#Deployment Plan|Deployment Plan]]<br />
<br />
=== Solve Problem Process ===<br />
Part of the [[#Deployment Process|Deployment Process]]<br />
# Check to see if the [[#Deployment Guide|Deployment Guide]] says how to solve the problem<br />
# Check to see if the [[#Deployment Wiki|Deployment Wiki]] says how to solve the problem<br />
# Check to see if there are any [[#Open Question|Open Question]]s in the [[#Deployment Wiki|Deployment Wiki]] that are similar to yours; If there are, contact the teams that created those questions to see if they have made progress and work together to solve the problem<br />
# If no solutions can be found, create an [[#Open Question|Open Question]] page so that others can see you are trying to solve this problem<br />
# Check the [[#Deployment Tracker|Deployment Tracker]] to see what other teams are currently working who are at the same or later stage in the [[#Deployment Process|Deployment Process]] as you and consult with them<br />
# Update the [[#Open Question|Open Question]] page when you find a solution<br />
<br />
=== Readiness Assessment Process ===<br />
This process helps you determine whether you are ready to start a deployment by providing a checklist. It also includes a questionnaire to help you determine the major areas of challenge you may have to point you in the right direction for how to overcome these challenges, such as <br />
* by providing links to specific collaboration areas in the [[#Deployment Wiki|Deployment Wiki]] that may be more up to date than the guide as it is used by those involved in deployments right now to collaborate and share ideas<br />
* by pointing you at the most relevant areas in the [[#Dealing with exceptions|Dealing with exceptions]] section of the ''Deployment Guide''<br />
<br />
=== Process for releasing new Deployment Guide ===<br />
<br />
Assumptions:<br />
* The ''Deployment Guide'' will always be available from the same URL<br />
* A draft of the new release will be created in a separate document whilst it is being worked on<br />
* Once the new release is ready for publication, the google doc will be updated and an announcement made on the ''Deployment Wiki''<br />
<br />
Process:<br />
# Identify volunteers from currently active deployment teams to support the process by providing up to date experience and review of changes to the wiki and document<br />
# Create a new page in the [[#Deployment Wiki|Deployment Wiki]] for collaborating on producing the new version of the ''Deployment Guide''<br />
# Update the front page of the wiki to say that a new version of the deployment guide is currently being produced, the expected date by which it will be available, and provide a link to the collaboration page inviting input<br />
# Produce a draft of the new ''Deployment Guide'' by copying the current release into a new google doc<br />
# Review changes made to the [http://wiki.laptop.org wiki.laptop.org Deployment Wiki] since the last release of the ''Deployment Guide'' was created<br />
## Consolidate similar entries in the wiki and add these to the draft deployment guide or replace sections if these entries supercede them and also remove the corresponding superceded sections of the wiki<br />
## Review the [[#Open Question|Open Question]]s section of the [[#Deployment Wiki|Deployment Wiki]]<br />
### Answer the questions if possible, consulting the deployment teams who raised them in the process to validate the answers<br />
### Update the Open Question page and incorporate the answer into the draft deployment guide<br />
# Send the draft to the volunteers and members of the core team who have agreed to review it<br />
# Apply review comments<br />
# Issue the new document by publishing a message on the ''Deployment Wiki''<br />
<br />
== Documents ==<br />
<br />
=== Deployment Guide ===<br />
'''Notes:'''<br />
As well as containing a refinement of the current ''Deployment Guide'', this revised document will also contain the following:<br />
# A process for requesting improvements to the guide<br />
# A process for requesting help when the guide does not contain the expected information (the [[#Solve Problem Process|Solve Problem Process]])<br />
# A FAQ (Frequently Asked Questions) section<br />
# The Anatomy of an OLPC deployment<br />
## A high level overview of the deployment process<br />
## The typical roles and responsibilities of deployment team members<br />
## A list and description of all the typical parts (e.g. laptops, power, connectivity) and associated deployment activities<br />
## A list of alternative parts, pros and cons of each and when you would usually choose one over another (e.g. forms of power)<br />
# Glossary of terms<br />
# A [[#Dealing with exceptions|Dealing with exceptions]] section listing the circumstances that are not dealt with by the standard deployment process either because they are problem situations or exceptional or rare circumstances that would otherwise clutter the process and make it difficult to follow<br />
<br />
'''Sections:'''<br />
==== Dealing with Exceptions ====<br />
<br />
=== Contacts List ===<br />
Containing the following details for each contact:<br />
* Name<br />
* Role<br />
* Location<br />
* Areas of expertise<br />
* Email<br />
* Mobile<br />
* Land line<br />
* Address<br />
* Deployment experience (which locations have they been involved in deploying)<br />
<br />
=== Report ===<br />
Containing the following sections:<br />
# Summary of work done to create the deliverables to enable this activity to be repeated at a future date<br />
# Observations on potential issues that should be addressed or opportunities that could be exploited<br />
# Recommendations for how to increase the use and effectiveness of the deployment guide<br />
<br />
<br />
=== Location Deployment Plan ===<br />
The ''Location Deployment Plan'' provides a plan for a specific deployment.<br />
It is created by the [[#Guideline and Process for Customising Deployment Guide|Guideline and Process for Customising Deployment Guide]] from the [[#Deployment Guide|Deployment Guide]].<br />
<br />
== Templates for ''Deployment Wiki'' Pages ==<br />
<br />
=== Open Question ===<br />
<br />
Contents<br />
# Question title<br />
# Description of the problem<br />
# Solutions considered and discarded and why<br />
# Ideas for how to solve the problem that are currently being explored<br />
# Contact details for the team</div>Alexandros.Papadopouloshttp://wiki.laptop.org/mediawiki/index.php?title=Improving_the_Deployment_Toolkit&diff=244586Improving the Deployment Toolkit2010-08-27T08:22:32Z<p>Alexandros.Papadopoulos: /* Core Team */</p>
<hr />
<div>A place to gather ideas about creating a process to perpetually improve the [[Deployment Guide]] and deployment toolkit.<br />
<br />
If you are not a member of the team that created this page please add your comments to the [[{{TALKPAGENAME}}|Discussion page]].<br />
<br />
{{draft}}<br />
<br />
== Principles ==<br />
# Improvements will be based on real experiences<br />
# Improvements in documents and process will not depend on individuals but will stand alone and naturally support a changing OLPC team<br />
# Documents should be self explanatory (documents should be as easy to pick up and use as possible with no prior experience or training)<br />
# Improvements will be made in a sustainable way (the process by which the improvements are achieved will be documented so as to enable repeated improvement)<br />
<br />
<br />
== Challenges ==<br />
# The people involved in each deployment may be different and have never completed a deployment before<br />
# The technology being deployed evolves with time, ahead of the changes to the deployment guide<br />
# Each location to which laptops are deployed will have different challenges<br />
<br />
<br />
== Resources ==<br />
This section contains links to other sites that may contain useful information<br />
# What can we learn from Sugar Labs, e.g. via their [http://wiki.sugarlabs.org/go/Deployment_Team/Resources wiki]<br />
# "Deployment Meetings"<br />
## [http://wiki.laptop.org/go/Deployment_meetings This wiki's deployment meetings page]<br />
## [http://pipka.org/blog/2009/01/18/olpc-deployment-meetups/ Pipka deployment meeting page]<br />
# [http://wiki.laptop.org/go/OLPC_UK OLPC UK Community Effort]<br />
# [http://www.olpcnews.com/ OLPC News (separate website)]<br />
# [http://www.olpcfriends.org/ OLPC Friends]<br />
<br />
== Deliverables ==<br />
This section shows the deliverables as described in the statement of work for this improvement activity. Each deliverable contains a link to the section in this wiki where the planning for that deliverable can be conducted<br />
# Improved '''[[#Deployment Wiki|Deployment Wiki]]''' ([http://wiki.laptop.org wiki.laptop.org])<br />
## Achieved by following the process in (1) above<br />
## Clearer structure<br />
## Clearer reference to the official Deployment Guide, Deployment Toolkit and Contacts List<br />
## Links to all useful information for Deployments (e.g. sample training guides)<br />
## Additional content to include:<br />
### How to address national & regional education policy (including sponsorship) <br />
### Funding scenarios decision tree<br />
### NGO v Gov v Philanthropist v Charity<br />
### Team set up and deployment management<br />
### Links to related documents such as training guides<br />
### Templates, e.g. training & deployment timetables<br />
### Lessons learned, e.g. Don’t rely on solar power, ...<br />
### A teachers perspective / how to facilitate learning with the XO<br />
# Improved '''[[#Deployment Guide|Deployment Guide]]''' (Google Docs "official release" version)<br />
## Achieved by following the process in (1) above<br />
## Official ‘release’ of the improved Deployment Wiki suitable for printing. The purpose of this is to provide a reference document containing a cleansed and structured form of the content of the wiki.<br />
# '''[[#Process for releasing new Deployment Guide|Process for releasing new Deployment Guide]]''' (Google Doc) - to allow OLPC to continue updating new releases of the ''Deployment Guide'' from the wiki, as the information on the wiki is continually updated<br />
## Refined through delivery of 2,3, & 4 below<br />
## How to create a new release of the [[#Deployment Guide|Deployment Guide]] Google Doc from the [[#Deployment Wiki|Deployment Wiki]]<br />
## How to cleanse and restructure the [[#Deployment Wiki|Deployment Wiki]] to aid continued collaboration and maintain consistency with the [[#Deployment Guide|Deployment Guide]]<br />
## How to update the [[#Deployment Toolkit|Deployment Toolkit]] from the updated [[#Deployment Guide|Deployment Guide]]<br />
### To maintain consistency<br />
### To incorporate any new configurations, technologies or services into the cost model from new developments identified in the [[#Deployment Wiki|Deployment Wiki]]<br />
# Improved '''[[#Deployment Toolkit|Deployment Toolkit]]''' (Currently an Excel Spreadsheet; Convert to Google Docs spreadsheet?)<br />
## Achieved by following the process in (1) above<br />
## Contains a parameterized estimating model for building a laptop and infrastructure order suitable for a specific deployment, including financials and the Economic Template<br />
## Purpose is to encapsulate the knowledge of what is required to deploy one laptop per child in a form suitable for determining the infrastructure and budget requirements for a deployment<br />
## Additional content to include:<br />
### Make consistent with updated deployment guide<br />
### Include further examples of templates filled in by various deployment type (large, medium, small etc.)<br />
### Embed Economic template into same toolkit, and update to deliver a tool for showing the split of costs over time, to allow for incremental budgeting, and a tool to allow for budgeting for ongoing maintenance and laptop replacement<br />
### Include links to useful information on topics covering tax, import, replacing parts etc.<br />
# '''[[#Guideline and Process for Customising Deployment Guide|Guideline and Process for Customising Deployment Guide]]''' (Google Doc) for creating a ''Deployment Plan'' for a specific deployment. The official deployment guide contains all guidance for all kinds of deployment to all kinds of environment. Only certain parts of this guide will be relevant to each specific deployment. The official guide also becomes out of date as new lessons from new deployments are captured in the wiki. This process provides guidance on how to create a specific deployment plan by taking just the relevant material out of the official deployment guide and updating this with any new material from the deployment wiki. The purpose of this activity is to simplify things for the deployment team and make sure they have the latest information.<br />
## Guidance document about how to create a customised Deployment Guide that will be appropriate for YOUR deployment.<br />
## This is to ensure that those preparing for a Deployment complete all necessary documentation to procure the necessary laptops and associated infrastructure and complete all necessary documentation for the deployment team to commence deployment<br />
## It will include major deployment milestones, as well as collaboration and knowledge sharing activities<br />
## Outputs of using this process include:<br />
### A budget plan and order sheet created using the Deployment Toolkit<br />
### A Deployment Plan that has been tailored for this deployment by taking relevant parts of the Deployment Guide, Contacts Database and Deployment Wiki<br />
### Updated deployment tracking wiki<br />
# '''[[#Deployment Tracker|Deployment Tracker]]''' (within the ''Deployment Wiki'')<br />
## Who is at what phase (team contact details, location, nature of deployment)<br />
## What open questions they have<br />
## What problems they've solved<br />
## A copy of their deployment plan<br />
# '''[[#Contacts list|Contacts list]]''' (Google Docs Spreadsheet) - people involved in OLPC deployments across the globe, as well as their role (where known)<br />
# '''[[#Report|Report]]''' containing lessons learned, observations & recommendations<br />
## The report will summarise the changes and provide additional observations and recommendations made during the course of the work<br />
## The purpose of the report is to provide OLPC with additional insights into how people are thinking and how to improve communication, knowledge management, and effectiveness of the deployment process<br />
## To enable this activity to be repeated in the future<br />
## To identify additional improvement areas outside the scope of this piece of work<br />
## The report will include:<br />
### Summary of work done to create the deliverables to enable this activity to be repeated at a future date<br />
### Observations on potential issues that should be addressed or opportunities that could be exploited<br />
### Recommendations for how to increase the use and effectiveness of the deployment guide<br />
<br />
== Approach ==<br />
# Technical Research<br />
## Is there a way to generate a document from a wiki? (Alex P)<br />
## Create a wiki editing quick reference<br />
### Technical reference for wiki notation for numbered lists, references etc.<br />
### Organisational standards<br />
#### Place the following text and a link back to this page at the top of any new page that is part of this improvement: ''This page is work in progress as part of the [[Improving the Deployment Toolkit]] activity. Please only edit if you are part of that team otherwise you can contribute ideas or review comments via the [[{{TALKPAGENAME}}|discussion page]]''<br />
### Collect references to other relevant pages like the [[Style guide]] and ensure consistency<br />
#### Prefix each page of the [[Deployment Guide]] with ''Deployment Guide/''<br />
#### Capitalise words in short phrases for page and section titles<br />
## Is there a way to automatically count the number of pages below a given page like the [[Deployment Guide]]<br />
# Create a plan<br />
## Assess the size of the guide (number of pages linked from the [[Deployment Guide]])<br />
## Identify key sections<br />
## Identify candidate pages for merging or differentiating (e.g. similar title/content)<br />
## Prioritise update activity<br />
## Allocate update tasks<br />
# Identify people to contribute or review<br />
## Identify people to interview<br />
## Identify members of the [[Wiki gang]] who could advise or review<br />
## Use the wiki history pages to:<br />
### Identify frequently active users<br />
### Identify main authors/experts for key pages<br />
# Setup interviews and meetings for status updates and reviews<br />
# Create a copy of the [[Deployment Guide]] page as a [[Draft Deployment Guide]]<br />
# Update the [[Draft Deployment Guide]]<br />
## Preparation<br />
### Check sections with the same title as new sections you want to add don't already exist and if they do make a decision about whether to edit that live page directly or to take a copy and publish it by copying it back later as we do with the main [[Deployment Guide]] page<br />
### Review material in the [[ClassActs/Resources]] section<br />
### Identify existing material that could be referred to by or moved into the new sections<br />
## Add new sections<br />
### [[How to align with national & regional education policy]] (including sponsorship)<br />
### [[Planning scenarios decision tree]] (use Policy Questions word doc as basis)<br />
#### Funding<br />
#### Policy<br />
#### NGO<br />
#### Government<br />
#### Philanthropist<br />
#### Charity<br />
### [[Team setup and deployment management]]<br />
### [[Links to related documents]] such as training guides<br />
### [[Templates]], e.g. training & deployment timetables<br />
### [[Lessons learned]], e.g. Don’t rely on solar power, ...<br />
### [[A teachers perspective]] / how to facilitate learning with the XO<br />
### [[How to edit this wiki]]<br />
## Follow all links from the [[Draft Deployment Guide]] according to priorities<br />
### Combine or delete pages where appropriate, updating any references to these at the same time<br />
### Review and update pages to improve clarity, navigation and accuracy<br />
### Split pages into multiple sections or pages where appropriate<br />
### Add cross references between pages where appropriate<br />
## Review structure and flow of the [[Draft Deployment Guide]]<br />
## Add additional navigation / cross references between sections as required<br />
## Add clearer reference to the official Deployment Guide, Deployment Toolkit and Contacts List<br />
## Go through the google doc and add missing material back into the [[Working Deployment Wiki]]<br />
## Use the discussion tab for each wiki page for sharing ideas and review comments<br />
# Review [[Draft Deployment Guide]] with OLPC<br />
# Create google doc from [[Draft Deployment Guide]]<br />
# Review google doc with OLPC<br />
# Agree publishing date and comms with OLPC<br />
# Copy the [[Draft Deployment Guide]] back into the [[Deployment Guide]]<br />
# Announce new [[Deployment Guide]] and google doc<br />
# Use this section as a basis for creating the [[Process for Releasing New Deployment Guide]]<br />
# Create a [[Deployment Toolkit]] (wiki page and excel spreadsheet)<br />
## Obtain latest versions of spreadsheets<br />
## Combine the ''OLPC Deployment Workbook'' Excel spreadsheet (country budget planner) with the ''Economic Template'' Excel spreadsheet<br />
## Simplify<br />
## Improve usability<br />
## Update assumptions if required (contact authors)<br />
## Align the [[Deployment Toolkit]] with the [[Deployment Guide]]<br />
### For each line item in the spreadsheet there should be a corresponding section in the wiki<br />
### For each relevant section in the wiki, the spreadsheet should allow budget planning for it, e.g.<br />
#### Power generation solutions<br />
#### Teacher training options<br />
#### Project support resourcing options<br />
# Create [[Guidelines and Process for Customising the Deployment Guide]]<br />
# Create [[Deployment Tracker]]<br />
## Leverage existing resources such as the google map showing deployments<br />
<br />
== Plan ==<br />
<br />
== Core Team ==<br />
The core team are managing the project described in this page, allocation of tasks, and communication with OLPC and other third party contacts.<br />
<br />
The core team consists of the following people:<br />
# Pippa Thomas<br />
# [[User:Mark.Burnett|Mark Burnett]]<br />
# [[User:Alexandros.Papadopoulos|Alexandros Papadopoulos]]<br />
<br />
== Extended Team ==<br />
The extended team consists of the following people:<br />
# Toyosi Ogedengbe<br />
# Sergio Coury<br />
<br />
This list is maintained by the [[#Core Team|Core Team]]<br />
<br />
== Task Management ==<br />
=== Ideas ===<br />
As Ideas emerge and are discussed they will be added into the deliverables below<br />
<br />
# Identify and document the major [[#Processes|Processes]] in simple to follow steps<br />
# Get a non consultant, non technical author to review our deliverables from a readability perspective<br />
## Early on to help ensure write in simple non consultant English<br />
## Near the end to review the final deliverables<br />
# Include an orientation and induction process<br />
# Find other initiatives similar to OLPC that we can learn from<br />
# Find other kinds of deployment guide that we can learn from<br />
# Who else can we learn from?<br />
# Include a map of the various different resources / web sites and their purposes - list forming under the [[#Resources|Resources]] section<br />
# There seem to be a lot of people enthusiastically sharing their experiences via all sorts of different wikis, and the way some of the entries are written is more like a personal blog - i.e. a stream of consciousness of their lessons learned and experiences. This is no doubt effortless for the individuals by comparison to attempting to edit a wiki by finding the right place to update information. So something to think about is how can we increase the ease of updating the wiki or how can we more effectively harvest the personal experiences without having a team to do it<br />
# Consider how children can pass on knowledge from one generation to the next, so as younger children come into a school and are given a laptop they learn from older children and the older children are challenged to put their knowledge into practice through the questions of the younger children<br />
# Create a facebook page for children with an XO so they can communicate and share ideas with each other<br />
<br />
=== Unallocated tasks ===<br />
This section contains a list of tasks identified by the extended team or collated from discussion pages creates as part of this project. Tasks will be moved from this section into the [[Allocated tasks]] section by the core team as they are allocated.<br />
# Identify duplicate pages and recommend approach to consolidate / delete<br />
=== Allocated tasks ===<br />
This section contains tasks allocated to specific members of the extended team by the core team.<br />
==== [[User:PippaThomas]] ====<br />
# Create a single page FAQ describing what OLPC do and what we are doing on this project<br />
<br />
=== Tasks pending review ===<br />
=== Completed Tasks ===<br />
== Processes ==<br />
<br />
=== Guideline and Process for Customising Deployment Guide ===<br />
# Update the [[#Deployment Tracking Wiki|Deployment Tracking Wiki]] to indicate you are preparing a deployment<br />
# Follow the [[#Readiness Assessment Process|Readiness Assessment Process]] to check you have everything you need to start a deployment and understand the main areas of challenge for your particular location<br />
# Make a copy of the [[#Deployment Guide|Deployment Guide]] and call it "[[#Location Deployment Plan|Location Deployment Plan]]" (replacing the word "Location" with the name of the location you are deploying to<br />
# Remove sections from the document that do not apply to you<br />
# Update the ''Team'' section with roles and responsibilities and contact details for your team<br />
# Update the ''Support Team'' section with roles, areas of expertise and contact details of any people in other teams that have agreed to support your team<br />
# Follow the [[#Deployment Plan|Deployment Plan]]<br />
<br />
=== Solve Problem Process ===<br />
Part of the [[#Deployment Process|Deployment Process]]<br />
# Check to see if the [[#Deployment Guide|Deployment Guide]] says how to solve the problem<br />
# Check to see if the [[#Deployment Wiki|Deployment Wiki]] says how to solve the problem<br />
# Check to see if there are any [[#Open Question|Open Question]]s in the [[#Deployment Wiki|Deployment Wiki]] that are similar to yours; If there are, contact the teams that created those questions to see if they have made progress and work together to solve the problem<br />
# If no solutions can be found, create an [[#Open Question|Open Question]] page so that others can see you are trying to solve this problem<br />
# Check the [[#Deployment Tracker|Deployment Tracker]] to see what other teams are currently working who are at the same or later stage in the [[#Deployment Process|Deployment Process]] as you and consult with them<br />
# Update the [[#Open Question|Open Question]] page when you find a solution<br />
<br />
=== Readiness Assessment Process ===<br />
This process helps you determine whether you are ready to start a deployment by providing a checklist. It also includes a questionnaire to help you determine the major areas of challenge you may have to point you in the right direction for how to overcome these challenges, such as <br />
* by providing links to specific collaboration areas in the [[#Deployment Wiki|Deployment Wiki]] that may be more up to date than the guide as it is used by those involved in deployments right now to collaborate and share ideas<br />
* by pointing you at the most relevant areas in the [[#Dealing with exceptions|Dealing with exceptions]] section of the ''Deployment Guide''<br />
<br />
=== Process for releasing new Deployment Guide ===<br />
<br />
Assumptions:<br />
* The ''Deployment Guide'' will always be available from the same URL<br />
* A draft of the new release will be created in a separate document whilst it is being worked on<br />
* Once the new release is ready for publication, the google doc will be updated and an announcement made on the ''Deployment Wiki''<br />
<br />
Process:<br />
# Identify volunteers from currently active deployment teams to support the process by providing up to date experience and review of changes to the wiki and document<br />
# Create a new page in the [[#Deployment Wiki|Deployment Wiki]] for collaborating on producing the new version of the ''Deployment Guide''<br />
# Update the front page of the wiki to say that a new version of the deployment guide is currently being produced, the expected date by which it will be available, and provide a link to the collaboration page inviting input<br />
# Produce a draft of the new ''Deployment Guide'' by copying the current release into a new google doc<br />
# Review changes made to the [http://wiki.laptop.org wiki.laptop.org Deployment Wiki] since the last release of the ''Deployment Guide'' was created<br />
## Consolidate similar entries in the wiki and add these to the draft deployment guide or replace sections if these entries supercede them and also remove the corresponding superceded sections of the wiki<br />
## Review the [[#Open Question|Open Question]]s section of the [[#Deployment Wiki|Deployment Wiki]]<br />
### Answer the questions if possible, consulting the deployment teams who raised them in the process to validate the answers<br />
### Update the Open Question page and incorporate the answer into the draft deployment guide<br />
# Send the draft to the volunteers and members of the core team who have agreed to review it<br />
# Apply review comments<br />
# Issue the new document by publishing a message on the ''Deployment Wiki''<br />
<br />
== Documents ==<br />
<br />
=== Deployment Guide ===<br />
'''Notes:'''<br />
As well as containing a refinement of the current ''Deployment Guide'', this revised document will also contain the following:<br />
# A process for requesting improvements to the guide<br />
# A process for requesting help when the guide does not contain the expected information (the [[#Solve Problem Process|Solve Problem Process]])<br />
# A FAQ (Frequently Asked Questions) section<br />
# The Anatomy of an OLPC deployment<br />
## A high level overview of the deployment process<br />
## The typical roles and responsibilities of deployment team members<br />
## A list and description of all the typical parts (e.g. laptops, power, connectivity) and associated deployment activities<br />
## A list of alternative parts, pros and cons of each and when you would usually choose one over another (e.g. forms of power)<br />
# Glossary of terms<br />
# A [[#Dealing with exceptions|Dealing with exceptions]] section listing the circumstances that are not dealt with by the standard deployment process either because they are problem situations or exceptional or rare circumstances that would otherwise clutter the process and make it difficult to follow<br />
<br />
'''Sections:'''<br />
==== Dealing with Exceptions ====<br />
<br />
=== Contacts List ===<br />
Containing the following details for each contact:<br />
* Name<br />
* Role<br />
* Location<br />
* Areas of expertise<br />
* Email<br />
* Mobile<br />
* Land line<br />
* Address<br />
* Deployment experience (which locations have they been involved in deploying)<br />
<br />
=== Report ===<br />
Containing the following sections:<br />
# Summary of work done to create the deliverables to enable this activity to be repeated at a future date<br />
# Observations on potential issues that should be addressed or opportunities that could be exploited<br />
# Recommendations for how to increase the use and effectiveness of the deployment guide<br />
<br />
<br />
=== Location Deployment Plan ===<br />
The ''Location Deployment Plan'' provides a plan for a specific deployment.<br />
It is created by the [[#Guideline and Process for Customising Deployment Guide|Guideline and Process for Customising Deployment Guide]] from the [[#Deployment Guide|Deployment Guide]].<br />
<br />
== Templates for ''Deployment Wiki'' Pages ==<br />
<br />
=== Open Question ===<br />
<br />
Contents<br />
# Question title<br />
# Description of the problem<br />
# Solutions considered and discarded and why<br />
# Ideas for how to solve the problem that are currently being explored<br />
# Contact details for the team</div>Alexandros.Papadopouloshttp://wiki.laptop.org/mediawiki/index.php?title=Improving_the_Deployment_Toolkit&diff=244585Improving the Deployment Toolkit2010-08-27T08:20:40Z<p>Alexandros.Papadopoulos: /* Extended Team */</p>
<hr />
<div>A place to gather ideas about creating a process to perpetually improve the [[Deployment Guide]] and deployment toolkit.<br />
<br />
If you are not a member of the team that created this page please add your comments to the [[{{TALKPAGENAME}}|Discussion page]].<br />
<br />
{{draft}}<br />
<br />
== Principles ==<br />
# Improvements will be based on real experiences<br />
# Improvements in documents and process will not depend on individuals but will stand alone and naturally support a changing OLPC team<br />
# Documents should be self explanatory (documents should be as easy to pick up and use as possible with no prior experience or training)<br />
# Improvements will be made in a sustainable way (the process by which the improvements are achieved will be documented so as to enable repeated improvement)<br />
<br />
<br />
== Challenges ==<br />
# The people involved in each deployment may be different and have never completed a deployment before<br />
# The technology being deployed evolves with time, ahead of the changes to the deployment guide<br />
# Each location to which laptops are deployed will have different challenges<br />
<br />
<br />
== Resources ==<br />
This section contains links to other sites that may contain useful information<br />
# What can we learn from Sugar Labs, e.g. via their [http://wiki.sugarlabs.org/go/Deployment_Team/Resources wiki]<br />
# "Deployment Meetings"<br />
## [http://wiki.laptop.org/go/Deployment_meetings This wiki's deployment meetings page]<br />
## [http://pipka.org/blog/2009/01/18/olpc-deployment-meetups/ Pipka deployment meeting page]<br />
# [http://wiki.laptop.org/go/OLPC_UK OLPC UK Community Effort]<br />
# [http://www.olpcnews.com/ OLPC News (separate website)]<br />
# [http://www.olpcfriends.org/ OLPC Friends]<br />
<br />
== Deliverables ==<br />
This section shows the deliverables as described in the statement of work for this improvement activity. Each deliverable contains a link to the section in this wiki where the planning for that deliverable can be conducted<br />
# Improved '''[[#Deployment Wiki|Deployment Wiki]]''' ([http://wiki.laptop.org wiki.laptop.org])<br />
## Achieved by following the process in (1) above<br />
## Clearer structure<br />
## Clearer reference to the official Deployment Guide, Deployment Toolkit and Contacts List<br />
## Links to all useful information for Deployments (e.g. sample training guides)<br />
## Additional content to include:<br />
### How to address national & regional education policy (including sponsorship) <br />
### Funding scenarios decision tree<br />
### NGO v Gov v Philanthropist v Charity<br />
### Team set up and deployment management<br />
### Links to related documents such as training guides<br />
### Templates, e.g. training & deployment timetables<br />
### Lessons learned, e.g. Don’t rely on solar power, ...<br />
### A teachers perspective / how to facilitate learning with the XO<br />
# Improved '''[[#Deployment Guide|Deployment Guide]]''' (Google Docs "official release" version)<br />
## Achieved by following the process in (1) above<br />
## Official ‘release’ of the improved Deployment Wiki suitable for printing. The purpose of this is to provide a reference document containing a cleansed and structured form of the content of the wiki.<br />
# '''[[#Process for releasing new Deployment Guide|Process for releasing new Deployment Guide]]''' (Google Doc) - to allow OLPC to continue updating new releases of the ''Deployment Guide'' from the wiki, as the information on the wiki is continually updated<br />
## Refined through delivery of 2,3, & 4 below<br />
## How to create a new release of the [[#Deployment Guide|Deployment Guide]] Google Doc from the [[#Deployment Wiki|Deployment Wiki]]<br />
## How to cleanse and restructure the [[#Deployment Wiki|Deployment Wiki]] to aid continued collaboration and maintain consistency with the [[#Deployment Guide|Deployment Guide]]<br />
## How to update the [[#Deployment Toolkit|Deployment Toolkit]] from the updated [[#Deployment Guide|Deployment Guide]]<br />
### To maintain consistency<br />
### To incorporate any new configurations, technologies or services into the cost model from new developments identified in the [[#Deployment Wiki|Deployment Wiki]]<br />
# Improved '''[[#Deployment Toolkit|Deployment Toolkit]]''' (Currently an Excel Spreadsheet; Convert to Google Docs spreadsheet?)<br />
## Achieved by following the process in (1) above<br />
## Contains a parameterized estimating model for building a laptop and infrastructure order suitable for a specific deployment, including financials and the Economic Template<br />
## Purpose is to encapsulate the knowledge of what is required to deploy one laptop per child in a form suitable for determining the infrastructure and budget requirements for a deployment<br />
## Additional content to include:<br />
### Make consistent with updated deployment guide<br />
### Include further examples of templates filled in by various deployment type (large, medium, small etc.)<br />
### Embed Economic template into same toolkit, and update to deliver a tool for showing the split of costs over time, to allow for incremental budgeting, and a tool to allow for budgeting for ongoing maintenance and laptop replacement<br />
### Include links to useful information on topics covering tax, import, replacing parts etc.<br />
# '''[[#Guideline and Process for Customising Deployment Guide|Guideline and Process for Customising Deployment Guide]]''' (Google Doc) for creating a ''Deployment Plan'' for a specific deployment. The official deployment guide contains all guidance for all kinds of deployment to all kinds of environment. Only certain parts of this guide will be relevant to each specific deployment. The official guide also becomes out of date as new lessons from new deployments are captured in the wiki. This process provides guidance on how to create a specific deployment plan by taking just the relevant material out of the official deployment guide and updating this with any new material from the deployment wiki. The purpose of this activity is to simplify things for the deployment team and make sure they have the latest information.<br />
## Guidance document about how to create a customised Deployment Guide that will be appropriate for YOUR deployment.<br />
## This is to ensure that those preparing for a Deployment complete all necessary documentation to procure the necessary laptops and associated infrastructure and complete all necessary documentation for the deployment team to commence deployment<br />
## It will include major deployment milestones, as well as collaboration and knowledge sharing activities<br />
## Outputs of using this process include:<br />
### A budget plan and order sheet created using the Deployment Toolkit<br />
### A Deployment Plan that has been tailored for this deployment by taking relevant parts of the Deployment Guide, Contacts Database and Deployment Wiki<br />
### Updated deployment tracking wiki<br />
# '''[[#Deployment Tracker|Deployment Tracker]]''' (within the ''Deployment Wiki'')<br />
## Who is at what phase (team contact details, location, nature of deployment)<br />
## What open questions they have<br />
## What problems they've solved<br />
## A copy of their deployment plan<br />
# '''[[#Contacts list|Contacts list]]''' (Google Docs Spreadsheet) - people involved in OLPC deployments across the globe, as well as their role (where known)<br />
# '''[[#Report|Report]]''' containing lessons learned, observations & recommendations<br />
## The report will summarise the changes and provide additional observations and recommendations made during the course of the work<br />
## The purpose of the report is to provide OLPC with additional insights into how people are thinking and how to improve communication, knowledge management, and effectiveness of the deployment process<br />
## To enable this activity to be repeated in the future<br />
## To identify additional improvement areas outside the scope of this piece of work<br />
## The report will include:<br />
### Summary of work done to create the deliverables to enable this activity to be repeated at a future date<br />
### Observations on potential issues that should be addressed or opportunities that could be exploited<br />
### Recommendations for how to increase the use and effectiveness of the deployment guide<br />
<br />
== Approach ==<br />
# Technical Research<br />
## Is there a way to generate a document from a wiki? (Alex P)<br />
## Create a wiki editing quick reference<br />
### Technical reference for wiki notation for numbered lists, references etc.<br />
### Organisational standards<br />
#### Place the following text and a link back to this page at the top of any new page that is part of this improvement: ''This page is work in progress as part of the [[Improving the Deployment Toolkit]] activity. Please only edit if you are part of that team otherwise you can contribute ideas or review comments via the [[{{TALKPAGENAME}}|discussion page]]''<br />
### Collect references to other relevant pages like the [[Style guide]] and ensure consistency<br />
#### Prefix each page of the [[Deployment Guide]] with ''Deployment Guide/''<br />
#### Capitalise words in short phrases for page and section titles<br />
## Is there a way to automatically count the number of pages below a given page like the [[Deployment Guide]]<br />
# Create a plan<br />
## Assess the size of the guide (number of pages linked from the [[Deployment Guide]])<br />
## Identify key sections<br />
## Identify candidate pages for merging or differentiating (e.g. similar title/content)<br />
## Prioritise update activity<br />
## Allocate update tasks<br />
# Identify people to contribute or review<br />
## Identify people to interview<br />
## Identify members of the [[Wiki gang]] who could advise or review<br />
## Use the wiki history pages to:<br />
### Identify frequently active users<br />
### Identify main authors/experts for key pages<br />
# Setup interviews and meetings for status updates and reviews<br />
# Create a copy of the [[Deployment Guide]] page as a [[Draft Deployment Guide]]<br />
# Update the [[Draft Deployment Guide]]<br />
## Preparation<br />
### Check sections with the same title as new sections you want to add don't already exist and if they do make a decision about whether to edit that live page directly or to take a copy and publish it by copying it back later as we do with the main [[Deployment Guide]] page<br />
### Review material in the [[ClassActs/Resources]] section<br />
### Identify existing material that could be referred to by or moved into the new sections<br />
## Add new sections<br />
### [[How to align with national & regional education policy]] (including sponsorship)<br />
### [[Planning scenarios decision tree]] (use Policy Questions word doc as basis)<br />
#### Funding<br />
#### Policy<br />
#### NGO<br />
#### Government<br />
#### Philanthropist<br />
#### Charity<br />
### [[Team setup and deployment management]]<br />
### [[Links to related documents]] such as training guides<br />
### [[Templates]], e.g. training & deployment timetables<br />
### [[Lessons learned]], e.g. Don’t rely on solar power, ...<br />
### [[A teachers perspective]] / how to facilitate learning with the XO<br />
### [[How to edit this wiki]]<br />
## Follow all links from the [[Draft Deployment Guide]] according to priorities<br />
### Combine or delete pages where appropriate, updating any references to these at the same time<br />
### Review and update pages to improve clarity, navigation and accuracy<br />
### Split pages into multiple sections or pages where appropriate<br />
### Add cross references between pages where appropriate<br />
## Review structure and flow of the [[Draft Deployment Guide]]<br />
## Add additional navigation / cross references between sections as required<br />
## Add clearer reference to the official Deployment Guide, Deployment Toolkit and Contacts List<br />
## Go through the google doc and add missing material back into the [[Working Deployment Wiki]]<br />
## Use the discussion tab for each wiki page for sharing ideas and review comments<br />
# Review [[Draft Deployment Guide]] with OLPC<br />
# Create google doc from [[Draft Deployment Guide]]<br />
# Review google doc with OLPC<br />
# Agree publishing date and comms with OLPC<br />
# Copy the [[Draft Deployment Guide]] back into the [[Deployment Guide]]<br />
# Announce new [[Deployment Guide]] and google doc<br />
# Use this section as a basis for creating the [[Process for Releasing New Deployment Guide]]<br />
# Create a [[Deployment Toolkit]] (wiki page and excel spreadsheet)<br />
## Obtain latest versions of spreadsheets<br />
## Combine the ''OLPC Deployment Workbook'' Excel spreadsheet (country budget planner) with the ''Economic Template'' Excel spreadsheet<br />
## Simplify<br />
## Improve usability<br />
## Update assumptions if required (contact authors)<br />
## Align the [[Deployment Toolkit]] with the [[Deployment Guide]]<br />
### For each line item in the spreadsheet there should be a corresponding section in the wiki<br />
### For each relevant section in the wiki, the spreadsheet should allow budget planning for it, e.g.<br />
#### Power generation solutions<br />
#### Teacher training options<br />
#### Project support resourcing options<br />
# Create [[Guidelines and Process for Customising the Deployment Guide]]<br />
# Create [[Deployment Tracker]]<br />
## Leverage existing resources such as the google map showing deployments<br />
<br />
== Plan ==<br />
<br />
== Core Team ==<br />
The core team are managing the project described in this page, allocation of tasks, and communication with OLPC and other third party contacts.<br />
<br />
The core team consists of the following people:<br />
# Pippa Thomas<br />
# [[User:Mark.Burnett|Mark Burnett]]<br />
# Alexandros Papadopoulos<br />
== Extended Team ==<br />
The extended team consists of the following people:<br />
# Toyosi Ogedengbe<br />
# Sergio Coury<br />
<br />
This list is maintained by the [[#Core Team|Core Team]]<br />
<br />
== Task Management ==<br />
=== Ideas ===<br />
As Ideas emerge and are discussed they will be added into the deliverables below<br />
<br />
# Identify and document the major [[#Processes|Processes]] in simple to follow steps<br />
# Get a non consultant, non technical author to review our deliverables from a readability perspective<br />
## Early on to help ensure write in simple non consultant English<br />
## Near the end to review the final deliverables<br />
# Include an orientation and induction process<br />
# Find other initiatives similar to OLPC that we can learn from<br />
# Find other kinds of deployment guide that we can learn from<br />
# Who else can we learn from?<br />
# Include a map of the various different resources / web sites and their purposes - list forming under the [[#Resources|Resources]] section<br />
# There seem to be a lot of people enthusiastically sharing their experiences via all sorts of different wikis, and the way some of the entries are written is more like a personal blog - i.e. a stream of consciousness of their lessons learned and experiences. This is no doubt effortless for the individuals by comparison to attempting to edit a wiki by finding the right place to update information. So something to think about is how can we increase the ease of updating the wiki or how can we more effectively harvest the personal experiences without having a team to do it<br />
# Consider how children can pass on knowledge from one generation to the next, so as younger children come into a school and are given a laptop they learn from older children and the older children are challenged to put their knowledge into practice through the questions of the younger children<br />
# Create a facebook page for children with an XO so they can communicate and share ideas with each other<br />
<br />
=== Unallocated tasks ===<br />
This section contains a list of tasks identified by the extended team or collated from discussion pages creates as part of this project. Tasks will be moved from this section into the [[Allocated tasks]] section by the core team as they are allocated.<br />
# Identify duplicate pages and recommend approach to consolidate / delete<br />
=== Allocated tasks ===<br />
This section contains tasks allocated to specific members of the extended team by the core team.<br />
==== [[User:PippaThomas]] ====<br />
# Create a single page FAQ describing what OLPC do and what we are doing on this project<br />
<br />
=== Tasks pending review ===<br />
=== Completed Tasks ===<br />
== Processes ==<br />
<br />
=== Guideline and Process for Customising Deployment Guide ===<br />
# Update the [[#Deployment Tracking Wiki|Deployment Tracking Wiki]] to indicate you are preparing a deployment<br />
# Follow the [[#Readiness Assessment Process|Readiness Assessment Process]] to check you have everything you need to start a deployment and understand the main areas of challenge for your particular location<br />
# Make a copy of the [[#Deployment Guide|Deployment Guide]] and call it "[[#Location Deployment Plan|Location Deployment Plan]]" (replacing the word "Location" with the name of the location you are deploying to<br />
# Remove sections from the document that do not apply to you<br />
# Update the ''Team'' section with roles and responsibilities and contact details for your team<br />
# Update the ''Support Team'' section with roles, areas of expertise and contact details of any people in other teams that have agreed to support your team<br />
# Follow the [[#Deployment Plan|Deployment Plan]]<br />
<br />
=== Solve Problem Process ===<br />
Part of the [[#Deployment Process|Deployment Process]]<br />
# Check to see if the [[#Deployment Guide|Deployment Guide]] says how to solve the problem<br />
# Check to see if the [[#Deployment Wiki|Deployment Wiki]] says how to solve the problem<br />
# Check to see if there are any [[#Open Question|Open Question]]s in the [[#Deployment Wiki|Deployment Wiki]] that are similar to yours; If there are, contact the teams that created those questions to see if they have made progress and work together to solve the problem<br />
# If no solutions can be found, create an [[#Open Question|Open Question]] page so that others can see you are trying to solve this problem<br />
# Check the [[#Deployment Tracker|Deployment Tracker]] to see what other teams are currently working who are at the same or later stage in the [[#Deployment Process|Deployment Process]] as you and consult with them<br />
# Update the [[#Open Question|Open Question]] page when you find a solution<br />
<br />
=== Readiness Assessment Process ===<br />
This process helps you determine whether you are ready to start a deployment by providing a checklist. It also includes a questionnaire to help you determine the major areas of challenge you may have to point you in the right direction for how to overcome these challenges, such as <br />
* by providing links to specific collaboration areas in the [[#Deployment Wiki|Deployment Wiki]] that may be more up to date than the guide as it is used by those involved in deployments right now to collaborate and share ideas<br />
* by pointing you at the most relevant areas in the [[#Dealing with exceptions|Dealing with exceptions]] section of the ''Deployment Guide''<br />
<br />
=== Process for releasing new Deployment Guide ===<br />
<br />
Assumptions:<br />
* The ''Deployment Guide'' will always be available from the same URL<br />
* A draft of the new release will be created in a separate document whilst it is being worked on<br />
* Once the new release is ready for publication, the google doc will be updated and an announcement made on the ''Deployment Wiki''<br />
<br />
Process:<br />
# Identify volunteers from currently active deployment teams to support the process by providing up to date experience and review of changes to the wiki and document<br />
# Create a new page in the [[#Deployment Wiki|Deployment Wiki]] for collaborating on producing the new version of the ''Deployment Guide''<br />
# Update the front page of the wiki to say that a new version of the deployment guide is currently being produced, the expected date by which it will be available, and provide a link to the collaboration page inviting input<br />
# Produce a draft of the new ''Deployment Guide'' by copying the current release into a new google doc<br />
# Review changes made to the [http://wiki.laptop.org wiki.laptop.org Deployment Wiki] since the last release of the ''Deployment Guide'' was created<br />
## Consolidate similar entries in the wiki and add these to the draft deployment guide or replace sections if these entries supercede them and also remove the corresponding superceded sections of the wiki<br />
## Review the [[#Open Question|Open Question]]s section of the [[#Deployment Wiki|Deployment Wiki]]<br />
### Answer the questions if possible, consulting the deployment teams who raised them in the process to validate the answers<br />
### Update the Open Question page and incorporate the answer into the draft deployment guide<br />
# Send the draft to the volunteers and members of the core team who have agreed to review it<br />
# Apply review comments<br />
# Issue the new document by publishing a message on the ''Deployment Wiki''<br />
<br />
== Documents ==<br />
<br />
=== Deployment Guide ===<br />
'''Notes:'''<br />
As well as containing a refinement of the current ''Deployment Guide'', this revised document will also contain the following:<br />
# A process for requesting improvements to the guide<br />
# A process for requesting help when the guide does not contain the expected information (the [[#Solve Problem Process|Solve Problem Process]])<br />
# A FAQ (Frequently Asked Questions) section<br />
# The Anatomy of an OLPC deployment<br />
## A high level overview of the deployment process<br />
## The typical roles and responsibilities of deployment team members<br />
## A list and description of all the typical parts (e.g. laptops, power, connectivity) and associated deployment activities<br />
## A list of alternative parts, pros and cons of each and when you would usually choose one over another (e.g. forms of power)<br />
# Glossary of terms<br />
# A [[#Dealing with exceptions|Dealing with exceptions]] section listing the circumstances that are not dealt with by the standard deployment process either because they are problem situations or exceptional or rare circumstances that would otherwise clutter the process and make it difficult to follow<br />
<br />
'''Sections:'''<br />
==== Dealing with Exceptions ====<br />
<br />
=== Contacts List ===<br />
Containing the following details for each contact:<br />
* Name<br />
* Role<br />
* Location<br />
* Areas of expertise<br />
* Email<br />
* Mobile<br />
* Land line<br />
* Address<br />
* Deployment experience (which locations have they been involved in deploying)<br />
<br />
=== Report ===<br />
Containing the following sections:<br />
# Summary of work done to create the deliverables to enable this activity to be repeated at a future date<br />
# Observations on potential issues that should be addressed or opportunities that could be exploited<br />
# Recommendations for how to increase the use and effectiveness of the deployment guide<br />
<br />
<br />
=== Location Deployment Plan ===<br />
The ''Location Deployment Plan'' provides a plan for a specific deployment.<br />
It is created by the [[#Guideline and Process for Customising Deployment Guide|Guideline and Process for Customising Deployment Guide]] from the [[#Deployment Guide|Deployment Guide]].<br />
<br />
== Templates for ''Deployment Wiki'' Pages ==<br />
<br />
=== Open Question ===<br />
<br />
Contents<br />
# Question title<br />
# Description of the problem<br />
# Solutions considered and discarded and why<br />
# Ideas for how to solve the problem that are currently being explored<br />
# Contact details for the team</div>Alexandros.Papadopouloshttp://wiki.laptop.org/mediawiki/index.php?title=Talk:Improving_the_Deployment_Toolkit&diff=244030Talk:Improving the Deployment Toolkit2010-08-16T15:08:44Z<p>Alexandros.Papadopoulos: Created page with 'OLPC's mission aligns very well with the [http://www.un.org/millenniumgoals/ UN's Millennium Development Goals] (the 2nd goal is "Universal Education") How can we use this to ge…'</p>
<hr />
<div>OLPC's mission aligns very well with the [http://www.un.org/millenniumgoals/ UN's Millennium Development Goals] (the 2nd goal is "Universal Education")<br />
<br />
How can we use this to get more exposure & more people on board?<br />
<br />
[[User:Alexandros.Papadopoulos|Alexandros.Papadopoulos]] 15:08, 16 August 2010 (UTC)</div>Alexandros.Papadopouloshttp://wiki.laptop.org/mediawiki/index.php?title=Keyboard_field_repairs&diff=242388Keyboard field repairs2010-08-02T12:33:55Z<p>Alexandros.Papadopoulos: /* Repair Without Keyboard Removal */ Added link to keyboard removal page</p>
<hr />
<div>{{TOCright}}<br />
<br />
While OLPC recommends replacing ripped keyboards, that may not always be possible or, may be too costly if several laptops are involved. This simple fix uses a relatively non-toxic silicone sealer that has no harmful fumes. The repair could be, and has been, done safely by children.<br />
<br />
== Materials ==<br />
<br />
[[image:A1-Supplies.jpg|thumb|center]]<br />
<br />
<br />
*Clear Silicone tub and tile sealant (goes on white, dries clear). A 6 oz tube costs less than $3 at most hardware stores and is enough to do dozens of laptops.<br />
<br />
*Toothpicks for applying the sealer<br />
<br />
*Cotton swabs, tissues and water for cleanup<br />
<br />
*Something to protect your table top if doing the repair with the keyboard removed from the laptop (aluminum foil is shown here).<br />
<br />
If only a few keys are involved, you may wish to do the repair with the keyboard in place. Follow the second set of directions below to do the repair without removing the keyboard.<br />
<br />
If the damage is more extensive, you will probably want to remove the keyboard following these [[Disassembly|disassembly instructions]].<br />
<br />
==Repair With Keyboard Removal==<br />
<br />
After removing the keyboard, gently lift off the green silicone keypad, being careful to not tear additional keys. Lay it on your table protector.<br />
<br />
Using one toothpick to hold the key in place, gently apply a small amount of silicone to the torn sides of the key with a second toothpick. <br />
<br />
[[image:A2-Apply Silicone.jpg|thumb|center]]<br />
<br />
<br />
Use a damp (not soaking wet) cotton swab to remove the excess silicone sealer. <br />
<br />
[[Image:A3-Remove Excess.jpg|thumb|center]]<br />
<br />
<br />
More cleanup may be needed. <br />
<br />
[[Image:A4-Needs More Cleanup.jpg|thumb|center]]<br />
<br />
<br />
Use a damp tissue for a final touchup. In this photo, the F, G, and H keys and the right half of the space bar were repaired previously and have already dried. <br />
<br />
[[Image:A5-Touch Up With Tissue.jpg|thumb|center]]<br />
<br />
<br />
Allow the silicone to dry overnight before re-assembling the laptop according to the directions on the wiki.<br />
<br />
==Repair Without Keyboard Removal==<br />
<br />
While this may seem easier than removing the keyboard, you must work very carefully to not allow silicone to get under the green silicone keypad.<br />
<br />
A key that had been completely torn off was re-fitted in this repair. <br />
<br />
[[Image:B1-"R" Key ripped completely off.jpg|thumb|center]]<br />
<br />
<br />
Carefully fit the key back into its place in the keyboard. <br />
<br />
[[Image:B2-Put key back in place.jpg|thumb|center]]<br />
<br />
Apply silicone to one edge of the key and carefully clean it. If you try to do the entire key at once, it will be difficult to keep it in place while working. <br />
<br />
[[Image:B3-Apply silcone to one side.jpg|thumb|center]]<br />
<br />
Allow the first side to dry overnight. <br />
<br />
[[Image:B4-Wait for first side to dry.jpg|thumb|center]]<br />
<br />
Holding the key in place with one toothpick, carefully apply silicone to the remaining three sides, being careful not to get it under the key. <br />
<br />
[[Image:B5-Apply Silicone To Other 3 Sides.jpg|thumb|center]]<br />
<br />
Clean up with a toothpick. To avoid having sealer run under the key, it is probably best not to use the wet cotton swab or wet tissue here. <br />
<br />
[[Image:B6-Clean With Toothpick.jpg|thumb|center]]<br />
<br />
Let they keyboard dry overnight. Note the repair isn't as clean as the one with the keyboard removed. That is because we did not use the water in the cleanup. <br />
<br />
[[Image:B7-Silicone Has Dried.jpg|thumb|center]]<br />
<br />
Test the results. This one worked. <br />
<br />
[[Image:B8-It Works!.jpg|thumb|center]]<br />
<br />
If the key does not work, you may wish to [http://wiki.laptop.org/go/Disassembly_bottom#Removing_the_keyboard remove the keyboard] according to the dis-assembly instructions, clean off any excess sealer, and follow the instructions above.<br />
<br />
[[Category:Repair]]</div>Alexandros.Papadopouloshttp://wiki.laptop.org/mediawiki/index.php?title=Improving_the_Deployment_Toolkit&diff=242386Improving the Deployment Toolkit2010-08-02T12:01:51Z<p>Alexandros.Papadopoulos: </p>
<hr />
<div>A place to gather all ideas about creating a process to perpetually improve the deployment toolkit.<br />
<br />
{{draft}}<br />
<br />
== Ideas ==<br />
<br />
* Idea 1<br />
* Idea 2<br />
* Idea 3<br />
<br />
== Deliverables ==<br />
<br />
# Improved deployment guide (wiki WIP version)<br />
# Improved deployment guide (Google Docs Word "release" version)<br />
# Improved deployment workbook (Google Docs spreadsheet)<br />
# Guidance document about how to create a customised deployment guide that will be most appropriate for YOUR deployment.<br />
# Deployments tracker - who is at what phase, what problems they've solved.<br />
# Contacts list - who are the key people.<br />
<br />
== Work in Progress ==<br />
<br />
* Add content here</div>Alexandros.Papadopouloshttp://wiki.laptop.org/mediawiki/index.php?title=Improving_the_Deployment_Toolkit&diff=242385Improving the Deployment Toolkit2010-08-02T11:59:31Z<p>Alexandros.Papadopoulos: Page creation</p>
<hr />
<div>A place to gather all ideas about creating a process to perpetually improve the deployment toolkit.<br />
<br />
{{draft}}<br />
<br />
== Ideas ==<br />
<br />
+ Idea 1<br /><br />
+ Idea 2<br /><br />
+ Idea 3<br /><br />
<br />
== Deliverables ==<br />
<br />
+ Improved deployment guide (wiki WIP version)<br /><br />
+ Improved deployment guide (Google Docs Word "release" version)<br /><br />
+ Improved deployment workbook (Google Docs spreadsheet)<br /><br />
+ Guidance document about how to create a customised deployment guide that will be most appropriate for YOUR deployment.<br /><br />
+ Deployments tracker - who is at what phase, what problems they've solved.<br /><br />
+ Contacts list - who are the key people.<br /><br />
<br />
== Work in Progress ==<br />
<br />
+ Add content here</div>Alexandros.Papadopouloshttp://wiki.laptop.org/mediawiki/index.php?title=Deployment_Guide/Workbook&diff=239217Deployment Guide/Workbook2010-07-12T19:52:59Z<p>Alexandros.Papadopoulos: /* Workbook Description */ Fixed internal link</p>
<hr />
<div><noinclude>{{Google Translations}}</noinclude><br />
{{OLPC}}<br />
<br />
This is a workbook for estimating the cost of a large-scale deployment of One Laptop Per Child. It is a working document that reflects lessons learned from initial pilots and deployments. Additional ideas will be incorporated as we learn from each other.<br />
<br />
The latest version is available in Microsoft Excel format: [[Media:Deployment_Workbook_v14.xls|Deployment_Workbook.xls]]<br />
<br />
Older versions: [[Media:Deployment_Guide_Worksheet_v10.xls|v10]], [[Media:Deployment_Workbook_v12.xls|v12]] [[Media:Deployment_Workbook_v13.xls|v13]]<br />
<br />
<br />
=Introduction=<br />
<br />
The One Laptop per Child (OLPC) Deployment Workbook contains six worksheets. There are two worksheets for use in planning: Country and [[#Individual_School_Expenses_Estimate|School]]. The Country worksheet takes information about overall number of laptops and rough percentages of schools and provides a rough estimate of the costs. The [[#Individual_School_Expenses_Estimate|School worksheet]] takes detailed information about a particular school and provides an estimate of the required infrastructure, power, and costs given different power scenarios.<br />
<br />
These estimated costs depend on the accuracy of the system component costs specified in the Laptop Costs, [[#Program_Costs|Program Costs]], and [[#Other_Costs|Other Costs]] worksheets. While the defaults provided are based on commercially available components, '''these must be updated to reflect current and local prices for these components before using this workbook to estimate costs'''.<br />
<br />
==How to use the workbook==<br />
<br />
* Download the workbook (see the top of this page)<br />
<br />
* Determine local prices for items such as school servers, generators, wireless access points, wireless switches, the cost of running a Cat5 network cable or power cable for 30m in a typical school, and update the [[#Other_Costs|Other Costs worksheet]].<br />
<br />
* If estimating costs across the entire deployment, the [[#Program_Costs|Program Costs worksheet]] should also be updated.<br />
<br />
* At this point, you can estimate costs across the entire deployment using the [[#Country_Expenses_Estimate|Country Expenses Estimate worksheet]].<br />
<br />
* If you want to see the estimated cost of a single school, and compare the costs of different methods of powering the laptops, use the [[#Individual_School_Expenses_Estimate|Individual School Expenses Estimate worksheet]].<br />
<br />
==Similar Workbooks==<br />
<br />
Similar spreadsheets are available from other sources. For example, the [http://www.gesci.org/ Global e-Schools and Communities Initiative] has [http://www.gesci.org/knowledge-tools.html#tco Total Cost of Ownership Tools] which are more general and long-term.<br />
<br />
=Workbook Description=<br />
The workbook is a database of the cost (both in money and power) of system components, contained in the [[#Laptop_Costs|Laptop Costs]], [[#Other_Costs|Other Costs]], and [[#Program_Costs|Program Costs]] worksheets. The [[#Country_Expenses_Estimate|Country Expenses Estimate]] and [[#Individual_School_Expenses_Estimate|School Expenses Estimate]] worksheets provide two methods of making expense estimates using that database. The [[#Examples|Examples]] worksheet contains intermediate calculations used by the [[#Country_Expenses_Estimate|Country Expenses Estimate]], and the Changes worksheet indicates what version of the workbook you have, and any recent changes.<br />
<br />
==Country Expenses Estimate==<br />
<br />
This worksheet calculates the estimated expenses for a one-time deployment in a country, estimating both the initial capital expenditure and the monthly technical operating expenses. It has two sections. The first contains information needed about the deployment, and the second shows the estimated costs of deployment.<br />
<br />
===To be filled by the Country===<br />
<br />
====Total Number of Laptops====<br />
The total number of laptops, both to students and teachers, should be specified here.<br />
<br />
====Percentage of Laptops going where====<br />
<br />
This is a coarse description of the types of schools where the laptops will be deployed, grouped by size and source of power. Enter the percentage of laptops (not schools) which will be deployed to each group. Any remaining schools are assigned to the "large schools on the national grid" group.<br />
<br />
Three sizes of schools are identified: those smaller than 50 students, those between 50 and 500 students, and those with more than 500 students. These groups were selected as the costs of a school are roughly linear within them.<br />
<br />
The sources of power considered here are national grid, solar, generator, and individual solar panels (for small schools). Some of the variations in power distribution within the school supported by the [[#Individual_School_Expenses_Estimate|School Expenses Estimate]] are not<br />
directly selectable in the Country estimate.<br />
<br />
====Percentage of Schools with Internet Connectivity====<br />
<br />
The types of Internet connections that will be used by schools in a country are specified here. Allowed options are:<br />
* DSL - A DSL broadband connection<br />
* VSAT - A satellite connection<br />
* GSM - A cellular telephone data connection, GPRS, EDGE, or other (3G)<br />
* Other - An alternative local method may be specified<br />
* None - no Internet connection will be provided<br />
<br />
What is needed for this estimate is the percentage of schools that will have each type of connection. Any schools not accounted for are assumed to have no Internet connection.<br />
<br />
This input impacts the budget estimate in a variety of ways: the initial cost of the terminal equipment, and the power and monthly subscription cost of the connection. It does not impact the decision to have a school server or wireless network.<br />
<br />
The local costs of each of these connectivity options, in terms of money and power, must be specified in the [[#Other_Costs|Other Costs worksheet]]. <br />
<br />
====Additional Usage Information====<br />
These are parameters about laptop usage which can greatly impact the price estimates of off-grid schools.<br />
<br />
=====Laptop Usage=====<br />
The number of times a laptop in the school will be charged in a day. To specify a usage model where laptops are continuously connected (both charging and operating) throughout the day, specify 2. Fractional values --- such as 0.5, indicating one charge every two days --- may be specified. This workbook assumes that if multiple charges per day are supplied to the laptops, they are supplied sequentially, not simultaneously (for example, using a multi-battery charger in addition to the laptop).<br />
<br />
''This value is typically 0.5 to 2. It should not be smaller than 0.33, which indicates that the student is only getting one charge per three school days. It should not be larger than the [[#Infrastructure Usage|Infrastructure Usage]] divided by the Laptop & MBC Charge time (two hours, in [[#System_Constants|System Constants in the Other Costs worksheet]]).''<br />
<br />
=====Laptops simultaneously charging=====<br />
This is the percentage of the laptops in a school that will be charging (or connected to power) at any one time. This ratio should be 100% if all of the students are capable of plugging their laptops in simultaneously. This is used to estimate the peak power draw, necessary when estimating the required generators, inverters, and school power infrastructure.<br />
<br />
''This value is typically 60 to 100%. It must not be smaller than Laptop Usage (above) times Laptop & MBC Charge time (two hours, in [[#System_Constants|System Constants in the Other Costs worksheet]]) divided by the [[#Infrastructure Usage|Infrastructure Usage]].''<br />
<br />
=====Infrastructure Usage=====<br />
The number of hours in a school day that networking infrastructure and the school server are operated. It is surprising how little it costs to operate the infrastructure for longer periods of time, compared to the capital cost of installing it.<br />
<br />
It is assumed in this workbook that infrastructure is turned off on the weekends. This may be altered by changing the ''Number of School Days <br />
<br />
''This value should be at least the Laptop & MBC Charge time (two hours, in [[#System_Constants|System Constants in the Other Costs worksheet]]). It should not be larger than 24.''<br />
<br />
=====How much storage=====<br />
The number of days of electrical power storage that is provided in solar powered schools. Fractional portions of a day (0.5, 0.2) may be specified.<br />
<br />
''This value is typically between 0 and 2''<br />
<br />
=====Hours of sunlight per day=====<br />
The number of hours per day that the school receives sunlight acceptable for generating solar power.<br />
<br />
''This value is typically between 2 and 4.5''<br />
<br />
===Estimated Deployment Expenses===<br />
<br />
This is a table showing the Capital and Operating expenses for the laptop and infrastructure costs. It is organized first with the costs by group of school, then the repair costs, the Internet connectivity, and the associated program costs.<br />
<br />
The expenses (capital and operating) are also detailed into Laptop, laptop repair, networking, and power infrastructure.<br />
<br />
The [[#Examples|Examples]] worksheet contains the intermediate calculations whose results are reported here.<br />
<br />
====Total Estimated Capital Costs====<br />
This is the total estimated cost to deploy the indicated amount of laptops into schools of the the specified size, power, and connectivity.<br />
<br />
====Total Estimated Monthly Operating Costs====<br />
This is the total estimated cost per month to provide Internet connectivity and increased power to support laptops and associated infrastructure in the specified schools.<br />
<br />
====Estimated Total Number of Schools====<br />
<br />
This number is computed from the information given. If an accurate number is available, it should be entered here to improve the quality of the estimate.<br />
<br />
==Individual School Expenses Estimate==<br />
<br />
This worksheet calculates the estimated expenses for a particular school, illustrating the costs of different power generation and distribution schemes. It has two sections. The first contains six fields that describe the school, the remainder of the worksheet shows estimated power usage and costs.<br />
<br />
===To be filled by the Country===<br />
These are the variables that describe the school for which power and cost estimates are being made.<br />
<br />
====Number of laptops in the school====<br />
The total number of XO laptops deployed at the school, including teachers and students.<br />
<br />
====Internet Connectivity====<br />
How this school will be connected to the Internet. Allowed options are:<br />
* DSL - A DSL broadband connection<br />
* VSAT - A satellite connection<br />
* GSM - A cellular telephone data connection, GPRS, EDGE, or other (3G)<br />
* Other - An alternative local method may be specified<br />
* None - no Internet connection will be provided<br />
<br />
The local costs of each of these options, in terms of money and power, must be specified in the [[#Other_Costs|Other Costs worksheet]].<br />
<br />
====Additional Parameters====<br />
These are identical to those described in [[#Additional_Usage_Information|Additional Usage Information for the Country worksheet]]. In this case they apply only to this school.<br />
<br />
===Suggested Infrastructure===<br />
<br />
This is information provided by the worksheet about the school infrastructure.<br />
<br />
'''Number of Servers''' - The number of school servers that are recommended for this school, and its size. The number of servers is one in most cases. Even when two is specified, this may be viewed as encouragement to buy one server with twice the disk space and memory. The size of the server depends on the number of laptops being supported.<br />
<br />
'''Number of Access Points''' - The number of 802.11 WiFi Access Points (APs) in a school is roughly determined by the number of laptops in the school. This laptop/AP ratio is assumed to be 50:1 for small schools, but increases for larger schools.<br />
<br />
'''Number of Switches''' - The number of network switches required for a school. These are assumed to be eight port switches, with four ports providing power (for access points). The number required is determined by the number of access points.<br />
<br />
====Power Requirements====<br />
'''Laptops''' - This is the [http://en.wikipedia.org/wiki/Power_factor real power] required for laptops in a school, expressed both as a peak power and the total power per day.<br />
The peak power, expressed in kiloWatts, is calculated as the number of laptops simultaneously charging in the school times the real power (in Watt Hours) required to charge a laptop, divided by the time it takes to charge. The total power, expressed in kiloWatt Hours per day, is the number of laptops in the school times the number of charges per day times the real power (in Watt Hours) required to charge a laptop.<br />
<br />
'''Laptops (assuming XO power adapter)''' - This is the [http://en.wikipedia.org/wiki/Power_factor apparent power] required for laptops in a school, expressed both as a peak power and the total power per day. This takes into account irregularities in the way that the power adapter consumes power. If a large number of them are the main consumers of electricity in a system, it is necessary to use the apparent power in estimating power requirements.<br />
The apparent power, expressed in kiloVolt Amps, is calculated as the number of laptops simultaneously charging in the school times the real power (in Watt hours) required to charge a laptop, divided by the time it takes to charge times the laptop power adapter's power factor. The total apparent power, expressed in kiloVolt Amp Hours per day, is the number of laptops in the school times the number of charges per day times the real power (in Watt Hours) required to charge a laptop, divided by the laptop power adapter's power factor.<br />
<br />
'''Servers''' - This is the apparent power required for the [[School server]], expressed both as a peak power (in kiloVolt Amps) and the total power per day (in kiloVolt Amp hours).<br />
<br />
'''Networking''' - This is the apparent power required for the school networking infrastructure, expressed both as a peak power (in kiloVolt Amps) and the total power per day (in kiloVolt Amp hours). The networking infrastructure includes the 802.11 access points, the network switches, and any Internet access equipment (DSL/VSAT/GSM modem).<br />
<br />
====Peak Power Draw at this school====<br />
Specified in kiloVolt Amps. This is estimated as the power required to continuously power the server and networking infrastructure, plus that required to power the "Simultaneous Charging" portion of the laptops in a school. If multiple charges per day are supplied to the laptops, it is assumed that they are not supplied simultaneously.<br />
<br />
====Power per day required by this school====<br />
Specified in kiloVolt Amp hours. This is the total amount of energy required to operate the schools laptops and associated infrastructure for a single day.<br />
<br />
====Server====<br />
These are characteristics of the recommended [[School server]]:<br />
<br />
'''Processor''' - A rough recommendation of processor speed<br />
<br />
'''Minimum Memory (DRAM)''' - The minimum amount of memory (DRAM) the server should have.<br />
<br />
'''Minimum Disk Storage''' - The minimum amount of disk storage that the server should have.<br />
<br />
===Estimated Costs===<br />
<br />
These are estimates of the infrastructure needed for each of a number of power source and distribution combinations.<br />
<br />
====With Grid Power====<br />
This is the detailed estimate for this school with a connection to the national power grid, using power strips and the XO power adapter to distribute power.<br />
<br />
====With Grid Power and XOP====<br />
This is the detailed estimate for this school with a connection to the national power grid, using the Belkin XOP (or equivalent) to distribute power to the laptops.<br />
<br />
====With Grid Power and MBC====<br />
This is the detailed estimate for this school with a connection to the national power grid, using the Multi Battery Charger (or equivalent) to recharge the laptop batteries.<br />
<br />
The number of Multi Battery Chargers could be based on how many charges you required each day, how long people are in school to swap batteries and how many hours it takes the MBC to charge a battery.<br />
It is instead currently based on the Simultaneous_Charging ratio specified as a constant in the [[#Other_Costs|Other Costs worksheet]].<br />
<br />
====With Solar Power====<br />
This is the detailed estimate for this school using a centralized solar system for power.<br />
<br />
====With Solar Power and XOP====<br />
This is the detailed estimate for this school with a centralized solar system, using the Belkin XOP (or equivalent) to distribute power to the laptops.<br />
<br />
====With Solar Power and MBC====<br />
This is the detailed estimate for this school with a centralized solar system, using the Multi Battery Charger (or equivalent) to recharge the laptop batteries.<br />
<br />
====With Generator====<br />
This is the detailed estimate for this school using a diesel/gasoline powered generator for power, and distributing the power using power strips and XO power adapters.<br />
<br />
====With Generator and XOP====<br />
This is the detailed estimate for this school using a diesel/gasoline powered generator, using the Belkin XOP (or equivalent) to distribute power to the laptops.<br />
<br />
====With Individual Solar====<br />
This is the detailed estimate for this school with a centralized solar system for the server and networking infrastructure, and individual solar panels for recharging the laptops.<br />
<br />
==Laptop Costs==<br />
<br />
<br />
==Program Costs==<br />
<br />
<br />
==Other Costs==<br />
<br />
This worksheet specifies the equipment costs and power requirements used for estimates across the workbook. It contains all costs, other than those associated directly with the XO laptop (specified in [[#Laptop_Costs|Laptop Costs]]), or with the pedagogical aspects of a deployment (specified in [[#Program_Costs|Program Costs]]). While example prices are provided, '''actual prices quoted on the local market must be substituted before using this workbook for budget estimates'''. All prices should include shipping costs and duties.<br />
<br />
===Server and Networking===<br />
<br />
===Internet Access===<br />
<br />
===Power Infrastructure===<br />
<br />
'''XOP Distributed or Rack''' - This is the Belkin XOP Distributed power system for the laptops. It is a power supply which supports four laptops per node, and may be chained to simply accomodate more laptops. It includes a rack for creating a charging station for the laptops. ''This is an estimated price of $150 ex-works, and $15 shipping''<br />
<br />
'''Multi Battery Charger''' - This is the OLPC multi battery charging system for the laptops. It is a battery charger which charges up to fifteen laptop batteries at a time, and takes either an AC input or a DC input direct from an array of solar panels. ''This is an estimated price of $300 ex-works, with $50 shipping''.<br />
<br />
===System Constants===<br />
<br />
<br />
==Examples==<br />
<br />
This worksheet contains an abbreviated version of the individual school cost estimates for the various example schools used in generating [[#Country_Expenses_Estimate|an estimate for a country deployment]]. These should only be changed in order to refine the country estimate. Use the [[#Individual_School_Expenses_Estimate|School Expenses Estimate worksheet]] to experiment with school parameters.<br />
<br />
Several school infrastructure parameters, such as the number of sunlight hours, the number of laptop charges per day, and the various types of internet connections are defined in common in the Country worksheet. <br />
<br />
The costs of Internet connections are not present in these example school estimates. Their cost is represented separately in the country estimate, and their power is appropriately averaged and accounted for in the calculations on this worksheet.<br />
<br />
===Example #1: Small School===<br />
This is a school with 30 students. This sample point illustrates the higher cost of providing infrastructure to small schools.<br />
<br />
===Example #2: Medium School===<br />
This is a school with 200 students. This sample point is representative of a wide range of school sizes between the small school and the large schools (500 or more students).<br />
<br />
===Example #3: Large School===<br />
This is a school with 500 students. Our models do not take advantage of any economies of scale present in schools larger than this, making this an appropriate sample point.<br />
<br />
[[Category:Documentation]]<br />
[[Category:Hardware]]</div>Alexandros.Papadopouloshttp://wiki.laptop.org/mediawiki/index.php?title=Deployment_Guide/Workbook&diff=239216Deployment Guide/Workbook2010-07-12T19:50:54Z<p>Alexandros.Papadopoulos: /* Similar Workbooks */ Updated 404 TCO tools link</p>
<hr />
<div><noinclude>{{Google Translations}}</noinclude><br />
{{OLPC}}<br />
<br />
This is a workbook for estimating the cost of a large-scale deployment of One Laptop Per Child. It is a working document that reflects lessons learned from initial pilots and deployments. Additional ideas will be incorporated as we learn from each other.<br />
<br />
The latest version is available in Microsoft Excel format: [[Media:Deployment_Workbook_v14.xls|Deployment_Workbook.xls]]<br />
<br />
Older versions: [[Media:Deployment_Guide_Worksheet_v10.xls|v10]], [[Media:Deployment_Workbook_v12.xls|v12]] [[Media:Deployment_Workbook_v13.xls|v13]]<br />
<br />
<br />
=Introduction=<br />
<br />
The One Laptop per Child (OLPC) Deployment Workbook contains six worksheets. There are two worksheets for use in planning: Country and [[#Individual_School_Expenses_Estimate|School]]. The Country worksheet takes information about overall number of laptops and rough percentages of schools and provides a rough estimate of the costs. The [[#Individual_School_Expenses_Estimate|School worksheet]] takes detailed information about a particular school and provides an estimate of the required infrastructure, power, and costs given different power scenarios.<br />
<br />
These estimated costs depend on the accuracy of the system component costs specified in the Laptop Costs, [[#Program_Costs|Program Costs]], and [[#Other_Costs|Other Costs]] worksheets. While the defaults provided are based on commercially available components, '''these must be updated to reflect current and local prices for these components before using this workbook to estimate costs'''.<br />
<br />
==How to use the workbook==<br />
<br />
* Download the workbook (see the top of this page)<br />
<br />
* Determine local prices for items such as school servers, generators, wireless access points, wireless switches, the cost of running a Cat5 network cable or power cable for 30m in a typical school, and update the [[#Other_Costs|Other Costs worksheet]].<br />
<br />
* If estimating costs across the entire deployment, the [[#Program_Costs|Program Costs worksheet]] should also be updated.<br />
<br />
* At this point, you can estimate costs across the entire deployment using the [[#Country_Expenses_Estimate|Country Expenses Estimate worksheet]].<br />
<br />
* If you want to see the estimated cost of a single school, and compare the costs of different methods of powering the laptops, use the [[#Individual_School_Expenses_Estimate|Individual School Expenses Estimate worksheet]].<br />
<br />
==Similar Workbooks==<br />
<br />
Similar spreadsheets are available from other sources. For example, the [http://www.gesci.org/ Global e-Schools and Communities Initiative] has [http://www.gesci.org/knowledge-tools.html#tco Total Cost of Ownership Tools] which are more general and long-term.<br />
<br />
=Workbook Description=<br />
The workbook is a database of the cost (both in money and power) of system components, contained in the [[#Laptop_Costs|Laptop Costs]], [[#Other_Costs|Other Costs]], and [[#Program_Costs|Program Costs]] worksheets. The [[#Country_Expenses_Estimate|Country Expenses Estimate]] and [[#School_Expenses_Estimate|School Expenses Estimate]] worksheets provide two methods of making expense estimates using that database. The [[#Examples|Examples]] worksheet contains intermediate calculations used by the [[#Country_Expenses_Estimate|Country Expenses Estimate]], and the Changes worksheet indicates what version of the workbook you have, and any recent changes.<br />
<br />
==Country Expenses Estimate==<br />
<br />
This worksheet calculates the estimated expenses for a one-time deployment in a country, estimating both the initial capital expenditure and the monthly technical operating expenses. It has two sections. The first contains information needed about the deployment, and the second shows the estimated costs of deployment.<br />
<br />
===To be filled by the Country===<br />
<br />
====Total Number of Laptops====<br />
The total number of laptops, both to students and teachers, should be specified here.<br />
<br />
====Percentage of Laptops going where====<br />
<br />
This is a coarse description of the types of schools where the laptops will be deployed, grouped by size and source of power. Enter the percentage of laptops (not schools) which will be deployed to each group. Any remaining schools are assigned to the "large schools on the national grid" group.<br />
<br />
Three sizes of schools are identified: those smaller than 50 students, those between 50 and 500 students, and those with more than 500 students. These groups were selected as the costs of a school are roughly linear within them.<br />
<br />
The sources of power considered here are national grid, solar, generator, and individual solar panels (for small schools). Some of the variations in power distribution within the school supported by the [[#Individual_School_Expenses_Estimate|School Expenses Estimate]] are not<br />
directly selectable in the Country estimate.<br />
<br />
====Percentage of Schools with Internet Connectivity====<br />
<br />
The types of Internet connections that will be used by schools in a country are specified here. Allowed options are:<br />
* DSL - A DSL broadband connection<br />
* VSAT - A satellite connection<br />
* GSM - A cellular telephone data connection, GPRS, EDGE, or other (3G)<br />
* Other - An alternative local method may be specified<br />
* None - no Internet connection will be provided<br />
<br />
What is needed for this estimate is the percentage of schools that will have each type of connection. Any schools not accounted for are assumed to have no Internet connection.<br />
<br />
This input impacts the budget estimate in a variety of ways: the initial cost of the terminal equipment, and the power and monthly subscription cost of the connection. It does not impact the decision to have a school server or wireless network.<br />
<br />
The local costs of each of these connectivity options, in terms of money and power, must be specified in the [[#Other_Costs|Other Costs worksheet]]. <br />
<br />
====Additional Usage Information====<br />
These are parameters about laptop usage which can greatly impact the price estimates of off-grid schools.<br />
<br />
=====Laptop Usage=====<br />
The number of times a laptop in the school will be charged in a day. To specify a usage model where laptops are continuously connected (both charging and operating) throughout the day, specify 2. Fractional values --- such as 0.5, indicating one charge every two days --- may be specified. This workbook assumes that if multiple charges per day are supplied to the laptops, they are supplied sequentially, not simultaneously (for example, using a multi-battery charger in addition to the laptop).<br />
<br />
''This value is typically 0.5 to 2. It should not be smaller than 0.33, which indicates that the student is only getting one charge per three school days. It should not be larger than the [[#Infrastructure Usage|Infrastructure Usage]] divided by the Laptop & MBC Charge time (two hours, in [[#System_Constants|System Constants in the Other Costs worksheet]]).''<br />
<br />
=====Laptops simultaneously charging=====<br />
This is the percentage of the laptops in a school that will be charging (or connected to power) at any one time. This ratio should be 100% if all of the students are capable of plugging their laptops in simultaneously. This is used to estimate the peak power draw, necessary when estimating the required generators, inverters, and school power infrastructure.<br />
<br />
''This value is typically 60 to 100%. It must not be smaller than Laptop Usage (above) times Laptop & MBC Charge time (two hours, in [[#System_Constants|System Constants in the Other Costs worksheet]]) divided by the [[#Infrastructure Usage|Infrastructure Usage]].''<br />
<br />
=====Infrastructure Usage=====<br />
The number of hours in a school day that networking infrastructure and the school server are operated. It is surprising how little it costs to operate the infrastructure for longer periods of time, compared to the capital cost of installing it.<br />
<br />
It is assumed in this workbook that infrastructure is turned off on the weekends. This may be altered by changing the ''Number of School Days <br />
<br />
''This value should be at least the Laptop & MBC Charge time (two hours, in [[#System_Constants|System Constants in the Other Costs worksheet]]). It should not be larger than 24.''<br />
<br />
=====How much storage=====<br />
The number of days of electrical power storage that is provided in solar powered schools. Fractional portions of a day (0.5, 0.2) may be specified.<br />
<br />
''This value is typically between 0 and 2''<br />
<br />
=====Hours of sunlight per day=====<br />
The number of hours per day that the school receives sunlight acceptable for generating solar power.<br />
<br />
''This value is typically between 2 and 4.5''<br />
<br />
===Estimated Deployment Expenses===<br />
<br />
This is a table showing the Capital and Operating expenses for the laptop and infrastructure costs. It is organized first with the costs by group of school, then the repair costs, the Internet connectivity, and the associated program costs.<br />
<br />
The expenses (capital and operating) are also detailed into Laptop, laptop repair, networking, and power infrastructure.<br />
<br />
The [[#Examples|Examples]] worksheet contains the intermediate calculations whose results are reported here.<br />
<br />
====Total Estimated Capital Costs====<br />
This is the total estimated cost to deploy the indicated amount of laptops into schools of the the specified size, power, and connectivity.<br />
<br />
====Total Estimated Monthly Operating Costs====<br />
This is the total estimated cost per month to provide Internet connectivity and increased power to support laptops and associated infrastructure in the specified schools.<br />
<br />
====Estimated Total Number of Schools====<br />
<br />
This number is computed from the information given. If an accurate number is available, it should be entered here to improve the quality of the estimate.<br />
<br />
==Individual School Expenses Estimate==<br />
<br />
This worksheet calculates the estimated expenses for a particular school, illustrating the costs of different power generation and distribution schemes. It has two sections. The first contains six fields that describe the school, the remainder of the worksheet shows estimated power usage and costs.<br />
<br />
===To be filled by the Country===<br />
These are the variables that describe the school for which power and cost estimates are being made.<br />
<br />
====Number of laptops in the school====<br />
The total number of XO laptops deployed at the school, including teachers and students.<br />
<br />
====Internet Connectivity====<br />
How this school will be connected to the Internet. Allowed options are:<br />
* DSL - A DSL broadband connection<br />
* VSAT - A satellite connection<br />
* GSM - A cellular telephone data connection, GPRS, EDGE, or other (3G)<br />
* Other - An alternative local method may be specified<br />
* None - no Internet connection will be provided<br />
<br />
The local costs of each of these options, in terms of money and power, must be specified in the [[#Other_Costs|Other Costs worksheet]].<br />
<br />
====Additional Parameters====<br />
These are identical to those described in [[#Additional_Usage_Information|Additional Usage Information for the Country worksheet]]. In this case they apply only to this school.<br />
<br />
===Suggested Infrastructure===<br />
<br />
This is information provided by the worksheet about the school infrastructure.<br />
<br />
'''Number of Servers''' - The number of school servers that are recommended for this school, and its size. The number of servers is one in most cases. Even when two is specified, this may be viewed as encouragement to buy one server with twice the disk space and memory. The size of the server depends on the number of laptops being supported.<br />
<br />
'''Number of Access Points''' - The number of 802.11 WiFi Access Points (APs) in a school is roughly determined by the number of laptops in the school. This laptop/AP ratio is assumed to be 50:1 for small schools, but increases for larger schools.<br />
<br />
'''Number of Switches''' - The number of network switches required for a school. These are assumed to be eight port switches, with four ports providing power (for access points). The number required is determined by the number of access points.<br />
<br />
====Power Requirements====<br />
'''Laptops''' - This is the [http://en.wikipedia.org/wiki/Power_factor real power] required for laptops in a school, expressed both as a peak power and the total power per day.<br />
The peak power, expressed in kiloWatts, is calculated as the number of laptops simultaneously charging in the school times the real power (in Watt Hours) required to charge a laptop, divided by the time it takes to charge. The total power, expressed in kiloWatt Hours per day, is the number of laptops in the school times the number of charges per day times the real power (in Watt Hours) required to charge a laptop.<br />
<br />
'''Laptops (assuming XO power adapter)''' - This is the [http://en.wikipedia.org/wiki/Power_factor apparent power] required for laptops in a school, expressed both as a peak power and the total power per day. This takes into account irregularities in the way that the power adapter consumes power. If a large number of them are the main consumers of electricity in a system, it is necessary to use the apparent power in estimating power requirements.<br />
The apparent power, expressed in kiloVolt Amps, is calculated as the number of laptops simultaneously charging in the school times the real power (in Watt hours) required to charge a laptop, divided by the time it takes to charge times the laptop power adapter's power factor. The total apparent power, expressed in kiloVolt Amp Hours per day, is the number of laptops in the school times the number of charges per day times the real power (in Watt Hours) required to charge a laptop, divided by the laptop power adapter's power factor.<br />
<br />
'''Servers''' - This is the apparent power required for the [[School server]], expressed both as a peak power (in kiloVolt Amps) and the total power per day (in kiloVolt Amp hours).<br />
<br />
'''Networking''' - This is the apparent power required for the school networking infrastructure, expressed both as a peak power (in kiloVolt Amps) and the total power per day (in kiloVolt Amp hours). The networking infrastructure includes the 802.11 access points, the network switches, and any Internet access equipment (DSL/VSAT/GSM modem).<br />
<br />
====Peak Power Draw at this school====<br />
Specified in kiloVolt Amps. This is estimated as the power required to continuously power the server and networking infrastructure, plus that required to power the "Simultaneous Charging" portion of the laptops in a school. If multiple charges per day are supplied to the laptops, it is assumed that they are not supplied simultaneously.<br />
<br />
====Power per day required by this school====<br />
Specified in kiloVolt Amp hours. This is the total amount of energy required to operate the schools laptops and associated infrastructure for a single day.<br />
<br />
====Server====<br />
These are characteristics of the recommended [[School server]]:<br />
<br />
'''Processor''' - A rough recommendation of processor speed<br />
<br />
'''Minimum Memory (DRAM)''' - The minimum amount of memory (DRAM) the server should have.<br />
<br />
'''Minimum Disk Storage''' - The minimum amount of disk storage that the server should have.<br />
<br />
===Estimated Costs===<br />
<br />
These are estimates of the infrastructure needed for each of a number of power source and distribution combinations.<br />
<br />
====With Grid Power====<br />
This is the detailed estimate for this school with a connection to the national power grid, using power strips and the XO power adapter to distribute power.<br />
<br />
====With Grid Power and XOP====<br />
This is the detailed estimate for this school with a connection to the national power grid, using the Belkin XOP (or equivalent) to distribute power to the laptops.<br />
<br />
====With Grid Power and MBC====<br />
This is the detailed estimate for this school with a connection to the national power grid, using the Multi Battery Charger (or equivalent) to recharge the laptop batteries.<br />
<br />
The number of Multi Battery Chargers could be based on how many charges you required each day, how long people are in school to swap batteries and how many hours it takes the MBC to charge a battery.<br />
It is instead currently based on the Simultaneous_Charging ratio specified as a constant in the [[#Other_Costs|Other Costs worksheet]].<br />
<br />
====With Solar Power====<br />
This is the detailed estimate for this school using a centralized solar system for power.<br />
<br />
====With Solar Power and XOP====<br />
This is the detailed estimate for this school with a centralized solar system, using the Belkin XOP (or equivalent) to distribute power to the laptops.<br />
<br />
====With Solar Power and MBC====<br />
This is the detailed estimate for this school with a centralized solar system, using the Multi Battery Charger (or equivalent) to recharge the laptop batteries.<br />
<br />
====With Generator====<br />
This is the detailed estimate for this school using a diesel/gasoline powered generator for power, and distributing the power using power strips and XO power adapters.<br />
<br />
====With Generator and XOP====<br />
This is the detailed estimate for this school using a diesel/gasoline powered generator, using the Belkin XOP (or equivalent) to distribute power to the laptops.<br />
<br />
====With Individual Solar====<br />
This is the detailed estimate for this school with a centralized solar system for the server and networking infrastructure, and individual solar panels for recharging the laptops.<br />
<br />
==Laptop Costs==<br />
<br />
<br />
==Program Costs==<br />
<br />
<br />
==Other Costs==<br />
<br />
This worksheet specifies the equipment costs and power requirements used for estimates across the workbook. It contains all costs, other than those associated directly with the XO laptop (specified in [[#Laptop_Costs|Laptop Costs]]), or with the pedagogical aspects of a deployment (specified in [[#Program_Costs|Program Costs]]). While example prices are provided, '''actual prices quoted on the local market must be substituted before using this workbook for budget estimates'''. All prices should include shipping costs and duties.<br />
<br />
===Server and Networking===<br />
<br />
===Internet Access===<br />
<br />
===Power Infrastructure===<br />
<br />
'''XOP Distributed or Rack''' - This is the Belkin XOP Distributed power system for the laptops. It is a power supply which supports four laptops per node, and may be chained to simply accomodate more laptops. It includes a rack for creating a charging station for the laptops. ''This is an estimated price of $150 ex-works, and $15 shipping''<br />
<br />
'''Multi Battery Charger''' - This is the OLPC multi battery charging system for the laptops. It is a battery charger which charges up to fifteen laptop batteries at a time, and takes either an AC input or a DC input direct from an array of solar panels. ''This is an estimated price of $300 ex-works, with $50 shipping''.<br />
<br />
===System Constants===<br />
<br />
<br />
==Examples==<br />
<br />
This worksheet contains an abbreviated version of the individual school cost estimates for the various example schools used in generating [[#Country_Expenses_Estimate|an estimate for a country deployment]]. These should only be changed in order to refine the country estimate. Use the [[#Individual_School_Expenses_Estimate|School Expenses Estimate worksheet]] to experiment with school parameters.<br />
<br />
Several school infrastructure parameters, such as the number of sunlight hours, the number of laptop charges per day, and the various types of internet connections are defined in common in the Country worksheet. <br />
<br />
The costs of Internet connections are not present in these example school estimates. Their cost is represented separately in the country estimate, and their power is appropriately averaged and accounted for in the calculations on this worksheet.<br />
<br />
===Example #1: Small School===<br />
This is a school with 30 students. This sample point illustrates the higher cost of providing infrastructure to small schools.<br />
<br />
===Example #2: Medium School===<br />
This is a school with 200 students. This sample point is representative of a wide range of school sizes between the small school and the large schools (500 or more students).<br />
<br />
===Example #3: Large School===<br />
This is a school with 500 students. Our models do not take advantage of any economies of scale present in schools larger than this, making this an appropriate sample point.<br />
<br />
[[Category:Documentation]]<br />
[[Category:Hardware]]</div>Alexandros.Papadopouloshttp://wiki.laptop.org/mediawiki/index.php?title=Ask_OLPC_a_Question_about_Social_Issues&diff=238178Ask OLPC a Question about Social Issues2010-07-01T11:46:08Z<p>Alexandros.Papadopoulos: </p>
<hr />
<div><noinclude>{{Translations}}</noinclude><br />
= Social Issues =<br />
<includeonly> <br />
<!-- This is a subpage of the "Ask OLPC a Question" page. Instructions for using it are at http://wiki.laptop.org/go/Answering_questions. Summary: The funny tags you see, such as noinclude.../noinclude and includeonly...includeonly are to enable it to be viewed both stand-alone and as part of that page. Please do not change these tags unless you understand them. Also, when answering a new question (at the end of the page), please cut and paste it to before the line near the end that begins with /noinclude; that will keep answered questions from clogging up the main FAQ page. --><br />
{{ask-olpc|title=Ask_OLPC_a_Question_about_Social_Issues}}<br />
</includeonly><br />
<noinclude><br />
This page deals with issues related to Social Issues.<br />
{{Header2|title=FAQ}}</noinclude><br />
The full impact of the OLPC will only be determined with time. Nevertheless, you may have concerns about [[Ask OLPC a Question about Social Issues#Government concerns|recipient governments]], [[Ask OLPC a Question about Social Issues#Child Safety Concerns|child safety]], [[Ask OLPC a Question about Social Issues#Privacy and Anonymity|privacy]], [[Ask OLPC a Question about Social Issues#Rights Abuse|abuse]]. A discussion of metrics can be found [[Our_mission#Metrics|here]], and a general discussion of social issues surrounding laptop deployment '''[[Ask OLPC a Question about Social Issues|can be found here]]'''.<br />
=== Child Safety Concerns ===<br />
There is a general statement on child safety at [[Online threats and security]].<br />
<br />
=== Cultural impact ===<br />
Replace with a link to summary/discussion of this issue.<br />
<br />
=== Ownership and theft ===<br />
Replace with a link to summary/discussion of this issue.<br />
<br />
==Other social issue questions==<br />
<br />
<br />
<noinclude><br />
== Child Safety ==<br />
<br />
=== Physical Security ===<br />
<br />
We passed out bracelets in Rio Branco Brazil and there was a mini-riot. How do you expect people to secury these laptops, especially children, when they usually don't have locks, doors, and in some cases houses? <br />
<br />
:This is really a question for the Brazilian government ministry of education who are the ones handing them out. Since these people have lived in Brazil all of their lives and are intimately familiar with Brazilian culture and Brazilian problems, one can expect that they have some sort of plan to deal with this issue. One solution would be to start with projects in small isolated towns where you can easily give 100% of children an XO. Then there is little incentive to steal them within the town since there is no scarcity. As for [[grey market]] sales, perhaps this cannot be prevented, but if they are government property, then Brazil has laws and enforcement apparatus that can be applied to the problem. The OLPC project really hasn't got much to do with this.<br />
<br />
=== Privacy issues from microphone ===<br />
<br />
Can the microphone be enable/disabled by hardware (e.g., a switch), in a way that you can obviously see?<br />
I'm concerned that the microphone may be solely controlled by software.<br />
If it is, it could be used as a surreptitious "bug" (recording device).<br />
Since it's on a mesh, an attacker could remotely attack a machine,<br />
and if/when they break in, monitor the surroundings unknown to all.<br />
Malevolent governments could do the same.<br />
<br />
:AFAIK there is no button for the microphone, for cost reasons: a button adds extra plastic, one more wire, and is just one more mechanical thing that can break. You bring up a good point about enabling the microphone and software and listening-in remotely: this wiki needs to have a security considerations page... --[[User:SamatJain|SamatJain]] 14:13, 8 August 2006 (EDT)<br />
<br />
:The microphone and the web camera have hard wired activity LEDs. These are connected at the hardware level and can't be controlled by software. If the microphone was enabled remotely, the light would go on. There is nothing that the software can do to prevent this. This is a deliberate design decision to prevent just such a scenario as you've described.[[User:Alc|Alc]] 23:11, 31 January 2008 (EST)<br />
<br />
:This issue should be raised in the Discussion section of the [[Security]] page.<br />
<br />
=== Privacy and Anonymity ===<br />
<br />
What measures are being taken to insure that this device does not become the instrument of an international id program?<br />
<br />
For all the [http://www.epic.org/privacy/id_cards/ reasons that people are concerned] about national id cards, the danger of this platform becoming a unique identifier of virtual identities is present. Will the platform ship with [http://tor.eff.org/ tools which support anonymous network activity]? [[User:Mrenoch|Mrenoch]] 05:53, 9 August 2006 (EDT)<br />
<br />
:While the laptops will have serial numbers (of course), there are no plans to ship the laptops with any remotely accessible unique identifiers. For a variety of technical, social, and design related reasons, we are not pursuing such a solution. --[[User:Mako|Mako]] 13:53, 10 August 2006 (EDT)<br />
<br />
<font size="1">(Moved discussion to [[Talk:Ask OLPC a Question about Social Issues]])</font><br />
<br />
=== Child Safety Concerns ===<br />
<br />
We are already seeing cases where social networking sites are being misused by criminals. Kids put a lot of trust on each other and will never doubt a message from someone who seems like a buddy to them. How can we warn the kids that in any network application, the person sitting on the other end need not be his/her friend? What about displaying some kind of a warning in chat and mail apps? I believe educating parents about potential dangers of misuse is also very important.<br />
<br />
:This is being taken seriously by the OLPC team. If you want to discuss this or other security issues, please do it in the Discussions section of the [[Security]] page.<br />
<br />
=== On potential child predators ===<br />
<br />
What precautions is your organization taking against potential child predators due to increased internet activity in the countries receiving laptops?<br />
<br />
:First answer is that we are designing a laptop that functions without any Internet access whatsoever. In many of the areas it will be deployed, the Internet is either unavailable or too expensive for educational use.<br />
<br />
:Second answer is that the educators who will be teaching the kids are being made aware of this potential issue.<br />
<br />
I need to know... how does a web camera (or digital camera whatever it so be called) help educate children? Don't get me wrong, I think education is extremely important and I use computers to learn more than I ever learned in school. The OLPC is a great idea with pros and cons like any tool ever invented. However; being a graduate of a Computer Security Investigations diploma and working with law enforcement on the subject of technology involved with online child exploitation, it is evident that yes a powerful and positive tool may be used for most any ill intended act.<br />
<br />
What I do not understand is why a web camera is essential in a tool for education. I understand that a large portion of communities who receive this laptop will not have Internet access, but it doesn't take Internet access to exploit children. One camera that can self develop digital photos is just as dangerous as having so many young children prowling through the Internet. I do not see loosing any educational value by removing the web camera from these laptops. The only outcome would be less power consumption, lower cost, and a safer experience for any child. I agree that Internet safety training can help educate children safe Internet use, but even with just community networking, is “safe computer training” really as efficient as removing a piece of this laptop that does not contribute to any educational purpose. D, Canada.<br />
<br />
<br />
=== Router-based content filtering/ parental controls ===<br />
<br />
How can I protect my child from porn and adults-only content? <br />
:In the US, most parents have access only to Windows-based content filtering software. That means that for children accessing the net at home in the US, the only ways to monitor content are 1)being in the same room and 2) implement some router-based content-filtering solution. Obviously, this is not a XO specific problem, but perhaps the Wiki can have community pages to recommend some router solutions.<br />
<br />
:I read that as either ''"How can I spare myself the awkwardness of walking in on my child while he enjoys some porn?"'' or ''"Can I have the computer enforce my morals so that I don't have to spend time with my kids?"''. (in other words, focused on '''''you''''' rather than the child) FYI, in many parts of the world it is common for families to live in 1-room houses. The kids get live action! Even Abraham Lincoln grew up that way, and he turned out OK. When I was 6 to 9, my school got numerous porn magazines blown into the yard from the construction sites next to the school. I too turned out OK. (with a strong decade-old marriage) Kids can even draw their own porn with the paint program (done it), dare each other to show off their parts (a friend did), or make the family dog ejaculate (my wife did). It's normal. It's a learning activity. It doesn't turn them into perverts, get anybody pregnant, or spread diseases.<br />
<br />
:In the US, most parents don't teach math and science to their kids. Your effort is better spent doing that.<br />
<br />
:If there is any computer-related thing that you need to keep from your kids, it is addictive games. Little is learned, and much time is wasted. Random web surfing is more useful. Even chatrooms are more useful.<br />
<br />
Please spare me your uniformed rant. Kids being exposed to porn is not a good thing, if you don't agree, then feel free to raise your own children with plenty of porn. Anyone have a helpful answer to the question?<br />
<br />
=== Marketing to Children ===<br />
<br />
What access will third parties (corporations) have to the mesh network, more specifically will direct marketing be permitted to children via this computer? <br />
<br />
:The intention is for the mesh network to be secure. Since it is a mesh, there is no central point at which communications can be tapped even if we wanted to do it. For instance, imagine a long narrow valley with a town at one end, and two kids living 100 km away but on opposite slopes with 5 km between the houses. The two kids will be able to communicate directly with the mesh network capability, but no-one in town will even detect their wifi signal.thats wats it is <br />
<br />
:Or to answer more directly, no, direct marketing to children will not be permitted over the mesh.<br />
<br />
== Gender and Gender Neutrality Objectives ==<br />
<br />
Many studies over the years have shown that the only proven, effective, long-term development strategies in developing countries are those which take into account and improve the lives, skillsets, health, or educational opportunities/access of women and girls. Yet in many developing countries, boys continue to be disproportionately represented in the classroom, particularly in countries where tuition must be paid, and in the realm of technology. <br />
<br />
Will OLPC be taking any steps to assure either the gender-neutrality of its laptops, software, distribution and marketing, or better yet, to include positive female models in its software or marketing from which both genders can learn? <br />
<br />
By this I emphatically do not mean something as superficial as pink laptops, but rather encourage your development teams and marketing/distribution teams to consider and at all stages keep in mind the issue of gender and the proven effectiveness of development strategies which pay special attention to the educational needs of women and girls. <br />
MKW, New York<br />
<br />
:In many cultures, even western countries, there is no blue/pink gender distinction. In such countries boys have no problem with pink things and children wear a wider variety of colours than in North America or England.<br />
<br />
:The OLPC does not distribute computers to kids. They design computers, arrange for them to be built and arrange for them to be shipped to national governments. If you want national governments to pay attention to gender issues, then you must target them directly. The OLPC will not be a shortcut for dealing with such issues. Note that one way to address the issues is to develop educational content that will lead the target government to want to give more computers to girls. But again, that content development is YOUR responsibility, not that of OLPC.<br />
<br />
::It is well known in development circles that educating girls is the key element in population control, health, the education of the next generation, creating a fair system of laws, and the growth of the economy. None of us are stupid enough to ignore this. Anyway, it's an open system running Free Software. Write your own gender-neutral education materials, if that's what you think we need most. Show the rest of us how to do it, and we'll pitch in. --[[User:Mokurai|Mokurai]] 06:59, 21 November 2006 (EST)<br />
<br />
== Overall impact ==<br />
<br />
What would be the possible social, technological and economic implications of the commitment to the initiative for a country like Nigeria or similar?<br />
<br />
:You mean like ending poverty, empowering the entire population politically, recording and saving all of Yoruba, Igbo, Hausa, and other Nigerian culture, and setting Nigeria on the path to full development? I have no idea what technology will come out of Nigeria after all that, but I'm sure that it will.--[[User:Mokurai|Mokurai]] 02:23, 13 October 2006 (EDT)<br />
<br />
:See [[Social Impact]]--[[User:Mokurai|Mokurai]] 18:17, 15 October 2006 (EDT)<br />
<br />
=== Lack of Schools and Infrastructure ===<br />
<br />
How will OLPC benefit countries when the majority of children do not attend public school or public school is not available?<br />
<br />
:Your statistics are questionable. What is your source for such an outrageous statement? In any case, the OLPC is not distributing laptops to schools, they are distributing laptops to kids. In thousands of small towns and villages, the existence of a mesh of laptops will create a learning infrastructure that can function without a school building.<br />
<br />
=== Intellectual Property Rights ===<br />
Another poster mentioned scams, but I can see spam and virus generation as also a problem (there goes the Linux virus advantage).<br />
<br />
I love the idea. In addition to the effect on the countries involved, I think that worldwide, lots of open source projects, including Wikipedia, are going to get a tremendous boost from this. I don't think the world has any idea what's going to hit it. But there's also a tremendous potential for abuse, and I think that OLPC (and your community, i.e. us) has a responsibility to be thinking about that also.<br />
<br />
--[[User:192.118.34.228|192.118.34.228]] 07:31, 17 October 2006 (EDT)<br />
<br />
:We are talking licensing very seriously with the machine. We will be introducing "digital rights expression" as a core feature of the machine. --[[User:Walter|Walter]] 18:53, 17 October 2006 (EDT)<br />
<br />
:: These sound like very hackable machines. Beyond expression, how do you do enforcement? --[[User:192.118.34.228|192.118.34.228]] 05:47, 18 October 2006 (EDT)<br />
<br />
:: Theoretically, just because a person is poor or lives in a poor country does not mean that he should be treated as a criminal. If a Western government sees fit to permit computer exports to the wealthy elite of a poor nation with mild copyright laws, they should not bar the way of computers sent for humanitarian purposes to their common people. If a wealthy American or European is allowed to buy a computer that may permit him to pirate software or music if he chooses to, the same should be true for Bolivian schoolchildren. But I fear that it may take a great deal of advocacy to try to persuade many people of this basic principle. Yet consider the irony: the poor of the world spend little if anything on music or software, so the actual cost of their violations to authors is exceedingly low - while the software they learn to create and freely distribute on these open-access systems will be of great value to everyone in the world. [[User:Mike Serfas|Mike Serfas]] 22:32, 25 October 2006 (EDT)<br />
<br />
:::Linux users do not pirate software, as a rule. This is because their software is Free. We will be promoting Creative Commons-Developing Countries licensing for other media, so that piracy will not be necessary. --[[User:Mokurai|Mokurai]] 18:45, 9 November 2006 (EST)<br />
<br />
=== Malware and Productivity Security ===<br />
<br />
How secure is the UI against virus, malware and other attacks? Because, it would seem that it wouldnt take long to infect all of Thailand's computers if they are all networked.<br />
<br />
:The OLPC doesn't run Windows. In fact it doesn't run standard Linux either.<br />
<br />
:The OLPC is designed so that the software in ROM can be easily and quickly be upgraded in the field. If we discover that someone is exploiting a security weakness, we can and will quickly fix it.<br />
<br />
::Does that not contradict itself? If it's field-upgradable, it's not ROM. If it's not ROM, then it's writable. If it's writable, then what keeps malware from writing to it?<br />
<br />
== Deployment Governability ==<br />
<br />
=== Government efficiency ===<br />
<br />
Also, I fear for the safety of the project, when you say the computers will be given to governments, who will distribute them to the people...We have all seen on TV the enormous amount of waste/inequality and abuse of power by governments of poor nations, that are given large handouts by outsiders. If food is wasted, and sold on the black market, you'd better be awfully careful with handing out computers! Even cheap ones! Why not get involved with teachers in schools in these poor nations, and head directly for the source instead of going through the middleman, and the buerocracy?.<br />
<br />
:Don't fear for the safety of OLPC. We don't have all our eggs in one basket; we are working with many different governments. If one government misbehaves, then they will be publicly embarassed because people can compare their behavior with other country governments. In particular, if Libya lives up to its promises then they will set a very high standard for other governments.<br />
<br />
:Also, the laptops will not be GIVEN to governments. The government must buy the laptops. And OLPC is not walking away from teachers and schools. On the contrary, we are developing working groups of teachers and school officials in the target countries to explain to them how the laptops can be used. We will provide ongoing support for these working groups and they, in turn, will support the teachers and schools in their country.<br />
<br />
=== Corruption ===<br />
<br />
I am concerned about Government abuse with this program. How would you monitor the Government of the country in which these laptops are distributed, to be sure that they go directly to the needy children? Some of these government officials are corrupted and might distribute these laptops to their relatives and friends with just a few going to the needy. How will this program be monitored? I am very concerned about this.<br />
<br />
:The OLPC cannot solve all the ills of the world. However we have gone to some effort to design a laptop that is unlike any existing laptops. The OLPC laptops are smaller than normal, slower than normal with less storage than normal. They are ideal for kids to use in education but not very useful for running a business or playing video games. From a cost-benefit point of view it would seem that a corrupt government leader would do better to spend their $100 million on something other than OLPC laptops.<br />
<br />
===Ownership and Selling of Laptops===<br />
<br />
If children are given the laptops, isn't it reasonable to assume that their families (most of which will assumingly be poor) might sell the laptops? I see the potential for a black market of these wonderful devices.<br />
<br />
I think the participant countries can reduce the possibility of OLPC theft and illegal resale by:<br />
<br />
# keeping the laptops at school and only allowing the kids to take them home if there are needs like homework and exams. <br />
# Making parents to sign a promissory note at the initial issue agreeing that they will do their best to take care of it when the child brings it to home.<br />
# The wifi adapter can be used to track stolen OLPCs.<br />
# In the countries with high OLPC theft incidents the government in the country can launch public awareness media campaign to educate the public that stealing an OLPC = robbing a child's future.<br />
# With cooperation from online auctions like Ebay they can ban/restrict the unauthorized resale of OLPCs.<br />
# Buy 2 give one free" program will reduce the demand for the OLPC in the developed world. Like rich first worlders willing to pay unreasonably high prices for the OLPC for novelty purposes.<br />
# As a more objective solution to the issue in your question, the UN child labor laws should be slightly altered to adapt the needs of the children today. What I mean by that is although it is wrong to exploit children by forcing them to work in dangerous manual labor jobs, if the IT companies want to provide them will opportunities to earn some money in exchange for doing some light programming or data entry jobs for limited periods it should be allowed. That way the OLPC will become a tool that they can use to earn money too and hence they wont need to sell it for food money :-)<br />
<br />
JK, USA<br />
<br />
:That is a risk. The main solution currently put forward by the OLPC (afaik) is flooding the environment with laptops (making them effectively worthless in a monetary sense since every child would have access to them, and through them, the whole community), and using social condemnation or stigma for when a person (adult) is known to have one (because after all the laptop is visibly a child's property). Now lets move to your items... :)<br />
:# the intent is for the child to '''own''' the laptop. Ownership is a much better deterrent when damage may occur. Depriving them (and their families) from access to it makes that sense of property disappear.<br />
:# signing a piece of paper would imply some sort of penalization if the 'deal' is broken... don't like it (personally)<br />
:# wifi tracker? maybe... but since MAC addresses (although burned) can be spoofed...<br />
:# campaigns should anticipate, not follow the problem - the damage will have been done already and the social stigma may be too hard to recover<br />
:# eBay and similar will most likely help if the problem arises<br />
:# a [[Buy 2 Get 1]] program ''may'' in some ways make the problem worse: why pay double if you can get it half-price?<br />
:# the [http://www.un.org United Nations] doesn't make laws - just treaties, conventions, and similar to be signed (and passed into laws) by each country. Exploitation is condemmed, the same as hazardous and other types of 'improper' work. The charter (afaik) doesn't forbid a child from performing work and participating in the family's well-being (that would be inaplicable in most of the world - even in the developed world) For the record, the [http://www.unhchr.ch/html/menu3/b/k2crc.htm Convention on the Rights of the Child] in Article 32 states:<br />
:#* 1. States Parties recognize the right of the child to be protected from economic exploitation and from performing any work that is likely to be hazardous or to interfere with the child's education, or to be harmful to the child's health or physical, mental, spiritual, moral or social development.<br />
:#* 2. States Parties shall take legislative, administrative, social and educational measures to ensure the implementation of the present article. To this end, and having regard to the relevant provisions of other international instruments, States Parties shall in particular: <br />
:#** (a) Provide for a minimum age or minimum ages for admission to employment;<br />
:#** (b) Provide for appropriate regulation of the hours and conditions of employment;<br />
:#** (c) Provide for appropriate penalties or other sanctions to ensure the effective enforcement of the present article.<br />
:Cheers --[[User:Xavi|Xavi]] 14:03, 20 January 2007 (EST)<br />
<br />
===Military use===<br />
<br />
While this issue is mostly overlooked, it may surprise you to know that XO hardware, being somewhere in between industrial and MILSPEC hardened, equipped with extremely sophisticated networking measures, makes for a very powerful tactical computer. with the right software changes, a lot of militias, insurgents or even third-world state armies would be happy to put their paws on a shipment. XO's relatively modest hardware can easily host an embedded combat application. moral considerations would also not be a deterrant to these kind of people. with some modification capability, such an organization can remove distinctive marks from the laptops.<br />
While all the components are readily available in the market, the research, development and integration effort is beyond the capabilities of most such organizations. by performing this service for them and shipping "free" laptops, there is potential for serious havoc.<br />
(I'm a retired c4l officer and a systems administrator and have dealt with tactical computing before).<br />
<br />
</noinclude> <!-- *********Please cut and paste answered questions to above this line******** --></div>Alexandros.Papadopouloshttp://wiki.laptop.org/mediawiki/index.php?title=User:Alexandros.Papadopoulos&diff=237137User:Alexandros.Papadopoulos2010-06-08T16:40:39Z<p>Alexandros.Papadopoulos: Created page with 'Not much to show here... I hope to be useful to this project. Based in the UK. Got experience with GNU/Linux, teaching, systems administration, documentation, IT security, consu…'</p>
<hr />
<div>Not much to show here...<br />
<br />
I hope to be useful to this project. Based in the UK. Got experience with GNU/Linux, teaching, systems administration, documentation, IT security, consulting, project management and a keen interest in education development.<br />
<br />
You may contact me by appending @gmail.com at the end of my username.<br />
<br />
Alex</div>Alexandros.Papadopoulos