All of the unique benefits of the system:inmation data historian function can be broken down into one of the following categories: Connectivity, Scalability, Accessibility, Availability and Security. Each of these categories is covered within a separate section. Each section introduces a new set of functionalities building up on one another to establish a full understanding of the benefits offered by the data historian function of system:inmation.
Figure 71:Supported data sources and industrial standards
Figure 72:General scalability overview
Figure 73:Overview of data access options
Figure 74:General overview of MongoDB security concepts
Figure 75:Data Studio security configuration schmatic
- Do Not Persist: This is the default mode and can be used for objects of lower priority or importance.
- Persist Periodically: Changes in dynamic property values are persisted in periodically in batches. This is the preferred mode for objects that you want to persist the dynamic values
- Persist Immediately: Changes in dynamic property values are persisted immediately. This should only be used for objects where it is imperative that all changes in dynamic values are recorded.
- Persist when Service is Stopped: Changes in dynamic property values are persisted when the service is shut down normally. This ensures that values will be persisted when a service is stopped manually.