Cloud rules, search, analytics and connected device data for operational and security workflows.
Product and system guidance
Arcules analytics can surface people/vehicle detections and support centralized rules/notifications. Access-control and IoT integrations require compatible gateways/devices and a written data/event ownership plan. Current Milestone Arcules branding and mobile-app choice should be confirmed for each account.
- Forensic people/vehicle search and timeline detections
- Rules, alerts, heat maps and operational analytics
- Access-control and IoT device integration
- Arcules versus Milestone Arcules account/app migration
- Scene survey, pixels on target, lens and mounting
- Bandwidth, storage, retention and evidence export
- Firmware, cybersecurity, user roles and remote access
- Current regulatory, procurement and customer compliance requirements
Engineering before procurement
Boston High Tech validates current model availability, firmware, licenses, analytics, VMS compatibility and storage calculations. We do not publish private certificate numbers or named certificate-holder records; qualifications can be confirmed through appropriate private channels.
Request a video-system design review
Serving projects from our Charlotte headquarters and local client offices in Massachusetts, New York and New Jersey. Office visits are arranged in advance.
Official manufacturer references
How to compare and specify this product family
For Arcules AI Analytics, Access and IoT Integrations, the right model and architecture depend on the site, existing infrastructure and operating policy. A proposal should clearly document the following video-surveillance system decisions before equipment is ordered:
- Scene purpose and required pixels on target
- Lens, mounting height, WDR, IR and low-light needs
- Analytics supported by the selected camera and VMS
- Bandwidth, PoE and network segmentation
- Retention, storage throughput and export workflow
- User roles, cybersecurity, health monitoring and support
Installation, testing and handoff
Design starts with the evidence or operational result required at each scene—not megapixels alone. We document fields of view, identification targets, lighting, camera placement, network load, recording profiles and retention assumptions. Commissioning covers focus, exposure, time synchronization, analytics calibration, user permissions, mobile or remote access, export testing and health alerts. Final documentation records device names, locations, addressing, retention settings and administrator procedures without publishing private credentials.
Frequently asked questions
Questions about Arcules analytics, connected device integrations and what each account confirms before a rollout begins.
Can recorded video be searched for a person or a vehicle?
Yes. Arcules analytics can surface people/vehicle detections, and forensic search with timeline detections is one of the listed workflows. What the search hands back depends on the scene behind it: a camera set for wide coverage produces detections an operator can find, while identifying who a person is takes the pixels on target planned for that job.
Is Arcules the same thing as Milestone Arcules?
This page treats them as one product line whose branding has moved, and it asks that current Milestone Arcules branding and the mobile-app choice be confirmed for each account. Account and app migration between the two names is listed as a decision, so settle it before user documentation is written and before staff are told which app to install.
Will Arcules take in events from our access control and other devices?
Access-control and IoT integrations run through compatible gateways and devices, so the answer turns on whether the equipment at your site falls inside that compatibility. Check the gateway requirement per device family rather than per brand, and price gateway hardware in the same scope so the integration is not an afterthought discovered during installation.
Who owns the event data once integrations are running?
Ownership is set by the written data/event ownership plan this page asks for with access-control and IoT integrations, naming the account holder, the retention applied and who may export evidence. Put that in place before the first integration is switched on, since centralized rules and notifications begin producing records that belong to somebody from the first day.
How much bandwidth and storage should we budget?
Bandwidth and storage follow from camera count, the streams each camera sends and the retention you commit to, which is why bandwidth, storage, retention and evidence export are decided as one group instead of after the cameras are chosen. Fix the retention target per camera group first; the storage number is arithmetic once that target and the stream settings are set.
Where do cameras have to be aimed for the detections to be useful?
At the part of the scene the detection has to describe, with the pixels on target that job requires, which is what the scene survey establishes before lens and mounting are picked. A camera hung for general coverage still records, but detections from it answer a coarser question than a camera set deliberately across an entrance lane.
Arcules owner, administrator and buyer resources
Discuss Arcules installation, maintenance or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.
Official Arcules software, firmware and support
Official manufacturer resources. We link out rather than host firmware.
Before updating: confirm model, hardware revision, current version, entitlement and rollback plan, and schedule monitored or life-safety-adjacent systems with the administrator.