For the resource manager
People, skills, allocations, leave and scenarios in one model, so overcommitment shows on the heatmap before it shows on the delivery date.
In one sentence
AlignX shows the resource manager true capacity against real demand, with skills, availability, leave and conflicts visible before work is committed.
Written forResource ManagerWorkforce Planning DirectorDelivery Director
The challenge
If any of these takes a week to answer, the rest of this page is for you.
The solution
Capacity heatmap
Under, healthy, full or over, with a forecast marker where firm plus tentative crosses the line. Read-only, computed from the bookings.

Resource workbench
Proposed, confirmed, on hold, firm or tentative. Quick-add from the row, and the peak shows against the ceiling.

Skills and proficiency
Integration architecture, threat modelling, Azure landing zones. Demand names the skill it needs, so the match is skills-aware.

Rebalance scenarios
Fourteen resources change. Over-booked months go from fifteen to none. Promote it and the live bookings follow; leave it and nothing moves.

Leave and availability
Annual, parental, long service, study. The heatmap already knows, so the December plan is not a surprise.

Day to day
The AlignX technology
Questions
AlignX replaces the resource module of your PPM (Planview, Clarity, ServiceNow SPM) and your standalone capacity spreadsheets. It integrates with your HR/HCM (Workday, SuccessFactors), Jira for actual effort, and finance for cost rates. One resource model, drawing from the systems that already own the data.
Yes. AlignX is not there to replace where work happens or where employee data lives. It integrates. Teams keep working in Jira, HR keeps managing people in Workday, and AlignX holds the connected demand-capacity-skills model that no single system holds today. This is what makes consolidation work.
The model separates funded, unfunded, shared and dedicated capacity with visible ceilings for each. You see who is committed to what, and how much runway is left before over-commitment. Shared service teams appear against every consuming portfolio without double counting.
Yes. Every resource carries a skills profile, and demand records specify required skills, not just FTE. Matching is skills-aware, so you spot the \"we have capacity but not the right capacity\" gap before it becomes a hiring rush or a delivery slip.
Demand can be raised at pipeline stage, before funding. You see what is coming down the tunnel and can flag capacity conflicts to the portfolio board before commitments harden.
Yes. Enterprise-wide visibility means demand from every portfolio, transformation programme and BAU stream aggregates against your team. No more surprises when three programmes all need your architects in Q3.
Every resource type has its own record with contract dates, cost rates and reporting lines. Secondments and dotted-line commitments are first-class, not workarounds. When a contract ends, downstream demand it was covering flags automatically for rebalancing.
Ten minutes, twenty-one questions, an instant maturity score.