OneVision

JD Edwards EnterpriseOne

A good system to stay on, if you stay on it deliberately.

EnterpriseOne implementations, 9.2 upgrades, tools releases, CNC, and re-implementations that undo years of accumulated customization — plus an honest view on when moving off it is worth it.

Draft for review — Module coverage and version statements on this page are drafts and go stale fast. Confirm them against what OneVision currently staffs and supports.

You are probably here because

  • You are several tools releases behind and nervous about getting current
  • Your customization layer is undocumented and the people who built it have left
  • You are being pushed toward a cloud re-implementation and want an independent view on whether now is the time
  • You need EnterpriseOne support that understands manufacturing and project costing, not just the technical stack

How we think about it

JD Edwards remains a strong fit for manufacturing, construction, and distribution businesses, and plenty of organizations running it well have no good reason to move. The ones in trouble are usually not in trouble because of the product — they are carrying a decade of customizations, a tools release several years behind, and nobody left who remembers why either happened.

We are straight about this. If staying on EnterpriseOne is the right answer, we will modernize it, get you current, and support it. If moving to a different platform is the right answer, we will say that too — and because we do not implement the product you would be moving to, there is nothing in it for us either way.

What we do on JD Edwards EnterpriseOne

Upgrades & tools releases

Getting current on 9.2 and staying current on tools releases, with customization impact assessed before the upgrade rather than discovered during it.

Re-implementation

Rebuilding on standard functionality where years of customization have made the system unmaintainable — retiring the extensions nobody can justify.

CNC & technical services

Configurable Network Computing administration, environment management, Orchestrator, and integration work.

Stay-or-move assessment

An independent, costed comparison of modernizing EnterpriseOne versus replacing it — including the do-nothing case — before you commit to either.

Module coverage

The modules we staff

If your module is not on this list, say so when you get in touch. We would rather tell you we are not the right firm than learn it in week six.

Financials

  • General Accounting
  • Accounts Payable
  • Accounts Receivable
  • Fixed Assets
  • Advanced Cost Accounting

Distribution & manufacturing

  • Inventory Management
  • Procurement
  • Sales Order Management
  • Shop Floor Management
  • Product Data Management
  • Quality Management

Projects & assets

  • Job Cost
  • Contract & Service Billing
  • Capital Asset Management
  • Change Management

Technical

  • CNC / tools releases
  • Orchestrator
  • AIS / integrations
  • UDO management

Don’t take our word for it

The JD Edwards EnterpriseOne community meets at INFOCUS

The JD Edwards conference, run by the independent Quest Oracle Community rather than by Oracle or by a systems integrator. It is where the roadmap gets discussed candidly and where you can ask someone running your configuration what it is actually like — which is worth more than any vendor reference call.

Visit the INFOCUS site
  • Run by Quest Oracle Community, an independent user group
  • Oracle roadmap sessions, release updates, and hands-on education
  • Tracks across manufacturing & distribution, financials, HCM, system administration, and capital asset management
Straight answers

Questions we get asked

Is JD Edwards a dead end?

No. Oracle has committed to EnterpriseOne well into the next decade, and for a lot of manufacturing and construction businesses it does the job better than a cloud re-implementation would. The dead end is running it several tools releases behind with undocumented customizations — that is a maintenance problem, not a product problem.

How far behind is too far behind on tools releases?

The practical answer is: far enough that getting current has become a project rather than a maintenance task. If you are asking the question, you are probably there. The upgrade gets harder, not easier, with every release you skip.

Will you tell us to replace EnterpriseOne?

Only if that is what the numbers say. We do not sell the platform you would be replacing it with, so we have no commercial reason to push you either direction — and we have told clients to stay on EnterpriseOne when the migration case did not hold up.