Pro-Watch Software Suite Architect and Engineering Specifications Revision 3.7.0 Ed.
Contents 1 General................................................................................................. 5 1.1 2 Summary ................................................................................................................... 5 1.1.1 References..................................................................................................... 5 1.1.2 System Overview.......................................................................................... 6 Products ............
2.1.13 Compliance and Validation........................................................................ 16 2.1.14 Clean Room Solution …………………………………………………….17 2.2 2.3 2.4 Operational Requirements....................................................................................... 18 2.2.1 System Operations ...................................................................................... 18 2.2.2 Access Control Functional Requirements................................................... 28 2.2.
3 4 2.8.3 E-Mail ....................................................................................................... 159 2.8.4 Stentonfon Intercom Interface .................................................................. 159 2.8.5 VISTA-128FBP and VISTA-250FBP controllers ............................. 160 2.8.6 Visitor Management System (VMS)……………………………………165 Execution ......................................................................................... 171 3.1 Examination ............
. 4 Ed.
1 General 1.1 Summary The intent of this document is to specify the minimum criteria for the design, supply, installation, and activation of the Security Management System, hereinafter referred to as the System, which shall be a modular and network enabled access control system.
1.1.1.5. Federal Information Processing Standard (FIPS): • • 1.1.2 Advanced Encryption Standard (AES) (FIPS 197) FIPS 201: Personal Identity Verification (PIV) of Federal Employees and Contractors System Overview The Security Management System shall integrate access control, alarm monitoring, CCTV, digital video, video badging, and database management.
• Database partitioning shall provide the option to restrict access to sensitive information by user ID. 2 Products 2.1 System Software Requirements The system shall be a modular and network enabled access control system. The System shall be capable of controlling multiple remote sites, alarm monitoring, video imaging, video badging, paging, digital video and CCTV switching and control that allows for easy expansion or modification of inputs and remote control stations.
2.1.3 • • Microsoft® Certifications A Microsoft® Gold Certified Partner shall develop the System software. Microsoft Gold Certified Partners meet a higher set of criteria for each category, including enhanced certification and a portfolio of real-world customer references, and are thus identified as the most skilled partners in specific solution areas.
• • • • Ensure compatibility with the High Contrast option Provide documented keyboard access to all features Expose the location of the keyboard focus Not place shortcuts to documents, help or uninstall in the Start Menu Microsoft Windows 2000 Professional Unique Certification requirements: 2.1.3.
• Win32 clients running in the context of a trusted domain account must support Single Sign-On. 2.1.4 Security Key The System shall only require a single security key dongle to be present on the database server for the System to operate. Security keys shall not be required at the client workstations. The System shall allow a user to read the information that is programmed on the server security key dongle.
supports a “generic channel” capability that allows customized interfaces to previously unsupported third-party devices. • Integrated badge, hardware and permission wizards reduce the number of clicks required to configure and deploy a system. • Hand geometry template storage and administration through application. • Multiple database partitioning provides a higher level of security by allowing the system administrator to restrict access to sensitive information by user ID.
• • • • • • • • • • • • • • • • • Certified for Microsoft Windows 2000 Professional and Server Leverages existing network infrastructure by using standard network protocols to communicate to all system hardware CHIP hardware protocol support (communicates to existing Honeywell’s Star II series controllers) PW series hardware protocol support (communicates to existing Honeywell’s PW2000, PW-3000, and PW-6000 series controllers) SEEP hardware protocol support (communicates to existing Honeywell’s Star I, 4
2.1.5.3 Corporate Edition Corporate Edition shall be provided for more demanding security management applications. The System shall operate in the Windows 2000 server environment and utilize SQL 2005 as the database engine. In addition to the features listed for the Professional Edition, Corporate Edition shall also include the following features and benefits: • • • • • 2.1.5.
• • • • • • • • • 2.1.6 Existing Corporate Edition system shall be easily integrated into an Enterprise Edition without loss of data or history. The System shall provide one central cardholder and badging file so that an operator in any region in an Enterprise shall have the capability to view and modify cardholder data and grant or deny access enterprise-wide.
2.1.8 Relational Database Management System The System shall support industry standard relational database management systems. This shall include relational database management system Microsoft SQL Server 2005. 2.1.
2.1.10 OLE-DB The System shall utilize Microsoft’s OLE-DB object-oriented, database access method. Microsoft’s OLE-DB method shall provide support of not only relational databases, but also to “hierarchical data sets” such as Microsoft Exchange stores and XML record sets. OLE-DB shall allow easier integration of disparate data sources. 2.1.11 Unicode The System shall utilize Unicode worldwide character set standard.
2.1.14 Clean Room Solution 2.1.14.1 Overview The System shall provide a clean room solution which enables users to manage their “Clean Environments” or other areas requiring special restricted access through a process oriented graphical user interface. The clean room solution shall provide tools that enable security directors and technical review boards to audit and implement complex human work flows in ultra clean environments or other areas.
rooms shall be defined through cardholder Clearance Codes. The System shall provide a “Cards” tab which shall display the Access Allowed column. This column shall indicate which valid cardholders currently have access to the clean room selected at the top of the screen. The System shall provide two methods to manage the Access Allowed column (select or deselect the checkboxes): • Manual—The user shall have the capability to click the checkbox to select and de-select.
administrator to login over a restricted class user to perform a function on the System that the current user does not have permission to perform. This provides a level of security in that the user’s workstation shall never need to go offline or be unattended. 2.2.1.
• • • • • 2.2.1.7 • • 2.2.1.8 • side of the screen. Selecting this box shall bring all system readers to view for tour selection. Once a logical device has been selected, a dialog requesting the ‘Time’ required reaching designation shall appear. This entry shall be in military format (00:00) and represents the amount of time required to reach each checkpoint. After the ‘Time’ has been entered, the tolerance needs to be entered, the ‘+’ and ‘-’ values shall be defined.
• support the addition and deletion of items to the partitioning scheme as required. The System shall be capable of limiting an operator’s access to one, or multiple partitions.
2.2.1.9 Status Groups The System shall support a real-time system status monitor that graphically depicts all logical devices. The Status Groups window shall be a split window with logical device icons displayed in the upper portion and the Device Types associated with a selected logical device displayed in the lower portion. The Status Groups shall be available in the hardware configuration view and the alarm monitor view. 2.2.1.9.
2.2.1.9.
2.2.1.10 Keyboard Accelerators The System shall allow the user to use a shortcut key to enable designated system commands. The System operator shall have the capability to set up accelerators for two options: Commands and Event Procedures. The operator shall have the capability to add, edit, and delete accelerators for commands and event procedures, as well as grant or revoke user access to these options.
input points along the pathway to the office will be masked and the output point activated. If the user attempts to access any areas other than the Pathway, an alarm will be generated. After a set number of minutes have elapsed, the input points shall be un-masked and the output point deactivated. The Pathway shall have the capability to be deactivated before the elapsed time if another card is configured to “stop” a Pathway in progress. Systems that do not provide Pathway programming shall be unacceptable.
assigned to users or user classes, including single or multiple groups. Each item in the routing group shall be associated with a time zone, which shall control when the routing group is valid. For example, a specific workstation shall be a valid target for routing after 6:00 pm. Events from a specific facility (channel) shall be routed to a different set of operators during the day and certain kinds of events shall be routed to a different set of operators on the weekend.
a door unlock time of 10 seconds, this produces a 20 second window of opportunity. If only one valid card is presented or if too much time elapses between swipes, the door shall not unlock and an access denied message shall be generated. The “Two Person Rule” feature shall be selected for all doors controlling entry to and exit from the specified area. 2.2.1.19 Occupancy Restrictions The System shall allow the user to define the minimum and maximum occupancy allowed in a designated area.
being reprogrammed for any other desired functionality if a request to exit device is not required. Systems that do not provide this capability shall be unacceptable. Modifications can be made to templates after creation, where users will have the ability to select if the changes are to be applied to existing logical devices using the resource buttons Yes, Yes to All, No, and No to All. 2.2.
The following requirements shall apply: • • • • 2.2.2.3 Holiday name: Shall be at least 24 characters. Holiday description: Shall be at least 40 characters. Date: Shall be the date on which the holiday falls. Type: Shall define holiday type 1, 2, or 3. Response Codes The System shall allow the user to enter a predefined code to represent a response to an alarm occurring in the facility. The following requirements shall apply: • • 2.2.2.4 Response code name: Shall be at least 10 characters.
• • Clearance code download schedule: Shall allow the user to download the data at a later time and schedule a date and time. The dialog box shall include the date, time, and number of cards. It shall also be possible to edit or remove the date and time. The System shall provide the ability to create clearance codes that can have predetermined automatic expiration. The Clearance Code screen shall provide a checkbox to select “Never Expires” if the selected time zone will always remain in effect.
2.2.2.5 Companies Each badgeholder entered into the System shall be assigned a company code identifying the individual’s employer. The Company Information dialog box displays and maintains information related to companies having access to the facility. The following requirements shall apply: • • • • • • • • • • • • • • • 2.2.2.6 The user will have the ability to search by a Company Code name and to define search criteria. The desired Company name may then be selected for editing from the “short” list.
access function shall limit access to a group of cardholders, overriding all other access criteria. The group access shall have a start and stop time/date along with the assigned logical devices (Type Door). The System shall support Multiple Logical Devices (Type Door) to be assigned to one Group Access Project. A Group Access Project shall be assigned to a card on the Card Information Screen of the Badge Viewer. 2.2.2.
• Time: Shall indicate the time this trigger would have to occur for the event to happen. • Group Code: Shall display the group code associated with the group of doors or alarms that will trigger the event. • Clearance Code Cards: Shall display the cards assigned this clearance code that will trigger this event. • Type of Transaction: Shall display the type of transaction that would cause the event to occur. • Time Zone: Shall indicate the time zone during which the trigger is enabled.
o 2.2.2.8 • De-activate output point. The command issued for the System to perform Parameters 1 and 2 shall be from the event processor parameters. Alarm Pages Application shall include the capability to create an unlimited number of customized alarm pages for the alarm monitor and each shall be assignable to users and user classes. The following information shall be individually configured for each alarm page: • • Alarm description: Shall provide a brief description of the alarm type.
• • • • • • Re-issuance frequency: Shall indicate (in minutes), how often alarms shall re-issue if the alarm state continues. Global shunt status: Shall indicate whether alarms are shunted, overriding the individual alarm shunt status, or are armed or shunted on an alarm-by-alarm basis. Auto clear field: Shall indicate whether an alarm will be automatically cleared from the alarm monitor or “normal” operation for this alarm type shall occur.
• • represent the resources associated with the System devices. The icons available for positioning on the alarm map shall include logical devices, groups, maps, and CCTV cameras. The user shall have the capability to add and edit a resource, display resource text, and clean up a resource. The lower portion of the Map Resource dialog box shall allow for the definition of the icon position within the selected map.
• Badge Information window: This window shall allow the user to search for badgeholders in the System that meet certain search key information. The badge information window shall be divided into three sections: Top (Search Field) section: Shall select the fields that will be returned in the search results area. o Middle (Search Key) section: Shall initiate a search for badge or card records. o Bottom section: Shall list the results of a search.
• • • • • • • • • Unique card number between 1–15 digits in length. Badge type as defined in the Badge Maintenance application. The company code associated with this particular card. The card shall take on the default access/clearance codes for this company. Date the card was issued. Date the card will expire shall including month, day, and year. Last date and time the card attempted access. Door ID of the last door the cardholder attempted to access with this card.
o o o • Brass Keys: Shall be assigned to badgeholders on the Brass Keys property sheet on the Badge Maintenance dialog box. When added, they shall appear on the brass key list on the property sheet.
• • • The System shall provide a minimum of 37 default badge fields. Each field shall be displayed in a grid in which the each of the attributes of the field is displayed in a separate column. Fields marked as “true” in the user-defined field shall have the capability to be deleted as desired; those marked “false” shall be system fields that shall not have the capability to be deleted.
• • • • Short - Select to create a field, which can hold an integer from 0 to 67,535. Time - Select to create a time field. User defined - Selection of this datatype shall create a pick list from which the badging user can select predefined values. The System shall support Badge Field pick-list definitions. For example: Badge eye color pick-list may be user defined to include brown, blue, green, hazel, gray, etc. The values are defined by selecting the “Edit User Defined Values” button.
• The toolbar buttons shall include: o o o o o o o o o o o • • • • • Save: Saves Badge Designer settings. Exit: Exits from Badge Designer. Idle: Selects one or more Badge Designer items. Place Text: Inserts text into Badge Designer. Place Bitmap: Inserts bitmap image into Badge Designer. Place Photo: Inserts photograph into Badge Designer. Place Barcode: Inserts bar code into Badge Designer. Place Shape: Places shape into Badge Designer layout.
• The System shall support data from the badge field database to be linked directly to the record holder and visible in a barcode output.
o o o o o o o 2.2.2.13.4 Show Spacer: this option shall display the space before and after the barcode data. Switch Text: this option shall switch the top and bottom text. Check Digit 2: this option shall provide for error checking. Arial: this option shall designate the text font type. Courier New: this option shall designate the text font type. Bold: this option shall designate the text font type. Italic: this option shall designate the text font type.
2.2.2.13.5 Layering Badge Items The System shall allow the user to properly layer badge layout items within a selected layout. 2.2.2.13.6 Badge Profiles The System shall allow the user to add, edit and delete Profiles that establish control information for the access page, partition page, assets, and searchable card fields. Profiles shall include an Auto Disable Card function, which automatically voids a card if a defined timeframe has elapsed without a card read.
The System shall provide “live trace” functionality which provides the ability to select an event defined as the “selected event.” The System shall invoke and visualize all live events associated with the “selected event,” specifically providing a streaming event capability. Live trace functionally shall be available only if the “selected event” has an associated logical device or badgeholder.
The Trace-on feature shall be accessible from a drop-down menu item. The System shall present a window where the user can enter a card number or select a logical device. The System shall provide Historical Trace functionality with the ability to select an event defined as the selected event. The System shall invoke historical events associated with the selected event.
• • Modifying user information: Information related to a user shall be modified on dialog boxes, which are accessed from the Main User Maintenance dialog box. User Maintenance application: Shall allow a user to be added, modified, partitioned, or deleted. User information shall be in addition to that defined for the user’s class. This information shall include, but not be limited to, the following: o o o o o o o o o o o ID name: Shall be at least 10 characters.
• • • Standard Relay Output Selection: The ability to program predefined readers and relay outputs through device templates which will allow assignment of devices for floor control. Relay Output Selection with Floor Select: The ability to program predefined readers, inputs, and relay outputs through device templates which will allow assignment of devices for floor control with selection lockout abilities.
• Mustering 2.2.2.16.2 Badge holder Reports • • • • Area Attendance Badgeholder Detail Badgeholder Summary Key Assignment List 2.2.2.16.3 Company Reports • • Company Clearance Code Company Summary 2.2.2.16.
• • • • • • • Panel Types Partitions Printers Response Codes Routing Groups Time Zones Workstations 2.2.2.16.5 Logging Reports • • • • Database Audit Log Compliance and Validation Event Log Operator Log 2.2.2.16.
Provide feature to generate a history report for system operator activities. Activities shall be at least, but not limited to, acknowledged transactions, database file modification, and comments made to alarm events. Provide complete database reporting of all data programmed into the System data files. 2.2.3 2.2.3.1 System Administration Tape Backup The System server(s) shall utilize a tape backup system for backup and archiving capabilities.
• • The System shall provide option buttons to specify a data source: o Delimited: Data in a text file, individual fields separated by I-vertical bars, commas or tabs. o Fixed: Data with a fixed length shall allow import but cannot export fixed length data. o SQL server native database driver o ODBC (Open Data Base Connectivity): An Application Programming Interface (API) that allows import from and export to a database.
o System Key Identifier. This is the System data field that maintains the keys of the external system. This shall be used to determine if a record shall be an Update or Insertion. o System Database Location. This shall display the read-only fields that shall be enabled when a System Key Identifier is entered. The first field shall display the name of the database table and the second field shall display the name of the database column in that table to which the data shall be transferred by DTU.
• • In addition, depending upon the data source type, additional tabs shall be provided to configure the import procedure: o Data files tab shall provide the location of the data source and option buttons for which files are desired to be loaded, including: Load all files in Directory, Load only the file with the following name, Load all files that match the following naming pattern. Selecting this option will load all the files that match the specified naming pattern.
2.2.3.4 • • • Generic Channel Interface The System shall provide the ability to define generic communications channels over serial port or TCP/IP network socket including IP address and port/socket, to support custom integration of external foreign devices. The System shall generate events based on data received from the channel matching operator pre-defined instructions. The System shall allow the user to define a Channel Description and provide an Installed checkbox.
Poll String shall be enabled to poll an unsupported hardware device. The required Poll String for the unsupported hardware device shall be found in the associated Technical Manual. The user shall have the capability to define inbound messages in the standard event definition screen to define the translation string from the generic device. The translation string shall be a string of ASCII and control characters, which acts as triggers for the event when detected in the input stream.
2.2.5.3 Unacknowledged Alarms The unacknowledged alarms log will allow users to control items that are currently being dumped into the UNACK_AL. The ability to control what data is being inserted is important as a large majority of customers are not utilizing the alarm monitoring functionality. The ability to have the information easily truncated will be advantageous for smaller MSDE systems where database size limitations exist. A new resource will be placed on the left pane of the Administration Viewer.
2.3 Hardware Requirements 2.3.1 Hardware Support The System shall support, at a minimum, three separate manufacturer’s hardware panel platforms simultaneously. System hardware shall support: • • • • • • • • • • • 2.3.2 2.3.2.1 • 2.3.2.
2.3.2.3 • Corporate Edition • System server shall support Microsoft Windows 2000, 2003, and XP and SQL Server 2005 MSDE. Corporate Edition server activity levels: • o LCS - Low Activity Corporate Site (less than 10,000 transactions per day) o MCS - Medium Activity Corporate Site (less than 50,000 transactions per day) o HCS - High Activity Corporate Site (more than 50,000 transactions per day) Refer to Section 4 for minimum CPU requirements. 2.3.2.
2.4 Field Controllers 2.4.1 System Controllers The security management system shall be equipped with access control field hardware required to receive alarms and administer all access granted/denied decisions. All field hardware shall meet UL requirements. The supported field hardware will include, but not be limited to, the following components: 2.4.1.
o Embedded Web Server—The IC shall include embedded Web Server for ease of configuring key hardware attributes. - Web Server shall be password protected with specific user account. - User names and passwords for Web Server access shall be downloadable from the host. - Web Server shall optionally be disabled. On by default, off by option. o • • • • o o o o Communications—The IC shall include a primary and a secondary port for the purpose of communication to the host computer.
o • o Readers Capacities—Reader functionality and connectivity will be achieved through reader modules, and not directly to the IC. The IC will, however, support at a minimum the following: • Up to 8 card formats and facility codes • Multiple card technologies • Biometrics interface support • Smart card interface support • Integration with other manufacturers’ card readers • Issue code support for both magnetic and Wiegand card readers • Up to 8 digit PIN codes.
o 2.4.1.2 Electrical Power—Primary input power shall be 12 VDC +/- 10% @ 400 mA with an operating range of 10 VDC to 16 VDC. The IC shall be equipped with an uninterruptible power supply (UPS) and backup battery. Single Reader Module (SRM) The SRM shall provide an interface between the IC and the card readers. The SRM shall operate with any card reader that produces a standard Wiegand (Data 1/Data 0 or Clock and Data) communication output.
• Input power shall be 12 VDC +/- 10% @ 400 mA with an operating range of 10 VDC to 16 VDC. . 65 Ed.
2.4.1.4 Alarm Input Module (AIM) The AIM shall monitor all System alarm inputs. The following requirements shall apply: • • • • • • The AIM shall provide up to 16 supervised alarm inputs to monitor and report fault conditions (open, short, ground, or circuit fault) alarm conditions, power faults, and tampers. Upon alarm activation, the associated alarm condition shall be reported to the IC and subsequently to the System alarm monitoring workstation.
defaults as request-to-exit device for door #1, etc. Systems that do not allow for user definition of all input points shall be unacceptable. 2.4.1.5 Relay Output Module (ROM) The ROM shall incorporate 16 output relays that are capable of controlling a corresponding output device upon any input activation or on command from the System. Relay outputs shall be capable of responding to: • • • • Input alarms from within the same IC. Commands from a System operator.
2.4.1.6.1 Contactless Smart Access Control Readers Provide OmniAssure™ Contactless Smart Card readers as shown on the drawings. Card readers shall be “single-package” type, combining controller, electronics and antenna in one ROHS compliant package in the following configurations: 2.4.1.6.1.1 OT30 – 13.56 MHz ISO14443-4, DESFire, FIPS 201/PIV II (end-point), FRAC, TWIC, CAC Contactless Reader a.
f. Read/write compatibilities: 1) The reader/writer shall comply fully with ISO14443 parts 1, 2, 3, and 4 open card standards to fully enable interoperability among suppliers of similar products. 2) The reader/writer shall conform fully to ISO14443 Part 3 - Anti-collision and Transmission Protocol and must be capable of identifying multiple credentials in a single field and defining a common command set. 3) The reader/writer shall operate in the 13.56 MHz high frequency band only.
3) ISO7811 Clock & Data ABA track 2 emulation port, for connection to standard control panels requiring mag stripe interface. i. The reader/writer shall provide the functionality of the following operational modes: 1) Internal control: Read-only access control applications, transmitting Wiegand Data or Clock & Data j. Reader updates: 1) The contactless smart card reader shall provide the ability to change operational features in the field through the use of a factory-programmed CONFIG card.
2) Cable type: 5-conductor (with overall shield). 3) Standard reader termination: terminal block n. Warranty of contactless smart card readers shall be lifetime against defects in materials and workmanship. o. Contactless smart card reader shall be Honeywell OT30 with optional IEMOUNT U.S. gangbox mounting kit and optional IETAMPER tamper kit. 2.4.1.6.1.2 OT31 – 13.56 MHz ISO14443-4, DESFire, FIPS 201/PIV II (end-point), FRAC, TWIC, CAC Contactless Reader + 125 kHz Prox Reader (SmartTRANS) a.
d. The reader/writer shall conform to UL 294, and shall be FCC and CE certified, and shall conform to the following ISO Standards: ISO14443 parts 1 thru 4 type A and B (read/write). e. The reader/writer shall support the HSPD-12/FIPS 201/PIV II, TWIC, and FRAC card ISO14443 platforms. f. Read/write compatibilities: 1) The reader/writer shall comply fully with ISO14443 parts 1, 2, 3, and 4 open card standards to fully enable interoperability among suppliers of similar products.
g. Security keys in the credentials and reader/writers shall be required to match, and may be customized for individual sites. h. The reader/writer shall provide the functionality of the following communication ports: 1) Wiegand port, for connection to standard access control panels 2) RS232, RS422, or RS485 port, for connection to PCs or access control systems, either individually or on a multi-drop bus.
1) Operating temperature: -4 to 140°F (-20 to 60°C) 2) Operating humidity: 5% to 95% relative humidity non-condensing 3) Weatherized design suitable to withstand harsh environments m. Contactless smart card reader cabling requirements shall be: 1) Cable distance: (Wiegand): 500 feet (150m) at AWG 18 or 200 ft #22 AWG 2) Cable type: 5-conductor (with overall shield). 3) Standard reader termination: terminal block n.
4) The reader/writer shall be of potted ABS material, sealed to a rating of IP67. 5) The reader/writer shall have separate terminal control points for the green and red LEDs, and for the audible indicator. 6) The reader/writer shall have an audio transducer capable of producing tone sequences for various status conditions. d. The reader/writer shall conform to UL 294, and shall be FCC and CE certified, and shall conform to the following ISO Standards: ISO14443 parts 1 thru 4 type A or B (read/write). e.
7) The contactless interface of the reader shall support bit rates of fc/128 (~106 kbits/s), fc/64 (~212 kbits/s), fc/32 (~424 kbits/s) and fc/16 (~847 kbits/s) as defined in ISO/IEC 14443-3:2001/Amd.1:2005 8) The reader/writer shall support MAD (Mifare Applications Directory) for ISO14443 Mifare credentials. g. Security keys in the credentials and reader/writers shall be required to match, and may be customized for individual sites. h.
l. Contactless smart card readers shall meet the following electrical specifications: 1) Operating voltage: 4.5-16V UL approved regulated linear power supply recommended. 2) Current requirements: (average/peak) 125/167 mA @ 12 VDC m. Contactless smart card readers shall meet the following environmental specifications: 1) Operating temperature: -4 to 140°F (-20 to 60°C) 2) Operating humidity: 5% to 95% relative humidity non-condensing 3) Weatherized design suitable to withstand harsh environments n.
c. Contactless smart card readers shall meet the following physical specifications: 1) Dimensions mullion: 5.59” x 1.81” x 0.98” (14.2 x 4.62 x 2.5 cm) 2) cm) Dimensions with U.S. gangbox mounting kit: 5.59” x 2.87” x 1.1” (14.2 x 7.32 x 2.8 3) Color: Silver gray 4) The reader/writer shall be of potted ABS material, sealed to a rating of IP67. 5) The reader/writer shall have separate terminal control points for the green and red LEDs, and for the audible indicator.
5) The reader/writer shall require that a card, once read, must be removed from the RF field for two seconds before it will be read again, to prevent multiple reads from a single card presentation and anti-passback errors. 6) The reader/writer shall be capable of reading access control data from any ISO14443 part 4 type A or B compliant contactless credential, and transmitting that data in SIA standard Wiegand format.
1) The contactless smart card reader shall provide the ability to change operational features in the field through the use of a factory-programmed CONFIG card. CONFIG card operational programming options shall include reader output configurations, LED configurations, reader keys, card memory locations and keypad configurations. 2) The reader shall have flash memory to allow future feature enhancements to be added in the field.
2.4.1.6.1.5 OT70 – 13.56 MHz ISO14443, FIPS 201, FRAC, TWIC Reader (SmartTOUCH) a. Provide mullion or single-gang mounting style contactless reader/writers for door frame mounting, non-metal wall mounting, non-metal vehicle stanchions and non-metal pedestals, and where shown on plans. b. The reader/writer optional single-gang mounting kit shall be designed for U.S., European and Asian electrical back boxes having a mounting hole spacing of 52-60 mm. c.
1) The reader/writer shall comply fully with ISO14443 parts 1, 2, 3, and 4 open card standards to fully enable interoperability among suppliers of similar products. 2) The reader/writer shall conform fully to ISO14443 Part 3 - Anti-collision and Transmission Protocol and must be capable of identifying multiple credentials in a single field and defining a common command set. 3) The reader/writer shall operate in the 13.56 MHz high frequency band only.
3) ISO7811 Clock & Data ABA track 2 emulation port, for connection to standard control panels requiring mag stripe interface. j. The reader/writer shall provide the functionality of the following operational modes: 1) Internal control: Read-only access control applications, transmitting Wiegand Data or Clock & Data k. Reader updates: 1) The contactless smart card reader shall provide the ability to change operational features in the field through the use of a factory-programmed CONFIG card.
3) Standard reader termination: terminal block o. Warranty of contactless smart card readers shall be lifetime against defects in materials and workmanship. p. Contactless smart card reader shall be Honeywell OT70 with optional IEMOUNT2 U.S. gangbox mounting kit and optional IETAMPER tamper kit. 2.4.1.6.1.6 OT75 – 13.56 MHz ISO14443-4, DESFire, FIPS 201/PIV II (end-point), FRAC, TWIC, CAC Contactless + Keypad Reader (SmartTOUCH PIN) a.
e. The reader/writer shall support the HSPD-12/FIPS 201/PIV II, TWIC, and FRAC card ISO14443 platforms. f. The reader/writer shall support the storage of biometric templates on smart cards for Mifare Classic and DESFire. g. Read/write compatibilities: 1) The reader/writer shall comply fully with ISO14443 parts 1, 2, 3, and 4 open card standards to fully enable interoperability among suppliers of similar products.
i. Security keys in the credentials and reader/writers shall be required to match, and may be customized for individual sites. j. The reader/writer shall provide the functionality of the following communication ports: 1) Wiegand port, for connection to standard access control panels 2) RS232, RS422, or RS485 port, for connection to PCs or access control systems, either individually or on a multi-drop bus.
2) Operating humidity: 30% to 80% relative humidity non-condensing 3) Weatherized design suitable to withstand harsh environments o. Contactless smart card reader cabling requirements shall be: 1) Cable distance: (Wiegand): 500 ft (150m) at AWG 18 or 200 ft at AWG 22. 2) Cable type: 5-conductor (with overall shield). 3) Standard reader termination: terminal block p. Warranty of contactless smart card readers shall be lifetime against defects in materials and workmanship. q.
The reader style and finish shall be selected from the manufacturer’s product list as shown on the installation documents. • • • 2.4.1.6.5 Power: 5 VDC supplied by the controller shall power the reader. Electronics: The reader electronics shall be encapsulated for environmental security. Encoding: The reader shall recognize several encoding formats. Barcode readers Barcode readers shall be provided.
• • • • 2.4.1.6.7 Hidden mounting screws deter vandalism Potted for superior weather resistance Selectable Wiegand, Clock & Data, or serial output The reader shall include three covers included with every reader; black, charcoal and ivory Fingerprint Reader The System shall support the Precise BioAccess™ plug and play fingerprint reader for areas that require heightened security. The unique Precise BioMatch technology provides reliable one-to-one matches to verify that people are who they claim to be.
create biometric templates during the cardholder enrolment process. The System shall support reader template storage at the intelligent controller gateway module. 2.4.1.6.9 Keypads (5 wire type) The keypad shall be of piezoelectric construction. The reader style and finish shall be selected from the manufacturer’s product list as shown on the installation documents. The reader shall support at a minimum the following key features: • • • • 2.4.2 LEDs shall provide a visual acknowledgment of a valid code.
• • • • o Downloading of System Parameters • • • • • o Event Privilege Level InXit Status Executive Privilege User-defined PIN codes Facility Code Upload Enable Time Zone Enable Flags Card Events, Time Zones, and Holidays Controller Time and Date Downloading of reader parameters • • • • • • Reader type Card Type Reader Time Zone Access Times Warning Times Input/Output Linkage o Downloading of input point parameters • Soft Alarm Parameters • Arming/Shunting of Alarm Input Points • Point Type • Enabled
• Output Groups 2.5 Enclosure • • • Cabinet: The controller enclosure shall be a NEMA Type 1 cabinet suitable for wall mounting, with knockouts. The cabinet shall have a hinged cover, tamper switch, and key lock. Dimensions: The dimensions shall not exceed 15” (35.56 cm) in height, 14.2” (40.64 cm) in width, and 7.6” (10.16 cm) in depth. Capacity: The enclosure shall hold up to 9 control modules, a 4 A power supply and a self-contained replaceable backup battery. 2.
o o o Operating Temperature: The System shall be designed for an operating temperature of 36° to 109°F (2° to 43°C). Humidity: The System shall be designed for normal operation in an 85% relative humidity, non-condensing environment. Electromagnetic Interference: The System shall meet or exceed the requirements of FCC Part 15, Class B devices, FCC Part 68, IEC EMC directive. . 93 Ed.
2.8 System Interfaces 2.8.1 Analog CCTV Switchers The System shall include CCTV integration. The matrix switcher capability support of the System shall include camera call up, monitor switching, CCTV command support, and PTZ support. The CCTV subsystem shall be the controller device for CCTV cameras, monitors, and videocassette recorders (VCRs), and shall associate camera inputs with monitor outputs.
• • • • • • • 2.8.1.2 Characters: Shall be the minimum number of characters to be read from a CCTV subsystem at one time. Time: Shall be the amount of time, in tenths of a second, allowed to read a message from the node. Communications break tests: Shall be the number of seconds between communication break tests on the line to which the CCTV device is connected with the server.
• 2.8.1.3 Map identification number: Shall be the number of the map to be displayed in the Map Manager application should this camera be activated. CCTV Monitor Views The System shall allow the user to create and assign CCTV monitors for switching purposes. The user shall be able to add, edit, delete, and partition CCTV monitors.
• Integral Technologies DSXpress Series digital recorders The System shall provide fully integrated support for a powerful digital video recording and transmission system. The DVRS shall be an extremely secure and flexible digital storage management tool. The System shall record, search and transmit video, and shall provide users with both live and post event assessment capabilities. The DVRS shall be seamlessly integrated with existing video equipment and incorporated into any TCP/IP network.
with Honeywell’s video analytics and IDM (Integrated Data Manager) applications. As a software-based enterprise-level video, and data management system, HVMS provides a single GUI that monitors, records, and offers analysis functionality to deliver the timely, accurate information required for effectively responding to any challenge. HVMS is a fully scaleable enterprise-class media management system.
B. SYSTEM (APPLICATION) PERFORMANCE HVMS shall include, as a minimum, the following features, functions and specifications: 1. HVMS must be protected by the most extensive support services in the industry, including customer service, pre-sales applications assistance, aftersales technical assistance, access to technical online support, and online training using Web conferencing. The manufacturer shall provide 24/7 technical assistance and support via a toll-free telephone number at no extra charge. 2.
Matrix Switcher – These are analog matrix switchers. 7. There shall be more than one IP engine/DVR connected to HVMS. One IP engine shall have more than one camera server depending on the number of cameras in the System. On an average with video motion detection disabled, one camera server shall cater to 25-32 cameras based on end user configuration requirements. 8. There shall be more than one switcher connected to HVMS. 9.
Honeywell’s VideoBloX Series Honeywell’s MAXPRO Series 10. The number of recorders and switchers shall be scalable within a network to handle any size installation. 11. The HVMS application shall have the following major capabilities: a. Live viewing of up to 64 cameras on a single workstation with up to 4 monitors set up at CIF resolution. For D1 resolution, the number of live streams needs to be benchmarked based on client hardware configuration deployed. b.
12. This document details the specifications only for the Honeywell IP engine. For other recording systems (i.e., Rapid Eye, Fusion, Enterprise, etc.), please refer to the respective A&E specs The Honeywell IP engine NVR system shall include: Redundant database servers Camera servers Network connected cameras or network connected camera encoders 13. Database Server - The database server contains a database of all networkconnected cameras and their configurations.
Receive camera control commands from HVMS workstations and then send the commands to cameras Store live video to hard disk Transmit previously stored video to HVMS workstations Archive previously stored video to off-line storage media Retrieve archived video from off-line storage media The camera servers shall rely on the database server for all camera database information. The IP engine shall support multiple camera servers, with no limit to the number of camera servers. 15.
s. AXIS Communications 232D t. AXIS Communications 2400 u. AXIS Communications 2400+ v. AXIS Communications 2400+ Blade w. AXIS Communications 2401 x. AXIS Communications 2401+ y. AXIS Communications 2400+ Blade z. AXIS Communications 240Q aa. AXIS Communications 2411 bb. AXIS Communications 241S cc. AXIS Communications 241SA dd. AXIS Communications 241S Blade ee. AXIS Communications 241Q ff. AXIS Communications 241QA gg. AXIS Communications 241Q Blade hh. AXIS Communications 2420 ii.
Recorders Configuration – This shall provide an option to add/edit/delete recorders such as IP engine, Rapid Eye, Fusion, Enterprise, etc. Camera Configuration – This shall provide an option to add/edit/delete cameras and associate to a particular recorder or switcher and map to a particular site, partition or event group. Cameras need to be added manually for IP engine, whereas for other recorders cameras are automatically discovered.
Port Configuration – This shall provide an option to add/edit/delete devices to the ports available on the controller. These devices shall be keyboard controllers, switchers, etc. 19. The following configuration shall be possible with cameras mapped to IP engine: a. Camera Details - The user shall be able to configure the following parameters for each IP engine camera: • Name • Location • Description • Camera Number • Camera Encoder Type • Resolution.
For Motion JPEG encoding: 30, 25, 20, 15, 10, 5, 3, 2 and 1. Slower frame rates of 1 frame every 2, 3, 5, or 10 seconds shall also be available. For MPEG encoding: 30, 25, 15, 12.5, 7.5, 6.25, 3.75 and 1. • Choice of five levels of video compression, equally distributed from minimum to maximum compression. • Encoder IP address. • Encoder camera number (when connected to a multiple port camera encoder). • Choice of frame rate or bandwidth limited streaming. • Unicast or Multicast transmission of video.
• Focus speed • Iris speed • Increment step size For the VCL Orbiter and Honeywell’s RapidDome camera ranges, the following additional functionality shall be provided: Configuration of Privacy Zones. The IP engine shall allow the user to select the regions for privacy zones and automatically download the configuration to the camera. Configuration of Camera Tours. The IP engine shall allow the user to fully configure all required camera tours, automatically downloading the configuration to the camera.
User Activated - The user shall be able to configure the following parameters for each camera: • Pre-record Duration: The amount of pre-recorded video that will be associated with a user request for recorded video. This will allow the camera server to capture video prior to the user request, as well as after the request. Shall be selectable from a list of values ranging between 0 seconds and 5 minutes. • Frame Rate: Video quality required for user activated recording.
• Pre-record Duration: The amount of pre-recorded video that will be associated with an alarm/event. This shall allow the camera server to capture video prior to the alarm/event, as well as after the alarm/event. Shall be selectable from a list of predefined manufacturer default values ranging between 0 seconds and 5 minutes. • Post-record Duration: Event activated recordings shall terminate after this period.
For cameras that support PTZ presets, a specified preset location shall be selected automatically when the alarm/event occurs prior to the event activated recording commencing. For example, when an alarm is detected on a security door, the alarm shall trigger a PTZ camera to move to a preset position, which is pointing at the door prior to the DVRMS commencing recording. Scheduled – The System shall support the ability to schedule recordings for each individual camera for times in the future.
• Enable/disable archiving of the clip and the period after which to archive • Retention period before the recording will be deleted • Enable or disable audio recording (if available) Systems that require the configuration of multiple time periods to manage background recordings shall not be accepted. d.
The user shall be able to configure the following parameters for each camera: • • Detection type: Continuous or scheduled Actions to perform when motion is detected: When motion is detected, the following actions shall be performed automatically: Start a recording, with the following configurable settings: Pre-record Duration: The amount of pre-recorded video, allowing the camera server to capture video prior to the detection of motion, as well as after the detection of motion.
• Motion Finished Time: The amount of time where no motion (inactivity) is detected before the previous motion is classified as completed. This shall be used for allowing recordings to continue until motion has finished. The IP engine must provide a means of automatic and manual tuning of the video motion detection for each camera.
Object Tracking – The IP engine must provide the ability to acquire and track an object within a predefined field of view on selected cameras.
server before being deleted. The retention period of individual recordings shall be able to be changed as necessary. Shall be selectable from a list of predefined manufacturer default values ranging between one hour and forever. Archive data: Enable/disable archiving and set the period after which the recording will be automatically archived. Deletion data: Set the period after which the recording will be automatically deleted.
This live tuning window shall show the live video as well as the regions of interest. During the time that motion is detected within a region, the border of the region shall change to a different color. In this way, tuning can be performed to achieve the desired performance. Text shall also be provided in the window to alert the user that motion has been detected.
Activated recordings will terminate after this period. Shall be selectable from a list of predefined manufacturer default values ranging between 0 seconds and 5 minutes or the object is no longer in the region of interest. Frame Rate. Video quality required for object tracking and classification-activated recordings. Shall be selectable from the entire range of frame rates supported for the camera/encoder.
• Specification of a minimum object size to allow noise filtering in the System to reduce false detections and alarms The IP engine shall also provide the ability to only track objects in particular regions of the camera view. The ability to graphically select these regions using the mouse must be provided, with an unlimited number of regions permitted per camera.
d. The Viewer shall have the option to send command to the controller to switch particular analog camera onto the analog monitor through drag operation. e. The Viewer shall be capable of configuring and running scan sequences. f. The Viewer shall be capable of adjusting the contrast, brightness, and saturation settings for each camera independently g. The Viewer shall support both analog and digital PTZ through GUI or through the keyboard. h.
o. The Viewer shall have the option to perform various operations through context menu on a particular video (live/recorded/sequence). These operations include: Full Screen Point and Drag Enable Square Select Maintain Aspect Ratio Toggle Text Digital PTZ Add Bookmark Send Message Start Recording Stop Recording Mark In Mark Out Save Image Save Image As Show Surrounding Cameras p.
r. The Viewer shall have the facility of configuring the preferences which shall include: FPS of unselected panels Rendered type Preview pane Text display format 22. Search - The Search facility in the HVMS shell shall include, as a minimum, the following features/functions/specifications: a. Search based on date and time for IP engine 23. Reports - The Report facility in the HVMS shell shall include, as a minimum, the following features/functions/specifications: a. Event History Report b.
A failure of any one of the database servers or camera servers shall NOT cause the IP engine to cease operation. As a worst case, only the cameras controlled by the failed camera server will be temporarily unavailable until reallocated to other camera servers. No physical changes to hardware, cabling or connections shall be required. D. ELECTRICAL POWER REQUIREMENTS The HVMS components must have the following electrical specifications: a. Power Requirement………………… 100-240 VAC (50/60 Hz) E.
2.8.2.3.2 SYSTEM PERFORMANCE A. The digital recording and transmission system shall include, as a minimum, the following features/functions/specifications: 1. The digital recording and transmission system must be protected by the most extensive support services in the industry, including customer service, pre-sales applications assistance, after-sales technical assistance, access to technical online support, and online training using Web conferencing.
2. The digital recorder shall be optimized and designed for Microsoft Windows Embedded XP, offering unparalleled stability, security, and ease of use, and shall allow the user to fully create and edit all network settings available with Windows Embedded XP. 3. The digital recorder shall come preconfigured with a DHCP enabled IP address and subnet mask to allow for installation in many IP settings without the need to reconfigure TCP/IP settings. 4.
10. The digital recorder, regardless of number of inputs, shall offer the following on-board storage hard drive capacity options with four removable drive bays: a. 2.0 Terabytes b. 1.5 Terabytes c. 1.0 Terabytes d. 750 Gigabytes e. 500 Gigabytes f. 250 Gigabytes 11. The digital recorder must be housed in a high-performance metal case. The case shall be no higher than 4 rack units (4U) and be designed to fit into a 19” EIA rack. 12.
17. When backing up the video to a CD, the unit shall include the ability to record the video on to multiple CDs, automatically prompting the user to insert the next CD when the previous CD is full. 18. The digital recorder shall include backup viewer software, allowing the user to playback the exported video in its proprietary format on a PC. The backup viewer must have essentially the same search features as the digital recorder’s software. 19.
d. Control Outputs e. 110V/220V auto-switching power-supply f. PS/2 Mouse Input g. PS/2 Keyboard Input h. USB Ports i. DB9 Serial Input j. LPT Parallel Printer Port k. Audio Line In l. Audio Microphone In m. S-Video Output (on Real Time models) n. SVGA Monitor Output o. RS422/485 Interface (with RX, TX, and Operation LEDs) p. RCA Video Out q. RCA Audio Inputs r. RJ-45 Network Jack (with Activity and Link LEDs) 23.
f. PTZ Adapter g. Rack Mount Attachments with Screws h. DVR Key i. User Manual 25. The digital recorder shall come pre-configured for fast and seamless integration within existing IT infrastructures. The unit must offer the following network setup options: a. The ability to enable or disable access to the digital recorder from remote locations. b. A designated time-out period that the connection will be terminated after unsuccessful user attempts to connect to the digital recorder. c.
27. The digital recorder shall include a user management console that allows the user to create, edit, and delete user accounts. Each account can be assigned different privileges that limit the usage of the system. Privileges shall include, but not be limited to, the following functions: a. Search b. Setup c. Pan/Tilt d. Backup e. Shutdown f. Intensive g. Forbidden Cameras h. User Ranking i. Auto Log Off 28.
e. A user specified contact number. f. Digital recorder manufacturer’s technical support number. g. A note space for the user to type in any details about the system. 31. A Gigabit 10/100/1000 network interface adapter shall be available as an option from the manufacturer, P/N HF3GBNIC. 32. The 8 input digital recorder shall include 8 sensor inputs for use with devices such as motion detectors, glass breakage alarms, door and window sensors, etc.
c. First 16: On 32 channel units, displays the first set of 16 cameras. d. Date/Time: Displays the current date and time. This date/time shall also be “stamped” into the recorded video and displayed whenever the video is played back. e. Search: Displays the search features that allow the operator to search previously recorded video. f. PTZ: Opens the options for controlling PTZ enabled cameras. g. Setup: Accesses the setup menu from which all customizable settings can be edited. h.
38. The following screen division sets shall be available to the operator of the digital recorder: a. Display the first four videos (1-4) in the video display area. b. Display the next four videos (5-8) in the video display area. c. Display the next four videos (9-12) in the video display area. d. Display the next four videos (13-16) in the video display area. e. Display videos 1-9 in the video display area. f. Display videos 8, 9, 10-16 in the video display area. g.
44. The digital recorder shall include the ability for pre-alarm and post-alarm recording, which must record video for a specified time before and/or after a motion or sensor alarm has occurred. The time period must be selectable from 1 to 60 seconds. 45. The digital recorder shall incorporate a “Regular Interval Recording” feature, allowing the unit to record a single frame every few seconds, every few minutes, every few hours, etc.
e. Relay output(s) activation 50. Each of the digital recorder’s 32 detailed customized schedules shall allow the operator to “link” camera(s) and relay output(s) activation to particular sensor input(s). The schedules can be activated by date/time, motion alarms, and/or sensor inputs. Advanced options must also be available that allows the user to send alarm events, either motion or sensor activated, to the remote emergency agent software or the video management software. 51.
f. CNB-AN102 g. CNB-PTZ100 h. Computar i. Dong Yang Unitech (DRX-502A) j. Dynacolor k. Ernitec l. Fine System (CRR-1600) m. Focusvision (KD1602) n. Honeywell (HSD-250) o. Inter-M (VRX-2101) p. Kalatel (Cyberdome) q. KDC r. LG (LVC-A70x’s) s. LG (LPT-A100L) t. Merit LI-LIN u. Panasonic v. Pelco D w. Pelco P (4800 baud) x. Philips (TC8560 & TC700) y. SAE z. Samsung (DRX-502A) aa. Samsung (SCC-641) bb. SANTACHI cc. Sensormatic SpeedDome (RS-422) . 136 Ed.
dd. SungJin (SJ2819RX) ee. Toshiba P (4800 baud) ff. Ultrak (KD6) or Honeywell (HD6) gg VCL hh. Vicon ii.Vicon SpeedDome jj.WonWoo 56. The digital recorder shall include on-screen play controls to playback the recorded video frame by frame (either forward or reverse), or play at normal speed (either forward or reverse). An on-screen hour/minute slide control bar must also be available to allow the operator to select the hour and minute of the desired video.
second of each hour. The operator must then have the ability to further narrow the search down to 10 minute and 1 minute increments by simply double-clicking a displayed image. 61. The digital recorder must allow the operator to specify a region on an image and perform a search based upon any motion that had occurred in that region. To indicate the progress of the search being performed, a status bar shall be displayed on the screen.
2. The remote software shall provide the user with most of the features and functions available at the local digital recorder. The remote features and functions must include viewing live video, searching through archived video, exporting images and video clips, and virtually all setup functions. 3. The remote video software shall allow up to 5 users to simultaneously connect to a single digital recorder. Each user can perform functions on the unit and not affect the other users.
2. The video management software shall incorporate multiple screen divisions, allowing the operator to create several groups of cameras and customize the organization of the cameras. Each screen shall contain up to 36 different cameras. 3. The video management software shall include the ability to have multiple windows open at any given time.
a. Total Status: Indicates if the unit is healthy and running correctly. b. Network Status: Indicates if the network component of the unit is running correctly and error free. c. Disk Status: Indicates if the hard drives of the unit are running correctly and have available storage space. d. Video Status: Indicates if the video component of the unit is running correctly and error free. e. Recording Status: Indicates if the recording component of the unit is running correctly and error free. f.
13. The video management software must allow the operator to export single images in the JPEG file format and save video clips in the AVI file format. This shall allow compatibility with any PC that supports these file formats. 14. The video management software shall incorporate a log to keep track of when the software was opened and closed and who logged in and out. The software must also utilize an alarm log to allow the user to view different types of alarms coming into the system.
EN55022 + A1: 1995 and A2: 1997 EN61000-3-2, EN61000-3-3 3. Immunity EN55024:1998 + A1:2001 and A2:2003 4. Safety UL, cUL 60950-1:2003 IEC/EN 60950-1:2001 CB report and certificate 2.8.2.4 RAPID EYE MULTI-MEDIA, DIGITAL RECORDING AND TRANSMISSION SYSTEM 2.8.2.4.1 SYSTEM DESCRIPTION A. The digital recording and transmission system shall provide a powerful, intelligent enterprise-class digital storage management tool that combines video, audio, and data capabilities in a single recorder unit (RU).
3. The digital recording and transmission system shall provide a powerful, intelligent enterprise-class digital storage management tool that combines video, audio, and data capabilities in a single RU. This system must be designed to record, search, and transmit video, audio, and data transactions, both live and post-event. 4. The digital recording and transmission system’s default priority shall be to capture and store video, audio, data, and alarms.
1. The RU’s operating system shall be VxWorks™, a secure, stable, and multi-tasking networked real-time operating system designed to be used in a distributed environment. Windows and other non real-time based operating systems are not acceptable. 2. The system’s RU must be offered in a minimum of 36 standard configurations, allowing the choice of length of time for storage of video, video capture rate (ips), and the option to record incident clips to a CD at the RU site.
search and review recorded data and video streams associated with the time at which the data is obtained. An operator shall have the option of designating serial data from POS/ATM to automatically initiate an action (alarm) and/or report (log). A post-event search of a specific recorded data stream qualifier must be available.
e. Monitor live video, audio, and POS data. f. View recorded video, audio, and POS data. g. View a video clip. h. Copy a video clip to the local CD-RW drive. Depends on model of RU. i. Set up a camera tour. 11. The local user interface shall include the ability to review and play back recorded video in its own Clip Builder.
with a manufacturer-installed CD-RW drive, a field upgradeable CD-RW bay to support a future upgrade to the CD-RW drive must be included. 16. The RU must include a removable front panel with key lock to conceal the 4 fieldupgradeable/replaceable hard drive bays and the optional CD-RW drive. Also secured behind the lockable front panel shall be the front panel control and display module, which shall include the following: a. Power Switch (low voltage control) b. System Ready LED c. Alarm State LED d.
22. The RU shall include 16 5V TTL alarm/control inputs on removable 5mm terminal block plugs. The inputs must be configurable via software as Normally Closed (NC), Normally Open (NO), or 2K End-of-Line (EOL) resistor sense. 23. The RU shall incorporate a fault relay to interface with an external alarm panel. The RU must have the ability to signal failure to operate or failure to report alarms. 24.
29. The RU shall work with either a 115 VAC or 230 VAC 50/60 Hz input, 6A or 3A and shall automatically select the correct supply. 30. The RU shall have the ability to connect to a designated PC, using either a telephone connection or network connection, when an alarm is triggered by an event. 31. The RU shall automatically adjust for Daylight Saving Time changes, with no loss of video.
based. This template shall make it easy to set up operator accounts with a predefined set of rights. 5. A record of each event shall be entered in the alarm log of the central database during an alarm session. The unit must have the ability to sort the alarms in true chronological order. The alarm log must contain a minimum of the following information for each event: a. Name of user logged on to alarm station or using alarm session b. Name of site c. Alarm action taken (e.g., new, acknowledge, rearm) d.
j. The right to access certain camera at a specific site, while allowing access to other cameras 7. The administrative software shall feature encrypted password protection. Passwords can be up to 50 alphanumeric characters, and the system administrator shall have the option of assigning individual unique passwords or assigning the same password to a group of users.
be available, with many of the controls designed to mimic the controls on VCRs. The controls must include: a. Print image b. Print preview c. Copy one image d. Start/stop record e. Detailed seek f. Jump-to-time g. Pause h. Next image i. Play j. Fast forward (2x, 3x, 5x, 10x) k. Playback speed slider l. Best fit image m. Tile image 7. Simply by double-clicking the title bar of the camera window, the operator shall have the ability to quadruple the size of the video displayed. 8.
11. The viewing software shall allow bitmaps to be saved from the video, at a rate that equals the camera frame rate. The size of each bitmap file shall not exceed 180 KB. Producing bitmaps must be available when running either a live, retrieval, or clip session. The user shall have the ability to view and print bitmaps using any bitmap reading software (e.g., Corel Paint Studio, Adobe PhotoShop, Microsoft Paintbrush, etc.).
c. Automatic record for live alarm: Recording of a clip starts immediately and automatically when an alarm is received at the operator’s PC. 16. The following alarm/events shall be recorded and/or reported and/or ignored by the view operator: a. Session request b. Session rejection c. Session disconnect d. Run-time failure e. Self restart f. Reboot g. Synchronize time h. System configuration i. Security modification j. System file modification k. Clear storage l. Input sensor activation/deactivation m.
purpose outputs shall be automatically displayed to the operator on the PC during a live video session. 19. The viewing software shall incorporate advanced video motion detection, allowing the operator to set motion detection parameters, such as region-of-interest, mass, and motion intensity on a per-camera basis. The following motion detection features/parameters must be available: a. Enable: Enables motion detection on selected camera. b. Sensitivity: Adjusts the sensitivity to motion. c.
may close, add, and adjust camera settings while the site tour is in progress. The order in which sites are toured, the time spent at each site, and the connection to be used to reach the site must be selectable during programming of the site tour with the administration software. The operator shall have the ability to temporarily suspend the tour if required, such as to investigate an event.
1. Unit Dimensions (H x W x D) 5.23” (3U) x 17.3” x 18.8” (133 mm x 440 mm x 478 mm) 2. Unit Weight 32-42 lbs. (14.5-19 kg.) 3. Shipping Weight 38-48 lbs. (17.5-22 kg.) 2.8.2.4.4 ELECTRICAL POWER REQUIREMENTS A. The RU must have the following electrical specifications: 1. Power Requirement 115-23 VAC, 60-50 Hz, 6-3A 2. Auto Sensing 120V/240V Operation 2.8.2.4.5 ENVIRONMENTAL CONDITIONS A. The RU shall be designed to meet the following environmental conditions: 1.
2.8.3 E-Mail Upon recognition of an event or alarm, the system shall be capable of sending user defined data via e-mail. The user shall have the capability to assign an e-mail address that the system shall notify should the designated alarm originate from this point. This process shall be a function of SQL 2000 server, which shall negotiate e-mail transfer to the Microsoft Exchange Server.
o o o o o o o o o o o o o Station Disconnected Function Dialed Outside Connection Intelligent Station ID Station Reset Station Lamp Test Audio Program Changed Group Hunt Occurred Mail Message Digit Dialed During Connection Direct Access Key Pressed Handset Off Hook M-key Pressed C-key Pressed 2.8.
• confirm (i.e., the OK button). No data shall be written to the database until the user hits apply or OK Communications with the VISTA panel shall be efficient and provide for no unnecessary deleting and re-inserting data. 2.8.5.
Location (Pro-Watch purposes) • Descriptor uploaded from panel (Read only) • Logical device of which it is a member (Read only) • Checkbox indicating whether it should be put into or taken out of a logical device • Zone number (Read only) • Zone type (See VISTA-128FBP and VISTA-250FBP Installation and Setup Guide, Pages 4-6) • Input type (See VISTA-128FBP and VISTA-250FBP Installation and Setup Guide, Pages 4-7) • Partition of which it is a member (Read only.
• • • • • • Provide the capability to delete a VISTA logical device. All dependencies must be appropriately updated Provide a context menu of manual commands for partition logical devices. The choices must be Arm Away, Arm Home, Arm Instant, Arm Maximum, Force Arm Away, and Force Arm Home Provide a context menu of manual commands for zone list logical devices. The choices will be auto bypass and auto un-bypass Provide the capability to place zones, partitions and zone lists on a map.
• • Unified access and intrusion tracking and compliance feature Real-time alarm/event monitoring – Receive and integrate intrusion events. – Control and response, including acknowledge, clear, annotate, live video, recorded video – Manual override, lock and unlock doors, shunt/unshunt zones and input points – Manual override of system functions – Lock and unlock doors – Arm/disarm partitions and zone lists including context sensitive arming behaviors (arm, arm away, arm immediate, etc.
• Pop-up video on access or intrusion function • Live system control – Arm/disarm intrusion system – Multiple partition control – Bypass/un-bypass doors – Live camera view, including PTZ • Logical devices automatically created during panel configuration 2.8.6 Visitor Management System (VMS) 2.8.6.1 Overview The system shall support integration to the LobbyWorks™ Visitor Management System to allow the user to track visitors, employees, assets and deliveries as they enter and exit the facilities.
2.8.6.3 Visitor Information Capture The system shall support quick and complete capture of visitor information as an essential component for proper record keeping and security checks. The system shall support various hardware devices in order to capture visitor information, including but not limited to scanning business cards, scanning driver licenses, capturing visitor photo, capturing visitor signature, and 2-D barcode scanning of driver licenses.
2.8.6.7 Host Notification The system shall notify host of a visitor’s arrival by e-mail, office phone, mobile phone, or realtime network messaging. Delegated notification and customizable announcement shall also be provided. The system shall notify host when a visitor does not sign out. 2.8.6.8 Visitor Tracking The system shall keep an accurate log by automatically tracking events as they relate to the visitor’s activities on site. The system shall track visitor sign in and sign out times.
• Detailed visit reports • Time and attendance reports for contractors and other visitors • Reports on demand or schedule reports for regular generation and email delivery 2.8.6.12 Assets and Deliveries The system shall track assets and deliveries as they enter and leave premises. The system shall have the capability to generate asset and delivery tags and to scan assets and deliveries in and out with a barcode scanner.
2.8.6.15 Installation The system shall provide a simple installation process, including wizard-based installation, attended and unattended installation support, and batch import of employee data. 2.8.6.16 Flexibility The system shall be designed to meet the needs of large and small companies in many industries. The system shall support configuration as a standalone or networked solution, single or multi-tenant facility, or single or multiple facility company.
• • Commercial Scalable Database o The system shall utilize a commercial scalable database including Microsoft MSDE or Microsoft SQL Server. o Full SQL Server licenses shall not be required for database storage of 100,000 visit records or less. Traffic Control o • ID Authentication o • The system shall provide the capability to limit the number of simultaneous visitors per host, as well as the maximum number of visitors per host, per day.
3 Execution 3.1 Examination Submission of a proposal confirms that the contract documents and site conditions are accepted without qualifications unless exceptions are specifically noted. The site shall be visited on a regular basis to appraise ongoing progress of other trades and contracts, make allowances for all ongoing work, and coordinate the requirements of this contract in a timely manner. 3.
4 CPU Minimum Requirements 4.1 Pro-Watch Lite Edition • • File server CPU Requirements o Microsoft Windows 2003 Server or Windows 2000 Server o CPU - Xeon 2.66 with 1 GB RAM or better (4 GB recommended) Workstation CPU Requirements o Microsoft Windows XP Professional or Windows 2000 Professional o Xeon 900 MHz and 512 MB RAM or better (1 GB recommended) 4.2 Pro-Watch Professional Edition • Professional Edition System Server CPU Requirements: o o o o o o o o o o o o Pentium IV with 1.
• • • • o Operating System support: • • • • • Microsoft Windows 2000 Server Microsoft Windows 2000 Professional Microsoft Windows 2003 Server Microsoft Windows XP Professional Edition Professional Edition System Client Workstation CPU Requirements: o o o o o o o o o o Pentium IV with 1.
o o o o 2 Communication Ports 10/100 Network interface Card 16 X CD-ROM Minimum Operating System support: • • Microsoft Windows 2000 Professional Microsoft Windows XP Professional Edition The badging client workstation shall support the following badge printers: • Magicard Rio™ o Print speed: Rio, single-sided: 20 seconds o Security Features: HoloKote® anti-forgery protection preconfigured with UltraSecure® logo plus custom security mark when used with the optional HoloKote Custom Key™.
o o o o o o o o o • Security Features: HoloKote anti-forgery protection preconfigured with UltraSecure logo plus custom security mark when used with the optional HoloKote Custom Key. Use of HoloPatch cards produces high visibility security seal. Printer Interface: IEEE standard 1284-1994 compatible (Centronics) parallel port and Universal Serial Bus (USB rev 1.1) port (user choice). Software: Supplied with Windows 98, ME, NT4 and 2000, XP driver Power Source: Auto-ranging 90 to 265 VAC 47-63 Hz.
o o o • Card Stock: 50 30 mil (0.76 mm) PVC cards in sealed one shot dispenser. Plain, HoloPatch and HiCo™ magstripe cards available. Card Capacity: 50 cards in external dispenser. Safety: CE certified - UL listing pending (USA & Canada). Magicard Prima 2e™ o Print speed: YMCKO About 30 seconds per full color (YMCK) side. Prints both sides in YMCK in about 60 seconds. o Security Features: Built-in re-transfer laminate protection. Image is printed on rear of re-transfer film.
4.3 Pro-Watch Corporate Edition • Corporate Edition System Server CPU Requirements – Low Activity (LRS): o o o o o o o o o o o o Xeon Processor (1+ GHz) 2 GB Ram 36 GB SCSI HD One (1) USB Port Mouse and Keyboard 17" SVGA Monitor with 1024x768 Resolution 2 Com Ports Minimum 10/100 Network interface Card 16 X CD-ROM Minimum Backup media (SCSI Recommended) 56K-V.
o Operating System support: • • • Corporate Edition System Server CPU Requirements – High Activity (HRS): o o o o o o o o o o o o Quad Xeon Processor (1+ GHz) 4+ GB Ram 72 GB SCSI HD in Array One (1) USB Port Mouse and Keyboard 17" SVGA Monitor with 1024x768 Resolution 2 Com Ports Minimum 10/100 Network interface Card 16 X CD-ROM Minimum Backup media (SCSI Recommended) 56K-V.
o o 16 X CD-ROM Minimum Operating System support: • • • Microsoft Windows 2000 Professional Microsoft Windows XP Professional Edition Corporate Edition System Badging Client Workstation CPU Requirements: o o o o o o o o o o Pentium IV with 1.
o o o o o Lamination: The optional Sicura (PBVP35LAM) standalone laminating station can be used to apply a tough, 1 mil (0.0254 mm) thick polyester overlaminate. Dimensions: 7.5”W x 8.0”H x 17.5”L (190 mm x 200 mm x 445 mm). Card Stock: ISO Standard CR80 Card Thickness 0.015-0.063” (0.38-1.6 mm). Card Capacity: 100 card feed hopper, 50 output stacker. Safety: CE certified - UL listed (U.S. & Canada). • Magicard Tango o Print speed: Tango, double-sided: 40 seconds.
o o o o o o o o o • Security Features: HoloKote anti forgery mark across face of card. Custom security mark with optional Custom Key. Use of HoloPatch cards produces high visibility security seal. Key controlled printing option with Custom Key. Printer Interface: USB rev.1.1 (USB 2.0 compatible). Software: Supplied with Windows 98, ME, 2000, XP driver software Power Source: External power “brick” for 90-265V 40-60 Hz (autoranging).
In-line Laminator Compact, single-sided in-line laminator. Thin, 0.5 mil and 1 mil laminates available. Clear and holographic laminates. 8.2” /207 mm W x 12.2” /308 mm H x 12.2” /310 mm D. Weight 18 lbs/8kg. Double-sided lamination also available. Magstripe Encoder Prima 2e with HiCo/LoCo Magstripe encoder. Contactless Card Optional encoder. Contactless cards supported: Encoder Philips: MIFARE, DESFire, MIFARE ProX and i.code. HID: iCLASS. Texas Instruments: TagIT. ST Micro: x-ident, SR 176, SR 1X 4K.
o o o o o o o o o One (1) USB Port Mouse and Keyboard 17" SVGA Monitor with 1024x768 Resolution 2 Com Ports Minimum 10/100 Network interface Card 16 X CD-ROM Minimum Backup media (SCSI Recommended) 56K-V.
4.4 HONEYWELL VIDEO MANAGEMENT SYSTEM (HVMS) A. HVMS Server (HVMS Core Server and Controller) The HVMS server shall be able to operate with no performance degradation using the following hardware and operating system configuration: • Dual Core Intel Xeon 5160 3.00. These are minimum clock speeds; Faster GHz clock speeds are optional • System memory (RAM) 4 GB of RAM minimum • DVD-R drive and a 3.5” 1.
B. HVMS Workstation The HVMS workstation shall be able to operate with no performance degradation using the following hardware and operating system configuration: • Intel Core 2 Duo Processor E6750 2.66 GHz or Quad Core Intel Xeon E5405 2.0 GHz. These are minimum clock speeds; Faster GHz clock speeds are optional. • Standard and Performance Workstation System memory (RAM) 4 GB of RAM minimum for Microsoft Windows XP Professional 32-bit only. • DVD-RW drive and a 3.5” 1.
• 1000 Mbps NIC or compatible pair for network connection to the other components of the DVRMS • Windows 2000 Server and Windows 2003 Server The database server must provide the following system fault tolerance: • Support RAID 0+1 or 1 for the operating system • Support RAID 0+1 or 1 for the database (SQL Server 2005) D. IP Engine Camera Server The camera server shall be able to operate with no performance degradation using the following hardware and operating system configuration: • Pentium IV or Xeon 2.
