Success at properly identifying coverage.
If that is only working at 50% then the state would have never paid for it, or sued if the company selling it couldn't get it working. That sounds like a failure in leadership, if not outright fraud.
NY does it fine. Perhaps NV needs to see how another state successfully implements this? Perhaps they just need to bring in someone, even as an expert consultant, to plan an execute on this properly.
It's pretty simple really. The state defines which data, in which format, and how often. The insurance companies meet these requirements if they want to be licensed to sell automobile insurance in the state. If they fail, their licensed is revoked.
What can go wrong? Let's see...
How often do the insurers update the system? Monthly? Weekly? Daily? There's still the possibility that insurance has lapsed.
Daily for the system to be useful. If daily, the posibility that insurance has lapsed on the same date that the tags are run by the police are quite slim. Nowhere near 50%. More like a tiny fraction of a percent.
We are a relatively small state, yet we have over 500 insurers that write some form of private passenger motor vehicle liability insurance. DO you know how many different database systems they use? About 500. That means that whatever system the DMV uses needs to be able to accept data dumps from 500 proprietary systems.
No, that means the insurers who do business in this state need to provide the info in the format your state requires or else they cannot do business in your state. It's starting to sound like Nevada politicians are in the pockets of the insurance industry.
How does the system process data? What happens if two insurers report the same car? What happens you change insurers and the new insurer reports the car add before the old insurer reports the car drop? (many systems don't track history, so the late report on the drop will override the report of the add and show as no insurance)
This is a rather simple problem that any competent developers/contractors could solve. It would actually be the concern of the company contracted to implement the system. If they can't do it, don't pay and find a company that can. If other states can do this, why can't NV?
How does the system error-check the data? Is John Sullivan the same as John D. Sullivan? How about Jon Sullivan? Or Jhon Sullavan?
Why does this matter with automobile insurance? The car is insured, not the owner of the car or the policy. Every car has a unique VIN, so why the policy holders name would be an issue is beyond me. Do you know what unique identifiers are?
I've been in the room as DMV and insurers have fought over the requirements of digital insurance verification and it is not a simple subject.
I wouldn't brag about such a failure, especially on a forum filled with developers and other IT professionals.