TACOMA POWER REQUEST FOR INFORMATION PHYSICAL ACCESS CONTROL SYSTEM FOR TACOMA PUBLIC UTILITIES FACILITIES PG F

Transcription

1 TACOMA POWER REQUEST FOR INFORMATION PHYSICAL ACCESS CONTROL SYSTEM FOR TACOMA PUBLIC UTILITIES FACILITIES PG F

2

3 City of Tacoma Physical Access Control System for Tacoma Public Utilities Facilities Specification No. PG F Request for Information (RFI) Contents 1.0 INTRODUCTION INFORMATION REQUESTED RFI RESPONSE FORMAT PROJECT CONTACT RFI PROCESS COST OF PREPARATION PROPRIETARY OR CONFIDENTIAL DESIGN INFORMATION... 3 APPENDIX A Introduction The City of Tacoma, Tacoma Public Utilities, Light Division (dba Tacoma Power) requests information on Physical Access Control Systems (PACS) features and functions relative to meeting Tacoma Power s needs to control and monitor physical access into its facilities, and to meet documentation requirements mandated by all laws, regulations, and standards that apply to electrical utilities. The information submitted will be used to standardize PACS systems for Tacoma Power. Tacoma Power has an existing, 267-door PACS that controls and monitors access into many Tacoma-area facilities. The current PACS functionality is limited to card access control, point monitoring, and photo-id badging with PACS clients located variously according to function. Connections between Communications Server and controllers is via TCP/IP over a closed, secure LAN. Any new PACS system selected must have the capacity to replace the existing system and expand to accommodate future system needs that will likely extend to all Tacoma Power properties and which may eventually number between 800 and 1000 doors. In addition, the system may eventually be expanded to Tacoma Water, Tacoma Rail, and Click properties. PACS system installations may be required at the following locations: A. Tacoma Public Utilities Administrative Complex B. Cowlitz Hydroelectric Project in Lewis County C. Cushman Hydroelectric Project in Mason County D. Nisqually Hydroelectric Project in Pierce and Thurston Counties E. Wynoochee Hydroelectric Project in Grays Harbor County F. Tacoma Water Headworks in King County G. Other Tacoma Power, Tacoma Water, Tacoma Rail, or Click! properties within Tacoma Public Utilities service areas. Responses and any subsequent demonstration(s) as a result of this RFI may directly influence product standardization. Note, however, that there will be no awards made as a result of this Physical Access Control System

4 RFI. Once product standardization is complete, Tacoma Power will engage suppliers by either issuance of a separate RFP or by a cooperative interagency agreement, if available. 2.0 Information Requested The questions in Appendix A request information about your system relative to the functions, features, and technical capabilities desired by the City of Tacoma. All responding firms must answer the listed questions to the best of their ability. Firms should not modify the questions in any manner. The control system vendor shall follow these general guidelines when responding to the RFI questions: A. Provide numbered answers to the numbered questions in Appendix A. B. Where feasible, keep the explanations brief. Feel free to include appropriate attachments. C. Use of graphical tools (charts, sketches, drawings) is encouraged if applicable. D. Be technical where this would be helpful to support the response. 3.0 RFI Response Format RFI responses should be provided with a cover letter. Clearly indicate in the subject line Request for Information for PG F: Physical Access Control System (PACS) for Tacoma Public Utilities Facilities. The cover letter should clearly list the submitting company s name, address, contact name, title, address, phone number, and fax number. The cover letter should also clearly indicate, by name, the PACS system being presented/proposed. Attachments to the cover letter should include: A. Responses to Appendix A questions. B. Product Literature including technical specifications of significant hardware components (e.g. door controllers) and software including any add-on feature sets. Please do not include literature on generic components such as card readers except as may be unique to the system. C. At least five (5) end user product references of the submitted PACS system including customer contact information for verification. Of particular interest to Tacoma Power are references from existing system installations for electrical utilities. D. Any other additional information relevant to the RFI. Tacoma Power anticipates that most responses to this RFI will be made by installing dealers of PACS manufacturers, while others might be made directly by PACS manufacturers. It is also understood that some PACS manufacturers have more than one dealer in the Seattle-Tacoma area and so there may be duplicate responses/presentations of some PACS manufacturer s PACS products. 4.0 Project Contact Any questions regarding this RFI should be directed to John Glover, Security Engineer, at or by to jglover@cityoftacoma.org. 5.0 RFI Process Interested vendors must return their RFI response by 11:00 a.m., Tuesday, August 5, 2014 to: Physical Access Control System 2

5 City of Tacoma Public Utilities Purchasing Division 3628 South 35th Street Tacoma, Washington Attn: Joe Parris, Senior Buyer The City intends to complete its reviews of vendor RFI responses by Thursday, August 21, Vendor(s) may be invited to demonstrate their system onsite at Tacoma Public Utilities Administrative Complex in Tacoma, WA. In late August, Tacoma Power will deliver a demonstration agenda to the selected vendor(s). The agenda will detail specific functions and features the City wishes to see during vendor demonstrations (which may be up to 3 hours in length). Any demonstrations will be held in early to mid-september. Firms that are not invited to demonstrate their systems are still encouraged to submit proposals in response to any RFP for PACS System Materials & Installation that may be released at a future date. Failure to be selected as a finalist as a result of this RFI will not eliminate your firm from submitting a proposal in response to any RFP for PACS System Materials & Installation that may be released at a future date. 6.0 Cost of Preparation Proposers are solely responsible for all costs incurred in the development, submission and demonstrations as a result of the RFI. All materials submitted in response to this RFI, except for noted proprietary materials, shall become the property of the City. 7.0 Proprietary or Confidential Design Information Washington State Public Disclosure Act (RCW et seq.) requires public agencies in Washington to promptly make public records available for inspection and copying unless they fall within the specified exemptions contained in the Act, or are otherwise privileged. Documents submitted under this RFI shall be considered public records and, with limited exceptions, will be made available for inspection and copying by the public. If the Vendor considers any submittal document to be protected from disclosure under the law, they shall clearly identify on the page(s) affected such words as CONFIDENTIAL, PROPRIETARY or BUSINESS SECRET. The Vendor shall also submit an index with its information identifying the affected page number(s) and location(s) of all such identified material. Marking the entire Informational packet as confidential or proprietary is not acceptable and is grounds to reject such information. If a request is made for disclosure of such identified documents or portions thereof, the City will determine whether the material is exempt from public disclosure. If, in the City s opinion, the material is subject to disclosure, the City will notify the Vendor of the request and impending release and allow the Vendor ten (10) days to take whatever action it deems necessary to protect its interests. The City will cooperate with any legal action initiated by the Vendor to prevent release; provided that all expense of such action shall be borne solely by the Vendor, including any damages, attorney s fees or costs awarded by reason of having opposed disclosure and Vendor shall indemnify City against same. If the Vendor fails or neglects to take such action within said period, the City will release all materials deemed subject to disclosure. Submission of materials in response to this RFI shall constitute assent by the Vendor to the foregoing procedure and the Vendor shall have no claim against the City on account of actions taken pursuant to such procedure. Physical Access Control System 3

6 APPENDIX A Sales Process / Sales Charges 1. Does the PACS system manufacturer apply any per-element charges at initial sale and/or as the end-user's system grows? For example 'per user' charges, 'per cardholder' charges, 'per door' charges, 'per workstation' charges, or any other similar charges. 2. List all software modules' that should be considered separately - for example Photo-ID, Guard Tour, Time and Attendance, etc. Clarify which are included in the base software cost and which are available for an additional charge. 3. Does PACS system manufacturer apply any annual or other periodic charges based on system configuration? Provide full disclosure of licensing structure and framework, i.e. per installation, per door, per workstation, per photo-id, etc. Dealer & End User Support 4. Does PACS system manufacturer provide direct technician training to end user technicians and system administrators? Provide a list of all training courses available related to the proposed PACS including course title, outline, duration, student prequalification s, and training locations. 5. Does PACS system manufacturer provide Factory-to-End-User Telephone Technical Support to Technicians and Administrators? What are the hours of technical support? PACS System Security & Resilience 6. Is fail-over clustering supported to provide database availability in all circumstances? 7. Does your system support Hot Failover Communications Server functions? 8. Is Active Directory Integration available for Single Sign-on? 9. Describe Administrator/Operator access and privilege control features. 10. Describe Communications Encryption Options. Is communications encrypted from Communications Server to Workstations and Controllers? Is controller to controller communications encrypted? 11. Can Door Controllers be assigned any valid IP Address and TCP/UDP Port? Or is a certain range specified. 12. Describe the system fault detection, integrity checking, and fault tolerance. Does a failure of any single component of the PACS adversely affect the operations of any other component? 13. Describe Computer requirements for servers, workstations, and any other computers. Include hardware requirements, database software, and operating systems. 14. Describe how Door Control Panels attach to the security network. 15. Do the door controllers feature non-volatile controller memory will the controller will be operational upon power up with no need for download. Appendix A

7 16. Describe the communication links and protocols used to connect the Communications Server to Door Control Panels and from Door Control Panels to other Door control panels. Is communications encrypted / are there any encryption options? 17. Can/do certain Door Control Panels operate as 'supervisory panels', disseminating/downloading database changes to 'sub panels' and administrating linking operations? Or are all panels within an installation location peers in relation to the communications server. 18. Do/can system servers perform any daily testing? Do key components such as door control panels perform any automatic and/or daily testing operations? 19. Are door controllers labelled with serial numbers and manufacturing dates. Can these numbers be accessed via the PACS software? Is commissioning date available from the software? 20. Describe the PACS data historian search (query) tools and reporting capabilities. Does the system provide a full-featured report writer that is easily user configured and able to product reports for internal operations? Can report configurations be saved for future use? 21. Describe your software development, testing, and security verification procedures. 22. Describe how the system addresses CIP compliance. Warranty, Updates, and Upgrades 23. Describe your standard warranty provision and what extended warranty options are available. 24. Provide a description of your overall strategy for system hardware and software upgrades. 25. How are software updates handled? Is there a software maintenance plan? Or is all software updates provided at no charge? Or just significant updates (excepting bug fixes). How are bug fixes differentiated from significant updates? 26. How are software and firmware releases documented and communicated. Is this information automatically sent to dealers immediately after changes? Is it sent also to system owners - or can system owners be placed on the circulation list upon they request? Is an up to date Software and Firmware Release/Control Document available online at all Times? Manufacturing / Component Sourcing 27. Does your system have its own Ethernet interface, or does it rely on third party components such as Lantronix network appliances? 28. Provide a list of any proprietary or custom (i.e. not "off-the-shelf) hardware, software, and communications components of your system. 29. Are controllers designed to operate with multiple communications interfaces? For example LAN/WAN connect with modem back-up. 30. Which suppliers, if any, do you depend upon for major system components? How does this affect your long-term ability to support your system? Appendix A

8 31. Where is proprietary PACS Hardware - door controllers and other important components - made? In the USA, offshore at a single manufacturer, or at multiple locations. How long have controllers been made by the current manufacturers. Reliability 32. Are all controllers 'burned in' / tested. Or just a sampling. 33. What is mean time between failure for Door Control Panels? 34. Describe your manufacturing factory testing and quality control procedures and any published MTBF and MTTF are determined. Equipment Supply & Installation Sources 35. Is proposed PACS system available through at least three dealers in the Seattle-Tacoma area? If so please list at least three dealers. Software Operation Options & Features 36. What video integration options are available? Does proposed system integrate with Pelco Digital Sentry via software API? 37. Does the system provide integrated photo-id? 38. Does the system support HID Corporate 1000 Format Cards 39. Does the system support anti-pass back? Will it support multiple zones? 40. Does the system support Guard Tour 41. Does the System Support Integrated Mapping with Customizable Icons? 42. Ability to Import Cardholder Data including and Photos from Existing PACS (SQL Database) 43. Does the system support global lockdown from software or Input/Switch. 44. Does the system support flexible linking to and from card reads, inputs, and outputs? Describe the variety of linking options/capabilities. 45. How many Access Levels are available per user? Are temporary access levels available? 46. Can the system be configured for Auto-Unlock with 1st man in 47. Is Use It or Lose It available as a feature. 48. How many cardholder custom fields are available? 49. Can specific doors / readers be disabled by time zone? 50. Does the system reporting capability provide integral reporting of all cardholder & system events and operator actions? 51. Is the system configured to provide local alarms at doors with an output designated for this purpose? 52. Is door relay operation selectable - fail safe versus fail secure - in the software? 53. Does the PACS provide automatic documentation of the hardware configuration Appendix A

9 54. Does the PACS Software provide a standard door control template or templates to facilitate programming? Or does the system allow for creation of new door as a copy of an old door. 55. Provide a complete list of system features. Highlight any unique features. Manufacturer 56. Describe the product management and development team, years of service, etc. 57. Describe the company's history, ownership changes, ownership structure, etc. 58. Provide references of electrical utility customers and description of systems installed. Include contact name, , address and telephone number. Appendix A