Configure Season-Amount Readiness

A fixed seasonal commitment and its payment dates become visible for planning without pretending that each crossing creates another owner charge.

Track

Accesses & Agreements

Phase

Season commitment

Starts with

Agreement without seasonal readiness

Ends with

Season commitment configured

The situation

The Agreement uses a fixed season amount instead of a usage charge.

Operations selects a per-season calculation kind.

OperationsManagerSystem

1
Operations confirms the payee and a valid start date.
Operations
2
Operations records the positive season amount and currency.
Operations
3
Operations records the first payment date and, when needed, a second payment date.
Operations
Payment dates are available only on season-amount agreements, and at least one date is required for readiness.
4
Trailhead removes direction and usage-settlement choices that do not apply.
System
This is the key moment: the amount becomes one commitment, not a repeated crossing instruction.
5
Trailhead marks the Access configured for committed-cost reporting.
System
6
Program execution creates no per-crossing accrual or guide payment task from this rule.
System

Operations

Records the fixed commitment and payee.

Manager

Compares committed cost with actual usage.

System

Excludes usage-only settlement choices.

Operations

The season commitment and its payment dates beside actual Access usage.

Why: Maintain planning readiness.

Manager

Committed Access cost even when usage is zero.

Why: Compare commitment with activity.

A season amount is a setup-time commitment; only this agreement type has payment dates, and it never creates a per-Program payment instruction.