ROI slides slowed approvals — ServiceNow intake with Anaplan & Oracle EPM alignment

Overview

Capital allocation at a mid-market industrial supplier slowed down because Return on Investment (ROI) cases lived in slide decks with inconsistent assumptions. Discount rates, labor costs, and risk flags varied by business unit, and approvals bounced across email threads. Intelligex implemented a standardized intake in ServiceNow connected to Anaplan models and Oracle Enterprise Performance Management (EPM). Legal and Risk reviews were built into the workflow so the Chief Financial Officer (CFO) saw only validated cases. Leadership gained apples-to-apples comparisons, a clear audit trail, and quicker approvals because every request drew from the same governed assumptions and process.

Client Profile

• Industry: Industrial supply and services
• Company size (range): Established mid-market with multi-site operations
• Stage: Mature operator scaling disciplined capital allocation
• Department owner: Strategy, Analytics & Executive Leadership (Office of the CFO and Corporate Strategy)
• Other stakeholders: FP&A, Business Unit Leaders, Operations Engineering, Procurement, Legal, Risk & Compliance, IT/Enterprise Apps, Internal Audit

The Challenge

Capital requests arrived as bespoke slide decks and spreadsheets. Each presenter framed ROI and Net Present Value (NPV) with their own discount rates, inflation assumptions, and labor benchmarks. Supportive details like vendor quotes, safety impacts, and data handling considerations were attached in email, if at all. During reviews, Finance spent time reconciling assumptions rather than assessing options, Legal discovered contract gaps late, and Risk flagged compliance issues after the CFO had already seen the case.

Core systems were in place: Anaplan contained driver-based financial models, Oracle EPM managed planning and capital budgeting, and ServiceNow handled operational workflows. The problem was not tooling; it was the absence of a governed intake tied to authoritative models and a clear approval path. Leaders wanted a way to standardize assumptions, fold Legal and Risk into the process at the right moment, and log decisions with traceability, without ripping out systems or forcing teams into rigid templates that did not reflect real operations.

Why It Was Happening

Data and process were fragmented. There was no data contract for required fields across cases, and no single place to confirm which assumptions applied. Business units reused old slides with copied math, and version control broke as attachments moved across email. Oracle EPM held the plan, but intake happened outside of it. Anaplan could run scenarios, yet cases did not feed it consistently, so Finance rebuilt them by hand.

Governance arrived too late. Legal and Risk were pulled in after a deck was drafted, and their feedback changed the structure and timing of requests. Approvals were informal and lacked an auditable trail. Without a consistent path, the CFO’s reviews turned into working sessions to normalize inputs, and decisions slipped as documents cycled for edits.

The Solution

We built a standardized capital request intake in ServiceNow that captured required fields, validated assumptions, and drove calculations through Anaplan with results surfaced to Oracle EPM. The workflow applied Legal and Risk gates before CFO review. Approved assumptions, rate tables, and cost libraries lived in Anaplan; final budget alignment and tracking lived in Oracle EPM. The process produced a consistent summary view with links to supporting evidence, and stored an immutable snapshot of each case’s inputs and outputs for later audit. Nothing was replatformed; the orchestration made existing tools behave as one coherent system.

• ServiceNow request form with required fields for scope, category, site, justification, cost breakdown, benefits, risk factors, data handling, and vendor status (ServiceNow)
• Assumption validation against a shared library in Anaplan: discount rates, inflation curves, labor and energy benchmarks, and FX tables (Anaplan Help)
• Automated push of case inputs to Anaplan for ROI/NPV and scenario runs; calculated outputs returned to the request
• Mapping of approved cases to Oracle EPM capital planning for budget alignment, project codes, and reporting (Oracle EPM Documentation)
• Workflow gates for Legal (contract terms, data processing, IP) and Risk (safety, regulatory, third-party risk), aligned to internal policy and enterprise risk principles such as COSO ERM
• Evidence attachments with required document types: vendor quotes, safety assessments, architectural diagrams, and data handling worksheets
• Role-based views: Business units see their requests; Finance sees portfolio views; Legal and Risk see flagged fields; executives see normalized summaries
• Immutable snapshots of assumptions and outputs at submission, approvals, and final decision points
• Dashboards for pipeline of requests, stage aging, portfolio ROI distribution, and exceptions requiring rework
• Change logs and versioned assumption libraries with owner stewardship

Implementation

• Discovery: Cataloged the current capital request formats, the assumptions Finance trusted, and the fields Legal and Risk required. Reviewed Anaplan modules and Oracle EPM structures, including capex categories, project hierarchy, and reporting needs. Identified common failure modes from prior cycles.
• Design: Defined the data contract for requests and mapped each field to an owner and a system of record. Documented the approval path and return reasons. Designed the Anaplan integration for model inputs and outputs, and the Oracle EPM alignment for project codes and budget status. Planned snapshots and audit trails.
• Build: Configured the ServiceNow intake with conditional fields and validations. Connected to Anaplan to read assumption libraries and post scenario inputs, and to Oracle EPM to create or map projects. Implemented Legal and Risk gates with checklists, and built dashboards. Added role-based permissions and evidence requirements.
• Testing and QA: Replayed recent cases through the new flow to compare outputs to Finance’s baselines. Tuned validation messages to reduce noise. Checked Legal and Risk gate behavior on sensitive scenarios. Verified project creation and status sync with Oracle EPM. Confirmed snapshots and audit logs recorded every transition.
• Rollout: Launched in observe-only mode where the new intake produced parallel cases while teams continued their legacy process. After validation, enabled required intake for new requests and phased in Legal and Risk gates by category. Kept a manual exception path for urgent safety and continuity items with post-review.
• Training and hand-off: Delivered short guides for business units on the intake, for Finance on assumption stewardship, and for Legal and Risk on gate criteria. Published a playbook on how to request changes to the assumption library. Established a cadence for portfolio reviews and a human-in-the-loop process for edge cases.

Results

CFO reviews focused on trade-offs rather than reconciling math. Every case arrived with the same discount rates, inflation curves, and cost libraries applied. Legal and Risk concerns were resolved earlier, and evidence lived with the request. Portfolio views reflected comparable ROI and risk profiles, allowing leaders to move through decisions with fewer edits and clearer rationale.

Audit readiness improved. Each decision carried a snapshot of assumptions, approvals, and outputs, with links to Anaplan runs and Oracle EPM project records. When a case was revisited, teams regenerated the summary from the stored state instead of reassembling slides. Business units gained transparency into why a request was returned and how to fix it, which reduced rework in subsequent cycles.

What Changed for the Team

• Before: ROI cases were built in slides with bespoke math. After: A governed intake fed Anaplan with shared assumptions and returned standardized outputs.
• Before: Legal and Risk feedback arrived late by email. After: Workflow gates captured their review and rationale before CFO review.
• Before: Finance rebuilt cases to normalize inputs. After: ServiceNow enforced required fields and validations against approved libraries.
• Before: Decision trails lived in inboxes and file shares. After: Snapshots and approvals created a durable record tied to Oracle EPM projects.
• Before: Portfolio views mixed incompatible assumptions. After: Dashboards compared cases on the same basis across categories and sites.

Key Takeaways

• Standardize capital request intake and tie it to authoritative models; governance at the front door prevents downstream rework.
• Keep modeling in Anaplan and planning in Oracle EPM; orchestrate the flow from intake to approval to budget rather than replatforming.
• Insert Legal and Risk at defined gates with clear checklists, not after the CFO has seen the case.
• Snapshot assumptions and outputs at every stage so decisions are auditable and easy to revisit.
• Steward a shared assumption library with clear ownership to maintain consistency as conditions change.

FAQ

What tools did this integrate with?
ServiceNow captured requests and orchestrated workflow. Assumptions and calculations ran through Anaplan models, and approved cases aligned to Oracle EPM for budgeting, project codes, and reporting. Dashboards lived in the client’s BI environment, and evidence remained attached to the request record. For product references, see Anaplan Help, Oracle EPM Documentation, and ServiceNow.

How did you handle quality control and governance?
Quality was enforced through a data contract in ServiceNow, validations against Anaplan’s assumption libraries, and workflow gates for Legal and Risk with documented checklists. Each transition created a snapshot with inputs, outputs, and approver identity. Changes to assumption libraries followed stewardship and change control, and dashboards surfaced exceptions and return reasons for coaching.

How did you roll this out without disruption?
We ran the new intake and modeling path in parallel with the legacy slide process for a cycle, reconciled differences, and tuned validations. Once stakeholders were comfortable, we required the new intake for fresh requests and phased in gates by category. An urgent exception path existed for safety or continuity items, with post-review to keep governance intact.

What happens when discount rates or benchmarks change?
Assumptions lived in Anaplan libraries with named stewards. When rates or benchmarks updated, the library version changed and new requests used the latest values automatically. In-flight requests displayed the version they used; sponsors could opt to refresh assumptions before approval if warranted, preserving an audit trail either way.

Did this replace Anaplan or Oracle EPM?
No. Anaplan remained the modeling engine and Oracle EPM remained the planning and reporting system. The change was the introduction of a governed intake, integration to those systems, and approval gates that ensured consistent assumptions and documented reviews before CFO consideration.