Oracle Blog Network

Rapidflow Solution

Fueling Your Digital Transformation

How EV Battery Planning Teams Move to Oracle Redwood Supply Planning Without Disrupting Plan Cycles

Nishita Joshi
Nishita Joshi
Nov 16, 2026
How EV Battery Planning Teams Move to Oracle Redwood Supply Planning Without Disrupting Plan Cycles

How do you move a planning team to a new user experience when plan runs, exception reviews and release decisions still have to happen on schedule?

EV battery planners cannot pause for a migration. Customer demand changes frequently, supplier lead times are long and variable, and every plan run brings exceptions to work through.

That is the case for a managed move to Redwood Supply Planning. With the right guidance, planners keep their recurring planning cycles while gaining access to the newer capabilities in Oracle Fusion Cloud Supply Planning.

How do you migrate planners to Redwood without disrupting recurring planning cycles?

Migrate users in a managed sequence, with guidance on navigation and on how Redwood differs from the classic pages. Then support them through the workflow questions that follow go-live, so recurring plan runs and reviews stay on schedule. Before migrating, confirm the Redwood pages are enabled and users hold the required privileges.

Key takeaways

  • Redwood Supply Planning is the Redwood user experience for Oracle Fusion Cloud Supply Planning, and newer capabilities such as Lead Time Insights and AI agents are delivered through it.
  • Disruption risk sits in navigation, differences from the classic pages, access setup and post-go-live workflow questions.
  • A guided migration keeps recurring planning cycles running.
  • Rapidflow migrated planning users for a commercial EV battery manufacturer and supported them after go-live, as the foundation for later phases.

What is Redwood Supply Planning?

Redwood Supply Planning is the Redwood user experience for Oracle Fusion Cloud Supply Planning. Planners reach it through the common Supply Chain Planning work area, where they can access, analyze, compare and simulate a supply plan using flexible page layouts, advanced searches, plan actions and planning tasks. A plan selector lists the plans that have run successfully, and pages can be grouped into page groups for specific analysis, such as exceptions and late demands.

Why do EV battery planning teams need Redwood?

Newer Supply Planning capabilities, including Lead Time Insights and AI agents, are delivered through the Redwood user experience. For a manufacturer supplying battery modules and packs, these address real pressure: high-value, specialized components with long and variable supplier lead times, frequently changing demand, and a high volume of plan exceptions. Staying on the classic interface means staying outside those capabilities.

Why can a Redwood migration disrupt plan cycles?

The plan calendar does not stop for a user experience change, and a planner who cannot find a familiar screen still has to release orders and review exceptions that day. Four things tend to cause friction:

  • Navigation: planners know the classic pages by habit.
  • Differences from classic pages: familiar workflows look and behave differently.
  • Access: Redwood access depends on privileges granted through job roles, so a missing privilege can leave a planner without the work area.
  • Questions after go-live: most workflow questions surface once planners run real cycles.

What changes for planners moving from classic pages?

Classic Redwood
Layouts on the Supplies and Demands page Views, which planners can save, restore or delete
Actions menu options such as Mark for Release Toolbar buttons that work the same way
Separate planning work areas A common work area, with the plan last opened in either experience as the default
Setup and configuration actions Some are not yet in Redwood and remain in the classic experience

Views are the counterpart to classic layouts, and toolbar buttons such as Mark for Release work like the classic Actions menu options. The default plan is the one last accessed through either the classic or the Redwood work area, and some setup and configuration actions are not yet available in Redwood.

What can planners do in Redwood from day one?

Planners find familiar capabilities in a more flexible layout:

    • Build their own pages. Planners create pages and page groups by dragging graphs and tables from a content library, with up to four visualizations per row
    • Compare plans. Compare mode shows the same measure from up to three plans side by side in a single row.
    • Manage supplier lead times. The Suppliers visualization lets planners maintain planning attributes such as lead times, with the same editable fields as the classic version.
    • Search consistently. A common search and filter component works the same way across planning modules, and columns can be dragged and dropped.

What does Redwood Supply Planning need before users move?

The Redwood supply planning pages are turned on with a site-level profile option, Redwood Supply Planning Pages Enabled. Users also need privileges, granted through seeded or custom job roles, that decide which plan types and which work areas appear in the plan selector.

How does a managed migration work step by step?

This is an illustrative sequence, drawn from Oracle’s documentation and Rapidflow’s engagement.

      1. 1. Enable the Redwood supply planning pages and confirm privileges for each planner role.
      1. 2. Identify the planning users and plan types in scope.
      1. 3. Migrate planning users to the Redwood experience.
      1. 4. Guide planners on navigation and on how Redwood pages differ from classic ones.
      1. 5. Note which setup and configuration actions still sit in the classic experience.
      1. 6. Support go-live by answering workflow questions as planners run real cycles.
      1. 7. Consolidate recurring questions into reusable guidance.

Steps 3, 4, 6 and 7 reflect work Rapidflow carried out for its client. Steps 1, 2 and 5 are general practice drawn from Oracle’s documentation.

How did Rapidflow support the move for a commercial EV battery manufacturer?

Rapidflow, as the Oracle implementation partner, supported a US-based commercial EV battery manufacturer in two connected phases. Phase 1 came first by design: strengthen the foundation, then add AI.

    • Redwood migration: planning users moved to the Redwood experience, giving planners a modern, consistent workspace and access to the latest Supply Planning capabilities.
    • User guidance: navigation, differences from the classic pages and workflow questions raised after go-live, so recurring planning cycles continued without disruption.
    • Support during and after: help stayed in place through the transition, not just on go-live day.
    • What followed: Lead Time Insights and Plan Comparison in Phase 1, then AI agents in Phase 2. [Plan Comparison and root-cause analysis post]
    • Ongoing support: day-to-day answers on exception handling, plan runs and reviews, pegging questions, and engine topics such as fixed lead time and the link between projected available balance (PAB) and safety stock.

For the client, the engagement went beyond feature enablement. It helped establish a more modern, data-driven and AI-assisted supply planning operating model, and the move to Redwood was the first step. The result is a planning team on a modern workspace with a scalable base for adopting new Oracle Supply Planning capabilities.

How do planners keep adoption on track after go-live?

    • Capture the questions. Turn recurring ones into reusable guidance, which cuts repeat queries.
    • Keep pages light. Oracle recommends keeping a page group under 10 visualizations for better performance.
    • Review on a cycle. Revisit planner feedback, planning parameters and new Supply Planning capabilities regularly, so adoption keeps pace with what Oracle releases.

Ready to move your planners to Redwood?

Explore Rapidflow’s AI-enabled, insight-driven supply planning solution for EV battery manufacturers, to read how the engagement worked. We support planning teams across North America, EMEA and APAC.

 

Frequently Asked Questions

Migrate users in a managed sequence with navigation guidance and support for post-go-live workflow questions, so plan runs and reviews continue on schedule. Confirm access and enablement first.

It is the Redwood user experience for Oracle Fusion Cloud Supply Planning, used to access, analyse, compare and simulate supply plans.

Lead Time Insights and AI agents are delivered through Redwood, and they address long supplier lead times, changing demand and high exception volumes.

The Redwood supply planning pages must be enabled, and users need privileges through job roles that control which plans and work areas they can open.

Some setup and configuration actions remain in the classic experience, and the plan last opened in either experience is the default in Redwood. Check your release’s documentation for the current list.

Layouts become views, and familiar Actions menu options appear as toolbar buttons. Planners need guidance on the rest.

Navigation, differences from the classic pages and answers to workflow questions raised after go-live.

Navigation, differences from the classic pages and answers to workflow questions raised after go-live.

Lead Time Insights and AI agents are delivered through Redwood. Rapidflow enabled Plan Comparison alongside the migration.

Provide day-to-day answers, consolidate recurring questions into reusable guidance, and review feedback and new capabilities regularly.

Share This Article
Spread the knowledge with your network
LinkedIn Icon Facebook Icon YouTube Icon
info@rapidflowapps.com

Explore Rapidflow AI

An accelerator for your AI journey