VENDOR INTAKE WORKBENCH

Vendor ODC Intake Workbench

The practical workflow is not asking engineers to fill 144 elements one by one. Import manuals, configuration tables, operating rules, or sanitized excerpts first; generate an ODC draft table and boundary-combination candidates; then let authorized vendor contacts confirm and publish.

Organization Verification

Verify submitters through corporate email domains, vendor-admin invitations, or trusted partner allowlists. Selecting a vendor name on a public page is not authentication.

Source Import

Import owner manuals, feature guides, configuration tables, robotaxi operating rules, OTA notes, or sanitized internal boundary documents.

ODC Extraction

Map text to the 144 elements in GB/T 45312—2025, including evidence snippets, parameter ranges, unspecified gaps, and boundary-combination candidates.

Confirm and Publish

After vendor confirmation, publish through a portal, API, CSV review package, or GitHub community contribution path.

MANUAL TO ODC TABLE

Generate an ODC Draft Table

Browser-local processing

Organization / Vendor Feature Name Model / Operating Scenario Automation Level Corporate Email or Domain Source URL Source File The public page records the filename only; it does not upload or parse the file. Paste Manual, Rule, or Sanitized Excerpt

Import source material to generate a draft table across the 144 ODC elements.

Publication Should Not Depend on GitHub Alone

Target Mode

Vendor Portal

Corporate-domain verification, admin approval, role permissions, version freeze, legal sanitization, and publication confirmation happen inside the portal.

Near-Term

Review Package

Export CSV / JSON / Markdown and submit it through email, enterprise IM, or a web form for OpenODC administrator review.

At Scale

API / Batch Sync

Suitable for OEMs and Tier 1 suppliers maintaining many models, markets, feature versions, SOP releases, and OTA updates.

Community Path

Open-Source PR

Useful for researchers, developers, and contributors who already use GitHub. Vendor engineers can use review packages, portals, or APIs first.

Minimum Vendor-Confirmation Loop

Stage	Question to Resolve	OpenODC Artifact
Identity	Who is submitting on behalf of the vendor, and is the submission authorized?	Corporate domain, contact role, review record
Extraction	Which of the 144 elements are covered by manuals or rules, and which remain gaps?	ODC draft table, evidence snippets, source links, page references
Confirmation	Which fields can be public, and which must remain internal?	Public field list, sanitization notes, version identifier
Publication	How does the confirmed record enter the gallery and remain traceable?	Approved JSON, CSV, changelog, and evidence snapshot