🚗 E-Mobility Driver App

A comprehensive SAP CAP-based application for e-mobility charging station management, built with TypeScript, Vue.js, and modern development tools.

📋 Description

This is a full-stack e-mobility application that enables drivers to:

🔑 Manage badges for charging station access
⚡ Start and stop charging sessions
📊 View charging statistics and history
🗺️ Find available charging stations
💳 Track charging costs and consumption

📦 Requirements

SAP Software

Software	Version	Notes
SAP Cloud Application Programming Model (CAP)	Latest	Core backend framework
SAP IAS (Identity Authentication Service)	-	Required for production authentication
SAP BTP Cloud Foundry	-	Required for deployment

Development Tools (Required)

Tool	Version	Notes
Node.js	>= 20	JavaScript runtime
npm	>= 8	Package manager
SAP CDS CLI	Latest	Installed automatically via `npm run install:all`

Development Tools (Optional)

Tool	Notes
MBT (SAP Multitarget Application Build Tool)	Required only for building the MTA archive
CF CLI (Cloud Foundry CLI)	Required only for deploying to Cloud Foundry
VS Code	Recommended IDE, with preconfigured launch configurations

🏗️ Architecture

driver-app/
├── 📱 app/driver-vue/         # Vue.js Frontend (UI5 Web Components)
├── 🔧 cli/                   # Development CLI Tools
├── 🎛️ srv/                   # CAP Backend Services & Business Logic
├── 📦 gen/                   # Generated Deployment Artifacts
│   ├── srv/                  # Generated CAP Server
│   └── policies/             # AMS Security Policies
└── 📄 mta.yaml              # Multi-Target Application Descriptor

🚀 Quick Start

Prerequisites

Node.js >= 20
npm >= 8
SAP CDS CLI

1. One-Command Installation

# Clone the repository
git clone <repository-url>
cd driver-app

# Install all dependencies across all modules
npm run install:all

The install command will:

✅ Check prerequisites (Node.js >= 20, npm >= 8)
✅ Install root project dependencies
✅ Install CLI tool dependencies
✅ Install frontend Vue.js app dependencies
✅ Install SAP CDS CLI globally (if not already installed)

Note: Generated service dependencies (gen/srv, gen/policies) are not installed automatically. These are created during build processes (cds build, npm run build:ams) and should be installed separately if needed.

2. Development Workflow

Option A: One-Command Start (Recommended)

cd cli
npm run cli bootstrap  # Configures environment + starts both servers

Option B: Step-by-Step Setup

# 1. Configure development environment
cd cli
npm run cli config     # Setup profiles and service bindings

# 2. Start development servers
npm run cli start      # Starts both backend + frontend

Option C: Backend Only (for debugging)

cd cli
npm run cli backend --debug  # Backend with debugging enabled

Note: If you haven't run the install script yet, use npm run install:all from the root directory to install all dependencies first.

📚 Module Documentation

Module	Description	Documentation
🎛️ Backend Services	CAP services, authentication, business logic	srv/README.md
📱 Frontend App	Vue.js SPA with UI5 Web Components	app/driver-vue/README.md
🔧 CLI Tools	Development automation and environment management	cli/README.md

🛠️ Development

Available Scripts

# Installation scripts
npm run install:all      # Install all dependencies (CLI-based)

# Root project scripts
npm run dev              # Start CAP server (hybrid profile)
npm run build:ams        # Build AMS policies
npm run lint             # Lint all code
npm run lint:fix         # Fix linting issues
npm run format           # Format code with Prettier

# CLI-based development (recommended)
cd cli
npm run cli install      # Install all dependencies via CLI
npm run cli config       # Configure environment
npm run cli start        # Start both servers
npm run cli backend      # Backend only
npm run cli profiles     # List configured profiles
npm run cli build        # Build MTA archive
npm run cli deploy       # Deploy to Cloud Foundry

🐛 Debugging

Backend Debugging

VS Code: Use F5 → "CLI - Start Servers (hybrid)" for full stack debugging
IntelliJ: Run → "CLI - Backend Only (Debug)"

Note: VS Code launch configurations are available in .vscode/launch.json. You can create additional configurations for backend-only debugging if needed.

You can also run the backend in debug mode directly from the CLI:

cd cli
npm run cli backend --debug    # Debug mode on port 9229
npm run cli start --debug      # Both servers with backend debugging

🔧 Configuration Profiles

The CLI supports multiple environment profiles:

npm run cli config          # Create/update profiles
npm run cli start --profile production

Profiles are stored in .cdsrc-private.json and include:

Service bindings (Cloud Foundry)
Authentication configurations
Environment-specific settings

🚀 Build & Deploy

Using CLI Commands (Recommended)

# Build MTA archive
cd cli && npm run cli build

# Deploy to Cloud Foundry
cd cli && npm run cli deploy

Manual Commands

# Build MTA archive
mbt build

# Deploy to Cloud Foundry
cf login -a <API_ENDPOINT> -o <ORG> -s <SPACE>
cf deploy mta_archives/driver-app_1.0.0.mtar

The CLI commands provide:

Prerequisites checking (MBT and CF CLI availability)
Interactive deployment (archive selection, confirmation prompts)
Error handling with helpful troubleshooting tips
Status feedback throughout the process

🔐 Security & Authentication

Production: SAP IAS (Identity Authentication Service)
Development: Custom mock authentication via CLI profiles
Authorization: Role-based access control with badges
AMS Integration: Authorization Management Service for policies

AMS Policies

This project integrates SAP Authorization Management Service (AMS) for policy-based authorization. At the moment, a single policy named "Driver" is used. You can extend the policy set to fit your needs.

Current default policy:

POLICY "Driver" {
  ASSIGN ROLE "Driver";
}

Assigning roles to users (IAS):

Policies are deployed to AMS and linked to the IAS tenant used for authentication.
In the IAS admin console, you can assign the "Driver" policy to users or groups.

QR Code

The application includes a secure QR code system for quick charging station access:

🔒 Security First: QR codes are encrypted using AES-256-GCM encryption
📱 Mobile Resolution: The app securely decrypts and resolves QR codes to start charging sessions
🏭 CLI Generation: Generate QR codes via cd cli && npm run cli generate-qr
📄 PDF Output: PDF documents ready for printing and distribution
🔐 Encryption Key: user-provided credential key configured in production (cli commands available for setup and synchronization)

Configuration

Production: The driver-app-qr-config user-provided service is automatically created during deployment, but the encryption key must be manually synchronized using CLI commands:

cd cli
npm run cli -- generate-qr --setup-key        # Generate and configure initial key
npm run cli -- generate-qr --sync-key-to-cf   # Push local key to CF service  
npm run cli -- generate-qr --sync-key-from-cf # Pull key from CF service
npm run cli -- generate-qr --show-key-status  # Check synchronization status

Development: Add encryption key to your local configuration (or use CLI commands to set it up):

// .cdsrc-private.json
{
  "qr-encryption": {
    "QR_ENCRYPTION_KEY": "your-64-character-hex-key"
  }
}

Usage Example:

cd cli
npm run cli start                       # Start backend server
npm run cli -- generate-qr --interactive  # Generate QR codes with prompts

Troubleshooting: If you see 🚨 QR_ENCRYPTION_KEY not configured!, use the CLI commands above to create and synchronize your encryption key.

🧪 Testing

# Frontend tests
cd app/driver-vue
npm run test              # Run unit tests
npm run test:coverage     # Run with coverage

# Backend tests
npm test                  # Run backend tests

📖 Technology Stack

Layer	Technology	Purpose
Frontend	Vue.js 3 + TypeScript	Reactive user interface
UI Components	SAP UI5 Web Components	Enterprise-grade UI components
Backend	SAP CAP + TypeScript	Business logic and OData services
Authentication	SAP IAS	Identity management
Authorization	SAP AMS	Policy-based access control

🌐 External Services & APIs

This application integrates with the following external services at runtime:

SAP E-Mobility

The backend proxies three OData APIs exposed by an SAP E-Mobility instance:

Service	API Path	Purpose
Charging Station Service	`/cpo/odata/chargingStation/v1`	Retrieve EVSE and charging station data
Charging Session Service	`/cpo/odata/chargingSession/v1`	Start/stop sessions, read CDRs and statistics
Badge Service	`/emsp/odata/badge/v1`	Read and manage driver badges

All three services use OAuth2 Client Credentials. In development the credentials are stored in .cdsrc-private.json (not committed); in production they are injected via a Cloud Foundry service binding (emobility-api).

See srv/README.md for the full list of required OAuth scopes and configuration details.

OpenStreetMap

The station map view uses two OpenStreetMap services:

Service	URL	Purpose
Tile Server	`https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png`	Renders interactive map tiles via Leaflet
Nominatim Geocoding	`https://nominatim.openstreetmap.org/search`	Place-name search and location suggestions

Both services are free and require no API key, but usage must comply with the OpenStreetMap Tile Usage Policy and the Nominatim Usage Policy. Map tiles are attributed as "© OpenStreetMap contributors" in the map UI.

🔄 Development Workflow

Setup: npm run install:all (installs all dependencies)
Configure: cd cli && npm run cli config (environment setup)
Start: cd cli && npm run cli start (start servers)
Code: Edit backend services in srv/ or frontend in app/driver-vue/src/
Test: Automatic hot-reload for both frontend and backend
Debug: Use IDE or npm run cli backend --debug for backend debugging
Build: cd cli && npm run cli build (create MTA archive)
Deploy: cd cli && npm run cli deploy (deploy to Cloud Foundry)

📞 Support

CLI Help: cd cli && npm run cli --help
CAP Documentation: SAP CAP Documentation
Vue.js Guide: Vue.js 3 Documentation
UI5 Web Components: UI5 Web Components

🤝 Contributing

We welcome contributions to this project! Please read our Contributing Guidelines before submitting a pull request.

For project-specific questions or issues, feel free to open a GitHub issue.

📜 Code of Conduct

We are committed to fostering a welcoming and respectful community. All participants are expected to uphold our Code of Conduct, which is based on the Contributor Covenant v3.0.

Key points:

Be respectful — treat everyone with dignity regardless of background or identity
Be constructive — give and receive feedback gracefully
Take responsibility — own your actions and commit to repairing harm when it occurs
Report issues — violations can be reported by opening a GitHub issue or contacting the maintainers directly

Please read the full CODE_OF_CONDUCT.md for details on expected behaviors, restricted behaviors, and the enforcement process.

Name		Name	Last commit message	Last commit date
Latest commit History 20 Commits
.github		.github
.run		.run
.vscode		.vscode
LICENSES		LICENSES
ams/dcl		ams/dcl
app/driver-vue		app/driver-vue
approuter		approuter
cli		cli
diagrams		diagrams
srv		srv
test		test
types		types
.cdsrc.json		.cdsrc.json
.clinerule		.clinerule
.eslintignore		.eslintignore
.gitignore		.gitignore
.prettierignore		.prettierignore
.prettierrc		.prettierrc
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
LICENSE		LICENSE
README.md		README.md
REUSE.toml		REUSE.toml
eslint.config.mjs		eslint.config.mjs
jest.config.js		jest.config.js
mta.yaml		mta.yaml
package-lock.json		package-lock.json
package.json		package.json
renovate.json		renovate.json
tsconfig.json		tsconfig.json

Folders and files

Latest commit

History

Repository files navigation

🚗 E-Mobility Driver App

📋 Description

📦 Requirements

SAP Software

Development Tools (Required)

Development Tools (Optional)

🏗️ Architecture

🚀 Quick Start

Prerequisites

1. One-Command Installation

2. Development Workflow

Option A: One-Command Start (Recommended)

Option B: Step-by-Step Setup

Option C: Backend Only (for debugging)

📚 Module Documentation

🛠️ Development

Available Scripts

🐛 Debugging

Backend Debugging

🔧 Configuration Profiles

🚀 Build & Deploy

Using CLI Commands (Recommended)

Manual Commands

🔐 Security & Authentication

AMS Policies

QR Code

Configuration

🧪 Testing

📖 Technology Stack

🌐 External Services & APIs

SAP E-Mobility

OpenStreetMap

🔄 Development Workflow

📞 Support

🤝 Contributing

📜 Code of Conduct

📄 License

About

Topics

Resources

License

Code of conduct

Security policy

Uh oh!

Stars

Watchers

Forks

Releases

Uh oh!

Contributors

Uh oh!

Languages