<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
	
	<channel>
		<title>distributedspreadsheet's blog</title>
		<link>http://distributedspreadsheet.myblogsite.com/index.html</link>
		<description>Creative Uses of Distributed Spreadsheet</description>
		<language>en</language>
		<managingEditor>admin@fortunecity.com</managingEditor>
                <copyright>Copyright 2008</copyright>
		<generator>Pivot Pivot - 1.30 RC: 'Rippersnapper'</generator>
		<pubDate>Tue, 25 Mar 2008 15:05:02 -0400</pubDate>
		<ttl>60</ttl>
		
		
		
		
		<item>
			<title>Please explain the limit of 12 Contributors</title>
			<link>http://distributedspreadsheet.myblogsite.com/entry7.html</link>
			<comments>http://distributedspreadsheet.myblogsite.com/entry7.html#comm</comments>
                        <description><![CDATA[ <p>In version 1.0 of Distributed Spreadsheet, the limit of 12 applies only to the merging process.&nbsp; This means that in a single merge of contributed worksheets, only the work of 12 Contributors can be merged in a single step.&nbsp; Allow me to explain further.</p>

<p>Distributed Spreadsheet works by assigning users as “Contributors” to worksheets within a workbook.&nbsp; Let’s assume the workbook in question had a total of 25 worksheets.&nbsp; There are 20 employees who will act as Contributors and each has been assigned a unique page within the workbook (it is permitted to assign a single user to multiple worksheets if necessary.&nbsp; It is not recommended to assign multiple users to the same worksheet).&nbsp; All of the 25 employees receive their worksheet(s) via e-mail and modify the content of their assigned worksheet.&nbsp; The completed worksheets are all returned.</p>

<p>The Distributor now has the option of merging the updated worksheets into the original workbook, viewing the individual worksheets as received or merging only a selected few of the overall worksheets received.&nbsp; If the Distributor desires to merge all of the received worksheets, the merge limit of 12 contributions is imposed.&nbsp; These 12 can be any 12 received contributions the Distributor desires to merge.&nbsp; It does not matter if each of the 12 Contributors received multiple worksheets as part of the initial request.&nbsp; What matters is that no more than 12 received contributions is merged.</p>

<p>In many cases, the 12-merge limit is of no concern. &nbsp;Unless there is a summary or roll-up worksheet through which totals across all the worksheets is being generated, the need to merge everything together is not so vital as to be a show stopper. &nbsp;The worksheets received from each Contributor can be viewed individually and groups of 12 can be merged as separate actions if necessary. &nbsp;It all comes down to how Distributed Spreadsheet is being used. &nbsp;</p>

<p>If you have questions about this application of Distributed Spreadsheet, please drop a note to <a href="http://login.myblogsite.commailto:info@distributedspreadsheet.com">info@distributedspreadsheet.com</a>. </p> ]]></description>
			<guid isPermaLink="false">7@http://distributedspreadsheet.myblogsite.com/</guid>
			<category>default</category>
			<pubDate>Tue, 25 Mar 2008 14:53:00 -0400</pubDate>
		</item>
		
		
		
		<item>
			<title>Protecting Cells from Changing</title>
			<link>http://distributedspreadsheet.myblogsite.com/entry6.html</link>
			<comments>http://distributedspreadsheet.myblogsite.com/entry6.html#comm</comments>
                        <description><![CDATA[ <p>If I protect cells in my workbook, will using Distributed Spreadsheet bypass the protection?</p>

<p>No.&nbsp; Distributed Spreadsheet retains all of the capabilities of Microsoft Excel while enabling multi-user convenience. &nbsp;Features such as macros, cell protection, VBA scripts, Pivot tables and others work as expected. &nbsp;</p>

<p>If you have questions about this application of Distributed Spreadsheet, please drop a note to <a href="http://login.myblogsite.commailto:info@distributedspreadsheet.com">info@distributedspreadsheet.com</a>. </p> ]]></description>
			<guid isPermaLink="false">6@http://distributedspreadsheet.myblogsite.com/</guid>
			<category>default</category>
			<pubDate>Tue, 25 Mar 2008 14:29:00 -0400</pubDate>
		</item>
		
		
		
		<item>
			<title>I like the idea of pushing Excel worksheets out to a variety of users.  I want to send worksheets to my customers but I don’t want them to be forced to buy a license.  Is there a “reader” version for those who only receive worksheets?</title>
			<link>http://distributedspreadsheet.myblogsite.com/entry5.html</link>
			<comments>http://distributedspreadsheet.myblogsite.com/entry5.html#comm</comments>
                        <description><![CDATA[ <p>All Distributed Spreadsheets are transmitted in an encrypted format.&nbsp; The Distributed Spreadsheet software is the only software that knows how to unlock the files.&nbsp; For this reason, a copy of software must be installed to both send and receive worksheets.&nbsp; While some may argue that this inhibits the broad adoption of the product, the security benefits and ease of both sending and receiving worksheets make the small price an easy trade-off.&nbsp; </p>

<p>So what will $20 buy if not a license of Distributed Spreadsheet?</p>

<p>$20 is the price of 1 small meal in any major city in the US…..before the bar tab.&nbsp; Is it worth 1 meal?</p>
<p>$20 is the price of a small round of drinks in most bars during normal business hours.&nbsp; Is it worth 1 round?</p>
<p>$20 is the value of the 20 minutes of time for an average executive.&nbsp; Is it worth 20 minutes of your time?</p>

<p>Yes, we made a pricing decision a long time ago to require everyone to possess a valid license in order to be a participant.&nbsp; Today, we still feel the value is more than fair.</p>

<p>If you have questions about this application of Distributed Spreadsheet, please drop a note to <a href="http://login.myblogsite.commailto:info@distributedspreadsheet.com">info@distributedspreadsheet.com</a>. </p> ]]></description>
			<guid isPermaLink="false">5@http://distributedspreadsheet.myblogsite.com/</guid>
			<category>default</category>
			<pubDate>Tue, 18 Mar 2008 15:21:00 -0400</pubDate>
		</item>
		
		
		
		<item>
			<title>Goal:  Minimize costs for product training, product acquisition, data communications while meeting the need to collect consolidated information</title>
			<link>http://distributedspreadsheet.myblogsite.com/entry4.html</link>
			<comments>http://distributedspreadsheet.myblogsite.com/entry4.html#comm</comments>
                        <description><![CDATA[ <p>The challenge:&nbsp; provide route managers of a food products company with an easy-to-use tool for tracking sales out and “Stock needed” information.&nbsp; Cost was a concern.&nbsp; Using a familiar tool versus learning a new tool was desired.&nbsp; Real-time access could not be a required.&nbsp; Microsoft Excel was the obvious solution but how to get the information from the route mangers without introducing a large learning curve.</p>

<p>Distributed Spreadsheet met the requirements and a sample of the resulting workbook can be downloaded from the Community Forum section of the Distributed Spreadsheet web site.&nbsp; </p>

<p>Using a variety of Excel features, a worksheet was created that provided drop-down boxes for selecting products sold or needing to be ordered.&nbsp; Names of accounts were selected from drop downs menus.&nbsp; Costs of orders were quickly calculated in order for the store owner to be able to immediately approve the order.&nbsp; Extensive use of comments helps guide users as to what information needs to be collected.</p>

<p>Installing Distributed Spreadsheet allowed the route manager to collect the inventory and order information 1 store at a time and forward this information back to the home office at the end of each week with 2 simple mouse clicks.&nbsp; </p>

<p>Looking at the alternative methods of capturing the customer’s information, Distributed Spreadsheet was easily the lowest cost alternative while also bringing the lowest cost of implementation and lowest impact to the data communications budget.&nbsp; </p>

<p>If you have questions about this application of Distributed Spreadsheet, please drop a note to <a href="http://login.myblogsite.commailto:info@distributedspreadsheet.com">info@distributedspreadsheet.com</a>. </p> ]]></description>
			<guid isPermaLink="false">4@http://distributedspreadsheet.myblogsite.com/</guid>
			<category>default</category>
			<pubDate>Tue, 18 Mar 2008 15:03:00 -0400</pubDate>
		</item>
		
		
		
		<item>
			<title>Using Distributed Spreadsheet as a Push Tool</title>
			<link>http://distributedspreadsheet.myblogsite.com/entry3.html</link>
			<comments>http://distributedspreadsheet.myblogsite.com/entry3.html#comm</comments>
                        <description><![CDATA[ <p>&nbsp;A question that is frequently raised as I talk with prospective customers is the viability of Distributed Spreadsheet as strictly a “push” tool.&nbsp; The answer is absolutely.&nbsp; As there are a number of large accounting applications that are able to output reports in Excel format with breakpoints at worksheets rather than the traditional printed page, the opportunity is very clear.&nbsp; Installing a license of Distributed Spreadsheet on each machine where 1 of more of the worksheets will be destined allows for a secure way to send out individual pages of the report without having to cut out the individual pages.</p>

<p>Thus a large, international company could perhaps produce a quarterly financial report with a single worksheet for each agent’s territory with a summary page for each region and possibly other levels of roll-up.&nbsp; </p>

<p>The territory manager is assigned as a Contributor for their respective worksheet.&nbsp; The area manager is assigned as a Contributor for all the territory manager’s worksheets.&nbsp; The regional manager is assigned as a Contributor for all the summary pages assigned to each area manager in the region.&nbsp; This continues on up through the management hierarchy.&nbsp; </p>

<p>As there is no need for updates to be coming back via the worksheets, the v1.0 limit of 12 Contributors per worksheet is not applicable.&nbsp; The limit of 12 applies only to cases where merging of Contributions is needed.&nbsp; Thus Distributed Spreadsheet provides an easy and secure way to sending out individual worksheets containing the very data upon which financial models are built.&nbsp; Once received, the recipient is able to save the file and then proceed to do any modeling they desire.&nbsp; </p>

<p>If you have questions about this application of Distributed Spreadsheet, please drop a note to <a href="http://login.myblogsite.commailto:info@distributedspreadsheet.com">info@distributedspreadsheet.com</a>. </p> ]]></description>
			<guid isPermaLink="false">3@http://distributedspreadsheet.myblogsite.com/</guid>
			<category>default</category>
			<pubDate>Sun, 16 Mar 2008 14:38:00 -0400</pubDate>
		</item>
		
		
		
		<item>
			<title>Real-Estate Development Tool</title>
			<link>http://distributedspreadsheet.myblogsite.com/entry2.html</link>
			<comments>http://distributedspreadsheet.myblogsite.com/entry2.html#comm</comments>
                        <description><![CDATA[ <p>Imagine running a small business that oversees the acquisition and build-out of franchise locations.&nbsp; How would you track the status of each site as it progresses through the steps from basic site selection through lease negotiation to the management of build-outs.&nbsp; </p>

<p>That is what a property management company is Phoenix is doing.&nbsp; Using Distributed Spreadsheet, a team of 8 are overseeing the process of simultaneously bringing up multiple franchise sites for multiple franchise companies and tracking all of it through a large Excel Workbook.</p>

<p>The setup of the workbook started out as a listing of the major milestones for a single, generic site location and build project.&nbsp; As the team worked through the initial tracking process, the worksheet became worksheets and were changed to add greater levels of details through breaking the milestones into smaller and smaller distinct steps.&nbsp; Each individual site is now a separate worksheet in the workbook and each worksheet is assigned to a single site manager.&nbsp; Each Monday, the site managers receive an e-mail containing their worksheets as last submitted.&nbsp; Each site manager is responsible for returning the updated worksheets on Friday. This may mean updating between 3 and 8 worksheets each.&nbsp; Distributed Spreadsheet allows for the executives to view the status of all projects on the following Monday after the worksheets are merged back into the master.&nbsp; </p>

<p>Embedding target dates for specific milestones into the workbook allows for comparisons of target to actual.&nbsp; Actuals that exceed targets are automatically highlighted.&nbsp; Comments from site managers are included thus explanations regarding reasons for slipping dates can be included.</p>

<p>By sending out the worksheets for updating on a weekly basis, progress can be easily tracked as each week’s reports are separate submissions thus avoiding overwriting last week’s submission with this week’s submission.&nbsp; Tracking who has sent in their weekly reports is also easy to track through the Analysis Center.</p>

<p>Providing reports to the franchise corporate office has also been streamlined.&nbsp; By building a summary page that reflects the status of the individual franchise location sheets, monthly reports to the corporate office are facilitated by adding the corporate contact as a “Contributor” for a single distribution.&nbsp; On the first Monday of the month, the additional Contributor is added, the worksheets distributed and the additional Contributor is removed.&nbsp; The $20 for a software license at the franchise corporate office is very inexpensive relative to the time saved.&nbsp; </p>

<p>Thus, this usage model combines traditional distribution and contribution along with a one-way push of the summary page.&nbsp; </p>

<p>I have often been asked if a single workbook was the only option or could a workbook be created for each franchise.&nbsp; The answer is whatever works best.&nbsp; Depending upon the number of franchise operations, the number of site managers and overall organization structure, one model may be better suited than the other.&nbsp; Perhaps a mixture of the 2 models is ideal.&nbsp; The beauty of Excel is that changing the model is very easy to accomplish.</p>

<p>If you have questions about this application of Distributed Spreadsheet, please drop a note to <a href="http://login.myblogsite.commailto:info@distributedspreadsheet.com">info@distributedspreadsheet.com</a>.&nbsp; </p> ]]></description>
			<guid isPermaLink="false">2@http://distributedspreadsheet.myblogsite.com/</guid>
			<category>default</category>
			<pubDate>Sun, 16 Mar 2008 14:16:00 -0400</pubDate>
		</item>
		
		
		
		<item>
			<title>Welcome to the official Blog for users of Distributed Spreadsheet</title>
			<link>http://distributedspreadsheet.myblogsite.com/entry1.html</link>
			<comments>http://distributedspreadsheet.myblogsite.com/entry1.html#comm</comments>
                        <description><![CDATA[ <p>Welcome to the offical blog for any and all users of Distributed Spreadsheet.&nbsp; This blog is designed to allow users and developer's to share creative uses of Distributed Spreadsheet as well as allow users to pose usage-related questions.&nbsp; Please be sure to sign up for the RSS feed in order to stay current with the latest thinking and wild ideas.</p>
<p>Mark Ryan</p> ]]></description>
			<guid isPermaLink="false">1@http://distributedspreadsheet.myblogsite.com/</guid>
			<category>default</category>
			<pubDate>Mon, 10 Mar 2008 15:07:00 -0400</pubDate>
		</item>
		
		
		
	</channel>
</rss>
