We have quite a few customers starting to add X-CAD (Catia V5 and SoildWorks) data to the cloud.

This is fine until it comes to mapping revision information.

If the customer has a lot of data at a current revision say "E" then this needs to be reflected in the platform when the data is first saved and then the revision control taken over in the platform and progressed from that point onwards.

It is not acceptable to add data to the platform and for it to revert back to "A.1" for example on first save as this causes a lot of confusion, particularly if that revision is already be referred to at the pre-defined level in a company in procurement and ERP systems.

In those cases, the platform needs to fall into line with the incumbent systems and not the other way around.

What advice/methodology can be given to ensure that the correct revision of data is maintained on first save to the platform.