Picture Perfect 4.6 User Manual - UTCFS Global Security Products

More documents

Recommendations

Info

2 Picture Perfect 4.6 User Manual Overview The Picture Perfect system is a powerful, flexible, integrated, computer-based physical access management system. It is a complete end-to-end solution for today's most commonly deployed physical security applications, providing real-time monitoring, command and control, automation, database administration and report management in a single, unified system. Picture Perfect integrates access control, photo identification and credentialing, video surveillance, alarm monitoring, intrusion detection and visitor management. Picture Perfect uses industry leading products such as the Linux and AIX operating systems, Informix Dynamic Server, and a Java RunTime Environment (JRE). The Picture Perfect platform functions, in large measure, as a database server. The majority of access, alarm, and time-of-day decisions are made locally by intelligent micro controllers. Data necessary to make these intelligent decisions is downloaded from the host to the micro controller (referred to as “micro” in this document) as required. Since the majority of the decisions are performed at the micro, the host is free to concentrate on operator functions such as data entry, database queries (requests for data), and report generation. The system controls access readers using various technologies including, magnetic-stripe, barium ferrite, Wiegand, bar code, and proximity technologies. Smart Card readers and readers with keypads for user-defined PIN entry are also accommodated. The smallest system monitors thousands of badge records, transaction history records, digital inputs (alarm contacts), and digital outputs. Capacity limits depend on system resources. The system supports multiple operator work stations and printers, and the Picture Perfect configuration that is deployed. Scheduling features allow time allocations for use of readers and alarms. Micros, such as the M5, have the capability to perform the majority of scheduling tasks. This provides the user with full scheduling capabilities, even when a communication problem has caused the micro and host to temporarily stop talking to each other. The user interface is menu driven and user-friendly. The menus provide the operator with various options which lead to input screens, providing the ability to add, change, or delete information. By assigning operator levels to individuals, operators can be restricted in their control of the system. They can be denied the authority to change previously set parameters, and may be able to view information on a screen, but may not be permitted to modify or print out the information. All conditions sensed by the system can be assigned unique messages, which can be displayed on the computer screen and made available to the operator. A sensor on a door can be coded within the system, not only to activate an alarm if the door is opened, but to notify the operator of where the breach occurred and what action to take. Alarms can be given priorities for action in the event that multiple alarms occur. All alarms are provided with an audio display tone and a flashing alert to warn security personnel of severe conditions. The system maintains a history of all occurrences reported by its micros, such as access attempts or alarms. Management reports are available to provide the system administrator with the activities within the system any time, on demand. The program is personalized by customers to their specific requirements and configuration by simple windows and menus. An operator can change the size and position of a screen, the forms can be customized to include specific fields, and custom lists can be added.
Chapter 1 Introduction 3 The system uses a relational database management system (RDBMS) which allows the operator to query the database using menu driven forms. These forms allow the operator to specify data fields requested, logical relationships between the fields, and the order in which the fields are to be selected. Once the request for data is made, the matching records are displayed in a grid; the operator selects a record from the grid to display the form. If desired, the operator can print the requested data by selecting the appropriate option. The system architecture uses a distributed approach, comprised of micros and the host processor. • On an AIX system, all terminals are graphics terminals except the host console, which could be a character-based terminal. • On a Linux system, all terminals (including the host console) are graphics terminals. New in Picture Perfect 4.6 Picture Perfect 4.6 introduces the following key capabilities, features, and product enhancements: • Server operating systems: - Support for AIX 6.1 (64-bit) TL 6 - Support for Red Hat Linux 5.6 (32 bit) • Client operating systems: - Support for Microsoft Windows XP SP3 (32-bit) - Support for Microsoft Windows 7 Ultimate (32-bit and 64-bit) (Microsoft Windows Vista is no longer supported) • Support for the latest available JRE for server and client • Client browsers: - Support for Microsoft Internet Explorer (IE) 8.0 on Windows 7 (32-bit and 64-bit) and on Windows XP SP3 (32-bit) - Support for Mozilla Firefox 3.6.10 (or later) on all supported client operating systems • Support for native Informix based Enterprise Architecture (Informix 11.5 UC8). This feature introduces changes to the database schema. Refer to the section titled “Picture Perfect 4.6 database interface changes” in the Picture Perfect 4.6 Tables and Fields Reference Manual. • Support for Enterprise Replication (ER). For more details, see Picture Perfect 4.6 Enterprise Edition User Manual. • Support for FQDN usage for browser/client connections to the Picture Perfect host. See Picture Perfect 4.6 Installation Manual. • Micro controller firmware versions: - Support for mixed versions of R118, R117, and R120 or currently shipping version in a single system for PXNPlus and DirecDoor. - Support for legacy firmware on PX micros. - Flashing of micros is not required before upgrading the host software For detailed system requirements, see the Picture Perfect 4.6 Installation Manual. • Support for the DirecDoor I/O expansion board which provides five additional 4-state inputs and five additional relay outputs. See Chapter 8, Device management on page 121.
Page 1 and 2: Picture Perfect 4.6 User Manual P/N
Page 3 and 4: i Contents Preface . . . . . . . .
Page 5 and 6: iii Scheduling backup events. . . .
Page 7 and 8: v Preface This document provides in
Page 9: Chapter 1 Introduction This chapter
Page 13 and 14: Chapter 1 Introduction 5 • Digita
Page 15 and 16: Chapter 2 Getting started This chap
Page 17 and 18: Chapter 2 Getting started 9 To rest
Page 19 and 20: Chapter 2 Getting started 11 Figure
Page 21 and 22: Chapter 2 Getting started 13 To log
Page 23 and 24: Chapter 2 Getting started 15 4. To
Page 25 and 26: Chapter 2 Getting started 17 Table
Page 31 and 32: Chapter 2 Getting started 23 The si
Page 35 and 36: Chapter 2 Getting started 27 Other
Page 37 and 38: Chapter 3 Configuration checklist T
Page 39 and 40: Chapter 3 Configuration checklist 3
Page 41 and 42: Chapter 3 Configuration checklist 3
Page 43 and 44: Chapter 4 Setup This chapter provid
Page 45 and 46: Chapter 4 Setup 37 2. From the tool
Page 47 and 48: Chapter 4 Setup 39 • Select Tabul
Page 49 and 50: Chapter 4 Setup 41 Assigning system
Page 51 and 52: Chapter 4 Setup 43 Table 24. Parame
Page 57 and 58: Chapter 4 Setup 49 Configuring LDAP
Page 59 and 60: Chapter 4 Setup 51 Fields and contr
Page 61 and 62:
Chapter 4 Setup 53 Fields and contr
Page 63 and 64:
Chapter 4 Setup 55 Setting up works
Page 65 and 66:
Chapter 4 Setup 57 Setting up SSL e
Page 67 and 68:
Chapter 4 Setup 59 For the client
Page 69 and 70:
Chapter 4 Setup 61 su - root 4. Typ
Page 71 and 72:
Chapter 5 System configuration This
Page 73 and 74:
Chapter 5 System configuration 65 F
Page 75 and 76:
Page 77 and 78:
Chapter 5 System configuration 69 T
Page 79 and 80:
Chapter 5 System configuration 71 D
Page 81 and 82:
Page 83 and 84:
Chapter 5 System configuration 75 D
Page 85 and 86:
Chapter 6 Operator administration T
Page 87 and 88:
Chapter 6 Operator administration 7
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Chapter 7 Alarm/activity configurat
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Chapter 8 Device management This ch
Page 131 and 132:
Chapter 8 Device management 123 Fie
Page 133 and 134:
Chapter 8 Device management 125 Fig
Page 135 and 136:
Chapter 8 Device management 127 Par
Page 137 and 138:
Chapter 8 Device management 129 Do
Page 139 and 140:
Chapter 8 Device management 131 Tab
Page 141 and 142:
Page 143 and 144:
Chapter 8 Device management 135 12.
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Chapter 8 Device management 141 To
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Chapter 8 Device management 151 Net
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Chapter 8 Device management 161 Rel
Page 171 and 172:
Page 173 and 174:
Chapter 9 Area management This chap
Page 175 and 176:
Chapter 9 Area management 167 Field
Page 177 and 178:
Chapter 9 Area management 169 Note:
Page 179 and 180:
Chapter 9 Area management 171 Timed
Page 181 and 182:
Chapter 9 Area management 173 Table
Page 183 and 184:
Chapter 9 Area management 175 Defin
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Chapter 9 Area management 181 Field
Page 191 and 192:
Page 193 and 194:
Chapter 10 Schedules, modes, and ev
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Chapter 11 Badge management This ch
Page 225 and 226:
Chapter 11 Badge management 217 Fie
Page 227 and 228:
Chapter 11 Badge management 219 Tab
Page 229 and 230:
Chapter 11 Badge management 221 •
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Chapter 11 Badge management 231 To
Page 241 and 242:
Chapter 11 Badge management 233 Pri
Page 243 and 244:
Chapter 11 Badge management 235 The
Page 245 and 246:
Chapter 11 Badge management 237 Rel
Page 247 and 248:
Chapter 11 Badge management 239 Rel
Page 249 and 250:
Chapter 11 Badge management 241 4.
Page 251 and 252:
Chapter 11 Badge management 243 Fie
Page 253 and 254:
Chapter 12 Badge design This chapte
Page 255 and 256:
Chapter 12 Badge design 247 To enco
Page 257 and 258:
Chapter 12 Badge design 249 Table 1
Page 259 and 260:
Chapter 13 Alarm/activity monitors
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Chapter 14 Reports This chapter des
Page 289 and 290:
Chapter 14 Reports 281 Creating and
Page 291 and 292:
Chapter 14 Reports 283 Table 116.Re
Page 293 and 294:
Chapter 14 Reports 285 Table 117.De
Page 295 and 296:
Chapter 14 Reports 287 • From the
Page 297 and 298:
Chapter 14 Reports 289 Importing ar
Page 299 and 300:
Chapter 14 Reports 291 Output: Repl
Page 301 and 302:
Chapter 14 Reports 293 {$time_range
Page 303 and 304:
Chapter 14 Reports 295 Characters t
Page 305 and 306:
Chapter 14 Reports 297 Example Defi
Page 307 and 308:
Chapter 14 Reports 299 # sqlstmt "u
Page 309 and 310:
Chapter 15 Backup and restore This
Page 311 and 312:
Chapter 15 Backup and restore 303 F
Page 313 and 314:
Chapter 15 Backup and restore 305 T
Page 315 and 316:
Chapter 15 Backup and restore 307 R
Page 317 and 318:
Chapter 15 Backup and restore 309 F
Page 319 and 320:
Chapter 16 Data Generator and templ
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Chapter 17 User interface customiza
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Chapter 18 Advanced features This c
Page 339 and 340:
Chapter 18 Advanced features 331 Fi
Page 341 and 342:
Page 343 and 344:
Chapter 18 Advanced features 335 Mo
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Chapter 18 Advanced features 347 To
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Chapter 18 Advanced features 357 Ta
Page 367 and 368:
Chapter 18 Advanced features 359 me
Page 369 and 370:
Chapter 18 Advanced features 361 El
Page 371 and 372:
Chapter 18 Advanced features 363 Du
Page 373 and 374:
Chapter 18 Advanced features 365 De
Page 375 and 376:
Chapter 18 Advanced features 367 Ta
Page 377 and 378:
Chapter 18 Advanced features 369 Ex
Page 379 and 380:
Chapter 18 Advanced features 371 Ca
Page 381 and 382:
Page 383 and 384:
Chapter 18 Advanced features 375 En
Page 385 and 386:
Chapter 18 Advanced features 377 Wh
Page 387 and 388:
Chapter 18 Advanced features 379 De
Page 389 and 390:
Chapter 18 Advanced features 381 2.
Page 391 and 392:
Page 393 and 394:
Chapter 19 Troubleshooting and supp
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
399 Glossary This section explains
Page 409 and 410:
401 Table 134.Picture Perfect 4.6 t
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
407 Index A About Picture Perfect..
Page 417 and 418:
409 DES ...........................
Page 419 and 420:
411 L LAN..........................
Page 421 and 422:
413 R Radio Buttons ...............
show all

Picture Perfect 4.6 User Manual - UTCFS Global Security Products

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?