Mobility Systems
Designs adaptive mobility solutions that improve access, safety, and resilience in transportation.
- Transit equity
- Operations optimization
- Accessibility
Research
The common research layer coordinates data, models, services, and evaluation.
Builds the shared digital backbone that powers ASPIRE research, data exchange, and human-centered tools. In practice, this shared layer hosts common methods and services that can be adapted in Mobility, Manufacturing, Nursing, and Agriculture without fragmenting the research architecture.
Digital Twin (DT) lifecycle orchestration: The shared platform coordinates how data, models, and operational context move across the Digital Twin lifecycle.
Artificial Intelligence (AI) models: AI models are developed as reusable platform components rather than isolated single-domain outputs.
Communication and edge-cloud coordination: The research agenda includes communication pathways that connect field settings, platform services, and distributed computation.
Core services, APIs, and SDKs: Core services, Application Programming Interfaces (APIs), and Software Development Kits (SDKs) provide reusable interfaces for project components.
Each Domain Program applies the shared platform in context and contributes new evidence back to the common system.
Designs adaptive mobility solutions that improve access, safety, and resilience in transportation.
Develops resilient manufacturing platforms and workforce-centered production workflows.
Creates digital tools to support nursing practice, care coordination, and patient outcomes.
Builds adaptive platforms for sustainable and resilient agricultural operations.
The shared platform and the four Domain Programs are linked through a recurring cycle of collection, modeling, deployment, and feedback.
Step 1
Collect real-time field data.
Step 2
Align data, models, and services.
Step 3
Test methods in domain settings.
Step 4
Feed evidence back into the platform.
Shared orchestration, models, and services are adapted in each domain as field conditions and use cases become more concrete.
Domain PoCs feed evidence back into platform design so interfaces, services, and evaluation practices can improve across the project as a whole.