Company Type
Alstom Power — Turbine & Generator Repair, the Global 500 turbine/generator repair division; shop-floor scheduling inside the Estimating-to-Cash operating model. One of the four stated exceptions to the full-lifecycle claim: architected and designed by the principal; built by a programmer hired and directed for the purpose.
What Drove the Need
A master schedule was needed across estimating, bidding, contract, scheduling, execution, delivery, and closure with a 6–12-month look-ahead
Up to 50 users, 15–20 concurrent, pulling real-time JDE data into Project without re-keying
Business Impact
Supported the ETC operating model that took cycle times from 8+ months to under 3 (Case 1)
Systems/Data Integration
Bi-directional JDE World ↔ Microsoft Project Server; Oracle data warehouse
Design
Real-time pull filtered by five key fields (work order business unit, order type, status; routing order type and operation status) against user-maintained master lists with per-combination Add/Update/Delete actions mapped to Project fields — a status-code-driven ETL rule table maintained by users, not code
Checked-out-project protection; separate test/prototype environment
July 2005 prototype in ODBC-enabled Access/VBA producing XML per job loaded via the PDS driver
Technology Stack
MS VB.NET; MS SQL Server; MS Project Server
JDE World on DB2/AS400; Oracle data warehouse integration
Bi-Directional JDE ↔ MS Project Server Interface
Imports JDE Work Orders and Routing operations into Microsoft Project for shop-floor scheduling and exports schedule changes back to JDE, updating work orders and routings for MRP and production execution.
