Active formats
-
available parser paths
Platform map
Platform Capabilities
ActiveCurrent workspace: Capabilities
Page usage manualManual
Capabilities guide
Use Platform Capabilities as the engineering feature map for active, preview, admin-only, and roadmap workflows.
What it provides
- Capability coverage for upload, processing, diagnostics, signal viewing, rules, reports, exports, AI, and administration.
- Parser-format readiness for CSV, JSON/JSONL, ASC + DBC, DTC/UDS, PCAP/DoIP, BLF, MF4/MDF, DLT, and roadmap formats.
- Role-aware links so Engineers stay in assigned project workflows while Admins can open governance pages.
How to use it
- 1. Review active, preview, admin-only, and roadmap capabilities with direct links into the right workflow page.
- 2. Scan Active, Preview, Admin, and Roadmap labels before using a workflow.
- 3. Open the linked page for the capability you need.
- 4. Use Admin-only links only for platform configuration and governance.
Outcome: Teams understand what the platform supports today, what is preview, and where each feature is used.
Preview
-
visible with limits
Roadmap
-
not production workflow
AI context
-
approved summary source
Role
Engineer
assigned projects
Workflow capability map
This page is the user-facing feature map. It shows which platform areas are ready for engineering work, which are preview, and which are controlled by Admin governance.
| Area | Capability | Status | Role | Engineering value | Action |
|---|---|---|---|---|---|
| Projects | Project registry, readiness, technical data, and diagnostic context | Active | Both | Vehicle program setup and assigned project context | Open |
| Uploads | Single log intake, upload sessions, and batch import | Active | Both | Governed project evidence intake | Open |
| Processing | Parser jobs, analysis runs, and decoder results | Active | Both | Structured signal statistics and decoded evidence | Open |
| Diagnostics | Offline diagnostic decode, DTC review, timeline, freeze frames, and evidence export | Active | Both | UDS, DTC, negative-response, and diagnostic evidence workflows | Open |
| Signals | Log Analysis Viewer, signal workbench, dictionary, protocol trace, and analytics | Active | Both | Signal and trace evidence inspection | Open |
| Rules | Rule library, evaluation, templates, and calibration limits | Active | Both | Threshold and duration gates | Open |
| Findings | Findings queue, event timeline, DTC review, and evidence pack | Active | Both | Reviewable engineering findings | Open |
| Reports | Report generation, library, review, and controlled templates | Active | Both | Engineering report evidence workflow | Open |
| AI Assistant | Context builder, narrative drafts, approved context, and AI audit | Active | Both | Controlled Anthropic Claude narrative support | Open |
| Admin | Team access, format registry, parser workbench, observability, operations, audit | Admin | Admin | Platform governance and production operations | Admin controlled |
| Exports | Signal exports, trace exports, evidence bundles, diagnostic bundle records | Preview | Both | Traceable export artifact history | Open |
| Future formats | ROSBAG/MCAP ingestion, deeper ODX enrichment, broader PCAP/BLF/MF4 depth | Roadmap | Admin | Roadmap parser expansion after production baseline | Admin controlled |
Parser and format support
Format rows come from the platform registry. Engineers see support expectations; Admins manage activation and parser diagnostics from the Admin section.
| Format | Domain | Parser | Runtime | Signals | Events | AI Context | Status |
|---|---|---|---|---|---|---|---|
| Loading formats... | |||||||