I'd like to talk with someone who is processing work orders in MT Cloud, particularly those with a large volume of work orders. WOs are the core of our business and there are concerns that we may not see the performance that we need.
Hi @John Panzenhagen , what problems are you seeing? We've built an Experience Designer app recently that automates a lot of the complexity in reporting WOs for one of our customers.
@Alistair Johnson we aren't on cloud yet. In our on-prem environment, there are times that the system is having problems keeping up with the volume of work orders. We process about 10,000 work orders per day. If someone has to do a bulk change of more than 100 orders, it slows the process down. Work orders are our lifeblood, and if it takes more than 10 seconds for one to create and print a flow sheet, the line is impacted.
We are moving to cloud, and want to see if the dynamic autostart jobs and dynamic resource allocation of AWS are able to alleviate these issues.
We currently have a mashup to simplify the user processing, and will be looking at an EDA or H5 app in cloud.
@John Panzenhagen Sounds like you're on the way to solving this. Look at xtendM3 APIs too for your EDA/H5 app if you're making multiple calls to perform a task as there's performance improvements possible from calling a series of these within the xtendM3 API as you avoid the latency of round tripping back to the EDA/H5 app. You're probably already looking at some form of RPA so you can assess performance under load? I'd bake that in to the migration process so you can identify early if you're seeing the benefits you're seeking. We have sites with thousands of MOs per day that run without any issues, but WOs do behave somewhat differently.
