SOLVED!Turns out the Alias of the column (back in the Data Source Designer) is what is used as the parameter name to pass.Data Source Designer: IE Element Designer Aurena URL:/lobby/a23db9e8-091…..?pageParams=MACHINE_NAME:$[Manager Name] This can be closed.
Correct, creating a new revision ‘clears the deck’ of active and historic work orders and it was something I was really trying to avoid. I really don’t want to go and create new revisions of hundreds of work task templates when we decommission a site. It really appears the error is poorly written.
Hello @pekase ,Interesting - yes, it does allow for negative numbers and that does remove the old Published Demand. I appreciate the feedback since I wouldn’t have tried that based on the help for that line.I agree that additional testing is needed to see what impact this has. I’ve tried it in our TEST environment this morning and it didn’t create demand when the work order was created. More work to be done before I say this has been resolved, so I’d appreciate any additional feedback anyone can provide!Thank you.
Hello @pekase ,Thank you for the response. Unfortunately shortening the ‘PM Inventory Part Demand Horizon (Days)’ will not work in this instance because all the dates it’s planning for are in the past. That would work fine for future dates, but not when the machine has shut down and those predetermined ‘Due Dates’ are in the past.Making all these non-generatable is not a good option either because it would be a constant battle to keep on top of them. I’m not in control of how long the machines are shut down, that is up to the organization that is contracting with us to do the work. They may tell us we are shut down for many months, only to come back a week later and tell us to start the machine up for more work. With so many machines, I don’t have the resources to ‘micro manage’ all the PM’s.I believe that demand shouldn’t be automatically created this way. It would be perfectly acceptable to generate demand for one of the past lines, but it should stop there. No organization is going
@Nipun Gunaratne - thank you for the response. Prior to creating the original post I read all of what you posed above in the IFS help documentation and it wasn’t clear. The first image below is an example of what I’m attempting to explain in words (keep in mind, I stated there were close to 300 different PM Actions for a single machine, most have materials required).This machine has been shut down since April. As you can see, the PM Job is “planning” for monthly maintenance even though on 5/20 the remaining hours before the next service was 670 (the 513% Due appears to be calculated based on the date, not the condition). That hasn’t changed since April, yet every month it’s generating inventory part demand for a work order that hasn’t been created. An organization would never complete 5 work orders (in this specific example) for the same PM during a shutdown. Why is it planning for this even though the last recorded value has not yet reached the Planned Value? This creates significant
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.