slug: decisiv
provider: Decisiv
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: 26
edges:
- tag: Registered Assets
  spec_file: decisiv-registered-assets-api-openapi.yml
  capability_id: BC-2430
  capability_id_l1: BC-2430
  capability_name: Fleet & Mobile Asset Management
  confidence: 0.9
  evidence: createRegisteredAsset 'Create a new Registered Asset'; asset_management_ra_update_meter_data
    'Update an existing Registered Asset meter data'; getBuildInformation 'Get the SRM verified build
    information for a registered asset'; schemas meter_data_odometer_registered_asset, transfer_registered_asset
  reason: Full lifecycle of vehicle asset records for a fleet account — registration, update, deactivation,
    transfer, odometer/engine-hour meter readings and OEM build information — is squarely provisioning
    and upkeep of mobile assets. No single L2 covers the asset register itself.
- tag: Account User Roles
  spec_file: decisiv-account-user-roles-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.85
  evidence: POST .../users/{account_user_id}/relationships/roles  addAccountUserRoles  Add roles to an
    account user
  reason: Grants and revokes roles for platform user accounts, which is role-based access administration
    (IAM), not an industry business capability.
- tag: Cases
  spec_file: decisiv-cases-api-openapi.yml
  capability_id: BC-2430.20
  capability_id_l1: BC-2430
  capability_name: Fleet Maintenance Management
  confidence: 0.85
  evidence: POST /service_management/.../cases/{id}/update_meter_data "Updates Meter Data"; schemas case_update_meter_data_odometer_meter,
    case_update_meter_data_eng_hours; module manages "an asset's case lifecycle"
  reason: Core repair-case lifecycle for commercial vehicles including odometer and engine-hour meter
    capture — this is fleet maintenance management of mobile assets.
- tag: Service Requests
  spec_file: decisiv-service-requests-api-openapi.yml
  capability_id: BC-2430.20
  capability_id_l1: BC-2430
  capability_name: Fleet Maintenance Management
  confidence: 0.85
  evidence: POST /asset_management/{srm_account_id}/v1/service_requests 'Create a new Service Request'
    ... 'cancelServiceRequest'
  reason: Creation, update and cancellation of vehicle service (repair) requests by a fleet against its
    assets — this is corrective/preventive maintenance work request management for mobile assets.
- tag: Diagnostic Readings
  spec_file: decisiv-diagnostic-readings-api-openapi.yml
  capability_id: BC-2430.40
  capability_id_l1: BC-2430
  capability_name: Fleet Telematics and Monitoring
  confidence: 0.82
  evidence: GET /telematics/{srm_account_id}/v1/diagnostic_readings  listDiagnosticReadings  List all
    diagnostic readings for the requested account; POST createDiagnosticReading
  reason: Ingestion and retrieval of vehicle diagnostic readings via the vendor's telematics API, also
    surfaced against service cases. This is continuous monitoring of mobile-asset condition to inform
    maintenance — Fleet Telematics and Monitoring.
- tag: Registered Components
  spec_file: decisiv-registered-components-api-openapi.yml
  capability_id: BC-2430
  capability_id_l1: BC-2430
  capability_name: Fleet & Mobile Asset Management
  confidence: 0.8
  evidence: POST /asset_management/{srm_account_id}/v1/registered_components createRegisteredComponent
    'Create a new Registered Component'; schema registered_component_properties-data
  reason: CRUD over components registered against commercial vehicles in a fleet account extends the mobile-asset
    record; component-level registry is part of fleet/mobile asset management.
- tag: Account Roles
  spec_file: decisiv-account-roles-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.78
  evidence: GET /account_management/v1/accounts/{account_id}/roles  listAccountRoles  List account roles
  reason: Read operations over the roles available on an account within the platform's Account Management
    module — authorisation/role reference data, i.e. identity and access management plumbing, not a transport
    business capability.
- tag: Case Line Items Technician Stories
  spec_file: decisiv-case-line-items-technician-stories-api-openapi.yml
  capability_id: BC-2430.20
  capability_id_l1: BC-2430
  capability_name: Fleet Maintenance Management
  confidence: 0.78
  evidence: POST /service_management/{srm_account_id}/v1/cases/{case_id}/line_items/{line_item_id}/technician_stories
    — "Creates a technician story for the line item"; module manages "an asset's case lifecycle from a
    Service Providers perspective"
  reason: Technician narratives attached to repair-order line items document corrective maintenance work
    performed on commercial vehicles, i.e. fleet maintenance execution records.
- tag: Faults
  spec_file: decisiv-faults-api-openapi.yml
  capability_id: BC-2430.40
  capability_id_l1: BC-2430
  capability_name: Fleet Telematics and Monitoring
  confidence: 0.78
  evidence: POST /telematics/{srm_account_id}/v1/faults  createFault  Create a new fault; GET /service_management/.../cases/{case_id}/faults  List
    all Faults for a specific Case
  reason: Vehicle fault codes captured through the telematics API and associated with service cases —
    monitoring of asset condition feeding maintenance. Fleet Telematics and Monitoring is the best fit;
    'Faults' is not an IT incident surface here.
- tag: VMRS
  spec_file: decisiv-vmrs-api-openapi.yml
  capability_id: BC-2430.20
  capability_id_l1: BC-2430
  capability_name: Fleet Maintenance Management
  confidence: 0.78
  evidence: '"List all VMRS Reasons for Repair (Code Key 14)", "List all VMRS Work Accomplished values
    (Code Key 15)", "List all VMRS Technician Part Failure Codes"'
  reason: VMRS is the Vehicle Maintenance Reporting Standard code set; these endpoints serve repair reasons,
    priorities, components, work-accomplished and part-failure codes used to record vehicle repairs. That
    is maintenance reference data for fleet assets, not generic master data — though it is read-only taxonomy,
    hence not maximal confidence.
- tag: Customer Assets
  spec_file: decisiv-customer-assets-api-openapi.yml
  capability_id: BC-2430
  capability_id_l1: BC-2430
  capability_name: Fleet & Mobile Asset Management
  confidence: 0.75
  evidence: POST /service_management/.../customer_assets "Create a new Customer Asset"; GET .../customer_assets/{id}/service_history
    "List Service History for the specific Customer Asset"
  reason: Registration and service-history retrieval for customer vehicles (mobile assets) held by a service
    provider — fleet/mobile asset management; spans registry and maintenance history so only the L1 is
    asserted.
- tag: Service Group - Customers
  spec_file: decisiv-service-group-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.75
  evidence: GET /service_management/{srm_account_id}/v1/service_group/customers 'List all Customers from
    Service group'; PATCH .../customers/{id} 'Updates a Customer from Service group'; schemas update_registered_customer,
    customer_properties-data
  reason: Listing and updating customer records held by a service provider is maintenance of the customer
    master record, mapping to Customer Data Management.
- tag: assets
  spec_file: decisiv-assets-api-openapi.yml
  capability_id: BC-2430
  capability_id_l1: BC-2430
  capability_name: Fleet & Mobile Asset Management
  confidence: 0.75
  evidence: '"GET /assets/{asset_id}/recalls", "GET /assets/{asset_id}/warranties", "GET /assets/{asset_id}/service_history",
    "GET /assets/{asset_id}/build_information"'
  reason: CRUD over commercial-vehicle assets plus their recalls, campaigns, warranties, build information
    and service history — the mobile-asset register underpinning fleet management. Kept at L1 because
    the surface spans registry, warranty and maintenance history rather than one sub-capability.
- tag: Customers
  spec_file: decisiv-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.72
  evidence: POST /service_management/{srm_account_id}/v1/customers  Create a new Customer; schemas 'create_customer',
    'update_registered_customer'
  reason: CRUD over customer master records (create, retrieve, update a Customer) within the SRM platform
    — this is customer data/master record maintenance, not service execution. Mapped to Customer Data
    Management; some chance it is better read as account setup, hence moderate confidence.
- tag: Deactivated Assets
  spec_file: decisiv-deactivated-assets-api-openapi.yml
  capability_id: BC-2430
  capability_id_l1: BC-2430
  capability_name: Fleet & Mobile Asset Management
  confidence: 0.72
  evidence: POST /asset_management/{srm_account_id}/v1/deactivated_assets/{id}/activate  Re-enable a previously
    inactive asset for use within the Account
  reason: Assets here are commercial vehicles registered by a fleet account ('Account registered with
    a Fleet subscription'); the operations manage the active/inactive state of the fleet asset register.
    That is fleet/mobile asset management, but the evidence does not name a specific sub-capability (not
    clearly acquisition/disposal vs utilisation), so only L1 is asserted.
- tag: Sublet Cases
  spec_file: decisiv-sublet-cases-api-openapi.yml
  capability_id: BC-2430.20
  capability_id_l1: BC-2430
  capability_name: Fleet Maintenance Management
  confidence: 0.72
  evidence: GET /service_management/{srm_account_id}/v1/sublet_cases 'Retrieves a list of sublet cases'
    within the module 'managing an asset's case lifecycle from a Service Providers perspective'
  reason: Sublet repair cases are the work orders for outsourced portions of a commercial-vehicle repair
    event; this is maintenance work management for mobile assets.
- tag: Sublet Requests
  spec_file: decisiv-sublet-requests-api-openapi.yml
  capability_id: BC-2430.20
  capability_id_l1: BC-2430
  capability_name: Fleet Maintenance Management
  confidence: 0.72
  evidence: POST /service_management/{srm_account_id}/v1/sublet_requests 'Create a new sublet request'
    ... 'Cancel sublet request', schemas 'sublet_case', 'service_provider', 'parent_case'
  reason: Requests to sublet part of a vehicle repair to another service provider, with cancel/update
    lifecycle — repair work order management for commercial vehicles.
- tag: Webhooks
  spec_file: decisiv-webhooks-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.72
  evidence: '''Create new webhook for the requested account'', ''Refresh webhook signing key'', schemas
    webhook_create, update_webhook_request'
  reason: Full lifecycle management of outbound webhook endpoints and their signing keys exposed to platform
    integrators, which is exactly the frame's webhook & event subscription capability. Not raised higher
    because webhook endpoints can also be read as pure integration plumbing.
  recovered_from: sweep-20260828T235257Z-edges.json
- tag: Case Actions
  spec_file: decisiv-case-actions-api-openapi.yml
  capability_id: BC-2430.20
  capability_id_l1: BC-2430
  capability_name: Fleet Maintenance Management
  confidence: 0.7
  evidence: '"The Decisiv SRM Gateway `Service Management` module provides the API functionality for managing
    an asset''s case lifecycle from a Service Providers perspective"; POST .../cases/{case_id}/actions/close
    "Close a specific case"'
  reason: A 'case' here is a service/repair event on a commercial vehicle asset handled by a service provider;
    opening and closing cases is repair-event lifecycle control, i.e. fleet maintenance management. Confidence
    held below 0.8 because 'case' could also be read as a generic service ticket.
- tag: Case Line Item Parts
  spec_file: decisiv-case-line-item-parts-api-openapi.yml
  capability_id: BC-2430.20
  capability_id_l1: BC-2430
  capability_name: Fleet Maintenance Management
  confidence: 0.7
  evidence: 'POST .../cases/{case_id}/line_items/{line_item_id}/parts "Create a estimate item part"; schemas:
    create_estimate_item_part, update_estimate_item_part'
  reason: Manages the parts attached to repair-estimate line items on a vehicle service case, which is
    core repair/maintenance work-order content for commercial vehicles.
- tag: Case Line Items
  spec_file: decisiv-case-line-items-api-openapi.yml
  capability_id: BC-2430.20
  capability_id_l1: BC-2430
  capability_name: Fleet Maintenance Management
  confidence: 0.7
  evidence: POST .../cases/{case_id}/line_items createCaseLineItem "Create a line item for the requested
    case"; module "provides the API functionality for managing an asset's case lifecycle from a Service
    Providers perspective"
  reason: Line items are the repair/estimate work lines of a vehicle service case, so this surface realises
    maintenance work-order content management for commercial vehicle assets.
- tag: Contacts
  spec_file: decisiv-contacts-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: GET /service_management/{srm_account_id}/v1/customers/{customer_id}/contacts "List all Contacts
    for the requested Customer"; createContact/updateContact/deleteContact
  reason: CRUD over customer contact master records for fleet/customer accounts — customer data management.
- tag: Registered Components Relationships
  spec_file: decisiv-registered-components-relationships-api-openapi.yml
  capability_id: BC-2430
  capability_id_l1: BC-2430
  capability_name: Fleet & Mobile Asset Management
  confidence: 0.7
  evidence: PATCH /asset_management/.../registered_components/{component_id}/relationships/registered_asset
    'Add, Update or Remove a Registered Asset from Registered Component'
  reason: Maintains the component-to-vehicle association in the asset register, i.e. structural upkeep
    of mobile asset records. Single relationship endpoint keeps confidence moderate.
- tag: Service Group - Customer Assets
  spec_file: decisiv-service-group-customer-assets-api-openapi.yml
  capability_id: BC-2430.20
  capability_id_l1: BC-2430
  capability_name: Fleet Maintenance Management
  confidence: 0.7
  evidence: POST /service_management/.../service_group/customer_assets/{id}/create_case 'Create a case
    for the specific Customer Asset from Service Group'; GET .../service_history 'List Service History
    for the specific Customer Asset'
  reason: Creating repair cases against a customer's vehicle and retrieving its service history is maintenance
    event initiation and history for mobile assets, i.e. fleet maintenance management from the service
    provider side.
- tag: Service Group - Customer Contacts
  spec_file: decisiv-service-group-customer-contacts-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: POST /service_management/.../service_group/customers/{customer_id}/contacts 'Create a Contact
    for Service Group Customer'; schemas contact, contact_update, create_contact
  reason: CRUD over contact records attached to service-provider customers is customer contact master
    data upkeep rather than any transport-specific capability.
- tag: Webhooks Events
  spec_file: decisiv-webhooks-events-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.7
  evidence: '''List webhook events which are available for subscription by the designated account'''
  reason: Publishes the catalogue of event types subscribable via webhooks — event schema/subscription
    surface of the developer integration platform. Single read operation keeps confidence moderate.
  recovered_from: sweep-20260828T235257Z-edges.json