digital transformation on shop floor

The impact of JD Edwards EnterpriseOne on Orchestration

I cut my technical teeth on JD Edwards Orchestration and am an avid proponent for UX One Personal Forms. So, it isn’t surprising to see which new features caught my eye at Collaborate 19 last week. Topping the list—Orchestrations and Form Extensions.

New features are full of potential, but a use case isn’t always apparent. Let’s dig in to a case study and consider the impact of EnterpriseOne Tools.

A JD Edwards Orchestration USE case

This year at Collaborate, I partnered with Stanley Black & Decker, Inc. (Stanley) to share their digital transformation journey.1 It began several years ago when I was brought in to assist with their process improvement goals. A significant lag time in reporting production data to JD Edwards (JDE) meant their completed inventory was always a step behind. The business demanded quicker results to respond to errors, guarantee resin availability, increase speed to market, and speed up accounting. 

Collecting and presenting live production data

Using the IoT Orchestrator, we synced shop floor data collectors to JDE for real-time reporting and material availability monitoring. We then displayed Stanley’s manufacturing execution system (MES) data on dashboards within JDE using CaféOne. This allowed employees to easily analyze live production data. They could react to issues within seconds of reporting and alert necessary parties.

Exceeding production goals with IoT Orchestrator

Inspired by this transformation, we wondered what else we could improve. And we set our sights on shipping. Using JDE’s IoT Orchestrator once again, we set up a process to automatically transfer inventory from weighpack to shipment locations. Employees could then print labels with the relevant supplier-mandated data we had captured earlier.

The new process quickly drew attention as Stanley exceeded customer requirements. In fact, one multinational customer was so impressed they adopted the setup as their own Gold Standard for suppliers.

How can EnterpriseOne Tools make an impact?

Open Standards 2.0

In the case of Stanley, data is collected and input to REST POST call. Then, it is sent as a string to the IoT Orchestrator. This week’s Open Standards 2.0 announcement gives us greater flexibility. The feature enables MES and other partner systems to discover orchestrations using the OpenAPI 2.0 standard. Now, we can use XML notation, as well as JSON, for orchestration inputs. 

High-Volume Data

High-volume data collection is paramount in a paperless production environment. But large data sets can really put your AIS Server to test. I’m excited to see how page size considerations can help. This feature allows you to choose the number of records that the server fetches at a time using the HTML Server. By collecting data in smaller chunks before returning the complete request, the server may be able to respond even faster.


Notifications have been on our radar to keep employees informed about critical issues. With Tools, notifications can take them directly to E1 apps, URLs, BI Publisher reports, and even orchestrations. And links aren’t the only new feature. We will also be able to attach PDF reports that are easily viewed in email, the Message Center, and/or the Notifications List.

Learn more about the new notification features here:

These are only a handful of the Tools updates Oracle shared at Collaborate 19. In my next post, I’ll share a case study fresh from my UX One Personal Forms presentation and explore new Form Extensions.

For help implementing these and other EnterpriseOne tools, visit

1 Case, Riesa, Frank Jordan and Thomas Liptak. “Digital Transformation in Action with JDE Tools — The Stanley Implementation Journey.”
Education session, Collaborate 19, San Antonio, TX, April 8, 2019.