Canonical URL: https://density.io/resources/density-vs-xovis

# Density Entry vs. Xovis PC2SE: from doorway counts to building decisions

[Density Entry](https://density.io/entry) connects entrance-and-exit measurement with building and floor analysis. A workplace team can evaluate the installed counts and the resulting report together before deciding how much space it needs.

Xovis PC2SE is a people-counting sensor with its own integration options. A useful comparison follows one building boundary from the doorway survey through to the software the workplace team will operate.

## Compare the proposed system, starting at the doorway

Xovis describes the [PC2SE](https://www.xovis.com/technology/sensor/pc2se-sensor) as an overhead sensor with Power over Ethernet and multisensor capabilities. Its [technical datasheet](https://api.xovis.com/fileadmin/user_upload/file/ressources/Xovis-TechnicalDatasheet-PC2SE-EN-V6.0.pdf) specifies indoor 3D stereo vision, embedded processing, an API and data-push interfaces.

Check which sensor variant, lens, mounting arrangement and software the quote includes. Keep the exact model beside its specification; features listed for another Xovis sensor do not establish what the quoted PC2SE provides.

For Density Entry, bring the same doorway survey to the deployment discussion. Density's [installation guidance](https://support.density.io/hc/en-us/articles/6203216172699-Quick-Start-Entry-Installation-Guide) requires coverage above every entryway to the measured space. Placement depends on the threshold and sensing coverage, so have Density confirm the applicable hardware and installation plan.

## Make the boundary explicit

Imagine an office floor with a main entrance, a connecting stair and a side entrance used by staff. This is a hypothetical layout. A counter at the main entrance describes that route; it does not by itself account for the other two.

Draw the boundary around the floor and mark every crossing. Then ask each supplier to show how its proposed system assigns those crossings to the floor. Record any route outside the measurement plan before interpreting a floor-level total.

Use the [Density Entry guide](https://density.io/resources/entry-counts-building-occupancy) to distinguish arrival totals from the number of people currently present.

## Follow one observation into the building report

Density's [Atlas platform](https://density.io/atlas) provides occupancy and visits reporting, building and floor views, and exports. The team can assess Entry's counts and the report it will use for space planning in the same evaluation.

Ask Density to demonstrate the proposed floor in Atlas. Trace an agreed observation period from the installed boundary to the report. Check the reporting hours and the meaning of each measure before sharing the result with the team making the space decision.

For a Xovis-based proposal, ask the supplier to demonstrate the corresponding reporting path. The PC2SE datasheet establishes integration interfaces; it does not establish which workplace application, implementation services or reporting definitions your particular quote includes. Xovis can be part of a larger software solution, so evaluate that complete solution rather than comparing a sensor quote with a different software package.

## Review sensing and privacy configuration together

Xovis documents privacy modes and text-based data transmission without personally identifiable information in the PC2SE datasheet. Review the selected mode, configuration access and downstream application with the proposed supplier. Stereo-vision technology alone does not establish the privacy behavior of the whole deployment.

Density's [privacy guidance](https://density.io/resources/people-counting-privacy) provides a sensor-to-application review for anonymous occupancy measurement. Ask to see the actual output and data flow for the Entry hardware in your proposal. Review the selected deployment rather than relying on a general technology label.

## Put the handover in the comparison

Have each supplier identify who owns these four deliverables:

- **Doorway coverage:** the surveyed boundary, approved placement and commissioned crossings.
- **Data delivery:** the count definitions, timestamps, health information and recovery behavior.
- **Workplace reporting:** the building or floor view, reporting hours and export the buyer will use.
- **Ongoing operation:** device administration, software access, support and responsibility for changes to the space.

Compare complete quotes against those deliverables. Request comparable pilot results, itemized pricing and an installation plan for the proposed systems.

Bring Density one floor plan and the report you need for your building decision. [Book a demo](https://demo.density.io), or email [sales@density.io](mailto:sales@density.io), to follow Entry's counts into Atlas reporting.