# How to change production parameters based on workpiece carrier ID?

**URL:** <https://forum.inductiveautomation.com/t/how-to-change-production-parameters-based-on-workpiece-carrier-id/58255>\
**Category:** Ignition\
**Created:** [April 9, 2022, 10:25am UTC](https://forum.inductiveautomation.com/t/how-to-change-production-parameters-based-on-workpiece-carrier-id/58255 "2022-04-09T10:25:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nicolas\_Grilly](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nicolas_grilly/32/33625_2.png) [@Nicolas\_Grilly](https://forum.inductiveautomation.com/u/Nicolas_Grilly)\
**Post date:** [April 9, 2022, 10:25am UTC](https://forum.inductiveautomation.com/t/how-to-change-production-parameters-based-on-workpiece-carrier-id/58255/1 "2022-04-09T10:25:06Z")

</div>

We have workpiece carriers moving from one station to another, on a line composed of about 35 stations. Each workpiece carrier may have a different recipe. To do this, we want to equip each station with a Siemens S7 PLC that would read the workpiece carrier RFID, and get from Ignition the recipe associated to the workpiece carrier ID in an SQL database. What would be a good way to do this in Ignition?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [April 9, 2022, 2:29pm UTC](https://forum.inductiveautomation.com/t/how-to-change-production-parameters-based-on-workpiece-carrier-id/58255/2 "2022-04-09T14:29:04Z")

</div>

This would typically be a transaction group (possibly multiple-row in a block type group) set to DB-\>OPC direction. If you don’t have the SQL Bridge module, equivalent functionality can be scripted in a tag change event.

Consider doing this one station ahead and transferring the data in the PLC as part of the carrier movement logic. That minimizes/eliminates any DB delay before starting the machine cycle.
