Capture component data

Users with the user profiles Technology Manager, Portfolio Manager, and Portfolio Admin can add and edit components in Alfabet FastLane. Click for an overview of permission concepts.

A component is a reusable block of functionality that is implemented by software. Applications are built on components that provide the technologies that enable the applications.

In Alfabet FastLane, components typically represent an interface for data exchange, a shared element that is able to deliver functionality to multiple applications, a subsystem of an application or a semi-finished application. In contrast to an application, a component typically does not deliver functionality to end users but rather provide technical functionality to support an application. Typical examples for components are databases, operating systems, and vendor products.

What's the difference between an application and component? An application differs from a component in that the application provides functionality that is used by end users. Typically, users will know the application by name and the name is typically different than the name of the vendor delivering the application. Components, on the other hand, do not typically provide functionality to end users but rather provide technical functionality to support an application. For example, applications include products like customer portals, project management systems, vacation tracking systems, or a product like SAP@CRM System. Components include operating systems, Web servers, and Web browsers, or a product like SQL Server Database Management Studio.

The following table serves as an aid when trying to determine whether an object in your IT architecture is an application or a component.

Is it an application or a component? Application Component

Does it provide support to business capabilities or business processes

yes

no

Does it provide business benefit on its own?

yes

no

Does it have a service desk?

yes

maybe

Does it have an internal name or business-related name that is known by the end user?

yes

maybe

Can an end user work with it?

yes

maybe

Can it be used in different applications?

no

yes

Is it a standard IT product such as an operating system, infrastructure component, or database?

no

yes

Components can be created and defined in Alfabet FastLane or imported based on IT products from ITPedia®. Click to find out how to import components and their vendors from IT-Pedia.

In the navigation panel, click Technology Architecture > Component to open the data workbench for components.​ Per default, the data workbench displays only a set of basic attributes. You can add more columns to capture other attributes directly in the data workbench or you can navigate to a component's content area and define it in more detail there. Click to learn about how to use data workbenches.

You can add components by defining new components, as described below. Or you can import components based on IT products from IT-Pedia®. Click to find out how to import components and their vendors from IT-Pedia.

Add a new component. Click the New button. The edit panel opens on the right where you can define basic data.

Edit an existing component. Edit the component directly in the data table. Or select the checkbox  DWB_Checkbox for the component you want to edit and click the Edit  dlt-icon-edit_Teal button to open the edit panel.

Define the component's basic data. All mandatory fields must be defined to create the component and save it.

IT-Pedia® is a comprehensive IT product library that provides an up-to-date source of data about IT products of all types including, for example, hardware, software, and network devices. Alfabet FastLane provides an out-of-the-box integration with IT-Pedia that allows you to import components and the vendors that supply them to the Alfabet FastLane repository.

Only the IT-Pedia model catalog is available in the integration to ITPedia. Items from the procurement catalog cannot be created in Alfabet FastLane.

When an IT product is imported form IT-Pedia, it is imported as a component. The following data will be imported with the component:

  • Start and end dates: The Start Date of the component in Alfabet FastLane is based on the Release Date of the imported product. The End Date of the component is based on the End of Extended Support of the imported product.
  • Lifecycle: The component lifecycle will be automatically created based on the lifecycle data in IT-Pedia. The following lifecycles phases are available for components imported from IT-Pedia: Plan, Production, End of Sale, End of Support, and End of Extended Support.
  • Vendors: The vendor that supplies the component will be specified based on the Manufacturer of the imported product. If the vendor already exists in the repository, the vendor will be automatically associated with the component. If the vendor does not yet exist in the repository, it will be automatically added to the repository along with the new component based on the Manufacturer.

Import components and vendors from IT-Pedia. In the navigation panel, go to Components to open the data workbench for components.

  1. Click the three vertical dots ThreeDots button in the right corner of the toolbar and select Import from IT-Pedia.
  2. Click the Update button to fill the selector with initial data.
  3. You can use the following fields to enter search criteria to find the IT products to add to Alfabet FastLane. You can enter the name or just part of the name.
    • Product: Enter the name or part of the name of the products you want to find.
    • Version: Add the version number to limit the results found based on the product name.
    • Edition: Add the edition to limit the results found based on the product name.
    • Manufacturer: Enter the name or part of the name of the manufacturer of the products.
    • Model: Enter the product model name to find the products.

Review the IT-Pedia product data for components. Components that have been imported from IT-Pedia will be added to the Components data workbench.

  • You can add columns for various IT-Pedia product attributes such as Product Name, Product ID, Manufacturer Name, Manufacture ID, Model Name, and Model ID.
  • You can view a composite of all information about the IT-Pedia product that a component is based on. In the data table, click the navigate Navigate button of the component you want to view. Click the More tab and select IT-Pedia Data to view all relevant information about the IT-Pedia product.

Review the IT-Pedia product data for vendors. Vendors that have been imported from IT-Pedia will be added to the Vendors data workbench.

In Alfabet FastLane, responsibilities are documented via the concept of roles, whereby each role is based on a preconfigured role type or a custom role type defined by your company. In contrast to an authorized user who has read/write permissions, a person assigned a role for an asset will not have read/write permissions based on the role definition. The role is primarily for documentation purposes to provide information about stakeholders interested or responsible for the asset. If the user should have read/write permissions, they must either be the authorized user of the asset or assigned to an authorized user group associated with the asset.

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 component, click the navigate Navigate button of the component to open the content area. Go to the Overview page and scroll to the Responsibilities view and open it. Click in a column cell to open a selector to define a role for the component. Depending on the role column, you may be able to select a person or an organization. Switch between Person or Organization in the selector.

A 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 component.
  • Business Owner: A person who owns the component and is responsible for managing the functional requirements.
  • IT Owner: A person who owns the component and thus typically responsible for approval decisions.
  • Stakeholder: A person who has an interest in the component and therefore requires read-only access permissions.

An organization can have one of the following roles or a custom role added by your company:

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

An evaluation is a measurement of the performance of a component. Preconfigured indicator types and possibly custom indicator types added by your company are available to evaluate and are used in various analyses in Alfabet FastLane. Indicator types that are colored orange can be automatically computed by the system. All other indicator types must be manually defined.

Define the component's indicators. Click the navigate  Navigate button of the component to open the content area. Go to the Overview page and scroll to the Evaluations view and open it. Select an indicator type and click Edit Indicator or click Group Edit to open a dialog where all indicator types can be edited that are not automatically computed by the system.

Update computed indicators. Click the Calculate button to update computed indicators via the Calculate button. The indicators will be recalculated based on the current data.

The component lifecycle describes the succession of stages that the component goes through over time. A robust component lifecycle management includes versioning and planning for successor components to ensure that IT continues to support critical business areas.

Not all company's document their component lifecycles and it is not mandatory in Alfabet FastLane. However, robust component lifecycle management is key to the health to the business and helps you to understand identify and manage lifecycle conflicts. By documenting the lifecycles of the components in your technology portfolio, you will be able to identify which components are approaching end-of-life but have no defined successor components. Furthermore, you can understand which applications are at risk if the relevant technologies are no longer available.

In Alfabet FastLane, a component lifecycle consists of the following stages:

  • Manufacturer Support: Indicates that the technology is relevant to be used in a production environment.
  • Manufacturer Extended Support: Indicates that the technology is still available, but should be avoided for use in a production environment.

The active period of the component is the time between the component's start and end date. Each lifecycle phase is aligned with the proceeding and succeeding lifecycle phase that has been defined. Typically, the object state is set to Active during the lifecycle phase Manufacture Support. Gantt reports that visualize the component lifecycle will also reflect the component’s active period which is when the component is actually being used in the enterprise. This object state typically corresponds to the component’s start and end dates and should be set to Active when the active is in use.

Define the component's lifecycle. Click the navigate  Navigate button of the component to open the content area. Go to the Overview page and scroll to the Lifecycle view and open it.

  • Add lifecycle phases to the component's lifecycle. Include lifecycle phases by setting a checkmark in the checkbox for the lifecycle phase in the left pane. Only lifecycle phases that are selected can be defined.
  • Set the start and end of a lifecycle phase. In the timeline, select a lifecycle phase (colored bar) and drag the handles to define the start and end dates for the lifecycle phase. Select the Keep Phases Duration checkbox to retain the current definition in the adjacent lifecycle phases. If you do not select the Keep Phases Duration checkbox, the adjacent lifecycle phases will increase or decrease proportionally.
  • Set the start and end of the active period. Click the red bar for the active period and drag the handles to define the start and end dates for the active period. The selected object’s start and end dates will change correspondingly.
  • Align the start and and of the active period with the lifecycle phase. Click Align Active Period to automatically align the start/end dates of the active period with the start/end dates of the lifecycle phases that begin and end the active period.