slug: coperniq
provider: Coperniq
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Oil & Gas
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: 10
edges:
- tag: opportunities
  spec_file: coperniq-opportunities-api-openapi.yml
  capability_id: BC-410.30
  capability_id_l1: BC-410
  capability_name: Opportunity & Pipeline Management
  confidence: 0.9
  evidence: POST /opportunities  create-opportunity; schemas OpportunitySalesRep, OpportunityOwner, PhaseInstance
  reason: Full lifecycle of sales opportunities with sales rep, owner and pipeline phase is opportunity
    and pipeline management.
- tag: invoices
  spec_file: coperniq-invoices-api-openapi.yml
  capability_id: BC-200.30
  capability_id_l1: BC-200
  capability_name: Accounts Receivable Management
  confidence: 0.85
  evidence: POST /invoices  create-invoice; schemas InvoiceLineItemCreate, InvoiceAccount, InvoiceStatus,
    GetAccountInvoicesRequestUnauthorizedError
  reason: Creation and lifecycle of customer invoices tied to accounts and projects is accounts receivable
    / customer invoicing.
- tag: quotes
  spec_file: coperniq-quotes-api-openapi.yml
  capability_id: BC-410.40
  capability_id_l1: BC-410
  capability_name: Quote & Configuration Management
  confidence: 0.85
  evidence: POST /quotes create-quote; GET /quotes/{quoteId}/pdf get-quote-pdf; POST /quotes/{quoteId}/send
    send-quote; schemas QuoteLineItemCreate, QuoteDiscountType, QuoteSection
  reason: Operations create, price (line items, discount type), render and send customer quotes tied to
    opportunities — classic configure/price/quote surface in the lead-to-order flow.
- tag: contacts
  spec_file: coperniq-contacts-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.8
  evidence: GET /contacts  list-contacts; schemas ContactCreate, ContactAccountsItems, ContactProjectsItems
  reason: CRUD over contact master records linked to accounts and projects is customer/contact data management
    in the vendor's contractor CRM.
- tag: payments
  spec_file: coperniq-payments-api-openapi.yml
  capability_id: BC-200
  capability_id_l1: BC-200
  capability_name: Financial Management
  confidence: 0.8
  evidence: POST /invoices/{invoiceId}/payments  create-invoice-payment; POST /bills/{billId}/payments  create-bill-payment
  reason: Records payments against both customer invoices and supplier bills, spanning receivables cash
    application and payables disbursement, so the L1 Financial Management level is the accurate mapping.
- tag: accounts
  spec_file: coperniq-accounts-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: GET /accounts list-accounts 'List Accounts'; POST /accounts 'Create Account'; schemas AccountContactsItems,
    AccountAccountType, AccountUpdate
  reason: CRUD plus search over customer/account records with associated contacts and account types in
    a contractor CRM/operations platform — this is customer account master data maintenance. Some ambiguity
    between Customer Data Management and Sales Account Management, so confidence is held at 0.7.
- tag: projects
  spec_file: coperniq-projects-api-openapi.yml
  capability_id: BC-900.30
  capability_id_l1: BC-900
  capability_name: Project Management
  confidence: 0.7
  evidence: POST /projects create-project Create Project; schema ProjectWithPhaseInstancesPhaseSlaStatus,
    ProjectStage
  reason: Coperniq is a contractor operating system 'consolidating sales, project management, service
    operations'; this tag is CRUD over project records with stages, phases and SLA status — i.e. execution
    tracking of delivery projects, mapping to cross-industry Project Management. Not an oil & gas subsurface
    or drilling programme, so no industry capability applies.
- tag: users
  spec_file: coperniq-users-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.7
  evidence: POST /users invite-user Invite User; GET /roles list-roles; GET /teams list-teams; schemas
    UserRole, TeamMemberRole
  reason: Application user provisioning via invitation plus role and team enumeration is access administration
    for the platform, not HR employee records; maps to Identity & Access Management.
- tag: vendors
  spec_file: coperniq-vendors-api-openapi.yml
  capability_id: BC-510
  capability_id_l1: BC-510
  capability_name: Supplier Management
  confidence: 0.7
  evidence: POST /vendors create-vendor; POST /projects/{projectId}/vendors/{vendorId} Create Vendor-Project
    Link; VendorCreateVendorType
  reason: Maintains a supplier/subcontractor register and links vendors to projects — supplier master
    and relationship management for the contractor.
  recovered_from: vertical-power-water-utilities-edges.json
- tag: workOrders
  spec_file: coperniq-work-orders-api-openapi.yml
  capability_id: BC-1150.30
  capability_id_l1: BC-1150
  capability_name: Construction Supervision Management
  confidence: 0.7
  evidence: POST /projects/{projectId}/work-orders Create Project Work Order; WorkOrderVisits; WorkOrderTemplateLineItemsItems
  reason: Work orders with scheduled visits and line items created against projects/accounts for trade
    contractors is field/site work execution — construction supervision and day-to-day site work management.
    Sub-capability choice is somewhat uncertain (could be service dispatch), hence moderate confidence.
  recovered_from: vertical-engineering-services-edges.json
  reanchored_from: coperniq-workorders-api-openapi.yml