slug: simpro provider: Simpro generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Manufacturing & Industrial - 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: 8 edges: - tag: Customers spec_file: simpro-customers-api-openapi.yml capability_id: BC-420.10 capability_id_l1: BC-420 capability_name: Customer Data Management confidence: 0.85 evidence: POST /companies/{companyID}/customers/companies/ createCompanyCustomer Create a company customer; POST /companies/{companyID}/customers/individuals/ createIndividualCustomer reason: Full CRUD over company and individual customer master records (CustomerInput/CustomerListItem) — customer data mastering within the field service platform. - tag: Quotes spec_file: simpro-quotes-api-openapi.yml capability_id: BC-410.40 capability_id_l1: BC-410 capability_name: Quote & Configuration Management confidence: 0.85 evidence: POST /companies/{companyID}/quotes/ createQuote Create a quote reason: Quote lifecycle CRUD matching the vendor's 'estimating, quoting' workflow — Quote & Configuration Management within sales. - tag: Vendor Orders spec_file: simpro-vendor-orders-api-openapi.yml capability_id: BC-500.30 capability_id_l1: BC-500 capability_name: Purchase Order Management confidence: 0.85 evidence: POST /companies/{companyID}/vendorOrders/ createVendorOrder "Create a vendor order"; vendor scope includes "purchasing" reason: Vendor orders are purchase orders raised to suppliers; create/update/delete lifecycle maps to Purchase Order Management. - tag: Invoices spec_file: simpro-invoices-api-openapi.yml capability_id: BC-200.30 capability_id_l1: BC-200 capability_name: Accounts Receivable Management confidence: 0.8 evidence: POST /companies/{companyID}/invoices/ "Create an invoice"; schema InvoiceInput reason: Customer invoicing in a field-service platform whose workflow ends in "invoicing" — accounts receivable / customer invoicing. - tag: Jobs spec_file: simpro-jobs-api-openapi.yml capability_id: BC-1050 capability_id_l1: BC-1050 capability_name: Field Service Management confidence: 0.75 evidence: '"Create a job", "Update a job" in a platform covering "estimating, quoting, job management, scheduling and dispatch, asset maintenance"' reason: Jobs are the field-service work records for trade contractors, so Field Service Management is the right L1; the CRUD surface alone does not distinguish request capture, dispatch, or execution, so no L2. - tag: Stock spec_file: simpro-stock-api-openapi.yml capability_id: BC-530 capability_id_l1: BC-530 capability_name: Inventory Management confidence: 0.75 evidence: GET /companies/{companyID}/storageDevices/{storageDeviceID}/stock/ listStock List stock on a storage device reason: Read-only visibility of stock quantities held on storage devices/locations, i.e. inventory on hand within the vendor's 'inventory and catalog' workflow. Maps to Inventory Management at L1; the thin read-only surface does not clearly name a sub-capability (stock levels vs. accuracy vs. allocation). - tag: Cost Centers spec_file: simpro-cost-centers-api-openapi.yml capability_id: BC-200.50 capability_id_l1: BC-200 capability_name: Cost Accounting Management confidence: 0.7 evidence: GET /companies/{companyID}/setup/accounts/costCenters/ listCostCenters List all cost centers reason: CRUD over cost centres under the accounts setup area — maintenance of cost objects used for cost allocation, i.e. Cost Accounting Management. Thin surface (setup master data only) so moderate confidence. - tag: Schedules spec_file: simpro-schedules-api-openapi.yml capability_id: BC-1050.20 capability_id_l1: BC-1050 capability_name: Service Dispatch Management confidence: 0.7 evidence: GET /companies/{companyID}/schedules/ listSchedules "List all schedules"; vendor covers "scheduling and dispatch" for trades contractors reason: Schedules in this field-service platform represent technician job scheduling/dispatch records; read-only surface so sub-capability inferred from vendor scope, hence moderate confidence.