SOURCES SOUGHT
D -- Physical Security Information Management System
- Notice Date
- 6/14/2013
- Notice Type
- Sources Sought
- NAICS
- 511210
— Software Publishers
- Contracting Office
- United States Capitol Police, Office of Procurement, Procurement Section, 499 South Capitol Street SW, Washington, District of Columbia, 20003, United States
- ZIP Code
- 20003
- Solicitation Number
- RFI-13-0001
- Archive Date
- 7/27/2013
- Point of Contact
- Gail P DelRose, Phone: 2025933541, Angela.B. Chew, Phone: 202-593-3544
- E-Mail Address
-
gail.delrose@uscp.gov, angela.chew@uscp.gov
(gail.delrose@uscp.gov, angela.chew@uscp.gov)
- Small Business Set-Aside
- N/A
- Description
- The United States Capitol Police (USCP), Security Services Bureau (SSB), Physical Security Division (PSD) is seeking a Physical Security Information Management (PSIM) System. The USCP intends to purchase a product and implement the system in FY14. The specific schedule, deliverables and roles and responsibilities between the USCP and the vendor during implementation are yet to be determined. At a high level, the USCP has the following goals: • The system will provide a platform to integrate and manage our disparate physical security systems with one common interface. • This system should enable additional automation of security actions. • This system will support improved situation awareness and allow the USCP to more efficiently and more proactively report security issues. • Commercially available products that require minimal development to meet all of the requirements are preferred. • Platforms that have been deployed in a large scale production environment are preferred. Vendors are encouraged to provide a "best practice" solution for the implementation of their solution. Core Elements Desired in PSIM 1. Hardware Requirements 1.1. Hardware neutral solution for major components such as servers 1.2. Hardware shall be commercially available with no customized components 1.3. Shall support redundant and/or clustered hardware to enable server failover capability 2. Network Requirements 2.1. Supports SNMPv2 and SNMPv3 for network management 2.2. Integrates into Active Directory 2.3. System will be able to dynamically push alarm queue information using UDP or other connectionless protocol to a specified IP address or Active Directory FQN 2.4. Supports multicast connections 3. General Operational Requirements 3.1. Modular features (alarm, video, voice, etc) that allows users access to only designated modules 3.2. Modules are configured by personnel with administrator level access 3.3. Addition of "modules" or activity within modules will not obscure other modules 3.4. Additional systems can be added without the need to take down or reconfigure the rest of the system 3.5. USCP and manufacturer will have a direct relationship without intermediate contractors 4. Client Side Reporting 4.1. Reporting tools will be made available from the user interface that will allow users to create reports on information that is available to them 4.2. Provides a contact directory (first name, last name, work phone, cell phone, home phone, office name, office address)(link to CCure dbo.Person) 4.3. Search features for persons, access permissions, alarm activation events, logged messages 4.4. Data information change requests with validation notices for contacts and alarm information 5. Management Requirements 5.1. Extensive logging features that report to a central management interface 5.2. All logs, alarm events, user actions will be logged to a management database using SQL 5.3. Web based or centralized management interface 5.4. Access to logging, programming, administrative features is permissions based (ADS) 5.5. Access to monitoring features is permissions based 5.6. Permissions have a hierarchical structure 5.7. Permissions in the PSIM do not supercede permissions in integrated systems 6. Software Requirements 6.1..Net based solutions preferred 6.2. Software runs on Windows Server 2008R2 and/or Windows 7 Professional or higher 6.3. Software development kit provided 6.4. Microsoft SQL Server 2008 R2 or 2012 for relational database 7. Integration Requirements 7.1. Two concurrent instances of CCure 800/8000 7.2. Two concurrent instances of CCure 9000 7.3. Genetec Omnicast 4.8 and later 7.4. Genetec Security Center 5.0 and later 7.5. Zenitel IP based intercom solutions 7.6. SIP VOIP protocol based devices 7.7. Cisco Communicator 7.8. User interface for like systems does not change solely based on a change of integrated system (i.e. the VMS UI looks the same for all VMS systems) 8. Alarm Monitoring 8.1. Alarms are linked to corresponding icons in the mapping function (see below) 8.2. Consolidates all alarms from integrated systems to a central alarm queue 8.3. Dual phase acknowledgement (alarm acknowledgement initially, than acknowledgement on resolution) 8.4. Two way acknowledgement (i.e. acknowledgement in PSIM = acknowledgement in CCure and vice versa) 8.5. Acknowledgement in any phase requires operator comments 8.6. System status monitoring for integrated platforms 8.7. Received alarms can call up linked cameras 8.8. Camera call up allow access to live and archived video 8.9. Provides automated actions based of receipt of certain alarms (e-mail, etc) 8.10. Alarms display response instructions, notification lists, special procedures and/or notices (i.e. "asbestos in room") 8.11. Alarms can be assigned a priority that is visually distinguished from higher/lower priority alarms, with flags (popup window or other feature) for critical items 8.12. Priorities assigned by subordinate systems are respected 9. Voice Over IP (VOIP) 9.1. Can answer and make calls from VOIP based intercom and phone systems 9.2. Calls received log in the alarm queue 9.3. Calls may be answered via the alarm queue 9.4. Calls may be prioritized 10. Mapping 10.1. Hierarchical mapping for alarms and cameras (campus > building > floor >specialized areas) 10.2. Zoom features to allow users to zoom in on site and building floor plans 10.3. Alarms, intercom, and cameras represented by icons displayed on site and building floor plans 10.4. Clicking on icons representing active alarms opens dialog for that alarm 10.5. Alarm icons change colors/shape/etc to represent current alarm status (secured, alarmed state, access mode, etc) 10.6. A single icon may represent multiple alarm events, each capable of activating independently with independent acknowledgement 10.7. Hovering/right-click or similar action on camera or alarm icon will bring up additional details such as response instructions, location description, point of contact for that alarm, etc 10.8. Point of contact links to contact information listed above 10.9. System must accept drawings in AutoCAD 2004 or later or vendor will provide a utility to convert drawings 10.10. System must accept image formats to include Raster, Vector, and 3D Vector formats or the vendor will provide a utility to convert these file types 10.11. Floor plans can be tagged with items of interest (construction, maintenance activity, etc) 11. Performance 11.1. Alarms populate in the alarm queue no more than 500ms after it populates in a CCure monitoring client installed on the same machine 11.2. Alarm status update in the CCure server database not more than 1000ms after acknowledgement 11.3. Alarm logging functions must not lock the database so that to prevent other rows from updating 11.4. PSIM operation must not interfere with normal operation of integrated systems 11.5. Integrated systems must be able to operate concurrent with the PSIM or independently in the event of PSIM failure 11.6. Monitors health/status of integrated systems 11.7. System architecture must be structured and optimized for both application and network infrastructure performance, data transfers must not impede existing system performance 12. Training 12.1. Operator training for approximately 70 users will be provided 12.2. Administrator training for approximately 15 administrators and engineers will be provided 12.3. SDK training will be provided for two 13. Secure programming techniques 13.1. Software was developed using one or more secure coding standards (i.e. CERT Secure Coding Standard or comparable) 14. Optional but Desirable Features 14.1. Operators can push floor plans to designated locations 14.2. Integration with existing maintenance management system using SQL and.Net Submission Requirements Responding vendors should provide all responses to this RFI in the form of a matrix which includes: • An individual listing of each requirement; • The vendor's compliance with each requirement; and, • A supporting explanation or a reference to documentation that can be attached to as an addendum. Respondents should also provide a separate document which includes: • A description of their architecture; • Their willingness to provide a live demonstration: • Local references and whether they would allow the USCP visit and view their system; • Their willingness to provide a demo license (minimum 90 days) for review and testing by the USCP; and, • Potential pricing information. Timing of Submissions Vendors have thirty (30) days from the date this RFI is posted to provide a written response with all necessary documentation. Disclaimer This RFI is issued as a means of technical discovery and information gathering. This RFI is for planning purposes only and should not be construed as a solicitation nor should it be construed as an obligation on the part of the USCP to make any purchases. This RFI should not be construed as a means to pre-qualify vendors. The USCP may utilize the results of this RFI in drafting a competitive solicitation (RFP) for the subject services/products/equipment. Any future contract that may be awarded must comply with USCP's procurement requirements. Participation in this RFI is voluntary and the USCP will not pay for the preparation of any information submitted by a respondent or for the USCP's use of that information.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/USCP/OFM_USCP/PS/RFI-13-0001/listing.html)
- Place of Performance
- Address: 499 South Capitol St. SW, washington, District of Columbia, 20003, United States
- Zip Code: 20003
- Zip Code: 20003
- Record
- SN03089996-W 20130616/130614234650-a07a02e0315903071bfa680eae66407f (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 |