Managing physical security information

by Catherine Howlett | June 1, 2013 11:31 am

[1]

by Mike Webster, CPP
Over the past 20 years, physical security systems have evolved from hardware and software components to a comprehensive professional, functional, and technological domain. This requires specialized knowledge and subject matter expertise to design and specify security solutions.

The most recent and significant development in integrated security systems is physical security information management (PSIM)––a software and professional services solution requiring a non-traditional approach to specification, design, and deployment for architects, engineers, consultants, and security professionals. Until now, it has rested on designers and specifiers of integrated security systems to hold this knowledge.

A brief history of security
For many years, it was fairly easy for architectural and engineering firms to incorporate security systems into a set of project specifications. Access control, closed-circuit television (CCTV) video,and intrusion alarms were all largely standalone, hardwired, analog systems that did not require much integration or coordination with other design elements or team members. Over time, the security industry and technologies involved matured and developed.

Protecting assets within an organization became vital to each one’s mission and bottom line, spreading the concept of ‘security.’ This required collaboration, including information-sharing, with other departments, business systems, and databases within the organization.

While information-sharing and systems integration have progressed, the industry remains largely underdeveloped in this area. Historically, most hardware, software, and technology manufacturers have created closed, proprietary products to gain a competitive advantage in the marketplace, and to prevent competitors from infringing on their market share. As a result, the security industry continues to be fractured and fragmented. Individual subsystems––including access control, video surveillance, and alarm systems––have limited interaction, and critical security information is kept in separate silos.

[2]

Fragmented security management, monitoring, command and control environments, and architecture have left security operation center personnel and management with many challenges, such as:

• inability to integrate disparate security systems for information-sharing and automation of system responses to alarm and event activity;
• need for users to maintain operable knowledge of numerous different systems; and
• lack of enterprise system functionality, and the subsequent forcing localized and regionalized deployments.

As systems integration evolves in other areas of the built environment, a better common operating platform is needed, allowing all facility security systems to be monitored with information-sharing for improved situational awareness and a more effective response to incidents.

As security systems and technology become more software-driven and move toward network-based communications, new opportunities for integration and information-sharing are being created. Along with this progression, the old, entrenched distinctions between access control, video surveillance, alarms, and reporting have blurred and, in some cases, disappeared. These disparate systems are replaced with a more holistic approach to security management, where a unified user-interface platform can be established to combine all functions and data. The security industry has finally responded to this need with the development of PSIM.

[3]

The benefits of creating a single operating platform
Physical security information management integrates various subsystems into a single, common operating platform. These can include:

• video;
• audio;
• access control;
• intrusion alarm;
• fire alarm;
• building management;
• computer-aided dispatch; and
• power management.

Intelligent analysis of system information is then applied, automating system activities through rules-engine-based workflows. These workflows map the automated system activities and security operator actions in response to specific events. For example, in response to an alarm event, the software rules engine can direct video cameras to be displayed and recorded, controlled doors to be locked/unlocked, and template e-mail and text messages to be automatically sent to make notifications. For security control operators, pre-defined lists of instructions can be displayed to direct alarm response activities, which can be configured to change, as an event escalates.

This connects disparate security systems and devices to provide a common operating environment for shared data, enhanced event management, and improved situational awareness. Not only does the PSIM solution collect, normalize, correlate, and analyze information from these varying systems, but it can also interact with them to generate automated system activities. The solution can:

• lock and unlock doors;
• control pan-tilt-zoom (PTZ) cameras;
• archive and access recorded video related to an event;
• turn alarm zones on or off;
• shut down elevators; and
• send out evacuation messages.

PSIM software integrates disparate security subsystems into a single operating platform. Intelligent software modules collect, normalize, and correlate data from subsystems to operate in a common system language and protocol. Automated system activities are enabled by rule engine-based workflows, and visibility is maximized through customizable screens and user interfaces that display event information.

Components of PSIM
PSIM provides a complete situation awareness and physical security management solution to effectively manage any security, business-critical, or emergency situation in real-time. Unlike access control, alarms, or video systems, PSIM is not limited to managing events from a single input or trigger within a given subsystem, or within one group of hardware devices. A PSIM solution has the ability to aggregate information from all its connected systems for a more holistic view of a situation, automating processes and actions throughout to better manage the area. A scalable PSIM solution includes several primary components.

Open connectivity and integration
This component offers a platform for the connection and management of multiple disparate security systems. It should be capable of integration with other business systems within a corporate IT infrastructure, such as enterprise resource planning (ERP), data warehouses, and provisioning systems. The PSIM platform must be open and ‘vendor-agnostic,’ providing capabilities to connect to any input sensor or external application.

Real-time policy and configuration management
This element creates integrators to define and change policies and parameters related to various connected devices in the underlying subsystems, such as access control and video.

[4]

Correlation and verification engine
The engine generates the ability to integrate events and alarms from multiple systems along with other information––such as time and geography––to automatically assess situations, then responds to them in accordance with established rules and policies.

Rules engine
The rules engine allows a step-by-step action plan for security operators, based on pre-determined rules and policies, to more effectively respond to and manage security and critical events. The rules-based workflow includes the complexity to adapt to escalating situations.

Geospatial engine
This component uses location coordinates to dynamically locate various devices, people, and assets, and creates relationships between them. It instinctively knows which camera is closest to an event and can automatically provide the security operation with an image from that camera.

Dynamic mapping
Mapping offers the ability to graphically display situational information for security operators with a picture of the event, location, and scope in real-time.

Post-event reporting and analysis
Reporting and analysis create an audit log for the forensic review of event details, and record the actions taken during and after the event. This feature includes the capability to develop customized reports for analysis of multiple events and trends to optimize response operations.

[5]

Municipal safety and security integration
Located 24 km (15 mi) north of Dallas, the city of Plano, Texas, sought a centralized management platform that could bring together its disparate security systems, including the ever-changing number of city agency participants. The city deployed a comprehensive PSIM solution to upgrade and modernize security systems in city buildings and facilities. Existing investments in security technology were leveraged to avoid the rip-and-replace approach.

The solution provided enhanced safety and security for citizens, enabling the city to collaborate and share resources with multiple city agencies in real-time for more effective responses to emergency situations. Plano is now able to integrate and manage all data from its security systems, devices, and collaborating city agencies to enable command center operators to easily distribute information to decision-makers for improved situation management.

‘Situation management’ is a more holistic view of incident information than ‘alarm management,’ which is more typical within the security industry. As opposed to viewing each piece of alarm data independently, situation management combines and correlates information from multiple alarm and data sources to provide a broader view of the overall ‘situation’ versus an individual alarm. This broader view of a situation provides a more intuitive and informative solution for managing incidents and crisis-type events.

Large-scale security system integration
At a large, Middle Eastern international airport, 12 new operations centers were constructed and integrated. PSIM/crisis incident management systems were installed for emergency event management and optimized situational awareness. These emergency event management features provide expanded capabilities for the assignment, tracking, and communication of manpower and assets during crisis/emergency situations.

These systems were also interfaced with local emergency response organizations for sharing of incident information and combined event notifications. Each control center was equipped with a number of dedicated PSIM workstations for use in daily security event management and during crisis situations.

[6]

This project included the integration of many disparate systems into the PSIM environment, including:

• telephone;
• geospatial mapping;
• records management;
• e-mail;
• automatic vehicle locator;
• access control;
• video;
• global positioning system (GPS) transponder sources;
• emergency dispatch;
• perimeter intrusion detection;
• radio; and
• airport operations database systems.

Return on investment (ROI) of labor savings
At a well-known global broadcasting company, 13 existing security control centers located throughout England, Scotland, and Northern Ireland were consolidated into one primary security control center. All security-monitoring activities for facilities throughout the United Kingdom are now managed from a single location.

The project included the design and deployment of a comprehensive PSIM software solution to integrate all security subsystems into a common operating platform for unified control and enhanced event management and monitoring functionality. The PSIM solution integrated the following systems:

• access control;
• intrusion alarm;
• video surveillance;
• intercom;
• radio; and
• fire alarm.

These individual systems were integrated to enable the full decommissioning of the existing security control centers, and the relocation of alarm and event monitoring activities to primary and secondary control centers. The ROI of labor savings achieved through this consolidation of monitoring activities took just over one year and drove the financial business case for the project.

Understanding the specialized requirements for PSIM implementation
As a software-based solution requiring the integration of other hardware and software systems, and the customization of policies, rules, and user practices, the full PSIM solution requires a non-traditional, multi-disciplined consulting, engineering, and installation approach.

[7]

PSIM deployment tasks typically include:

1. Analyzing the existing system’s environment to identify integration requirements.
2. Evaluating security operations and security systems use.
3. Consulting with users to identify security policies, procedures, and strategic plans.
4. Developing the functional software performance requirements.
5. Custom engineering of application programming interface (API) software for subsystem connectivity.
6. Software and system environment testing and test plan development.
7. Identifying and designing network communication enhancements.
8. Installing and modifying security systems and computing hardware and software.
9. Customizing software application rules and workflow programming.
10. Developing and administering customized user training programs.

The varied skill sets, knowledge, and experience required to deliver all of the elements of a PSIM project have challenged security integrators to expand and update their usual methodologies and resources. Security integrators are the system installers and service providers whose project scope of work typically includes the integration to other building and enterprise systems. Security integrators are typically contracted under a general contractor or directly to the owner. Technicians typically install PSIM solutions with a laptop in their hands, rather than a tool belt on their waists.

The majority of security integrator organizations do not maintain the full array of multi-disciplined, in-house staff required to deliver PSIM projects. Instead, most integrators must rely on many subcontractors in various specializations and heavily depend on their PSIM software vendor partner to complete the solution.

Qualified security integrators need to demonstrate a thorough understanding of PSIM solutions and the benefits provided to end-users. They should keep dedicated personnel who have received training and certification with the products. Additionally, security integrator team members should be able to demonstrate past successful PSIM project experience and have backgrounds of varying disciplines to include:

• security management consulting;
• security systems engineering;
• network design and engineering;
• software development;
• database integration; and
• project management.

Finally, qualified security integrators should also be able to demonstrate their ability for ongoing technical support of the PSIM solution after initial deployment.

A strong deployment team will help to ensure a firsttime, successful PSIM solution and the ongoing technical support needed to maintain, customize, and grow the solution with the end-user’s organizational needs. A typical PSIM deployment team includes:

• technical project manager–overall project manager with technology specialization;
• solution architect–consults with owner and defines the overall technical solution;
• solution engineer–builds the software configuration and programming scheme;
• IT/network specialist–evaluates and designs IT/network enhancements needed;
• security system engineer–plans and designs improvements needed to security subsystems;
• application specialists–performs the system programming and configuration activities;
• software development engineer–develops integrations and interfaces with subsystems;
• software test and evaluation engineer–develops and performs testing of overall solution;
• trainer–develops and provides training to owner/user personnel; and
• technical support specialist–defines and builds customized solution support program.

Key elements of a specification for a PSIM solution
To adequately convey the full scope of work for a PSIM project and to properly define all of the elements necessary to receive accurate bid/proposal pricing, key elements of information must be included in the PSIM specification and request for proposal (RFP) documents.

Detailed description
A detailed description of the project scope of work should include not only the PSIM software design and deployment requirements, but also a definition of work required to prepare the existing subsystems for incorporation into the PSIM environment. These include upgrading existing systems, conversion to TCP/IP communication protocols, and establishing network connectivity to subsystem components.

Building and floor plan
Detailed building and floor plan information should also be included. The quantity of maps and floor plans to be incorporated into the PSIM software are calculated in the pricing of the software and professional services required.

Existing business processes
An overview of the existing business processes within the owner’s environment, including security alarm and emergency response plans should be included. The extent to which security response plans must be developed and updated affects the pricing of the professional services required.

[8]

Inventory of subsystems
A full inventory of existing or planned subsystems that will be connected to the PSIM solution—including manufacturer name, model, series, part, and version information (i.e. access control, video management software, digital video recorders, intrusion alarm panels/systems, intercommunications systems, and radio systems)––must be included. Each subsystem ‘connector’ is a cost item for PSIM solution pricing.

Data types
A definition of the data types expected to be received from each of the installed or planned subsystems for use in the PSIM environment must also be incorporated in the specification. The complexity of each subsystem integration can affect the engineering services that will be required.

Subsystem field components
A full inventory of subsystem field components will be mapped and incorporated into the PSIM software environment (i.e. cameras, card readers, alarm sensors, and call stations). PSIM software pricing and professional services labor costing are directly calculated from this data.

Monitoring locations
The number and location of centralized, regional, or local system monitoring locations, as well as the number of concurrent users of the solution, should be incorporated in the specification. This information is used in defining the number of client workstations, software user licenses, and computing hardware and resources needed.

Compliance matrix
A technical compliance matrix should be provided that details the technical capabilities, features, functions, capacities, and performance requirements of the PSIM solution. Bidders and proposers should be required to respond with the extent of their proposed solution’s compliance to each item.

Security integrator requirements
Minimum security integrator requirements should also be incorporated to ensure qualification for deployment of PSIM solutions. These should include:

• past successful experience deploying PSIM solutions for similar environments and project requirements;
• team member training and certification with the specific PSIM software solution and subsystems being deployed and integrated;
• project team member knowledge, skills, training, experience, and make up to include security subject matter experts, PSIM solution experts, IT/network specialists, software development engineers, and project managers;
• the ability to provide in-house professional services for the design, deployment, and support of the overall PSIM solution; and
• offices and professional service delivery capabilities at all of the owner locations involved in the PSIM deployment, whether local, national, or global geographies are required.

Creating an innovative security solution
With a full PSIM solution, key security solutions—which were formerly difficult, if not impossible to attain with available security technology—can be implemented. The practice of ripping and replacing systems can be substituted with leveraged investments in existing security technology, while updating and modernizing security systems. Separate security systems in an enterprise environment can be integrated into a single, common operating system for enhanced situational awareness. Additionally, ROI can be achieved through the regional or global consolidation of security control and monitoring centers. A successful, full PSIM solution can provide significant benefits and enhancements to an organization’s security and asset protection programs. Key benefits include:

• leveraging and extending physical security investments;
• reducing operational costs;
• improving security response times, effectiveness, and efficiency;
• minimizing risk; and
• impacting the company’s bottom line.

Designers and specifiers must understand PSIM is not an out-of-the-box installation. It combines software and highly technical professional deployment services to deliver an end-to-end, integrated physical security solution. By gaining knowledge and familiarity with the solution, designers and specifiers can effectively specify physical security information management solutions and select qualified integrators to effectively implement them.

Mike Webster, CPP, is the manager of the Global Security Center of Excellence at Johnson Controls. With more than 27 years of progressive government, corporate, and private security management and consulting experience, his career includes U.S. military security and counter-terrorist operations, security director assignments for large public companies, and ownership and management of a security consulting and engineering company. Webster can be reached via e-mail at michael.a.webster@jci.com[9].

Source URL: https://www.constructionspecifier.com/managing-physical-security-information/

---