CRM-ERP Integration via Technical Place Object

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Coordination between Customer Resource Management (CRM) and Enterprise Resource Management (ERP) systems is lacking, leading to incomplete information sharing, which hampers effective service management and communication of maintenance issues in facilities or equipment, resulting in inaccurate status updates for customers.

Innovation Solution

A technical place object is provided to the CRM system containing information from the ERP system, including layout, equipment, and service information, enabling the CRM to generate a service object that integrates with service requests, and updates are made based on responses from the ERP system to ensure accurate and efficient service management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If CRM system operates independently without ERP system integration, then CRM system complexity is reduced, but information completeness and service accuracy deteriorate

Engineering Contradiction:
ImproveCRM system complexityVSAvoidfacility information completeness
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The patent implements an intermediary integration layer that mediates between the CRM and ERP systems. This layer includes components such as an ERP adapter, data synchronization service, and object model translator that enable information exchange without requiring direct complex integration between the two systems. The intermediary handles data transformation, mapping facility information from ERP to CRM format, and managing the integration complexity centrally rather than within each system.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If CRM system integrates with ERP system, then information completeness improves, but system complexity increases

Engineering Contradiction:
Improvefacility information completenessVSAvoidsystem integration complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The integration architecture is segmented into distinct functional modules: an ERP adapter module that connects to the ERP system, a data synchronization service module that manages data exchange, an object model translator module that converts data formats, and a CRM interface module that presents integrated information to users. This segmentation allows each module to handle specific integration tasks independently, reducing overall system complexity while maintaining complete information flow.

Inventive Principle:
Principle #1Segmentation

3Measurement precision

If real-time data synchronization is implemented between CRM and ERP, then service status accuracy improves, but data processing time increases

Engineering Contradiction:
Improveservice status accuracyVSAvoiddata processing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system implements periodic data synchronization cycles rather than continuous real-time synchronization. The data synchronization service operates at scheduled intervals to update facility information, service status, and work order data between CRM and ERP systems. This periodic approach maintains sufficiently accurate service status information while significantly reducing the time and computational resources required for data processing compared to continuous real-time synchronization.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS7870561B2Technical place servicing integration
Publication Date: 2011.01.11 SAP SE
  • US7870561B2 patent drawing
  • US7870561B2 patent drawing
  • US7870561B2 patent drawing

AI summary

A method includes providing a technical place object to a Customer Resource Management (CRM) system wherein the technical place object includes information from an Enterprise Resource Management (ERP) system about a technical place including information associated with servicing the technical place. A service object may be provided to the ERP system wherein the service object includes information from the CRM system including information based on the technical place object and a service request associated with the servicing of the technical place. The CRM system may be provided an update of the service object wherein the update is based on a response to the service object by the ERP system.