<?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>Telemetry Talk &#187; vending technology</title>
	<atom:link href="http://www.telemetrytalk.com/blog/tag/vending-technology/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.telemetrytalk.com/blog</link>
	<description>Welcome to MEI's telemetry talk blog – the first site 100% dedicated  to vending telemetry technology. On this blog you can post questions to MEI experts and read the latest information on telemetry hardware and software. Browse through the posted content, or click on the links on the right side of the screen to get started.</description>
	<lastBuildDate>Sun, 27 Sep 2009 12:38:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Telemetry Choices – NAMA Vending Data Interchange (VDI) Standards</title>
		<link>http://www.telemetrytalk.com/blog/2009/09/telemetry-choices-%e2%80%93-nama-vending-data-interchange-vdi-standards/</link>
		<comments>http://www.telemetrytalk.com/blog/2009/09/telemetry-choices-%e2%80%93-nama-vending-data-interchange-vdi-standards/#comments</comments>
		<pubDate>Fri, 18 Sep 2009 16:34:52 +0000</pubDate>
		<dc:creator>Don Finley, MEI Product Manager</dc:creator>
				<category><![CDATA[Hardware Components]]></category>
		<category><![CDATA[telemetry]]></category>
		<category><![CDATA[vending technology]]></category>

		<guid isPermaLink="false">http://www.telemetrytalk.com/blog/?p=10</guid>
		<description><![CDATA[The technology in the vending community is expanding the ability for vending operators to enhance the user experience, deliver more payment options, keep machines running, and increase the efficiencies of operations.
Much of this new technology lies in the telemetry arena, enabling the use of credit cards and closed payment systems, along with alarm management and [...]]]></description>
			<content:encoded><![CDATA[<p>The technology in the vending community is expanding the ability for vending operators to enhance the user experience, deliver more payment options, keep machines running, and increase the efficiencies of operations.</p>
<p>Much of this new technology lies in the telemetry arena, enabling the use of credit cards and closed payment systems, along with alarm management and dynamic scheduling applications.  While there is a significant upside to having telemetry in your machines, until now, once you choose a vendor for dynamic scheduling or alarm management, you’re effectively locked in.</p>
<p><span id="more-10"></span></p>
<p>The problem of being locked into one vendor with limited options has had some adverse effects on the effectiveness of telemetry in the vending community:</p>
<p>•    What happens when one vendor comes out with the feature of the year?  If you’re not with that vendor, before now, you would have been out of luck.<br />
•    One telemetry provider offers cashless functionality and another has a dynamic scheduling application that meets your needs.  Earlier this year, one or the other but not both.<br />
•    You purchase another operator’s business and acquire their telemetry solution, and hope they utilized the same telemetry provider.  Otherwise, the telemetry equipment wasn’t worth anything.</p>
<p>As you can see, this situation doesn’t benefit anyone &#8212; operators are unable to realize the full potential of telemetry equipment, and selection is limited due to the lack of interoperability between telemetry equipment.</p>
<p>In the early part of 2009, NAMA formed a committee to address this problem, and a significant number of telemetry providers stepped up to assist in development and become early adopters of the Vending Data Interchange (VDI) standards.  Through months of hard work by the members of the VDI committee, and a commitment to deliver a workable solution back to the industry by NAMA ’09, the NAMA VDI standards Version 1.0 is being released.</p>
<p>This standard will enable telemeters from different manufacturers to communicate with other service providers.  As an early adopter of the VDI specification, MEI will be able to integrate the RDP into other dynamic scheduling software, allowing our customers to take advantage of the MEI RDP, the combo bezel and cashless, while utilizing another dynamic scheduling application.<br />
<!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> <w:UseFELayout /> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" LatentStyleCount="156"> </w:LatentStyles> </xml><![endif]--> <!--[if gte mso 10]></p>
<style>
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";
	mso-ansi-language:#0400;
	mso-fareast-language:#0400;
	mso-bidi-language:#0400;}
</style>
<p><![endif]--></p>
]]></content:encoded>
			<wfw:commentRss>http://www.telemetrytalk.com/blog/2009/09/telemetry-choices-%e2%80%93-nama-vending-data-interchange-vdi-standards/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
