Autosave for SP?

From the AVEVA Sales Brief,
AutoSave for System Platform (A4SP) will complete AUVESY-MDT’s End-of-Life process on December 31, 2025.

This means that from January 1st, 2026, onwards, AutoSave for System Platform will cease to be supported.

The last supported A4SP is 2023.

What is the proposed recommended Alternative?

If OctoPlant, what is the positioning and collateral to support this? 

Thanks

Parents
  • This thread was updated almost a year ago . Do we have any recent  updates from Aveva on the topic? As discussed here, Octoplant seems to be the alternative, but sadly Octoplant won’t support 2023 R2 SP1 yet. And as we know, A4SP won’t support beyond V2023. What alternatives do we have for version control and compare feature for 2023 R2 SP1 installations? 

  • Unfortunately, there is no quick fix. A4SP was developed over several years, and creating a replacement will require significant time and investment. We are working on two fronts to get there:

    1. We are developing text-based configuration files that can describe an entire galaxy, with the aim of enabling customers to store these in Git repositories and lay the foundations for a source control solution we hope to expand. We already support CSV files that describe instances, and in the next release (System Platform 2026, targeted for Q4 this year), we are adding the ability to export/import graphics to/from XML, as well as export/import Templates to/from XML. Initially, this will be a somewhat manual process, but we plan to build on it over time.

    2. We are also attempting to engage an external solutions provider. However, these negotiations are under NDA, so there is little I can share at this time.

    I understand these answers may be unsatisfactory, and that everyone would prefer an immediate solution with all the capabilities lost when the A4SP product was deprecated by its OEM. We are working on this as quickly as possible, without compromising the rest of the product or neglecting broader market demands.

     - Ernst

Reply
  • Unfortunately, there is no quick fix. A4SP was developed over several years, and creating a replacement will require significant time and investment. We are working on two fronts to get there:

    1. We are developing text-based configuration files that can describe an entire galaxy, with the aim of enabling customers to store these in Git repositories and lay the foundations for a source control solution we hope to expand. We already support CSV files that describe instances, and in the next release (System Platform 2026, targeted for Q4 this year), we are adding the ability to export/import graphics to/from XML, as well as export/import Templates to/from XML. Initially, this will be a somewhat manual process, but we plan to build on it over time.

    2. We are also attempting to engage an external solutions provider. However, these negotiations are under NDA, so there is little I can share at this time.

    I understand these answers may be unsatisfactory, and that everyone would prefer an immediate solution with all the capabilities lost when the A4SP product was deprecated by its OEM. We are working on this as quickly as possible, without compromising the rest of the product or neglecting broader market demands.

     - Ernst

Children
  • Hi Ernst , Thanks for the answer.

    git repository is a really good way of going ahead with configurations and version control as this is agnostic, supports branching and merging and multiple versioning. This is vendor agnostic so will prevent us from having this problem in future.

    xml import and export for graphics is a huge game changer for SCADA nerds like us. This will significantly reduce engineering time and allow easier find replace functions that we are well used to.

    There used to be Galaxy backup utility, Will AVEVA release a newer version of that ?