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.
Do you use the pmwogen where clause?
I think i have all that figured out now, but run into more of a math issue! Say on the 20th of every month i want to generate the next months PMs.. So normally that works out to 42 days.. On months where that doesn't equal 42 days, say Feburary it will also generate for 2 days in March as well.. How are you handling these situations?
Shannon Sutton
Cell: 571-970-7965
On May 10, 2012, at 11:44 AM, david_teece@cargill.com wrote:
> Shannon,
> We use the PmWogen Crontask for this. We then set up instances of the CRON for each site using a user with the proper rights at that site for the Run As User. You can set specific days and times you want the CRON to run. Then in your Org setup you set how many days ahead to generate for each site. It works like a champ for us.
>
> Dave Teece
>
>
>
>
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are
not the intended recipient.
Looking at this from a planning/scheduling perspective, can you give some background on why the monthly PM generation on the 20th is being requested? That may give some light for ideas on possible options for you.
--- In MAXIMO@yahoogroups.com, Shannon Sutton <ssutton@...> wrote:
>
> Do you use the pmwogen where clause?
>
> I think i have all that figured out now, but run into more of a math issue! Say on the 20th of every month i want to generate the next months PMs.. So normally that works out to 42 days.. On months where that doesn't equal 42 days, say Feburary it will also generate for 2 days in March as well.. How are you handling these situations?
>
>
>
> Shannon Sutton
> Cell: 571-970-7965
>
> On May 10, 2012, at 11:44 AM, david_teece@... wrote:
>
> > Shannon,
> > We use the PmWogen Crontask for this. We then set up instances of the CRON for each site using a user with the proper rights at that site for the Run As User. You can set specific days and times you want the CRON to run. Then in your Org setup you set how many days ahead to generate for each site. It works like a champ for us.
> >
> > Dave Teece
> >
> >
> >
> >
>
> This message is for the named person's use only. It may contain confidential,
> proprietary or legally privileged information. No confidentiality or privilege
> is waived or lost by any mistransmission. If you receive this message in error,
> please immediately delete it and all copies of it from your system, destroy any
> hard copies of it and notify the sender. You must not, directly or indirectly,
> use, disclose, distribute, print, or copy any part of this message if you are
> not the intended recipient.
>
>
>
>
>
Hi,
We generate PMs 45 days ahead every day. That way we have all of the work orders for the next 45 days available to plan materials and labor. You could do this then give them queries to look for the PMs due next month or this month.
and datediff(mm, SCHEDFINISH,getdate()) >= 0
and datediff(mm, SCHEDFINISH,getdate()) < 1
We added a couple of fields OSCEARLIESTSTARTDATE and OSCLATESTFINISHDATE finish dates that are +/- a number of days from the SCHEDFINISH date based on the frequency of the job plan. Say the PM frequency is 30 days and the job plan on the work order is the one using job plan sequence 6 so the job plan frequency is 180 days. For our KPI that work order has to be completed +/- 28 days of the SCHEDFINISH date to be considered completed on time. So the escalations and actions update the OSCEARLIESTSTARTDATE finish to SCHEDFINISH - 28 and the OSCLATESTFINISHDATE finish to SCHEDFINISH + 28.
The users and planner have queries to find work orders in the zone to be completed on time. Basically the query uses the date difference.
and datediff(dd,OSCEARLIESTSTARTDATE,getdate()) >= 0
and datediff(dd,OSCLATESTFINISHDATE,getdate()) < 0
The planners can adjust the SCHEDFINISH based on the plant production plan and then the system will readjust the OSCEARLIESTSTARTDATE and OSCLATESTFINISHDATE. The escalations run every 5 minutes.
Dave Bone
--- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@...> wrote:
>
> Looking at this from a planning/scheduling perspective, can you give some background on why the monthly PM generation on the 20th is being requested? That may give some light for ideas on possible options for you.
>
> --- In MAXIMO@yahoogroups.com, Shannon Sutton <ssutton@> wrote:
> >
> > Do you use the pmwogen where clause?
> >
> > I think i have all that figured out now, but run into more of a math issue! Say on the 20th of every month i want to generate the next months PMs.. So normally that works out to 42 days.. On months where that doesn't equal 42 days, say Feburary it will also generate for 2 days in March as well.. How are you handling these situations?
> >
> >
> >
> > Shannon Sutton
> > Cell: 571-970-7965
> >
> > On May 10, 2012, at 11:44 AM, david_teece@ wrote:
> >
> > > Shannon,
> > > We use the PmWogen Crontask for this. We then set up instances of the CRON for each site using a user with the proper rights at that site for the Run As User. You can set specific days and times you want the CRON to run. Then in your Org setup you set how many days ahead to generate for each site. It works like a champ for us.
> > >
> > > Dave Teece
> > >
> > >
> > >
> > >
> >
> > This message is for the named person's use only. It may contain confidential,
> > proprietary or legally privileged information. No confidentiality or privilege
> > is waived or lost by any mistransmission. If you receive this message in error,
> > please immediately delete it and all copies of it from your system, destroy any
> > hard copies of it and notify the sender. You must not, directly or indirectly,
> > use, disclose, distribute, print, or copy any part of this message if you are
> > not the intended recipient.
> >
> >
> >
> >
> >
>
I think we need to take a field trip to Dave's office sometime and pick his brain for an afternoon. More great stuff to think about.
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> Hi,
>
> We generate PMs 45 days ahead every day. That way we have all of the work orders for the next 45 days available to plan materials and labor. You could do this then give them queries to look for the PMs due next month or this month.
>
> and datediff(mm, SCHEDFINISH,getdate()) >= 0
> and datediff(mm, SCHEDFINISH,getdate()) < 1
>
> We added a couple of fields OSCEARLIESTSTARTDATE and OSCLATESTFINISHDATE finish dates that are +/- a number of days from the SCHEDFINISH date based on the frequency of the job plan. Say the PM frequency is 30 days and the job plan on the work order is the one using job plan sequence 6 so the job plan frequency is 180 days. For our KPI that work order has to be completed +/- 28 days of the SCHEDFINISH date to be considered completed on time. So the escalations and actions update the OSCEARLIESTSTARTDATE finish to SCHEDFINISH - 28 and the OSCLATESTFINISHDATE finish to SCHEDFINISH + 28.
>
> The users and planner have queries to find work orders in the zone to be completed on time. Basically the query uses the date difference.
>
> and datediff(dd,OSCEARLIESTSTARTDATE,getdate()) >= 0
> and datediff(dd,OSCLATESTFINISHDATE,getdate()) < 0
>
> The planners can adjust the SCHEDFINISH based on the plant production plan and then the system will readjust the OSCEARLIESTSTARTDATE and OSCLATESTFINISHDATE. The escalations run every 5 minutes.
>
>
> Dave Bone
>
> --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> >
> > Looking at this from a planning/scheduling perspective, can you give some background on why the monthly PM generation on the 20th is being requested? That may give some light for ideas on possible options for you.
> >
> > --- In MAXIMO@yahoogroups.com, Shannon Sutton <ssutton@> wrote:
> > >
> > > Do you use the pmwogen where clause?
> > >
> > > I think i have all that figured out now, but run into more of a math issue! Say on the 20th of every month i want to generate the next months PMs.. So normally that works out to 42 days.. On months where that doesn't equal 42 days, say Feburary it will also generate for 2 days in March as well.. How are you handling these situations?
> > >
> > >
> > >
> > > Shannon Sutton
> > > Cell: 571-970-7965
> > >
> > > On May 10, 2012, at 11:44 AM, david_teece@ wrote:
> > >
> > > > Shannon,
> > > > We use the PmWogen Crontask for this. We then set up instances of the CRON for each site using a user with the proper rights at that site for the Run As User. You can set specific days and times you want the CRON to run. Then in your Org setup you set how many days ahead to generate for each site. It works like a champ for us.
> > > >
> > > > Dave Teece
> > > >
> > > >
> > > >
> > > >
> > >
> > > This message is for the named person's use only. It may contain confidential,
> > > proprietary or legally privileged information. No confidentiality or privilege
> > > is waived or lost by any mistransmission. If you receive this message in error,
> > > please immediately delete it and all copies of it from your system, destroy any
> > > hard copies of it and notify the sender. You must not, directly or indirectly,
> > > use, disclose, distribute, print, or copy any part of this message if you are
> > > not the intended recipient.
> > >
> > >
> > >
> > >
> > >
> >
>
"field trip", this is called (external) benchmarking
Sent on the Sprint� Now Network from my BlackBerry�
-----Original Message-----
From: "Jason Verly" <jason.verly@yahoo.com>
Sender: MAXIMO@yahoogroups.com
Date: Fri, 11 May 2012 18:38:52
To: <MAXIMO@yahoogroups.com>
Reply-To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: PM Generation
I think we need to take a field trip to Dave's office sometime and pick his brain for an afternoon. More great stuff to think about.
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> Hi,
>
> We generate PMs 45 days ahead every day. That way we have all of the work orders for the next 45 days available to plan materials and labor. You could do this then give them queries to look for the PMs due next month or this month.
>
> and datediff(mm, SCHEDFINISH,getdate()) >= 0
> and datediff(mm, SCHEDFINISH,getdate()) < 1
>
> We added a couple of fields OSCEARLIESTSTARTDATE and OSCLATESTFINISHDATE finish dates that are +/- a number of days from the SCHEDFINISH date based on the frequency of the job plan. Say the PM frequency is 30 days and the job plan on the work order is the one using job plan sequence 6 so the job plan frequency is 180 days. For our KPI that work order has to be completed +/- 28 days of the SCHEDFINISH date to be considered completed on time. So the escalations and actions update the OSCEARLIESTSTARTDATE finish to SCHEDFINISH - 28 and the OSCLATESTFINISHDATE finish to SCHEDFINISH + 28.
>
> The users and planner have queries to find work orders in the zone to be completed on time. Basically the query uses the date difference.
>
> and datediff(dd,OSCEARLIESTSTARTDATE,getdate()) >= 0
> and datediff(dd,OSCLATESTFINISHDATE,getdate()) < 0
>
> The planners can adjust the SCHEDFINISH based on the plant production plan and then the system will readjust the OSCEARLIESTSTARTDATE and OSCLATESTFINISHDATE. The escalations run every 5 minutes.
>
>
> Dave Bone
>
> --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> >
> > Looking at this from a planning/scheduling perspective, can you give some background on why the monthly PM generation on the 20th is being requested? That may give some light for ideas on possible options for you.
> >
> > --- In MAXIMO@yahoogroups.com, Shannon Sutton <ssutton@> wrote:
> > >
> > > Do you use the pmwogen where clause?
> > >
> > > I think i have all that figured out now, but run into more of a math issue! Say on the 20th of every month i want to generate the next months PMs.. So normally that works out to 42 days.. On months where that doesn't equal 42 days, say Feburary it will also generate for 2 days in March as well.. How are you handling these situations?
> > >
> > >
> > >
> > > Shannon Sutton
> > > Cell: 571-970-7965
> > >
> > > On May 10, 2012, at 11:44 AM, david_teece@ wrote:
> > >
> > > > Shannon,
> > > > We use the PmWogen Crontask for this. We then set up instances of the CRON for each site using a user with the proper rights at that site for the Run As User. You can set specific days and times you want the CRON to run. Then in your Org setup you set how many days ahead to generate for each site. It works like a champ for us.
> > > >
> > > > Dave Teece
> > > >
> > > >
> > > >
> > > >
> > >
> > > This message is for the named person's use only. It may contain confidential,
> > > proprietary or legally privileged information. No confidentiality or privilege
> > > is waived or lost by any mistransmission. If you receive this message in error,
> > > please immediately delete it and all copies of it from your system, destroy any
> > > hard copies of it and notify the sender. You must not, directly or indirectly,
> > > use, disclose, distribute, print, or copy any part of this message if you are
> > > not the intended recipient.
> > >
> > >
> > >
> > >
> > >
> >
>
Lol
OK, Jason, I agree - we need to do some external benchmarking at Dave's
place of work sometime.
Dave: prepare to be external benchmarked! :)
Shannon
P.S. John: seriously, though, that's not to denigrate your point - I
appreciate the terminology correction. It's good to know these things.
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
john reeve
Sent: May-11-12 11:59 AM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Re: PM Generation
"field trip", this is called (external) benchmarking
Sent on the SprintR Now Network from my BlackBerryR
-----Original Message-----
From: "Jason Verly" <jason.verly@yahoo.com>
Sender: MAXIMO@yahoogroups.com
Date: Fri, 11 May 2012 18:38:52
To: <MAXIMO@yahoogroups.com>
Reply-To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: PM Generation
I think we need to take a field trip to Dave's office sometime and pick his
brain for an afternoon. More great stuff to think about.
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> Hi,
>
> We generate PMs 45 days ahead every day. That way we have all of the work
orders for the next 45 days available to plan materials and labor. You could
do this then give them queries to look for the PMs due next month or this
month.
>
> and datediff(mm, SCHEDFINISH,getdate()) >= 0
> and datediff(mm, SCHEDFINISH,getdate()) < 1
>
> We added a couple of fields OSCEARLIESTSTARTDATE and OSCLATESTFINISHDATE
finish dates that are +/- a number of days from the SCHEDFINISH date based
on the frequency of the job plan. Say the PM frequency is 30 days and the
job plan on the work order is the one using job plan sequence 6 so the job
plan frequency is 180 days. For our KPI that work order has to be completed
+/- 28 days of the SCHEDFINISH date to be considered completed on time. So
the escalations and actions update the OSCEARLIESTSTARTDATE finish to
SCHEDFINISH - 28 and the OSCLATESTFINISHDATE finish to SCHEDFINISH + 28.
>
> The users and planner have queries to find work orders in the zone to be
completed on time. Basically the query uses the date difference.
>
> and datediff(dd,OSCEARLIESTSTARTDATE,getdate()) >= 0
> and datediff(dd,OSCLATESTFINISHDATE,getdate()) < 0
>
> The planners can adjust the SCHEDFINISH based on the plant production plan
and then the system will readjust the OSCEARLIESTSTARTDATE and
OSCLATESTFINISHDATE. The escalations run every 5 minutes.
>
>
> Dave Bone
>
> --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> >
> > Looking at this from a planning/scheduling perspective, can you give
some background on why the monthly PM generation on the 20th is being
requested? That may give some light for ideas on possible options for you.
> >
> > --- In MAXIMO@yahoogroups.com, Shannon Sutton <ssutton@> wrote:
> > >
> > > Do you use the pmwogen where clause?
> > >
> > > I think i have all that figured out now, but run into more of a math
issue! Say on the 20th of every month i want to generate the next months
PMs.. So normally that works out to 42 days.. On months where that doesn't
equal 42 days, say Feburary it will also generate for 2 days in March as
well.. How are you handling these situations?
> > >
> > >
> > >
> > > Shannon Sutton
> > > Cell: 571-970-7965
> > >
> > > On May 10, 2012, at 11:44 AM, david_teece@ wrote:
> > >
> > > > Shannon,
> > > > We use the PmWogen Crontask for this. We then set up instances of
the CRON for each site using a user with the proper rights at that site for
the Run As User. You can set specific days and times you want the CRON to
run. Then in your Org setup you set how many days ahead to generate for each
site. It works like a champ for us.
> > > >
> > > > Dave Teece
> > > >
> > > >
> > > >
> > > >
> > >
> > > This message is for the named person's use only. It may contain
confidential,
> > > proprietary or legally privileged information. No confidentiality or
privilege
> > > is waived or lost by any mistransmission. If you receive this
message in error,
> > > please immediately delete it and all copies of it from your system,
destroy any
> > > hard copies of it and notify the sender. You must not, directly or
indirectly,
> > > use, disclose, distribute, print, or copy any part of this message if
you are
> > > not the intended recipient.
> > >
> > >
> > >
> > >
> > >
> >
>
------------------------------------
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
Hi,
I've never been externally benchmarked. I hope it does not have anything to do with whips and chains :-0
Although it does not sound as bad as being internally benchmarked :-(
I work out of Las Veags so maybe we'll do some club benchmarking :-)
Dave Bone
--- In MAXIMO@yahoogroups.com, "Shannon Rotz" <shannonrotz@...> wrote:
>
> Lol
>
> OK, Jason, I agree - we need to do some external benchmarking at Dave's
> place of work sometime.
>
> Dave: prepare to be external benchmarked! :)
>
>
>
>
> Shannon
>
> P.S. John: seriously, though, that's not to denigrate your point - I
> appreciate the terminology correction. It's good to know these things.
>
>
>
> -----Original Message-----
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
> john reeve
> Sent: May-11-12 11:59 AM
> To: MAXIMO@yahoogroups.com
> Subject: Re: [MAXIMO List] Re: PM Generation
>
> "field trip", this is called (external) benchmarking
>
> Sent on the SprintR Now Network from my BlackBerryR
>
>
>
> -----Original Message-----
>
> From: "Jason Verly" <jason.verly@...>
>
> Sender: MAXIMO@yahoogroups.com
>
> Date: Fri, 11 May 2012 18:38:52
>
> To: <MAXIMO@yahoogroups.com>
>
> Reply-To: MAXIMO@yahoogroups.com
>
> Subject: [MAXIMO List] Re: PM Generation
>
>
>
> I think we need to take a field trip to Dave's office sometime and pick his
> brain for an afternoon. More great stuff to think about.
>
>
>
> --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
>
> >
>
> > Hi,
>
> >
>
> > We generate PMs 45 days ahead every day. That way we have all of the work
> orders for the next 45 days available to plan materials and labor. You could
> do this then give them queries to look for the PMs due next month or this
> month.
>
> >
>
> > and datediff(mm, SCHEDFINISH,getdate()) >= 0
>
> > and datediff(mm, SCHEDFINISH,getdate()) < 1
>
> >
>
> > We added a couple of fields OSCEARLIESTSTARTDATE and OSCLATESTFINISHDATE
> finish dates that are +/- a number of days from the SCHEDFINISH date based
> on the frequency of the job plan. Say the PM frequency is 30 days and the
> job plan on the work order is the one using job plan sequence 6 so the job
> plan frequency is 180 days. For our KPI that work order has to be completed
> +/- 28 days of the SCHEDFINISH date to be considered completed on time. So
> the escalations and actions update the OSCEARLIESTSTARTDATE finish to
> SCHEDFINISH - 28 and the OSCLATESTFINISHDATE finish to SCHEDFINISH + 28.
>
> >
>
> > The users and planner have queries to find work orders in the zone to be
> completed on time. Basically the query uses the date difference.
>
> >
>
> > and datediff(dd,OSCEARLIESTSTARTDATE,getdate()) >= 0
>
> > and datediff(dd,OSCLATESTFINISHDATE,getdate()) < 0
>
> >
>
> > The planners can adjust the SCHEDFINISH based on the plant production plan
> and then the system will readjust the OSCEARLIESTSTARTDATE and
> OSCLATESTFINISHDATE. The escalations run every 5 minutes.
>
> >
>
> >
>
> > Dave Bone
>
> >
>
> > --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
>
> > >
>
> > > Looking at this from a planning/scheduling perspective, can you give
> some background on why the monthly PM generation on the 20th is being
> requested? That may give some light for ideas on possible options for you.
>
> > >
>
> > > --- In MAXIMO@yahoogroups.com, Shannon Sutton <ssutton@> wrote:
>
> > > >
>
> > > > Do you use the pmwogen where clause?
>
> > > >
>
> > > > I think i have all that figured out now, but run into more of a math
> issue! Say on the 20th of every month i want to generate the next months
> PMs.. So normally that works out to 42 days.. On months where that doesn't
> equal 42 days, say Feburary it will also generate for 2 days in March as
> well.. How are you handling these situations?
>
> > > >
>
> > > >
>
> > > >
>
> > > > Shannon Sutton
>
> > > > Cell: 571-970-7965
>
> > > >
>
> > > > On May 10, 2012, at 11:44 AM, david_teece@ wrote:
>
> > > >
>
> > > > > Shannon,
>
> > > > > We use the PmWogen Crontask for this. We then set up instances of
> the CRON for each site using a user with the proper rights at that site for
> the Run As User. You can set specific days and times you want the CRON to
> run. Then in your Org setup you set how many days ahead to generate for each
> site. It works like a champ for us.
>
> > > > >
>
> > > > > Dave Teece
>
> > > > >
>
> > > > >
>
> > > > >
>
> > > > >
>
> > > >
>
> > > > This message is for the named person's use only. It may contain
> confidential,
>
> > > > proprietary or legally privileged information. No confidentiality or
> privilege
>
> > > > is waived or lost by any mistransmission. If you receive this
> message in error,
>
> > > > please immediately delete it and all copies of it from your system,
> destroy any
>
> > > > hard copies of it and notify the sender. You must not, directly or
> indirectly,
>
> > > > use, disclose, distribute, print, or copy any part of this message if
> you are
>
> > > > not the intended recipient.
>
> > > >
>
> > > >
>
> > > >
>
> > > >
>
> > > >
>
> > >
>
> >
>
>
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------------
>
> 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
>
Lol - sounds great - particularly the club benchmarking!
And I hope no workers were harmed during the internal benchmarking . :)
Shannon
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
in2data
Sent: May-11-12 2:00 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: PM Generation
Hi,
I've never been externally benchmarked. I hope it does not have anything to
do with whips and chains :-0
Although it does not sound as bad as being internally benchmarked :-(
I work out of Las Veags so maybe we'll do some club benchmarking :-)
Dave Bone
--- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "Shannon
Rotz" <shannonrotz@...> wrote:
>
> Lol
>
> OK, Jason, I agree - we need to do some external benchmarking at Dave's
> place of work sometime.
>
> Dave: prepare to be external benchmarked! :)
>
>
>
>
> Shannon
>
> P.S. John: seriously, though, that's not to denigrate your point - I
> appreciate the terminology correction. It's good to know these things.
>
>
>
> -----Original Message-----
> From: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
[mailto:MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ] On Behalf
Of
> john reeve
> Sent: May-11-12 11:59 AM
> To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
> Subject: Re: [MAXIMO List] Re: PM Generation
>
> "field trip", this is called (external) benchmarking
>
> Sent on the SprintR Now Network from my BlackBerryR
>
>
>
> -----Original Message-----
>
> From: "Jason Verly" <jason.verly@...>
>
> Sender: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
>
> Date: Fri, 11 May 2012 18:38:52
>
> To: <MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> >
>
> Reply-To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
>
> Subject: [MAXIMO List] Re: PM Generation
>
>
>
> I think we need to take a field trip to Dave's office sometime and pick
his
> brain for an afternoon. More great stuff to think about.
>
>
>
> --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ,
"in2data" <in2data@> wrote:
>
> >
>
> > Hi,
>
> >
>
> > We generate PMs 45 days ahead every day. That way we have all of the
work
> orders for the next 45 days available to plan materials and labor. You
could
> do this then give them queries to look for the PMs due next month or this
> month.
>
> >
>
> > and datediff(mm, SCHEDFINISH,getdate()) >= 0
>
> > and datediff(mm, SCHEDFINISH,getdate()) < 1
>
> >
>
> > We added a couple of fields OSCEARLIESTSTARTDATE and OSCLATESTFINISHDATE
> finish dates that are +/- a number of days from the SCHEDFINISH date based
> on the frequency of the job plan. Say the PM frequency is 30 days and the
> job plan on the work order is the one using job plan sequence 6 so the job
> plan frequency is 180 days. For our KPI that work order has to be
completed
> +/- 28 days of the SCHEDFINISH date to be considered completed on time. So
> the escalations and actions update the OSCEARLIESTSTARTDATE finish to
> SCHEDFINISH - 28 and the OSCLATESTFINISHDATE finish to SCHEDFINISH + 28.
>
> >
>
> > The users and planner have queries to find work orders in the zone to be
> completed on time. Basically the query uses the date difference.
>
> >
>
> > and datediff(dd,OSCEARLIESTSTARTDATE,getdate()) >= 0
>
> > and datediff(dd,OSCLATESTFINISHDATE,getdate()) < 0
>
> >
>
> > The planners can adjust the SCHEDFINISH based on the plant production
plan
> and then the system will readjust the OSCEARLIESTSTARTDATE and
> OSCLATESTFINISHDATE. The escalations run every 5 minutes.
>
> >
>
> >
>
> > Dave Bone
>
> >
>
> > --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "Jason
Verly" <jason.verly@> wrote:
>
> > >
>
> > > Looking at this from a planning/scheduling perspective, can you give
> some background on why the monthly PM generation on the 20th is being
> requested? That may give some light for ideas on possible options for you.
>
> > >
>
> > > --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ,
Shannon Sutton <ssutton@> wrote:
>
> > > >
>
> > > > Do you use the pmwogen where clause?
>
> > > >
>
> > > > I think i have all that figured out now, but run into more of a math
> issue! Say on the 20th of every month i want to generate the next months
> PMs.. So normally that works out to 42 days.. On months where that doesn't
> equal 42 days, say Feburary it will also generate for 2 days in March as
> well.. How are you handling these situations?
>
> > > >
>
> > > >
>
> > > >
>
> > > > Shannon Sutton
>
> > > > Cell: 571-970-7965
>
> > > >
>
> > > > On May 10, 2012, at 11:44 AM, david_teece@ wrote:
>
> > > >
>
> > > > > Shannon,
>
> > > > > We use the PmWogen Crontask for this. We then set up instances of
> the CRON for each site using a user with the proper rights at that site
for
> the Run As User. You can set specific days and times you want the CRON to
> run. Then in your Org setup you set how many days ahead to generate for
each
> site. It works like a champ for us.
>
> > > > >
>
> > > > > Dave Teece
>
> > > > >
>
> > > > >
>
> > > > >
>
> > > > >
>
> > > >
>
> > > > This message is for the named person's use only. It may contain
> confidential,
>
> > > > proprietary or legally privileged information. No confidentiality or
> privilege
>
> > > > is waived or lost by any mistransmission. If you receive this
> message in error,
>
> > > > please immediately delete it and all copies of it from your system,
> destroy any
>
> > > > hard copies of it and notify the sender. You must not, directly or
> indirectly,
>
> > > > use, disclose, distribute, print, or copy any part of this message
if
> you are
>
> > > > not the intended recipient.
>
> > > >
>
> > > >
>
> > > >
>
> > > >
>
> > > >
>
> > >
>
> >
>
>
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------------
>
> Email addresses you might need:
> Posting: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
> Join : MAXIMO-subscribe@yahoogroups.com
<mailto:MAXIMO-subscribe%40yahoogroups.com>
> Leave : MAXIMO-unsubscribe@yahoogroups.com
<mailto:MAXIMO-unsubscribe%40yahoogroups.com>
> Cry : MAXIMO-owner@yahoogroups.com <mailto:MAXIMO-owner%40yahoogroups.com>
> Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
>