Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This article explains how to integrate production orders from any ERP into RS Production using the Standard Integration PINT-205.

We also cover how to retrieve production data from these orders.

Table of Contents

What is the standard integration


The standard integration is a way to integrate production orders, production plan and articles from any system into RS Production. It's also a used to input information about the production from RS Production into a ERP-system.

Installation

The interface between RS Production and the ERP-system is made out of two predefined sql-tables (Microsoft SQL). RS Production read and write to these tables cyclically. In the following guide we talk a bit about how it works and where we need database tables and integrations services to be installed.

Guide to RS Production Standard ERP integration.pdf

The installation of the RS Integration service is preferably installed by technicians at Good Solutions. Thecreation of integration tables can be done by either side but it's important that the integration service can access the tables. It's also important that the tables are created by the provided sql-scripts. 

Integration

The integration consists out of two sql tables. We continually read and write from/to these tables.

How to work with the standard ERP-integration.pdf

Order table 

We read from the table and add all the information to RS Production.

Info

Some things to note

  • The rows can be updated and the change will be updated in RS Production automatically.
  • Removing rows are not recommended and we advice you not do it as it can cause a lot of trouble.
    • A removed row means that you can't ever change information on that order again.
    • It's harder to troubleshoot if the history is removed
    • If the same order is added again a new one will be created in RS Production and the customer will see two identical orders.
  • Some fields a mandatory and some are optional. (More information in How to work with the standard ERP-integration.pdf)
    • Optional
      • OperationNumber
        • If the same order is available on more than one machine an operation number may be handy
      • OrderedQuantity (0 if not applied)
      • OrderStatus
        •  The status of the order. We only have one status at the moment: 99
          99 means that the order is aborted and should not be visible to the operators anymore.    
      • PlannedStartDate
      • PlannedFinishedDate
      • Priority
        • Orders are sorted by this number in the Operator UI if available.

           
      • ReportNumber
        • When a report is created in RS Production this number will be added to that report when it’s saved to the database/sent back to the integrating ERP system.

      • ArticleInstruction
      • ArticleType
      • AllocatedSetupTime
      • OptimalCycleTime
        • The optimal cycle time is the time it should take for the machine to produce one unit * UnitFactor. This will override the settings made in RS Production. If it’s not provided we will use the settings in RS Production. If it's provided it will affect the calculation of stops in RS Production.
      • UnitFactor
        • Factor for calculating produced amount from number of captured machine cycles. If not provided 1 will be used as default. If it's provided it will affect the produced quantity in RS Production.

    • Mandatory
      • OrderNumber
      • PlanningGroup
        •  A planning group can be one or more machines that are able to produce this production order. The order will be visible in the production plan (where the machine operators start and stops orders) on all machines that belong to the planning group. A machine can belong to more than one planning group.   The mapping between planning groups and machines (which belongs to which) are done in RS Production.  In the case where orders are planned to a single machine in the ERP, fill this field with the machine name.
      • ArticleNumber
      • ArticleName

Report table

We write a new row to this table when the status of the production order is changed.

  • When the order is started.
  • (Optional) When the order is paused
    • (Optional) This report can contain information about produced quantities.
  • (Optional) When the order is resumed after a paused
  • When the order is finished
    • This is the only report to contain setup time and production time
  • (Optional) It possible to give the machine operators the ability to create a progress report that contains the produced quantity and an optional print flag.

For troubleshooting purposes it's appreciated if the Executed, ExecutionDate and ExecutionMessage fields are filled after retrieving/reading a report.
The Executed field should be filled when the ERP has retrieved the report.

Rows are not updated by RSP by default but if there has been a problem with a report it's possible for the customer to, for example, set Executed to false. This is done to trigger a reread of the report in the ERP.

Info

Some things to note

  • There are three fields that should be filled when reading a new report.
  • The rows can be updated by the ERP and the change will be updated in RS Production automatically.
  • Some fields ProductionTime and SetupTime are only filled when an order is marked as done in RS Production.
  • Rows are never deleted from the table. You could use the bool Executed to see if you should read it or not and then set it to true after reading it.


Information that will be visible to the machine operators

If the I button will only be visible if there is an article instruction and if it is clicked it will be displayed.

In the administrative UI the following information will be displayed.

 


Order number, Article number, Article name and Article type will be available in reports when analyzing data.

 


 


Some of the data in the ERPReports table will be provided by the operator but most will be calculated automatically by the system.