V2X — Connected Mobility
Audience-specific engagement and pilot design.
On this page
Partners & pilots
Approved intake for engineering discovery, architecture review, integration assessment and controlled pilot design — without invented scheduling.
- Engagement menu
- Pilot design
- Intake journey
- Deliverables
Page contract
What, who, boundaries and next step.
- What it is
- Audience-specific engagement menu and pilot design intake — without invented scheduling.
- Who needs it
- All five cohorts ready for a concrete next deliverable.
- Problem / intended benefit
- Accepted inquiries are mistaken for booked pilots.
- Ciright responsibility
- Owns durable inquiry acceptance and routing.
- Keyra responsibility
- Required only for protected pilot/workspace records.
- Demonstrated
- Engagement menu and contact handoff.
- Proposed / Unverified
- Pricing, schedules and deployment dates.
- Evidence
- Inquiry state machine in docs/r3/registers/inquiry-state-machine.md; runtime tests Not Run.
Prerequisites
- Role, country/region, use case, requested next step
- No VINs, subscriber details, precise trips, private keys or confidential engineering evidence via public forms
Limitations
- Success UI only after durable acceptance
- Failed notification must not lose accepted inquiry
- Scheduling confirmation is a separate state
Engagement menu
Concrete next steps — not a shopping cart.
- Engineering discovery
Deliverable Scoped problem framing and dependency map.
Team V2X product + engineering
Inputs Role, region, use case, equipment context (no VINs or private keys).
Does not imply production availability or commercial terms.
- Architecture review
Deliverable Direct/network path review against your configuration assumptions.
Team V2X engineering
Inputs Target profiles, identity model, operator constraints.
Review is advisory; not protocol conformance certification.
- Integration assessment
Deliverable Interface and Core/Keyra boundary assessment.
Team Integration lead
Inputs Existing Ciright subscription context if any; sandbox needs.
Uses approved api.ciright.com contracts only.
- Controlled pilot design
Deliverable Pilot design package with success criteria and safety boundaries.
Team V2X product + QA
Inputs Audience, geography, equipment inventory, success measures.
Commercial terms separately agreed; no invented deployment dates.
- Supported production integration
Deliverable Integration plan where production evidence exists for the configuration.
Team Release + operations
Inputs Approved readiness evidence and commercial authorization.
Only where configuration readiness is Production and authorized.
Evidence posture
Demonstrated versus proposed.
Every material claim requires configuration scope, source/version, owner and review date before it can leave Unverified. Industry explanations (including 5GAA direct/network context) are not Ciright hardware proof.
Take a reliable next step.
Public education stays readable. Protected accounts, pilot records and privileged functions require Keyra verification. General corporate inquiry assurance policy is preserved until product/security owners change it.