Plans and Autoplan

For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs; this page is available as Markdown.

What is a plan?

A plan is a grouping of milestones/schedules (plan inputs) for parts and tasks (plan items) required to fulfill those milestones. Plans enable you to track progress against a factory schedule.

Creating a new plan

Plans are initialized by creating at least a single plan input as shown below. Below that is the results section, where plan items can be added to the plan.

{% embed url="https://www.loom.com/share/bba2f74891a8486abe269b2381efd882" %}

Plan items

Plan items can be added manually or automatically by using IONs MRP engine. To have plan items added automatically, move the plan to "In progress", click on "View MRP jobs" and click "Run MRP". It will take a few minutes for the job to run, but you can track the status in real time. Read about MRP in the next section to learn more!

You can manually create a plan item as well, as shown below.

A plan item represents a need for a part with optional start and completion dates. This need is fulfilled by linking a result, in the form of the inventory, runs, or purchase orders.

{% embed url="https://www.loom.com/share/19c27b77a4eb4ac6b813defcbe6a9082" %} Manually creating a plan item {% endembed %}

Plan items across all plans can be viewed from the Plan results page by clicking the "See all plan items" button:

{% embed url="https://www.loom.com/share/ce2d4d2af10c4ad28defb1fcb63cdb4d" %} Plan Results {% endembed %}

Plan items can be viewed here in flat or hierarchical format. Hierarchical will require clicking on parent plan items to display nested parts, while Flat will show all plan items.

Ready vs Not ready

Plan items for assemblies that have children will include a "Ready" or "Not ready" flag. "Ready" means that all child components are in inventory. This can be a helpful indicator when deciding whether to create a new run.

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://manual.firstresonance.io/plans-and-autoplan.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.