deployment guide: managed workspaces - bentley communities · the trane ductulator installed with...

Bentley Building Deployment Guide ProjectWise Managed Workspace

Copyright © 2009 Bentley Systems, Incorporated| Bentley Building Technote 1

Bentley Building Application Deployment Guide: ProjectWise Managed Workspaces Version 1.7 – May 2011, v8i (SELECTseries 1) ‐ ProjectWise 08.11.07.443 or later Installing Building Applications into a ProjectWise Managed Workspaces (Typical Configuration) This document:

is intended to provide recommendations and implementation guidance to provide the best integration of the Bentley Building applications into a ProjectWise Environment. The Bentley Building suite of applications include; Bentley Architecture (BA), Bentley SpacePlanner (BSP), Structural Modeler (formally Bentley Structural (BS)), Bentley Building Mechanical Systems (BBMS), and *Bentley Building Electrical Systems (BBES)

is a supplemental document to the "ProjectWise Implementation Guide” and the help documentation provided by ProjectWise Administrator and ProjectWise Client and shares common concepts and instructions. However, this document is intended to provide the best path of ProjectWise integration for the Building Applications.

will focus on topics concerning ProjectWise application definition, workspace integration and Project association, please refer to ProjectWise documentation for topic not addressed.

*Note: For additional information on integration of Bentley Building Electrical Systems see section: Configuring a ProjectWise managed Workspace for BBES V8i

Restriction and Limitations of integrating Building Application in a ProjectWise Managed workspace:

ProjectWise managed workspace support for building applications was introduced in 08.11.07.xx (SELECTseries 1) and integrated with ProjectWise 08.11.07.xx (SELECTseries 1) and is not supported in previous version.

PW managed workspace does not support an offline or briefcase mode, PW manage workspace require an active connection to a PW server.

PW managed workspace is a thick client solution and is not support with the ProjectWise Web Client

(SharePoint Web parts)

When working with ProjectWise managed workspaces, users should be encouraged to access and open files through the ProjectWise Explorer and not through application shortcuts in the start menu, quick launch toolbar or desktop. These application shortcuts will open the application in an unmanaged mode and require the application to restart when opening a managed file.

It is encouraged that the ProjectWise environment be configured for a "Captive" environment. (When

working in integrated applications, the term captive environment refers to the state of integration when the user cannot save documents to or open documents from the local file system. They are “captive” to working in the ProjectWise environment. ) ‐Please consult your ProjectWise implementation team and/or administrators before ProjectWise is configured for a "Captive" environment.



The "iDesktop integration for Bentley MicroStation" is required to be installed to support MicroStation's integration with ProjectWise.

To disable ProjectWise Integration when MicroStation is launched from the desktop, edit the pw.cfg (..\Program Files\Bentley\MicroStation (SELECTseries 1)\config\appl), uncomment (remove the # from the beginning of the line) the following lines:

%if !defined (_PWEXPLORER) PW_DISABLE_INTEGRATION=1 %endif

For ProjectWise Manage Workspaces, ProjectWise administrators / users are encouraged to set the user option to "Leave Local Copy on check in". This will increase operational performance with large projects. If changes in files are detected, ProjectWise will synchronize as required.

The following building application sub systems can run as external standalone applications, independently of the primary building applications. These building application sub systems can also be launch internally from within the building applications. When the building applications are integrated with ProjectWise Managed workspaces, these subsystems are only supported when launched internally. ProjectWise Managed workspace integration is NOT available for these subsystems when launched as an external standalone application.

Datagroup Catalog Editor

Datagroup Definition Editor

JSpace Interference Detection Engine

Parametric Cell Studio (PCS)

The Trane Ductulator installed with Bentley Building Mechanical Systems, the RAM Viewer, installed with Structural Modeler (formally Bentley Structural), MicroStation Triforma Backup utility and the JSpace Class editor have not been integrated and/or may not benefit from integration with ProjectWise Managed Workspaces.

Configurations file located in either the local workspace\standards directory or a centralized "Shared"

workspace\standards directory are automatically processed and are incorporated as part of the ProjectWise Managed workspace. Diligence is required to insure the configuration files contained within either of these directories does not contaminate the ProjectWise Managed Workspace Configuration.



Before You Begin

A fully operational and configured ProjectWise Server and a defined datasource must be available. Access to ProjectWise Administrator and the ProjectWise Client applications with corresponding administrator privileges are required. Please consult your ProjectWise implementation team and/or administrators before initiating ProjectWise Manage workspaces. Install and configure all the Bentley Building and other Bentley application onto a client workstation. This will ensure the \Documents and Settings\All Users\Application Data\Bentley\MicroStation\Workspace has all the require components for you application prior to importing it into ProjectWise. Use this client to complete the instruction in this document.

Overview of Steps: 1. Import Workspace files into PW in a folder called Building Workspace (Using Manage Workspace Wizard)

(approx. 30+ Min) 2. Import MicroStation Configuration File to ProjectWise Configuration Setting Blocks (Using Manage

Workspace Wizard) (approx. 10 min) 3. Add/Edit ProjectWise CSBs (approx.5 Min) 4. Add exclusions (approx.5 Min) 5. ProjectWise Application Support (approx. 5 min ) 6. Link CSBs to the Projects (approx.5 Min) 7. Test/Validate (Troubleshoot)



* Time estimates are approximated based on out‐of‐the‐box configuration and based on a remote connection to the PW server. Individual result will vary

Step 1: Import Workspace & Dataset files into PW (Using Manage Workspace Wizard) ‐ 30+ minutes

Use the Import Managed Workspace wizard; Import Data to ProjectWise from the File System

1. In ProjectWise Administrator, under Workspace Profiles>Managed (Right‐Click) and select “Import Managed Workspace”. This will open the Import Managed Workspace Wizard. In the Welcome dialog, Select Next



2. On the Choose Desired Action page, from the actions options, select the second option to "Import Data ProjectWise from File System", Then select Next

3. On the Import and Validate ProjectWise Folder Structure and Documents page, select the workspace to import in the Local File System list (default locations ‐ ..\Documents and Settings\All Users\Application Data\Bentley\MicroStation\WorkSpace). Then in the ProjectWise list, select the folder to import the workspace into. If the folder does not exist yet, you can right‐click in the list and select New Folder to create one.

In your ProjectWise repository, create a folder that will contain the workspaces to manage. For the purpose of this document define a directory called "Building Workspace"

Once you have selected a folder on both sides of the lists, click the Map button that is between the two lists, Then Finish to process.



4. Click Validate. During the validation process, the wizard is compares the content of the local workspace with the contents stored in ProjectWise. Since this is a fresh install, there shouldn’t be any files to compare against and this process should be rather quick. In the future, you can use this utility to update a workspace and/or dataset, It will perform a compare of the two directories and identify whether files exist or not, it does not compare the content of the file, only whether the files exist or not. Once the validation is complete the Validation of File System Structure against ProjectWise dialog opens. The following dialog compares the File system to the ProjectWise Mappings you have selected. Select an item to view its status. Items with a red ‘X’ indicates the file/folder is not present in the mapped ProjectWise repository, while the green check indicates it is present in the mapped ProjectWise repository. The tree structure in the left hand panel will display the status of each item as whether it present or not in the ProjectWise repository. Items with a red ‘X’ indicates the file/folder is not present in the ProjectWise repository, while the green check indicates it is present in ProjectWise repository Select an item in the list on the left to see what the status of the item is in ProjectWise. Since this is a fresh install, the entire workspace will be marked as not present and can be imported in its entirety, verify all directories are selected and select Resolve.

5. When ready, click Resolve to upload all missing and/or mismatched items to ProjectWise. When

finished, click Next, and then Continue to return to the first page of the wizard to begin Step 2.



Step 2: MicroStation Configuration File to ProjectWise Configuration Setting Blocks (Using manage Workspace wizard)

Use the Import Managed Workspace wizard; import MicroStation Configuration File to ProjectWise Configuration Setting Blocks (CSB).

If you are continuing from Step 1, skip to task 2, bypassing task 1 (opening the "Import Managed Workspaces…" wizard.)

1. Open the "Import Managed Workspaces…" wizard. In ProjectWise Administrator, under Workspace

Profiles>Managed (Right‐Click). Then select "Import Managed Workspaces…" this will open the Managed Workspace Wizard. In the Welcome dialog, Select Next

2. On the Choose Desired Action page, from the actions options, select the first option to "Import MicroStation Configuration File to ProjectWise Configuration Setting Blocks", Then select Next



3. Choose a MicroStation Installation and Workspace Root:

Locate the MicroStation Installation by browsing and locating the ustation.exe executable.

Default installation ‐ (Windows XP) …\Program Files\Bentley\MicroStation V8i (SELECTseries1)\ustation.exe, (Windows 7) …\Program Files (x86)\Bentley\MicroStation V8i (SELECTseries1)\ustation.exe

Locate the Workspace Root Directory Default installation ‐ (Windows XP) …\Documents and Settings\All Users\Application

Data\Bentley\MicroStation V8i (SELECTseries1)\WorkSpace, (Windows 7) …\ ProgramData\ Bentley\MicroStation V8i (SELECTseries1)\WorkSpace

Verify that the option to "Create configuration block for workspace root variable" is selected

Select Next

4. Scan Workspace, In the Workspace Configuration Files dialog, select the Scan Workspace, this will

initiate a Scanning Workspace process



5. When the text, “Scanning for Workspace Configuration Files completed successfully”, appears, Select Next

6. The Workspace configuration scan will result in a list of Site, Project and User configuration files that will be imported.

For this Building application integration, not all the configuration files are required to be converted into CSB., It is acceptable to import all configurations file found, but for ease of management, you want to be more selective and exclude:

all the Users Level files

all the MicroStation delivered example files (Building.pcf, Civil.pcf, General.pcf, Geospatial.pcf, Plant.pcf and untitled.pcf).

all the DatasetUnitSystem.cfg(s)



Selecting the "Level” label in the table header will sort the configuration files, making the task easier. Select the configuration files you do not want to process and select Remove, and then select Next to process.

7. This scans the entire workspace that you selected to import on the previous page. Once this is done you

can also add or remove individual files. Upon successful completion of the processing of the configuration files, Select Next again



8. On the Configuration Settings Blocks page, review the ProjectWise Configuration Settings Blocks that will be created. Configuration Settings Block names can be changed and/or reassigned to different ProjectWise levels, or they can be removed if unwanted.

Locate Workspace Root, change ProjectWise level from level from ‘Site’ to ‘Predefined’

Locate and select arch_roles, change the ProjectWise level from ‘Site’ to ‘Project’ Locate intmgr_imperial.cfg and Intmgr_si.cfg, change the ProjectWise level from ‘Site’ to

‘Project’ When finished, click Next

9. Please review the configuration file setting, if any errors or changes are noted, please use the back button to step backward in the Workspace Import Wizard, however if satisfied select Import, this will begin the process to convert your configuration files into ProjectWise Configuration Setting Blocks also referred to by the acronym CSB or CSBs (plural). Select the Import button to import the configurations.



10. When the import is finished (*** IMPORT SUCCESSFUL ***), click Next.

11. After this you have the option to either close the wizard or go back to the first page of the wizard to select another action. For this exercise, we are done with the Workspace Import Wizard, therefore select Close. Proceed to the ProjectWise Administrator to review the newly‐created configuration blocks in ProjectWise Administrator to verify the import. (Datasource>Workspace Profiles>Managed)



Step 3: Add/Edit ProjectWise CSBs

In ProjectWise Administrator, under Workspace Profiles>Managed

In this step, you are going to complete the following tasks:

Edit ‘Predefined’ CSB for WorkspaceRoot (_USTN_WORKSPACEROOT)

Create new ‘Predefined ’CSB for the Building WorkspaceRoot (_TF_WORKSPACEROOT)

Create new ‘Global ‘ CSB Edit ‘Project’ CSB File to support Project Data (_USTN_PROJECTDATA)

In V8i SELECTseries 1 Refresh release (ProjectWise 08.11.07.133+), a new level called ‘Predefined’ was added to the top of the processing order for configuration settings blocks in manage workspace. This level gives users the ability to set predefined variables in ProjectWise managed workspaces. Variables assigned to the Predefined level will be processed before the MicroStation local configuration is gathered. In previous versions, the processing of the MicroStation local configuration would incorporate any configuration files defined in the local MicroStation workspace into the managed workspace. The out‐of‐the‐box installation delivers only one configuration file (workspace/standards/standards.cfg) which by itself is fairly harmless too most managed workspaces but this directory is also a very popular destination for local customizations which could inadvertently alter the desired result of a manage workspace. Defining the Workspace Root at the ‘Predefined’ level will provide you the highest level of configuration management available in ProjectWise.



Predefined:

Edit the ‘Predefined’ Level CSB called "WorkspaceRoot" ‐ This is a critical task Assign the _USTN_WORKSPACEROOT to the appropriate ProjectWise Folder. This is the root directory of the ProjectWise workspace defined and imported in Step 1.

Edit Variable to the WorkspaceRoot CSB Name: _USTN_WORKSPACEROOT Description: _USTN_WORKSPACEROOT Edit Value: Operation Type: '='‐ Assignment

Value Type: Change 'String' to 'ProjectWise Folder' Value: Change value to point to ProjectWise Workspace, browse to pw:\\<server name>:<datasource name>\Documents\Building Workspace.

Tip: Since Workspaces can be version specific, you may want rename the WorkspaceRoot CSB to include the major version number, such as WorkspaceRoot_081107.

Tip: Use the CSB description to organize and manage collection of CSB. For example, change the description of WorkspaceRoot_081107 CSB to "08.11.07 Workspace Root", this will allow us to sort 08.11.07 CSB by description.



Step by Step Guide to edit WorkspaceRoot CSB:

Edit the ‘Predefined’ Level CSB called "WorkspaceRoot" ‐ This is a critical task Assign the _USTN_WORKSPACEROOT to the appropriate ProjectWise Folder. This is the root directory of the ProjectWise workspace defined and imported in Step 1.

Edit Variable to the WorkspaceRoot CSB Name: _USTN_WORKSPACEROOT Description: _USTN_WORKSPACEROOT Edit Value: Operation Type: '='‐ Assignment Value Type: Change 'String' to 'ProjectWise Folder' Value: Change value to point to ProjectWise Workspace, browse to pw:\\<server name>:<datasource name>\Documents\Building Workspace.

1. In ProjectWise Administrator , under Workspace Profiles>Managed>Predefined, open the WorkspaceRoot CSB for editing by double clicking or right‐clicking and selecting properties from the right ‐click menu.

2. Select the Configuration tab in the WorkspaceRoot Properties dialog. Select the pencil icon

to edit the _USTN_WORKSPACEROOT variable



3. Select the row in the values table and select modify

4. This will initiate the "Edit Value" Dialog. In this dialog, this is where we reassign the workspace to point to the ProjectWise workspace. Change the Value type: from String to ProjectWise Folder, this will enable the browse button, next to the Value: entry box, select the browse button and locate the ProjectWise workspace. For this example, we are looking for pw:\\<server name>:<datasource name>\Documents\Building Workspace.

Before:



After:

5. Select OK, to close Edit Value dialog, select OK, to close the _USTN_WORKSPACEROOT dialog

and proceed to Task 2. Select OK, to return to the Workspace Properties dialog. The results

of the WorkspaceRoot properties CSB should be as follows:

END – Step by Step Guide to edit WorkspaceRoot CSB:



Predefined: (Continued)

Create new ‘Predefined’ Level CSB called "Building_WorkspaceRoot”

Add Variable to the Building_WorkspaceRoot CSB Name: _TF_WORKSPACEROOT Description: Default Building_WorkSpace (_TF_WORKSPACEROOT) Add Value:

Operation Type: '='‐ Assignment Value Type: String Value: $(_USTN_WORKSPACEROOT)




Add Variable to the Building_WorkspaceRoot CSB Name: HVACDIR_WORKSPACE Description: BBMS Building Workspace Root Add Value:

Operation Type: '='‐ Assignment Value Type: String Value: $(_TF_WORKSPACEROOT)hvac/




Add Directive to the Building_WorkspaceRoot CSB Directive: %include Description: Default MicroStation Workspace

Add Value: Value type: Configuration Setting Block Value: WorkspaceRoot: Predefined Configuration File Block

The final Building_WorkspaceRoot CSB should look like the following:



Global: Create New Global Level CSB called "Global_Variables” (Recommended for Administration, Certification and debugging)

Add Variable to the Global_Variables CSB Name: _USTN_DISPLAYALLCFGVARS Description: Display All Configuration Variables Add Value:

Operation Type: '='‐ Assignment Value Type: Numeric Value: 1

Note: _USTN_DISPLAYALLCFGVARS displays all system level configuration variable and is useful for Administrators during certification and debugging.



Project:

Perform the following configuration options depending on the method of Project integration with ProjectWise:

(Please consult your ProjectWise implementation team as to the appropriate method for project integration)

Preferred method: Project Support for ProjectWise Projects If your projects folders have been promoted to PW projects, then the _USTN_PROJECTDATA can be automatically extracted by defining the following dynamic Project level CSB. The _USTN_PROJECTNAME is no longer necessary.

Folders that have been promoted to a ProjectWise Project have the ProjectWise icon associated with the Folder icon as displayed in the diagram above.

Create New Project Level CSB called "Dynamic_Project" Add Variable to the Dynamic_Project CSB

Name: _USTN_PROJECTDATA Description: ProjectWise Project Name Add Value:

Operation Type: '='‐ Assignment Value Type: String Value: $(dms_project(_DGNDIR))



Project: (Continued)

Please note: Since the _USTN_PROJECTNAME is automatically populated by the MicroStation Manager, and ProjectWise bypasses the MicroStation Manager , the information about the project name displayed from MicroStation file menu, Workspace>About Workspace, may not display the correct information. _USTN_PROJECTNAME remains undefined.

Edit Project Level CSB ‐ identify the Project CSB that was created from a project configuration file

(i.e. ArchProjectTemplateNcsUS, Structural_Imperial , Triforma_Imperial, etc…)

Locate the _USTN_PROJECTDESCR in the CSB file and add the following directive.

Add Directive to the project configuration CSB (i.e. ArchProjectTemplateNcsUS project CSB)

Directive: %include Description: Dynamic Project Name Add Value:

Value type: Configuration Setting Block Value: Dynamic_Project: Project Configuration File Block



Project: (Continued) Alternate Method: Project support for the standard ProjectWise Folders (works with ProjectWise Projects also)

In order to support .pcf files converted into a ProjectWise CSBs as they are supported in MicroStation, a new variable in the Project CSBs needs to be defined. The _USTN_PROJECTNAME is required to properly resolve the definition of _USTN_PROJECTDATA which is equal to $(_USTN_PROJECT)$(_USTN_PROJECTNAME) . The _USTN_PROJECTNAME configuration variable will need to be defined for each project CSB in order to properly support project content and datasets.

Add Variable to the project configuration CSB (i.e. ArchProjectTemplateNcsUS project CSB)

Name: _USTN_PROJECTNAME Description: Project Directory Name Add Value:

Operation Type: '='‐ Assignment Value Type: String Value: ArchProjectTemplateNcsUS (Value should correspond to the directory (folder) name in the PW repository)



Step 4: Add exclusions (variables to be exclude from copy‐out)

By default there are certain configuration variables that ProjectWise may not use when managed workspaces are in use. You can remove any of these variables so that ProjectWise will use them, or you can add to the list of excluded variables

In ProjectWise Administrator, under Workspace Profiles>Managed>Variables to exclude from copy out

Add the following additional Variables to exclude from copy out

MS_BUMP (Supports Visualization) MS_ROSEDB (Supports STEP import/export in MicroStation)

MS_ROSEDB_STRUCTURAL (Supports STEP import/export in Structural Modeler)

These files, defined by these configuration variables, will be excluded during the download of the workspace

Step 5 ProjectWise Application Support

ProjectWise Application Associations for Building Applications using the Program Class Name

Program Class Name ‐ A Program Class Name defines and stores, in the Windows registry both, the executable and any command line arguments as defined during the installation on the local machine. This is the most reliable and universal application definition since ProjectWise does not store any hard coded directory path information. Registry supports relies on the clients registry to provide ProjectWise with the proper drive/directory location of application to launch. This allows an organization to have the applications installed in varying directories and drive locations on the local machines and reduce the requirement of installation consistency across an organization. All other customizations can be accommodated through strategic definitions of CSB files. In the v8i 08.11.07 (SELECTseries 1) release of building applications, a registry based program class definitions to support Building applications was introduced. The corresponding v8i 8.11.7 release of ProjectWise will deliver the default building application definitions using these registry program class definitions. The program class name is the preferred method to define ProjectWise application support because it uses the Window registry to locate the designated executables. This is the recommended and most reliable method for building application initiation in a ProjectWise Managed Workspace.



In ProjectWise Administrator, under Applications:

1. Select on one of the building application and either double click or right‐click and select properties from the right‐click options menu.

2. Select, the Actions Tab, Select the default Open Action (indicated by the Open), then select the modify button

3. In the Modify Properties dialog, verify the Program Class name:



The following tables list the Building application and their corresponding Program Class name for v8i 08.11.07:

Bentley Architecture Bentley.Architecture.Application.081107

Structural Modeler (Bentley Structural) Bentley.Structural.Application.081107

Bentley Building Mechanical Systems Bentley.Mechanical.Application.081107

Bentley Building Electrical Systems (DE) Bentley.Electrical.DE.Application.081107

Bentley Building Electrical Systems (US) Bentley.Electrical.US.Application.081107

Bentley Building Electrical Systems (UK) Bentley.Electrical.UK.Application.081107

Bentley Building Suite Bentley.Building.Suite.Application.081107

Bentley SpacePlanner Bentley.MicroStation.Application Add command line Argument: ‐ws_SPACEPLANNER=1

Bentley Architecture w/ SpacePlanner Bentley.Architecture.Application.081107 Add command line Argument: ‐ws_SPACEPLANNERDG=1

4. If you need to edit or create a new program class association, select the browse button adjacent

to the program class entry field to open the 'Select Associated Programs' dialog. Select the Advance tab, and edit or enter the program class name.



Unfortunately, to date, there is no program class browser. These program classes will need to be populated manually during the Select Associated Programs. Once the program class is entered, Select the option designating the "Enter text is a program class name" and Select OK to save your changes and close the "Select Associated Programs" dialog.

5. Select OK to close "Modify Properties.." dialog. 6. Select OK to close the application properties dialog.



FOR BENTLEY ARCHITECTURE ONLY: Bentley Architecture requires the inclusion and assignment of the arch_roles CSB to either the Project or the Application to successfully initiate the Bentley Architecture Application. Please select the best method based on your environment and requirements. The preferred method is to attach the arch_roles via the Bentley Architecture definition in ProjectWise. Please note, If an arch_roles CSB is attached at both the application and Project, the arch_roles at the project will override those defined in the application.

Note: As mention previously, when the Workspace Root is defined at the ‘Predefined’ level, configuration files that are loaded into ProjectWise, as part of the workspace, are processed from within the ProjectWise repository. Since the building datasets are included into the MicroStation workspace, this issues extends to any configuration files located in the datasets. The out‐of‐the‐box installation of building application delivers only one configuration file, arch_roles.cfg, as part of the Bentley Architecture Dataset. Like the standards.cfg, it is recommended that the arch_roles.cfg be deleted from the datasets in the ProjectWise repository and allow configuration to be managed by the ProjectWise CSB version of arch_roles.

Option 1: Attaching the archroles per the Projector Project Configuration (Preferred Method)

Add the following Directive to all valid Bentley Architecture Projects (i.e. ArchitectureTemplateNcsUS & BentleyBuildingSuiteUS)

Add Directive Directive: %include Description: Arch_roles Support Add Value:

Value type: Configuration Setting Block Value: Arch_roles : Application Configuration File Block



Option 2: Attaching the arch_roles to the Bentley Architecture definition in ProjectWise

With this method, you may experience the following message switching between file that are not associated with the application "Bentley Architecture", because architecture is linked to the arch_roles CSB. It is not necessary to restart unless the file you are accessing is outside your project or other CSB are defined.

In ProjectWise Administrator, under Applications:

1. Select on 'Bentley Architecture' application definition and either double click or right‐click and select properties from the right‐click options menu.

2. Select the Managed Workspace tab and Add the arch_roles CSB to the Application level to the application definition

The arch_roles CSB should also be attached to the ProjectWise application definition for 'Bentley Architecture / SpacePlanner'



Step 6 Link CSBs to the Project

In the ProjectWise Explorer locate the project directory. (For example: pw:\\<server name>:<datasource name>\Documents\Building Workspace\ArchProjectTemplateNcsUS), right‐click and get the properties of this folder. Select the Workspace Tab

Associate to the project directories with Predefined CSB called "Building_WorkspaceRoot".

Associate to the project directories with the Global CSB called “Global_Variables”. Associate to the project directories with the appropriate Project CSB.

For example: the Project CSB called "ArchProjectTemplateNcsUS"

The result should be similar to the image below, (with/without Personal Workspace)

Personal workspace settings allows user‐specific workspace configuration for managed workspaces. By default, you may not have Personal workspace associated if there is nothing defined in your personal workspace, once something is defined in the personal workspace it is automatically associated. (To review the contents of your personal workspace CSB, in ProjectWise Explorer file menu select Tool>Options, select the Personal Workspace tab.

Note: The option, not to display the compatibility warning when building applications are initiated, is stored in your Personal Workspace.



Step 7 Test/Validate (Troubleshoot)

To test or Validate you Integration, in the ProjectWise Explorer, locate the project directory the delivered file empty.dgn in the project ArchProjectTemplateNcsUS (pw:\\<server name>:<datasource name>\Documents\Building Workspace\ArchProjectTemplateNcsUS). Associate the empty.dgn with the Bentley Architecture application by selecting the properties option from the right‐click menu. Then open the file and validate it is in a managed workspace, if it is properly configured you should see –

Manage Workspace Export Progress Dialog, which successfully completes all tasks

Note: Errors in the first three tasks usually are the result of an error in the application definition or association. Please validate the application definition in the ProjectWise Administrator. Note: Opening a managed project or application the first time will require ProjectWise to download the workspace and datasets locally, this can 5 minutes and up the first time depending on your connection speed. Please be patient, subsequent loads will have more acceptable load times.



From with the Building application, Select Workspace>About Workspace from the file menu.



Troubleshooting If you are presented with the following message to restart your MicroStation Session, then there is something different in the managed configuration that requires a change in your manage workspace.

This dialog is common and to be expected if you are opening files from another project. However, this dialog does not typically appear if you are opening different files from within the same project but from different subdirectories. If it does occur:

Verify that the files contain the same ProjectWise manage Workspace assignments. They should all be inherited from the Project Folder.

Verify that there is no ProjectWise Manage Workspace CSB assignments on the ProjectWise Application associated to the document. This alert will appear if you switch to a file that does not share the same application association as the original file opened and the application has a CSB assigned to the application definition.

Inspect your configuration files, any configuration variable defined to equal _DGNDIR or _DGNFILE will need to be add the exclusion list defined by PW_MWP_COMPARISON_IGNORE_LIST in the ProjectWise mcm.cfg file.



Configuring a ProjectWise managed Workspace for BBES V8i Detailed Path Configuration BBES builds prior to 8.11.7.5 used the configuration variable "BBESDATA" to point to the entire Bentley Building Electrical Systems dataset. All other directories below the main dataset folder (ElecDatasetNcsUS) were hard‐coded. This caused problems when trying to setup a ProjectWise managed workspace for BBES, because PW needs distinct configuration variables to determine what data needs to be downloaded to the local DMS folder on each machine. BBES 8.11.7.5 and later versions provide a mechanism that allows users to configure all relevant paths in the dataset individually. BBES is backwardcompatible with earlier versions of CFG‐files. To activate the detailed path configuration, we will create an additional configuration file bbes_PW.cfg. PW specific configuration can also be added to any existing pcf or cfg file. The first step is to set the variable BBES_DETAILED_CFG to 1. This variable must be set for BBES to read the detailed path settings and use them for data access. This Configuration variable can be set in any pcf or cfg file. Below is an example of a complete detailed path configuration for ProjectWise Managed electrical workspace in file bbes_PW.cfg:

BBES_DETAILED_CFG = 1 BBES_MWS_METADATA = $(BBESDIR)/METADATA/ BBES_MWS_IES=\\BldPS_PWISrv01\Project_Drive\TestProject\con_Docs\Standards\Project_Dataset\IES

;In order for light sources to be displayed in the model, this variable has to be set to folder outside of PW managed workspace that is accessible to all project participants. (Any easily accessible project specific network location)

BBES_MWS_SEED = $(BBESDIR)/SEED/ BBES_MWS_RES = $(BBESDIR)/RES/ BBES_MWS_SYMLIBNO = 080 BBES_MWS_SYMLIBS = $(BBESDIR)/SYMLIBS/ BBES_MWS_SYMLIB = $(BBES_MWS_SYMLIBS)$(BBES_MWS_SYMLIBNO)/ BBES_MWS_CSS = $(BBES_MWS_SYMLIBS)CSS/ BBES_MWS_VIS = $(BBES_MWS_SYMLIBS)VIS/ BBES_MWS_WIRING = $(BBES_MWS_SYMLIBS)WIRING/ MS_LIGHTING < $(BBES_MWS_IES)

Path Settings and Variables Below is a list of all variables and their default values when installing locally.

BBES_MWS_METADATA = C:\Documents and Settings\All Users\Application Data\Bentley\MicroStation V8i (SELECTseries)\WorkSpace\TriForma\Elecdatasetncsus\Metadata BBES_MWS_IES = C:\Documents and Settings\All Users\Application Data\Bentley\MicroStation V8i (SELECT Series)\WorkSpace\TriForma\Elecdatasetncsus\Metadata\IES BBES_MWS_SEED = C:\Documents and Settings\All Users\Application Data\Bentley\MicroStation V8i (SELECTseries)\WorkSpace\TriForma\Elecdatasetncsus\seed BBES_MWS_RES = C:\Documents and Settings\All Users\Application Data\Bentley\MicroStation V8i (SELECTseries)\WorkSpace\TriForma\Elecdatasetncsus\res BBES_MWS_SYMLIBNO = 080 BBES_MWS_SYMLIBS = C:\Documents and Settings\All Users\Application Data\Bentley\MicroStation V8i (SELECTseries)\WorkSpace\TriForma\Elecdatasetncsus\symLibs BBES_MWS_SYMLIB = C:\Documents and Settings\All Users\Application Data\Bentley\MicroStation V8i (SELECTseries)\WorkSpace\TriForma\Elecdatasetncsus\symLibs\080 BBES_MWS_CSS = C:\Documents and Settings\All Users\Application Data\Bentley\MicroStation V8i (SELECTseries)\WorkSpace\TriForma\Elecdatasetncsus\symLibs\CSS BBES_MWS_VIS = C:\Documents and Settings\All Users\Application Data\Bentley\MicroStation V8i (SELECTseries)\WorkSpace\TriForma\Elecdatasetncsus\symLibs\Vis



BBES_MWS_WIRING = C:\Documents and Settings\All Users\Application Data\Bentley\MicroStation V8i (SELECTseries)\WorkSpace\TriForma\Elecdatasetncsus\symLibs\Wiring

BBES_DBDIR should point to the project specific _bbes folder outside of ProjectWise. This location is user definable. This folder contains project specific database files that cannot be properly managed by ProjectWise at this point. Information about building structure, room spaces, elements count and mounting heights is stored in _bbes folder. To troubleshoot configuration issues with a ProjectWise managed workspace, refer to the bbes.ini file located at C:\Program Files\Bentley\MicroStation V8i (SELECTseries)\TriForma\ELECTRICAL\ServerApp\bin. The bbes.ini file is updated each time Bentley Building Electrical Systems is launched, and it will provide overview of all variables as shown in the example below: [PROJECTWISE]

BBES_DBDIR=\\BldPS_PWISrv01\Project_Drive\BBESProjects\TestProject\Con_Docs\_Standards\ Project_Dataset\BBES_Database\_BBES BBES_DETAILED_CFG=1 BBES_MWS_IES=\\BldPS_PWISrv01\Project_Drive\TestprojectManaged1\con_Docs\Standards\Project_Dataset\IES (noticethat this is location on the network outside of PW) BBES_MWS_SEED=pw://BldPS_PWISrv01.bentley.com:BLDPS_TEST/Documents/Workspaces/TS_Workspaces/TS_Dataset_09Q4b_v8i/Workspace/Dataset/TS_ELEC/SEED/ BBES_MWS_SYMLIBNO=080 BBES_MWS_SYMLIBS=c:\pwworkdir\dms00534\ BBES_MWS_SYMLIB=c:\pwworkdir\dms00535\ BBES_MWS_CSS=c:\pwworkdir\dms00539\ BBES_MWS_WIRING=c:\pwworkdir\dms00541\ BBESDIR_LOCALSETTINGSFOLDER=\\BldPS_PWISrv01\Project_Drive\BBESProjects\TestProjectMan aged1\Con_Docs\_Standards\Project_Dataset\BBES_Database\Electrical_Subtypes\ BBES_MWS_METADATA=c:\pwworkdir\dms00531\ BBES_MWS_VIS=c:\pwworkdir\dms00540\ BBES_MWS_RES=c:\pwworkdir\dms00533\

Symbol Libraries in PW Managed Workspace With the detailed path configuration activated, the number of symbol libraries that are accessible is restricted to one single library. The symbol library number is specified by the BBES_MWS_SYMLIBNO variable. The BBES_MWS_SYMLIB variable must point to the directory which hosts the files for the specified library. All BBES tools will only display the one specified library. If additional libraries are stored in the database they will not be visible. Selected symbol library is available in read only mode. Limitations of ProjectWise Managed Electrical Workspace If the electrical dataset is managed by PW, the following limitations will take place:

1) Only one symbol library can be used in a project. 2) No additional symbols or symbol subtypes can be created or existing ones modified. 3) Bidirectional Interface with Visual will not be able to update subtype definitions when lights are imported from Visual Professional. 4) No additional cable types can be defined 5) No additional tag styles can be defined or existing ones changed.

Further enhancements in ProjectWise managed workspace are currently in progress.