iNTERFACEWARE™ Inc.

Why Should You Upgrade?

Upgrades keep you eligible for support

• To receive support, customers must be on an official release of Chameleon that is no older than 2 years. In practice this means your organization should be running one of these official releases:

Version 4.0.7 - Supported until January 2009

Version 4.1.3 - Supported until May 2009

Version 4.5.1 - Supported until September 2009

	Snapshot beta releases are not supported for production environments. They are intended for use by customers to verify bug fixes and new features but must not be used in production unless you have a specific written agreement from iNTERFACEWARE management. Generally iNTERFACEWARE operates on a four month release cycle to ensure we have timely updates for new versions of third party databases, operating systems and languages that we support.

Upgrades introduce improvements and new features that continually increase your efficiency and time to market (go live)

• At iNTERFACEWARE, we work to ensure upgrades include a variety of new features and improvements that provide real efficiencies and improved ease-of-use in order to save you time, effort and expense.

Upgrades address/correct bugs encountered in previous versions

• We place each new version through a rigorous testing process. Nevertheless, bugs can and do sometimes get through. Because of our broad customer base and the multiple environments in which they operate, we are made aware of bugs quickly, often well before you encounter them. Using the latest version ensures that you can take advantage of fixes and avoid issues that have already been corrected.

Support is geared to address the most common, most recent issues faced by the majority of customers

• You expect a support team that is knowledgeable and responsive when you encounter problems. Our support staff are obviously more familiar with current features and issues. By using the more recent versions, we are better able to support and help quickly, effectively, and with less disruption to your customer or end-user. Similarly, your own support staff may find it more confusing to have to deal with multiple releases, especially where issues in older versions have been resolved in more recent versions. The ability to focus and build expertise in fewer, more recent versions means fewer staff are able to resolve more issues faster.

You want to retain control of your upgrade schedule, ensuring that releases are tested and stable

• If you plan and execute a reasonable upgrade policy, you retain control. You can test, adjust (if need be) and deploy in your time. You avoid having to scramble to resolve on-site headaches when changes to some component of the interface environment changes and is found to cause problems.

Avoid being stuck with obsolete versions

• The fact that an interface is working well, may inadvertently result in that installation being 'forgotten' and eventually encumbering you with a version that is no longer supported. Unfortunately, adjusting to a current release may now require more effort, delay and aggravation than would otherwise be the case. While our products are well tested for backwards compatibility, that is true only for a reasonable number of prior releases.

	If you implement interfaces less often: Upgrading is no less important. Less frequent use means less opportunity to interact with the software, resulting in less familiarity with issues that surface when you or others implement changes. By keeping up-to-date in your own time, you are less likely to encounter compatibility issues in a live setting, better able to deal with new issues, and less likely to find yourself with an obsolete version. Moreover, our support staff who are more familiar with current features and issues, are better able to support in a timely manner.