# Prometheus Planning & Scheduling with JD Edwards EnterpriseOne maintenance > Source: https://netray.co/stack/prometheus-planning-scheduling-jd-edwards-enterpriseone > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Stack ## Short answer Prometheus Planning & Scheduling for JD Edwards is a Gantt-based maintenance planning tool that runs as a web application on JDE data, using JDE login credentials. Approved schedules and time confirmations post back to JD Edwards, which stays the system of record for work orders. ## Erp Oracle JD Edwards EnterpriseOne ## Erp Key jd-edwards ## On Prem true ## Product Prometheus Planning & Scheduling ## Vendor Prometheus Group ## Category EAM and maintenance planning ## Integration **Method:** Web application on JDE data with JDE credentials **Detail:** Per the vendor, planners sign in with their existing JDE credentials and work from the maintenance work orders held in EnterpriseOne (the Work Order Master, F4801, family). The tool reads that data, lets planners level and schedule on a Gantt view, and writes the approved dates and confirmations back. **Method:** Write-back of schedules and time **Detail:** Scheduled start and finish dates, craft assignments and confirmed hours are returned to JDE so costing, parts and reporting stay in the ERP. Ask Prometheus exactly which fields and which JDE programs it uses for your release. ## Data Flows **From:** JD Edwards **To:** Prometheus **Data:** Open maintenance work orders, status, priority, craft and estimated hours **Trigger:** Refresh when planner opens a schedule **From:** JD Edwards **To:** Prometheus **Data:** Equipment master, work centers and parts reservation **Trigger:** Planning session **From:** Prometheus **To:** JD Edwards **Data:** Approved scheduled start and finish dates and assigned crafts **Trigger:** Schedule approval **From:** Prometheus **To:** JD Edwards **Data:** Time confirmations and completion hours **Trigger:** Work confirmed by crew or planner ## Setup ### Define the planning scope **Detail:** Pick the plants, work order types and statuses the planners will schedule, so the tool does not load every historical order. ### Align JDE security **Detail:** Give planner roles the JDE permissions they need for work order updates, since the tool signs in with JDE credentials. ### Check craft and work center data **Detail:** Crew capacity, shifts and calendars in JDE drive the Gantt. Fix missing crafts and zero-hour estimates first. ### Map statuses **Detail:** Agree which JDE work order status means ready to schedule, scheduled and complete, and mirror that in the tool. ### Run a pilot on one plant **Detail:** Schedule one week of real work, compare confirmed hours to JDE, and adjust before wider rollout. ### Train planners and supervisors **Detail:** Cover leveling, backlog review and how confirmations reach JDE. ## Pitfalls - Poor estimates on JDE work orders produce an unrealistic Gantt, so the schedule looks fine but crews cannot meet it. - Missing parts reservations mean work is scheduled without material, which shows up as delays on the day. - Two people editing the same work order in JDE and in the scheduler cause overwritten dates. - Work order status customizations in JDE are not understood by the tool unless mapped explicitly. - Time confirmation posted late or twice distorts labor cost and backlog reports. ## Ai Layer ### Backlog triage **Description:** A private assistant can read JDE work orders and history to flag aged, duplicate or unestimated orders and propose a clean-up list for the planner to approve. ### Schedule risk check **Description:** Before a weekly schedule locks, compare it against parts availability and crew calendars in JDE and list orders likely to slip, with the evidence. ### Plain-language questions **Description:** Let supervisors ask which orders on a unit are overdue or which crafts are over-committed, answered from live JDE data with the query shown. ### Estimate suggestions **Description:** Draft hour estimates for unestimated work from similar closed orders, for a planner to accept or change. ## Alternatives - JDE's Capital Asset Management and Condition-Based Maintenance may be enough for smaller maintenance teams with simple scheduling. - A spreadsheet-based weekly schedule is workable if you have a handful of crafts and few shutdowns. - A full EAM replacement is a much larger project and is rarely justified only to fix scheduling. ## Faq ### Does Prometheus replace JD Edwards maintenance management? **Answer:** No. JDE remains the system of record for work orders, equipment, parts and cost. Prometheus adds planning and scheduling on top, then posts approved schedules and time confirmations back to JDE. Planners still need the right JDE security roles, and any customization of work order statuses should be reviewed with the vendor before rollout. ### How do users sign in? **Answer:** The vendor says the web application uses JDE login credentials, so there is no separate user directory to maintain for the scheduler. Role permissions in JDE still control what a person can change. Plan for password policy, expiry and single sign-on questions early, because the tool inherits whatever your JDE environment enforces. ### Can we add AI on-prem for maintenance planning? **Answer:** Yes. A model hosted on your own servers can read work orders and history, flag risks and draft estimates, while writes to JDE stay behind human approval. This avoids sending plant data to an outside service. Start read-only, such as exception reports and answers to questions, and only add approved write-backs once people trust the output. ## Source https://www.prometheusgroup.com/resources/prometheus-planning-scheduling-for-oracle-jd-edwards ## Search terms prometheus group jd edwards maintenance scheduling, jde maintenance planning and scheduling, jd edwards work order scheduling, enterpriseone gantt maintenance, prometheus jde --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json