1. 1234567891011 Washington State Enterprise Architecture Program 1213Voice over IP Initiative Charter 14 EA Committee Document 15Version 1.4 16 1

2. 2Washington State Enterprise Architecture ProgramDecember 14, 20053Voice over IP Initiative CharterEA Committee DocumentVersion 1.4417 December 14, 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..........................................................................................................9 298. Schedule: Document Process.....................................................................................................9 30 8.1. Key Dates.............................................................................................................................9 31 8.2. Timeline................................................................................................................................9 32 8.3. Time Commitment of the Documenter Team......................................................................10 339. Schedule: Review Process.......................................................................................................10 34 9.1. Key Dates...........................................................................................................................10 35 9.2. Timeline..............................................................................................................................10 3610.Evolving a Single, Cohesive Enterprise Architecture..............................................................11 3711.Initiative Status Reporting.......................................................................................................11 3812.Initiative Sunset.......................................................................................................................12 3913.Attachments............................................................................................................................12 4041 42431.Document History 44DateVersion EditorChange October 19, 20051.0 Julian SohInitial DraftScott Came November 16, 2005 1.1 Scott Came Updates from 11/11 EACmeeting5Page 2 of 12 3. 6Washington Enterprise Architecture ProgramDecember 14, 2005 7Voice over IP Initiative CharterEA Committee DocumentVersion 1.4 8Date Version EditorChange November 30, 20051.2 Paul Cox Updates from 11/15 DT meeting Scott Came December 14, 20051.4 Scott Came Edits as requested by EAC at 11/30 meeting Plain Talk December 21, 20051.4 Scott Came Adopted by EA Committee45462.DocumentContext47This 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. 9Page 3 of 12 4. 10Washington Enterprise Architecture ProgramDecember 14, 2005 11Voice over IP Initiative CharterEA Committee DocumentVersion 1.4 12 523.Description of the Initiative 53The purpose of this initiative is to provide tools that will assist agencies in making decisions about 54the deployment of Voice over IP technologies.These tools will focus on: 55 Establishing a standard set of measures to assess agencies technical readiness to 56implement Voice over IP 57 Establishing standard factors that agencies should consider in making a business case 58for implementation of Voice over IP 59 Defining standard features of Voice over IP implementations and establishing potential 60standard techniques or protocols for implementing those features 61The initiative will base these tools on the experiences ofand solutions developed byagencies 62participating on the Documenter Team.634.Key Stakeholders64This section identifies key stakeholders of the initiative. 654.1.Enterprise Architecture Committee Stewards66Eachinitiative must have at least one steward from the Enterprise Architecture Committee. 67Committee stewards can be considered as the executive sponsors of the initiative. As such, the 68stewards are responsible for coordinating communication with the Committee, coordinating 69communication with other executive stakeholders, assisting in removal of obstacles to the 70initiatives progress, and assisting in making resources available to the initiative. In all of these 71responsibilities, the Enterprise Architecture Program will support the stewards as needed.72For this initiative, the stewards are: 73 Julian Soh, Chief Information Officer, Department of Revenue (lead) 74 Jim Albert, DIS Deputy Director 754.2.BusinessSponsorship76This initiative has no additional business sponsorship beyond the Enterprise Architecture 77Committee.784.3.Documenter Team79Each initiative must have a Documenter Team, consisting of subject-matter experts and other 80stakeholders who can assist the Enterprise Architecture Program in evolving viable standards, 81policies, guidelines, and architectural components. The expectations, including time commitment, 82of Documenter Team members will be documented later in this document. Note that the term 83Documenter Team originates from the Documenter role in the NASCIO Enterprise Architecture 84framework; this is to signify that the teams objective is to play (or assist in playing) that role as 85defined in the framework, not that the team is responsible for all architectural documentation 86effort in the initiative.87Each Documenter Team should ensure that the following roles are sufficientlycovered. (These 88roles and their definitions are taken from the EA Program Management Plan.) Role Definition/Purpose Executive SponsorCommunicates with key stakeholders on behalf of the initiative 13 Page 4 of 12 5. 14Washington Enterprise Architecture ProgramDecember 14, 2005 15Voice over IP Initiative CharterEA Committee DocumentVersion 1.4 16Role Definition/PurposeEnsures 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 Subject-Matter Provides technical expertise in the initiatives topic areasExpert 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 ManagerMonitors and reports initiatives progress towards milestones Provides logistical support to Documenter Team (meeting coordination, support resources, etc.) Facilitates team meetings and ensures maximum meeting productivity/effectiveness ArchitectSupports 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 teams 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 Teams8990The following table identifies the members of the Documenter Team for this initiative. This 91initiative will not move forward until all of the roles above are satisfied by the team membership. 17 Page 5 of 12 6. 18Washington Enterprise Architecture ProgramDecember 14, 2005 19Voice over IP Initiative CharterEA Committee DocumentVersion 1.4 20Member TitlePhone contact Team role Organization Email contact Julian Soh Department of360-586-9826Executive Sponsor RevenueJulianS@dor.wa.gov Paul Cox Department of360-902-6062Project Manager Labor andCOXP235@lni.wa.gov Industries Paul AmundsunDepartment of360-902-5990SME Labor andAMUP235@lni.wa.gov Industries Colin Corbin Department of360-586-7984SME RevenueColinC@dor.wa.gov David CurtissDepartment of360-902-0162SME LicensingDcurtiss@dol.wa.gov Brian EversonWashington State SME PatrolBeverso@wsp.wa.gov Mike Frost Department of360-902-7506SME Social and HealthFrostmj@dshs.wa.gov Services Geoff LakemanUniversity of206-543-7454SME WashingtonGlakeman@washington.edu John HaddenDepartment of360-664-6547SME LicensingJhadden@dol.wa.gov Stu Lundmark Washington State 360-705-5351SME Patrolstu.lundmark@wsp.wa.gov Jerry MarshDepartment of360-902-0290SME Social and HealthMarshse@dshs.wa.gov Services Fred McDowellLegislative Service360-759-7034SME CenterMcdowell.fred@leg.wa.gov 21Page 6 of 12 7. 22Washington Enterprise Architecture Program December 14, 200523Voice over IP Initiative Charter EA Committee DocumentVersion 1.424 Member Title Phone contact Team roleOrganizationEmail contactEmanuel Perera Department of 360-586-7903SMERevenueEmanuelP@dor.wa.govJoe RussoWashington State360-705-5145SMEPatrolJoseph.Russo@wsp.wa.govBob DeshayeDepartment of 360-902-3336SMEInformationBobd@dis.wa.govServicesDan WebsterWashington State253-536-42884 SMEPatrolDaniel.Webster@wsp.wa.govScott Came Chief Enterprise360-902-3519ArchitectArchitect,Scottca@dis.wa.govDepartment ofInformationServicesPaul WarrenSenior Policy (360) 902-3471Policy Advisor DouglasAdvisorpaulw@dis.wa.govDIS 92 934.4.Coordination with Related Efforts 94This section identifies related efforts (planned or underway) to address issues similar to the95issues in the scope of this initiative. Preferably, representatives from these related efforts will96serve on the initiatives Documenter Team. To the extent this is not possible, this section97documents the strategy for coordination with these related efforts. 98This initiative also expects to coordinate with the effortsof the Networking Standards EA initiative,99through overlap in the documenter team memberships.1005.KeyIssues or Decisions to be Addressed 101The purpose of the statewide enterprise architecture is to support strategic technology decision- 102making. Consequently, enterprise architecture initiatives are chartered for the purpose of building 103a framework (or set of tools) to support important decisions.104The purpose of this section is to documentthe issues or decisions to be supported by the 105architectural components produced by this initiative. 106The framework elements developed in the course of this initiative will assist state agencies in 107making decisions such as:108 Is my agency technically prepared to implement VoIP? If not, what is the gap?25Page 7 of 12 8. 26Washington Enterprise Architecture Program December 14, 200527Voice over IP Initiative Charter EA Committee DocumentVersion 1.428109 Does it make good business sense for my agency to implement VoIP? 110 How can the enterprise ensure that investments in VoIP implementations align with 111business priorities, eliminate duplication without compromise and where technically and 112operationally feasible, and maximize interoperability? 113 What should be the key elements of the states plan for strategic investments in VoIP? 1146.ExpectedTier One Component Scope115To provide support for making the decisions documented above, this initiativewill develop 116components in the enterprise architecture as described in this section.117This section should not be viewed as limiting the scope of the initiative; rather, it is a rough guide 118for what the initiative may accomplish.119The purpose of the first phase of each initiative is to conduct a contextual-level pass at the Tier 120One components to be evolved by the initiative. During this contextual pass, the Enterprise 121Architecture Program and the Documenter Team are expected to define the initiatives scope 122more precisely (in terms of components to be evolved.)123The VoIP Documenter Team expects to identify a set of principles to aid in decision making 124associated with VoIP standard-setting and implementation. For instance, the team has 125traditionally recognized a principle that VoIP should not introduce new telephony requirementsfor 126implementing organizations, absent a business case to the contrary.127The VoIP Documenter Team expects to identify an IP Telephony domain in the technology 128architecture. The team expects this domain to contain the following two Compliance Components 129(guidelines) that will help agencies determine the feasibility of VoIP implementations in their 130environment.131 A technical readiness assessment tool will provide standard guidelines for agencies to 132use in determining whether their internal networks are capable of supporting a VoIP 133implementation 134 A business case factors tool will identify a set of basic factors that agencies should 135consider in making a business case for a VoIP implementation 136The VoIP Documenter Team also expects to define VoIP Solution Sets in the Solution 137Architecture. These Solution Sets will describe existing VoIP implementations in the state 138enterprise, using a standard set of features to structure the descriptions. Each description will 139identify technology standards on which the implementation is based.140After definition of existing Solution Sets, the Documenter Team will explore the definition of VoIP 141implementation profiles that describe to-be Solution Sets that fit defined sets of agency 142requirements and usage scenarios. The Documenter Team recognizes that there will not be a 143one size fits all VoIP implementation, and that the team will define common solutions or 144components without compromise and only where technically and operationally feasible.145The business case factors tool will address, at a minimum, the following factors: 146 Cost 147 Interoperability 148 Flexibility 149 Lifecycle/Scalability 150The technical readiness assessment tool, as well as the standard setof features to be addressed 151in the description of each implementation, will include, at a minimum:152 911/E911 support29Page 8 of 12 9. 30Washington Enterprise Architecture ProgramDecember 14, 200531Voice over IP Initiative CharterEA Committee DocumentVersion 1.432153 Inline power standards 154 Interface to existing telephony solutions, such as PBX 155 Legacy telephony (PSTN) integration 156 Legal requirements 157 Security (confidentiality, intrusion prevention and detection) 158 Virus and patch management processes 159 Operations maintenance processes 1607.Past Work on this Initiative161This section identifies any past or ongoing workin the area of this initiative, which the 162Documenter Team can use as a starting point.163The Enterprise Voice over IP task force was started in July, 2005. Task members were identified 164and selected based upon skills that would allow for informed input related to developing VoIP 165standards recommendations. This task force is cross administration. Several iterations related to 166format and direction has forced this task force to re-develop task force documentation. The task 167force has developed the business drivers and task force scope1688.Schedule:Document Process169This section identifies the expected schedule for the initiatives activities and deliverables in the 170Document Process.1718.1.KeyDates172This section identifies any key dates to which the initiative must align its activities. 173No key dates are identified for this initiative. 1748.2.Timeline175This section identifies the expected delivery timeline for the initiatives deliverables. Each 176enterprise initiative must evolve architectural components (including policies, standards, and 177guidelines) in accordance with the Architecture Lifecycle documented in the Enterprise 178Architecture Programs Program Management Plan. In particular, the evolution of components 179must follow a progression through specific levels of detail.180This initiative expects to evolve components through the lifecycle levels of detail on the following 181schedule:Level of DetailTarget Milestone DateContextual December 14, 2005Conceptual February 1, 2006LogicalApril 1, 2006 (target)Physical18233 Page 9 of 12 10. 34Washington Enterprise Architecture Program December 14, 200535Voice over IP Initiative Charter EA Committee DocumentVersion 1.436183The Enterprise Architecture Committee and Program recognize that by its very nature, the effort 184to reach architectural milestones is difficult to predict. At the same time, the Committee and 185Program have established that the Enterprise Architecture must be in the habit of frequently 186producing valuable deliverables. Therefore, initiatives must practice effective project 187management techniques, including time boxing of objectives as needed, to remain on-track with 188this schedule. Schedule deviations must be communicated and coordinated with the Enterprise 189Architecture Committee.190The target milestone dates listed above are the EA Programs best estimate at the outset ofthe 191Contextual pass. At the conclusion of each level of detail, the Documenter Team and EA 192Program will have a much better estimate as to the time required to complete the initiative.193It is the responsibility of the Enterprise Architecture Program to provide project management 194services to each initiative and Documenter Team.1958.3.TimeCommitment of the Documenter Team196This section sets forth the expectations of the Enterprise Architecture Committee and the 197Enterprise Architecture Program as to what commitment of time and resources will be requested 198of team members.199Documenter teamis composed of cross administration Subject Matter Experts (SME). The task 200force meets everytwo weeks for two hours. Assignments and tasks are delegated amongst the 201team.2029.Schedule:Review Process 203This section identifies the expected schedule for the initiatives activities and deliverables in the 204Review Process. Note that the Review Process need not follow the Document Process 205sequentially; some of the Review Process milestones may occur during the Document Process 206timeline.2079.1.Key Dates208This section identifies any key dates to which the initiative must align its activities. 209 Monthly Customer Advisory Board (CAB) meetings 210 Information Services Board (ISB) meetings in March, May, and July 2119.2.Timeline212This section identifies the expected dates on which Review Process milestones will take place. 213This section must conform to the existing ISB Policy Creation and Update Process maintained by 214MOSTD, which identifies a Comment and Review followed by an Endorsement Phase. 21537Page 10 of 12 11. 38Washington Enterprise Architecture ProgramDecember 14, 200539Voice over IP Initiative CharterEA Committee DocumentVersion 1.440 PhaseActivity (note stakeholder group)DateComment/Revision Review of conceptual pass artifacts with CAB Jan. 2006(IT Community) Review of conceptual pass artifacts with CAB Feb. 2006(IT Community) Review of logical pass artifacts with CAB (ITMarch 2006Community) Review of logical pass artifacts with CAB (ITApril 2006Community) Initial presentation of logical pass artifacts toMarch 2006ISBEndorsementCAB Endorsement (IT Community) May 2006 ISB Adoption of components and policiesJuly 200621621710.Evolvinga Single, Cohesive Enterprise Architecture 218The Enterprise Architecture Committee has established the goal of having all enterprise initiatives 219evolve a single, cohesive Tier One Enterprise Architecture for Washington State.220Members of the Documenter Team are asked to share in this goal with the Committee and the 221Enterprise Architecture Program. The Program will provide the coordination, leadership, and 222consulting expertise to ensure the achievement of this goal through development of standard 223architecture artifacts with standard tools and housed in a single repository. The Program will also 224ensure that artifacts from all initiatives are presented to the stakeholder community as a cohesive 225architecture, in accordance with the Programs Communications Plan.22611.Initiative Status Reporting 227The Enterprise Architecture Program will prepare an initiative status report for each Enterprise 228Architecture Committee meeting (every other Wednesday). The status report will contain, at a 229minimum:230 Status of initiative versus expected timeline for each level of detail, established above 231 Indicator of whether this status is on track or not 232 If no progress has been made on the initiative in the past two weeks, the status report will 233 indicate a reason 234The Enterprise Architecture Program Director will circulate the status report for review by the 235Documenter Team.41Page 11 of 12 12. 42Washington Enterprise Architecture ProgramDecember 14, 200543Voice over IP Initiative CharterEA Committee DocumentVersion 1.44423612.Initiative Sunset 237When either the Documenter Team, Enterprise Architecture Committee, or Enterprise 238Architecture Program Director believes the initiative has achieved its initial objectives, the topic of 239closing out the initiative will be placed on the agenda of the Enterprise Architecture Committee. 240The initiative will be closed, or not, at the discretion of the Committee.24113.Attachments 242 None45 Page 12 of 12