An asset corresponds to a portfolio item whose nature has the management constraint: Unique asset tag ( Management constraint). The Unique-asset-tag management constraint means an asset will be managed individually (individual management).
In the database, an asset is represented by a record in the Assets table and a record in the Portfolio items table.
Other than the General, Portfolio and Project domains of Assets, the Assets table concern different domains of tracking:
3) Fixed assets
2) Maint. (maintenance)
Portfolio item users
For each portfolio item, you need to choose between 2 modes of user management
1) Assign a single user
2) Assign a principal user and secondary users (Shared portfolio item box (bUsers))
Find all portfolio item users
When searching for all portfolio item users (filter or request, for example), think of referring to the following links: User (User) and Users (Users).
Models, which are based on natures, enable you to organize your portfolio items.
Depending on your requirements, models can go from very generic to very specific.
Example of organization of software models
The following example represents a way of organizing your software models:
1) All the software models are based on a nature that creates a portfolio item.
The management constraint depends on the way you want to manage your
software: individually, by batch or by untracked batch.
2) A generic Software model is created.
3) Sub-models enable you to classify software according to their use: Office
automation, ERP, Project management, etc.
4) Other models are created for the Office Automation sub-model for specific
applications:Word processor, Spreadsheet, DTP, File Management.
5) Models created at the bottom of the hierarchy correspond to specific models
which can be used to create individual software items in the Portfolio items
table: Software/Office Automation/Word processor/Microsoft Word 2000.
Natures are required to create the models that you use to create the portfolio items. Because the nature governs the management constraints of the portfolio items, you must create as many natures as you require for a given type of portfolio item.
Example: If you manage software as assets, batches and untracked assets, you must create three corresponding natures: Software, Software (batch), Software (untracked batch).
It is recommended to create as many natures as there are models of portfolio items.
1) Natures (amNature)
2) Models (amModel)
3) Portfolio items (amPortfolio)
4) Assets (amAsset)
5) Computers (amComputer)
6) Software installations (amSoftInstall)
7) Telephones (amPhone)