Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
cli:franke:smartmom-integration [2023/10/25 16:58] n.bergantino [Stop Causes] |
cli:franke:smartmom-integration [2024/05/03 11:10] (current) m.zingaretti [Attivare verso GEC] |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| * one REST POST for retrieving data related to Machine Statuses. | * one REST POST for retrieving data related to Machine Statuses. | ||
| Details and documentation related to the parameters (both mandatory and non-mandatory) that will be transmitted via these APIa have already been discussed in a preliminary meeting between the parties, where German Edge Cloud made itself available for any future interactions that may facilitate the NeXT team with the integration process. \\ \\ | Details and documentation related to the parameters (both mandatory and non-mandatory) that will be transmitted via these APIa have already been discussed in a preliminary meeting between the parties, where German Edge Cloud made itself available for any future interactions that may facilitate the NeXT team with the integration process. \\ \\ | ||
| - | {{: | + | {{: |
| + | 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: | ||
| + | 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 side: Work Order Status ===== | ||
| IMPROVE 4.0 can provide the following family of data: | IMPROVE 4.0 can provide the following family of data: | ||
| Line 17: | Line 20: | ||
| * real takt time (calculated by the system if the related module will be activated) | * 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 |
| ===== IMPROVE 4.0 side: Machine status ===== | ===== 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 |
| * work center | * work center | ||
| * time of beginning of the stop machine | * time of beginning of the stop machine | ||
| * stop reason | * 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 |
| * work center | * work center | ||
| * time of ending of the stop machine | * time of ending of the stop machine | ||
| Line 31: | Line 34: | ||
| Each event can be sent once is detected via REST POST API. \\ \\ | 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 ? | FIXME If an operator changes the stop information a posteriori how IMPROVE 4.0 can update the GEC platform ? | ||
| - | ===== Information | + | |
| + | ===== MAPPING | ||
| It is required to create a mapping between IMPROVE 4.0 dataset and GEC platform dataset, in particular for the following structures: | It is required to create a mapping between IMPROVE 4.0 dataset and GEC platform dataset, in particular for the following structures: | ||
| * stop causes | * stop causes | ||
| * work centers | * 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 ==== | ==== 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: \\ \\ |
| {{: | {{: | ||
| - | 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: \\ \\ |
| {{: | {{: | ||
| ==== Work centers ==== | ==== Work centers ==== | ||
| - | Using the related menù item it can be possible to access the work centers list: \\ \\ | + | Using the related menù it is |
| {{: | {{: | ||
| - | 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: \\ \\ |
| {{: | {{: | ||
| - | For the case of work-center it is necessary to check if GEC platform will use the same code of the SAP system. | + | For the case of work-center it is necessary to check if GEC platform will use the same code of the SAP system. |
| ===== Activities ===== | ===== Activities ===== | ||
| Activities will be divided as follows: | 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; | * 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 | + | * Support to the users for mapping |
| * Preparation of the software module for API #1, cloud testing and activation in production environment; | * 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. \\ \\ | * Preparation of the software module for API #2, cloud testing and activation in production environment. \\ \\ | ||
| + | Some details about the API: | ||
| + | * [[.: | ||
| + | * [[.: | ||
| + | |||
| + | ===== Attivare verso GEC ===== | ||
| + | |||
| + | mandare i fermi e i prel verso agente babbo natale | ||
| + | |||
| + | usare wip-dbparams touchgec nei parametri touch | ||