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.
Hello everyone,
Here at where I work we have 3 different work order priorities:
#3: Emergency (Immediate)
#2: Urgent (Within 7 days)
#1: Low
We are thinking about adding more priorities to the system and was wondering what kind of different priorities some of you are using for your system.
Maximo 6.2.1
Weblogic
SQL 2005
Thx in advance,
mrggutz
I've always liked four priorities:
1 - Emergency.
2 - Preventative Maintenance (can be interrupted only for Emergency work).
3 - Corrective Maintenance (can be interrupted for Emergency or
Preventative Maintenance).
4 - Project (can be interrupted for Emergency, Preventative
Maintenance, or Corrective Maintenance).
Obviously, SLAs can be tied to each priority according to your business rules.
Chris McClinch
On 6/25/12, George <ggutierrez@pasadenarefining.com> wrote:
> Hello everyone,
> Here at where I work we have 3 different work order priorities:
> #3: Emergency (Immediate)
> #2: Urgent (Within 7 days)
> #1: Low
>
> We are thinking about adding more priorities to the system and was wondering
> what kind of different priorities some of you are using for your system.
>
> Maximo 6.2.1
> Weblogic
> SQL 2005
>
> Thx in advance,
> mrggutz
>
>
Take a look at the attachment, this is what we did a few years ago. Since we have had time to use the definitions, reality is that our priority 1 and 2 do not get used that often. The priority 4 has been a source of much discourse due to how different work groups view their needs. However it has helped us better direct our work force to the right places and right times.
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of George
Sent: Monday, June 25, 2012 7:58 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Work Order Priorities
Hello everyone,
Here at where I work we have 3 different work order priorities:
#3: Emergency (Immediate)
#2: Urgent (Within 7 days)
#1: Low
We are thinking about adding more priorities to the system and was wondering what kind of different priorities some of you are using for your system.
Maximo 6.2.1
Weblogic
SQL 2005
Thx in advance,
mrggutz
Does not look like the attachment made it, so here is the important part.
5-Emergency. Critical asset has failed. Needs immediate attention; requires dispatch of personnel from another facility, or reassignment from another work order, or unscheduled overtime, or a call out.
4-Urgent. Failure of critical asset is suspected or pending, or a non-critical asset has failed. Scheduled overtime may be required. Attention required within 1-5 business days.
3-Medium Priority. Attention needed 6-14 calendar days.
2-Low priority. Several work orders may be consolidated prior to being scheduled at a particular facility. Attention desired 15-60 calendar days.
1-No failure; Lowest priority. Several work orders may be consolidated prior to being scheduled at a particular facility. Attention desired within 6 months.
Process
1. Person creating the work order should read the definitions in the Work Order priority field and select the priority that best describes the time frame they need the work completed.
2. Person creating the work order should use the "Priority Justification" field to note reasons for high priority work orders.
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Lampert, Lance R.
Sent: Monday, June 25, 2012 8:12 AM
To: 'MAXIMO@yahoogroups.com'
Subject: RE: [MAXIMO List] Work Order Priorities
Take a look at the attachment, this is what we did a few years ago. Since we have had time to use the definitions, reality is that our priority 1 and 2 do not get used that often. The priority 4 has been a source of much discourse due to how different work groups view their needs. However it has helped us better direct our work force to the right places and right times.
From: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com> [mailto:MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>] On Behalf Of George
Sent: Monday, June 25, 2012 7:58 AM
To: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
Subject: [MAXIMO List] Work Order Priorities
Hello everyone,
Here at where I work we have 3 different work order priorities:
#3: Emergency (Immediate)
#2: Urgent (Within 7 days)
#1: Low
We are thinking about adding more priorities to the system and was wondering what kind of different priorities some of you are using for your system.
Maximo 6.2.1
Weblogic
SQL 2005
Thx in advance,
mrggutz
We've typically used the following...
EQDEG
Equipment Degraded
EQDWN
Equipment Down
EQRUN
Equipment Running
EV
Event Report
PM
Preventative Maintenance
PROJ
Project
SE
Safety Emergency
SNE
Safety Non Emergency
Best Regards,
Butch
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of George
Sent: Monday, June 25, 2012 10:58 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Work Order Priorities
Hello everyone,
Here at where I work we have 3 different work order priorities:
#3: Emergency (Immediate)
#2: Urgent (Within 7 days)
#1: Low
We are thinking about adding more priorities to the system and was wondering what kind of different priorities some of you are using for your system.
Maximo 6.2.1
Weblogic
SQL 2005
Thx in advance,
mrggutz
________________________________
MEMC Confidentiality Statement: The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain information that is legally privileged and confidential. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately by telephone or by return E-mail and delete this message, along with any attachments, from your computer.
No Contract: Regardless of content, this email shall not operate to bind MEMC to any purchase order or contract unless pursuant to a written agreement signed by MEMC expressly permitting the use of email for such purpose.
I think the takeaway here should be ... one should not try to make the WOpriority field the one-and-only field to delineate all possible categories.
Why not add addtional fields which can be applicable to all Priority values.
The possible combinations will increase giving you more ways to sort & and slice-dice.
The other consideration is asset priority.
If your priority system is working well your maintenance backlog will be fairly ranked and properly distributed.
Sent on the Sprint� Now Network from my BlackBerry�
-----Original Message-----
From: Butch Willinger <bwillinger@memc.com>
Sender: MAXIMO@yahoogroups.com
Date: Mon, 25 Jun 2012 11:28:02
To: MAXIMO@yahoogroups.com<MAXIMO@yahoogroups.com>
Reply-To: MAXIMO@yahoogroups.com
Subject: RE: [MAXIMO List] Work Order Priorities
We've typically used the following...
EQDEG
Equipment Degraded
EQDWN
Equipment Down
EQRUN
Equipment Running
EV
Event Report
PM
Preventative Maintenance
PROJ
Project
SE
Safety Emergency
SNE
Safety Non Emergency
Best Regards,
Butch
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of George
Sent: Monday, June 25, 2012 10:58 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Work Order Priorities
Hello everyone,
Here at where I work we have 3 different work order priorities:
#3: Emergency (Immediate)
#2: Urgent (Within 7 days)
#1: Low
We are thinking about adding more priorities to the system and was wondering what kind of different priorities some of you are using for your system.
Maximo 6.2.1
Weblogic
SQL 2005
Thx in advance,
mrggutz
________________________________
MEMC Confidentiality Statement: The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain information that is legally privileged and confidential. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately by telephone or by return E-mail and delete this message, along with any attachments, from your computer.
No Contract: Regardless of content, this email shall not operate to bind MEMC to any purchase order or contract unless pursuant to a written agreement signed by MEMC expressly permitting the use of email for such purpose.
My apologies, I misread the original...the below list of 8 are our "Work Order Types" and not "Priorities".
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of john reeve
Sent: Monday, June 25, 2012 11:44 AM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Work Order Priorities
I think the takeaway here should be ... one should not try to make the WOpriority field the one-and-only field to delineate all possible categories.
Why not add addtional fields which can be applicable to all Priority values.
The possible combinations will increase giving you more ways to sort & and slice-dice.
The other consideration is asset priority.
If your priority system is working well your maintenance backlog will be fairly ranked and properly distributed.
Sent on the Sprint(r) Now Network from my BlackBerry(r)
-----Original Message-----
From: Butch Willinger <bwillinger@memc.com>
Sender: MAXIMO@yahoogroups.com
Date: Mon, 25 Jun 2012 11:28:02
To: MAXIMO@yahoogroups.com<MAXIMO@yahoogroups.com>
Reply-To: MAXIMO@yahoogroups.com
Subject: RE: [MAXIMO List] Work Order Priorities
We've typically used the following...
EQDEG
Equipment Degraded
EQDWN
Equipment Down
EQRUN
Equipment Running
EV
Event Report
PM
Preventative Maintenance
PROJ
Project
SE
Safety Emergency
SNE
Safety Non Emergency
Best Regards,
Butch
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of George
Sent: Monday, June 25, 2012 10:58 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Work Order Priorities
Hello everyone,
Here at where I work we have 3 different work order priorities:
#3: Emergency (Immediate)
#2: Urgent (Within 7 days)
#1: Low
We are thinking about adding more priorities to the system and was wondering what kind of different priorities some of you are using for your system.
Maximo 6.2.1
Weblogic
SQL 2005
Thx in advance,
mrggutz
________________________________
MEMC Confidentiality Statement: The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain information that is legally privileged and confidential. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately by telephone or by return E-mail and delete this message, along with any attachments, from your computer.
No Contract: Regardless of content, this email shall not operate to bind MEMC to any purchase order or contract unless pursuant to a written agreement signed by MEMC expressly permitting the use of email for such purpose.
------------------------------------
Email addresses you might need:
Posting: MAXIMO@yahoogroups.com
Join : MAXIMO-subscribe@yahoogroups.com
Leave : MAXIMO-unsubscribe@yahoogroups.com
Cry : MAXIMO-owner@yahoogroups.com
Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
MEMC Confidentiality Statement: The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain information that is legally privileged and confidential. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately by telephone or by return E-mail and delete this message, along with any attachments, from your computer.
No Contract: Regardless of content, this email shall not operate to bind MEMC to any purchase order or contract unless pursuant to a written agreement signed by MEMC expressly permitting the use of email for such purpose.
Thank you all for the response's they will come in handy.
--- In MAXIMO@yahoogroups.com, Butch Willinger <bwillinger@...> wrote:
>
> My apologies, I misread the original...the below list of 8 are our "Work Order Types" and not "Priorities".
>
>
>
> -----Original Message-----
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of john reeve
> Sent: Monday, June 25, 2012 11:44 AM
> To: MAXIMO@yahoogroups.com
> Subject: Re: [MAXIMO List] Work Order Priorities
>
> I think the takeaway here should be ... one should not try to make the WOpriority field the one-and-only field to delineate all possible categories.
>
> Why not add addtional fields which can be applicable to all Priority values.
>
> The possible combinations will increase giving you more ways to sort & and slice-dice.
>
> The other consideration is asset priority.
>
> If your priority system is working well your maintenance backlog will be fairly ranked and properly distributed.
>
>
>
> Sent on the Sprint(r) Now Network from my BlackBerry(r)
>
>
>
> -----Original Message-----
>
> From: Butch Willinger <bwillinger@...>
>
> Sender: MAXIMO@yahoogroups.com
>
> Date: Mon, 25 Jun 2012 11:28:02
>
> To: MAXIMO@yahoogroups.com<MAXIMO@yahoogroups.com>
>
> Reply-To: MAXIMO@yahoogroups.com
>
> Subject: RE: [MAXIMO List] Work Order Priorities
>
>
>
> We've typically used the following...
>
>
>
> EQDEG
>
>
>
> Equipment Degraded
>
>
>
> EQDWN
>
>
>
> Equipment Down
>
>
>
> EQRUN
>
>
>
> Equipment Running
>
>
>
> EV
>
>
>
> Event Report
>
>
>
> PM
>
>
>
> Preventative Maintenance
>
>
>
> PROJ
>
>
>
> Project
>
>
>
> SE
>
>
>
> Safety Emergency
>
>
>
> SNE
>
>
>
> Safety Non Emergency
>
>
>
>
>
> Best Regards,
>
>
>
> Butch
>
>
>
>
>
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of George
>
> Sent: Monday, June 25, 2012 10:58 AM
>
> To: MAXIMO@yahoogroups.com
>
> Subject: [MAXIMO List] Work Order Priorities
>
>
>
>
>
>
>
> Hello everyone,
>
> Here at where I work we have 3 different work order priorities:
>
> #3: Emergency (Immediate)
>
> #2: Urgent (Within 7 days)
>
> #1: Low
>
>
>
> We are thinking about adding more priorities to the system and was wondering what kind of different priorities some of you are using for your system.
>
>
>
> Maximo 6.2.1
>
> Weblogic
>
> SQL 2005
>
>
>
> Thx in advance,
>
> mrggutz
>
>
>
>
>
> ________________________________
>
> MEMC Confidentiality Statement: The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain information that is legally privileged and confidential. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately by telephone or by return E-mail and delete this message, along with any attachments, from your computer.
>
> No Contract: Regardless of content, this email shall not operate to bind MEMC to any purchase order or contract unless pursuant to a written agreement signed by MEMC expressly permitting the use of email for such purpose.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------------
>
> Email addresses you might need:
> Posting: MAXIMO@yahoogroups.com
> Join : MAXIMO-subscribe@yahoogroups.com
> Leave : MAXIMO-unsubscribe@yahoogroups.com
> Cry : MAXIMO-owner@yahoogroups.com
> Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
>
>
>
>
> MEMC Confidentiality Statement: The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain information that is legally privileged and confidential. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately by telephone or by return E-mail and delete this message, along with any attachments, from your computer.
> No Contract: Regardless of content, this email shall not operate to bind MEMC to any purchase order or contract unless pursuant to a written agreement signed by MEMC expressly permitting the use of email for such purpose.
>
Hi,
value description
1 Immediate Shutdown Do Now
2 Urgent: Next Production Stop
3 Routine: CM/Planned/Scheduled
4 PM or Complete by Not Later Than Date
5 Major Shutdown Required
Dave Bone
--- In MAXIMO@yahoogroups.com, "Lampert, Lance R." <lance.lampert@...> wrote:
>
> Does not look like the attachment made it, so here is the important part.
>
> 5-Emergency. Critical asset has failed. Needs immediate attention; requires dispatch of personnel from another facility, or reassignment from another work order, or unscheduled overtime, or a call out.
>
> 4-Urgent. Failure of critical asset is suspected or pending, or a non-critical asset has failed. Scheduled overtime may be required. Attention required within 1-5 business days.
>
> 3-Medium Priority. Attention needed 6-14 calendar days.
>
> 2-Low priority. Several work orders may be consolidated prior to being scheduled at a particular facility. Attention desired 15-60 calendar days.
>
> 1-No failure; Lowest priority. Several work orders may be consolidated prior to being scheduled at a particular facility. Attention desired within 6 months.
>
> Process
>
> 1. Person creating the work order should read the definitions in the Work Order priority field and select the priority that best describes the time frame they need the work completed.
>
> 2. Person creating the work order should use the "Priority Justification" field to note reasons for high priority work orders.
>
>
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Lampert, Lance R.
> Sent: Monday, June 25, 2012 8:12 AM
> To: 'MAXIMO@yahoogroups.com'
> Subject: RE: [MAXIMO List] Work Order Priorities
>
>
>
> Take a look at the attachment, this is what we did a few years ago. Since we have had time to use the definitions, reality is that our priority 1 and 2 do not get used that often. The priority 4 has been a source of much discourse due to how different work groups view their needs. However it has helped us better direct our work force to the right places and right times.
>
> From: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com> [mailto:MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>] On Behalf Of George
> Sent: Monday, June 25, 2012 7:58 AM
> To: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
> Subject: [MAXIMO List] Work Order Priorities
>
> Hello everyone,
> Here at where I work we have 3 different work order priorities:
> #3: Emergency (Immediate)
> #2: Urgent (Within 7 days)
> #1: Low
>
> We are thinking about adding more priorities to the system and was wondering what kind of different priorities some of you are using for your system.
>
> Maximo 6.2.1
> Weblogic
> SQL 2005
>
> Thx in advance,
> mrggutz
>
>
>
>
>
>
>
It is a very complete priority work order I think....
I agree with Lampert that priority of wo does always refer to datetime
where the work should be done.....because of criticality of asset...
Warm Regards,
Juniko W Batista
On Jun 25, 2012 11:14 PM, "Lampert, Lance R." <lance.lampert@awwu.biz>
wrote:
> **
>
>
> Does not look like the attachment made it, so here is the important part.
>
> 5-Emergency. Critical asset has failed. Needs immediate attention;
> requires dispatch of personnel from another facility, or reassignment from
> another work order, or unscheduled overtime, or a call out.
>
> 4-Urgent. Failure of critical asset is suspected or pending, or a
> non-critical asset has failed. Scheduled overtime may be required.
> Attention required within 1-5 business days.
>
> 3-Medium Priority. Attention needed 6-14 calendar days.
>
> 2-Low priority. Several work orders may be consolidated prior to being
> scheduled at a particular facility. Attention desired 15-60 calendar days.
>
> 1-No failure; Lowest priority. Several work orders may be consolidated
> prior to being scheduled at a particular facility. Attention desired within
> 6 months.
>
> Process
>
> 1. Person creating the work order should read the definitions in the Work
> Order priority field and select the priority that best describes the time
> frame they need the work completed.
>
> 2. Person creating the work order should use the "Priority Justification"
> field to note reasons for high priority work orders.
>
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
> Lampert, Lance R.
> Sent: Monday, June 25, 2012 8:12 AM
> To: 'MAXIMO@yahoogroups.com'
> Subject: RE: [MAXIMO List] Work Order Priorities
>
> Take a look at the attachment, this is what we did a few years ago. Since
> we have had time to use the definitions, reality is that our priority 1 and
> 2 do not get used that often. The priority 4 has been a source of much
> discourse due to how different work groups view their needs. However it has
> helped us better direct our work force to the right places and right times.
>
> From: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com> [mailto:
> MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>] On Behalf Of
> George
> Sent: Monday, June 25, 2012 7:58 AM
> To: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
> Subject: [MAXIMO List] Work Order Priorities
>
> Hello everyone,
> Here at where I work we have 3 different work order priorities:
> #3: Emergency (Immediate)
> #2: Urgent (Within 7 days)
> #1: Low
>
> We are thinking about adding more priorities to the system and was
> wondering what kind of different priorities some of you are using for your
> system.
>
> Maximo 6.2.1
> Weblogic
> SQL 2005
>
> Thx in advance,
> mrggutz
>
>
>
>
>
>
>
You can only upload to the files section attachments won't come through.
(Moderator)
Wes Williams
http://www.weswilliams.net
http://www.williamsconnell.com
________________________________
From: "Lampert, Lance R." <lance.lampert@awwu.biz>
To: "'MAXIMO@yahoogroups.com'" <MAXIMO@yahoogroups.com>
Sent: Monday, June 25, 2012 11:14 AM
Subject: RE: [MAXIMO List] Work Order Priorities
Does not look like the attachment made it, so here is the important part.
5-Emergency. Critical asset has failed. Needs immediate attention; requires dispatch of personnel from another facility, or reassignment from another work order, or unscheduled overtime, or a call out.
4-Urgent. Failure of critical asset is suspected or pending, or a non-critical asset has failed. Scheduled overtime may be required. Attention required within 1-5 business days.
3-Medium Priority. Attention needed 6-14 calendar days.
2-Low priority. Several work orders may be consolidated prior to being scheduled at a particular facility. Attention desired 15-60 calendar days.
1-No failure; Lowest priority. Several work orders may be consolidated prior to being scheduled at a particular facility. Attention desired within 6 months.
Process
1. Person creating the work order should read the definitions in the Work Order priority field and select the priority that best describes the time frame they need the work completed.
2. Person creating the work order should use the "Priority Justification" field to note reasons for high priority work orders.
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Lampert, Lance R.
Sent: Monday, June 25, 2012 8:12 AM
To: 'MAXIMO@yahoogroups.com'
Subject: RE: [MAXIMO List] Work Order Priorities
Take a look at the attachment, this is what we did a few years ago. Since we have had time to use the definitions, reality is that our priority 1 and 2 do not get used that often. The priority 4 has been a source of much discourse due to how different work groups view their needs. However it has helped us better direct our work force to the right places and right times.
From: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com> [mailto:MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>] On Behalf Of George
Sent: Monday, June 25, 2012 7:58 AM
To: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
Subject: [MAXIMO List] Work Order Priorities
Hello everyone,
Here at where I work we have 3 different work order priorities:
#3: Emergency (Immediate)
#2: Urgent (Within 7 days)
#1: Low
We are thinking about adding more priorities to the system and was wondering what kind of different priorities some of you are using for your system.
Maximo 6.2.1
Weblogic
SQL 2005
Thx in advance,
mrggutz
Hi,
We use this as one of our KPIs. Priority 1 and 2 on our list are reactive maintenance that has to be done as soon as possible with 1 being that the production line was actually stopped because of the failure.
All of the others can be planned.
So we total the hours charged to 1 and 2 and divide by the total hours charged across all priorities to get the percentage reactive.
Total hours for 3,4 and 5 and divide by total to get planned.
We use fialure codes to indicate where the issue was not a failure but an operator error like set up or having a e-stop pushed. That gives us a sub-set of operator induced reactive.
Dave Bone
--- In MAXIMO@yahoogroups.com, Juniko <juniko@...> wrote:
>
> It is a very complete priority work order I think....
> I agree with Lampert that priority of wo does always refer to datetime
> where the work should be done.....because of criticality of asset...
>
> Warm Regards,
> Juniko W Batista
> On Jun 25, 2012 11:14 PM, "Lampert, Lance R." <lance.lampert@...>
> wrote:
>
> > **
> >
> >
> > Does not look like the attachment made it, so here is the important part.
> >
> > 5-Emergency. Critical asset has failed. Needs immediate attention;
> > requires dispatch of personnel from another facility, or reassignment from
> > another work order, or unscheduled overtime, or a call out.
> >
> > 4-Urgent. Failure of critical asset is suspected or pending, or a
> > non-critical asset has failed. Scheduled overtime may be required.
> > Attention required within 1-5 business days.
> >
> > 3-Medium Priority. Attention needed 6-14 calendar days.
> >
> > 2-Low priority. Several work orders may be consolidated prior to being
> > scheduled at a particular facility. Attention desired 15-60 calendar days.
> >
> > 1-No failure; Lowest priority. Several work orders may be consolidated
> > prior to being scheduled at a particular facility. Attention desired within
> > 6 months.
> >
> > Process
> >
> > 1. Person creating the work order should read the definitions in the Work
> > Order priority field and select the priority that best describes the time
> > frame they need the work completed.
> >
> > 2. Person creating the work order should use the "Priority Justification"
> > field to note reasons for high priority work orders.
> >
> > From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
> > Lampert, Lance R.
> > Sent: Monday, June 25, 2012 8:12 AM
> > To: 'MAXIMO@yahoogroups.com'
> > Subject: RE: [MAXIMO List] Work Order Priorities
> >
> > Take a look at the attachment, this is what we did a few years ago. Since
> > we have had time to use the definitions, reality is that our priority 1 and
> > 2 do not get used that often. The priority 4 has been a source of much
> > discourse due to how different work groups view their needs. However it has
> > helped us better direct our work force to the right places and right times.
> >
> > From: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com> [mailto:
> > MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>] On Behalf Of
> > George
> > Sent: Monday, June 25, 2012 7:58 AM
> > To: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
> > Subject: [MAXIMO List] Work Order Priorities
> >
> > Hello everyone,
> > Here at where I work we have 3 different work order priorities:
> > #3: Emergency (Immediate)
> > #2: Urgent (Within 7 days)
> > #1: Low
> >
> > We are thinking about adding more priorities to the system and was
> > wondering what kind of different priorities some of you are using for your
> > system.
> >
> > Maximo 6.2.1
> > Weblogic
> > SQL 2005
> >
> > Thx in advance,
> > mrggutz
> >
> >
> >
> >
> >
> >
> >
>
>
>
>