Q&A from Sessions

Q: Can I re-run the Application Framework after generation to change configuration choices?

A: Yes — you can re-configure and re-generate. However, post-generation customizations (extensions, manual fixes, data loads) may need to be reapplied. Plan your configuration carefully upfront to minimize re-generation. Catch dimension and hierarchy decisions before starting post-gen work.

Q: What happens if generation fails partway through?

A: Check the PAF configuration logs to see where it failed. Common causes: (1) missing roles — you need all 4 roles; (2) wrong default tenant — Integration Admin must generate in their default tenant; (3) source model not included in generation. Fix the issue and re-generate.

Q: Can a customer use their existing data hub instead of ADO?

A: Yes — but they'll need to configure import actions during implementation instead of using ADO links. ADO is the recommended and supported path for new implementations. If a customer has an existing data hub they want to keep, factor in the import action configuration work during scoping.

Q: What's the maximum number of hierarchy levels? What happens if a customer needs more?

A: Maximum 8 levels per model, minimum 2 levels. If a customer needs more, this would require a bespoke extension — the Application Framework enforces this limit. Have the dimension conversation early in discovery to identify any risk.

Q: Can IFP plan at the named employee level?

A: Not directly — IFP HC plans at job/role level to protect PII. For position or employee-level detail, use OWP (Operational Workforce Planning), which integrates natively with IFP HC, or Workforce Budgeting (WFB). Both feed into IFP via the DAT Headcount Planning Import module.

Q: Why can't I delete a job from the job metadata page?

A: You can only delete jobs with no headcount assigned. The system checks total FTE in HRIS Actuals — if any FTE is assigned, the Delete checkbox is read-only. Remove or reassign headcount first, then the checkbox becomes available.

Q: How do pay band deviations work? Do they block planning?

A: Deviations do NOT block planning — they flag for management review. The system calculates a Cost Multiplier for each job (fully loaded cost ÷ salary). If it falls outside the min/max benchmark range from the pay band, a deviation is shown in the Insights Panel. Finance teams can review and approve exceptions.

Q: Can we plan CapEx by department?

A: Not directly in v2.0 — CapEx is Entity-level only. The entity-to-department mapping in CapEx General Admin distributes depreciation to the correct P&L dimensions. For full department-level CapEx planning (e.g., each department owns its own CapEx budget), an extension is required.

Q: What is CWIP (Construction Work in Progress)?

A: Assets flagged as CWIP don't start depreciating until the in-service date is reached. Until then, the asset sits in the CWIP balance sheet account. This handles scenarios like a facility being built — you're spending money but it's not yet depreciating.

Q: Why do BS inputs represent activity instead of balances?

A: IFP uses a roll-forward approach: Closing Balance = Last Actual Balance ± Activity. This means entering nothing still produces a valid result — the last actual balance simply rolls forward. You only need to enter changes, not restated balances each period. This is simpler and less error-prone than balance-based input.

Q: The balance sheet isn't balancing — what should I check?

A: In order: (1) Run the Balancing Routine, (2) verify all BS accounts have cash offset categories assigned, (3) verify all leaf-level BS accounts have cash flow mappings, (4) confirm FIN – Import from CapEx Model has been run recently. Most BS balance issues trace to missing cash offset or CF mappings.

Q: Why do some ADO links fail to generate out of the box?

A: Known PAF generation issue. The following are documented as broken or missing: Vendor Hierarchy (FP), SYS by J2/J3 Job (HC), SYS by J4 Job (HC — no link created at all), and Job Grade (HC). These must be created manually. This is expected and documented — plan for it in your post-generation schedule.

Q: In what order should I load data?

A: Always: (1) complete Admin model source-to-planning mappings first, (2) push planning hierarchies and master data to all spoke models, (3) then load actuals. Actuals loads will fail if planning lists aren't populated yet. Source files must match the template format exactly.

Q: How do I add a new reporting currency?

A: Add the currency to the Report Currency list and give it its ISO code. That's it — all financial data is immediately available in the new currency via triangulation. No module changes, no additional rate loading, no code changes required.

Q: What is the Statistical Rate Type used for?

A: Non-financial metrics like headcount and FTE counts. These always translate at a rate of 1 (no currency conversion makes sense for headcount). You don't need to load statistical rates — the system automatically assumes 1. This prevents headcount numbers from being multiplied by FX rates in reporting.

Q: What is the base currency and does it matter which one we choose?

A: The base currency is the intermediary in the triangulation calculation — all loaded exchange rates go from local currencies INTO the base. Any currency can be the base. USD is the most common choice. The base currency itself is always available in reporting. The choice affects which rates you need to load (always local → base) but doesn't affect reporting capability.