UNL ebid # SCOPE OF WORK (CSN Network Management)

Transcription

1 UNL has provided the following Scope of Work document in order to provide each bidder with specific and relevant background information related to this bid document. 1. History and Background a. The University consists of the University of Nebraska Central Administration and four (4) campuses: University of Nebraska Kearney (UNK), University of Nebraska Lincoln (UNL), University of Nebraska Omaha (UNO), and the University of Nebraska Medical Center (UNMC). b. The primary mission of University of Nebraska Computing Services Network (UNCSN) is to function as the information technology services division of the University of Nebraska Central Administration. UNCSN is the primary administrative computing services and intercampus data communications provider for the University of Nebraska campuses as well as the Nebraska State College System. Each of the four University campuses have correlated IT systems and networks that interact with UNCSN. c. The University of Nebraska consists of a student body of almost 50,000 and a workforce of 13, Description of the Goods or Services Sought: a. The University of Nebraska ( the University ) invites proposals from qualified bidders to provide the deliverables and services described below for the University. If the bid process is successful, the University will enter into a contract with the successful bidder. b. The University is seeking proposals to provide an enterprise wide network monitoring and management solution. The network monitoring and management solution will be used for monitoring and management of K-12 Distance Education, political subdivisions, and Higher Education Networks (Network Nebraska). c. The selected vendor is expected to be a knowledgeable service provider capable of providing all equipment and services required to meet the needs of the University. Should this RFP not specifically identify all components necessary for the intended operation of the systems requested, the vendor should identify such components in its bid and include the components in the installation and maintenance costs. d. The selected vendor must provide maintenance for the duration of the contract and any subsequent renewal periods. Equipment specifications can be found later in this document. e. The specifications and requirements listed in this RFP are the minimal standards by which proposals will be judged. Consideration will be given to the realism of estimates, ease of use, and sound technical performance of product. f. Each Proposal shall provide the information requested or indicate consent to the requirements described. The submitted proposal should be numbered so that responses in the Proposal correspond to the number and letter of the items in the RFP. g. Mandatory bid location: University of Nebraska Computing Services Network Room 230 Nebraska Hall University of Nebraska-Lincoln 901 North 17th Street Lincoln, Nebraska h. Requested alternate bid location: University of Nebraska - Lincoln 29 SEC City Campus Lincoln, Nebraska Description of proposal requirements: 1

2 a. The University will not publish sensitive details about its internal systems in this publicly available RFP. Appropriate details about internal systems directly related to the RFP will be sent directly to all bidders who make requests for such information during the RFP question and response period. b. ALL recommendations for products and services must be vendor neutral and any deliverables, which include vendor or product specific recommendations, may be REJECTED. c. The proposal must: i. Describe your company, the nature of its legal entity (e.g. a Nebraska corporation, a limited partnership), its size, locations, and number of employees. Include the firm s history information, ownership and management structure, business practices, products and services you provide, locations, human and technology and other resources, financial profile and other information you deem relevant. Confirm that your company is qualified to do business in Nebraska. ii. Identify any litigation or claim brought against your company within the last seven years, which might reflect adversely on your company s professional image or ability in relation to providing the goods or services sought under this RFP. iii. Document if your company is currently for sale or involved in any transaction to expand or to become acquired by or merged with another organization? If so, please explain. Has your company been involved in any reorganization, acquisition or merger within the last two years? If so, please explain. iv. Provide the firms qualifications and experience in providing similar services. 4. Description of Service Requirements: a. Auto ping of device status, record of uptime and response time. b. Network Discovery with inventory and maps. i. Must Support discovery of devices using network address (subnet zero) and /31 subnets or less. c. Asset / Inventory Management based on the following criteria: i. Firmware Version ii. Serial Number iii. Ip Address / networks iv. Interface ID v. Device Name vi. Circuit ID vii. Unlimited Custom Fields d. Heads up display based on the following criteria: i. Web interface compatible with all browsers. Preference will be given to solutions that include a user friendly interface for use in management, provisioning and operation of the network elements ii. Dash board display. iii. Enhanced network Maps with auto link discovery. iv. Drill down capabilities on logical topologies (OSPF, BGP, Layer3 links). v. Compatible Google Maps integration. vi. Compatible with Geo Location. vii. Customizable. viii. Third party app integration. e. Historical graphing on utilization, bit rate, errors, discards, CPU usage, and memory. f. Report on Application and conversation traffic, # of conversations, Top talkers i. Netflow, Jflow and IPFIX g. Real time graphing h. Create custom thresholds that trigger predefined alerts and send an alert response via: i. SMS ii. Text Message or iii. Customizable event notifications that utilize data fields based on Device properties iv. Audio alarms 2

3 v. Data retention on capture, conversation, issues, and Syslog data i. Report IPSLA data on jitter, RTT, dropped packets, and latency j. QOS management to determine if QOS goals are being met. k. IPv6 Support l. Multi-vendor Device Support i. Cisco ii. Cisco Nexus iii. Juniper iv. Aruba Wireless v. Radwin vi. Cyan vii. Polycom viii. LifeSize HP ix. Cienna x. F5 xi. Fortinet xii. Import unknown device mibs xiii. browse mibs xiv. SNMP v1/v2/v3 m. Users Authenticate to network management system based on the following criteria: i. ACS ii. ldap or Active Directory iii. Local Authentication iv. Group or directory permissions. n. Distributed management with multiple levels of permissions based on the following criteria: i. Group ii. Device Name iii. Interface o. Distributed Monitoring p. Custom Reporting i. Errors/Discards ii. Utilization iii. Outages iv. Response Times v. Inventory vi. Interface Up/Down times vii. Service Level Agreement viii. Other q. Automated Device Tracking & Switch Port Management i. Monitor switches, ports, and network devices ii. Search switch for IP address, Hostname or MAC address iii. Enable and disable ports iv. Configuration Management r. Configuration management based on the following criteria: i. Automated backups ii. Automated configuration changes c. Real-Time Change Notifications iii. Configuration rollback s. IP Address Management t. Configuration compliance audits 3

4 u. Down/up info for interfaces, routing changes, routing neighbor changes, SNMP traps, power and fan, environmental levels/changes (temperature, humidity, etc.), CPU memory, errors and discards, routing states (OSPF BGP, EIGRP) v. Backup configurations using SNMP v1/v2/v3, Telnet, SSH v1/v2, and TFTP w. Root Core analysis which only alerts on the real cause of a problem and not the alerts from nodes downstream. x. Integration with other vendor network management and monitoring tools. y. Application Performance Management. z. TCP ports monitoring. aa. Web Page content monitoring. bb. Preferences will be given based on the following criteria: i. Ease of use and navigation. ii. Pricing. iii. Ease of configuration. iv. Ease of maintainability. v. Support accessibility and response times. vi. Online forums, training, documentation and knowledge base. vii. User view customizations. viii. Ability to patch and upgrade with minimal impact on current version. ix. Ability to rollback to previous software versions with minimal effort. x. Ability to delegate management. xi. All respondents must provide online demo of network management system. 1. Top 3 selected vendors must provide proof of concept. 5. Maintenance and Reliability: a. The selected vendor must have Technical Support access with the following criteria: i. Available by toll free access number and by either or web portal. ii. 24/7 and next business day support options. iii. 4 hour response time to tickets submitted as urgent. b. Software patches and upgrades: i. Documentation, patches and upgrades must easily accessible. ii. Provide a method to test all patches and upgrades in on site non-production environment. iii. Patches and upgrades must have minimal impact on previous versions and have the ability to easily roll back to previous versions without loss of data. 6. Deliverables: a. The successful bidder is required to present a proposed timeline and detailed installation plan. b. The vendor must provide for all training, hardware installations, software installations and configurations, 1st year of maintenance, on site configuration and installation support included but not limited to equipment, tools and any other goods and services necessary to accomplish the project. Vendor must include in its price all costs associated with the installation process. c. It is the University s intent that the entire installation be completed for the quoted price. Therefore, any items omitted but reasonably necessary to accomplish the project must be furnished and installed by the vendor at no additional cost to the University. d. Contract Start Date: i. The contract period will begin on the date when both parties agree that the provided service is fully operational and ready for use. ii. If it is determined at a future date that the software was in fact not able to move into production environment due to other unanticipated deficiencies in the software, the initial billing date will be moved 4

5 up to the date when the software is able to provide services listed in the requirements section of this RFP. 7. Detailed and Itemized Pricing: a. The University requests bids for a network management system starting with 500 devices with incremental increases. b. The Vendor should provide the following pricing information in a clear and concise manner for the different contract periods and options available for the University s consideration: i. Total one-time installation costs. ii. If allowable changes in capacity are requested by the University during the life of the contract, all activation, termination, and/or processing fees must be specified. c. Applicable taxes, licenses, and fees must be incorporated into the items and service bid. d. If pricing is impacted based upon the duration of the contract, the difference in price vs. time (for example, 1yr, 2yr, 3yr, 4yr, 5yr) must be clearly documented. This is to include applicable maintenance costs. e. The vendor should provide pricing for optional on site training. The pricing must detail total cost and document the cost per person and/or cost per day. f. Any costs not clearly identified will not be paid by the University. g. The University is able to participate in State of Nebraska contracts if an applicable State of Nebraska contract for Internet services exists. h. The University is able to participate in federal GSA contracts if applicable. 8. Time Schedule: a. Since time is of the essence in scheduling and completing this project, it is essential that the successful bidder agree to begin work within thirty (30) days from the date that the vendor is notified that they are the successful bidder. b. Installation Time: i. Unless otherwise indicated, the Vendor agrees to have the system fully operational within sixty (60) calendar days from the date the Vendor is notified that they were a successful bidder. ii. If the selected Vendor(s) is not successful in installing a fully operational circuit within the agreed time period, the University reserves the right to terminate the contract without penalty and award the contract to another Vendor. iii. The installation will not be considered to be complete until both the Vendor and the University agree that the connection is operational and properly carrying production traffic. c. Include in the proposal a timeline to meet this completion date. If you cannot meet this limitation, please indicate your alternate proposed time frame and schedule for completion (or on a separate sheet, if necessary). 5