Format: .pdf, .doc, .docx, .rtf, .txt, .md

Deliverable Requirements

Produce a structured document covering the four areas below.

1. EDM Cloud Configuration Design

Define the node types, views, and validation rules you would configure in Oracle EDM Cloud for Meridian's Chart of Accounts hierarchy. Your response must address:

• The proposed EDM Cloud structure and why you designed it this way
• What governance controls are built into the configuration
• How this design differs from the existing on-premise Primous configuration

2. Migration Approach

Outline your end-to-end migration plan from Primous to EDM Cloud within the 12-week window. Your plan must cover:

• Data extraction strategy — how data is extracted from Primous
• Transformation and mapping approach — how on-premise structures are mapped to EDM Cloud equivalents
• Data validation and reconciliation checkpoints — how accuracy is confirmed at each stage
• Phasing across the three migration stages:

3. FCCS Integration Continuity

Explain how you will ensure FCCS continues to receive accurate hierarchy data during and after migration. Your response must address:

• Cutover approach — parallel run, big bang, or phased — and your rationale for the chosen approach
• In-flight hierarchy changes — how change requests are handled during the migration window without disrupting FCCS
• Post-migration reconciliation — what checks you perform to confirm FCCS mapping integrity after go-live

4. Versioning & Archival Strategy

The Primous environment contains 90+ quarterly hierarchy snapshots spanning 6+ years. Define:

• What migrates to EDM Cloud vs. what gets archived
• The rationale driving those decisions, with specific reference to:
  • Business continuity requirements
  • Regulatory audit requirements applicable to a financial services firm

Format: .pdf, .doc, .docx, .rtf, .txt, .md

Evaluation Criteria

Section A — Migration Risk Assessment

300–500 words

Identify the top 3–5 risks to this migration and explain how you would mitigate each. For each risk, address three things:

1. What could go wrong
2. How you would detect it
3. What your contingency is

Consider risks across the following areas:

• Data integrity during extraction and load
• FCCS disruption during cutover
• Governance workflow gaps during transition
• Stakeholder resistance to cloud adoption
• Timeline risk given the fiscal year-end deadline

Section B — Stakeholder Communication & Knowledge Transfer Plan

Three business teams interact with EDM daily, each with different needs and different levels of technical sophistication:

Part 1 — Stakeholder Communication

For each of the three teams, describe:

• What information they need about the migration timeline, impacts, and required actions
• When they need it
• What format and communication channel works best for their audience

Part 2 — Knowledge Transfer Plan

Outline how Meridian's internal team will be able to operate EDM Cloud independently after your engagement ends. Address:

• What documentation you create
• What training you provide
• How you confirm the team is ready before you disengage

Section C — AI Usage Log (Mandatory)

This is not a trick. We want to see how you work with AI — not whether you used it.

In a short section of your submission, document your AI collaboration process. For each significant interaction with an AI tool, briefly note:

• What you asked the AI to help with
• What it gave you
• What you kept, changed, or rejected — and why

Three interactions documented is sufficient. The log does not need to be exhaustive.

Format: .pdf, .doc, .docx, .rtf, .txt, .md

Video Walkthrough

Record your walkthrough as an MP4 or MOV file and upload it directly on the Provn platform as a separate file.

Structure & Time Targets

1. Summary (~60 seconds)

The migration challenge and your recommended approach — explain it as if you were briefing Meridian's CFO and CIO together.

2. Configuration Walkthrough (~2–3 minutes)

Walk through your EDM Cloud configuration design. Cover:

• Your key design decisions for node types, views, and validations
• Why you structured them the way you did
• What trade-offs you made

3. Migration & Risk Walkthrough (~1–2 minutes)

Walk through your migration approach and the risks you identified. Address:

• What is the single biggest risk to this migration?
• How would you mitigate it?

4. Mandatory AI Question (~1–2 minutes)

Walk through one moment where you disagreed with, pushed back on, or redirected what the AI gave you — and what you did instead. Your response must:

• Name the specific moment
• Explain what the AI produced that did not meet the bar
• Explain what you did differently, and why

5. Reflection (~30–60 seconds)

• What would you do differently with more time?
• What would you want to validate with Meridian's team before executing this plan?

Communication Note

Speak naturally. Communication is assessed on clarity of technical ideas, ability to explain Oracle EDM concepts to a mixed business/technical audience, and structured stakeholder awareness — not verbal polish, accent, or filler words.