Bill Block

From: Kurt Miller [KurtMiller@npumail.com]Sent: Friday, July 25, 2008 2:38 PMTo: Bill BlockSubject: FW: Addendum #2 to NPU's Request for Proposal for I. Net. Design and Implementation

Page 1 of 1

7/28/2008

Bill, See changes below.

From: Jeremiah Kvasnik Sent: Friday, July 25, 2008 11:10 AM To: Jeremiah Kvasnik; 'daleb@digitalbackoffice.com'; 'ronr@digitalbackoffice.com'; 'brusso@automatech.com'; 'Jack Nedelman'; 'jgolden@cbetech.com'; 'fcollett@cbetech.com'; 'ghedge@southportcom.com'; 'mzaloumis@foundrynet.com'; 'cschultz@foundrynet.com'; 'nmanhertz@sysntech.com'; 'sharris@sysntech.com'; 'jack.pantina@CompuCom.com'; 'mconn@CompuCom.com' Cc: Susan Fowler; 'Eric Wirth'; 'David Randolph'; Kurt Miller Subject: RE: Addendum #2 to NPU's Request for Proposal for I. Net. Design and Implementation Dear All, Due to the amount of documentation that NPU has requesting, we are pushing back the proposal submission date from July 29th at 4:00 to August 1st at 4:00. We will not push the submission date back any further. There will not be any changes to the list of vendors submitted in Addendum #1. Documentation of any design changes in critical. Jeremiah Kvasnik Norwich Public Utilities

NORWICH PUBLIC UTILITIES NORWICH, CONNECTICUT

NPU 002P

REQUEST FOR PROPOSAL FOR CONSULTANT SERVICES

FOR INSTITUTIONAL NETWORK DESIGN AND IMPLEMENTATION

Norwich Public Utilities (NPU) is constructing a fiber optic Institutional Network (I-Net) for the purpose of enhancing the reliability of existing communications services and scaling network capacity to meet expanding technology requirements for NPU, the City of Norwich, and Norwich Public School (NPS) facilities. NPU intends to select a qualified contractor to provide network design services, integration services and equipment in support of the network implementation. Detailed requirements for submittal of proposals are available at the office of the Norwich Public Utilities, 16 South Golden Street, Norwich, Connecticut, between the hours of 8:30 AM and 4:00 PM, Monday though Friday. There will be a Pre-Proposal Conference on July 15 at 9:00 AM at the NPU Administration Building. Responses to all questions will be presented in writing in a formal RFP Addendum. Inquires relating to this request for proposal should be directed to Jeremiah Kvasnik at (860) 823-4154. Six (6) sets of the Proposal package, clearly marked “REQUEST FOR ROPOSAL FOR CONSULTANT SERVICES FOR INSTITUTIONAL NETWORK DESIGN AND IMPLEMENTATION” will be accepted no later than July 29, 2008, 4:00 PM, local time in the Office of the Norwich Public Utilities, 16 South Golden St., Norwich, CT 06360; Attention: Jeremiah Kvasnik, Project Manager. NO PROPOSALS WILL BE ACCEPTED AFTER THE 4:00 P.M. DEADLINE. The work shall be awarded base on weighted criteria documented in the Statement of Work. NPU reserves the right to reject any or all proposals or parts thereof based on our assessment of the criteria; to waive any formality in same, or accept any proposal deemed to be in the best interest of the City.

Norwich Public Utilities Institutional Network Implementation

Statement of Work

June 19, 2008

Prepared by Columbia Telecommunications Corporation

10613 Concord Street Kensington, MD 20895

301-933-1488 www.ctcnet.us

Table of Contents I. Introduction............................................................................................................................3 II. Existing Networks ..................................................................................................................4

2.1. NPU..................................................................................................................................4 2.2. NPS ..................................................................................................................................4 2.3. City of Norwich ...............................................................................................................4 2.4. NPU Fiber Optic Network ...............................................................................................5

2.4.1. Fiber Loop A Network Architecture...........................................................................................................5 2.4.2. Fiber Loop B Network Architecture...........................................................................................................7

III. Proposal Requirements .........................................................................................................9 3.1. Schedule...........................................................................................................................9 3.2. Proposal Evaluation Criteria ............................................................................................9

3.2.1. Proposal Document Requirements ...........................................................................................................10 3.2.2. Technical Proposal ...................................................................................................................................10 3.2.3. Timeline....................................................................................................................................................10 3.2.4. Price Quotation.........................................................................................................................................10 3.2.5. Contractor Qualifications .........................................................................................................................11

IV. Statement of Work...............................................................................................................12 4.1. General Scope of Work..................................................................................................12 4.2. Network Upgrade Architecture......................................................................................13

4.2.1. System-Level Network Design.................................................................................................................13 4.2.2. Core Equipment Configuration.................................................................................................................15 4.2.3. Typical I-Net Site Configuration ..............................................................................................................16 4.2.4. SCADA Equipment Configuration...........................................................................................................17

4.3. Equipment Specifications ..............................................................................................18 4.3.1. General Ethernet Switch Specifications ...................................................................................................18 4.3.2. Core Ethernet Switch................................................................................................................................19 4.3.3. Typical I-Net Site Backbone Switch ........................................................................................................20 4.3.4. Network Management System..................................................................................................................20

4.4. Integration Requirements...............................................................................................20 4.4.1. General Implementation Responsibilities .................................................................................................20 4.4.2. Cutover Plan .............................................................................................................................................22 4.4.3. Work Hours ..............................................................................................................................................23 4.4.4. Testing ......................................................................................................................................................23

4.5. Equipment Maintenance ................................................................................................24

Table of Figures

Figure 1: Loop A Logical Network ................................................................................................ 6 Figure 2: Loop B Top Logical Network ......................................................................................... 7 Figure 3: Loop B Lower Logical Network ..................................................................................... 8 Figure 4: Proposal Submission and Contract Award Schedule ...................................................... 9 Figure 5: System-Level I-Net Architecture .................................................................................. 14 Figure 6: City Core Equipment Configuration ............................................................................. 15 Figure 7: Typical I-Net Site Equipment Configuration ................................................................ 17 Figure 8: SCADA Equipment Configuration ............................................................................... 18

Appendices Appendix A: Institutional Network Site List and Estimated Fiber Losses

DRAFT

3

I. Introduction

Norwich Public Utilities (NPU) is constructing a fiber optic Institutional Network (I-Net) for the purpose of enhancing the reliability of existing communications services and scaling network capacity to meet expanding technology requirements for NPU, the City of Norwich, and Norwich Public School (NPS) facilities within the NPU service area. NPU intends to select a qualified contractor to provide network equipment and integration services in support of the network implementation. The I-Net topology will consist of two interconnected fiber optic backbone rings over which NPU will operate a network to support a variety of data communications for the NPU, the City, and NPS, each of which currently use a variety of leased services to provide data communications between facilities. NPU plans to create a flexible and scalable communications solution based on Gigabit Ethernet, a widely accepted, standards-based technology. The objective of this Request for Proposals (RFP) is to specify the requirements for the implementation of a Gigabit Ethernet fiber optic network. The requirements in this document encompass the work product to be provided by the successful bidder, including technical equipment specifications, network architecture, implementation strategy, and contractor responsibilities.

DRAFT

4

II. Existing Networks

The following sections outline the existing data networks of NPU, NPS, and the City of Norwich. The intent is to provide respondents to this RFP with the background information necessary to generate comprehensive proposals.

2.1. NPU

NPU is the municipally owned utility in Norwich, Connecticut that provides electricity, gas, water, and sewer services. As part of its internal operations, NPU maintains a data communications and supervisory control and data acquisition (SCADA) network. The data communications network serves locations in which the NPU has staff located, including the NPU administration building, customer service center, and the waste water treatment plant. The data network supports a range of enterprise data applications. Currently, voice and video services are not supported universally on the data network, however NPU does have a some surveillance and VoIP in place. The NPU SCADA network supports monitoring and control of over 50 NPU utility locations. The system is connected through leased copper lines or analog phone lines. Much of the existing SCADA system relies on analog and digital I/O connections, although NPU’s planned SCADA upgrade will migrate many of the SCADA devices to Ethernet.

2.2. NPS

NPS is the local school district that provides kindergarten through 8th grade public education in Norwich. NPS operates a data communications network between the School Administration building and the 15 other school sites in Norwich, supported over leased T1 circuits. NPS currently uses Intel Ethernet switches in the LAN, but is considering upgrading the LAN equipment due to the age and the available support of the current equipment. NPS operates a variety of applications over their network, using local servers, where bandwidth does not permit server centralization. NPS applications include email, student management database, accounting system, and other enterprise applications. NPS also operates a video surveillance system that is not currently centralized due to bandwidth limitations.

2.3. City of Norwich

The City of Norwich operates a data communications network for internal City departments. The data network consists primarily of encrypted VPN connections between the City Administration Building and several remote sites over DSL connections. The City’s central data network resources are located at the administration building. The City has LAN equipment from a variety of manufacturers, although the City has deployed HP ProCurve switches at City Hall.

DRAFT

5

2.4. NPU Fiber Optic Network

NPU is constructing new fiber optic infrastructure throughout its service area, which will be located on existing NPU utility poles or placed underground using All Dielectric Self-Support Fiber (ADSS). The new ADSS fiber will be placed in the power neutral location wherever possible. The I-Net design includes 106 sites grouped into four different categories. These categories include 23 City sites, 7 hospital sites, 56 NPU sites, and 16 school sites. The scope of this RFP does not include the hospital sites. The I-Net fiber design consists of two interconnected 144-count fiber optic loops. Loop A covers the eastern half of the city; Loop B covers the western half of the city and is divided into two sections to decrease fiber distances. Each ring contains a Core site; the Core site for Ring A is the NPU Administration Building; for Ring B, it is the Bean Hill Substation. Each non-SCADA NPU site, NPS site, and City site will have access to a dedicated pair of fiber optic strands around the ring in both directions to the Core site. The NPU SCADA sites will be connected together by a single pair of fiber optic strands around the ring to the Core Site.

2.4.1. Fiber Loop A Network Architecture

Fiber Loop A consists of a 144-count fiber ring that serves the eastern side of Norwich. It is interconnected to Fiber Loop B at two redundant points. Fiber Loop A provides direct services to 45 locations with approximately eleven miles of backbone fiber. The NPU office at 16 South Golden serves as the major hub site, at which all fibers from both directions of the loop will terminate. A northern spur to Occum has been provided using 144-count fiber to allow a future loop to be constructed to interconnect back to the hub sites. A southern spur using 144-count fiber provides fiber for future development projects. All other fiber spurs are designed with 48-count fiber for future uses. Figure 1 includes a block diagram illustrating Loop A detailing institutional sites, splice locations and distances between splices. Appendix A contains the site listings and distances between each I-Net site and its corresponding Core site.

DRAFT DRAFT

6

Figure 1: Loop A Logical Network

7

2.4.2. Fiber Loop B Network Architecture

Fiber Loop B consists of a 144-count fiber that serves the western side of Norwich. It is interconnected to Fiber Loop A at two redundant points. Fiber Loop B provides direct service to 54 locations with approximately 22 miles of backbone fiber. The NPU Bean Hill Substation at 20 Connecticut Avenue serves as the major hub site. The B loop has been divided into a top loop with approximately eight miles of fiber and a lower loop with 12 miles of fiber. Twelve fiber optic strands are spliced together in the A and Lower B loops to provide connectivity between hub sites. All fiber spurs are designed with 48-count fiber for future uses. Figures 2 and 3 include block diagrams illustrating Loop B top and lower sections that detail institutional sites, splice locations, and distances between splices.

Figure 2: Loop B Top Logical Network

DRAFT

8

Figure 3: Loop B Lower Logical Network

DRAFT

9

III. Proposal Requirements

Respondents to this RFP shall adhere to the specific proposal documentation requirements and proposal submission logistical requirements detailed in the following sections.

3.1. Schedule

The contract award process will follow a strict schedule (Figure 4).

Figure 4: Proposal Submission and Contract Award Schedule

Event Date RFP Presented June 19, 2008

Pre-Proposal Conference July 15, 2008 9:00 AM EST

RFP Addendum Presented July 18, 2008 Proposal Submission Deadline July 29, 2008

4:00 PM EST Notification of Contract Award Recipient Aug. 8, 2008

A pre-proposal submission conference will be held at the NPU Administration Building at 9:00 AM on July 15th, and will be open to any candidate respondents to the RFP. Respondents unable to attend this meeting are requested to e-mail their intent to jeremiahkvasnik@npumail.com. The conference will be a forum for presenting NPU with verbal and written questions relating to the RFP. NPU will provide responses during the conference as appropriate. Responses to all questions presented in writing at the Pre-Selection Conference will be provided to all candidate respondents in a formal RFP Addendum. All subsequent questions will be answered in writing and submitted as an Addendum to this RFP to all candidate respondents. Proposals will not be considered unless respondents to this RFP are in attendance at the Pre-Proposal Conference and submit proposals before the deadline. Proposals shall be delivered to: Norwich Public Utilities Attn: Jeremiah Kvasnik 16 South Golden St. Norwich, CT 06360 Receipt of delivery will be provided upon delivery if requested.

3.2. Proposal Evaluation Criteria

A contract will be awarded to provide services and equipment, in accordance with this RFP, based upon an evaluation of proposals according the following criteria and associated weighting:

25%: Compliance with proposal document requirements as specified in Section 3.2

DRAFT

10

25%: Price quotation for all professional services and equipment proposed to meet the requirements of this RFP

20%: Qualifications of equipment vendor 30%: Qualifications of candidate contractor

Proposals shall not be considered that:

1. Are submitted to NPU after the submission deadline; 2. Are submitted by a respondent without a representative in attendance at the Pre-Proposal

Conference; 3. Do not meet the technical equipment and functional specifications defined in Section IV.

Multiple proposals from a single respondent shall not be considered. If multiple proposals are received from a single respondent, only the first proposal received by the City shall be considered in response to the RFP.

3.2.1. Proposal Document Requirements

All proposals shall include the components specified in Sections 3.2.2 through 3.2.5. Additional information may be provided to illustrate specific competitive advantages of a proposal, or provide additional recommendations beyond the minimum requirements of the document.

3.2.2. Technical Proposal

The proposal shall include an explanation of the technical solution proposed to meet the requirements of the RFP. The explanation shall address all technical requirements of the RFP, providing a list of the hardware and software components, including manufacturer and model information. For each equipment component, manufacturer information shall be provided to illustrate compliance with the technical equipment specifications defined in Section 4.3. Descriptions of applicable hardware and software configurations shall be provided, in addition to network diagrams, to illustrate the architecture of the proposed solution.

3.2.3. Timeline

The proposal shall include a timeline defining key milestones, resources, and time requirements. The awarded contractor shall be expected to adhere to the proposed timeline, which shall be stipulated as terms within an awarded contract. The timeline shall indicate project completion within six months from contract award. The actual project timeline will be developed by NPU, and may occur in a phased implementation.

3.2.4. Price Quotation

A price quotation shall be provided encompassing all equipment and services proposed to meet the requirements of this RFP. Pricing for equipment shall be itemized for each site and organized by end user (i.e. NPU, the City of Norwich, and NPS). Pricing for network integration must be provided on a per-site basis. Pricing for maintenance shall be itemized by equipment component as defined by Section 4.5.

DRAFT

11

NPU shall reserve the right to purchase or reject any itemized portion of the proposal at quoted prices, and shall reserve the right to modify quantities of itemized equipment and services after the award of a contract. Itemized prices for equipment and services shall be valid for six months.

3.2.5. Contractor Qualifications

The proposal shall identify the technical qualifications of key staff proposed to provide professional services in accordance with this RFP. Capabilities of the proposed staff shall be illustrated with respect to the technologies and skill sets required to complete the scope of work defined by this RFP. Descriptions of the respondent’s involvement in three similar projects, including reference contact information, shall be provided.

DRAFT

12

IV. Statement of Work

4.1. General Scope of Work

The following sections define the scope of work required for the implementation and ongoing maintenance of the data networks operated by NPU. The objective of this implementation is to construct an IP-based, Ethernet network capable of supporting NPU, NPS, and the City of Norwich’s data communications needs. The network upgrade shall utilize Gigabit Ethernet switching equipment at each non-SCADA site to provide direct, redundant connectivity to a core router at the nearest hub site. The network shall include a ten Gigabit Ethernet backbone ring between core hub facilities. The NPU SCADA network shall utilize environmentally hardened Gigabit Ethernet data equipment in a ring formation. The requirements defined in this document are intended to provide a high-capacity, scalable infrastructure to meet current and future application requirements. The contractor selected to perform the network implementation shall be required to fulfill the following general tasks:

• Meet with NPU to revise and finalize equipment selection and system designs following contract award;

• Develop a final, detailed project timeline for review and approval by NPU following

contract award;

• Develop a work plan with NPU to ensure continued network connectivity during implementation;

• Supply all equipment, cabling, and accessories necessary to meet the functional and

technical design specifications; • Pre-stage, install, and configure all equipment, cabling, and accessories required to meet

the functional and technical design specifications;

• Meet with NPU on a weekly basis, or as needed, during planning and installation phases to provide status updates;

• Staff augmented support “help-desk” during network implementation to facilitate rapid

response to network outages or network application problems relating to the network upgrade;

• Provide manufacturer equipment documentation and system as-built diagrams following

completion of the installation; • Complete comprehensive acceptance testing of the completed network;

DRAFT

13

• Provide operational training for NPU staff; and • Offer optional equipment maintenance contracts and/or extended warranties.

The I-Net implementation must support the existing applications and communications protocols. All existing client devices and addressing must be supported. The contractor shall provide all labor, materials, equipment, permits, and documentation necessary to fulfill the requirements contained in this RFP. The contractor shall be required to furnish and install the required equipment, including interfacing the equipment to the outdoor fiber optic plant and existing network and user devices. The contractor shall supply and install all necessary jumper and patch cables at each site. NPU shall be responsible for verification of fiber performance and remediation of any problems relating to the outdoor fiber optic plant.

4.2. Network Upgrade Architecture

4.2.1. System-Level Network Design

The upgraded network shall include Gigabit Ethernet switching equipment at each NPU non-SCADA, NPS, and City site. Each site shall utilize a single pair of fibers around the backbone ring to the hub. The contractor shall provide hardened Gigabit Ethernet equipment at each NPU SCADA site. All of the SCADA sites on a particular backbone ring shall utilize one pair of fiber around the backbone ring. Core Ethernet routing switches shall be located at the NPU administration building and the Bean Hill Electric Substation for aggregation of Gigabit Ethernet links to I-Net sites. The core equipment shall utilize a ten Gigabit Ethernet ring over a single pair of fibers between the core hub sites. The core router shall have a chassis-based design for modular support of interface cards, and shall have fully redundant common components (processors, power supplies, etc.) within each switching chassis. Except as discussed in Section 4.2.3, the Contractor shall use standards-based Gigabit Ethernet equipment to implement a topology consisting of logical point-to-point, redundant connections between the core and each NPU non-SCADA, NPS, and City site. With the initial cutover from leased services to Ethernet, the existing layer-3 Ethernet architecture shall remain the same, with routing between VLANs occurring on the core switching equipment. Figure 5 illustrates the general network architecture.

DRAFT

14

Figure 5: System-Level I-Net Architecture

DRAFT

15

4.2.2. Core Equipment Configuration

The network core shall contain layer-3 switching equipment to support the aggregation of Gigabit Ethernet connections to I-Net sites. NPU, NPS, and the City shall share common switches. Core switching equipment shall have a modular design supporting cost-effective expansion and hot swapping of interface modules. The core switching equipment shall provide layer-3 packet forwarding rates of at least 48 Mpps, and support non-blocking layer-2 switching capacity between all possible interfaces simultaneously. The core switching equipment shall meet all technical specifications defined in Section 4.3.2. NPU shall be provided with two redundant core switches, one at the NPU Administration Building and one at the Bean Hill Substation. Each core switch shall be equipped with redundant power supplies and redundant switching and routing processors. All redundant components within a single switch chassis shall be configured for automatic cutover in the event of a hardware failure. NPU’s core switching equipment shall be configured to support Gigabit Ethernet connectivity to I-Net sites as defined within Section 4.2.3, and provide full core hardware redundancy (Figure 6).

Figure 6: City Core Equipment Configuration

NPU’s two core switches shall be redundantly interconnected with a ten Gigabit Ethernet connections. The interconnection shall be terminated on different interface modules in each switch, and shall be bundled to act as a single layer-2 connection, transparent to Spanning Tree Protocol (STP) and layer-3 protocols. The bundled interconnection links shall provide load sharing during normal operation, and shall support the re-convergence of traffic over a single functional link within one second in the event that the other link fails or is removed. Additionally, all core switches shall be capable of bundling redundant connections between the

DRAFT

16

core and switches at I-Net sites. Gigabit Ethernet connections shall be distributed across switching interface modules such that the westbound and eastbound connections from an I-Net site are not both connected to the same interface module in the switch. NPU’s core switching equipment shall support the utilization of Rapid Spanning Tree Protocol (RSTP). Core switches shall support VLAN trunking (IEEE 802.1q), enabling multiple VLANs to be carried over individual Gigabit Ethernet links. VLAN trunks shall be configured between the core and City Hall, containing all City VLANs. VLAN trunks shall be configured between the core and NPU Administration Building, containing all NPU VLANs. VLAN trunks shall be configured between the core and NPS Administration Building, containing all NPS VLANs. All routing between VLANs shall be performed within the core switches.

4.2.3. Typical I-Net Site Configuration

Each I-Net site shall be equipped with a new Gigabit Ethernet switch for connectivity to local client devices and existing access layer switches, where necessary, and support Gigabit Ethernet uplinks over the I-Net backbone fiber. The backbone Gigabit Ethernet uplinks shall be supported using standards-based Gigabit Ethernet optical interfaces with the proper optical power output to provide connectivity to the core Ethernet switching equipment. The Ethernet backbone switch shall provide at least 24 autosensing 10/100Base-TX ports, which will serve as a direct replacement for switching provided by the existing leased services routers. Equipment currently connected to the Ethernet ports on existing leased services routers, including workgroup switches, hubs, transceivers, workstations, and other client devices, shall be directly connected to the Ethernet backbone switch. All access-layer switches in intermediate wiring closets within an I-Net shall be connected directly to the backbone Ethernet switch at a given site. Existing IP addressing shall be retained for all NPU, City, and NPS facilities. The backbone Ethernet switch shall meet the requirements in Section 4.3.3. Figure 7 illustrates the upgraded typical equipment configuration.

DRAFT

17

Figure 7: Typical I-Net Site Equipment Configuration

4.2.4. SCADA Equipment Configuration

The SCADA network shall support a Gigabit Ethernet backbone network connecting each SCADA site together in ring architecture over a pair of fiber optic strands within each fiber optic ring. The SCADA backbone ring shall terminate on Gigabit Ethernet optical interfaces on redundant interface modules at each core site. The SCADA access switch shall support two (2) standards-based Gigabit Ethernet optical interfaces. The equipment shall be configurable in a ring formation capable of Rapid Spanning Tree Protocol. In the event of an outage at one SCADA site, the ring shall reroute traffic around the outage. The SCADA access switch shall provide at least six (6) 10/100 Mbps copper Ethernet ports. The SCADA system shall meet or exceed with the following environmental conditions: a temperature range of -40 °C to 80 °C, and a humidity rating of 95% non-condensing. Figure 8 depicts the SCADA equipment configuration.

DRAFT

18

Figure 8: SCADA Equipment Configuration

4.3. Equipment Specifications

4.3.1. General Ethernet Switch Specifications

Certain general specifications and standards compliance are required for all Ethernet switching equipment provided in accordance with this RFP. The specifications provided in this section, defined by the Institute of Electrical and Electronics Engineers (IEEE) and the Internet Engineering Task Force (IETF), are intended to serve as a minimum baseline for hardware support. All switches provided in accordance with this RFP shall be compliant with the following standards and protocols:

• IEEE 802.1q (Virtual LANs) • IEEE 802.1d (Spanning Tree/Bridging) • IEEE 802.1w Rapid Spanning Tree Protocol • IEEE 802.1s Multiple Spanning Tree Protocol (MSTP) • IEEE 802.1p (QoS) with support for 8 priority queues; • IEEE 802.3 (10Base-T, 10Base-FL)

DRAFT

19

• IEEE 802.3u (100Base-TX, 100Base-FX) • IEEE 802.3x (Flow Control) • IEEE 802.3z (1000Base-SX, 1000Base-LX) • IEEE 802.3u Auto-negotiation on Twisted Pair • SNMPv3 Simple Network Management Protocol version 3 • RMON (RFC 1757) Remote Network Monitoring Management • Telnet (RFC 854) • DiffServ (QoS) • BootP/DHCP relay (RFC 2131) • IGMP Snooping (RFC 2236) Internet Group Management Protocol Snooping

Additionally, all switches shall be rack mountable in standard 19-inch equipment racks. All power supplies shall be compatible with standard 110 VAC electrical power.

4.3.2. Core Ethernet Switch

In addition to the minimum specifications in Section 4.3.1, the core switches shall support the following standards and protocols:

• IEEE 802.3ae (10 Gigabit Ethernet) • OSPFv2 (RFC 2328) Open Shortest Path First • RIPv1 (RFC 1058) Routing Information Protocol • RIPv2 (RFC 1723) • IP (RFC 791) Internetworking Protocol Routing • IPv4 Router Requirements (RFC 1812) • DVMRP (RFC 1122) Distance Vector Multicast Routing Protocol • IGMP (RFC 1112, RFC 2236) Internet Group Management Protocol

A modular switching chassis shall support core switching for the network at both NPU Administration Building and Bean Hill Substation. Each core switch shall be equipped to meet the following minimum requirements:

• Chassis-based, 19-inch rack-mounted design allowing modular expansion and hot-swapping of interface modules without interruption to service;

• Provide non-blocking switching capacity equal to the total throughput of all installed interface modules, scalable for future growth to at least 100 Gbps total layer-2 switching capacity. The switching equipment must demonstrate non-blocking throughput port-to-port on the same backplane;

• Capable of packet-forwarding throughput of at least 48 million packets per second (48 Mpps) in each switching chassis;

• Capable of supporting 10 Gigabit Ethernet interfaces (IEEE 802.3ae); • Contain redundant power supplies and applicable processing engines in each

switching chassis, capable of automatic failover; and

DRAFT

20

Each of the core switches shall be equipped to support at least 64 Gigabit Ethernet ports in two or more hot swappable modules. The Gigabit Ethernet ports shall be equipped with standards-based Gigabit Ethernet optical interfaces with the proper optical power output to provide connectivity to the I-Net sites.

4.3.3. Typical I-Net Site Backbone Switch

Each I-Net site specified by Section 4.2.4 shall be equipped with an Ethernet backbone switch that, in addition to the minimum specifications in Section 4.3.1, shall support:

• Mounting in a standard 19-inch equipment rack; and • Installation of redundant power supplies, internal or external, configured for automatic

fail-over and load sharing. Each typical backbone Ethernet switch shall support the following port densities:

• (2) 1000Base-LX or 1000Base-ZX (depending upon the fiber optic loss to the core); and • 24 10/100Base-TX autosensing ports for connectivity to existing client devices, including

workstations and printers.

4.3.4. Network Management System

The contractor shall provide a network management solution in the proposal capable of providing LAN and WAN management features for all provided switching equipment and other SNMP compatible devices. The management solution must meet the following minimum specifications:

• Provide topology maps of network connections; • Allow configuration of VLAN services and corresponding switch port assignments; • Provide control of access lists and filtering policies; • Provide performance statistics; • Monitor and report hardware statistics and problems; • Provide remote access for status monitoring; • Provide access to vendor-specific remote management and monitoring tools; • Provide equipment inventories; and • Support centralized remote firmware upgrades for switching equipment.

4.4. Integration Requirements

4.4.1. General Implementation Responsibilities

Upon being awarded the proposal, the contractor shall survey all network sites, and provide NPU with a list of site remediation recommendations necessary for reliable, safe installation of the network equipment, such as upgrades to electrical service, structure enhancements for equipment mounting, or LAN cabling improvements. The contractor shall indicate whether site remediation

DRAFT

21

requirements will impact the implementation timeline, and identify any risks relating to interruptions in services. The contractor shall work with designated technical staff from NPU, NPS, and the City before and during the installation of equipment to ensure that the I-Net equipment is installed and configured to support the existing networks. The contractor shall participate in weekly status meetings to report on progress, plan installations, and discuss any risks or necessary network service interruptions expected. Site Surveys All sites shall be evaluated for the purpose of identifying any attributes of the physical site preparation that may result in network service interruptions or cause difficulties with the installation:

• Physical space requirements for equipment; • Existing LAN cabling; • Electrical power requirements of the equipment; • Climate control; • Network application requirements; and • Existing network configuration.

Any necessary site preparations shall be identified and reported to NPU. The contractor shall provide each agency with minimum specifications for physical space, electrical service, and HVAC requirements needed to support the equipment to be installed under the awarded proposal. NPU will evaluate any recommendations for site preparations requiring construction, cabling, or additional electrical powering, and provide the contractor with a schedule for the site preparations they will perform. The contractor is responsible for ensuring that existing applications that utilize backbone connections to other sites, such as e-mail, are supported after the upgrade and shall ensure that the necessary information regarding applications are collected in advance of each site cutover to mitigate the risk of service outages. The contractor is expected to meet with NPU, City and NPS staff to discuss application requirements in detail. The contractor shall coordinate integration work with NPU to allow NPU, the City, or NPS to elect to have personnel on-site during installations to work with the contractor Equipment Installation All equipment shall be delivered and physically installed at each site by the contractor. I-Net hardware shall be installed in existing equipment racks. If the site surveys identify inadequate rack space, NPU, the City, or NPS shall be responsible for providing the necessary rack space. Existing UPS hardware shall be utilized unless deemed inadequate, in which case UPS equipment shall be provided by the contractor. Bids should reflect UPS hardware as optional line items for each site in the itemized price proposal.

DRAFT

22

Proper connections to electrical power, LAN cabling, and fiber optic I-Net cabling will be performed by the contractor. The contractor will provide all jumper cables and other necessary cabling accessories. The contractor will be responsible for removing boxes and packaging materials from I-Net facilities. Network Configuration NPU is requiring a turnkey integration of the network, such that the installed equipment meets the requirements defined in this document. The contractor shall configure network devices so that the network maintains all existing network functionality, including support of existing network protocols and all current applications. The contractor will be expected to maintain existing addressing schemes, VLANS, and routing configurations with the configuration of new equipment, unless otherwise agreed by NPU. The contractor shall perform all network site cutovers in such a way as to minimize service outage risk, including maintaining network connectivity for back-out purposes in the event that a problem occurs during the network cutover. The contractor shall provide product documentation for all equipment, including operating manuals and warranty information in electronic form. The contractor shall provide as-built documentation of all equipment connections and configurations.

4.4.2. Cutover Plan

The upgrade shall occur in the following main phases:

1. Design and Planning 2. Equipment Burn-In 3. Core Integration 4. Ring Cutovers

Design and Planning Following site surveys, the contractor shall develop detailed network designs for the approval by NPU. The designs shall include diagrams of physical device connectivity for the entire network, diagrams of device connectivity for individual sites, and device configurations. The contractor shall develop a cutover schedule, identifying the NPU, City, or NPS resources required, including contact information, building access, and modifications to existing network devices. Equipment Burn-In All network equipment shall be setup and configured according to the detailed design prior to delivery. The equipment shall be tested and operated on the contractor’s premises for a minimum of three days prior to delivery to minimize the risk of delivering and installing defective equipment.

DRAFT

23

Core Cutover Prior to the first site cutover, the new core equipment shall be installed and configured to provide connectivity to all sites. Cutover of I-Net sites to the network shall coincide with the cutover schedule developed by the contractor and NPU. All equipment shall be installed, configured, and tested for continuity before active network equipment, such as workstations, existing hubs and switchers, printers, and servers, are connected to the new backbone switching equipment. The SCADA network cutover shall occur on an individual ring basis, one site at a time. The SCADA cutover shall begin at the Core site for each ring, and progress consecutively around to each site on the ring back to Core site. The rotational progression of the SCADA cutover shall be performed to allow the cutover to occur at a given site without affecting connectivity to all other SCADA sites on the same ring. All equipment shall be installed, configured, and tested for continuity before active SCADA equipment is connected to the new backbone switching equipment. The contractor shall be prepared to back-out of any site cutover and restore existing network connectivity in the event of an unscheduled service outage caused by the cutover. Following successful completion of the initial cutovers, the contractor shall be responsible for proposing a core routing configuration to optimize traffic flows, security, manageability, and scalability. During implementation and all site cutovers, the contractor shall have staff onsite or nearby and available to augment existing network support operations for at least two full business days following the cutover of any individual site to respond rapidly to problems arising as a result of the cutovers.

4.4.3. Work Hours

All work performed under this RFP shall be scheduled with the appropriate contact for each I-Net agency a minimum of 24 hours in advance, except in an emergency. Contractors must be able to perform work after normal business hours (8AM to 5PM), if requested to prevent interruption to critical network services.

4.4.4. Testing

Upon completion of implementation at a particular site, the contractor is required to test all systems. A written performance evaluation will be submitted to NPU, reporting the results of the testing and verifying proper system operation. Testing shall include, but shall not be limited to, verifying connectivity between sites and the core over redundant links. Both ping testing and file transfer will be adequate to demonstrate system operation in most cases. The contractor shall work with NPU, the City, and NPS to ensure that network applications function properly. If any network services are not satisfactorily

DRAFT

24

supported after any stage of the upgrade, the contractor shall return the affected portion of the network to its original state until a resolution can be developed. Failover to redundant links shall be tested by demonstrating the preservation of continuity after disconnecting corresponding primary links. Redundancy testing shall also be performed on core network equipment in order to demonstrate failover of redundant controller cards, power supplies, interface cards, etc.

4.5. Equipment Maintenance

The contractor shall offer a support contract for all equipment provided under this RFP. The support contracts shall be offered with the following options for each component on an individual basis: Option 1 – 24x7x4 Maintenance:

The contractor shall provide a comprehensive maintenance contract providing a four-hour response time (24x7x4) from the time of notification for repairing hardware failures or replacing equipment. The contractor must be available at all times for notification of network problems.

Option 2 – 8x5x4 Maintenance:

The contractor shall provide a comprehensive maintenance contract providing a four-hour response time during normal business hours (Monday through Friday, 8AM to 5PM) for repairing failures or replacing equipment. The contractor must be available at all times for notification of network problems.

Option 3 – Two-Day Advanced Replacement: The contractor shall offer equipment replacement contracts, to be delivered within two days of notification of hardware problems. The contractor must be available for notification during normal business hours.

All equipment support contracts shall be made for a one-year period, and renewable at the discretion of NPU. A price quote shall be provided for each option on an individual equipment component basis.

DRAFT

Appendix A: Institutional Network Site List and Estimated Fiber Losses

Block Diagram A Fiber LoopCity

Site Name Address EastEast

Footage East km

East Est Fiber

Loss (0.5) WestWest

Footage West km

West Est Fiber

Loss (0.5)C12 Laurel Hill VFD 509 Laurel Hill Rd 00-C12 50,943 15.5 8.5 C12-00 12,290 3.7 2.6C11 Parking Comm. 307 Main St 00-C11 44,156 13.5 7.5 C11-00 4,239 1.3 1.4C10 Public Library 261 Main St 00-C10 43,949 13.4 7.4 C10-00 4,032 1.2 1.4C9 Tourism 77 Main St 00-C9 43,919 13.4 7.4 C9-00 5,266 1.6 1.6C8 Human and Youth Services 80 Broadway 00-C8 43,588 13.3 7.4 C8-00 5,779 1.8 1.6C7 Community Development 23 Union St 00-C7 42,597 13.0 7.2 C7-00 5,632 1.7 1.6C6 City Hall 100 Broadway 00-C6 42,560 13.0 7.2 C6-00 5,595 1.7 1.6C5 Recreation 75 Mohegan Rd 00-C5 34,985 10.7 6.1 C5-00 13,650 4.2 2.8C4 Rose Senior Center 8 Mahan Dr 00-C4 33,489 10.2 5.9 C4-00 14,906 4.5 3.0C3 Taftville VFD 134 Providence 00-C3 19,961 6.1 3.8 C3-00 28,382 8.7 5.1C2 Occum VFD 44 Taftville Occum Rd 00-C2 27,204 8.3 4.9 C2-00 39,125 11.9 6.7C1 EMS 444 N. Main St 00-C1 11,439 3.5 2.5 C1-00 48,272 14.7 8.1C24 Dog Pound Mohegan Park 00-C24 3,483 1.1 1.3 C24-00 44,558 13.6 7.5School

Site Name Address EastEast

Footage East km

East Est Fiber

Loss (0.5) WestWest

Footage West km

West Est Fiber

Loss (0.5)S11 Veterans Memorial 80 Crouch Ave 00-S11 53,739 16.4 8.9 S11-00 15,086 4.6 3.0S10 Bishop Elementary 526 E. Main St 00-S10 47,960 14.6 8.1 S10-00 9,307 2.8 2.2S9 Norwich Adult Education 182 Cedar St 00-S9 41,690 12.7 7.1 S9-00 7,923 2.4 2.0S6 Kelly Middle School 25 Mahan Dr 00-S6 33,642 10.3 5.9 S6-00 15,059 4.6 3.0S5 John Moriarity 20 Lawler Ave 00-S5 24,098 7.3 4.4 S5-00 30,569 9.3 5.4S4 Wequonnoc School 155 Providence St 00-S4 20,171 6.1 3.8 S4-00 28,592 8.7 5.1S3 Greenville School 165 Golden St 00-S3 5,473 1.7 1.6 S3-00 48,142 14.7 8.1S2 Norwich High School 191 Hickory St 00-S2 4,504 1.4 1.4 S2-00 47,173 14.4 7.9S1 Hickory Street School 201 Hickory St 00-S1 4,383 1.3 1.4 S1-00 47,052 14.3 7.9NPU

Site Name Address Site Footage KmEst Fiber Loss (0.5)

13 NPU Service Center 173 N. Main St 00-13 1,723 0.5 1.011 N. Main Street Substation 149 N. Main St 13-11 662 0.2 0.912 N. Main Street Gas 157 N. Main St 11-12 264 0.1 0.810 Rose Alley Sewer 8 City Landing 12-10 3,619 1.1 1.360 Market St Sewer 90 Chelsea Dr 10-60 2,630 0.8 1.239 River Sewer 121 River Avenue 60-39 3,946 1.2 1.415 Talman Gas 196 Talman St 39-15 5,990 1.8 1.714 Talman Sewer 220 Talman St Ext. 15-14 839 0.3 0.943 Talman Ext. Gas 291 Talman Street Extension 14-43 1,174 0.4 0.951 Victoria Landing 296 Hamilton Ave. 43-51 6,459 2.0 1.79 Orchard Radio 59 Orchard 51-9 14,304 4.4 2.955 Mohigan Park Tank 40 Judd Rd. 9-55 1,627 0.5 1.056 Taftville Gas Banjo 16 Hunters Ave 55-56 25,331 7.7 4.65 Taftville Electric 8 Providence Ave 56-5 2,339 0.7 1.16 Occum Sewer 208 Taftville Occum Rd 5-6 5,021 1.5 1.57 Occum Hydro 1 Bridge Rd 6-7 5,496 1.7 1.621 Bolduc Sewer 39 Bolduc Ln. 7-21 15,453 4.7 3.14 Greenville Gas 23 Lorenzo St 21-4 3,662 1.1 1.38 Ruth Street Gas 328 Boswell Ave 4-8 6,804 2.1 1.83 Mohegan Gas 87 Mohegan Park 8-3 2,294 0.7 1.12 10th Street Hydro 7 Eighth St 3-2 3,640 1.1 1.31 2nd Street Hydro 387 N. Main St 2-1 3,296 1.0 1.30 NPU Admin Building 16 South Golden Street 1-00 3,666 1.1 1.3

DRAFT

Norwich Connecticut I-Net Design

Block Diagram B Top Fiber LoopCity

Site Name Address EastEast

Footage East km

East Est Fiber

Loss (0.5) WestWest

Footage West km

West Est Fiber

Loss (0.5)C13 Comm Tower 409 Plain Hills 00-C13 20,472 6.2 3.9 C13-00 19,248 5.9 3.7C14 Public W orks 50 Clinton Ave 00-C14 3,124 1.0 1.2 C14-00 39,174 11.9 6.7NPU

Site Name Address Site Footage kmEst Fiber

Loss (0.5)00 Bean Hill Substation 20 Connecticut Ave 00-50 3,388 1.0 1.350 Parkwoods Condo 34 Parkwood 50-16 2,847 0.9 1.216 Water Booster 33 Connecticut 16-17 4,431 1.4 1.417 LNG Facility 10 Wisconsin Ave 17-59 3106 0.9 1.259 Forestview Pump Station 59-46 6,642 2.0 1.846 Dodd Stadium 14 Stott Ave 46-18 4,114 1.3 1.418 Industrial W ater Tank 304 Plain Hills 18-19 20,863 6.4 3.919 Royal Oaks Water 92 Plain Hills 19-20 4,846 1.5 1.520 Norwich W ell 242 W. Town St 20-37 2,418 0.7 1.137 Yantic Flats Gas 281 W. Town St 37-00 1,049 0.3 0.9

DRAFT

Block Diagram B Lower Fiber LoopCity

Site Name Address EastEast

Footage East km

East Est Fiber

Loss (0.5) WestWest

Footage West km

West Est Fiber

Loss (0.5)C23 Yantic VFD 151 Yantic Rd. 00-C23 2,773 0.8 1.2 C23-00 2,773 0.8 1.2C15 Police 70 N. Thames 00-C15 23,134 7.1 4.3 C15-00 39,938 12.2 6.8C16 Fire 10 N. Thames 00-C16 25,573 7.8 4.6 C16-00 38,151 11.6 6.6C17 Health Dept 372 W. Main Street 00-C17 27,206 8.3 4.9 C17-00 36,370 11.1 6.3C18 Ice Rink 641 New London Tpk 00-C18 35,236 10.7 6.1 C18-00 35,835 10.9 6.2C19 Golf 685 New London Tpk 00-C19 36,416 11.1 6.3 C19-00 37,024 11.3 6.4C20 East Great Plain VFD 488 New London Tpk 00-C20 31,172 9.5 5.5 C20-00 31,780 9.7 5.6C21 Child Care 92 Salem Tpk 00-C21 35,182 10.7 6.1 C21-00 29,576 9.0 5.3School

Site Name Address EastEast

Footage East km

East Est Fiber

Loss (0.5) WestWest

Footage West km

West Est Fiber

Loss (0.5)S12 Zinewicz School 30 Case St 00-S12 59,466 18.1 9.8 S12-00 6,208 1.9 1.7S13 Sam Huntington School 80 W.Town St 00-S13 57,377 17.5 9.5 S13-00 6,337 1.9 1.7S14 School Admin 90 Town St 00-S14 54,768 16.7 9.1 S14-00 8,284 2.5 2.0S15 Uncas School 280 Elizabeth 00-S15 36,877 11.2 6.4 S15-00 33,031 10.1 5.8S16 Mahan School 94 Salem Tpk 00-S16 29,145 8.9 5.2 S16-00 34,751 10.6 6.0S17 Teachers Middle School 15 Teachers Dr 00-S17 22,876 7.0 4.2 S17-00 47,840 14.6 8.0S18 Stanton School 386 New London Tpk 00-S18 22,428 6.8 4.2 S18-00 47,392 14.4 8.0NPU

Site Name Address Site Footage kmEst. Fiber Loss (0.5)

47 Sunnyside Sewer 49 Sunnyside Street 00-47 2,813 0.9 1.253 Norwich TWN Banjo 114 W. Town St. 47-53 7,943 2.4 2.052 Yantic Landing 86 Otrobando Ave. 53-52 2,767 0.8 1.242 Fairview Pump 56 Reservoir Rd. 52-42 9,545 2.9 2.244 Falls Mills Apt 150 Yantic St. 42-44 14,248 4.3 2.954 Sachem St. Banjo 72 Sachem St. 44-54 5,028 1.5 1.524 Cove Sewer 10 N. Thames 54-24 6,549 2.0 1.722 Falls Ave Wastewater 106 Falls Ave 24-22 2,360 0.7 1.123 S.Thames Sewer 151 S. Thames 22-23 4,076 1.2 1.438 Dunham Sewer 223 Dunham Street 23-38 4,389 1.3 1.457 Shipping St Sewer 38-57 2,429 0.7 1.148 Edgewood Dr. Pump 13 Edgewood Dr. 57-48 3,206 1.0 1.225 Dunham Gas 256 Dunham St 48-25 12,579 3.8 2.749 Uncas Condos 527 W. Thames St. 25-49 10,931 3.3 2.429 Shore Road Sewer 20 Shore Rd 49-29 3,999 1.2 1.426 Old Salem Sewer 31 Old Salem Rd 29-26 10,025 3.1 2.327 Marcus Sewer 90 Norman Rd 26-27 2,870 0.9 1.228 Salem Sewer 1 46 Salem Tpk 27-28 3,326 1.0 1.340 Great Plain Sewer 98 Great Plain Road 28-40 3,372 1.0 1.358 Salem Sewer Pump 2 128 Salem Tpk 40-58 1,762 0.5 1.031 Salem Gas 245 Salem Tpk 58-31 3,862 1.2 1.330 Salem Sewer 3 326 Salem Tpk 31-30 2,408 0.7 1.133 Dudley Electric 111 Dudley St 30-33 18,082 5.5 3.534 Matlack Electric Substation Matlack Rd 33-34 3,563 1.1 1.341 Phelps Dodge Sewer/Power 41 Wawecus St. 34-41 9,791 3.0 2.235 Browning Gas 14 Barnsider Ln 41-35 6,468 2.0 1.736 Yantic Water 36 Philanne Dr 35-36 4,608 1.4 1.500 Bean Hill Substation 20 Connecticut Ave 36-00 12,717 3.9 2.7 Notes: 1 Fiber distances are based on cable operator construction design plans.

2 Link loss based on maximum of 0.5 dB loss per km of fiber (including splice loss) and 0.75 dB loss per mated connector pair (includes jumper cable connections from termination panel to network interface device).

General comments about fiber build • The statement of work has a general layout of the fiber network. There are some minor

changes to this layout but the overall structure has not changed. We still have 3 major loops for the fiber. These changes do include adding and deleting some sites.

o Sites removed: C8, C7, S1 o Sites added include 3 city sites and 2 NPU SCADA sites.

• All fiber installed is single mode fiber Questions from attendees: 1. Do you have 144-count fiber throughout the network?

• No the core backbone is 144-count, spurs are 48-count fiber and drops are 12-count. 2. You have about 15 schools on the list. Are you exploring any alternative funding? Schools could qualify for E-Rate.

• We are not a telecommunication company so we are not qualified for E-RATE. This is a private network and we do not intend to become a telecommunications company.

3. Do you have a time frame for all this to be completed? How much time do you require the contractor to complete the work?

• The fiber build is on course to be completed in mid August. NPU plains to be ready for the hardware installation by September 1st 2008. This RFP does not contain a strict timeline however, NPU would like to see steady progress. While we understand that design takes time and that lead times for equipment can be as much as 1 month, we do not want to be waiting 6 months for parts to be delivered.

• The winner of the RFP is expected to complete a site survey to every site. This site survey will take at least 2 days.

• NPU would like to see as much work as possible done during our normal operating hours of 8:00AM to 4:30PM. Understandably some work will need to be done during off hours.

• NPU would like to cut over NPU sites prior to cutting over city and school sites. Coordination of all cutovers will be done through the NPU project manager.

4. General comments about the sites

• All the NPU sites will have back up generation but not all of them have UPS. Upon completion of the site survey NPU will ask the contractor to make a recommendation on the sizes of the UPS needed. Generally speaking every station of NPU needs backup batteries. (UPS)

• Norwich Public Utilities supplies its customers with Electric, Gas, Sewer and Water. Our Hydro Generation plants, Sewers pump stations and water tanks tend to be moist environments. Understanding that moisture and electronics do not mix, NPU takes as many precautions as possible, however we feel that some type of industrial hardened equipment will be necessary.

• At most NPU gas facilities we do not allow electronics inside the building. At these locations all electronics are and will continue to be stored in weather resistant enclosures mounted to the outside of the building.

• School and City sites are non-industrial sites and should not require industrial hardened equipment

• Some NPU sites will not require industrial equipment. Each core site, all electric substations, the NPU Sewer Plant and NPU LNG plant are examples of NPU sites that contain environments where equipment can easily be placed in cool dry areas.

• Not all sites have racks. Where needed, NPU can install racks and run conduit and wire based on the contractor’s recommendations.

5. How much research was done in terms of the physical aspects of the network going into the logical layer 1 2 and 3 of design, existing network protocol and VLAN applications? How much research has been done prior to the design of the network..

• We have gathered some information. NPU’s network structure is VLAN based and will be structured. The Norwich Public School (NPS) network contains separate VLANs at each site. Generally speaking city sites have very little network structure as many sites have no connectivity prior to the completion of this project. NPU will coordinate interaction with both NPS’s and the City’s IT departments when finalizing network design.

6. I have a concern regarding SCADA design. School and City will have a pair dedicated to them. You get a limitation coming in and out of the switch based on Ethernet standards. Could you go into a little bit more detail in terms how SCADA is logically connected?

• It really depends on what kind of switch you are recommending, what kind architecture you will be recommending.

7. Are you going to specify the equipment we provide you?

• No, NPU has left the hardware vendor decision up the integrator, the winner of this RFP 8. Figure 8 on your RFP is the only figure that shows SCADA sites and it also shows work station and telephone. That would be the exception – not the rule? I am assuming you will need a 24 port switch instead of a 6 port switch for SCADA?

• Currently at a SCADA site we have a 4 wire data phone line connected to the QEI Quindar I/O module. Our intent is to replace these modules with Ethernet I/O blocks and use the fiber network to transmit back to the control center. At most SCADA sites this Ethernet I/O module will be the only connection during the initial build. Figure 8 of the RFP shows VOIP as it is one thing that we would like to plan for if possible. Additionally there are a few sites, particularly our LNG facility that have or may have work stations. Generally speaking, a site that requires the industrial hardened switch will not have a work station and or a VoIP phone.

9. Can you identify all the sites that require those switches?

• Yes I can. 99 percent of the time the SCADA site will have nothing but just SCADA at the site. All SCADA sites are NPU sites. The following is a list of NPU sites that ARE NOT just SCADA sites: Site #’s: 0, 13, 00, 17, 22.

• Sites 11 and 33 are electric substations. At these sites an industrial hardened switch may not be required.

10. Do you have any wireless meters?

• No, right now almost everything is hard wired. At one-site we have a short wireless bridge for SCADA control of a non-regulated device. All other telemetry is hardwired.

11. Will any video surveillance possibly be implemented in the future?

• Yes some sites are going to have video surveillance. The LNG, Occum Hydro and 10th St. sites already have a surveillance system. We plan to implement video surveillance in the future at more sites.

12. Are you going to use IP base cameras?

• Yes we are going to use some IP based cameras. The cameras at the three sites noted in the previous questions are all IP based cameras. NPU is currently looking at different surveillance system designs but will not likely to make any decisions in the near future.

13. Are there any critical sites?

• The core sites, 911 dispatch located at the police department and the communication towers are critical sites. Most of them are going to have a diversely routed drop. The schools are going to be 12- count drop too.

14. Why are we asking 10/100 switches instead of a better switch?

• 10/100 Base T is the base requirement for switches. We will allow for design changes, the proposal should outline changes in design, properly document them and justify the change.

15. Do you have enough spaces to store all the equipment for this project?

• We can find spaces if we need to but we don’t want to leave the equipment here for a long period of time.

16. Would you be taking support calls just from NPU or other places too?

• NPU will be the primary contact for support. NPU has good communication with the city and schools and will act as a channel for them.

17. Will you have a support tracking ticket system?

• We don’t have a support ticket system at the moment but we can certainly work on that. NPU does have 5 staff to handle easy-to-fix issues. NPS and the City also each have their own IT departments.

18. Are you looking for possibly the design of the network also?

• Your professional services and hardware should be included. We decided to do a proposal instead of bid because if it’s a bid we have to award it to the lowest bidder. We want to consider the technology you are proposing, your experience doing this type of project and having the correct equipment instead of the lowest cost equipment.

19 Will you be maintaining the fiber yourselves?

• Yes we will. US Utility Contractor Co. Inc. are putting up the fiber as we speak. After the build is completed we will maintain it ourselves.

20. Will any sites need a DC power supply?

• All of our sites will have 110V power, even the small sites. 21. How many minutes do you want the sites to be run on UPS?

• Most NPU sites have a back up generator. Typically within 5 minutes we will be up on generator power. At the core sites we would prefer UPS to be able to operate for about 20 minutes. The NPU Office core site, 16 South Golden St currently has a well over sized UPS system to utilize.

22. Are these all the competitors for the bid or are there is? Page 10 on the bid states you can’t bid on the proposal if you don’t show for the pre-bid meeting.

• NPU’s intent was to have all of the bidders present at the pre-proposal conference. The one company, not present at the pre-proposal conference, had made arrangements with NPU prior to the conference, to perform a site visit and to participate in the pre-proposal meeting via conference call. NPU will not accept any additional respondents. NPU will also be submitting the list of respondents with the addendum.

23. What kind routing protocol are you currently using?

• The NPU corporate network has VLANs set up. 90 percent of the SCADA network is not on the corporate network. Most of NPU sites do not have a network configuration, just a simple phone line.

24. What type of autonomy do you want for School sites, NPU sites? Your sites will be the hub sites?

• In terms of routing we don’t want school to see our network and vice versa. School system, City sites, Police Department and NPU will be separate entities. As far as their internal networks, it’s up to them to maintain them. Winner of this proposal is not required to support the school internal networks.

25. What type of firewall are you using?

• Right now NPU is using CISCO routers. 26. How will this project be financed?

• NPU will be responsible for paying for this proposal. NPU took out loan through Bank of America and will be paying the rest through the Electric Division. The Electric Division will be reimbursed by all other divisions thru a monthly charge.

27. Do you happen to know when it will actually start? Start date?

• We would like to start installing equipment sometime in September. However, equipment install dates and cut over dates will vary. NPU will cut over all equipment as soon as possible. For the City and Schools it may be difficult to get the money in the budget at the

right places. They do not have as much leeway as we do, since they have not necessarily budgeted for this fiscal year to cut over to this network.. The City and Schools have committed to this project. NPU will do its best to address the financial issues in regards to final cutovers in a timely manner.

28. You want the schools and their facilities to be independent and you are not responsible for their internal network. But you are bringing all the VLAN into your core sites so you are going to be responsible.

• Certainly when they have T1 lines and AT&T gives them an IP address to talk out through. Our intent is act in the same way. Certainly they will have to change the gateways on there own internal routing but we want to avoid causing a need to change their entire current network structure.

29. There is nothing on this network other than Ethernet and IP right? Or other network needs to be routed?

• No. 30. In terms of the network management are we using hardware or software?

• The contractor is responsible for supplying both the hardware and software for network management.

31. Do you have any preferences in terms of Dell or HP servers?

• NPU has no preference. Everyone is asked for their recommendation and please document why.

32. Do you have any network management right now?

• We don’t have any network management at the moment. 33. Contractor will be supplying the patch cables?

• Yes the contractor will need to provide that.

34. How long or what kind of connectors? • At most sites a standard 3 meter patch cable will be adequate. • The fibers will be terminated with SC-APC connectors

35. Do we reserve the right to change those? • SC is the preferred connection for the fiber termination panels. The equipment may have

whatever connectors that are standard. 36. For our corporation we need a facility to do the testing and work with you guys; can you provide that?

• Yes we can make some space available for you to do the equipment testing and configuration.

37. Can equipment be deployed at some of the sites to do the testing? • Yes some sites can provide enough room for the testing and cutover. Some sites needs to be

done during regular hours; some sites will needs to be done at night. 38. If we have an alternative way to do this project can we indicate that in the proposal?

• Yes, but please tell us why you want this change. Your documentation of any proposal changes will be crucial for our decision making.

39. Are you going to need some professional support in the gap during cutover?

• Yes we are going to need some support if the school system is not cutover correctly. 40. Would you guys facilitate meetings between School, City, NPU and Contractor?

• Yes we will facilitate all the meetings. 41. Do you expect us to manage our resources? You guys manage your resources? Or do you want someone to provide a full time project manager for this project?

• NPU prefers a single point of contact, the project manager, for your resources. In regards to the city and schools please consider this, we are your customer and the school/city will be our customers.

42. Other than AT&T, are there any other internet providers within the area?

• Comcast is another provider in this area. • AT&T provides the current internet for NPU, city and schools. The schools connect to the

internet via the CT Education Network. • No internet service will be part of this plan.

43. Some of the NPU sites are sewer pump stations, are they going to be in the pit? Do they need to be rack mounted?

• The electronic equipment for a sewer pump stations is typically in an enclosure standing outside to the pit. These enclosures are not large enough for a rake. A din rail mountable unit is recommended for these type sites.

Email final addendum by Friday to bidders.