IT capabilities are structured in an IT capability hierarchy. Before you begin, you should consider which IT capabilities are your main IT capabilities and which are their subordinate IT capabilities. It is recommended that you conceptualize your IT capabilities in a hierarchy with at least two levels. The top two levels of IT capabilities are analyzed in the context of various business questions in Alfabet FastLane.

Start with the main IT capabilities in your company and assign each of these IT capabilities a number such as 1, 2, and so on. Next consider the subordinate IT capabilities below each top-level IT capability and assign a logical numerical system: 1.1, 1.2., 1.3, etc. For example, Servers, Database, and Programming Languages would be typical high level IT capabilities with Level ID attributes set to 1, 2, and 3 respectively. The IT capability Servers ( Level ID = 2) might have the subordinate IT capabilities Application Servers ( Level ID = 2.1), Web Servers ( Level ID = 2.2), and Messaging Systems ( Level ID = 2.3).

In the navigation panel, click Technology Architecture > IT Capabilities to open the explorer for IT capabilities.​

Add a new root-level IT capability. Click the root node of the explorer and click New button to open the wizard to create a IT capability.

Add a subordinate IT capability. Click the parent IT capability in the explorer, go to the Overview tab and open the Sub-Domains view. Click New > Create New IT Capability to open the wizard.

Change the parent of a IT capability. In the Sub-Domains view, click New > Move Existing IT Capability Here to open a selector where you can chose the IT capability to move to the new parent IT capability.

Edit an existing IT capability. Select the checkbox   for the IT capability 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 IT capability.

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

• Level ID: (Recommended) Enter a level ID for the IT capability in the IT capability hierarchy. Each IT capability should be assigned a number in the Level ID attribute. The IT capabilities will be displayed in alphabetical and numerical order. You can leave this attribute empty at first and assign the level ID to your IT capabilities after they have been created.
• Name: (Mandatory) The name of the IT capability. The name should capture an abstract description of what is done to meet it the company's technological objectives.
• Description: Provide an explanation about the IT capability.

Ideally your company has documented its components. Components should already be in the repository in order to define the component that supports the IT capability. Some business questions in Alfabet FastLane can only be answered if the relationships between components and IT capabilities are defined. component A component is a reusable block of functionality that provides technical functionality to the application or to the platforms that an application runs on. Components do not usually provide functionality to end users. Typical components are operating systems, database management systems, or application servers.

Component support the company to realize its IT capabilities. For each IT capability, you should specify the components that support the IT capability in order to understand how the IT infrastructure may be at risk due to IT failure.

1. In the navigation panel, click Technology Architecture > IT Capabilities to open the data workbench for IT capabilities.​
2. Select the checkbox  for the IT capability you want to edit and click the Edit    button to open the wizard.
3. Click the Edit button to open the wizard and select Components in the Go to Step field.
4. Click New > Add Existing Component to IT Capability. Select the compnents that provide support to the IT capability and click OK. Click Next in the wizard to save your changes.

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.