What does the IVMS readiness self-assessment check?
Many oil and gas clients ask contractors to show that their in-vehicle monitoring system works the way the contract says. This tool turns that request into short questions about five areas: devices and installation, settings, reports, data, and people and review.
You pick the reference list your client works from and answer yes, partly, no or not sure. You get a readiness score, a numbered list of gaps, a comparison of your device settings with your contract values and a closure plan in three waves.
Which reference lists can you choose?
| List | What the questions follow | Questions |
|---|---|---|
| PDO / OPAL SP-2000 style | Items summarized from public copies of the PDO road safety standard SP-2000 (version 4): driver identification, tamper events, speed source and zones, event settings, recording, reports and review. | 19 |
| ADNOC style | Items named in supplier summaries of ADNOC IVMS requirements: speed signals, detailed recording, red-amber-green rating, tamper audit and data location. | 14 |
| IOGP Report 365 style | The core of the IOGP land transport recommendation as summarized publicly: coverage of vehicles, driver identification, tamper detection, review and driver feedback. | 10 |
| General good practice | Every question. Use it when your client has not named a standard. | 21 |
These lists follow public summaries and supplier articles, not the official documents. Requirements change between versions, and each operator publishes its own. Ask your client for the current text before you rely on any item.
How is the readiness score calculated?
Each answer earns points: yes 1, partly 0.5, no 0 and not sure 0. Every item has a weight: core items 3, important items 2, supporting items 1. The score is the share of the weighted points you earned.
| Band | Rule | What to do |
|---|---|---|
| Close to ready | 85% or more and no core item at no or not sure | Keep the records ready. |
| Gaps to close | 60% to 84%, or a core item at no or not sure | Close the core items first. |
| Not ready yet | Below 60% | Start with wave 1 of the plan. |
Settings check
Each row compares one device setting with the value your contract asks for. At most means the device value must not be higher. At least means it must not be lower. A blank device value is not a match: it is listed as not checked.
Closure plan
Core items weigh most and settings are quick to change, so both go in wave 1. Important items follow in wave 2 and supporting items in wave 3. With an audit date, the waves end after 40%, 70% and 90% of the days left. The last 10% is kept for a dry run.
Which typical values does the settings check start with?
| Setting | Required value | Rule for the device value |
|---|---|---|
| Speeding event: km/h over the limit | 10 km/htypical | at most |
| Speeding event: seconds over the limit | 30 stypical | at most |
| Excessive speeding: km/h over the limit | 20 km/htypical | at most |
| Seat belt event: vehicle speed in km/h | 10 km/htypical | at most |
| Seat belt event: seconds unbuckled | 10 stypical | at most |
| Harsh braking: km/h per second | 15 km/h/stypical | at most |
| Harsh braking: applies above km/h | 30 km/htypical | at most |
| Recording interval: seconds | 1 stypical | at most |
| Rolling record on the unit: minutes | 5 mintypical | at least |
| Position report on speed change: km/h | 5 km/htypical | at most |
| Position report on heading change: degrees | 10 °typical | at most |
Typical values from public copies of SP-2000 version 4 (2017). Replace them with the values in your contract.
Worked example
- A contractor chooses the SP-2000 style list: 19 questions. It answers yes to 8, partly to 7, no to 3 and not sure to 1.
- The weighted score is 25.5 of 41 points: 62%. The band is gaps to close. Two core items are only partly in place: driver identification and thresholds that match the contract.
- In the settings check, 4 of 11 settings differ: seconds over the limit (60, contract 30), seat belt speed (20, contract 10), harsh braking (18, contract 15) and the rolling record (3 minutes, contract 5).
- With the audit 90 days away, wave 1 holds 6 items (2 core items and 4 settings) and ends on day 36. Wave 2 holds 8 items and ends on day 63. Wave 3 holds 1 item and ends on day 81.
How do you read the result?
- The band is a summary. The score by area shows where the gaps sit.
- A core item at no or not sure keeps the band below close to ready, whatever the score.
- Not sure counts as no. Check it on the device or in the platform and answer again.
- Use the gap list as a work list. Each row says what to do and which record to keep.
Common mistakes
- Answering for the best vehicle. Answer for the vehicles that are weakest today.
- Counting a feature that is switched off as a yes. A yes means it is on, tested and recorded.
- Typing thresholds from memory. Export the configuration of a few units and read the values from it.
- Treating the score as an audit result. The auditor decides what counts.
Assumptions and limits
This is a self-assessment built from public summaries. It is not an audit and does not show approval or certification by any operator, authority or Tracom. Weights, bands and typical values are indicative. Verify every requirement against the current official text from your client or operator before you act on it.