Connects to your stack. No rip-and-replace.
ServiceCPQ augments the systems your business already runs — ERP, PLM, CRM, telematics and dealer management. A live data fabric keeps the knowledge graph current and pushes approved actions back into your systems of record.
Three layers under every module.
Every ServiceCPQ module — warranty, parts, CPQ, field service, asset health — runs on the same three-layer foundation. That’s why adopting one module makes the next one faster to deploy.
Your products, variants, installed base, parts, contracts and service history modelled as one connected graph — the single source of truth every module reasons over. Seeded from ERP and PLM at onboarding; updated continuously by every transaction.
Task-specific AI agents for diagnosis, adjudication, configuration and quoting — grounded in the graph and your policies. Humans stay on exceptions; agents handle volume.
Live connectors to ERP, PLM, CRM, telematics, dealer management and parts catalog keep the model current and push approved actions — quotes, requisitions, settlements — back into your systems of record.
What connecting ServiceCPQ actually looks like.
Six systems. Pre-built connectors for all of them.
Standard connectors cover the systems every machinery manufacturer runs. Each is bidirectional — ServiceCPQ reads what it needs and writes back what your systems of record need to stay current.
Bidirectional: ServiceCPQ reads stock, costs, BOM and contracts. Writes back parts requisitions, work orders, billing documents and warranty settlements — no manual re-entry.
Product structure, variant rules and BOM data sourced from your PLM master. Config rules in ServiceCPQ stay in sync with product engineering without a separate data team.
Installed base and service history enriches CRM opportunity records. Quotes generated in ServiceCPQ push back to CRM as activities — the sales team works one system.
REST, MQTT or event-stream ingestion from any OEM platform, AWS IoT, Azure IoT Hub or custom telemetry source. Fault codes and asset signals route into the alert monetisation layer automatically.
Dealer-submitted warranty claims, parts orders and service records flow through the DMS connector — dealers work their native system; ServiceCPQ processes the data.
OEM parts catalog, supersession tables and cost structures loaded and kept current. Multi-tier dealer pricing enforced at quote time without manual price-list management.
Enterprise-ready from day one.
Data encrypted in transit (TLS 1.3) and at rest (AES-256). Residency configurable by region — EU, US, APAC — to meet local compliance requirements.
Integrates with your existing identity provider. Granular roles control what each user, dealer or partner can see and do — down to field level.
Every configuration, quote, claim and approval is logged with user, timestamp and change — so compliance and dispute resolution have a complete record.
Every AI agent action has configurable approval thresholds. High-value claims, large quotes and sensitive decisions require human review before execution.
Frequently asked questions
No. ServiceCPQ augments your ERP — reading the data it holds (stock, BOM, cost, contracts) and writing approved actions back (parts requisitions, work orders, warranty settlements, billing documents). Your ERP of record stays in place; ServiceCPQ removes the workflow that never belonged there.
Standard ERP connectors (SAP S/4HANA, Oracle EBS, Dynamics 365) are pre-built — the first connection typically completes in under a day of technical setup. Full data mapping and knowledge-graph seeding for a single product line takes two to four weeks depending on catalog size.
The integration fabric accepts REST, MQTT, AMQP and event-stream protocols. For proprietary formats, a lightweight normalisation adapter is built during onboarding — most OEM telemetry platforms can be connected within the first implementation phase.
Yes. Dealers work through ServiceCPQ's portal layer and DMS connector — they submit claims, orders and service records through their own interface, and the data flows into the knowledge graph without giving dealers access to your ERP.
Connectors are versioned and tested against each supported ERP and PLM release. When SAP or Oracle releases a new version, the connector is updated before customers need to upgrade — so integration stability isn't something your team carries.