Search FCW


Subscribe Now!
Table of Contents
Sprint
Business
BPM
CXOs
Columns
Columnists
Defense
E-Government
Elections 2008
Enterprise Architecture
Funding
Homeland Security
Health IT
IPv6
LOB
Management
Procurement
Privacy
Policy
Program Management
State and Local
Security
Technology
Telework
Training and Certification
Workforce

More Topics
resourcecenter
Home
Letters to the Editor
Current Issue/Download
Print/Online Archives
Editorial Calendar
researchstore
resourcecenter
Communications for Continuity Operations

Oracle Resource Center
NEW! Transforming Data Center
Managed Services
Service Oriented Architecture
Training & Simulation
Networking Communications
Security Directives and Compliance
Data Center Virtualization
Air Force ELSG Contract Guide

More >>



Latest News
ADVERTISEMENT





 

How to write a good agreement

By Paul Korzeniowski
Published on July 23, 2001

Comment

Click here to comment on this article


Related story links

Focus shifts to performance

Choosing the right performance tool

Measuring customer satisfaction

Service-level agreements defined

Checking up on your ASP


Newsletters

You might also be interested in these FCW newsletters:

Daily

To learn more, click here.


Agencies today face the difficult task of translating their users' desires into formal service-level agreements. Here are a few areas agencies should focus on when writing their agreements, according to experts in the field. * Completeness. The document should clearly outline all of the functions that will be monitored and include end-to-end response time expectations or goals for specific components, such as router throughput. * Reporting functions. The agreement should list the reports that will be used to gauge performance, how often they will be generated and who will be able to access them. * Change management. Networks are dynamic entities; applications, devices and users are added or subtracted. The agreement should outline the impact such changes will have on performance requirements. * Clarity. Although a service-level agreement is a formal contract, it should not read like a legal brief. Both parties should easily understand the basic principles as well as the potential penalties. * Consistency. Service-level agreements tend to be complex and lengthy, so the authors should ensure that terms, such as "end-user response time," are used in a consistent manner throughout the document.

upcoming event

Green Computing Summit, Ronald Reagan Building, Washington, DC
December 2 - December 3, 2008

Trusted Internet Connection and the Comprehensive National Cyber Security Initiative, The Willard Intercontinental Hotel, Washington, DC
December 4, 2008


 

head
fcw
issue
First Name State
Last Name Zip
Title Email