Yes. With Managed Services 24/7, we can take over management entirely—or handle just a portion of it alongside your own team. This includes monitoring, incident response, JDE Tools updates, security patches, and performance tuning.

Don't just consider when you want to upgrade, but above all, consider which technical decisions and dependencies you need to take into account.

Identify which custom Java business functions, integrations, and tools you use. A Java upgrade often affects more than just the servers.

Determine whether you rely on IBM AIX, Oracle Solaris, IBM DB2 LUW, WebSphere, Kubernetes or Docker containers, Oracle SOA Suite, Oracle Enterprise Manager, or HP-UX. Keep the timing in mind: some of these technologies will have a different support status starting with Release 25 or 26.

If your current deployment processes are still based on Platform Pack installers, now is a good time to gain knowledge and experience with One-Click.

In that case, it's a good idea to define a migration path to Oracle WebLogic.

Check whether there are any 32-bit components remaining in your environment and whether your Deployment Server is ready for future ESU delivery.

Think about instantly leveraging UX One dashboards, simple Orchestrations and process optimizations that deliver efficiencies from day one.

We use a proven approach with multiple rounds of migration, validation and testing scenarios. This ensures that data is correct, complete and reliable.

Greenfield is a completely new setup from scratch. Brownfield is migrating and optimizing an existing environment. We advise which approach is best for your organization.

We work on the principle of standard where we can, customization where we must. We often replace customization with UDOs or standard functionality so that upgrades and management remain easier.

The lead time varies, but usually between 6 and 12 months. With a clear roadmap and phased approach, we keep a grip on time and budget.

Through clear SLA agreements and periodic reports on performance, availability and incidents.

Flexible: we supplement where needed. This can be completely unburdening or complementary to your own team.

Yes. Our support includes process flows, UDOs, roles and permissions, and functional updates.

Among other things, server management, database, middleware, JDE Tools updates, security patches and performance tuning.

Standard support provides coverage during business days. 24/7 support guarantees monitoring and intervention day and night.

We do this by performing a license optimization. We analyze the current usage of your modules and compare this with your license package. In this way, we identify unused functionality and adjust your licenses so that you only pay for what you really need.

An upgrade or migration can have a significant impact on your licenses. We therefore perform a detailed analysis in advance to determine whether your current licenses are suitable, or whether any adjustments are needed. This prevents compliance problems and unexpected costs during or after the project.

Improvements in Orchestrator, UX One dashboards and security enhancements that instantly make you more productive and secure.

Yes, in many cases it is possible to reuse or modify existing licenses. reuse or modify them. This is an important part of our license optimization.

We analyze your customizations and interfaces in advance and minimize retrofits. We often replace customizations with UDOs or standard functionality.

Yes. Oracle links new functionality and security fixes to the most recent Tools Release (such as R26). Without an update, you will miss out on innovations.

Many organizations choose a set rhythm (e.g., semi-annually) so that updates remain predictable and manageable.

Patching is implementing a loose fix. Code Current is a structural update policy that includes Tools Releases, security and new functionality.

It depends on your unique business processes and growth objectives. Our experts perform an analysis to determine which modules deliver maximum value and avoid unnecessary costs.

Think of UX One landing pages, watchlists, and simple orchestrations. They immediately provide more insight and reduce manual work.

Not necessarily right away. But around Release 27, there will be significant changes to the technical foundation: WebLogic only, Java 21, 64-bit ESUs only starting in 2027, and Web PAR only starting in 2028. Our advice? Put Release 27 on your roadmap now, so you can choose the timing—not the deadline.

That depends on the type of upgrade, the size of your environment, and the extent of testing required. For a standard tools upgrade, we typically estimate 80 to 100 hours of work, or about 10 to 12 business days. An application upgrade is a different story: the time required depends on your customizations, the volume of your data, and the development work involved. After the impact scan, you’ll know exactly where you stand.

We fully map this out in the impact scan. Standard solutions where possible, custom solutions where necessary: wherever UDO’s or standard functionality can replace your custom solutions, we’ll recommend that. We’ll carefully migrate and test the rest.

A tools upgrade updates the technical layer of JD Edwards: the Tools Release, which includes Orchestrator, UX One, and security. An application upgrade brings new functionality and ESUs to your modules. You often combine them into a single project.

Not always. We examine beforehand whether your current version is suitable or whether an upgrade will benefit you.

Low-code/no-code platforms are updated automatically. We ensure that integrations with JD Edwards remain compatible.

In many cases, yes. We analyze together what is cost-effective and technically feasible.

It depends on your IT landscape and goals. We have extensive experience with Oracle Visual Builder, which integrates extremely well with JD Edwards. In addition, we are actively exploring other leading platforms such as Mendix and Microsoft Power Platform.

Yes. We provide secure architecture and integration, including authorizations and data security

• Yes. We offer 24/7 Managed Services for monitoring, updates and support.

We plan migrations carefully and align them with your business deadline or operating rhythm. This keeps your environment maximally available and minimizes impact.

We test these beforehand and ensure that they continue to work smoothly after migration.

Both is possible. Together, we will consider which order provides the most benefit and least risk.

Yes, we support both full and hybrid cloud models, depending on your IT strategy.

Higher adoption of JD Edwards, fewer errors, less reliance on customization and a team better prepared for future changes.

Yes, you can. We prefer to train in an environment that connects to your daily practice.

No, training can be on-site, online or hybrid.

For end users, key users, functional and technical administrators. Each target group is given an appropriate level.

We offer both. From standard modules to full customization tailored to your processes and JDE configuration.

With an ESG impact scan and proof of concept, you can often get initial results within a few weeks.

No. Every organization dealing with ESG reporting benefits from the framework - from finance to retail and logistics.

Through existing processes, external integrations or Orchestrator flows, sustainability data is collected automatically.

Yes. The framework supports reporting in accordance with CSRD, GRI and other international standards.

No, the Sustainability Framework is native to JD Edwards 9.2. With configuration and integrations, you leverage what you already have.

Orchestrations run within the JD Edwards security framework. Users can only access the data and processes for which they have permissions, ensuring security.

Absolutely. Orchestrator is ideally suited for integrations with external software and devices via APIs. This ensures fast and efficient data exchange.

No. With training and guidance, your team independently creates orchestrations and workflows. We provide support, from start to finish.

Yes, in many cases customizations can be replaced by Orchestrations or Logic Extensions. This makes your environment more flexible and simplifies future upgrades.