GMS Roles & Procedures


GMS Roles & Procedures. 1

GMS Engineer (Local model). 1

Qualifications. 1

Training. 1

Role Procedures. 2

GMS Engineer (Cloud model). 2

Qualifications. 2

Hours. 2

Training. 2

Role Procedures. 3

Tablet Organization Manager. 5

Qualifications. 5

Notes. 5

Hours. 5

Training. 6

Role Procedures. 6

GMS Developer. 6

Qualifications. 6



Each event needs at least one dedicated volunteer to support and operate GMS. Most events use the Cloud Model and staffing the GMS Cloud Model Engineer will be sufficient. The Tablet Organization Manager (TOM) role is broken out just so that it can be staffed by an enthusiastic student volunteer. The Cloud Model is described separately.


GMS Engineer (Local model)

Events using the Local model have their own dedicated GMS server. The GMS Engineer will be responsible for setting up and operating the local server, in addition to performing all the tasks described for the Cloud Model Engineer. This requires a lot more dedication, technical expertise and training than for the Cloud Model Engineer.





Role Procedures



GMS Engineer (Cloud model)

The GMS Cloud Engineer is responsible for operating GMS at the event site. They work with the GMS Developer and will be the onsite contact point for GMS at the Event. They do not have to set up or operate the GMS server, as that is done by the GMS Developer. They also have the responsibilities described for the Tablet Organization Manager (TOM).



The GMS Manager should be available for:

-       Have a tablet & laptop handy

-       About 2 hours to set up tablets, then charge them overnight

-       From before Robot Inspection starts

-       till after the matches end.


Role Procedures


-       Talk with local IT administrator

-       Get event footprint and WiFi coverage

-       Get access credentials (SSID & Password)

-       Get WiFi authentication options: open/guest, SSID/Key auth, secondary web page

-       Try to get access to the Event Site Staff (teachers') network

-       Discuss above details with GMS developer (Raj)

-       Visit site and test WiFi quality (extra credit option)


-       Tablets, stylus

-       Chargers, charger cables

-       Laptop

-       Tablet Signout sheets:

-       Commemorative stickers:

Stock: Avery 5160, 1" x 2-5/8"


-       charge overnight

-       connect to any WiFi with Internet access, install any updates, including GMS

-       delete files: pictures, GMS folder, browsing history

-       sanitize with alcohol wipe

-       set up WiFi for event using QRM


-       A laptop with GMS installed must be provided

-       Connect to your event server in cloud

  Verify that it is receiving Sync updates

-       Add/delete teams at event (rarely necessary)

-       Get and configure User list & Roles

-       Make Pit Map

-       Update WiFi credentials in GMS,

-       Start the Backup Server (it may be already started.)

-       Test WiFi configuration on tablet using QRM display

  Briefly make the Backup the Master by turning off Sync


-       Get Event specific Cloud Server details from Raj. (Host, Port, etc.)

-       Check with Raj to verify that the GMS Cloud Server is set up and available for testing.  The server address and port number may vary from what is shown below.

-       Start with an Android or Fire device, preferably a tablet. Turn the volume up, so you can hear if GMS beeps for help. Enable error display. (Menu Settings Vibrate & Toast.)

-       Connect device to the event site WiFi.

-       Login: demo / demo / LRI / Online. Use Cloud Server details.

-       Walk around to find dead spots.

-       Check WiFi in Lunch and Break Rooms. Users expect GMS to work there.


-       See


During Event

-       install Practice schedule if available (rarely)

-       make and update Pit Map

-       add additional users

-       add/change user roles

-       reset user passwords

-       force logoff users (mostly for fun)


-       see role details below


-       Switch the Backup laptop from "Backup" to "Master" mode.

  Tools Configuration, "Sync from Master": No Sync.


-       Power up the preconfigured supplied WiFi AP,

-       Display a Setup QR code on the laptop and use it to quickly re-configure all tablets. That is it. Done.

This switch should take about 10 minutes. The backup server will be used for the remainder of the event; there are no procedures to revert back to the cloud model. The 'emergency' WiFi coverage may be limited to about 100' from the LRI desk, and Inspectors will have to approach the LRI desk periodically to update their tablets.


After the event

-       tablets, styluses, chargers, power cords

-       Laptop

-       Incidents, failures

-       Lossage

-       Feedback, complaints, and frustrations (suggestions for improvement.)


Tablet Organization Manager

The Tablet Organization Manager (TOM) will manage the 14+ tablets and be responsible for them during the event. They can provide some limited support for GMS tablets. This person in this role typically assists and reports to the onsite GMS Engineer. This role could be staffed by a student.



MADAM: Mobile Android Device Administrator / Manager


The TOM should be available:

-       From before Robot Inspection starts

-       till after the matches end.


TOM Training will be a 1/2 hour session prior to the event. After a brief overview, an event will be simulated. Trainees will perform each of the tasks described in the Role Description above. Best practices (listed below) will be discussed.

Role Procedures

-       Explain that stylus is to be returned

-       Hand out an alcohol cleaning pad

-       Get user signatures AND phone number on Sign-out sheet

-       Don't lose the Sign-out sheet

-       scrolling, swiping

-       bringing GMS to forefront

-       picture taking with camera

-       Auto rotate, screen lock, volume, etc

-       Reset user passwords or change user roles during the event.

-       Add new users

-       verify return of stylus, charger, power cord


GMS Developer

The functions are:


This role is Raj. :-)