charter

Washington State Enterprise Architecture Program

Networking Standards Initiative Charter

EA Committee Document

Version 1.41.4

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

1

Washington State Enterprise Architecture Program December 7, 2005Networking Standards Initiative Charter EA Committee Document—Version 1.4

December 8, 2005 Table of Contents

1. Document History....................................................................................................................... 2

2. Document Context...................................................................................................................... 3

3. Description of the Initiative..........................................................................................................4

4. Key Stakeholders........................................................................................................................ 4

4.1. Enterprise Architecture Committee Stewards.......................................................................4

4.2. Business Sponsorship..........................................................................................................4

4.3. Documenter Team................................................................................................................4

4.4. Coordination with Related Efforts.........................................................................................7

5. Key Issues or Decisions to be Addressed...................................................................................7

6. Expected Tier One Component Scope.......................................................................................7

7. Past Work on this Initiative..........................................................................................................8

8. Schedule: Document Process.....................................................................................................8

8.1. Key Dates............................................................................................................................. 8

8.2. Timeline................................................................................................................................ 8

8.3. Time Commitment of the Documenter Team.......................................................................9

9. Schedule: Review Process.........................................................................................................9

9.1. Key Dates............................................................................................................................. 9

9.2. Timeline................................................................................................................................ 9

10. Evolving a Single, Cohesive Enterprise Architecture..............................................................10

11. Initiative Status Reporting.......................................................................................................10

12. Initiative Sunset...................................................................................................................... 11

13. Attachments............................................................................................................................ 11

1. Document History

Date Version Editor Change

9/21/2005 1.0 Scott Came Initial Draft

10/19/2005 1.1 Scott Came Team updates

Removed original scope section and referenced contextual straw model

of 11

234

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

5

Washington Enterprise Architecture Program December 7, 2005Networking Standards Initiative Charter EA Committee Document—Version 1.4

Date Version Editor Change

11/2/2005 1.2 Scott Came

Jim Albert

Adjustments to solution sets

Edits to usage standards scope statement

11/30/2005 1.3 Scott Came

Jim Albert

Remove initial straw-model

Adjust scope per discussion with NTSC

New format and Document Context section

12/7/2005 1.4 Scott Came Updates per 11/30 committee discussion

Adopted by EAC 12/7/2005

2. Document Context

This document currently has EA Committee Document status. This status signifies that the document has been adopted by a vote of the ISB Enterprise Architecture Committee.

For more information about the Enterprise Architecture Program or the ISB Enterprise Architecture Committee and its initiatives, please visit the EA Committee website at:

http://isb.wa.gov/committees/enterprise/index.aspx.

of 11

678

45

46

47

48

49

50

51

9

http://isb.wa.gov/committees/enterprise/index.aspx


3. Description of the Initiative

The purpose of this enterprise initiative is to develop policies, standards, and guidelines for network infrastructure solutions, assets, and services that are common statewide. The initiative seeks to evolve a set of Tier One components in the statewide Enterprise Architecture.

The business case for this initiative is to support the making of key decisions documented in the section “Key Issues or Decisions to be Addressed” below.

4. Key Stakeholders

This section identifies key stakeholders of the initiative.

4.1. Enterprise Architecture Committee Stewards

Each initiative must have at least one steward from the Enterprise Architecture Committee.

Committee stewards can be considered as the executive sponsors of the initiative. As such, the stewards are responsible for coordinating communication with the Committee, coordinating communication with other executive stakeholders, assisting in removal of obstacles to the initiative’s progress, and assisting in making resources available to the initiative. In all of these responsibilities, the Enterprise Architecture Program will support the stewards as needed.

For this initiative, the stewards are:

Jim Albert, DIS Deputy Director (lead)

Julian Soh, Chief Information Officer, Department of Revenue

4.2. Business Sponsorship

This initiative has no additional business sponsorship beyond the Enterprise Architecture Committee.

4.3. Documenter Team

Each initiative must have a Documenter Team, consisting of subject-matter experts and other stakeholders who can assist the Enterprise Architecture Program in evolving viable standards, policies, guidelines, and architectural components. The expectations, including time commitment, of Documenter Team members will be documented later in this document. Note that the term “Documenter Team” originates from the Documenter role in the NASCIO Enterprise Architecture framework; this is to signify that the team’s objective is to play (or assist in playing) that role as defined in the framework, not that the team is responsible for all architectural documentation effort in the initiative.

Each Documenter Team should ensure that the following roles are sufficiently covered. (These roles and their definitions are taken from the EA Program Management Plan.)

Role Definition/Purpose

Executive Sponsor Communicates with key stakeholders on behalf of the initiative

Ensures the Documenter Team has adequate resources to meet its milestones

Reports on initiative progress to the EA Committee

Facilitates resolution of issues that cannot be resolved within the team

of 11

101112

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

78

79

80

81

82

83

13


Role Definition/Purpose

Subject-Matter Expert

Provides technical expertise in the initiative’s topic areas

Represents communities of interest

Brings best practices and lessons-learned from the statewide IT community to the initiative

Authors artifacts (supported by Architect and Policy Advisor)

Project Manager Monitors and reports initiative’s progress towards milestones

Provides logistical support to Documenter Team (meeting coordination, support resources, etc.)

Facilitates team meetings and ensures maximum meeting productivity/effectiveness

Architect Supports Documenter Team in identifying and using the correct framework artifacts, modeling notations, etc.

Supports executive sponsor in communicating with the EA Committee

Manages submission of team’s artifacts to central EA repository

Provides coordination across Documenter Teams

Authors artifacts (supported by SME and Policy Advisor)

Policy Advisor Supports Documenter Team in creation of Compliance Components (policies, standards, guidelines) in the Technology Architecture

Through artifact review, ensures Compliance Components meet ISB form and content standards

Supports SME and Architect in authoring of artifacts other than Compliance Components

Provides policy-oriented coordination across Documenter Teams

The following table identifies the members of the Documenter Team for this initiative. This initiative will not move forward until all of the roles above are satisfied by the team membership.

Member Title

Organization

Phone contact

Email contact

Team role

Jim Albert Deputy Director

DIS

(360) 902-9885

[email protected]

Executive Sponsor

Julian Soh Chief Information Officer, DOR

360-586-9826

[email protected]

Executive Sponsor

of 11

141516

84

85

86

17

mailto:[email protected]



Member Title

Organization

Phone contact

Email contact

Team role

Geoff Lakeman University of Washington

[email protected] SME

Mike Frost DSHS (360) 902-7506

[email protected]

SME

Mike McVicker Assistant Director

DIS

(360) 902-3335

[email protected]

SME

Michael Partlow DIS (360) 902-2291

[email protected]

SME

Ron Kappes DIS (360) 902-3355

[email protected]

SME

Mark Fortier OFM (360) 902-0604

[email protected]

SME

Fred McDowell LSC (360) 786-7034

[email protected]

SME

Dennis DeFries Network Services Manager

WSDOT

(360) 705-7707

[email protected]

SME

David Curtiss DOL (360) 902-0162

[email protected]

SME

Stu Lundmark Washington State Patrol

360-705-5351

[email protected]

SME

Joe Russo Washington State Patrol

360-705-5145

[email protected]

SME

of 11

181920

21













Member Title

Organization

Phone contact

Email contact

Team role

Peter Tamayo Chief Information

Officer, DRS

(360) 664-6758

[email protected] SME

Scott Came Chief Architect

DIS

(360) 902-3519

[email protected]

Project Manager

Architect

Paul Warren Douglas

Senior Policy Advisor

DIS

(360) 902-3471

[email protected]

Policy Advisor

4.4. Coordination with Related Efforts

This section identifies related efforts (planned or underway) to address issues similar to the issues in the scope of this initiative. Preferably, representatives from these related efforts will serve on the initiative’s Documenter Team. To the extent this is not possible, this section documents the strategy for coordination with these related efforts.

This initiative expects to coordinate its efforts with the K20 network redesign project, ongoing under the sponsorship of the K20 Network Technology Steering Committee (NTSC). Pending permission from the NTSC, this initiative will translate the artifacts resulting from the NTSC’s redesign effort into the NASCIO framework, and then ask the NTSC to validate the translation.

This initiative also expects to coordinate with the efforts of the Voice over IP EA initiative, through overlap in the documenter team memberships.

5. Key Issues or Decisions to be Addressed

The purpose of the statewide enterprise architecture is to support strategic technology decision-making. Consequently, enterprise architecture initiatives are chartered for the purpose of building a framework (or set of tools) to support important decisions.

The purpose of this section is to document the issues or decisions to be supported by the architectural components produced by this initiative.

The main decision to be addressed by this initiative concerns investing in networking technology/assets. Specifically, the initiative seeks to develop a set of tools (principles, policies, standards, models) to answer the following questions:

How can we ensure that investments in networking assets align with business priorities, eliminate duplication without compromise and where technically and operationally feasible, and maximize interoperability?

What should be the key elements of the state’s plan for strategic investments in networking assets?

Note that the second question above is a primary focus of the K20 network redesign initiative sponsored by the K20 Network Technology Steering Committee (NTSC). Pending permission from the NTSC, the Networking Standards EA Initiative will record the results of the K20 redesign initiative in the NASCIO framework, and then present the resulting components back to NTSC for validation.

of 11

222324

87

88

89

90

91

92

93

94

95

96

97

98

99

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

25





6. Expected Tier One Component Scope

To provide support for making the decisions documented above, this initiative expects to develop the following components:

Solution sets in the solution architecture that describe the “as-is” design of the networks that connect government business locations at the state and local levels of government

Pending permission from the K20 Network Technology Steering Committee (NTSC), solution sets that describe the “as-is” design of the K20 network

Pending permission from the K20 Network Technology Steering Committee (NTSC), and the NTSC completion of the K20 redesign initiative, solution sets that describe the “to-be” design of the K20, SGN, and IGN networks

Policies, standards, and guidelines concerning usage and provisioning of the IGN and SGN solution sets

7. Past Work on this Initiative

This section identifies any past or ongoing work in the area of this initiative, which the Documenter Team can use as a starting point.

This initiative builds on the work of the IGN standard drafting effort that took place in early 2005.

8. Schedule: Document Process

This section identifies the expected schedule for the initiative’s activities and deliverables in the Document Process.

8.1. Key Dates

This section identifies any key dates to which the initiative must align its activities.

The current expectation is that the K20 NTSC will complete its redesign project in March, 2006. Pending NTSC permission, the translation of the NTSC materials into the NASCIO framework will begin after the redesign project is complete. Detailed dates for completing the translation will be provided (in an amended charter for this initiative) once the redesign materials are available.

8.2. Timeline

This section identifies the expected delivery timeline for the initiative’s deliverables. Each enterprise initiative must evolve architectural components (including policies, standards, and guidelines) in accordance with the Architecture Lifecycle documented in the Enterprise Architecture Program’s Program Management Plan. In particular, the evolution of components must follow a progression through specific levels of detail.

This initiative expects to evolve components through the lifecycle levels of detail on the following schedule:

Level of Detail Target Milestone Date

Contextual November 2, 2005

Conceptual December 14, 2005

Logical April 30, 2005 (target)

of 11

262728

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

29


Physical

The Enterprise Architecture Committee and Program recognize that by its very nature, the effort to reach architectural milestones is difficult to predict. At the same time, the Committee and Program have established that the Enterprise Architecture must be in the habit of frequently producing valuable deliverables. Therefore, initiatives must practice effective project management techniques, including time boxing of objectives as needed, to remain on-track with this schedule. Schedule deviations must be communicated and coordinated with the Enterprise Architecture Committee.

The target milestone dates listed above are the EA Program’s best estimate at the outset of the Contextual pass. At the conclusion of each level of detail, the Documenter Team and EA Program will have a much better estimate as to the time required to complete the initiative.

It is the responsibility of the Enterprise Architecture Program to provide project management services to each initiative and Documenter Team.

8.3. Time Commitment of the Documenter Team

This section sets forth the expectations of the Enterprise Architecture Committee and the Enterprise Architecture Program as to what commitment of time and resources will be requested of team members.

In this initiative, team members will be asked to provide existing models and diagrams, and review components as they are drafted. Time commitment is not expected to exceed two hours per week for team members. To support the contribution of team members located outside of the Olympia area, the Enterprise Architecture Program will attempt to conduct as much business as possible in a manner that supports remote participation. It is possible that a small number of meetings may require travel for remote participants.

9. Schedule: Review Process

This section identifies the expected schedule for the initiative’s activities and deliverables in the Review Process. Note that the Review Process need not follow the Document Process sequentially; some of the Review Process milestones may occur during the Document Process timeline.

9.1. Key Dates

This section identifies any key dates to which the initiative must align its activities.

Late December (CAB Meeting)

Late January (CAB Meeting)

Late February (CAB Meeting)

Late March (CAB Meeting)

January 12, 2005 (ISB Meeting)

March 9, 2005 (ISB Meeting)

May 11, 2005 (ISB Meeting)

9.2. Timeline

This section identifies the expected dates on which Review Process milestones will take place. This section must conform to the existing ISB Policy Creation and Update Process maintained by MOSTD, which identifies a Comment and Review followed by an Endorsement Phase.

of 11

303132

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

33


Phase Activity (note stakeholder group) Date

Comment/Revision Review of conceptual pass artifacts with CAB (IT Community)

Late Dec 2005

Review of logical pass artifacts with CAB (IT Community)

Late Jan 2006

Review of logical pass artifacts with ACCIS (Community of Interest)

Feb 2006


Late Feb 2006


Late Mar 2006

Review of proposed policies with Business Executives (Business Executives)

March 2006

ISB Briefing of components and policies Jan, Mar 2006

Endorsement ACCIS Final Endorsement (Community of Interest)

April 2006

CAB Endorsement (IT Community) Late Apr 2006

ISB Adoption of components and policies May 2006

10. Evolving a Single, Cohesive Enterprise Architecture

The Enterprise Architecture Committee has established the goal of having all enterprise initiatives evolve a single, cohesive Tier One Enterprise Architecture for Washington State.

Members of the Documenter Team are asked to share in this goal with the Committee and the Enterprise Architecture Program. The Program will provide the coordination, leadership, and consulting expertise to ensure the achievement of this goal through development of standard architecture artifacts with standard tools and housed in a single repository. The Program will also ensure that artifacts from all initiatives are presented to the stakeholder community as a cohesive architecture, in accordance with the Program’s Communications Plan.

11. Initiative Status Reporting

The Enterprise Architecture Program will prepare an initiative status report for each Enterprise Architecture Committee meeting (every other Wednesday). The status report will contain, at a minimum:

of 11

343536

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

37


Status of initiative versus expected timeline for each level of detail, established above

Indicator of whether this status is on track or not

If no progress has been made on the initiative in the past two weeks, the status report will indicate a reason

The Enterprise Architecture Program Director will circulate the status report for review by the Documenter Team.

12. Initiative Sunset

When either the Documenter Team, Enterprise Architecture Committee, or Enterprise Architecture Program Director believes the initiative has achieved its initial objectives, the topic of closing out the initiative will be placed on the agenda of the Enterprise Architecture Committee. The initiative will be closed, or not, at the discretion of the Committee.

13. Attachments

EA IGN Tier 1 Standards Draft 5.0

IGN Standard Feedback and Questions

IGN Tier One Business Case

of 11

383940

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

41

charter

Education

Transcript of charter