© Invensys 00/00/00Invensys proprietary & confidentialSlide 1

© 2009 Invensys. All Rights Reserved. The names, logos, and taglines identifying the products and services of Invensys are proprietary marks of Invensys or its subsidiaries. All third party trademarks and service marks are the proprietary marks of their respective owners. © Invensys 00/00/00Invensys proprietary & confidentialSlide 2 MDT AutoSave – Managing Changes for System Platform Objects Presented by Matthew Lawson Director of Technical Operations MDT Software November 2009

© Invensys 00/00/00Invensys proprietary & confidentialSlide 3 The Problem  DevStudio IDE InTouch for SP w/Trend GR ! Automation Process & Devices All Clear!ChangeProblemsDisaster ?

© Invensys 00/00/00Invensys proprietary & confidentialSlide 4 The Hero !  DevStudio IDE InTouch for SP w/Trend GR ! Automation Process & Devices ? DisasterSolution 1)Compare 2)Restore 3)Deploy Party Time!

© Invensys 00/00/00Invensys proprietary & confidentialSlide 5 How did the hero save the day? The Answer: AutoSave for System Platform Latest product from MDT Software, the inventors of Change Management Software for Programmable Devices. MDT has been safeguarding plant automation assets in the most advanced manufacturing facilities over 20 years. Thousands of end-users in numerous industries worldwide have selected MDT AutoSave. MDT AutoSave effectively manages plant floor automation devices, enabling you to minimize downtime, increase safety and maximize production.

© Invensys 00/00/00Invensys proprietary & confidentialSlide 6 What is it? InTouch for SP w/Trend GR Automation Process & Devices  DevStudio IDE The AutoSave Server is an archive for the historical revisions of your graphical objects, templates, instances & controls AutoSave for System Platform runs on the Galaxy Repository, and acts as a monitor of incoming activity AutoSave for System Platform captures changes as they are made AutoSave Server  DevStudio IDE  AutoSave for System Platform By actively managing changes on the GR Node, A 4 SP can track changes for multiple users, simultaneously

© Invensys 00/00/00Invensys proprietary & confidentialSlide 7 How is it set up? 1.Install the AutoSave Server This is the archive/repository for the revision, user, client and other information. Can be a new installation or expansion of your existing AutoSave installation. 2.Install AutoSave for System Platform Installed on the Galaxy Repository, this will update the database and install as a service, monitoring for any incoming activity or changes. 3.Run the Galaxy Export The final step is to export the entire Galaxy into AutoSave to establish a baseline for all objects. In 3 steps AutoSave for System Platform can be up and managing changes in your facility.

© Invensys 00/00/00Invensys proprietary & confidentialSlide 8 How does it work? AutoSave for System Platform provides an intuitive client interface that gives you access to your historical data. This includes graphical objects, templates, instances, client controls and InTouch applications.

© Invensys 00/00/00Invensys proprietary & confidentialSlide 9 How does it work? Additional tabs of information, such as “Revision History”, provide additional data that is not found in the DevStudio IDE.

© Invensys 00/00/00Invensys proprietary & confidentialSlide 10 How does it work? Operations are a single-click away to provide you with the ability to compare or restore to a prior revision of a graphical object, template or instance.

© Invensys 00/00/00Invensys proprietary & confidentialSlide 11 Why do I need it? Complements your Wonderware System Platform solution with unparalleled change management lowering risk and increasing control.

© Invensys 00/00/00Invensys proprietary & confidentialSlide 12 When do I need it? In the “Build” phase of your project to capture & track changes and manage conflict between users developing the system. Build Phase

© Invensys 00/00/00Invensys proprietary & confidentialSlide 13 When do I need it? During the “Operate” phase to manage changes and identify causes of downtime or problems that may occur. Build Phase Operate Phase

© Invensys 00/00/00Invensys proprietary & confidentialSlide 14 When do I need it? During the “Maintain” phase to adapt to process changes and enhancements and to access to your historical data. Build Phase Operate Phase Maintain Phase

© Invensys 00/00/00Invensys proprietary & confidentialSlide 15 Expandable? Yes! AutoSave supports the most comprehensive range of devices and editors in the industry! Microsoft Allen-Bradley Rockwell Automation Schneider Omron Kuka ABB Mitsubishi FANUC Telemecanique Toyoda Siemens GE Indramat PLCs Robots CNCs Welders Drives HMI's (OIT) Workstations Project Files Documents

© Invensys 00/00/00Invensys proprietary & confidentialSlide 16 Success? MDT AutoSave is installed in the most advanced manufacturing facilities in the world. Our customers include: –3M –Allvac –BAA –BHP Billiton –Campbell’s Soup Company –Caterpillar –Chevron –Chrysler –Coca-Cola –Continental Corporation –ConvaTec –Coors Brewing –Fonterra –Ford Motor Company –General Mills –General Motors Corporation –Georgia Pacific –GlaxoSmithKline –Hewlett-Packard –Iams –Kraft Foods –Melox –Merck –Mozal Aluminum –Miller Brewing –National Starch & Chemical –Michelin –Nestlé –Procter & Gamble –Rio Tinto –SABMiller plc –Sara Lee –Scaw Metals –Shagang Steel –Toyota –Tropicana –Unilever –Vale (formerly CVRD) –Vistakon –Weyerhaeuser –Whirlpool –Wyeth

© Invensys 00/00/00Invensys proprietary & confidentialSlide 17