on 01-02-2014 1:27 PM
Dear Friends,
For 31/12/2013 nearly 13 calls triggered and i will attach the algorithm details below
cal no. 44 to 48 call triggered with 100 increment in the reading.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
it seems 'Completion requirement' have not tick marked.
reading on 23.07.13- 22290 & 30.12.13- 24529, difference is 2239 /125 hrs cycle = 17.9 (18) calls
check also for 18.06.13, there might be similar case.
also check the scheduled period, is it kept beyond 31.12.13?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
reason behind lot of orders generated already answered, if you have still query, please mention clearly.
it is suggested further:
1. auto-schedule for Weekly/Fortnightly instead of Daily as meas. reading is not being entered daily at your end.
2. Do the tick 'çomp. requirement', it will prevent to release multiple orders on same day (if meas. reading difference is calculated more than 125 hrs with last reading).
It seems system created orders when you ran IP10 after entering reading 24529. System calculated missed maintenance at 125 hrs.
- When was last time maint plan schedule via IP10/IP30?
- When was last order confirmed? in July 2013?
- Is there 'Completion requirement' in maintenance plan?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.