Authorized dealer · Certified installers · Charlotte, NC headquarters
360 Technology Group is an authorized Avigilon dealer and certified installer
We have been selling, installing, programming and servicing Avigilon systems across North and South Carolina since 2018 — more than 8 years. Our scope covers Avigilon Alta cloud access control, Alta Video cameras, Unity Video and ACC, smart readers, mobile credentials and video intercom.
- Authorized Avigilon dealer — we quote and supply genuine Avigilon equipment, licensing and subscriptions.
- Certified Avigilon installers — our technicians install, wire, program, commission and document the system.
- Repair and takeover — we service, troubleshoot, expand and take over existing Avigilon installations we did not originally install.
- 24/7 emergency service — on-call service technicians for emergency repairs, plus scheduled preventive maintenance.
We cover every city in North Carolina and South Carolina from our Charlotte headquarters. Request a quote or service call Call 704-726-4254
Avigilon equipment we supply and install
Avigilon spans cloud and on-premise on both the video and access sides — Alta for cloud, Unity for on-premise. Choosing between them is the first real decision, and it drives cost far more than the camera model does. Here is a cross-section of what we install; the camera range in full is on the Unity Video page.
H6A Dome
The default interior and sheltered-exterior camera, with video and audio analytics onboard. Dome housings resist tampering and hide the aim, which matters in public areas.
H6A Bullet
Exterior runs, long views and anywhere the visible direction of coverage is itself a deterrent. Mounting height and glare direction decide whether it produces evidence.
H6A PTZ
Pan-tilt-zoom for large yards, lots and perimeters. Worth remembering that a PTZ pointed elsewhere records nothing — pair it with fixed cameras rather than replacing them.
H5A Multisensor
Several sensors in one housing covering a wide area from a single cable drop and a single mount. Usually the cheapest way to cover an intersection of corridors or an open lot corner.
H5 Pro
Very high resolution for large scenes where you need to zoom into recorded footage after the fact rather than at the time.
L6A LPR camera
Enterprise plate recognition. Plate capture needs its own camera, angle, shutter and lighting — a general-purpose camera pointed at a driveway will not read plates reliably.
Unity AI NVR 2
On-premise recording appliance with analytics. Sizing follows retention, camera count and bitrate, and RAID plus a UPS are not optional on a system anyone will rely on.
Alta cloud video
Cloud-managed video with no on-site recorder to maintain. Verify upload bandwidth and retention before committing — this is where cloud video projects fail.
Alta smart reader
Multi-technology reader supporting mobile, card and fob. Specify OSDP rather than Wiegand wherever the full design supports it.
Alta 8-door smart hub
The panel behind the doors. Door count, expansion capacity and offline behavior during an outage drive the selection.
Avigilon Alta was formerly Openpath — see our Avigilon Alta access pages for the cloud access platform and its hardware, and Unity Video for on-premise video and the full camera range. We install, migrate and service both, including takeovers of existing Openpath and ACC deployments.
Product images are supplied by the manufacturer. 360 Technology Group is an authorized Avigilon dealer and certified installer. Models, finishes and availability change — the proposal names the exact part numbers for your project.
North Carolina and South Carolina planning guide
Avigilon
A defensible Avigilon decision starts with the facility, the people operating the system and the evidence required at acceptance. This guide separates published product-family topics from the site-specific engineering decisions that determine whether the solution is appropriate.
Start with the decision, not the catalog
360 Technology Group evaluates Avigilon as part of a complete video-surveillance and evidence-management system. The recommendation should follow a field-verified problem statement, not a presumption that every published feature belongs in the project.
Discovery documents the current equipment, affected users, desired workflows, required integrations, security and privacy expectations, project constraints and measurable acceptance criteria. That evidence creates a fair basis for comparing reuse, migration and replacement.
For Carolina facilities, the scope should also account for occupied work areas, weather exposure, lightning and surge conditions, local construction coordination, network readiness, service access and the owner’s long-term administration model.
Detailed product and planning guides
Each card below opens a published guide with deeper product-family, design or implementation information.
Avigilon Alta Video Cloud Cameras and Integrations
Open the detailed product, design or implementation guide.
Avigilon Unity Video, Cameras and Analytics
Open the detailed product, design or implementation guide.
Capabilities and selection checkpoints
The cards in this section summarize information to evaluate; they are not separate pages. Availability and compatibility can change, so final models and releases must be confirmed against current manufacturer resources.
Avigilon Certified Partner
Confirm which current models, editions, licenses and dependencies support this requirement before procurement.
Avigilon ACC Software
Treat this as a design checkpoint; the final selection depends on field conditions and supported releases.
Authorized Avigilon Dealers
Compare retained equipment, migration effort, subscription impact and replacement options for this topic.
Who Should Use Avigilon ACC and Cameras?
Confirm which current models, editions, licenses and dependencies support this requirement before procurement.
How to Implement Avigilon Control Center and Cameras
Review compatibility, capacity, infrastructure and lifecycle implications with the complete system design.
Buying and Installing Avigilon
Document who configures, tests, administers and supports this function after the project is accepted.
Avigilon Certified Partners
Connect this capability to a named user workflow and a testable result at the actual facility.
Milestone vs Avigilon
Confirm which current models, editions, licenses and dependencies support this requirement before procurement.
Avigilon: New Products and Innovations 2019
Connect this capability to a named user workflow and a testable result at the actual facility.
An Overview of Avigilon Control Center
Treat this as a design checkpoint; the final selection depends on field conditions and supported releases.
Evidence to collect before design
A useful survey and stakeholder review should produce the following project evidence for Avigilon:
- Scene objectives for every camera, including identification detail, direction of travel and operating hours.
- Day, night, backlight, glare, weather, vibration, privacy and mounting conditions at each location.
- Retention period, recording mode, resolution, frame rate, failover and export requirements.
- PoE load, switching, uplinks, bandwidth, storage, remote access and network-security constraints.
- VMS, analytics, access control, alarm, intercom and third-party integration expectations.
- User permissions, evidence handling, health monitoring, software support and replacement planning.
Architecture and integration review
Image objective
Specify the event and visual detail the camera must capture instead of selecting resolution in isolation.
Recording architecture
Calculate storage, retention, failover and export needs for the complete camera count.
Network design
Validate PoE, bandwidth, segmentation, time services, remote access and monitoring with IT.
Analytics use
Connect each analytic to a response workflow and test it under representative site conditions.
Privacy and evidence
Document viewing rights, exports, retention, audit history and applicable organizational policy.
Lifecycle support
Track model status, firmware, VMS compatibility, licenses, warranties and replacement options.
Compare proposals on the same evidence
Product names and device counts do not make competing proposals equivalent. Ask each bidder to identify assumptions, exclusions, supported versions, owner responsibilities and the proof that will be delivered at acceptance.
| Comparison area | Evidence a complete proposal should provide |
|---|---|
| Fit for the operating need | A written explanation of how Avigilon supports the required users, events and workflows. |
| Compatibility | A supported-parts, software, license and integration matrix tied to the proposed architecture. |
| Infrastructure | Documented power, network, pathways, environmental and owner-furnished dependencies. |
| Acceptance | Named tests, expected results, exception handling and responsibility for correcting deficiencies. |
| Lifecycle | Current support status, update approach, warranty, subscriptions, spares and replacement planning. |
Deployment and acceptance sequence
- Discovery: agree on users, operating outcomes, retained systems, constraints and acceptance criteria.
- Field validation: verify dimensions, infrastructure, environmental conditions, pathways, power, network and integration points.
- Documented design: name the architecture, supported components, licenses, responsibilities, assumptions and change process.
- Staging and implementation: prepare configuration, backups, labels and test scripts before controlled field deployment.
- Operational acceptance: exercise normal use, exceptions, outages and recovery; then deliver training and system records.
Software, firmware and lifecycle responsibility
Record the installed model, hardware revision, software or firmware release, license or subscription, warranty and administrator ownership at handoff. Those details make later troubleshooting and upgrade planning materially safer.
Downloads, release notes, advisories and manuals should come from the manufacturer’s official portal. 360 Technology Group links to official resources and does not host firmware files locally. Some portals require an authorized customer, dealer or support entitlement.
Before any update, confirm the exact model and region, prerequisites, supported intermediate releases, backup, maintenance window, integration compatibility, rollback limits and post-update test plan. Cloud-managed products may control release timing differently from locally managed systems.
Choose between Avigilon Alta and Unity architecture
Avigilon Alta Video is cloud-managed, while Avigilon Unity Video is centered on locally hosted recording with cloud-enabled management options. The selection affects where video is stored, how remote users connect, which cameras and appliances are required, how internet loss is handled and who controls software updates. A proposal should explicitly name Alta or Unity instead of using “Avigilon system” as if the platforms were interchangeable.
| Decision | Alta Video | Unity Video |
|---|---|---|
| Management model | Cloud-based video management and health visibility | On-premise video management with optional Unity Cloud Services |
| Recording design | Camera and cloud architecture defined by the selected Alta deployment | Local NVR, AI NVR, appliance or server storage sized for the recording load |
| Primary fit | Organizations prioritizing simplified multi-site cloud operation | Organizations requiring local recording, advanced on-premise control or enterprise integration |
Analytics require a scene and response plan
Avigilon analytics can help operators find people or vehicles, prioritize events and associate video with access activity. Performance depends on camera model, mounting, lens, lighting, scene geometry and the enabled analytic mode. For each alert, document the region of interest, target type, schedule, expected operator action and escalation path. A pilot should measure useful detections and nuisance events under day, night, weather and occupancy conditions.
Unity Video editions and supported infrastructure have different camera, server, rule and analytic capabilities. Confirm the current Core, Standard or Enterprise entitlement, Smart Assurance coverage, supported camera firmware and storage appliance limits. For Alta, document cloud identity, roles, retention, device ownership, internet resiliency and the process for exporting evidence.
Review Avigilon’s official Unity platform and current system requirements before ordering.
Size the selected Avigilon edition and infrastructure together
Current Unity Video documentation distinguishes Core, Standard and Enterprise editions and provides different limits for cameras, client licenses, rules and advanced functions. Published figures are ceilings, not guaranteed server performance. Hardware, bitrate, analytics, playback and redundancy determine practical capacity. A design should name the edition, server or appliance model, usable storage, camera allocation, expected throughput and required Smart Assurance term.
For migrations from earlier ACC releases, inventory camera support, licenses, integrations, server operating systems and client workstations before selecting the upgrade path. Preserve a verified configuration backup and test representative cameras, analytics and exports in the target Unity release.
Build a project-specific comparison
Share the facility type, Carolina location, existing platform, approximate device count, operating problem, required integrations and target schedule. 360 Technology Group can use that context to determine whether Avigilon deserves a detailed site and design review.
Avigilon Alta and Unity owner and buyer resources
Use these Avigilon resources to connect Alta and Unity research with surveyed design, installation, configuration, migration, maintenance and support in North and South Carolina.
Official Avigilon Unity and Alta Video software, firmware and support
Use these manufacturer-owned portals for current downloads, release notes, manuals, advisories and technical resources. 360 Technology Group links to official sources and does not copy or host firmware files.
Update carefully: confirm the exact model, region, hardware revision, installed version, prerequisites, required intermediate releases, support entitlement, integrations, backup, maintenance window, rollback limitations and post-update tests. The wrong package or sequence can interrupt service or prevent a downgrade.
Some portals require a customer, dealer, certified-technician or active-support login. Cloud-managed products may update automatically and may not offer a public firmware file.