Project workspace
Vehicle program, validation campaign, role access, and traceability boundary.
Platform features
AurigaTrace connects test-log intake, parser capability management, signal statistics, rule findings, report generation, and controlled AI narratives in one engineering workspace.
CSV/JSONL/ASC
active parser paths
11
format capabilities
AI-safe
controlled context
Feature architecture
S3 raw logs
upload session registered
Parser registry
CSV, JSONL, ASC active; MF4 diagnostics preview
Signal statistics
sample count, min, mean, max
Rules
threshold and duration gates
Reports
HTML preview and exports
End-to-end workflow
The feature set is organized around evidence lineage. Engineers should always know which raw file, parser, signal statistic, rule, and report decision produced a conclusion.
Vehicle program, validation campaign, role access, and traceability boundary.
Upload session, raw object storage, checksum, source filename, and file registry.
Format capability, parser ID, parser version, and signal extraction contract.
Units, sample count, min, average, max, and first/last timestamp windows.
Threshold checks, duration gates, severity, finding status, and engineering summary.
HTML preview, export artifacts, controlled AI narrative, approval, and audit trail.
Feature modules
Register raw files against a project, preserve object-storage metadata, and queue analysis jobs without losing the original test evidence.
Expose each active, preview, and roadmap log format with capability level, parser identity, protocol coverage, and engineering notes.
Turn time-series data into repeatable numeric summaries that engineers can compare across runs and vehicle variants.
Run project rules against processed signals and generate traceable findings with severity and threshold evidence.
Create report previews from processed statistics, findings, and approved context, with export-ready HTML artifacts.
Draft narratives from stored statistics and rule findings while keeping raw logs and credentials out of AI context.
Parser coverage
CSV statistics, JSON/JSONL telemetry summaries, and ASC + DBC CAN foundation parsing are active now. MF4/MDF and diagnostics are preview diagnostics, while BLF, DLT, PCAP, and ROSBAG remain roadmap parser families.
The next hardening slice should deepen ASC + DBC coverage with multiplexed signals, CAN FD metadata, and bus-load summaries, then add BLF and MF4/MDF production parsers.
| Format | Status | Capability | Use |
|---|---|---|---|
| CSV | Active | full-signal-statistics | Generic time-series validation and EV logs |
| JSON/JSONL | Active | numeric-telemetry-statistics | Fleet telemetry, operational events, and structured validation logs |
| ASC + DBC | Active | can-frame-statistics-dbc-foundation | CAN and CAN FD text traces with DBC signal decoding foundation |
| MF4/MDF | Preview | runtime-inventory | Calibration and measurement channel inventory diagnostics |
| DTC/ODX/UDS | Preview | diagnostic-inventory | Diagnostic payload, service, and catalog inventory foundation |
| BLF | Roadmap | binary-trace-parser | High-throughput Vector binary bus traces |
| DLT | Roadmap | software-log-parser | AUTOSAR Adaptive, IVI, HPC, and software logs |
| PCAP | Roadmap | ethernet-flow-parser | Automotive Ethernet, SOME/IP, DoIP, and flows |
| ROSBAG | Roadmap | inventory-only | ADAS/autonomy topic inventory and replay linkage |
Rule evaluation
Engineers need more than charts. AurigaTrace stores rule thresholds, observed values, severity, finding status, and report references so each issue can be reviewed repeatedly.
min / avg / max
stored statistics
duration gates
sustained events
severity tags
finding priority
report links
review evidence
Signal rule board
| Signal | Metric | Observed | Rule | Severity |
|---|---|---|---|---|
| battery_temp_c | maximum | 45.5 | > 45.0 | critical |
| soc_pct | maximum | 91.2 | > 88.0 | info |
| brake_pressure | maximum | 86.0 | > 82.0 | warning |
| can_id_18ff50e5 | period drift | 12.7 ms | > 10.0 ms | warning |
AI and reports
AI narrative drafts are generated from stored project metadata, processed signal statistics, and findings. Request logs preserve provider, model, prompt version, context hash, token counts, and review outcomes.
Project metadata
Processed signal statistics
Rule findings
Prompt context hash
AI draft
Human approval
Report attachment
The dev environment already contains sample projects, log files, rules, findings, reports, and the format registry foundation for the next parser plugins.