Plans

Plans and physical details provide the first two views. They show how the security devices relate to the building and site and to the conduit system.

Floor plans and site plans are sometimes called “maps” by the uninitiated. A plan view is any drawing that illustrates a view of the area looking down on it from above. For ceilings, the term is reflected ceiling plan, based on the idea of placing a mirror on the floor of the building and viewing the ceiling by looking up at it from the mirror on the floor, thus making it possible to see the underside of the ceiling by looking down on it. Site plans are plans that show the locations of buildings and structures on a property, whereas floor plans show the areas within the building, including its walls, doors, windows, and often fixtures.

Floor plans are normally created by the architect and adapted for use by other consultants. When working on projects in which an architect is involved, including both new construction and renovation projects, it is almost always possible to obtain “architectural backgrounds” in the form of CAD files for new construction. This may not be the case for retrofit projects where there is no architect on the job and CAD files may be hard to find or obsolete. In such cases, the CAD designer may have to create clean backgrounds from one of the following methods:

- Scan a paper drawing to a PDF file and clean up the PDF file of extraneous information, then use the PDF file as a background for new CAD work.

- Receive drawings in the form of PDF files from the client. Process as noted above.

- In rare cases, the CAD designer may have to generate entirely new backgrounds from Fire Evacuation Plans or Survey Sketches.

The security designer will need to obtain the CAD files in a form usable both to him or her and to others (typically AutoCAD files). It is advisable for the security designer or CAD staff to modify the architect’s backgrounds to a 50% opacity screen (gray line in lieu of black line) form. This will ensure that the security designer’s work will stand out compared to the architectural background, making the system devices and conduits easy to identify versus the building and site.

Many architects require all consultants to work in Revit™, which is a 3D Building Information Model (BIM) architectural environment. Typically Revit projects store the backgrounds centrally on the architect’s servers, and consultants access those files for their own work. Revit projects help assure that conflicts in the physical space do not occur, such as assigning terminal cabinets to a space occupied by a HVAC duct, or locating a camera in an atrium where its view will be blocked by a tree in another design. In the Revit design environment, all designers can see each other’s work in 3D so they can move devices in order to avoid such conflicts.

The designer will use a standardized set of device symbols to represent security devices, including card readers, cameras, door locks, request-to-exit devices, door position switches, alarm devices, security terminal cabinets, conduit pull-boxes, power supplies, and switches. These will be shown on the plans to identify where they should be installed. Each device will require a note and/or detail identifying its intended mounting height and special mounting provisions. For example, does the device require reinforcement to ensure that it does not fall during an earthquake? For wall-mounted devices, it is advisable to utilize a symbol that will identify their exact intended locations on the wall. This can be done by creating symbols that have “mounting tags” with a point or dot to indicate the exact mounting location in the plan. For every device type on every plan, it is important to illustrate a mounting detail of that device (see Physical Details). A detail callout is needed for each unique device on each plan, referring the reader to the appropriate physical detail. It is common to combine detail callouts and notes together on a single leader pointer, pointing to the device, which minimizes drawing clutter.

For Revit designs, the designer will also need a set of three-dimensional templates of each wall- or ceiling-mounted device, so that it is photo-realistic in the final drawing. Additional benefits of Revit are that the mounting assembly of wall-mounted devices includes the conduit and boxes to which the devices mount. This helps assure a completely integrated design.

Floor and site plans show not only security system devices but also the conduits that connect them together. Typically, conduit types are shown with varying line types to designate the type of conduit. Conduit types include:

• Nonflexible conduits, including rigid (steel), aluminum, and Schedule 40 and 80 (PVC plastic)

• Flexible conduit

• Waterproof conduit

• Armored cables (cables that are enclosed in flexible conduit)

Conduit may also be identified by line types to signify existing and new conduit runs or runs in ceilings, walls, or under floors and within concrete pours.

Conduit installation practices should be identified by reference to code or designated standard. These may include requirements for bushed chase nipple ends on conduits to eliminate the possibility of sharp edges (burrs) from ripping through cable insulation and for 200-pound test pull strings to be placed within empty conduits to facilitate the pulling of cables through the conduit. The security designer may also want to require that conduits be marked with a conduit number corresponding to a conduit number on the plan.

A drawing convention is to show conduit paths as conceptual paths only and allow the field installer to make final determination as to the appropriate actual path of the conduit. This is because there may be obstructions that are encountered in actual practice that may not be known to the designer. However, it is incumbent upon the designer to attempt to show a practical path. I once saw a conduit drawing that illustrated a conduit path across the fifth floor from one side of the building to the other side right through a 10-story open atrium. I have also seen a conduit illustrated from the upper floor of one building to the upper floor of another nearby building. I wonder if there really is a conduit somewhere in the sky between two buildings.

Each conduit shown on the plan should include a projected size (this might change in the shop and field drawing submittal based on the requirements of a specific system versus the one planned by the consultant). It is also important to note the size and type of each pull-box into which conduits connect.

Note that conduits terminate to any of several devices, including j-boxes (similar to light switch or electrical outlet boxes), pull-boxes (boxes through which wire is pulled but where no terminations should be made), terminal or junction boxes (where wire terminations may be made but not where powered equipment would be located), and equipment cabinets (where powered equipment will be located). All locations where cable terminations and connections occur should be accessible, and they should never be located above a ceiling space unless an access panel is provided.

Risers

A riser is a drawing that illustrates another view of the relationship of the devices to the conduit system, specifically the conduits that rise from floor to floor (hence the term riser diagram). The riser diagram also usually illustrates power drop points, including information about the source panel and breaker for each power drop. Although some security system designers like to illustrate all system conduit on the riser diagram, which can be useful, it is generally recommended to show only the vertical conduits and the major laterals leading to power drops and major equipment rooms, not every lateral conduit. This is recommended to keep the drawing simple and to maintain accuracy between the conduits shown on the floor plan and those shown on the riser diagram. If all conduits are shown on both plans, it is likely that somewhere there may be a mistake, especially when a minor change occurs in the design that ends up being shown on one plan but not the other.

Radio Frequency Communications Paths

Radio frequency (RF) communications paths are just as important to show as conduit paths. When showing RF communications paths, it is advisable to show them as line-of-sight paths and Fresnel signal paths. The line-of-sight path is the clear path directly between a transmitting and receiving antenna. The Fresnel signal path defines the outer boundary of the signal that is sensitive to moisture and multipath reflections. It is also a good idea to show the intended direction of communications toward the “home” RF node.

Single-Line Diagrams

Single-line diagrams are also commonly called “block diagrams.” Single-line diagrams offer the third view—that is, the relationship of the security devices to other security devices. Single-line diagrams represent the signal flow path, not the conduit or wiring path. Although these may often be the same, the conduit drawing illustrates the physical relationship, whereas the single-line diagram illustrates the electrical or signal relationship.

The single-line diagram for each system should illustrate the major devices that either signal, process a signal, or make the results of that signal available to a security professional to use in securing the facility. For a video system, this includes the cameras, pan/tilt drives, receiver/drivers, codecs, digital switches, servers, and workstations. For an alarm/access control system, it includes edge devices (e.g., card readers, electrified locks, door position switches, request-to-exit devices, gates, gate operators, loop detectors, alarm origination devices), alarm/access control system controllers (data-gathering panels), switches, servers, and workstations. For security intercom systems, it may include field intercom stations, bullhorns, digital switches, and workstations.

Each single-line diagram should include power pickup points and system interconnections to other systems.

For example, if a digital switcher is being shared between all three systems, it can be shown on one with match points to its connections on other systems, or it can be shown on all three systems using the same switcher device nomenclature (e.g., SW-2), with a note that it is indeed the same switcher. Usually, when the exact device is shown on two or more drawings, it is shown in black lines on one and gray lines on the others, with a detail callout referring the observer to the first drawing. It is also important to note switcher input numbers in order to ensure that there are no duplications.

Title Sheet

The title sheet is a drawing that precedes all of the others. It should include the following:

• The project and system title in large bold letters; for example, “Mega Corp—Integrated Security System”

• A list of the symbols used throughout the drawings (This may include default sizes, mounting heights, and a place for remarks.)

• A list of abbreviations used throughout the drawings—not device abbreviations (these are listed under the device schedule) but other abbreviations, such as “NIC: Not in Contract.” (Try to make the list exhaustive. It is extremely frustrating for readers to find an abbreviation that is intuitive to the security designer but nobody else can figure it out.)

• A set of general notes that apply throughout all the drawings (e.g., notes about conduit and power requirements and environmental requirements for typical devices)

• A device schedule listing device abbreviations (e.g., IC—field intercom)

• A cable schedule listing all the cable types used throughout the drawings

• A drawing list including drawing numbers and drawing sheet titles (It is useful on large drawing packages to further break these down by drawing type and sometimes location specifics on multisite drawing packages.)

Title Block

The title block is the standard border of each drawing in the drawing package. Its form may be dictated by the client or architect, but it should include the following:

• A border delineating the drawing boundaries

• Sector identifiers for plans (e.g., row/column markers to help people on the telephone refer to a specific device by its location in drawing sector “C-6”)

• The name of the project and system

• The name of the specific drawing (e.g., “Riser Diagram/Fifth Floor Plan”)

• The drawing number

• The initials of the designer, engineer, draftsman, reviewer, or other personnel

• The date of the original drawing issue

• The name of the original drawing issue (e.g., “Construction Document Issue” or “Issued for Pricing”)

• The revision number (delta number), date, and revision issue name (e.g., Addendum #4)

• The names of the client, architect, major engineers, and the security design firm

Introduction

The introduction should contain a description of the project (where, what, new or retrofit, etc.) and a general description of the deliverables (specifications, drawings, addenda, and bulletins).

Precedence

This article is not typically used in new construction projects because its elements are normally included in Division 0, General Provisions. This article instructs the installer as to the order or precedence of documents and what to do if any conflict occurs during the project. Change orders, language for training, submittals, and screens are all included in this article.

System Descriptions

I describe the total integrated system and each subsystem that makes it up by using four distinct methods to describe each element of the overall system.

Provide an overview of what the entire system is, what subsystems it has, and what the overall system should do.

System Infrastructure

In this section, list all of the switches, router, firewall, fiber-optic media converters, RS-485/RS-232 media converters, and others.

Monitoring and Control System

In this section, list the servers and workstations, external storage media, operating systems, microphones and speakers, footswitches, and any other console devices, such as monitor mounts, desks, and ergonomic chairs. Do not list application programs except as they relate to the management of the computers. Application programs should be listed under the systems they serve.

Digital Video System

The digital video system section should list any cameras, lenses, mounts, enclosures, codecs, application software, and other DVS items.

Voice Communications System

List any field intercom stations and interface devices, intercom master stations, switches, and software.

Alarm/Access Control System

List all access control devices, including

• Card readers and cards

• Photo ID equipment (e.g., digital camera, lamp, background, badge holders, badge printers, clips, lanyards)

• Electrified door locks

• Door position switches

• Request-to-exit devices

• Infrared

• Electrified panic hardware

• Push buttons, etc.

• Motion alarms

• Other alarms

• Output control devices

• Access control software

• Perimeter detection system: software, hardware, cable, attaching devices, interface devices

• Miscellaneous products

• Spare parts

Wire and Cable Installation Practices

This section should include

• Conduit and wire pulling practices

• Wire lacing and dressing standards

• Prohibitions against class mixing

• Wire tagging

• Other standards and practices as appropriate

Commissioning: System Setup and Configurations

• Final hardware configurations and testing.

• Camera focusing, etc.

• Perimeter alarm balancing, etc.

• Wireless node configurations, balancing, and any other appropriate configurations.

• Setting up operating systems and domains

• User authorizations

• System configurations

• Application program loading and configurations

• Enterprise system configurations

System Testing: Testing Overview

• Test equipment requirements

• Preliminary checks and testing requirements

Acceptance Testing

After the system is tested by the contractor to his or her satisfaction, acceptance testing begins.

• Statement of the scope of the required tests

• Test scheduling readiness and documentations

• Wireless testing

• Infrastructure testing

• System testing

• Remedial correction of testing observations

Project Completion

• Notice of completion

The system infrastructure schedule outlines in spreadsheet form all of the system infrastructure elements, including switches, routers, fiber optic communications nodes, uninterruptible power supplies, and the like. Any device that connects system elements together or supports their stable and safe operation should be listed. At a minimum, spreadsheet fields should include the site, building, location, floor, area, device by category number of ports, and remarks.

Control and Monitoring System

The control and monitoring system is designated as a separate system on larger security systems and may be included as part of a subsystem or smaller system. This system may include servers and workstations, video monitors, radios, headphones, keypads, mice, and the like, plus a remarks field. At a minimum, spreadsheet fields should include the site, building, location, floor, area, device by category, device specifications (if relevant for bid), and the like.

Alarm/Access Control System

The alarm/access control system schedule should include credential readers, locks, request-to-exit devices, door position switches, alarm points, output controls, alarm/access control system panels, parking gate controllers, and remarks. At a minimum, the spreadsheet should include site, building, floor, area, devices by category, and remarks.

Digital or Analog Video System

The video system schedules should include cameras, lenses, pan/tilt drives, enclosures, codecs (multiplexers, quad units, and matrix switches, if analog), video keyboards, and the like. At a minimum, the spreadsheet should include site, building, floor, area, devices by category, and remarks.

Security Intercom System

The security intercom system schedule may be on its own table or might be included as part of the video system, if so equipped. The schedule should include field intercom stations, security intercom stations, intercom bullhorns, amplifiers, microphones, headphones, intercom master stations, and matrix switches (if analog). At a minimum, the spreadsheet should be formatted as discussed previously.

System Interfaces

System interfaces may be on their own schedule or could be implemented into the others. System interfaces should include the connection points between systems and the functions to be performed.

Power

Power schedules should include the high-voltage power drops locations and the devices served at each location. Some designers prefer to include low-voltage power supplies in this schedule. The spreadsheet should be formatted as discussed previously.

Cable

A system cable spreadsheet should include the cable types, brand, model of cable, and the outside diameter and rating of the cable (e.g., voltage class of insulation, indoor, plenum [above ceiling] rated, direct burial rated)

Conduit and Fill

Some designers place conduit and fill schedules on each floor, site, or ceiling plan in the construction drawing package. This made good sense in the old days when virtually every system utilized very similar system wiring architecture. However, as system architectures become more diverse, it can in fact be confusing to the bidders to dictate a specific wiring scheme when the products they prefer to submit use another. For many systems, I now leave conduit and fill schedules to the shop and field drawing set, to be submitted by the contractor who is awarded the project. Conduit and fill schedules, if shown on the construction drawing set, should include the conduit number for each conduit shown on that specific plan, its size, and the types and numbers of wires to be in each conduit (the fill).

General Network Device Configuration Schedules

Network device configurations should be illustrated conceptually on a configuration schedule. The configuration schedule should have two parts or be shown as three schedules (hardware configuration, firmware/software configuration, and user access configurations). The schedule should include all the basic requirements the security system designer intends for the system to operate under as a prerequisite to its stable and safe operation. These may include disabling unused switcher ports, access classes and permissions, for example.

Shop and Field Drawings

In addition to the schedules identified previously for construction drawing packages, shop and field drawings should also include conduit and fill schedules as described previously, if not included in the construction drawing package.

Device Wiring Schedules

A device wiring schedule (also called “run sheet”) will list the exact input and output connections from and to every device in the security system. These are typically done by cabinet, rack, or console assembly. Each schedule will show all of the devices for that assembly, its connection point, and the connection by connector type and wiring type. This will be correlated to its source or destination assembly, device, and wiring point. A good practice is to show this assembly in the center of the spreadsheet and the source points to the left and destination points to the right of the schedule.

Configuration Schedules

System configuration schedules should include the exact desired configuration for each programmable device. Configurations may be shown for hardware devices, firmware or software devices, and users by class.

Physical Details

Physical details are drawings that identify all of the mounting and installation requirements for each device. These may include mounting height, positioning, structural mounting requirements, conduit and box connections, and the like.

System Interfacing Details

System interfacing details illustrate connections between systems that are necessary to create integration functions. These should usually also include a brief sequence of operation of theory of operation, not in conflict with the description provided in the specifications. Interfacing details should be provided from and to other systems being interfaced, possibly including elevators, parking, building automation, PABX, VoIP, radio, lighting, signage, concrete, and landscape.

Revised Construction Budget

Following completion of the construction drawing package, it is common to make a final revision to the construction budget.

Complete Specification

The complete specification provided as part of the construction drawing package must include all of the system requirements, fleshing out the outline provided in the design development issue.

Review Drawings, Specifications, and Prioritized Budgets

Following submission of the final construction documents package, the client may perform a final review. This may also include an interdiscipline coordination review. The client will return the package with final comments.

Revise after Review

Following receipt of the final comments, the designer will perform final corrections and issue the package for bid through proper project management channels.