<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: In a VAN down by the river&#8230;</title>
	<atom:link href="http://blogs.inovis.com/2008/01/10/in-a-van-down-by-the-river/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.inovis.com/2008/01/10/in-a-van-down-by-the-river/</link>
	<description>Power Profitable Business Communities™</description>
	<lastBuildDate>Fri, 12 Mar 2010 23:00:08 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: What does the grass look like on the other side of the fence? &#171; The Inovis Blog</title>
		<link>http://blogs.inovis.com/2008/01/10/in-a-van-down-by-the-river/#comment-844</link>
		<dc:creator>What does the grass look like on the other side of the fence? &#171; The Inovis Blog</dc:creator>
		<pubDate>Tue, 29 Jan 2008 15:08:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.inovis.com/2008/01/10/in-a-van-down-by-the-river/#comment-844</guid>
		<description>[...] it green, brown, or nothing but dirt? So, as a follow up to my earlier post &#8220;In a VAN down by the river…&#8221; I wanted to pose the question to the most important people to service providers—the [...]</description>
		<content:encoded><![CDATA[<p>[...] it green, brown, or nothing but dirt? So, as a follow up to my earlier post &#8220;In a VAN down by the river…&#8221; I wanted to pose the question to the most important people to service providers—the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Dunham</title>
		<link>http://blogs.inovis.com/2008/01/10/in-a-van-down-by-the-river/#comment-774</link>
		<dc:creator>Craig Dunham</dc:creator>
		<pubDate>Thu, 10 Jan 2008 16:39:58 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.inovis.com/2008/01/10/in-a-van-down-by-the-river/#comment-774</guid>
		<description>Oh boy, oh boy, oh boy!  A comment space that I REALLY know something about!!!!

I&#039;ve been using Inovis for ALL of My EDI &quot;life&quot;....  We were on Harbinger (now part of Inovis) Trusted Link 2.11 for a long time and we used the IBM Advantis network that we purchased through QRS (now part of Inovis)...  I&#039;ve been dealing with folks from QRS since My beginning in EDI about 4 years ago...  Wow... Has it been that long...?

When QRS became a part of Inovis, so did we.  When the &quot;resell&quot; of the IBM Advantis network was going to move away from Inovis and be taken over by ... GEIS? ... we were faced with the option of migration...  but we had no choice...  we either had to migrate from the IBM Advantis through QRS/Inovis to IBM Advantis through GEIS (or whomever!) or we had to migrate to another network.... 

We chose to stay with Inovis and moved to the InovisWorks platform.

And nothing worked better....

The Migration Team from Inovis made it very simple and easy - taking care of every aspect of the migration - from notifications to all trading partners and VANS/Networks to walking us through any changes that we needed to make on our local systems and in TrustedLink i-Series (our translator product - now at V 6.1.4)...  Ella and Raul and Sue and Lisa and.... well, the entire Inovis crew.... made our transition super simple....

We were able to keep visibility into our &quot;old&quot; mailbox on the IBM network for a year and I would get reports whenever a vendor sent something to the &quot;old&quot; mailbox and I could contact them and remind them of the change....  We had very minimal issues with vendors &quot;missing&quot; that migration, but there were a few - maybe a dozen?  And if they didn&#039;t respond to My gentle nudges - &quot;you do know we migrated networks/VANS, right?&quot; - then I could also involve Inovis and they&#039;d be able to help out with contacting both the vendor AND the network that they used....

Inovis was there through every step to make sure we were happy and set up properly with all our needs and the migration was pretty simple and easy...  certainly not the hair-pulling, heart-pounding experience that so many migrations can be.....

I still get calls - weekly - monthly - from this network or that VAN - saying that they can save Me &quot;a lot of money&quot; by switching from Inovis to brand X (or Y or Z or G or I or L or T or....)....  And what so many don&#039;t seem to understand is that COST is not the only factor to consider....  You need to consider so many other factors - such as up time/down time, errors or problems in the transmissions, and so forth - but another thing, as well...  If you&#039;re already using Inovis products and software and systems, why would you want to branch out to another product that may, even though it still &quot;works&quot; right with your existing systems, that may cause an issue down the road....

If I have an issue with a document, I can put in a service request and I know that since I&#039;ve got Inovis all over, I&#039;m not going to have Inovis tell Me that maybe it&#039;s with My &quot;brand X&quot; network.... or have brand X tell Me it&#039;s an issue with My application....  There&#039;s no &quot;it&#039;s their fault&quot; finger pointing...

By the way - if I seem like an &quot;Inovis Cheerleader&quot; - it&#039;s because I am...  I&#039;m exceptionally happy with the services and abilities from Inovis and will continue to be....</description>
		<content:encoded><![CDATA[<p>Oh boy, oh boy, oh boy!  A comment space that I REALLY know something about!!!!</p>
<p>I&#8217;ve been using Inovis for ALL of My EDI &#8220;life&#8221;&#8230;.  We were on Harbinger (now part of Inovis) Trusted Link 2.11 for a long time and we used the IBM Advantis network that we purchased through QRS (now part of Inovis)&#8230;  I&#8217;ve been dealing with folks from QRS since My beginning in EDI about 4 years ago&#8230;  Wow&#8230; Has it been that long&#8230;?</p>
<p>When QRS became a part of Inovis, so did we.  When the &#8220;resell&#8221; of the IBM Advantis network was going to move away from Inovis and be taken over by &#8230; GEIS? &#8230; we were faced with the option of migration&#8230;  but we had no choice&#8230;  we either had to migrate from the IBM Advantis through QRS/Inovis to IBM Advantis through GEIS (or whomever!) or we had to migrate to another network&#8230;. </p>
<p>We chose to stay with Inovis and moved to the InovisWorks platform.</p>
<p>And nothing worked better&#8230;.</p>
<p>The Migration Team from Inovis made it very simple and easy &#8211; taking care of every aspect of the migration &#8211; from notifications to all trading partners and VANS/Networks to walking us through any changes that we needed to make on our local systems and in TrustedLink i-Series (our translator product &#8211; now at V 6.1.4)&#8230;  Ella and Raul and Sue and Lisa and&#8230;. well, the entire Inovis crew&#8230;. made our transition super simple&#8230;.</p>
<p>We were able to keep visibility into our &#8220;old&#8221; mailbox on the IBM network for a year and I would get reports whenever a vendor sent something to the &#8220;old&#8221; mailbox and I could contact them and remind them of the change&#8230;.  We had very minimal issues with vendors &#8220;missing&#8221; that migration, but there were a few &#8211; maybe a dozen?  And if they didn&#8217;t respond to My gentle nudges &#8211; &#8220;you do know we migrated networks/VANS, right?&#8221; &#8211; then I could also involve Inovis and they&#8217;d be able to help out with contacting both the vendor AND the network that they used&#8230;.</p>
<p>Inovis was there through every step to make sure we were happy and set up properly with all our needs and the migration was pretty simple and easy&#8230;  certainly not the hair-pulling, heart-pounding experience that so many migrations can be&#8230;..</p>
<p>I still get calls &#8211; weekly &#8211; monthly &#8211; from this network or that VAN &#8211; saying that they can save Me &#8220;a lot of money&#8221; by switching from Inovis to brand X (or Y or Z or G or I or L or T or&#8230;.)&#8230;.  And what so many don&#8217;t seem to understand is that COST is not the only factor to consider&#8230;.  You need to consider so many other factors &#8211; such as up time/down time, errors or problems in the transmissions, and so forth &#8211; but another thing, as well&#8230;  If you&#8217;re already using Inovis products and software and systems, why would you want to branch out to another product that may, even though it still &#8220;works&#8221; right with your existing systems, that may cause an issue down the road&#8230;.</p>
<p>If I have an issue with a document, I can put in a service request and I know that since I&#8217;ve got Inovis all over, I&#8217;m not going to have Inovis tell Me that maybe it&#8217;s with My &#8220;brand X&#8221; network&#8230;. or have brand X tell Me it&#8217;s an issue with My application&#8230;.  There&#8217;s no &#8220;it&#8217;s their fault&#8221; finger pointing&#8230;</p>
<p>By the way &#8211; if I seem like an &#8220;Inovis Cheerleader&#8221; &#8211; it&#8217;s because I am&#8230;  I&#8217;m exceptionally happy with the services and abilities from Inovis and will continue to be&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
