> 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/engineering-feasibility-report.md).

# Engineering Feasibility Report

### Overview <a href="#overview" id="overview"></a>

The Engineering Feasibility Report is a standalone, formal documentation of the machine design project that presents the detailed calculation in analyzing the design feasibility to narrow down the most suitable dimensions or part selection within the safety factors and engineering specifications, which the machine needs to satisfy an alpha prototype, paving ways towards a final product of engineering.

* A template is provided here, which should cover the sections explained the [guidelines](https://x.ancorasir.com/me303-311/2020-autumn/project-work/engineering-feasibility-report#guidelines).
  * Refer to your Feishu shared folder to edit the password-protected version, accessible only by all members of your team.
* The link to submission is here.
  * The deadline for submission is on [Saturday noon on Week 09](https://maindl.ancorasir.com/?page_id=929).
  * The review will be released [the week after](https://x.ancorasir.com/me303-311/2020-autumn/weekly-teaching/syllabus#week-10-engineering-feasibility-review).

The Feasibility Engineer is mainly in charge of the submission of the [Engineering Feasibility Report](https://x.ancorasir.com/me303-311/2020-autumn/project-work/engineering-feasibility-report) on behalf of the task force, but all members of the task force shall be involved or consulted while preparing the report, and it is the Feasibility Engineer’s job to properly allocate any necessary sub-tasks to the rest of the task force towards a working report submission.

It should be noted that when conducting specific calculations and analysis of the design, it is common that many changes will be involved to resize, redefine, and redesign many aspects of the original design, considering the engineering fact and limitations. Therefore, it is critical for the feasibility engineer to keep updating the feasibility analysis throughout the design process by listening to the feedback from the task force and the team, making informed decisions on the necessary changes to the engineering design, and making sure that a feasible design is being selected during the process.

### Guidelines <a href="#guidelines" id="guidelines"></a>

A template is provided in your task force’s shared Feishu folder as a Feishu Doc, which can be simultaneously edited by all members on the browser as a collaborative effort. Don’t worry about making changes to the document, as you can access historical versions of the final while preparing it.

* General:
  * Report Name: Engineering Feasibility Report by \[Red/Green/Blue/Yellow] \[Apple/Banana/Cherry] on \[Machine Type]
  * Task Force Members: @ all members of the task force
  * Submitted by: @ Feasibility Engineer
  * Reviewed by: @ Fabrication Engineer @ Assembly Engineer
  * Date & Version: YY-MM-DD-V1.0
  * \[Proper use of document style is highly recommended to stay the file organized.]
  * \[Use the build-in Print function of Feishu Doc to save it as PDFs before making the submission.]
* Report Overview
  * Briefly clarify the specific Design Proposal this feasibility analysis is referring to \[Design Proposal 1/2/3/others?]
  * Briefly explain how you understand the feasibility analysis and your method of analysis \[How did you do it?]
  * Briefly summarize the key outcomes of this report \[what you have achieved in this report?]
* Feasibility Analysis
  * Analyze the design in detail to properly select the dimensions of all parts within safety factors. \[consult chapters 18 & 20 in the textbook]
  * Analyze the design in detail and make adjustments accordingly to make sure it meets the engineering specifications.
  * Explain the compromises you have made in sizing the parts and dimensions \[is the design feasible to move on to fabrication?]
* Engineering Drawings with Dimensions
  * Provide screenshots of the CAD drawings with detailed dimensions and mark with notes \[translate your feasibility analysis into engineering dimensions]
  * The engineering drawing in this section should be ready for consultation towards machining \[help the fabrication & assemble engineers to move on]
  * Indicate the Feishu folder where the CAD files are stored, and add all notes necessary when using these files.


---

# 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/engineering-feasibility-report.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.