> For the complete documentation index, see [llms.txt](https://docs.idew.org/project-robotics/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idew.org/project-robotics/project-instructions/2-design-and-build-solution/2.2-robot-specifications.md).

# 2.2 Robot Specifications

{% tabs %}
{% tab title="✓ TASK" %}
Your team will create design specifications for your robot prototype (including its demonstration environment), as well as for a fully-functional version of your robot concept.

These specifications will build upon your team’s robot task scenarios. Review your existing robot task scenarios, and determine if any changes should be made. You can use [this template](https://drive.google.com/open?id=1tK8MlYiteU9xbp79sl2Vyf3QP6dMXMHNyP2PRwS0gmw) to document your team's final robot specifications.

{% hint style="info" %}
**MAKE A COPY:**  To use a template, be sure you're logged in to your Google Account. From the template's **File** menu, select **Make a copy**. Save the copy to your shared team folder in Google Drive. You can now modify it.
{% endhint %}

### SPECS FOR ROBOT PROTOTYPE

1. Briefly describe each task that your robot prototype will demonstrate. Include a diagram for each task (update the diagrams if necessary).
2. Identify which specific [navigation mode(s)](https://docs.idew.org/code-robotics/references/navigation-modes) that your robot prototype will use to complete its tasks.
3. Identify which specific [types of robot behaviors](https://docs.idew.org/code-robotics/references/robot-behaviors) that your robot prototype will need to perform to complete its tasks.
4. Identify any robot behavior(s) that will need to be **simulated** during the demonstration, and describe how these will be simulated.
5. Identify specific metrics that could be used to measure or evaluate the robot's task performance (such as:  accuracy, efficiency, avoiding errors, etc.).
6. Identify any parts that will need to be added to the robot prototype for demonstration purposes. Identify whether these parts provide aesthetic value, functional value, or both. Briefly describe how these parts might be constructed and added to the robot prototype.
7. Identify any objects or other features (surface lines, etc.) that will need to be added to the robot demonstration environment. Identify whether these objects and features provide aesthetic value, functional value, or both. Briefly describe how these objects and features might be constructed and added to the robot demo environment.

### SPECS FOR FULLY-FUNCTIONAL ROBOT CONCEPT

1. Briefly describe any additional functions or features that a full-scale, fully-functional version of your robot concept would have.
2. Identify any additional components (specific sensors, motors, etc.) that a fully-functional version of your robot would require. You may need to conduct research to verify which specific components would be feasible to use for specific tasks or behaviors.
   * For example, a GPS receiver has a margin of error of about 15 feet compared to its actual location – while that might be close enough for navigating a vehicle on roadways, it might not be accurate enough for your robot’s intended use.
3. Create a multi-view drawing (also called an [orthographic drawing](http://www.technologystudent.com/prddes1/orthogrp1.html)) of a fully-functional version of your robot concept, which may have different parts and features that your robot prototype won’t have. Include an image of this drawing in your specifications document.
   * The multi-view drawing should show the front, side, and top views of the robot. Include enough detail to show and label key parts (such as: sensors, etc.).
   * Be sure the height, width, and depth of the robot and its parts are drawn to scale. Use the same scale for each view.
   * Each view should be dimensioned by listing the real-life sizes (height, width, depth) of the robot and its key parts.
   * **OPTIONAL:**  You could use your multi-view drawing to also create a 3D digital model of the robot design using CAD software (such as:  [Tinkercad](https://www.tinkercad.com/), etc.).

## **❏ Deliverable**

Submit your team's robot specifications document
{% endtab %}

{% tab title="➤ EXAMPLE" %}
Example
{% endtab %}

{% tab title="★ RUBRIC" %}

| **✓- Below Standard** | **✓ Meets Standard** | **✓+ Exceeds Standard** |
| --------------------- | -------------------- | ----------------------- |
| Description           | Description          | Description             |
| {% endtab %}          |                      |                         |
| {% endtabs %}         |                      |                         |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.idew.org/project-robotics/project-instructions/2-design-and-build-solution/2.2-robot-specifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.