Enterprise Security Camera Technology

Specifications include, but are not limited to: 1. The project is based on a phased approach in which individual buildings, open spaces, parking lots and related campus environments will be individually bid using an established time and materials pricing structure which shall include an inclusive itemized list of all one-time and recurring costs. a. Equipment must be new, not refurbished or returned b. Indicate lead time for product acquisition and implementation c. State all licensing fees (individual and bundled) for each product quoted  Camera licensing  Client licensing  Mobile software licensing  Integration licensing  Cloud storage licensing  Other applicable licensing 2. The security camera technology platform must be expandable through future investments by the university without the need to replace any equipment provided in this project for at least five (5) years. 3. The security camera technology platform must be: a. Turnkey and capable of seamlessly interfacing with the university’s current access management systems (e.g., Avigilon Access Control Manager, Cyber Lock Cyber Audit Web Enterprise Management Software and others as deemed appropriate), fire/intrusion alarm systems and related hardware/technology. b. Capable of centralizing video management, viewing, recording and storage capabilities across all Oregon Tech properties to include, at a minimum, the main campus in Klamath Falls, the Portland-Metro Campus in Wilsonville, Oregon, the Oregon Manufacturing Innovation Center (OMIC) in Scappoose, Oregon, and other ancillary locations. 4. At a minimum, the system must meet the following specifications: a. General  Security camera technology integrator shall be a certified dealer for all products bid, and in good standing with the manufacturer  Security camera technology integrator technicians must be trained and certified in the installation of all products bid, and in good standing with the manufacturer  Security camera technology integrator must provide a minimum of four (4) customer references from universities of comparable size to Oregon Tech  Include the name, address (email, if available), and phone number of the references  Oregon Tech reserves the right to reject a proposal based upon negative or non-responsive references b. Project Management  The security camera technology integrator shall provide a project manager that coordinates the planning, design, engineering, installation, programming, and maintenance of the security camera technology platform during each phase of the project  At the request of the university’s project team, the security camera technology integrator will conduct planning and engineering site assessments of all locations prior to the submission of individual bids  The security camera technology integrator’s project manager will routinely coordinate with the university’s project management team, conduct project briefings and provide an up-to-date project implementation plan  The project manager will collaborate with Oregon Tech’s network administrator in the integration of cameras and related infrastructure into the university’s network including, but not limited to, the following areas:  IP addressing  Hostnames  Passwords and network security  Port settings to allow video traffic to traverse firewalls  PoE requirements  Routers (as necessary)  Switches (as necessary)  Video bandwidth requirements  VLAN integration (as necessary)  VPN integration (as necessary)  Project manager will ensure that all Oregon Tech end users are provided training and training materials in the administration and operational use of the security camera technology platform  The security camera technology integrator shall expect to function as the prime contractor and acquire subcontractors as required  The security camera technology integrator shall be responsible for the removal and replacement of any existing security camera technology that cannot be supported by the new enterprise-wide security camera technology platform  The security camera technology integrator is expected to ensure that final products are fully operational, and meet the expectations of Oregon Tech c. Camera Technology  At a minimum, cameras will cover all hallways, exits, entrances, elevators, stairwells, adjacent open spaces/parking lots, fire escapes, fire escape landings and secured locations (e.g. Boeing Lab, chemical storage areas, radioactive materials storage, etc.) with enough detail to identify any individual  Internet Protocol (IP)-based, high-definition (HD) camera technology with capabilities up to 4K resolution at 30 frames per second (FPS) dependent on application, minimum acceptable capabilities no less than 5 MP (Super HD) resolution at 24 FPS  Bandwidth sufficient to support 24 to 30 frames per second (FPS) using cameras between 5MP (Super HD) to 4K resolution dependent on application, required capabilities and quantity  Use of standardized bandwidth calculations to be expressed in proposal  Indoor and outdoor cameras  Capable of providing body-worn, dome, bullet, box, pan/tilt/zoom, 360 degree, panoramic and specialty cameras to support Oregon Tech requirements  Vandal and weather resistant housings and mounts  UV protection required for outdoor cameras  Ingress Protection (IP) 66 compliant enclosures  Capable of recording at night through infrared or related technology  Built in motion detection and video analytics  On-board storage up to 30 days.  Power over Ethernet (PoE)  Open Network Video Interface Forum (ONVIF) and National Defense Authorization Act (NDAA) compliant camera and related technology required  Offer non-proprietary options to proprietary cameras with no degradation of capabilities d. Recording, Storage and Video Management Technology  Full cloud-based non-hosted video management, recording and storage solution (Video Surveillance as a Service - VSaaS) that requires no hosted device appliance preferred, edge recording capabilities as a minimum  Local storage for no less than 30 days  Long-term storage for no less than 30 days  Scalable to, at least, 750 cameras(state maximum limitations on number of devices supported)  Enterprise level software with capabilities to be managed over the remote client  Must have the capability to integrate with Active Directory  System must provide Shibboleth SSO or Active Directory/LDAP authentication  Must provide a multi-factor authentication solution or integrate with the university’s existing solution  Non-proprietary video export format  Email integration  Video compression  Video Analytics (full suite of analytical options to include but not limited to the following functions) and Management functions to include as a minimum:  Alarm notification  Appearance search or facial recognition feature  Camera layouts creation  Dynamic data masking  End-to-end chain of custody capabilities  Facility mapping  Geo-fencing  License plate recognition  Object identification and video tracking  Password manager  Rich content-based indexing and advanced search capability  Rules manager  System health alerts and monitoring  Tamper detection  Unusual activity/motion detection  User manager  Managed levels of access and zones of authority  Meets university ITS security standards, deviations may only be approved through the Chief Information Officer or their designee  Must run on Windows Server 2019 and beyond  Secure mobile application available for Google Android and Apple iOS devices e. Warranties and Maintenance  Provide and list manufacturer’s warranty on all parts and labor, state the process for obtaining warranty services  Provide and list no cost continuing support resources (i.e., online resource library, user groups, etc.) afforded to the university by the security technology integrator and manufacturer  Provide a time and materials bid for annual maintenance and service contract to repair, replace and reprogram any aspect of the security camera technology platform based on the complexity and scale of the existing system