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.
"Leadership is an essential and even dominant element in any company's business success."
. by Ron Moore.
If this is true, exactly what type of leadership is desired when it comes to EAM system operation/utilization?
There could be many answers to this but one common dialog goes like this:
MAXIMO is implemented. They go live. Processes and work flows were developed. Staff was trained. Working level is making work orders.
But, some procedural problems remain.
1) Planners are getting consumed by reactive maintenance.
2) Planners are not really planning any work.
3) Maintenance is given work orders straight away bypassing all forms of P&S.
4) In many cases, work is done first, and then a work order is created.
5) In other situations, no work order is created at all.
When upper management is asked about adherence to process, the answer is
"Management personnel at the sites have absolute control over what is done and how a core system like this is to be used".
The above situation requires a re-evaluation of the entire system and process.
The leadership team (e.g. Steering Team, Core Team, CMMS expert, business analysts) need to regroup and focus on original purpose of the system. Why did they buy this product? Why did they spend so much money implementing the system? Is there confusion at the top levels as to "how to achieve true ROI" from the product? Do they understand advanced processes? Were industry best practices explained as well as the corporate "end-game" goals/objectives? And lastly, was the system end-user training conducted in such a manner to include process and roles, along with, point-click navigational instruction?
w/br
John Reeve
Manager, Practice Leader Maintenance and Reliability Solutions
Cell: 423 314 1312
http://www.linkedin.com/pub/john-reeve/11/644/9b2
HI All,
It's been a while since I posted here, but I see there has been some discussion on the new processes around Revisions.
We are using Maximo 7.5.0.1. I'm looking to go to 7.5.0.3. In both versions, I'm working on 3 PMR's that have been identified as bugs dealing with Revisions. I have come to the conclusion, that who
ever came up with this new process, did a very poor job of development.
Detail listed below. Please contact me directly if you would like more detail.
1. You can NOT move an asset to another site if the Asset exists on a Revised PO.
2. You can NOT change any Item to Obsolete that exists on a revised PO
3. Auto Reorder looks at items on a Revised PO as being on order. (We fixed this for now by creating an escalation that updates the POLINES.RECEIPTSCOMPLETE = 0 and PO.RECEIPTS = 'COMPLETE' where
status = 'REVISD')
4. New for Maximo 7.5.0.3, can't change the Order Unit on PO's. Receiving will fail.
I hope to have hot fixes for these soon.
Thanks
Brian Swanson
Systems Analyst-Maximo
Information Technology
HermanMiller
Greetings. I am running v6.2.6 and just for my own personal understanding, and please forgive my ignorance, could you please define "Revised PO"? I am understanding this to mean the same thing as a "Change order", but when you say "exists on a revised PO" do you mean one with completed receipts? If so, then I understand your frustration.
Thanks
On Sep 17, 2012, at 1:19 PM, Brian Swanson <brian_swanson@hermanmiller.com> wrote:
>
> HI All,
> It's been a while since I posted here, but I see there has been some discussion on the new processes around Revisions.
>
> We are using Maximo 7.5.0.1. I'm looking to go to 7.5.0.3. In both versions, I'm working on 3 PMR's that have been identified as bugs dealing with Revisions. I have come to the conclusion, that who
> ever came up with this new process, did a very poor job of development.
>
> Detail listed below. Please contact me directly if you would like more detail.
>
> 1. You can NOT move an asset to another site if the Asset exists on a Revised PO.
>
> 2. You can NOT change any Item to Obsolete that exists on a revised PO
>
> 3. Auto Reorder looks at items on a Revised PO as being on order. (We fixed this for now by creating an escalation that updates the POLINES.RECEIPTSCOMPLETE = 0 and PO.RECEIPTS = 'COMPLETE' where
> status = 'REVISD')
>
> 4. New for Maximo 7.5.0.3, can't change the Order Unit on PO's. Receiving will fail.
>
> I hope to have hot fixes for these soon.
>
> Thanks
>
> Brian Swanson
> Systems Analyst-Maximo
> Information Technology
>
> HermanMiller
>
>
>
>
>
>
>
>
>
This is new functionality in version 7. It does not exist in your current version.
Brian Swanson
Systems Analyst-Maximo
Information Technology
HermanMiller
From: zeroxpectations@yahoo.com
To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>,
Date: 09/18/2012 08:47 AM
Subject: Re: [MAXIMO List] Maximo and Revision enhancement
Sent by: MAXIMO@yahoogroups.com
Greetings. I am running v6.2.6 and just for my own personal understanding, and please forgive my ignorance, could you please define "Revised PO"? I am understanding this to mean the same thing as a
"Change order", but when you say "exists on a revised PO" do you mean one with completed receipts? If so, then I understand your frustration.
Thanks
On Sep 17, 2012, at 1:19 PM, Brian Swanson <brian_swanson@hermanmiller.com> wrote:
>
> HI All,
> It's been a while since I posted here, but I see there has been some discussion on the new processes around Revisions.
>
> We are using Maximo 7.5.0.1. I'm looking to go to 7.5.0.3. In both versions, I'm working on 3 PMR's that have been identified as bugs dealing with Revisions. I have come to the conclusion, that who
> ever came up with this new process, did a very poor job of development.
>
> Detail listed below. Please contact me directly if you would like more detail.
>
> 1. You can NOT move an asset to another site if the Asset exists on a Revised PO.
>
> 2. You can NOT change any Item to Obsolete that exists on a revised PO
>
> 3. Auto Reorder looks at items on a Revised PO as being on order. (We fixed this for now by creating an escalation that updates the POLINES.RECEIPTSCOMPLETE = 0 and PO.RECEIPTS = 'COMPLETE' where
> status = 'REVISD')
>
> 4. New for Maximo 7.5.0.3, can't change the Order Unit on PO's. Receiving will fail.
>
> I hope to have hot fixes for these soon.
>
> Thanks
>
> Brian Swanson
> Systems Analyst-Maximo
> Information Technology
>
> HermanMiller
>
>
>
>
>
>
>
>
>
We are in the process of upgrading to Maximo 7.5.0.1 and have found an interesting issue. When we try and revise a PO associated with a Contract, it revises the contract as well. Interesting thing is this only occurs on upgraded POs\Contracts. If I create a new PO\Contract in 7.5.0.1, i don't see this issue. Funny thing is, we can no longer find the contract in the Purchasing Contracts application because that application uses a view that joins the CONTRACTS and CONTRACTPURCH tables and the contract only gets revised in the CONTRACTS table thus the join does not work.
Do you use contracts and have you seen this?
--- In MAXIMO@yahoogroups.com, Brian Swanson <brian_swanson@...> wrote:
>
> This is new functionality in version 7. It does not exist in your current version.
>
>
>
> Brian Swanson
> Systems Analyst-Maximo
> Information Technology
>
>
>
> HermanMiller
>
>
>
> From: zeroxpectations@...
> To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>,
> Date: 09/18/2012 08:47 AM
> Subject: Re: [MAXIMO List] Maximo and Revision enhancement
> Sent by: MAXIMO@yahoogroups.com
>
>
>
>
>
>
> Greetings. I am running v6.2.6 and just for my own personal understanding, and please forgive my ignorance, could you please define "Revised PO"? I am understanding this to mean the same thing as a
> "Change order", but when you say "exists on a revised PO" do you mean one with completed receipts? If so, then I understand your frustration.
>
> Thanks
>
> On Sep 17, 2012, at 1:19 PM, Brian Swanson <brian_swanson@...> wrote:
>
> >
> > HI All,
> > It's been a while since I posted here, but I see there has been some discussion on the new processes around Revisions.
> >
> > We are using Maximo 7.5.0.1. I'm looking to go to 7.5.0.3. In both versions, I'm working on 3 PMR's that have been identified as bugs dealing with Revisions. I have come to the conclusion, that who
> > ever came up with this new process, did a very poor job of development.
> >
> > Detail listed below. Please contact me directly if you would like more detail.
> >
> > 1. You can NOT move an asset to another site if the Asset exists on a Revised PO.
> >
> > 2. You can NOT change any Item to Obsolete that exists on a revised PO
> >
> > 3. Auto Reorder looks at items on a Revised PO as being on order. (We fixed this for now by creating an escalation that updates the POLINES.RECEIPTSCOMPLETE = 0 and PO.RECEIPTS = 'COMPLETE' where
> > status = 'REVISD')
> >
> > 4. New for Maximo 7.5.0.3, can't change the Order Unit on PO's. Receiving will fail.
> >
> > I hope to have hot fixes for these soon.
> >
> > Thanks
> >
> > Brian Swanson
> > Systems Analyst-Maximo
> > Information Technology
> >
> > HermanMiller
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
>
>
>
>
Thank you guys for info! Please let us know when hot fixes are release.
--- In MAXIMO@yahoogroups.com, Brian Swanson <brian_swanson@...> wrote:
>
>
> HI All,
> It's been a while since I posted here, but I see there has been some discussion on the new processes around Revisions.
>
> We are using Maximo 7.5.0.1. I'm looking to go to 7.5.0.3. In both versions, I'm working on 3 PMR's that have been identified as bugs dealing with Revisions. I have come to the conclusion, that who
> ever came up with this new process, did a very poor job of development.
>
> Detail listed below. Please contact me directly if you would like more detail.
>
> 1. You can NOT move an asset to another site if the Asset exists on a Revised PO.
>
> 2. You can NOT change any Item to Obsolete that exists on a revised PO
>
> 3. Auto Reorder looks at items on a Revised PO as being on order. (We fixed this for now by creating an escalation that updates the POLINES.RECEIPTSCOMPLETE = 0 and PO.RECEIPTS = 'COMPLETE' where
> status = 'REVISD')
>
> 4. New for Maximo 7.5.0.3, can't change the Order Unit on PO's. Receiving will fail.
>
> I hope to have hot fixes for these soon.
>
> Thanks
>
>
>
> Brian Swanson
> Systems Analyst-Maximo
> Information Technology
>
>
> HermanMiller
>
>
>
I agree - valuable information Brian - I'm just dealing with a bunch of
purchasing issues in an implementation right now. We didn't know about
these.
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
al_potanin
Sent: September-18-12 10:47 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: Maximo and Revision enhancement
Thank you guys for info! Please let us know when hot fixes are release.
--- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , Brian
Swanson <brian_swanson@...> wrote:
>
>
> HI All,
> It's been a while since I posted here, but I see there has been some
discussion on the new processes around Revisions.
>
> We are using Maximo 7.5.0.1. I'm looking to go to 7.5.0.3. In both
versions, I'm working on 3 PMR's that have been identified as bugs dealing
with Revisions. I have come to the conclusion, that who
> ever came up with this new process, did a very poor job of development.
>
> Detail listed below. Please contact me directly if you would like more
detail.
>
> 1. You can NOT move an asset to another site if the Asset exists on a
Revised PO.
>
> 2. You can NOT change any Item to Obsolete that exists on a revised PO
>
> 3. Auto Reorder looks at items on a Revised PO as being on order. (We
fixed this for now by creating an escalation that updates the
POLINES.RECEIPTSCOMPLETE = 0 and PO.RECEIPTS = 'COMPLETE' where
> status = 'REVISD')
>
> 4. New for Maximo 7.5.0.3, can't change the Order Unit on PO's. Receiving
will fail.
>
> I hope to have hot fixes for these soon.
>
> Thanks
>
>
>
> Brian Swanson
> Systems Analyst-Maximo
> Information Technology
>
>
> HermanMiller
>
>
>