General Kinematics: Salesforce–Infor SyteLine Integration with Duet360
Updated: 4 days ago
General Kinematics connected Salesforce and Infor SyteLine (CSI) through Duet360 by Endowance Solutions, giving teams a shared view of sales and ERP information.
This implementation story draws on Endowance’s original customer study and Jitterbit’s partner case study. Historical project details are distinguished from the planning guidance below.
The implementation at a glance
Customer: General Kinematics, a heavy-equipment manufacturer headquartered in Crystal Lake, Illinois.
Documented environment: Salesforce Sales Cloud, Partner Communities, Pardot, and Duet360 for Infor SyteLine (CSI).
Project duration: 10 weeks in Endowance’s customer study. Jitterbit describes delivery in under 10 weeks.
Integration foundation: Jitterbit’s account describes Harmony implemented as part of Duet360.
The problem: customer information was difficult to use
GK needed dependable customer information across a growing global business. An earlier integration effort had not delivered the required connectivity. Jitterbit reports that invoices, opportunities, and estimates were unavailable in the mobile experience; limited IT capacity made recovery difficult.
What Endowance delivered
Endowance reviewed requirements, obtained design approval, and deployed the integration. Its customer study describes near-real-time access to opportunities, quotes, orders, shipments, invoices, and receivables. Marketing and partner processes also gained a more useful view of customer activity.
The diagram summarizes published business information flows. It does not specify deployment topology, access controls, or every configured interface.
Results reported by the customer and partner
Global reporting: information previously assembled manually became available in Salesforce; a person dedicated to collecting and reporting it could focus on other work.
Sales adoption and mobility: Jitterbit reports greater Salesforce adoption and mobile access to opportunities, receivables, invoices, and estimates.
Marketing: Jitterbit describes campaign analysis and segmentation by product, industry, and geography.
“We could see what opportunities each sales executive was working around the world.”
— Jim Egan, identified in Endowance’s customer study as Vice President of North America Sales and Marketing.
These are historical, project-specific observations. The sources do not provide a controlled ROI study or current performance measurements. The documented ten-week project is separate from today’s scoped onboarding offers.
A short walkthrough: use the connected information
For an evaluation session, start with an account in Salesforce and trace the ERP information a salesperson needs to answer a customer. Ask to see the related order, shipment, invoice, and receivable context; then identify which system owns each value. This is a proposed demonstration agenda based on the reported use case, rather than a recording of GK’s production environment.
Watch Jim Egan’s customer testimonial on Jitterbit’s website. The partner resource is dated March 20, 2019.
Five questions to evaluate Duet360 for your business
1. Flexibility: what is prebuilt, configured, or custom?
Duet360’s current offering uses prebuilt processes and reusable mappings. Company/site relationships, business rules, validations, and exception handling are scoped around the customer environment. Agree a written fit-gap list: included package behavior, configuration choices, and requirements needing additional design or development.
Review Salesforce–Infor integration scope. Ask for a demonstration using your ERP release and representative transactions.
2. Data ownership and an orderly service exit
Endowance’s published MSA states that clients retain ownership of Client Data. Section 7.6 makes export after termination conditional on a written request before deletion and available export functionality. It is not an unconditional portability guarantee. Before signing, document export formats, retention timing, transition assistance, costs, and the handover materials available for your environment.
Read the MSA, especially sections 7.1, 7.6, 11.4, and 13. The applicable signed agreement and Order govern your engagement.
3. Enterprise trust: verify controls and operating responsibilities
MSA section 6 describes security safeguards, incident handling, and encryption with stated qualifications. Clients remain responsible for their systems, credentials, API policies, and endpoints. Specific service levels apply only when stated in the relevant Order or incorporated policy.
Request an architecture and responsibility review covering authentication, permissions, secrets, data paths, logging, incident escalation, and recovery. Obtain the evidence needed by your security team; a customer story or marketplace listing does not establish a security certification.
4. Platform fit: understand the role of each platform
GK is a concrete example of Duet360 delivered with an integration-platform foundation: Jitterbit’s case study identifies Harmony as part of the solution. That does not establish that every Duet360 deployment requires the same architecture or supports a specific MuleSoft or Boomi coexistence design.
If another integration platform is already in use, agree which platform owns each flow, credential, mapping, retry, and support escalation. Avoid overlapping writers for the same record. Request a proposed architecture and verify licensing and operational ownership before implementation.
5. Manufacturing fit: test the process you actually run
Use this story as evidence for a named manufacturer and documented systems. For your own evaluation, select one important workflow and agree its success criteria. A useful first scope might be order-status visibility, a quote handoff, or customer reporting; test it with the actual companies, sites, products, and exceptions involved.
Your Salesforce–SyteLine planning checklist
Identify the Infor release, deployment model, Salesforce products, companies, sites, and available interfaces.
List required records and fields; assign a system of record and a business owner to each.
Choose the first workflow and define what users should see or do at each handoff.
Agree update timing and what should happen when an identifier is missing, a service is unavailable, or a duplicate arrives.
Define acceptance tests, reconciliation, error ownership, and reprocessing procedures.
Record security requirements, monitoring, escalation, support coverage, documentation, and exit arrangements.
Measure current manual effort and transaction volumes so you can compare the same process after launch.
Discuss your Salesforce–SyteLine integration
Tell us your ERP product and version, Salesforce setup, and the workflow you want to improve. Include the teams involved, any existing integration platform, and the manual work you want to remove. We can use those details to discuss fit, scope, and a relevant demonstration.
In the contact form’s message field, include your ERP/version and target workflow so the conversation starts with your environment.
Comments