02.02.2018 Views

Practical_modern_SCADA_protocols_-_dnp3,_60870-5_and_Related_Systems

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

14.3.5 Uniform data model<br />

UCA protocol 369<br />

The UCA defines a uniform data model for utility devices <strong>and</strong> equipment via the device<br />

object modeling concepts. Device object models are UCA’s most powerful tool as a<br />

st<strong>and</strong>ard for utility data integration. Figure 14.6 illustrates the resulting UCA device object<br />

modeling concepts using a typical water utility pressure reducing valve (PRV) as an<br />

example.<br />

14.3.6 Logical devices<br />

14.3.7 Bricks<br />

UCA device object modeling describes utility equipment through four levels of abstraction.<br />

The highest level is the logical device. In a <strong>SCADA</strong> application, each individual site<br />

is usually modeled as a logical device, <strong>and</strong> the site RTU (or similar IED) implements the<br />

device object models. The site RTU contains a UCA server to provide device object<br />

information to the rest of the utility. In our example, the logical device is the PRV site.<br />

Logical devices are made up of a collection of bricks, which are the second layer of<br />

abstraction in the UCA. Bricks usually represent an individual equipment component<br />

within the site. In our example, the PRV logical device has five bricks: two pressure monitor<br />

bricks, a main PRV valve brick, a motorized pilot valve brick, <strong>and</strong> a flow monitor<br />

brick.<br />

Note that the bricks in our example are re-usable at many sites throughout a utility. This<br />

is particularly true of the pressure monitor <strong>and</strong> flow monitor bricks.<br />

14.3.8 Component data classes<br />

Bricks are made up of a collection of component data classes, which reside at the third<br />

level within the UCA object hierarchy. Component data classes define the various types of<br />

information available about a device.<br />

In our example, the pressure monitor brick contains information about the pressure<br />

input, which is the measured pressure signal.<br />

It also contains:<br />

• Statistical information about the input. For example, the daily highest value<br />

<strong>and</strong> time stamp <strong>and</strong> the daily lowest value <strong>and</strong> time stamp<br />

• The pressure monitor contains a group of alarm status flags indicating low<br />

alarm, high alarm, high-high alarm, etc<br />

• Pressure monitors also contain an associated set of alarm setpoints<br />

• Finally, pressure monitors contain st<strong>and</strong>ard CASM report control blocks to<br />

regulate when <strong>and</strong> how the pressure monitor reports information about its<br />

measurement value <strong>and</strong> alarm status flags

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

Saved successfully!

Ooh no, something went wrong!