Differences

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

--- cli:franke:smartmom-integration [2023/10/25 17:08]
n.bergantino [SmartMoM - Integration]
+++ cli:franke:smartmom-integration [2024/05/03 11:10] (current)
m.zingaretti [Attivare verso GEC]
@@ Line 10: / Line 10: @@
 It has been agreed that data will be exchanged on an event-by-event basis to enable the server to receive, in near real time, information regarding orders and machine status. \\ \\
 A cloud-based server will be provided that can enable appropriate testing activities to be performed in parallel with developments: the estimated timing includes, in addition to and prior to the aforementioned software development and testing activities, the entire process of analyzing the documentation mentioned above, preparatory to the data mapping required for proper communication between the two systems, and the implementation of the mapping itself for all required parameters. \\ \\
-In the following paragraphs the IMPROVE 4.0 available data are defined. For any additional required data it will be necessary to evaluate if they are available or not in the IMPROVE 4.0 platform.
+In the following paragraphs are specified the data available in Improve 4.0. For any additional required data it will be necessary to evaluate if they are stored or not in the IMPROVE 4.0 platform.
 ===== IMPROVE 4.0 side: Work Order Status =====
 IMPROVE 4.0 can provide the following family of data:
@@ 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:
   * Credential retrieval to obtain the token for access to the provided API, study and test of the provided APIs, implementation of the interface (middleware) for sending data to    the server;
-  * Mapping out causes of downtime/scraps currently set in the NeXT system for FIP according to the nomenclature of the German Edge Cloud system;
+  * Support to the users for mapping out causes of downtime currently set in the NeXT system for FIP according to the nomenclature of the German Edge Cloud system;
   * Preparation of the software module for API #1, cloud testing and activation in production environment;
   * 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