On Jun 25, 2008, at 8:30 AM, Adrian Crum wrote:
If I want to maintain meter readings on a fixed asset, I should
not have to create a fixed asset maintenance. I might want to log
the copy count on a copier, or hours used on a projector. I should
be able to keep a log of meter readings outside of creating
maintenances.
On the other hand, a meter reading might trigger the creation of a
fixed asset maintenance - if that meter reading crosses a
maintenance threshold.
If no one objects, I'd like to refactor the meter reading code and
data a little bit to make it more usable.
Is this a declaration that you're giving up on seeking to
understand before you seek to be understood?
Either way, I look forward to hearing your thoughts on specific
improvements.
You are correct that there is place to record an arbitrary meter
reading... but from a business process perspective what would that
actually be used for? When and why would that data be entered into
the system?
A lathe operator records a meter reading after a production run. A
delivery driver records an odometer reading at the end of the day.
An office assistant records the copy count of a copier. I could go
on...
Each meter reading could be entered without the need to create a
maintenance. In addition (as I mentioned earlier) those meter
readings could trigger the creation of a maintenance - when they
cross a maintenance threshold.
When I was working with Anil on original requirements for this they
didn't do arbitrary meter readings, they just wanted reports of the
meter readings to look for when maintenance would be needed next and
such (ie read/check the meters, but there was no need to record them
except along with maintenance done, so they would know when the next
maintenance needed to be done, etc).
The main reason I was thinking of where meter readings would be
valuable is in manufacturing. You actually need that sometimes to
determine the cost of operation the machine and associating it with
the cost of goods produced, or at least keep track of how much the
machine is used for different types of products, etc.
Anyway, the entity would be really simple, a lot like
FixedAssetMaintMeter, but with a few differences, something like:
FixedAssetMeterReading
fixedAssetId*
productMeterTypeId*
readingDate*
readingReasonEnumId (could be optional; use begin reading, use end
reading, calendar/scheduled reading, etc)
meterValue
workEffortId (if the reading was done before or after a certain work
effort)
-David
