In the navigation panel, go to Virtual Servers to open the data workbench for virtual servers.

Add a new virtual server. Click the New button to open the wizard.

Edit an virtual physical server. Select the checkbox   for the physical server you want to edit and click the Edit    button to open the wizard. The Go to Step ​ field displayed at the bottom of the wizard should show Basic Data so that you can capture the mandatory information about the virtual server.

Define the virtual server's basic data. Define the following fields in the wizard and click OK or Next to save your data. All mandatory fields must be defined to create the virtual server and save it.

• Name: (Mandatory) Enter a unique name for the virtual server.
• Version: (Mandatory) Enter a version number for the virtual server. The name and version number of the virtual server should be unique.
• Start Date and End Date: (Mandatory) The start and end date captures the period when the virtual server is actively running and can be used in the company. This is also when the Object State attribute should be specified as Active. Click the calendar icon to select the date or enter the date in the date format Month/Day/Year. For example: 4/30/2023
• Release Status: (Optional) This is an approval status and typically indicates the level of quality of the information about the virtual server. The release status determines whether a virtual server can or cannot be deleted. Possible values are:
  • Draft: The virtual server has only mandatory data defined.
  • Under Review: The virtual server is documented and being reviewed. A virtual server with this release status cannot be deleted.
  • Approved: The virtual server has been approved by the responsible stakeholders. A virtual server cannot be deleted when it has an approved release status. A virtual server with this release status cannot be deleted.
  • Data imported: The data regarding this virtual server has been imported from an external system. Additional changes may be required to improve the data quality. A virtual server with this release status can be deleted.
  • Trash: The virtual server is no longer valid and can be deleted.
• Object State: (Mandatory) The object state describes the use of the virtual server in the real word. This can be understood as the operational status of the virtual server. Possible values are:
  • Plan: The virtual server is proposed to be used and still in the stages of planning and building.
  • Active: The virtual server is currently and used now. The active period begins with the virtual server's start date and ends with the end date.
  • Retired: The virtual server is no longer used

  The object state should be changed from Plan to Active once the virtual servers start date is reached. It should be changed to Retire when the virtual server's end data is reached.

• Server Type: Select whether the server is an application server, Web server, mail server, FTP server, collaboration server, or another type of server.
• Physical Server: Select the physical server that the virtual server runs on.

  physical server

  A physical server is a device that deploys applications and components. Virtual servers may run on physical servers that are located in different locations around the world.

• Description: Enter a meaningful description that will clarify the purpose of the virtual server.
• Authorized Access tab: The user who creates the virtual server is the authorized user per default. This can be changed. Select one or more authorized user groups that shall have write permissions to the object. All users in the authorized user group can edit the virtual server.

  authorized user

  An authorized user has primary responsibility to maintain the data for an object. Typically this is the user that has created the object. The authorized user as well as members of authorized user groups have write permissions to objects they are responsible for.

  authorized user group

  An authorized user group is a set of users that have been granted write permissions to an object. More than one authorized user group may be specified for an object.

In contrast to the concept of an authorized user or authorized user group which grants read/write permissions to an object, roles which are fulfilled by people or organizations may also be specified for an object. The role definition specifies the functional relationship or responsibility that a user or organization has to an object. The specification of a role is primarily for documentation purposes and provides additional information about stakeholders interested or responsible for the object. A person assigned to have a role for an object will not have read/write permissions based on the role definition. If the user shall have read/write permissions, they must be assigned to an authorized user group specified for the object.

Alfabet FastLane provides out-of-the-box role types that enable you to understand who is responsible for your IT assets in your IT portfolio. Additional role types that are relevant for your company can also be added.

Assigning users and organizations to roles is critical to understanding responsibility for assets in the IT and is required to answer the business question Who is responsible for our assets? 

To define the users and organizations that have a role for an asset, navigate to the data workbench where the asset is defined. You can either:

• Click the Edit button to open the wizard and select Responsibilities in the Go to Step field
• In the data table, click the navigate  button of the asset you want to define. Click Overview and scroll to the Responsibilities page and open it.

Define the users that have a role for an asset. In the toolbar, click Person to associate a user with the asset. The user can have one of the following roles or a custom role added by your company:

• Architect: A person who is responsible for the governance of the asset.
• Business Owner: A person or organization that owns the asset and is responsible for managing the functional requirements.
• IT Owner: A person or IT organization that owns the asset and thus typically responsible for approval decisions.
• Stakeholder: A person or organization that has an interest in the asset and therefore requires read-only access permissions.

In the selector, find the user to assign the role to and click OK.

Define the organizations that have a role for an asset. In the toolbar, click Organization to associate an organization with the asset. The user can have one of the following roles or a custom role added by your company:

• Business Owner: A person or organization that owns the asset and is responsible for managing the functional requirements.
• IT Owner: A person or IT organization that owns the asset and thus typically responsible for approval decisions.
• Operations: An IT organization responsible for the operations of the asset.
• Stakeholder: A person or organization that has an interest in the asset and therefore requires read-only access permissions.

In the selector, find the organization to assign the role to and click OK.

A generic attribute is a custom attribute that allows the ad-hoc capture of information for an asset. An administrator user may have already created predefined custom attributes that are relevant for an object class. The preconfigured generic attribute can be added to an asset (object) of the respective object class. For example, the generic attribute Rationalization Status could be configured to capture whether an application is in the scope of rationalization activities. Thus it would be assigned to the class Application with a default value set to False. As an authorized user of an application, you can add this attribute to your application and change the value if you want to.

You may also create your own generic attributes for an asset you are working with. You can also copy generic attributes created for other assets of the same class as the one you are working with and change the value.

in the context of the Generic Attributes view for the object.

To define a generic attribute for an asset, navigate to the data workbench where the asset is defined. In the data table, click the navigate  button of the asset you want to define. Click Overview and scroll to the Generic Attributes page and open it.

Add a preconfigured generic attribute to the asset. Click New > Add Generic Attributes from Class Configuration. Change the default value in the Value field as needed. The values that may be specified will depend on the type of property defined in the Type field.

Create a new generic attribute for the asset. Click New > Create New Generic Attribute. Define the following fields and click OK:

• Name: Enter a name that is easy for other users to understand.
• Type: Select the type of property that the generic attribute is. The field will display standard property types and enumerations. If you select an enumeration, the enumeration values will be displayed in the Value field.
• Value: Specify the attribute value for the selected object class. The values that may be specified will depend on the type of property defined in the Type field. Other users might copy this attribute. The value you define will be the default value but they will be able to change it for their asset.

Copy an existing generic attribute from an asset based on the same object class. Click New > Copy Existing Generic Attributes. In the selector, select the assets that have the generic attributes you want to copy to your asset and click OK. You can change the value as needed.

You can attach documents to objects in Alfabet FastLane in the Attachments view available in object profiles.

To define a generic attribute for an asset, navigate to the data workbench where the asset is defined. In the data table, click the navigate  button of the asset you want to define. Click Overview and scroll to the Attachments page and open it.

Upload a document to the asset.

Click New > Add Document. Select the file from your local drive and click Upload. The document is displayed in the data table.

Note that when you upload a document, you must ensure that the document is not encrypted. Encryption might be caused by Microsoft™ Information Protection. Only documents with the sensitivity label "Public" can be uploaded. Other reasons for encryption might also apply due to your company's security policies. The following file types are allowed: .xlsx, .doc, .docx, .ppt, .pptx, .pdf, .zip, .png, .jpg, and .json The following file types are not allowed: .exe, .bat, .cmd, .ps1, .txt, .xml, .wsdl, .html, .svg

Add a URL to the asset. You can define a URL for the selected object. The user must have access permissions to the document and have access to the network path specified in the link and, typically, be in the same network domain.

• Title: Enter a meaningful title for the URL link to help users understand why you included this URL with the selected object.
• URL: Enter a valid URL starting with the prefix https://www. or http://www. The URL link may contain up to 511 characters. The user’s Windows® environment must be able to identify the document extension and identify the correct application to open the document. A validation will be executed to ensure that a new URL is well-formatted and does not contain a period <.> without a leading or trailing blank space.

The following browsers support opening the files via the Web link definition in Alfabet FastLane: Microsoft® Internet Explorer® 11.0 and Microsoft® Edge® in conjunction with Windows® 10. Mozilla® Firefox® 24.0 or higher including Mozilla® Firefox® Quantum are also supported but require additional configuration in the browser settings.