Academy of Profit Center — Your Journey

Models Pavilion

Hall 3 of 9 · Academy of Profit Center · EPCM Study Tour

The perspective machine

Every calculation in EPCM runs inside a model. A model is not a cube or a report — it is a named configuration that fixes which Scenario, Version, and calculation logic applies to a given run. NovaPrism has four models. Understanding why — and how the POV selector controls which one you are working in — is the foundation of everything that follows.

Conceptual Technical Interactive Lab Exam: 1Z0-1082-25

📐

Conceptual

What a model actually is

Not a cube. Not a report. Not a dimension. A model is a named, reusable calculation context — the container that tells EPCM which POV to operate on, which rules apply, and what the output represents.

In EPCM, a model is a named configuration that ties together a Scenario, a Version, and a set of rule sets into a single runnable object. When you run a model, EPCM executes every rule set assigned to it against the POV defined by that model's Scenario × Version intersection. The results land in PCM_CLC — in those specific Scenario and Version cells.

This matters because NovaPrism needs to run the same allocation logic against four completely different business questions simultaneously. What did we actually spend in Q1 Actual? What does Q2 look like in Forecast? What does the CFO's restructure scenario show? Each question needs its own model — not its own rule set, not its own cube, but its own named context that directs the same rules to a different part of the Scenario × Version address space.

💡

The key insight: NovaPrism writes one set of allocation rules — once, in Hall 4. Those same rules run across all four models by simply changing the POV context. The IT pool allocation logic for IS ($33.09M of $52M) is the same arithmetic whether you are calculating Actual, Forecast, or What-If. The model determines which cells that arithmetic writes into. This is why models are a design decision, not a technical detail.

NovaPrism's four models

NovaPrism's four models are defined in constants.js and cover every business use case the CFO needs to answer. Each model is independent — running M04 What-If does not affect M01 Actual results.

📋

M04 — the CFO's restructure model: NovaPrism's CFO wants to model a scenario where Infrastructure Solutions headcount drops by 800 (from 4,200 to 3,400) and its square footage is reduced by 30,000 sq ft. The What-If model runs the same allocation rules against modified driver values — the Finance and HR pool allocation to IS shrinks, the Facilities pool allocation shrinks. The model produces a "what would IS margin be if we restructured?" answer without touching any Actual or Forecast data. This is what M04 exists for.

🎯

Conceptual

The POV selector — your address in the cube

POV stands for Point of View. It is not a dimension — it is the intersection of dimension members that defines which slice of the cube you are currently working in.

Think of the PCM_CLC cube as a multi-dimensional address space. NovaPrism's cube has 11 dimensions. Any specific cell in that cube has an address with one coordinate on each dimension — Account × Entity × Region × Function × Product × Customer × PCM_Balance × Period × Scenario × Version × View. The POV selector is the EPCM UI control that fixes the values of the dimensions that are not on rows or columns of your current form or report.

In practice: when NovaPrism's Finance Controller opens a data form to review Q1 allocations, the form shows Entity on rows and Account on columns. The POV selector sits at the top of the form and fixes Period = Q1, Scenario = Actual, Version = Working, PCM_Balance = PCM_Output, and View = Periodic. Change Period to Q2 in the POV selector — every number on the form refreshes to show Q2 data. The form design has not changed. The data has not changed. The POV has changed.

⚠️

POV vs dimension members — the critical distinction: A dimension member (like "Actual") is a permanent part of the cube outline. The POV selector is a runtime control that picks which member you are looking at. You cannot save the POV into the cube. You can save a named POV as a shortcut so you can recall it — but the data is always addressed by the member, not by the POV selector position. Exam questions test whether you know the POV selector is a navigation tool, not a data storage concept.

🎭

Conceptual

Scenario × Version — the two-axis address

Every cell in NovaPrism's model lives at a Scenario × Version intersection. Understanding which combinations are valid — and which model controls which — is essential before you run a single calculation.

The Scenario dimension answers: what is the business context of this data? Actual means it happened. Forecast means it is expected. Budget means it was planned. What-If means it is hypothetical. The Version dimension answers: what stage of the process is this? Working means it is in progress. Final means it has been signed off. Pass1 and Pass2 support multi-pass allocation sequences where preliminary results feed into a second calculation pass.

NovaPrism's four models each own a specific Scenario × Version cell in this space. M01 writes Actual/Working results. M02 writes Forecast/Working results. M03 writes Budget/Working results. M04 writes Actual/WhatIf results — using Actual as the base Scenario but a separate Version so the restructure numbers never contaminate the real Actual data.

NovaPrism — Scenario × Version ownership matrix

Actual

M01 — Actuals
Allocation Process

Promoted from Working after CFO sign-off

M04 — What-If
Scenario Analysis

Not used

Forecast

M02 — Forecast
Allocation Process

Promoted from Working at quarter lock

Not used

Budget

M03 — Budget
Allocation Process

Promoted at budget sign-off

Not used

What-If

Not used

✓

Why M04 uses Actual/WhatIf and not What-If/Working: The CFO's restructure model needs to start from real Q1 Actual data and apply hypothetical driver changes. By using Actual as the Scenario and WhatIf as the Version, M04 can read from M01's Actual/Working results as the base, then write restructured allocation results into Actual/WhatIf — completely separate. If M04 used What-If/Working, it would need its own base data load from the GL. The Actual/WhatIf design reuses real data as the starting point.

⚙️

Technical

Model properties — what you configure at creation

When you create a model in EPCM, you set five properties. Three of them cannot be changed after the model is used in a calculation run. This makes model design a one-shot decision.

Property	What it controls	Changeable after creation?	NovaPrism M01 value
Model Name	Display name used across the UI, in logs, and in EPMAutomate commands	Yes	Actuals Allocation Process
Model ID	Internal identifier used in API calls and EPMAutomate	No — locked on first calc run	M01
Scenario	Which Scenario dimension member this model writes to	No	Actual
Version	Which Version dimension member this model writes to	No	Working
Rule Sets assigned	Which rule sets execute when this model runs — and in what sequence	Yes	All 5 rulesets (seq 10–50)

⚠️

The exam trap on model properties: "After creating model M01 with Scenario = Actual and running the first calculation, the Finance team wants to change the Scenario to Forecast to save time. This is possible by editing the model properties." — FALSE. Scenario and Version are locked after the first calculation run. You must create a new model. The exam will offer this as a plausible answer. It is wrong.

📋

Technical

Copy POV — publishing results from PCM_CLC to PCM_REP

Running a model writes results to PCM_CLC. The CFO does not read from PCM_CLC. Copy POV is the explicit operation that publishes a specific Scenario × Version × Period intersection from the calculation cube to the reporting cube.

After NovaPrism's M01 Actuals model runs for Q1, the Finance Controller reviews the results in PCM_CLC — checking balances, verifying IS's $80.82M allocation, confirming the 60 engagement totals reconcile. Once satisfied, she runs Copy POV to push Actual/Working/Q1 from PCM_CLC to PCM_REP. From that point, the CFO's Smart View reports and dashboards — which read from PCM_REP — show the Q1 results.

The architectural significance: while the Q1 Copy POV is running, or while Q2 M01 is calculating in PCM_CLC, the CFO can continue reading Q1 results from PCM_REP without interruption. PCM_REP is only updated when Copy POV explicitly runs — it is never updated mid-calculation.

Step	Action	Cube affected	Who runs it
1. Load	GL actuals loaded into PCM_CLC for Actual/Working/Q1	PCM_CLC	Data Integration (Hall 8)
2. Calculate	M01 model runs — all 5 rulesets execute, allocating $134M	PCM_CLC	Finance Controller
3. Review	Finance Controller inspects PCM_CLC — balances, rule balancing checks	PCM_CLC	Finance Controller
4. Copy POV	Actual/Working/Q1 pushed from PCM_CLC to PCM_REP	PCM_REP updated	Finance Controller
5. Report	CFO, division heads, auditors read from PCM_REP via Smart View	PCM_REP	Read-only consumers

📋

Named POVs vs Copy POV: These are two completely different concepts with confusingly similar names. A Named POV is a saved shortcut in the POV selector — it remembers your preferred Scenario/Version/Period combination so you do not have to reset it every session. Copy POV is an administrative operation that transfers data between cubes. One is a navigation shortcut. The other is a data publication workflow. The exam tests that you know the difference.

⚙️

Copy POV in production — it's rarely a manual UI step. In NovaPrism's automated monthly close, Copy POV is triggered via epmautomate copyDataByPointOfView "PCM_CLC" "PCM_REP" "Actual#Working#Q1#FY2025" as step 6 of the nightly pipeline — no human clicks required. Note the EPM Automate command is copyDataByPointOfView (EPCM), not copyPov (which is the Planning command). A common exam trap when candidates switch between products. For the full EPM Automate vs Groovy automation debate, see the EPM Automate reference page.

🔄

Technical

Running a model — what actually happens

When you click Calculate on a model in EPCM, the system does not just run rules. It executes a precise sequence — clear, load drivers, execute rule sets in sequence order, verify balance.

Phase	What EPCM does	NovaPrism detail
Clear	Clears the target POV in PCM_CLC before writing new results. Default clear type: Logical (not Physical).	Clears Actual/Working/Q1 data in PCM_CLC. Logical Clear removes data from the model's POV without touching other POVs or PCM_REP.
Driver load	Refreshes any driver members with current source values if driver staging rules are included.	IT ticket counts (DS: 1,240, IS: 2,890, CL: 410) confirmed. Headcount and sqft driver values verified from constants.
Ruleset seq:10	IT Cost Pool Formation — Serial. Pools IT GL accounts into a single stageable member.	$52M IT pool formed from 1,200 GL accounts via Account alt hierarchy. Serial: must complete before seq:40.
Rulesets seq:20–30	Facilities and Finance/HR Allocation — Parallel. Both can run simultaneously.	$38M by sqft + $28M+$16M by headcount. IS receives $24.16M + $15M + $8.57M = $47.73M from these pools.
Ruleset seq:40	IT Allocation — Serial. Depends on seq:10 having completed.	$52M allocated by ticket count. IS: $33.09M. DS: $14.19M. CL: $4.70M.
Ruleset seq:50	Engagement Contribution — Parallel. Pushes division costs to 60 engagement codes.	IS's $80.82M allocated cost distributed across its engagement portfolio. 17 engagements revealed as loss-making.
Balance check	System verifies PCM_Input = PCM_Allocated_Out for cost centres. ES must net to zero.	ES: $134M in, $134M out. Difference = $0. Model is balanced.

⚠️

Logical Clear vs Physical Clear — the default that trips people up: EPCM defaults to Logical Clear. Logical Clear removes data only from the stored cells that are part of the current model's POV. Physical Clear removes all data from the entire ASO database slice — including data that was not written by this model. For NovaPrism: running a Physical Clear before M01 would wipe Forecast and Budget data from the same Period slice. Never use Physical Clear in a multi-model environment unless you know exactly what you are doing. The exam tests this default.

🧭

Interactive

POV Simulator

Select any combination of Scenario, Version, Period, and Entity below. The simulator shows you which model owns that POV, which cube to read from, and what NovaPrism data you would see.

NovaPrism_EPCM_PROD — POV Selector Simulating the EPCM UI POV control

Scenario

Version

Period

Entity

POV Resolution

Change any dimension above to see how EPCM resolves the POV to a model, a cube, and a data state.

🔬

Lab Scenario

Design and validate NovaPrism's four models

The Finance Director has approved the EPCM build. Before rule sets can be assigned in Hall 4, the four models must be created with the correct Scenario and Version properties — and justified to the CFO.

Mission Brief — Model Configuration Sign-off

Situation: NovaPrism's Oracle implementation partner has provisioned the application. You must configure all four models before the Hall 4 rule set build begins — because rule sets cannot be assigned to a model that does not exist. The CFO also wants a one-page brief explaining why four models are needed rather than one, and what the WhatIf Version is for. You have two hours before the project governance review.

Create all four models with correct Scenario and Version. Using NP.models from constants.js, specify the exact Scenario and Version for M01, M02, M03, and M04. For each, state the business process it supports and why those specific dimension members were chosen — not alternatives.

Explain why M04 uses Actual/WhatIf rather than What-If/Working. Write the two-sentence rationale the CFO needs. The answer must explain what base data M04 reads from, why a separate Version is required rather than a separate Scenario, and what would break if you used What-If/Working instead.

Map the Copy POV workflow for M01 Q1 close. Describe the exact five-step sequence from GL data load through to CFO-readable results in PCM_REP. Name which cube holds data at each step, who performs each action, and what the Finance Controller verifies before running Copy POV.

Identify what happens if Clear Type is set to Physical before running M01. State what data would be wiped beyond M01's intended scope, which other models would be affected, and whether the data could be recovered without a full reload. This is the governance risk brief for the IT team.

Write the CFO brief on why four models instead of one. The CFO's question: "Why can't we just run one model and change the Scenario filter in the report?" Answer this directly — what would break, what would be lost, and what does model isolation give us that a single model cannot. Maximum three sentences.

0 of 5 tasks completed

🎓

Dean's hint on task 5: The CFO's question reveals a common confusion between dimensions and models. One model with Scenario changed in the report filter would work for reporting — but it would not work for calculation isolation. When M01 runs its Clear phase, it clears its own Scenario/Version/Period slice. If M02 Forecast were running in the same model, the Clear would hit Forecast data too. Four separate models means four completely independent calculation lifecycles — independent Clear, independent run schedule, independent rule set assignment. They share cubes, but they never interfere with each other's data.

📝

Exam Alignment · 1Z0-1082-25

What Models Pavilion covers on the exam

Hall 3 maps to the third syllabus topic: Working with POVs and Models. Expect 4–6 questions across the 50-question exam. The POV/Copy POV distinction and the Logical vs Physical Clear trap are the two highest-probability questions in this topic.

📝 Syllabus — Working with POVs and Models

Sub-bullet 1: Describe POVs and models in EPCM.
Know what a model is (a named calculation context tied to Scenario × Version). Know what a POV is (a runtime intersection of dimension members). Know that Named POV ≠ Copy POV.

Sub-bullet 2: Manage POVs and models.
Know the five model properties. Know which are locked after the first calculation run (Scenario, Version, ID). Know the Copy POV workflow — PCM_CLC to PCM_REP. Know that Logical Clear is the EPCM default and what Physical Clear does differently.

⚠️ The three most-tested traps in this section

Trap 1: "You can change a model's Scenario after it has been used in a calculation."
FALSE. Scenario and Version are locked after the first run. Create a new model.

Trap 2: "Copy POV copies data from PCM_REP to PCM_CLC so analysts can work on published results."
FALSE. Copy POV goes from PCM_CLC (calculation) to PCM_REP (reporting) — not the other way. The direction matters on the exam.

Trap 3: "Physical Clear is the EPCM default and is preferred for multi-model environments."
FALSE on both counts. Logical Clear is the default. Physical Clear is dangerous in multi-model environments because it clears beyond the model's POV scope.

0/5

Hall 3 Exam Score

Concept	Exam answer	Implementation reality
What is a model	A named calculation context tied to a specific Scenario × Version	The model is also the object you reference in EPMAutomate scripts — every automated close schedule calls a model by name
Default Clear Type	Logical Clear	Always verify this is set before a production run — Physical Clear in the wrong hands clears data across all POVs in the slice
Copy POV direction	PCM_CLC → PCM_REP	The direction is enforced by the system — you cannot accidentally copy the wrong way, but you must explicitly trigger it after each calculation
Named POV	A saved shortcut in the POV selector for navigation — not data	Most NovaPrism users save Named POVs for Actual/Working/Q1, Forecast/Working/Q2, etc. — so they do not have to reset the selector each session
Properties locked after first run	Scenario, Version, Model ID	Model Name and Rule Set assignments remain editable — so you can rename a model or reassign rule sets without recreating it