RSS Feed
Posted by Johan Nel on 08 January 2018 05:37 PM

If you hold a licence for AIMS software you would have received the email announcement from Autodesk regarding their decision to discontinue AIMS as an individual product.  This does not come as a surprise since AIMS has been “Open Sourced”, for a little while now.  The only impact this has for AIMS users as far as the Open Spatial Software Suite is concerned, is on Enlighten.

 If I use Enlighten with AIMS, what is the impact?

Enlighten has been functioning with AIMS and/or Mapguide Open Source (MGOS) since Enlighten ver 3.0.   AIMS was actually built based on MGOS to start with  only 3 components added by Autodesk, those being:

  • Autodesk Infrastructure Studio (which is interchangeable with Mapguide Maestro, the Open Source equivalent);
  • Oracle Provider which is not used in Enlighten because of a bug, the Open Source equivalent “The King Provider” is used;
  • Raster Provider, the Open Source equivalent “GDAL Providers” are used.

We are committed to the continued enhancement and growth of Enlighten and therefore will continue to support AIMS as required, and we will increase our support to the maintenance of Mapguide Open Source.  The growth in Enlighten by the elimination of the “blue dragon” dependency and our efforts to support a modern React Viewer will ensure Enlighten keeps up with current IT trends. 

Enlighten 3.4 (release January 2018) and 4 (Release end of Q1 2018) will be compatible with AIMS 2017 and MGOS 3.1, and Open Spatial will continue to support these releases into the future.  As new MGOS release and made available, Open Spatial will support and contribute to the new functionality.

 In summary:

  • Any impact as a result of the discontinuance of AIMS as an individual product, is totally mitigated and should be without impact on  enlighten Customers.
  • Munsys, ACDC and the As Constructed Portal have no connection with AIMS and therefore remain completely unaffected.

 We will be in contact, personally within the next few weeks to give any clarification or explanations further to the above.

The Open Spatial Support Team

Open Spatial Logo

Comments (0)