AXIS P8815-2 People Counting and the New AXIS Object Analytics Approach
Overview and context
AXIS P8815-2 was a dedicated counter combining special hardware with 3D people-counting software.
Technology and analytics capabilities
Axis’s current support page states that the product has been replaced by AXIS Object Analytics.
Limitations and field criteria
On compatible cameras, AXIS Object Analytics supports scenarios such as Crossline counting and Occupancy in area for people/vehicle counts and occupancy estimation.
Procurement / integration decision
P8815-2 and Object Analytics are not the same sensing architecture, so retail footfall performance should be validated in the actual scene.
What the shift from a dedicated 3D counter to general edge analytics means
Products such as P8815-2 combined dedicated people-counting hardware and software. Axis now points to AXIS Object Analytics as the replacement direction, illustrating how more general edge-AI cameras can take on counting scenarios.
The wider industry shows the same pattern: some measurements remain dedicated-sensor tasks while others move into software scenarios on capable cameras. The old and new architecture should still be judged against the same field acceptance criteria.
Discontinuation is not the same as end of support
A final order date does not mean hardware and software support end the next day. Axis publishes separate hardware/RMA and AXIS OS support dates for P8815-2, so lifecycle planning should track each milestone independently.
Large installations can then migrate by risk and support window rather than removing every working counter immediately.
Thinking about counting with AXIS Object Analytics
Object Analytics supports scenarios such as crossline counting and occupancy in area on compatible cameras. This flexibility can serve multiple operational environments, although the sensing physics differ from a dedicated 3D entrance counter.
For a retail conversion KPI, the exact camera, lens and geometry should be validated. For broader occupancy and flow tasks, the general edge-application approach may be attractive.
The integration layer during migration
Legacy P8815-2 output and new Object Analytics events may use different schemas. A central platform should normalize them into consistent entrance and occupancy metrics so a hardware refresh does not rewrite historical dashboards.
Lifecycle assessment should cover data-architecture continuity as well as hardware renewal. This protects historical KPIs and centralized reporting during device migration.
The CS Otomasyon approach
For Axis lifecycle projects, CS Otomasyon manages installed P8815-2 devices by support timeline and data quality while piloting Object Analytics scenarios under the same acceptance criteria. The central data layer protects KPI history during migration.
FAQ
Is P8815-2 discontinued?
Axis support material shows it as replaced/discontinued.
Can Object Analytics count people?
Yes, on compatible devices through crossline and occupancy scenarios.
How long is P8815-2 supported?
Axis publishes separate hardware/RMA and AXIS OS support dates; the official page should be checked at project time.
Does Object Analytics require a separate license?
Verify against the current Axis licensing policy before procurement.
Can old and new counting data remain in one trend?
Yes, with parallel validation and centralized normalization.
Conclusion
Choose the technology against the real entrance geometry and target KPI rather than the logo on the device. A site survey and controlled pilot with CS Otomasyon can validate the architecture before rollout and connect the resulting data to centralized reporting.