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 Alta equipment we supply and install
Avigilon Alta — formerly Openpath — is cloud access control administered in the same platform as Alta video, so a door event and its clip sit together. We install, migrate and service it across North and South Carolina, including takeovers of existing Openpath deployments.
Standard smart reader
The default opening. Mobile, card and fob credentials in one reader. Specify OSDP rather than Wiegand wherever the full design supports it.
Mullion smart reader
Narrow-format reader for aluminium storefront frames, where a full-size reader will not fit the stile. Very common on Carolina retail and office glass fronts.
Standard keypad reader
Adds a PIN for openings that need two factors, or a PIN-only fallback for people who will never carry a credential.
Video Intercom Reader Pro
Reader and video intercom in one device, so a single opening handles both credentialed staff entry and visitor call-and-release without two sets of hardware.
Alta 8-door smart hub
Core Series panel for eight openings. Count readers, contacts, exit devices, inputs and outputs before choosing — door count alone under-specifies most jobs.
Secure elevator board
Floor-by-floor access from inside the cab. Needs to be scoped with the elevator contractor rather than assumed — that coordination is where these projects slip.
Mercury MP controller
Open-architecture Mercury hardware, supported where a site wants a controller platform that is not tied to one head-end forever.
Credentials
Mobile passes and physical cards. Decide credential technology alongside the reader, never after it.
Alta Access platform
The cloud administration layer: users, groups, schedules, audit trail and identity-provider integration.
Alta Access pairs with Alta Video so door events carry their own footage, and with Avigilon Unity where a site keeps recording on premise. See controllers, video intercom and integrations.
Product images are supplied by the manufacturer. 360 Technology Group is an authorized Avigilon Alta 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
Openpath
A defensible Openpath 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 Openpath as part of a complete access-control and electronic-door 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 Access Cloud, Smart Readers and Mobile Access
Open the detailed product, design or implementation guide.
Avigilon Alta Controllers, Video Intercom Reader and Integrations
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.
Openpath Access Control Installers
Connect this capability to a named user workflow and a testable result at the actual facility.
Openpath Cloud Based Access Control
Treat this as a design checkpoint; the final selection depends on field conditions and supported releases.
Openpath Property Management
Compare retained equipment, migration effort, subscription impact and replacement options for this topic.
Openpath Video Management (VMS) Integration
Confirm which current models, editions, licenses and dependencies support this requirement before procurement.
Who Should Use Openpath Access Control?
Connect this capability to a named user workflow and a testable result at the actual facility.
Opening compatibility
Compare retained equipment, migration effort, subscription impact and replacement options for this topic.
Identity workflow
Treat this as a design checkpoint; the final selection depends on field conditions and supported releases.
Failure behavior
Compare retained equipment, migration effort, subscription impact and replacement options for this topic.
Integration boundary
Confirm which current models, editions, licenses and dependencies support this requirement before procurement.
Administration model
Confirm which current models, editions, licenses and dependencies support this requirement before procurement.
Migration path
Confirm which current models, editions, licenses and dependencies support this requirement before procurement.
Evidence to collect before design
A useful survey and stakeholder review should produce the following project evidence for Openpath:
- Door and frame survey, existing lock function, handing, egress behavior and accessibility conditions.
- Credential population, visitor flow, schedules, exception handling and administrator responsibilities.
- Controller, reader, lock, request-to-exit, door-position and power requirements for every opening.
- Fire-alarm, elevator, video, intrusion, directory and identity-system integration boundaries.
- Network segmentation, cloud connectivity, offline behavior, battery runtime and cybersecurity standards.
- Licensing, mobile-credential policy, spare capacity, migration sequence and long-term support ownership.
Architecture and integration review
Opening compatibility
Match the proposed hardware to the actual door, frame, latch, traffic pattern and required free egress.
Identity workflow
Define enrollment, approval, revocation, visitor access and audit responsibilities before configuration.
Failure behavior
Record what must happen during network, cloud, controller, power and fire-alarm events.
Integration boundary
Name the systems exchanging identities, alarms, video, elevator commands or property data.
Administration model
Decide who owns accounts, roles, schedules, reports, backups, updates and after-hours support.
Migration path
Plan retained doors, phased cutover, credential transition and rollback without weakening security.
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 Openpath 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.
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 Openpath 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 Alta Access 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.