Planning foundation
Products, customers, horizons, versions, lines, roles, and review cadence.
Support
Help that starts from the exact planning evidence.
Support covers the planning process itself: setup, version control, signal quality, supply response, role boundaries, workflow controls, and the questions that surface during review.
Support that follows the evidence trail.
Complex planning becomes easier when help uses the same controlled objects and decision vocabulary as the team.
Signal and scenario quality
Impact, confidence, feasibility, capacity, cost, and record relationships.
Workflow boundaries
Submission, constraint escalation, and approved consensus publication.
Daily planning use
Version comparison, review preparation, decision capture, and plan traceability.
Common questions.
The fastest answer begins with the actual version and review state, not a generic planning category.
Can we keep multiple forecast versions?
Yes. Versions carry their own horizon, status, and linked lines so draft, submitted, consensus, and locked snapshots remain distinct.
What happens when supply is constrained?
The scenario records available quantity, cost, and feasibility. A constrained state can add an internal exception to the scheduled review without silently changing the plan.
Who can publish consensus?
Your assigned roles and approval policy determine authority. Publication follows a recorded consensus decision with quantity, type, and rationale.
Where does Proto Agent fit?
Proto Agent helps people work with the planning application, understand evidence, and adapt processes within ERP.ai and available usage.