Top page for planning Data Architecture work between the 2025 Spring and Autumn AMMs.
As ideas become more formed it would be natural for them to become tasks in the Github issues backlog.
CAN feeders
CAN feeders
- Are feeders an example, or a core component that needs to be dockerized?
- Kuksa CAN Provider (Python version)
- Status: Initial fork adding IoTDB northbound (write) support is working
- Possible next steps / open questions
- Upstream? Steve asked Erik about this but
- Add IoTDB subscription support? May not be relevant outside the context of the Kuksa data provider
- Support writing to Information Layer?
- VISSR feeder template system: Add Information Layer and IoTDB support and upstream
Online Documentation improvements
Online doc improvements
- Navigation and UX improvements
- Introduction sections
- Task navigation
Examples/Patterns/Blueprints
Examples/patterns/blueprints
- Focus Areas
- AI / Advanced Reasoning
- Interoperability Vehicle-Cloud-Mobile
- Use Cases Ideas
- Predictive maintenance
- OTA
- In-car assistants
- Fleet data management
- Last-known-state
Data Modelling/definition
Data modelling/definition
Spring AMM workshop topics
Spring AMM workshop topics
- Summer dev strategy
- What do people want to work on and why? What is achievable and what is a stretch?
- Touchpoints – suggests longer chains
- What, why: smart use of resources, maintenance, showing integration versus stacks
- Examples in general
- Backlog for strengthening 'core'
- Is the idea of a 'core' still useful or is it simply reference compose combinations? If former when is something 'core'?
- Supporting VSS-next investigations
- AI connectors
- LLM data store abstractions, e.g. MCP
- Semantic Reasoning abstractions, e.g. Hybrid queries
- Enhancements to documentation to ease development
- Look and feel. Ease of navigation
- The UX template we are using is deprecated. Move to Hextra?
- Integration
- Feeder connection guide
- Server connection guide
- KL, IL relationship (connections?) to VISS/VISSR
