Overview
In Chap. 2 you learned the concepts of modeling information in OPC UA. In this chapter we will tighten your knowledge by looking at a concrete example showing how to apply the concepts. We will start with a simple scenario only exposing data similar to Classic OPC. Then we will go forward by adding type information, multiple references, etc. to demonstrate the full power of information modeling in OPC UA. This already shows a way of how to migrate existing Classic OPC applications to OPC UA with respect to the modeling. However, in Chap. 10, we talk about more details on how to migrate from Classic OPC to OPC UA.
In the example, we target an application scenario typical for Classic OPC applications. However, in the second part of this chapter we will generalize the example by looking at some general best practices on how to model information in OPC UA. In the example, we will not consider standard Information Models other than using types of the base Information Model. In Chap. 4, we will introduce standard Information Models. When modeling your information, you should consider using those Information Models and extend them rather than creating your own Information Model from scratch when this is appropriate in your domain.
The notation used in the example to expose details on the Information Model is described in Appendix A of this book. The Appendix does not only describe the notation but also discusses its relation to UML.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
In Chap. 4, we will learn more about the entry points into the Address Space.
- 2.
We are considering this issue only from the modeling perspective. Of course, providing sub-variables may be some coding effort for you, so you may want to go for solution two based on those considerations.
- 3.
The overhead is compared to one built-in DataType. Since a structured DataType often contains the data of several built-in DataTypes, providing the same data in a structured DataType is typically more efficient. You only get one set of status code and timestamps (see Chap. 5 for details).
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
Copyright information
© 2009 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Mahnke, W., Leitner, SH. (2009). Information Modeling: Example and Best Practice. In: OPC Unified Architecture. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-68899-0_3
Download citation
DOI: https://doi.org/10.1007/978-3-540-68899-0_3
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-68898-3
Online ISBN: 978-3-540-68899-0
eBook Packages: Computer ScienceComputer Science (R0)