DC-Net Goals

1
(No Transcript)
2
DC-NET Goals

• Implement a citywide broadband fiber-optic
  private voice/data network for the District
  Government.
• Satisfy education and public safety
  communications requirements.
• Interconnect over 300 District govt. offices,
  data centers, PD, FD, schools, libraries and
  partners (e.g. WASA, UDC and Convention Center).

3

• The fiber network serves as the foundation for
  all major technologies going forward.

4
DC-NET Project Approach

• Deliver data services first, starting at center
  of city and working out toward outlying areas.
• Two data centers already interconnected (DWDM).
• DC-NET data and voice services will be available
  to about 80 of the DC government by the end of
  2003.

5
DC-NET Design

• 9 Major Backbone loops 30 Secondary Loops
• Acquired through IRUs and cable franchise
  agreements
• Approximately 30 secondary fiber distribution
  loops
• 2 NOCs manned 24x7
• Full suite of network management applications and
  GUI-based provisioning
• High reliability 99.98 availability architecture
  NEBS 3 carrier grade battery backup
• No single points of failure at Critical Buildings
  
• Secure, alarmed equipment cabinets with remote
  monitoring
• OC-48 backbone. Upgradeable to OC-192 and DWDM.

6
Simplified System Block Diagram
7
DC Net Design

• DC-NET uses Multi-Service SONET provisioning
• GUI based provisioning
• Battery backup to operate through a loss of
  commercial power
• Meet all the requirements including the transport
  of E911 traffic
• Scaleable to meet the Districts needs throughout
  the life of the project.

8
Requirements and Services

• Support Existing Protocols
• Ethernet (TCP/IP)
• Voice
• TDM
• Traffic lights/telemetry
• Video Conferencing (point-to-point and
  interactive)
• Webcasting (point-to-multipoint)
• Storage Area Networks (SANs)
• ATM

9
Requirements and Services

• Network is managed from two redundant NOCs
• Network management applications include
• HP Openview/OVO with agents on all servers
• Remedy Help Desk (also District wide help desk)
• Remedy Inventory
• Remedy Change Management
• Micromuse Netcool to monitor security events
• Infovista for Performance Management
• Cisco Works for WAN equipment
• Hummingbird for X-Windows

10
Requirements and Services

• No single point of failure on the backbone or
  tributary rings
• Key locations have diverse entry when possible
• Single entry conduits are encased in concrete 3
  or deeper in the ground
• Backbone rings have 24 strands of fiber
• Tributary rings have 18 strands of fiber
• Scalable
• Support year 5 demands at initial deployment
• Easily upgradeable to year 10 demands
• Scaleable to year 15 demands without a major
  equipment (forklift) upgrade

11
DC-NET Business Issues

• Business Strategy
• We are not going into the phone business.
• Will contract for all operations services that
  can feasibly be contracted.
• Proposed entrepreneurial entity to own/operate
  DC-NET will increase ROI.
• E.g. Sell services to WMATA and Convention
  Center.
• This fall, will propose legislation for this
  purpose.

• Investment/ROI
• Project cost 93 million. 66 million
  available.
• 27 million shortfall will be paid out of
  savings.
• Savings ROI 10 million per annum when built
  out (2005).
• Savings start when we begin cut-over, fall
  2003.
• First few high-population buildings will produce
  most savings.

12
DC-NET Conduit Routes

• Black box Fire zone.
• Inside fire zone all fiber in underground
  conduit.
• Outside fire zone fiber may be in conduit or
  aerial.
• 9.5 of DC-NET is planned to be in Verizon
  conduit (or duct).

13
DC-NET Conduit Law

• Operative DC Code provision
• 34-1911.05 provided, that in all conduits,
  space shall be furnished to the District as may
  be necessary for its fire alarm or police patrol
  wires or cables, free of charge andthe number
  of ductsshall not be more than 3.

• Replacing old lead-shielded cable with new
  fiber-optic cable.
• Work to upgrade cable from old to new continues