Product composition
BOX 5.0 combines the operational functionality of BOX 3.2 with the technological components of Platform 4.0. The application scope includes cameras and sites, events, users and roles, review workflows, logging, archive, reports, counters, backups and external signals as specified for the delivery.
Platform foundation
| Component | Deployment questions |
|---|---|
| CORE | Cameras, users, events and processing nodes |
| MM | Model types, runtime profiles and storage |
| RS | Block palette, scenario graphs, assets and sessions |
| MLLM | Enabled multimodal components and parameters |
Compatibility boundaries
Functional continuity does not establish compatibility of BOX 3.x compose files, environment variables or internal APIs. Check the versions of all components, published model/scenario versions, API schema and node profiles.
Acceptance
Validate the complete path: source input, scenario processing and a result received by the intended consumer. Checking one component does not replace this end-to-end test.
Shared instructions and version-specific setup
The detailed manuals describe shared operations once: sign-in, profile, monitoring, event review, archive, personnel, vehicles, access, global settings and LLM. The BOX 3.2 and BOX 5.0 navigation trees link to those same articles. Camera forms, catalogs, video recorder workflows and API fields have version-specific instructions. Models, assets, scenarios and execution belong to Platform 4.0 / BOX 5.0.
In the inspected BOX 5.0 camera form, the “Detectors” tab still assigns presets; a separate “Scenarios” tab was not shown. Presets and scenarios coexist. Use the documented assignment route for the installed build rather than assuming that adding a preset assigns a scenario.