Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from sapnomad on May 29 at 12:35 PM I should add that I do have my shift factors set to 100% and call horizon 0%.
| | | ---------------Original Message---------------
From: Vlad Selsky
Sent: Thursday, May 29, 2014 11:00 AM
Subject: Single Cycle Count Scheduling
Please help me understand system behavior for a single cycle count plan.
Say I have it set up with an annual estimate of 52,000 and PM to be done weekly, ie a count of every 1000. I initialize my counter at 100,000. When I schedule my first order, it is set a week out for 6/5 for projected counter reading 101,000. So far so good.
Now technician decides to do the PM work a week early. He confirms the work order today (5/29), and a counter reading of 100,500 is entered. The system responds by scheduling a new order for 6/2 and keeps next projected counter reading at 101,000.
Questions:
1) Why is the next counter reading kept at 101,000 instead of 101,500? Say a bicycle chain needs to be greased every 1000 revolutions of the chain. If I grease the chain after only 500 revolutions, why would the system not schedule the next greasing 1000 revolutions out? (And is there a setting to enable this?!)
2) Why did system pull in the next work order a few days early to 6/2? If I have consumed my 52,000 annual estimate at an accelerated rate, shouldn't all subsequent orders be stretched out (still 52 weeks, divided by 51,500)?
Thanks,
Vlad |
| Reply to this email to post your response. __.____._ | In the Spotlight Become a blogger at Toolbox.com and share your expertise with the community. Start today.   _.____.__ |
