Establish what an entry counts
Lexoh entry statistics summarize recorded entry activity over a reporting period. Operators can use them to understand arrival patterns and select sessions for investigation. The statistics view serves a different purpose from the detailed entry list or an occupancy report.
Before interpreting a count, identify the event or session that creates an entry in your installation. A credential presentation, accepted access decision, barrier command and confirmed passage are separate steps. Repeated attempts or missing device records can change the relationship between reported entries and physical arrivals.
Use the entry-statistics view available to your operator role. Record the site, devices, selected period, time zone and last refresh. A report is limited by the records received and the scope you can view; it does not establish complete coverage of every entrance.
Read each metric with its own scope
Total entries
Treat this as the count produced by the report’s entry definition and filters. Verify which devices and directions contribute, whether repeated entries count separately and whether the period is based on arrival time or another timestamp. An exit device should not be assumed to contribute an arrival simply because it appears in a device list.
Today’s entries
Check the actual beginning and end of the displayed day and its time zone. A card for today may have a different scope from the selected reporting period. Confirm its response to filter changes rather than assuming that every card changes together.
Peak hour
Identify whether this means the busiest single dated hour or the busiest hour of day aggregated across several dates. Check how ties and empty results appear. A default midnight label is not evidence of a measured midnight peak.
Data freshness
Read the available update timestamp or refresh state. Recently recorded activity may not yet be reflected in every chart. Check device communication, delayed records and the report’s refresh behavior before describing the figures as live.
Distinguish hourly totals from hourly averages
Read the horizontal axis, vertical unit and aggregation before comparing charts. A sequence of dated hours differs from a profile that combines the same hour across many days. A smooth line between points does not add measurements between the recorded intervals.
The example below uses complete records for 08:00–09:00 on two comparable days. It explains the arithmetic; it is not a claim about Lexoh’s configured calculation.
| Measure | Calculation and meaning |
|---|---|
| Day A | 20 recorded entries during 08:00–09:00. |
| Day B | 40 recorded entries during 08:00–09:00. |
| Combined total | 20 + 40 = 60 entries across both hourly intervals. |
| Daily average for this hour | 60 ÷ 2 = 30 entries per observed day for 08:00–09:00. |
| Largest observed hourly count | 40 entries on Day B. The average of 30 does not show this individual peak. |
Missing days and zero counts
Confirm which days enter the denominator. A verified open day with no entries can be a zero; a day with missing records is unknown. Do not silently treat missing data as zero or omit zero days. Check partial days, closures and clock changes before combining intervals.
Use peaks to plan a specific response
Compare similar operating days and the same hour boundaries. Separate weekdays, weekends, special events and closures when those differences matter. Arrival peaks depend on the site; an office, hospital or marina should not inherit a generic timetable from this guide.
Use the busiest intervals to plan staffing and observation, then compare arrival bursts with actual queue length, processing time and lane availability. A high hourly count alone does not demonstrate a queue or justify an additional lane.
For maintenance planning, consider exit demand and emergency access as well as arrivals. A quiet arrival hour is not necessarily a safe maintenance window. Follow the site’s operating and equipment procedures.
Investigate sessions behind the summary
Use the available recent-entry records to inspect individual sessions, then open the detailed list if the summary is limited. Confirm sort order, filters and row count; a short list of recent records is not the full population behind a chart.
Keep the record reference with its device, associated customer or operator, and available timestamps. An associated operator is not necessarily the person or vehicle that passed. Confirm the time zone and timestamp meaning before comparing records from different systems.
Missing exit or duration
A blank exit or duration can reflect an open session, a missing exit record, an unmatched event or delayed data. It does not by itself prove that a vehicle is still inside. Investigate the linked events and the site’s observation process.
Session duration
For a correctly matched example with entry at 09:10 and exit at 10:00 on the same day and time basis, elapsed time is 50 minutes. Check rounding and matching rules in the report. Displayed session duration is not automatically billable duration; grace periods and pricing rules may differ.
Unusual or duplicate records
Compare stable record references, timestamps, devices and related events before treating similar rows as duplicates. Re-entry can be legitimate. Preserve the original evidence and use the approved correction process instead of deleting rows to make totals agree.
Choose comparable periods and verify the result
- Write down the operational question, such as comparing Monday morning arrivals before and after a lane change.
- Select the intended site, devices and available date range. Record the exact bounds and time zone. A rolling 24 hours is different from today since midnight; a calendar month is not always 30 days.
- Check which date field and boundary rules the filter uses. Confirm whether a session arriving before the period but leaving inside it belongs in the result.
- Apply the filters and wait for the report to finish updating. Confirm the labels and scope of each card, chart and recent-entry list separately.
- Compare equivalent periods and operating hours. Include closures, incomplete days, missing device data and changes to entry-recording rules in the explanation.
- If export is available, verify its format, columns, filters and row population. Retain the original export with the report settings; do not assume a recent-row export contains every entry in the selected period.
Separate arrivals, occupancy and revenue
Arrival volume is not occupancy
Entries measure activity over a period. Occupancy concerns how many are present at a time. For an illustrative consistent count: 20 vehicles initially inside + 60 entries − 50 exits = 30 vehicles at the end. The 60 arrivals do not mean 60 occupied spaces, and the final 30 do not reveal the maximum during the period.
Entry growth is not revenue growth
A visit may be paid, included in a permit, complimentary or followed by a refund. Use the relevant transaction and revenue records, with matching scope, to explain financial results. Arrival counts alone cannot establish receipts or settled funds.
A change is a finding to investigate
An increase after a promotion can coincide with weather, an event, longer opening hours or restored device reporting. Compare those conditions before attributing the increase to the promotion. Keep the observation separate from the proposed explanation.
Keep the analysis reproducible
- Capture the report date, exact period, time zone, device scope, filters and counting definition with each review.
- Reconcile a small set of known sessions with their underlying records. Investigate gaps, delayed data and unexpected direction assignments before relying on totals.
- Use an approved test or known operational record to check that the intended entrance records correctly. Do not create unplanned access or alter live records merely to test reporting.
- Keep customer and credential information limited to the people who need it. Share aggregate figures when record-level details are unnecessary, and follow the site’s retention procedure.
- Record the decision, responsible person and follow-up measurement. When reporting an issue, include the affected references and expected versus displayed result through the approved support channel.