1 AZNet II Steering Committee June 16, 2014. 2 Agenda AZNet II Steering Committee | 2014 » Opening Remarks » Refresh Status/Updates » Dashboard and Solarwinds.

Slides:



Advertisements
Similar presentations
© Exordium Networks All Rights Reserved. Agenda 1. Our Understanding of your needs 2. Our Recommended Solution 3. Who we are 4. Solution Pricing.
Advertisements

Shared Resources For Telecommunications Project Update – February 22, 2001 Arizona Department of Transportation.
University of Baltimore Telecommunications Technology
AZNet II – Arizona Network
BAI613 Module 2 - Voice over IP Technology. Module Objectives 1. Describe the benefits of IP Telephony/Packet Telephony/VoIP over traditional telephone.
MX25: Multifunction SIP Gateway Zultys Technologies.
Overview of DVX 9000.
Voxiplus.
Mobile to landline or Landline to Mobile Costs PhP 7.00/min GSM Carriers(SMART,GLOBE,SUN)Landline Carrier (PLDT etc.) Business Legacy PBX.
All Transportation Counts The Sky’s the Limit! Greg Jackson State of Ohio Chief Information Officer October 7-8, 2003 Ohio University, Athens.
Lean Program at CTS and Incident Management Notification Project.
* County Seat is Back to Map End Answer * County Seat is Back to Map End Answer.
Arizona Long Term Care (ALTCS) An Overview. Determined by the AHCCCS Division of Member Services (DMS) Casa Grande Chinle Cottonwood Flagstaff Glendale.
CISCO IP TELEPHONY Phone System, 2 Years Later. Presented By: John Nickell, Technology Director and Bill Koegle, Technology and Network Specialist. North.
1 Introduction to Aeonix Presented by:. 2 What is Aeonix?
VoipNow Core Solution capabilities and business value.
11 Public Safety Recording – Sharing Resources Quality, Accountability, Reliability. and Performance for the Mission-critical Environment Western Regional.
New Opportunities with Telecommunications Technology change in the telecommunications infrastructure is opening new doors to increased service levels,
ICT Infrastructure Project 19 May Limpopo Profile According to the National Census of 2001 Limpopo is home to 11.8% of South Africa’s population.
Use of Informational Change Request to Communicate Agency Changes.
Connecting to Remote Networks © 2004 Cisco Systems, Inc. All rights reserved. Using Circuit Switching in WANs INTRO v2.0—7-1.
ENTERPRISE NETWORK IMPLEMENTATION
Lesson 18-Internet Architecture. Overview Internet services. Develop a communications architecture. Design a demilitarized zone. Understand network address.
June 16, 2010 GovTrip Notification of Foreign Travel Workshop.
TDC 461: Wide Area Network Services DePaul University 22 May, 2001.
Facilitated by: FACILITATOR Community Needs Assessment Template Community Health Needs Assessment R National Center for Rural Health Works Community Needs.
Arizona Telecommunications! The Center for Computing & Information Technologies Fred Neasham, Technical Support Program Coordinator.
Mediacom. More Than Cable Mediacom is the nation’s 8 th largest cable company Brings broadband to community anchor institutions, including school districts,
AASTRA CLEARSPAN: CAMPUS PHONE SYSTEM IT SERVICES TECH TALK TUESDAY, FEBRUARY 24, 2015.
1 CCM Deployment Models Wael K. Valencia Community College.
Employee Self Service Demo December 17, 2009 Presented by: Michael Grisser Jeanie Robards.
Services Tailored Around You® Business Contingency Planning Overview July 2013.
Welcome to the Minnesota SharePoint User Group. Introductions / Overview Project Tracking / Management / Collaboration via SharePoint Multiple Audiences.
Large Enterprise with Multiple Locations Source: Avaya.
1 IT Governance 2006 Strategy/Business Case Presentation Department of Human Services.
Tennessee Network Update >> Gathering of State Networks February 9, 2005.
Administration and Finance Incident Prioritization Document
Current Job Components Information Technology Department Network Systems Administration Telecommunications Database Design and Administration.
Corporate Information Systems Delivery of Infrastructure IT Services.
Presentation by Paul Vine In partnership with Version Sabre and Business Continuity Planning.
Networking LAN (Local Area Network)  A network is a collection of computers that communicate with each other through a shared network medium.  LANs.
Network Hardware (I) Networks and Protocols Prepared by: TGK First Prepared on: Last Modified on: Quality checked by: Copyright 2009 Asia Pacific Institute.
VoIP Technology Briefing
Citywide Voice and Video Using Asterisk and Open-Source Embedded Hardware Kelvin Chua Chief Technology Officer NEXTix Inc. Astricon 2009.
1 Proprietary & Confidential December 9, 2008 Bandwidth.com Saving You Money Through Voice & Data.
GOVERNOR’S EARLY CHILDHOOD ADVISORY COUNCIL (ECAC) September 9, 2014.
IP TELEPHONY AT THE AUSTRALIAN CATHOLIC UNIVERSITY A CASE STUDY WIL DANIELS MANAGER, INFORMATION TECHNOLOGY SERVICES.
Client Presentation. When you choose Telechoice Consulting, you will get the attention you deserve. First, we provide a no obligation, in-depth analysis.
October 10-13, 2006 San Diego Convention Center, San Diego California Effective Deployment and Migration Strategies Leigh Fatzinger, VP.
ICT Infrastructure Used By Organisations Additional Exercise ANSWERS.
STATE OF ARIZONA DEPARTMENT OF ADMINISTRATION INFORMATION SERVICES DIVISION May 2008 Assistant Director and CIO
NOAA Aviation Safety Board Meeting May 16, 2006 Lieutenant Commander Debora Barr NOAA Aviation Safety Program.
Employee Self Service Demo October 20, 2009 Presented by: Michael Grisser Jeanie Robards.
The free and easy way to manage your lab. Teaching Presentation.
PRP XFG ENGAGEMENT PLAN July © 2015 Xchanging plc AGENDA 2  Who are we engaging with?  What are we doing?  Why are we doing it?  The project.
Training Module: APD Template County APD Process Training November 16, 2007 California Health and Human Services Agency - Office of Systems Integration.
Transportation, Technology, Infrastructure Committee February 2016 HOUSTON IT SERVICES (HITS) TINA CARKHUFF, INTERIM DIRECTOR/CIO.
The Future of IP Telephony Kevin Gavin Chief Marketing Officer Andrew Pryfogle Director of Sales GoBeam Communications.
Out of Sight, But Not Out of Touch Remote Office, Branch Office IP Telephony Solutions Charles Henderson Director, Product Management EADS TELECOM North.
ADOT RCN DCR MAGTAG Update Meeting WELCOME. - Background - Stage I (Draft Initial DCR) - Stage II (Initial DCR) - Project Focus Area - Stage III (Final.
SIP & How It Relates To YOUR Business. Jeff S. Olson Director of Marco Carrier Services David Bailey-Aldrich Technology.
Computer Networks.  Which is the best definition of a circuit switched network?  An electric circuit where the connections get switched based on who.
OUR FOCUS… We utilise the latest technological advances in telecommunications services. Business to business telephone systems with all associated outbound.
Telephone Service Andrea Beesing November 15, 2016.
ECEN5553 Telecom Systems Week #9 Read [17a] "Rapidly Recovering from the Catastrophic Loss of a Major Telecom Office" [17b] "How IT Leaders Can Best.
Introducing FOR LIBRARIES.
SIP Trunk Deployment Use Case WellStar Health System
The Design Process—Planning
SIP Trunk Deployment Use Case WellStar Health System
Marius Jennings | Open Data Project Manager
Presentation transcript:

1 AZNet II Steering Committee June 16, 2014

2 Agenda AZNet II Steering Committee | 2014 » Opening Remarks » Refresh Status/Updates » Dashboard and Solarwinds » IP Telephony Shared Resources » Closing Remarks

REFRESH STATUS/UPDATES

4 AZNet II Steering Committee | 2014 Refresh Status / Projects Completed Sites Completed # Seats Affected Sites Completed # Seats Affected Sites Completed Total Sites Refreshed To Date: 162 Total Seats Affected: * 2014 To Date N ETWORK R EFRESH V OICE R EFRESH C ALL C ENTER * 2014 reflects up to May 2014

AZNet II Steering Committee | 2014 Refresh Status Updates » Focus on Legacy Voice Platforms » Communicate state wide on still in service legacy systems as to increase decommissioning of systems » Communication to All » Agency, Boards and Commission, communications for refresh. » Identifying those not contacted at this point and beginning talks. » Voice Cut Sheets » Help when needed and time frames for cut offs/changes

DASHBOARD AND SOLARWINDS

AZNet II Steering Committee | 2014 Dashboard and Solarwinds To Request Access: » Open an RFI ticket via AZNet Support Desk Maximum 5 accounts per Agency » Include name, and phone # for each account requested AZNet II Solarwinds and Sharepoint access will also be provided with this request Content : » Service Level Requirement (SLR) Reports Agency and Core SLR Reports » Trending Reports Various reports for month-over-month SLR trending » Other Reports Non-SLR reports or links to documents/maps, etc. AZNet II Solarwinds or SharePoint access may also be needed to view these items.

IP TELEPHONY SHARED RESOURCES

AZNet II – Shared PSTN Resources Shared Resource Proposal Cost Savings Proposed Shared Resource Locations Number of Offices per Shared Location Agencies that will benefit

AZNet II – Shared PSTN Resources Shared Resource Proposal The State of Arizona currently have offices throughout the state both in small remote cities and heavily populated areas. Most of these sites have dedicated circuits, some digital T1/PRI’s (Primary Rate ISDN) and some are standard analog lines that do not support DID’s (Direct Inward Dialing). Dedicated circuits cost money and may not be fully utilized, for instance an office with a PRI, (23) voice circuits, may only require a maximum of 5 circuits to support their business needs but the PRI may be required to support DID’s. This resource can be shared with other agencies within the same calling area reducing the circuits costs at the other agencies while sharing the total cost of the PRI.

AZNet II – Shared PSTN Resources Shared Resource Proposal Cont’d Some agencies only have analog lines available, which does not support DID’s. With a shared T1/PRI DID’s can now be available to these agencies without the added cost of a dedicated PRI. Finally shared resources can also reduce the cost of instate long distance which all agencies can benefit from. To explain further, a shared PRI located in Kingman can be used to route all calls, from around the state, local to the Kingman calling area out this PRI. No long distance charges will apply for any of these calls.

AZNet II – Shared PSTN Resources Shared Resource Proposal Cont’d Redundancy is inherent with shared resources for outbound calling, if a circuit is down due to carrier failure the outbound calls can be rerouted to other shared resources throughout the state with no intervention required by the system administrator. This can reduce the impact voice circuit outages will have on individual agencies. In the event a network outage to a single site occurs all agencies will need to maintain at least two local analog lines. These lines would be used for local 911 calls and outbound dialing if the WAN connection fails and IP calls cannot complete across the IP network.

AZNet II – Shared PSTN Resources Cost Savings With shared resources all agencies within a single calling area can share the cost of a single or multiple PRI circuits while reducing the cost of dedicated circuits for each agency Instate long distance charges are reduced for all agencies by routing calls to shared resources if the call is local to the calling area the resource is located in. Agencies requesting DID (Direct Inward Dialing) numbers, currently unavailable to them, can now share in the benefit of having DID’s for a minimum cost to the state.

AZNet II – Shared PSTN Resources Current Shared Resource Locations Tucson (currently a shared infrastructure) Phoenix (currently a shared infrastructure) Flagstaff (currently a shared infrastructure) Winslow (currently a shared infrastructure)

AZNet II – Shared PSTN Resources New Proposed Shared Resource Locations The proposed shared resource locations begin with the following sites: Kingman Sierra Vista Holbrook Cottonwood Payson Glendale Scottsdale Globe Casa Grande Safford Yuma Prescott/Prescott Valley

AZNet II – Shared PSTN Resources Number of Offices per Shared Location The following lists the quantity of state offices that will benefit from each of the proposed shared infrastructure locations: Kingman 16 offices will benefit from shared resources for inbound calling and DID availability All state agencies will benefit on instate calling to this area. Sierra Vista 23 offices will benefit from shared resources for inbound calling and DID availability All state agencies will benefit on instate calling to this area. Holbrook 8 offices will benefit from shared resources for inbound calling and DID availability All state agencies will benefit on instate calling to this area. Cottonwood 6 offices will benefit from shared resources for inbound calling and DID availability All state agencies will benefit on instate calling to this area.

AZNet II – Shared PSTN Resources Number of Offices per Shared Location Cont’d Payson 4 offices will benefit from shared resources for inbound calling and DID availability All state agencies will benefit on instate calling to this area. Glendale 27 offices will benefit from shared resources for inbound calling and DID availability All state agencies will benefit on instate calling to this area. Scottsdale 44 offices will benefit from shared resources for inbound calling and DID availability All state agencies will benefit on instate calling to this area. Globe 10 offices will benefit from shared resources for inbound calling and DID availability All state agencies will benefit on instate calling to this area. Casa Grande 14 offices will benefit from shared resources for inbound calling and DID availability All state agencies will benefit on instate calling to this area.

AZNet II – Shared PSTN Resources Number of State Offices per Shared Location Cont’d Safford 11 offices will benefit from shared resources for inbound calling and DID availability All state agencies will benefit on instate calling to this area Yuma 24 offices will benefit from shared resources for inbound calling and DID availability All state agencies will benefit on instate calling to this area. Prescott/Prescott Valley 25 offices will benefit from shared resources for inbound calling and DID availability All state agencies will benefit on instate calling to this area. Tucson (currently a shared infrastructure) 93 offices will benefit from shared resources for inbound calling and DID availability All state agencies will benefit on instate calling to this area. Phoenix (currently a shared infrastructure) 275 offices will benefit from shared resources for inbound calling and DID availability All state agencies will benefit on instate calling to this area.

AZNet II – Shared PSTN Resources Number of Offices per Location Cont’d Flagstaff (currently a shared infrastructure) 37 offices will benefit from shared resources for inbound calling and DID availability All state agencies will benefit on instate calling to this area. Winslow (currently a shared infrastructure) 5 offices will benefit from shared resources for inbound calling and DID availability All state agencies will benefit on instate calling to this area.

AZNet II – Shared PSTN Resources Agencies that will Benefit All agencies will benefit from the shared infrastructure for outbound dialing across the state of Arizona. The following lists the agencies that will benefit the most from this shared infrastructure proposal as it relates to inbound dialing and DID support. DE – DEPT OF ECONOMIC SECURITY 133 sites around the state will benefit from the shared resources in this proposal DT – DEPARTMENT OF TRANSPORTATION 114 sites around the state will benefit from the shared resources in this proposal PS – DEPARTMENT OF PUBLIC SAFETY 40 sites around the state will benefit from the shared resources in this proposal GF – DEPARTMENT OF GAME AND FISH 11 sites around the state will benefit from the shared resources in this proposal CD – EARLY CHILDHOOD DEVELOPMENT HEALTH BOARD 13 sites around the state will benefit from the shared resources in this proposal HC – AHCCCS 7 sites around the state will benefit from the shared resources in this proposal

CLOSING REMARKS

22 AZNet II Steering Committee | 2014 OPERATIONS UPDATE AZNet II Arizona Network

Ticket Activity / 12-Month Summary AZNet II Steering Committee | RESOLVED TICKETS CREATED TICKETS Total Tickets Closed: 31193/ Average Closed Per Month: 2399 CANCELLED TICKETS

Ticket Activity / Sev 1 & Sev 2 Tickets AZNet II Steering Committee |

Task Activity / Created & Closed Monthly AZNet II Steering Committee |

Task Activity / Created Weekly by Type AZNet II Steering Committee |

Task Activity / Closed Weekly by Type AZNet II Steering Committee |

28 Network Change Control (NCC) / Monthly by Type AZNet II Steering Committee | 2014 NCC Completion StatusCORE SITE CORE SITE SITE Security Network/ Voice Network Voice CORE