How to use Library Objects

Hi Ms Jan de Groot,

I think the first thing to do is to draft a 'Modeling Convention Document' whereby you will specify important modeling rules. One of which can be for example:

'Modellers are requested to use the following object from the library:

• Person Type / Position
• Application System Type
• Organisation Unit
• Organisation Unit Type

In not circumstance should a Modeller create any of the above object without informing the Administrator'

Well you can re phrase the above of course:) but stress on the fact that non of these objects are to be created by Modellers. 

Then after doing this, you as an Administrator you can create the above objects in the said library.

You can also lock the objects in your library so that non of the Modellers can change the object name.

The above is just an idea of how to go about it:)

I currently use the 'Modeling Convention Document' and lock objects functionality in our organisation.

At start I came across the same problem you are having but soon after I made it clear to Modellers the importance of using specific objects from the library. I also ensure that all Modellers abide to the rules defined in the 'Modeling Convention Document'. 

As for the Modellers, they will not have any trouble finding the right object name because they just have to type the first 3 letters of a 'Person Type' for example and a pop up will all the 'Person Type' object will be displayed. The Modeller will then have to select the one needed from the library location.

The steps are quite simple:

1. Select the appropriate object - e.g Person Type
2. Type the first 3 letters - e.g. 'Tel' for 'Teller'
3. Click on the '...' -  see below

4. The following pop up will be displayed

5. Choose the appropriate 'Person type'.

Also don't forget to perform a consolidation of objects from the library and reorganisation of DB often :)

Hope the above helps.

Cheers

Shameem

Using the ... search when creating an object on the model works fine when you have a reasonable idea of the name of the object you care looking for. One downside is that it searches the entire DB instead of just the "official" library group. It never ceases to amaze me how quickly an object can proliferate through an ARIS DB. In a multi-modeler environment it is easy for folks to pick up and make use of objects that are created by others which may not be the "official" version from the library. 

There are other ways to use existing objects. You can use the Navigation window in Designer and click the Objects check box on. You can then navigate to the library and scan the entries to find the one you need and drag and drop it into your model. You can also use the Explorer to find multiple objects and copy and paste them into your model. This works really well when you have little or no knowledege of the name of the object, especially if you are using a newer version with Rocket Search. Of course you can also copy and paste from one model to another if you have built Application models.

There is no way in ARIS to stop people from creating their own objects of a specific type.  You have to establish modeling proecdures as mentioned above. By managing permissions (read only on the libraries) you can at least control who creates the official version of the object.

Hi,

I am pretty new with ARIS. I have a question about the library. In our library I come across at least 100 'OR' rules, 'XOR' rules and 'AND rules.

This does not sound really logical, but since I am new to this, I wonder if this is considered to be normal. If it is not normal to have so many rules in a library folder, what are the options to limit this. What are the consequences if changes are made?

Best regards,

Nancy Wong