Build New Server

Edit online

This section describes and defines the processes and procedures that will be used to manage catalog requests to Build New Server.

Purpose

A catalog request is required to kick off the deployment of a server build by the various Service Delivery teams. It signals the start of any service level agreements (SLAs).

Authorization

The creation and approval of a new standard server build is complex and is therefore described as part of authorization process. These steps may be combined and in some organizations they are. Typically, in smaller organizations some of the steps clearly will not be as detailed or be subjected to detailed reviews. However, in most large enterprises, checks and balances are in place to ensure the continuous business operations and these enterprises will have the steps that are described here. The tasks of the approvers will include verification of funding for the request. Multiple approvers may be required in some organizations. Notifications are sent to the service requisition user indicating the disposition of the approval request with reason codes.

The authorization process for the new server build requests solicits approval from the requester's manager as well as the approver of the Server Build delivery team. Notifications are sent to the service requisition user in either case.

The following tasks are performed as part of the authorization process:
  1. Requester manager approval
    Note: If management does not approve the request, the request is closed and the requester is notified of rejection.
  2. Delivery approval
    Note: If delivery does not approve the request, the request is closed and the requester is notified of rejection.
  3. Notify requester of approval
  4. Start fulfillment
  5. Notify requester of acceptance

Fulfillment

The following tasks are performed as part of the fulfillment process:
  1. Validate Installation/Configuration Pre-requisites (Hardware Planning Team)
  2. Order Hardware (Hardware Planning Team)
  3. Receive Hardware (Hardware Planning Team)
  4. Initial Installation (Hardware Planning Team)
  5. Validate SAN Requirements (SAN Team)
  6. Implement SAN (SAN Team)
  7. Physical Network Implementation (FS Team)
  8. Network Configuration (Network Services Team)
  9. Create SM Configuration (Storage Management Team)
  10. Complete Server Install and Cabling (Hardware Planning Team)
  11. Validate Build Requirements (Server Build Team)
  12. Load OS (Server Build Team)
  13. Install Standard Applications (Server Build Team)
  14. Configure SAN LUNs (if needed; Server Build Team)
  15. Verify Platform Security Compliance (Server Build Team)
  16. Requester Server Lockdown (Server Build Team)
  17. Test Backups (Server Build Team)
  18. Configure Monitoring System (Server Build Team)
  19. Update Inventory System & SR Information (Server Build Team)

Resource assignment

Generally, direct assignment by analysts to specialist or the team queue. SAN PM Assigns the SAN specialist in the course of the validation step.

Role assignment

Roles are meant as logical groupings of tasks. They are not meant to match any particular organizational structure. The same individual may perform Several roles may. A role may be split up among several individuals.

Table 1. Build New Server role assignments
Role Responsibilities related to Build New Server Requests
Server Build Team Receives service request and performs all activities related to installing and configuring the server, coordinates with other functional areas that may be providing services for the request, makes updates to the configuration management and asset management systems, and performs lockdown activities and turnover activities.
Hardware Planning Receives hardware asset, creates/updates Inventory tool, installs and configures server hardware and cabling.
SAN Engineer Participates in SAN planning activities, provides SAN implementation scripts, and performs SAN installation activities in coordination with the hardware planning team.
Storage Management The TSM team is involved in planning activities, and provides a TSM option file for the servers during the fulfillment process.
Network Services NS network services provisions network switches and routers. NS coordinates with facilities team to ensure physical connectivity is provided as specified.
Facilities Team The facilities team coordinates with NS and SAN teams to provide physical connectivity and power for servers included in the service request.
Steady State Team (Fulfiller) The steady state team accepts the responsibility for managing the servers once they have been completely installed and configured by the other fulfillment teams.