slug: cnh
provider: CNH
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Automotive & Mobility
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: 3
edges:
- tag: Equipment
  spec_file: cnh-equipment-api-openapi.yml
  capability_id: BC-3540.30
  capability_id_l1: BC-3540
  capability_name: Farm Equipment Management
  confidence: 0.8
  evidence: GET /equipment  listEquipment  List equipment; 'vehicle telemetry for both agronomic machinery
    and construction equipment connected to a FieldOps account'
  reason: Inventory and retrieval of connected agricultural machines with ISO 15143-3 telemetry maps to
    Farm Equipment Management (equipment inventory, machinery telemetry). Construction-equipment coverage
    adds slight ambiguity.
  recovered_from: vertical-agriculture-food-production-edges.json
- tag: Prescriptions
  spec_file: cnh-prescriptions-api-openapi.yml
  capability_id: BC-3530.20
  capability_id_l1: BC-3530
  capability_name: Nutrient Management Planning
  confidence: 0.7
  evidence: POST /prescriptions  sendPrescription  Send prescription Rx file to vehicle or FieldOps
  reason: Agronomic prescription (Rx) files are variable-rate application prescriptions sent to machinery;
    this matches nutrient/application prescription generation and delivery. Some ambiguity between nutrient
    management planning and crop protection planning, so confidence moderate.
  recovered_from: vertical-agriculture-food-production-edges.json
- tag: Vehicle Telemetry
  spec_file: cnh-vehicle-telemetry-api-openapi.yml
  capability_id: BC-3460.10
  capability_id_l1: BC-3460
  capability_name: Vehicle Connectivity Platform Operations
  confidence: 0.7
  evidence: GET /telemetry/{vehicleId} 'Get vehicle telemetry (ISO 15143-3)', GET /telemetry/{vehicleId}/fault-codes
    'Get fault codes for a vehicle', schemas Location, Telemetry
  reason: Operations serve vehicle-to-cloud telemetry, location and fault-code data for connected machines,
    which is the vehicle connectivity/telemetry platform capability. Some ambiguity remains with diagnostic
    service operations (fault codes) and vehicle data platform, hence moderate confidence.