<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for GreyCloud</title>
	<atom:link href="http://greycloud.co.uk/index.php/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://greycloud.co.uk</link>
	<description>Services and Tools for Continuous Maintenance Improvement</description>
	<lastBuildDate>Thu, 03 Feb 2011 18:47:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on The Concept of NEGATIVE WORK by admin</title>
		<link>http://greycloud.co.uk/index.php/2011/02/03/the-concept-of-negative-work/comment-page-1/#comment-263</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 03 Feb 2011 18:47:04 +0000</pubDate>
		<guid isPermaLink="false">http://greycloud.co.uk/?p=156#comment-263</guid>
		<description>There is a work execution metric that I have used to identify NEGATIVE WORK both in terms of number of work orders and the estimated hours scheduled v the actual hours recorded. 

This metric is &#039;Completed in the Scheduled Week&#039;. The base assumption is that usually there is a weekly agreed prioritised WO schedule which can be measured against during the execution week as the &#039;frozen schedule&#039;. 

As work orders are marked as completed during that execution week they can be compared against the &#039;frozen schedule&#039;. 

So each completed work order has a derived &#039;Completed in the Scheduled Week&#039; indicator. 
&#039;Completed on the Scheduled Day&#039; 
&#039;Completed in the Scheduled Week&#039; 
&#039;Break-in completion in the scheduled week&#039; 
&#039;Break-in completion raised in the previous week&#039; 
&#039;Completed NOT in the Scheduled Week&#039; 
&#039;Unscheduled Completion&#039; 
&#039;Scheduled&#039; 

Once the execution week has past, the number of WOs/Est.Hrs scheduled in the frozen week remains for trending purposes. WOs that were not done can be re-scheduled to a future time without affecting the trending. 

For identifying NEGATIVE WORK we are interested in the Break-ins and &#039;Completed NOT in the Scheduled Week&#039; and &#039;Unscheduled Completion&#039; categories and need to drill down to the work orders to see the context of the &#039;Schedule Breakers&#039;. 

For my BI-Cycle implementations of this metric these reports are refreshed daily and we can analyse the trend over time and sort/filter and group by responsibility, craft, work type etc and drill through the various charts/grids to the work orders. 

This visibility highlights the &#039;Schedule Breakers&#039; and the groups/individuals behaviors responsible for not sticking to the plan. 

One immediate response that I have seen from the technicians and supervisors to the introduction of this report is their commitment to record in the CMMS all the activities/interventions that they are asked to do. They like the idea of taking the credit for all the the hours that they put in and are much more accurate about recording actual hours and the actual dates for completing the work.</description>
		<content:encoded><![CDATA[<p>There is a work execution metric that I have used to identify NEGATIVE WORK both in terms of number of work orders and the estimated hours scheduled v the actual hours recorded. </p>
<p>This metric is &#8216;Completed in the Scheduled Week&#8217;. The base assumption is that usually there is a weekly agreed prioritised WO schedule which can be measured against during the execution week as the &#8216;frozen schedule&#8217;. </p>
<p>As work orders are marked as completed during that execution week they can be compared against the &#8216;frozen schedule&#8217;. </p>
<p>So each completed work order has a derived &#8216;Completed in the Scheduled Week&#8217; indicator.<br />
&#8216;Completed on the Scheduled Day&#8217;<br />
&#8216;Completed in the Scheduled Week&#8217;<br />
&#8216;Break-in completion in the scheduled week&#8217;<br />
&#8216;Break-in completion raised in the previous week&#8217;<br />
&#8216;Completed NOT in the Scheduled Week&#8217;<br />
&#8216;Unscheduled Completion&#8217;<br />
&#8216;Scheduled&#8217; </p>
<p>Once the execution week has past, the number of WOs/Est.Hrs scheduled in the frozen week remains for trending purposes. WOs that were not done can be re-scheduled to a future time without affecting the trending. </p>
<p>For identifying NEGATIVE WORK we are interested in the Break-ins and &#8216;Completed NOT in the Scheduled Week&#8217; and &#8216;Unscheduled Completion&#8217; categories and need to drill down to the work orders to see the context of the &#8216;Schedule Breakers&#8217;. </p>
<p>For my BI-Cycle implementations of this metric these reports are refreshed daily and we can analyse the trend over time and sort/filter and group by responsibility, craft, work type etc and drill through the various charts/grids to the work orders. </p>
<p>This visibility highlights the &#8216;Schedule Breakers&#8217; and the groups/individuals behaviors responsible for not sticking to the plan. </p>
<p>One immediate response that I have seen from the technicians and supervisors to the introduction of this report is their commitment to record in the CMMS all the activities/interventions that they are asked to do. They like the idea of taking the credit for all the the hours that they put in and are much more accurate about recording actual hours and the actual dates for completing the work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

