13.07.2015 Views

Information Engineering Style Guide - Control System

Information Engineering Style Guide - Control System

Information Engineering Style Guide - Control System

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Before You Begin 7Before You BeginAbout This DocumentThe InBatch Deployment <strong>Guide</strong> provides recommendations and "best practice"information to help define, design and implement integration projects withinthe Wonderware® InBatch <strong>System</strong> environment.Recommendations included in this guide are based on experience gained frommultiple projects using InBatch and other Wonderware <strong>System</strong> components.Recommendations contained in this document should not preclude discoveringother methods and procedures that work effectively.Note This Deployment <strong>Guide</strong> was developed using the InBatch 8.1, ServicePack 1 release. All information is specific to that release.AssumptionsThis deployment guide is intended for:• Engineers and other technical personnel who will be developing andimplementing InBatch <strong>System</strong> solutions.• Engineers and other technical personnel who will be developing andimplementing FactorySuite A2 <strong>System</strong> solutions.• Sales personnel or Sales Engineers who need to define system topologiesin order to submit InBatch and/or FactorySuite A2 <strong>System</strong> projectproposals.It is assumed that you are familiar with the working environment of theMicrosoft Windows 2000 Server, Windows Server 2003, and Windows XPProfessional operating systems, as well as with a scripting, programming, ormacro language. Also, an understanding of concepts such as variables,statements, functions, and methods will help you to achieve best results.It is assumed that you are familiar with the individual components thatconstitute the Wonderware <strong>System</strong> environment. For additional informationabout a component, see the associated user documentation.All topologies referenced in this Deployment <strong>Guide</strong> assume a "Bus" topology,which comprises a single main communications line (trunk) to which nodes areattached; also known as Linear Bus. Exceptions are noted.For more information on standard topology schemas, seehttp://www.microsoft.com/technet/prodtechnol/visio/visio2002/plan/glossary.mspx or http://en.wikipedia.org/wiki/Category:Network_topologies.InBatch Deployment <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!