The above example uses a scenario familiar with most instrument or process engineers. The Module Database certainly is not limited to these personas. The important aspects of the module database can be summarized with these points:
Provides easier access to PI Archive.
The PIAliases collection allows access to PI Points associated with a module.
PIAlias provides use of common names.
Display time resolution of PI Points by referencing aliases rather than PI Points.
Associate other data with modules.
PIProperties collection allows storage of nearly any data; including binary data such as images.
PIProperties collection is hierarchical. Allows organization of properties within properties.
Track Module Edits and Upgrades.
Historize major changes.
Revisions for minor changes.
A module can exist in multiple hierarchical positions.
Build a module once, use it in several places.
Historize module changes through time.
Applications can gracefully handle changes.
ActiveX based interface allows easy programmatic access in any programming language.
VB, VBA, VBS, Java, C++
Application data stored in the module database is reachable by many applications.
Data typically programmed into an application, such as spreadsheet, can be stored on the server.