So many of our customers repair products based on hours of usage. replace belts at 300 hours, inspect something at 200 hours. We should have the ability to build maint schedules under products or assets which then automatically generate work orders or work order tasks when these Timers are met.
Comments
This could be run off Asset Property data to make the solution adaptable to different scenarios.
Related to this we have an asset property for machine cycle counts where we forecast what the current cycle count approximately is based on previously recorded data re-calculated each week.
Category: Agreement
Reaction on Matt Klein.
'We have customers who want some of these readings to be conditionally required based on service and equipment/asset type, as well. For example, tech must input an "engine hours" reading when conducting a PM on a particular asset or asset type.'
Until using IoT the above mentioned solution direction is very feasible for customers.
Category: Agreement
Agree with Matt Klein that this is the AM Maintenance Plan feature.
Category: Agreement
Forgot to comment: Regarding the questions asked, here's my perspective if helpful:
Q: Is this a simple timer (i.e. things run continuously) or does the equipment start/stop? We suspect the latter.
A: This is about actual equipment operation, so yes the latter. For example: an odometer on a vehicle.
Q: If the equipment starts/stops and if the asset is connected, we could potentially use IoT signals or Flow to pass run-time details back to the system. Otherwise, how have you heard or given thought to how this run information would be captured?
A: IoT would be nice, but definitely not prominent enough yet. The ability to capture "meter readings" - or whatever it might be called - would be a distinct feature, with close tie-in to work order management in the field so it would be easy for techs to provide inputs. Maybe this could leverage the Asset Property Values and Property Log vs create a new feature, but usability for mobile users is extremely important. We have customers who want some of these readings to be conditionally required based on service and equipment/asset type, as well. For example, tech must input an "engine hours" reading when conducting a PM on a particular asset or asset type.
Category: Agreement
Yes, please! We get this one all of the time.
A potential model for FS/Dataverse is the D365 F&SCM EAM feature set and its concept of a "Counter". The "Maintenance job types" and "Maintenance job type defaults" would also be great concepts to have.
There is plenty more that could be leveraged from F&SCM EAM, as well, along with dual-write tie between FS/DV and F&SCM on all aspects of asset management. I'm guessing this is the broader vision, hopefully? D365 Project Ops brings in a few of the shared concepts, which is great.
Category: Agreement
Administrator on 3/5/2019 8:14:32 PM
Thank you for your feedback. We think this idea has merit.
We need some more details to understand this suggestion better:
Obviously, we would want such a feature to be useful and not another manual task. We're eager to see what kind of votes this gets.
Sincerely,
PM, Jason Cohen
Microsoft.