Maricopa Association of Governments

1
Regional Community Network

• Maricopa Association of Governments
• Telecommunications
• Advisory Group
• PROJECT UPDATE
• November 17, 2005
• Presented By
• David S. Haines, P.E.

2
Presentation Overview

• Overall Project Status
• Phase 1 Project Funding
• Future RCN Equipment Configuration
• JUICE Deployment Efforts
• Operations Maintenance for AZTech Network
• Managing RCN Growth with IT Departments
• Questions / Discussion

3
Overall RCN Network Architecture
Phase 1 (blue) Phase 2 (red) Future (green)
4
Project Status

• AZTech Integrated Emergency and Transportation
  Communications Network Grant funds
• Phase 1 Deployment DCR (West Valley and Core)
  Completed Nov. 2004
• Phase 2 Deployment DCR (East Valley)
  Circulated for comments in June 2005
• To be finalized within the month
• Phase 1 Deployment PSE Packages
  In progress, scheduled
  completion in Dec. 2005

5
Project Funding Highlights

• MAG has 1.6 million reallocated from the
  Regional Video Conferencing System.
• Funding for Video Conferencing upgrades to
  support IP Ethernet is included in RCN Phase 1.
• A portion of Phase 1 can be constructed under the
  available 1.6M, and the region will need to
  pursue additional funding for the remaining
  portions.

6
Phase 1A The 1.6M Package

• Video Conferencing IP-Ethernet Upgrade
• Core Ring (3 Regional Hubs)
• Regional Hub fiber / building access
• ADOT fiber bottleneck relief (I-17, TOC to I-10)
• Partial West Ring
• Glendale Regional Hub
• Six Metropolitan Hubs
• - ADOT TOC - Glendale TMC - Phx Public
  Transit
• - Phoenix TMC - Peoria TMC - MAG

7
(No Transcript)
8
Phase 1A The 1.6M Package

• Advantages
• Builds the core ring part of west ring
• Provides RCN connectivity to Glendale TMC
  (arena / stadium events, Superbowl, etc.)
• Provides RCN connectivity to Peoria TMC
  (ADOTs alternate TOC location)
• Eliminates ADOT fiber bottleneck point
• Connects Six Metropolitan Hubs
• - ADOT TOC - Glendale TMC - Phx Public
  Transit
• - Phoenix TMC - Peoria TMC - MAG

9
Future RCN Equipment Config.

• RCN Phase 1 2 will provide the fiber
  connectivity and AZTech network switches needed
  for transportation agencies.
• It is anticipated that IT departments will
  install CWDM / SONET equipment in the future,
  while maintaining AZTech network connectivity at
  design bandwidth.

10
AZTech Network Configuration

• AZTech Ethernet Network (Phase 1 2)

2 fibers and 2 spares
2 fibers and 2 spares
AZTech Regional Hub
AZTech Regional Hub
AZTech Regional Hub
2 fibers and 2 spares
11
Future RCN Equipment Config.

• AZTech Ethernet Network with IT department CWDM
  / SONET

SONET OC-48
AZTech Regional Hub
CWDM
CWDM
CWDM
CWDM
AZTech Regional Hub
AZTech Regional Hub
CWDM
CWDM
SONET OC-48
SONET OC-48
12
JUICE Deployment

• JUICE Joint User Interoperability
  Communications Enterprise
• Project Partners
• ADOT
• Arizona DPS
• City of Phoenix Street Transportation Dept.
• City of Phoenix Information Technology Dept.
• Maricopa County Telecommunication Dept.

13
JUICE Deployment

• The original JUICE Proof of Concept

14
JUICE Deployment

• Installs 3 SONET OC-48 Regional Hub nodes
• ADOT Traffic Operations Center
• DPS Encanto Headquarters
• City of Phoenix Calvin Goode Building (IT Hub)
• Uses existing fiber from DPS to ADOT to Phoenix
• Will use RCN Core Ring path in future

15
JUICE Deployment

• SONET OC-48 Regional Hub networks
• - AZTech WAN - DPS CAD LAN Extensions
• - ACTIC Video WAN - City of Phoenix WAN
• - ADOT WAN - Maricopa County WAN
• - DPS WAN
• DPS currently has primary responsibility for
  JUICE network configuration changes.
• Equipment procurement / installation is underway.
• Discussions have started for third party
  OM support.

16
Future RCN Configuration

• AZTech Ethernet Network with IT department CWDM
  / SONET

SONET OC-48
AZTech Regional Hub
CWDM
CWDM
CWDM
CWDM
AZTech Regional Hub
AZTech Regional Hub
CWDM
CWDM
SONET OC-48
SONET OC-48
17
OM for AZTech Network

• AZTech Ethernet Network (Phase 1 2)

2 fibers and 2 spares
2 fibers and 2 spares
AZTech Regional Hub
AZTech Regional Hub
AZTech Regional Hub
2 fibers and 2 spares
18
OM for AZTech Network

• MCDOT will manage project to develop OM plan for
  AZTech network under current grant funding.
• It is currently envisioned that each agency will
  be responsible for maintaining the RCN fiber in
  their jurisdiction.
• Each jurisdiction will be responsible for
  providing and maintaining their own firewall.

19
OM for AZTech Network

• OM plan for AZTech network components will
  cover the development of a JPA/MOU for RCN Phase
  1 2.
• AZTech partners will need to decide if ADOT will
  continue to be the lead agency for AZTech
  network configurations (i.e., IP address
  assignments, equipment maintenance)

20
Managing RCN Future Growth

• AZTech Ethernet Network with IT department CWDM
  / SONET

SONET OC-48
AZTech Regional Hub
CWDM
CWDM
CWDM
CWDM
AZTech Regional Hub
AZTech Regional Hub
CWDM
CWDM
SONET OC-48
SONET OC-48
21
Managing RCN Future Growth

• What multi-agency forum will take the lead for
  the following?
• Coordinating connectivity to other facilities
• Deciding how the bandwidth will be utilized
• Selecting an appropriate SLA
• Policy decisions on how future upgrades will be
  funded
• Policy decisions on how the cost of OM will be
  divided up among participating agencies and/or
  their respective departments

22
Managing RCN Future Growth

• JPA / MOU Needed for future RCN
• OM Plan Needed for future RCN
• Maintaining fiber links
• Maintaining network equipment
• Control of access
• Other issues

23
Project Contacts

• Debra Barker, P.E., ITS Project Manager
• ADOT Transportation Technology Group
• [phone]
• dbarker_at_azdot.gov
• David Haines, P.E., Project Manager
• Kimley-Horn and Associates, Inc.
• [phone]
• david.haines_at_kimley-horn.com