Guide
Monthly batch admin
The Monthly batch admin view is the central control interface for the monthly allocation process. Here you can plan, start, monitor, and finalize batch runs. The goal is to ensure that monthly allocations are created in a predictable, controlled, and well-documented way.
Run, planning, and finalization
The monthly batch process can be divided into three main statuses: planning, execution, and finalization. These steps ensure that allocations can be reviewed first and only become final after validation.
- Planning: start a preparatory run for the month to preview expected allocations, capacity utilization, and conflicts.
- Execution: the batch algorithm runs with the defined parameters and generates an allocation proposal. At this stage, review and adjustments are still possible.
- Finalization: closing the approved allocation, which locks in the monthly schedules and makes the result official.
It is recommended to verify input data (e.g. capacities, availability, priorities) before each run to ensure accurate batch results.
Managing locks
Locks prevent unwanted changes during batch execution or after finalization. This is especially important when multiple admins are working on the same month.
- Temporary lock: used during the planning phase to ensure only designated admins can modify batch parameters.
- Final lock: activated after finalization and prevents any subsequent overwriting of allocations.
- Unlock process: allowed only in exceptional cases and in an audited manner. In such cases, document the reason and the approver.
Exports
The Monthly batch admin allows you to export allocations for further processing or for external systems. Exports also support financial, resource-planning, and customer service workflows.
- Aggregated export: complete monthly allocation in a single file, for example in CSV or XLSX format.
- Filtered export: export limited to a specific service, resource, or status.
- Versioned export: enables comparison of multiple runs to track the history of changes.
Monitoring and metrics
Monitoring helps you immediately see how successful a batch run was, where anomalies occurred, and to what extent allocation goals were met.
- Success rate: how many allocations were completed without errors and how many requests remained unprocessed.
- Capacity utilization: comparison between planned and actual usage.
- Duration and load: runtime and system load, helping with future scheduling.
- Alerts: automatic notifications if abnormal ratios, excessive errors, or unexpected locks occur.
Recommended workflow
- Plan the batch run and verify input data.
- Start the execution and review preliminary results.
- Use exports and monitoring for quick validation.
- Finalize and activate final locks.
If the batch requires multiple iterations, document changes after each run so the rationale behind decisions remains transparent for the team.