<?xml version="1.0" encoding="UTF-8"?><rss version="0.92">
<channel>
	<title>Assurety Consulting</title>
	<link>http://www.assuretyconsulting.com/blog</link>
	<description>Updates from the mailing and publishing industry</description>
	<lastBuildDate>Mon, 26 Jul 2010 04:00:56 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	<!-- generator="WordPress/3.0" -->

	<item>
		<title>&#8220;Data is the King” &#8211; Article I &#8211; Understanding Full Service roles for the USPS FAST Appointment management system</title>
		<description><![CDATA[The focus of this article is to explain the full service appointment needs and how they can be fulfilled by the mailing industry. Up until the initiation of full service program, electronic appointments and content were only used by mailers for automation, efficiency, and cost avoidance. Non Full service FAST appointments do not require content details such as IMcb(s), sort levels and other mailing details.
 Full service requires the availability of the electronic appointment information with content in a proactive manner to the USPS, so the USPS can proactively perform resource management at the plants and induction offices, meet or exceed service performance measurement needs of the mailers and reporting of Start-the-Clock information, and provide visibility into the mailing through pallet barcode scans. The long term objective, under evaluation, of electronic appointments/content  is to help remove more paper from the induction process, such as paper 8125s/8017s, when eDoc(s) are also available electronically, perform verification post-induction; hence, further lower the costs of doing business.
]]></description>
		<link>http://www.assuretyconsulting.com/blog/2010/07/data-is-the-king%e2%80%9d-article-i-understanding-full-service-roles-for-the-usps-fast-appointment-management-system/</link>
			</item>
	<item>
		<title>Mail.XML and SOA (Services Oriented Architecture) &#8211; Use cases for the Mailing/Postal Industry</title>
		<description><![CDATA[In this article, “Mail.XML and SOA - Use cases for the mailing industry” we will focus on defining SOA. We will also focus on explaining the future direction of IDEAlliance Mail.XML specification and Services Oriented Architecture which is the communication architecture driving  the IDEAlliance Mail.XML specification development. We will describe the possible usages and benefits of SOA to a company and the industry as a whole]]></description>
		<link>http://www.assuretyconsulting.com/blog/2009/04/mailxml-and-soa-use-cases-for-the-mailing-industry/</link>
			</item>
	<item>
		<title>Getting to Know Mail.XML</title>
		<description><![CDATA[Mail.XML - The change that can positively impact everyone's bottom-line. Learn more about SOA in the next article]]></description>
		<link>http://www.assuretyconsulting.com/blog/2009/03/please-come-bacl-later-under-construction/</link>
			</item>
</channel>
</rss>
