The concept of a unified software platform which provides the interfacing (communications) between subsystems, manages the data, dictates system parameters and operations, and provides the user interface is the basis for the modern integrated system. It is differentiated from another technique once the mainstay of electronic security, system interfacing.
System interfacing is still essential to security system design. However, when the transition from discrete physical panels to software “modules” occurs the nature, interfacing, and dynamics of the interaction between the modules makes a quantum leap in flexibility and power. It means communication between:
- Sensors, cameras, readers, auxiliary modules.
- Hardware (power supplies, locking devices, relays).
- Data and Database management.
- Processors/Software.
- GUI and control surfaces (workstations, keypads, pushbuttons, etc.).
Some of these elements are no doubt new ground for the typical dealer to cover, but at the same time, others are on familiar turf. There are few individuals who can claim to have all of these areas mastered. Additionally, there are many integrated systems being upgraded and new ones continually being introduced. No mortal can master them all.
WHERE TO BEGIN
To narrow down the learning curve you can tackle the ones that fit your most immediate requirements. Then you can become proficient in as many aspects of each system component in that discipline as quickly as possible. In this era of high technology and specialization, proficiency is measured in terms of technical training, implementation skill, knowing who to ask when you have a question, and the bottom line ability to get the job done.
If you have strength in a particular area, then you need to get up to speed on the areas where you need improvement. You also need to team up with folks whose expertise will synergize with yours.
The importance of the PC is inescapable. Also the ability to maneuver around the operating systems they use, such as Windows XP pro, is essential. There are plenty of training aids and opportunities to gain these skills, including a favorite: OTJ (On the Job) training. A genetic predisposition to build and repair things, referred to by geneticists as the “Fix-It Gene” also helps.
For years security was hardware based: a box with wires, inputs and relays. Eventually decision making logic circuitry was added, and then some wires were eliminated with wireless technology. Many industry insiders now believe the industry is software based. The delineation is analogous to the concept in calculus: the Function (and you thought you’d never have to use all that stuff in real life!). A variety of inputs are dynamically processed to produce the desired output. Software is the function’s engine, and the hardware handles the inputs and outputs.
In the world of Integration, there are lots of variables and debate with respect to system architecture and functionality, even among the experts. And because this is relatively new field, there are not too many standards and a fair amount of confusion. Therefore, security managers are sometimes making buying decisions for the wrong reasons.
As hard as it is for security professionals to figure it all out, it is even harder for end users to know what the right answer is. Security insiders can all agree on a few things though. One is that many companies can put up an impressive corporate image which many buyers find hard to resist (No one ever got fired for buying an IBM). Yet, although networks are surely the super highway to the future, they can pose hurdles to the typical system integrator.
Integrated systems which have matured engineering design will offer a number of communications protocols, one of which is usually some degree of LAN/WAN connectivity. The essence of the integrated system is communication. The “system” which is essentially the software, resides in a computer. It must interact with the various other elements, and also with the system operator.
Integrated systems may be set up as standalone which means that the services which comprise the “system” reside in one PC. A networked system may be comprised of a separate communications server, a separate database server, and additional workstations where one or more of the system features may be used. For example, a workstation near a main entry point could be used for monitoring of door usage and video verification of badge holders, while another workstation might be situated in a security console, and be used to monitor video alarm events or monitor overall system activity.
The system must also communicate with the various devices associated with it. These devices include devices like door controllers and DVRs. The controllers are in turn connected to items such as the FACP, card readers, door locks, motion detectors, door sensors and REX devices. The DVRs are connected to the cameras.
Depending on the manufacturer the controllers and DVRs may be interconnected in a loop and/or be connected to the “host system.” The loops and interconnections may permit the use of a variety of protocols such as hardwire (RS232, for example), fiber, TCP/IP, WIFI, DSL/ISDN and dial-up.
TOPOGRAPHY, TRAINING AND POLITICS
Keeping abreast of all these networking techniques is a full time preoccupation for those in the field. For example, Ethernet networks can range in speed from 10mB to 1 Gigabyte. They are frequently labyrinths of hubs, switches and routers the inner secrets of which are fiercely protected by the IT department.
Documentation and tech support from the manufacturer is critical. The majority of network issues encountered during an installation can be overcome relatively fast when the average dealer’s fix-it gene kicks in.
Another defense mechanism you should employ is your contract with the client. The deal should be: you bring the boxes, they provide the backbone. Let them convince you that they have established the required connections before you hook up your hardware. Do your own homework by bench, and pre-testing your hardware prior to arriving on-site.
- System integration provides unified services to multiple security modules which might include:
- ACCESS CONTROL: Card readers and door locks, with a centralized database of cardholders and access schedules and other parameters.
- ELEVATOR CONTROL: A sub module which provides security management options with respect to floor access privileges.
- INTRUSION DETECTION: Door sensors and motion detectors which are controlled and monitored.
- BADGING AND PHOTO ID: The database of employee data and images along with the imaging and printing resources required to produce credentials.
- GUARD TOUR: The special application which verifies that guards are patrolling the required areas of a site at predefined time schedules.
- KEY CONTROL: Utilizing an access credential to supervise the distribution of specialized keys into sensitive areas or control proprietary devices.
- DVR/CCTV: A variety of services, monitoring features and control functions whereby cameras and digital recorders are controlled, and real time as well as centrally archived images are viewed stored and transmitted over the network. Control functionality includes time based activation, preset pan & tilt and computer defined motion sensing.
- TIME & ATTENDANCE: The adaptation of access control readers and hardware to record the comings and goings of employees as basis for calculating attendance and payroll.
- BUILDING MANAGEMENT: A variety of controllable functions associated with building management including heating and cooling, lighting, locking and unlocking of doors and elevator control.
- FIRE: monitoring and annunciation of fire detection and life safety building features.
OPEN ARCHITECTURE
Open architecture refers to the capability of different system elements such as biometric readers, video equipment and access readers and controllers to work with one another. Let’s explore a few analogies so you can best appreciate the power and ramifications of open architecture.
Early on, the alarm dealer was able to use anyone’s magnetic contacts and motion detectors, with anyone else’s’ alarm panel. You could not however use one brand keypad with another brand control panel.
Rather early on, card readers became open architecture; or to be more precise, card reader manufacturers standardized on their output protocols. (Example: Consider the Weigand output as a universal standard. Therefore, access control system designers could select the brand and style of card reader to suite the particular application).
Card technologies also fell into line early on so that new controller hardware could be “backed into” large existing credential populations. The way the card data was stored by the system also standardized under standard database engines such as Sybase, Microsoft SQL or for the very high-end systems ORACLE. This enabled databases to be modular, portable and therefore more readily supported archiving and database sharing between a facility’s other management functions.
The trend now continues to include the ability to upgrade software while leaving the existing physical layer of hardware (controllers, card readers, DVRs, etc.). Truly a revolutionary concept and one which is worth the investment of your time to become familiar with. This feature is important for a reason which may not be obvious to many. Access control systems have been around for several years and PC-based systems are certainly nothing new either.
To the end user, the only factors that differentiate one system from the other, are things like how scalable the system is, how user friendly the interface is, how reliable the system is, and of course, how much it costs to implement.
The fact is that there are a lot of legacy systems out there being passed off to end users which are essentially built upon DOS or designed upon an outmoded architecture. They may give the outward appearance of being similar to the rest but in fact, they are under-powered and massaged with bells and whistles bolted onto them. From experience after encountering one of these systems, they are basically a bad investment for both the dealer to support and for the end user to purchase.
Even though the access control industry addressed the issue hardware scalability in the 1980s, the issue of software scalability was not always addressed. This is due to the fact that development of new software is very expensive, and introducing revised systems which are not backward compatible will cause a riot among the ranks of end users and dealers. The point is that by selecting the correct integrated system house in the first place, you will be able to negotiate the future and better service your clients. They are counting on you and your judgment to guide them.
INTEGRATION VS. REDUNDANCY A final consideration is the issue of redundancy. This refers to the merits of individual systems as opposed to software which resides in a single PC. There are several points of view on this topic and perhaps no single correct answer. Frequently building codes or pre-existing systems on a site will help to make the decision for you. Perhaps your own background and orientation will instinctively direct your design philosophy in a particular direction.
Some system designers prefer that the fire systems be autonomous to the integrated system, with interfacing limited to perhaps alarm and status monitoring, off site notification and emergency door release. Some system designers prefer to keep the intrusion alarm in a separate box. Some system integrators warn you to steer clear of offering time and attendance functionality to your clients unless you enjoy pain and suffering (yours).
The truth is that even though integrated architectures offer you a system whose capabilities are limited by only your imagination as the system designer, you should keep both feet on the ground. Pragmatically factor in the potential collateral damages along with the collateral benefits system integration will bring to your projects.
