QUOTE(sikenga @ Jul 15 2008, 05:06 PM) [snapback]71570[/snapback]
Well, we need to find the better way to control the changes in a group of PLCīs (a big group of PLCīs), and we are thinking of install Factory Talk from Allen Bradley but i dont know if this aplication have the option to connect with other systems inclusive with Siemens PLCīs.
Who can talk me about the providence of Factory Talk in this case.
Rewards.
FactoryTalk Asset Centre is the name of the software AB sells. It's about $5,000 for the basic system.
It has a copy of RS-Linx Gateway built in. The first thing you have to do is to get rid of all other copies of RS-Linx so that everyone must access the system through FT. This is how it controls PLC programming access. If you don't have permissions according to FT, then you can't access the PLC (since it controls the only copy of RS-Linx).
It does support some ways to at least partly get around some obvious limitations such as letting you check out temporary copies of PLC programs and allowing temporary (time limited) RS-Linx access on your local laptop if you need to access a remote project.
Beyond that, it is a document control system on ANY document. So you can load things like Siemens PLC program files into it, drawings, graphics, HMI files, or anything else you can dream up. To get access to the file, someone has to "check it out" and "check it back in". This is typical of any revision control system.
It also logs everything that is going on and you can easily browse the logs.
The access control is to the files stored in the FactoryTalk system. It doesn't have 100% control over the PLC's like it does for AB PLC's. AB claims that they are going to be expanding it. They already support at least backups and document control of Motoman and Fanuc robots.
Don't let the "asset tags" thing confuse you. This is strictly for automated backups. If you pay another $5,000, you can get the "disaster recovery" feature. This system automatically scans all the PLC's in your network and automatically updates the master copies of all the software. Then in the event that something goes wrong, you can tell it to auto-restore the entire plant, or go back and look at changes that have been happening over time. You need one asset tag for each automatic backup.