Capture, networking, recording, management and events planned as a verifiable system.
AcuSense, DeepinView, NVR and HikCentral used within their defined roles, regions and versions.
An enterprise video system must produce useful images, preserve recordings and support an organized response. Hikvision equipment and software can form part of this architecture in authorized installations, from capture to centralized management. Selection starts with the operational purpose and requirements for infrastructure, digital security and privacy. Founded in 2011 and based in São José do Rio Preto, ADD Solution focuses on engineering, deployment and operations. In Video Intelligence, this means linking each capability to a verifiable need: reviewing an incident in a logistics area, monitoring a perimeter or organizing alerts across sites. The design considers what the team can operate, the limitations of each component and the expected service continuity. Technical references: AcuSense and HikCentral Professional. ADD Solution corporate information supplied in the project brief.
AcuSense is a technology used in certain Hikvision products to distinguish people and vehicles from other moving objects. In supported scenarios, this classification helps prioritize alerts and locate recordings. The benefit must be measured at the installation; lighting, framing and configuration affect results. The function may reside in the camera or the recorder. Generation, model, firmware, event type and simultaneous capacity must be checked. Motion Detection 2.0, perimeter rules and search functions must not be treated as equivalent or as universal brand attributes. Classifying a person in video does not establish identity or intent. The operational process must provide for human confirmation of the context before any action that has consequences for someone. False alarms and missed events must be included in the project assessment. Sources: AcuSense technology and second-generation AcuSense.
DeepinView includes cameras with analytics capabilities whose composition depends on the model. Some products target perimeter protection and other applications. Selection must start with the desired function and the specific data sheet, preserving equipment suffixes, lens and revision. For example, the IDS-2CD7A46G2/V-XZHS(Y), presented as DeepinViewX, has perimeter functions with person and vehicle classification. Its documentation also specifies power supply and privacy masks. That data sheet cannot be generalized to all DeepinView cameras. Promotional percentages and analytics distances published under test conditions must not become guarantees for every environment. Engineering validates positioning, lighting, occlusions, motion and the area actually analyzed. The family name guides research; accepted performance depends on testing in a representative scene. Source: IDS-2CD7A46G2/V-XZHS(Y).
The camera captures, compresses and, where equipped to do so, generates events and metadata. The NVR receives streams, records and provides playback; some models also perform analytics. The VMS organizes resources, users and management operations. Each layer depends on the capabilities of the others. In the consulted DS-7608NXI-K2/8P data sheet, eight camera inputs coexist with specific bandwidth, decoding and storage limits. Eight connected channels do not mean eight images at any resolution can be decoded simultaneously. This reference is an architecture example, not an automatic purchasing recommendation or confirmation of regional availability. To avoid gaps, record where each analysis takes place, how events reach the operator and which recording allows the alert to be verified. Also confirm behavior after connection loss, a full disk and component restarts. Source: official DS-7608NXI-K2/8P data sheet.
HikCentral Professional is a management platform that can bring video and other applications together in a centralized operation. Functions, modules, permissions and integrations must match the contracted edition, licenses and architecture. The management server does not remove the need to size recording systems or viewing clients. When consulted in October 2026, the official MENA portal listed HikCentral Professional 3.1.1, with OpenAPI documentation available for that version. Some regional pages still describe 3.0.1. The specification must use the documentation set for the proposed version, without combining limits from different generations. For integrations, check API, authentication, certificates, events and failure handling. A documented interface does not prove that ready-made integration exists with every system. Customizations and upgrade paths require assessment before changes. Sources: HikCentral Professional, official downloads and OpenAPI 3.1.1.
The survey must separate recording, viewing, playback and export traffic. Links between sites must support the planned sessions, with headroom for peaks. Bitrate reduction through compression depends on the scene and settings; a fixed saving must not be applied to every installation. PoE requires checking the standard and power per port, total budget, cabling and backup power. In the cited DeepinViewX example, the data sheet specifies IEEE 802.3at. A switch chosen solely by port count may be inadequate. Illumination and accessories also affect consumption. To estimate volume, 24 cameras at an average 3 Mbps, recording continuously for 30 days, generate 23.328 decimal TB of video. Audio, metadata, reserves, redundancy and variations are excluded from that example. The project compares usable disk capacity and performance against the justified retention period, validating the estimate in operation. Requirement sources: DeepinViewX and reference NVR. Calculations and margins: engineering recommendation.
ONVIF organizes functions into profiles: Profile T for advanced video, Profile G for recording and retrieval, and Profile M for metadata and analytics events. Some features are mandatory and others conditional. Check conformance for the product and version at both ends, as well as the selected software’s matrix. A working video stream does not demonstrate full support for analytics, search, audio or commands. Test events, time, playback, export and reconnection with the actual models. Proprietary and third-party integrations may require additional components. Testing must produce a matrix of approved functions, limitations and versions that can be repeated after an update. ONVIF ends new Profile S conformance submissions on 31 March 2027 and recommends Profile T for new products with advanced video. This milestone does not automatically stop deployed Profile S equipment; versions, required functions and conformance at both ends still need checking. Sources: ONVIF interoperability, profiles, conformance registry and Profile S deprecation questions and answers.
As an engineering practice, maintain a version inventory, individual access, least privilege and segmentation. Avoid direct exposure of administrative interfaces and disable services with no operational purpose. Apply secure connections and certificate management according to the actual capabilities of the camera, recorder, VMS and client. The Hikvision hardening guide covers sending camera logs to a remote server. Implementation must be checked by model and firmware. Define who reviews access and operations, how long records are retained and how unauthorized changes are identified. Security updates require testing, a change window and support lifecycle tracking. Video configuration must limit areas, data and retention periods to what is necessary for the authorized purpose. Document the applicable legal basis and responsibilities with the privacy team. Prioritize aggregate statistics where sufficient and assess privacy masks. LGPD requires analysis of context and responsibilities; no product automatically makes a project legally compliant. Sources: Hikvision hardening guide, HikCentral lifecycle and ANPD.
Acceptance must cover image quality, recording, alarms, searches, export, access profiles and failure response. Document test scenarios, results and restrictions. Train operators to verify alerts and recognize when the system is not recording or is presenting incomplete information. Licensing, support and updates must be confirmed for the selected version, region and modules. Lifecycle conditions must not be inferred from a commercial name. Preserve existing integrations and configurations during migrations. For continuity, distinguish configuration backup, copies of relevant recordings and service recovery. RAID or clustering, where applicable, does not replace disaster recovery. Establish recovery objectives, owners and tests, considering power, network and storage failures and a site becoming unavailable. Sources: HikCentral 3.0.1 documentation and requirements as a version-specific reference, and product lifecycle. Continuity criteria: engineering recommendation.
Complete answers for Hikvision architecture, deployment and operational decisions.
No. The technology is available in specific products and can vary by generation. Check the data sheet, firmware and enabled functions. It is also necessary to identify whether analysis occurs in the camera or NVR, because that changes the project’s limits and dependencies. Source: AcuSense.
AcuSense describes classification technology used in certain devices. DeepinView identifies a camera family with model-dependent features. Comparison must consider the application and specific data sheet, without establishing a universal performance ranking between the names. Sources: AcuSense and DeepinViewX example.
The decision depends on scale, users, sites and integrations. One project may use the recorder’s local functions, while another needs centralized management. The assessment compares operations, infrastructure, licensing and maintenance, avoiding complexity without a demonstrated purpose. Source: HikCentral Professional.
Yes, in compatible combinations. Confirm model, firmware, ONVIF profile and the software matrix. Test every required function, particularly events and metadata. Basic video compatibility does not mean full functional equivalence or universal cross-vendor support. Source: ONVIF guidance.
No. Lighting, partially visible objects, weather and configuration can affect classification. The project must test representative situations, record limits and provide for human verification. Manufacturer test data must remain linked to the conditions under which it was produced. Source: performance conditions of the DeepinViewX example.
First define the purpose and a period appropriate to the context. Then size usable capacity, bitrate, camera count, schedule and reserves. Validate the result with actual recordings. Keeping footage longer because disk space is available does not replace an assessment of necessity. References: ANPD and data protection principles.
Preservation must be verified along the applicable upgrade path. Check modules, licenses, clients, APIs and customizations. Document backup and recovery, and repeat operational tests. Do not use the requirements of an old version as a guarantee for a later version. Sources: OpenAPI 3.1.1 and lifecycle.
The survey brings together the objective, areas, existing equipment, network availability and operator routines. The scope can then define architecture, tests and responsibilities. Sensitive information, such as recordings and credentials, is not needed for the first commercial contact. Planning references: HikCentral documentation and ANPD guidance.
Define capture, retention, management, compatibility and operations without assuming universal capabilities.