Capacity Modeling
Capacity Modeling in ProBeya provides two complementary capabilities: user-level capacity planning (tracking weekly available hours per team member) and production capacity modeling (simulating output across production lines with what-if scenarios). Together, they give transformation leaders a clear picture of whether the organization can absorb planned work.
These tools are essential during operational transformation programs where resource constraints are the primary bottleneck — they help managers balance workload against real availability.
Overview
Transformation programs often fail because they overload teams without understanding true capacity. ProBeya's capacity module solves this by:
- Tracking each user's weekly available hours over time (full-time, part-time, transitions)
- Aggregating capacity across the organization for dashboard views
- Modeling production line throughput with efficiency factors
- Running what-if scenarios to compare baseline versus alternative configurations
Getting Started
User Capacity Planning
- Navigate to Settings > Capacity Planning in your workspace.
- Click + Add Capacity Plan for a team member.
- Enter the user, weekly hours (e.g., 40, 32, 20), and the effective-from date.
- Leave the effective-to date blank for ongoing assignments, or set an end date for temporary arrangements.
Production Capacity Modeling
- Navigate to Capacity Models from the main menu.
- Click + New Model and choose a type: production, service, or resource.
- Add production lines with max capacity, unit of measure, and efficiency factor.
- Create scenarios (baseline and alternatives) to compare configurations.
How It Works
User Capacity Records
Each capacity record represents a user's weekly available hours over a date range. Users can have multiple records covering different periods — for example, when transitioning from full-time (40h) to part-time (20h).
| Field | Description |
|---|---|
| User | The team member this capacity applies to |
| Weekly Hours | Available hours per week (supports decimals, e.g., 37.5) |
| Effective From | Start date for this capacity setting |
| Effective To | End date (null means ongoing/current) |
The capacity overview dashboard shows:
- Total Users with at least one capacity record
- Average Weekly Hours across all active records
- Total Records including historical entries
Production Lines
Production lines define the physical or logical units where work is performed. Each line has:
- Max Capacity: theoretical maximum output per time unit
- Unit: measurement unit (e.g., "units/hour", "batches/day")
- Efficiency Factor: realistic throughput multiplier (default 0.85)
What-If Scenarios
Scenarios let you model different configurations against the same production lines. Each scenario stores input parameters (shifts per day, hours per shift, days per week) and computed results (effective capacity, utilization, surplus/deficit).
The system computes: Effective Capacity = Max Capacity x Efficiency Factor x Scenario Parameters
Configuration
Model Lifecycle
| Status | Description |
|---|---|
| Draft | Being configured, not yet used for planning |
| Active | Current production plan in use |
| Archived | Preserved for historical reference |
Scenario Comparison
Mark one scenario as Baseline and create alternatives to compare. The calculation engine evaluates each scenario against all production lines in the model, producing utilization percentages and surplus/deficit indicators.
Permissions
- Workspace Members can view capacity data and model results
- Workspace Admins can create, update, and delete capacity records and models
- Organization Admins have full access across all workspaces
Tips & Best Practices
Set up capacity records for all team members at the start of a transformation program. This makes workload vs. capacity analysis accurate from day one.
Use an efficiency factor of 0.85 as a starting point for production lines — this accounts for typical planned downtime, changeovers, and breaks.
Create at least two scenarios per model: a baseline (current state) and a target (post-transformation). This makes improvement quantifiable.
Related Features
- Resource Planning — allocation and scheduling across projects
- KPI Boards — track utilization KPIs like OEE
- Routines — standardized work procedures that consume capacity