Gateway for 3D Data 6​.1 release notes

These release notes describe enhancements to and include resolved and known issues where applicable.

Note: Resolved issues included here are the highest priority issues reported by customers, not a complete list of bug fixes.

New features and enhancements

The following new features and enhancements were added:

• Support extraction of STEP files
  The Gateway now supports the extraction of STEP format files. For more information, see Extract Step.

• Support extraction of MicroStation 3D DGN files
  The Gateway now supports Microstation 3D DGN V8 format files extraction, supported previously only in legacy GCT product.

• Upgrade MicroStation 3D configuration from GCT
  MicroStation 3D configuration upgrades from GCT enable conversion of project configurations from legacy products, allowing them to be reused..

• Support extraction of Navisworks viewpoints
  Viewpoints created in Navisworks and stored in NWD files now can be extracted and used in AIM for visualization. For more information, see Extract Navisworks.

• Support extraction of Navisworks user data
  User-defined attributes in Navisworks NWD models can now be extracted by the Gateway. For more information, see Extract Navisworks.

• Add a segment prefix to Navisworks attributes to avoid duplicates
  Navisworks Extractor now adds section names as prefixes to attributes names to avoid duplication. For more information, see Extract Navisworks.

• Support case-sensitive attribute matching via caseInsensitive parameter
  Attribute matching now supports case sensitivity to exactly match the attribute with the provided pattern in the cases where an object has multiple attributes with same name but in different cases. For more information, see Object Mapping.

• Allow manifest attributes in mapping conditions
  Mapping conditions support the use of Manifest attributes to enable more flexible and precise filtering. For more information, see Manifest references.

• Case no. 960378899 - Group output object files and datasets by class: The Gateway enables grouping of output files along with dataset files based on object class.

• Timeout to break processing immediately when separate processing is enabled
  When separate processing is enabled, the Gateway terminates the file processing promptly after the configured timeout period has elapsed. For more information, see General Settings.

• Option to cancel processing based on estimated ZGL size for IFC input files
  IFC file processing allows cancellation based on estimated ZGL size to optimize resource usage and processing efficiency. For more information, see Extract IFC.

• Option to cancel processing based on estimated ZGL size for NWD input files
  NWD file processing allows cancellation based on estimated ZGL size to optimize resource usage and processing efficiency. For more information, see the Conditional processing section in Extract Navisworks.

• Support class mappings for AIM bootstrap files
  The Gateway now supports the generation of AIM Bootstrap files for classes, Characteristics, Properties and Associations from the EIWM Data.

• Migrate to .NET 8.0
  The Gateway is upgraded from .NET Framework 4.8 to .NET 8.0 to enhance performance, strengthen security, and ensure long-term support.

• Extract data from S3 locations when on a VM or using a VPN
  S3 data extraction works when running on a VM or over a VPN, ensuring consistent connectivity in different environments.

• Option to generate unique columns with CSV loader
  CSV loader supports generation of unique columns in CSV output by preventing duplication of attributes when using the #Attributes parameter. For more information, see Appendix B: CSV Reporting.

Resolved issues

The following issues were resolved for this release of Gateway for 3D Data:

Known issues

The following problems and enhancement requests have been deferred until a future release:

Expectations and limitations

The following expectations and limitations should be considered for this release of the Gateway:

• Limitation Supporting Non-English User Locales

  When the Gateway is installed on a system where the user has selected a non-English locale that uses a comma as the decimal separator (that is, a number 123.45 in a Windows system with a French locale would be expressed as 123,45), the Gateway does not interpret such numbering formats from input sources and configurations nor does it export them into output files.

• Layer attributes missing from Navisworks files derived from MicroStation 3D DGN files

  When NWD files are derived from an import of MicroStation 3D models, the 'layer' attributes of objects are not extracted by the Gateway. Navisworks files derived from other 3D sources such as AutoCAD and IFC are unaffected by this limitation.

  For the original full release, latest list of exceptions and other updates, please see the Product Release Latest Update Note. For more information, visit https://www.aveva.com/en/support-and-success.

System requirements

Operating system prerequisites

The Operating systems prerequisites for the Gateway are listed below:

Note: The recommended/supported hardware and software configurations are constantly subject to review, so please consult the AVEVA support (https://www.aveva.com/en/support-and-success) for the latest recommendations.

Gateway prerequisites

The prerequisites for this Gateway release are as follows:

• Microsoft .Net 8.0 Runtime (x64)

• Microsoft Visual C++ Redistributable 2015-2022 (64-bit)

• Disk Space – When the Gateway processes large models it requires disk space to store temporary graphics files. For example, to create a 7 GB ZGL it requires 100 GB of temporary space. Processing times will also be extended if the server isn’t using a Solid-State Drive. Note that the size of the ZGL must be < 9 GB when using 3DVS in AIM.

• RAM - Huge input files may take significant time to process if the memory required by the Gateway process nears the limit of the RAM, as the Windows system will then start memory paging. For example:

  • Input NWD files up to 500 MB will require 32 GB of RAM and NWD files above 500 MB will require 64 GB RAM

  • Input IFC files up to 4 GB will require 64 GB RAM

    Therefore, if you expect to be processing such large files you should ensure the Gateway server has enough RAM to avoid memory paging.

    Note: Neither the AVEVA Licensing System nor LaaS are required for this version.

Compatibility information

• AVEVA Asset Information Management (AIM) on-premise version 6.0

• Input 3D files in the following formats:

  • Autodesk® AutoCAD® 3D .DWG and .DXF files up to version 2018 (version AC1032), produced by all versions of AutoCAD up to AutoCAD 2024

  • IFC STEP files conforming to the IFC 2x3 or IFC 4 schema definitions

  • Bentley MicroStation™ 3D .DGN files V7, V8 XM (aka V8.9),V8i (aka V8.11)

  • Autodesk® Navisworks® NWD files generated by Autodesk Navisworks Manager versions 2012-2024, 2016-2025, and 2026

  • PCF files created by piping design systems that support the use of Isogen®

  • XGL/ZGL files produced by AVEVA Gateways for UE, PDMS, PDS 3D or SmartPlant 3D

  • STEP data from files with extensions .STP, .STEP, .STPZ, .STPX, .STPXZ conforming to versions AP 203 Ed1 and Ed2, AP 214, AP 242 Ed1, Ed2 and Ed3, including XML

• Microsoft SQL server (64-bit) 2022 *

• Oracle database 21c (21.3.0.0.0) *

• Access Database Engine (ADE) 2016, 2021 (64-bit) * **

  Notes:

• * Connections to these databases are only required if they are being used for lookups.

• ** Installing ADE provides the ODBC driver needed by the Gateway to access data sources such as EXCEL files, MS ACCESS, CSV files, SQL server, Oracle and other ODBC-compliant databases. The 2016 version is officially no longer supported by Microsoft so we recommend the 2021 version, which can be installed via the Microsoft 365 Access Runtime if you need to avoid installing Microsoft 365.

To Install product release:

Please read the installation section of the online help (under the Get Started page of the AVEVA Gateway for 3D Data) or contact local support.

Note: Before this AVEVA Gateway for 3D Data 6.1 is installed, please ensure that any previous version of AVEVA Gateway for 3D Data is uninstalled.