Authorized dealer · Certified installers · Charlotte, NC headquarters
Authorized dealer and certified installers — North and South Carolina
360 Technology Group is an authorized dealer and certified installer for the manufacturers we represent, and has been installing commercial access control, card and key-fob systems, electronic door locks and mobile access across North and South Carolina since 2018 — more than 8 years.
- Authorized dealer — genuine equipment, licensing and manufacturer support entitlement.
- Certified installers — factory-trained technicians handle the cabling, mounting, power, programming and commissioning.
- Repair, service and takeover — we maintain, repair, upgrade and take over existing systems.
- 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
North Carolina and South Carolina planning guide
Access Control Installation
A defensible Access Control Installation 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 Access Control Installation 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.
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.
Access Control Installers
Confirm which current models, editions, licenses and dependencies support this requirement before procurement.
Professional Access Control Installation
Confirm which current models, editions, licenses and dependencies support this requirement before procurement.
Remote access if desired. Authorized personnel can make system changes and review audit trails from wherever they are.
Connect this capability to a named user workflow and a testable result at the actual facility.
White Glove Service
Review compatibility, capacity, infrastructure and lifecycle implications with the complete system design.
Large and Localized
Connect this capability to a named user workflow and a testable result at the actual facility.
Plan the right system for the site
Confirm which current models, editions, licenses and dependencies support this requirement before procurement.
Opening compatibility
Review compatibility, capacity, infrastructure and lifecycle implications with the complete system design.
Identity workflow
Compare retained equipment, migration effort, subscription impact and replacement options for this topic.
Failure behavior
Confirm which current models, editions, licenses and dependencies support this requirement before procurement.
Integration boundary
Review compatibility, capacity, infrastructure and lifecycle implications with the complete system design.
Administration model
Connect this capability to a named user workflow and a testable result at the actual facility.
Migration path
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 Access Control Installation:
- 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 Access Control Installation 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.
Create an opening schedule before selecting the platform
Every controlled opening should have a line item for door and frame type, handing, lock, reader, credential, door contact, request-to-exit device, closer, power supply, controller, network connection and emergency-release behavior. Add accessibility, fire rating, egress hardware, automatic operator and elevator interfaces where applicable. This schedule exposes construction and code issues before equipment is ordered.
Locking sequence
Define normal, after-hours, lockdown, fire alarm, power loss and controller-offline behavior. State whether each lock is fail safe or fail secure and why that behavior is appropriate.
Credential lifecycle
Document enrollment, approval, activation, expiration, suspension and revocation for employees, visitors and contractors. Include lost phone, card and fob procedures.
Administration boundary
Separate installer, IT, security, property-management and tenant permissions. Use named administrator accounts, multi-factor authentication where supported and an approved recovery process.
Acceptance testing by opening
Test valid and denied access, door-held and door-forced alarms, request to exit, unlock schedules, emergency release, controller restart, server or cloud interruption and notification routing. For integrated video or intercom, verify that the correct door event opens the correct camera or call workflow. Record each result and unresolved exception.
The owner should receive as-built drawings, opening and device schedules, network and power records, credential policy, backup, support contacts and training. License numbers, certificate numbers and personal certificate details do not need to appear on the public website or in general marketing material.
Coordinate access control with the building
Access control crosses electrical, locksmith, fire alarm, network and architectural scopes. The drawings should identify who supplies the lock, transfer hinge or electrified trim, door position switch, request-to-exit device, power supply, pathway, controller and final connection. Penetrations, listed assemblies and fire-door modifications must be coordinated before field work. A pre-installation door meeting helps prevent controls from being installed on openings that cannot close, latch or release correctly.
For occupied facilities, add a cutover sequence showing temporary security, affected entrances, badge continuity, after-hours contacts and rollback. Users should know which doors and credentials change at each stage.
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 Access Control Installation deserves a detailed site and design review.