 |
Related Topics: |  |
 |
 |
|
 |
 |
 |
You can convert/import data from an RCM++ 5 database into a Version 8 database. This topic explains how to convert data from Version 5, including:
Converting Libraries: If you have not customized the settings in your Version 5 library, we recommend using the new default library that is shipped with Version 8. If you have customized the settings in your Version 5 library, you can automatically convert the library to Version 8. Since this conversion will add default settings for features that are new in Version 8, we recommend that you review these settings before using the converted library.
Converting Projects and Other Database Settings: With a Version 5 standard database, you can convert the entire database (including all projects and all database settings) to a new Version 8 database. With a Version 5 enterprise database, you can choose which specific database settings and projects you wish to convert and import to a selected Version 8 enterprise database. In either case, before beginning this process, you should be aware of a few details concerning how the software will convert certain kinds of information.
Updating the Configurable Settings for Converted Projects: When you convert a Version 5 project to Version 8, the software automatically adds settings for features that are new in Version 8. There are two ways to make sure that the converted project properties will fit your preferences: 1) reapply the profile to implement the latest settings from the active library or 2) separately review and update the new settings in every converted project.
The steps for converting a Version 5 library will differ depending on whether you are converting from a standard or enterprise library, and whether you're converting the entire library or just importing selected profiles (and all associated settings). Note that since Version 8 libraries include more settings than Version 5 libraries, the following defaults will be applied to any converted library/profile. You may need to review and modify these settings after the conversion.
The quantitative values defined in the occurrence and failure probability scales will be set to the same values specified in the default "RS DFR Focus" profile.
The same default PFD worksheet settings will be applied to every interface style.
The Op Sequence Number field will be added for function records in all interface styles. The new property will be disabled by default when an interface style is converted from Version 5 to Version 8, but you may wish to enable this field for any interface styles that will be used to perform process FMEAs.
All profiles will be set to use risk discovery questions. However, the risk discovery ratings defined in the Version 5 library will still be included in the converted profiles. Thus, you can easily edit a profile so it uses the same ratings defined in the old library by selecting Use Risk Discovery Ratings in the Profiles/Library Manager or Project Properties window.
Tip: To move information from a Version 5 library of one database type (i.e., standard or enterprise) to a Version 8 library of the other database type, first convert the Version 5 information to a Version 8 library of the same type. You can then use the Profiles/Library Manager to copy the new settings to the currently active standard/enterprise library.
With Version 5 standard libraries, you can convert the entire library or just selected profiles.
To convert an entire Version 5 standard library to Version 8, open any standard database, then choose File > Manage Repository > Profiles/Library Manager to open the Profiles/Library Manager. Click the Browse button in the top-right corner and choose Xfmea 5/RCM++ 5 Library (*.lb5) from the Files of type drop-down list, then select the Version 5 library file that you wish to convert. The software will create a new Version 8 file based on the old one, and the converted library will become active on your computer.
To only convert selected profiles (and all associated settings) from a Version 5 standard library and add them to the currently active Version 8 standard library, choose File > Manage Repository > Profiles/Library Manager, and then click the Import button on the Profiles page. See Import to Library Window.
Tip: If you did not customize any of the default library settings that were shipped with Version 5, it may be preferable to reset your Version 8 library instead of converting the Version 5 library. This way, you can use the most up-to-date default standard library without having to review the changes that would occur during a conversion.
To reset the library, open the Profiles/Library Manager and click the Reset Library button. This will create a new standard library with all the default settings that are shipped with RCM++ 8, and it will make this new library active on your computer.
To convert and import profiles from a Version 5 enterprise library, you must have the following permissions:
The “Admin” access level in the Version 5 database.
The “Manage all projects” and “Manage users and logins” permissions in the Version 8 database.
To begin the process, choose File > Manage Repository > Enterprise > Import from Prior Version.
In the Import from Version 5 Enterprise Database window that appears, enter the connection information for the database and click Connect. Under the Profiles heading, you can select to convert all the profiles in the library, or you can expand the list of profiles and individually choose which ones to convert. The selected profiles (and their associated settings) will be added to the library of the current database.
Note: If you wish to convert and import phrase sets, checklists, assumptions, surveys and DFR planner templates, you must select the Profiles check box to import the entire library. If you expand the list and select only some of the profiles, the software will only convert the selected profiles and the settings used by those profiles.
For SQL Server databases, the Create SQL Server login check box will be displayed at the bottom of the window. Select the check box if you want to create an individual SQL Server login when you create each new Synthesis user account. The SQL Server login will be created if a login does not already exist for the username and if you have the appropriate authority in SQL Server to create logins. If you clear this check box, the user can still be recognized by SQL Server if a) an individual SQL Server login was created in advance in SQL Server, b) the user belongs to an Active Directory group that has a SQL Server login shared by all members of the group or c) the user connects to the repository with an enterprise connection file (*.rserp) that impersonates another Windows user account that has a SQL Server login. See SQL Server Logins or Using Impersonation.
The steps for converting projects and other settings from a Version 5 database differ depending on whether you are converting projects from a standard or enterprise database. Instructions for both are presented below. In addition, please note the following:
Certain types of information in the Version 5 projects will be converted to resources in Version 8. This includes reliability information (which will be converted to models), controls, actions and tasks. In these cases, records that have identical properties will be merged into a single resource. For example, if there were two identical actions in the original project, a single action would be created as a resource in the Synthesis project and used in both locations.
For secure databases:
Repository-level security: User permissions assigned by access level in Version 5 will be assigned by the corresponding security group in Version 8. For example, if a user had the Admin access level in the original database, then that user will be assigned to the Admin security group in Version 8. If there is no corresponding security group in Version 8, the user will be imported with no security groups assigned, and a user with "Admin" access level permissions will have to manually assign security groups to the imported user.
Project-level security: For each access group in the Version 5 database, a security group will be created in the Version 8 database. Because the Version 5 access groups could have different access levels for different users in the same group, it is not possible to automatically determine which permissions should be assigned for the new security group in Version 8. Therefore, these groups will initially be assigned the default permissions; you can edit the permissions via the Security Groups tab of the Manage Repository Security window. Projects that had access limited by access group in Version 5 will continue to have their security set by the appropriate security group(s) at the project level in Version 8.
Tip: To move information in a Version 5 database of one type (i.e., standard or enterprise) to a Version 8 database of a different type, first export the Version 5 data to a Version 8 database of the same type. You can then use the Import Wizard to copy the converted projects to the current standard/enterprise database.
Convert To convert all the projects and other database settings in a Version 5 standard database, choose File > Open Repository, select RCM++ 5/Xfmea 5 (*.rx5) from the Files of type drop-down list, and then browse for the desired file. A new standard database will be created that includes all the projects from the old database and all the relevant database settings.
To convert projects and other settings from a Version 5 enterprise database, an authorized user must connect to a Version 8 enterprise database, choose File > Manage Repository > Enterprise > Import from Prior Version, and then select all the projects and settings from the Version 5 database that will be converted. These projects and settings will be added to the current database.
After you convert Version 5 projects to Version 8, they will include default settings for the new features that were added in Version 8. There are two ways to adjust these settings in the converted projects:
If the original projects used profiles that also exist in the active Version 8 library, and if you have already reviewed/updated all the new settings in the library, you can reassign the profiles to the projects. This allows you to quickly apply all the latest applicable settings in the library to the converted projects. To do this, use the Select Profile from Library drop-down list in the Project Properties window. For example, if the selected profile is [Based on DFMEA: AIAG-4], you could change it to DFMEA: AIAG-4.
If you prefer to manually review and update each project's settings, you can do so via the Configurable Settings tab of the Project Properties window.
© 1992-2013. ReliaSoft Corporation. ALL RIGHTS RESERVED.