> For the complete documentation index, see [llms.txt](https://x.ancorasir.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://x.ancorasir.com/me303-311/2020-autumn/project-work/workflow.md).

# Workflow

The project workflow is depicted below. The process leading to a functional alpha prototype is delineated by 5 major milestones: the design need review; the engineering feasibility review; the fabrication & cost review; the testing& optimization review; and the final presentation.

**A team** is comprised of **three task forces** that work in cooperative collaboration to generate design alternatives – the team works in full cooperation throughout the project towards an integrated prototype of waste sorting production line. Engineering specifications of the production line is prepared in advance with three functional machines to be designed: a splitting machine, a speedy picker, and a dex picker.

* The *splitting machine* functions by spreading the waste evenly on the conveyor belt to avoid stacking, making them easier to be picked up;
* The *speedy picker* functions by providing rapid picking capability using linear actuators with a suction cup, performing simple picks at a high speed;
* The *dex picker* functions by providing dexterous picking for wastes that are challenging to be picked using a custom gripper on a robotic arm.

Each task force of the team will pick a machine of their choice and be in charge of this machine’s design based on a predefined engineering need and budget. This is an effective way to ensure that the engineering designs generated fall within the need of clients when developed by a large team within a limited time frame. It also allows students to practice collaboration and cooperation within a smaller group (\~5) before working as a larger team (\~15).

![fig-workflow-new.png](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2FsZOINjsSckTnbg8BWBm4%2Ffig-workflow-new.png?alt=media\&token=4da96495-391e-42a5-9ab5-f8b6491ea3a7)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://x.ancorasir.com/me303-311/2020-autumn/project-work/workflow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.