Methodology version WSCC-AA 1.0 (Scoring Logic Matrix V1)
How sites are assessed
This is an operational assessment and decision-support tool. It summarises recorded evidence; it does not automatically recommend equipment replacement, and it never implies a repair, diagnosis or operational state the evidence does not establish. Every rule below is applied identically to every site and is defined in a single configuration.
What each score measures
- Condition Score (0–100) — observed condition from recorded evidence. Higher is better. Points achieved ÷ available assessable points × 100.
- Investment Priority (0–100) — how strongly the site merits WSCC's consideration. Higher means greater priority. Not an instruction to replace equipment.
- Assessment Coverage (%) — weight of assessed tests ÷ total applicable test weight. High ≥90%, Moderate ≥75%, below 75% Low / Provisional. A high score with low coverage is always flagged and never shown as equivalent to a fully evidenced score.
Component weights and point allocations
| Component | Weight |
|---|---|
| Road Loops | 25 |
| Counter | 30 |
| Signal / Communications | 15 |
| Power & Solar | 20 |
| Cabinet & Site | 10 |
| Component | Test | Max points | Rule |
|---|---|---|---|
| Road Loops | Loop continuity (A–L) | 18 | 18 × passes ÷ expected loop count. Unused loop fields are never failures. |
| Road Loops | Visual condition | 7 | Good 7, OK 5, Average 3, Bad 0 |
| Counter | Powers on (known-good battery) | 12 | Yes 12, No 0 — critical |
| Counter | Front panel | 8 | Yes 8, Partly 4, No 0 |
| Counter | Lane detector cards | 10 | 10 × working ÷ total |
| Signal / Comms | Has comms | 3 | Yes 3, No 0 |
| Signal / Comms | Has details | 2 | Yes 2, No 0, N/A excluded |
| Signal / Comms | Dial / transmit data | 8 | Yes 8, No 0 — critical |
| Signal / Comms | Signal strength | 2 | Green 2, Amber 1.5, Red 0 |
| Power & Solar | Main battery voltage | 8 | Green 8, Amber 6, Amber-low 3, Red 0 |
| Power & Solar | Solar exposure / appearance | 3 | Good 3, Vegetation 1.5, Damaged 0 (per panel) |
| Power & Solar | Solar panel voltage | 3 | Split equally across panels; each assessed individually |
| Power & Solar | Solar inverter | 3 | Yes 3, No 0; not applicable to 12V installations |
| Power & Solar | Internal wiring | 3 | Yes 3, No 0 |
| Cabinet & Site | Vegetation | 2 | Good 2, Needs Attention 1, Not Accessible 0 |
| Cabinet & Site | Locks | 2 | 2 × operational ÷ total |
| Cabinet & Site | Internal condition | 3 | All Good 3, Muddy 2, Ants 1.5, Rodent 1, Rust/water 0 (worst applies) |
| Cabinet & Site | Wiring & terminal equipment | 3 | Yes 3, No 0 |
Technical thresholds
Counter type selects which thresholds apply. It is never an age penalty: a functioning Type F scores the same as a functioning BlackCat.
| Measure | Green | Amber | Red |
|---|---|---|---|
| Battery — legacy 6V | >6.4V | 6.2–6.4V; 6–<6.2V (low) | <6V |
| Battery — 12V | ≥12.6V | 12.2–<12.6V; 12–<12.2V (low) | <12V |
| Solar panel — legacy 6V | >3.2V | 3–3.2V | <3V |
| Solar panel — 12V BlackCat | 20–23V | Outside range but non-zero (requires interpretation) | 0V or confirmed failure |
| Signal — legacy counter | 21+ | 11–20 | 0–10 (red signal quality) |
| Signal — BlackCat | 70.00–99.99 | 10.00–<70.00 | Below 10.00 (red signal quality) |
Some BlackCat counters run on 6V batteries; the voltage system is taken from the recorded counter type (e.g. “BlackCat (6v)”), then from recorded readings. Battery and solar voltages were measured disconnected and are snapshots, not measures of battery health or capacity. Signal strength measures reception, not bandwidth. Signal values converted by Excel into dates are recovered only where unambiguous (“11-20”); otherwise they are marked unclassified — a reading is never invented.
Component traffic lights
- Precedence: Red (confirmed significant failure) → Amber (partial functionality / observed concern) → Green (all essential evidence healthy) → Grey (insufficient evidence). Grey is never shown as green.
- Road loops: red if any expected loop fails continuity; amber if all pass but visual condition is Average/Bad; green if all pass with Good/OK. The score reflects the proportion of failed loops.
- Counter: red if it fails the independent power-on test or no lane cards indicate correctly (with loops intact); amber for a partly/fully unresponsive front panel or a documented intermittent issue. An RMA never turns an otherwise healthy counter red.
- Communications: red only for a confirmed inability to transmit where testing was meaningful; amber when transmitting with moderate/poor signal or documented intermittent connectivity; green when transmitting with good signal. A strong signal never overrides a confirmed transmission failure.
- Power & Solar: combines batteries, each panel, wiring and (legacy 6V only) the inverter. 12V installations are never penalised for having no inverter.
- Cabinet & Site: cosmetic and maintenance observations (vegetation, dirt, pests) are amber and do not by themselves create a repair requirement.
Hierarchical testing and Assessment Coverage
- Not Assessable — a prerequisite failed (e.g. the counter did not power on, so front panel, lane cards and communications could not be tested). Excluded from the score denominator, reduces coverage, reason recorded. Downstream tests are never counted as separate failures.
- Not Recorded — missing without explanation. Excluded from the denominator, reduces coverage, raises a data-quality warning.
- Not Applicable — genuinely does not apply (e.g. inverter on a 12V site). Excluded from both score and coverage.
- Provisional — coverage below 75%, or a critical test (counter power-on, expected loop continuity, data transmission) missing without explanation.
- Untested components are never assumed to have failed.
How Final Notes are used
Final Notes are treated as evidence through a transparent, deterministic rule set (no external AI). Evidence hierarchy: recorded technical tests → explicit notes describing the final verified condition → explicit intervention selections and repair requirements. Hedged wording (“could”, “possibly”, “may”, “likely”, “recommend”, “if”…) never creates a confirmed fault or requirement — it is flagged for review. Where notes and structured answers conflict, both are preserved and a validation warning is raised; original data is never rewritten.
| Rule | Effect | Component |
|---|---|---|
| SITE-OPERATIONAL | Notes describe the site as operational / nothing required | site |
| SITE-NOT-APPRAISABLE | Site could not be appraised (no access to equipment) | site |
| CTR-NO-COUNTER | No counter present on site | counter |
| CTR-FRONT-PANEL | Front panel fault described | counter |
| CTR-UNRESPONSIVE | Counter unresponsive during testing | counter |
| CTR-POWER-CYCLE | Counter repeatedly power-cycling / resetting | counter |
| CTR-FAULTS-CLEARED | Logged faults self-resolved and were cleared on site | counter |
| CTR-SENSOR-FAULT-REPORTED | A sensor fault is reported but not confirmed by indicators — review | counter |
| CTR-INTERNAL-SUSPECTED | Possible internal counter component fault | counter |
| COM-RESTORED-AFTER-RESTART | Connection restored after a restart during the visit | comms |
| COM-VERIFIED-WITH-KNOWN-GOOD-POWER | Communications verified working with known-good (test) power | comms |
| COM-INTERMITTENT | Intermittent connectivity — recurring disconnections documented | comms |
| COM-FAULT | Communications failure described | comms |
| COM-MODEM-CORROSION | Corroded modem card contacts | comms |
| COM-POWER-CAUSE | Communications failure attributed to low battery voltage (suspected power cause) | comms |
| COM-LOW-SIGNAL-AREA | Low signal area noted | comms |
| LOOP-NO-CONTINUITY | Loss of loop continuity described | loops |
| LOOP-CONTINUITY-UNCERTAIN | Engineer could not confirm loop continuity results | loops |
| LOOP-ROAD-CONDITION | Road surface condition around loops noted | loops |
| LOOP-TERMINATION-MONITOR | Termination block corrosion to be monitored (no repair required) | loops |
| PWR-DELAMINATION | Solar panel delamination / damage described | power |
| PWR-PANEL-NOT-WORKING | Solar panel(s) not working / unresponsive | power |
| PWR-DEAD-BATTERIES | Site batteries dead / exhausted | power |
| PWR-FUTURE-RISK | Engineer anticipates the site may go offline (e.g. winter / low light) | power |
| CAB-VEGETATION | Vegetation clearance noted (observation, not a repair) | cabinet |
| CAB-PESTS | Ants nest / pests noted | cabinet |
| CAB-FOLIAGE-CUT | Foliage cut back during the visit | cabinet |
- Resolved faults: if a test initially failed but the notes confirm successful restart / known-good-power retest, the final verified condition is scored and the initial failure kept in the audit trail.
- Intermittent faults confirmed in the notes make the component amber unless a significant confirmed failure warrants red.
- Explicit repair requirements in the notes count as interventions even when the checklist is blank, and are never counted twice. Repairs completed during the visit are not outstanding.
Interventions and Investment Priority
A blank repair checklist means no specific repairs were identified — not that the appraisal is incomplete. Interventions are classified as None Identified, Potential Routine, Specialist (RMA), Mixed, or Further Investigation.
| Contribution | Max | Rule |
|---|---|---|
| Observed condition deterioration | 50 | 0.5 × (100 − Condition Score) |
| Specialist / intervention burden (provisional) | 35 | RMA identified 25; +5 per additional independent confirmed internal fault; suspected internal fault without RMA 12 |
| Infrastructure concerns (provisional) | 15 | New Loops 10; Road Loop Termination Block 4; Wiring Loom / Battery Cables 5; Solar Panel(s) 3; Solar Inverter 3; Batteries 2; SIM 2; Cabinet Lock(s) 1; capped |
Burden values are provisional and configurable until WSCC agrees intervention costs; they are not quotes. Only confirmed (outstanding) interventions add burden — uncertain and completed ones are listed but not counted. A score threshold never triggers a replacement recommendation.
Why equipment age is not penalised
Age does not, by itself, evidence a fault. A functioning legacy counter that passes its tests is in satisfactory condition. Counter type is used only to choose the correct technical thresholds (e.g. 6V or 12V, signal scale).
Limitations
- Results reflect a single site visit and the engineer's recorded observations.
- Voltage readings are snapshots; they are not load tests or capacity measurements.
- An RMA indicates specialist assessment is likely needed; it does not confirm an internal fault, prove the counter cannot record traffic, or guarantee repair.
- Notes interpretation recognises explicit, well-defined patterns only. Ambiguous text is retained verbatim and flagged rather than interpreted.
- Intervention burden and priority weights are provisional.
