PAUMS – Calculation Manual

Document Type: Calculation Manual | Version: v2.0 | Audience: TPMO Leadership, Finance, Audit, Engineering, Program Management
Type to filter questions
No matching questions found. Try different keywords.

Core Design Principles

What are the core design principles of PAUMS calculations?

A:

Regional Data Semantics

How does PAUMS handle different regional data semantics?

A:
RegionPrimary SourceNature of DataInterpretation
APACClockify TimesheetsActual worked hoursObserved utilization
EMEAAllocation SheetsPlanned FTE allocationDerived equivalent hours
Important: EMEA figures represent planned capacity consumption. They must never be interpreted as actual time-tracked hours.

Core Entities & Schema

What are the key fields in the employees table?

A:

How are projects classified in PAUMS?

A:

What data granularity does PAUMS support?

A:

Available Capacity Calculation

How is available capacity calculated?

A:
available_hours = fte_default_hours

Utilized Hours Calculation

How are utilized hours calculated for APAC?

A:
utilized_hours = SUM(timesheets.hours)

Sum of all timesheet hours for the month.

How are utilized hours calculated for EMEA?

A:
utilized_hours = allocation_pct × fte_default_hours
Allocation percentages are assumed to represent full-month distribution.

TPMO Hours Treatment

How are TPMO hours treated in calculations?

A:
effective_utilized = utilized_hours − tpmo_hours

Utilization Percentage

How is utilization percentage calculated?

A:
utilization_pct = (effective_utilized / available_hours) × 100
If available_hours = 0, utilization is forced to 0 to avoid distortion.

What is the difference between utilization and billable percentage?

A:
Utilization % = (Utilized Hours / Available Hours) × 100
Billable % = (Billable Hours / Available Hours) × 100
TPMO % of Available = (TPMO Hours / Available Hours) × 100
Idle Hours = Available Hours − Utilized Hours
    

Leadership vs PM Classification

How are leadership hours handled?

A:

Monthly Snapshot Model

What is the purpose of monthly snapshots?

A:

What fields are included in monthly snapshots?

A:

Snapshot Rebuild Rules

When can snapshots be rebuilt?

A:

Executive Summary Logic

How is the executive summary calculated?

A:

Executive Summary Table Deep Dive

What does the executive summary table represent?

A:

A year-level aggregation of employee capacity and time usage, split by role bucket (Project Managers vs Leadership), computed from immutable monthly_snapshot data.

Key Principle: Nothing is estimated. Nothing is recalculated. Nothing is averaged incorrectly.

What is the source data for executive summary?

A:
monthly_snapshot
WHERE scope = 'EMPLOYEE'
AND year = 2025
    

Grouped by employee, then role bucket, then summed across all 12 months.

Can you show an example executive summary table?

A:
BucketHeadcountAvailableUtilizedTPMOUtil%
Project Managers2029,208.0020,101.552,508.2568.82%
Leadership510,712.005,166.06918.5048.23%

How is the "Bucket" column determined?

A:
CASE
  WHEN (
    e.job_title IN LEADERSHIP_TITLES
    OR e.full_name IN LEADERSHIP_NAME_EXCEPTIONS
  )
  THEN 'leadership'
  ELSE 'project_managers'
END
    

How is "Headcount" calculated?

A:

Definition: Number of distinct employees who had ≥1 snapshot row in the year

COUNT(DISTINCT ms.employee_id)
⚠️ This is not FTE count, not weighted, not prorated.

How is "Available Hours" calculated?

A:

Definition: Total theoretical capacity across the year

SUM(ms.available_hours)

Where available_hours is already pre-calculated per employee per month.

How is "Utilized Hours" calculated?

A:

Definition: All delivery + governance work performed (including TPMO)

SUM(ms.utilized_hours)
Important: Utilized includes TPMO hours. Utilized does NOT include idle time. Utilized ≠ Billable (billable is a subset).

How is "TPMO Hours" calculated?

A:

Definition: Subset of utilized hours spent on TPMO-coded work

SUM(ms.tpmo_hours)

How is "Util %" calculated?

A:
Util % = (Utilized ÷ Available) × 100

Project Managers Calculation:

20,101.55 ÷ 29,208.00 × 100 = 68.82%

Leadership Calculation:

5,166.06 ÷ 10,712.00 × 100 = 48.23%

How should the Project Managers utilization (68.82%) be interpreted?

A:
Project Managers — 68.82%
  • Below the typical 75–80% target
  • Indicates idle or under-allocated delivery capacity
  • TPMO load is noticeable but not excessive

How should the Leadership utilization (48.23%) be interpreted?

A:
Leadership — 48.23%
  • Expected to be lower than PMs
  • Indicates: Governance, strategy, presales, non-delivery time
  • TPMO % is higher relative to utilized, which is worth monitoring

Why can we trust these calculations?

A:
Single source of truth: monthly_snapshot
No recalculation of history
Same service feeds: UI table & Executive PDF
No UI math
No frontend rounding errors

Auditor Response: If an auditor asks "How did you get 68.82%?", you can point to the formula and underlying monthly_snapshot rows. Every number is traceable to source data.

Data Health Indicators

What data health indicators does PAUMS monitor?

A:

Known Limitations

What are the known calculation limitations?

A:

Governance & Audit

How does PAUMS support governance and audit requirements?

A: