Connectivity and automation

ERP Integration

Scope the exchange of agreed records and results between existing ERP systems and Divera applications.

Request a site assessment How does it work?

Overview

The need it addresses

ERP Connection is positioned to share necessary information between the business's existing commercial system and Divera applications. It is not a new ERP in itself; it is a connection service that links the record of the existing ERP with the record of the application on the shop floor.

How does it work?

In the first stage, the information to be shared is selected, such as customer, product, material, work order, order, stock status or production result. The primary system is determined for each record. For example, while the work order is created in the ERP, the actual production can be recorded in Divera. The completed quantity is reported to the ERP through an approved flow. Sharing all information in both directions is not necessary in every project.

The connection deals with situations such as the same transaction being transferred again, a missing record, a wrong match and later correction. A connection error is not hidden from the user; which record was not transferred and what needs to be done is tracked. Whether data transfer will be live, at set intervals or with user approval is chosen according to the business need.

Existing infrastructure and data

Inputs

Needs discussion: The problem, users, priority and examples of existing records
Site and infrastructure assessment: Relevant owners, process access and permitted data samples
Scope and plan: Priorities and implementation limits
Installation and adaptation: Verified starting data and authorized people
Validation and training: Users applying sample jobs
Go-live and support: A usage owner and support contact

Scope conditions

The scope, deliverables, assumptions and plan are written in the scope and plan step; responsibility and acceptance conditions are determined together.

Price, warranty and service periods are confirmed separately; this page does not define a finished standard package.

Example use

In a business that uses Harmony ERP, the aim may be to bring the relevant work order to the Divera production screen and to report production results back. For which information this will be provided is clarified after examining the ERP version in use, access permissions and the available connection options. The existence of an ERP connection does not mean that all brands and versions are ready with the same scope.

Steps

Needs discussion: Clarifying the business question and the success criterion
Site and infrastructure assessment: Assessing the workflow, software, machines and data sources
Scope and plan: Writing down the product/service selection, responsibilities and acceptance conditions
Installation and adaptation: Preparing content, data transfer and the specified connections
Validation and training: Trying opening, correction, approval and closure together
Go-live and support: Monitoring use, handling problems and planning expansion

Outputs

Needs discussion: Preliminary needs summary
Site and infrastructure assessment: Assessment notes, data and connection list
Scope and plan: Scope, deliverables, assumptions and plan
Installation and adaptation: Starting environment, applied
Validation and training: Acceptance records and task-based training
Go-live and support: Support arrangement and improvement list

Suitable industries

Businesses that continue to use their existing ERP while wanting to detail production, maintenance, quality, assembly or field processes.

Frequently asked questions

Which of our business questions determines the starting scope?

In the first meeting we determine which question your business is looking to answer. We assess your process and existing infrastructure to define the starting scope.

Discuss your project

Request a site assessment Contact