NERSA Contracting Capabilities & Security Project Planning Guide

NERSA Contracting Capabilities & Security Project Planning Guide

This NERSA-managed guide helps general contractors, security integrators, and facilities teams turn security requirements into clearly assigned work packages. Use it to understand NERSA’s commercial and industrial capability areas and prepare a better installation or subcontractor brief.

Northeast Remote Surveillance and Alarm, LLC (NERSA) provides the service information linked throughout this guide. Confirm the project-specific scope, qualifications, location coverage, staffing, and schedule directly with NERSA; this resource does not establish a subcontract or promise availability.

Define the delivery model first

A labor-only assignment, a materials-and-installation package, and a fully configured system require different responsibilities. Before comparing proposals, state who designs the system, supplies equipment, approves substitutions, installs supporting infrastructure, configures software, witnesses tests, and supports the owner after completion. Where another trade or vendor owns a dependency, name that party and its required delivery date.

Explore the contracting work packages

Video surveillance installation

Start with the operational question for each view: observing activity, reviewing an incident, or identifying a relevant detail. Site lighting, mounting height, obstructions, distance, and retention needs affect the scope. A camera count alone cannot establish whether the intended result is achievable.

Define the contractor’s responsibilities

Separate camera supply, mounts, cable pathways, lifts, network configuration, recording, licensing, and user setup. Confirm who provides power, storage, network capacity, and approved mounting locations.

Agree on acceptance and handover

Record representative views and playback results, demonstrate evidence export, verify time settings, and document camera labels, recording settings, permissions, and equipment ownership.

Explore the related NERSA capability.

Access control and door coordination

Map the people and workflows using each opening: staff, visitors, deliveries, contractors, and after-hours users. Document schedules, exceptions, and the owner’s administrative process before selecting a device package.

Define the contractor’s responsibilities

Assign doors, frames, locking hardware, power, cabling, network connections, credential setup, and integration responsibilities. Coordinate egress and life-safety questions with the responsible professionals and authorities for the project.

Agree on acceptance and handover

Test approved access scenarios, schedules, exception handling, and owner-approved responses. Provide opening identifiers, a permissions handover, and training for adding, changing, and removing users.

Explore the related NERSA capability.

Intrusion alarm work packages

Define the areas and events to be monitored and the people responsible for using the system. Occupancy, shift changes, loading activity, environmental conditions, and existing equipment affect detection and operating procedures.

Define the contractor’s responsibilities

Distinguish field installation from programming, communications, monitoring enrollment, and ongoing service. Name the party coordinating test windows and communicating with the owner and monitoring provider.

Agree on acceptance and handover

Use an authorized test plan to verify named zones, expected notifications, user procedures, and exception reporting. Record unresolved deficiencies and the party responsible for correction before acceptance.

Explore the related NERSA capability.

Fire alarm and life-safety coordination

Treat life-safety work as a separately defined professional scope. Identify the project’s design team, responsible contractor, owner representatives, required approvals, and the interfaces with other building systems.

Define the contractor’s responsibilities

Make responsibility for design, permits, installation, testing, inspections, documentation, and existing-system transitions explicit. Requirements vary by location and project; a generic educational checklist is not an approval or a code determination.

Agree on acceptance and handover

Agree on the required test and inspection records, approved drawings, owner training, and deficiency resolution. Direct specific system and jurisdiction questions to the project’s qualified professionals.

Explore the related NERSA capability.

Monitoring and response coordination

Monitoring performance depends on a defined event and response process. Identify the event types, who receives notifications, who may authorize changes, and how contact details and response instructions are maintained.

Define the contractor’s responsibilities

Separate installation from communications services, monitoring enrollment, recurring charges, and owner response responsibilities. Confirm supported equipment and the provider’s agreed scope before making assumptions about existing systems.

Agree on acceptance and handover

Document authorized testing, signal descriptions, contact verification, account ownership, and the handover of operating instructions. Confirm who supports a communications fault or a change in site operations.

Explore the related NERSA capability.

Remote video monitoring and live talk-down

Begin with operating hours, permitted activity, areas of concern, and the response the owner expects. Explain how site lighting, connectivity, camera views, and changing activity may affect event evaluation.

Define the contractor’s responsibilities

Assign the camera and network prerequisites, any audio equipment, configuration, monitoring setup, and testing. Confirm site-specific privacy and operating requirements with the owner and the responsible professionals.

Agree on acceptance and handover

Demonstrate agreed scenarios under authorized conditions. Record notification paths, escalation instructions, operating schedules, and the process for updating the provider when site activity changes.

Explore the related NERSA capability.

Vehicle gate access and entry workflows

Map employees, deliveries, visitors, queues, and unusual arrivals before defining a vehicle entry system. The security scope should fit the property’s actual traffic pattern and the owner’s operating procedures.

Define the contractor’s responsibilities

Coordinate gate equipment, civil work, electrical supply, controls, communications, access credentials, and intercom responsibilities. Identify which specialist owns gate safety and required acceptance procedures.

Agree on acceptance and handover

Test approved entry scenarios and handoff between systems with the responsible trades. Deliver system ownership records, operating instructions, and the process for reporting a fault or changing permissions.

Explore the related NERSA capability.

Intercom and visitor entry coordination

Decide who answers a visitor, how they identify the destination, and what happens when the normal contact is unavailable. Locate entry points and the staff roles that must participate in the workflow.

Define the contractor’s responsibilities

Define station installation, power and data, network and account setup, any door or gate interface, and training. Confirm supported capabilities with NERSA for the selected equipment and project scope.

Agree on acceptance and handover

Demonstrate the approved call path, escalation behavior, and entry authorization workflow. Provide endpoint labels, administrator ownership, and clear instructions for common staffing changes.

Explore the related NERSA capability.

Unified and integrated security systems

Describe the operational result of an integration rather than assuming every platform can exchange every event. Identify the system of record, the data owner, the permitted actions, and the supported interfaces.

Define the contractor’s responsibilities

Assign configuration, licensing, credentials, network approvals, version compatibility checks, and change control to named parties. Include responsibility for existing-system limitations and third-party participation.

Agree on acceptance and handover

Test a written sequence of operations. Record the expected result, observed behavior, exceptions, and the party responsible for correction. Hand over configuration documentation and future change responsibilities.

Explore the related NERSA capability.

Cabling, network, and wireless infrastructure

Field devices depend on suitable pathways, power, network capacity, and environmental protection. Survey existing routes and owner restrictions before assuming cable reuse or a wireless link is appropriate.

Define the contractor’s responsibilities

Separate pathways, cable installation, termination, labeling, testing, switches, network configuration, grounding-related responsibilities, and outdoor support work. Assign specialized work to the appropriate project trades.

Agree on acceptance and handover

Require the agreed cable or link test records, device and port schedules, labeling, and as-built documentation. Confirm that infrastructure supports the selected security application under the agreed operating conditions.

Explore the related NERSA capability.

Upgrades, retrofits, and system takeovers

Inventory existing equipment, account ownership, configuration access, licenses, maintenance history, and known faults. Define the problem being solved before deciding what can remain in service.

Define the contractor’s responsibilities

Make reuse conditional on an agreed survey and validation process. Name the parties responsible for access to existing systems, transition windows, owner communications, and recovery planning if the cutover cannot be completed.

Agree on acceptance and handover

Document retained and replaced components, test results, changed operating procedures, and unresolved limitations. Securely transfer access to authorized owner representatives and agree on ongoing support boundaries.

Explore the related NERSA capability.

Multi-site installation and regional delivery

A common standard helps distributed sites, but each location still needs a readiness review. Record site contacts, access hours, infrastructure, local restrictions, and differences that affect the standard scope.

Define the contractor’s responsibilities

Create a repeatable work package with site-specific exceptions. Assign materials, staging, scheduling, travel, progress reporting, change approval, and closeout review. Confirm NERSA coverage and availability for each actual site.

Agree on acceptance and handover

Pilot the standard at an agreed location, resolve issues, and use consistent acceptance records for later sites. Track equipment, documentation, training, and outstanding items separately for every facility.

Explore the related NERSA capability.

A practical proposal comparison worksheet

Compare equivalent responsibilities before comparing totals. For each line below, record the proposed party, included deliverable, exclusion, dependency, and evidence required for acceptance.

  • Site survey, design assumptions, and approved device locations.
  • Equipment, licenses, consumables, shipping, and approved substitutions.
  • Pathways, cable, power, network, lifts, and site protection.
  • Installation, labeling, configuration, integration, and testing.
  • Schedule, mobilization assumptions, work windows, and change process.
  • As-built records, training, credentials, warranty terms, and support boundaries.

Regional planning for Pennsylvania and the Mid-Atlantic

For Lehigh Valley, northeastern Pennsylvania, and other regional projects, record the actual site locations and required attendance windows. Do not treat a broad service-area label as confirmation that a particular crew or specialty is available on a particular date. Coordinate travel, staging, parking, escorts, and local project requirements before mobilization. Consult NERSA’s service-area information and confirm project coverage with NERSA.

Continue your planning

Use the scope planning guide, handover checklist, and planning glossary alongside this capability guide.

Facility-specific guides