What is the general implementation concept for a recipe system ? Is it to store parameters, set points, and other components in a dababase and retrieve them when the sequence is running?
This is the key. Some processes only have a few different parameters, but the sequence is the same. Others use the same equipment, but the sequences vary wildly. Sometimes the process requires that a sequence spawn two diverging tracks that operate independently, then merge back up; or take optional paths, depending on conditions. It can get very messy, very quickly.
In the former case (different setpoints, same sequence), some simple PLC code with some indirect addressing to load the parameters into the Active Recipe might be all you need, with perhaps some sort of graphic to edit the parameters and create / delete recipes.
In the later case (different sequence) -- well, it
can be done in a similar way (I've done it, more than once), or you can use some canned software (InBatch, IBatch, FTBatch, et al) to manage both the sequence and parameter part, and just let the PLC do the phase and equipment/control module control. (I've done that too; even had to write my own PLI (phase logic interface) when there wasn't one provided).
But this is not something that someone new to PLCs or process control is just going to learn in a "tutorial". Now if you're willing to cut a PO, I can come out and guide you through the process....
---
Where can I find a good tutorial on how it's implemented or maybe a good book ?
Apparently, you did not read the first reply, where I posted a link to a good book. This is not a simple subject, so you will not get a simple answer. How to chop your physical process into Units and Equipment Modules, and how to chop your process into phases takes practice, and some trial and error.