<?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 on: Examining Chrysler Closures With Monarch</title>
	<atom:link href="http://ExcelWithMonarch.com/calcfield/examining-chrysler-closures-with-monarch/feed" rel="self" type="application/rss+xml" />
	<link>http://ExcelWithMonarch.com/calcfield/examining-chrysler-closures-with-monarch</link>
	<description>Stop working for your data. Make your data work for you.</description>
	<lastBuildDate>Tue, 26 Apr 2011 22:17:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chickenman</title>
		<link>http://ExcelWithMonarch.com/calcfield/examining-chrysler-closures-with-monarch/comment-page-1#comment-7095</link>
		<dc:creator>Chickenman</dc:creator>
		<pubDate>Fri, 03 Jul 2009 14:29:04 +0000</pubDate>
		<guid isPermaLink="false">http://ExcelWithMonarch.com/calcfield/examining-chrysler-closures-with-monarch#comment-7095</guid>
		<description>Echoing the other poster, this is an Excel-lent illustration of fast and powerful data analysis!
Nice job.

BTW - Foulke Management Corp has a 4-digit zip and so faked out the address block and gave a blank region. Obviously, in practice one could fiddle with some more calc fields to parse the state.</description>
		<content:encoded><![CDATA[<p>Echoing the other poster, this is an Excel-lent illustration of fast and powerful data analysis!<br />
Nice job.</p>
<p>BTW &#8211; Foulke Management Corp has a 4-digit zip and so faked out the address block and gave a blank region. Obviously, in practice one could fiddle with some more calc fields to parse the state.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandy</title>
		<link>http://ExcelWithMonarch.com/calcfield/examining-chrysler-closures-with-monarch/comment-page-1#comment-6081</link>
		<dc:creator>Sandy</dc:creator>
		<pubDate>Sun, 31 May 2009 21:44:20 +0000</pubDate>
		<guid isPermaLink="false">http://ExcelWithMonarch.com/calcfield/examining-chrysler-closures-with-monarch#comment-6081</guid>
		<description>Thanks! I&#039;m glad that you&#039;re enjoying the site.

Calculations such as what you&#039;ve suggested really do assist in finding commonality and outliers where combinations exist. Nice work! Techniques such as these not only work very well with this particular case, but are also readily portable to other challenges. Thanks for taking the time to share your thoughts.</description>
		<content:encoded><![CDATA[<p>Thanks! I&#8217;m glad that you&#8217;re enjoying the site.</p>
<p>Calculations such as what you&#8217;ve suggested really do assist in finding commonality and outliers where combinations exist. Nice work! Techniques such as these not only work very well with this particular case, but are also readily portable to other challenges. Thanks for taking the time to share your thoughts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mrzer0</title>
		<link>http://ExcelWithMonarch.com/calcfield/examining-chrysler-closures-with-monarch/comment-page-1#comment-6077</link>
		<dc:creator>mrzer0</dc:creator>
		<pubDate>Sun, 31 May 2009 20:56:41 +0000</pubDate>
		<guid isPermaLink="false">http://ExcelWithMonarch.com/calcfield/examining-chrysler-closures-with-monarch#comment-6077</guid>
		<description>FWIW, I suggest that the following enhancement might be worthwhile as an example of another analysis technique.  

Add ...
Chrysler_Line_2: if(instr(&quot;C&quot;,Lines)&gt;0,1,0)
Dodge_Line_2: if(instr(&quot;D&quot;,Lines)&gt;0,2,0)
Jeep_Line_2: if(instr(&quot;J&quot;,Lines)&gt;0,4,0)
Truck_Line_2: if(instr(&quot;T&quot;,Lines)&gt;0,8,0)

These additional calculations allow is an interesting analysis extension effect represented by the value 

Lines_Sum =  Chrysler_Line_2 + Dodge_Line_2 + Jeep_Line_2 + Truck_Line_2.  

This calculation yields a number which will be found in the range of 1 - 15.  Each increment of Lines_Sum value represents a unique combination of Vehicle Lines closed *possible* in the data.

Thus ... IF Lines_Sum = 6 then the lines closed can only Dodge and Jeep and no other combination.  (The more anal-retentive readers (Does anal-retentive have a Hyphen??? (grin!)) will have noticed that the values assigned by the suggested additional calculated fields are powers of 2.) 

Further, the absence of a value for Lines_Sum in the range of 1 - 15 in summary data means that the represented condition is NOT found in the data.  For example, there are no 6 values (DJ only) of Sum_Lines and only two 9&#039;s (CT only) found in the 789 closed dealerships.  Also, multiple specific values for Lines_Sum could be selected to represent underlying combination condition.  Dealerships having odd values of Lines_Sum must have the Chrysler line, etc.    

I present this only for consideration as another tool for the analysis tool belt.  Sometimes this technique can yield some interesting insights into data with which one is unfamiliar and which may contain hidden patterns that might have some significance.</description>
		<content:encoded><![CDATA[<p>FWIW, I suggest that the following enhancement might be worthwhile as an example of another analysis technique.  </p>
<p>Add &#8230;<br />
Chrysler_Line_2: if(instr(&#8220;C&#8221;,Lines)&gt;0,1,0)<br />
Dodge_Line_2: if(instr(&#8220;D&#8221;,Lines)&gt;0,2,0)<br />
Jeep_Line_2: if(instr(&#8220;J&#8221;,Lines)&gt;0,4,0)<br />
Truck_Line_2: if(instr(&#8220;T&#8221;,Lines)&gt;0,8,0)</p>
<p>These additional calculations allow is an interesting analysis extension effect represented by the value </p>
<p>Lines_Sum =  Chrysler_Line_2 + Dodge_Line_2 + Jeep_Line_2 + Truck_Line_2.  </p>
<p>This calculation yields a number which will be found in the range of 1 &#8211; 15.  Each increment of Lines_Sum value represents a unique combination of Vehicle Lines closed *possible* in the data.</p>
<p>Thus &#8230; IF Lines_Sum = 6 then the lines closed can only Dodge and Jeep and no other combination.  (The more anal-retentive readers (Does anal-retentive have a Hyphen??? (grin!)) will have noticed that the values assigned by the suggested additional calculated fields are powers of 2.) </p>
<p>Further, the absence of a value for Lines_Sum in the range of 1 &#8211; 15 in summary data means that the represented condition is NOT found in the data.  For example, there are no 6 values (DJ only) of Sum_Lines and only two 9&#8217;s (CT only) found in the 789 closed dealerships.  Also, multiple specific values for Lines_Sum could be selected to represent underlying combination condition.  Dealerships having odd values of Lines_Sum must have the Chrysler line, etc.    </p>
<p>I present this only for consideration as another tool for the analysis tool belt.  Sometimes this technique can yield some interesting insights into data with which one is unfamiliar and which may contain hidden patterns that might have some significance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mrzer0</title>
		<link>http://ExcelWithMonarch.com/calcfield/examining-chrysler-closures-with-monarch/comment-page-1#comment-6076</link>
		<dc:creator>mrzer0</dc:creator>
		<pubDate>Sun, 31 May 2009 19:39:52 +0000</pubDate>
		<guid isPermaLink="false">http://ExcelWithMonarch.com/calcfield/examining-chrysler-closures-with-monarch#comment-6076</guid>
		<description>I just wanted to thank you for the effort that is so evident in this posting.  I found it to be most instructive as I have with so many of your posts on this excel-ent site.

I am looking forward to your next post.</description>
		<content:encoded><![CDATA[<p>I just wanted to thank you for the effort that is so evident in this posting.  I found it to be most instructive as I have with so many of your posts on this excel-ent site.</p>
<p>I am looking forward to your next post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

