Model version
Package, categories and runtime validation.
Scenario version
Graph, model references and local settings.
Asset run
Reproducible input and reviewed results.
Camera assignment
Published version executed on a source.
Publication and runtime execution are separate steps.
The platform components
Platform 4.0 brings together data management, model management and scenario development. These components form the technological foundation of BOX 5.0. Existing BOX 3.x deployments have a separate deployment and operating branch.
| Component | Responsibility | Main entities |
|---|---|---|
| CORE | Data and distributed processing | Cameras, sites, events, users and assignments |
| MM | Model management and validation | Models, versions, packages, categories and validation results |
| RS | Scenario editing and execution | Scenarios, versions, graphs, block parameters and test runs |
| MLLM | Multimodal processing | Multimodal tasks and component configuration |
From development to camera processing
A model and a scenario have independent versions. A test run links a selected version to test data. Publication makes a version available to consumers; camera processing additionally requires assignment and execution in the computing environment.
- Model version: package, categories, validation and a control inference run.
- Scenario version: flow_data, extracted flow_settings and references to model versions.
- Test run: launch_uuid, progress, original and visualised frames, messages and events.
- Camera execution: the runtime loads the selected graph and model dependencies and processes the source.
Publishing a model does not load it into GPU memory. Loading takes place when a scenario using the model executes.
Roles and responsibilities
Developers create versions and run checks. Administrators provide resources and access and monitor services and storage. Operators review results and make decisions in the application interface.
Product, configuration and development status
Camera and zone management, model and scenario versions, testing, event workflows, roles and audit are described platform capabilities. Model formats, runtime profiles, MLLM/RAG, adapters, topology and retention depend on the delivered configuration. Event chat and AI-assisted scenario generation and testing are development concepts; a requirement or concept document does not establish release availability.
From platform components to operator tasks
The detailed operational guides connect the technical components to the application workflow. Site structure and camera settings establish the physical location and access scope; model/scenario settings establish categories and processing rules; journals preserve evidence and review decisions. Integration configuration supplies source mappings, recipients and exchange rules.
Quality criteria, resource limits, audit requirements and publication procedures must become testable design and acceptance conditions for the delivery. These requirements do not establish that every described interface is available in the installed release.