Skip to content

Vehicle fleet operations

Generated from the architecture model

This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
Vertical Fleet
Prototype reference Fleet prototype (ConnectSoft.DesignPrototypes)
Managed edition Managed (D33, D34)
Data residency tenant-region (D31)
Catalog Examples catalog · Vision-to-Production path for this vertical

Business problem

Vehicles, drivers, maintenance and telematics are in separate systems; compliance deadlines are missed.

Product intent

Fleet inventory, assignments, maintenance scheduling, telematics ingestion and compliance tracking.

What the Factory makes different here: telematics as inbound deliveries through the webhook pattern with replay and deduplication.

Vision-to-Production path for this vertical

Step Factory platform Agents Blueprints
Vision and product plan Agent Mesh, Control plane Enterprise Architect Agent, Integration Architect Agent vision
Architecture and domain Template & Library (BC-02) Enterprise Architect Agent service, module, integration, database
Experience Template & Library, Factory Studio UX track UX Designer Agent, Frontend Developer Agent mobile
Recipe and generation Template & Library (BC-15), Agent Mesh, Tools & MCP Enterprise Architect Agent, Integration Architect Agent, Backend Developer Agent, Mobile Developer Agent, QA Agent module plan from the context map
Quality Observability (BC-22), DevOps / GitOps QA Agent test
Delivery and provisioning DevOps / GitOps (BC-23, BC-24), Runtime Cloud (BC-25) DevOps Agent, Infrastructure Architect Agent —
Operations Product Fleet Operations (BC-35..37) — handover, objectives, rollouts, incidents, off-boarding

Delivery workflows exercised: monitoring-and-observability-workflows.

Generated product shape

C4Context
    title Vehicle fleet operations system context
    Person(user, "Users", "Fleet users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Vehicle fleet operations") {
        System(ctx_Vehicles, "Vehicles", "vehicles, documents, compliance")
        System(ctx_Assignments, "Assignments", "drivers, trips")
        System(ctx_Maintenance, "Maintenance", "work orders, parts")
        System(ctx_Telematics, "Telematics", "positions, events, alerts")
    }
    Rel(user, ctx_Vehicles, "uses through the product gateway GW-07")
    Rel(factory, ctx_Vehicles, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Vehicles vehicles, documents, compliance InspectionDue
Assignments drivers, trips TripCompleted
Maintenance work orders, parts WorkOrderClosed
Telematics positions, events, alerts AlertRaised

Modules and templates

Module Template Notes
Microservice ×4 connectsoft-microservice
Shell connectsoft-blazor-shell
Driver app connectsoft-maui-base
Every product also gets the SaaS foundations (tenants, editions, entitlements, billing, metering) and the product host shape (descriptor, health, operations handover) unless it is a library-only product.

Prototype reference

Fleet prototype in ConnectSoft.DesignPrototypes shows the intended screens; the UX track (U1–U4) maps prototype destinations to the UX model's screens with keep, merge, rename, retire or new decisions.

Operations as a managed product

Managed; telematics provider through a connector.