New Search
I <br />' 1.6 Recommended Steps for Network Expansion <br />' The communications deployment plan in this report focuses primarily on the selection of <br />physical media (copper vs. fiber) and communications technology (Ethernet vs. analog) for <br />communication to transportation network devices. The plan also identifies a phased approach <br />' for installing the physical infrastructure and addresses the potential relocation of the 858 Pearl <br />Street facilities. During implementation of the communications infrastructure the City should <br />consider these recommendations: <br />1. Partner with ISD for configuration and maintenance of the Ethernet network to <br />transportation devices. Typically, Public Works Department technicians maintain <br />copper twisted pair networks, but lack the expertise to maintain fiber optic networks and <br />Ethernet components. Information services network technicians at the City already have <br />the networking skills to configure switches, firewalis, assign IP addresses, monitor the <br />network infrastructure, and plan new deployments. The Public Works Department should <br />use this resource to assist with the installation, configuration and ongoing maintenance <br />of a transportation Ethernet network when feasible. <br />2. Plan an IP address scheme for the transportation network. Public Works should plan <br />an IP address scheme for field devices with ISD involvement. IP addresses for traffic <br />components will likely be routed on the City network. This requires Public Works to <br />coordinate IP addresses with other City departments and devices. <br />3. Install a minimum of 96 fibers for trunk line communication routes. Based on <br />Figure 14, this plan anticipates a maximum of 20 fibers will be used for the transportation <br />network on a single route. To create a robust and self healing communications network, <br />this plan recommends alternate physical paths for communications cable. As alternate <br />paths are developed, additional fibers will be required to support self healing capabilities. <br />The fiber optic cable also becomes an asset that many other public agency departments <br />may benefit from. <br />4. Develop policies for fiber usage. Consider reserving individual buffer tubes within a <br />fiber optic cable for certain agency departments or specific uses. The Public Works <br />department should develop a policy for buffer tube assignments within their cables. <br />5. Develop and update a detailed network plan with each communications <br />construction project. A detailed network plan is dynamic and changes as new fiber <br />optic cable and components are installed. The detailed network plan accounts for the <br />existing infrastructure and includes planned near term expansions. It provides a road <br />map that can be used to plan fiber quantity and track network port requirements. The <br />network plan should include existing and planned fibers, network switch bandwidth <br />capability, number of network ports on switches, and existing and planned physical <br />paths for the network connections. <br />6. Develop and maintain detailed maintenance and configuration documents. The <br />City maintains Excel databases and AutoCAD drawings to track copper twisted pair <br />terminations and assignments today. Similar documentation will be required to track <br />configuration of the fiber optic cable and electronics (e.g., splice and termination <br />locations, IP addresses, warranties, user's manuals, configuration requirements). The <br />City should consider developing these maintenance and configuration documents as <br />part of each construction project. <br />DKS Associates Eugene Master Traffic Communications Plan March 2008 <br />' <br />Page 6 <br />