DECISION 01
OEM Automakers
STANDARDIZE GLOBAL VEHICLE PLATFORMS
Establish compute and autonomy stack baselines across model lines, regions, and vehicle generations.
AUR / SOLUTIONS / OEM
SEGMENT 01 OF 03 · 3 DECISIONS
01 / STATEMENT
Compute and autonomy stack baselines maintained across model lines, regions, and vehicle generations.
02 / ADDRESSED DECISIONS
DECISION 01
OEM Automakers
Establish compute and autonomy stack baselines across model lines, regions, and vehicle generations.
DECISION 02
OEM Automakers
Define ADAS compute, perception, and software architecture baselines across multi-year vehicle programs.
DECISION 03
OEM Automakers
Set Tier-1, compute, and software partner boundaries within unified vehicle platform architectures.
03 / PRESENCE
RELIED ON ACROSS ADAS AND AUTONOMY EXECUTIVE FUNCTIONS
OEM Automakers
04 / FUNCTIONAL DOMAINS
FUNCTIONAL DOMAIN
5 DOMAINS · 5 ENTRIESEach entry of the record specimen, assigned to the executive function or functions it concerns
Domain
Record specimen AR-2026-04-01-V1
Entries
E1
E2
E3
E4
E5
01AUTONOMY AND PERCEPTION ENGINEERING
Perception stack, sensor fusion, autonomy architecture
02SIMULATION, VERIFICATION AND VALIDATION
Simulation, scenario testing, verification, safety case
03VEHICLE PLATFORM AND SYSTEMS INTEGRATION
Vehicle integration, sensor hardware, E/E architecture, zonal systems
04SOFTWARE INFRASTRUCTURE AND DATA OPERATIONS
Middleware, operating layers, data pipelines, ML data operations
05EXECUTIVE PRODUCT AND STRATEGY
Platform roadmap, product direction, sourcing timing, architecture transition
01AUTONOMY AND PERCEPTION ENGINEERING
Perception stack, sensor fusion, autonomy architecture
E3 · E4
02SIMULATION, VERIFICATION AND VALIDATION
Simulation, scenario testing, verification, safety case
E1 · E2 · E5
03VEHICLE PLATFORM AND SYSTEMS INTEGRATION
Vehicle integration, sensor hardware, E/E architecture, zonal systems
E2 · E5
04SOFTWARE INFRASTRUCTURE AND DATA OPERATIONS
Middleware, operating layers, data pipelines, ML data operations
E3
05EXECUTIVE PRODUCT AND STRATEGY
Platform roadmap, product direction, sourcing timing, architecture transition
E4
Entry key · Record specimen AR-2026-04-01-V1
05 / FUNCTIONS
FUNCTION · REGISTRY
3 FUNCTIONS06 / ENGAGEMENT PROCESS
ENGAGEMENT · PROCESS
INQUIRY → RECORD · 5 STAGESSubmitted through Inquiry by the executive.
Accepted or declined on relevance, scope, and program stage.
Constituted bilaterally with the executive and scoped per program.
Conducted multi-month to multi-year under non-public, non-attributable terms.
Maintained as an internal engagement record across the relationship.
07 / ISSUANCE TIMELINE
ISSUANCE TIMELINE · 52 WEEKS
2025-W43 – 2026-W43
Q4 2025
10 ISSUED · 1 NONE
Q1 2026
12 ISSUED
Q2 2026
13 ISSUED
Q3 2026
14 ISSUED
Q4
2
NEXT
DUE
Cross-References
3 REFERENCES
SVC.01
BY REVIEW / INVITATIONAurigent Research issues governed intelligence records on a fixed 7-day cadence, relied upon in executive decision processes on multi-year ADAS and autonomy roadmap direction.
SVC.02
BY REVIEW / INVITATIONAurigent Advisory engages directly with select senior executives responsible for multi-year ADAS and autonomy architecture, platform, and vehicle program investments.
SVC.03
INVITATION ONLYAurigent Events convenes private, invite-only roundtables for senior ADAS and autonomy executives to calibrate platform and architecture direction across autonomy programs.
08 / INQUIRY
Aurigent engagements with OEM automaker executives are constituted on an inquiry basis. Submissions are reviewed on relevance, scope, and program stage.