What are VisionFM's processes for supporting upgrades, patches, service packs and hot fixes regarding:

• Solution defects:
  Defects identified by a client will be fixed in their system as soon as possible. If the problem was in the core of the application, then the fix will be distributed in the next update. If the problem is with a process or default data, then instructions will be included in the next newsletter.

• Security issues:
  Security issues would be addressed in a quarterly patch.

• Operating systems:
  Support for new operating systems would be included in major upgrades.

• Other third party software that VisionFM is dependant upon:
  VisionFM supports third party upgrades for the current version of VisionFM and the last two major releases. We endeavor to support new third party product releases as close to their public release date as possible.

• User licensing method (concurrent, named, by role):
  There is no per-user licensing in VisionFM client or web client. There is named per-user licensing for VisionFM's mobile client.

• Server licensing method (per server, CPU, environment):
  VisionFM is sold as a per-server license for VisionFM (client application), Web Server and Event Notification Server. We allow our clients to use the same server license to run a production and test environment.

What are VisionFM's product update releases strategies, procedures and time frames?
New versions are released once a year. Patches and updates are released every three months. Depending on the extent of the enhancement, upgrade procedures will vary. If the database requires restructuring, VisionFM offers the service as part of its upgrade pricing.

Are future releases backward compatible? How many releases does VisionFM support before a user must upgrade?
Typically releases are not backward compatible due to changes in the database to support new features. VisionFM supports its current release and the two previous versions.