This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Is anyone successfully using the MXMETERDATA object structure on its own to
log meter readings against a work order? While I can do so with a larger
combined object structure I believe the intent is that MXMETERDATA should
provide a single interface for capturing meter readings in a variety of
formats - however when a WONUM is references it gives java exceptions with
little detail as to the cause.
How are others bringing meter readings in via integration against a work
order?
Maximo 7.5.0.4
Chris.
Chris,
We are setup to load by spreadsheet but we do it against an asset or a location since that is where the meter is set up against.
Roy Cline
Phone: (203) 492-8189
Cell: (203) 640-9743
FAX: (203) 492-8462
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Chris Lawless
Sent: Tuesday, January 21, 2014 10:57 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Meter Readings against a WO Using MXMETERDATA
Is anyone successfully using the MXMETERDATA object structure on its own to log meter readings against a work order? While I can do so with a larger combined object structure I believe the intent is that MXMETERDATA should provide a single interface for capturing meter readings in a variety of formats - however when a WONUM is references it gives java exceptions with little detail as to the cause.
How are others bringing meter readings in via integration against a work order?
Maximo 7.5.0.4
Chris.
Its probably because there is no wonum on the meterreading table
They use assetmeter and locationmeter tables to take the reading in the work order screen these tables only ever have the last meter reading for the asset / location meter and DON'T reference the work order
I can see there is a wonum field on the non-persistent table used by mif for meter readings but I don't know why it's there
This is very annoying as I wanted to use characteristic meter's to hold pass / fail results but there is no direct reference between the reading and the work order (not that I can find anyway)
The only persistent relationship is on tasks where you can enter a reading value but this is related to the condition monitoring application and requires a point number, it writes a measurement and also write's to the meter reading table. So I guess you could load your readings as work order updates (woactivity never tried it though) but it means you would need a point for each meter and the location / asset it was used at .
Rgds Ian
BPD Zenith Ltd
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Cline, Roy
Sent: 23 January 2014 14:23
To: MAXIMO@yahoogroups.com
Subject: RE: [MAXIMO List] Meter Readings against a WO Using MXMETERDATA
Chris,
We are setup to load by spreadsheet but we do it against an asset or a location since that is where the meter is set up against.
Roy Cline
Phone: (203) 492-8189
Cell: (203) 640-9743
FAX: (203) 492-8462
From: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com> [mailto:MAXIMO@yahoogroups.com] On Behalf Of Chris Lawless
Sent: Tuesday, January 21, 2014 10:57 AM
To: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
Subject: [MAXIMO List] Meter Readings against a WO Using MXMETERDATA
Is anyone successfully using the MXMETERDATA object structure on its own to log meter readings against a work order? While I can do so with a larger combined object structure I believe the intent is that MXMETERDATA should provide a single interface for capturing meter readings in a variety of formats - however when a WONUM is references it gives java exceptions with little detail as to the cause.
How are others bringing meter readings in via integration against a work order?
Maximo 7.5.0.4
Chris.
GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.
**************************************************************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
**************************************************************************************************************
I agree, however I believe that the idea is that MXMETERDATA acts as a
single point of call for all meter readings, it expects an Asset or
Location, optionally a WONUM and it is suppose to put the reading in the
right place based on the data that is supplied - such that you don't need
to worry about writing to ASSETMETER or LOCATIONMETER etc, via a WO or not,
it is supposed to do all of that for you via its processing class - it just
doesn't seem to work.
I have a PMR open with IBM, maybe they'll come up with something!
Thanks,
Chris.
On Thu, Jan 23, 2014 at 9:22 AM, Ian Wright <ian.wright@gdfsuezep.co.uk>wrote:
>
>
> Its probably because there is no wonum on the meterreading table
>
> They use assetmeter and locationmeter tables to take the reading in the
> work order screen these tables only ever have the last meter reading for
> the asset / location meter and DON’T reference the work order
>
>
>
> I can see there is a wonum field on the non-persistent table used by mif
> for meter readings but I don’t know why it’s there
>
>
>
> This is very annoying as I wanted to use characteristic meter’s to hold
> pass / fail results but there is no direct reference between the reading
> and the work order (not that I can find anyway)
>
>
>
> The only persistent relationship is on tasks where you can enter a reading
> value but this is related to the condition monitoring application and
> requires a point number, it writes a measurement and also write’s to the
> meter reading table. So I guess you could load your readings as work order
> updates (woactivity never tried it though) but it means you would need a
> point for each meter and the location / asset it was used at .
>
>
>
> Rgds Ian
>
> BPD Zenith Ltd
>
>
>
> *From:* MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] *On Behalf
> Of *Cline, Roy
> *Sent:* 23 January 2014 14:23
> *To:* MAXIMO@yahoogroups.com
> *Subject:* RE: [MAXIMO List] Meter Readings against a WO Using MXMETERDATA
>
>
>
>
>
> Chris,
>
> We are setup to load by spreadsheet but we do it against
> an asset or a location since that is where the meter is set up against.
>
>
>
> Roy Cline
>
>
>
> Phone: (203) 492-8189
>
> Cell: (203) 640-9743
>
> FAX: (203) 492-8462
>
>
>
> *From:* MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com<MAXIMO@yahoogroups.com>]
> *On Behalf Of *Chris Lawless
> *Sent:* Tuesday, January 21, 2014 10:57 AM
> *To:* MAXIMO@yahoogroups.com
> *Subject:* [MAXIMO List] Meter Readings against a WO Using MXMETERDATA
>
>
>
>
>
> Is anyone successfully using the MXMETERDATA object structure on its own
> to log meter readings against a work order? While I can do so with a larger
> combined object structure I believe the intent is that MXMETERDATA should
> provide a single interface for capturing meter readings in a variety of
> formats - however when a WONUM is references it gives java exceptions with
> little detail as to the cause.
>
>
>
> How are others bringing meter readings in via integration against a work
> order?
>
>
>
> Maximo 7.5.0.4
>
>
>
> Chris.
>
> GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and
> Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N
> 2PB.
>
>
>
> ****************************************************************************************************************************************************************************************
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
>
> If you have received this email in error please notify the system manager.
>
> ****************************************************************************************************************************************************************************************
>
>
>
Cheers Chris let us know what they say
Rgds Ian
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Chris Lawless
Sent: 23 January 2014 15:40
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Meter Readings against a WO Using MXMETERDATA
I agree, however I believe that the idea is that MXMETERDATA acts as a single point of call for all meter readings, it expects an Asset or Location, optionally a WONUM and it is suppose to put the reading in the right place based on the data that is supplied - such that you don't need to worry about writing to ASSETMETER or LOCATIONMETER etc, via a WO or not, it is supposed to do all of that for you via its processing class - it just doesn't seem to work.
I have a PMR open with IBM, maybe they'll come up with something!
Thanks,
Chris.
On Thu, Jan 23, 2014 at 9:22 AM, Ian Wright <ian.wright@gdfsuezep.co.uk<mailto:ian.wright@gdfsuezep.co.uk>> wrote:
Its probably because there is no wonum on the meterreading table
They use assetmeter and locationmeter tables to take the reading in the work order screen these tables only ever have the last meter reading for the asset / location meter and DON'T reference the work order
I can see there is a wonum field on the non-persistent table used by mif for meter readings but I don't know why it's there
This is very annoying as I wanted to use characteristic meter's to hold pass / fail results but there is no direct reference between the reading and the work order (not that I can find anyway)
The only persistent relationship is on tasks where you can enter a reading value but this is related to the condition monitoring application and requires a point number, it writes a measurement and also write's to the meter reading table. So I guess you could load your readings as work order updates (woactivity never tried it though) but it means you would need a point for each meter and the location / asset it was used at .
Rgds Ian
BPD Zenith Ltd
From: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com> [mailto:MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>] On Behalf Of Cline, Roy
Sent: 23 January 2014 14:23
To: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
Subject: RE: [MAXIMO List] Meter Readings against a WO Using MXMETERDATA
Chris,
We are setup to load by spreadsheet but we do it against an asset or a location since that is where the meter is set up against.
Roy Cline
Phone: (203) 492-8189<tel:%28203%29%20492-8189>
Cell: (203) 640-9743<tel:%28203%29%20640-9743>
FAX: (203) 492-8462<tel:%28203%29%20492-8462>
From: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com> [mailto:MAXIMO@yahoogroups.com] On Behalf Of Chris Lawless
Sent: Tuesday, January 21, 2014 10:57 AM
To: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com>
Subject: [MAXIMO List] Meter Readings against a WO Using MXMETERDATA
Is anyone successfully using the MXMETERDATA object structure on its own to log meter readings against a work order? While I can do so with a larger combined object structure I believe the intent is that MXMETERDATA should provide a single interface for capturing meter readings in a variety of formats - however when a WONUM is references it gives java exceptions with little detail as to the cause.
How are others bringing meter readings in via integration against a work order?
Maximo 7.5.0.4
Chris.
GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.
****************************************************************************************************************************************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
****************************************************************************************************************************************************************************************