quick start

RuleManager V8 Quick Start

Copyright 19992013 Axiom. All Rights Reserved. Page 1 of 6.

Quick Start ObjectivesThe purpose of this Quick Start is to introduce you to the basic features of RuleManagerso that you can immediately use the program.

This Quick Start should take less than 30 minutes.

Prerequisites1. MicroStation V8 version 8.1 or later.

2. RuleManager must be installed on your computer. You can verify this by selectingthe Axiom menu from MicroStations main menu bar, then select RuleManager. IfRuleManager does not appear in the Axiom menu, follow the instructions in theInstallation chapter of your User Guide.

3. You will need some design files to practice with. The sample files that are deliveredwith RuleManager are used in this quick start.

4. You can run RuleManager with any production file.

Demonstration VersionDemonstration versions of RuleManager expires after 30 days.

Licensed versions of RuleManager do not have this restriction.

The BasicsThis Quick Start will briefly introduce:

How to use RuleManager to create your own rules.

Quick Start Step 1 Automatic design file analysis and rulesgeneration.

RuleManagers Automatic design file analysis and rules generation is accomplished byusing one or more of your design files as a template a model file which is known toadhere to your standards. RuleManager automatically generates rules based on thecomposition of the specified file(s).



1. Install RuleManager as described earlier.

2. In MicroStation, open the provided rulemgr3.dgn:

C:\Program Files\axiom\v8\rulemgr\sample\rulemgr3.dgn3. Load RuleManager from the Axiom menu.

Your main RuleManager dialog box should look like this:

4. From the drop down menu in the Action field, we will use the default, Automaticdesign file analysis and rule generation as seen in the image above.

5. The active design file name, rulemgr3.dgn, will already be selected in the DesignFile(s): field.

6. The program will suggest a Rules File name. In this case we will use the suggestedrulemgr3.rul name. To use a different name or location, click the {Select} buttonand specify a name for the rules file to be created. Remember the name well needit to view the file contents later.

7. Select Rule Generation Options from the Options pull down menu at the top ofthe dialog box.



The displayed Rejection message is the default, user-definable message that will beused for all rejections. The symbols like %TY and %LV are called messagevariables, and these two will display the type number and level number of anyelement that is rejected using this rules file. You can retype this message to suit yourneeds. There are more than 100 message variables you can use all described laterin this document.

Other fields on this dialog box represent element characteristics that are important toyour Quality Control process. By turning them on and off or making differentselections you can control which element properties the generated rules file willcheck. For example, if you un-check Cell name, the generated rules file will notcontain rules that check for valid cell names.

8. Click the {OK} button to close this options box.

9. Click the {Start} button. The new Rules File is generated based on the elements inthe active design file, rulemgr3.dgn.

10. When processing is complete, you can use RuleManagers Rule Wizard to view (oredit) the rules that have been automatically created. Select Edit a rules file from theAction menu button and then click the {Start} button to activate the Rule Wizard.

The guilty until proven innocent approach is used in building the rules (See thesection of this manual titled, The Rules File, for more information). RuleManagerbegins the file with REJECT ALL. This statement is followed by the rejectionmessage that will display for all rejected elements.

Next, RuleManager inserts some default rules which accept the non-graphicalelements that are present in all design files, sets some default runtime options andmakes allowances for accepting the components of complex elements, allowinginvisible elements that MicroStation uses behind the covers, etc.

Finally, RuleManager inserts the rules generated from the elements in your templatedesign files. Scroll down to see some of these rules.



11. You can use the Rule Wizard to change, add, or delete rules but were using it fordisplay only in this step. Press {Close}. See the section titled Rule Wizard for moreinformation.

12. You can now use the rules file just created with SpecChecker or SpecMonitor.

Note: The above steps are intended to quickly show you how rules can be generatedautomatically with RuleManager. The remainder of this RuleManager SystemAdministrators Guide explains rules and other features in detail.

Additional examplesAdditional rules file examples are provided in the folder:

...\axiom\v8\checker\sample\

Quick Start Step 2 Automatic DGN library analysis andrules generation.

RuleManagers Automatic DGN library analysis and rules generation is accomplished byusing one or more of your DGN libraries as a template for creating rules that verify thelevel settings contained in your project design files level table, that verify graphicelement symbology, that verify text uses the correct text style name and that dimensionelements use the correct dimension style name.

1. In MicroStation, open the provided Civil.dgnlib:

...\axiom\v8\rulemgr\sample\civil.dgnlib2. Load RuleManager from the Axiom menu.

3. From the Action drop down menu choose {Automatic DGN library analysis andrule generation} as seen in the image above.

4. The active DGN library name, civil.dgnlib, will already be selected in the DesignFile(s): field.



5. The program will suggest a Rules File name. In this case we will use the suggestedcivil.rul name. To use a different name or location, click the {Select} button andspecify a name for the rules file to be created.

6. Select Rule Generation Options from the Options pull down menu at the top ofthe dialog box.

7. Now select DGN Libraries from the list box on the left side of the dialog box.

There are 4 separate sections for creating rules using DGN libraries. All 4 sectionsare turned on by default. Click the {Restore Defaults} button to set the defaults.

The displayed Rejection message: for each section is the default, user-definablemessage that will be used for all rejections pertaining to that section of rules. Thesymbols like %TY, %LV and %Level_Color are called message variables.When an element is rejected by a rule using them, these variables will displayspecific information like the element type number (%TY), the elements levelnumber (%LV) and the byLevel color of a level table entry (%Level_Color). You canretype these messages to suit your needs. There are more than 100 message variablesyou can use all described later in this document.

Other fields on this dialog box represent element or level table characteristics that areimportant to your Quality Control process. By turning them on and off or makingdifferent selections you can control which element or level table properties thegenerated rules file will check.



8. Click the {OK} button to close this options box.

9. Click the {Start} button. The new Rules File is generated based on the level table,text style table and dimension style table stored in the selected DGN librarycivil.dgnlib.

10. When processing is complete, you can use RuleManagers Rule Wizard to view (oredit) the rules that have been automatically created. Select {Edit a rules file} from theAction menu button and then click the {Start} button to activate the Rule Wizard.

The guilty until proven innocent approach is used in building the level table andgraphic element rules (See the section of this manual titled, The Rules File, for moreinformation). RuleManager begins the file with two REJECT rules. One thatrejects each named level in the master files level table and one that rejects allgraphic elements in the model. Each of these reject criteria statements is followed bya generic rejection message that will be displayed or reported for all rejectedelements.

Next, RuleManager inserts the ACCEPT rules generated from the tables in yourDGN libraries. Scroll down to see some of these ACCEPT rules.

11. You can use the Rule Wizard dialog and controls to change, add, or delete rules but were using it for display only in this step. Press {Close}. See the section titledRule Wizard for more information.

12. You can now use the rules file just created with SpecChecker or SpecMonitor.

Note: The above steps are intended to quickly show you how rules can be generatedautomatically with RuleManager. The remainder of this RuleManager SystemAdministrators Guide explains rules and other features of the Rule Wizard in detail.

Quick Start ObjectivesPrerequisitesDemonstration VersionThe BasicsQuick Start Step 1 Automatic design file analysis and ruleAdditional examplesQuick Start Step 2 Automatic DGN library analysis and rule

quick start

Documents