System Requirements for 3Ts Project
The 3Ts project has been envisaged as a tool to bring together a community of interested, dedicated
and repeat travellers/off-roaders of Ladakh, and organizing and channelizing their interests to divert
some attention and support to remote and ignored schools of rural Ladakh
The first phase of this project, has an aggressive go-live timeline of early-mid July 2012, to target the
beginning of the trekking season of Ladakh, which starts by mid-June and ends by October. Keeping
in mind the timeframes, 17000 ft. has already started geo-mapping schools, a target of at least 200
of the 981 to be achieved by mid-June 2012.
A smart phone app to also be developed during that timeframe to enable the trekkers to store
information offline. Since a majority of these schools have limited to no data coverage, and takes
days to reach, it is important to capture the experiences of the traveller when he/she is in the school
rather than depend on him to upload it at a date which is probably weeks down the line.
This first phase is planned as an extension of the KLP project with minimum customization to capture
the essence of the project.
User Profile
The 3Ts project has a specific purpose. To involve the travel community that moves through Ladakh
and who can be relied upon to provide information and help to the remote schools of Ladakh. We
have broadly categorised the these travellers into the following profiles.
Types of Users
 Casual Visitor
 Volunteer
 Trekker –
 Off Roader
 Tourist
 Monastry Circuit Visitor
 Student Groups/Travel Groups
 Tourist Operators
 School Headmaster/Teacher
 Government Official ( Village Councillor / Cluster Head, DoE etc. )
Use Cases
Based on the profiles mentioned above and the requirements of phase I, we have simplified the use
cases into the following three scenarios
 User knows exactly which school he wants to visit
 User is a traveller/off-roader/trekker and has a specific itinerary that he has already decided
on.
o The itinerary can either have a specific name, i.e. Marka Valley Trek, or can be a start
to finish, for e.g. Spituk to Hemis
o The trekking routes and the off-roading routes are completely different and will
have a completely different set of villages on the route.
 User is on a monastery circuit and would wish to visit all monasteries/nunneries, most of
which have attached schools.
Back End Data Gathering Limitations
Owing to the sheer distances, altitudes and inaccessibility of some of these village schools, it is
impossible for 17000 ft. to Geo-Map all of these before the go-live of the site. Which therefore
implies that only a partial list of all the schools will be mapped. However, we would not want it in
anway to hamper the usage of the site, as we can use the very trekkers that we are targeting, to
even geo-map each school and add it back to the site. – Point to be discussed with KLP Team
Customizations to Basic KLP interface
The visualization of the first phase of the 3Ts website is being seen as a customization of the KLP
website, with minimal changes to flow, addition of the layer of trekking route information, and only
simple interface changes.

Legend Menu on top – Currently, we do not wish to display the District, Block, Cluster etc.
Level info, even though we have the data. We still have to think it through on how the
interface will appear to a traveller and if it is useful. However, if it is too much of a
customization to remove that visualization, it can remain.

Main Page
o Would need a link for the download of the Mobile App
Map Display
o Am not sure if all the villages of Ladakh are already mapped on Google Maps or
whichever other source you are taking the map from. Do you need anything from us
on that ?
o Given the possibility that a lot of the schools would probably not be geo-coded, how
can we handle display of those schools. We do not want to lose out on that
opportunity to have them geo-coded through trekkers.
Search ( This is the area which will require customization )
Based on the user profile and the type of routes that a traveller can follow, following is the
user interface that we have envisaged. ( Please feel free to suggest alternatives, as we think
this is a little clutzy! ).
Search for a school
 I know the school name that I want to go to.
o School name to be entered ( preferable to be a drop down or a
suggestive list, as the spellings differ vastly )
 I am a traveller, show me the schools on my route
This needs to be broken down to the 3 kinds of travellers, i.e. Trekker, Off Roader
( biker, bicyclist , safari etc) and Monastery visitor ) So, there could possibly be
icons for each kind of a traveller.
 Trekker
o Enter Trek Name
OR
o Enter Start and End points
 Off roader
o Enter Start and End points
 Monastry Visitor
o No inputs here, all monastery schools will show up
Detail Page for school
While we would like to keep this page essentially similar to the KLP page to minimize
customization, the usage is a little different than was envisaged for KLP. We would like it to
be an active sharing page rather than an information gathering page. Like Megha mentioned
in an email reply earlier, what is really needs is an active content area which can take in user
inputs as well as integrate with social media sites. We leave it to the KLP team to suggest on
the best course of action at this point. Couple of essential changes would be



o






A content area where 17000 ft. can post updates/requirements, which will not be
tied to other user updates and needs to be always visible. ( Probably on top of the
page )
o The active content area for user sharing to be moved up in the page and the rest of
the RTE data gathering to be moved below. ( Emphasis on experience sharing, rather
than on information gathering )
o We would probably reduce the number of criteria / check boxes that would be
gathered
User Database
o Is there a login / user database being captured in the current version ( I do not see it,
but if it exists in the database, can it be used ? )
Social Media Integration
o As mentioned, it would be nice to have updates on the 17000 ft. FB page, as well as
the user’s page, if he desired so. We would prefer updates to our page to be
moderated, of course
Updates
o Would need to be moderated
Database Structure
o Will send you table structure of the extra information needed for 3Ts, in a day or
two. Will need to discuss Search Criteria information in detail before we can freeze
that.
Data
o As understood, we will give you data from DISE for Ladakh schools, are there any
other sources that are being pooled ? We couldn’t find the DISE ID, so if you could
tell us where that is, we can take a look at it again
o Question for the future - Does DISE have its own API, or would we have to store and
update our own copy of the Data periodically ?
Mobile Interface
o Currently, this is envisaged as a tool that will capture images, some text, geo-code
and the name of the school on site and will be synced to the web server on
availability of data connectivity. So, in essence, the data that would be coming to
you would be
School Code, School Name, Lat, Long, experience(text), email id, timestamp, pic1 –
pic x ( x can be frozen to say 5 )
o Will send separate attachment of Mobile Module System Requirements