Capture physical server data

Physical servers are devices and hardware that are tangible assets owned by an organization . Virtual servers are run on top of physical servers which are located in different locations around the world. Documenting physical servers and their virtual servers and where they are located is critical for disaster recovery management.

In the navigation panel, click Technical Architecture > Physical Servers.​ 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 physical server's content area and define it in more detail there. Click to learn about how to use data workbenches.

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

Edit an existing physical server. Edit the physical server directly in the data table. Or select the checkbox   for the physical server you want to edit and click the Edit   button to open the edit panel.

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

• Name: (Mandatory) Enter a unique name for the physical server.
• Version: (Mandatory) Enter a version number for the physical server. The name and version number of the physical server should be unique.
• Start Date and End Date: (Mandatory) The start and end date captures the period when the physical 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 physical server. The release status determines whether a physical server can or cannot be deleted. Possible values are:
  • Draft: The physical server has only mandatory data defined.
  • Under Review: The physical server is documented and being reviewed. A physical server with this release status cannot be deleted.
  • Approved: The physical server has been approved by the responsible stakeholders. A physical server cannot be deleted when it has an approved release status. A physical server with this release status cannot be deleted.
  • Data imported: The data regarding this physical server has been imported from an external system. Additional changes may be required to improve the data quality. A physical server with this release status can be deleted.
  • Trash: The physical server is no longer valid and can be deleted.
• Object State: (Mandatory) The object state describes the use of the physical server in the real word. This can be understood as the operational status of the physical server. Possible values are:
  • Plan: The physical server is proposed to be used and still in the stages of planning and building.
  • Active: The physical server is currently and used now. The active period begins with the physical server's start date and ends with the end date.
  • Retired: The physical server is no longer used.

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

• Serial Number: Enter the physical server's serial number.
• Location: Select the location where the physical server is.

  location

  A location is a geographic place that could be a country, city, building, or room, for example.

• Description: Enter a meaningful description that will clarify the purpose of the physical server.
• Authorized Access tab: The user who creates the physical 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 physical 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.