Appendix C: Product Licensing FAQ

Appendix C

Product Licensing FAQ – RAM Structural System

The RAM Structural System is composed of several modules, each of which has their own licenses. The program also contains links to two related Bentley products, RAM Concept and RAM Connection, providing design interoperability, as well as a link to Bentley’s ProjectWise for project management. Each of those programs also have their own licenses. It is possible to have several licenses of one or more modules, and few or no licenses of other modules. Because of the ease with which these various modules and programs can be invoked, a method of restricting the use of each has been incorporated in order to prevent unwanted or inadvertent usage by an unsuspecting user from being logged against the licenses that the company actually owns.

These modules are invoked using the tool bar buttons on the left of the RAM Manager screen:

or by using the Model or Design menu items:

If RAM Concept or RAM Connection are not installed, they will not be available to be selected.

There is no license associated with RAM Manager, so no usage data is logged against it, but usage data is logged against each of the other modules as soon as they are invoked.

There is no demo version available for the RAM Structural System modules.

In RAM Manager, the Tools – Manage License Restrictions command opens the following dialog:

This provides a mechanism for the user to prevent a module from being inadvertently executed. When the program is first installed all of these options are selected. It is important therefore to execute this command and deselect any modules or links for which the user wants to restrict access.

To prevent a module or program link from being executed, deselect that item.

If a module is deselected here and that module or link is subsequently invoked, the following dialog appears:

If Allow is selected the module will open, and usage will be logged. If Cancel is selected the module will not open and no usage will be logged. Settings opens the previous command, allowing the user to modify the selections of the allowed modules.

Versions prior to V14.07 lacked the ability to manage these license restrictions, restrictions could only be achieved by deleting the module from the installation Prog directory. If you are using an earlier version and want to prevent use of a module, delete the file(s) listed here for the module to be prevented: