1

AZNet II Steering CommitteeJ u n e 1 6 , 2 0 1 4

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

1019953

1119189

21219142

Sites Completed# Seats Affected

543292

1087979

16211271

Sites Completed 5 10 15

Total Sites Refreshed To Date: 162Total Seats Affected: 30413

2013 * 2014 To DateN E T W O R K R E F R E S H

V O I C E R E F R E S H

C A L L C E N T E R

* 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 SolarwindsTo Request Access:

» Open an RFI ticket via AZNet Support DeskMaximum 5 accounts per Agency

» Include name, email and phone # for each account requestedAZNet 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 ResourcesShared 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 ResourcesShared 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 ResourcesShared 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 ResourcesCost 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 ResourcesCurrent 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 ResourcesNew 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 ResourcesNumber 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 ResourcesNumber 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 ResourcesNumber 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 ResourcesNumber 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 ResourcesAgencies 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 UPDATEAZNet II Arizona Network

Apr-13

May-13

Jun-13Jul-1

3

Aug-13

Sep-13

Oct-13

Nov-13

Dec-13

Jan-14

Feb-14

Mar-1

4

Apr-14

May-14

0

500

1000

1500

2000

2500

3000Ticket Activity / 12-Month Summary

AZNet II Steering Committee | 201423

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 | 201424

Mar Apr May0

5

10

15

20

25

30

35

40

45

Software

Planned Maintenance

Customer

Other

No Trouble Found

Firewall/VPN

Hardware

Carrier

Task Activity / Created & Closed Monthly

AZNet II Steering Committee | 201425

Mar-14 Apr-14 May-140

2000

4000

6000

8000

10000

12000

14000

16000

18000

20000

22000

24000

Active

Cancelled

Resolved/Closed

Created

Task Activity / Created Weekly by Type

AZNet II Steering Committee | 201426

22-Mar 29-Mar 26-Apr 31-May0

200

400

600

800

1000

1200

1400

1600

Outage

RFI

Project

MAC

Repair

Task Activity / Closed Weekly by Type

AZNet II Steering Committee | 201427

22-Mar 29-Mar 26-Apr 31-May0

200

400

600

800

1000

1200

1400

OutageRFIProjectMACRepair

28

Network Change Control (NCC) / Monthly by Type

AZNet II Steering Committee | 2014

NCC Completion Status

CORE

SITE

CORE

SITE

SITE

SITE

Security

Network/Voice

Network

VoiceCORE

CORE

Aug-13 Sep-13 Oct-13 Nov-13 Dec-13 Jan-14 Feb-14 Mar-14 Apr-14 May-14

0

10

20

30

40

50

60

70

Successful 95%

Unsuccesful 1%Cancelled 4%