N067--Replace/Upgrade Exterior Camera Surveillance System
This is a SOURCES SOUGHT ANNOUNCEMENT ONLY. It is neither a solicitation announcement nor a request for proposals or quotes and does not obligate the Government to award a contract. Requests for a solicitation will not receive a response. Responses to this sources sought must be in writing. The purpose of this sources sought announcement is for market research to make appropriate acquisition decisions and to gain knowledge of potential qualified Service Disabled Veteran Owned Small Businesses, Veteran Owned Small Businesses, 8(a), HubZone and other Small Businesses interested and capable of providing the services described below. Documentation of technical expertise must be presented in sufficient detail for the Government to determine that your company possesses the necessary functional area expertise and experience to compete for this acquisition. Responses to this notice shall include the following: (a) company name (b) address (c) point of contact (d) phone, fax, and email (e) DUNS number (f) Cage Code (g) Tax ID Number (h) Type of small business, e.g. Services Disabled Veteran Owned small Business, Veteran-owned small business, 8(a), HUBZone, Women Owned Small Business, Small disadvantaged business, or Small Business HUBZone business and (i) must provide a capability statement that addresses the organizations qualifications and ability to perform as a contractor for the work described below.
Network Contract Office (NCO) 22-Gilbert is seeking a qualified vendor to Remove the existing Outdoor Wireless Security Camera System, and Design and Install a new Outdoor Wireless Security Camera System at the Southern Arizona VA Healthcare System (SAVAHCS) at 3601 S. 6th Avenue in Tucson, Arizona. The contractor shall provide all labor, supplies, materials, and travel to meet the needs of this solicitation. Prospective contractors must be authorized/certified to provide the required service and must show proof with any provided documents at the time of responding to this Sources Sought announcement of the capabilities stated below:
An onsite project manager shall have a minimum of 5 years-experience performing similar projects of equal complexity or greater.
Engineers, technicians, and installers working onsite shall have the following training and certifications: CISCO Certified Network Professionals (CCNP-Wireless) and Cisco Certified Network Associates (CCNA-Wireless).
-- A CISCO Certified CCNP Wireless Engineer shall have a minimum of 5 years-
experience performing similar projects of equal complexity or greater as a Validation
Survey Lead Engineer. A CISCO Certified CCNP Wireless Engineer with less than 5
years-experience must have hands-on knowledge configuring VA Cisco Unified
Wireless Network (CUWN) infrastructures.
-- A CISCO trained and certified CCNA Wireless Engineer shall have a minimum of 3
years- experience performing onsite surveys and installations.
Provide documentation of 2 to 3 projects demonstrating your companies experience designing and installing outdoor wireless security camera systems of the same magnitude or greater that meet project requirements.
Provide a one-page paper on how you would internalize and manage this project.
DRAFT STATEMENT OF WORK DRAFT
TITLE: Design, Remove, and Replace SAVAHCS Outdoor Closed-Circuit Video Surveillance WIFI System
1.0 BACKGROUND
The Southern Arizona VA Healthcare System (SAVAHCS) currently has a need for a Contractor to design and install a new outdoor closed-circuit video surveillance WIFI system using a standards-based, outdoor Enterprise Class multi-point mesh solution, replacing the facility s existing Firetide (Hotport 7020) monitoring system that is currently shared with 13 Solar Photovoltaic (PV) arrays on campus (12 Solar PV carport structure arrays and one Ground Mount array).
The purpose of the mesh is to provide an outdoor data back-haul for both the high definition Internet Protocol (IP) cameras and Solar PV arrays. Once a new mesh is designed, and the current mesh is removed, a new turnkey outdoor wireless mesh network solution will be installed, separating the monitoring systems into two individual networks.
Monitoring of the Solar PV arrays will remain on the stand-alone Engineering Server located in Biomedical Engineering, while the video surveillance system (VSS) is moved to SAVAHCS IT Server located in the IT Server room. The Contractor will lead the project s software and server design through the VA s Technical Reference Model (VA TRM) and VA IT Process Request portal (ViPR) to procure permissions to add new software and camera memory to the IT server.
2.0 CONTRACTOR QUALIFICATIONS
Contractor shall have the following qualifications:
An onsite project manager shall have a minimum of 5 years-experience performing similar projects of equal complexity or greater.
Engineers, technicians, and installers working onsite shall have the following training and certifications: CISCO Certified Network Professionals (CCNP-Wireless) and Cisco Certified Network Associates (CCNA-Wireless).
-- A CISCO Certified CCNP Wireless Engineer shall have a minimum of 5 years-experience
performing similar projects of equal complexity or greater as a Validation Survey Lead
Engineer. A CISCO Certified CCNP Wireless Engineer with less than 5 years-experience
must have hands-on knowledge configuring VA Cisco Unified Wireless Network (CUWN)
infrastructures.
-- A CISCO trained and certified CCNA Wireless Engineer shall have a minimum of 3 years-
experience performing onsite surveys and installations.
Deliverables:
Certification Certificates
3.0 PROJECT MANAGEMENT
A. CONTRACTOR PROJECT MANAGEMENT PLAN
The Contractor shall deliver a Contractor Project Management Plan (CPMP) that lays out the Contractor s approach, timeline, and tools to be used in execution of the contract.  The CPMP should take the form of both a narrative and graphic format that displays the schedule, milestones, risks, and resource support.  The CPMP shall also include how the Contractor shall coordinate and execute planned, routine, and ad hoc data collection reporting requests as identified within the SOW. The initial baseline CPMP shall be concurred upon and updated in accordance with Section B of the contract. The Contractor shall update and maintain the VA Project Manager approved CPMP throughout the Period of Performance.
Deliverables:
Contractor Project Management Plan
B. PROJECT RISK AND ISSUES MANAGEMENT
Contractor shall perform risk and issues management activities, utilizing project management standards and best practices. Contractor shall develop and implement a robust risk and issues management plan. This shall include but not be limited to the development of risk management processes and the establishment and maintenance of a risk management tool for tracking risks and issues. The Contractor shall facilitate weekly risk management meetings and perform risk and issues tracking in accordance with the risk management plan.
The risk and issues tracking tool shall list all open and historical risks associated with the effort. The Contractor shall participate in comprehensive risk analysis activities and document the results in the risk tracker. Mitigation strategies and approaches shall be developed for each risk, documented, tracked and managed utilizing the risk tracking tool.
Deliverables:
A. Risk Management Plan
B. Risk Tracking & Management Tool
C. REPORTING REQUIREMENTS
The Contractor shall provide the COR with Weekly Progress Reports in electronic form in Microsoft Word and Project formats. The report shall include detailed instructions/explanations for each required data element, to ensure that data is accurate and consistent. These reports shall reflect data as of the last day of the preceding week.
The weekly Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall also identify any problems that arose and a description of how the problems were resolved. If problems have not been completely resolved, the Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The report shall also include an itemized list of all Electronic and Information Technology (EIT) deliverables to allow SAVAHCS Logistics staff prepare inventory listings. The Contractor shall monitor performance against the CPMP and report any deviations. It is expected that the Contractor will keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.
Deliverable:Â
Weekly Progress Report
D. DOCUMENT REPOSITORY
The Contractor will establish and maintain a document repository (i.e., Share Point site) that serves as the official repository of all contract documents and deliverables. Contractor will provide the Government with the link to the repository. The Contractor shall maintain the repository for 1 year beyond system turnover. The Contractor shall provide all documentation in soft format via DVD to VA prior to termination of the repository.
Deliverable:
Repository DVD
4.0 APPLICABLE DOCUMENTS
In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following:
Federal Information Security Modernization Act of 2014.
Federal Information Processing Standards (FIPS) Publication 140-3, Security Requirements for Cryptographic Modules.
VA Directive and Handbook 6102, Internet/Intranet Services, August 5, 2019.
36 C.F.R. Part 1194 Electronic and Information Technology Accessibility Standards, July 1, 2011.
Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended by the Workforce Investment Act of 1998 (P.L. 105-220), August 7, 1998.
Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004.
VA Handbook 6500.8, Information System Contingency Planning , April 6, 2011.
National Institute Standards and Technology (NIST) Special Publications (SP).
VA Directive 6508, Implementation of Privacy Threshold Analysis and Privacy Impact Assessment, October 15, 2014.
VA Handbook 6508.1, Procedures for Privacy Threshold Analysis and Privacy Impact Assessment, July 30, 2015.
OMB Memorandum, Transition to IPv6 , September 28, 2010.
VA Directive 0735, Homeland Security Presidential Directive 12 (HSPD-12) Program, October 26, 2015.
VA Handbook 0735, Homeland Security Presidential Directive 12 (HSPD-12) Program, March 24, 2014.
OMB Memorandum M-06-18, Acquisition of Products and Services for Implementation of HSPD-12, June 30, 2006.
OMB memorandum M-11-11, Continued Implementation of Homeland Security. Presidential Directive (HSPD) 12 Policy for a Common Identification Standard for Federal Employees and Contractors, February 3, 2011.
OMB Memorandum, Guidance for Homeland Security Presidential Directive (HSPD) 12 Implementation, May 23, 2008.
Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, December 2, 2011.
NIST SP 800-164, Guidelines on Hardware-Rooted Security in Mobile Devices (Draft), October 2012.
5.0 REQUIREMENT DESCRIPTION
The Contractor shall remove the current Firetide infrastructure at SAVAHCS and replace it with a standards-based, outdoor Enterprise Class mesh solution that is 100 percent compatible and can be integrated seamlessly into the existing CUWN. The CUWN infrastructure is comprised of 10 active meshes on campus. Meshes 1- 9 support Video while Mesh 10 is dedicated to Photovoltaic Management. This solution shall replace Meshes 1-10.
Reference Addendum A-Map Node Locations for specific data pertaining to endpoint/node relationship, distribution and location. The Firetide solution currently utilizes 90° panel antennas @ 19dB and supports 26 photovoltaic system nodes (13 invertors +13 meters) and 80 IP cameras. Special attention shall be given to the area where the current Mesh 9 is located due to node density to insure mitigation of co-channel interference and lack of throughput.
The existing Firetide solution in operation is depicted in Figure 1 below:
FIGURE 1: FIRETIDE MESH LOCATIONS AT TUCSON VAMC
The existing wireless infrastructure solution is based on these strategic design philosophies:
System Management
Scalable
Hierarchical
Upgradeable
Flexible client support (FIPS 140-2 Supplicant)
Standards based IEEE, IETF, FIPS 140-2, NIST, etc.
Security Focused
Interoperability With Existing VA Infrastructure
Wireless client agnostic
Legacy Client support
Resilient & Self-healing
Redundant
Tunable
Ease of Configuration, Operation, Management, Maintenance, and Use
Standardized across all deployed systems, able to be C&A Type Accredited
See Figure 2 below for a high-level overview of the existing system architecture.
FIGURE 2: VA WIFI SOLUTION ARCHITECTURE OVERVIEW
5.1 DESIGN AND TECHNICAL CONSIDERATIONS
The Contractor shall design an outdoor wireless mesh solution to entail SAVAHCS outdoor campus, approximately 119 acres in size as depicted in Figure 1 on page 5. In order for the mesh to be properly designed and engineered, the following aspects of the site must be considered:
Node locations
Line of Site
Fresnel Zone
Channel utilization
Transmit power
End-to-End Throughput
Antenna usage
Power availability
Existing cable plant fitness
The outdoor wireless network solution shall:
Fully support the prescribed End-to-End data rate levels and other requirements delineated within this document to include minimum end-to-end throughput as follows:
8Mbps for each IP camera
10Kbps per Inverter
10Kbps per meter
Provide data backhaul from endpoints to the VA Network via 5 GHz frequency spectrum, utilizing the appropriate FCC approved frequency bands for outdoor use. Only non-overlapping FCC licensed channels are to be used.
Each mesh AP shall fully support the current device bandwidth backhaul plus an additional end-to-end 16Mbmps to support the addition of 2 additional security cameras for each node to be installed to accommodate for any.
Enable resiliency and the self-healing design of the Wireless Infrastructure. The features of Radio Resource Monitoring (RRM) that enable this functionality are:
Dynamic channel assignment (DCA)
Interference detection and avoidance
Dynamic transmit power control (TPC)
Co-exist without interference with the existing Firetide System during the transition period.
No mobile 2.4/5.0 GHz clients shall be utilizing the solution.
Operate in a Point-to-Multipoint Wireless or Point-to Point paradigm.
Be designed to scale (to support a total of 250 HD cameras at a minimum) in support of VA s growing capacity needs and open in support of additional nodes. System Expansion and Scalability is a primary concern of the system solution. The system device load is expected to grow from the current base of 83 HD Security Cameras and Photovoltaic equipment to a total of 250 HD Cameras due to campus growth. The exact placement for the additional security cameras is not known at this time and it is understood by the VA that the contractor designed system mesh solution will not host the full 250 camera load and will require additional MESH APs to augment the system at a future date based on campus construction projects. The Root AP(s) for the contractor designed system shall be sized to fully accommodate the bandwidth requirements of the projected system size of 250 cameras and the existing photovoltaic connections.
Be scalable in support of additional mesh nodes because it is based on ratified Internet Engineering Task Force (IETF) and Institute for Electrical and Electronic Engineers (IEEE) standards providing the widest range of third-party vendor products. In terms of capacity, the solution shall scale 5.0GHz frequencies based on the 802.11a/n/ac specification following the summary of IEEE standard.;
Comply with all Ethernet transport standards including IEEE 802.3, IEEE802.11 a/n/ac, and IEEE 802.1p for quality of service and traffic prioritization.
Comply with Federal Information Processing Standards (FIPS) 140-2 security policies provided by NIST. The modules deployed must be configured to operate in an acceptable FIPS mode of operation as specified by the applicable Security Policy. All cryptographic modules in the delivered system components required as part of the solution to protect sensitive information or access of any kind shall be FIPS 140-2 validated and have a certificate issued by the National Institute of Standards and Technology (NIST) that can be found posted on their validation list website. The vendor shall supply a signed letter stating their application, product or module is a validated module or incorporates a validated module, the module provides all the cryptographic services in the solution and reference the modules validation certificate number. The certificate number will provide reference to the CMVP list of validated modules. The Contractor shall be responsible for maintaining the FIPS 140-2 validation throughout the performance period.
Be fault tolerant in the case of a FboNotice AP failure. In the case of FboNotice AP failure, the system shall continue to operate in 100% capacity.
Be designed in a High-Availability (HA) configuration/redundancy model.
Be designed in such a manner as to reduce or eliminate co- channel interference.
Have the ability to provide Ethernet switch functionality.
Be modular and not share any radios with access point functionality.
Be designed for VA s mission-critical environment where up-time is critical. Maximum uptime (99.999%) shall be ensured through proper design specifically focused on system performance.
Be designed to provide the MAXIMUM data rate possible with minimal re-transmits in support of HD Video.
Be FCC certified.
Provide the ability to eliminate weak radio links in the network.
Provide the ability to configure any channel in the specified frequency bands.
Support Dynamic Channel Allocation for optimal RF performance.
Provide the capability to logically combine the two radios in Bonded Mode of operation for higher bandwidth.
Support a minimum of three 10/100/1000 Base-T Ethernet switch port using RJ45 connections.
Have the ability to connect to each other over Ethernet.
Have the ability to bridge multiple remote wireless mesh networks over IP.
Support static route configurations.
Support multicast capabilities.
Support low latency of the order of 0,9 ms (average) per hop.
Support simultaneous support for video, voice and data multi services.
Support Quality of Service (QoS) and 802.1p standards based QoS.
Support username and password security for all networking interfaces.
Have hardware to support encryption.
Be capable of distinguishing between authorized infrastructure components and alien/rogue devices.
Have digitally signed firmware files.
Support 802.11i Enterprise connections as the primary form on connectivity. As such, it will support and be configured with the WPA2 protocol with AES encryption and 802.1x EAP- TLS authentication. It shall also support 802.11i Personal with WAP2 and PSKs. The 802.11i implementation must be in accordance with NIST Special Publication 800-97 Establishing Wireless Robust Security Networks (RSN): A Guide to IEEE 802.11i.
Support 256-bit AES, 40/104-bit WEP, 64/128-bit WEP, 256-bit WPA2-PSK encryption keys, 802.11i, WPA2, and RADIUS authentication.
Support ESSID encryption, and MAC address filtering.
Be rugged NEMA 4X/IP67 rated for outdoor deployments.
Include surge suppression equipment.
Be provisioned (e.g. sunshields if necessary) to operate in the specified area s environment and shall be physically secure from theft and tampering.
Be ROHS & WEEE compliant.
Operate at temperatures ranging from -40°C to 55°C (-40 to 131°F) plus Solar Loading
Each NEMA box supporting the MESH Node shall:
Require special tool to open
Vendor shall provide 2 (two tools to the VA)
Be secured with a pad lock (all locks shall be keyed the same).
Contain a hard-laminated card with the node specific name, switch name, and node specific antenna orientation data to include.
Antenna angular deflection from 0 (North)
Antenna angular deflection from 0 (Level) +up/-down
The contractor shall have the latitude to redesign the individual MESHs to provide the best distribution of Mesh Access Points (MAPs) to Routed Access Points (RAPs) for system throughput.
Each node of the Mesh has specific endpoint device loads. The Contractor shall be responsible for developing all power and channel assignments based on specifications for data rates as defined in Cisco Wireless Mesh Access Points, Design and Deployment Guide, Release 8.0, Chapter 3, Design Considerations to ensure that endpoint device throughput is assured End-to-End.
5.2 VIDEO SALIENT CHARACTERISTICS
This section provides video surveillance specifications that must be met or exceeded.
A. FEATURES
All cameras shall be:
1. Color during the day and monochromatic at night.
2. Shall be Powered over Ethernet (PoE). Network switches supporting PoE cameras
shall have a back-up power source to ensure cameras are still operational in the
event of loss of primary power to the Video Surveillance System (VSS) System.
3. Shall be rated for continuous operation under environmental conditions.
4. Be home-runed to remote nodes.
5. Each function and activity shall be addressed within the system by a unique user
defined name, with minimum of twenty (20) characters. Use of codes or
mnemonics identifying the VSS action shall not be accepted.
6. Shall come with built-in video motion detection that shall automatically monitor and
process information from each camera. The camera motion detection shall detect
motion within the camera's field of view and provide automatic visual, remote alarms
as a result of detected motion.
7. Shall be programmed to digitally flip from color to black and white at dusk and vice
versa at low light conditions.
8. Shall be fitted with Automatic Maximum Aperture Indexing/Defocus Control (AI/DC)
lenses to ensure image quality under differing light conditions.
9. Pan, tilt, and zoom (P/T/Z) cameras shall be utilized in a manner that they
complement fixed cameras and shall not be used as a primary means of monitoring
activity.
10. Dummy or fake cameras will not be utilized at any time.
11. Appropriate signage shall be designed, provided, and posted that notifies people that
area is under camera surveillance.
B. VIDEO CAMERAS
All High Definition Integrated Digital Network Cameras shall have:
Dual video streams with up to 8.3 Megapixel resolution (3848 x 2160) in progressive
scan format.
Pickup devices (CCD or CMOS) shall be matched to the conditions to provide optimum picture quality and transmission.
3. Alarm inputs and relay outputs built-in for integration with hard-wired external sensors.
4. Or be capable to upgrade firmware throughout the Network using software-based
device utilities.
5. Auto back focus (ABF) functionality using a push button on the camera. ABF
parameters shall also be configurable through a standard Web browser interface.
6. A video output port providing a means for adjusting the field of view and focus at the
camera.
7. Advanced low-light capabilities for color and day/night models with sensitivity down to
0.12 lux in color and 0.03 lux in black and white (B-W).
8. A removable IR cut filter mechanism for increased sensitivity in low-light installations.
The sensitivity of IR cut filter removal shall be configurable through a Web browser.
9. Or support two simultaneous, configurable video streams. H.264 and MJPEG
compression formats shall be available for primary and secondary streams with
selectable unicast and multicast protocols. The streams shall be configurable in a
variety of frame rates and bit rates.
10. Industry standard Power over Ethernet (PoE)
11. Or be IEEE 802.3af compliant, suppling power to all Network cameras. Network
cameras shall also offer a 24 VAC power input for optional use.
12. A standard Web browser interface for remote administration and configuration of
camera parameters.
13. A window blanking feature to conceal user-defined privacy areas which cannot be
viewed by an operator. The network camera shall support up to four blanked windows.
A blanked area shall appear on the screen as a solid gray window.
14. Or support standard IT protocols.
15. Or support open architecture best practices with a published API available to third-party
network video recording and management systems.
16. Or be configured for exterior use.
17. Or use category CAT6A cable as the primary source for carrying signals up to 100 m
(300 ft.) from a switch hub or network server. If any camera is installed greater than 100
m (300 ft.) from the controlling device, then the following will be required:
a. A local or remote 12 VDC or 24 VAC power-source from a Class 2, UL compliant
power supply.
b. A signal convert to convert from a CAT6A cable over to a fiber optic or standard
signal cable. The signal will need to be converted back to a CAT6A cable at the
controlling device using a signal converter card.
18. Or be routed to a controlling device via a network switch.
19. A programmable IP address that allows for installation of multiple units in the same
Local Area Network (LAN) environment.
20. The capability to incorporate a minimum of Transmission Control Protocol (TCP)/IP,
User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), File Transfer
Protocol (FTP), Internet Control Message Protocol (ICMP0, Address Resolution
Protocol (ARP), Real-Time Transport Protocol (RTP), Dynamic Host Configuration
Protocol (DHCP), Network Time Protocol (NTP), Simple Mail Transfer Protocol
(SMTP), Internet Group Management Protocol (IGMP), and Differentiated Service
Code Point (DSCP) protocols for various network applications.
High Definition Integrated Digital Network Camera Technical Specifications
Imaging Device
1/3-inch, effective
Imager Type
CCD/CMOS, Progressive scan
Maximum Resolution
2048 x 1536 (4K)
Signal-to-Noise Ratio
50 dB
Auto Iris Lens Type
DC drive
Electronic Shutter Range
1~1/100,000 sec
Wide Dynamic Range
60 dB
White Balance Range
2,000° to 10,000°K
Sensitivity
f/1.2; 2,850K; SNR >24dB Color (1x/33ms) 0.50 lux Color SENS (15x/500 ms) 0.12 lux
Mono SENS (15x/500 ms) Mono (1x/33ms)0.25 lux 0.03 lux
Dome Attenuation
Clear Zero light loss
Smoke f/1.0 light loss
Compression
H.264 in base profile and MJPEG
Video Streams
Up to 2 simultaneous streams, the second Stream variable based on the setup of the primary stream
Frame Rate
Up to 30, 25, 24, 15, 12.5, 12, 10, 8, 7.5, 6.5, 4, 3, 2, and 1 (depending upon coding, resolution, and stream configuration
Available Resolutions
8.3 MPx3840 x 2160; 16:9 aspect ratio; 15.0 ips max., 10.0 Mbps bit rate for MJPEG; 5.0 ips max., 3 Mbps bit rate H.264
5.0 MPx2688 x 1520; 4:3 aspect ratio; 15.0 ips max., 10.0 Mbps bit rate for MJPEG; 5.0 ips max., 5 Mbps bit rate H.264
3.1 MPx2048 x 1536; 4:3 aspect ratio; 2.0 ips max., 10.0 Mbps bit rate for MJPEG; 3.0 ips max., 2.6 Mbps bit rate H.264
2.1 MPx1920 x 1080; 16:9 aspect ratio: 15.0 ips max.,10.0 Mbps bit rate for MJPEG; 5.0 ips max., 2.7 Mbps bit rate H.264
1.9 MPx1600 x 1200; 4:3 aspect ratio; 15.0 ips max.,10.0 Mbps bit rate for MJPEG; 6.0 ips max., 2.6 Mbps bit rate H.264
1.3 MPx1280 x 1024; 5:4 aspect ratio; 15.0 ips max.,10.0 Mbps bit rate for MJPEG; 8.0 ips max., 2.5 Mbps bit rate H.264
1.2 MPx1280 x 960; 4:3 aspect ratio; 15.0 ips max., 9.8 Mbps bit rate for MJPEG; 9.8 ips max., 8.5 Mbps bit rate H.264
0.9 MPx1280 x 720; 16:9 aspect ratio; 30.0 ips max.,10.0 Mbps bit rate for MJPEG; 12.5 ips max., 2.5 Mbps bit rate H.264
0.5 MPx800 x 600; 4:3 aspect ratio; 30.0 ips max., 5.8 Mbps bit rate for MJPEG; 25.0 ips max., 2.0 Mbps bit rate H.264
0.3 MPx640 x 480; 4:3 aspect ratio; 30.0 ips max., 3.7 Mbps bit rate for MJPEG; 30.0 ips max.,1.6 Mbps bit rate H.264
0.1 MPx320 x 240; 4:3 aspect ratio; 30.0 ips max., 0.9 Mbps bit rate for MJPEG; 30.0 ips max., 0.4 Mbps bit rate H.264
Additional 640 x 512, 640 x 352, 480 x 368, 480 x 272, 320 x 256, 320 x 176
Supported Protocols
TCP/IP, UDP/IP (Unicast, Multicast IGMP), UPnP, DNS, DHCP, RTP, RTSP, NTP,IPv4, SNMP, QoS, HTTP, HTTPS, LDAP(client), SSH, SSL, STMP, FTP, MDNS(Bonjour), and 802.1x (EAP)
Security Access
Password protected
Software Interface
Web browser view and setup, up to 16 cameras
Connectors
RJ-45 for 100Base-TX, Auto MDI/MDI-X
Cable
Cat6A cable or better for 100Base-TX
Input Voltage
24 VAC or PoE (IEEE802.3af class 3)
Power Consumption
6 W
Current Consumption
PoE
36C25821Q0028 Department of Veterans Affairs Veterans Health Administration Veterans Integrated Service Network 22
4/30/21, 6:45 PM