ROC Archive Collection Tab

Archive Collection Tab

Open

Collection Priority

• Low (Default).Queues up with other Low priority items.

• Medium. Interrupts Low priority items, and queues up with other Medium priority items.

• High. Interrupts Medium and Low priority items, and queues up with other High priority items.

Collect Archive

Default = Not selected. Select to collect. 

For more information on Haul, Gas Lift, and Cycle Transaction Log collection, see Transaction Logs. 

Collection Interval

Select the desired Interval relating to the Schedule object assigned on the Connection tab.

Archive Limits

Click […]  to select or create an Archive Limits for each archive type. See the Archive Limits section for more details.

Archive Mapping (Optional)

The AUTOSOL ROC protocol driver has an internal archive map for each type of ROC device it supports.

The internal archive maps are based on information obtained from Emerson’s documentation on EFM and AGA Reporting.  They contain the details of each point that is expected to be defined in the ROC history configuration and cover the majority of gas and liquid measurement applications.

The Archive Mapping option is intended to be used to supplement the internal archive maps, or for special cases that the internal maps do not cover.  It is recommended that you start off using the internal maps and ensure the ROC history configuration is configured to match before building user defined maps. To view the internal archive mappings, click on “view Internal Archive Map Details…” button on the “Archive Collection” tab.

Under the Archive Mapping option, each type of archive can be configured as “Internal”, “External” or “Both”. Choosing “External” will completely override the internal mapping and use only the points defined in the user-assigned map object. Choosing “Both” will use the internal map plus any points that are defined in the user-assigned map object. If any points are found in both the internal map and the user-assigned map object, the point will be handled as configured in the user-assigned map object.

Open

An Example

In the example which follows, the eighth meter (AKA LiqMtr6) is oddly configured (in ROCLink) to history segment 6.

And if we examine history segment 6 we see four points configured as seen below.

Now to upload the proper history for that meter we must make a ROC Mapping Object.

The two most important configurable properties in the ROC Mapping object are “History Point Base” and “History Point Record Data”.

The “History point Base” is used to define whether the first point is “0” or the first point is “1”. The example above shows ROCLink history configuration, specifically for Segment 6 (called “#6, Segment 6”). The first point (CCF) is listed as point “1”. If “History Point Base” is configured with “0” then in the map it should be referred to as point “0”.

The “History Point Record Data” contains the actual map of points. Access it by clicking the ellipsis (...) next to "(Collection)".

Be sure to click “Tabular Display” to see the map in the spreadsheet-style editor as illustrated below.

• The first column (RecordId) can be anything you like.

• The second column (Map Type) determines if you are mapping by History Point or by TLP.

• The third, fourth and fifth columns are the TLP values if you chose TLP for Map Type. Leave zeros if not.

• The sixth column is the archive Type (Totalize, Average, etc.) and should match the archive type as defined in the ROCLink history segment configuration.

• The seventh column is the History Segment and should match the ROCLink configured history segment for that meter.

• The eighth column is the index down the History point list if Map Type is “History Point”, leave zeros if Map Type is TLP.

• The ninth column is the EFM field that this data will go into for FlowCal, etc. Click the underlined field to get a selectable list of EFM fields.

• The tenth column is the meter being configured.