iriss Space Robotics Competition
ANNEXE
1
LETTER OF INTENT
Information: The purpose of the Letter of Intent is to not only register in the
competition but also to let ESA and organisers know the details of your team,
the team composition. This will be checked against the competition rules for
eligibility.
Please use whenever possible letter headed paper (school, robotics club etc)
and submit in PDF format to [email protected] before 6th February
2015 at 23:59.
Be sure your letter contains the following:Introductory paragraph
State your motivation for joining the competition.
State previous experience in robotic activities (if any).
State previous activities involving space or space education (if any)
State possible strategy and any information on what type of robot will
be used/built (if any)
State expected workload anticipated (hours per week per person)
State any expected external support (technical/financial) (if known)
State strategies of outreach and communication at local/regional level
(if known)
Details of the team
Team Name:Team logo (if any):Team motto (if any):Number of team members (students):Team Leader name (adult supervisor):Team Leader contact details:
-email address
-phone number
-backup phone number (i.e. mobile phone)
-postal address
Team member details (exactly as below)
-First name, Last name, birthdate (DD/MM/YYYY), sex
Jorge, Diaz, 03/12/1997, male
Ruth, Barton, 16/05/2000, female
IMPORTANT Please note that copies of passports are required
to access ESA sites, any discrepancy in submitted age in this LoI
and passports at the Gatehouse will result in disqualification.
3) Signed and dated by the Team Leader.
1
iriss Space Robotics Competition
2
PDR
2.1
Video
Teams should submit a 5 minute video to YouTube and mail the link to
[email protected] before 6th March 2015 at 23:59.
The video is important as the quality of filming, presentation, use of language,
use of graphics could lead to a multiplier constant (see section 8 in main
document)
The video should include:
-Team name / logo if any
-Presentation of the team members
-Presentation of the strategy currently under consideration (i.e. robot type,
multi cargo per trip, additional camera, colour sensing for hazard avoidance,
comms setup)
-Presentation of capabilities of robot prototype (if any) (load lift, camera,
comms setup, ..)
The video should be preferably uploaded to YouTube in HD quality. Please
keep your links hidden and unsearchable.
2
iriss Space Robotics Competition
3
CDR
3.1
CDR Documentation
Teams should submit to [email protected] the following template (at
end of document) correctly filled in by 22nd May 2015 at 23:59.
Please remove all text in grey in the following pages, these are guidelines.
The process of building a robot or hardware for the ISS is very complex and
costly. That is why, in a real mission, there are some documents that have to
be delivered before, during and after space hardware is built. These
documents serve to provide detailed information about the hardware being
developed and to ensure that it complies with all the requirements regarding
the mission.
The process of designing and building your robot is much simpler than the
one followed for a real space hardware. Nevertheless, we believe that exposing
students to good engineering procedures will be very beneficial for their
educational experience.
These guidelines provide information about the expected content of each
phase. This information will ensure that the work you are doing is aligned
with your mission goals and it can help us to identify possible problems at an
early stage. It will also help us to determine that your robot will be able to
behave according to the mechanical and safety requirements.
Attached to this document there is a blank design document with a given
structure that you can modify to describe all the aspects of your project. There
is no limit to the number of pages used but it should be well-structured and
appendices should be used for detailed information to keep the main body of
the document as concise as possible. This detailed information may be e.g.
technical drawings or component datasheets. The documentation should be
written in a clear and concise manner that allows a person who is not a
member of your team to understand its purpose and design.
The design document should provide ESA with all important information on
the robot. The chapters can be modified and additional sections can be added
by the team if appropriate. The design documents will be used for establishing
who goes through to the next phases.
In general, these documents should convey the following information:
• The work that has been completed
• The work that is in progress
• The work that remains to be done
• Any problems, complications or other issues you have encountered
3
iriss Space Robotics Competition
•
A general overview of how the project is going
Documents consist of 4 parts:
1. Progress statement summary (1-2 paragraphs)
2. Task list
3. Detailed project status
4. Your Design Document
1. The progress statement should consist of 1-2 paragraphs (max). This is
a general lay-man statement to give the public an idea of how things are
going with your project.
2. In the “Task List” section, you should break down the project work into
a list of individual tasks, and indicate which ones have been completed,
which ones are in progress, and which ones remain to be done.
3. In the “Detailed Project Status” section, write any comments you have
about any specific issues you are having, and let us know how the
project is going in general. Although there is no minimum length for
this section, we encourage you to go more in-depth here than with the
progress statement.
4. As your project progresses, you should be constantly updating your
“Design Document” to reflect the work you have done.. When
completing the CDR, fill in as much information as possible based on
the current status of the project.
3.2
WebEx
At a date to be defined later in the competition, ESA shall organise televideo
conferencing with the teams. This session should last approximately 15
minutes. The content of the 15 minutes shall be as follows:
-Brief presentation of the team and its members (±2 minutes)
-Announcement of any team changes since the beginning of the process
-Presentation of the robot in detail (whether breadboard or final) (±7-8
minutes)
-please use slides (powerpoint, keynote, PDF are all acceptable)
-please cover most topics in the design document
-please discuss problems encountered and proposed workarounds
-ESA/ASI expert questions to the team (±5 minutes)
We expect the students to participate in this telecom and the team leaders to
only step in when absolutely required.
4
iriss Space Robotics Competition
All that is required for WebEx is a computer with a (USB/FireWire) camera
(built in is ok but external is preferred) and external microphone (USB or
audio in). Tests will be performed in advance to the teleconference to ensure
compatibility of your hardware.
5
iriss Space Robotics Competition
CDR DOCUMENTATION
template
6
iriss Space Robotics Competition
PROGRESS STATEMENT SUMMARY
7
iriss Space Robotics Competition
TASK LIST
in progress High level task
in progress Lower level task
done specific task
done specific task
in progress specific task
not done specific task
in progress specific task
not done specific task
done Lower level task
done specific task
done specific task
done specific task
8
iriss Space Robotics Competition
DETAILED PROJECT STATUS
9
iriss Space Robotics Competition
DESIGN DOCUMENT
1
ROBOT DESCRIPTION
Mechanical/ structural design
Describe the mechanical design, the material used for the robot structure
and how every component is mounted to the structure. Identify the major
components of the robot and include a preliminary drawing or picture of
how the robot structure will look and where the major components such
as main board, sensors, transmitter, and battery will be placed.
Include mechanical drawings and a list of parts. Explain what each part of
the robot does.
Electrical design
Describe the electrical interface (and selected components) of the robot –
you can use electronic drawings.
Provide a power budget, detailing how much power each component
consumes and battery capacity. Make an estimation of the power
consumption and the duration of the batteries.
Since batteries are used, give their type and number.
Software design
Describe the software design of the robot and how is expected to work
and detail the On-Board Data Handling (OBDH).
10
iriss Space Robotics Competition
Give a flow diagram of the software program flow. If applicable, describe
different software modes.
Indicate what programming language(s) and development environments
are used.
Communication design
Give details of your communication mechanisms and protocols used
between GCC and your robot.
2
PROJECT PLANNING
Time schedule of the robot preparation
Provide a schedule that includes the phases of design, prototyping,
construction, testing, and all key dates.
Resource estimation
Budget
List all the foreseen costs in a table form.
External support
List
the
organisations,
departments
or
companies
that
provide
sponsorship or in-kind support. For example, professors of a university or
institute, local companies or nearby research laboratories, facilities to
which access is possible, etc. Mention any support or expertise which is
lacking.
11
iriss Space Robotics Competition
Test plan
Describe all the tests that will be performed in order to verify that your
robot can carry out the required tasks on the Taskboard.
You can add videos, graphics or pictures.
12
iriss Space Robotics Competition
3
OUTREACH PROGRAMME
Outline the approach to publicising and communicating about your
project.
Describe the team’s website or blog (if any) and how it is planned to
evolve.
Include a summary list or table of all outreach actions performed and
media coverage received. This should include:
•
The URL of the website / blog
•
Any performed outreach actions, e.g. publishing press releases,
contacting journalists, designing a logo or information brochure
•
Details of media coverage, e.g. newspaper articles, radio / TV
interviews, internet news articles, etc
•
Presentations given by the team members, e.g. at the school or a
local event
•
Exhibitions of the experiment, e.g. at a fair or school open day
Attach copies or photographs of the above if possible and include
reference numbers in the list.
13