[ver]
	4
[sty]
	
[files]
[charset]
	82
	ANSI (Windows, IBM CP 1252)
[revisions]
	0
[prn]
	Apple LaserWriter II NT
[port]
	LPT2:
[lang]
	1
[fldnames]
	Field1
	Field2
	Field3
	Field4
	Field5
	Field6
	Field7
	Field8
[desc]
	
	
	
	
	
	801442262
	19
	795209099
	1616
	6
	0
	0
	0
	0
	
	
	
	
	
	
	1
[fopts]
	0
	1
	0
	0
	
	
[lnopts]
	2
	Body Text
	1
[docopts]
	5
	2
[GramStyle]
	
[ParaNum]
	1
[tag]
	Body Text
	2
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		100
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Body Text
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Ahead
	3
	[fnt]
		Arial
		220
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		240
		4
		79
		0
		3
		100
	[brk]
		112
	[line]
		16
		2160
		3
		0
		1
		1
		1
		65
		10
		1
	[spec]
		0
		1
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Bhead title
	4
	[fnt]
		Arial
		200
		0
		16385
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		220
		4
		79
		0
		3
		100
	[brk]
		80
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		2
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Chead title
	5
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		79
		0
		3
		100
	[brk]
		112
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		3
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Bhead
	6
	[fnt]
		Arial
		200
		0
		16385
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		220
		4
		180
		0
		3
		100
	[brk]
		68
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		2
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Chead
	7
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		100
		0
		3
		100
	[brk]
		68
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		3
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Numbered list
	8
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		300
		300
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		5
		<*:>.
		0
		3
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Numbered list
	0
	0
[tag]
	1st lev para
	9
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		0
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		68
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	1st lev para
	0
	0
[tag]
	Bullet
	11
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		120
		180
		180
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		</U>
		0
		3
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Bullet
	2
	1
	160
	1
	400
	0
[tag]
	Indnt bullet
	12
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		420
		180
		180
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		16
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		</U>
		0
		3
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Indnt bullet
	0
	0
[tag]
	2nd lev para
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		600
		0
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	2nd lev para
	0
	0
[tag]
	See also prnt
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	See also prnt
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Book art
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Book art
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Callout text
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Callout text
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Figure title
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		40
		60
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Figure title
	0
	0
[tag]
	Chapter title
	0
	[fnt]
		Arial
		280
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		300
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Chapter title
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	1st pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	1st pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Right pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Right pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Left pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Left pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Table title
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		60
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		7
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Table title
	0
	0
[tag]
	Table col hd
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		100
		0
		3
		100
	[brk]
		4
	[line]
		10
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		6
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		
		
		
	Table col hd
	0
	0
[tag]
	Table Text
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		200
		4
		79
		0
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		
		
		
	Table Text
	0
	0
[tag]
	See also hlp
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		40
		4
		180
		0
		3
		100
	[brk]
		96
	[line]
		9
		0
		3
		0
		1
		1
		1
		70
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	See also btn
	0
	120
[tag]
	See also btn
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		240
	[spc]
		24
		200
		4
		0
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	See also btn
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Crossref
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		513
		3
		0
		300
		600
	[spc]
		24
		200
		4
		19
		0
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Crossref
	0
	0
[tag]
	Indnt caution
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		720
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Caution
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Indnt caution
	0
	0
[tag]
	Indnt tip
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		324
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Tip
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Indnt tip
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Indnt note
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		468
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Note
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Indnt note
	0
	0
[tag]
	Caution
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		720
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Caution
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Caution
	0
	0
[tag]
	Tip
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		324
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Tip
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Tip
	0
	0
[tag]
	Note
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		468
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Note
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Note
	0
	0
[tag]
	Mono
	0
	[fnt]
		Courier New
		180
		0
		32768
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		48
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Mono
	15
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	1
	2880
	1
	3360
	1
	3840
	1
	4320
	1
	4800
	1
	5280
	1
	5760
	1
	6240
	1
	6720
	1
	7200
	0
[tag]
	Indnt mono
	0
	[fnt]
		Courier New
		180
		0
		32768
	[algn]
		1
		3
		300
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		32
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Indnt mono
	15
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	1
	2880
	1
	3360
	1
	3840
	1
	4320
	1
	4800
	1
	5280
	1
	5760
	1
	6240
	1
	6720
	1
	7200
	0
[tag]
	Dhead
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		100
		0
		3
		100
	[brk]
		68
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		4
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Parameter
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		0
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Parameter
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Formula
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Formula
	0
	0
[tag]
	Browse
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		+
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Browse
	0
	0
[tag]
	Keyword
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		K
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Keyword
	0
	0
[tag]
	Context
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		#
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Context
	0
	0
[tag]
	Title
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		$
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Title
	0
	0
[tag]
	Macros
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		!
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Macros
	0
	0
[tag]
	Footnote
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		244
		0
	[spc]
		40
		2400
		3
		0
		0
		1
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		256
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Footnote
	0
	0
[tag]
	Alink
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		A
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Alink
	0
	0
[tag]
	Butnbar
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		0
		0
		3
		100
	[brk]
		48
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		\li-140 
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Butnbar
	0
	0
[tag]
	Window
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		>
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Window
	0
	0
[tag]
	Win95 macros
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		W
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Win95 macros
	0
	0
[tag]
	Win31 macros
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		X
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Win31 macros
	0
	0
[tag]
	Build tag
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		*
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Build tag
	0
	0
[tag]
	_COND_IF
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	_COND_IF
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	_COND_ELSE
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	_COND_ELSE
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	_COND_ENDIF
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	_COND_ENDIF
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[lay]
	Standard
	3079
	[rght]
		12960
		10166
		1
		960
		1200
		3
		960
		720
		0
		1
		0
		1
		0
		2
		1
		960
		9446
		1
		1
		3120
	[lft]
		12960
		10166
		1
		720
		1200
		3
		960
		960
		0
		1
		0
		1
		0
		2
		1
		720
		9206
		1
		1
		3120
	[hlft]
	[lyfrm]
		1
		3008
		0
		0
		10166
		960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		3
	[frmlay]
		960
		10166
		1
		720
		180
		3
		0
		960
		0
		1
		0
		1
		1
		0
		1
		720
		9206
		1
		2
		4674
	[txt]
>
	[hrght]
	[lyfrm]
		1
		11200
		0
		0
		10166
		960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		1
	[frmlay]
		960
		10166
		1
		960
		180
		3
		0
		720
		0
		1
		0
		1
		1
		0
		1
		960
		9446
		1
		2
		4674
	[txt]
>
	[flft]
	[lyfrm]
		1
		5056
		0
		11760
		10166
		12960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		4
	[frmlay]
		12960
		10166
		1
		720
		480
		3
		11940
		960
		0
		1
		0
		1
		1
		0
		1
		720
		9206
		1
		3
		9900
	[txt]
@Left pg foot@<:R1,1,3,8486,><:P12,2,1 - >  Deployment Guide	Lotus Confidential

>
	[frght]
	[lyfrm]
		1
		13248
		0
		11760
		10166
		12960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		2
	[frmlay]
		12960
		10166
		1
		960
		480
		3
		11940
		720
		0
		1
		0
		1
		1
		0
		1
		960
		9446
		1
		3
		9900
	[txt]
@Right pg foot@<:R1,1,3,8486,>Lotus Confidential	Deployment Guide <:P11,1,1 - >

>
[elay]
[l1]
	0
[pg]
	6
	23 513 28 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	43 0 5 512 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	67 0 5 512 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	96 101 31 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	104 291 16 512 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	117 0 0 1025 1 0 0 300 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
[edoc]
@Chapter title@<:s><:#300,8486><:ZDDE_BOOKMARK1>Chapter 1: Planning a Notes Deployment

<+@><:s><:I0,0,0,0><:#1000,8486><:f180,BArial,0,0,0>Because of the power and complexity of Notes, you should carefully plot a deployment strategy for your organization.  Take the time now to assess your computing and communication infrastructure and to put people into place to assist with
 the deployment. After you select a pilot Notes application and a set of users, roll out Notes slowly, so you can learn from your early experiences and refine your deployment strategy and processes as you go. 
<:f>

<+@><:I0,0,0,0><:R1,5,1,480,1,960,1,1440,1,1920,1,2400,><:#600,8486><:f180,BArial,0,0,0>This chapter contains guidelines for a basic Notes roll out. Although each Notes roll out is as unique as the organization that deploys it, there are a set of considerations and guidelines that you can use to plan a successful deployment
 strategy.<:f>

@Ahead@<:s><:R><:#240,8486>About the deployment process

<:s><:#200,8486>There are two major considerations for deploying Notes:

@Bullet@<:#400,8486>organizational concerns -- personnel planning, setting up workgroups, and selecting a roll-out application 

@Bullet@<:s><:#200,8486>physical implementation of the system -- setting up networks, servers, and workstation

<:s><:#400,8486>Your planning should address the organizational concerns, because these will affect decisions you make about the physical implementation of Notes.

<:s><:#200,8486>Your Notes deployment planning phase and pilot program might look something like this:

@Numbered list@<:s><:#200,8486>Assemble a Notes roll-out team

@Numbered list@<:s><:#200,8486>Select a pilot Notes application for deployment

@Numbered list@<:s><:#200,8486>Identify a group of users who will participate in the initial roll-out

@Numbered list@<:s><:#200,8486>Take an inventory of your network infrastructure

@Numbered list@<:s><:#200,8486>Assess hardware and software needs

@Numbered list@<:s><:#200,8486>Prepare for Notes support and administration

@Numbered list@<:s><:#200,8486>Consider how you want to structure your Notes system

@Numbered list@<:#200,8486>Develop administrative processes for Notes

@Bhead title@<:s><:#220,8486>About assembling a roll-out team

<:s><:#600,8486>The very nature of Notes -- an enterprise-wide communications tool -- means that deploying and maintaining a Notes system will involve all areas of your organization. Understanding this and involving people in the planning phase might eliminate problems aft
er you deploy Notes.

<:s><:#1000,8486>Consider building a team with a representative from each Information System (IS) group in your organization. The team should include people who understand your existing network infrastructure, hardware, and software setups. Also include representatives from
 key departments, such as Finance, Sales, and Support, so you can use their input into planning a system that will meet the needs of the entire user community.

<:#400,8486>Eventually, as you determine the scope of your Notes system, you should begin to identify personnel who will administer Notes, design and deploy applications, and train and support users.

@Bhead title@<:s><:#220,8486>About selecting an application for deployment

<:#1200,8486>Delivering one key Notes application to a workgroup can be an effective way to begin a Notes roll-out. The application you choose should be something that shows users the power and efficiency of Notes. It might be something as simple as a corporate educatio
n database, that not only shows employees what classes are available and when, but takes a registration form that an employee fills out, relays it to a manager for approval, submits it to the education coordinator for processing, then sends a confirmation n
otice back to the employee.

<:#600,8486>At the same time you might set up a discussion database for your pilot workgroup. The idea is to encourage the workgroup to actively use Notes so that you can start collecting feedback from them and initiate support activities.

<:#600,8486>Notes includes a variety of application templates for such common applications as a discussion database, a phone book, and a news service. One of these might be suitable for use as a roll-out application.

@Bhead title@<:#220,8486>About identifying a workgroup for initial roll-out

<:#600,8486>Instead of trying to deploy a Notes system to a large organization all at once, choose one workgroup for the first phase of deployment. Doing so allows you to identify problems, learn from them, and establish processes that will make the remainder of the ro
ll-out easier to manage.

<:#1000,8486>Select a pilot workgroup that can benefit from the initial application or applications that you deploy. Encourage them to use the system and provide feedback. Make sure that the pilot group is trained on the hardware they are using as well as how to use Not
es. Have in place a trained, responsive Notes administration team, and you will be able to gather some very useful data from this phase of deployment.

@Bhead title@<:s><:#220,8486>About taking an inventory of existing network infrastructure

<:#800,8486>A key piece of your deployment planning depends on your getting an accurate picture of your communication infrastructure. How workgroups are connected will have a major impact on your strategy for server deployment, mail routing, and database replication. A
s you perform the network inventory, pay careful attention to the following:

@Chead@<:s><:#200,8486>WAN communication between locations

<:s><:#400,8486>You can use existing WAN communications to reduce the cost of dial-up lines and plan an efficient scheme for deploying servers in your Notes system.

@Chead@<:s><:#200,8486>WAN bandwith

<:#600,8486>Knowing the speed of each bandwith connection will help you to schedule mail delivery and database replication. Also, take a careful look at your WAN utilization. If you are close to capacity, you will probably want to increase the bandwith to prepare for N
otes.

@Chead@<:#200,8486>LAN scalablilty

<:s><:#400,8486>Is your network set up for rapid growth? If you are nearing maximum utilization, you might need to consider making some changes to increase network throughput.

<:s><:#200,8486><[><+!><+">Note to reviewers:<-"><-!> what should we say about the following with regard to infrastructure inventory:

<:s><:#200,8486>operating systems

<:s><:#200,8486>protocols

<:s><:#200,8486>types of server hardware

<:s><:#200,8486>modems

<:s><:#200,8486>phone lines]

<:s><:p<* >>

@Bhead title@<:s><:#220,8486>About assessing hardware and software needs

<:s><:#400,8486><:f180,BArial,0,0,255><+!><+">Reviewers: How does a site assess hardware and server needs<:f><:f180,BArial,0,0,255>? Do we offer guidelines for how many users per server?<-"><-!>

<:#1000,8486><:f180,BArial,0,0,0>As you consider what hardware and software you will need to get your pilot workgroup up and running with Notes, keep in mind your goals for completing a full Notes deployment. For example, you may decide to<:f><:f180,BArial,0,0,0> dedica
te one <:f><:f180,BArial,0,0,0>server to the pilot group. Then for each workgroup you add, you might dedicate another server. This method might not be efficient if workgroups do not fully utilize their servers. A better plan might be to deploy a few high ca
pacity Notes servers that will serve multiple workgroups.  <:f><:f180,BArial,0,0,0> 

<:s><:#600,8486><:f180,BArial,0,0,0>As you plan to<:f><:f180,BArial,0,0,0> add servers to support your Notes deployment, keep in mind that using servers of the same type and configuration will simplify 
<:f><:f180,BArial,0,0,0>administrative tasks. You will be able to establish a common Notes configuration and setup for that type of server.

<:s><:#800,8486>Part of planning your hardware needs will be allocating space for servers. Make sure that you plan for growth when you allocate space. It is much easier to administer multiple servers if they are physically close. Also consider the physical security of Note
s servers. They should be in a locked room or office with access restricted to authorized administrators.

<:#200,8486>Finally, make sure you have adequate equipment for backing up Notes servers.

@Bhead title@<:s><:#220,8486>About preparing for support and administration

<:s><:#400,8486>Planning to support a Notes system requires planning in a variety of areas. Here are some areas to consider when preparing to roll-out, support, administer, and maintain Notes:

@Bullet@<:s><:#200,8486>End-user Notes training

@1st lev para@<:s><:#200,8486>Users require training in basic Notes tasks, such as using mail and accessing databases on servers.

@Bullet@<:s><:#200,8486>Administrative training

@1st lev para@<:s><:#200,8486>Notes administrators require training in administering Notes servers and users.

@Bullet@<:s><:#200,8486>Application-design training

@1st lev para@<:s><:#200,8486>Plan to provide some training and guidelines for people designing applications for your organization.

@Bullet@<:s><:#200,8486>End-user support

@1st lev para@<:s><:#600,8486>Establish a "help desk",  where users can call for assistance with Notes. The help desk should be prepared to deal with end-user questions and problems, as well as notify the administrative team of administration problems, such as server failures.

<:s><:#400,8486>As you develop a support plan, keep in mind that the support providers must be able to respond consistently to remote as well as local users.

<:s><:#200,8486>For information on Notes training courses offered by Lotus' Consulting Services Group,  see <[>XREF].

<:#600,8486><:f180,BArial,0,0,255><+!><+">Reviewers: what are some techniques for meeting this goal?<:f> 
<:f180,BArial,0,0,255>Do we make recommendations on how many users one support person can handle? How about how many servers one administrator can handle?<-"><-!><:f>

@Bhead title@<:s><:#220,8486>About structuring your Notes system

<+@><:s><:I0,0,0,0><:R1,5,1,480,1,960,1,1440,1,1920,1,2400,><:#600,8486><:f180,BArial,0,0,0>As part of your deployment strategy, you need to make some important decisions about how to structure your Notes system to meet your short-term goals as well as  to allow for future growth.<+!><:f180,BArial,0,0,0> 
<-!>Some of the decisions you need to make early in the process are:<:f>

@Bullet@<+@><:R><:#400,8486><:f180,BArial,0,0,0>topology, that is, connecting<:f><:f180,BArial,0,0,0> Notes server physically and logically to provide the most efficient communication for your organization.<:f><:f180,BArial,0,0,0> Various 
<:f>strategies for server topologies are discussed <[>XREF].

@Bullet@<+@><:#400,8486><:f180,BArial,0,0,0>developing<:f><:f180,BArial,0,0,0> an organizational structure, which includes choosing a method for certification, deciding on organizational units, and developing a naming strategy for servers and users in your system.<:f>

<:s><:p<* >>

@Bhead title@<:s><:#220,8486>About developing administrative processes

<:s><:#1000,8486>Establishing administrative processes early in your Notes deployment will prevent future chaos. If you do not establish controls, servers and databases can become a tangle that will frustrate users and administrators alike. A critical aspect of your pilot p
rogram is gathering administrator and user feedback that will translate into processes for smoothly deploying Notes. Consider setting up a Notes discussion database that users can use to submit feedback to the Notes roll-out team.

<:s><:#400,8486>The following are some basic processes you should address and communicate before fully deploying Notes.

<:#400,8486><:f180,BArial,129,0,255><+"><+!>Question to Phyllis: Should I provide all of the detail for these items? If so, should the detail go as separate topics?<-"><-!><:f>

@Chead title@<:s><:#200,8486>Server processes

@Bullet@<:s><:#200,8486>Develop a server upgrade policy

@Bullet@<:s><:#200,8486>Establish a naming convention for servers

@Bullet@<:s><:#200,8486>Plan backup/restore policies and procedures

@Bullet@<:s><:#200,8486>Decide how and when databases can be added to servers

@Bullet@<:s><:#200,8486>Establish a standard configuration for servers

@Chead@<:s><:#200,8486>Support processes:

@Bullet@<:s><:#200,8486>Develop an end-user help strategy

@Bullet@<:s><:#200,8486>Develop a server support strategy

@Chead title@<:s><:#200,8486>Training processes

@Bullet@<:s><:#200,8486>Develop a training plan for end users

@Bullet@<:s><:#200,8486>Develop a training plan for administrators

@Chead title@<:s><:#200,8486>Administration processes

@Bullet@<:s><:#200,8486>Establish security guidelines

@Bullet@<:s><:#200,8486>Decide how administrative requests will be submitted and handled<:Z~DDE_BOOKMARK1>

@Bullet@<:s><:#200,8486>Decide whether servers will be administered centrally or whether administration will be decentralized

@Ahead@<:#240,8486>About Notes training courses offered by Lotus

<:#600,8486>The Lotus Consulting Services Group offers training classes designed to address the needs of the individuals who will be supporting and using Notes. Lotus CSG consultants will work with your organization to provide training that meets your particular needs.

@note:note@<:#400,8486>The following courses are for Lotus Notes Release 4.0. For more information and schedules, please call the Lotus CSG Education Services Helpline at (800) 346</m>6409.

@Chead@<:s><:#200,8486>Update Course

<:#600,8486>This course is designed to familiarize trained and experienced Notes Release 3.0 Application Developers and System Administrators with the features of Notes Release 4.0. This is a three day course using mostly lecture with some hands</m>on exercises.

@Chead@<:s><:#200,8486>Basic Notes Concepts

<:s><:#400,8486>This one-day course introduces users to the power and flexibility of Note. Users learn to navigate within the Notes workspace, compose and view documents in a database, and use Notes mail.

@Chead@<:s><:#200,8486>Notes Technical User

<:s><:#400,8486>This one-day course presents more technical user features of Notes. Users learn about Notes database design and automation features.

@Chead@<:s><:#200,8486>Notes Application Development I

<:s><:#600,8486>This two-day course provides a solid foundation in Notes database design for the Application Developer. Designed for core programming team members, the course moves quickly through each fundamental aspect of building Notes applications.

@Chead@<:s><:#200,8486>Notes Application Development II

<:s><:#400,8486>This three-day course provides a detailed study of Notes application design for software professionals. The depths of the software are explored in an intensive, accelerated workshop environment.

@Chead@<:s><:#200,8486>Notes System Administrator I

<:s><:#600,8486>This three-day course provides a solid foundation for the Notes System Administrator. Designed for core systems team members, the course moves quickly through every aspect of setting up, operating, and maintaining Notes servers and client workstations.

@Chead@<:s><:#200,8486>Notes System Administrator II

This two-day course provides advanced information for the Notes Administrator responsible for the roll-out of Notes in large, multi</m>domain, multi</m>Notes named network, and multi</m>protocol environments. Designed for lead systems team members, the cour
se extends Notes from the workgroup to the enterprise.<:p<* >>

@Chapter title@<:s><:#300,8486>Chapter 1: Planning a Notes Deployment

@Ahead@<:s><:#240,8486>About the deployment process

@Bhead title@<:s><:#220,8486>   About assembling a roll-out team

@Bhead title@<:s><:#220,8486>   About selecting an application for deployment

@Bhead title@<:#220,8486>   About identifying a workgroup for initial roll-out

@Bhead title@<:s><:#220,8486>   About taking an inventory of your network infrastructure

@Bhead title@<:s><:#220,8486>   About assessing hardware and software needs

@Bhead title@<:s><:#220,8486>   About preparing for support and administration

@Bhead title@<:s><:#220,8486>   About structuring your Notes system

@Bhead title@<:s><:#220,8486>   About developing administrative processes

@Ahead@<:s><:#240,8486>About Notes training courses offered by Lotus

@Ahead@<:s><:#240,8486>

@Chapter title@<:#300,8486>

>

[Embedded]
00037669
