44 lines
1.7 KiB
Markdown
44 lines
1.7 KiB
Markdown
# Portfolio case-study template
|
|
|
|
## Title
|
|
|
|
MobilityOps — connected operations for vehicle rental and service teams
|
|
|
|
## One-sentence summary
|
|
|
|
A working synthetic-data PoC that unifies vehicle and booking operations, automates vehicle returns, surfaces data-quality problems and exposes grounded internal knowledge through reusable RAG and MCP platforms.
|
|
|
|
## Problem
|
|
|
|
Operational information was modelled as fragmented across booking, vehicle and procedure sources, causing manual checks, inconsistent states and slow access to instructions.
|
|
|
|
## Approach
|
|
|
|
- MobilityOps owns canonical operational data and business rules.
|
|
- A transactional return workflow persists inspections, derives status and queues post-commit orchestration.
|
|
- Explainable rules detect duplicates, mileage regressions, overlaps, missing fields and status conflicts.
|
|
- RAGcore provides source-grounded procedure answers.
|
|
- ITWorx MCP Hub exposes narrowly scoped read-only AI tools.
|
|
- n8n orchestrates secondary processing without becoming the business-rule engine.
|
|
|
|
## Demonstrable results
|
|
|
|
Use only facts actually measured in the final build, such as:
|
|
|
|
- 50 deterministic synthetic vehicles and 245 bookings;
|
|
- five automated data-quality rule types;
|
|
- one end-to-end return workflow;
|
|
- ten versioned source procedures;
|
|
- four read-only MCP tools;
|
|
- tested degraded modes for RAGcore and n8n.
|
|
|
|
Do not claim real customer adoption, production use or percentage time savings.
|
|
|
|
## Stack
|
|
|
|
React, TypeScript, FastAPI, PostgreSQL, n8n, RAGcore, ITWorx MCP Hub, Docker Compose and Playwright.
|
|
|
|
## Demo disclosure
|
|
|
|
All data and the represented company are fictitious. The software behaviour, integration contracts, audit trail and validation are implemented as a real proof of concept.
|