Product Release Summary LFM Modeller Release Date: 26/05/2017

Size: px

Start display at page:

Download "Product Release Summary LFM Modeller Release Date: 26/05/2017"

Clementine Wilkerson
5 years ago
Views:

1 Product Release Summary LFM Modeller Release Date: 26/05/2017 This document outlines all changes made in the above release of LFM software. Document Prepared by: Neil Cocker Team Lead, LFM Support Document Approved by: Jennifer Copple Senior Application Consultant Superseded software version: LFM Modeller LFM Software version numbers: X.X.X.X First version field denotes general software series number. Second version field is incremented to track major new feature implementation. Third version field is incremented to track minor new feature implementation. Final (fourth) version field is incremented to track error fixes. PC minimum supported specification: Processor Intel Core 2 Duo Memory (4x1024) 667Mhz DDR2 Dual Channel ECC Hard Drive 80GB (7200RPM) Serial ATA11 Optical Drive 16x DVD +/- RW Drive Graphics card NVIDIA Quadro FX 2000 Operating system Windows XP SP3 / Windows 7 x86 and x64 Network 1GB Ethernet card

It is extremely desirable to keep as much information within the model when creating the export macros, to reduce the intervention required in CAD. LFM Modeller 3.97.0.

2 Enhancements for this release: Focused export improvements to maintain modelled intelligence. As-built objects modelled in LFM Modeller carry more intelligence than some rival packages, and more closely resemble the final native CAD formats. It is extremely desirable to keep as much information within the model when creating the export macros, to reduce the intervention required in CAD. LFM Modeller has small but significant improvements to further this aim. Level 1 Tagging The ability to store tag ID s on their respective components. These can replace the item catalogue reference & class information or be appended to this data for clarity. This intelligence is maintained upon intelligent export. Custom Component Grouping Geometric export to AVEVA software results in a series of equipment groups to represent the model hierarchy. Previous versions of LFM Modeller were not capable of storing ancillary equipment with their parent component, which resulted in disconnected geometry inside the E3D or PDMS project database. LFM Modeller now supports custom additions to standard components so that they are all held in the same group. This is important to customers wishing to maintain a basic level of intelligence in the AVEVA environment. The changes introduced to tag ID s and grouping support lean modelling for visualisation, where simple models are linked to information management systems used in operating and maintaining the asset. This allows realistic as-operated models to be produced that occupy the same spatial footprint in CAD as on plant, and these models can be named & grouped to suit the underlying data held for the item.

3 Error fixes for this release: The following table contains the LFM Software internal reference for each fix in this release, a description of the error, and a description of the solution. Internal Reference B #5592 B #907 B #908 B #909 Description PCF export first item exported is not written into the PCF file. Blank flanges not being written into PCF via intelligent export End-caps not being written into PCF via intelligent export Gaskets not being written into PCF via intelligent export Solution An alternate method of connecting to the component database was created to ensure all modelled items are written into the PCF file Defect addressed to allow export Defect addressed to allow export Defect addressed to allow export Error fixes for release: Internal Reference B #5581 B #5589 Description When setting a tag name on a component, use the object name as the initial tag, and allow the user to edit instead of clearing the field for re-entry PDMS [Geometric] export: new export structure for the grouping of components inside PDMS/E3D Solution The tag name defaults to be the component type/class prior to editing [Appendix A] Standard components may now be modified to include custom geometry to represent actuation systems & instrumentation etc. This is grouped within one equipment SUBE upon export. [Appendix B]

4 Error fixes for release: Internal Reference B #754 B #867 Description CHS fitting uses picked points rather than point cloud Solution Point cloud is now used correctly rather than the points the user picks in the BubbleView Square section fitting defaulting to RHS Now defaults to SHS B #536 # # # # # # # Angled section fitting defaulting to the incorrect side/orientation Angled beams exported to PDMS import in the wrong position Mitred items do not look graphically correct when exported Negative extrusions within a panel and not exported to PDMS Planes with curved edges are exported with a jagged edge rather than a curve Only SITE and ZONE names are maintained on export to PDMS. All EQUI and SUBE groups take an arbitrary name Patch valve always asks the user for the flange type regardless of the valve type. Nozzles cannot be created. When in the equipment task the user is prompted to select a pipe. On doing so the nozzle command in no longer activated There is now the ability to specify whether the picked points are on the outside or inside of the angled section. The angled section is then fitted to the appropriate side. To specify the side, roll the mouse wheel to the appropriate icon whilst in fitting mode. Angled beams now export correctly to PDMS Mitred items now correctly displayed on export Negative extrusions now exported correctly Curved planes now export correctly EQUI and SUBE groups now maintain their name. New procedure is to ask for the valve type first and the only ask for the flange type only if the valve has flanges Pipes can now be selected when fitting a nozzle without cancelling the nozzle command allowing the successful creation of nozzles

Ability to apply tag names/descriptions to items at the point of

sub-equipment [SUBE] collections Requirement: The screenshot

There are many examples in my design; the model also contains

5 APPENDIX A 1. Model hierarchy names are now fully supported upon export. 2. Ability to apply tag names/descriptions to items at the point of modelling. 1. LFM Modeller & PDMS layer naming 2. LFM Modeller Set Tag APPENDIX B 1. Enhancement Request [AVEVA Grouping]: Exporting custom objects as sub-equipment [SUBE] collections Requirement: The screenshot shows a typical component made of multiple primitives. There are many examples in my design; the model also contains some hybrid components where the Valve body is a SUBE and the Actuator is made of free primitives not related to the valve. We need to create 1 grouped item in E3D/PDMS and Navisworks.

Background: LFM Modeller exports to E3D/PDMS (1) as equipment [geometric] only, and consequently all the resulting models are constrained by E3D & PDMS having a 4-level equipment hierarchy.

6 Background: LFM Modeller exports to E3D/PDMS (1) as equipment [geometric] only, and consequently all the resulting models are constrained by E3D & PDMS having a 4-level equipment hierarchy. Therefore, all completed models must be layered to adhere to this convention (2) or the resulting model cannot be instantiated within the E3D/PDMS project database. (1) AVEVA Laser Modeller is separately available should the user wish to create intelligent models that are fully compatible with E3D/PDMS. Please contact AVEVA or LFM Software Support for more information. (2) Please refer to: LFM_Modeller_Export2CAD.pdf [included with the LFM Modeller installation] for information relating to layering or export workflow. Issue: The 4-Level hierarchy does not allow sufficient depth to support logical groupings that represent site, zone, pipe systems, branches and components etc. This restriction is compounded when additional geometry is added to represent custom componentry. Solution: LFM Modeller can now support model hierarchies of: SITE ZONE EQUI SUBE, where the SUBE can contain a standard component [e.g Valve or Flange etc.] inclusive of custom geometry to represent actuators, instrumentation, or items unavailable within the standard catalogue. This results in a general (EQUI) group that contains all the pipe cylinders and other standard objects. The SUBE would include the geometry associated with a standard component and any additional geometry added by the creator.

The group is named, and this name will be written into the resulting macro for identification purposes in

7 This following example illustrates the recommended hierarchy. The valve is stored in a group that contains all the additional objects that represent the actuator. The group is named, and this name will be written into the resulting macro for identification purposes in PDMS/E3D. Once viewed inside E3D or PDMS, the assembly will be stored as one item [SUBE]. Please note the name added by the designer (inside LFM Modeller) is respected upon import.

This Level 1 tagging and grouping will allow designers to search for and select components in a more realistic manner than was previously possible without a degree of rework in the target

8 This Level 1 tagging and grouping will allow designers to search for and select components in a more realistic manner than was previously possible without a degree of rework in the target software package. This example illustrates multiple Valve selection inside Navisworks. Both these valves have been modified to include actuation systems unavailable in the standard LFM Modeller catalogue.

9 Product QA cycle: The LFM Software development philosophy uses AGILE principles to ensure a high-quality product which evolves to match customer requirements. Throughout the development cycle, test and evaluation is used to guide the process and minimise the final test overhead. The final test process has three stages, and this document has been prepared after these have been completed. These stages are outlined below. Individual Function Test All LFM Modeller desktop functionality is examined for correct responses. Functions called from the Main Menubar, Main Toolbar, Modelling Toolbars, and Component Browser are tested in turn. This ensures that the functionality matches the design intent, and previously recorded errors have been fixed. Destructive Test This section of the test schedule is aimed at investigating to see if a software product exhibits proper behaviour when subjected to improper usage, or improper input. The tests are applied to different data samples, machines, and in a random manner to try to replicate 'real world' variations in user conditions. Software Acceptance Tests LFM Software concludes the LFM test cycle with a series of controlled examples aimed at simulating real life use situations. The finished models are QA checked against calibrated historical data, to ensure that the product maintains the previous output standard.

Product Release Summary AVEVA LFM Server

Product Release Summary AVEVA LFM Server 5.0.0.5 Release Date: 18/03/2019 This document outlines all changes made in the above release of AVEVA LFM Server. Document Prepared by: Praveen Vankdoth Application