1 / 17

Ohio Digital Government Summit October 2004

Ohio Digital Government Summit October 2004. OH*1 Project Charter.

Download Presentation

Ohio Digital Government Summit October 2004

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Ohio Digital Government SummitOctober 2004

  2. OH*1 Project Charter • Develop an OH*1, Next-Generation Network that is reliable, redundant, and demonstrates quality of service characteristics by effectively aggregating the converged (voice, data, video) communications needs of Ohio state government that includes 120 agencies, boards, and commissions. • Allow other governmental entities to leverage the service and/or pricing derived out of the state telecommunication investment. Other governmental entities may include: • 384 courts, 118 clerks offices, integrated justice partners, the public, and related state agencies to a secure centralized data repository • 2,300 local governments 700 public library facilities • Over 2,500 K-12 facilities

  3. OH*1 Goals • Identify Network Alternatives • Develop technical, support and financial requirements • Surface technology issues • Examine feasibility of utilizing a private fiber infrastructure • Develop strategic network architecture • Design • Services (data, video, voice) • Security • Support

  4. OH*1 Quality Factors / Principles

  5. Project Approach OH*1 Project Objective: Create a statewide communication vision, strategy, and enterprise architecture with a governance model that reduces operational risk and effectively aggregates bandwidth. Lifecycle Methodology Perform Network Traffic and Capacity Analysis Gather and Analyze Network Requirements RecommendNetworkArchitecture Business Case Development Marketing Plan Development Project Phases Current Network Architecture Project Kickoff • Develop Project Charter • Develop Project Plan • Identify key contacts • Develop a Strategy for Communications • Review current network environment • Compile and update network documentation • Review financial information related to the network • Review strategic plans and existing projects • Identify key sources for business and network detail • Collect data via interviews, surveys, focus groups, etc. • Document technical and functional requirements • Collect critical utilization data on current network • Identify new network requirements and project future traffic demands • Document analysis • Develop critical design criteria and parameters • Identify network architecture alternatives • Identify estimated cost • Assess impact of new and emerging technologies • Develop cost benefit analysis • Develop preliminary business case • Assess risk and complexity • Refine and final-ize business case • Develop deploy-ment strategy • Identify guiding principles and philosophies • Define categories of products and target audiences • Develop catalog of specific service offerings • Identify programs to communicate service offerings KeyDeliverables

  6. Current Ohio Infrastructure

  7. *Source: Network Inventory Database - April 3, 2003 DAS/Computer Services Division/Network Services Current Environment • 98.5 % of the lines currently on State of Ohio Multi-Agency Communications Systems (SOMACS) contract* will be affected by the expiration of the contract. (12931 lines out of 13127) • There are 7538 Lottery Analog lines that are part of the SOMAC contract. • The remaining 5393 lines support DS0, DS1, DS3, OC3, 0C12, OC48, FE, GE traffic throughout the agencies. • 1.5% of the lines currently on other contracts will not necessarily expire at the same time as SOMACS. (196 lines out of 13127) • 21% of 5393 lines have a presence in the county that a POP for TFN is located. • Core WAN protocols include TCP/IP, IPX, Transactional Bridging, AppleTalk, Vines and CLNS. • Network Management Applications include HP Openview, IBM/Tivoli, Cabletron Spectrum, CA Unicenter TNG, AT&T Accumaster and SUN NetManager

  8. OH*1 Future Network Architecture • State Fiber Network and Service Provider Networks will be dual connected to provide additional level of connectivity and redundancy • The network addressing tags will be maintained and routing is enabled between the two networks to enable communication between services as required

  9. State Fiber Network Design

  10. State Owned Fiber & Service Provider OH*1 Network Description • The State Fiber Network would constitute the foundational backbone for the statewide network • “Last Mile Connectivity” would be provisioned either to State Fiber Network or Service Provider POP’s depending on distance, availability and cost • Interconnectivity between State Fiber Network and Service providers (telco’s, cable, fiber, and wireless) will provide core network redundancy. Routing and switching information would be maintained across the entire network • Required services (data, video, & voice) would be made available to the agencies on demand • The State may elect to manage the OH*1 network including the ring and switching layers • OARnet will manage the fiber ring optics • The number of wavelengths (lambdas) enabled would be proportional to the number of services (data, video, & voice) enabled

  11. OH*1 Proposed Network Map over TFN

  12. OH*1 Network Architecture

  13. Sample Connectivity

  14. OH*1 POP Local Office Layer 2/3 Switch Transport Core VLAN 10 Wireless VLAN 20 IP Phones VLAN 30 Workstations VLAN 40 VLAN 50 Servers Sample Local Office Connectivity

  15. Sample Last Mile Connectivity Layer 2/3 Switch OH*1 POP Transport Core Printer PCs • POP • Layer 2/3 Switch Medium/ Large Location Layer 2/3 Switch Servers 10/100/1000 Workstations Small Location

  16. Last Mile Connectivity with Firewall Option Layer 2/3 Switch OH*1 POP Transport Core Printer Firewall PCs • POP • Layer 2/3 Switch Medium/ Large Location Layer 2/3 Switch Servers 10/100/1000 Firewall Workstations Small Location

  17. Next Steps • Review and finalize OH*1 network architecture, including POP locations and ‘Last Mile’ options • Validate traffic modeling statistics • Current application • Future applications • Review security approach • Develop Business Plan

More Related