<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Business And Process &#187; Business Services Industry</title>
	<atom:link href="http://www.businessandprocess.com/category/business-services-industry/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.businessandprocess.com</link>
	<description>A talk about business and productivity</description>
	<lastBuildDate>Fri, 11 Feb 2011 22:36:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
		<item>
		<title>A visit to Kinko&#8217;s</title>
		<link>http://www.businessandprocess.com/2006/02/a-visit-to-kinkos/</link>
		<comments>http://www.businessandprocess.com/2006/02/a-visit-to-kinkos/#comments</comments>
		<pubDate>Sun, 12 Feb 2006 23:11:00 +0000</pubDate>
		<dc:creator>Jose Emilio Leon</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Business Services Industry]]></category>
		<category><![CDATA[Process]]></category>

		<guid isPermaLink="false">/archive/2006/02/12/201.aspx</guid>
		<description><![CDATA[An interesting story and how an idea surged. A couple of days ago I had to go to Kinko&#8217;s for printing some pricing and marketing material for a customer I was going to visit the next day. I asked for normal color printing with a special paper, something that made it look good. This was [...]]]></description>
			<content:encoded><![CDATA[<p>An interesting story and how an idea surged. A couple of days ago I had to go to<br />
<a href="http://www.fedex.com/us/officeprint/main/?link=1">Kinko&#8217;s</a> for<br />
printing some pricing and marketing material for a customer I was going to visit<br />
the next day. I asked for normal color printing with a special paper, something<br />
that made it look good. This was in kind of a rush mode. I was on the trip and<br />
visiting the client was a pure coincidence. </p>
<p>When the person in the front desk took my order, he took out the huge form (it<br />
looks something like a poster for some movie or concert) and he fills it out<br />
with my order request. I couldn&#8217;t understand anything he was writing but I know<br />
there are a bunch of fields in the form. He entered the color preference, the<br />
paper type, the number of copies, my name, address and phone number. After<br />
finishing, he marks every field in the form with a green highlighter (I still<br />
don&#8217;t know why is this). Then he takes the form and puts it in sealed bag (like<br />
a huge Ziploc) and then calls somebody in the background to handle the new<br />
request. </p>
<p>First, nobody answered. He didn&#8217;t know who was free to work and who was working<br />
with something (and nobody was paying attention to him either). Then he needed<br />
to copy my PDF files to the machine where the printing was going to be done. He<br />
didn&#8217;t remember the files I just told him to print so I had to go back and point<br />
him the files I wanted. I noticed that with every printing work they have, they<br />
create a folder with the customer name. Inside the folder they create three more<br />
folders: Original, Process, and Final. Then he placed my files in the original<br />
folder. I think the folders mark the workflow that needs to be followed for<br />
printing. I suppose it goes something like this: they first open the files in<br />
the original folder, then edit them with some program for best printing (still<br />
haven&#8217;t figured out what they edit; documents always have this blank border and<br />
they say it&#8217;s impossible to take it out). Then they put the edited files in the<br />
final folder.</p>
<p>After copying and filling the request and everything was done, he told me the<br />
estimated time that everything will be ready and that&#8217;s it, ready. </p>
<p>When I got out I started thinking (in critique mode) the whole process. I said<br />
why they haven&#8217;t done something more automatic for handling these request and<br />
assignment. Maybe they would only need one person in the front taking the<br />
requests and something behind prepares the environment of work and assigns the<br />
right person in the back.</p>
<p>Using a workflow application would help them great automating the manual<br />
process. And how they can do that? I came with something simple for the problem.</p>
<p>First I though the best way to port the paper forms to an electronic form was<br />
InfoPath. In InfoPath you have the ability to create sections inside the form<br />
and digitally signed them preventing these sections to be tampered (we don&#8217;t<br />
need anymore the plastic Ziploc bag for protecting the form). One issue<br />
resolved.</p>
<p>In InfoPath you can define an attachment field that allows you to attach a file<br />
to the form. You can attach as many files as needed and they traveled inside the<br />
form always. Now you can take the files needed for the work and attach them to<br />
request. They are never loss and you just have to ask for them one time. Another<br />
issue solved.</p>
<p>The form is going to be electronic in first place. You can publish it to a<br />
<a href="http://www.skyxoft.com/sharepointworkflow">SharePoint</a> site for<br />
example and have a central repository form them, allowing searching and<br />
indexing. This is not an issue, but maybe would be a great add on.</p>
<p>And now for the workflow part. A simple process can be made for handling the<br />
request form. You would have the start activity with permissions for only the<br />
front desk person to start the process. Security. Then a second activity for<br />
handling the input request form. </p>
<p>As an improvement, we could create a web service that generates a unique number<br />
for the request. This can be the second activity in the process. The third<br />
activity would be to assign this number to a field in the form. Next?</p>
<p>The next thing we can do is actually create another web service that creates the<br />
folders they need for processing the files. We don&#8217;t need the first folder, the<br />
Original folder, because the original files are already attached to the form.<br />
The web service would only need to create the other two: Process and Final. A<br />
good improvement would be to create them directly in SharePoint and have a<br />
central repository for them.</p>
<p>The most important step would be the assignment of the request to one of the<br />
back office personnel that actually executes the job. I though the best way to<br />
do this was to use the workload feature. I could specify the personnel available<br />
for this and assign requests on a one by one basis or a least busy basis. Then<br />
let the software manage the work queue. Maybe every personnel in the back office<br />
can have like a Pocket PC and they can receive their tasks and immediately know<br />
their new assignments.</p>
<p>The final step would be to send an email to the front desk person notifying that<br />
the job was finished. An improvement here we could consider is asking the<br />
customer for his email and place it in the form. Then we can put another<br />
activity in the process for sending an email to the client saying that his job<br />
is finished (customer service improvement!!).</p>
<p>Now the whole process is automated. Errors in the process will be far less.<br />
Security in the form c<a href="http://www.businessandprocess.com/images/KKProcess.png"><img border="0" src="http://www.businessandprocess.com/images/KKProcess.png" width="307" height="187" align="right"></a>annot<br />
be compromised. And we guarantee that every back office personnel are receiving<br />
their tasks in a balanced way. The next phase for this would be to make another<br />
web service for saving the information in the form to a database table for<br />
future statistics and analysis.</p>
<p>A major thing? To simply enabled <a href="http://www.skyxoft.com/procx">Procx</a><br />
to receive the form requests via email and have the form publish to the<br />
Internet. I can fill the form myself from my house and I only have to leave to<br />
actually pickup the final work after I have received the notification. A simple<br />
step towards the<br />
<A href="http://businessandprocess.com/archive/2005/10/07/151.aspx">electronic<br />
enterprise</a>. An example of how the process will look like is on the right.<br />
 </p>


<!-- Begin SexyBookmarks Menu Code -->
<div class="sexy-bookmarks sexy-bookmarks-expand sexy-bookmarks-bg-love">
<ul class="socials">
		<li class="sexy-twitter">
			<a href="http://twitter.com/home?status=A+visit+to+Kinko%27s+-+http://bit.ly/9P0qLF+(via+@joseacta)&amp;source=shareaholic" rel="nofollow" title="Tweet This!"> </a>
		</li>
		<li class="sexy-mail">
			<a href="mailto:?subject=%22A%20visit%20to%20Kinko%27s%22&amp;body=I+thought+this+article+might+interest+you.%0A%0A%22An%20interesting%20story%20and%20how%20an%20idea%20surged.%20A%20couple%20of%20days%20ago%20I%20had%20to%20go%20to%0D%0AKinko%26%238217%3Bs%20for%20%0D%0Aprinting%20some%20pricing%20and%20marketing%20material%20for%20a%20customer%20I%20was%20going%20to%20visit%20%0D%0Athe%20next%20day.%20I%20asked%20for%20normal%20color%20printing%20with%20a%20special%20paper%2C%20something%20%0D%0Athat%20made%20it%20look%20good.%20This%20was%20%22%0A%0AYou+can+read+the+full+article+here%3A%20http://www.businessandprocess.com/2006/02/a-visit-to-kinkos/" rel="nofollow" title="Email this to a friend?"> </a>
		</li>
		<li class="sexy-printfriendly">
			<a href="http://www.printfriendly.com/print?url=http://www.businessandprocess.com/2006/02/a-visit-to-kinkos/" rel="nofollow" title="Send this page to Print Friendly"> </a>
		</li>
		<li class="sexy-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.businessandprocess.com/2006/02/a-visit-to-kinkos/&amp;t=A+visit+to+Kinko%27s" rel="nofollow" title="Share this on Facebook"> </a>
		</li>
		<li class="sexy-digg">
			<a href="http://digg.com/submit?phase=2&amp;url=http://www.businessandprocess.com/2006/02/a-visit-to-kinkos/&amp;title=A+visit+to+Kinko%27s" rel="nofollow" title="Digg this!"> </a>
		</li>
		<li class="sexy-delicious">
			<a href="http://delicious.com/post?url=http://www.businessandprocess.com/2006/02/a-visit-to-kinkos/&amp;title=A+visit+to+Kinko%27s" rel="nofollow" title="Share this on del.icio.us"> </a>
		</li>
		<li class="sexy-linkedin">
			<a href="http://www.linkedin.com/shareArticle?mini=true&amp;url=http://www.businessandprocess.com/2006/02/a-visit-to-kinkos/&amp;title=A+visit+to+Kinko%27s&amp;summary=An%20interesting%20story%20and%20how%20an%20idea%20surged.%20A%20couple%20of%20days%20ago%20I%20had%20to%20go%20to%0D%0AKinko%26%238217%3Bs%20for%20%0D%0Aprinting%20some%20pricing%20and%20marketing%20material%20for%20a%20customer%20I%20was%20going%20to%20visit%20%0D%0Athe%20next%20day.%20I%20asked%20for%20normal%20color%20printing%20with%20a%20special%20paper%2C%20something%20%0D%0Athat%20made%20it%20look%20good.%20This%20was%20&amp;source=Business And Process" rel="nofollow" title="Share this on LinkedIn"> </a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>
<!-- End SexyBookmarks Menu Code -->

]]></content:encoded>
			<wfw:commentRss>http://www.businessandprocess.com/2006/02/a-visit-to-kinkos/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

