Annual Operating Plan (AOP) build
Construct the company-wide budget for the coming fiscal year across revenue, headcount, opex and capex. Involves top-down targets negotiated against bottom-up cost-center submissions.
must happen before
3A hard sequencing dependency: the target cannot correctly start until the source is done. The note gives the reason.
There is no variance without an approved baseline to vary from.
Quotas are derived from the approved revenue plan. Setting them first guarantees the sales plan and the financial plan disagree from day one.
The reforecast is measured against the approved plan, and inherits its driver structure.
consumes
3A canonical data object the task needs as input.
owned by
1The business-partner org unit accountable for the task.
runs in
1The end-to-end shared-services process the task sits inside.
serves
1The verb-level intent the task exists to satisfy.
performed in
3Software the task is actually carried out in.
Relationships pointing at this node.
depends on
2A hard sequencing dependency: the target cannot correctly start until the source is done. The note gives the reason.
The driver structure has to be settled before numbers are loaded into it, or the plan becomes a set of hardcoded line items that cannot be reforecast.
Headcount is the largest and least reversible cost line, so the plan is built around the hiring plan rather than the other way round.
performed by
2A job title someone actually holds does this work.
Unresolved from the source registry
not yet modelledFree-text strings from the source spreadsheet that have not been resolved to a node. Preserved verbatim so nothing is silently dropped — these are backlog, not content.
Produces: Consolidated AOP model · Cost center budget templates