1. WASHINGTON DC: INTEGRATED NETWORK TECHNOLOGY OVERVIEW Maryland Technology Council June 2006 Chris Peabody Deputy CTO - Office of the Chief Technology Officer Government of the District of Columbia chris.peabody@dc.gov

2. 2 Washington DC  Unique  City / County / State Governance (all in one)  Executive Office of the Mayor  66 Agencies  Elected City Council  Independent Agencies  Public Schools  CFO  Water and Sewer Authority (WASA)  Major Federal Oversight and funding  Primary business is government  No Smokestack industry allowed  DHS is having a major impact on city  Business is currently very good

3. 3 Washington DC  Approximately 400,000 Residents  DC.GOV presence in over 600 locations within the city.  Major Federal presence  Hub of a major urban metropolis  Dulles – Baltimore and beyond  Major Schools  GU / GWU / American / Catholic / Howard / Trinity

4. 4 OCTO www.octo.dc.gov  Office of the Chief Technology Officer  Formed in 1998 with 4 employees  Over 600 employees & contractors today  Centralized technology support  All agencies under the Mayor  Not Independent Agencies  Agencies managed own technology before OCTO  “Worst to First”  District Website DC.Gov named Best of the Web  The portal was named Best of the Web by the Center for Digital Government,  Major ERP initiatives complete or underway  Amazing network and public safety initiatives

5. 5 OCTO: www.octo.dc.gov  Undergoing major transformation right now  Moving from entrepreneurs to production programs  Major emphasis on transforming contractors to FTE’s  Network has grown in “smokestacks”  Major Peabody task is integration of network technology smokestacks  Separate networks – separate programs  Separate people, separate budgets, separate helpdesks  Politics - real politics – plays a major role in everything  Sound familiar?

6. 6 OCTO HAS BEEN VERY BUSY “In order to great things in the world of technology you need to have 2 very critical things: Great people and lots of money. OCTO has been blessed with both over the last few years.” Suzanne PeckCTO - OCTO

7. 7 DC Gov’t Networks In-Source Vs Out-Source  Most network services were outsourced  CENTREX telephony service  MAN data circuits all from ILEC  Public Safety networks from traditional vendors  Contractors versus FTE’s  In process of complete reversal  Citywide/city owned and managed communications networks.  Key: District owned and managed  Shift from Contractors to FTE’s

8. Ultimate In-Source Solution Build it yourself!

9. 9 DC-NET: Strategic Drivers 1. Need for a high-speed citywide data communications network because of the growing demand for advanced data services, data transport services, and wireless service. 2. Historic problems of service installation delays, problems with access to the city’s data, errors in the telephone bills, and overbilling by telecommunications carriers

10. 10 DC-NET: Goals  Build and maintain a comprehensive technology network that meets the needs of the ENTIRE District Government  All voice services  All Intranet WAN connectivity  Enhance Public Safety applications  Working group determined that the network must have “at least” these attributes:  Scalable (especially future growth; both size and services)  Highly available, fault-tolerant  Minimize total cost of ownership, particularly operational costs  Secure (traffic isolation and privacy)  Accommodate the wide variety of network needs and data flow patterns present in the District

11. 11 DC-Net: Architectural Issues In The District  Many agencies require encryption  Extranet connections need to filter/firewall their traffic before it reaches other agencies  Redundancy  Different preferences, requirements, budgets, etc.  Some agencies are 100% stand-alone, others use centralized resources such as e-mail Bottom Line: The Districts network needs and applications differ by agency, by building and by budget.

12. 12 DC-NET: Options Overview  Considered a variety of options - variety of approaches:  Different types of equipment considered  Different layers of the OSI model considered for service delivery  “Legacy,” “mature,” “state-of-the-art,” and “bleeding edge” technologies were all considered  Impact of teams ability to effectively manage/administer  Both point-to-point and shared (cloud) models  Consistent factors  DC Net should be the transport mechanism not desktop  All traffic should use SONET as the “convergence layer”  Ethernet over SONET vs. a separate Gigabit Ethernet network  Ethernet aggregation at the edge of the network for cost savings, while maintaining necessary resiliency levels.

13. 13 DC-NET Fast Facts  DC Loves Teddy Roosevelt  1903 Statute required “the phone company” to provide conduit space for public safety use. Very powerful discovery!  $93 mil multiyear project  Local Capital dollars  Some Federal dollars  Goal is to be self sustaining by FY08  Approximately 86 employees working on the project  Currently in “Construction and Production”  Final production team should be substantially smaller  DC-NET currently provides Voice and MAN transport  Does not manage LAN/WAN or Internet  Both Groups under single Deputy CTO (Peabody)

14. 14 DC-NET: Independent Agency?  Plan has been to “spin out” DC-NET into an Independent Agency  This is on again, off again.  Requires full support from EOM and Council  New Mayor elected next year  Requires “full time “driver””  Independent agency not “hamstrung” by same “inane Gov’t rules and regulations”  Can become an Erate eligible Company  Can provide services to Federal Agencies  Can provide services to non-Gov’t entities

15. 15 DC-NET: Fiber  SONET Fiber planned to all Gov’t locations  400 – 600 Gov’t sites across the city  Currently at 165 buildings and planned for all sites “which make sense”  Some fiber deployed direct in Verizon Conduits  Needless to say, Verizon not been happy about this  Other fiber obtained via CATV Franchise Agreements  Comcast  23 Additional miles just obtained in “fire zone”  Great to have, but hard to integrate into network  RCN (formerly Starpower)  Some minor/original fiber purchased on IRU’s (Level3)

16. 16 DC-NET: Core and Edge electronics  Cisco 15454's as the core routing hardware  Other than one major software issue, very stable  Chosen for it’s carrier class abilities  Chosen because “they’re Cisco” over other vendors  Chosen for it’s ability to support SONET  SONET chosen for it’s proven redundancy (circa 2003)  Great for T1 Handoffs  Lots of Government Applications for T1’s  Motorola Radio circuits to Towers (42 of them across the city)  Voice circuits for ancillary products like ACD  Cisco 3750’s currently used at edge  Edge is almost always at the BDF

17. 17 DC-NET: Replacing the Legacy Services  Rapidly replacing legacy MAN circuits from Verizon  District has hundreds of Point – Point circuits  Major Frame Relay networks installed today  Multiple 45 Mbps at host sites  Independent agencies like DCPS manage their own network  DC-NET replacing these circuits as fast as possible  Layer 3 MPLS VPN’s  Currently offer 2Mbps – 500Mbps  T1’s also provided  Pricing of DC-NET services currently mirrors Verizon fees to ensure no impact to agency budget.  DC-NET “costs” still hard to determine at this phase

18. 18 DC-NET: Voice Platform  Avaya s8700 is core voice platform.  Redundant servers in two host centers  Connected via DC-NET SONET fiber  MCI (now Verizon) provides PRI + DID numbers  Service provided from 2 CO’s  28,000+ phones when complete.  28,000+ phones when complete.  13,000 have been ported  20,000 ISDN/CENTREX remain  10 – 15% unused inventory discovered during cutovers  Avaya Modular Messaging voicemail  Still 10,000 Verizon Optimail boxes not migrated

19. 19 DC-NET: Terminal Plans  Voice terminal plans mirror most large enterprise plans:  Get out of the “Henry Ford Phone business”  Any set you want as long as it’s my black phone…  SIP (of course)  Single number on multiple terminals (SIP or Standard)  EC500 has been available for years, not largely deployed  First responder’s anxious for single number  Hardphone  Softclient on “rugged - ized” laptop in cruiser  Cellphone  Utilize private 700Mhz spectrum to deploy softclients for first responders and other Gov teams.

20. 20 DC-NET: Terminals Bacground  Phone terminals have been problematic  Legacy ISDN sets retained because of $$  Most purchased within last 5 years  S8700 platform supports these older sets  New sites are deploying “newer” digital sets  VoIP terminals were not “deployable” in phase I  DC LAN/WAN is separate network  DC-NET voice traffic is in single Voice VPN  VoIP could only be deployed today at “green field” sites Bottom line – we’ve got a racehorse fiber network with world class routing and switching hardware and last generation terminals.

21. 21 2007 Terminal Plans  Major plans to replace the ISDN terminals  We’re backing into VoIP strategy, because of the terminals.  We can support ISDN / Analog / Digital /VoIP  Major effort underway to upgrade the LAN’s to Support VoIP  Power – Power – Power!  Working cohesively on a strategy  Hiring new people with “end – end” network talent  Hiring Sr. Architect + Sr. Project Director  Focus on QOS enablement  Have to make $5mil+ decisions in 3 months!  Concerned about customer care side:

22. 22 Network World: 06/21/06 No waste in Kimberly-Clark VoIP plans For a company that sells billions of disposable consumer products each year, …..conservationist's approach to its VoIP and IP telephony plans. The VoIP plan at Kimberly-Clark is to consolidate voice traffic for more than 200 sites into three data centers while retrofitting existing Avaya PBXs with gear that will turn the devices into digital/VoIP gateways. The revamped PBXs will let the company keep the tens of thousands of digital handsets now in use while centralizing its call processing and messaging applications. That move could save close to $10 million in new IP phone costs if Kimberly-Clark upgrades its sites to VoIP while saving half its Avaya digital phone installed base. "IP handsets will be more of an exception, rather than the rule" in the VoIP road map, says Mike Post, senior manager of IT communication services for the Irving, Texas, company. "For our business and how it operates, we didn't see a great amount of value in deploying IP phones widely... so we're going to try and keep our digital sets wherever we can."

23. 23 DC-NET: NOC  NOC is carrier class / world class  24 x 7 x 365  Underground  Hub of all.gov technology performance mgmt  Application management not just monitoring & performance mgmt  DC-NET opted to outsource to legacy OCTO NOC

24. 24 DCNET: Beyond Voice and Data

25. DC-NET/ DC.Gov E911 Network Update June 2006

26. 26 DC.Gov: Direct Connect Overview  90% complete with modernization of District’s E911 Network  8 years ago, DC’s Verizon-managed 9-1-1 system was the worst in the country.  Verizon’s existing technology was unreliable, slow, expensive, contained inaccurate data, and had two primary weaknesses:  ALI  Trunking (pathways)

27. 27 DC has built fully a redundant E911 network infrastructure that enables Carriers to “Direct Connect” to the PSAP  All wireless (cellular) carriers have been on the District’s “selective router” system for 4 years.  50+% of the traffic to PSAP is cellular.  Wireline carriers are now being migrated  System will accommodate VoIP carriers  0 calls have been blocked or dropped in 4 years  Call delivery and processing has dramatically improved  National Emergency Number Association (NENA) has reviewed the District 911 network and believes the District’s network is how NGN-E911 services should be engineered: Redundant, secure, and on a robust network.

28. 28 Unreliable vs Reliable Trunking DC-NET Fiber

29. 29 WASHINGTON DC E911 CURRENT ARCHITECTURE VERIZON SINGLE POINTS OF FAILURE FULLY REDUNDANT DISTRICT NETWORK

30. 30 DC-NET: Citywide Motorola Radio System  42 Towers across the District  Supports entire First Responder Community  T1 Based Connectivity  Cutover in a single weekend from Verizon  Never Failed  Adding 28 new circuits due to UCC building

31. 31 DC-NET: “Digital Inclusion Wi-Fi”  Mayor gets calls and Emails every day  “Why does DC not have a network like “Phili”?  Currently exploring “win – win” options  Looking for partners  Not sure where the $$ will come from  DC-NET will provide citywide backbone for network service partner

32. 32 DC-NET: WARN  The Wireless Accelerated Responder Network (WARN) is the nation’s first city-wide broadband wireless public safety network. This pilot network was unveiled in September 04 and was first operationally used in January, 2005 for the Inauguration followed by the State of the Union.  The Wireless Accelerated Responder Network (WARN) is the nation’s first city-wide broadband wireless public safety network. This pilot network was unveiled in September 04 and was first operationally used in January, 2005 for the Inauguration followed by the State of the Union.

33. 33 DC-NET: WARN Network Attributes  WARN is supported, managed and operated by the OCTO Wireless Programs Office (WPO).  WARN is supported, managed and operated by the OCTO Wireless Programs Office (WPO).  WARN is a pilot network run on an experimental license in the 700 MHz band provided by the FCC.  WARN consists of 12 radio sites and 200 network devices (i.e. PC cards) that facilitate wireless interconnection of Local and Federal public safety mobile devices throughout the District of Columbia. In addition, users of the network can access applications that, heretofore, were only accessible from the desktop computers.

34. 34 DC-NET: WARN Network Attributes  Covers 95% of the District  Uplink rate -- 900 kbps (peak)/300 kbps (average)  Downlink rate -- 3 Mbps (peak)/900 kbps (average)  Uses Flash/OFRM  Low latency (30-50ms)  Full mobility (communications sustained while device mobile throughout the city)  Dedicated Public Safety network – no contention with cellular or commercial users.  All IP network; features include full quality of service (QOS) capabilities, and static IP addresses  Single phone # trial being engineered (hardphone/Softphone/Cell)

35. 35 Why we build our own!!! (no dropped calls, packets or radio transmissions!)

36. 36 Thanks - Questions