Applies To Product(s): Bentley OpenPlant Modeler Version(s): 08.11.09.397 Environment: Windows 7, Windows Server 2008 Area: Installation Subarea: Original Author: Nancy Mahmoud, Bentley Technical Support Group This article should serve as a guideline/help for users who have been working with OpenPlant Modeler (OPM) standalone and want to move on to OpenPlant Model Server (OPMS) mode. Background Typically the following scenarios would appear in the standalone mode: A single pipeline will be spread across multiple dgn files and it would also be associated with some root instances (unit, services, or additional user specific root nodes). Typically equipment and nozzles will be created in a separate dgn files and then connected piping components will be created in other dgn files. If there are 2 pipelines connected to each other at a joint, they will be created in separate dgn files. Steps to Accomplish When user wants to start using OPMS, the first thing to do is make sure the correct ProjectWise versions at the server and client end is used. More details about this and the general ProjectWise-OpenPlant compatibility information are provided in the OPMS_Setup.pdf document as well as the OpenPlant Administrator.chm (help file for OP Admin) available with the installation of OpenPlant Administrator. Once the server is setup, confirm that ProjectWise Explorer is used at the user’s end. This means the version of ProjectWise has to be above the minimum recommended version as mentioned in the readme file. Also, it is recommended to have the same version of ProjectWise at server and client end. If the user does not have ProjectWise Explorer when working in standalone mode, then un-install OPM, install ProjectWise Explorer then install OPM again. The following are the steps while working with a clean datasource of ProjectWise-OPMS. Launch the first dgn which will have newly created unit/service/pipeline and piping components. Perform a check in all so that all components are checked in successfully. Launch the second dgn which will have the same unit/service/pipeline (same tag name as used in previous dgn) and different set of components than the first dgn. Connect to server and perform a check in all. This will report duplicates for components that are present in server as well as in dgn file (typically unit/service/pipeline). Use the Fix Duplicate option to fix the duplicates for unit/service/pipelines. The Fix Duplicate option works on components that can be auto-fixed for duplicity which have been defined in the schemas, typically unit/service/pipelines/HVAC systems/Cable Traylines. Fix Duplicate replaces the instance of unit/service/pipeline in the dgn file (which is a newly created one) with the (duplicate) instance of the corresponding unit/service/pipeline on the server. So the result of Fix Duplicate is that the newly created unit/service/pipeline in the dgn file is replaced with the referenced out version of unit/service/pipeline from the server, and the instance (GUID) of unit/service/pipeline on server and dgn is ensured to be the same. When duplicates are fixed, the check in operation is automatically aborted then user needs to re-issue the check in command to continue the operation. If all duplicates were successfully fixed in step 3 above then no duplicates will be reported now and user can check in successfully. If there are additional dgn files containing same unit/service and/or pipeline then same procedure is to be used; open the dgn file, run check in all, fix duplicates and then re-issue the check in command. Repeat this for all the dgn files. No check out operation should be initiated until all such dgn files have been checked in. A check out operation with same unit/service/pipeline in server and dgn file will break relationships between unit/service and pipeline. Equipment’s and nozzles are not expected to be fixed with Fix Duplicate, they need to be manually fixed for duplicity. A good design will typically nothave duplicate equipment’s and since nozzle tag names are derived from equipment tag, the nozzle names will also be unique. In case of standalone mode, typically dgn files are attached as reference where equipment and nozzles is in one dgn file and connected piping components and pipeline are in another dgn file. In such case, the files have to be checked in individually, doing a check in all with attached reference will not perform any operation on the file attached as a reference. Either the equipment dgn or the piping dgn can be checked in first. Same is true for 2 connected pipelines in separate dgn files in standalone mode, dgn can be opened first and then checked in. In cases related to attaching references (where the root elements like unit/service are same across different dgn files), the ideal workflow while creating the models is: Create unit/service (in first dgn only) and then create equipment or piping data by associating it with unit/service. In second dgn, skip connecting to the OPMS repository, create new unit/service, create equipment or piping data and then attach the other dgn file as a reference. Then connect to repository and check in all. Again open the dgn 1 and perform check in all and this will report duplicates, perform fix duplicates and then do a check in all. After the check in for such equipment-pipeline or pipeline-pipeline data is complete, it is recommended to multi-select the equipment-pipeline from server tab and do a check out. Verify the presence of a valid joint between the 2 connecting components which were a part of separate dgn files before check in all. If there is no joint present, manually create the joint by a drag manipulation and dragging the pipe backwards (to create disconnect) and then again do a drag manipulation till end of nozzle/connecting piping component which will insert a joint. Then perform connectivity checker operations and verify the continuity is correct. Also verify that isometric sheets have continuity information. If needed, recreate the iso-sheet so it has the information of connected components. Perform a check in all operation again once all such data has been verified. Please note that in standalone mode if the dgn file is copied to have the information of unit/service/pipeline instead of recreating a new dgn file to have the same unit/service/pipeline then this will result in having same GUID for such components which upon check in will not have correct results. It is recommended to check the GUID of these root instances before checking in. The GUID can be viewed by selecting the entity in items browser and then opening the OpenPlant Modeler Tools Details. While in standalone mode if ProjectWise repository has been used for storing the dgn files as documents, the same repository can be used for OPMS. A schema import will need to be performed and the project will need to be setup. More details on this are available in OPMS_Setup.pdf document. Optionally, the user can create a new repository for connecting to OPMS. In which case, the dgn files will be stored in a PW repository (which is non-OPMS based) and the OPMS operations will be done in another repository with OPMS configured. See Also Plant Design and Engineering Wiki
↧