Differences

This shows you the differences between two versions of the page.

--- cli:franke:smartmom-integration [2023/10/26 17:59]
l.bravi [SmartMoM - Integration]
+++ cli:franke:smartmom-integration [2024/05/03 11:10] (current)
m.zingaretti [Attivare verso GEC]
@@ Line 20: / Line 20: @@
   * real takt time (calculated by the system if the related module will be activated)
-For any produced item and for any scrap item IMPROVE 4.0 can call the related REST POST API.
+For any produced item and for any scraped item IMPROVE 4.0 can call the related REST POST API.
 ===== IMPROVE 4.0 side: Machine status =====
-IMPROVE 4.0 can provide the following family of data in case of beginning of a stop machine:
+IMPROVE 4.0 can provide the following family of data when a machine stop starts:
   * work center
   * time of beginning of the stop machine
   * stop reason
-IMPROVE 4.0 can provide the following family of data in case of ending of a stop machine:
+ IMPROVE 4.0 can provide the following family of data when a machine stop ends:
   * work center
   * time of ending of the stop machine
@@ Line 34: / Line 34: @@
 Each event can be sent once is detected via REST POST API. \\ \\
 FIXME If an operator changes the stop information a posteriori how IMPROVE 4.0 can update the GEC platform ?
-===== Information MAPPING =====
+===== MAPPING Informations =====
 It is required to create a mapping between IMPROVE 4.0 dataset and GEC platform dataset, in particular for the following structures:
   * stop causes
   * work centers
-In both the cases IMPROVE 4.0 provides a page where the user can himself set this mapping.
+In both the cases IMPROVE 4.0 provides a page where the user can by himself set this mapping.
 ==== Stop Causes ====
-Using the related menù item it can be possible to access to the machine stop causes list: \\ \\
+Using the related menù it is possible to access to the machine stop causes list: \\ \\
 {{:cli:franke:pasted:20231025-164434.png?300}} \\ \\
-Opening the page of a specific machine stop cause, it can be possible to configure the GEC platform related code in the indicated field: \\ \\
+Opening the page of a specific machine stop cause, it is possible to configure the GEC platform related code in the indicated field: \\ \\
 {{:cli:franke:pasted:20231025-164447.png?1000}}
 ==== Work centers ====
-Using the related menù item it can be possible to access the work centers list: \\ \\
+Using the related menù it is  possible to access the work centers list: \\ \\
 {{:cli:franke:pasted:20231025-165054.png?300}} \\ \\
-Opening the page of a specific work center, it can be possible to configure the GEC platform related code in the indicated field: \\ \\
+Opening the page of a specific work center, it is possible to configure the GEC platform related code in the indicated field: \\ \\
 {{:cli:franke:pasted:20231025-165105.png?1000}} \\ \\
-For the case of work-center it is necessary to check if GEC platform will use the same code of the SAP system. In positive case no additional operation will be required since IMPROVE 4.0 is already configured for this scope. In negative case it will be necessary to add another field in the same page for mapping the GEC platform work centers codes.
+For the case of work-center it is necessary to check if GEC platform will use the same code of the SAP system. If YES, no additional operation will be required since IMPROVE 4.0 is already configured for this scope. If NOT, it will be necessary to add another field in the same page for mapping the GEC platform work centers codes.
 ===== Activities =====
 Activities will be divided as follows:
@@ Line 61: / Line 63: @@
   * Preparation of the software module for API #2, cloud testing and activation in production environment. \\ \\
+Some details about the API:
+  * [[.:franke:SmartMom-integration:api|SmartMoM - Integration API]]
+  * [[.:franke:SmartMom-integration:fmtonextapi|From GEC to Next]]
+===== Attivare verso GEC =====
+mandare i fermi e i prel verso agente babbo natale
+usare wip-dbparams touchgec nei parametri touch