Case description.
	CIMPLICITY project configuration.
	Managed characteristics configuration.
	User setup.
	Configuration changes guidelines.
	Exceptions

1. Case Description

Multiple users use Change Management.

Users do not use shared drives.

Users use separate local copies of the project.

2. CIMPLICITY Project Configuration

1. Create a project in CIMPLICITY.

2. Add all of the users who will need access to CIMPLICITY and/or Proficy Change Management to the new project.

3. Configure the CIMPLICITY project to perform according to your system specifications.

3. 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.	Check Prompt for user name and password at logon. Make sure there is a unique user name for each PCM user who may be performing the configuration.
	CIMPLICITY/PCM user names and passwords are the same.	Clear Prompt for user name and password at logon. Make sure there is a unique user name for each CIMPLICITY/PCM user who may be performing configuration.
2	Check Require check out before changes.

3. Add the CIMPLICITY project to the Change Management server.

4. 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.

2. Enter the PCM Server name and name of the project to be fetched.

3. Select a unique directory location for the project.

4. Configure the characteristics to match those specified on the original project.

5. Configuration Changes Guidelines

Always follow these guidelines when performing configuration changes:

Always close all configuration applications before performing a check in operation, when performing configuration transactions.

Perform a check out of the item(s) before beginning application changes.

Never check Don't overwrite local files with managed copy when performing a check out operation.

Never check Don't overwrite local files with managed copy when performing an undo check out.

Never share PCM user names with different users.

6. 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.

More information

1. Best practices: Initial development.

---