Skip to content

ABS Platform Business Models

The ABS Platform supports multiple business models, each representing a distinct service type in the energy ecosystem. Each model is implemented as a self-contained DIRAC-enabled service unit.

Scope: Technology Implementation Only

This repository focuses on DIRAC framework implementation for operational technology. Financial modeling and unit economics are maintained in a separate project repository.

🔍 Service Models vs. Business Units

Service Models (ABS Platform Perspective)

The ABS Platform implements service models that define customer-facing operational services: - BSS: Battery Swap Service - Customer subscription and battery swap operations - SNS: Swap Network Service - Multi-station network coordination and optimization - FCS: Fast Charging Service - EV charging operations and management - EPS: Electric Power Service - Power distribution and grid integration - VRS: Vehicle Rental Service - Vehicle rental and fleet operations

Each service model defines workflows, FSMs, agents, and technical implementation details.

Business Units (BUFM Financial Perspective)

Financial analysis treats participants as business units with distinct P&L: - BCS (Battery Circulation Service): Asset owner/provider managing battery assets - SNS (Swap Network Service): Station operator managing customer relationships - EPS (Electric Power Service): Energy supplier managing power distribution

Relationship Example: The BSS service model involves both BCS (asset provider) and SNS (network operator) business unit participants.

Note: This repository focuses on operational service models. Business unit financials (BUFM) are maintained separately.

🏗️ Business Model Architecture

Each business model follows the Self-Containment Principle:

  • Complete Functional Unit: All related code, documentation, tests, and configuration together
  • Agent Implementation: Model-specific service agents with FSM workflows
  • Setup Data: Configuration templates and sample data
  • Design Intent: Business logic specifications and workflow documentation
  • Integration Patterns: DIRAC framework integration and external system connectivity

📊 Current Business Models

✅ BSS - Battery Swap Service

Status: ✅ Production Ready
Location: bss/

Ecosystem Role: Service operator managing battery swap networks for end customers

  • Service Type: Asset-based subscription with battery fleet management
  • Target Market: Electric mobility riders (motorcycles, scooters, devices)
  • Key Features: Real-time battery swapping, location-based service, IoT integration
  • DIRAC Implementation: Enhanced functional architecture with centralized state management

🔄 SNS - Swap Network Service

Status: 📋 Planned
Location: sns/

Ecosystem Role: Network operator coordinating multiple swap stations and fleet resources

  • Service Type: Multi-station network operations and optimization
  • Target Market: Regional swap network operators and franchisees
  • Key Features: Network coordination, station management, fleet optimization
  • DIRAC Implementation: Network-level orchestration and resource balancing

🔄 FCS - Fast Charging Service

Status: 📋 Planned
Location: fcs/

Ecosystem Role: Charging station operator providing rapid charging infrastructure

  • Service Type: High-speed EV charging operations and management
  • Target Market: EV owners, fleet operators, charging network providers
  • Key Features: Rapid charging, dynamic pricing, station monitoring
  • DIRAC Implementation: Real-time charging session management and grid integration

🔄 EPS - Electric Power Service

Status: 📋 Planned
Location: eps/

Ecosystem Role: Energy supplier managing power distribution and grid integration

  • Service Type: Power distribution and grid integration services
  • Target Market: Energy consumers (residential, commercial, industrial)
  • Key Features: Grid integration, demand management, renewable energy
  • DIRAC Implementation: Smart metering, demand response, and energy trading workflows

🔄 VRS - Vehicle Rental Service

Status: 📋 Planned
Location: vrs/

Ecosystem Role: Fleet operator providing vehicle rental and mobility services

  • Service Type: EV rental with flexible terms and fleet operations
  • Target Market: Individual renters, ride-sharing operators, delivery companies
  • Key Features: Fleet tracking, usage billing, maintenance scheduling
  • DIRAC Implementation: Asset lifecycle management and rental agreement workflows

🎯 Business Model Standards

Required Components

Each business model MUST include:

{model}/
├── README.md                    # Model overview and documentation
├── model-status.md              # Implementation status and progress
├── {model}-agent-v{n}.ts        # Service agent implementation
├── {model}-fsm-v{n}.json        # FSM state definitions
├── design-intent/               # Business logic and workflow specifications
├── setup-data/                  # Configuration templates and sample data
├── tests/                       # Model-specific tests
├── diagrams/                    # Model-specific diagrams
└── interactions/                # System interaction patterns

Naming Conventions

Following the File Naming Convention Standardization:

  • Model codes: 3-4 letter lowercase abbreviations (bss, sns, fcs, eps, vrs)
  • File prefixes: All files use model code prefix (bss-, sns-, fcs-, etc.)
  • Version suffixes: Version numbers when applicable (-v1, -v2)
  • Location suffixes: Geographic specificity when needed (-nairobi, -kenya)

Integration Requirements

Each business model integrates with:

  • DIRAC Framework: FED (API layer) and BRO (messaging layer)
  • Platform Services: ARM (Asset Relations), Odoo (ERP), BIA (Analytics)
  • External Systems: IoT devices, payment gateways, regulatory systems
  • Common Infrastructure: FSM engine, agent system, GraphQL schema

🚀 Development Workflow

Adding New Business Models

  1. Create model directory: models/{model-code}/
  2. Copy template structure: Use BSS as reference template
  3. Define business logic: Create design-intent documentation
  4. Implement agent: Service agent with FSM workflows
  5. Create setup data: Configuration templates and samples
  6. Integration testing: DIRAC framework integration
  7. Documentation: Update model status and navigation

Model Development Phases

  1. 📋 Planned: Business requirements defined, directory structure created
  2. 🔄 Development: Active implementation in progress
  3. 🧪 Testing: Integration testing and validation
  4. ✅ Production Ready: Deployed and operational

📋 Cross-Model Architecture

Shared Infrastructure

  • FSM Engine: O(1) performance finite state machine implementation
  • Agent System: Data-driven agent architecture with plugin support
  • GraphQL Schema: Unified API layer for all business models
  • Template System: ServicePlanTemplate and versioning architecture
  • MQTT Integration: Real-time messaging and IoT device connectivity

Business Model Isolation

  • Independent Development: Models can be developed and deployed independently
  • Separate Configurations: Each model has its own setup data and agent configuration
  • Model-Specific APIs: GraphQL resolvers and mutations per business model
  • Isolated Testing: Independent test suites and validation frameworks

Platform Architecture: DIRAC Framework
Development Guidelines: Development Guide
Platform Overview: Architecture Overview