Lab Policy for Operating Spot

Principles

Human safety first, robot safety second
Leave the robot as you would want to find it
Know what to do before you have to do it
Maintaining the robot is part of using it
Understanding the robot is key to using it safely
The operator is responsible for bystanders. Do not assume that bystanders understand the robot
Share your experiences with other Spot operators
Think as a community of robot users

There must be at least one authorized user present when Spot is handled (even if it is powered off).
Authorized users must have completed the required reading and received authorization from the PI.
The Boston Dynamics procedures and safety instructions should be followed (authorized users will be familiar with them). Lab policies extend these.
Authorized users are expected to stay current with the Slack channel and Wiki updates.
The Spot may only be touched in the presence of an authorized operator, even if it is powered off. The controller (and robot) should only be powered when an authorized operator is present.
When taking Spot out of the lab for approved demos and events, be prepared to respectfully and thoughtfully answer questions from the general public about the robot. That includes knowing basic things about the robot (weight, battery-life, AI smarts (can Spot take over the world? -- this question does come up occasionally)). And knowing how different people in the Lab are using the robot so that you can explain its research purpose and what we hope to accomplish with it. Additionally, be prepared to operate Spot in a manner that makes the general public feel safe around the robot, while reminding people to stay 2 meters away.

Before powering on the robot, log your usage in the paper usage log.
Ensure that printed operating procedures are handy before using the Spot.
Check the battery charge. If the battery you are not using is not charged, consider this as an opportunity to charge it.
Ensure that you will have enough time to clean up properly after using the Spot.
Make sure you are current with the #spot channel on Slack.
Follow the Boston Dynamics Startup Procedures. This includes inspecting the robot and battery.
To lift the robot, two people are required. Rolling the robot can be done by a single (careful) person.
Before powering on the robot, tell all bystanders not to touch the robot while it is powered on, and to maintain a 2 meter distance when possible. Inform all bystanders that the Spot is not a human-safe robot, and point out pinch points (arm and legs).
If you intend to power up the robot while it is lying on its side (to install the battery) you should leave enough space around the robot for it to "self-right".
While it is permissible for an authorized user to use the robot in the lab by themselves, it is advisable to have another person around (in case the robot needs to be moved when powered off). If you are alone in the lab, have someone you can call if you need help.

At least one authorized user must be present. (this bears repeating)
The Spot may not leave the lab unless two authorized users are present, and the outing has been cleared with the #spot channel on Slack and has Prof. Gleicher's approval.
All users should attempt to maintain a 2 meter distance from the robot when it is powered on. A user should only be within two meters of the robot when they are paying close attention to it.
It is the operator's responsibility to warn bystanders, and keep them an appropriate distance from the robot.
Avoid touching Spot while its motors are powered on (e.g., the motors are not locked out). Only get close enough to touch the robot if you are paying careful attention and know that no movement commands will be issued to the robot. Be as certain as possible that the robot will not move (but always be aware that unexpected movements are possible - for example, for self-balancing).
When trying something new (with the controller or via the API), inform all bystanders and maintain a 2 meter distance from the robot.
Follow the Boston Dynamics guidelines. For example, if something happens, have the robot "sit". Avoid the "emergency stop" which causes the robot to lose power and collapse, unless there is a really good reason to do so.
If anything potentially anomalous or dangerous happens, have the robot sit.

Put the Spot in its designated storage place (marked by TBD). It is best to walk the Spot to this place before powering it off.
After powering off and putting away the robot, log the end time of your usage in the paper usage log.
Battery must be removed from robot OR robot should be connected to shore power at the end of a session. If a battery is left in the robot, even if it's OFF, without connecting to shore power it will drain completely and become damaged. If you will be around while it charges, charge the battery to full before putting it away. Do not leave the battery charging overnight. If you leave the battery uncharged (because you are leaving), coordinate to get it charged.
Plug in the controller to the USB-C cable next to the paper usage log. The controller can stay plugged in when not in use.
Do not place the Spot in its storage box unless you intend to transport it (or know that the next user needs it in the box).
Be present when charging the battery. If you know the battery is uncharged and you are around the lab when no one is using it, charge it. (charging the battery should be done only by authorized users).
If anything unusual happens, or there are any problems, note it in the slack channel and inform the PI.

Coordinate with other Spot users about usage. Be considerate of others' deadlines / needs.
Coordinate with other Spot users about any hardware modifications to the robot (e.g. adding a gripper, changing sensors) to make sure that your modification is compatible with their use cases. Try to leave the robot in the state that the next user will want it in.
Do not make software updates to the Spot (or the controller) without checking with all other authorized users who may be effected (i.e. everybody using the API) and receiving permission from the PI. Announce changes before and after they are applied.