Technical Reference
Data Model and Schedule Lifecycle
The desktop application keeps reusable definitions separate from event-specific task instances, then records optimiser and final values without overwriting the original planning intent.
Schedule data lifecycle
Publishing copies a deliberate final state. It does not expose the working project database.
1
Planning inputs
People, capabilities, locations, templates
2
Task instances
Editable event-specific work
3
Optimised result
Suggested times and assignments
4
Final schedule
Reviewed tasks and assignments
5
Published copy
Full event or selected dates
Planning entities
| Entity | Responsibility | Important relationships |
|---|---|---|
| Event | Planning and publishing boundary | Contains people, task instances, schedules, and integration state |
| Person | Assignable participant | Capabilities, group memberships, availability, and location state |
| Capability | A qualification or assignable property | Used by task requirements and held by people |
| Group | A typed collection of people | Membership and role information can affect planning |
| Location | A task or person position | Fixed locations and solver-selected any-location work are supported |
| Task type or template | Reusable task definition | Seeds event-specific task instances without becoming their live schedule |
Task instance states
A task instance is the editable event-specific unit. Its planning fields describe requirements and allowed timing. Its optimised value records the solver result. Its final value records the reviewed schedule, including deliberate manual changes.
Finalisation and publishing use the current final schedule where available, with the optimiser result retained for comparison. This is why the interface can report manual changes after optimisation without losing the original result.
Publishing boundaries
- Destinations: any combination of Google Calendar, MP-OPT Server, and local PDF; an empty selection disables publishing.
- Scope: the whole event or the currently selected date, depending on the publishing action.
- Representation: the private Masterplan and public General Schedule are distinct datasets.
- Web edits: saved edits are shared server-side overlays; unsaved browser drafts are local.
- Replacement: a publish replaces the covered published scope and clears applicable web overlays, while unrelated dates remain untouched by a date-scoped publish.