<?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>Telecom Spend Trends &#187; Mobile Device Management</title>
	<atom:link href="http://www.hyounpark.com/tag/mobile-device-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hyounpark.com</link>
	<description>A Blog About Telecom Expense Management and Telecom Life Cycle Management</description>
	<lastBuildDate>Sun, 14 Feb 2010 15:20:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Rivermine Acquires MBG: mindWireless is the Wild Card</title>
		<link>http://www.hyounpark.com/2009/12/17/rivermine-acquires-mbg-mindwireless-is-the-wild-card/</link>
		<comments>http://www.hyounpark.com/2009/12/17/rivermine-acquires-mbg-mindwireless-is-the-wild-card/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 00:48:16 +0000</pubDate>
		<dc:creator>Hyoun Park</dc:creator>
				<category><![CDATA[Telecom Expense Management]]></category>
		<category><![CDATA[Wireless Expense Management]]></category>
		<category><![CDATA[Blackberry]]></category>
		<category><![CDATA[Call Accounting]]></category>
		<category><![CDATA[chargebacks]]></category>
		<category><![CDATA[MBG]]></category>
		<category><![CDATA[mindWireless]]></category>
		<category><![CDATA[Mobile Device Management]]></category>
		<category><![CDATA[Rivermine]]></category>
		<category><![CDATA[telecom lifecycle management]]></category>
		<category><![CDATA[Unified Communications]]></category>
		<category><![CDATA[wireless help desk]]></category>

		<guid isPermaLink="false">http://www.hyounpark.com/?p=28</guid>
		<description><![CDATA[On December 15th 2009, Rivermine acquired MBG, continuing a trend of consolidation in the Telecom Lifecycle Management industry. With this acquisition, Rivermine gained several strong capabilities that have differentiated MBG from the market in recent years.
MBG has traditionally been known for its strong accounting-based approach to expense management, which has resulted in call accounting and [...]]]></description>
		<wfw:commentRss>http://www.hyounpark.com/2009/12/17/rivermine-acquires-mbg-mindwireless-is-the-wild-card/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Fragmentation of Telecom Expense Management</title>
		<link>http://www.hyounpark.com/2008/05/10/the-fragmentation-of-telecom-expense-management/</link>
		<comments>http://www.hyounpark.com/2008/05/10/the-fragmentation-of-telecom-expense-management/#comments</comments>
		<pubDate>Sat, 10 May 2008 15:43:09 +0000</pubDate>
		<dc:creator>Hyoun Park</dc:creator>
				<category><![CDATA[Cell Phones]]></category>
		<category><![CDATA[Telecom Expense Management]]></category>
		<category><![CDATA[Wireless Expense Management]]></category>
		<category><![CDATA[Call Accounting]]></category>
		<category><![CDATA[Glossary]]></category>
		<category><![CDATA[Mobile Device Management]]></category>
		<category><![CDATA[Telecom Cost Management]]></category>

		<guid isPermaLink="false">http://www.hyounpark.com/2008/05/10/the-fragmentation-of-telecom-expense-management/</guid>
		<description><![CDATA[One of the biggest challenges of covering the Telecom Expense Management space is that there is such a high level of fragmentation and vagueness of categorization in the marketplace.  In looking at a "Telecom Lifecycle Management" solution, the typical end user has no clue whether this refers to ordering a phone number, handling a cell [...]]]></description>
		<wfw:commentRss>http://www.hyounpark.com/2008/05/10/the-fragmentation-of-telecom-expense-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
