1

2

3

4

5

6

7

8

9

10

11   Washington State Enterprise Architecture Program
12

13        Networking Standards In...
2Washington State Enterprise Architecture Program                                                                     Dece...
6Washington Enterprise Architecture Program                                                 December 7, 2005
7Networking S...
10Washington Enterprise Architecture Program                                             December 7, 2005
11Networking Sta...
14Washington Enterprise Architecture Program                                               December 7, 2005
15Networking S...
18Washington Enterprise Architecture Program                                            December 7, 2005
19Networking Stan...
22Washington Enterprise Architecture Program                                               December 7, 2005
 23Networking ...
26Washington Enterprise Architecture Program                                                December 7, 2005
 27Networking...
30Washington Enterprise Architecture Program                                                December 7, 2005
 31Networking...
34Washington Enterprise Architecture Program                                                 December 7, 2005
 35Networkin...
38Washington Enterprise Architecture Program                                              December 7, 2005
 39Networking S...
Upcoming SlideShare
Loading in...5
×

charter

257

Published on

Published in: Education, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
257
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "charter"

  1. 1. 1 2 3 4 5 6 7 8 9 10 11 Washington State Enterprise Architecture Program 12 13 Networking Standards Initiative Charter 14 EA Committee Document 15 Version 1.4 16 1
  2. 2. 2Washington State Enterprise Architecture Program December 7, 2005 3Networking Standards Initiative Charter EA Committee Document—Version 1.4 4 17 December 7, 2005Table of Contents 181. Document History.......................................................................................................................2 192. Document Context......................................................................................................................3 203. Description of the Initiative..........................................................................................................4 214. Key Stakeholders........................................................................................................................4 22 4.1. Enterprise Architecture Committee Stewards.......................................................................4 23 4.2. Business Sponsorship..........................................................................................................4 24 4.3. Documenter Team................................................................................................................4 25 4.4. Coordination with Related Efforts.........................................................................................7 265. Key Issues or Decisions to be Addressed...................................................................................7 276. Expected Tier One Component Scope........................................................................................8 287. Past Work on this Initiative..........................................................................................................8 298. Schedule: Document Process.....................................................................................................8 30 8.1. Key Dates.............................................................................................................................8 31 8.2. Timeline................................................................................................................................8 32 8.3. Time Commitment of the Documenter Team........................................................................9 339. Schedule: Review Process.........................................................................................................9 34 9.1. Key Dates.............................................................................................................................9 35 9.2. Timeline................................................................................................................................9 3610. Evolving a Single, Cohesive Enterprise Architecture..............................................................10 3711. Initiative Status Reporting.......................................................................................................10 3812. Initiative Sunset.......................................................................................................................11 3913. Attachments............................................................................................................................11 40 41 42 431.Document History 44 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 5 Page 2 of 11
  3. 3. 6Washington Enterprise Architecture Program December 7, 2005 7Networking Standards Initiative Charter EA Committee Document—Version 1.4 8 Date Version Editor Change 11/2/2005 1.2 Scott Came • Adjustments to solution sets Jim Albert • Edits to usage standards scope statement 11/30/2005 1.3 Scott Came • Remove initial straw-model Jim Albert • 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 45 462.Document Context 47This document currently has EA Committee Document status. This status signifies that the 48document has been adopted by a vote of the ISB Enterprise Architecture Committee. 49For more information about the Enterprise Architecture Program or the ISB Enterprise 50Architecture Committee and its initiatives, please visit the EA Committee website at: 51http://isb.wa.gov/committees/enterprise/index.aspx. 9 Page 3 of 11
  4. 4. 10Washington Enterprise Architecture Program December 7, 2005 11Networking Standards Initiative Charter EA Committee Document—Version 1.4 12 523.Description of the Initiative 53The purpose of this enterprise initiative is to develop policies, standards, and guidelines for 54network infrastructure solutions, assets, and services that are common statewide. The initiative 55seeks to evolve a set of Tier One components in the statewide Enterprise Architecture. 56The business case for this initiative is to support the making of key decisions documented in the 57section “Key Issues or Decisions to be Addressed” below. 584.Key Stakeholders 59This section identifies key stakeholders of the initiative. 604.1.Enterprise Architecture Committee Stewards 61Each initiative must have at least one steward from the Enterprise Architecture Committee. 62Committee stewards can be considered as the executive sponsors of the initiative. As such, the 63stewards are responsible for coordinating communication with the Committee, coordinating 64communication with other executive stakeholders, assisting in removal of obstacles to the 65initiative’s progress, and assisting in making resources available to the initiative. In all of these 66responsibilities, the Enterprise Architecture Program will support the stewards as needed. 67For this initiative, the stewards are: 68 • Jim Albert, DIS Deputy Director (lead) 69 • Julian Soh, Chief Information Officer, Department of Revenue 704.2.Business Sponsorship 71This initiative has no additional business sponsorship beyond the Enterprise Architecture 72Committee. 734.3.Documenter Team 74Each initiative must have a Documenter Team, consisting of subject-matter experts and other 75stakeholders who can assist the Enterprise Architecture Program in evolving viable standards, 76policies, guidelines, and architectural components. The expectations, including time commitment, 77of Documenter Team members will be documented later in this document. Note that the term 78“Documenter Team” originates from the Documenter role in the NASCIO Enterprise Architecture 79framework; this is to signify that the team’s objective is to play (or assist in playing) that role as 80defined in the framework, not that the team is responsible for all architectural documentation 81effort in the initiative. 82Each Documenter Team should ensure that the following roles are sufficiently covered. (These 83roles 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 13 Page 4 of 11
  5. 5. 14Washington Enterprise Architecture Program December 7, 2005 15Networking Standards Initiative Charter EA Committee Document—Version 1.4 16 Role Definition/Purpose Subject-Matter Provides technical expertise in the initiative’s topic areas Expert 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 84 85The following table identifies the members of the Documenter Team for this initiative. This 86initiative will not move forward until all of the roles above are satisfied by the team membership. Member Title Phone contact Team role Organization Email contact Jim Albert Deputy Director (360) 902-9885 Executive Sponsor DIS jima@dis.wa.gov Julian Soh Chief Information 360-586-9826 Executive Sponsor Officer, DOR JulianS@dor.wa.gov 17 Page 5 of 11
  6. 6. 18Washington Enterprise Architecture Program December 7, 2005 19Networking Standards Initiative Charter EA Committee Document—Version 1.4 20 Member Title Phone contact Team role Organization Email contact Geoff Lakeman University of glakeman@cac.washington.edu SME Washington Mike Frost DSHS (360) 902-7506 SME frostmj@dshs.wa.gov Mike McVicker Assistant Director (360) 902-3335 SME DIS mikem@dis.wa.gov Michael Partlow DIS (360) 902-2291 SME michaelp@dis.wa.gov Ron Kappes DIS (360) 902-3355 SME ronk@dis.wa.gov Mark Fortier OFM (360) 902-0604 SME mark@ofm.wa.gov Fred McDowell LSC (360) 786-7034 SME mcdowell.fred@leg.wa.gov Dennis DeFries Network Services (360) 705-7707 SME Manager defries@wsdot.wa.gov WSDOT David Curtiss DOL (360) 902-0162 SME dcurtiss@dol.wa.gov Stu Lundmark Washington State 360-705-5351 SME Patrol stu.lundmark@wsp.wa.gov Joe Russo Washington State 360-705-5145 SME Patrol Joseph.Russo@wsp.wa.gov 21 Page 6 of 11
  7. 7. 22Washington Enterprise Architecture Program December 7, 2005 23Networking Standards Initiative Charter EA Committee Document—Version 1.4 24 Member Title Phone contact Team role Organization Email contact Peter Tamayo Chief Information (360) 664-6758 Officer, DRS petert@dis.wa.gov SME Scott Came Chief Architect (360) 902-3519 Project Manager DIS scottca@dis.wa.gov Architect Paul Warren Senior Policy (360) 902-3471 Policy Advisor Douglas Advisor paulw@dis.wa.gov DIS 87 884.4.Coordination with Related Efforts 89This section identifies related efforts (planned or underway) to address issues similar to the 90issues in the scope of this initiative. Preferably, representatives from these related efforts will 91serve on the initiative’s Documenter Team. To the extent this is not possible, this section 92documents the strategy for coordination with these related efforts. 93This initiative expects to coordinate its efforts with the K20 network redesign project, ongoing 94under the sponsorship of the K20 Network Technology Steering Committee (NTSC). Pending 95permission from the NTSC, this initiative will translate the artifacts resulting from the NTSC’s 96redesign effort into the NASCIO framework, and then ask the NTSC to validate the translation. 97This initiative also expects to coordinate with the efforts of the Voice over IP EA initiative, through 98overlap in the documenter team memberships. 995.Key Issues or Decisions to be Addressed 100The purpose of the statewide enterprise architecture is to support strategic technology decision- 101making. Consequently, enterprise architecture initiatives are chartered for the purpose of building 102a framework (or set of tools) to support important decisions. 103The purpose of this section is to document the issues or decisions to be supported by the 104architectural components produced by this initiative. 105The main decision to be addressed by this initiative concerns investing in networking technology/ 106assets. Specifically, the initiative seeks to develop a set of tools (principles, policies, standards, 107models) to answer the following questions: 108 • How can we ensure that investments in networking assets align with business priorities, 109 eliminate duplication without compromise and where technically and operationally 110 feasible, and maximize interoperability? 111 • What should be the key elements of the state’s plan for strategic investments in 112 networking assets? 113Note that the second question above is a primary focus of the K20 network redesign initiative 114sponsored by the K20 Network Technology Steering Committee (NTSC). Pending permission 115from the NTSC, the Networking Standards EA Initiative will record the results of the K20 redesign 116initiative in the NASCIO framework, and then present the resulting components back to NTSC for 117validation. 25 Page 7 of 11
  8. 8. 26Washington Enterprise Architecture Program December 7, 2005 27Networking Standards Initiative Charter EA Committee Document—Version 1.4 28 1186.Expected Tier One Component Scope 119To provide support for making the decisions documented above, this initiative expects to develop 120the following components: 121 • Solution sets in the solution architecture that describe the “as-is” design of the networks 122 that connect government business locations at the state and local levels of government 123 • Pending permission from the K20 Network Technology Steering Committee (NTSC), 124 solution sets that describe the “as-is” design of the K20 network 125 • Pending permission from the K20 Network Technology Steering Committee (NTSC), and 126 the NTSC completion of the K20 redesign initiative, solution sets that describe the “to-be” 127 design of the K20, SGN, and IGN networks 128 • Policies, standards, and guidelines concerning usage and provisioning of the IGN and 129 SGN solution sets 1307.Past Work on this Initiative 131This section identifies any past or ongoing work in the area of this initiative, which the 132Documenter Team can use as a starting point. 133This initiative builds on the work of the IGN standard drafting effort that took place in early 2005. 1348.Schedule: Document Process 135This section identifies the expected schedule for the initiative’s activities and deliverables in the 136Document Process. 1378.1.Key Dates 138This section identifies any key dates to which the initiative must align its activities. 139The current expectation is that the K20 NTSC will complete its redesign project in March, 2006. 140Pending NTSC permission, the translation of the NTSC materials into the NASCIO framework will 141begin after the redesign project is complete. Detailed dates for completing the translation will be 142provided (in an amended charter for this initiative) once the redesign materials are available. 1438.2.Timeline 144This section identifies the expected delivery timeline for the initiative’s deliverables. Each 145enterprise initiative must evolve architectural components (including policies, standards, and 146guidelines) in accordance with the Architecture Lifecycle documented in the Enterprise 147Architecture Program’s Program Management Plan. In particular, the evolution of components 148must follow a progression through specific levels of detail. 149This initiative expects to evolve components through the lifecycle levels of detail on the following 150schedule: Level of Detail Target Milestone Date Contextual November 2, 2005 Conceptual December 14, 2005 Logical April 30, 2005 (target) 29 Page 8 of 11
  9. 9. 30Washington Enterprise Architecture Program December 7, 2005 31Networking Standards Initiative Charter EA Committee Document—Version 1.4 32 Physical 151 152The Enterprise Architecture Committee and Program recognize that by its very nature, the effort 153to reach architectural milestones is difficult to predict. At the same time, the Committee and 154Program have established that the Enterprise Architecture must be in the habit of frequently 155producing valuable deliverables. Therefore, initiatives must practice effective project 156management techniques, including time boxing of objectives as needed, to remain on-track with 157this schedule. Schedule deviations must be communicated and coordinated with the Enterprise 158Architecture Committee. 159The target milestone dates listed above are the EA Program’s best estimate at the outset of the 160Contextual pass. At the conclusion of each level of detail, the Documenter Team and EA 161Program will have a much better estimate as to the time required to complete the initiative. 162It is the responsibility of the Enterprise Architecture Program to provide project management 163services to each initiative and Documenter Team. 1648.3.Time Commitment of the Documenter Team 165This section sets forth the expectations of the Enterprise Architecture Committee and the 166Enterprise Architecture Program as to what commitment of time and resources will be requested 167of team members. 168In this initiative, team members will be asked to provide existing models and diagrams, and 169review components as they are drafted. Time commitment is not expected to exceed two hours 170per week for team members. To support the contribution of team members located outside of the 171Olympia area, the Enterprise Architecture Program will attempt to conduct as much business as 172possible in a manner that supports remote participation. It is possible that a small number of 173meetings may require travel for remote participants. 1749.Schedule: Review Process 175This section identifies the expected schedule for the initiative’s activities and deliverables in the 176Review Process. Note that the Review Process need not follow the Document Process 177sequentially; some of the Review Process milestones may occur during the Document Process 178timeline. 1799.1.Key Dates 180This section identifies any key dates to which the initiative must align its activities. 181 • Late December (CAB Meeting) 182 • Late January (CAB Meeting) 183 • Late February (CAB Meeting) 184 • Late March (CAB Meeting) 185 • January 12, 2005 (ISB Meeting) 186 • March 9, 2005 (ISB Meeting) 187 • May 11, 2005 (ISB Meeting) 1889.2.Timeline 189This section identifies the expected dates on which Review Process milestones will take place. 190This section must conform to the existing ISB Policy Creation and Update Process maintained by 191MOSTD, which identifies a Comment and Review followed by an Endorsement Phase. 33 Page 9 of 11
  10. 10. 34Washington Enterprise Architecture Program December 7, 2005 35Networking Standards Initiative Charter EA Committee Document—Version 1.4 36 192 Phase Activity (note stakeholder group) Date Comment/Revision Review of conceptual pass artifacts with CAB Late Dec 2005 (IT Community) Review of logical pass artifacts with CAB (IT Late Jan 2006 Community) Review of logical pass artifacts with ACCIS Feb 2006 (Community of Interest) Review of logical pass artifacts with CAB (IT Late Feb 2006 Community) Review of logical pass artifacts with CAB (IT Late Mar 2006 Community) Review of proposed policies with Business March 2006 Executives (Business Executives) ISB Briefing of components and policies Jan, Mar 2006 Endorsement ACCIS Final Endorsement (Community of April 2006 Interest) CAB Endorsement (IT Community) Late Apr 2006 ISB Adoption of components and policies May 2006 193 19410.Evolving a Single, Cohesive Enterprise Architecture 195The Enterprise Architecture Committee has established the goal of having all enterprise initiatives 196evolve a single, cohesive Tier One Enterprise Architecture for Washington State. 197Members of the Documenter Team are asked to share in this goal with the Committee and the 198Enterprise Architecture Program. The Program will provide the coordination, leadership, and 199consulting expertise to ensure the achievement of this goal through development of standard 200architecture artifacts with standard tools and housed in a single repository. The Program will also 201ensure that artifacts from all initiatives are presented to the stakeholder community as a cohesive 202architecture, in accordance with the Program’s Communications Plan. 20311.Initiative Status Reporting 204The Enterprise Architecture Program will prepare an initiative status report for each Enterprise 205Architecture Committee meeting (every other Wednesday). The status report will contain, at a 206minimum: 37 Page 10 of 11
  11. 11. 38Washington Enterprise Architecture Program December 7, 2005 39Networking Standards Initiative Charter EA Committee Document—Version 1.4 40 207 • Status of initiative versus expected timeline for each level of detail, established above 208 • Indicator of whether this status is on track or not 209 • If no progress has been made on the initiative in the past two weeks, the status report will 210 indicate a reason 211The Enterprise Architecture Program Director will circulate the status report for review by the 212Documenter Team. 21312.Initiative Sunset 214When either the Documenter Team, Enterprise Architecture Committee, or Enterprise 215Architecture Program Director believes the initiative has achieved its initial objectives, the topic of 216closing out the initiative will be placed on the agenda of the Enterprise Architecture Committee. 217The initiative will be closed, or not, at the discretion of the Committee. 21813.Attachments 219 • EA IGN Tier 1 Standards Draft 5.0 220 • IGN Standard Feedback and Questions 221 • IGN Tier One Business Case 41 Page 11 of 11

×