Video Analytics & Spatial Management · E24

Left-Object, Stationary-Object and New-Foreign-Object Detection

JIVISION offers project development and technical assessment for Left-Object, Stationary-Object and New-Foreign-Object Detection. Scope: New objects, associated source tracks, positions and persistence.

Discuss scope & request a quote Browse this category →

Scope and project-specific requirements

Task / output

New objects, associated source tracks, positions and persistence

Critical decision conditions

Report candidate left-object events without inferring ownership or danger; retain candidate states through temporary occlusion.

Candidate technical approach

These are candidate implementation paths. Establish a baseline on real samples, then select or combine methods for imaging, speed and deployment constraints. Model names do not imply measured project results.

Object detection and confidence gating

RT-DETR, RTMDet, YOLOX, PP-YOLOE or rotated-box detection → non-maximum suppression and confidence thresholds → task rules

Object tracking and trajectory management

Object detection → ByteTrack, OC-SORT, BoT-SORT or Norfair association → Kalman filtering and track management

Spatial rules and event state machines

Detection and tracking → polygons, crossing, distance, time-to-collision, dwell and hysteresis rules → event state machine

Inputs for assessment

Provide camera layouts, authorized video, target sizes, day/night samples, region/event definitions, concurrent streams, alert-review workflows and retention periods.

Deliverables and interface agreement

Result schema, algorithm or processing configuration, example outputs and evaluation records for: New objects, associated source tracks, positions and persistence. Software format and source-code scope are agreed in the contract.

Specify input formats, output fields, coordinates/units, error states, versions and invocation methods. Define review and failure handling. The statement of work determines the exact scope of source code, executables, model files or analysis reports.

Acceptance method and measures

Task-specific acceptance measures

Left-object recall; false calls per hour; discovery delay

Evaluate events rather than only frames: misses, false alerts per hour, duration error, alert latency and recovery after occlusion. Include empty scenes and hard negatives.

These are measures to agree and test, not achieved-performance claims. Freeze samples, reference truth, thresholds and hardware/software versions before acceptance; report subgroup results and failures, identifying under-sampled conditions as uncovered.

Implementation and procurement stages

Define scope
Agree targets, stations, inputs and responsibilities in a statement of work, separating required and excluded conditions.
Sample validation
Use representative samples to test critical risks, document feasibility/failures and scope the next-stage estimate.
Development and integration
Implement agreed functions and interfaces with configuration/change records; use offline replay before authorized device or site integration.
Acceptance and handover
Retest against individual measures and hand over contracted artifacts with known limits; manage maintenance, expansion and changeovers as subsequent work packages.

Scope limits and licensing

Use data minimization, anonymization and access controls as needed. Do not infer sensitive traits, emotions or medical status from appearance; review alerts and retain existing safety measures.

Candidate technologies are not license clearance. Check code, model weights, training data and dependency versions separately. Replace, license or exclude components unsuitable for the intended commercial delivery. Customer data is not used for public training by default.

Project FAQs

What does this service produce?

New objects, associated source tracks, positions and persistence. Deliverables: Result schema, algorithm or processing configuration, example outputs and evaluation records for: New objects, associated source tracks, positions and persistence. Software format and source-code scope are agreed in the contract.

What needs to be confirmed first?

Report candidate left-object events without inferring ownership or danger; retain candidate states through temporary occlusion.

How is acceptance defined beyond a demonstration?

Task-specific measures: Left-object recall; false calls per hour; discovery delay. Evaluate events rather than only frames: misses, false alerts per hour, duration error, alert latency and recovery after occlusion. Include empty scenes and hard negatives.

How are cost and schedule assessed?

After reviewing samples for new objects, associated source tracks, positions and persistence, equipment conditions and interfaces, scope validation, development, deployment and acceptance separately. Data coverage, site changes and delivery rights affect the estimate; no fixed performance or schedule is promised before assessment.

PROJECT INQUIRY

Discuss this service for your project

Service ID: E24 · Left-Object, Stationary-Object and New-Foreign-Object Detection

Describe available samples, equipment and target measures. Agree confidentiality and permissions before transferring sensitive or personal data through an approved channel.

+86 13910119357
xuzhiyang0928@gmail.com