<?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: o2, Carphone and the Flexible Workflow PhD researcher</title>
	<atom:link href="http://www.mobileindustryreview.com/2008/07/o2_carphone_and_the_flexible_workflow_phd_researcher.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.mobileindustryreview.com/2008/07/o2_carphone_and_the_flexible_workflow_phd_researcher.html</link>
	<description>Daily news and opinion for 250,000 industry executives and mobile fanatics</description>
	<lastBuildDate>Tue, 14 Feb 2012 08:39:00 +0100</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Richard</title>
		<link>http://www.mobileindustryreview.com/2008/07/o2_carphone_and_the_flexible_workflow_phd_researcher.html/comment-page-1#comment-242540</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Thu, 17 Jul 2008 14:35:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.com/?p=7173#comment-242540</guid>
		<description>From a techincal point of view the whole problem with o2 iphone launch appears to be about the number of concurrent sessions any of their systems can take. The website crashed because it couldn&#039;t handle the number of sessions. The upgrade processes failed because it had more points for the session to disappear than the new customers (extra step for the sms codes on the upgrade). The in-shop activation processs stopped working because of the demand. &lt;br&gt;&lt;br&gt;When the o2 shops opened on the high street they had queues outside, it was controlled there wasn&#039;t a bundle of people stuck in the doorway. Use the same idea for the website, if the demand was kept lower none of the sessions fail, everyone who starts the process can finish or timeout within a short period. To keep it first come first served anyone who visits the website during a period of high demand would be allowed to create an account or login if they have an existing account but not go any further. Then use a process like ticketmasters website to queue everyone. &lt;br&gt;&lt;br&gt;The shop activation problem is an odd one, the activation system has a known amount of possible concurrent users (no of shops * no of activation terminals), on the launch day there was only going to be that number of users. Then the only backup system they use is paper, its not suprising that it takes 5 days to enter all the data and activate everyone. A failover system that just gathers data and doesn&#039;t process could have been in place.</description>
		<content:encoded><![CDATA[<p>From a techincal point of view the whole problem with o2 iphone launch appears to be about the number of concurrent sessions any of their systems can take. The website crashed because it couldn&#39;t handle the number of sessions. The upgrade processes failed because it had more points for the session to disappear than the new customers (extra step for the sms codes on the upgrade). The in-shop activation processs stopped working because of the demand. </p>
<p>When the o2 shops opened on the high street they had queues outside, it was controlled there wasn&#39;t a bundle of people stuck in the doorway. Use the same idea for the website, if the demand was kept lower none of the sessions fail, everyone who starts the process can finish or timeout within a short period. To keep it first come first served anyone who visits the website during a period of high demand would be allowed to create an account or login if they have an existing account but not go any further. Then use a process like ticketmasters website to queue everyone. </p>
<p>The shop activation problem is an odd one, the activation system has a known amount of possible concurrent users (no of shops * no of activation terminals), on the launch day there was only going to be that number of users. Then the only backup system they use is paper, its not suprising that it takes 5 days to enter all the data and activate everyone. A failover system that just gathers data and doesn&#39;t process could have been in place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://www.mobileindustryreview.com/2008/07/o2_carphone_and_the_flexible_workflow_phd_researcher.html/comment-page-1#comment-233989</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Thu, 17 Jul 2008 09:35:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.com/?p=7173#comment-233989</guid>
		<description>From a techincal point of view the whole problem with o2 iphone launch appears to be about the number of concurrent sessions any of their systems can take. The website crashed because it couldn&#039;t handle the number of sessions. The upgrade processes failed because it had more points for the session to disappear than the new customers (extra step for the sms codes on the upgrade). The in-shop activation processs stopped working because of the demand. &lt;br&gt;&lt;br&gt;When the o2 shops opened on the high street they had queues outside, it was controlled there wasn&#039;t a bundle of people stuck in the doorway. Use the same idea for the website, if the demand was kept lower none of the sessions fail, everyone who starts the process can finish or timeout within a short period. To keep it first come first served anyone who visits the website during a period of high demand would be allowed to create an account or login if they have an existing account but not go any further. Then use a process like ticketmasters website to queue everyone. &lt;br&gt;&lt;br&gt;The shop activation problem is an odd one, the activation system has a known amount of possible concurrent users (no of shops * no of activation terminals), on the launch day there was only going to be that number of users. Then the only backup system they use is paper, its not suprising that it takes 5 days to enter all the data and activate everyone. A failover system that just gathers data and doesn&#039;t process could have been in place.</description>
		<content:encoded><![CDATA[<p>From a techincal point of view the whole problem with o2 iphone launch appears to be about the number of concurrent sessions any of their systems can take. The website crashed because it couldn&#39;t handle the number of sessions. The upgrade processes failed because it had more points for the session to disappear than the new customers (extra step for the sms codes on the upgrade). The in-shop activation processs stopped working because of the demand. </p>
<p>When the o2 shops opened on the high street they had queues outside, it was controlled there wasn&#39;t a bundle of people stuck in the doorway. Use the same idea for the website, if the demand was kept lower none of the sessions fail, everyone who starts the process can finish or timeout within a short period. To keep it first come first served anyone who visits the website during a period of high demand would be allowed to create an account or login if they have an existing account but not go any further. Then use a process like ticketmasters website to queue everyone. </p>
<p>The shop activation problem is an odd one, the activation system has a known amount of possible concurrent users (no of shops * no of activation terminals), on the launch day there was only going to be that number of users. Then the only backup system they use is paper, its not suprising that it takes 5 days to enter all the data and activate everyone. A failover system that just gathers data and doesn&#39;t process could have been in place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://www.mobileindustryreview.com/2008/07/o2_carphone_and_the_flexible_workflow_phd_researcher.html/comment-page-1#comment-227100</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Thu, 17 Jul 2008 08:35:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.com/?p=7173#comment-227100</guid>
		<description>From a techincal point of view the whole problem with o2 iphone launch appears to be about the number of concurrent sessions any of their systems can take. The website crashed because it couldn&#039;t handle the number of sessions. The upgrade processes failed because it had more points for the session to disappear than the new customers (extra step for the sms codes on the upgrade). The in-shop activation processs stopped working because of the demand. &lt;br&gt;&lt;br&gt;When the o2 shops opened on the high street they had queues outside, it was controlled there wasn&#039;t a bundle of people stuck in the doorway. Use the same idea for the website, if the demand was kept lower none of the sessions fail, everyone who starts the process can finish or timeout within a short period. To keep it first come first served anyone who visits the website during a period of high demand would be allowed to create an account or login if they have an existing account but not go any further. Then use a process like ticketmasters website to queue everyone. &lt;br&gt;&lt;br&gt;The shop activation problem is an odd one, the activation system has a known amount of possible concurrent users (no of shops * no of activation terminals), on the launch day there was only going to be that number of users. Then the only backup system they use is paper, its not suprising that it takes 5 days to enter all the data and activate everyone. A failover system that just gathers data and doesn&#039;t process could have been in place.</description>
		<content:encoded><![CDATA[<p>From a techincal point of view the whole problem with o2 iphone launch appears to be about the number of concurrent sessions any of their systems can take. The website crashed because it couldn&#39;t handle the number of sessions. The upgrade processes failed because it had more points for the session to disappear than the new customers (extra step for the sms codes on the upgrade). The in-shop activation processs stopped working because of the demand. </p>
<p>When the o2 shops opened on the high street they had queues outside, it was controlled there wasn&#39;t a bundle of people stuck in the doorway. Use the same idea for the website, if the demand was kept lower none of the sessions fail, everyone who starts the process can finish or timeout within a short period. To keep it first come first served anyone who visits the website during a period of high demand would be allowed to create an account or login if they have an existing account but not go any further. Then use a process like ticketmasters website to queue everyone. </p>
<p>The shop activation problem is an odd one, the activation system has a known amount of possible concurrent users (no of shops * no of activation terminals), on the launch day there was only going to be that number of users. Then the only backup system they use is paper, its not suprising that it takes 5 days to enter all the data and activate everyone. A failover system that just gathers data and doesn&#39;t process could have been in place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Whatley</title>
		<link>http://www.mobileindustryreview.com/2008/07/o2_carphone_and_the_flexible_workflow_phd_researcher.html/comment-page-1#comment-227099</link>
		<dc:creator>James Whatley</dc:creator>
		<pubDate>Wed, 16 Jul 2008 21:01:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.com/?p=7173#comment-227099</guid>
		<description>Excellent point on re: Step 2. &lt;br&gt;&lt;br&gt;I feel a blog post coming on myself...</description>
		<content:encoded><![CDATA[<p>Excellent point on re: Step 2. </p>
<p>I feel a blog post coming on myself&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Smith</title>
		<link>http://www.mobileindustryreview.com/2008/07/o2_carphone_and_the_flexible_workflow_phd_researcher.html/comment-page-1#comment-227098</link>
		<dc:creator>Ben Smith</dc:creator>
		<pubDate>Wed, 16 Jul 2008 17:17:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.com/?p=7173#comment-227098</guid>
		<description>Excellent write-up.  Welcome to the Ben-zone.</description>
		<content:encoded><![CDATA[<p>Excellent write-up.  Welcome to the Ben-zone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: juliancooling</title>
		<link>http://www.mobileindustryreview.com/2008/07/o2_carphone_and_the_flexible_workflow_phd_researcher.html/comment-page-1#comment-227097</link>
		<dc:creator>juliancooling</dc:creator>
		<pubDate>Wed, 16 Jul 2008 16:42:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.com/?p=7173#comment-227097</guid>
		<description>I agree entirely. However, do they think that they have a problem that even needs to be solved?&lt;br&gt;&lt;br&gt;Reading all the chats and websites etc, it is constantly pointed out that the iPhone is a small seller in a big market. While all of this is going on, O2 is still competently running a really, really big engineering and customer service operation. It is fun to think that powmobs, because they are high value customers (min </description>
		<content:encoded><![CDATA[<p>I agree entirely. However, do they think that they have a problem that even needs to be solved?</p>
<p>Reading all the chats and websites etc, it is constantly pointed out that the iPhone is a small seller in a big market. While all of this is going on, O2 is still competently running a really, really big engineering and customer service operation. It is fun to think that powmobs, because they are high value customers (min</p>
]]></content:encoded>
	</item>
</channel>
</rss>

