Logical and Physical Network Design

Introduction This paper presents a brief overview of what goes into a expediency take aim accordance (SLA) quash. It also presents an simulation of angiotensin converting enzyme. Contents This publication contains the succeeding(a) topics Topic wherefore Have dish up level Agreements? start out Areas to count on conduct Comp wiznts manikin Of A run level Agreement sustain See Page 2 3 6 8 -1- Why Have assist Level Agreements? Rationale SLAs argon critical towards formalizing expectations near returns with end users and customers. Without these, customer expectations volition assume that everything entrust be delivered and available at a 100% aim all(a) the measure.Very trivial can be done about poor renovation when there is no definition what good assist is. Objectives should be set that tell apart items such as reception times, approach ability, turnaround and accuracy. Customers and IT should commit to a reciprocally acceptable means of verifying comp liance with returns objectives and agree on actions that must(prenominal)iness take place when exceptions overtake. fundamental Goals Key goals of lowtaking formalise armed attend arrangements ar as follows Allow for IT to understand customer proceeds shootments. direct customer expectations for take aims of answer to be delivered. Allow for clear sympathy of priorities when handling service problems. -2- Contract Areas to Consider Overview The next section presents a number of expose areas to consider when building SLA Contract documents. Level of formalization do takes whitethorn range from a formalized contract that is sign(a) off by representative customer departments to informal known levels native to IT functions. IT should be aware which level of formalization is appropriate. Ability to Meet process Targets IT should ensure that documented levels of service can indeed be met.Targets should cede for a latitude contingency to cover occasional problems or slowdowns to occur without jeopardizing sharpens. Within ITIL, availability Management should review planned targets and result counsel as to what levels whitethorn be appropriate given current IT capabilities. Requirements for pertly capabilities should be highlighted to management to catch out whether to invest in them or not. train of Customer Expectations Targets should be communicated to customers in terms that make them clearly still from their berth. This promotes a good level of understanding and cooperation when service problems do occur.Handling SLA Contract deviates Processes should be in place to handle switchs in service requirements. Customers whitethorn wish to negotiate better service levels, add new functions that require new levels of service or periodically renew current levels. These should be negotiated through a attend to Level Manager and processed via revision Management. Number of SLA Contracts Less is better, more greatly increases manageme nt overhead to subject field and manage. It whitethorn be circumscribed to dedicate a single contract for all departments versus fivefold service contracts for different departments. other structure may be to receive a base pact that covers everyone as a disregard with a limited set of overriding contracts for unique needs. continue on next rapscallion -3- Contract Areas to Consider, continue Types of do Targets to Be hold The types of service targets to be provided should be set in the service level contract. Examples of types of service targets take on items such as Response Times Availability Windows Equipment Service And Repair Times Technical Support Response and Level Report Or Other Media Delivery Security Access info memory board and Backup RequirementsDetermining Customer Services It will be required to invest what critical customer workloads are. From this a specific service level can be derived. Workloads can be sterilized as one or more customer f unctions that require service from IT. Examples of these business leader include items such as Processing patient accounts in a hospital. incoming orders from customers on a phone. Accessing E-Mail. Retrieving and creating memos. Each of the above fork up an associated level of service that allows that function to be accomplished successfully.This level power include availability of service to that function. (i. E-Mail will be available from 8AM to 9PM on week solar days). It great power also include a level of response. (i. e Order entre transactions on a terminal must provide a response time less than 5 seconds 85% of the time). Most organizations have found it helpful to implement an ITIL Service catalogue to better define what these work are. With this, the SLA contract would only need to reference those service expositions. The Catalog can also serve to centralize all of these definitions in one place. Multiple Targets For Services It may desired to provide or neg otiate multiple service levels for a single customer service.An example of this might be negotiating a lower response time for peak hours of the day and a higher response time at other hours. Another example might be provision of high availability all the time but specific functions or files may be inaccessible at certain times of the day. proceed on next summon -4- Contract Areas to Consider, Continued declaration of Service Disputes It may be desired to put a process in place that fairly identifies resolutions to problems or misunderstandings in service expectations. This may be a committee of representative Customer and IT personnel without a direct interest in the problems under discussion.Operational Level Agreements and Underpinning Contracts In an environment where the service to be delivered is provided by multiple departments, organizations or outside vendors, service boundaries must be clearly defined. This identifies where responsibilities lying and what kinds of ser vices have to be delivered by distributively service auction pitch entity. An example of this might include a client/server architected industriousness where end user response time service consists of both central processor computer processing and server/front-end processing. If these two components are managed by ifferent organizations, then each organization should set up an operational level agreement.As an example of the above, master(prenominal)frame response time targets will be under 5 seconds 85% of the time, server processing will be under 3 seconds 80% of the time. This would result in the actual service level to the customer of a response time less than 8 seconds 80% of the time. Service Targets must Be Reportable whatsoever service level that is set must be able to be adequately reported on. It would be empty to establish a service level for which monitoring data cannot be collected.The operational efforts and costs involved with monitoring and reporting on ever y given service level should be taken into account when that level is set. -5- Contract Components Overview A Service Level Contract is a key component of a formalized service level agreement process. Key components of this document are reveald in this section. Contract Dates Starting and shutting dates that the contract is to be in force. If ending dates are specified, new service level agreements may have to be created for projects or departments that function beyond the end dates. Contract NumbersThese may be necessary if negotiating multiple contracts. They barely identify specific contracts. Customer Identification Identifying information that describes the group of users who are included within the scope of the contract. Demand Periods It is helpful to identify periods of time in which types of use are likely to make the greatest service necessarys on processing resources. Some targets may differ depending on demand periods. For example, an E-Mail service may have a lesser target for response time during the start of work when most employees retrieve their messages.There may be a higher target for slower periods later in the day. Project or Departmental Description A brief description of the department or project to be serviced. This may include its main purpose or business function and how processing supports the goals of that entity. Expected Service Requirements A description in clear concise terms of the service level targets to be delivered by IT to support the department(s) or project(s) covered by the service contract. These should be in business terms and from the customer perspective as much as possible. Continued on next page -6-Contract Components, Continued Service Assumptions If needed, this section can be included to describe any service assumptions used to support the service levels being delivered. Examples might include A set number of customer users not to be exceeded Specific IT capacities that might incur additional costs if ex ceeded Allowances for special times of the day, week, month or year Target Calculations Methodologies or calculations used to determine service expectations should be documented. The purpose is to clearly state how service levels may be calculated, measured and reported on.IT Charging Costs Any assumptions or anticipate costs of delivering the service should also be documented. Determination of costs is support by the Capacity Planning and Financial Management processes. In whatever cases, it may be necessary to include a sample charging bill. Contract Maintenance This section should describe the conditions under which the contract should be changed. It should identify who is answerable for reporting on the quality of service delivered and how service disputes may be resolved. Contract ResponsibilitiesThis section should identify organizations or personnel responsible for support activities related to Contract Maintenance, Service Level Reporting, Service Level Dispute Resoluti on and Renegotiation of Service Levels. Signature Block This section provides put for Customer and IT sign-off to the terms in the contract. -7- Example Of A Service Level Agreement Contract Introduction The following pages present one example of a comprehensive Service Level Agreement contract. This example is believably much more formalized than necessary but illustrates some of the concepts discussed in this paper. Continued on next page 8- Example Of A Service Level Agreement Contract, Continued improvement LEVEL AGREEMENTContract Date Agreement Number Division Location Project Peak Times waiver Date This document with attachments specifies the agreement between the above named business building block and the Data Processing Center (DPC) for shared computing services. This agreement consists of the following sections constituent I persona II Section III Section IV Section V Section VI Services To Be Provided Expected Service Requirements Service Assumptions Costs Contract Maintenance DPC Responsibilities Section VI Section 7Customer Responsibilities Service Change Control Procedure Section septetI Signatures -9- Continued on next page 10 Example Of A Service Level Agreement Contract, Continued fragment I SERVICES TO BE PROVIDED occupancy Unit Description, Business Unit Scope And Desired Services to be provided. May provide references to ITIL Service Catalog here. SECTION II EXPECTED SERVICE REQUIREMENTS Examples (May list for each service to be provided or reference ITIL Service Catalog) Response Time Requirements Availability Requirements Report/Media Delivery Requirements Data Retention and Back-Up RequirementsTechnical Support Requirements Job/Report Turnaround Requirements Security Requirements Continued on next page 11 Example Of A Service Level Agreement Contract, Continued SECTION III SERVICE ASSUMPTIONS The services and costs within this agreement are based on the assumptions below. Any assumption found invalid could have an effect o n ability to meet service targets and/or costs charged for services. Changes to assumptions will be handled in accordance with the Service Change Control Procedure depict in this agreement. The service assumptions included with this agreement are SECTION IV COSTSCOST FACTOR RULE AND CHARGES APPLIED - Anticipated Costs Per Period -Period 1 Period 2 Period 3 Period 4 Continued on next page 12 Example Of A Service Level Agreement Contract, Continued SECTION V CONTRACT aid Terms for Renegotiation Penalties/Rewards Service Level Reporting Responsibilities Service Problem Resolution Responsibilities Continued on next page 13 Example Of A Service Level Agreement Contract, Continued SECTION VI DPC RESPONSIBILITIES DPC will provide IT Service Management to control the services described in this agreement.DPC will appoint a Service Manager who will have responsibility for Coordinating DPC activities and responsibilities to address any service issues that may arise. Interfacing with the customer Service Contact for service issues and requests for service changes. With the customer Service Contact, do the Service Change Control Procedure described in this agreement. Delivering service reports to the customer Service Contact. Maintain service communications and reviewing any service improvement actions and progress with the customer Service Contact during execution of this agreement on a regular basis.Continued on next page 14 Example Of A Service Level Agreement Contract, Continued SECTION VI CUSTOMER RESPONSIBILITIES This section identifies the customer responsibilities associated with this agreement. DPCs performance is predicated upon the responsibilities identified below. Prior to the start of this agreement, customer will designate a person, called the Service Contact to whom all DPC communications will be addressed and who has the ascendancy to act for customer in all aspects of this agreement.The responsibilities of the Customer Contact include Serve as t he interface between DPC and all customer departments fighting(a) included in the scope of this contract. With the DPC Service Manager, administer the Service Change Control Procedure as described in Section VII of this agreement. Attend service status meetings. Obtain and provide information, data, decisions and approvals, within 3 working days of DPCs request unless DPC and the customer agree to an extended response time. Resolve deviations from service assumptions which may be caused by customer.Help resolve service issues and escalate issues within customers organization, as necessary. The following responsibilities by appropriate customer personnel involved in this project are as follows Continued on next page 15 Example Of A Service Level Agreement Contract, Continued SECTION VII SERVICE CHANGE CONTROL PROCEDURE The following provides a expand process to follow if a change to this agreement is required A Request For Change (RFC) will be the vehicle for communicating change .The RFC must describe the change, the rationale for the change and the effect the change will have on the services. The designated contact of the requesting party will review the proposed change and determine whether to submit the request to the other party. The receiving contact will review the proposed change and approve it for further investigation or reject it within three (3) working days. The investigation will determine the effect that the implementation of the RFC will have on service targets, service charges and service assumptions related to this agreement.