23.08.2013 Views

Specification of Reactive Hardware/Software Systems - Electronic ...

Specification of Reactive Hardware/Software Systems - Electronic ...

Specification of Reactive Hardware/Software Systems - Electronic ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

3.6 Practical Use <strong>of</strong> Concepts 41<br />

Therefore design <strong>of</strong> a so-called system architecture should play a role from the beginning<br />

<strong>of</strong> a design project. Note that we are talking about the specification phase <strong>of</strong> a project<br />

yet. In this respect the Mailing Machine line is very illustrative for a lot <strong>of</strong> design and<br />

Product<br />

information<br />

server<br />

Feeder Feeder Feeder Wrapper Separator Stacker<br />

Figure 3.4: Mailing Machine with Network<br />

specification problems. The plug-and-play concept leads to an architecture as illustrated<br />

in Figure 3.4. The functionality <strong>of</strong> the system is distributed over relatively autonomous<br />

stations that are structured into a production line. Each station gets its local controller.<br />

Neighbour stations have plug-and-play interfaces with each other. In principle these can<br />

be direct and generic interfaces between pairs <strong>of</strong> stations. So each line station between<br />

two neighbour stations has at least two such interfaces.<br />

An early design decision might provide all stations with a generic interface to a network<br />

backbone. Figure 3.4 illustrates an architecture design imposed as a preliminary structure<br />

<strong>of</strong> the system to be modelled. Although the initial requirement is to design autonomous<br />

stations, it is likely that it is more efficient to provide also some centralised server<br />

for some dedicated tasks. Figure 3.4 shows a Product Information Server which is<br />

responsible for the distribution <strong>of</strong> product information over the system and for sending<br />

initial configuration information to all stations. This can be information for power up<br />

after reconfiguration <strong>of</strong> mechanical options on the machine as well for job configuration<br />

information. The server can also gather and process information for improvement <strong>of</strong> the<br />

quality <strong>of</strong> the processing by the machine. The requirement <strong>of</strong> personalising the product<br />

packets also requires a conceptual solution. Figure 3.5 shows the basic solution for this<br />

problem. The idea is to create a transport <strong>of</strong> product information objects through the<br />

station controllers that is synchronous with the flow <strong>of</strong> the physical product packets in<br />

the machine. The considerations so far lead to a structure <strong>of</strong> a control system that consists<br />

<strong>of</strong> autonomous controllers. Figure 3.6 shows the controllers <strong>of</strong> stations in a machine line.<br />

These controllers pass product information (PI) objects. Product information objects are<br />

data objects that are transported via the plug-and-play interfaces <strong>of</strong> the stations. When<br />

the first feeder station (left side) transports a product packet to the next feeder, their<br />

respective controllers must transport the corresponding data object.

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

Saved successfully!

Ooh no, something went wrong!