Recommended sequence to import data

A general sequence to import data is recommended so that you can adequately define the relationships between objects as you capture data. For example, it is important to have users and organizations in the database to specify the responsibilities that they have for assets in the IT landscape. Therefore, some assets (objects) should already exist in the repository so that you can define an asset's relationships to other assets. P

Here is an explanation of some of the categories of assets that are useful to have in the repository in order to be able to efficiently capture data about your most important IT artifacts like applications and components:

1. Users and user groups: This is the first data that must be captured so that the user community can access Alfabet. This allows you to specify access permissions to objects as well as the users (class Person ) that have a functional responsibility for the objects. Users and user groups may already exist in the database if they were defined in the Manage User Access view.

2. Organizations, locations, vendors, physical servers, and virtual servers: This structural information is necessary to describe who owns assets and where they are located. This data can be imported by a user with the Portfolio Admin user profile. It can also be manually captured by a user with the Portfolio Manager user profile.

3. Business capabilities, business processes, business data, and application groups: These assets are necessary to be able to capture information about applications in the IT landscape. Whether your company captures how applications support business capabilities or business processes will depend on your company's methodology. This data can be imported by a user with the Portfolio Admin user profile. It can also be manually captured by a user with the Portfolio Manager user profile.

4. IT capabilities: IT capabilities are necessary to be able to capture information about components in the IT landscape. This data can be imported by a user with the Portfolio Admin user profile. It can also be manually captured by a user with the Portfolio Manager user profile.

5. Project groups: These assets are necessary to be able to maintain and analyze projects focused on IT change.

6. Applications, components, projects: With the structural data mentioned above already in the repository, you will be able to specify the most important information in XLSX files for the applications, component, projects, etc. in your IT portfolio.

7. References between the assets in the repository: A solid dark arrow diagram element displayed in the Data Roundtrip view represents a reference between two object classes. These relationships between assets can be documented in XLSX files. Typical references that should be documented include:

Working through this sequence ensures a high level of data quality and data completeness so that the results of business questions and other reports will be meaningful.

Copyright © Software GmbH   ContactPrivacyImprintLegal Aspects