Review accepted evidence from completed Guided Diagnostic runs in a structured, deterministic report, then export it locally to PDF. Evidence context and limitations remain part of the report. Engine Fault Scan is separate; a code list or an imported session is not automatically a SmartReport.
Coming soon for Windows. V1 scope: Giulia/Stelvio 2.2 JTD. The documented reference is a 2020 Stelvio 2.2 JTD with Bosch EDC17C69; other configurations require review.
Compare how complete, partial and insufficient evidence affect what can be concluded.
Read the evidence alongside its limitations.
Look for missing signals before drawing a conclusion.
Compare the recommendation with the available context.
Reading the examples
01Vehicle profile
02Report scope
03Overall status
04Capture snapshot
05Key evidence
06Summary
07Evidence ledger
08Deterministic rule evaluation
09Recommendation
10Inspection boundary
11Footer
Synthetic examples
The examples below use invented data and an illustrative layout. They are not actual SmartReport/PDF output, customer reports or live results, and do not demonstrate implemented signals or diagnostic rules. The example documents remain in English; the surrounding explanation is translated.
Report A
Synthetic example
Complete synthetic example — no abnormal pattern illustrated
Every expected signal in the Core / Standard scope was recognised, so the interpretation runs in full. The status is still qualified: it applies to the captured evidence, not to the vehicle.
No abnormal pattern in this synthetic exampleComplete
Illustrative diagnostic report — No abnormal pattern in this synthetic example
OBDVeloce
Diagnostic report
Deterministic
Local
Source-linked
Illustrative report facsimileSynthetic example data — not a real customer report or live diagnostic capture.
Vehicle profile
Vehicle
Alfa Romeo Stelvio
Engine
2.2 MultiJet / JTD
ECU
Bosch EDC17C69
Protocol
ISO 15765-4 CAN 29/500
Platform
Windows desktop
Report scope
Selected diagnostic group
Core / Standard
Source relationship
Linked source session
Interpretation
Deterministic and rule-based
Generation
Generated locally
Overall status
No abnormal pattern in this synthetic example
This status applies only to recognised evidence within the selected Core / Standard scope. It is not a complete mechanical verdict.
Capture quality
Complete
All five expected signals in this synthetic Core / Standard fixture are represented.
Capture evidence snapshot
Synthetic example data
Duration00:52
Recognised signals5 / 5
Missing signals0
Samples processed864
Selected groupCore / Standard
Capture qualityComplete
Key evidence — Core / Standard group
Synthetic example data
Engine RPM820rpm
Min
780
Avg
835
Max
910
Recognised
Vehicle speed0km/h
Min
0
Avg
0
Max
0
Recognised
Coolant temp.88°C
Min
86
Avg
88
Max
90
Recognised
Control-module voltage14.2V
Min
13.9
Avg
14.1
Max
14.4
Recognised
Intake air temp.24°C
Min
23
Avg
24
Max
25
Recognised
Summary
The recognised Core / Standard evidence is internally consistent within this illustrative capture.
No missing evidence limits the selected report scope.
OBDVeloce
Evidence ledger and deterministic interpretation
Illustrative report facsimileSynthetic example data — not a real customer report or live diagnostic capture.
Evidence ledger
Synthetic example data
Evidence ledger for the illustrative Core / Standard report
Signal
Current value / state
Minimum
Average
Maximum
Availability
Limitation
Engine RPM
820 rpm
780 rpm
835 rpm
910 rpm
Recognised
Limited to the captured Core / Standard scope
Vehicle speed
0 km/h
0 km/h
0 km/h
0 km/h
Recognised
Represents only the illustrated capture context
Coolant temperature
88 °C
86 °C
88 °C
90 °C
Recognised
Does not establish the complete cooling-system condition
Control-module voltage
14.2 V
13.9 V
14.1 V
14.4 V
Recognised
Represents captured electrical evidence only
Intake air temperature
24 °C
23 °C
24 °C
25 °C
Recognised
Limited to recognised captured evidence
Deterministic rule evaluation
When
the Core / Standard group is selected;
all expected fixture signals are recognised;
capture quality is Complete;
sufficient operating context is available.
Then
deterministic rules evaluate the available evidence;
supporting values are listed;
no missing-evidence limitation is recorded;
a qualified Healthy status may be assigned within the captured scope.
Otherwise
the interpretation becomes limited;
missing evidence remains visible;
another capture may be recommended.
Known limitations
Synthetic example data
This report covers only the selected Core / Standard diagnostic group.
It does not include all vehicle systems or operating conditions.
It does not replace workshop testing, service records or physical inspection.
Recommendation
No immediate focused recapture is recommended within this illustrative Core / Standard report scope.
Professional inspection boundary
This report organises and interprets captured diagnostic evidence. It does not replace professional mechanical inspection.
Report context
Local generation
Source-linked workflow
Visible limitations
Deterministic interpretation
Report B
Synthetic example
Partial but usable — caution, with the gaps named.
Two regeneration-history signals were not recognised. The available evidence still supports a limited interpretation, the missing signals stay visible in the ledger, and the recommendation asks for them rather than estimating them.
Caution within captured evidencePartial but usable
Illustrative diagnostic report — Caution within captured evidence
OBDVeloce
Diagnostic report
Deterministic
Local
Source-linked
Illustrative report facsimileSynthetic example data — not a real customer report or live diagnostic capture.
Vehicle profile
Vehicle
Alfa Romeo Stelvio
Engine
2.2 MultiJet / JTD
ECU
Bosch EDC17C69
Protocol
ISO 15765-4 CAN 29/500
Platform
Windows desktop
Report scope
Selected diagnostic group
DPF / Exhaust
Source relationship
Linked source session
Interpretation
Deterministic and rule-based
Generation
Generated locally
Overall status
Caution within captured evidence
This status applies only to recognised evidence within the selected DPF / Exhaust scope. It is not a complete mechanical verdict.
Capture quality
Partial but usable
Two expected contextual signals are missing. The available evidence is sufficient for limited interpretation.
Capture evidence snapshot
Synthetic example data
Duration01:18
Recognised signals8 / 10
Missing signals2
Samples processed1,284
Selected groupDPF / Exhaust
Capture qualityPartial but usable
Key evidence — DPF / Exhaust group
Synthetic example data
DPF differential pressure12.4mbar
Min
8.1
Avg
11.7
Max
17.2
Recognised
Exhaust gas temperature210°C
Min
184
Avg
205
Max
232
Recognised
Calculated soot load18g
Min
N/A
Avg
N/A
Max
N/A
Recognised
Regeneration stateInactive
Min
N/A
Avg
N/A
Max
N/A
Recognised
Engine load22%
Min
16
Avg
21
Max
29
Recognised
Engine RPM1,840rpm
Min
1,620
Avg
1,790
Max
2,080
Recognised
Vehicle speed68km/h
Min
55
Avg
64
Max
76
Recognised
Coolant temperature89°C
Min
87
Avg
89
Max
91
Recognised
Missing context — regeneration history
Distance since regeneration
Missing
Average distance between regenerations
Missing
Summary
Eight of ten expected DPF / Exhaust signals were recognised in this illustrative capture.
The two missing regeneration-history signals remain visible and limit the interpretation.
OBDVeloce
Evidence ledger and deterministic interpretation
Illustrative report facsimileSynthetic example data — not a real customer report or live diagnostic capture.
Evidence ledger
Synthetic example data
Evidence ledger for the illustrative DPF / Exhaust report
Signal
Current value / state
Minimum
Average
Maximum
Availability
Limitation
DPF differential pressure
12.4 mbar
8.1 mbar
11.7 mbar
17.2 mbar
Recognised
Limited to the captured DPF / Exhaust scope
Exhaust gas temperature
210 °C
184 °C
205 °C
232 °C
Recognised
Represents captured exhaust context only
Calculated soot load
18 g
N/A
N/A
N/A
Recognised
Model-derived value from captured signals
Regeneration state
Inactive
N/A
N/A
N/A
Recognised
State observed during captured interval
Engine load
22 %
16 %
21 %
29 %
Recognised
Limited to operating conditions captured
Engine RPM
1,840 rpm
1,620 rpm
1,790 rpm
2,080 rpm
Recognised
Limited to captured operating conditions
Vehicle speed
68 km/h
55 km/h
64 km/h
76 km/h
Recognised
Limited to captured operating conditions
Coolant temperature
89 °C
87 °C
89 °C
91 °C
Recognised
Represents captured engine thermal context
Distance since regeneration
Missing
N/A
N/A
N/A
Missing
Not recognised in this capture
Average distance between regenerations
Missing
N/A
N/A
N/A
Missing
Not recognised in this capture
Deterministic rule evaluation
When
DPF / Exhaust group selected
Recognised evidence available
Capture quality Partial but usable
Two contextual signals unavailable
Then
Evaluate available evidence
Show recognised measurements
Record missing context
Recommend follow-up capture
Otherwise
Insufficient data
No finding fabricated
Known limitations
Synthetic example data
This report covers only the selected DPF / Exhaust diagnostic group.
It does not include all vehicle systems or operating conditions.
It does not replace workshop testing, service records or physical inspection.
Recommendation
Repeat a focused DPF / Exhaust capture. Seek distance since regeneration and average distance between regenerations to reduce the recorded limitation.
Professional inspection boundary
This report organises and interprets captured diagnostic evidence. It does not replace professional mechanical inspection.
Report context
Local generation
Source-linked workflow
Visible limitations
Deterministic interpretation
Report C
Synthetic example
Insufficient data — no conclusion beyond the evidence.
Four of five expected EGR signals were unavailable. Rather than reach further, the report declines to interpret the group, lists what it did recognise, and names exactly which signals another capture should seek.
Insufficient dataInsufficient data
Illustrative diagnostic report — Insufficient data
OBDVeloce
Diagnostic report
Deterministic
Local
Source-linked
Illustrative report facsimileSynthetic example data — not a real customer report or live diagnostic capture.
Vehicle profile
Vehicle
Alfa Romeo Stelvio
Engine
2.2 MultiJet / JTD
ECU
Bosch EDC17C69
Protocol
ISO 15765-4 CAN 29/500
Platform
Windows desktop
Report scope
Selected diagnostic group
EGR
Source relationship
Linked source session
Interpretation
Deterministic and rule-based
Generation
Generated locally
Overall status
Insufficient data
The available evidence is insufficient for deterministic interpretation within the selected EGR scope.
Capture quality
Insufficient data
Most expected signals were not recognised. Another focused capture is recommended.
Capture evidence snapshot
Synthetic example data
Duration00:15
Recognised signals1 / 5
Missing signals4
Samples processed42
Selected groupEGR
Capture qualityInsufficient data
Key evidence — EGR group
Synthetic example data
Intake air quantity450mg/strokeRecognised
EGR valve positionMissingNot recognised
Commanded EGRMissingNot recognised
EGR cooler temperatureMissingNot recognised
Manifold absolute pressureMissingNot recognised
Summary
Only one of five expected EGR-scope signals was recognised.
The available evidence is insufficient for a deterministic group interpretation.
No conclusion has been inferred beyond the recognised evidence.
OBDVeloce
Evidence ledger and deterministic interpretation
Illustrative report facsimileSynthetic example data — not a real customer report or live diagnostic capture.
Evidence ledger
Synthetic example data
Evidence ledger for the illustrative EGR report
Signal
Current value / state
Minimum
Average
Maximum
Availability
Limitation
Intake air quantity
450 mg/stroke
N/A
N/A
N/A
Recognised
Recognised value only. Limited operating context.
EGR valve position
Missing
N/A
N/A
N/A
Missing
Signal not available in this capture.
Commanded EGR
Missing
N/A
N/A
N/A
Missing
Signal not available in this capture.
EGR cooler temperature
Missing
N/A
N/A
N/A
Missing
Signal not available in this capture.
Manifold absolute pressure
Missing
N/A
N/A
N/A
Missing
Signal not available in this capture.
Deterministic rule evaluation
When
The selected EGR group lacks sufficient recognised evidence.
Then
No deterministic group interpretation is produced.
Recognised evidence is listed.
Missing evidence remains visible.
Insufficient data is reported.
Another focused capture may be recommended.
Otherwise
Deterministic rules evaluate the available evidence.
Known limitations
Synthetic example data
Four expected EGR signals were unavailable.
The current capture does not provide sufficient context for deterministic interpretation.
No mechanical conclusion has been generated.
Recommendation
Review connection and group selection. Repeat a focused EGR capture.
Seek recognition of
EGR valve position
Commanded EGR
EGR cooler temperature
Manifold absolute pressure
Purpose
Obtain sufficient recognised evidence for deterministic evaluation.
Professional inspection boundary
This report organises and interprets captured diagnostic evidence. It does not replace professional mechanical inspection.
Report context
Local generation
Source-linked workflow
Visible limitations
Deterministic interpretation
Side by side
What actually differs between the three.
Compare the evidence, the gaps and the conclusions across the three examples.
What actually differs between the three.
Aspect
Report A
Report B
Report C
Selected group
Core / Standard
DPF / Exhaust
EGR
Capture quality
Complete
Partial but usable
Insufficient data
Overall status
No abnormal pattern in this illustration
Caution within captured evidence
Insufficient data
Recognised signals
All expected signals
Most expected signals
One expected signal
Group interpretation
Produced in full
Produced with stated limits
Withheld
Recommendation
No focused recapture needed
Recapture to recover the missing context
Recapture, seeking named signals
Layout and components
Identical
Identical
Identical
Why deterministic reporting matters
A report you can check is worth more than one you must trust.
Every finding above can be traced to the evidence that produced it, and every gap in that evidence is stated where a reader will see it.
01
Reproducible
With unchanged accepted evidence, context and rule version, the interpretation is repeatable. SmartReport/PDF does not rely on the separate AI Analysis prototype.
02
Evidence-linked
SmartReport retains the accepted evidence context of its completed diagnostic run, so findings can be read with their supporting measurements and limitations.
03
Transparent about gaps
Missing evidence is recorded rather than estimated. A gap narrows a finding; it is never filled in to make the report look complete.
04
Explicitly bounded
Every report states what it does not establish, in the report itself rather than in a footnote elsewhere.
Understanding example statuses
What a status does and does not say.
These status descriptions explain the synthetic examples above. Read any actual report within its evidence scope: a clean fault scan or an available signal does not establish the vehicle’s complete mechanical condition.
No abnormal pattern in this illustration
Means
No rule reached a caution or warning state within the evidence available.
Does not mean
That the vehicle has been mechanically certified healthy.
Caution
Means
Recognised evidence met a rule that asks for further investigation.
Does not mean
That a repair is definitely required.
Warning
Means
Recognised evidence deviated markedly from what the rule expected.
Does not mean
That a specific component has been conclusively diagnosed without further verification.
Insufficient data
Means
Required evidence was missing, so no dependable conclusion was reached.
Does not mean
That the vehicle has failed or is unsupported.
A report status reflects captured diagnostic evidence. It is not a verdict on the complete mechanical condition of the vehicle.
Missing data
Absent evidence is recorded, not invented.
Expected evidence is sometimes not there. What happens next is the part worth understanding, because it is where a diagnostic tool is most tempted to guess.
Missing evidence is recorded rather than silently substituted.
Unsupported or unavailable data stays visible as a limitation.
Missing evidence may narrow a finding to what remains supportable.
One missing signal does not invalidate every other recognised sample.
It may produce a recommendation for another focused capture.
Where too little remains, a finding is withheld rather than guessed.
Missing evidence is not proof of a mechanical fault.
Never done
Estimating a missing value
Generating a value to fill the gap
Promising the signal will appear on another attempt
Treating a repeatedly missing signal as component failure
A partial capture, read honestly
Where a focused group returns most of its expected evidence but not all of it, the available evidence is preserved, the gap is listed, the finding is stated with its limitation, and a focused recapture is recommended. Nothing is discarded and nothing is filled in.
Report library
Reports are kept apart from the sessions that produced them.
A saved report is its own item. It is stored separately from diagnostic sessions and does not appear among them, so an interpretation is never mistaken for the evidence it came from.
Diagnostic sessions
Carry a source badge that keeps their origin visible.
Live
Imported JSON
Legacy
Demo
Saved reports
SmartReport retains accepted evidence from a completed Guided Diagnostic run. PDF export creates a local document for review; it does not add measurements or send the report to anyone.
A report does not replace its source session.
A report retains its source-session relationship.
A report is listed apart from active sessions.
A report remains an interpretation of the available evidence.
Keep the source context
Keep the source sessions and run context alongside any exported PDF when you need to review how the evidence was collected. Sharing a document remains your choice.
Source traceability
The report stays linked to the evidence behind it.
Traceability here means the application workflow retains the relationship between a report and what produced it, so the evidence behind a finding can be reviewed.
What the retained relationship preserves
The completed run and its accepted source evidence
The diagnostic groups that were selected
The evidence accepted for the completed run
The interpretation that was applied to it
The original capture is not modified
Generating or regenerating a report reads the saved source data. The original session is not rewritten, and another session is never silently substituted for it.
When source evidence is unavailable
An exported PDF remains a readable document, but it cannot replace missing session or run data for further analysis.
Not claimed
Immutable or tamper-proof evidence
Cryptographic signatures or notarisation
A certified audit trail or forensic chain of custody
Protection against a file being changed by hand
What reports do not establish
The boundary of any report.
A report organises the available evidence and states its limits. It does not establish any of the following.
AI Analysis is a separate prototype/planned capability, not an integrated production feature. SmartReport/PDF is deterministic.
Unexplained AI judgement
Self-learning diagnosis
Machine-learning confidence
Automatic diagnosis
Guaranteed diagnosis
Guaranteed repair
A complete mechanical inspection
Universal vehicle coverage
Confirmation that a missing signal is a fault
Confirmation that an available signal is mechanically healthy
Immutable evidence
Tamper-proof evidence
Cryptographic signatures
Built-in email sending
Public report links
Cloud report hosting
Automatic off-device backup
A report organises and interprets what a capture contained. It does not replace professional mechanical inspection.
Before a report exists
A useful report starts with a supported capture.
Interpretation is limited by the evidence available, and the evidence is limited by the configuration. Confirm compatibility first.
