Exception Process for Ordering Non-Standard Notebooks

Introduction

This document outlines the exception process for ordering non-standard notebooks, which are notebooks that do not meet the specifications or requirements of the notebooks provided by Zühlke.

Scope

This exception process applies to all employees who wish to order non-standard notebooks for their project work. Non-standard requests can only be made for existing models/series, e.g. Dell Precision or Apple MacBook Pro. It does not apply to "Standard" notebooks (Dell Latitude or Apple MacBook Air).

Possible Reasons for Requesting Non-Standard Notebooks

The following is the only reason that might justify the request for a non-standard notebook:

The standard configuration has performance issues that affect the speed, reliability, or functionality of the project work. For example, the notebook has insufficient memory to run the required software.

Procedure for Requesting Non-Standard Notebooks

The exception process for ordering non-standard notebooks consists of the following steps:

Fill out the respective Notebook Order Service Request and provide a detailed explanation of the reason, the impact on the client project and the specifications of the desired notebook in the Comment field.
The IT department will consult with the requestor's People Lead to ensure that the budget, business need, and value of the non-standard notebook are met.
The People Lead should then consult with the requester's Project Lead to ensure that the budget, project need, and value of the non-standard notebook are met.
If all involved parties approve the request, the IT department places the order for the non-standard notebook and notifies the employee of the expected delivery date.
If the request is rejected or modified at any stage, the requester is notified of the reason and the options for resubmitting or appealing the decision.

Criteria for Approval

The IT department and the People Lead/Project Lead will review the request and the evidence and decide whether to approve or reject the request. The decision should be based on the following criteria:

The reason is valid and directly related to the client project.
The impact is significant and measurable and cannot be resolved by other means.
The benefit is clear and outweighs the additional cost.
The request is feasible and available within the IT budget and timeframe of the project.