List of Fault Corrections
This release resolves defects identified through the following support incidents
| Module / Application | Description |
|---|---|
| Model | Title: Request for Support Regarding E3D Savework Hang Issue in Spectrum Environment Resolution: Fixed – A problem occurred when checking the status of the spatial map during savework, which led to empty DESI databases with no mappable elements to be updated unnecessarily. This resulted in long savework times and disruption to other users on the project. The problem has been resolved by preventing these updates when checking the status of the spatial map |
Exceptions – Significant Defects and Recommended Workarounds
| Module / Application | Description | Alternative Workflow / Recommendation |
|---|---|---|
| Engineering: P&ID | P&ID Default Rules are not displayed if the “P&ID Drawing” type name is renamed or removed. | Create a drawing type named “P&ID Drawing”, or rename any existing P&ID drawing type to this name to enable the out‑of‑the‑box default rules. |
| Engineering: Datasheets | Refresh issue when updating a discipline attribute from datasheets. | Reopen the datasheets to view the updated values. |
| Engineering: Datasheets | Explicit alignment settings (Symbols, Checkboxes, Radio Buttons) are not preserved when exporting to Excel or PDF. | Use these controls with their default alignment settings. |
| Engineering | Unable to link elements from different ENGWLDs in a global environment. | Linking/cloning tags across global location databases is not supported. A fix is planned for a future release. |
| Engineering | Model Analysis does not fully handle overridden class associations. If an overridden association exists on a child class that is the only child of its parent, Model Analysis may incorrectly suggest moving it to the parent. Applying the fix removes the overridden association. | No workaround currently. Each suggested fix should be reviewed manually. A permanent fix is planned for an upcoming release. |
| Engineering | RDFXML file from ISM is not fully supported in Data Model import. | Conceptual Model import does not fully support RDF XML from AVEVA ISM. Use GEICLE format instead. Full support will come in a later release. |
| Engineering: E&I | Power calculations do not support vertical busbars, horizontal busbars, couplers, and incomers. | Calculations are correct if Load Flow = false is set for the connection between the two busbars within the same Switchgear tag. |
| Engineering: E&I | After importing a device tag from etap that has been marked as couple, the “Is Coupler Device” attribute is not set correctly | Select device tag from etap import grid and execute Update Database option from ribbon bar for a second time |
| Engineering: E&I | If Switchgear/Controlgear class tag has at least 3 busbars and 2 coupler there can be a power calculation error for power flowing through the middle busbar (second busbar). This only exists if both couplers have Load Flow = True and if only 1 incomer has Load Flow = True which are connected to the first or third busbar | There is no workaround for this scenario but the power calculations for incomer are correct as seen by Supply tag |
| Engineering: E&I | Etap import creates FIC (Fed Item Connection) records between 2 tags even if Connection Voltage / Output Voltages are incorrect. | Ensure Connection Voltages setup in Engineering agrees with values in etap before executing etap import in AVEVA Unified Engineering. |
| Engineering: E&I | Termination Diagram Template Region vs. Content Boundary: In earlier versions of AVEVA Unified Engineering, termination diagrams relied on the Template region coordinates to define the area of the template that the software could insert symbols when the termination diagram is generated. With AVEVA Unified Engineering 4.0, the area of the template that the software could insert symbols should be defined by creating and adding a boundary symbol such as the Drawing Contents Boundary shown below. If a project has been upgraded to AVEVA Unified Engineering 4.0, templates that subsequently have a content boundary symbol added will in effect have 2 regions defined that the software can use to insert symbols. In this case, the content boundary symbol symbols. In this case, the content boundary symbol symbols. In this case, the content boundary symbol the Template region coordinates are ignored. However, if a template is used to generate a termination diagram that does not have a content boundary symbol inserted, the software reverts to using the Template region coordinates. | If a drawing is generated that displays content and yet a content boundary symbol has not been inserted into the template, this is because the software is using the original Template region coordinates. In the next release of AVEVA Unified Engineering the Template region coordinates are being removed and templates must have a content boundary symbol inserted. |
| Engineering: E&I | Changes made for the new loop regions functionality have affected hook-up drawing creation and the hook-ups appear blank. | For each symbol on the hook-up template, set the Sequence Number attribute to “0.1”. |
| Piping: Integrator | Integrator cannot currently resolve the DISPNN intelligent text attribute for P&ID elements. This means that the display name text will not be shown. | There is no workaround for this case at present. |
| Piping: Sub-Components | Sub-component weights are presently included twice in Material Take-Off for Isometric drawings – included with the parent element (e.g. valve) and the individual element listed under miscellaneous components. | There is no workaround for this case at present except for turning off weight reporting in the Isometric. |
| Model | AVEVA have identified that time taken to add elements to the 3D View is observed to be longer than product benchmark requirements. This is most evident where elements are observed to comprise complex geometry e.g. highly faceted GENPRI elements | Optimisation has been identified that will improve the add to drawlist scenario so that this operation is aligned with the benchmark performance expectations. The update is targeted to be included in AVEVA Unified Engineering 4.1.0 |
| All modules except Administration | In exceptional circumstances a user may have been expunged from a project and not be aware they are expunged. If a user types SAVEWORK in the command line in this condition, they receive a useful warning that condition, they receive a useful warning that have been expunged and steps to follow. However, if the user presses the savework button they get no warning message, and the system appears to have saved even though it has not. | In situations where a user may have been expunged without their knowledge, request or consent, they should be encouraged to use to type SAVEWORK at the command line. |
| HVAC | When creating HVAC Sketch drawings within the Draw module, The MTO table is not being populated with the correct description and item data for components created with the new HVAC Specifications: AVEVA_RECT SIMDUCT CLASS C/F AVEVA OVAL | This issue will be addressed by Sample data update in an upcoming fix release version of AVEVA Unified Engineering. |
This page summarizes key improvements from the official AVEVA release notes. For full details, please refer to AVEVA’s official documentation.