<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>IT Communications Blog</title>
	
	<link>http://blogs.perficient.com/communications</link>
	<description>A blog by Perficient providing insights and trends in the enterprise information technology industry for organizations involved in communications.</description>
	<lastBuildDate>Mon, 30 Aug 2010 18:26:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/ItCommunicationsBlog" /><feedburner:info uri="itcommunicationsblog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><creativeCommons:license>http://creativecommons.org/licenses/by-sa/2.0/</creativeCommons:license><image><link>http://creativecommons.org/licenses/by-sa/2.0/</link><url>http://creativecommons.org/images/public/somerights20.gif</url><title>Some Rights Reserved</title></image><item>
		<title>Learn about “mission critical” Siebel implementation at OpenWorld</title>
		<link>http://feedproxy.google.com/~r/ItCommunicationsBlog/~3/ZlboqWLLcVM/</link>
		<comments>http://blogs.perficient.com/communications/blog/2010/08/30/learn-about-mission-critical-siebel-implementation-at-openworld/#comments</comments>
		<pubDate>Mon, 30 Aug 2010 18:26:53 +0000</pubDate>
		<dc:creator>Erin</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[crm]]></category>
		<category><![CDATA[oow10]]></category>
		<category><![CDATA[oracle]]></category>
		<category><![CDATA[siebel]]></category>

		<guid isPermaLink="false">http://blogs.perficient.com/communications/?p=289</guid>
		<description><![CDATA[(This is a special guest post from Jeff Shaw, Director of Client Development here at Perficient, regarding our work with Oracle solutions for Communications clients as we prepare to attend Oracle OpenWorld 2010.) Self-service and personalized customer care is what propels industry leading organizations to success through strong relationships with their customers. Perficient developed a [...]]]></description>
			<content:encoded><![CDATA[<p><em>(This is a special guest post from <strong>Jeff Shaw</strong>, Director of Client Development here at Perficient, regarding our work with Oracle solutions for Communications clients as we prepare to attend Oracle OpenWorld 2010.)</em></p>
<p>Self-service and personalized customer care is what propels industry leading  organizations to success through strong relationships with their customers.  Perficient developed a global customer care system using <strong>Oracle Siebel</strong> to do  just that for <strong>a major unified communications equipment vendor</strong>. A leader in communications  systems, applications, and services incrementally rolled out a multi-phase  global implementation for its Global Services Support organization. In addition to deflecting a majority of incoming phone calls, it will enable thousands of  agents to more effectively serve end customers with a personal touch by  efficiently identifying the customer, the installed base, and the entitlement  information.</p>
<p>This  program is a “mission critical” to our client as it provides the foundation necessary  for the company to drastically reduce costs and increase efficiencies across  their support organization while improving their customers&#8217;  experiences.</p>
<p>Perficient  is responsible for the overall Siebel program inclusive of</p>
<ul>
<li>program management</li>
<li>enterprise architecture</li>
<li>business requirements</li>
<li>implementation</li>
<li>data migration</li>
<li>integration</li>
<li>offshoring</li>
</ul>
<p>Business capabilities include a “push” case model,  intelligent routing, CTI, and over a dozen real-time integration points into back  office systems. Visit with our Oracle team to learn more about this project and <strong>Perficient’s Communications Practice</strong> at Oracle OpenWorld 2010, September 19-23 in San Francisco.</p>
<p>We&#8217;ll be Booth <strong>301 Moscone South. <a href="http://www.perficient.com/openworld/">More info Here.</a><br />
</strong></p>
<p>Don&#8217;t forget to follow us on Twitter for regular updates throughout OpenWorld: <a href="http://twitter.com/prft_oracle" target="_blank">@PRFT_Oracle</a> and follow the conference hash tag on Twitter:<a href="http://twitter.com/#search?q=%23oow10" target="_blank"> #OOW10</a></p>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow: hidden;"><a title="View profile" href="http://twitter.com/dougbachelor">dougbachelor</a> RT <a href="http://twitter.com/PRFT_Oracle">@PRFT_Oracle</a>: Enterprise  Architecture vs. Service Oriented Architecture Part II <a href="http://dld.bz/sBgq">http://dld.bz/sBgq</a> <a href="http://search.twitter.com/search?q=%23soa">#soa</a></div>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=ZlboqWLLcVM:q7CZV9R_gfg:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=ZlboqWLLcVM:q7CZV9R_gfg:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=ZlboqWLLcVM:q7CZV9R_gfg:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=ZlboqWLLcVM:q7CZV9R_gfg:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=ZlboqWLLcVM:q7CZV9R_gfg:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=ZlboqWLLcVM:q7CZV9R_gfg:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=ZlboqWLLcVM:q7CZV9R_gfg:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=ZlboqWLLcVM:q7CZV9R_gfg:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=ZlboqWLLcVM:q7CZV9R_gfg:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=ZlboqWLLcVM:q7CZV9R_gfg:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ItCommunicationsBlog/~4/ZlboqWLLcVM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.perficient.com/communications/blog/2010/08/30/learn-about-mission-critical-siebel-implementation-at-openworld/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blogs.perficient.com/communications/blog/2010/08/30/learn-about-mission-critical-siebel-implementation-at-openworld/</feedburner:origLink></item>
		<item>
		<title>Telecommunications: Industry technology trends</title>
		<link>http://feedproxy.google.com/~r/ItCommunicationsBlog/~3/O6fUF5oqCbg/</link>
		<comments>http://blogs.perficient.com/communications/blog/2010/08/23/telecommunications-industry-technology-trends/#comments</comments>
		<pubDate>Mon, 23 Aug 2010 06:46:19 +0000</pubDate>
		<dc:creator>Erin</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[mobile]]></category>
		<category><![CDATA[order management]]></category>
		<category><![CDATA[telecommunications]]></category>

		<guid isPermaLink="false">http://blogs.perficient.com/communications/?p=282</guid>
		<description><![CDATA[The key market players in the telecommunications industry are reacting to industry demands by making their systems more effective, flexible and scalable. One of Oracle&#8217;s latest blog posts in the &#8220;Telecommunications Architecture Corner&#8221;, titled &#8220;Establish Order Management in Telecommunications&#8221; discusses these latest trends and describes how &#8220;the first critical business area to be addressed to [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://blogs.perficient.com/communications/files/2010/08/telecom.jpg"><img class="alignright size-medium wp-image-286" title="telecom" src="http://blogs.perficient.com/communications/files/2010/08/telecom-300x195.jpg" alt="" width="240" height="156" /></a>The key market players in the telecommunications industry are reacting to industry demands by making their systems more effective, flexible and scalable. One of Oracle&#8217;s latest blog posts in the &#8220;Telecommunications Architecture Corner&#8221;, titled &#8220;<a href="http://blogs.oracle.com/raulgoy/2010/07/establish_order_management_in.html" target="_blank">Establish Order Management in Telecommunications</a>&#8221; discusses these latest trends and describes how &#8220;the first critical business area to be addressed to achieve this goal is order management.&#8221; This is an excellent blog post for those working in IT within the communications industry.</p>
<p>Overall telecommunications industry trends:</p>
<ol>
<li>Increasing speed of delivery for data, voice, video and other data transfer</li>
<li>Rapid deregulation: &#8220;governments are revoking monopolistic policies and older players face a  new breed of competitors.&#8221;</li>
<li>&#8220;wireless  communication, Internet, cable and satellite program  distribution are  increasing their share in overall industry earnings&#8221;</li>
<li>Increasing focus on self-service</li>
<li>Focus on next-generation mobile platforms and services</li>
<li>Demand for pre-payment and real-time billing infrastructure</li>
</ol>
<p><span id="more-282"></span></p>
<p>How the corporate market differs from the consumer market:</p>
<ol>
<li>Ready to pay more for quality and reliability of servers</li>
<li>Less price sensitive in areas such as VPN, data security and video conferencing</li>
</ol>
<p>This article finishes up with an end-to-end perspective on order management, from order capture to provisioning all the way through to fulfillment.</p>
<p>It then reviews the challenges in order management and then how current telecom trends (listed above) are impacting how the major players are managing processes such as order management.</p>
<p>Read the full post <a href="http://blogs.oracle.com/raulgoy/2010/07/establish_order_management_in.html" target="_blank">here</a>.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=O6fUF5oqCbg:_ex1Ti5dIh4:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=O6fUF5oqCbg:_ex1Ti5dIh4:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=O6fUF5oqCbg:_ex1Ti5dIh4:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=O6fUF5oqCbg:_ex1Ti5dIh4:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=O6fUF5oqCbg:_ex1Ti5dIh4:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=O6fUF5oqCbg:_ex1Ti5dIh4:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=O6fUF5oqCbg:_ex1Ti5dIh4:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=O6fUF5oqCbg:_ex1Ti5dIh4:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=O6fUF5oqCbg:_ex1Ti5dIh4:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=O6fUF5oqCbg:_ex1Ti5dIh4:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ItCommunicationsBlog/~4/O6fUF5oqCbg" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.perficient.com/communications/blog/2010/08/23/telecommunications-industry-technology-trends/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blogs.perficient.com/communications/blog/2010/08/23/telecommunications-industry-technology-trends/</feedburner:origLink></item>
		<item>
		<title>Status – Red, Yellow, Green – Part 3 – More Than Just Timelines</title>
		<link>http://feedproxy.google.com/~r/ItCommunicationsBlog/~3/_u_EgRd2xIk/</link>
		<comments>http://blogs.perficient.com/communications/blog/2010/07/02/status-red-yellow-green-%e2%80%93-part-3-%e2%80%93-more-than-just-timelines/#comments</comments>
		<pubDate>Fri, 02 Jul 2010 18:47:57 +0000</pubDate>
		<dc:creator>Michael Schwarz</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://blogs.perficient.com/communications/?p=274</guid>
		<description><![CDATA[Although almost every project uses this paradigm, Red, Yellow, Green status is not very useful unless implemented in a certain way. The following suggestions are ways to improve the effectiveness of using this kind of status indicator. 1 – Define Red, Yellow, Green in terms of its most common perceived use (timeline). 2 – Expand [...]]]></description>
			<content:encoded><![CDATA[<p>Although almost every project uses this paradigm, Red, Yellow, Green status is not very useful unless implemented in a certain way. The following suggestions are ways to improve the effectiveness of using this kind of status indicator.<br />
1 – Define Red, Yellow, Green in terms of its most common perceived use (timeline).<br />
2 – Expand the color coded status paradigm to report on more than just tracking to plan.<br />
3 – Pull the emotion out of the color coding.<br />
We talked about item 1 in a previous post. We’ll use this post to discuss item 2, and leave item 3 for a following blog post.<br />
Most often, red, yellow, green is implied to indicate how an initiative is tracking to plan. That’s fine, but tracking to plan (or schedule adherence) is only one element of a healthful project, and is hardly the most important element.<br />
In IT project management (and often in other disciplines), there are 3 levers that can be pulled to change the dynamics of a project:<br />
1) Schedule<br />
2) Scope<br />
3) Quality<br />
You can compromise scope or quality to adhere to a schedule. And if scope and/or quality are more important than a date, than reporting status on dates only, is a poor indicator of project health. However, it’s almost always what red, yellow, green is implying.<br />
There is a better way… The creation of a dashboard that looks at a project in high level, color coded, simple concepts can convey far more information than a single status indicator. Expanding past the three categories listed above is recommended. For example, a weekly status report could report “Red”, “Yellow”, “Green” status on a series of project health indicators, such as:<br />
1) Schedule<br />
2) Scope<br />
3) Quality<br />
4) Budget<br />
5) Resources<br />
And then all of that get’s wrapped into an “Overall” status. In my previous post, I said that color coding only works if each status indicator has well defined and socialized metrics behind it. This applies to all status indicators. So for each of the 5 criteria, and in turn the overall indicator, there needs to be rules for why it is Red, Yellow, or Green.<br />
This discipline increases the effectiveness of the status reporting process because the report creator must think critically on what the status really means, and where the problems are at. It also encourages the recipients to acknowledge that projects can be complex organisms which require constant tuning to approach a successful outcome.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=_u_EgRd2xIk:pqnfLxW5vfc:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=_u_EgRd2xIk:pqnfLxW5vfc:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=_u_EgRd2xIk:pqnfLxW5vfc:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=_u_EgRd2xIk:pqnfLxW5vfc:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=_u_EgRd2xIk:pqnfLxW5vfc:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=_u_EgRd2xIk:pqnfLxW5vfc:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=_u_EgRd2xIk:pqnfLxW5vfc:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=_u_EgRd2xIk:pqnfLxW5vfc:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=_u_EgRd2xIk:pqnfLxW5vfc:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=_u_EgRd2xIk:pqnfLxW5vfc:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ItCommunicationsBlog/~4/_u_EgRd2xIk" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.perficient.com/communications/blog/2010/07/02/status-red-yellow-green-%e2%80%93-part-3-%e2%80%93-more-than-just-timelines/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blogs.perficient.com/communications/blog/2010/07/02/status-red-yellow-green-%e2%80%93-part-3-%e2%80%93-more-than-just-timelines/</feedburner:origLink></item>
		<item>
		<title>Status – Red, Yellow, Green Part 2 – Defining Metrics</title>
		<link>http://feedproxy.google.com/~r/ItCommunicationsBlog/~3/_7zaPyNm3h0/</link>
		<comments>http://blogs.perficient.com/communications/blog/2010/06/21/status-red-yellow-green-part-2-%e2%80%93-defining-metrics/#comments</comments>
		<pubDate>Mon, 21 Jun 2010 14:42:55 +0000</pubDate>
		<dc:creator>Michael Schwarz</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://blogs.perficient.com/communications/?p=269</guid>
		<description><![CDATA[It seems like every IT organization requires project managers, team leads, and program managers to produce status reports and dashboards displaying the successes and failures of current initiatives. Almost without exception, the focal point of the status report is the indicator colors of “Red”, “Yellow”, and “Green”. As stated in a previous blog posting, I [...]]]></description>
			<content:encoded><![CDATA[<p>It seems like every IT organization requires project managers, team leads, and program managers to produce status reports and dashboards displaying the successes and failures of current initiatives. Almost without exception, the focal point of the status report is the indicator colors of “Red”, “Yellow”, and “Green”.<br />
As stated in a previous blog posting, I often question the usefulness of this color coding strategy. However, forgoing the color indication entirely would leave most reviewers at a complete loss. So how do we make the Red, Yellow, Green status more effective? Here are three suggestions:<br />
1 – Define Red, Yellow, Green in terms of its most common perceived use (timeline).<br />
2 – Expand the color coded status paradigm to report on more than just tracking to plan.<br />
3 – Pull the emotion out of the color coding.</p>
<p>We’ll talk about this first concept in this blog. The remaining two points will be discussed in following postings.<br />
<span id="more-269"></span> The biggest problem with Red, Yellow, Green, is that it is usually not well defined. It’s often implied to be indicative of how an initiative is tracking to a socialized plan (or date). However, this point is usually not explicitly stated, and furthermore, what does Red, Yellow, or Green really say about how a project is tracking to plan. Without defining this, based on clear metrics, it should not mean much to anyone.<br />
When this is not defined, it usually leads the status creators and recipients to fall into very poor behavioral habits. We’ll discuss some of this later.<br />
However, let’s say we do define what the color coding means. Let’s say that the status color coding pertains to adherence to a stated schedule. Furthermore, let’s announce that Red means we are tracking 25% or more behind plan. Green means that we are tracking within 5% or less behind plan.<br />
Finally, and most importantly, yellow is used for two purposes. First, from the point a project is first baselined up to about 15% into the project timeline, the color coded status for timeline can be no better than yellow. It could be red, but it can’t be green. The reason for this is that early into the execution of a plan, especially one that lasts for long periods of time, it is impossible to tell if the plan is realistic until proper metric tracking is conducted. This cannot be done until there is enough timeline based data, which takes time to collect. Therefore, yellow should be used during this period of time.<br />
And of course the second purpose for using yellow is if the actual project is tracking in between 5% and 25% behind plan.<br />
Stating this up front in a clear and concise way will inhibit poor behavior from both the status report creator, and the report recipients. Basing color coded status on timeline is only useful if there are clear metrics used for defining the methodology behind the color coding.<br />
Doing it this way takes the emotion out of the equation. Reporting using color coded status without metrics is usually done through the emotions of the project manager or the team at whole. In fact, without metrics, emotion is the only way to do it. Furthermore, if the color coding is scrutinized from the recipients of the report, there is often a tendency to report things as green through the majority of the project, then yellow for the last 25% of the timeline, and then red a few days prior to a delivery. How many times have we all seen that? This is one thing I mean by poor behavior.<br />
On the flip side, not stating what the color coding means to the recipients of the report causes them to very often misconstrue what is being conveyed. When it goes yellow, they often freak because they have been provided no context to what yellow means when all it should mean is that the stated date, based on a plan is not guaranteed. Since very little in life is guaranteed, this should not be that big of a deal.<br />
However, since most projects start out as green and stay that way far longer than they should (lack of metrics), when the status changes to yellow towards the end of a project, it simply tells the report reviewers that all is not well. Stating the metrics/conditions for why the color is the way it is will help prevent this reaction from status report reviewers. Starting off as yellow helps enforce what a baselined plan really is; an estimated, not guaranteed, plan of record.<br />
In my next post, we’ll discuss the importance on reporting status on other areas of a projects health. Because it’s not all about timeline!</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=_7zaPyNm3h0:uG0ILCNsmVg:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=_7zaPyNm3h0:uG0ILCNsmVg:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=_7zaPyNm3h0:uG0ILCNsmVg:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=_7zaPyNm3h0:uG0ILCNsmVg:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=_7zaPyNm3h0:uG0ILCNsmVg:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=_7zaPyNm3h0:uG0ILCNsmVg:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=_7zaPyNm3h0:uG0ILCNsmVg:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=_7zaPyNm3h0:uG0ILCNsmVg:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=_7zaPyNm3h0:uG0ILCNsmVg:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=_7zaPyNm3h0:uG0ILCNsmVg:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ItCommunicationsBlog/~4/_7zaPyNm3h0" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.perficient.com/communications/blog/2010/06/21/status-red-yellow-green-part-2-%e2%80%93-defining-metrics/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blogs.perficient.com/communications/blog/2010/06/21/status-red-yellow-green-part-2-%e2%80%93-defining-metrics/</feedburner:origLink></item>
		<item>
		<title>I am on 4G now… Really?</title>
		<link>http://feedproxy.google.com/~r/ItCommunicationsBlog/~3/VrSpZLmOIHc/</link>
		<comments>http://blogs.perficient.com/communications/blog/2010/06/13/i-am-on-4g-now%e2%80%a6-really/#comments</comments>
		<pubDate>Mon, 14 Jun 2010 03:47:28 +0000</pubDate>
		<dc:creator>Srividya Ramachandran</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[3G]]></category>
		<category><![CDATA[4G]]></category>
		<category><![CDATA[iPhone]]></category>
		<category><![CDATA[LTE]]></category>
		<category><![CDATA[WiMax]]></category>
		<category><![CDATA[wireless services]]></category>

		<guid isPermaLink="false">http://blogs.perficient.com/communications/?p=266</guid>
		<description><![CDATA[This post came about from a conversation I had with a friend. She said – “I am going to be on 4G soon.” Knowing her to be a crazy iPhone user, I was surprised that she had decided to switch to Android and furthermore, to Sprint. Then she added, “I am preordering an iPhone 4”. [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: justify">This post came about from a conversation I had with a friend. She said – “I am going to be on 4G soon.” Knowing her to be a crazy iPhone user, I was surprised that she had decided to switch to Android and furthermore, to Sprint. Then she added, “I am preordering an iPhone 4”. That is when I realized how marketing campaigns can be so tricky that they could potentially fool even savvy people into believing what is not. Then we continued the conversation.</p>
<p style="text-align: justify">Me: First of all, iPhone 4 may be the fourth version of the iPhone itself, but since the iPhone is not launching on the Sprint network, we know for sure that it cannot be 4G, because AT&amp;T has no 4G service in the US.</p>
<p style="text-align: justify"><span id="more-266"></span></p>
<p style="text-align: justify">She: What do you mean? But it’s the iPhone 4G, right?</p>
<p style="text-align: justify">Me: Again, they call it the iPhone 4, not the iPhone 4G. Note the difference? The iPhone 4 works pretty much like the iPhone 3G/iPhone 3GS, except this time, it has some additional cool features. Those features are hooked to the device itself and having these added on your phone will still not affect what lies underneath it – i.e. AT&amp;T’s network is still the same.</p>
<p style="text-align: justify">She: Jeez, they had me there for a bit, believing that I am going to be getting 4G service soon. So if I am not getting 4G service with AT&amp;T, how can Apple be so sure that the iPhone 4 will be faster and provide me with the better speeds? What exactly are they selling to me then, if we strip the phone of all the “coolness”?</p>
<p style="text-align: justify">Me: They are tweaking what’s inside the phone so that they can promise the consumer all that speed. One would want to compare this to a highway situation. Suppose Apple was selling you a car with all the cool stuff in it. The fact still remains that even though you are in a cool car, you may still need to share the 405 with all the other people ,with or without the cool cars. Your car&#8217;s coolness however still deserves praise, because on an empty highway, clearly, your cool car would outperform its non-cool counterparts.</p>
<p style="text-align: justify">(That lit a bulb in her head and she began questioning me more)</p>
<p style="text-align: justify">She: Oh, I get it now. It would not really help having the cool car on 405 unless they build a new 405+ for just the cool cars. That would then enable the real experience, right?</p>
<p style="text-align: justify">Me: Exactly! There you go. Only Sprint currently has the 4G WiMax network operational and the HTC’s EVO phone is the first 4G phone. Even though Sprint actually claims that its WiMax service is 4G, the International Telecommunications Union still classifies WiMax under 3G. AT&amp;T, T-Mobile and Verizon have decided to adopt the LTE (Long Term Evolution) standard developed by the 3GPP consortium. The new spectrum that Verizon and AT&amp;T acquired in the 700 MHz frequency band in 2008 is being used for testing LTE and LTE is still around 2 years away from being deployed. Even though LTE and WiMax can be called sister technologies, there are still some noticeable architectural differences between them. We would need to sit down and talk about them in detail next time.</p>
<p style="text-align: justify">She: Great, so are you buying the iPhone 4 then even though it is not really 4G?</p>
<p style="text-align: justify">Me: You bet!</p>
<p style="text-align: justify">To most of us techies, these nuances in definition and naming are obvious already, but cleverly designed marketing campaigns hide the technical details under strings of jargon making the package look more complicated than it needs to be. In my mind, the step up from 2G to 3G was definitely more significant than the move from 3G to 4G. I would love to hear what the reader thinks.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=VrSpZLmOIHc:xLLgAOLzDJ0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=VrSpZLmOIHc:xLLgAOLzDJ0:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=VrSpZLmOIHc:xLLgAOLzDJ0:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=VrSpZLmOIHc:xLLgAOLzDJ0:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=VrSpZLmOIHc:xLLgAOLzDJ0:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=VrSpZLmOIHc:xLLgAOLzDJ0:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=VrSpZLmOIHc:xLLgAOLzDJ0:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=VrSpZLmOIHc:xLLgAOLzDJ0:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=VrSpZLmOIHc:xLLgAOLzDJ0:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=VrSpZLmOIHc:xLLgAOLzDJ0:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ItCommunicationsBlog/~4/VrSpZLmOIHc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.perficient.com/communications/blog/2010/06/13/i-am-on-4g-now%e2%80%a6-really/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://blogs.perficient.com/communications/blog/2010/06/13/i-am-on-4g-now%e2%80%a6-really/</feedburner:origLink></item>
		<item>
		<title>Addressing mobile communications management challenges</title>
		<link>http://feedproxy.google.com/~r/ItCommunicationsBlog/~3/QTblzZ5gIJM/</link>
		<comments>http://blogs.perficient.com/communications/blog/2010/05/14/addressing-mobile-communications-management-challenges/#comments</comments>
		<pubDate>Fri, 14 May 2010 15:54:57 +0000</pubDate>
		<dc:creator>Erin</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[communications]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[mobile]]></category>
		<category><![CDATA[mobility]]></category>

		<guid isPermaLink="false">http://blogs.perficient.com/communications/?p=262</guid>
		<description><![CDATA[As an IT manager for an organization, can you imagine having to support 15,000 wireless users in 400 locations for your company? Can you imagine that it might get a little tough to provide an adequate level of support to all 15,000 users? Think about how quickly technology &#8212; platforms, screen resolutions, apps, memory size, [...]]]></description>
			<content:encoded><![CDATA[<p>As an IT manager for an organization, can you imagine having to support 15,000 wireless users in 400 locations for your company? Can you imagine that it might get a little tough to provide an adequate level of support to all 15,000 users? Think about how quickly technology &#8212; platforms, screen resolutions, apps, memory size, etc. &#8211; is evolving and changing.  And the more quickly these evolve, the higher the expectations of the end user and the greater the level of frustration they experience if the technology cannot adapt to their business needs quickly enough.</p>
<p>ComputerWorld conducted a study of the situation that I found pretty fascinating.</p>
<blockquote><p>Given the wireless mega-trend and associated growing pains, it&#8217;s fair to  ask how midsize and large IT shops are managing wireless and what  they&#8217;re doing to prepare for the evolution of wireless over the coming  decade. For example, are companies creating a new position of chief  mobility officer, or appointing someone with a title similar to Wright&#8217;s  to oversee all the moving parts? Are IT shops integrating wireless into  their technology processes and systems?</p></blockquote>
<p>You can read more about it in this article, &#8220;<a href="http://www.cio.com/article/593568/For_IT_Enterprise_Wireless_to_Be_More_Gnarly_in_Next_Decade?source=rss_all" target="_blank">For IT, Enterprise Wireless to Be More Gnarly in  Next Decade</a>&#8221;</p>
<p>Where do you and your organization  stand with this issue?</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=QTblzZ5gIJM:ryqz3V47p0o:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=QTblzZ5gIJM:ryqz3V47p0o:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=QTblzZ5gIJM:ryqz3V47p0o:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=QTblzZ5gIJM:ryqz3V47p0o:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=QTblzZ5gIJM:ryqz3V47p0o:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=QTblzZ5gIJM:ryqz3V47p0o:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=QTblzZ5gIJM:ryqz3V47p0o:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=QTblzZ5gIJM:ryqz3V47p0o:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=QTblzZ5gIJM:ryqz3V47p0o:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=QTblzZ5gIJM:ryqz3V47p0o:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ItCommunicationsBlog/~4/QTblzZ5gIJM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.perficient.com/communications/blog/2010/05/14/addressing-mobile-communications-management-challenges/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blogs.perficient.com/communications/blog/2010/05/14/addressing-mobile-communications-management-challenges/</feedburner:origLink></item>
		<item>
		<title>Causes and Prevention of Bill Shock</title>
		<link>http://feedproxy.google.com/~r/ItCommunicationsBlog/~3/k09Vqcz6-SU/</link>
		<comments>http://blogs.perficient.com/communications/blog/2010/05/12/causes-and-prevention-of-bill-shock/#comments</comments>
		<pubDate>Wed, 12 May 2010 16:44:09 +0000</pubDate>
		<dc:creator>Srividya Ramachandran</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[consumer protection]]></category>
		<category><![CDATA[FCC]]></category>
		<category><![CDATA[telecom bills]]></category>

		<guid isPermaLink="false">http://blogs.perficient.com/communications/?p=256</guid>
		<description><![CDATA[No, Bill Shock has nothing to do with the shocking stuff Bill did.  It is what the telecommunications companies do to us in the United States when they send a bill that spooks the daylights out of you and me.  Since it is more common to see a black swan or a live dodo than [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: justify">No, Bill Shock has nothing to do with the shocking stuff Bill did.  It is what the telecommunications companies do to us in the United States when they send a bill that spooks the daylights out of you and me.  Since it is more common to see a black swan or a live dodo than to receive a bill charging the customer less than what he or she rightfully owes, it is prudent to assume that bill shock refers to the case when the customer gets charged exorbitantly more than what he believes he owes the telco for the service provided. And almost never is such a shock good!</p>
<p style="text-align: justify">One such popular case of bill shock that has been in the media since 2006 now is the St. Germain case.The St. Germain family of Dover, Mass., received their monthly Verizon bill amounting to more than $12000 in 2006 – Now, <em>that</em> definitely qualifies for bill shock. Bob St. Germain had renewed his family’s 2 year contract with Verizon. What the “agent” missed telling Bob was that the promotional period for free data download had ended for his service and that he was going to be charged per kilobyte for using data on his phone plan. Unaware of and uninformed about this change, Bob’s son had been connecting his laptop to the internet via the cell phone’s internet service, because it was faster than their dial up. However, he was cautiously only using it in the evenings and weekends assuming that his minutes were free then. But, Verizon’s bill meter was ticking away for very kilobyte Bryan was sending or receiving and when the bill for $12,233 came home, the entire family got afflicted with bill shock! When Bob called Verizon to find out what was going on, they told him that he owed them additional $5600 because of the last few days&#8217; unbilled activity. After years’ of haggling over his phone bill, having his credit score affected by this huge amount, being constantly harassed by the not-so-nice collections agencies, and after Bob sued Verizon, Verizon cut the bill in half. However the $9000 that he still owed can still account for bill shock.</p>
<p style="text-align: justify"><span id="more-256"></span>The St. Germain case became popular in the media after Bob sued Verizon, but that does not rule out the presence of many other similar cases around the country, when consumers do not have the resources or chance to sue the telcos for causing them bill shock. A comparison between telecom services in Europe and the US reveals that American telecom services are among the highest priced services in the entire developed world. Moreover, European customers have tighter consumer protection laws that can help prevent bill shock. Every time the minutes are 80% (or any user-defined threshold) close to being consumed completely or if roaming charges appear abnormally high or if there is unusual activity in the usage of minutes or data, European telecom service providers are legally obliged to send the consumer free text message alerts pointing to the unusual activity and the impact that this activity could cause on the bill. American consumers are familiar with this service from a banking perspective. Banks send out activity alerts to people and that prevents shock to the consumer at a later date, when they see their monthly bank statement.</p>
<p style="text-align: justify">On May 11, 2010, FCC&#8217;s Consumer and Governmental Affairs Bureau (CGB) has issued a <a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-803A1.pdf">public notice</a> to identify the feasibility of setting up such alert systems for telecom services in the US.</p>
<p style="padding-left: 30px;text-align: justify">“In this public notice we seek to gather information on the feasibility of instituting usage alerts and cut-off mechanisms similar to those required under the EU regulations that would provide wireless voice, text, and data consumers in the United States a way to monitor, on a real-time basis, their usage of a wireless communications service, as well as the various charges they may incur in connection with such usage (e.g., roaming services, voice service “minute plans,” text message plans). Specifically, we seek comment on whether technological or other differences exist that would prevent wireless providers in this country from employing similar usage controls as those now required by the EU.“</p>
<p style="text-align: justify">This filing is open to public comments for 45 days. While the majority of the comments so far have been supportive of this latest FCC initiative, there was <a href="http://fjallfoss.fcc.gov/ecfs/document/view?id=7020455164">one comment</a> that I found with a different, yet particularly funny note to it –</p>
<p style="padding-left: 30px;text-align: justify">If %^$#@ can&#8217;t read and keep track of their own bills, they deserve to get hit with bill shock. Think of it as a tax on &amp;^%$#*)^%.</p>
<p style="text-align: justify">Please check back <a href="http://fjallfoss.fcc.gov/ecfs/comment_search/execute?proceeding=09-158">here</a> later for more consumer comments.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=k09Vqcz6-SU:sLlvXCt5-kI:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=k09Vqcz6-SU:sLlvXCt5-kI:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=k09Vqcz6-SU:sLlvXCt5-kI:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=k09Vqcz6-SU:sLlvXCt5-kI:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=k09Vqcz6-SU:sLlvXCt5-kI:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=k09Vqcz6-SU:sLlvXCt5-kI:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=k09Vqcz6-SU:sLlvXCt5-kI:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=k09Vqcz6-SU:sLlvXCt5-kI:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=k09Vqcz6-SU:sLlvXCt5-kI:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=k09Vqcz6-SU:sLlvXCt5-kI:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ItCommunicationsBlog/~4/k09Vqcz6-SU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.perficient.com/communications/blog/2010/05/12/causes-and-prevention-of-bill-shock/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blogs.perficient.com/communications/blog/2010/05/12/causes-and-prevention-of-bill-shock/</feedburner:origLink></item>
		<item>
		<title>Back to MDM</title>
		<link>http://feedproxy.google.com/~r/ItCommunicationsBlog/~3/T8LV3T8Vqro/</link>
		<comments>http://blogs.perficient.com/communications/blog/2010/05/11/back-to-mdm/#comments</comments>
		<pubDate>Tue, 11 May 2010 21:37:47 +0000</pubDate>
		<dc:creator>Shivam Khullar</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[change management]]></category>
		<category><![CDATA[data steward]]></category>
		<category><![CDATA[mdm]]></category>

		<guid isPermaLink="false">http://blogs.perficient.com/communications/?p=249</guid>
		<description><![CDATA[I almost vanished from this space. Blame it on an upcoming wedding, where I happen to be the bride. But the show never stops. And thus we are back to talking about Master Data Management. I just finished a series of discussions with the business community of a test equipment manufacturer, where we strongly suggested [...]]]></description>
			<content:encoded><![CDATA[<p>I almost vanished from this space. Blame it on an upcoming wedding, where I happen to be the bride. But the show never stops. And thus we are back to talking about Master Data Management.</p>
<p>I just finished a series of discussions with the business community of a test equipment manufacturer, where we strongly suggested some immediate measures be implemented, to maintain data integrity and sanctity. When I started this project, my initial impression was this could be a hard sell &#8211; people often resist change. And I was quite right. It was a very very hard sell.</p>
<p>So I recommended that we take small steps. Keep all the interests, from across the organization aligned. And march forward with the belief that once we can prove the return on investment &#8211; in this case for time and money, rest will follow. So we have structured our plan in phases with simple, short and achievable goals. To initiate the process, we talked with the Business and IT stakeholders and documented some processes that will be followed to achieve these short-term goals.</p>
<p>The current phase of this initiative is primarily focused on educating users about data archiving practices and leveraging life cycle states for customers and products, to segment data. These are two short and simple objectives that are mostly system driven. Further we are putting together some training for the users on how to start leveraging these tools in their day-to-day jobs.</p>
<p>This is just a beginning. Ideally every organization must have a Data Steward who can assist with these activities. Perficient can then work with these Stewards, and assess where they need to focus their resources.</p>
<p>Stay tuned for more on this topic.</p>
<p>To read my last article on this topic &#8211; click here, <a title="MDM Overview" href="http://blogs.perficient.com/communications/blog/2010/04/01/master-data-management/" target="_blank">http://blogs.perficient.com/communications/blog/2010/04/01/master-data-management/</a></p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=T8LV3T8Vqro:SRQNBGZ5UoA:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=T8LV3T8Vqro:SRQNBGZ5UoA:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=T8LV3T8Vqro:SRQNBGZ5UoA:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=T8LV3T8Vqro:SRQNBGZ5UoA:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=T8LV3T8Vqro:SRQNBGZ5UoA:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=T8LV3T8Vqro:SRQNBGZ5UoA:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=T8LV3T8Vqro:SRQNBGZ5UoA:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=T8LV3T8Vqro:SRQNBGZ5UoA:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=T8LV3T8Vqro:SRQNBGZ5UoA:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=T8LV3T8Vqro:SRQNBGZ5UoA:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ItCommunicationsBlog/~4/T8LV3T8Vqro" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.perficient.com/communications/blog/2010/05/11/back-to-mdm/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blogs.perficient.com/communications/blog/2010/05/11/back-to-mdm/</feedburner:origLink></item>
		<item>
		<title>Status:  Red, Yellow, Green Leaves Much to be Desired</title>
		<link>http://feedproxy.google.com/~r/ItCommunicationsBlog/~3/vWY32ZOLLtk/</link>
		<comments>http://blogs.perficient.com/communications/blog/2010/05/03/status-red-yellow-green-leaves-much-to-be-desired/#comments</comments>
		<pubDate>Mon, 03 May 2010 21:15:10 +0000</pubDate>
		<dc:creator>Michael Schwarz</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://blogs.perficient.com/communications/blog/2010/05/03/status-red-yellow-green-leaves-much-to-be-desired/</guid>
		<description><![CDATA[It seems like every IT organization requires project managers, team leads, and program managers to produce status reports and dashboards displaying the successes and failures of current initiatives. Almost without exception, the focal point of the status report is the indicator colors of “Red”, “Yellow”, “Green”. I often question the usefulness of using such an [...]]]></description>
			<content:encoded><![CDATA[<p>It seems like every IT organization requires project managers, team leads, and program managers to produce status reports and dashboards displaying the successes and failures of current initiatives. Almost without exception, the focal point of the status report is the indicator colors of “Red”, “Yellow”, “Green”. I often question the usefulness of using such an arbitrary paradigm. First, it does not mean very much to the people that review these status reports, although these people may not realize this. Second, it’s often more of an indicator of the general mood of the people contributing to the project or writing the status report, than objective metrics and data that could then be translated to red, yellow, or green. So let’s first talk about what Red, Yellow, Green is supposed to mean. Green usually means that the project is progressing as planned and that the dates socialized are realistic and almost guaranteed. Yellow means that there are risks to the schedule and there is hopefully a mitigation plan in place to alleviate these issues, but the schedule is at risk or the scope is reduced. Red means that the project is not going to meet its objectives, and it usually refers to the socialized dates that the team is driving to. The problem with all of this is that the sizing up of status based on this type of system alone is very subjective, and usually follows a very familiar pattern. The project starts as green for a timeframe that starts right after the initial plan is baselined to about 25% into the project plan. The project then turns yellow because obstacles have been identified that jeopardize the plan (in terms of dates), and towards the end, most projects go red (from a timeline perspective), and need to be re-baselined. Once the project is re-baselined, it goes back to green or yellow status and the process repeats. The reality is that the color coding is not helpful in assessing the health of a project or the plan that underlies it. All projects should start out as yellow, because planning is no guarantee of success, and timelines are only one metric that should be considered when communicating the health of a project. There is also scope, quality, budget, morale, business value, ROI, etc. Usually none of this is represented in the color coding. So what else could be done to communicate status more effectively? The answer is metrics and tools that allow managers to assess health based on these metrics. I’ll post some comments on this approach in a future blog.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=vWY32ZOLLtk:MZ3FwvcobKw:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=vWY32ZOLLtk:MZ3FwvcobKw:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=vWY32ZOLLtk:MZ3FwvcobKw:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=vWY32ZOLLtk:MZ3FwvcobKw:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=vWY32ZOLLtk:MZ3FwvcobKw:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=vWY32ZOLLtk:MZ3FwvcobKw:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=vWY32ZOLLtk:MZ3FwvcobKw:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=vWY32ZOLLtk:MZ3FwvcobKw:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=vWY32ZOLLtk:MZ3FwvcobKw:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=vWY32ZOLLtk:MZ3FwvcobKw:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ItCommunicationsBlog/~4/vWY32ZOLLtk" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.perficient.com/communications/blog/2010/05/03/status-red-yellow-green-leaves-much-to-be-desired/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://blogs.perficient.com/communications/blog/2010/05/03/status-red-yellow-green-leaves-much-to-be-desired/</feedburner:origLink></item>
		<item>
		<title>Deconstructing the Comcast v. FCC case</title>
		<link>http://feedproxy.google.com/~r/ItCommunicationsBlog/~3/tM6oSbvcXvE/</link>
		<comments>http://blogs.perficient.com/communications/blog/2010/04/12/deconstructing-the-comcast-v-fcc-case/#comments</comments>
		<pubDate>Tue, 13 Apr 2010 00:35:25 +0000</pubDate>
		<dc:creator>Srividya Ramachandran</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[FCC]]></category>
		<category><![CDATA[network neutrality]]></category>
		<category><![CDATA[recent court case]]></category>

		<guid isPermaLink="false">http://blogs.perficient.com/communications/?p=242</guid>
		<description><![CDATA[The D.C. Circuit court’s decision [1] on whether FCC possesses the authority to regulate Comcast’s network management practices has spurred a lot of murmur among regulatory analysts across the US. Some proponents of network neutrality vehemently dislike this outcome, while others think it could be beneficial to curb FCC&#8217;s authority. The full text of this [...]]]></description>
			<content:encoded><![CDATA[<p>The D.C. Circuit court’s decision [1] on whether FCC possesses the authority to regulate Comcast’s network management practices has spurred a lot of murmur among regulatory analysts across the US. Some proponents of network neutrality vehemently dislike this outcome, while others think it could be beneficial to curb FCC&#8217;s authority. The full text of this ruling can be found <a href="http://www.scribd.com/doc/29489974/Full-Text-Comcast-vs-FCC-Federal-Court-Ruling">HERE</a>. In this post, let us deconstruct this court decision and recall the historical background that led to this ruling.</p>
<p><span id="more-242"></span><span style="text-decoration: underline"><strong>Issue and Historical Background –</strong></span> In 2007, Comcast customers began to notice that their peer-to-peer (P2P) file-sharing BitTorrent application seemed to have slowed down a lot or completely stopped working without prior notice and Comcast appeared to have been exercising certain questionable methods to interfere with customers’ use of these peer-to-peer networking applications. Following this finding, advocacy groups filed complaints to the FCC about Comcast’s debatable network management practices. The issue was that Comcast was violating the FCC’s internet policy statement which asserted that consumers are entitled to access all lawful content of their choice over the internet and that internet service providers should strive to achieve that goal [2]. In 2008, the FCC issued an Order stating that Comcast should explore alternate options of network management instead of blocking peer-to-peer communications and ordered Comcast to make detailed disclosures describing the alternate approaches and how the company plans to implement it. Even though Comcast had started to look at alternate network management practices and was in the process of exploring other options as ordered by FCC, it petitioned for review under the objection that (a) the FCC has no jurisdiction over network management practices of an internet service provider like Comcast (b) There was procedural flaws in passing this Order, because the FCC deviated from the normal lawmaking procedure as delineated in the Administrative Procedures Act (c) Parts of the Order were arbitrary and capricious.</p>
<p><span style="text-decoration: underline"><strong>Outcome of hearing –</strong></span> The petition for review was decided by the United States Court of Appeals, for the District of Columbia Circuit on April 6, 2010. The hearing completely circled around whether FCC has justifiable jurisdiction over this matter or not. And the decision of the court was that FCC does not have the authority to regulate the network management practices of Comcast’s internet service.</p>
<p><span style="text-decoration: underline"><strong>Ancillary Jurisdiction – </strong></span>Through the Communications Act of 1934 (amended over the decades), the Congress has vested the FCC with the broad authority to regulate common carrier services under Title II, broadcast, radio and cellular telephony under Title III, and cable services under Title VI.  In addition to the authority from the Act, past court rulings [4] have vested FCC with what is called “ancillary jurisdiction” using which the FCC can make rules and regulations, pass Orders, etc as long as the overall goal aligns with the wider policy goals espoused in the Communications Act. Also, through these past court rulings, FCC has allowed for deregulation of the “internet and information” space, claiming that this deregulation would lead to innovation and more consumer choice [5].</p>
<p>In this particular case, the FCC does not claim that it has the authority to regulate Comcast’s internet service under neither Title II, as a “telecommunications service” nor using Title VI as a “cable service” [6]. Instead it uses its “ancillary jurisdiction” to subject Comcast to the Order.</p>
<p><span style="text-decoration: underline"><strong>Comcast’s defense –</strong></span> Comcast defends its need to block and slow down P2P applications as an important step in ensuring that a particular set of customers do not hog scarce bandwidth at the expense of other Comcast customers’ bandwidth availabilities. Although Comcast has been looking at alternate network management practices since FCC’s Order, the first response was to block these applications that hogged the bandwidth. Following the establishment of this practice, Comcast was sued by consumers – one e.g. <em>Hart v. Comcast of Alameda, Inc., </em>No. 07-6350 (N.D. Cal. 2008). However, Comcast managed to acquire a stay for this case, by suggesting that this case should be deferred to an agency that has the subject matter expertise and within whose jurisdiction this would fall (of couse, the FCC). This case is still pending with the FCC.  Comcast seems to agree that the FCC has subject matter jurisdiction over network management practices, however it disagrees with the procedural aspects of the Order in question and challenges FCC’s ancillary authority.</p>
<p><span style="text-decoration: underline"><strong>Potential Impacts in the industry –</strong></span> According to many news reports, this decision could trigger many unwanted actions in the industry. With Comcast’s acquisition of NBC under review, there is a cause for as Comcast, empowered by the decision of this case, could then potentially favor its own content as opposed to content from competitors. Similarly, Comcast could start blocking Google, if it teams up with Bing, or it could slow down YouTube considerably in favor of promoting its own contents.  This ruling has suddenly caused the situation to appear bleak, as analysts have begun to scream about the lack of internet consumer protection laws. Some analysts also argue that this ruling could also potentially impact the implementation of the National Broadband Plan (NBP), as proposed by the FCC. Through the NBP, FCC is trying to get basic high speed internet service to all Americans, instead of merely getting them phone service. With this ruling, the question remains as to whether FCC needs to change its strategy and take a fresh look at its jurisdiction and authority before moving ahead with the NBP or not.</p>
<p><span style="text-decoration: underline"><strong>Open Issues – </strong></span>There is a lack of clarity in the definitions of and the differences between “telecommunications service” and “information service”. “Information service” is currently not regulated, because it is believed to be a competitive space, while “telecommunications service” is subject to common carrier regulations under Title II of the Act. If the FCC succeeds in proving that internet service provided by cable companies falls under “telecommunications service” as opposed to the “information service”, then there would be a way for the FCC to impose regulation. This might mean revisiting and reversing the rulings of some past court cases.</p>
<p>The current structure of the Communications Act remains fractured into non-overlapping silos. In the past, services and industries were non-overlapping – there was telephone, cable TV, over the air (OTA) broadcasting, etc. separated by technology, modes of operation and companies. In today’s converging platforms, we see that these silos do not exist anymore. Cable TV providers carry the digital OTA channels along with their respective cable content; they provide high-speed internet service through cable modems, and also provide digital voice phone services; similarly, cellular phone companies provide internet service, etc. Court rulings like these repeatedly remind us that in a convergent technology platform that we experience today, obsolete regulation could have the negative impact of slowing down innovation and thwarting competition by creating an environment of regulatory uncertainty. If at some point the FCC and the Congress decide to revisit the Communications Act, many would agree that it would be very helpful if they adapted the Act to address some of the current and relevant challenges in the industry today.</p>
<p><span style="text-decoration: underline"><strong>References and Interesting Reads:</strong></span></p>
<p>[1] <em>Comcast Corporation</em> v. <em>Federal Communications Commission</em>, On Petition for Review of an Order of the Federal Communications Commission, United States Court of Appeals for the District of Columbia Circuit, No 08-1291, Decided: April 6, 2010.</p>
<p>[2] <em>In re Appropriate Framework for Broadband Access to the Internet Over Wireline Facilities</em>, 20 F.C.C.R. 14,986, 14,988, ¶ 4(2005).</p>
<p>[3] <em>In re Formal Compl. Of Free Press &amp; Public Knowledge Against Comcast Corp. for Secretly Degrading Peer-to-Peer Applications</em>, 23 F.C.C.R. 13,028 (2008) (<em>Order</em>)</p>
<p>[4] The three Supreme Court cases that authorized FCC’s “ancillary jurisdiction” – <em>United States v. Southwestern Cable Co.</em>, 392 U.S. 157 (1968), <em>United States v. Midwest Video Corp.</em>, 406 U.S. 649 (1972) (<em>Midwest Video I</em>), anf <em>FCC v. Midwest Video Corp.</em>, 440 U.S. 689 (1979) (<em>Midwest Video II</em>).</p>
<p>[5] These cases are part of the Computer Inquiries I, II and III. Also see Robert Cannon,<em> The Legacy of the Federal Communications Commission’s Computer Inquiries, </em>Available at &#8211; <a href="http://www.law.indiana.edu/fclj/pubs/v55/no2/cannon.pdf">http://www.law.indiana.edu/fclj/pubs/v55/no2/cannon.pdf</a></p>
<p>[6] In a 2005 case, the FCC had to conclude that Internet service provided by cable companies was neither “telecommunications” nor “cable”, therefore neither Title II nor Title VI applied to it. However, the FCC used ancillary jurisdiction to settle the case.  See <em>Nat’l Cable &amp; Telecomms. Ass’n v. Brand X Internet Servs.</em>, 545 U.S. 967 (2005). Also see  Cable Modem Order of 2002 &#8211; <em>In re High-Speed Access to the Internet Over Cable and Other Facilities</em>, 17 F.C.C.R. 4798, 4802  (2002).</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=tM6oSbvcXvE:ngIbivCU1sw:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=tM6oSbvcXvE:ngIbivCU1sw:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=tM6oSbvcXvE:ngIbivCU1sw:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=tM6oSbvcXvE:ngIbivCU1sw:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=tM6oSbvcXvE:ngIbivCU1sw:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=tM6oSbvcXvE:ngIbivCU1sw:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=tM6oSbvcXvE:ngIbivCU1sw:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=tM6oSbvcXvE:ngIbivCU1sw:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?d=qj6IDK7rITs" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?a=tM6oSbvcXvE:ngIbivCU1sw:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/ItCommunicationsBlog?i=tM6oSbvcXvE:ngIbivCU1sw:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ItCommunicationsBlog/~4/tM6oSbvcXvE" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.perficient.com/communications/blog/2010/04/12/deconstructing-the-comcast-v-fcc-case/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blogs.perficient.com/communications/blog/2010/04/12/deconstructing-the-comcast-v-fcc-case/</feedburner:origLink></item>
	</channel>
</rss>
