<?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>Assurety Consulting &#187; IDEAlliance Specifications &#8211; Mailing Software</title>
	<atom:link href="http://www.assuretyconsulting.com/blog/category/mailingsoftware/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.assuretyconsulting.com/blog</link>
	<description>Updates from the mailing and publishing industry</description>
	<lastBuildDate>Mon, 02 Aug 2010 05:23:33 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Mail.XML and SOA (Services Oriented Architecture) &#8211; Use cases for the Mailing/Postal Industry</title>
		<link>http://www.assuretyconsulting.com/blog/2009/04/mailxml-and-soa-use-cases-for-the-mailing-industry/</link>
		<comments>http://www.assuretyconsulting.com/blog/2009/04/mailxml-and-soa-use-cases-for-the-mailing-industry/#comments</comments>
		<pubDate>Wed, 15 Apr 2009 03:23:26 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[IDEAlliance Specifications - Mailing Software]]></category>

		<guid isPermaLink="false">http://www.assuretyconsulting.com/blog/?p=38</guid>
		<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>
			<content:encoded><![CDATA[<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small; font-family: Times New Roman;">By Shariq (aka Sharick) Mirza</span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small; font-family: Times New Roman;">The last article “Getting to know Mail.XML™ &#8211; Understanding the latest specification from IDEAlliance: Mail.XML” focused on the basics of XML as a language overwhelmingly used on the internet and the fundamental business functions and current implementation of the IDEAlliance® Mail.XML™ specification v6.0. The article described the USPS® and industry’s phased approach for implementing IMB® Full-service solutions through Mail.XML and the business solutions available now and in Fall of 2009 from the USPS®.</span></p>
<p><span id="more-38"></span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small; font-family: Times New Roman;">In simple terms, we defined XML as a way to describe and communicate data and Mail.XML as an IDEAlliance specification designed in collaboration with the USPS to move business transactions and communications into Mail.XML from Mail.dat for certain business functions. We also briefly described the SOA architecture stating that the Mail.XML specification is designed to use Web services or SOA architecture where computers are’ talking’ with each other in a conversational mode using XML messages.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small;"><span style="font-family: Times New Roman;">In this article, “Mail.XML and SOA &#8211; 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<span style="mso-spacerun: yes;"> </span>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.</span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small; font-family: Times New Roman;">What is Services Oriented Architecture (SOA)?</span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small; font-family: Times New Roman;">Services Oriented Architecture is a request/response communication methodology that allows computers (business applications such as CRM, transportation management, operations management, financials, HR, Sales, Inventory management) on a network (intranet or internet) to ‘talk or conduct business’ with each other in a standard pre-defined XML language. This mode of communication bypasses the need to understand what old or new technology is used to implement each of the business applications. In a SOA environment, a business application’s logic is modularized to enable a service request/response mode creating a standard communication method that uses the internet protocol for bi-directional communication; bypassing any technology and application security limitations of the business applications such as Cobol, Mainframe, .Net, Java, Unix, Windows, etc.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small; font-family: Times New Roman;">How can we tell if SOA architecture is in use?</span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small; font-family: Times New Roman;">The main characteristics of the SOA services include: <strong style="mso-bidi-font-weight: normal;">a.</strong> defining who can access which service and how, mainly authorization, authentication, and predefinition of security and roles; <strong style="mso-bidi-font-weight: normal;">b. </strong>XML based communication which is predefined and used to describe and communicate the data; <strong style="mso-bidi-font-weight: normal;">c.</strong> XML communication structure existing in the form of messages or schemas also called XSD (XML Schema Definition)where the actual services are defined by WSDL (Web Services Definition Language). WSDL defines which services are available and how to access them; <strong style="mso-bidi-font-weight: normal;">d. </strong>Just like when we type </span><a href="http://www.rbpub.com/"><span style="font-size: small; font-family: Times New Roman;">http://www.rbpub.com</span></a><span style="font-size: small; font-family: Times New Roman;"> in our internet browser’s URL and the internet ‘knows’ through a directory listing to show you RB Publications website, same way the SOA services are registered through a Universal Description, Definition, Integration (UDDI) registry which serves as a directory listing for web services.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small; font-family: Times New Roman;">What are the benefits of SOA to an enterprise?</span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small; font-family: Times New Roman;">Most companies rather they be printers, consolidators, publishers, transporters or any other type of enterprise in the mailing industry have a mixture of both legacy and new technology solutions in their IT environments. Several IT organizations in the mailing industry are already increasing the value of their legacy and new IT assets by converting the existing business applications into customized services for their customers.<span style="mso-spacerun: yes;"> </span>The SOA architecture allows these companies to utilize existing hardware, software, and business applications; and increase the usage and value of existing IT assets for the enterprise by converting the existing assets into services. The SOA architecture is making decision making faster for many mailers, bringing the cost of doing business down by bringing more efficiency through automation. Think about instead of processing a whole Mail.dat to do sample analysis on cost of printing and transportation, having a service that takes sample container data from Mail.dat and gets the mailer answers in minutes on the printing, postage, and transportation costs in a request/response messaging model. </span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small; font-family: Times New Roman;">What are the benefits of SOA to the mailing industry?</span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small; font-family: Times New Roman;">The basic case study of SOA for the mailing supply chain started with the implementation of the IDEAlliance Transportation Messaging specification in 2004, now called Mail.XML. The IDEAlliance and the USPS collaborated to bring in a SOA solution to automate USPS FAST appointment management business process which was manual and prone to errors and data integrity issues. The IDEAlliance, industry, and the USPS agreed that the Mail.dat and mailers transportation systems needed to be complimented with a nimble transaction level communication solution. The Mail.XML SOA solution allowed the mailers to convert their Mail.dat and transportation management systems into services to work with the USPS to automate the appointment process and remove manual labor and data integrity issues from the old manual appointment process. The SOA solution removed manual data entry for mailers which resulted in cost avoidance and increased data integrity and the ability to manage change and communicate change to the USPS in a timely manner. For the USPS, the resource management costs and planning improved resulting in enhanced service delivery while providing more intelligence to the USPS about what to expect with each shipment and when. </span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small; font-family: Times New Roman;">What is the future direction of Mail.XML?</span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small; font-family: Times New Roman;">Think of mailing supply chain as a supply chain ‘network’.<span style="mso-spacerun: yes;"> </span>A network of computers representing different services by different mailing roles in the supply chain with business decision-making capabilities stored in the computers or business applications. The capability can enhance finding service providers, getting cost and time information in near real time and making business decisions on manufacturing, production, transportation, postage, and extra service capabilities from business partners.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small; font-family: Times New Roman;">Summary</span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small; font-family: Times New Roman;">The SOA can increase efficiency and speed of conducting business by communicating business specific information through Mail.XML in an automated and conversational mode and complimenting Mail.dat and existing IT assets within the mailing industry by converting them into services. The SOA also opens up the opportunity for the industry to think about removing single points of failure from the mailing supply chain, such as the USPS IT systems currently used by many as a single data store to communicate and touch their business partners data. Instead, the SOA architecture removes such risks by enabling more nimble and quick communication between the industry players outside and away from the USPS IT systems. Mail.XML SOA is bringing positive change to the industry that will benefit everyone’s bottom line.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><em style="mso-bidi-font-style: normal;"><span style="font-size: 10pt; line-height: 115%;"><span style="font-family: Times New Roman;"> </span></span></em></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><em style="mso-bidi-font-style: normal;"><span style="font-size: 10pt; line-height: 115%;"><span style="font-family: Times New Roman;">About the author: Shariq (Sha-rick) Mirza is the President and CEO of Assurety Consulting Inc. and currently serves as the IDEAlliance Technical Director for the Mail.dat and Mail.XML specifications. Mr. Mirza has over 12 years of USPS compliance and BPM experience. He can be reached at </span></span></em><a href="mailto:Smirza@AssuretyConsulting.com"><em style="mso-bidi-font-style: normal;"><span style="font-size: 10pt; line-height: 115%;"><span style="font-family: Times New Roman;">Smirza@AssuretyConsulting.com</span></span></em></a><em style="mso-bidi-font-style: normal;"><span style="font-size: 10pt; line-height: 115%;"><span style="font-family: Times New Roman;"><span style="mso-spacerun: yes;"> </span>Assurety Consulting Inc. is the leading professional services company providing business consulting and mailing software solutions for the Full-Service and the mailing supply chain. For more information, visit the Assurety Consulting website at </span></span></em><a href="http://www.assuretyconsulting.com/"><em style="mso-bidi-font-style: normal;"><span style="font-size: 10pt; line-height: 115%;"><span style="font-family: Times New Roman;">www.AssuretyConsulting.com</span></span></em></a><em style="mso-bidi-font-style: normal;"><span style="font-size: 10pt; line-height: 115%;"><span style="font-family: Times New Roman;"> or call 866-750-4924</span></span></em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.assuretyconsulting.com/blog/2009/04/mailxml-and-soa-use-cases-for-the-mailing-industry/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Getting to Know Mail.XML</title>
		<link>http://www.assuretyconsulting.com/blog/2009/03/please-come-bacl-later-under-construction/</link>
		<comments>http://www.assuretyconsulting.com/blog/2009/03/please-come-bacl-later-under-construction/#comments</comments>
		<pubDate>Sat, 28 Mar 2009 03:23:28 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[IDEAlliance Specifications - Mailing Software]]></category>

		<guid isPermaLink="false">http://208.106.182.82/assurety/blog/?p=33</guid>
		<description><![CDATA[Mail.XML - The change that can positively impact everyone's bottom-line. Learn more about SOA in the next article]]></description>
			<content:encoded><![CDATA[<p>by Shariq Mirza and Wallace Vingellis</p>
<table border="0" cellspacing="5" cellpadding="5" width="100%">
<tbody>
<tr>
<td><span style="font-size: 8pt; font-family: Arial;"><strong> Understanding the latest specification from IDEAlliance</strong></span></td>
</tr>
<tr>
<td>
<div><span style="font-size: 10pt; font-family: Arial;">As mailers learn more about the USPS Intelligent Mail program that begins in May, they see two things repeated over and over in relation to the electronic documentation (eDoc) requirements for the Full-Service option: Mail.dat and Mail.XML. However, very few understand what the differences are between the two. Both specifications are developed by the International Digital Enterprise Alliance (IDEAlliance) — an industry association specializing in technology, supply chain, and best practices for the mailing, printing and publishing industries — and freely available as a service to the mailing industry. The specifications are used to share information among organizations in the mailing supply chain and the Postal Service and their structure and purpose are significantly different.</span></div>
<p><span id="more-33"></span><br />
In the last issue, we discussed the Mail.dat specification and answered some basic questions about what it is, some of its benefits, etc. In this issue we are going to take a similar look at the latest specification from IDEAlliance: Mail.XML. The information presented here will again be in a Q&amp;A format and will provide a basic understanding of the Mail.XML specification and its purpose. A more detailed article, focusing on business communication strategy and services architecture, will be printed in the next edition.</p>
<p><strong>What is XML?</strong> XML stands for Extensible Markup Language, and is often defined as “a human-readable way of describing data or structured data.” It also means that you can extend a specification with fields — without necessarily impacting your communication software. XML is the current standard of communication between two or more computers over the internet and is the Business-to-Business communication and automation standard. Today, almost all eCommerce occurs through XML.</p>
<p><strong>What is Mail.XML?</strong> Mail.XML, which really began several years ago as the Transaction Messaging specification, is an XML-based communication specification developed by the IDEAlliance in collaboration with the USPS to automate business processes and communication wherever possible. Mail.XML is a messaging protocol that enables two-way communication between parties in the mailing supply chain and is designed to increase efficiency and lower costs by removing many manual data entry processes and enabling quick, near real-time communication between business partners. The core focus of Mail.XML is light-weight, business-function-specific communication where computers are “talking” with each other.</p>
<p><strong>What information is Mail.XML communicating?</strong> Mail.XML uses the comprehensive Mail.dat database to communicate mailing related information and specific transactions between members of the mailing supply chain, i.e., buying of services for printing, manufacturing, and transportation processes. In addition, the information communicated to and from the USPS supports mail verification, acceptance, and induction processes.</p>
<p><strong>What types of messages does Mail.XML support?</strong> Mail.XML currently supports container-based scheduling, pick up and drop off business processes, as well as identifying different business entities responsible for performing different services such as quality of mailing, address correction, and delivery confirmation on a mailing. Mail.XML also supports the communication of eDoc with the PostalOne! system.</p>
<p><strong>Does the USPS currently support Mail.XML?</strong> Yes. The original Transaction Messaging specification has been supported by the USPS since 2004. The initial focus was FAST appointment scheduling and automation processes. The new version of Mail.XML (version 6.0) supports eDoc requirements for the Intelligent Mail Full-Service option, as well as the Full-Service data feedback requirements from the USPS to the industry.</p>
<p>The USPS is taking a phased approach to the Mail.XML version 6.0 implementation: In May 2009, the USPS will support all transportation and appointments needs for the Full-Service option. It will also provide the capability for mailers to receive ACS Change Of Address (COA) and Nixie data, as well as Start-the-Clock and Container Scan data. In November 2009, the USPS plans to support all Full-Service eDoc functionality through Mail.XML version 6.0.</p>
<p><strong>What types of messages will be supported with version 6.0?</strong> The following types of messages will be supported in Mail.XML version 6.0:<br />
   &#8211;Transportation and Scheduling <br />
      Truck Availability for certain facilities and pick-up requests<br />
      Scheduling requests and responses for the USPS FAST system<br />
      Joint-Scheduling (multi-party) communication between the industry and from the industry to the USPS<br />
      Ability to download Customer Supplier Agreements for Origin-entered mailings<br />
   &#8211;Full-Service eDoc <br />
      Qualification reports<br />
      Container and Bundle reports<br />
      All Postage Statements currently supported through Mail.dat<br />
      Ability to request Mailer IDs and CRIDs from the USPS<br />
      Third-party data distribution for ACS COA, ACS Nixie, Confirm and Start-the-Clock data<br />
   &#8211;Full-Service Data Feedback <br />
      ACS &#8211; Change of address and Nixies <br />
      Start-the-Clock<br />
      Container Scans</p>
<p><strong>What are some of the benefits of Mail.XML?</strong> Mail.XML is designed for two-way conversational communications that occur in near real-time. This increase in speed of communicating allows for more efficient business processes and can help you lower your cost of doing business. Also, Mail.XML can let you automate certain business functions because when you know all the “conflict situations” and you store the answers or triggers for each situation in your software, then the software is resolving most of the conflicts, thereby minimizing human interaction wherever possible and increasing the speed of business decision-making and improving the quality of services to everyone within the industry.</p>
<p><strong>Will Mail.XML replace Mail.dat?</strong> NO. Mail.dat and Mail.XML are different specifications, and Mail.XML will not replace Mail.dat. These specifications currently exist side-by-side and will continue to do so for many years to come. (Remember &#8211; Mail.dat provides a storage/database model for mailing information while Mail.XML enables two-way business-function specific communication between members of the supply chain.) As mentioned earlier, the next issue of this publication will have a more detailed article devoted to Mail.XML and the benefits of Services Oriented Architecture (SOA). In the meantime, for more information about both Mail.dat and Mail.XML, you can visit the IDEAlliance website at <a href="http://www.idealliance.org">www.idealliance.org</a>.</p>
<div><em></p>
<div><em> </em></div>
<div><em>About the author: Shariq (aka Sharick) Mirza is the President and CEO of Assurety Consulting Inc. and currently serves as the IDEAlliance Technical Director for the Mail.dat and Mail.XML specifications. Mr. Mirza has over 11 years of USPS compliance experience. He can be reached at <a href="mailto:Smirza@AssuretyConsulting.com" target="_blank">Smirza@AssuretyConsulting.com</a>.</em></div>
<p>Wallace Vingelis is Director of Product Management and Postal Affairs for Anchor Software, LLC, and currently serves as Co-Chair for the Mail.dat Specification for IDEAlliance. He can be reached at <a href="mailto:wvingelis@anchorcomputersoftware.com" target="_blank">wvingelis@anchorcomputersoftware.com</a>.  </em></div>
<div><em><a href="http://mailingsystemstechnology.com/ME2/dirmod.asp?sid=E8941DB3E6A4499196334DC6734E5945&amp;nm=Contact+Us&amp;type=Publishing&amp;mod=Publications%3A%3AArticle&amp;mid=8F3A7027421841978F18BE895F87F791&amp;tier=4&amp;id=466ADD2842C943D085F5105FFA8CE390">http://mailingsystemstechnology.com/ME2/dirmod.asp?sid=E8941DB3E6A4499196334DC6734E5945&amp;nm=Contact+Us&amp;type=Publishing&amp;mod=Publications%3A%3AArticle&amp;mid=8F3A7027421841978F18BE895F87F791&amp;tier=4&amp;id=466ADD2842C943D085F5105FFA8CE390</a></em></div>
<div><em> </em></div>
<div><em> </em></div>
<div><em> </em></div>
<div><em> </em></div>
<p><em> </p>
<p></em></td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://www.assuretyconsulting.com/blog/2009/03/please-come-bacl-later-under-construction/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
