slug: servicechannel
provider: ServiceChannel
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- 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: 9
edges:
- tag: Invoices
  spec_file: servicechannel-invoices-api-openapi.yml
  capability_id: BC-200.20
  capability_id_l1: BC-200
  capability_name: Accounts Payable Management
  confidence: 0.85
  evidence: '''Add an invoice to a work order''; ''Allows approve non-MLI(Multilevel Invoice Approval)
    invoice''; ''Allows reject...''; POST /invoices/{invoiceId}/Payment ''Add a payment to an invoice'''
  reason: Contractor invoice capture, approval/rejection/hold, discrepancy checking and payment posting
    is classic accounts-payable invoice processing and vendor payment, as the vendor description confirms
    ('process contractor invoices').
- tag: NotificationSubscriptions
  spec_file: servicechannel-notification-subscriptions-api-openapi.yml
  reanchored_from: servicechannel-notificationsubscriptions-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.82
  evidence: '''List existing subscriptions''; POST /NotificationSubscriptions/Http ''Create a subscription'';
    ''Get a signing key''; ''Regenerate a signing key'''
  reason: HTTP callback subscription lifecycle with payload signing keys is outbound webhook/event subscription
    management on the vendor's developer platform. Not a facilities capability — it is API ecosystem plumbing,
    which this L2 explicitly covers.
- tag: Assets
  spec_file: servicechannel-assets-api-openapi.yml
  capability_id: BC-700
  capability_id_l1: BC-700
  capability_name: Facilities Management
  confidence: 0.75
  evidence: GET /assets/{assetId}  Get an asset; POST /assets/assetsforreplacement  Get Assets For Replacement;
    ServiceChannel.Services.Messaging.Assets.UpdateAssetRepairStatusRequest
  reason: Registry and lifecycle of physical equipment assets (meters, repair status, replacement, location
    trees) for a facilities-management platform — building/equipment asset management rather than financial
    fixed-asset accounting. Sub-capability split between hard and soft FM is not determinable.
- tag: WorkOrders
  spec_file: servicechannel-work-orders-api-openapi.yml
  reanchored_from: servicechannel-workorders-api-openapi.yml
  capability_id: BC-700
  capability_id_l1: BC-700
  capability_name: Facilities Management
  confidence: 0.75
  evidence: POST /workorders 'Create a Work order', 'Update a Work order Status', 'Change Work order Trade',
    'Add Work order Resolution'
  reason: 'Core facilities work-order lifecycle for multi-location sites: creation, status, priority,
    NTE, scheduled date, trade, resolution. Clearly Facilities Management; the trade-agnostic surface
    spans hard and soft FM so no L2 is asserted.'
- tag: PlannedMaintenance
  spec_file: servicechannel-plannedmaintenance-api-openapi.yml
  capability_id: BC-700.20
  capability_id_l1: BC-700
  capability_name: Hard Facilities Management
  confidence: 0.72
  evidence: GET /PlannedMaintenance/LocationPmSummary; schema 'PreventiveMaintenance.PlannedMaintenanceSummaryItemResponse'
  reason: Planned/preventive maintenance summaries and services by location are the scheduled upkeep of
    building systems and equipment, i.e. hard facilities management.
- tag: Providers
  spec_file: servicechannel-providers-api-openapi.yml
  capability_id: BC-510
  capability_id_l1: BC-510
  capability_name: Supplier Management
  confidence: 0.72
  evidence: POST /providers 'Create blank provider', POST /providers/{providerId}/feedback, 'Returns provider
    ranks for specified Fixxbook primary trade and locations'
  reason: Creates and maintains service-provider (contractor) records, captures feedback and ranking,
    and controls dispatch eligibility — supplier master data plus performance/relationship management.
    Spans multiple sub-capabilities so L1 only.
- tag: Rfps
  spec_file: servicechannel-rfps-api-openapi.yml
  capability_id: BC-500.10
  capability_id_l1: BC-500
  capability_name: Sourcing Management
  confidence: 0.72
  evidence: POST /rfps 'Create an RFP', PUT /rfps/{rfpId}/assign 'Assign an RFP to another provider'
  reason: Creating and routing requests for proposal to service providers is textbook RFx issuance within
    strategic sourcing/supplier selection.
- tag: WorkRequests
  spec_file: servicechannel-work-requests-api-openapi.yml
  reanchored_from: servicechannel-workrequests-api-openapi.yml
  capability_id: BC-700
  capability_id_l1: BC-700
  capability_name: Facilities Management
  confidence: 0.72
  evidence: POST /workrequests 'Creates a work request', 'Update a work request status', 'Reassign work
    request to another provider'
  reason: Lifecycle of facilities service requests raised against locations and dispatched to service
    providers — Facilities Management. No single L2 is named by the operations.
- tag: SingleSignOn
  spec_file: servicechannel-single-sign-on-api-openapi.yml
  reanchored_from: servicechannel-singlesignon-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.7
  evidence: POST /sso/clients/register; PUT /sso/clients/{clientIdentifier}/deactivate; RegisterSsoClientRequest
  reason: Lifecycle of single-sign-on client registrations (register, activate, deactivate, delete) is
    identity federation / access management. Some ambiguity whether these are tenant IdP clients or developer
    OAuth clients, so the generic IAM sub-capability is used.