Any new point created in the FIN Framework - DB builder app is going to have about the same properties (with the exception of the type-specific ones):

navName & Type

...

The default value can be changed by selecting on the text-field

...

Point Kind

 The point kind property enables the user to choose the kind of point to add:

...

• if configuring hisCollectInterval in seconds, it must be evenly divisible into 60sec minute

• if configuring hisCollectInterval in minutes, it must be evenly divisible into 60min hour

• If configuring hisCollectInterval in hours, it must be evenly divisible into 24hr day

• COV collection is rate throttled using a limit determined as follows:

  • use hisCollectCovRateLimit if configured

  • for numeric points with hisCollectInterval, COV will never collect faster than 1/10 of the interval or 1min (whichever is lower)

  • for numeric points without hisCollectInterval, then use 1min as rate limit

  • fallback to 1sec rate limit for non-numerics

    

• The following tags may be used to tune local history collection:

  • hisCollectNA (marker): Historize the NA value whenever the curVal is null or curStatus is not equal to "ok". If this marker is omitted, then no value is logged in this sitaution. This behavior may be changed on for the entire project by adding this tag as a point setting.

  • hisCollectCovRateLimit (duration): It is a duration tag that rate limits the frequency for hisCollectCov. When configured COV logging will never log any faster than this frequency. For example if set to 10sec, then the historian will log no faster than every 10sec even if the underlying data is changing every second.

  • hisCollectWriteFreq (duration): This tag configures how long to buffer collected history items in memory before flushing them to the historian. If this tag is missing, then collected items are immediately flushed to the historian and to disk. But when this tag is configured with a duration number, items are be buffered in memory and then written to the historian in batch. Batch writes enable more efficient compression of the history data and allows you to tune how often data is sync'ed to disk.

• Additional history tags:

  • hisTotalized (marker): Indicates values which are a continuous stream of totalization. History data reads and should be normalized by computing the delta.

  • hisMode (string): Indicates the way that history data is collected for a point. The value of this tag can be either sampled, cov, or consumption.

    • sampled - Data is sampled on a regular interval. The timestamp indicates exactly when the sample was taken, and we assume linear interpolation between samples.

    • cov - Data is logged when it changes. The means the timestamp indicates exactly when it changed (inclusive) and it remains that value until the next sample's timestamp (exclusive).

    • consumption - Integral data is sampled on a regular interval and logged at the end of the interval. The timestamp indicates the end of the interval. Therefore, the raw data is logged as start exclusive, end inclusive. This is mode is typical for consumption meters.

  • hisRollupAutoMinInterval (duration): Forces hisRollupAuto() to do a rollup using this interval when none is specified and the range of the source history grid is less than 2 days. This tag is primarily intended to be used on high frequency histories such as secondly collections to ensure that querying a single day doesn't result in an overwhelming amount of data.

...

The Computed option is history that is generated on demand via a function selected in the hisFunc field - the user will have already created a hisFunc history function for their computed history. The history function record needs to have the demoData and hisFuncReady marker tags tag for it to show up in the hisFunc dropdown list.

...

Basic View 

...

Marker Tags

...

1. The user will select on the  to be able to add a property tag

2. This will display the following

   1.  Type of Property

   2. Tag Name

   3. Tag Value

3. After filling out the text-fields, the user will select on the checkmark(√ ) to commit the changes.

...

...