Build New Standard Server Image

Edit online

This section describes and defines the processes and procedures that will be used to manage Catalog Requests for building new standard server images. A given image is effective until the next Image Create or Image Update request is initiated.

Image Create requests typically occur yearly, while Image Update requests occur quarterly. An Image Update occurs when there are changes to OS components or enterprise applications. Up to two images may be live in production simultaneously until all groups are fully deployed on the later platform. Unique data elements are usually handled with attachments to these requests. Typically, the elements will include information of the program package, version number, and license agreements.

Authorization process

The authorization begins when the Requester submits a service request for an Image Create or Image Update. The process completes after the new image is created or an existing image has been updated. The request ends when all activities related to the Image Create or Image Update Service Request are completed and the service request is closed. There are multiple roles responsible for managing the service request process. The following tasks are performed as part of the authorization process:

An approval request is validated and approved following its initiation.

Fulfillment workflow

An approved request is fulfilled by performing the following tasks:
  1. Validate request (A second validation step is optionally performed by the fulfillment team)
  2. Create automated install and test plan
  3. Validate image
  4. Announce User Acceptance Test (UAT) readiness
  5. Conduct UAT
  6. Provide build signoff
  7. Move build to PROD repository
  8. Remove image as designated

Resource assignment

The resource assignment process is complete when the analyst assigns the service request to a specialist or the team queue. Resource assignment is described as part of the fulfillment activities as the assignments are made.

Role assignment

Roles are provided as logical groupings of tasks. They are not meant to match any particular organizational structure. Several roles may be performed by the same individual, or a role may be split up among several individuals. Responsibilities include but are not limited to those listed for each role.
Note: The Queue Manager, Image Build Team, and QA Team roles are typically owned by a Desktop Design Integration (DDI) team.
Table 1. Role assignments
Role Responsibilities related to Image Create and Image Update requests
Requester
The Requester:
  • Completes and submits the Image Create & Image Update request form
  • The Requester designates who performs the User Acceptance Test (UAT)
  • Signs off on the build. A technology group within an organization drives the image requirements and therefore performs the Requester role within the process.
Queue Manager The Queue Manager acts as the customer liaison, coordinates the planning and completion of all work tasks from request to production. The Queue Manager role will be assigned to the DDI Team Lead.
Image Build Team (Fulfiller) The Image Build Team creates or develops the requested deliverable, e.g., image components, image integration, new workstations, etc.
QA Team The Quality Assurance (QA) Team conducts quality testing, reviews the software deliverable, and promotes code.