Asset Management
Introduction
The optional CoreOne Asset Management module enables you to manage any sort of assets and integrate them in existing processes such as on- and off-boarding. The type of assets and the information that you would like to store about them is not limited, you can create them dynamically and according to your use case.
Asset Types
Before you can start creating assets, you need to define an appropriate asset type. The asset type defines which attributes are being stored about a specific asset. You could create an asset type Phonenumber
where you simply store the phone-number in. Or you could create a more complex asset type like a Mouse
where you store the serial-number, the manufacturer and other Attributes.
When creating an asset type, you need to define the following properties.
Property | Description |
---|---|
| Defines the name of the asset type |
| How many times an asset can be assigned. A phone number may be assigned only once. A shared car may be assigned up to 5 times. |
| After how many assignments a warning should be displayed. |
| The display attribute that should be used to display an asset of said type. |
Asset Group
Each asset needs to be assigned to an asset group. The asset group simply groups multiple asset into a logical group. You can use this to group assets according to your needs. For example group Access Keys
into groups that represent the building they belong to or group Phone-numbers
into Ordinary and VIP numbers.
When creating an asset group, you need to define the following properties.
Property | Description |
---|---|
| Defines the name of the asset group |
| To which asset type the group belongs to |
| If an object has more than one asset of said type assigned to it, the weight will determinate which one should be used. Let’s say a Core Identity works at two offices and would receive phone numbers from two groups. The one with the highest weight will be assigned. |
| Who the owner of the group is. |
Assets
As soon as you have created the asset type and the asset group, you can start creating or importing assets. There is a new menu entry for each asset type that you created. By selecting that entry, you will get a list of all present assets, their group and their current status.
Asset status
There are a couple of asset status available:
State | Description |
---|---|
| The asset is not assigned to anything. |
| The asses is assigned to an object. |
| The asset is assigned to an object that is not managed by the CoreOne Suite. This could be for example an old hardware phone that has a phone number assigned to it. Said hardware phone does not have any API to interact to so we can not manage it automatically. |
| The asset is reserved and will not be assigned automatically to an object. |
| The asset was assigned to an object that is no longer present or valid. |
| The asset has been deleted. |
Create an asset
You can create assets either by selecting the create button in the list or by uploading an excel list. When uploading an excel list, you simply have to map the columns in the excel to the appropriate attribute.
You can only import assets for one specific assignment status and asset group at a time.
You can also import assets and automatically assign them to existing objects based on a mapping. You simply select the appropriate identity type and the matching attribute. For example you could have an excel list with the phone number and the SID of the assigned user. Map this in the following fields:
Attribute | Description |
---|---|
| The identity type that is used for the assignment lookup |
| In which column of the excel the identity identifier of the selected identity type is stored. When choosing an AD type for example, this column should contain the SID of the user. |
| In which Core Identity attribute the assignment should be stored in |
Asset Assignments
You can assign an asset to any object that holds an appropriate attribute for it. Let’s say you want to store a phone number on a Core Identity . You first need to create a new attribute of type Asset Type
. Let’s call it Primary Phone Number
. Then assign that newly created attribute to the appropriate Core Identity type.
Manual assignments
You can select any available phone number (status not assigned
, reserved
or vacant
) when creating or updating a Core Identity of the selected Core Identity Type.
Automatically assignments
You can also automatically assign assets to an object. The easiest way to achieve this is to pack the asset into Role. On the detail page of a role there is a tab called assets. On that tab you can create automatic asset assignments. You simply specify from which asset group an asset should be taken and choose on which attribute of the Core Identity the asset should be assigned to.
If you then map that role with an assignment to an organization unit you can achieve use-cases like assign a phone number from the IT Group to any employee that works in IT and assign it automatically to the Primary Phone Number
attribute.
Assignment removal
As soon as an object like a Core Identity gets deactivated or a Resource get’s deleted, the assigned assets are being released.
© ITSENSE AG. Alle Rechte vorbehalten. ITSENSE und CoreOne sind eingetragene Marken der ITSENSE AG.