Configuration Item - Physical Servers DRAFT

A physical server is a computer used to provide data to other computers or systems on a local network or over the internet. While any computer can be configured as a server, most production servers use specialized server hardware mounted in racks and installed in a data center. A physical server can be used for a number of applications, including databases, applications, network management, email, directory services, etc. The life cycle outlined here applies to any physical server equipment irrespective of its application.

Names of physical servers are often specified by the client at the time the server is ordered. However, when this is not the case, server names should follow the form of:

      {part1} [({part2})] [{part3}] [ - (part4)]

Where:

{part1}
{part2}
{part3}
{part4}

Physical Server CI Name Examples

The following are examples of CI names that have been standardized using the conventions described above.

Common	Standard
x	y
x	y
x	y

Typical Life Cycle for Physical Servers

Although some CIs have a special life cycle, the typical life cycle for most CIs representing hardware is:

Phase 1: Request & Approval
During this phase, a need for the asset is determined and a decision is made to deploy the asset. Specifications for the equipment are determined, quotes are obtained, approvals are collected from appropriate stakeholders, and a supplier is selected. In some cases, the "supplier" may be internal if, for example, an existing device can be repurposed or one is located in another department.

Phase 2: Ordering & Acquisition
If the asset is being acquired from a third party, an order is placed. If the asset is being transferred internally within OIT or from another department, the required documentation is prepared and executed. This phase ends at the point where the asset has been delivered and is ready for installation or configuration.

Phase 3: Testing & Installation
The asset must be compared to the original specifications and acquisition documents to confirm that it matches the original requirements. Any required assembly and configuration is done during this phase. This includes operating system software, application software and services, databases, network connections, user definition and security rules, and arrangements made for backups and disaster recovery. When all configuration steps are complete, a system test is performed on the asset in place to ensure it meets all client requirements. This phase ends when the asset is ready to be deployed into production.

Phase 4: In Service & Maintenance
This phase represents the useful production life of the asset. Throughout this phase, the asset will undergo periodic maintenance, upgrades, failures, and fixes. At some point, the usefulness of the asset will come to an end and plans need to be made to take it out of service. (Normally, these plans are made well in advance of the decommissioning of the asset.)

Phase 5: Retirement
When the asset is no longer needed, either because it is being replaced by something newer or it no longer serves any useful function, it is retired. Retirement can be a fairly complex process depending on the asset class. If the services provided by the asset are no longer needed then retirement can be as simple as taking the asset off line and disposing of it or making it available for other purposes. Plans for retirement are generally made well in advance of the actual deinstallation of the asset.