ABSTRACT
Defining automation boundaries is a technique for generating alternative, high-level, physical system designs. A single set of automation boundaries defines a family of related alternatives, so this technique can be used to identify numerous options. Using automation boundaries to identify alternatives requires expertise in data flow diagrams. Given the trigger events and response time requirements for each process, alternatives are generated by superimposing automation boundaries on the data flow diagram. An automation boundary is simply a line drawn around one or more processes. One possibility is to enclose each process within its own automation boundary. Given even a small data flow diagram, an amazing number of alternative solutions can be generated. If the cost of an alternative significantly exceeds the scope, that alternative is not economically feasible. The idea is to identify two or three reasonable alternatives that are worthy of further study.
