MVR Code Match
Compare caller-supplied expected and observed records for mvr code match.
Description
Motor-vehicle-record code matching compares recognized labels with reported codes.
Motor-vehicle-record code matching compares recognized labels with reported codes. It can identify unfamiliar labels without interpreting a driving record.1
Compare caller-supplied expected and observed records for mvr code match.
When to use MVR Code Match
Use this tool to compare caller-supplied expected and observed records for mvr code match.
Prepare the supplied policy terms, dates, assumptions or recorded indicators requested. Keep monetary amounts on one currency basis and select the applicable thresholds separately.
How to use MVR Code Match and understand its results
- Prepare the supplied policy terms, dates, assumptions or recorded indicators requested. Keep monetary amounts on one currency basis and select the applicable thresholds separately.
- Enter recognizedCodes, reportedCodes using the field table and calculation rules, then run the tool.
- Read coveragePercent, matched, missing, unexpected. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| recognizedCodes | Recognized MVR codes | list of string | Required |
| reportedCodes | Reported MVR codes | list of string | Required |
Supply recognized codes first and reported codes second. Coverage uses the recognized-code list as its denominator. Trim and lowercase labels; reject blanks and require a nonempty first list. Deduplicate by normalized key, retaining first position and last trimmed spelling. Return matches/missing first-list labels, unexpected second-list labels, and percentage; the second list may be empty.
coverage%=100×matchedUnique/requiredUnique Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| coveragePercent | Coverage (%) | number; minimum: 0; maximum: 100 |
| matched | Matched items | list of string |
| missing | Missing items | list of string |
| unexpected | Unexpected items | list of string |
{
"input": {
"recognizedCodes": [
"SPEED",
"DUI",
"FAIL_YIELD"
],
"reportedCodes": [
"SPEED",
"FAIL_YIELD",
"LOCAL_17"
]
},
"output": {
"coveragePercent": 66.66666666666666,
"matched": [
"SPEED",
"FAIL_YIELD"
],
"missing": [
"DUI"
],
"unexpected": [
"LOCAL_17"
]
}
}Limitations and assumptions
Unexpected labels identify unrecognized reported codes, while missing labels need not be a problem. No jurisdictional code meaning, record retrieval or underwriting decision is supplied.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Pilot Underwriting Score: Score pilot underwriting risk from experience, aircraft complexity, and incidents. For a complementary task, use Social Engineering Coverage Gap: Compare caller-supplied expected and observed records for social engineering coverage gap.
References
-
MVR Code Match — tool.io
Similar or alternative tools
- Pilot Underwriting Score
Score pilot underwriting risk from experience, aircraft complexity, and incidents.
- Social Engineering Coverage Gap
Compare caller-supplied expected and observed records for social engineering coverage gap.