Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF DECEMBER 24, 2006 FBO #1854
SPECIAL NOTICE

D -- Request for Information Digital Video Recording System

Notice Date
12/22/2006
 
Notice Type
Special Notice
 
NAICS
519190 — All Other Information Services
 
Contracting Office
Department of the Treasury, Bureau of Engraving and Printing (BEP), Office of Acquisition, 14th & C Streets, S.W., Washington, DC, 20228, UNITED STATES
 
ZIP Code
00000
 
Solicitation Number
RFI-07-0001
 
Response Due
2/1/2007
 
Description
DESCRIPTION: The Bureau of Engraving and Printing is seeking information from industry that will assist in the replacement of its Digital Video Recording System (DVRS) at its Washington and Ft Worth facilities. REQUIREMENTS: DVRS PERFORMANCE AND FUNCTIONAL REQUIREMENTS DVRS PERFORMANCE REQUIREMENTS ? The performance requirements for the digital video recording systems are as follows: The Digital Video Recording System (DVRS) encompasses recording video, viewing video, reviewing recorded video, and storing video for indefinite periods of time. All system components must be able to be linked together via a dedicated computer network. The DVRS shall feature multiple camera operation with the ability to individually configure each camera?s setting for recorded resolution/fps. The DVRS shall simultaneously record, display live video, play back video, and send recorded video to tape. None of the video operations shall interfere with each other. Recording shall not stop for playback, live video view, or video storage. The system shall provide for capturing, digitizing, and storing video. Digitize recorders shall be able to record full-time, at 4CIF 30 frames per second, to record in response to an alarm, or to record based on a user-programmable schedule. Full-time recording refers to 24 hours per day, 7 days per week, and 365 days per year at 4CIF at 30 frames per second. The DVRS shall be capable of long-term video storage. Live view and video playback shall not interrupt the recording process. A reporting utility shall provide tracking of alarms, incidents, operator logs and service requests. The DVRS shall be capable of attaching/inserting text, photo/image and video to a generic report application. Video authentication shall provide confidence in the integrity of the video to demonstrate that the video has not been altered. The DVRS shall provide a utility for enhancing single frames of video. A single frame shall be a copy of the recorded video frames. Any enhancement to the frame shall not alter the original recorded video The DVRS shall also capture, digitize, and store video. The DVRS shall be capable of processing a video signal from the following: fixed, PTZ, infrared, thermal cameras, low light, black and white, color cameras. The DVRS shall be capable of interfacing to x-ray machines via VGA to Component Video converter to digitally record items scanned. Video shall be stored on the DVRS internal hard drive. As the hard drive becomes full the oldest video shall be archived to make room for new video. The DVRS shall time and date stamp all recorded video. The DVRS shall be capable of interfacing to existing security system via a GPS time synchronization device. The video source, capture date, start time, and stop time shall be stored for each alarm event. The event that caused the alarm shall be identified as originating from either an alarm point or a camera. The DVRS shall support live video sent over the network to a workstation for review by an operator. The DVRS shall feature continuous DVRS recording of camera inputs without operator intervention. The DVRS shall allow event driven recordings. The DVRS shall record camera inputs when an alarm condition is present at other than normal resolution/fps settings. Recording in response to an alarm shall be user programmable. The DVRS shall allow for scheduled recording of camera inputs, at other than normal resolutions/fps settings, during specific hours of the day. The DVRS shall remain idle during nonscheduled times, or return to normal operations as determined by the user. The DVRS shall have the capability to allow an operator to set-up recording schedules through the Graphical User Interface (GUI). Schedules shall be specified for days of the week, weekends only, or daily. Start and stop times shall be part of the schedule. The DVRS shall be configured to interface to a variety of CCTV matrix switchers to control PTZ and monitor functions The DVRS shall provide for on-demand recording. This will allow the DVRS to record camera and/or monitor inputs at the request of an operator, and does not require a schedule or alarm condition for recording to start. DVRS FUNCTIONAL REQUIREMENTS ? The functional requirements for the digital video recording systems are as follows: The DVRS shall support storage of video at various frame rates and resolutions up to and including 4 CIF 30 FPS. The system shall record in a digital format. The DVRS shall be capable of providing simultaneous 1 frame per second, 2 frames per second, or 3 frames per second digital recording by operator request. (Frame by frame review.) The DVRS shall support selectable frame rates and resolutions, as required, for alarm recording. The DVRS shall capture, digitize, compress video, and provide export features to a computer hard drive, floppy disk, CD, and/or DVDRW or other external storage media. The DVRS shall have video authentication capability to verify the authenticity and integrity of the video. The DVRS shall have password protection for various levels of access and control. The DVRS archiving section shall accommodate 30 days of on-line storage for automatic retrieval. The DVRS shall be capable of providing near on line archive and retrieval of identified CCTV video for a minimum of one year. The DVRS shall be of modular construction so that the BEP can add or delete additional equipment/components. The manufacturer/vendor shall provide and maintain through the life cycle of the equipment, a proven hardware, software and firmware customer support infrastructure to include help desk and on-site assistance when necessary. The DVRS shall have the ability to interface with a variety of CCTV switchers to control PTZ and monitor functions. The DVRS shall have internal video motion detection capabilities. The DVRS shall provide for digital recording of a minimum of 1500 camera inputs at 4CIF, 30 FPS each. The DVRS shall be capable of handling up to a minimum of 30 workstations. The DVRS shall digitally store images automatically (short and long-term storage). The DVRS must process and record video from any type of camera operating on the EIA video signal standard (including color, black/white, low light) and record video inputs without operator intervention. The DVRS shall store digital images on a hard drive, or alternative storage media for immediate retrieval. The DVRS shall have an ?on-demand? recording capability. The DVRS shall allow authorized users to search and locate video scenes from any workstation. The DVRS shall employ continuous image storing. The DVRS shall be capable of printing images, in color where applicable. The DVRS shall be capable of enhancing images, without altering the original stored image. The DVRS shall record the captured date and time (start and stop), display the time, date, and source of the video during playback. The DVRS shall be capable of attaching stored images and video to reports. The DVRS shall be computer based and operate on a high-speed local area network (LAN) of 100Mb or higher. The DVRS shall operate on Windows XP Client/Server 2003, or specify the required operating system for proper utilization. The DVRS shall record pre-alarm, alarm, and post alarm conditions. The DVRS shall store the displayed camera number and name with the images. The DVRS shall simultaneously record; display live video, archive, and play back stored video. The DVRS shall support a graphical User Interface (GUI) for operator interface. The DVRS shall provide for a multiple camera display on a single monitor. The DVRS shall support recording capability at a user programmable frame rates and resolutions based on a user-defined schedule or operator request. The DVRS shall contain a utility that provides tracking of various functions including alarms, incidents, operator logs, and service requests. The DVRS shall support automatic switchover to another recorder in the event of a recorder failure. The DVRS shall be capable of feeding live video over its network to all workstations at various frame rates up to and including 30 fps. The DVRS shall support database connection for use in tagging video to data events. The DVRS shall support NTSC/PAL signal format with a programmable resolution from CIF format (352 x 240 pixels for NTSC; 352 x 288 pixels for PAL) to 4CIF (704 x 480 pixels for NTSC; 704 x 576 pixels for PAL) for each individual camera. Proposed information shall include approximate overall square footage/foot print of all necessary equipment. Responders shall specify the digital format used for recording. The DVRS shall support both analog and IP camera input. ASSUMPTIONS: Not Applicable PURPOSE: The purpose of this RFI is to gather information about those requirements enumerated above. The Government is open to alternative concepts for solutions that meet these requirements. This RFI seeks information about a fully dedicated federated solution as well as other approaches that could meet the functional requirements with additional levels of sharing of personnel, equipment, and connectivity paths. In doing so, the Government seeks to understand the tradeoffs among risks, costs (initial and ongoing) and alternative technical architectures that incorporate increasing degrees of sharing. Accordingly, respondents are encouraged to provide information about any alternatives that can be demonstrated. Following is a suggested outline and suggested page counts for a response to this RFI. This outline is intended to minimize the effort of the respondent and structure the responses for ease of analysis by the government. Nevertheless, respondents are free to develop their response as they see fit. Conceptual Alternatives: Briefly describe two or more concepts. Cost and Schedule Estimates: Provide cost estimates for each alternative Also, discuss cost drivers, cost tradeoffs, and schedule considerations Corporate Expertise: Briefly describe your company, your products and services, history, ownership, financial information, and other information you deem relevant. In particular, please describe any projects you have been involved in that are similar in concept to what is described in this RFI, including management and operations approach, security requirements, security assurance processes, and any relevant lessons learned. Include any comments on the structure of the requirements for a formal RFP response. Additional Materials: Please provide any other materials, suggestions, and discussion you deem appropriate. INFORMATION EXCHANGE MEETINGS Due to the time constraints, questions on further details will be handled through the government POC. In addition, BEP may consider meeting individually with respondents. DISCLAIMER This RFI is issued solely for information and planning purposes only and does not constitute a solicitation. All information received in response to this RFI that is marked Proprietary will be handled accordingly. Responses to the RFI will not be returned. In accordance with FAR 15.202(e), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Responders are solely responsible for all expenses associated with responding to this RFI. CONTACT INFORMATION Following is the Point of Contact (POC) for this RFI: Merwin Charles. Please submit responses via e-mail by 4:00 PM no later than February 1,2007, to the POC. You may also submit supplemental hardcopy materials such as brochures, etc. (5 copies each) to the POC.
 
Place of Performance
Address: 14th & C stereets SW, Washington, DC
Zip Code: 20250
Country: UNITED STATES
 
Record
SN01202170-W 20061224/061222221033 (fbodaily.com)
 
Source
FedBizOpps Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.