Tata Advanced Systems · Aerospace & defence
Scheduling engine kept, reimplementation avoided
Data transformation moved out of the scheduling engine so it only computes schedules. Run time dropped sharply, and a costly replacement programme was avoided. Live in three plants.
- Operation
- Three plants live
- Systems
- ERP, scheduling engine, Excel master data files
- Functions
- Scheduling and business teams
- First answer live
- Across three plants
- Plants live
- 3
- Scheduling run time
- Significantly reduced
- Reimplementation cost
- Avoided
From the Tata Advanced Systems deployment, published with their permission.
The situation
Existing ERP and scheduling systems were surrounded by a lot of Excel files holding master data that never made it into the ERP.
With significant growth, scheduling software performance had to improve — the alternative was looking for a different product and an entire reimplementation, which is very expensive.
Human errors in the Excel master data were sending the scheduling algorithms into infinite loops.
What they did
Moved all data transformation calculations out of the scheduling engine and into FactoryThread, leaving the engine to do scheduling computation only.
Validated and corrected the Excel-sourced master data before it reached the algorithm, so bad rows stop causing infinite loops.
Applied incremental data techniques and warning analytics so only what changed is processed, and anomalies surface early.
What changed
Scheduling time dropped significantly, and the scheduling team continues on the software they already know.
A full replacement and reimplementation programme was avoided.
FactoryThread is now live in three plants, and is under consideration to replace Alteryx across their factories.
More stories
Start here
Ask one question. Get one answer. Today.
Start on the free tier with a single connection, or bring a real question to a working session and we will build the first answer with you.
Free tier · No credit card · Cloud or self-hosted