Do you replace our JD Edwards partner?

Usually not. Most JDE estates already have a partner or an internal CNC team, and we work alongside them — anything that touches your environments or a tools release is coordinated with whoever runs them. What we add is the analysis, and the build work around the edges that a managed-services contract tends not to cover.

Which releases do you work with?

EnterpriseOne 9.1 and 9.2, and migrations off JD Edwards World on the AS400.

Can you take over a customization someone else built?

Yes. It starts as a fixed-fee assessment of what the change was meant to do against what it actually does, and then you decide what happens next.

Do we need a full specification before you quote?

No. A well-defined change can be quoted from a short scope annex. Larger or contested work starts with analysis, because that is where JD Edwards projects usually go wrong.

← All systems

JD Edwards EnterpriseOne integration and development.

Integrations, enhancements and the applications that sit beside JD Edwards — scoped by an analyst who has spent years inside EnterpriseOne maintenance, inventory and supply chain, and built by our engineers.

What we do

Integrations: Orchestrator and AIS REST services, business services, and the flat-file interfaces that still run a large part of most JDE estates — connecting planning, transportation, warehouse, scanning and finance systems, with the failure cases designed rather than discovered.
Enhancements and configuration: Changes inside EnterpriseOne — applications, reports, processing options and business rules — specified first, so the change is scoped and testable before it goes near your next upgrade.
Applications alongside JDE: When the need does not belong inside the ERP — an inspection app, a customer portal, an approval flow — it is built beside it, reading and writing through supported interfaces so JD Edwards stays the system of record.
Reporting: Reports and dashboards on JDE data that people can maintain, including replacing the ones nobody dares touch.
Upgrades and migrations: Moves off JD Edwards World on the AS400 and between EnterpriseOne releases: retrofit analysis of your customizations, data migration templates, test scripts and UAT.
Specification and review: Functional and technical specifications for JDE work — for our engineers, or reviewed before they go to your existing partner or an offshore team.

Where it usually hurts

If one of these sounds familiar, it is the kind of problem we are called in for.

Parts are not issued to work orders consistently, so maintenance cost per asset is wrong and nobody trusts it.
Replenishment runs from a spreadsheet beside JD Edwards because the reorder logic in the system never matched reality.
A flat-file interface fails quietly, and someone finds out at month end.
Years of undocumented customizations, which is why the upgrade keeps being postponed.
A process JDE handles badly, and a quote that assumes modifying the core to fix it.

Where this experience comes from

Our lead analyst's career history, described by sector — not an Elarion client list. More on the About page.

An EnterpriseOne 9.1 implementation off JD Edwards World (AS400) at a food manufacturer: supply chain process redesign, functional specifications for Oracle Demantra and MercuryGate integrations, data migration templates, and a month-end close for a make-to-order business.
Supply chain enhancements on EnterpriseOne 9.1 at a forest products company: demand planning, sales and operations, and inventory control; specifications for Oracle Demantra and OTM integrations; barcode-enabled cycle counting; oversight of an offshore development team.
Maintenance and stores at a public transit operator: automated material issuance to work orders, purchase orders generated from reorder points and vendor lead times, DRP transfers between warehouses, and RF scanning for spare-parts traceability.

Questions buyers ask

Do you replace our JD Edwards partner?: Usually not. Most JDE estates already have a partner or an internal CNC team, and we work alongside them — anything that touches your environments or a tools release is coordinated with whoever runs them. What we add is the analysis, and the build work around the edges that a managed-services contract tends not to cover.
Which releases do you work with?: EnterpriseOne 9.1 and 9.2, and migrations off JD Edwards World on the AS400.
Can you take over a customization someone else built?: Yes. It starts as a fixed-fee assessment of what the change was meant to do against what it actually does, and then you decide what happens next.
Do we need a full specification before you quote?: No. A well-defined change can be quoted from a short scope annex. Larger or contested work starts with analysis, because that is where JD Edwards projects usually go wrong.

Related services

Working in JD Edwards EnterpriseOne?

30 minutes, free. Bring the problem, or the change you already have in mind.

Book a discovery call