Post on 28-Dec-2015
transcript
2
Workbench 5.3
▼ New Features in 5.3 are:– New 3D Model Management module– Additions to the Admin module for Model
management configuration and setup– WriteAPI programmers toolkit for import of data– Technology upgrade
3
New 3DMM Module
▼ An Overview of the Model Management solution has been provided in the bulletin
▼ New module is part of the Model Management solution– NOTE: Will be renamed as ‘3D Design Coordinator’ in
the next release ▼ Why do we want it?
– Because it provides the ability to create all the data required for Model Management without having to use the full discipline modules of VPE Workbench, satisfying a customer who only wants Model Management
5
New 3DMM Module
▼ Provides ability to create limited data content for Lines, Equipment, and Instruments
12
New 3DMM Module
▼ each with data management
▼ Process has the only additional form, for Nozzle definition
13
New 3DMM Module
▼ New Instruments form– With data management
▼ All design forms have spreadsheet style wide views
14
New 3DMM Module
▼ Lines Equipment and Instruments are released with an engineering status (set in the Release purpose field) using the ‘Data Management by Status’ capability first released in VPE Workbench 5.2
15
New 3DMM Module
▼ On Release of the lines, equipment and instruments the data is back populated into the P&ID Plant connectivity tables – This is a configuration setting in VPE Workbench.
▼ It is NOT possible to mix P&ID Loads of data with this back population mechanism, or to switch methods mid-project
16
New 3DMM Module
▼ A link is made from the P&ID tables to the RELEASE data record, therefore making the design information and engineering status available to Model Management
17
New 3DMM Module
▼ This data is then ‘Issued for 3D Design’ and available to the Model Object Manager which synchronises the data between VPE Workbench and PDMS
18
New 3DMM Module
▼ Multiple releases can be kept for history tracking▼ These can also be purged in the ‘Release
History’ form as required
19
New 3DMM Module
▼ PDMS Attribute data is stored back in the VPE Workbench by Model Object manager and can be viewed under the deliverables menu– It can also be reported on through Business Objects
20
New 3DMM Module
▼ New module is self-contained – (Other than the user access, Model Management
configuration, data management setup etc in the Admin module)
– Providing all the necessary project configuration and setup forms.
21
New 3DMM Module
▼ Data created in the 3DMM module is stored in the same database schema as data created in the individual modules– Therefore providing FULL upward compatibility
22
Admin module additions - 3DMM
▼ A new 3DMM menu has been added▼ Provides:
– PDMS discipline setup for the Model Object Manager
24
WriteAPI
▼ A programmers toolkit has been added to allow data from an external source to be imported to the VPE Workbench– This is a COM dll and can be used in any automation
aware programming environment ie: Visual Basic, VBA inside Microsoft office, C++ etc.
▼ Includes Line, Equipment and Instruments data creation, modification and deletion– Drives data management to ensure database integrity– Change highlighting also enabled
25
WriteAPI
▼ Limited data content at present, only what can be seen in the Design forms in the 3D Model Manager module of VPE– In time this will be extended to include all data
▼ The installation of the WriteAPI is an optional part of the VPE Workbench Client installer
▼ It includes full programmers documentation and an optional test harness to show capability
▼ Uses an XML data definition and schema for the import– The XML schema and example files are included in
the documentation
26
WriteAPI
▼Data imported through the WriteAPI is compatible with all modules of the Workbench– Lines can be queried in Process, Piping or
3DMM modules– Process equipment in Process or 3DMM
modules– Electrical equipment in Electrical or 3DMM
modules– Mechanical equipment in Mechanical or
3DMM modules
27
WriteAPI
▼Interfaces have to be registered in the VPE Workbench Admin module for data to be imported– Controlling data access rights for the interface