David E Jones wrote:
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)
Why not add those fields to the existing entity? I did something similar
in the patch I just uploaded to Jira.
Where I work we have thousands of fixed assets that require maintenance.
Our maintenance department consists of a supervisor, four full time
maintenance workers, and some production workers who are used part time
(they wear two hats).
What we need from a fixed asset maintenance program is the ability to
set up recurring maintenances, and have them automatically assigned to
the appropriate personnel. I picture two triggers for that - timed
intervals (recurrence entries) and meter readings.
Doing meter readings after the maintenance is done is not useful here.
Our maintenance staff is very busy - they need the program to tell them
when maintenance is due.
-Adrian
