slug: bringg
provider: Bringg
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Transportation & Logistics
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 10
edges:
- tag: Delivery Blocks
  spec_file: bringg-delivery-blocks-api-openapi.yml
  capability_id: BC-2440.20
  capability_id_l1: BC-2440
  capability_name: Rostering and Scheduling Management
  confidence: 0.85
  evidence: '''delivery blocks (driver shift slots)''; POST /services/assign_delivery_block  assignDeliveryBlock  Assign
    Delivery Block; GET /services/users_delivery_blocks  Get Delivery Blocks By User'
  reason: Delivery blocks are explicitly driver shift slots, created and assigned to users and teams —
    this is construction and assignment of driver duty rosters, i.e. rostering and scheduling of drivers.
- tag: Routes
  spec_file: bringg-routes-api-openapi.yml
  capability_id: BC-2420.10
  capability_id_l1: BC-2420
  capability_name: Dispatch Management
  confidence: 0.85
  evidence: POST /services/assign_run_driver  Assign Driver To Route; POST /services/assign_run_vehicle  Assign
    Vehicle To Route
  reason: All four operations assign or unassign drivers and vehicles to delivery routes (runs), which
    is precisely dispatch — assignment of drivers and equipment to transport moves.
- tag: Orders
  spec_file: bringg-orders-api-openapi.yml
  capability_id: BC-2420.40
  capability_id_l1: BC-2420
  capability_name: Last-Mile Delivery Operations Management
  confidence: 0.8
  evidence: 'POST /services/start_task  Start Order; POST /services/end_task  End Order; POST /services/cancel_task  Cancel
    Order — within ''last-mile delivery orchestration: orders (tasks)'''
  reason: Full lifecycle of delivery orders (tasks) — create, update, start, end, cancel, open-order queries
    — on a last-mile delivery orchestration platform. This is execution of final-leg delivery jobs, i.e.
    Last-Mile Delivery Operations Management; some ambiguity versus generic order fulfilment orchestration.
- tag: Delivery Slots
  spec_file: bringg-delivery-slots-api-openapi.yml
  capability_id: BC-2330.50
  capability_id_l1: BC-2330
  capability_name: Consumer Delivery Slot Management
  confidence: 0.78
  evidence: POST /services/create_planned_delivery_window  Create Planned Delivery Window; "planned delivery
    windows (delivery slots)"
  reason: Operations create and update planned consumer delivery windows, which is exactly consumer delivery
    slot management in an omnichannel last-mile context.
  recovered_from: vertical-retail-consumer-goods-edges.json
- tag: Shifts
  spec_file: bringg-shifts-api-openapi.yml
  capability_id: BC-2440
  capability_id_l1: BC-2440
  capability_name: Driver & Crew Operations Management
  confidence: 0.75
  evidence: POST /services/start_shift  Start Shift; POST /services/end_shift  End Shift — "shift management
    (start/end shift, driver home events, availability)"
  reason: Operations record driver duty start/end, squarely driver & crew operations. Not clearly roster
    construction nor hours-of-service compliance, so only the L1 is asserted.
- tag: Vehicles
  spec_file: bringg-vehicles-api-openapi.yml
  capability_id: BC-2430
  capability_id_l1: BC-2430
  capability_name: Fleet & Mobile Asset Management
  confidence: 0.75
  evidence: POST /services/create_vehicle  Create Vehicle; GET /services/get_all_vehicles  Get All Vehicles;
    POST /services/assign_run_vehicle  Assign Vehicle To Route
  reason: Vehicle master records plus assignment of vehicles to routes is management of mobile assets;
    spans registry and dispatch use, so only L1 asserted.
- tag: Planned Routes
  spec_file: bringg-planned-routes-api-openapi.yml
  capability_id: BC-520.50
  capability_id_l1: BC-520
  capability_name: Logistics Operations Management
  confidence: 0.72
  evidence: '"Create Planned Route Identifier", "Update Planned Route Identifier"; API covers "routes
    (runs)"'
  reason: Route planning objects for delivery runs — transport route planning, a core logistics operations
    activity.
  recovered_from: vertical-automotive-mobility-edges.json
- tag: Customers
  spec_file: bringg-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: POST /services/create_customer  createCustomer  Create Customer; POST /services/update_customer  updateCustomer  Update
    Customer
  reason: Core operations create and maintain customer records in the delivery platform, which is customer
    master data maintenance. Slightly reduced confidence because the remaining operations manage customer-specific
    driver blacklists, a delivery-operations concern.
- tag: Drivers
  spec_file: bringg-drivers-api-openapi.yml
  capability_id: BC-2420.10
  capability_id_l1: BC-2420
  capability_name: Dispatch Management
  confidence: 0.7
  evidence: POST /services/assign_task  assignTask  Assign Order To Driver; POST /services/assign_run_driver  assignRunDriver  Assign
    Driver To Route
  reason: The dominant operations assign orders and routes to drivers, which is dispatch assignment of
    loads and drivers to transport moves. Confidence tempered because the tag also mixes in driver location
    updates, availability and QR-code utilities that belong to driver/crew and telematics capabilities.
- tag: Packages
  spec_file: bringg-packages-api-openapi.yml
  capability_id: BC-520.50
  capability_id_l1: BC-520
  capability_name: Logistics Operations Management
  confidence: 0.7
  evidence: '"Create Package", "Get Task Packages" in an API for "last-mile delivery orchestration: ...
    packages"'
  reason: Parcel/package records attached to delivery tasks — shipment handling within last-mile logistics
    operations.
  recovered_from: vertical-automotive-mobility-edges.json