slug: avnet provider: Avnet generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Electrical Components & Equipment - Software & Technology 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: 15 edges: - tag: OTA spec_file: avnet-ota-api-openapi.yml capability_id: BC-1950.30 capability_id_l1: BC-1950 capability_name: Over-the-Air Update Management confidence: 0.95 evidence: POST /api/v2/ota-update 'Send OTA update'; 'Get device list for OTA update with update status'; 'Update device OTA update cancel status' reason: Explicit over-the-air firmware update orchestration across devices, including status tracking and cancellation of scheduled updates — exactly Over-the-Air Update Management. - tag: Firmware spec_file: avnet-firmware-api-openapi.yml capability_id: BC-1950.20 capability_id_l1: BC-1950 capability_name: Firmware Build & Release Management confidence: 0.9 evidence: POST /api/v2/Firmware 'Add new firmware'; PUT '/api/v2/Firmware/{firmwareGuid}/deprecate Deprecate Firmware'; 'Validate firmware' reason: Firmware registry with versioning, validation and deprecation for connected devices — squarely Firmware Build & Release Management (version inventory and release approval). - tag: FirmwareUpgrade spec_file: avnet-firmwareupgrade-api-openapi.yml capability_id: BC-1950.30 capability_id_l1: BC-1950 capability_name: Over-the-Air Update Management confidence: 0.9 evidence: POST /api/v2/firmware-upgrade 'Add new firmware upgrade'; PUT '.../publish Publish firmware upgrade' reason: Creating and publishing firmware upgrade campaigns against devices in an OTA platform ('API methods to firmware communication and OTA') — Over-the-Air Update Management. - tag: Telemetry spec_file: avnet-telemetry-api-openapi.yml capability_id: BC-1950.40 capability_id_l1: BC-1950 capability_name: Device Telemetry & Connectivity Management confidence: 0.9 evidence: '''Get device sensor list''; ''Get telemetry historical data for all attributes''; ''Get mqtt reader information for gateway child device''' reason: Ingestion, streaming readers (MQTT/STOMP) and historical query of device telemetry attributes and locations — Device Telemetry & Connectivity Management on a connected-product platform. - tag: Certificate spec_file: avnet-certificate-api-openapi.yml capability_id: BC-1950.10 capability_id_l1: BC-1950 capability_name: Device Identity & Provisioning Management confidence: 0.85 evidence: Get self signed certificate for your device; Get certificate for your device according to platformType certificate-bundle; POST /api/v2.1/device/certificate-import Device certificate import reason: Operations issue, import, retrieve and delete X.509 credentials bound to devices, which is precisely issuance and lifecycle of device identities and cryptographic credentials. - tag: IoTEdgeDeployment spec_file: avnet-iotedgedeployment-api-openapi.yml capability_id: BC-1950.70 capability_id_l1: BC-1950 capability_name: Edge & Gateway Operations Management confidence: 0.85 evidence: POST /api/v2/iot-edge/deployments 'Create new IoT Edge Deployment'; schemas 'IoTEdgeModule', 'IoTEdgeRoute' reason: Deployment of edge modules and routes to gateway/edge devices — Edge & Gateway Operations Management. - tag: Device spec_file: avnet-device-api-openapi.yml capability_id: BC-1950 capability_id_l1: BC-1950 capability_name: Connected Product & Firmware Management confidence: 0.8 evidence: POST /api/v2.1/Device Add new device; PUT /api/v2.1/Device/{uniqueId}/acquire Acquire device broker info from cloud; schema DeviceLifeCycle reason: Large surface managing the registration, lifecycle, status and broker binding of connected devices in the /IOTCONNECT platform. Clearly Connected Product & Firmware Management at L1; too broad to pin one sub-capability. - tag: User spec_file: avnet-user-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.8 evidence: POST /api/v2.1/User 'Add new user'; 'Update user status'; 'Change password'; ChangePasswordRequest, ResetPasswordRequest, CognitoUserGetList reason: User account lifecycle, role/entity assignment and credential management — squarely Identity & Access Management. - tag: Deployment spec_file: avnet-deployment-api-openapi.yml capability_id: BC-1950.30 capability_id_l1: BC-1950 capability_name: Over-the-Air Update Management confidence: 0.78 evidence: POST /api/v2/deployments Create scheduled deployment for device update; schema DeviceUpdate reason: Creating scheduled deployments for device updates is over-the-air update planning and execution on fielded devices. Rollback is not shown, so slightly below top confidence. - tag: JitpRule spec_file: avnet-jitprule-api-openapi.yml capability_id: BC-1950.10 capability_id_l1: BC-1950 capability_name: Device Identity & Provisioning Management confidence: 0.78 evidence: POST /api/v2.1/JitpRule Add new jitp rule; GET /api/v2.1/JitpRule/regextype-lookup Get RegexType lookup reason: JITP (just-in-time provisioning) rules match device certificate attributes to auto-register devices, which is device identity and provisioning management on the IIoT platform. - tag: Role spec_file: avnet-role-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.75 evidence: POST /api/v2.1/Role 'Add new role'; 'Update role status'; 'Get role list with user count' reason: Lifecycle of authorisation roles assigned to platform users is access management; mapped to Identity & Access Management with moderate confidence since it is a platform-internal admin surface. - tag: Command spec_file: avnet-command-api-openapi.yml capability_id: BC-1950 capability_id_l1: BC-1950 capability_name: Connected Product & Firmware Management confidence: 0.7 evidence: POST /api/v2.1/template-command/device/{deviceGuid}/send Execute a command on device; Get scheduled command list reason: Defines and dispatches remote commands to fielded devices, including scheduling and command history — operational control of connected products. Evidence does not pin a single L2. - tag: Data Export spec_file: avnet-data-export-api-openapi.yml capability_id: BC-1950.40 capability_id_l1: BC-1950 capability_name: Device Telemetry & Connectivity Management confidence: 0.7 evidence: '''Export telemetry Data'', ''Export child telemetry Data'', schema ''CosmosExportHistoryList''' reason: Operations explicitly export device telemetry data accumulated by the IIoT platform, which falls under telemetry management for connected products. It is partly a generic data-export mechanism, hence moderate confidence. - tag: DeviceUpdate spec_file: avnet-deviceupdate-api-openapi.yml capability_id: BC-1950.30 capability_id_l1: BC-1950 capability_name: Over-the-Air Update Management confidence: 0.7 evidence: GET /api/v2/device-updates 'Get device updates list'; POST '/api/v2/device-updates/import-update Import Device Update' reason: IOTCONNECT device update management — orchestrating updates to fielded devices, which maps to OTA update management within Connected Product & Firmware Management. Sub-capability slightly uncertain (update campaign vs device tagging), hence moderate confidence. - tag: WirelessDevice spec_file: avnet-wirelessdevice-api-openapi.yml capability_id: BC-1950 capability_id_l1: BC-1950 capability_name: Connected Product & Firmware Management confidence: 0.7 evidence: POST /api/v2.1/WirelessDevice 'Add new wireless device'; 'Get lorawan master data'; POST /api/v2.1/WirelessDevice/lorawanGateway 'Create LorawanGateway' reason: Registration and profile management of LoRaWAN/Sidewalk wireless devices and gateways, queued messages and command status — connected-product operations spanning provisioning, connectivity and gateway ops, so the L1 is clear but the sub-capability is not.