REQUEST FOR PROPOSAL PROCEDURES

GEORGIA PORTS AUTHORITY Request for Proposal To Provide Various Security Systems Using DHS Port Security Grant Funding TABLE OF CONTENTS PROJECT OVERVIEW Executive Summary Port Operations (Background) Project Approach Bidder/Contractor Qualifications Terminology and Abbreviations Contacts RFP Timetable Vision Design Concerns LINC Partnership PORT SECURITY REQUIREMENTS DOCUMENT General Requirements Security Camera Networks Access Control System Requirements Low Light / High Vegetation Detection and Response SRIN and CIIN Add-ons Command and Control System Equipment Mounting Locations Post Installation Testing and Commissioning Maintenance Plan Logistic Supportability Research and Development / Future Capabilities SAVANNAH RIVER INTRUSION NETWORK System Description Budget COLONEL’S ISLAND INTRUSION NETWORK System Description Budget TWIC ACCESS SYSTEM INTEGRATION System Description Budget BID OPTIONS AND ALTERNATIVES Option 1: Access Control System Option 2: Lowlight/Thermal Detection and Response Option 3: Command and Control System Option 4: Remaining SRIN Components Including Radar, Cameras and other Equipment Option 5: Remaining CIIN Components Including Radar, Cameras and other Equipment Option 6: Connect Existing Cameras/Systems to New Systems Proposed Option 7: Unsolicited REQUEST FOR PROPOSAL PROCEDURES Release of Request For Proposal Notice of Intent to Propose Pre-proposal Conference Contact for Inquiries Last Date to Submit Written Questions Proposal Due Date, Time, and Location Bid Bond Bid Opening Contract Award Base Bid, Options, and Marginal Costs Proposal Format and Submission Requirements Technical Proposal Content Proposal Evaluation Final Offers GENERAL TERMS AND CONDITIONS Specifications Deviations and Exceptions Quality Quantities Delivery Pricing and Discount Acceptance-Rejection Method of Award Ordering Payment and Invoicing Guaranteed Delivery Default Fair Trade Pricing Excise, Transportation and Sales Taxes Sample Items Delivery to GPA Minority Business Enterprises Income Tax Incentives Entire Agreement Applicable law and Compliance Federal Regulations Antitrust Assignment Assignment Nondiscrimination/Affirmative Action Patent Infringement Equipment Safety Safety on Site Reporting of Accidents, Injuries or Damages GPA Credentialing TWIC Denial of Reimbursement Gratuity Prohibition Right of Rejection of Lowest Cost bid Rights to Submitted Material HAZ-MAT Material Safety Data Sheet Immigration Drug-Free Warranty Changes and Alterations Cure and Cover Clause Condition of Equipment Insurance Requirements Property Insurance Performance and Payment Bond Cancellation Public Records Access Proprietary Information Recycled Materials Promotional Advertising / News Releases Indemnification and Hold Harmless List of Tables Table 1: RFP Timetable Table 2: Wind Requirements Table 3: SRIN Conceptual Camera Locations Table 4:Technical Evaluation Criteria Table 5:Technical Evaluation Rating Table 6:Cost Evaluation Weights PROJECT OVERVIEW Executive Summary Since the tragic events that took place on September 11, 2001, much of our government’s focus has been on securing our nation’s infrastructure. The security of our nation’s ports has been a top priority for several years. Much of the needed port security infrastructure has been enhanced through the Port Security Grant Program (PSGP) funding. Georgia Ports Authority received several grants in the Round 7 PSGP. Three of the approved and funded projects are included in this Request For Proposal (RFP). The RFP’s for these three grants are combined to reduce paperwork and to allow reduced cost in the execution of the projects. Because these projects are similar in nature, GPA hopes to obtain better pricing on the combined projects than ordinarily would be obtained if all projects are prosecuted separately. However, due to federal funding laws, it is imperative that each project be contracted and funded separately. The first project, the Savannah River Intrusion Network (SRIN), is an effort to monitor the Savannah River shipping channel through the use of remote cameras that are monitored and controlled from the GPA command center. The project includes installing up to twenty-four cameras at various locations on the Savannah River from Elba Island to the Houlihan Bridge. Some of these will be in remote locations and will require their own, self-contained power sources and wireless transmission systems. This grant also provides analytic systems and monitoring stations in the command center. Finally, there will be a fiber optic connection made to connect GPA with the Savannah-Chatham Metropolitan Police Department (SCMPD) monitoring station. The second project, Colonel’s Island Intrusion Network (CIIN), is very similar to the first project; however, it is intended to protect GPA assets in Brunswick, Georgia. This project includes up to six cameras covering the navigation channels around Colonel’s Island (CI) and Mayor’s Point (MP) terminals. Again, some of these cameras will need their own power and data sources. A small monitoring station in Brunswick is included in this project. The third project, TWIC Access System Integration (ASI), is primarily aimed at preparing the Brunswick terminals for the new Transportation Worker Identification Credential (TWIC) program by adding fixed and mobile TWIC biometric readers to the existing AMAG access security system. Wireless coverage will be added to the terminals to allow GPA police to communicate freely with the access security system using handheld readers. Finally, the proliferation of various security systems is cause for concern regarding the long-term ability of the GPA police to monitor the systems efficiently. Consequently, an additional section has been added to the RFP in an attempt to determine capabilities of various state of the art systems and obtain cost data on various security system components for which GPA has an interest in purchasing. Depending on the results in this bid section, some items may be purchased as part of this proposal process, some may be used to apply for future PSGP grants, and some may be rejected entirely and drive the long term plans of the GPA security system in another direction. Port Operations (Background) Georgia Ports Authority operates five of their six terminals. This RFP only regards four terminals: two in the Savannah area and two in Brunswick. The largest and busiest terminal is the Garden City Terminal (GCT) located near Savannah. GCT is a 1200-acre container terminal through which approximately 2,500,000 twenty foot equivalent containers (TEU’s) pass through each year. GCT has almost 2 miles of continuous berthing – the largest single terminal in the country, holding 23 ship-to-shore container cranes and close to 150 other container lifting equipment including top lifts and rubber-tire gantries (RTG’s). Two Class I railroads with over 30,000 feet of track in two intermodal container transfer facilities (ICTF’s) and thousands of trucks move the cargo each day. Over 600 ships calls per year visit the 9-berth facility. Appendix 1 has been provided to aid bidders’ familiarity with the garden city terminal. Ocean Terminal (OT), also located in Savannah, sits on 208 acres and has 6 berths for 6,700 feet. OT has container and gantry cranes; but, mostly handles commercial and military loads of heavy equipment (tanks, helicopters, armored vehicles, backhoes, high hoes, paper and wood products, etc.), passenger vehicles, armament, yachts, and other non-containerized cargo. CI in Brunswick is a roll on – roll off facility sitting on 1,700 acres of fenced parking for the thousands of automobiles that pass through the port, import and export, each year. In addition, in the middle of the automotive facility sits one of the largest deepwater agri-bulk facilities in the country where thousands of tons of grain pass to and from the ships via a conveyor system. Two Class I railroads and thousands of trucks move the cargo through the facility. Over 150 ships dock at CI each year. MP is a small, dedicated breakbulk facility specializing in distribution of a variety of forest and solid wood products such as wood pulp, linerboard, plywood and paper products. With 22 acres, 1,750 linear feet of berthing, 355,000 square feet of transit shed space and 7.9 acres of open storage, the facility has the capacity to handle the largest cargo shipments quickly and efficiently. The MP Terminal is also served by two Class I railroads with 2,000 feet of track available for cross dock operation as well as truck traffic. Project Approach GPA’s approach to the development of these systems is to request proposals from bidders that have experience providing off-the-shelf systems that are already known to work in other ports. Although GPA wishes to use the most technologically and competitively advanced systems; there is no desire to be on the “bleeding” edge of technology. A failure in security could be devastating to the Port and the regional economy. Therefore, proposed systems that have the best chance of selection are those that are proven in other terminals around the world. Furthermore, by purchasing “off-the-shelf” systems, GPA will not design the system; rather, GPA looks to the selected vendors to provide designs that exceed the stated operational requirements. GPA will not rule out proposals on newer or different technologies without a thorough review. GPA recognizes that existing systems are still not as accurate and reliable as is desired. Thus, GPA welcomes proposals from bidders whose systems may not be described here or that may not be currently located in another port; but may provide solutions that are otherwise superior to the system being described. Thus, bidders should review the operational systems in existence and the operational intent/requirements being issued as a part of this RFP to ensure their proposed systems provide the overall system functionality necessary to support the Port of Savannah. Although a conceptual design and schedule are presented in this RFP; it should be used as a reference to help explain GPA’s expectations. It is up to the bidder to design a system that meets the needs of the Port and submit a proposed completion schedule. The systems GPA chooses to buy will be selected in part on the following attributes: Initial cost (within grant parameters), Lifetime cost, Predicted reliability, Demonstrated technology, Open architecture, Interoperability, Maintainability, Safety attributes, Ease of operation, Capabilities to grow, upgrade, or modify as requirements change. These systems are expected to work on site for many years to come; therefore, GPA must find vendors with whom they can forge good working relationships. Furthermore, these systems will from a baseline on which to grow. For example, the TWIC implementation in Brunswick precedes a much larger TWIC implementation on all GPA terminals. Already, over 100 cameras are installed and operating in GPA terminals. Once the SRIN and CIIN systems are in place, many of the existing systems will be combined to increase the overall effectiveness of both new and existing systems and sensor placements. In conclusion, GPA is seeking qualified vendors to provide systems that enhance the safety and security of the Ports of Savannah and Brunswick without negatively impacting the speed of operations in the terminals. Systems that reduce required manpower while increasing effectiveness will receive greater consideration. Bidder / Contractor Qualifications All contractors bidding on the project must meet certain minimum qualifications for their proposals to be considered. Each individual company shall be evaluated whether they submit a separate proposal or in a team or supplier / subcontractor position. If a company cannot qualify individually, they may be able to qualify as part of a larger team. In a team / partnering/ subcontractor scenario; the points are prorated amongst the team members depending on each member’s responsibilities and contributions to the overall team. The points system is defined below. Each team shall fill out the qualification sheet found in Appendix 2 and shall suggest an appropriate point value based on their qualifications; however, the teams will be rated by the project selection committee and the qualifications points will be determined and compared to the requested amount. If a contractor/team is deemed unqualified by the committee because the selection committee did not allocate as many points as the proposer submitted, the contractor/team shall have an opportunity to respond with more detail to explain why they believe they have enough points to remain qualified. If the selection Committee then determines the contractor/team to still not be qualified; the proposal shall be rejected. Prior GPA Projects. A contractor / team shall receive up to 10 points if they have completed projects on GPA terminals prior to this one. Port Projects. A contractor / team shall receive up to 20 points if they have completed projects in a seaport prior to this one. Projects at GPA terminals can be counted for this section too. More points will be allocated if the projects described are similar to this project. For example, installing outdoor video cameras would be considered similar; whereas, installing electronic systems on a crane would not. Previous Installations. A contractor / team shall receive up to 30 points if they have installed the exact components / systems in another location. Point scores will be higher if the system is still in operation. Company Age and Financial Condition. A contractor / team shall receive up to 40 points if they have been in business under their current name for five years or more and have a strong financial position. The longer they have been in operation under their current name, the more points they shall be awarded. Teams. Teams may receive additional points if they have worked together on other projects in the past. To be awarded additional points, the projects must be completed before the deadline for turning in the proposal. Terminology and Abbreviations The following terms and abbreviations are used throughout this document. ACSAccess Control System AIS:Automatic Identification System AMAG:An access control and IP video manufacturer ASI:Access System Integration Bidder:An entity responding to an RFP (may be a contractor or supplier). BTU:British Thermal Unit CAD:Computer-Aided Design CCTV:Closed-Circuit Television CFR:Code of Federal Regulations CHUID:Card Holder Unique Identifier CI:Colonel’s Island CIIN:Colonel’s Island Intrusion Network Contractor:An entity providing, or capable of providing, labor and materials to GPA, and may or may not have a written contract directly with GPA DHS:Department of Homeland Security EO:Electro-Optics Exclusion Zone:An area defined by system operators to mark where people, vehicle or vessels are not allowed entry. Entry into an exclusion zone by any person, vehicle or vessel constitutes a breach of security. GCT:Garden City Terminal GPA:Georgia Ports Authority GPS:Global Positioning System ICTF:Intermodal Container Transfer Facility ID:Identification IED:Improvised Explosive Device IR:Infra-Red KtsKnots LCD:Liquid Crystal Display LINCLogistics Innovation Center MP:Mayor’s Point MPEG:Moving Picture Experts Group MTBF:Mean-Time-Between-Failures Navis:Software and database system that manages container position and shipping information. It is also the name of the company that produced the Navis software, including Express and SPARCS. O.C.G.A.:Official Code of Georgia Annotated OT:Ocean Terminal PSGP:Port Security Grant Program PSRD:Port Security Requirements Document POV:Privately Owned Vehicle PTZ:Pan, Tilt and Zoom R&D:Research and Development RFP:Request for Proposal RTG:Rubber-Tired Gantry crane is an off road overhead cargo container crane with the lifting mechanism mounted on a crossbeam supported on vertical legs which run on rubber tires. SRIN:Savannah River Intrusion Network Subcontractor:An entity that provides labor and materials to GPA, but whose contract is with a vendor or bidder depending on reference. Subsystem:One of several parts to a larger system. Supplier:An entity that provides only materials, not labor, to either a vendor, bidder, or directly to GPA depending on reference. TCOTotal Cost of Ownership. For purposes of this document, TCO is defined as the sum total of all cost relating to specific technology over a 10-year period. TOS:Terminal Operating System. The software that manages the flow of containers through the terminal. TEU:A standard quot;
Twenty Foot Equivalent Unitquot;
steel ocean-shipping container Turnkey:A project in which a separate entity is responsible for setting up a plant or equipment and putting it into operations. It can include contractual actions at least through the system, subsystem, or equipment installation phase and may include follow-on contractual actions, such as testing, training, logistical and operational support. TWICTransportation Worker Identification Credential USCG:United States Coast Guard Vendor:An entity that has been selected by GPA to provide a subsystem (or partial subsystem) as described in an RFP, and has a written contract directly with GPA. WEP:Wired Equivalent Privacy and it is a security protocol for Wi-Fi networks. XML:Extensible Markup Language Contacts The following contact information is provided as a reference for particular questions regarding this RFP. All questions shall be submitted in writing by email (preferably) or by fax or letter and shall be submitted (arrive at GPA) no later than midnight of the date noted in the RFP timetable. All questions shall be submitted to Scott Rasplicka or they will not receive a response. Questions submitted to anyone else will not be answered. Also, note that all questions and responses will be collected into one document and published for all to bidders read. ,[object Object],Scott Rasplicka GPA Project Manager 125 E. 44th Street Savannah, GA 31405 (912) 667-4337 Scott@HomePortSolutions.net SRasplicka@GaPorts.com ,[object Object],Mill Lawson Port Security Systems Administrator PO Box 2406Savannah GA 31402-2406 (912) 966-6764 MLawson@GaPorts.com ,[object Object],Brad Goodman Network Manager City of Savannah 132. E Broughton Street 4th floorSavannah GA 31401 (912) 651-6919 Brad_Goodman@SavannahGa.Gov ,[object Object],Lewis Leonard ICS Director Chatham County Chatham County Courthouse 133 Montgomery Street, Suite 507 Savannah, Georgia 31401 (912) 652-7344 LLL@chathamcounty.org RFP Timetable EventDateIssue RFP’s13 March 2009Pre-proposal Conference Registration Deadline26 March 2009Pre-proposal Conference2 April 2009Submission of Written Questions Due24 April 2009Responses to Questions8 May 2009Proposals Due21 May 2009Bid Opening21 May 2009Notice of Intent28 August 2009 Table 1: RFP Timetable Vision As noted in Section 1.1 - Executive Summary above, this project consists of three projects in one. While the requirements section will provide some clues as to what each project should accomplish, sections 3, 4 and 5 will provide a generic designs, concepts of operations and schedules for each of the three projects outlined above. The descriptions defined here are provided merely to help describe the projects’ intents and should not be used as design blueprints nor should the information provided be the cause of reduced capabilities in submitted proposals. The selected proposal will be chosen in part based on the capabilities of the proposed solutions. If a proposal is submitted exactly as per the conceptual design described here and is not as robust as another vendor’s design; this RFP cannot be used as grounds for protest. Each bidder shall make their own design using the concepts and requirements described in this document. The merits and cost of each individual design shall be judged to select a vendor. Furthermore, if a design is submitted exactly per the conceptual design described here; the vendor shall have no grounds to hold GPA responsible for any performance failures. In fact, as part of the submission of a proposed design, each vendor shall indicate if and to what degree the proposed design will meet each and every requirement. Thus, any vendor that chooses to use the conceptual design as an actual design must still evaluate the design to determine its ability to meet the requirements and then make a formal commitment guaranteeing that level of performance. That evaluation and guarantee shall become part of the contract if selected. The concept presented here by GPA does not guarantee any particular level of performance. Design Concerns There are a number of specific concerns that should be addressed in the design and operation of the systems. These concerns are based on observed practices at GPA or failures identified at other facilities or described in professional journals. The concerns listed below are in no particular order: False Alarms. In many instances, camera monitoring room operators are overwhelmed by false alarms and the time it takes to sort through false alarms may allow a real event to pass unobserved or be observed too late to address the problem. The addition of these systems should not cause an increase in camera monitoring room personnel; thus, automatic notifications of potential issues should only occur when an event of interest is actually taking place. Transmission vs. Resolution or Frame Rates. Network limitations always cause reductions in the amount of data transmitted, either through a reduction in the number of frames per second or a reduction in the resolution of the frames. Where possible, built-in capacity should assume additional sensors will be added over time. Creativity will be required to make appropriate tradeoffs through the use of variable frame rates and resolutions. Recording capacities must also take the amount of transmitted data into account through distributed recording or other measures to ensure forensic evidence is available as needed. Savannah – Brunswick Network Limitations. Currently, there is a T-1 between GCT and CI and another T-1 between GCT and MP. These T-1’s are used for all network communications including passing video, email and other data. Next year, a transmission system of at least 300 MB/s data rates will be installed between GCT and CI. Another system will be installed between GCT and MP and a final system between MP and CI. These four links will be set up in a ring such that up to 600 MB/s can be transmitted between Brunswick and Savannah. Furthermore, if one side of the link is down, the traffic can be rerouted to the other side of the ring. Thus, system designs should assume that when first utilized, very little bandwidth will be available for use; however, within a year of installation, significantly more bandwidth should be available. Therefore, any proposal should include a plan for data transmission upon initial use and another plan for use later on. In either case, local recording, localized analytics and transmission on demand or other creative approaches should probably be considered. Camera Control Latency. Network limitations and other issues often work in reverse causing latency in camera movement. When the latency is too great, it is difficult to track moving objects, particularly when the angular crossing rate is significant. Proposers should discuss how the proposed system will address control latency and ensure the problem does not occur. Long-Term Repair/Replacement Costs. As more and more systems and components are added, it becomes increasingly difficult to afford the maintenance and replacement of these systems. Thus, proposals should address system design and other considerations made for reducing long-term, life-cycle costs. Video Security. Since these video systems are intended to allow the video and video control to be passed to multiple users inside and outside GPA firewalls, the security of these video systems is critical. Controls should be placed on the video that allow certain people or locations to view certain video signals. Furthermore, a hierarchical control mechanism should be in place to allow certain people to control video cameras and those with greater need should be able to take control at any time of any particular asset. It should be noted, too, that other port entities may also pass their video data to GPA to be used as part of the SRIN or CIIN. TWIC Speed. With over 8000 transactions occurring daily on GPA terminals, every second counts. A few seconds delay per truck or a few minutes delay for any one truck can cause truck traffic to backup, blocking roads and intersections for long periods of time. Therefore, any TWIC system or access control system (ACS) proposed should ensure that speed of operation is foremost in consideration. TWIC Read Failures. When truckers pull up to the scales to be weighed to have their credentials validated, he is already in one of a multitude of lines with numerous other trucks. Any issue that causes a trucker to not to be allowed to enter the facility can cause significant issues as the truck is delayed until he can pull across numerous lanes of traffic to reach a trouble kiosk. Thus, multiple failures to validate a TWIC or a trucker’s biometrics can cause long delays and backups at the gates. So, while it is critical to validate TWIC’s quickly; it is equally, or even more important, that the system in place is exceptionally accurate. Operational Interference. Due to the high capacity of terminal operations; installation, maintenance and equipment failures cannot be allowed to interfere with normal operations. If gate lanes must be taken down for installation, for example; it should be completed after hours or on weekends. At most, one lane can be out of operation during normal working hours. Normal gate hours are Monday through Friday, 0700 – 1900. Logistics Innovation Center (LINC) Partnership Georgia LINC is a unique partnership of private industry, academia and federal and state authorities such as GPA working together to develop, apply and promote new technologies, identify unique applications for existing technology, and create best practices for safe, efficient and secure supply-chains. The overall mission of LINC is to promote creative technology development and commercialization while providing an environment for new venture creation and entrepreneurial outreach in a specific, regionally targeted industrial area. The advancement of automation technology at port terminals in projects such as this one is a significant undertaking where LINC can lead, promote, and perform research and development necessary to develop ever more accurate and efficient logistic systems. Companies that support maritime logistics are invited to be a part of LINC and help drive its future. Contact Page Siplon for more information. Mr. Page Siplon Director Georgia Logistics Innovation Center 190 Technology Circle, Suite 173 Savannah, GA 31407 page.siplon@gatech.com Phone: (912) 966-7867 Fax: (912) 963-2549 www.GeorgiaLogistics.com PORT SECURITY REQUIREMENTS DOCUMENTS (PSRD) This section outlines the general requirements of the systems being purchased in various PSGP grants. In the proposal, bidders shall specify performance levels for each device as well as the system level. The specifications/performance levels provided in the proposals shall be compared to the performance levels identified in the PSRD to determine compliance. The performance levels specified in the proposal shall become the level to which devices and systems are tested. It is anticipated that the performance metrics provided by the bidder are more complete and more stringent in most cases than those provided in the RFP. Those metrics shall be used to compare proposals from various bidders to determine which proposals have the best capabilities. Consequently, the proposal shall become part of the contract if issued to a successful bidder, and if the bidder fails to meet the proposed metrics, they will be in breach of contract. Device and installation tests shall be performed during installation. Once installation is complete, operational tests shall be conducted against these requirements as well as all proposed metrics. A test plan shall be presented by the bidder to discuss how compliance testing shall be performed and what constitutes pass/fail criteria for each test. See Section 7.12.18 for more information on compliance testing. Specific nomenclature is used in this section to define and delineate requirements from goals or actions. There are three levels of requirements defined here: Any requirement stated as “shall” indicates that the requirement is mandatory. Any requirement stated as “should” indicates that the requirement is not mandatory; but, all reasonable efforts should be made to comply with the requirement. Any requirement stated as “may” is a valid requirement; but, is one the selection team thinks may negatively impact costs for very little gain or may too tightly restrict competition. Reasonable efforts should be made to comply with these requirements; but, prudence is more important. Inability to fully comply with any particular requirement does not automatically disqualify a bidder. Technology and cost restrictions may not allow every requirement to be met by any one proposer. Therefore, every bidder shall comment on whether their proposal will comply or not comply and to what level for each individual requirement. Any requirement that does not apply to the particular system or component being proposed should be marked “Not Applicable.” Obviously, those proposals that fail to comply with too many requirements will face difficulty winning a contract. General Requirements These requirements are applicable to all systems and subsystems including options or alternates that may be proposed. If conflicting requirements are identified in other sections of this RFP, the more stringent requirement applies. Reduced Personnel. Systems shall be designed using automation, automatic data entry and other methods to reduce the manpower required to operate and maintain fielded systems. Replacements. Bidders shall provide a realistic estimate of the number and type of replacement parts that will be required as well as the number of spares that must be kept on site for quick turn-around when items fail. GPA will not pay for equipment and services due to failures that exceed the estimates outlined in the proposals by more than 15%. Furthermore, GPA will not pay extra for any failures that require expedited services or shipping due to failures that exceed the number of spares recommended in the proposals. Maintenance. Bidders shall provide a realistic estimate of preventative and emergency maintenance costs. Penalties may be imposed if actual maintenance costs exceed estimated costs in the proposal by more than 20%. Initial installation. Installation costs are critical, as GPA has limited grant funding for these projects. However, 10-year life cycle costs will be as important as initial costs. Bidders shall provide 10-year life cycle costs as well as initial installation costs in the proposal. Improve Safety. The safety and well being of GPA personnel is paramount and bidders shall address safety in the design, maintenance procedures and operations of any equipment fielded for port operations. No Service Failures. GPA cannot afford failures that disrupt terminal operations; therefore, bidders shall ensure scheduled and unscheduled maintenance does not interfere with terminal operations. System Reliability. Reliability of these systems is critical to Port security. Fielded systems shall be operational 24-hours each and every day of the year. Any system fielded shall meet the following stringent reliability requirements. Total Annual Downtime. Fielded systems shall not be down more than 10 hours (cumulative) in any rolling 12-month period, including time spent for scheduled shutdowns for maintenance or upgrades. Total Monthly Downtime. Fielded systems shall not be down more than 3 hours (cumulative) in any one month, including time spent for scheduled shutdowns for maintenance or upgrades. Total Weekly Downtime. Fielded systems shall not be down more than 2 hours (cumulative) in any week, including time spent for scheduled shutdowns for maintenance and upgrades. Total Daily Downtime. The system shall not be down more than 1 hour (cumulative) in any 24-hour period, including time spent for scheduled shutdowns for maintenance or upgrades. Backups. Systems shall be designed to prevent data losses due to component, power or data transmission failures. Data shall be recorded and backed up to prevent losses due to system failures. Single Point Failures. Bidders shall eliminate all single point failures in the system designs if at all possible, including those caused by power and data transmission failures. All single point failures that cannot be eliminated shall be identified in the proposal. Power Failure. All systems shall be capable of operation for at least 1 hour without interruption in the event of a complete power failure. Grounding. All equipment shall be properly grounded to within 5 Ohms verified by a grounding resistance test. Resistance tests are invalid if done within 72 hours of rainfall on site. Weather Conditions. All outdoor and mobile equipment, unless otherwise specified, shall operate in all weather conditions likely to be endured over a 100 year period including high temperatures, heavy rain, fog, sleet, snow, ice and high winds. Exposure to any environmental conditions shall not reduce or eliminate warranties on any equipment. Temperatures. All outdoor and mobile equipment shall operate in all Savannah area temperatures without degradation or failure from -20º F to +120º F. Fog. All outdoor and mobile equipment shall operate in severe fog without degradation or failure. Rain and Humidity. All outdoor and mobile equipment shall operate in humidity levels between 0 and 100% without degradation or failure. These operational conditions include heavy rain, thunderstorms, hail, sleet, snow and saturated fog. Salt Water/Air. All outdoor and mobile equipment shall be capable of operating in salt water environments without special handling or reduced life. Sunlight. All outdoor and mobile equipment shall be capable of operating in direct sunlight / high UV-light without degradation. This includes camera sun spots caused when the lens is pointed directly at the sun or at a reflection of the sun, as well as other sun related effects such as material degradation due to ultraviolet light. Environmental Housing. Enclosures or other environmental housing may be provided to enhance the longevity of the outdoor equipment and ensure continued operations in weather extremes. If enclosures are used, they shall not interfere with nor slow the operation or maintenance of the system or reduce the capabilities of the system in any way. Winds. All outdoor and mobile equipment shall operate in winds that often exceed 20 knots (kts) on a typical day as defined in Table 2 below. Sustained winds up to 90 kts and gusts up to 110 kts.Outdoor and mobile equipment shall operate without degradation or failureSustained Winds above 90 kts; but below 150 kts and gusts above 110 kts, but below 180 kts.Outdoor and mobile equipment may be temporarily down (due to vibration, etc.); but, the system shall begin working again automatically once the winds calm back down to numbers below the above published limits unless the sustained winds exceed 150 kts for more than 5 minutes or experience gusts above 180 kts.Sustained winds above 150 kts or gusts above 180 kts.Security camera networks are not required to remain operational. Table 2: Wind Requirements Codes. All equipment, construction and installation procedures shall be compliant with local building codes, UL and other applicable codes. Turnkey installations. In as much as possible, GPA is seeking off-the-shelf turnkey solutions. However, any resources (such as power, fiber cabling, towers, etc.) the vendor requires from GPA to complete their installations must be outlined in detail in their proposal. Bidders assume the responsibility to install and/or pay for any infrastructure not properly identified in their proposal. Minimal Customization. As the complexity of systems increases, GPA wishes to reduce customized software as much as possible. Fielded systems shall not require customized software solutions. If customized software is proposed, it shall be identified in the proposal. Data Integration. GPA requires data integration to be seamless and work without error with existing systems. Standardized data types, such as Extensible Markup Language (XML) shall be used. As-built Drawings. As-built drawings and complete documentation shall be delivered within 30 days upon project completion. Final payment will not be made until as-built drawings are provided. Operations Manuals. Operations manuals with step-by-step instructions regarding equipment operations shall be delivered prior to personnel training. Manuals shall include system design layouts, software documentation and details of system operation as well as individual equipment operation procedures and troubleshooting techniques. Final payment will not be made until operations manuals are provided. Maintenance Manuals. Manuals detailing procedures for preventative maintenance and repair/replacement at the system level down to the unit levels shall be provided prior to maintenance training. Final payment will not be made until maintenance manuals are provided. Warranties and Standards. All equipment, hardware and software, shall be warranted by the manufacturer against failure for at least three years in accordance with Section REF _Ref224665677 8.39. Open System Architecture. To the greatest extent possible, GPA requires the use of industry standard equipment and software. Proprietary based systems are strongly discouraged. Where proprietary systems are used, the ability to transmit data in industry standard open system formats shall be provided. Security Camera Networks. Maritime Domain Awareness. The main objective of security camera networks is to improve Maritime Domain Awareness in the Port of Savannah and provide a strong foundation upon which to grow a comprehensive maritime surveillance system. Security camera networks shall help camera monitoring room operators maintain general awareness of river activities at all times. (What is happening on the river?) Security camera networks shall provide camera monitoring room operators with a general awareness of the amount and types of ship/boater traffic in the Port? Security camera networks shall provide camera monitoring room operators with a general awareness of the general conditions of the Port, including the weather, traffic, tides, etc. Security camera networks shall provide camera monitoring room operators with a general awareness of the activities underway along the waterfront (on the water and bordering land). Security camera networks shall help camera monitoring room operators identify if any activities on the river pose a threat to GPA operations Security camera networks may help camera monitoring room operators identify if any vessels are in danger, such as fire, listing, and loss of control or engine power? Security camera networks shall identify if any vessels are traveling at excessive rates of speed or otherwise out of control (driving) and notify the camera monitoring room operators immediately. (The set point for excessive speed shall be adjustable by the camera monitoring room operator.) Security camera networks shall notify camera monitoring room operators automatically if certain locations on the water or land (exclusion zones) are being violated. For large vessels (vessels greater than 25 tons), security camera networks shall ensure camera monitoring room operators can identify the ship’s flag and name. If flags are unfurled, camera resolution shall be adequate for camera monitoring room operators to identify the country flag. If flags are unfurled, camera resolution shall be adequate for camera monitoring room operators to identify the signal flags or any other similarly size markings. Security network cameras shall be properly positioned with appropriate lenses to allow a complete side view of an entire ship 1,000 feet long. Silhouette views should be performed at or near the “trip lines” and may use stitched, composite pictures so long as the “picture” can be viewed in its entirety and sent to other locations as one “picture.” Security camera networks should use adequate camera angles and resolution to allow views of the ships’ bridges and decks. For boats, security network cameras’ capabilities shall be adequate to determine boat/vehicle color and approximate size. Security camera networks shall ensure camera monitoring room operators can identify boat names and boat registration numbers. Using good camera positioning and lenses, security camera networks shall allow camera monitoring room operators to zoom in on the deck of a boat. Well planned camera angles and resolution shall provide camera monitoring room operators with the capability to identify the number of people in a vessel if topside as well as the activity in which they are engaging, such as fishing, looking under piers with binoculars, taking pictures, skiing, etc. Do not lose sight of a vessel. Security camera networks should not have any locations in the river where a vessel is not visible (blind locations) on at least one camera. Security camera networks should maintain camera visibility on both sides of the river to prevent inadvertent blind locations caused by passing ships. Security camera networks should correlate data provided by AIS with ship locations as determined by SRIN sensors. If the ship is not transmitting AIS data and should be (according to the ship’s size), security camera networks should notify camera monitoring room operators with an automatic alert. If the ship is transmitting AIS data; but, the data does not correlate with the parameters determined by security camera networks, camera monitoring room operators should be alerted. Track Ships. Security camera networks shall automatically track ships transiting the Port. Security camera networks shall use video analytics to identify and track ships and boats. Security camera networks shall discriminate between small boats and large vessels. Security camera networks shall automatically track vessels transiting the Port. Security camera networks should provide classification information for all boats and vessels in the Port (speed, course, location by latitude and longitude, flag (may require manual selection), etc. Security camera networks shall provide automatic alerts to camera monitoring room operators when ships cross preset boundaries. For the SRIN, security camera networks shall detect any ship or small surface boat passing into the port area at the Houlihan Bridge. For the SRIN, security camera networks shall detect any ship or small surface boat passing into the port area near Elba Island. Security camera networks shall also detect traffic passing behind Elba Island. For the SRIN, security camera networks shall detect any ship or small surface boat passing into the area between the Talmadge Bridge and just west of GCT near the Savannah Sugar refinery. For the CIIN, security camera networks shall detect any ship or small surface boat passing into the port area at the Sidney Lanier Bridge. For the CIIN, security camera networks shall detect any ship or small surface boat passing into the port area upstream in Turtle River or Oglethorpe Bay. The CIIN shall also detect traffic passing on both sides of Andrews Island. Security camera networks shall detect and alert camera monitoring room operators when any vessel exceeds a pre-established speed that can be set by each individual operator. Security camera networks shall alert camera monitoring room operators and track any vessel passing through an exclusion zone established by the controllers. The camera monitoring room operators shall have the ability to create these areas. Security camera networks shall provide camera monitoring room operators with the capability to define areas where the analytics shall ignore any activities. Even though the activities are ignored within those areas, security camera networks shall still record any activities that occur. Security camera networks shall use analytics to provide automatic alerts to camera monitoring room operators. Automatic visual and auditory alerts shall be used to notify camera monitoring room operators of the following events: Vessels passing trip lines set at Elba Island and Houlihan Bridge. Vessels passing the Talmadge Bridge or the Savannah Sugar Refinery property. Vessels stopping in the port area between Elba Island and the Houlihan Bridge. Vessels passing trip lines set upstream of Andrews Island. Vessels passing the Sidney Lanier Bridge. Vessels stopping in the port area between Andrews Island and the Sidney Lanier Bridge. Vessels getting too close to an exclusion zone. Vessels moving faster than 20 kts. When the plots of two vessels merge. For certain events, alerts shall allow camera monitoring room operators to pass text, audio and video information to other personnel via cell phones, laptops, emails messages, and other communication devices. Security camera networks shall provide a method to rank all events/alarms in the system. The ranking methodology should be established on a per-operator, per-data source basis. The display shall provide alerts based on a ranking system that includes the age of the alarms/events. Any automatic system installed should be free of false alarms caused by trees blowing in the wind, waves on the water, sun, shadows, clouds, lights or other natural or artificially occurring events in the environment. Monitoring Capabilities. Security camera networks shall provide adequate monitoring capabilities to allow camera monitoring room operators to maintain situational awareness to follow and dispatch as needed for incidents and potential incidents. The camera monitoring room shall be equipped for two operators plus a third supervisory position. The camera monitoring room shall allow one person to monitor security camera networks and dispatch responders from one monitoring station under most situations. The camera monitoring room shall have two monitoring stations that allow two operators to work together to monitor security camera networks and dispatch responders. The camera monitoring room shall have a third seat set up as a supervisory position to oversee the two operator stations, monitor sensors from that station separately, or have override authority to take control of any sensor being monitored by other watch stations. Camera monitoring room operator stations shall have the capability to divide sensors for monitoring in numerous, flexible ways and shall, at a minimum, be able to select all sensors from any particular terminal: GCT, OT, MP or CI. The SRIN shall be included in the GCT. The CIIN shall be included in the CI terminal. The CIIN and the SRIN shall also be selectable as independent sensor systems. Security camera networks shall have the ability to switch and display multiple video signals from digitized analog, IP digital video cameras, and other digital video sources on a single or multiple monitors in a single or multiple screen format; permit complete system control from a workstation; and view live stream and recorded video simultaneously. Security camera networks shall have the ability to freeze a picture and advance or rewind the video in variable speeds including frame-by-frame. Security camera networks shall allow the control of pan/tilt/zoom through the use of a mouse or other tactile input such as a joystick. Security camera networks shall allow the system administrator to configure user settings to allow the display of only those items the video operator is permitted to view. Monitors shall display resolutions as good as or greater than the resolution of any camera in the system, including all other existing cameras monitored at GPA facilities. Camera monitoring room operators shall be able to see a black kayak at night in bad weather at dead low tide. Camera monitoring room operators shall be able to identify the number of people above decks in a small boat. Security camera networks shall provide a graphical user interface that provides a “birds-eye-view” of the areas being monitored (Elba Island to Houlihan Bridge in the Port of Savannah and the Sidney Lanier Bridge to the I-95 bridges over the Turtle River and the South Brunswick River in the Port of Brunswick) with indications to show where the sensors are as they are selected for monitoring and what direction the sensor is pointing in real time. Sensor (camera) selection should be possible from the graphical interface. Additional data regarding the sensor should be available on the graphical screen such as the camera name, number, location, type, etc. On screen icons should make it easy to determine what type of asset/data source is being viewed. For example, a fixed camera should have a different icon than a PTZ or thermal camera. Security camera networks shall provide the ability for each camera/sensor to be assigned a unique name. Monitors shall not use plasma screen technology. Large, wall-mounted screens should be utilized to allow observers as well as operators to maintain visual awareness and desktop screens should be utilized for closer scrutiny. One camera monitoring room operator shall have the capability to view no more than 18 cameras at once. Video that is on screen shall be presented within 1/4th of a second from the actual event. The calculated latency shall take into account all transmission and network effects between the camera and the video screen. Audio alert volume shall be adjustable; but, with a maximum volume that is loud enough to be heard by monitoring personnel in a noisy environment. Camera monitoring room operators shall be able to hear alerts above room ambient noise, including personnel talking, equipment hums, and other system audio equipment. Personnel in the guard shack in CI shall be able to hear the alerts when standing within 15’ of the guard shack with the door or window open. Personnel at the front desk of GCT shall be able to hear the alerts at maximum volume above the ambient noise created by 25 people standing in the main lobby talking. Personnel at the credentialing center of GCT shall be able to hear the alerts at maximum volume above the ambient noise created by 25 people standing in the main lobby talking. PTZ control shall be adequate to track ships and other moving objects without losing them due to latent control signals. Camera control latency shall include network latency and shall be measured from the moment of movement of the camera control mechanism at any monitoring station to the beginning of the resulting movement of the camera. Network latency may vary depending on the network load at the time of camera movement. The network load used to calculate network latency shall be based on an average expected traffic load for each leg of the network which is based on the number of cameras in the system that will be transmitting over that leg of the network. Maximum loads shall be used to calculate network latency effects on legs that include traffic from other system devices. Existing traffic loads for any specific existing network leg can be provided upon request by the GPA IT department. Calculations used to show camera latency in the proposal shall be shown. Security camera networks shall be able to track boats moving at 40 kts or less without loss of visual. Camera control shall be based on priorities established and be adjustable by GPA personnel. Priorities for camera control shall be able to be established for each camera individually. Camera control priorities for each camera should be able to be set in groups. The time it takes to make changes to camera control priorities shall be less than 10 minutes. When outside users use security camera networks, GPA shall have the ability to maintain (primary) control of any camera purchased and installed under this proposal/contract. Recording and Playback. Security camera networks shall provide adequate recording and post incident software techniques to playback and view incidents without loss of video quality. Recording shall be capable of use for evidentiary purposes. Forensic protocols shall be employed. Initial recordings (30 days at a minimum) shall be lossless (no reduction in video data) regardless of any video compression employed. Artifacts shall not be added to the original video when recorded or anytime thereafter. Write protection shall be employed to ensure the video recording is not damaged. Video recording frame rates shall be equal to or greater than the frame rates viewed in the monitoring room. Increased frame rates shall not be recorded just to meet any forensic evidence protocols. Frame rates shall be determined based on system operational needs to meet requirements identified in this document. Video resolution/pixel counts shall be equal to or greater than the resolution delivered and viewed in the monitoring room. Resolution shall be determined based on system operational needs to meet requirements identified in this document. Video used for playback and any forensic analysis shall be copies of the original video. Under no circumstances shall the original video recording be altered in any way. Security camera networks shall have the ability to replay recorded video at various speeds including the rate at which it was recorded. Recording of all video shall be maintained for a minimum of 30 days. Recorded files shall be readily accessible over the local area network within 10 seconds. All files shall be time/date stamped. Standard, non-proprietary video formats such as MPEG-4 shall be used for recording and playback. Recordings shall include some form of redundancy such as RAID 5. Some form of analysis capability shall be included to review recorded video files, including the following, at a minimum: Search and playback by date/time. Search and playback by camera. Camera monitoring room operator shall be able to freeze the frame to view the frame in full resolution as recorded. Camera monitoring room operator shall have the ability to copy video clips between two time stamps and save them for additional playback. Clips should be viewable at standard computer monitoring stations without any additional software other than that supplied with Microsoft Windows. Additional software provided by the proposer may be used to provide additional video playback and analysis capabilities. The capability to save video clips to other mediums such as DVD’s shall be provided. For video clips that are too large to save onto one DVD, automatic file structures shall allow multiple DVD’s to be used. The camera monitoring room operator shall have the ability to group video from multiple cameras into one file for analysis. Power and Data Transmission. Power and data transmission shall be provided to and from security camera locations. Power may be obtained from nearby facilities or by creating stand-alone power and wireless data transmission. Proposer may use power over Ethernet. Proposer may use power from nearby facilities, such as existing light poles, buildings, etc. Confirmation on power availability at certain locations can be obtained from the GPA IT department. Proposer may install solar or other alternate power supplies. Power shall have a 72-hour backup capability. Solar power or other alternate power shall be adequately sized, including appropriate battery packs, such that five years from the date of installation, the cameras shall operate and transmit video signals without reductions in data for three days without a visible sun. If local power is used, battery backups shall be provided that ensure camera operations and data transmissions do not cease for three days. Reductions in frame rates and data transmission, etc. shall not be allowed. If the location of the power source has a generator, then the battery shall operate for one hour providing enough time to get the generator started. Proposer shall provide adequate data transmission capabilities from the camera or groups of cameras to the server room in the IT department of the Administrative Building located at GCT. (Note: Selected contractor may be required to demonstrate this capability before moving forward with the contract.) Local area networks already in place may be used as available. If connecting into an Ethernet or fiber network, any required equipment such as switches or hubs shall be included in the proposal. If adequate network equipment exists and is confirmed by the IT department, then it will be removed from the proposal before a contract is let. Wireless networks as well as internet networks may be used; however, reasonable precautions shall be taken to keep the data secure. Cameras and data transmission may be in analog or digital format so long as the camera and system meets the requirements of the RFP. Miscellaneous. Additional miscellaneous requirements shall be followed. All equipment hardware shall be off-the-shelf, meaning the equipment has been thoroughly tested and proven in actual use, is currently operating in other locations and is not proprietary in nature. Software used in the project shall not render other commercial components useless or prevent other components from being interconnected now or in the future. Prototypes are not acceptable. Due to ambient light conditions on most parts of the river (from the city, stars, etc.); low light level cameras may provide adequate night and bad weather coverage. Bidder must trade off capabilities vs. cost before proposing low light level cameras rather than thermal/IR. Ship identification/classification may be performed only once so long as security camera networks never lose sight of the ship. It is more important for security camera networks to see and identify fast moving speed boats than large commercial vessels. Security camera networks should automatically calculate the speed at which a ship is traveling. Security camera networks should provide 360º views at most locations, especially near Rousakis Plaza and GPA port facilities. Camera monitoring room operators should be able to manually control the cameras to investigate certain potential events. Camera monitoring room operators should be able to track a maneuvering high speed boat. Camera monitoring room operators should be able to zoom in and out on ships’ names or other boat details. Camera monitoring room operators should be able to manually switch from night to day and vice-versa on day-night cameras. Camera monitoring room operators shall be able to manually adjust camera monitoring room monitors for brightness, contrast, color and other features. Camera monitoring room operators should be able to zoom in on pictures/video on all monitors. Camera monitoring room operators should be able to view the same video on multiple screens. Camera monitoring room operators working together should be able to manipulate the same video. Proposals shall include an itemized list of all proposed equipment, its location, footprint, power requirement, and BTU’s so an analysis in the GPA IT department can ensure there will be sufficient space and HVAC available. Security camera networks shall ensure graceful degradation if failures occur. There shall be no single points of failure that would render the entire system unusable. Data storage shall be completed in such a way as to not lose data due to the failure of any one component. Security camera networks shall be expandable over time. Proposals shall identify what it takes in terms of additional equipment and cost to double the number of cameras and camera locations in the system. Access Control System (ACS) Requirements This section applies to all components of an ACS including TWIC mobile readers, fixed biometric readers, door locks, gates systems, enrollment and visitor systems and all other ACS components, subsystems and modules that comprise a complete ACS or act as stand-alone devices. Open Architecture. The security management system shall have an open architecture, giving it the ability to integrate with other critical access control subsystems such as texting, email, alphanumeric paging and closed-circuit television (CCTV). There shall be no proprietary software or hardware restrictions. The system shall easily import and export data in a standard format for use with other databases. The software should provide a graphical interface, including time graphs, full-color icons and toolbar buttons, making the program very intuitive and easy to use. The system shall provide complete facility management, access control and alarm monitoring. The system shall provide the flexibility to effortlessly grow and expand to accommodate the needs of GPA over a lengthy period of time. Enrollment System. The user enrollment system requires these data fields, at a minimum: Company Information is collected first: Company Name, Address, city, State/province, Zip Code, Phone, Extension, Tax ID, Minority Code (Non-Minority, Asian American, African American, American Indian, Hispanic, Other minority, Women), Fax Number, Email Address, Preferred notification Method, and Contact information on 3 points of contact within the company. Personal information is collected on those who require access to GPA facilities: Full Name, SSN, type payment (salary, hourly) Home Address, Home phone numbers, E-mail Address, Cell Phone Numbers, Date of Birth, Race, Gender, hair color, eye Color, Height, Weight, Job title, Emergency Contact Information including name and numbers, and the Picture from TWIC. The user enrollment system shall have a web portal that allows direct entry from companies to enroll their employees for access. A method for periodic verification shall also be included. The user enrollment system shall allow TWIC verification and automatic collection and entry of TWIC data into the system. The enrollment system shall print Mifare (or FIPS-201) GPA ID badges. For the time being, GPA plans to continue to issue GPA ID cards to GPA employees. Existing printers or other equipment may be used to lower the cost. The enrollment system shall automatically check the TSA hotlist for TWIC verification before enrolling new personnel. Furthermore, automatic TSA hotlist verification shall be run on the entire database on a schedule set by GPA. The schedule shall be adjustable. Any contact in the database linked to a TWIC card on the hot list shall automatically: Be denied further access onto GPA facilities, Cause notification to GPA officials, Cause notification to the camera monitoring room in the event that person attempts to enter GPA facilities. Enrollment stations shall be located at the following: Two systems shall be located at the GPA enrollment center, One system shall be located at the GCT Admin Building front desk, One system shall be located at the MP admin building front desk, Two systems shall be located at the CI admin trailer front desk, and Two mobile facilities shall be provided that can locate at any facility with wireless connectivity. All enrollment stations must be in compliance with all TWIC and FIPS-201 regulations, including 49 CFR Part 1572. Enrollment stations shall validate TWIC’s and the cardholder’s biometrics before enrolling the contact into the system. Enrollment stations shall verify the TWIC is not on the TSA hot list before concluding the enrollment. Enrollment of a TWIC holder shall not take more than 10 minutes and should not take more than 5 minutes, including the time it takes to type all personal information into the system. Use of the web or a kiosk to allow the enrollee to pre-enroll to save time at the enrollment station shall be allowed and is encouraged. Enrollment stations shall be secured so only authorized users can enroll personnel into the ACS. Visitor System Requirements. The visitor ID system shall store the following information on each visitor, at a minimum: Full Name, Company name, Drivers License Number, Drivers License State, Date of Birth, Date(s), Purpose of Visit, Host Name, Location Checking In, Location Checking Out, Vehicle Tag Number, Vehicle State, Department Host, and Escort. The visitor ID system shall keep track of each date a visitor checks in and be able to identify how many times a particular visitor has been on site within a certain period of time. It shall be possible to design and create photo-ID badges as part of the main system software. The visitor enrollment system shall print ID badges at multiple locations: GCT Enrollment Center, Front Desks at GCT, MP and CI, and GCT Gates 5 and 8, OT Main Gate, and the CI Main Gate. A badge design should be capable of being used for multiple cardholders without requiring modification between printing successive cardholder badges. There should be capacity for at least 50 badge designs. The system shall be capable of printing different colored visitor ID badges signifying the following: Visitor has a TWIC. Visitor does not have a TWIC. Colors identifying authorized locations where the visitor is allowed access. The system should have the capability to perform online background checks before granting access. The system shall have the capability to verify TWIC’s including biometrics. The system shall have the capability to store biometrics for verification if the visitor is going to be a repeat visitor. The system shall have the capability to capture the cardholder photograph from either a live image, or a stored image from a digital camera without requiring any re-formatting and print it on the temporary ID card. If the visitor has a TWIC, the picture included on the TWIC shall be used. A decent-quality (greater than 3 megapixels) camera shall be supplied along with any associated hardware needed to take photographs and transfer the image to the system. All visitor data shall be archived for future use and retrieval. Photographs shall be visible when browsing cardholder information. Printers used to print visitor badges shall be off-the-shelf printers that can be easily replaced using local office supply stores. ACS Database. The ACS database shall be a standard Oracle or Microsoft SQL database and shall not be proprietary. There shall be a single database, of a suitably secure (as determined by GPA) and reliable technology. Automated database back-up tools shall be provided that can back up the database each day. The following data, at a minimum, shall be maintained in the database at all times: All personal and corporate data collected at enrollment, Each person’s TWIC information captured on the TWIC cards including: security tokens, biometric identification, card holder unique identifier (CHUID), expiration date, and user-definable fields. Any of the user-definable fields shall be used to create quick indexes for sorting. These indexes shall also be available for use in the reports section. Usage data shall be stored for 1 year identifying when personnel entered and departed GPA facilities including what areas they accessed and all date/times associated. The database shall be capable of maintaining and accessing at least 100,000 different contacts. The system shall allow multiple credentials to be associated with each user. Upon editing credential information, the updated information shall be sent automatically to the appropriate access control panels with no other user intervention. The database shall interact with the Navis TOS to allow the Navis database to link a trucker’s name and other data to a truck as it enters a gate. The setting up of people, cards and access rights shall be capable of being performed from a single workstation. It shall also be possible to use multiple workstations simultaneously. It shall be possible to program individual modules by using a local programmer, either for commissioning and diagnostics purposes or for re-programming in the event of failure of some other part of the system. Access Control Operations. The ACS shall be integrated with the terminal operating system (TOS). The TOS shall not issue mission tickets to the truck drivers unless a valid authentication has been provided by the ACS. The system shall allow interaction with other systems to pass information back to the ACS. For example, in the future, the Navis TOS may pass information to the ACS when a truck departs the terminal. The TOS may detect that event using RFID and pass the information so the ACS knows the driver has left the terminal. At a truck gate, the ACS shall: Verify the TWIC is valid and not on the TSA Hot List, Verify the TWIC is registered with GPA, Verify the TWIC holder’s biometric identification, and Send a signal to the Navis TOS the trucker has been verified (or has not been verified). If the trucker is denied access, then an alert shall be sent to the camera monitoring room identifying the location of the offending TWIC holder. At a mantrap, building door, fuel tank or other automatic device access-controlled entry, the ACS shall: Verify the TWIC is valid and not on the TSA Hot List, Verify the TWIC is registered with GPA, Verify the TWIC holder’s biometric identification, and Send a signal to the gate, door, fuel tank, etc. allowing entry for one person. If the person is denied access, then an alert shall be sent to the camera monitoring room identifying the location of the offending TWIC holder. The ACS shall integrate wireless devices to allow manual verification using the wireless device to: Verify the TWIC is valid and not on the TSA Hot List, Verify the TWIC is registered with GPA, Verify the TWIC holder’s biometric identification. The ACS shall automatically deny access to anyone who’s TWIC has expired. Provisions shall be made to allow the ACS to link new TWIC data to a contact when replacement TWIC’s have been obtained. If a contact’s access has been revoked, the ACS shall allow the reason for the access revocation to be entered as well as the length of time the access revocation is in effect. ACS operators may set the time limit either by date (until a certain date) or length of time (permanently, 1 year, 1 month, etc.). The capability to utilize a photograph during “objective authentication” shall be provided. The picture of a user who has been denied access can be quickly retrieved for reference. The picture of an enrolled user or visitor can be retrieved for comparison to identification or the person himself. The system shall read biometric cards and validate biometrics within 2 seconds on average from the time the card holder places his fingers/hand, etc. on the device. In the event of a data failure connection to GCT admin building or a power failure, local readers shall be able to continue operation. (This requires pushing the database to the readers or close to the readers for continued operation.) It shall be possible to define holidays that allow standard daily/weekly schedules to be modified automatically. It shall be possible to specify a maximum door-open time, after which a “door ajar” event will be generated. Equipment and Maintenance. All equipment must be designed for optimum protection against vandalism. All outdoor equipment shall include a standard tamper monitor point. If a power failure occurs, all equipment must auto-boot to its user-defined condition before the power failure. Biometric readers shall comply with all requirements for TWIC and FIPS-201. The ACS shall be capable of utilizing a choice of reader technologies. All Card Readers shall be capable of reading the following card types at a minimum: TWIC, Federal Information Processing Standard Publication 201 (FIPS 201) smart cards, Military ID, Mifare, biometric seafarers identity document (SID), as well as existing GPA, police and fire ID cards. All Card Readers shall allow proximity readers for TWIC as well as keypads for PIN use and biometric readers for authentication. Magnetic swipe and contact readers may also be included. Programming shall allow the use of card plus PIN, PIN only, Card Only, Card or PIN, Card plus biometrics, and card plus biometrics plus PIN for access under varying degrees of MARSEC. Each type of verification shall be programmable by location/device and by groups of devices and by MARSEC levels. A change in MARSEC levels shall automatically change pre-programmed levels of security authorization. Biometric Card Readers shall validate TWIC’s using the TWIC digital signature. TWIC biometric readers shall be TWIC compliant and listed on the DHS Initial Capability Evaluation (ICE) list. The TWIC readers shall be capable of obtaining database information (lookups) as needed even when the communications link between the GCT Admin Building and the CI or MP terminals are interrupted. TWIC system shall be capable of linking to AMAG or a number of other ACS’s. (Note: Bidders shall provide a list of the ACS’s to which the TWIC reader system can be linked.) Power and Data. Power and data transmission shall be provided to and from the TWIC reader locations. Power shall be obtained from nearby facilities. Confirmation on power availability at certain locations can be obtained from the GPA IT department. Proposer may use power over Ethernet. Power shall have a 1-hour backup capability. Battery backups shall be provided that ensures the battery shall operate for one hour providing enough time to get the generator started. Proposer shall provide adequate data transmission capabilities from end devices to the backend system located in the GCT Admin building server room. (Note: This does not include transmission between Savannah and Brunswick.) Local area networks already in place may be used as available. If connecting into an Ethernet or fiber network, any required equipment such as switches or hubs shall be included in the proposal. If adequate network equipment exists and is confirmed by the IT department, then it will be removed from the proposal before a contract is signed. Wireless networks as well as internet networks may be used; however, reasonable precautions shall be taken to keep the data secure. WiFi networks shall not interfere and shall be approved by GPA IT department to ensure there is no interference with the current WiFi systems. Miscellaneous. Additional miscellaneous requirements shall be followed. All equipment hardware shall be off-the-shelf, meaning the equipment has been thoroughly tested and proven in actual use, is currently operating in other locations and is not proprietary in nature. Software used in the project shall not render other commercial components useless or prevent other components from being interconnected now or in the future. Proposals shall include an itemized list of all proposed equipment, its location, footprint, power requirement, and BTU’s so an analysis in the GPA IT department can ensure there will be sufficient space, backup generator capacity and HVAC available. The ACS System shall ensure graceful degradation if failures occur. There shall be no single points of failure that would render the entire system unusable. Data storage shall be completed in such a way as to not lose data due to the failure of any one component. Mobile Readers. TWIC mobile biometric readers shall be portable, capable of being easily carried and used in the field by the average person. TWIC mobile readers shall weigh no more than 5 lbs. TWIC mobile readers shall be compact. TWIC mobile readers shall be no larger than 12” x 6” x 8” and shall include a handle or strap for handheld or over-the-shoulder transportation. TWIC mobile readers shall read proximity cards/smart cards as well as magnetic stripe cards. Specifically, these readers shall be capable of reading and validating TWIC cards, Federal Information Processing Standard Publication 201 (FIPS 201) smart cards, biometric seafarers identity document (SID), as well as existing GPA, military, police and fire ID cards. TWIC mobile readers shall be capable of operating software using Microsoft Internet Explorer standard browser software over a 2.4 GHz 802.11 wireless network or be capable of accepting a wireless card to communicate using other protocols in place at GPA. Data security shall be accomplished by data encryption when saving or transmitting data. TWIC mobile reader data security should be HIPAA compliant. TWIC mobile readers shall provide onboard performance measurements and analysis. Standard reports shall be viewable by the operator to analyze and investigate unit operations. TWIC mobile readers shall maintain a running log that can be downloaded to a computer at the operator’s discretion. The log shall capture all events and the results of each event (positive or failed ID). Biometric Data. TWIC readers shall be capable of capturing biometric data and comparing (biometric authentication) the biometric data to data entered into a standard SQL database by a reader manufacturer by other companies. TWIC readers shall use technology that allows accurate biometric comparison on subjects with dirty (greasy or oily) hands. TWIC mobile readers shall be capable of capturing and reading fingerprint data. TWIC mobile readers shall be capable of capturing and displaying photographic data in standard picture formats. TWIC mobile readers shall be capable of storing a minimum of 1,000 user’s data to speed field operations. Reader Operations and Reliability. The ACS shall ensure that authorized personnel gain access in a timely manner, described below, and that only authorized personnel gain entry to the facilities. For all reliability calculations described below, few data exceptions shall be allowed. Reader failures, greasy hands, cut fingers, etc. shall all be included in the calculations. The only time an attempted access shall not be used in calculating success rates is when the ID card is damaged. There shall be no more than 3 successive attempted reads (counting as one read for success ratios; but, they also count towards the time limit average for validation). TWIC biometric reader system shall not erroneously fail more than 0.5% of all valid TWIC’s including failures to validate the TWIC digital signature, failures to validate valid biometrics, and failures to validate correctly entered PIN’s or any other failure not relating to false documentation or incorrectly entered data (i.e., ≤ 0.5% False Rejection Rate). TWIC biometric reader system shall operate in less than 5 seconds from the moment a TWIC holder inserts his card (or waves his card if read by contactless means) to the time the gate system receives a pass/fail signal. The time includes reading a biometric signature and comparing that to the TWIC or a linked database. It also includes any time required to transmit or obtain information to/from a database. TWIC readers shall have a False Acceptance Rate (authenticate an improper credential/fingerprint) of less than 0.01% (i.e., false positives). TWIC readers shall have a Mean-Time-Between-Failure (MTBF) rate of less than 4 major failures per year. A minor failure is a failure to operate properly regarding any aspect of the device; but, is quickly returned to service by a reset, software reboot, or similar method. This shall occur no more than once per week. For purposes of calculating MTBF, four minor failures equal one major failure. A major failure is any failure that requires repairs on-site or off-site taking longer than 15 minutes to repair. TWIC readers shall have a Mean-Time-To-Repair of less than 72 hours. Major failures are used to calculate MTTR. TWIC mobile readers shall be able to withstand multiple drops from 4 feet to a concrete deck with no more than a minor failure. Ease of Operation. TWIC mobile readers shall be easily operated with very little training (less than 1-hour). Bidders shall provide three training classes at GPA designated times and locations within one month of delivery of the equipment. At a minimum, TWIC mobile readers shall incorporate large (2.5” x 2”), backlit, 16 bit color touch screens that are easy to read and operated even in bright glare along with an easy to use illuminated QWERTY keyboard. Software and Firmware upgrades shall be easily completed by GPA personnel in less than 4 hours. Positive or failed identification shall be provided within 15 seconds of a manual read event. TWIC mobile readers shall be equipped with a USB or Fire Wire connection for interface with a standard computer. Battery life shall last a minimum of 12 hours of constant use allowing no hard drive or screen sleep modes and shall be recharged within 8 hours. Extra rechargeable batteries and a charger for each unit supplied shall be provided to allow extended operation of the units to ensure the unit can be operated for 24-hours without failure. Rechargeable batteries must last a minimum of 1 year with use every day before requiring replacement (failing to meet section 2.3.12.6 above). TWIC mobile readers shall incorporate self-calibration features with report functions that are easy to use and understand. Existing equipment may be used as well as existing wiring, network equipment, sounders, computers, keypads, card swipes, etc. Equipment that will be reused shall be identified in the proposal. Existing biometric readers may be used as a trade-in allowance with a credit for such use shown in the proposal by the proposers. See Appendix 15 for a list of equipment. Reports. The ability to generate reports shall be built into the system to allow standard or manually designed reports to be automatically or manually generated. Standard reports shall include the following at a minimum: A list of who is on any one terminal at any one time. This report shall be available to run in real-time (who is on the terminal right now?) or historically (who was on the terminal yesterday at 1602?). A query identifying if a certain person(s) was on the terminal at any one time, including real-time. Access device status at any time (real-time or historically)? Counts of the number of people entering or on terminal, etc., at any one time (real-time or historical). A query shall identify a list of those personnel who have been denied access to GPA terminals, the reason for the denial, as well as the length of time for which the denial is in effect. A single report listing all modules, doors, readers, inputs and relays. A single report showing all cardholders and their details (including last known location). A list of all the Groups for which a Cardholder is a member. A list of all the Areas that a Cardholder may enter. A list of all the cardholders currently in a chosen area. A list of all the Groups that may enter a chosen area. It shall be possible to produce a list of all cardholders whose last known location was on-site, together with the location and time of entry. It shall be possible to produce this as a printed report, paginated so that it is suitable for handing out to several people for a roll call. The criteria for deciding where the page breaks occur shall be selectable; for example the area, or department, or muster point. It shall be possible to define event report templates that can be saved and re-used. These templates shall include selection and sorting criteria. Alarms. The alarms shall notify appropriate personnel as defined by GPA. Screen pops, emails, text messages, pages and phone calls are all methods that should be available. Each event shall be programmed individually to provide automatic alerts to certain personnel, including those in the camera monitoring room, the front desk of the GCT Admin Building, and other GPA fixed or mobile personnel as required. The process of alarm management shall use the concept of alarm zones, so that a single operation (manual or automatic) to arm the zone results in all objects in that zone being armed. It shall be possible to selectively define which objects, and which events for those objects, can generate alarms. It shall also be possible to define schedules that determine whether an event is an alarm or not, based on the time of day. Each alarm shall be capable of having a priority level (for example, from a range of 1-12) associated with it, and a set of instructions for the operator. When an alarm occurs it shall cause an immediate visual and audible signal to the operator. It shall be possible to associate a sound file with an alarm, and to cause a relay to be triggered anywhere in the system. A further consequence of an alarm shall be that it can trigger a camera and its PTZ preset co-ordinates. When an alarm has been notified, the operator shall be able to locate the object that raised the alarm on a site plan with a single operation. Where multiple alarms have been notified, but have not yet been adjudicated, the system shall prioritize the alarms to allow the operator to view either the highest priority or the most recent. Multiple alarms should also be grouped by area or event such that the group of alarms may be caused by the same event. The system shall allow mandatory actions to be programmed for certain alarms and require the operator to complete each step of the instructions associated with the alarm before the alarm is removed from the alarm list. It shall be possible to produce a report at a later date showing who performed each step, and when. It shall be possible to disable an alarm preventing certain alarms from generating until it is re-enabled. It shall be possible for an operator to acknowledge an alarm so other operators know the incident is being adjudicated. It shall be possible to see in a single display whether there are any alarms that have not been acknowledged or cleared. Site Plans. It shall be possible to create graphical representations of site layout. Background images may be produced using another software program and imported into the ACS software. It shall be possible to create multiple site plans, linked together so that the operator can easily jump from one plan to another – which may represent other terminals, a zoomed-in view or a zoomed-out view. It shall be possible to place objects on the plan, such as Areas, Doors, Readers, Inputs, Relays, and Cameras. Objects on the plan must provide information and permit control directly from the plan, without the need to leave the plan. Lowlight / High Vegetation Detection and Response At CI, water surrounds the island with a stand of trees between the fence line and the water. The main objective of the Low Light/High Vegetation Detection and Response system is to detect intruders before they reach the fence line. The requirements in Section 2.2 also apply to the Lowlight / High Vegetation Detection and Response subsystem; however, some specific requirements follow. Maritime Domain Awareness. The Low light system shall help camera monitoring room operators maintain general awareness of surrounding activities at all times. (What is happening outside the fence line?) The Low Light system shall provide camera monitoring room operators with a general awareness of the amount and types of ship/boater traffic in the surrounding waters and trees. The Low Light system shall help camera monitoring room operators identify if any activities outside the fence pose a threat to GPA operations Power and Data Transmission. Proposer shall provide adequate data transmission capabilities from the camera or groups of cameras to a server in the CI Command Center. SRIN and CIIN Add-ons. General Requirements. In addition to the requirements found elsewhere in Section 2, radar systems shall be used to enhance the maritime domain awareness of the SRIN and CIIN by providing useful information in meaningful ways that enhance the knowledge of the surface picture and correlate with other sensor technologies such as cameras and analytic systems. Radar systems shall integrate with the AIS transponder system. Radar systems shall integrate with camera surveillance systems including CCTV, electro-optics, infrared and thermal imaging. Radar systems shall allow automatic correlation between various sensor targets. Radar systems shall distinguish surface swimmers from waves and automatically track surface contacts. Radar systems shall operate at manned or unmanned sites. Radar systems shall be proven in operation at other locations. Radar systems shall be scalable in operation. Environmental Conditions. It is critical that any system fielded remain operational during any weather condition experienced in the area. In addition to the requirements established in Section 2.1.10, the following requirements shall be met: Radar systems shall remain operational (meet all specifications) in any sea-state condition. In lieu of the wind requirements established in Table 2, Radar systems shall operate in sustained winds up to 80 kts or gusts up to 100 kts. If shut down temporarily due to high wins, including hurricane force winds, as soon as the storm passes and winds die down to certified levels; the radar system shall be operational again through remote/automatic power up. Network. Radar systems shall be networkable and expandable so that additional equipment such as displays and scanners in other locations can easily be incorporated, either at the time of installation or at a later date if necessary, without disruption to the existing system. Any number of radars shall be viewable at any number of displays simultaneously. Recording. Radar systems shall be recorded using the same 30-day requirement as video recordings. In the event that an incident requires further investigation, the appropriate section of the file shall be archived securely onto a CD, memory stick, or other recordable device and be passed to other users for further analysis and to provide a permanent record of the event. Along with event recording, the system shall automatically record raw radar, tracks, CCTV, AIS and other integrated systems. Target Tracking. Radar systems shall track contacts automatically while distinguishing moving targets from fixed targets such as land masses or buoys and shall provide the following information for each contact: Target ID Location Course and Speed Track Alarms and status Track Quality Accuracy and Resolution. Radar systems shall provide accuracy and resolutions that can be correlated to other sensors, and at a minimum shall: Provide location accuracy within 5 meters or actual position within 1 minute. Provide speed accuracy within +/- 0.5 kts of actual speed within 1 minute. ,[object Object],Command and Control System Sensors. A command and control system shall be a stand-alone software suite or may be part of a subsystem such as an ACS or security camera system. Regardless of the genesis of the command and control system, it shall allow integration of numerous sensors and security suites including; but not limited to the following: Maritime Surface Search Radar Closed Circuit Cameras Infrared sensors Automatic Identification System (AIS) Transponders Underwater Intruder Detection Land-based Mobile Sensors Direction Finding Sensors Chemical/Biological Sensors Situational Awareness/Maritime Domain Awareness. The system shall be designed to provide maritime domain awareness. The system shall be fully configurable to any location and application. The system shall provide operate in all weather, day and night without degradation in capability. The system shall be scalable in area coverage by each individual operator. The system shall integrate and display radar, EO and IR sensor technology. The system shall be capable of utilizing mobile and fixed sites for sensors. The system shall provide a shared, coordinated area picture along with a graphic representation in 3-dimensions. The system shall be capable of providing fixed or mobile areas for alert and alarm that are adjustable by the operators. The system shall track history, route prediction and behavior monitoring. The system shall Identify, evaluate and prioritize potential threats. The system shall calculate distance, speed, time and heading for timely and appropriate responses. The system shall provide configurable security levels. The system shall allow automatic, preprogrammed action and response as well as operator checklists. GIS Functionality. The system shall provide GIS functionality that can be easily manipulated by the operators and can share information with other GIS systems such as SAGIS. GIS functionality shall be used to display and edit the various overlays. GIs functionality shall be used for analysis and to support for decision-making. The system shall provide a common and accurate picture of any situation using real-time geographical presentation with maps, topology and global positioning system (GPS) presentations of vehicles and individuals. Flexible, modular architecture shall provide an easy implementation of any desired non-standard features without changing the entire application or solution. Dispatch/Response. The system shall provide a Computer-Aided Dispatch (CAD) system giving operators the tools they need to field calls, create and update incidents, and manage an organization's critical resources by providing real-time interaction of crucial data. The system shall allow operator to make web/data searches from within the system. The system shall provide on-site or remote access to the CAD system, allowing first responders and security personnel to access live operational information and the ability to search for historical data on incidents and resources. The system shall integrate voice and d

REQUEST FOR PROPOSAL PROCEDURES

Recomendados

Recomendados

Más contenido relacionado

Destacado

Destacado (6)

Similar a REQUEST FOR PROPOSAL PROCEDURES

Similar a REQUEST FOR PROPOSAL PROCEDURES (20)

Más de butest

Más de butest (20)

REQUEST FOR PROPOSAL PROCEDURES