Proposals and current plan
Proposal
Section titled “Proposal”A proposal is a computed plan that has not yet been accepted.
| Field | What it is |
|---|---|
| Start date | From when the plan starts |
| Orders | Which orders are included |
| Base plan | The current plan it starts from, if there is one |
| Objectives and constraints | Those of the project or a set specific to this proposal |
| Status | Where the computation stands |
Statuses
Section titled “Statuses”draft → queued → computing → planned ↘ failedComputation is asynchronous: the proposal is queued and the interface remains available while it is optimised. Several proposals can be computed at the same time with different priorities.
Current plan
Section titled “Current plan”The current plan is the accepted proposal: the plan being executed. When a new proposal is accepted, the previous one moves to the history, so you always know which plan was current at any moment and who accepted it.
Starting from the current plan
Section titled “Starting from the current plan”A proposal that starts from a base plan inherits as fixed:
- tasks that have already started;
- tasks someone has fixed by hand;
- optionally, only those already started (and the rest can be moved).
This way, a new order or an incident does not disrupt what is already running.
Outdated proposals
Section titled “Outdated proposals”If the data a proposal was computed with changes (an order, a resource, the current plan), the proposal is marked as outdated. Nobody accepts a plan computed on old data.
Comparing
Section titled “Comparing”Before accepting, the proposal is compared with the current plan: the indicators of each, which tasks or orders move and what the change costs. See Result of a plan.