> 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/teams-and-resources/budget-and-purchasing.md).

# Budget & Purchasing

### Budget <a href="#budget" id="budget"></a>

Each team has a budget of 10,000 CNY to purchase materials, supplies, and resources for the project. These resources have been generously provided by the BionicDL lab and donated by course sponsors.

Working to finish the projects on-time and on-budget are key lessons in the course. The project budget is important. Your teams must plan and work to keep their projects on budget. There may be budget extensions under extenuating circumstances with the approval of the course instructor. If there is an **unplanned**budget overrun that is not discussed with the instructor, each team member will pay an equal portion of the deficit.

Lab instructors should help their team plan on how they should allocate financial resources over the term. However, a rule-of-thumb is that teams should reserve roughly 5,000 CNY for the alpha/final prototype phase of the project.

The budget for each project will be managed by team financial officers, and there is a code of ethics that *must* be followed when making purchases.

### Purchasing <a href="#purchasing" id="purchasing"></a>

To be edited

### mainDL Store <a href="#maindl-store" id="maindl-store"></a>

To facilitate the course experience, our technology consultants developed the [DesignAIR](https://x.ancorasir.com/me303-311/2020-autumn/teams-and-resources/designair-system) system with custom support in cloud-based engineering design, which comes with an integrated purchasing service to ease the procurement process of the various purchase requests throughout this course.

#### Team & Student Account <a href="#team-and-student-account" id="team-and-student-account"></a>

All students will be assigned with an account, with all roles defined. Each student can raise a purchase request within their team, which will be approved by the financial officer, after which the request will be sent to the administrator assistant for processing and the course instructor / lab instructor / workshop instructor for review of any potential problems or suggestions.

After the purchase request is submitted and approved, our collaborators at the mainDL store will start the procurement process and will get back with the student designer that raised the purchase order to resolve any further details or feedback of this request. The shipping address in also provided at the bottom of the page.

Each members of the task force and the team will be able to review the overall budget record throughout the process and collaborate together.

#### For items available in the mainDL store <a href="#for-items-available-in-the-maindl-store" id="for-items-available-in-the-maindl-store"></a>

To be added.

#### For items not available in the mainDL store <a href="#for-items-not-available-in-the-maindl-store" id="for-items-not-available-in-the-maindl-store"></a>

To be added.

#### For custom fabrication service through the mainDL store <a href="#for-custom-fabrication-service-through-the-maindl-store" id="for-custom-fabrication-service-through-the-maindl-store"></a>

To be added.

### Shipping <a href="#shipping" id="shipping"></a>

For orders delivered to SUSTech, please use the following address:

Southern University of Science and Technology\
1088 Xueyuan Road\
Room 606, 7 Innovation Park\
**YourName**, c/o Team **YourColorAndTaskForce**\
Shenzhen, Guangdong 518055

广东省深圳市南山区学苑大道1088号创园7栋606室\
南方科技大学，518055\
你的姓名，**你的团队颜色以及任务分组**

When the order arrives make sure you **save the receipt** and give it to your financial officer.

You can contact your Teaching Assistant to see if your package has been received.


---

# 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/teams-and-resources/budget-and-purchasing.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.