Miguel
/
Obsidean_VM
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Obsidean_VM/03-VM/45 - HENKEL - VM Auto Chang.../Emails.md

2626 lines
128 KiB
Markdown
Raw Permalink Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Índice de Mensajes
- 22-07-2025 - Miguel Angel Vera - Vetromeccanica Srl - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#Max - Alpla-Henkel - AutoChange|Max---Alpla-Henkel---AutoChange]]
- 15-07-2025 - Sam.Colley - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#RE: [EXT] FW: Automatic changeover trial -|RE-EXT-FW-Automatic-changeover-trial--]]
- 06-03-2025 - Sam.Colley - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#Alpla BOW2 Automated changeover next steps|Alpla-BOW2-Automated-changeover-next-steps]]
- 20-02-2025 - Lenin Vera - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#RE: EXT Next + 1 - HENKEL - ALPLA - AUTEFA|RE-EXT-Next-1---HENKEL---ALPLA---AUTEFA]]
- 04-02-2025 - Maximilian Rossi - Vetromeccanica Srl - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#I: R: I: [EXT] R: Vetro Conveyor 9.3674|I-R-I-EXT-R-Vetro-Conveyor-93674]]
- 04-02-2025 - Miguel Angel Vera - Vetromeccanica Srl - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#Next + 1 - HENKEL - ALPLA - AUTEFA|Next-1---HENKEL---ALPLA---AUTEFA]]
- 04-02-2025 - Maximilian Rossi - Vetromeccanica Srl - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#R: [EXT] RE: Vetro/ALPLA information verification 9.3060-3067|R-EXT-RE-VetroALPLA-information-verification-93060-3067]]
- 03-02-2025 - Miguel Angel Vera - Vetromeccanica Srl - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#NEXT2 - Data - ALPLA information verification|NEXT2---Data---ALPLA-information-verification]]
- 31-01-2025 - Shannon.Johnson - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#Automatic changeover trial|Automatic-changeover-trial]]
- 19-12-2024 - L&E - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#Re: [EXT] RE: Vetro/ALPLA information verification|Re-EXT-RE-VetroALPLA-information-verification]]
- 04-01-2024 - Maximilian Rossi - Vetromeccanica Srl - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#I: 9.3061-TLO26-L42 automatic change over test|I-93061-TLO26-L42-automatic-change-over-test]]
- 04-01-2024 - Maximilian Rossi - Vetromeccanica Srl - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#I: Alpla BOW: Batch handling 9.3040-3074 ALPLA BG|I-Alpla-BOW-Batch-handling-93040-3074-ALPLA-BG]]
- 04-01-2024 - Maximilian Rossi - Vetromeccanica Srl - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#I: Alpla BOW: Batch Handling Issue for TG10 & TG20|I-Alpla-BOW-Batch-Handling-Issue-for-TG10-TG20]]
- 04-01-2024 - Maximilian Rossi - Vetromeccanica Srl - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#I: Bottle counters / Batch handling|I-Bottle-counters-Batch-handling]]
- 04-01-2024 - Maximilian Rossi - Vetromeccanica Srl - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#I: OPC-UA interface Vetro - Bowling Green 2|I-OPC-UA-interface-Vetro---Bowling-Green-2]]
- 29-10-2020 - Maximilian Rossi - Vetromeccanica Srl - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#R: 9.3040-3074 ALPLA data exchange with HENKEL - line commisioning|R-93040-3074-ALPLA-data-exchange-with-HENKEL---line-commisioning]]
- 28-10-2020 - Sam.Colley@alpla.com - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#FW: Post Operations Meeting Logistics Update - 10/28/2020|FW-Post-Operations-Meeting-Logistics-Update---10282020]]
- 21-05-2020 - Maximilian Rossi - Vetromeccanica Srl - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#R: Alpla - Vetro SKU via OPC 9.3040-3074|R-Alpla---Vetro-SKU-via-OPC-93040-3074]]
- 24-02-2020 - Osswald Ulrich (ASG) (Ulrich.Osswald@autefa.com) - [[03-VM/45 - HENKEL - VM Auto Changeover/Emails#Alpla BG: updated telegram description|Alpla-BG-updated-telegram-description]]
---
+ 44c2f4a4e9f50385b7f8968d55d4241a
### Max - Alpla-Henkel - AutoChange
- 22-07-2025
________________________________________________________________________________
Microsoft Teams
¿Necesita ayuda?
Unirse
a la reunión ahora
Id. de reunión:
325 023 227 109 6
Código de acceso:
nt98HN63
Para organizadores:
Opciones
de la reunión
________________________________________________________________________________
---
+ a0dbf41b0300470ad03a1c48552578eb
### RE: [EXT] FW: Automatic changeover trial -
- 15-07-2025
Hi all,
We have made arrangements for the site pre-evaluation for the automatic changeover function of the Autefa and Vetro systems.
The plan is to use the current scheduled downtime on line 41 on the July 30th and 31st.
@John Sledge Could you please have lots made on the line for those dates so
we can cycle through the changeovers for the trial? I believe William may have already mentioned this?
@Robert Nation@Brandon
B Miller Once Lenin and Sudheesh are set up and ready I will reach out to you for support as we need it.
This is not the final implementation, we’re just trialing the current system to confirm what needs to be done.
Please let me know if you have any questions,
Best regards
Samuel Colley
ALPLA Inc
377 Southwood Ct
42101 Bowling Green, KY USA
M: +1 / 270 / 392 9932
www.alpla.com
_______________________________________________________________
***
Subject: RE: [EXT] FW: Automatic changeover trial
Sounds like a plan!
***
Subject: RE: [EXT] FW: Automatic changeover trial
Hi Daniel,
We’ve now locked this in with Vetro for w/c 7/28.
I’m working with our logistics manager and John Sledge to get the dummy batch’s made so we can perform the testing
I’ll arrange a meeting for the week before so we’re all clear on the desired outcome of the trials.
Please let me know if you need any more information.
Thanks
Best regards
Samuel Colley
ALPLA Inc
377 Southwood Ct
42101 Bowling Green, KY USA
M: +1 / 270 / 392 9932
www.alpla.com
_______________________________________________________________
***
Subject: RE: [EXT] FW: Automatic changeover trial
I will be off for about a week and a half starting the 15th however any other time I should be able to help
***
Subject: [EXT] FW: Automatic changeover trial
Hi both,
Just checking if you’d had chance to look at this?
Thank you,
Best regards
Samuel Colley
ALPLA Inc
377 Southwood Ct
42101 Bowling Green, KY USA
M: +1 / 270 / 392 9932
www.alpla.com
_______________________________________________________________
***
Subject: Automatic changeover trial
Hi Daniel, Hi Brandon,
Vetro want to schedule some time to come on site to do a pre evaluation of the auto changeover/batch handling.
They’ve requested we have a line available for a few days which they can test with.
They would need the line to have a number of dummy lots that they could cycle the change overs through.
These lot’s would have to come from Henkel as if we are simulating real changeovers.
Is this something which is feasible from your end?
If so I can look at the schedule and see which lines are down in the coming weeks.
Thanks
Best regards
Samuel Colley
ALPLA Inc
377 Southwood Ct
42101 Bowling Green, KY USA
M: +1 / 270 / 392 9932
www.alpla.com
_______________________________________________________________
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
---
+ 444a9733c3be75a66f442c03b64e4310
### Alpla BOW2 Automated changeover next steps
- 06-03-2025
Hi Max, Hi Mirco, Hi Miguel
Hope I find you all well.
As you know with Lenins’ support we did some trials on the auto handling/changeover system.
From those trials we’ve seen that the system is more labor intensive than we need.
We need to automate the changeover further than it currently is, bringing the operator interventions to a minimum.
I’d like to organize a meeting on the 18th March to discuss how far we can automate the current system and the effort needed to make it happen.
Please let me know if this date works for you and I will send an invite accordingly.
Thankyou,
Best regards
Samuel Colley
ALPLA Inc
377 Southwood Ct
42101 Bowling Green, KY USA
M: +1 / 270 / 392 9932
www.alpla.com
_______________________________________________________________
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
---
+ 82d5b0bd5ce95f99b9be3585b8f337c5
### RE: EXT Next + 1 - HENKEL - ALPLA - AUTEFA
- 20-02-2025
Hello everyone,
Yesterday the test was carried out for the automatic changeover on the TLO25/L41 line, during this time no problems were presented by Vetromeccanica, the modification made worked without problems (good job Miguel), Sudheesh (AUTEFA) asked me for a small
modification so that, when a line is worked through the backup (TLO24 - TLO28), the error of a line not selected in his panel is omitted, I attach the FBs and the programming lines that were modified, this change was also copied to the backup PLC.
Yesterday afternoon we had a meeting with Shannon, Thomas, Sarah and Sam. From there I was able to capture Shannon's interest in the following points:
He asked if it is possible that when the counting of bottles to be sent to Henkel is finished (during automatic changeover), we can bypass the upstream backup signals from the bottle turners and merges, to avoid the operator having to manually activate
the sensors or remove the bottles.
I talked with Sam about the additional rejectors on the lines besides those from Vetromeccanica. ALPLA has a camera that monitors the caps on the bottles and whether the bottle is inverted, and at Henkel there is a label inspector at the exit of each labeler.
These rejectors do not reach our PLCs, so we cannot recalculate the bottles that must be sent to Henkel. ALPLA wondered at the meeting why the counts were not exact. I think they are ignoring the number of bottles rejected by the camera + the number of bottles
rejected by the label inspector + any jam that occurs in other machines (labelers, elevators, etc.). On our part, we must check the operation of all our ejectors, ensuring that they are counting correctly when a rejection is executed. We must also eliminate
or comment out from our logic the rejectors that are not physically on the lines (in the loweratos of the TLO22/L25 line the rejectors are not physically on, I must validate that they are turned off in the logic). In addition, we must ensure that all the bottle
counters that exist along the lines are working properly.
Sam asked me about automatic changeover on the conveyor guides. I think that ALPLA will soon make a formal request to activate this system. Currently this option exists in our PLCs and HMIs, but it has never been tested. When this option is working, we
must copy the simultaneous changeover logic carried out in Henkel to avoid two guide changes being made at the same time in ALPLA and eliminate the risk of the EMDs becoming uncalibrated.
From these points we must evaluate, if ALPLA requests them, which ones should be charged as additional and which ones are included in the current project.
Lenin Vera
Filling
& Process Machine Automation Engineer
+1 812 5602700
---
+ 2929f95219bc1e1a756bc8908453990d
### I: R: I: [EXT] R: Vetro Conveyor 9.3674
- 04-02-2025
Ciao Alex,
HENKEL ci ha chiesto di implementare il software in modo che non si sovrappongano i cambi formato. Puoi stimarmi le ore per la modifica software a casa e su quali quadri dobbiamo aggiornare il software
in cantiere?
Siccome il quadro di supervisione riceve i batch con i formati da fare da HENKEL e li compara nel registro ID bottiglie di ALPLA per avviare i cambi formato dovremmo essere in grado di gestire e
non sovrapporre cambi formato guide tra una linea e l’altra.
Allego le email che riassumono il funzionamento del batch handling. Riporto sotto la parte principale.
We confirm the following code sas per attached e-mail) are matching with what we agreed back in May therefore we can process P/N (customer article) but ALPLA should write in our
supervision PLC a list where customer article is associated to AV, AV Desc, Product Family as agreed.
This list will be constantly editable by ALPLA on a persistent memory as agreed in order for Vetromeccanica to handle new customer articles except for new formats (new bottle shapes)
which will require new recipes and commissioning first.
As per now we only have an excel list dated May 2020 which we cannot use for batch handling.
| ALPLA AV | Blank Bottle P/N |
|----------|------------------|
| 184 | 2638879 |
| 253 | 2688129 |
| 102 | 2638876 |
Agreed:
AV (must be forwared to Autefa, must be shown on your HMI’s)
AV Desc (must be shown on you HMI’s)
Product Family (must be used by Vetro to select right Recipe)
Customer article Number (used by Vetro to find matching AV)
| | HENKEL | Alpla | Vetromeccanica | AUTEFA |
|-------------------|--------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|------------------------------------------------------------------------------------------|
| Before Changeover | Sends IDH_BTL_NEXT number to be validated | | | |
| | Data_To_EbConvey[38] | | | |
| | | Validates IDH_BTL_NEXT is valid number and send acknowledge | | |
| | | Data_From_EbConvey[0].2 | | |
| Step 1 | Operator manually selects "Line Clearance" (?) and send signal "0" on "CalculatedBottlesRemainingToFill". | | | |
| | Data_To_EbConvey[23] | | | |
| Step 2 | | Stops taking bottles out of trays and sends what is already on the tables and conveyors. | Emptying Merger and Line | Stops taking bottles out of trays and sends what is already on the tables and conveyors. |
| | | N/A | TG10 Send 0 in Bottles for Actual Batch | |
| Step 3 | Operator verifies line is empty and sends "changeover request" signal after last bottle goes thorugh filler. | | | |
| | Data_To_EbConvey[0].0 | | | |
| Step 4 | | Operator verifies line is empty and sends "line is busy with changeover", confirming on Popup screen | | |
| | | Data_From_EbConvey[0].0 | | |
| Step 5 | | | Starts changeover | Starts changeover |
| | | | Data_From_EbConvey[0].0 | Data_From_EbConvey[0].0 |
| Step 6 | | | Ends changeover. Sends signal "Changeover is finished and ready. | Ends changeover. Sends signal "Changeover is finished and ready. |
| | | | Data_From_EbConvey[0].1 | Data_From_EbConvey[0].1 |
| | | | | |
| | | | | |
| Step 7 | Send Reset counters signal | | Reset Counters | |
| | Data_To_EbConvey[0].1 | | | |
| Step 8 | Send new value on "CalculatedBottlesRemainingToFill". | | | |
| | Data_To_EbConvey[23] | | | |
| Step 9 | Send Changeover Complete. To be considered "Production Ready" | Starts conveying bottles. | Finish Chanover Cycle | |
| | Data_To_EbConvey[0].2 | | | |
Signals:
****
FromHenkel
*************
Data_To_EbConvey[0].0 : Request Signal To Start ChangeOver
Data_To_EbConvey[0].1 : Reset Signal To Restart all Counter
Data_To_EbConvey[0].2 : ChangeOver Complete
Data_To_EbConvey[0].3 : Production Ready
To Henkel
*************
Data_From_EbConvey[0].0 : Line is busy with ChangeOver
Data_From_EbConvey[0].1 : ChangeOver is finished and ready
Data_From_EbConvey[0].2 : IDH_BTL_NEXT Proper: 1 = Found / 0 = Not Found
ToAutefa: x[0] : Reset
ToAutefa: x[1] : Request Signal To Start Changeover
| Program | AV | AV Desc | Henkel Color Desc | ALPLA Color Code | Packaging ID | Packaging Desc | Compound ID | Compound Desc | Product Family ID | Product Family Desc | Spout / Spigot Type | Spout / Spigot Id# | Dose Cup Type | Dose Cup Id# | Customer Article Number |
|---------|-----|---------------------------------|-------------------|--------------------|--------------|----------------------------------------------------|-------------|-------------------------------------------------|-------------------|---------------------|---------------------|--------------------|---------------|--------------|-------------------------|
| Beluga | 109 | HDPE Beluga 188oz White | White | Color White | 20 | 20 - NOPAL 14u X 56 TRA (784 pcs) Beluga 188oz | 2 | COEX HDPE PCR 50% 3lay Beluga 11748 | 8 | HDPE Beluga 188oz | SPG B | 2275368 | DC2X | 2404432 | |
| Beluga | 192 | HDPE Beluga 188oz Trans Green | Trans Green | Color Green | 20 | 20 - NOPAL 14u X 56 TRA (784 pcs) Beluga 188oz | 40 | COEX HDPE PCR 50% 3lay Beluga PM62284E111 | 8 | HDPE Beluga 188oz | SPG WBR | TBC | DC2X | 2404432 | |
| Beluga | 193 | HDPE Beluga 188oz Orange | Orange | Color Orange | 20 | 20 - NOPAL 14u X 56 TRA (784 pcs) Beluga 188oz | 41 | COEX HDPE PCR 50% 3lay Beluga PM3983 | 8 | HDPE Beluga 188oz | SPG R | 2275367 | DC2X | 2404432 | |
| Beluga | 194 | HDPE Beluga 188oz Pearl Blue | Pearl Blue | Color Blue | 20 | 20 - NOPAL 14u X 56 TRA (784 pcs) Beluga 188oz | 42 | COEX HDPE PCR 50% 3lay Beluga 1603778-N | 8 | HDPE Beluga 188oz | SPG WBR | TBC | DC2X | 2404432 | |
| H13 | 110 | HDPE H13 188oz All White | All White | Color White | 24 | 24 - NOPAL 14u X 54 TRA (756 pcs) H13 188oz | 7 | COEX HDPE PCR 50% 3lay H13 11748 | 9 | HDPE H13 188oz | SPG WBR | TBC | DC2X | 2404432 | |
| H13 | 164 | HDPE H13 188oz Purple | Purple | Color Pink / Lilac | 24 | 24 - NOPAL 14u X 54 TRA (756 pcs) H13 188oz | 59 | COEX HDPE PCR 50% 3lay H13 PM53536 | 9 | HDPE H13 188oz | SPG WBR | TBC | DC2X | 2404432 | |
| H13 | 165 | HDPE H13 188oz Dark Blue | Dark Blue | Color Blue | 24 | 24 - NOPAL 14u X 54 TRA (756 pcs) H13 188oz | 60 | COEX HDPE PCR 50% 3lay H13 PM52044E111 | 9 | HDPE H13 188oz | SPG WBR | TBC | DC2X | 2404432 | |
| H13 | 166 | HDPE H13 188oz Pearl Purple | Pearl Purple | Color Pink / Lilac | 24 | 24 - NOPAL 14u X 54 TRA (756 pcs) H13 188oz | 61 | COEX HDPE PCR 50% 3lay H13 165954 | 9 | HDPE H13 188oz | SPG WBR | TBC | DC2X | 2404432 | |
| H13 | 167 | HDPE H13 188oz Sunlight Yellow | Sunlight Yellow | Color Yellow | 24 | 24 - NOPAL 14u X 54 TRA (756 pcs) H13 188oz | 62 | COEX HDPE PCR 50% 3lay H13 PM25671 | 9 | HDPE H13 188oz | SPG WBR | TBC | DC2X | 2404432 | |
| H13 | 168 | HDPE H13 188oz Orange | Orange | Color Orange | 24 | 24 - NOPAL 14u X 54 TRA (756 pcs) H13 188oz | 63 | COEX HDPE PCR 50% 3lay H13 PM3983 | 9 | HDPE H13 188oz | SPG WBR | TBC | DC2X | 2404432 | |
| H13 | 169 | HDPE H13 188oz Red | Red | Color Red | 24 | 24 - NOPAL 14u X 54 TRA (756 pcs) H13 188oz | 64 | COEX HDPE PCR 50% 3lay H13 155097 | 9 | HDPE H13 188oz | SPG WBR | TBC | DC2X | 2404432 | |
| H13 | 170 | HDPE H13 188oz Pearl Blue | Pearl Blue | Color Blue | 24 | 24 - NOPAL 14u X 54 TRA (756 pcs) H13 188oz | 65 | COEX HDPE PCR 50% 3lay H13 1603778-N | 9 | HDPE H13 188oz | SPG WBR | TBC | DC2X | 2404432 | |
| H13 | 171 | HDPE H13 188oz Green | Green | Color Green | 24 | 24 - NOPAL 14u X 54 TRA (756 pcs) H13 188oz | 66 | COEX HDPE PCR 50% 3lay H13 PM67887 | 9 | HDPE H13 188oz | SPG WBR | TBC | DC2X | 2404432 | |
| H13 | 172 | HDPE H13 188oz Gain Green | Gain Green | Color Green | 24 | 24 - NOPAL 14u X 54 TRA (756 pcs) H13 188oz | 67 | COEX HDPE PCR 50% 3lay H13 PM61781E111 | 9 | HDPE H13 188oz | SPG WBR | TBC | DC2X | 2404432 | |
| H14 | 223 | HDPE H14 34oz White | White | Color White | 25 | 25 - NOPAL 14u X 210 TRA (2,940 pcs) H14 34oz | 68 | COEX HDPE PCR 50% 3lay H14 11748 | 17 | HDPE H14 34oz | SP63 | 2275481 | | | |
| H14 | 224 | HDPE H14 34oz Pearl White | Pearl White | Color White | 25 | 25 - NOPAL 14u X 210 TRA (2,940 pcs) H14 34oz | 72 | COEX HDPE PCR 50% 3lay H14 11748 and PM12048E63 | 17 | HDPE H14 34oz | SP63 | 2275481 | | | |
| H14 | 225 | HDPE H14 34oz Blue | Blue | Color Blue | 25 | 25 - NOPAL 14u X 210 TRA (2,940 pcs) H14 34oz | 69 | COEX HDPE PCR 50% 3lay H14 PM53399 | 17 | HDPE H14 34oz | SP63 | 2275481 | | | |
| H14 | 226 | HDPE H14 34oz Pearl Blue | Pearl Blue | Color Blue | 25 | 25 - NOPAL 14u X 210 TRA (2,940 pcs) H14 34oz | 70 | COEX HDPE PCR 50% 3lay H14 1603778-N | 17 | HDPE H14 34oz | SP63 | 2275481 | | | |
| H96 | 227 | HDPE H96 64oz All White | All White | Color White | 26 | 26 - NOPAL 14u X 143 TRA (2,002 pcs) H96 64oz | 71 | COEX HDPE PCR 50% 3lay H96 11748 | 18 | HDPE H96 64oz | SP63 | 2275481 | | | |
| H96 | 228 | HDPE H96 64oz Light Purple | Light Purple | Color Pink / Lilac | 26 | 26 - NOPAL 14u X 143 TRA (2,002 pcs) H96 64oz | 73 | COEX HDPE PCR 50% 3lay H96 161250 | 18 | HDPE H96 64oz | SP63 | 2275481 | | | |
| H96 | 229 | HDPE H96 64oz Blue | Blue | Color Blue | 26 | 26 - NOPAL 14u X 143 TRA (2,002 pcs) H96 64oz | 74 | COEX HDPE PCR 50% 3lay H96 PM53399 | 18 | HDPE H96 64oz | SP63 | 2275481 | | | |
| H96 | 230 | HDPE H96 64oz Green | Green | Color Green | 26 | 26 - NOPAL 14u X 143 TRA (2,002 pcs) H96 64oz | 75 | COEX HDPE PCR 50% 3lay H96 PM67887 | 18 | HDPE H96 64oz | SP63 | 2275481 | | | |
| H96 | 231 | HDPE H96 64oz All Blue | All Blue | Color Blue | 26 | 26 - NOPAL 14u X 143 TRA (2,002 pcs) H96 64oz | 76 | COEX HDPE PCR 50% 3lay H96 1603774-N | 18 | HDPE H96 64oz | SP63 | 2275481 | | | |
| H96 | 232 | HDPE H96 64oz Pearl Blue | Pearl Blue | Color Blue | 26 | 26 - NOPAL 14u X 143 TRA (2,002 pcs) H96 64oz | 77 | COEX HDPE PCR 50% 3lay H96 1603778-N | 18 | HDPE H96 64oz | SP63 | 2275481 | | | |
| LF04B H | 105 | HDPE LF04B H 40oz All White | All White | Color White | 8 | 8 - NOPAL 14u X 176 TRA (2,464 pcs) LF04B H 40oz | 9 | COEX HDPE PCR 50% 3lay LF04B H 11748 | 6 | HDPE LF04B H 40oz | SP70 | 1466712 | | | 2638861 |
| LF04B H | 126 | HDPE LF04B H 40oz All Blue | All Blue | Color Blue | 8 | 8 - NOPAL 14u X 176 TRA (2,464 pcs) LF04B H 40oz | 10 | COEX HDPE PCR 50% 3lay LF04B H 1603774-N | 6 | HDPE LF04B H 40oz | SP70 | 1466712 | | | 2638860 |
| LF10B H | 195 | HDPE LF10B H 100oz All White | All White | Color White | 16 | 16 - NOPAL 14u X 81 TRA (1,134 pcs) LF10B H 100oz | 3 | COEX HDPE PCR 50% 3lay LF10 H 11748 | 7 | HDPE LF10B H 100oz | SP70 | 1466712 | | | 2638863 |
| LF10B H | 196 | HDPE LF10B H 100oz All Blue | All Blue | Color Blue | 16 | 16 - NOPAL 14u X 81 TRA (1,134 pcs) LF10B H 100oz | 11 | COEX HDPE PCR 50% 3lay LF10 H 1603774-N | 7 | HDPE LF10B H 100oz | SP70 | 1466712 | | | 2638862 |
| SP01 | 104 | HDPE SP01 50oz White | White | Color White | 9 | 9 - NOPAL 14u X 176 TRA (2,464 pcs) SP01 50oz | 5 | COEX HDPE PCR 50% 3lay SP01 11748 | 5 | HDPE SP01 50oz | SP63 | 2275481 | | | |
| SP01 | 173 | HDPE SP01 50oz Dark Blue | Dark Blue | Color Blue | 9 | 9 - NOPAL 14u X 176 TRA (2,464 pcs) SP01 50oz | 12 | COEX HDPE PCR 50% 3lay SP01 PM52044E111 | 5 | HDPE SP01 50oz | SP63 | 2275481 | | | |
| SP01 | 174 | HDPE SP01 50oz Pearl Blue | Pearl Blue | Color Blue | 9 | 9 - NOPAL 14u X 176 TRA (2,464 pcs) SP01 50oz | 13 | COEX HDPE PCR 50% 3lay SP01 1603777-NE | 5 | HDPE SP01 50oz | SP63 | 2275481 | | | |
| SP01 | 175 | HDPE SP01 50oz Sunlight Yellow | Sunlight Yellow | Color Yellow | 9 | 9 - NOPAL 14u X 176 TRA (2,464 pcs) SP01 50oz | 14 | COEX HDPE PCR 50% 3lay SP01 PM25671 | 5 | HDPE SP01 50oz | SP63 | 2275481 | | | |
| SP01 | 176 | HDPE SP01 50oz Blue | Blue | Color Blue | 9 | 9 - NOPAL 14u X 176 TRA (2,464 pcs) SP01 50oz | 15 | COEX HDPE PCR 50% 3lay SP01 PM53939 | 5 | HDPE SP01 50oz | SP63 | 2275481 | | | |
| SP01 | 177 | HDPE SP01 50oz Purple | Purple | Color Pink / Lilac | 9 | 9 - NOPAL 14u X 176 TRA (2,464 pcs) SP01 50oz | 16 | COEX HDPE PCR 50% 3lay SP01 PM53536 | 5 | HDPE SP01 50oz | SP63 | 2275481 | | | |
| SP01 | 178 | HDPE SP01 50oz Green | Green | Color Green | 9 | 9 - NOPAL 14u X 176 TRA (2,464 pcs) SP01 50oz | 17 | COEX HDPE PCR 50% 3lay SP01 PM67887 | 5 | HDPE SP01 50oz | SP63 | 2275481 | | | |
| SP01 | 179 | HDPE SP01 50oz Gain Green | Gain Green | Color Green | 9 | 9 - NOPAL 14u X 176 TRA (2,464 pcs) SP01 50oz | 18 | COEX HDPE PCR 50% 3lay SP01 PM61781E111 | 5 | HDPE SP01 50oz | SP63 | 2275481 | | | |
| SP02 | 207 | HDPE SP02 150oz Pearl Green | Pearl Green | Color Green | 21 | 21 - NOPAL 14u X 72 TRA (1,008 pcs) SP02 150oz | 43 | COEX HDPE PCR 50% 3lay SP02 PM68140 | 14 | HDPE SP02 150oz | SP63 | 2275481 | | | |
| SP02 | 208 | HDPE SP02 150oz Pearl Blue | Pearl Blue | Color Blue | 21 | 21 - NOPAL 14u X 72 TRA (1,008 pcs) SP02 150oz | 44 | COEX HDPE PCR 50% 3lay SP02 1603778-N | 14 | HDPE SP02 150oz | SP63 | 2275481 | | | |
| SP02 | 209 | HDPE SP02 150oz Blue | Blue | Color Blue | 21 | 21 - NOPAL 14u X 72 TRA (1,008 pcs) SP02 150oz | 45 | COEX HDPE PCR 50% 3lay SP02 PM53939 | 14 | HDPE SP02 150oz | SP63 | 2275481 | | | |
| SP05 | 102 | HDPE SP05 100oz White | White | Color White | 17 | 17 - NOPAL 14u X 90 TRA (1,260 pcs) SP05 100oz | 4 | COEX HDPE PCR 50% 3lay SP05 11748 | 3 | HDPE SP05 100oz | SP63 | 2275481 | | | 2638876 |
| SP05 | 180 | HDPE SP05 100oz Orange | Orange | Color Orange | 17 | 17 - NOPAL 14u X 90 TRA (1,260 pcs) SP05 100oz | 19 | COEX HDPE PCR 50% 3lay SP05 PM3983 | 3 | HDPE SP05 100oz | SP63 | 2275481 | | | 2638881 |
| SP05 | 181 | HDPE SP05 100oz Sunlight Yellow | Sunlight Yellow | Color Yellow | 17 | 17 - NOPAL 14u X 90 TRA (1,260 pcs) SP05 100oz | 20 | COEX HDPE PCR 50% 3lay SP05 PM25671 | 3 | HDPE SP05 100oz | SP63 | 2275481 | | | 2638882 |
| SP05 | 182 | HDPE SP05 100oz Dark Blue | Dark Blue | Color Blue | 17 | 17 - NOPAL 14u X 90 TRA (1,260 pcs) SP05 100oz | 21 | COEX HDPE PCR 50% 3lay SP05 PM52044E111 | 3 | HDPE SP05 100oz | SP63 | 2275481 | | | 2638878 |
| SP05 | 183 | HDPE SP05 100oz Blue | Blue | Color Blue | 17 | 17 - NOPAL 14u X 90 TRA (1,260 pcs) SP05 100oz | 22 | COEX HDPE PCR 50% 3lay SP05 PM53399 | 3 | HDPE SP05 100oz | SP63 | 2275481 | | | 2638874 |
| SP05 | 184 | HDPE SP05 100oz Pearl Blue | Pearl Blue | Color Blue | 17 | 17 - NOPAL 14u X 90 TRA (1,260 pcs) SP05 100oz | 23 | COEX HDPE PCR 50% 3lay SP05 1603778-N | 3 | HDPE SP05 100oz | SP63 | 2275481 | | | 2638879 |
| SP05 | 185 | HDPE SP05 100oz Pearl White | Pearl White | Color White | 17 | 17 - NOPAL 14u X 90 TRA (1,260 pcs) SP05 100oz | 4 | COEX HDPE PCR 50% 3lay SP05 11748 | 3 | HDPE SP05 100oz | SP63 | 2275481 | | | 2638880 |
| SP05 | 186 | HDPE SP05 100oz Green | Green | Color Green | 17 | 17 - NOPAL 14u X 90 TRA (1,260 pcs) SP05 100oz | 25 | COEX HDPE PCR 50% 3lay SP05 PM67887 | 3 | HDPE SP05 100oz | SP63 | 2275481 | | | 2638873 |
| SP05 | 187 | HDPE SP05 100oz Gain Green | Gain Green | Color Green | 17 | 17 - NOPAL 14u X 90 TRA (1,260 pcs) SP05 100oz | 26 | COEX HDPE PCR 50% 3lay SP05 PM61781E111 | 3 | HDPE SP05 100oz | SP63 | 2275481 | | | 2638875 |
| SP12 | 197 | HDPE SP12 172oz All White | All White | Color White | 18 | 18 - NOPAL 14u X 56 TRA (784 pcs) SP12 172oz | 27 | COEX HDPE PCR 50% 3lay SP12 11748 | 13 | HDPE SP12 172oz | SPG B | 2275368 | DC5 | 2272746 | |
| SP12 | 198 | HDPE SP12 172oz Pearl Blue | Pearl Blue | Color Blue | 18 | 18 - NOPAL 14u X 56 TRA (784 pcs) SP12 172oz | 28 | COEX HDPE PCR 50% 3lay SP12 1603778-N | 13 | HDPE SP12 172oz | SPG B | 2275368 | DC5 | 2272746 | |
| SP12 | 199 | HDPE SP12 172oz Orange | Orange | Color Orange | 18 | 18 - NOPAL 14u X 56 TRA (784 pcs) SP12 172oz | 29 | COEX HDPE PCR 50% 3lay SP12 PM3983 | 13 | HDPE SP12 172oz | SPG B | 2275368 | DC5 | 2272746 | |
| SP12 | 200 | HDPE SP12 172oz All Blue | All Blue | Color Blue | 18 | 18 - NOPAL 14u X 56 TRA (784 pcs) SP12 172oz | 30 | COEX HDPE PCR 50% 3lay SP12 1603774-N | 13 | HDPE SP12 172oz | SPG B | 2275368 | DC5 | 2272746 | |
| SP12 | 201 | HDPE SP12 172oz Silver | Silver | Color Silver | 18 | 18 - NOPAL 14u X 56 TRA (784 pcs) SP12 172oz | 31 | COEX HDPE PCR 50% 3lay SP12 PM86534 | 13 | HDPE SP12 172oz | SPG B | 2275368 | DC5 | 2272746 | |
| SP12 | 202 | HDPE SP12 172oz Pink Pearl | Pink Pearl | Pink Pearl | 18 | 18 - NOPAL 14u X 56 TRA (784 pcs) SP12 172oz | 32 | COEX HDPE PCR 50% 3lay SP12 152985 | 13 | HDPE SP12 172oz | SPG B | 2275368 | DC5 | 2272746 | |
| SP12 | 203 | HDPE SP12 172oz Pearl White | Pearl White | Color White | 18 | 18 - NOPAL 14u X 56 TRA (784 pcs) SP12 172oz | 24 | COEX HDPE PCR 50% 3lay SP12 11748 | 13 | HDPE SP12 172oz | SPG B | 2275368 | DC5 | 2272746 | |
| SP12 | 204 | HDPE SP12 172oz Light Purple | Light Purple | Color Pink / Lilac | 18 | 18 - NOPAL 14u X 56 TRA (784 pcs) SP12 172oz | 33 | COEX HDPE PCR 50% 3lay SP12 161250 | 13 | HDPE SP12 172oz | SPG B | 2275368 | DC5 | 2272746 | |
| SP12 | 205 | HDPE SP12 172oz Blue | Blue | Color Blue | 18 | 18 - NOPAL 14u X 56 TRA (784 pcs) SP12 172oz | 34 | COEX HDPE PCR 50% 3lay SP12 PM53939 | 13 | HDPE SP12 172oz | SPG R | 2275367 | DC5 | 2272746 | |
| SP12 | 206 | HDPE SP12 172oz Gain Green | Gain Green | Color Green | 18 | 18 - NOPAL 14u X 56 TRA (784 pcs) SP12 172oz | 35 | COEX HDPE PCR 50% 3lay SP12 PM61781E111 | 13 | HDPE SP12 172oz | SPG B | 2275368 | DC5 | 2272746 | |
| SP14 | 210 | HDPE SP14 75oz White | White | Color White | 22 | 22 - NOPAL 14u X 117 TRA (1,638 pcs) SP14 75oz | 46 | COEX HDPE PCR 50% 3lay SP14 11748 | 15 | HDPE SP14 75oz | SP63 | 2275481 | | | |
| SP14 | 211 | HDPE SP14 75oz Pearl Blue | Pearl Blue | Color Blue | 22 | 22 - NOPAL 14u X 117 TRA (1,638 pcs) SP14 75oz | 47 | COEX HDPE PCR 50% 3lay SP14 1603778-N | 15 | HDPE SP14 75oz | SP63 | 2275481 | | | |
| SP14 | 212 | HDPE SP14 75oz Yellow | Yellow | Color Yellow | 22 | 22 - NOPAL 14u X 117 TRA (1,638 pcs) SP14 75oz | 48 | COEX HDPE PCR 50% 3lay SP14 PM22273 | 15 | HDPE SP14 75oz | SP63 | 2275481 | | | |
| SP14 | 213 | HDPE SP14 75oz Sunlight Yellow | Sunlight Yellow | Color Yellow | 22 | 22 - NOPAL 14u X 117 TRA (1,638 pcs) SP14 75oz | 49 | COEX HDPE PCR 50% 3lay SP14 PM25671 | 15 | HDPE SP14 75oz | SP63 | 2275481 | | | |
| SP14 | 214 | HDPE SP14 75oz Dark Blue | Dark Blue | Color Blue | 22 | 22 - NOPAL 14u X 117 TRA (1,638 pcs) SP14 75oz | 50 | COEX HDPE PCR 50% 3lay SP14 PM52044E111 | 15 | HDPE SP14 75oz | SP63 | 2275481 | | | |
| SP14 | 215 | HDPE SP14 75oz Blue | Blue | Color Blue | 22 | 22 - NOPAL 14u X 117 TRA (1,638 pcs) SP14 75oz | 51 | COEX HDPE PCR 50% 3lay SP14 PM53939 | 15 | HDPE SP14 75oz | SP63 | 2275481 | | | |
| SP14 | 216 | HDPE SP14 75oz Silver | Silver | Color Silver | 22 | 22 - NOPAL 14u X 117 TRA (1,638 pcs) SP14 75oz | 52 | COEX HDPE PCR 50% 3lay SP14 PM86534 | 15 | HDPE SP14 75oz | SP63 | 2275481 | | | |
| SP17 | 103 | HDPE SP17 125oz Green | Green | Color Green | 19 | 19 - NOPAL 14u X 72 TRA (1,008 pcs) SP17 125oz | 6 | COEX HDPE PCR 50% 3lay SP17 PM67887 | 4 | HDPE SP17 125oz | SP63 | 2275481 | | | 2638872 |
| SP17 | 188 | HDPE SP17 125oz Dark Blue | Dark Blue | Color Blue | 19 | 19 - NOPAL 14u X 72 TRA (1,008 pcs) SP17 125oz | 36 | COEX HDPE PCR 50% 3lay SP17 PM52044E111 | 4 | HDPE SP17 125oz | SP63 | 2275481 | | | 2638870 |
| SP17 | 189 | HDPE SP17 125oz Pearl Blue | Pearl Blue | Color Blue | 19 | 19 - NOPAL 14u X 72 TRA (1,008 pcs) SP17 125oz | 37 | COEX HDPE PCR 50% 3lay SP17 1603778-N | 4 | HDPE SP17 125oz | SP63 | 2275481 | | | 2638865 |
| SP17 | 190 | HDPE SP17 125oz Purple | Purple | Color Pink / Lilac | 19 | 19 - NOPAL 14u X 72 TRA (1,008 pcs) SP17 125oz | 38 | COEX HDPE PCR 50% 3lay SP17 PM53536 | 4 | HDPE SP17 125oz | SP63 | 2275481 | | | 2638869 |
| SP17 | 191 | HDPE SP17 125oz Sunlight Yellow | Sunlight Yellow | Color Yellow | 19 | 19 - NOPAL 14u X 72 TRA (1,008 pcs) SP17 125oz | 39 | COEX HDPE PCR 50% 3lay SP17 PM25671 | 4 | HDPE SP17 125oz | SP63 | 2275481 | | | 2638868 |
| SP26 | 217 | HDPE SP26 150oz All White | All White | Color White | 23 | 23 - NOPAL 14u X 64 TRA (896 pcs) SP26 150oz | 53 | COEX HDPE PCR 50% 3lay SP26 11748 | 16 | HDPE SP26 150oz | SP63 | 2275481 | | | |
| SP26 | 218 | HDPE SP26 150oz Sunlight Yellow | Sunlight Yellow | Color Yellow | 23 | 23 - NOPAL 14u X 64 TRA (896 pcs) SP26 150oz | 54 | COEX HDPE PCR 50% 3lay SP26 PM25671 | 16 | HDPE SP26 150oz | SP63 | 2275481 | | | |
| SP26 | 219 | HDPE SP26 150oz Purple | Purple | Color Pink / Lilac | 23 | 23 - NOPAL 14u X 64 TRA (896 pcs) SP26 150oz | 55 | COEX HDPE PCR 50% 3lay SP26 PM53536 | 16 | HDPE SP26 150oz | SP63 | 2275481 | | | |
| SP26 | 220 | HDPE SP26 150oz Dark Blue | Dark Blue | Color Blue | 23 | 23 - NOPAL 14u X 64 TRA (896 pcs) SP26 150oz | 56 | COEX HDPE PCR 50% 3lay SP26 PM52044E111 | 16 | HDPE SP26 150oz | SP63 | 2275481 | | | |
| SP26 | 221 | HDPE SP26 150oz Pearl Blue | Pearl Blue | Color Blue | 23 | 23 - NOPAL 14u X 64 TRA (896 pcs) SP26 150oz | 57 | COEX HDPE PCR 50% 3lay SP26 1603778-N | 16 | HDPE SP26 150oz | SP63 | 2275481 | | | |
| SP26 | 222 | HDPE SP26 150oz Green | Green | Color Green | 23 | 23 - NOPAL 14u X 64 TRA (896 pcs) SP26 150oz | 58 | COEX HDPE PCR 50% 3lay SP26 PM67887 | 16 | HDPE SP26 150oz | SP63 | 2275481 | | | |
Esatto, quella è l unica pagina che abbiamo.
A casa mia il manuale del pannello spega come usare i dati disponibili e basta.
Una gran parte della roba scritta in inglese andrebbe spiegata al cliente prima di fare l impianto pneumatico, comunque per me lo puoi far fare ai ragazzi in cantiere.
Per quanto riguarda i dubbi sull installazione, non ne ho idea di cosa sia stato fatto e le cose da guardare sono sempre le solite:
quanti attuatori ci sono per gruppo?
Sono state controllate eventuali perdite di aria su ogni singolo tubo colorato?
Una calata dell aria quanti gruppi valvole alimentano?
Quante linee devono fare il cambio formato contemporaneamente?
Quanti bar a riposo?
Quanti bar con impulso attivo?
Ho 39di febbre e mal di gola boia, oggi non credo di essere in grado di sostenere una telefonata
Inviato dal mio Galaxy
Data: 07/02/24 11:38 (GMT+01:00)
Ciao Alex,
Grazie per aver risposto subito.
Parli di questa pagina giusto? Se siete oberati, siccome Alok è in cantiere con Lenin e Todi chiedo a lui di interfacciarsi con i tecnici e il cliente per inserire tutte le info mancanti tra
cui i calcoli UTM allegati e chiarimenti evidenziati email a HENKEL sotto. Posso dirgli che se ha dei dubbi sulla corretta impostazione - funzionamento di contattarti finché in cantiere oggi e domani? Poi vedi tu se te la senti di rispondere. Se a tuo parere
rimangono dei dubbi importanti sulla corretta esecuzione dell’installazione sentiti libero di segnalarcelo.
Grazie,
Max
Max
Abbiamo solamente una piccola descrizione della pagina pannello perché ci sono 6 valori in tutto di cui 4 fissi(password livello alto) e 2 variabili in base alla ricetta(diametro
bottiglia e tolleranza)!
Per slide o cose varie devi sentire chi fa i manuali, noi non ne facciamo e non ne abbiamo.
Miguel non ha assolutamente tempo per seguire queste cose e lo devi escludere immediatamente.se devi chiedere cose a chi è in cantiere fallo tramite l assistenza.
I parametri di pneumatica sono calcoli che avevano fatto in utm (pressione a riposo, portata, numero attuatori per gruppo valvole) quando sono stati inventati gli emd, quindi
anche su questo devi chiedere al reparto giusto.
Sicuramente hanno dei problemi perché non saranno stati fatti correttamente i circuiti a livello di pressioni/portate/serbatoi
Inviato dal mio Galaxy
Data: 07/02/24 10:42 (GMT+01:00)
Ciao Miguel,
Come ci siamo detti, siccome hai altre urgenze, se riesci a delegare a Lenin, Todi e Alok la creazione di un paio di pagine con relative foto da inserire nel manuale 9.3674 poi le giriamo a Linda/Mattia
per metterle in bella.
Magari Alex ha già fatto delle slide per i manuali da cui possiamo partire e che possiamo girare a Lenin, Todi e Alok. Senti prima Alex cosa suggerisce.
Grazie,
Max
Ciao Alex,
Possiamo preparare un paio di pagine da integrare nel manuale per il corretto settaggio meccanico e software dei pressostati sulla 9.3674? Tutto quello che i tecnici regolano sul preparato manualmente e a software per assicurarsi che l’aria
in arrivo sia controllata e gli impulsi siano corretti per un buon funzionamento degli
EMD.
Suggerisco tramite Miguel di chiedere a Lenin di mettere insieme foto e testi come da nostro standard. Ovviamente dopo lo giriamo a Linda/Mattia per metterlo in bella.
Urgente, servirebbe questa settimana perché non saltandoci fuori stanno rifacendo in questi giorni il piping dell’aria compressa.
Grazie per il celere supporto.
Max
Begin forwarded message:
Date: 6 February 2024 at 20:29:01 CET
Bhrahmbhatt - Vetromeccanica S.r.l." <a.bhrahmbhatt@vmeccanica.com>, Timothy Bollenbecker <timothy.bollenbecker@henkel.com>
***
Subject: RE: [EXT] R: Vetro Conveyor 9.3674

Copy me on the manual for the regulator setup.
Indicate each setpoint as identifiable on the regulator and how it correlates to other setpoints within the program... please.
Many do not understand how it works.
The guys on site (Vetro) has been good trying to explain it but I’m wanting to hand something to the maintenance and automation group here so they can develop the proper setup sheets and SOP’s.
I’m also looking separately at the system design and challenges with volumes, pipe sizes, remote receiver tanks, hoses, condensate, routing… appears to have quite a few challenges not thought through in basic design principles of an air
system.
- Vetromeccanica S.r.l. <a.bhrahmbhatt@vmeccanica.com>; Timothy Bollenbecker <timothy.bollenbecker@henkel.com>
***
Subject: R: [EXT] R: Vetro Conveyor 9.3674
Hi David,
Apologies for letting you wait.
Attached you can find a file made for ALPLA showing in
green maximum and average air consumption per circuit for all lines except L20 which is the last one.
As agreed pneumatic system for L20 follows the same design as for the other lines.
This means we have an air circuit every 30m meaning we require an air drop connection point every 30 m.
In our construction layout we indicated an air drop connection point every 30 m with 8 Bar and 90N-liters/min.
Below I copy paste answers to your predecessors questions dated September 2021.
From our meeting last week, and your emails, the technical specification of the air required by the Vetro system is
90N-liters/min @ 8 bar. There is a misinterpretation, we require 8 Bar at each connection point and 90N-liters/min at 1 bar for 1 hour at each connection point.
This is a little misleading, since N (for “Normal” L/min) is at Standard Conditions – 1bar. We think Vetro were combining two parameters, saying we need 8bar
and the system requires a flow rate of 90, which is ~3.2 scfm.
Question – is this per pulse/cycle at the Festo regulator, or at each of the EMDs?
At every Festo regulator (connection point)
In our meeting on Thursday, we learned that air usage was 5 liters per pulse per EMD?
0.008 l at 8bar or 0.008x8 L at 1bar per each EMD per pulse
Is that true? To complete a rail adjustment of 8mm @ 0.25mm/pulse, you need 32 pulses/cycles, which means 32x5=160L of air to move each EMD.
à For a more realistic calculation for each line please consider the green values in the excel sheet which INCLUDES THE PIPING VOLUME to be filled and the suggested time for
impulse and release (see below).
Is this on the basis of 8bar or is it N-Liters?
See above
The 5-sec air pulse/5-sec hold (release) was the initial number we were given; they then said it could be up to 8 sec; we were able to see pulses from 10 to 20-sec
last Friday – is this correct? Were they modified on purpose? Yes they were modified on purpose to be sure every EMD has the right pressure
Hope this helps clear some doubts.
Kind regards,
Max
- Vetromeccanica S.r.l. <a.bhrahmbhatt@vmeccanica.com>; Timothy Bollenbecker <timothy.bollenbecker@henkel.com>
Hi David,
Well received, can I forward it to your early next week once back in the office?
Thank you and kind regards,
Max
On 1 Feb 2024, at 15:32, David Busch <david.busch@henkel.com> wrote:

I need documents with specific instructions on setup and usage.
Now I have heard or seen 4 bar 5.5 bar, 6 bar, 8 bar…
If I have nothing in documented format to give them… I will not present to them and they will continue to set it how they THINK is what is right.
Alok Bhrahmbhatt - Vetromeccanica S.r.l. <a.bhrahmbhatt@vmeccanica.com>
***
Subject: [EXT] R: Vetro Conveyor
Hi David
It is correct what M. Hodges writes , proper operation is guaranteed between 8 and 6 bar, so I recommend that you adjust the low air sensors at 5.5 bar , in order to be sure of the correct functioning of the guides.
I have already talked to Roberto to adjust the sensor in this way.
Best regrards
Mirco Magri
After Sales Department
Vetromeccanica srl
P
|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
Magri - Vetromeccanica S.r.l. <m.magri@vetromeccanica.it>; Alok Bhrahmbhatt - Vetromeccanica S.r.l. <a.bhrahmbhatt@vmeccanica.com>
Can you either forward me the spec setup sheet to the regulators on the air system supporting the conveyor change overs or guide me to someone who can?
We have a difference of opinion on how to set the regulators on the rail system. I want to squash this misunderstanding and get all on the same page.
From what I understand there is a setting on the regulator for air supply to the air system on the conveyor rails. Then we have a range of operation for the rail air system… as well as the compressor settings (separate of your air controls)
we need to be mindful of and ensure we supply enough air to change over.
Operations group is challenging the settings of the regulators and air supply and why we can not change over two lines at the same time.
I would like to understand the cfm required to change a line over (per the SOP) and balance that to the rate in which the compressor can supply, recovery rate, and constant average supply vs usage per change over. I need the engineering
design specs of the system to understand the needs of supply.
***
Subject: Re: Vetro Conveyor
Operates between 6-8 bar. Anything lower than 6 bar, the sensors should fault. I walked Vetro guys through this earlier due to they were lowering the low air sensors down to 4 bar. I explained to them they it will not function under
6 bar.
Lennon translated for me.
On Feb 1, 2024, at 8:44 AM, David Busch <david.busch@henkel.com> wrote:

Not that I would expect you to know this but… do you happen to know what load or recovery the system was originally spec’d at? Appears this system does not recover well at all for the use (as little as) it gets. I know it goes back a few
years on design.
***
Subject: Vetro Conveyor
Tim and Lenon have discovered we do not have enough air supply to two lines changing over at the same time. We will need to have a provision made with alarms that Line X is in change over. Once completed the other line can automatically
start C/O
Best Regards
Ken Desmond
Cell Manager, Liquids Packaging
Henkel Corporation
__________________________
385 Southwood Court
Bowling Green, KY 42101
www.henkel-northamerica.com
### Adjuntos
- [[AlplaProd_Articles - VM.xlsx]]
- [[Changeover process map v1.xlsx]]
- [[Vetro AUTEFA Communication Alpla BG IBSS_V3.pptx]]
- [[Vetro_communication_v0.2.docx]]
---
+ e7b1f7771eab45adb515253b612ba97b
### Next + 1 - HENKEL - ALPLA - AUTEFA
- 04-02-2025
Good morning,
I need to confirm my understanding of the NEXT + 1 data requirements from ALPLA/AUTEFA. HENKEL sends this data through the Malisko -> Prosoft system to the Vetromeccanica Q1 PLCs/Lines as three 12-character strings (PO_NUMBER, IDH_BTL, IDH_CON), which we label
as d1-d9 in our software. This data is word-swapped on the Q1 but not further processed on the Supervisor.
The Supervisor PLC manages batch communication with Autefa using AUTEFA's 'Autefa Standard Function Block AS_FB_TG_GENERAL'. The TG10 telegram includes Batch_ID, Next_Batch_Batch_ID, and Next_Batch_+1_Batch_ID, but only Batch_ID is processed on the PLC.
Please specify which data you need from PO_NUMBER_NEXT + 1, IDH_BTL_NEXT + 1, and IDH_CON_NEXT + 1 for the batch, and in what format.
Best regards,
Miguel Angel Vera
External Automation Design Engineer
Vetromeccanica srl Smart Moving Solutions
Strada
Isolanda 26, 43024 Provazzano, Parma - Italy
---
+ 4f3aed45042886599a853fe58b814f4b
### R: [EXT] RE: Vetro/ALPLA information verification 9.3060-3067
- 04-02-2025
Hi Lenin,
Thanks for clarifying with Sam.
We are going to review initial project specifications and try to follow what was agreed at that time.
Nevertheless since it was not possible to commission automatic change over before commssioning final formats, early 2022, not because of Vetromeccanica but because automatic batch change over involves
several companies, everything on this topic will have to be quoted separately, for work in Vetromeccanica and on site. ALPLA is already paying for your stay until February 15th so modifications on site after this date will have to be covered by additional
PO. Also we are awaiting a first PO for inhouse software modification but seems to me that another PO will be necessary for inhouse software modification since more details need to be clarified.
Thank you for your good work as always!
Max
Hi,
Today I spoke with Sam about this topic, and he told me that the new variables are needed to execute the change automatically. This completely changes the way we should work on this project.
He also told me that we should contact AUTEFA, since they are the ones who need this information.
The contacts of the AUTEFA people assigned to this project are:
Stephen.Buehler@autefa.com,
Lenin Vera
Filling & Process Machine Automation Engineer
+1 812 5602700
En lunes, 3 de febrero de 2025, 08:06:25 (-05:00), Miguel Angel Vera - Vetromeccanica S.r.l. <m.vera@vetromeccanica.it> escribió:
Hello Lenin,
I reviewed the requirements for the NEXT2 data for ALPLA. I'm unsure if only changing the data type is necessary, as ALPLA might not read the raw data from FromHenkel d1-d9 directly. Instead, they might need
it on the OPC server similar to the Next Batch structure. You mentioned converting the data type, but I believe the issue is with the data swap at the Q1s. Removing the automatic swap could solve this, but then where will ALPLA read the data from? This wasn't
discussed in last week's emails or call. Do you have more information on how ALPLA plans to access the data from d1-d9?
Best Regards,
Miguel Angel Vera
External Automation Design Engineer
Vetromeccanica srl Smart Moving Solutions
Strada
Isolanda 26, 43024 Provazzano, Parma - Italy
Alok Bhrahmbhatt - Vetromeccanica S.r.l. <a.bhrahmbhatt@vmeccanica.com>; Alex Biasini - Vetromeccanica S.r.l. <a.biasini@vetromeccanica.it>; Miguel Angel Vera
- Vetromeccanica S.r.l. <m.vera@vetromeccanica.it>
sarah.harmon@alpla.com <sarah.harmon@alpla.com>;
Sam.Colley@alpla.com <sam.colley@alpla.com>
Asunto: Re: [EXT] RE: Vetro/ALPLA information verification
Hello everyone
Alok, our friends at ALPLA are asking when the estimated date for this work will be.
Below I refresh our client's request:
Henkel is currently sending a new data package through the variables Data_From_EbConvey[1-9], in our DB (FromHenkelv2_U) these variables are as a DINT, we must change these variables to Array[0..11] of Char (equal to the variable
PO_Number). See image 1 of the attached PDF document
ALPLA wants to see the new variables sent from HENKEL in the same format as it is currently reading the variables PO_Number, AB_IDH_BTL and NB_IDH_BTL.
The names of the new variables must be:
Data_To_EbConvey[1].0 PO_Next2 SINT
Data_To_EbConvey[1].1 PO_Next2 SINT
Data_To_EbConvey[1].2 PO_Next2 SINT
Data_To_EbConvey[1].3 PO_Next2 SINT
Data_To_EbConvey[2].0 PO_Next2 SINT
Data_To_EbConvey[2].1 PO_Next2 SINT
Data_To_EbConvey[2].2 PO_Next2 SINT
Data_To_EbConvey[2].3 PO_Next2 SINT
Data_To_EbConvey[3].0 PO_Next2 SINT
Data_To_EbConvey[3].1 PO_Next2 SINT
Data_To_EbConvey[3].2 PO_Next2 SINT
Data_To_EbConvey[3].3 PO_Next2 SINT
Data_To_EbConvey[4].0 IDH_CON_NEXT2 SINT
Data_To_EbConvey[4].1 IDH_CON_NEXT2 SINT
Data_To_EbConvey[4].2 IDH_CON_NEXT2 SINT
Data_To_EbConvey[4].3 IDH_CON_NEXT2 SINT
Data_To_EbConvey[5].0 IDH_CON_NEXT2 SINT
Data_To_EbConvey[5].1 IDH_CON_NEXT2 SINT
Data_To_EbConvey[5].2 IDH_CON_NEXT2 SINT
Data_To_EbConvey[5].3 IDH_CON_NEXT2 SINT
Data_To_EbConvey[6].0 IDH_CON_NEXT2 SINT
Data_To_EbConvey[6].1 IDH_CON_NEXT2 SINT
Data_To_EbConvey[6].2 IDH_CON_NEXT2 SINT
Data_To_EbConvey[6].3 IDH_CON_NEXT2 SINT
Data_To_EbConvey[7].0 IDH_BTL_NEXT2 SINT
Data_To_EbConvey[7].1 IDH_BTL_NEXT2 SINT
Data_To_EbConvey[7].2 IDH_BTL_NEXT2 SINT
Data_To_EbConvey[7].3 IDH_BTL_NEXT2 SINT
Data_To_EbConvey[8].0 IDH_BTL_NEXT2 SINT
Data_To_EbConvey[8].1 IDH_BTL_NEXT2 SINT
Data_To_EbConvey[8].2 IDH_BTL_NEXT2 SINT
Data_To_EbConvey[8].3 IDH_BTL_NEXT2 SINT
Data_To_EbConvey[9].0 IDH_BTL_NEXT2 SINT
Data_To_EbConvey[9].1 IDH_BTL_NEXT2 SINT
Data_To_EbConvey[9].2 IDH_BTL_NEXT2 SINT
Data_To_EbConvey[9].3 IDH_BTL_NEXT2 SINT
Lenin Vera
Filling & Process Machine Automation Engineer
+1 812 5602700
En jueves, 19 de diciembre de 2024, 11:55:42 (-05:00), L&E <lenin.vera@leautomationandcontrol.com> escribió:
Hello
Miguel, could you please let us know what the estimated time would be to complete this request?
Lenin Vera
FSE
+1 812 5602700
On Dec 19, 2024, at 10:08 AM,
steve.mcevoy@alpla.com wrote:

Hi Lenin
If you could get Italy to offer a feedback on expected timing that would be appreciated.
This piece of work is being pushed by Senior Leadership in ALPLA and HENKEL and we need to manage their expectations
Thanks in advance.
Steve
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
Hi Steve,
I don't have an estimated date; in Italy they are working on the changes that must be made in all the Q1 PLCs and in the supervisory system PLC. As a rule, when a change is to be made in the supervisory PLC,
this change must be made in Italy.
Lenin Vera
Filling & Process Machine Automation Engineer
+1 812 5602700
En miércoles, 18 de diciembre de 2024, 13:42:51 (-05:00), <steve.mcevoy@alpla.com> escribió:
Hi Lenin
Thanks for the update
Can you give any indication on timings for the changes needed ?
Thanks. Steve
a.bhrahmbhatt@vmeccanica.com; Platt Federico <Federico.Platt@alpla.com>; Colley Sam <Sam.Colley@alpla.com>;
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
| | You don't often get email from<br>lenin.vera@leautomationandcontrol.com.<br>Learn why this is important | |
|--|---------------------------------------------------------------------------------------------------------|--|
Hi Steve,
I have been busy this week; I requested help from Italy to make the modification in the PLCs. We have to change the variables di1 - di9 from DINT to SINT.
Thank you and I am sorry for the delay.
Lenin Vera
Filling & Process Machine Automation Engineer
+1 812 5602700
En lunes, 16 de diciembre de 2024, 12:15:11 (-05:00), <steve.mcevoy@alpla.com> escribió:
Hello Lenin & Shannon
What is the status please on the validation of the PLC tags
Can you provide an update by end of today please?
As we have a meeting with Henkel Procurement tomorrow morning
Many thanks. Steve
a.bhrahmbhatt@vmeccanica.com; Colley Sam <Sam.Colley@alpla.com>;
<bmahanna@malisko.com>; Johnson Shannon <Shannon.Johnson@alpla.com>; McEvoy Steve <steve.mcevoy@alpla.com>
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
All of the PLC tags in all of the PLCs have been updated and are ready to be validated by lenin and then alpla. They are the same structure as the
other next tags. Let me know if you have any questions
lenin.vera@leautomationandcontrol.com; Robert Nation <robert.nation@henkel.com>
<bmahanna@malisko.com>;
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
It looks as if we are now receiving the next next IDH information now from SAP on our side.
@Robert Nation will begin making that data usable and updating our message maps per line. This will require help from Lenin to make sure that he is receiving them correctly and ultimately make sure
that Alpla is receiving the same values.
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
lenin.vera@leautomationandcontrol.com; Robert Nation <robert.nation@henkel.com>
<mscott@malisko.com>; Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
This is something we’re still working on. It has been added to line 40 from out end but we’re waiting to validate those tags with our global SAP/digital
team. Once we are getting those data points, we can update the message map and provide those data point locations.
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
From:
Federico.Platt@alpla.com <Federico.Platt@alpla.com>
lenin.vera@leautomationandcontrol.com; Robert Nation <robert.nation@henkel.com>
<mscott@malisko.com>; Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: [EXT] RE: Vetro/ALPLA information verification
Thanks Brandon.
Has the data for the next-next order been added already? This is the other critical piece of information we need for the automatic batch handling / changeover.
Regards
Federico Platt
Sr Project Engineering Manager
+1 (678) 545-5565
a.bhrahmbhatt@vmeccanica.com; Colley Sam <Sam.Colley@alpla.com>;
lenin.vera@leautomationandcontrol.com; Robert Nation <robert.nation@henkel.com>
<mscott@malisko.com>; Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: RE: Vetro/ALPLA information verification
Federico, Now that the signal exchange has been validated, next steps I believe would be to verify that the message map we sent is what Vetro is
using and that you are looking at the correct data type for the SAP data. Whenever Sam returns please verify these signals with Vetro. A bottles remaining is being sent from lines 40, 41 and 42 currently thanks to Daniel which is a DINT so it does not need
to be converted to a string like the SAP information. Once verified, this can be rolled out to the other 3 OSBB fed lines.
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
lenin.vera@leautomationandcontrol.com; Robert Nation <robert.nation@henkel.com>
Matt Scott (Ext@malisko.com) <mscott@malisko.com>; Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>;
Brent Page <brent.page@henkel.com>; Douglas Arnold <douglas.arnold@henkel.com>
***
Subject: Vetro/ALPLA information verification
Yesterday, the data exchange on each OSBB-fed line was verified with Vetro.
During testing, we found that some values were being read correctly but in the wrong data type. Data from SAP goes through multiple conversions between
Henkel and Vetro, as outlined below. On the left side of the PLX communication module, Henkel’s data is in one format, and on the right side, it’s Alpla's. The process is as follows:
SAP sends data as a string.
Henkel converts that string into three DINTs for the PLX communication module.
The PLX then converts each DINT into two words.
Vetro must then convert this back to the original string value to match the exact data SAP initially sent.
During the testing, we observed that when comparing certain data points, Vetro was reading the correct DINT values. However, to retrieve the original
string value, an additional conversion is needed on their end.
On Line 41, all values were read back as string values, so every IDH, PO #, etc., matched exactly as Henkel receives them from SAP. On other lines,
like Line 40, they received the correct values, and the DINTs matched those being sent. However, some data points still need to be converted back into a string to be fully usable.
@Robert Nation, I think that the logic you created for line 40 with the new strapping
table can be implemented across the OSBB fed lines to give Alpla a more accurate running bottle count now. This is assuming the tank dimensions are the same across the lines. Once completed, Vetro will need to verify that their message map matches the one
provided to them and this should be resolved.
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
Matt Scott (Ext@malisko.com) <mscott@malisko.com>; Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
I think that will be a second part once this is figured out.
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
From:
Federico.Platt@alpla.com <Federico.Platt@alpla.com>
Matt Scott (Ext@malisko.com) <mscott@malisko.com>; Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
Thanks Brandon. All of these signals are what Henkel is sending to Vetro/Alpla. Are there any issues on what ALPLA/Vetro are sending to you? Or this will be the
2nd part of the exercise?
Regards
Federico Platt
Sr Project Engineering Manager
+1 (678) 545-5565
a.bhrahmbhatt@vmeccanica.com; Colley Sam <Sam.Colley@alpla.com>;
Matt Scott (Ext@malisko.com) <mscott@malisko.com>; Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
This is what we’ve generated based on our PLCs. This needs to be compared to what Vetro has and corrected where there are discrepancies. It’d be
easy enough to rule out a conversion error at the same time. I could force a value into a DINT on all Alpla fed lines and if Vetro receives the same value on their end then at least that possibility has been ruled out.
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
From:
Federico.Platt@alpla.com <Federico.Platt@alpla.com>
Matt Scott (Ext@malisko.com) <mscott@malisko.com>; Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
Do you have the latest message map that we should refer to? If you have seen issues already with Vetro, it is very likely that those issues have been transferred
to us.
Federico Platt
Sr Project Engineering Manager
+1 (678) 545-5565
a.bhrahmbhatt@vmeccanica.com; Colley Sam <Sam.Colley@alpla.com>;
Matt Scott (Ext@malisko.com) <mscott@malisko.com>; Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
No changes on our end but that’s what we need someone to tell us if every data point is inaccurate or if just certain data points. We need to understand
if this is an issue with the data map or if there is some dint/word conversion error taking place or even if there is something in between Alpla and Vetro that is incorrect. We are already seeing discrepancies between the the message maps we have versus
what Vetro has but firstly need to verify the conversion between data types is also not an issue.
From what I see on our end the data in our PLC is correct, so again that data may not be where Vetro is expecting it to be or there is something
else going on with the data type conversion.
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
From:
Federico.Platt@alpla.com <Federico.Platt@alpla.com>
Matt Scott (Ext@malisko.com) <mscott@malisko.com>; Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: [EXT] RE: Vetro/ALPLA information verification
Hi Brandon,
This request will require some time on our end to evaluate. Sam is out of office for 2 more weeks and I will need to find time in the next days if the need is urgent.
Has anything been changed in your end for the last couple of months, since we discussed the topic?
Regards
Federico Platt
Sr Project Engineering Manager
+1 (678) 545-5565
Platt Federico <Federico.Platt@alpla.com>; Colley Sam <Sam.Colley@alpla.com>;
David Busch <david.busch@henkel.com>; Matt Scott (Ext@malisko.com)
<mscott@malisko.com>; Brett Mahanna (Ext@malisko.com)
<bmahanna@malisko.com>
***
Subject: RE: Vetro/ALPLA information verification
Hi Federico or Sam, can you provide any feedback on what exactly is not coming thru correctly? Is it everything or only certain data?
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
***
Subject: Vetro/ALPLA information verification
Good morning.
Brandon is trying to validate the information which has been re-mapped from the SAP and MES systems to ALPLA to verify the change overs and current
status of bottles is correct and what ALPLA needs to finish their side of inventory controls for staging.
This isn’t really something we are willing to wait on until Lenin is onsite if he can check this remotely please schedule it.
It doesn’t necessarily need to be Lenin… can be any one of the programmers on your side whom may be qualified and know what to look for.
We are at a standstill until the adjusted information has been validated and we don’t need this to fall through the cracks again for another few
years.
Currently it is to validate that we are now transmitting the requested information that ALPLA is looking for which Brandon can validate exactly what
is being transferred.
Respective to time spent on validating the information if we need to pay for the time to ensure its captured, I am cleared to cover the additional
cost within an existing project.
As this has been an open issue for a number of years, and that we have the potential to close this item finally, please help Brandon validate the
information quickly.
David Busch
Sr Project Manager
Henkel Bowling Green, Ky
(Cell) 270-282-3818
-----Original Message-----
mscott@malisko.com; Brett Mahanna
***
Subject: RE: [EXT] Re: Vetro Contact
Lenin, Attached is the evaluation we've completed on all of the Alpla fed lines. We need to understand where Alpla is not receiving the correct data. From my understanding it sounds like everything coming thru is incorrect.
@Federico.Platt@alpla.com, can you confirm what specific data is incorrect or is it everything? I understand that some lines are not sending a bottles remaining, that is being worked on but first need to make sure that data is being transferred
from Henkel to Vetro correctly. If I remember, even the SAP IDH # is not being received correctly.
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
-----Original Message-----
***
Subject: Re: [EXT] Re: Vetro Contact
Yes, I can work with you on this issue, I can connect remotely. Alok told me about this situation. I will speak with him tomorrow to confirm my involvement.
Lenin Vera
FSE
+1 812 5602700
> On Oct 23, 2024, at 5:02 PM, Brandon B Miller <brandon.b.miller@henkel.com>
wrote:
>
> I'm not sure either. Is this something that we can work together on? Alok mentioned that I should reach out to you for this. I
do not know your ability to help verify remotely.
>
> ______________________________________
> Brandon Miller
> Capital Automation & Digitalization - Engineering
>
>
>
>
> -----Original Message-----
> From: L&E <lenin.vera@leautomationandcontrol.com>
> Sent: Wednesday, October 23, 2024 3:58 PM
> To: Brandon B Miller <brandon.b.miller@henkel.com>
> Cc: Matt Scott (Ext@malisko.com) <mscott@malisko.com>
> Subject: Re: [EXT] Re: Vetro Contact
>
> This message is from an EXTERNAL SENDER – be CAUTIOUS, particularly
> with links and attachments ________________________________
>
> ALPLA has not commented anything to me, I am not sure if they have spoken to anyone in Italy.
>
> Lenin Vera
> FSE
> +1 812 5602700
>
>> On Oct 23, 2024, at 2:30 PM, Brandon B Miller <brandon.b.miller@henkel.com>
wrote:
>>
>> Thank you Lenin. This ask stems from Alpla saying that they are not receiving accurate data from us. When comparing what they are
seeing to what we are sending there is some mix up somewhere. Have you gotten word of this from Alpla?
>>
>> Ultimately, we want to validate that you are receiving the same values as what we are sending again.
>>
>> ______________________________________
>> Brandon Miller
>> Capital Automation & Digitalization - Engineering
>>
>>
>>
>>
>> -----Original Message-----
>> From: L&E <lenin.vera@leautomationandcontrol.com>
>> Sent: Wednesday, October 23, 2024 12:02 PM
>> To: Brandon B Miller <brandon.b.miller@henkel.com>
>> Cc: Matt Scott (Ext@malisko.com) <mscott@malisko.com>
>> Subject: Re: [EXT] Re: Vetro Contact
>>
>> This message is from an EXTERNAL SENDER – be CAUTIOUS, particularly
>> with links and attachments ________________________________
>>
>> It is the same for all lines.
>>
>> Lenin Vera
>> FSE
>> +1 812 5602700
>>
>>>> On Oct 23, 2024, at 12:11 PM, Brandon B Miller <brandon.b.miller@henkel.com>
wrote:
|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
---
+ 5c1fa79b53f87f1f70de1fb1e1c47935
### NEXT2 - Data - ALPLA information verification
- 03-02-2025
Hello Sam,
I need to verify my understanding of the NEXT2 data requirements from ALPLA. HENKEL sends this data through the Malisko -> Prosoft system to the Q1 PLCs as three 12-character strings (PO_NUMBER, IDH_BTL, IDH_CON), which we label as d1-d9 in our software. This
data undergoes word-swapping on the Q1 but isn't further processed on the Supervisor. Therefore, on the supervisor, the data remains swapped and isn't reverted to its original form.
What does ALPLA need on the supervisor? Currently, there's no specific area for NEXT2 in the OPC served data, only in the Raw data section (marked as 3 in the attached image). Is the raw data from FromHenkel.STW.d1-d9 sufficient for your needs?
Lenin requested and was confirmed during last Monday's call that data integrity must be maintained from the HENKEL system to the Supervisor data. No changes to the OPC structure were discussed.
OPC Data served on the Supervisor PLC:
Best regards,
Miguel Angel Vera
External Automation Design Engineer
Vetromeccanica srl Smart Moving Solutions
Strada
Isolanda 26, 43024 Provazzano, Parma - Italy
---
+ ebe8558bee69aa2567af358f7705824c
### Automatic changeover trial
- 31-01-2025
Team,
There have been several emails with numerous people talking about the Vetro/Alpla/Henkel communications needed to perform the automatic batch changes. I would like to identify who needs to be included in this project and/or on copy. If
you have been included in this email and do not need to be on copy or invited to the meetings please let me know and I will remove your email address. Likewise if you see that I have missed someone that needs to be included, please let me know.
Sam – Does Autefa need to be involved and if so, who?
We had discussed a trial next week, however there are no changeovers during the Monday-Friday work week and we would prefer not to try out changes on Saturday.
So we need to coordinate the next good opportunity. I would also like to establish a core group who will be involved in the trials and changes.
I would like to set up a meeting early next week to discuss when we can actually align a trial with the Henkel production schedule.
Thanks,
Mit freundlichen Grüßen / Best regards
Shannon Johnson
Plant Manager
– BOW2
Alpla Inc.
377 Southwood Ct
Bowling Green, KY 42102
M: +1 (270) 619-0452
www.alpla.com
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
---
+ 534656dd41f6d25df1c1b17a328e34e5
### Re: [EXT] RE: Vetro/ALPLA information verification
- 19-12-2024
HelloMiguel, could you please let us know what the estimated time would be to complete this request?
Lenin VeraFSE
+1 812 5602700
On Dec 19, 2024, at 10:08 AM, steve.mcevoy@alpla.com wrote:

Hi Lenin
If you could get Italy to offer a feedback on expected timing that would be appreciated.
This piece of work is being pushed by Senior Leadership in ALPLA and HENKEL and we need to manage their expectations
Thanks in advance.
Steve
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
Hi Steve,
I don't have an estimated date; in Italy they are working on the changes that must be made in all the Q1 PLCs and in the supervisory system PLC. As a rule, when a change is to be made in the supervisory PLC, this change must be made in
Italy.
Lenin Vera
Filling & Process Machine Automation Engineer
+1 812 5602700
En miércoles, 18 de diciembre de 2024, 13:42:51 (-05:00), <steve.mcevoy@alpla.com> escribió:
Hi Lenin
Thanks for the update
Can you give any indication on timings for the changes needed ?
Thanks. Steve
a.bhrahmbhatt@vmeccanica.com; Platt Federico <Federico.Platt@alpla.com>; Colley Sam <Sam.Colley@alpla.com>;
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
| | You don't often get email from<br>lenin.vera@leautomationandcontrol.com.<br>Learn why this is important | |
|--|---------------------------------------------------------------------------------------------------------|--|
Hi Steve,
I have been busy this week; I requested help from Italy to make the modification in the PLCs. We have to change the variables di1 - di9 from DINT to SINT.
Thank you and I am sorry for the delay.
Lenin Vera
Filling & Process Machine Automation Engineer
+1 812 5602700
En lunes, 16 de diciembre de 2024, 12:15:11 (-05:00), <steve.mcevoy@alpla.com> escribió:
Hello Lenin & Shannon
What is the status please on the validation of the PLC tags
Can you provide an update by end of today please?
As we have a meeting with Henkel Procurement tomorrow morning
Many thanks. Steve
a.bhrahmbhatt@vmeccanica.com; Colley Sam <Sam.Colley@alpla.com>;
Johnson Shannon <Shannon.Johnson@alpla.com>; McEvoy Steve <steve.mcevoy@alpla.com>
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
All of the PLC tags in all of the PLCs have been updated and are ready to be validated by lenin and then alpla. They are the same structure as
the other next tags. Let me know if you have any questions
lenin.vera@leautomationandcontrol.com; Robert Nation <robert.nation@henkel.com>
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
It looks as if we are now receiving the next next IDH information now from SAP on our side.
@Robert Nation will begin making that data usable and updating our message maps per line. This will require help from Lenin to make sure that he is receiving them correctly and ultimately make sure
that Alpla is receiving the same values.
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
lenin.vera@leautomationandcontrol.com; Robert Nation <robert.nation@henkel.com>
Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
This is something we’re still working on. It has been added to line 40 from out end but we’re waiting to validate those tags with our global
SAP/digital team. Once we are getting those data points, we can update the message map and provide those data point locations.
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
From:
Federico.Platt@alpla.com <Federico.Platt@alpla.com>
lenin.vera@leautomationandcontrol.com; Robert Nation <robert.nation@henkel.com>
Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: [EXT] RE: Vetro/ALPLA information verification
Thanks Brandon.
Has the data for the next-next order been added already? This is the other critical piece of information we need for the automatic batch handling / changeover.
Regards
Federico Platt
Sr Project Engineering Manager
+1 (678) 545-5565
a.bhrahmbhatt@vmeccanica.com; Colley Sam <Sam.Colley@alpla.com>;
lenin.vera@leautomationandcontrol.com; Robert Nation <robert.nation@henkel.com>
Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: RE: Vetro/ALPLA information verification
Federico, Now that the signal exchange has been validated, next steps I believe would be to verify that the message map we sent is what Vetro
is using and that you are looking at the correct data type for the SAP data. Whenever Sam returns please verify these signals with Vetro. A bottles remaining is being sent from lines 40, 41 and 42 currently thanks to Daniel which is a DINT so it does not
need to be converted to a string like the SAP information. Once verified, this can be rolled out to the other 3 OSBB fed lines.
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
lenin.vera@leautomationandcontrol.com; Robert Nation <robert.nation@henkel.com>
(Ext@malisko.com) <mscott@malisko.com>; Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>;
Brent Page <brent.page@henkel.com>; Douglas Arnold <douglas.arnold@henkel.com>
***
Subject: Vetro/ALPLA information verification
Yesterday, the data exchange on each OSBB-fed line was verified with Vetro.
During testing, we found that some values were being read correctly but in the wrong data type. Data from SAP goes through multiple conversions
between Henkel and Vetro, as outlined below. On the left side of the PLX communication module, Henkel’s data is in one format, and on the right side, it’s Alpla's. The process is as follows:
SAP sends data as a string.
Henkel converts that string into three DINTs for the PLX communication module.
The PLX then converts each DINT into two words.
Vetro must then convert this back to the original string value to match the exact data SAP initially sent.
During the testing, we observed that when comparing certain data points, Vetro was reading the correct DINT values. However, to retrieve the original
string value, an additional conversion is needed on their end.
On Line 41, all values were read back as string values, so every IDH, PO #, etc., matched exactly as Henkel receives them from SAP. On other lines,
like Line 40, they received the correct values, and the DINTs matched those being sent. However, some data points still need to be converted back into a string to be fully usable.
@Robert Nation, I think that the logic you created for line 40 with the new strapping
table can be implemented across the OSBB fed lines to give Alpla a more accurate running bottle count now. This is assuming the tank dimensions are the same across the lines. Once completed, Vetro will need to verify that their message map matches the one
provided to them and this should be resolved.
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
(Ext@malisko.com) <mscott@malisko.com>; Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
I think that will be a second part once this is figured out.
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
From:
Federico.Platt@alpla.com <Federico.Platt@alpla.com>
(Ext@malisko.com) <mscott@malisko.com>; Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
Thanks Brandon. All of these signals are what Henkel is sending to Vetro/Alpla. Are there any issues on what ALPLA/Vetro are sending to you? Or this will be the 2nd part of the exercise?
Regards
Federico Platt
Sr Project Engineering Manager
+1 (678) 545-5565
a.bhrahmbhatt@vmeccanica.com; Colley Sam <Sam.Colley@alpla.com>;
(Ext@malisko.com) <mscott@malisko.com>; Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
This is what we’ve generated based on our PLCs. This needs to be compared to what Vetro has and corrected where there are discrepancies. It’d
be easy enough to rule out a conversion error at the same time. I could force a value into a DINT on all Alpla fed lines and if Vetro receives the same value on their end then at least that possibility has been ruled out.
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
From:
Federico.Platt@alpla.com <Federico.Platt@alpla.com>
(Ext@malisko.com) <mscott@malisko.com>; Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
Do you have the latest message map that we should refer to? If you have seen issues already with Vetro, it is very likely that those issues have been transferred to us.
Federico Platt
Sr Project Engineering Manager
+1 (678) 545-5565
a.bhrahmbhatt@vmeccanica.com; Colley Sam <Sam.Colley@alpla.com>;
(Ext@malisko.com) <mscott@malisko.com>; Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: RE: [EXT] RE: Vetro/ALPLA information verification
No changes on our end but that’s what we need someone to tell us if every data point is inaccurate or if just certain data points. We need to
understand if this is an issue with the data map or if there is some dint/word conversion error taking place or even if there is something in between Alpla and Vetro that is incorrect. We are already seeing discrepancies between the the message maps we have
versus what Vetro has but firstly need to verify the conversion between data types is also not an issue.
From what I see on our end the data in our PLC is correct, so again that data may not be where Vetro is expecting it to be or there is something
else going on with the data type conversion.
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
From:
Federico.Platt@alpla.com <Federico.Platt@alpla.com>
(Ext@malisko.com) <mscott@malisko.com>; Brett Mahanna (Ext@malisko.com) <bmahanna@malisko.com>
***
Subject: [EXT] RE: Vetro/ALPLA information verification
Hi Brandon,
This request will require some time on our end to evaluate. Sam is out of office for 2 more weeks and I will need to find time in the next days if the need is urgent.
Has anything been changed in your end for the last couple of months, since we discussed the topic?
Regards
Federico Platt
Sr Project Engineering Manager
+1 (678) 545-5565
Platt Federico <Federico.Platt@alpla.com>;
Colley Sam <Sam.Colley@alpla.com>;
David Busch <david.busch@henkel.com>;
Matt Scott (Ext@malisko.com)
<mscott@malisko.com>;
Brett Mahanna (Ext@malisko.com)
<bmahanna@malisko.com>
***
Subject: RE: Vetro/ALPLA information verification
Hi Federico or Sam, can you provide any feedback on what exactly is not coming thru correctly? Is it everything or only certain data?
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
***
Subject: Vetro/ALPLA information verification
Good morning.
Brandon is trying to validate the information which has been re-mapped from the SAP and MES systems to ALPLA to verify the change overs and current
status of bottles is correct and what ALPLA needs to finish their side of inventory controls for staging.
This isn’t really something we are willing to wait on until Lenin is onsite if he can check this remotely please schedule it.
It doesn’t necessarily need to be Lenin… can be any one of the programmers on your side whom may be qualified and know what to look for.
We are at a standstill until the adjusted information has been validated and we don’t need this to fall through the cracks again for another few
years.
Currently it is to validate that we are now transmitting the requested information that ALPLA is looking for which Brandon can validate exactly
what is being transferred.
Respective to time spent on validating the information if we need to pay for the time to ensure its captured, I am cleared to cover the additional
cost within an existing project.
As this has been an open issue for a number of years, and that we have the potential to close this item finally, please help Brandon validate
the information quickly.
David Busch
Sr Project Manager
Henkel Bowling Green, Ky
(Cell) 270-282-3818
-----Original Message-----
mscott@malisko.com; Brett Mahanna
***
Subject: RE: [EXT] Re: Vetro Contact
Lenin, Attached is the evaluation we've completed on all of the Alpla fed lines. We need to understand where Alpla is not receiving the correct data. From my understanding it sounds like
everything coming thru is incorrect.
@Federico.Platt@alpla.com, can you confirm what specific data is incorrect or is it everything? I understand that some lines are not sending a bottles remaining, that is being worked on
but first need to make sure that data is being transferred from Henkel to Vetro correctly. If I remember, even the SAP IDH # is not being received correctly.
______________________________________
Brandon Miller
Capital Automation & Digitalization - Engineering
-----Original Message-----
***
Subject: Re: [EXT] Re: Vetro Contact
Yes, I can work with you on this issue, I can connect remotely. Alok told me about this situation. I will speak with him tomorrow to confirm my involvement.
Lenin Vera
FSE
+1 812 5602700
> On Oct 23, 2024, at 5:02 PM, Brandon B Miller <brandon.b.miller@henkel.com>
wrote:
>
> I'm not sure either. Is this something that we can work together on? Alok mentioned
that I should reach out to you for this. I do not know your ability to help verify remotely.
>
> ______________________________________
> Brandon Miller
> Capital Automation & Digitalization - Engineering
>
>
>
>
> -----Original Message-----
> From: L&E <lenin.vera@leautomationandcontrol.com>
> Sent: Wednesday, October 23, 2024 3:58 PM
> To: Brandon B Miller <brandon.b.miller@henkel.com>
> Cc: Matt Scott (Ext@malisko.com) <mscott@malisko.com>
> Subject: Re: [EXT] Re: Vetro Contact
>
> This message is from an EXTERNAL SENDER – be CAUTIOUS, particularly
> with links and attachments ________________________________
>
> ALPLA has not commented anything to me, I am not sure if they have spoken to anyone in Italy.
>
> Lenin Vera
> FSE
> +1 812 5602700
>
>> On Oct 23, 2024, at 2:30 PM, Brandon B Miller <brandon.b.miller@henkel.com>
wrote:
>>
>>
Thank you Lenin. This ask stems from Alpla saying that they are not receiving accurate data from us. When comparing what they are seeing to what we are sending
there is some mix up somewhere. Have you gotten word of this from Alpla?
>>
>> Ultimately, we want to validate that you are receiving the same values as what we are sending again.
>>
>> ______________________________________
>> Brandon Miller
>> Capital Automation & Digitalization - Engineering
>>
>>
>>
>>
>> -----Original Message-----
>> From: L&E <lenin.vera@leautomationandcontrol.com>
>> Sent: Wednesday, October 23, 2024 12:02 PM
>> To: Brandon B Miller <brandon.b.miller@henkel.com>
>> Cc: Matt Scott (Ext@malisko.com) <mscott@malisko.com>
>> Subject: Re: [EXT] Re: Vetro Contact
>>
>> This message is from an EXTERNAL SENDER – be CAUTIOUS, particularly
>> with links and attachments ________________________________
>>
>> It is the same for all lines.
>>
>> Lenin Vera
>> FSE
>> +1 812 5602700
>>
>>>> On Oct 23, 2024, at 12:11 PM, Brandon B Miller <brandon.b.miller@henkel.com>
wrote:
|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
---
+ e24d10cb7260612292f2979ea382bf80
### I: 9.3061-TLO26-L42 automatic change over test
- 04-01-2024
Hi Federico,
We corrected the error on
IDH_BTL_NEXT, now it will only validate the signal when a match is found.
Regarding TL27-4L41 it was only a text error, supervision is pulling the alarms from TL27-4L40.
We remain available for further requests.
Thank you and kind regards,
Max
From:
Federico.Platt@alpla.com <Federico.Platt@alpla.com>
Matteo Canetti <m.canetti@vetromeccanica.it>; Massimiliano Petrosino <m.petrosino@vetromeccanica.it>;
***
Subject: RE: 9.3061-TLO26-L42 automatic change over test
Max,
I do have 2 requests now that you have your automation team on copy. This list will grow as we keep checking your system bugs on detail.
Henkel is receiving a IDH_BTL_NEXT confirmation all the time. You are not really confirming if the number is valid, you just send the confirmation signal all the time, even when no
data is being sent.
On supervisor panel, we are not receiving data from TL27-L40. The actual legend says “TLO27 – 4L41” which is not right. It is not populating the alarms from the right HMI.
Federico Platt
Sr Project Manager - Engineering
+1 (678) 545-5565
-----Original Message-----
Massimiliano Petrosino <m.petrosino@vetromeccanica.it>
***
Subject: 9.3061-TLO26-L42 automatic change over test
** INFO: External Email ** ALPLA Corp-IT Systems
Good afternoon Federico,
We would like to test the automatic change over several times tomorrow while line 42 is down.
In order to test Henkel should simulate batch code signal and AUTEFA should as well complete the change over. Do you think it would be possible tomorrow from 8 till 11 AM?
Thank you for your cooperation,
Max
---
+ b48ae2825aa32aa86a19d448a6635977
### I: Alpla BOW: Batch handling 9.3040-3074 ALPLA BG
- 04-01-2024
Luca Brarda <l.brarda@vetromeccanica.it>; Obert Peter (ASG) <Peter.Obert@autefa.com>
Peter included now as well.
Max
Ureda Sudheesh (ASG-Extern) <Sudheesh.Ureda@autefa.com>; Andrea Attolini <a.attolini@vetromeccanica.it>; Luca Brarda <l.brarda@vetromeccanica.it>
Priorità: Alta
Good afternoon,
ALPLA is pushing to use the number with amount of bottles passing through bottle turner to calculate amount of bottles passing on the line.
Since this signal has been agreed last year I believe you should prioritzie this on site and tell ALPLA directly if there is any issue sharing this value.
Thank you and kind regards,
Max
Ureda Sudheesh (ASG-Extern) <Sudheesh.Ureda@autefa.com>; Andrea Attolini <a.attolini@vetromeccanica.it>; Luca Brarda <l.brarda@vetromeccanica.it>
Dear All,
I confirm that from Wednesday June 17th our programmer Wilbert will be available on site to follow up batch handling commissioning.
Kind regards,
Max
Ureda Sudheesh (ASG-Extern) <Sudheesh.Ureda@autefa.com>; Andrea Attolini <a.attolini@vetromeccanica.it>
Dear All,
I believe the following points are not solved yet.
Furthermore we are not receiving a number of bottles produced by AUTEFA other than 0. ALPLA is pushing us to sort this point within this week, perhaps the type of variable is not correct.
Perhaps we could have a call on Wednesday to discuss these?
Thank you and kind regards,
Max
Ureda Sudheesh (ASG-Extern) <Sudheesh.Ureda@autefa.com>
Hello Max,
Today while checking the information received from Supervision PLC,
We noticed 3 discrepancies from Vetro,( as per info from Wilbert and data received)
1: The Target count received by Autefa is remaining bottles... Where as we expect following a: Total target count and not remaining count....
b: And 0 target count as "batch finish" as a confirmation, when Henkel receives all required bottles count
2: No next batch+1 info received by Autefa (as per definition we need this data for organised supply)
3: The ejected bottles along line, after merger are not added in total target from time to time(???)
Right now we are receiving legitimate data for L25, L40, L42 (3 lines)
Best regards,
Sachin Dahane
---
+ 65b06d9edf0c5c3af15b15b276aa0139
### I: Alpla BOW: Batch Handling Issue for TG10 & TG20
- 04-01-2024
Fritzsche-Zoeschinger Martin (ASG) <Martin.Fritzsche-Zoeschinger@autefa.com>
Hello Max/ Willbert,
We are still not getting correct data in TG10 (Batch Data) and response to TG20 ( Accept is not received even if selected combination is correct).
That was the reason we had trouble yesterday delivering bottles on Line 43 from TLO24.
Also, now we cannot put TLO27 on line40 because we do not get "Accept" from your end, creating difficulty in "counting unloaded" bottles and supplying same to you. We observed that this TG20 Telegram sometimes work fine, but
sometimes its not accepted, as well as no error is given for rejection ...(error number remained 0)
Please look into this ASAP. Thanks.
The TG10 status is given below for your ready reference.
| Recorded at 22nd June 01:00 | L23 | L25 | L40 | L41 | L42 | L43 |
|--------------------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|------------------------|
| | TLO 21 | TLO 22 | TLO 27 | TLO 28 | TLO 26 | TLO 24 |
| Last Telegram INFO Received on | 21st June<br>at 20:29 | 17th June<br>at 22:10 | 22nd June<br>at 15:08 | 21st June<br>at 17:10 | 21st June<br>at 23:17 | 10th April<br>at 10:18 |
| Actual_Batch_ID[1] | '0' | '0' | '0' | '0' | '0' | ' ' |
| Actual_Batch_ID[2] | '0' | '0' | '0' | '0' | '0' | ' ' |
| Actual_Batch_ID[3] | '2' | '2' | '2' | '2' | '2' | ' ' |
| Actual_Batch_ID[4] | '0' | '0' | '0' | '0' | '0' | ' ' |
| Actual_Batch_ID[5] | '0' | '0' | '0' | '0' | '0' | ' ' |
| Actual_Batch_ID[6] | '4' | '4' | '4' | '4' | '4' | ' ' |
| Actual_Batch_ID[7] | '2' | '2' | '2' | '2' | '2' | ' ' |
| Actual_Batch_ID[8] | '7' | '5' | '6' | '5' | '6' | ' ' |
| Actual_Batch_ID[9] | '5' | '2' | '4' | '3' | '4' | ' ' |
| Actual_Batch_ID[10] | '3' | '9' | '6' | '1' | '6' | ' ' |
| Actual_Batch_ID[11] | '8' | '7' | '2' | '5' | '3' | ' ' |
| Actual_Batch_ID[12] | '7' | '9' | '6' | '8' | '8' | ' ' |
| | | | | | | |
| Active Batch Target | 138 | -5639 | 71659 | 35129 | 55747 | 59912 |
| Active Batch AVID | 0 | 105 | 186 | 167 | 207 | 0 |
| | | | | | | |
| Next_Batch_ID[1] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Batch_ID[2] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Batch_ID[3] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Batch_ID[4] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Batch_ID[5] | ' ' | ' ' | ' | ' ' | ' ' | ' ' |
| Next_Batch_ID[6] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Batch_ID[7] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Batch_ID[8] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Batch_ID[9] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Batch_ID[10] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Batch_ID[11] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Batch_ID[12] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| | | | | | | |
| Next Batch Target | 25640 | 0 | 23660 | 0 | 65484 | 0 |
| Next Batch AVID | 197 | 105 | 186 | 109 | 216 | 0 |
| | | | | | | |
| Next_Next+1_Batch_ID[1] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Next+1_Batch_ID[2] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Next+1_Batch_ID[3] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Next+1_Batch_ID[4] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Next+1_Batch_ID[5] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Next+1_Batch_ID[6] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Next+1_Batch_ID[7] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Next+1_Batch_ID[8] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Next+1_Batch_ID[9] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Next+1_Batch_ID[10] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Next+1_Batch_ID[11] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| Next_Next+1_Batch_ID[12] | ' ' | ' ' | ' ' | ' ' | ' ' | ' ' |
| | | | | | | |
| Next_Next+1_Batch Target | 0 | 0 | 0 | 0 | 0 | 0 |
| Next_Next+1_Batch AVID | 0 | 0 | 0 | 0 | 0 | 0 |
| | | | | | | |
Best regards,
Sachin Dahane
---
+ b8a392590c2ec14bdc907df9ed6bfde1
### I: Bottle counters / Batch handling
- 04-01-2024
Hi Max,
Replaying to your last message from this morning,
Bottle counters:
-still missing install the counter after lowerator line 40, 41 and 42.
-pending modification SW to add the new counters in line 40, 41 and 42 in Henkel side.
-only some counter have the new bracket, I think all of them have to be with the new bracket to avoid that the sensors move and do bad counting,
-still pending confirm how are going to work the counters, if we have to reset all of them to zero or not, I saw that the counter from filler till this moment is not reset, please confirm this to modify the software if
is necessary.
-still pending confirm TG61 with the right value of bottles load from Autefa in TLO22 and TLO21.
Changeover/batch handling:
-Now in logic we see if is a complete changeover (different family number) or same family product with a different color/spigot/dose cup (using Product ID when is different) or same bottle but different batch number,
that´s mean that we have to start the counters for a new batch, still pending check the last changes did for this.
-Add some signals to know when the EMD guides and lifter guides are in position before send changeover done to Henkel.
-still pending find a way to avoid that merger finish the empting before Bottle turner send all the bottles, we don´t know when the BT is and TLO is empty, now the emptying in merger start when we receive the remaining
bottle to fill in 0 from Henkel, so I think that is better have a signal that the BT is empty and in this point start the emptying in the merger.
-Last time when we did a test, Q2 didn´t start the changeover, now Q2 in 40, 41 and 42 has the same modification that Q1 and also in this case, Q2 have to wait that Q1 is empty to start the emptying in Q2 and in this
way avoid that conveyors before bottle counter stay with bottles.
-change signals of line empty and change over done to a SR memory, in this way the cycle machine have to complete all the steps in the same order in both panels and send this right signals to Henkel when have to be, before
the logic let that Q1 finish the changeover first and when finish by the conditions start again the empting and never send the signals to Henkel, this change is still pending to check.
I attached a file that with the step to follow for the changeover with Henkel as reference, the original version was send to me for Federico, I modify a little bit to let it according to the last changes did in SW.
Regards,
Wilbert Dzul
### Adjuntos
- [[Changeover process map v1.xlsx]]
---
+ d9191d159975cc0af2bf6a685ff5b6bc
### I: OPC-UA interface Vetro - Bowling Green 2
- 04-01-2024
Dear Christoph,
Thank you for describing step by step change of batch procedure.
We are modifyiing the software to follow exactly below procedure.
As agreed with Federico today the min accumulated bottles at the infeed of labeler and filler necessary for labeler and filler to work will not be take into account in the Vetromeccanica automatic
batch handling and change over procedure but AUTEFA will have to consideri t and sen additional bottles.
Siegrfied hope you are doing well. As per today ALPLA is still not writing the list fo SKU and AV in our supervision PLC memory therefore we are able to process HENKEL SKU in automatic.
Attached email for reference. This is quite urgent in order to start processing SKU.
Thank you and kind regards,
Max
Dear Max,
For the batch change and reset of the counters the process should be following:
Same bottle at next batch:
We will not purge the line from the bottles.
Manual confirmation ready for next batch -> set counter to 0
If we have a new bottle for the next batch:
Run until batch end
Line clearance
Manual confirmation that line is clear -> set counter to 0
Change over starts
Manual acknowledgement that changeover is completed, and line is ready for new bottles -> start of bottle count and start to send new bottle from TLO
As already agreed, the physically counter will not be reset to 0 it will keep counting up until. For example, if counter is 232,323,232 it stays at this number at the batch end and start of the new
batch.
Thanks
CK
***
Subject: R: OPC-UA interface Vetro - Bowling Green 2
Importance: High
** INFO: External Email ** ALPLA
Corp-IT Systems
Dear Christoph,
Thank you for your prompt respone!
I sincerely hope you enjoyed Christmas holidays and had a great start of 2021!
Going back to change over and counter reset topics we prepared attached excel sheet, this may help clarify each single step with HENKEL as well.
Furthermore take the chance to bring to your attention the need of completion of 3 important steps before we can proceed with automatic batch handling on the lines:
Confirmation of change over procedure and counters reset as per attachedALPLA sharing fully updated chart with SKU relating to article variant number and article variant description in the Vetromeccanica supervision data structure
Testing thoroughly on site communication with AUTEFA for automatic batch handling
I will be back from vacation on Monday January 11th but will forward your answer to my colleagues on this point. Tomorrow we will be closed due to national holiday.
Thank you and kind regards,
Max
Dear Max.
We are not planning to rest the counter until we have the max accumulated numbers reached.
The other two points are not needed since we have a counter from Henkel what indicated the still needed bottles before we can change over.
You will use this number to let Autefa know when we will push the last tray since you know the total amount of bottes on the conveyors.
We always will have some bottles left on the conveyor since we need to ensure that Henkel can empty the tank.
Best regards
CK
***
Subject: RE: OPC-UA interface Vetro - Bowling Green 2
Dear Max,
Let me check these points. Hope to have an answer still this week.
Best regards
CK
***
Subject: R: OPC-UA interface Vetro - Bowling Green 2
Importance: High
** INFO: External Email ** ALPLA
Corp-IT Systems
Good afternoon Christoph,
I would need a confirmation about when to reset counter in automatic mode for batch handling.
Based on your previous experience perhaps you can answer easily.
Automatic mode – signal counter reset from Henkel when switching to new batch
à pop up on Vetro HMI to ackwnoledge new batch (reset counter when operator press okay)
Furthermore we suggest to agree on procedure to empty the line when running last bottles on HENKEL side to avoid manual take out of bottles from conveyors:
Labeler – operator presses button on labeler HMI to by pass minimum bottles accumulationFiller – operator presses button on labeler HMI to by pass minimum bottles accumulation
Could we have a call tomorrow to go through these points? Perhaps you may answer all our questions or bring up furhter questions on these points.
Apologies for the late notice but since I am back in the office I am finally able to discuss face to face some openstanding points from our automation department.
Thank you and kind regards,
Max
Hi Carlo !
We are now daily reporting the Countervalues of TL27.
I recognized that counter SideGripDosingbelt was resetted suddenly on Monday from 443606 to 114.
Now since then counter SideGripDosingbelt does not really count anymore but FillerCount does count.
Can you explain this obsvervations ?
KR
Sigi Bereuter
Corporate IT
Head of Software Development
ALPLA Hard
Mockenstraße 34, A-6971 Hard
T: +43 / 5574 / 602-436
F: +43 / 5574 / 62017-139
M: +43 / 664 / 88931443
_______________________________________________________________
Alpla Werke Alwin Lehner GmbH & Co KG – Allmendstraße 81 – A-6971 Hard
Firmenbuchgericht LG Feldkirch, Firmenbuchnummer FN 13422 p
***
Subject: R: OPC-UA interface Vetro - Bowling Green 2
** INFO: External Email ** ALPLA
Corp-IT Systems
Good morning,
no for the moment the "BatchLast" is not updated by the lines, as soon as it is implemented I will inform you.
Best regards,
CF
Carlo Felici
Automation Development Manager
Vetromeccanica srl
Glass Packaging Solutions
P
|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
Hi Carlo !
Thanks for the update we can see the new structure in usbow2, we already did the necessary changes on our Scada System.
Will the BatchLast already be update with data from BatchActual once Batch changes happens and what is the trigger
for updating BatchLast ?
Sigi Bereuter
Corporate IT
Head of Software Development
ALPLA Hard
Mockenstraße 34, A-6971 Hard
T: +43 / 5574 / 602-436
F: +43 / 5574 / 62017-139
M: +43 / 664 / 88931443
_______________________________________________________________
Alpla Werke Alwin Lehner GmbH & Co KG – Allmendstraße 81 – A-6971 Hard
Firmenbuchgericht LG Feldkirch, Firmenbuchnummer FN 13422 p
Platt Federico <Federico.Platt@alpla.com>
***
Subject: [WARNING: ATTACHMENT UNSCANNED]OPC-UA interface Vetro - Bowling Green 2
** INFO: External Email ** ALPLA
Corp-IT Systems
Good morning,
attached an update of the OPC structures in which I have:
added as per your request the "batchLast" structure with the same data of the "Actual" plus the two values of the "DosignBelt" and "InfeedFiller" counters.
I removed the useless "Istance" "St" from the "ToAlplaStatusLine" structure.
added information for backup lines and TL26.
in addition these are not 2 "mergers" but the two inputs of the same merger
there are 4 "QE" structures which represent the maximum number of electrical panels present for each line,
for example in the TL28 which has only one electrical panel only the "QE1" structure will be considered,
for the TL22 which has 4 they will be considered all structures,
this is the "divider" present only on the TL22
"Combiner" present only on the TL22
"BottlesTurner" managed by Vetromeccanica present only on the TL21
Best regards,
CF
Carlo Felici
Automation Development Manager
Vetromeccanica srl
Glass Packaging Solutions
P
|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
liable for any damages, whatever their nature, arising out of transmission failures, viruses, external influence, delays and the like.
We deliver and order solely on the basis of our General Terms and Conditions of Sale and Delivery respectively of Purchase set forth in
www.alpla.com/en/gtc-listing/gtc, which both contain a venue clause and an arbitration clause. Contradictory commercial terms and conditions shall not apply.
jede Haftung für Schäden aus Übertragungsfehlern, Viren, fremden Einflüssen, Verzögerungen und dergleichen aus.
www.alpla.com/de/gtc-listing/agb zu finden sind. Sämtliche Allgemeinen Geschäftsbedingungen enthalten Bestimmungen hinsichtlich Gerichtsstand und Schiedsgericht. Widersprüchliche Geschäftsbedingungen kommen
nicht zur Anwendung.
### Adjuntos
- [[AlplaProd_Articles - VM.xlsx]]
---
+ aaa32d94c6e5adb61345066788744397
### R: 9.3040-3074 ALPLA data exchange with HENKEL - line commisioning
- 29-10-2020
Dear All,
We confirm the following code sas per attached e-mail) are matching with what we agreed back in May therefore we can process P/N (customer article) but ALPLA should write in our supervision PLC
a list where customer article is associated to AV, AV Desc, Product Family as agreed.
This list will be constantly editable by ALPLA on a persistent memory as agreed in order for Vetromeccanica to handle new customer articles except for new formats (new bottle shapes) which will
require new recipes and commissioning first.
As per now we only have an excel list dated May 2020 which we cannot use for batch handling.
| ALPLA AV | Blank Bottle P/N |
|----------|------------------|
| 184 | 2638879 |
| 253 | 2688129 |
| 102 | 2638876 |
Agreed:
AV (must be forwared to Autefa, must be shown on your HMI’s)
AV Desc (must be shown on you HMI’s)
Product Family (must be used by Vetro to select right Recipe)
Customer article Number (used by Vetro to find matching AV)
I know that our software engineer Wilbert has been in contact also today with Malisko and we are moving forward. Kindkly ask to be in the loop of communciation with our software engineers.
Thank you and kind regards,
Maximilian Rossi
Andrea Attolini <a.attolini@vetromeccanica.it>; Marco Bertagnolo <m.bertagnolo@vetromeccanica.it>; Giovanni Friggeri <g.friggeri@vetromeccanica.it>
Dear Federico,
In order to increase efficiency of line 25 and 40 it is quite clear since months that we need to work in automatic with speed synchronization between labeler and filler.
At the moment we receive the following data from line 40 only:
From labeller one speed value of 350, does it mean 21.000 bph or 21.000 mm/min ?
From filler only machine cycle on
Looking forward to your support on this topic. We are fully available for a meeting on site with MCC and RONCHI to move forward.
Thank you and kind regards,
Max
### Adjuntos
- [[AlplaProd_Articles - VM.xlsx]]
---
+ 426b39b4f49078cb1c38f6b115d94c67
### FW: Post Operations Meeting Logistics Update - 10/28/2020
- 28-10-2020
***
Subject: Post Operations Meeting Logistics Update - 10/28/2020
All,
Good Afternoon. Please find below an update on the current fill plans and production plans. Please note there are two change-overs scheduled for Henkel lines in the next 12 hours.
ALPLA Production Plan
Line7 Running LF04B H All Blue all week.
Line 8 Running SP05 with color change-overs. Currently running White with a change-over to Green expected on Wednesday/Thursday
Line 9 Down waiting on color for Beluga Orange.
Henkel Fill Schedule
Line 25 running 24 hours per day Monday 6:00 AM – Saturday 6:00 AM. Expected change-over to All Blue on
Wednesday (10/28/2020)
| Line | | Program | Color | ALPLA AV | Blank Bottle P/N | Desc. | Total | Bottles Per Stack | Total Stacks for Run | Day | Expected Change-over Date and Time |
|------|--|---------|-----------|----------|------------------|-----------------------------|---------|-------------------|----------------------|-----------|------------------------------------|
| 3L25 | | LF04B H | All White | 105 | 2638861 | HDPE LF04B H 40oz All White | 39,126 | 2,464 | 15.88 | Wednesday | 10/28/20 4:01 PM |
| 3L25 | | LF04B H | All Blue | 126 | 2638860 | HDPE LF04B H 40oz All Blue | 403,468 | 2,464 | 163.75 | Tuesday | 11/3/20 12:21 PM |
Line 40 is running Sunday at 8:00 PM – Friday at 4:00 PM 20 hours per day. Currently running Pearl Blue with expected change-over to Cuddle Blue on
Wednesday (10/28/2020)
| Line | | Program | Color | ALPLA AV | Blank Bottle P/N | Desc. | Total | Bottles Per Stack | Total Stacks for Run | Day | Expected Change-over Date and Time |
|------|--|---------|-------------|----------|------------------|-----------------------------|---------|-------------------|----------------------|-----------|------------------------------------|
| 3L40 | | SP05 | Pearl Blue | 184 | 2638879 | HDPE SP05 100oz Pearl Blue | 44,000 | 1,260 | 34.92 | Wednesday | 10/28/20 10:40 PM |
| 3L40 | | SP05 | Cuddle Blue | 253 | 2688129 | HDPE SP05 100oz Cuddle Blue | 127,062 | 1,260 | 100.84 | Sunday | 11/1/20 11:01 PM |
| 3L40 | | SP05 | White | 102 | 2638876 | HDPE SP05 100oz White | 72,011 | 1,260 | 55.49 | Tuesday | 11/3/20 1:01 AM |
If you have any questions or concerns, please let me know.
Best regards,
William Bucklew
Logistics Manager
Alpla Inc.
377 Southwood Court – New Address
Bowling Green, KY 42101 USA
T: +
M: +1 (270) 421-5476
www.alpla.com
liable for any damages, whatever their nature, arising out of transmission failures, viruses, external influence, delays and the like.
We deliver and order solely on the basis of our General Terms and Conditions of Sale and Delivery respectively of Purchase set forth in
www.alpla.com/en/gtc-listing/gtc, which both contain a venue clause and an arbitration clause. Contradictory commercial terms and conditions shall not apply.
jede Haftung für Schäden aus Übertragungsfehlern, Viren, fremden Einflüssen, Verzögerungen und dergleichen aus.
www.alpla.com/de/gtc-listing/agb zu finden sind. Sämtliche Allgemeinen Geschäftsbedingungen enthalten Bestimmungen hinsichtlich Gerichtsstand und Schiedsgericht. Widersprüchliche Geschäftsbedingungen kommen
nicht zur Anwendung.
---
+ 5aeb89b3c5bfb98c645b9101e3487b13
### R: Alpla - Vetro SKU via OPC 9.3040-3074
- 21-05-2020
Dear Siegfried,
Thank you for your prompt response.
Hereby our feedback:
We confirm we accept fully your SKU structure (see below image) but please specify the number of characters for AV description, we considered
for now 36 and needs to be defined. Waiting for your confirmation of structure and characters.The list as per your request will remain persistent, it means it will remain saved on our supervision PLC even after restart of our superivision
control cabinet or shut down of your SCADA. We underline we will not do any writing on this list, only ALPLA will edit this list through SCADA.Whenever we will receive SKU for new batch from one of 6 HENKEL line supervision PLC we will forward AV to AUTEFA and show on all Vetromeccanica
HMI of that line a pop-up request for new batch. At that point operator will have to confirm manually on all HMIs of that line:
Checked line is clear from bottles - confirm
Change over is started – confirm (when operator confirms change over is started the PLC automatically loads recipe corresponding to SKU,
shows AV and AV Desc on that precise HMI and changes guide width) Change over is completed – confirm
If you confirm the attached list(no changes from yours) including simplified association between AV Desc and Product family clearly visibile below just for sake of quick overview we will start shipping
control cabinets HMI with correct numbering of recipes avoiding extra work on site (20 control cabinets have been shipeed already with different numbering than below) plus enable visibility of AV and AV Desc on HMI. We have a shipping of 8 control cabinets
next week therefore your soonest confirmation is highly appreciated.
| Beluga | 8 |
|--------|----|
| H13 | 9 |
| H14 | 17 |
| H96 | 18 |
| LF04B | 6 |
| LF10B | 7 |
| SP1 | 5 |
| Sp2 | 14 |
| Sp5 | 3 |
| Sp12 | 13 |
| Sp14 | 15 |
| Sp17 | 4 |
| Sp26 | 16 |
For any question please do not hesitate to call me.
Thank you for your cooperation and kind regards,
Maximilian Rossi
Hi Maximilian !
As mentioned, attached you can find the whole SKU List.
For only those Fields are relevant:
AV (must be forwared to Autefa, must be shown on your HMI’s)
AV Desc
(must be shown on you HMI’s)
Product Family
(must be used by Vetro to select right Recipe)
Customer article Number
(used by Vetro to find matching AV)
Via OPC Ua we would expect form you to provide a Variable with a structure like this:
ALPLA_SKU : STRUCT
AV : DINT;
AvDesc : STRING;
ProductFamily : DINT;
CustomerNumber: DINT;
END_STRUCT;
Finally you define a DB with this Variabel inside:
AlplaSkuList Array[250] of ALPLA_SKU;
Sigi Bereuter
Corporate IT
Head of Software Development
ALPLA Hard
Mockenstraße 34, A-6971 Hard
T: +43 / 5574 / 602-436
F: +43 / 5574 / 62017-139
M: +43 / 664 / 88931443
_______________________________________________________________
Alpla Werke Alwin Lehner GmbH & Co KG – Allmendstraße 81 – A-6971 Hard
Firmenbuchgericht LG Feldkirch, Firmenbuchnummer FN 13422 p
***
Subject: R: minutes - update data points Vetromeccanica - Bowling Green 2 9.3040-3074
** INFO: External Email **
Do not click links, open attachments or reply, unless you recognize the sender's email address and know the content is safe!
ALPLA Corp-IT Network and Security.
Dear All,
following today short call with Christoph we await to know HENKEL SKUs proposal to evaluate the necessary work on all sides to get batch communication going.
Thank you for your support and cooperation.
Kind regards,
Maximilian Rossi
Hi CK and Maximilian,
Could you talk to Henkel if they could use the Alpla articlevariantId (double INT) for batch order communication from Henkel to Vetro?
This would make the communication much easier because we could use the same number in the entire system.
At the moment there are two Int numbers for type and colour in your list.
Also we additionally do need a unique batch number from Henkel to each order for traceability.
Thanks!
Best Regards,
Andre Alber
a.attolini@vetromeccanica.it; Bereuter Siegfried <Siegfried.Bereuter@alpla.com>; Greber Samuel <Samuel.Greber@alpla.com>;
Radl Michael <Michael.Radl@alpla.com>; Spathelf Uwe <Uwe.Spathelf@alpla.com>
Betreff: R: minutes - update data points Vetromeccanica - Bowling Green 2
Dear All,
thank you for your time yesterday.
As we all know Vetromeccanica needs to pin down details of data exchange for supervision as soon as possible for two reasons:
We are shipping control cabinets without havingt set up the same SKU you want to use. This is generating extra work on site which hasn’t been foreseen.Our supervision cabinet exchanges batch format information with HENKEL, ALPLA and AUTEFA and considering production start on line 4L40 is planned
begin of July we have planned our software technician starting end of May with dry commissioning and signal exchnage testing with HENKEL and AUTEFA. This means we need to complete supervision software in the next weeks which is becoming impossible.
For the reasons above we need to continue the software development without including options you requested for now such as HMI recipes synchronization with SCADA and images for alarm pop up on operator
Iphone or other alternatives.
Underneath in red our answers.
Looking forward to your feedback. Perhaps we can have a conference call about SKUs on Monday to answer your questions?
Thank you and kind regards,
Maximilian Rossi
Hi All,
please find updated minutes below in green.
Best Regards,
Andre Alber
Maximilian Rossi (m.rossi@vetromeccanica.it) <m.rossi@vetromeccanica.it>; Bereuter Siegfried <Siegfried.Bereuter@alpla.com>;
Greber Samuel <Samuel.Greber@alpla.com>; Radl Michael <Michael.Radl@alpla.com>; Spathelf Uwe <Uwe.Spathelf@alpla.com>
<a.biasini@vetromeccanica.it>; 'f.maggio@vetromeccanica.it' <f.maggio@vetromeccanica.it>
Betreff: AW: minutes - update data points Vetromeccanica - Bowling Green 2
Hi All,
see below the minutes of our review.
Best Regards,
Andre Alber
Kempter Christoph <Christoph.Kempter@alpla.com>;
a.attolini@vetromeccanica.it; Maximilian Rossi (m.rossi@vetromeccanica.it)
<m.rossi@vetromeccanica.it>; Bereuter Siegfried (Siegfried.Bereuter@alpla.com)
<Siegfried.Bereuter@alpla.com>; Greber Samuel <Samuel.Greber@alpla.com>;
Radl Michael <Michael.Radl@alpla.com>; Spathelf Uwe (Uwe.Spathelf@alpla.com)
<Uwe.Spathelf@alpla.com>
a.biasini@vetromeccanica.it; 'f.maggio@vetromeccanica.it' <f.maggio@vetromeccanica.it>
Betreff: minutes - update data points Vetromeccanica - Bowling Green 2
Hi All,
please find below the minutes of our review today:
Alarm Massage:
alarm message related to a certain picture with the highlighted part of the equipment
à Vetro to provide example and description
à relation of picture to the alarm is not possible. There is not enough information in the picture name. One possibility is an unique
alarm code for each motor with contains the picture name/number. Vetro to show an example for the motors, jamming B1, Jamming B2, etc. which show how to construct a relation of the alarm to the picture. The proposed unit type does not needed to be in the alarm
code – Vetro to submit by 23rd of Aprilentire alarms should be done in one structure
à will not be possible. Different lists will be availableSiegfried B. submit a proposal for a generic alarm array
à Vetro will use the orig. proposed structure of alarmsExport file into XML from OPC-UA from Vetro to be send to Siegfried
à once structure is agreedAlarms will be submitted in one big array, Siegfried confirmed in general this procedure;
We are proceeding with structure update including all data.Approx. 1200pictrues would be necessary
à Vetro to submit a proposal for the programming and submit an example which Alpla would test on the note system handheld
à Alpla to discuss internally if this solution really makes sense at this stage
Attached example of std pictures of line 4L40 we have on our HMI. Those pictures ending with “_Generale” are the main picture on the HMI and when you press on a pre-delimited area you get the other pictures showing devices such as
sensors and motors in green (functioning) or red (malfunctioning). Pictures of area between labeler and filler don’t show information about functioning since these are only an example in terms of zoom level.Vetro to investigate with Siemens if there is an optimized solution available to visualize the HMI on the handheld
We had a first meeting today at 14:00 and will have another early next week.
Data points from filling lines
Ready
SpeedBatch sizeBatch formatEtc.
OEE datas (ejected bottles per ejector)
Ejected bottles of each ejectorBottle counter on each positions where bottles are counted (elevator, lowerator, counter on HITW)
Preventive maintenance datas:
Maintenance message will be availableAre hours meters per motor available? –
Data points status sensors, speed of motors, etc. to be shared on the OPC-UA interface
Data points bottle turner to Autefa and via Autefa to the OPC-UA
SKU code to be generated by
Alpla à Alpla/Andre
Procedure to add an SKU to the PLC to be explained by Vetro (e.g. new colour)
à adding of a new SKU can be done on the HMI
Can Vetro receive a list of SKUs through OPC-UA – see example list of SKU’s attached
We can definitely work with ProdArticled and pass to you and AUTEFA ArticleVariantId or CustomerKey since you need to know the color. The important this is that HENKEL sends to us ProdArticledId plus ArticleVariantId
or CustomerKey so we don’t have to process the full list but just pass it throgh. Our recipes on the HMI would show Format associated to ProdArticleId since we do not work with colors. If you can still change the association of ProdArticleId – Format as per
attached (sheet recipes# VM) we would not have to change the recipes of the 17 cabinets we have shipped already and shared with AUTEFA as well.
Can Vetro store the list inside the PLC so the list is available also without SCADA system
How would this list be shown on the HMI
How to bring the list of SKU’s in relation to the parameter recipe
Vetro to submit a proposal how to administrate the SKUs as requested
Interface description Henkel/Vetro to be shared by Vetro
à confirmation from Henke is missing
– confirmation from Henkel in week 20
Best Regards,
Andre Alber
liable for any damages, whatever their nature, arising out of transmission failures, viruses, external influence, delays and the like.
We deliver and order solely on the basis of our General Terms and Conditions of Sale and Delivery respectively of Purchase set forth in
www.alpla.com/en/gtc-listing/gtc, which both contain a venue clause and an arbitration clause. Contradictory commercial terms and conditions shall not apply.
jede Haftung für Schäden aus Übertragungsfehlern, Viren, fremden Einflüssen, Verzögerungen und dergleichen aus.
www.alpla.com/de/gtc-listing/agb zu finden sind. Sämtliche Allgemeinen Geschäftsbedingungen enthalten Bestimmungen hinsichtlich Gerichtsstand und Schiedsgericht. Widersprüchliche Geschäftsbedingungen kommen
nicht zur Anwendung.
### Adjuntos
- [[AlplaProd_Articles - VM.xlsx]]
---
+ ced079dd654ff7fc7104943e29379205
### Alpla BG: updated telegram description
- 24-02-2020
Hi Max,
please find enclosed updated documents for batch handling.
Following was updated
-
bottle code definitions (see chapter 2.7.2.1 / 2.7.2.2)
-
export line added (line 24)
Note:
Export line will be handled as production machine.
Vetro to send batches similar to filling lines.
In case export is active, TLO24 cannot be assigned to filling line 1-3.
Feel free to get in contact with me, if you have any questions.
Mit freundlichen Grüßen / Kind regards
i.V. Ulrich Osswald
Dipl.-Ing. (FH)
Head of Control Systems & Service
Business Unit Automation
T: +49 (0)821 2608–267
F: +49 (0)821 2608–299
M: +49 (0)170 795 0983
AUTEFA SOLUTIONS GERMANY GMBH
PAUL-LENZ-STR. 1
86316 FRIEDBERG
GERMANY
www.autefa.com
Managing Director
Christian Egger (CEO)
Yanwu Liu
Amtsgericht Augsburg HRB 26374
### Adjuntos
- [[Vetro AUTEFA Communication Alpla BG IBSS_V3.pptx]]
- [[Vetro_communication_v0.2.docx]]
---
Reference in New Issue View Git Blame Copy Permalink