slug: solarwinds
provider: SolarWinds
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Banking & Capital Markets
- 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: 6
edges:
- tag: Changes
  spec_file: solarwinds-changes-api-openapi.yml
  capability_id: BC-600.30
  capability_id_l1: BC-600
  capability_name: IT Service Management
  confidence: 0.8
  evidence: GET /changes.json  listChanges  'Solarwinds List Change Requests'
  reason: Change requests alongside incidents and problems is the classic ITIL/ITSM process set, which
    is exactly BC-600.30 (incident, problem, change). Evidence is a single read operation, hence not maximal
    confidence.
- tag: Incidents
  spec_file: solarwinds-incidents-api-openapi.yml
  capability_id: BC-600.30
  capability_id_l1: BC-600
  capability_name: IT Service Management
  confidence: 0.8
  evidence: POST /incidents.json  createIncident  'Solarwinds Create an Incident'; schemas IncidentCreate,
    CategoryRef, UserRef
  reason: CRUD over incident tickets with category and assignee references is IT service management incident
    handling, not financial or safety incidents. Alternative reading as SaaS incident response keeps it
    below 0.9.
- tag: Search
  spec_file: solarwinds-search-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.72
  evidence: searchEvents "Initiate a Search Query", getEvents "Retrieve Search Results"; schemas LogEvent,
    EventsResponse
  reason: Operations search and page through log events (LogEvent schema) in a cloud log-management service
    — this is log observability, not a generic business search.
- tag: Checks
  spec_file: solarwinds-checks-api-openapi.yml
  capability_id: BC-600.40
  capability_id_l1: BC-600
  capability_name: IT Operations Management
  confidence: 0.7
  evidence: POST /checks  createCheck  'Solarwinds Create a New Check'; schemas Check, CheckDetail, CheckList
  reason: Full CRUD over monitoring 'checks' (uptime/synthetic monitors) from a vendor described as doing
    'IT infrastructure management, monitoring, and observability' — day-to-day IT operations monitoring.
    Could arguably be SaaS observability, hence moderate confidence.
- tag: Problems
  spec_file: solarwinds-problems-api-openapi.yml
  capability_id: BC-600.30
  capability_id_l1: BC-600
  capability_name: IT Service Management
  confidence: 0.7
  evidence: GET /problems.json  listProblems  Solarwinds List Problems; schema Problem
  reason: '''Problems'' sitting alongside Incidents and Change Requests is the ITIL problem-management
    record type, mapping to IT Service Management. Only one read operation, so confidence is moderate.'
- tag: ServiceRequests
  spec_file: solarwinds-servicerequests-api-openapi.yml
  capability_id: BC-600.30
  capability_id_l1: BC-600
  capability_name: IT Service Management
  confidence: 0.7
  evidence: GET /service_requests.json listServiceRequests "List Service Requests"; POST createServiceRequest
    "Create a Service Request"; schemas ServiceRequestCreate, ServiceRequest, UserRef
  reason: Creating and listing service requests raised by users against IT systems is IT service management
    (service catalogue / request fulfilment). Vendor is an IT management vendor, so ITSM is the honest
    reading rather than any customer-service or banking capability.