Case 1.1. Multiple Users, Non-shared Drives

1 Case description.
2 CIMPLICITY project configuration.
3 Managed characteristics configuration.
4 User setup.
5 Configuration changes guidelines.
6 Exceptions

Case Description

  • Multiple users use Change Management.
  • Users do not use shared drives.
  • Users use separate local copies of the project.

CIMPLICITY Project Configuration

  1. Create a project in CIMPLICITY.
  2. Add all of the userswho will need access to CIMPLICITY and/or Change Management to the new project.
  3. Configure the CIMPLICITY project to perform according to your system specifications.

Managed Characteristics Configuration

  1. Select the Change Management tab in the Project Properties dialog box.
  2. Do the following.
1 PCM user names and passwords vs. CIMPLICITY user names and passwords. CIMPLICITY/PCM user names and passwords are not the same.
2 Check Require check out before changes.
  1. Add the CIMPLICITY project to the Change Management server.

User Setup

  • For Computer level projects
  • On the same computer:

The computer level project is the same.

  • On different computers:
  1. Click Computer>Properties>Manage>Logon on the Workbench menu bar.
  2. Configure the characteristics to match those specified on the original project log in as a unique PCM user.
  3. Right-click the entity.
  4. Select Manage>Get Latest Version on the Popup menu.

Note: This will impact other computer project on the computer to which these files were fetched.

  • For CIMPLICITY projects
  1. Click File>Fetch Project on the Workbench menu bar.

The Fetch Project dialog box opens.

  1. Enter the PCM Server name and name of the project to be fetched.
  2. Select a unique directory location for the project.
  3. Configure the characteristics to match those specified on the original project.

Configuration Changes Guidelines

Always follow these guidelines when performing configuration changes:

Exceptions

Failure to follow these instructions can result in one user overwriting another user’s changes or an incoherent project as a result of concurrent changes.