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.
TRENDs to follow - for JOB PLANNERS:
~ of the total backlog, what percentage is planned at any given moment
~ Percent of work in Planned state vs. Unplanned (Note: need a field to mark as "fully planned")
~ Planned vs. Actual Hours variance
~ Planned vs. Actual Cost variance
~ Average time in Planning phase
~ Number of WO planned per week, by Planner
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
John,
How would you track the time spent by the PLANNER on a WO? is it reported
on the same WO being planned ? Sometime it`s not straight foreward to
capture the planning time on each WO being planned. Planning is prior to
approval, so the WO is not in a status to allow actuals to be reported.
As for the 2nd KPI what I usually recommend is to track this using Statuses
(Waiting to be Planned vs Planned)
On Sun, Sep 9, 2012 at 4:36 AM, planschd <planschd@yahoo.com> wrote:
> **
>
>
> TRENDs to follow - for JOB PLANNERS:
>
> ~ of the total backlog, what percentage is planned at any given moment
> ~ Percent of work in Planned state vs. Unplanned (Note: need a field to
> mark as "fully planned")
> ~ Planned vs. Actual Hours variance
> ~ Planned vs. Actual Cost variance
> ~ Average time in Planning phase
> ~ Number of WO planned per week, by Planner
>
> 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
>
>
>
--
Mohamed Skandaji, MBA, PMP
I (suggest) use of a combination of Status changes, and a new field called "Fully Planned", and another field called Planner Name.
There could be a synonym of WAPPR called "INPLANNING".
Then have another synonym of WAPPR called "PLANNED" (planning complete).
I have an escalation which then sets Fully Planned flag at instant PLANNED.
Otherwise it is the datetime difference in Wostatus table. No labor actuals should be necessary.
Sent on the Sprint® Now Network from my BlackBerry®
-----Original Message-----
From: Mohamed Skandaji <mohska@gmail.com>
Sender: MAXIMO@yahoogroups.com
Date: Sun, 9 Sep 2012 14:05:52
To: <MAXIMO@yahoogroups.com>
Reply-To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Tip of the Day #249
John,
How would you track the time spent by the PLANNER on a WO? is it reported
on the same WO being planned ? Sometime it`s not straight foreward to
capture the planning time on each WO being planned. Planning is prior to
approval, so the WO is not in a status to allow actuals to be reported.
As for the 2nd KPI what I usually recommend is to track this using Statuses
(Waiting to be Planned vs Planned)
On Sun, Sep 9, 2012 at 4:36 AM, planschd <planschd@yahoo.com> wrote:
> **
>
>
> TRENDs to follow - for JOB PLANNERS:
>
> ~ of the total backlog, what percentage is planned at any given moment
> ~ Percent of work in Planned state vs. Unplanned (Note: need a field to
> mark as "fully planned")
> ~ Planned vs. Actual Hours variance
> ~ Planned vs. Actual Cost variance
> ~ Average time in Planning phase
> ~ Number of WO planned per week, by Planner
>
> 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
>
>
>
--
Mohamed Skandaji, MBA, PMP
------------------------------------
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