Test LPR data by separating the captured plate, interpreted characters, matched account, membership status and final access decision. Define exception categories, reconcile repeated attempts and review staff overrides using the installed provider’s records. Protect customer information. A recognized plate or open gate does not alone establish a valid paid membership or an accurate operating report.
- Separate camera reads, account matches and access decisions.
- Verify installed rules instead of assuming vendor claims describe the site.
- Reconcile retries and overrides before calculating exception rates.
- Preserve relevant evidence while restricting customer identifiers.
Which events and installed capabilities should the review distinguish?
Trace the events between a vehicle’s arrival and its recorded service. A plate image, the characters read, an account lookup and an access decision are different events, even if the screen shows them together.
The operations hub connects this review with membership and throughput analysis. Define what the installed system records before asking for a report. Some fields may be missing, summarized or overwritten; note those limits instead of assuming every step can be traced.
Keep payment status separate from recognition. A vehicle may match an account whose eligibility changed, while a payment may concern a different billing period. State which records support each conclusion rather than treating all system activity as proof of recurring revenue.
Confirm the product, version and enabled functions with the operator and provider. Public product material may describe possible features, but does not show which features or rules are used at this wash.
SONNY’S public LPR specification describes how plates can link to member accounts and its pay station. It also lists reports on visits and retargeting. This 2024 sheet describes features; it does not prove how this wash works, quote a current price or measure site accuracy.
Request current documents and an authorized demonstration of the relevant reports. The pay stations and wash data guide connects installed features with account access and provider terms. Keep setup dates so a later comparison does not mix different rules without explanation.
How should exceptions and matching rules be reviewed?
Use categories that separate plate-reading, account eligibility and access questions. This register helps organize review; match its categories with the provider’s records and the workflow at the wash.
| Review category | Evidence to connect | Question to resolve |
|---|---|---|
| Unread or uncertain plate | Relevant capture and read event | What identifier did the system return? |
| Unexpected account match | Read, lookup result and matching rule | Does the result correspond to the intended account? |
| Eligibility exception | Account status and access decision | Which rule applied at that time? |
| Staff override | Operator action, reason and final service | What evidence supports the exception? |
Keep verified causes separate from unexplained events. A code called unreadable may be a reason selected by staff, rather than a measured camera condition. Ask how the field is created before treating its label as a technical diagnosis.
Check whether the installed system permits approximate matching and how it chooses the final account. A broader rule may resolve character differences, but also raises a question about whether the selected account is the right one.
DRB’s vehicle-identification documentation describes smart and aggressive whitelisting options. DRB warns that these options may increase false-positive matches. Review the rules used at the wash, but do not assume another product uses DRB’s rules. The warning does not prove that a false match occurred at this site.
Ask the provider to explain available records and the appropriate review. Do not change live access settings just to produce a diligence comparison. Keep observed results, setup changes and provider findings separate so the buyer can see what was measured under each arrangement.
How do vehicle records and counting units affect exception rates?
Trace the account and vehicle history before deciding that repeated identifiers mean fraud or more paying members. Corrections, vehicle changes and data imports may explain the records, while identical plate characters may need state or other available context.
Use consistent identifiers and the same review period to connect events. Keep the explanation and supporting records for each correction. Preserve the original data instead of silently merging similar-looking records in a spreadsheet.
Compare the corrected account view with billing and access records where authorized. A customer account, vehicle record, plate capture and billing entry may be different counting units. Name those units so a cleanup does not accidentally add or remove reported members.
Define the event counted, population reviewed and observation period before calculating a percentage. A rate based on read attempts answers a different question from a rate based on vehicle visits or final membership access decisions.
For hypothetical arithmetic only, assume a reviewed period contains 1,000 defined membership-entry events and 30 classified exceptions. The resulting 3% is meaningful only under those stated definitions. It is not an industry benchmark, recommended target or measured result for an actual wash.
If one vehicle makes several attempts before one service, check how the records link them. Repeated reads are not proof of multiple customers or washes. Keep open events in the reconciliation and disclose missing records rather than claiming an export covers every arrival.
How should operating patterns and staff overrides be reconciled?
Compare lanes, periods and conditions using the same event definitions. Differences may raise useful questions for the provider, but do not by themselves prove a technical cause or the value of a new system.
Record why each period was selected and whether the setup, cameras or operating procedures changed. Keep the before-and-after populations comparable where possible. A quiet weekday and busy weekend may differ in more than the feature under review.
The queue and membership capacity guide adds context when exceptions occur alongside delays. Keep recorded handling time separate from assumed lost visits. An exception count alone does not prove lost sales, staff savings or recovered demand.
Link each relevant staff action with account status, the allowed reason and the final access record. Check what staff were authorized to do and what records the system kept at that time.
Review clusters of unexplained overrides or missing reasons with the manager and provider. An override may be a valid service decision, a data problem or an issue needing further review. Do not blame staff or conclude fraud from a report category alone.
Summarize reviewed causes separately from open questions. Record any approved correction and what should be observed to assess its effect. Fewer reported overrides after a process change may reflect different recording, rather than better plate recognition.
How should customer evidence and the final summary be protected?
Limit identifiable records to the approved purpose and recipients. Review plates, images, visit histories and account details through a controlled process suited to the deal and applicable obligations.
The FTC personal-information guide advises businesses to know what data they hold, keep only what they need and limit access. Have qualified advisers review the actual data and sharing process. A vendor feature does not prove privacy compliance. It also does not give permission to reuse visit records for a new purpose.
Use grouped results or coded records when they answer the diligence question. Keep a suitable route to source records for authorized checks. Record access and retention limits, since removed images or logs may make the report impossible to reconstruct.
Connect the measurement with supporting records and unresolved questions. This original sequence keeps provider capabilities, operating results and proposed corrective work separate.
- Identify the installed product, configuration and available event records.
- Define the counted event, population, period and exception categories.
- Connect reads, account matches, eligibility and final access outcomes.
- Reconcile retries, corrected vehicle records and staff overrides.
- Obtain provider or qualified review for unexplained patterns.
- Report supported findings, data limits and approved follow-up separately.
Assign open questions to a reviewer in the operating plan. The membership pricing and retention guide keeps account changes and retention measures separate from access reliability. Show what the records support; vendor marketing, an open gate or a cleaned export does not by itself prove revenue quality.