Support Change Control Process

Typically ISAM drafts proposal (not always)
	focused on changes that impact users of isam computing resources.

Plan should include:
	Description of change
	Reason for Change
	Stakeholders (identify, but not an in depth analysis)
	Project Leader
	Detailed required changes in:
		Remedy (solutions, CTI adjustments, Group creation,
			assignments, etc.)
		Documentation (web, handouts, CSW, etc.)
		Training 
		Announcements (dept-computing, computing-news, etc)
		MyAndrew (Distribution changes)
	Proposed Schedule
	Include resource expectation for internal groups

1st draft comments accepted by (typically two week turn-around)
	ISAM Managers during weekly meeting
	Help Center manager (Clay)
	UES Outreach Coordinator (KVD)

Final plan distributed to:
	Computer Education
	Desktop Support
	Communications and Design group
	Clusters
	Computer Store (?)
	Network Group
	Network Security
	ACIS

General guidelines and comments:
--------------------------------

	All new service additions should include a 
	service reduction unless manpower has been adjusted
	in some other manner (e.g. recent reduction in another
	service, additional staffing, etc.)
	
	We should strive to focus support on Infrastructure
	Services (LDAP, Kerberos, AFS, Email, File Services
		Andrew Windows, Clusters, etc.)	

	Minor Change example - supported versions of a particular
		application, service pack release

	Major Change example - support of a new operating system.

	Provide an alternative solution for clients during Phase-outs.

	Try to limit support to only two active versions of a product
	or operating system (e.g. WinXP and Win2000).