<?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: 3 Ways to Reduce Mobile Expenses and Optimize Management</title>
	<atom:link href="http://www.telesoft.com/blog/2010/01/3-ways-to-reduce-mobile-expenses-and-optimize-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.telesoft.com/blog/2010/01/3-ways-to-reduce-mobile-expenses-and-optimize-management/</link>
	<description>TEM Edge: The Telesoft Blog</description>
	<lastBuildDate>Mon, 15 Aug 2011 17:52:03 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Hyoun Park</title>
		<link>http://www.telesoft.com/blog/2010/01/3-ways-to-reduce-mobile-expenses-and-optimize-management/comment-page-1/#comment-6</link>
		<dc:creator>Hyoun Park</dc:creator>
		<pubDate>Tue, 26 Jan 2010 17:25:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.telesoft.com/blog/?p=50#comment-6</guid>
		<description>For #1, I&#039;d add that international roaming, data usage, application and ringtone downloads, 411, and add-on services such as LBS should definitely be part of the mobility consumption policy. But having been in the trenches, creating a policy just means that a few IT or operations people understand how things should work.  It&#039;s not until the organization gains automated policy enforcement and routed approvals for service orders that these policies gain teeth and enforceability.

For #2, that breakout between data, voice (broken out into in-network, in-play, overage, international, and roaming), and SMS/MMS usage is increasingly important as the US catches up the the rest of the world from a messaging perspective. Companies leave a criminally large amount of money on the table because they don&#039;t have the skill sets to understand rate plan optimization and contract negotiations.

For #3, I&#039;d also add compliance issues such as Sarbanes Oxley and the Federal Rules of Civil Procedure, which require a level of archiving that many IT and telecom departments may not be familiar with. If they have call accounting systems, they may be covered on the landline side, but few companies are well equipped to meet these compliance issues from a wireless perspective.  Direct cost is important, but there&#039;s also a TCO perspective to consider for your readers.</description>
		<content:encoded><![CDATA[<p>For #1, I&#8217;d add that international roaming, data usage, application and ringtone downloads, 411, and add-on services such as LBS should definitely be part of the mobility consumption policy. But having been in the trenches, creating a policy just means that a few IT or operations people understand how things should work.  It&#8217;s not until the organization gains automated policy enforcement and routed approvals for service orders that these policies gain teeth and enforceability.</p>
<p>For #2, that breakout between data, voice (broken out into in-network, in-play, overage, international, and roaming), and SMS/MMS usage is increasingly important as the US catches up the the rest of the world from a messaging perspective. Companies leave a criminally large amount of money on the table because they don&#8217;t have the skill sets to understand rate plan optimization and contract negotiations.</p>
<p>For #3, I&#8217;d also add compliance issues such as Sarbanes Oxley and the Federal Rules of Civil Procedure, which require a level of archiving that many IT and telecom departments may not be familiar with. If they have call accounting systems, they may be covered on the landline side, but few companies are well equipped to meet these compliance issues from a wireless perspective.  Direct cost is important, but there&#8217;s also a TCO perspective to consider for your readers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

