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.
In our instance, this is not a default (not checked on).
There has been some talk of having spare parts associated with assets.
Rather than performing the task manually, we would turn on the check box.
Any thoughts on this approach?
Add as Spare Part
ITEM.SPAREPARTAUTOADD
Specifies whether the item will be added as a spare part for the asset when issued, if the item is not already a spare part. If the checkbox is selected, the item can be added as a spare part. If the check box is cleared (the default), the item is not used as a spare part.
The pro: It's a convenient way to build an item assembly structure for your
assets.
The con: You end up with an unrelated part listed whenever someone clicks
the "Select Spare Parts" button after someone else inadvertently chooses
the wrong part.
I've always used Spare Parts as a validation/downselect to ensure that the
technician is choosing parts that are authorized for the asset,
The answer is really going to depend on what you're looking to get out of
spare parts.
Chris McClinch
On Fri, Mar 7, 2014 at 2:01 PM, <swkim@getty.edu> wrote:
>
>
> In our instance, this is not a default (not checked on).
>
> There has been some talk of having spare parts associated with assets.
>
> Rather than performing the task manually, we would turn on the check box.
>
> Any thoughts on this approach?
>
> Add as Spare Part
>
> ITEM.SPAREPARTAUTOADD
> Specifies whether the item will be added as a spare part for the asset
> when issued, if the item is not already a spare part. If the checkbox is
> selected, the item can be added as a spare part. If the check box is
> cleared (the default), the item is not used as a spare part.
>
>
>
One of the things you might want to do is go by Commodity Group, if you don’t want to have to go through each item individually. Usually Commodity Group is a good indicator, although it’s not perfect.
I strongly recommend using that flag – over time, you’ll build up the Spare parts list and make life a lot easier for your planners, since they’ll be able to click on the “Select Asset Spare Parts” button on the Plan tab when trying to plan materials. It’s by far the easiest way to find the part you need.
If your Planners aren’t using the plan tab, they can still hyperlink to the Asset record and view the list there.
The risk of getting junk in that list is far outweighed by the benefit of finding your “real” parts quickly, IMO.
Shannon Rotz
P.S. Being sick a lot in the last month, I somehow didn’t notice that my automatic feed from this group stopped somewhere around the middle of December. This week, I got to wondering why I wasn’t seeing anything from the newsgroup … glad to be back!
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Chris McClinch
Sent: March-07-14 12:50 PM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Item Master - Add As Spare Part
The pro: It's a convenient way to build an item assembly structure for your assets.
The con: You end up with an unrelated part listed whenever someone clicks the "Select Spare Parts" button after someone else inadvertently chooses the wrong part.
I've always used Spare Parts as a validation/downselect to ensure that the technician is choosing parts that are authorized for the asset,
The answer is really going to depend on what you're looking to get out of spare parts.
Chris McClinch
On Fri, Mar 7, 2014 at 2:01 PM, <swkim@getty.edu> wrote:
In our instance, this is not a default (not checked on).
There has been some talk of having spare parts associated with assets.
Rather than performing the task manually, we would turn on the check box.
Any thoughts on this approach?
Add as Spare Part
ITEM.SPAREPARTAUTOADD
Specifies whether the item will be added as a spare part for the asset when issued, if the item is not already a spare part. If the checkbox is selected, the item can be added as a spare part. If the check box is cleared (the default), the item is not used as a spare part.
When creating a new report the following error is received.
This also happens when
duplicating a report.
BMXAA7816E
- Operation setValue(boolean value) is not supported on data type INTEGER.
Report the error to your system administrator.
This causes the browser to be completely shutdown.
No new reports can be created or imported causing the client
to potentially stop the go-live as they depend on these reports.
This is not occurring with new assets, job plans, work
orders or pm’s so it is hopefully isolated to this object.
This is an upgrade from 6.2.8 to 7.5.0.5.
This issue did not happen in the test upgrades that happened
before this with the same data set.
The standard upgrade process as outlined by IBM
documentation was used.
All Integrity Checkers ran have 0 Errors.
App Server IBM WebSphere Application Server 7.0.0.31
Version IBM Maximo Asset Management 7.5.0.5 Build
20130903-1504 DB Build V7505-00
Tivoli's process automation engine 7.5.0.5-IFIX20140108-2152
Build 20130903-1504 DB Build V7505-43 HFDB Build HF7505-02
IBM TPAE Integration Framework 7.5.1.0 Build 20130829-1209
DB Build V7510-28
IBM Maximo Mobile 7.5.1.0-20131009-1552 Build 20130603-1027
DB Build V7510-05 HFDB Build HF7510-02
Server OS Windows Server 2012 6.2 build 9200
Server DB Microsoft SQL Server 11.0 (11.00.3000)
Maxsequences have been verified as being correct.
Select * from reportlookup where reportlookup.reportnum in (select reportnum from report where runtype in ('ESPREADSHEET', 'QUERY', 'REPORT')) or
reportlookup.reportnum is null or reportlookup.reportname is null;
- no results found
select * from reportlabel where reportname like '%.rox'or reportname like '%.dox'or reportname like '%.vts'or reportname like '%.vtf';
- no results found
select * from report where reportname like '%.rox'or reportname like '%.dox'or reportname like '%.vts'or reportname like '%.vtf';
- no results found
Any thoughts would be helpful.
Thank you,
Lonnie Stone
lonnie_s_stone@yahoo.com
Just my opinion gang….but turning on the option to add all consumed items to the Asset Spare Parts list is dangerous !!!!!!!!!!!
MAXIMO ONLY USED BY MAINTENANCE MECHANICS
It can be done with some level of confidence IF AND ONLY IF Maximo is used only by your Maintenance Technicians. That means you will have “technically competent” users transacting parts to Work Orders on Assets. Your Mechanics need to know that if they do it right and make sure they use correct parts, the BOM’s will be created automatically over time. If they consume wrong parts, the BOM’s will be corrupt. Regardless, I would only leave the flag ticked for a fixed period of time….after which I would turn it off and assign BOM’s to system owners to confirm they are correct. Ultimately, I’d move them to be under the control of Planner/Schedulers. At some point you have to lock the BOM’s down like ICBM launch codes !
MAXIMO USED BY MAINTENANCE AND OPERATIONS/MANUFACURING ASSOCIATES - FLAG IS TICKED
Never ever under any circumstances turn that flag on when you have Mechanics and Operators able to create Work Orders, go to the Stockroom and get Parts. You will have technical and non-technical people transacting good and bad parts to the Asset. If you do this, you will regret it because your BOM’s will be corrupted in a single day.
MAXIMO USED BY MAINTENANCE AND OPERATIONS/MANUFACURING ASSOCIATES - FLAG NOT TICKED
This is the safest, least cost, fastest way to build good BOM’s. Take your site Assets and divide them up appropriately across your technicians and give them ownership for making the BOM’s, documentation, PM content, reliability initiatives, etc. complete. All of these are measureable and the Tech’s will amaze you with the results. You can start their BOM efforts by giving them a list of all the items consumed on their assets and let them build from there. Leveraging OEM’s, etc. can also help this.
Regards, Eric
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Chris McClinch
Sent: Friday, March 07, 2014 2:50 PM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Item Master - Add As Spare Part
The pro: It's a convenient way to build an item assembly structure for your assets.
The con: You end up with an unrelated part listed whenever someone clicks the "Select Spare Parts" button after someone else inadvertently chooses the wrong part.
I've always used Spare Parts as a validation/downselect to ensure that the technician is choosing parts that are authorized for the asset,
The answer is really going to depend on what you're looking to get out of spare parts.
Chris McClinch
On Fri, Mar 7, 2014 at 2:01 PM, <swkim@getty.edu<mailto:swkim@getty.edu>> wrote:
In our instance, this is not a default (not checked on).
There has been some talk of having spare parts associated with assets.
Rather than performing the task manually, we would turn on the check box.
Any thoughts on this approach?
Add as Spare Part
ITEM.SPAREPARTAUTOADD
Specifies whether the item will be added as a spare part for the asset when issued, if the item is not already a spare part. If the checkbox is selected, the item can be added as a spare part. If the check box is cleared (the default), the item is not used as a spare part.
Are these Actuate reports or BIRT reports? Can you preview the report in Report Administration? Can you create a new report with the Create Report option in an application like Asset? If these are BIRT reports can you test them with eclipse?
On Sunday, March 9, 2014 12:42 PM, Lonnie Stone <lonnie_s_stone@yahoo.com> wrote:
When creating a new report the following error is received.
This also happens when
duplicating a report.
BMXAA7816E
- Operation setValue(boolean value) is not supported on data type INTEGER.
Report the error to your system administrator.
This causes the browser to be completely shutdown.
No new reports can be created or imported causing the client
to potentially stop the go-live as they depend on these reports.
This is not occurring with new assets, job plans, work
orders or pm’s so it is hopefully isolated to this object.
This is an upgrade from 6.2.8 to 7.5.0.5.
This issue did not happen in the test upgrades that happened
before this with the same data set.
The standard upgrade process as outlined by IBM
documentation was used.
All Integrity Checkers ran have 0 Errors.
App Server IBM WebSphere Application Server 7.0.0.31
Version IBM Maximo Asset Management 7.5.0.5 Build
20130903-1504 DB Build V7505-00
Tivoli's process automation engine 7.5.0.5-IFIX20140108-2152
Build 20130903-1504 DB Build V7505-43 HFDB Build HF7505-02
IBM TPAE Integration Framework 7.5.1.0 Build 20130829-1209
DB Build V7510-28
IBM Maximo Mobile 7.5.1.0-20131009-1552 Build 20130603-1027
DB Build V7510-05 HFDB Build HF7510-02
Server OS Windows Server 2012 6.2 build 9200
Server DB Microsoft SQL Server 11.0 (11.00.3000)
Maxsequences have been verified as being correct.
Select * from reportlookup where reportlookup.reportnum in (select reportnum from report where runtype in ('ESPREADSHEET', 'QUERY', 'REPORT')) or
reportlookup.reportnum is null or reportlookup.reportname is null;
- no results found
select * from reportlabel where reportname like '%.rox'or reportname like '%.dox'or reportname like '%.vts'or reportname like '%.vtf';
- no results found
select * from report where reportname like '%.rox'or reportname like '%.dox'or reportname like '%.vts'or reportname like '%.vtf';
- no results found
Any thoughts would be helpful.
Thank you,
Lonnie Stone
lonnie_s_stone@yahoo.com
What does the log say when you do this ?
On Sunday, March 9, 2014 12:42 PM, Lonnie Stone <lonnie_s_stone@yahoo.com> wrote:
When creating a new report the following error is received.
This also happens when duplicating a report.
BMXAA7816E - Operation setValue(boolean value) is not supported on data type INTEGER. Report the error to your system administrator.
This causes the browser to be completely shutdown.
No new reports can be created or imported causing the client to potentially stop the go-live as they depend on these reports.
This is not occurring with new assets, job plans, work orders or pm’s so it is hopefully isolated to this object.
This is an upgrade from 6.2.8 to 7.5.0.5.
This issue did not happen in the test upgrades that happened before this with the same data set.
The standard upgrade process as outlined by IBM documentation was used.
All Integrity Checkers ran have 0 Errors.
App Server IBM WebSphere Application Server 7.0.0.31
Version IBM Maximo Asset Management 7.5.0.5 Build 20130903-1504 DB Build V7505-00
Tivoli's process automation engine 7.5.0.5-IFIX20140108-2152 Build 20130903-1504 DB Build V7505-43 HFDB Build HF7505-02
IBM TPAE Integration Framework 7.5.1.0 Build 20130829-1209 DB Build V7510-28
IBM Maximo Mobile 7.5.1.0-20131009-1552 Build 20130603-1027 DB Build V7510-05 HFDB Build HF7510-02
Server OS Windows Server 2012 6.2 build 9200
Server DB Microsoft SQL Server 11.0 (11.00.3000)
Maxsequences have been verified as being correct.
Select * from reportlookup where reportlookup.reportnum in (select reportnum from report where runtype in ('ESPREADSHEET', 'QUERY', 'REPORT')) or reportlookup.reportnum is null or reportlookup.reportname is null;
- no results found
select * from reportlabel where reportname like '%.rox'or reportname like '%.dox'or reportname like '%.vts'or reportname like '%.vtf';
- no results found
select * from report where reportname like '%.rox'or reportname like '%.dox'or reportname like '%.vts'or reportname like '%.vtf';
- no results found
Any thoughts would be helpful.
Thank you,
Lonnie Stone
lonnie_s_stone@yahoo.com
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.
**************************************************************************************************************