<?xml-stylesheet type="text/xsl" href="https://emersonexchange365.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Process Automation System Design&amp;#160;Techniques</title><link>/services/b/implementbuild/posts/process-automation-system-design-160-techniques</link><description>For an automation project, what design methodology should you follow? Emerson’s Scott Turner provides some thoughts for your consideration. When designing a new control scheme or strategy it is easy to underestimate the amount of design effort required</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator></channel></rss>