M037 Exaquantum Administrator Course Day 2

NTPP901 - Exaquantum Administrator Course 20th January 2014
This slide provides an overview of the required Exaquantum configuration tasks. It also shows the
various sessions of the course, which cover the various aspects of the configuration.
This diagram will be used at the start of each session again to overview the various steps.
Sessions 1 - 3 will be covered on day 1. Sessions 4 -6 will be covered on day 2.
Day 3 deals with day to day management issues (see next 2 slides).
The flow shows the typical order in which the various configuration tasks would be undertaken.
For training and logistical reasons manual creation of tags is considered in this course before the
automated methods. This allows us to look at various concepts in a structured and methodical
way.
Session 5 will also include a discussion on the HIS Tag Generation, which, although in the
Advanced Group, is actually a Tag Generation Method.
M037 Issue 18 Day 2 Slide No. 1


The Tag editor can be used for the following:

View current tag values
Modify existing tag attributes
Creating Folders
Creating Manual, Calculated and OPC tags
Creating Function Blocks
Two view modes are available:

Tag View
Function Block View
The example in this slide shows the Function Block View. The next slide shows the Tag View.
Clicking the Edit button will bring up the edit dialog for the type of entity selected.
The Tag Editor is not designed to be used to build all the Function Blocks and Tags required in a
normal system. This would be very time consuming and laborious. Automated methods of Tag
Generation will be covered in Session 5.

This slide shows just the Details Pane for an Individual Tag. It is generated when a single Tag is
selected in the Data Selector Tree View.
The details are the current information for the selected tag.

The active options in this menu will change depending on the selected item.
This slide shows the menu when a folder is selected.
Choose Add to add a new object. Displays the Add New Object dialog.
Edit to modify the attributes of the currently selected object. Note there is nothing that can be
edited for a folder and hence it is deactivated on the menu displayed here.
Remove will remove the currently selected object. If the object is referred to within a script or
shortcut then the remove will fail by default (see later in the session).
Rename allows you to change the name of the selected object.
The Cut option allows objects to be moved around the hierarchy. Care should be taken when
doing this however as it will change the access string. This might also affect Role Based Name
Space configuration. Once you have cut an object a paste option will appear in the menu to allow
the object to be placed in its new location.
It is possible to select more than one object by holding the shift key or control key down whilst
selecting the objects in the same way as in Windows Explorer.
Refresh Node will re-read the configuration database.
Use the Upgrade to Latest option to upgrade tags and function blocks affected by any templates
change.

Five types of objects are supported:

Folders provide a logical hierarchy of plant data. This should reflect the uses of the data. It
is possible to build up different views of the data using different folder sub-trees. The
Folder hierarchy used here may not be that seen by the user. This hierarchy may well be
just for the benefit of the Exaquantum Administrator. The user hierarchy will more
normally be created using the Role Based Name Space mechanism discussed later in this
presentation.
Function Blocks are logical structures containing one or more tags which are in some way
connected functionally. This could be as parameters to a calculation or attributes of PCS
control entities or a combination of information from different sources.
Calculated Tags are flat tags, which have a script which generates their value. Calculated
Tags update whenever one or more of their associated data items update.
Manual Tags are flat tags, which only change when updated explicitly either using the Tag
Editor or from an Exaquantum/Explorer screen.
OPC Tags always represent measured quantities sent via the OPC Server from the PCS.
They may represent attributes of a PCS function block or just a single measured value
depending on the PCS being monitored.

Choosing Folder from the Add Object dialog displays the Add Folder dialog. This allows the
name to be defined for the new folder which will be inserted below the selected folder.
It is a good idea to know what hierarchy you wish to have to create this first.
This will also help when the Tag Generation methods are used although it is possible to create the
folders during the Tag Generation process (see Session 5).

A similar dialog is displayed when the Edit option or Edit button is clicked. The only difference is
the caption, the presence of a lock check box and the initial contents of the dialogs edit boxes. An
example of an Edit dialog is shown on the next slide.

Depending on the level of security configured via the licence key a password may be required
whenever a change to a manual tag value using the tag editor is attempted. If this is the case then
before the change is made this dialog is displayed. The password required here is that of the user
making the change and will be indicated by their full name as recorded in the System or Domain
Authentication Database not the user name.

The difference between Manual Tags and OPC Tags is that the value will be obtained from an
OPC Gateway. To configure this two pieces of information are required:
OPC Item ID – Is the name by which the required item is known by the OPC Server. This
will in general be different for different OPC Servers (see Day 2 Slides 11 and 12 for
details).
OPC Gateway – The is the gateway through which the data will be read. It must be one of
the configured OPC Gateways and therefore can be selected from the drop down list.

Examples of an Exaquantum OPC Item ID would be
Root.Area1.Plant Data.00FIC001.PV.Value
You can also acquire other items such as Aggregations in this case a theOPC Item ID would have
the form: -
Root[.Folder[…]][.FuncBlock].Tag.Aggragation.Period.Aggregation Type.Value


In the case of the Manual tag, a value is all that is expected but in the case of the Calculated tag a
script is required. Scripts are defined using the Expression Editor. You display the Expression
Editor by clicking on the Expression… button.
Like OPC Tags and Manual, Calculated tags must be associated with a Tag Template. The Tag
Template is set using the drop down list (the third edit line on the dialog). This will display all the
Tag Templates which have been created of the correct types.
The offline check box sets the Primary Quality to Assumed. No further updates will be made to
this tag. See Day 2 slides 35– 38 for a discussion of Offline tags.

You can build up the expression simply by dragging tags (raw or aggregated) from the tree at the
bottom of the dialog and adding fixed text which may be constants, language statements and
mathematical operators.
It is not possible to drag anything lower than an item. When an item is dragged, the Value element
of the dragged item is assumed. To use the Timestamp or Quality elements you need to append
.Quality or .Timestamp after the ].
It is also possible to set the quality values and also to update more than one tag from within a
script. Setting quality values is covered on a later slide.
The highest level at which you may drag is the tag. If a drag operation is performed at this level
then the Value item is assumed.
The scripting language is Microsoft VBScript and therefore much of the power of VB is available
to you.
The OK button will not become active until the script has been tested via the Expression Tester
dialog.
The syntax is checked automatically when the Test Expression… button is clicked and any errors
will be indicated in red. The Expression Tester will only be displayed if there are no syntax errors.
During operation calculation will timeout, after 5 seconds by default, if there is a problem and
return a quality of Bad and a secondary quality of Bad Calculation.

When the Expression editor is displayed via the Edit details button on the FB Templates Screen
and extra tab is displayed showing just those tags in the currently selected FB template.
When you drag a item from this tab it will be displayed with the Parent keyword rather than the
full path.


This allows you to test the new expression prior to committing it to the database.
You should note that no external data is gathered and you will need to set every variable used in
the expression manually prior to clicking on the Test button.
Scripts will not, in general, comprise only a single line of code. Condition handling code will
often be required to ensure that input values do not cause the scripts to error. Conditions which
are often checked for are:
Divide by Zero
Arithmetic Overflows
Value outside the validity limits of the result tag
Functions like LOG/LN/SQRT must not have negative arguments
Input Values are bad or outside the validity limits
Bad or Uncertain quality of Input values
The Expression Tester gives you a safe environment in which to test to see that the code works as
expected under a wide range of input conditions.
You should plan your testing carefully to test the expected error conditions.
In Exaquantum you must at least use the Expression Tester once before the calculation can be
committed.

The System Configuration Tool (QSystemConfig) can be found in the Developer Tools Folder in
the install path.
This option is on the RTDB tab (see Day 3 Slide 148).


The addition of new function blocks uses the function block templates created using the Function
Block Template Screen. Function Block templates must exist before you can use this dialog.
A drop down of all Function Block Templates is provided from which you may choose.
The information displayed at the bottom of the screen (FB Tag Definition) will display a list of all
the tags configured in the selected template.
Tag Shortcuts allow use of tags belonging to another function block or have been created as flat
tags to be shared. No actual tag is created, instead a reference to the existing tag will be made.
Shortcuts are not included as tags for licence considerations (see Day 2 Slide 22 for details of Tag
Shortcuts).

Select the OPC Gateway using the drop down list.
The OPC Item ID will default to the Exaquantum Function Block and the Tag name already
configured in the Add dialog and Function Block template respectively.
If a data is to be obtained using the Exaquantum OPC Server then the OPC Item ID would be
similar to that discussed earlier in relation to flat tags (see Day 2 Slides 11 and 12).

Shortcuts provide alternative routes to an existing Tag. If you modify a Tag Template upon which
this original tag was built you can edit either the original Tag or a shortcut in order to apply the
changes. You will however be notified that you are about to affect other shortcut tags.
Shortcuts can be made to any type of tag but can only be created within a function block and the
selected tag must match the data type of the tag defined in the function block template.

This shows the case where the function block template is defined with four tags of type Shortcut.
Double click on the far left of the Settings field to display the shortcut tag selector dialog.

If you select a tag which is itself a shortcut then the Shortcut Path will display the path to the
actual tag not the shortcut that has been selected.

The shortcut dialog will not allow you to select a tag which is not of the appropriate type.


It is possible that removal of objects would cause other objects which had references to the
removed object to fail. Such instances would occur when a tag is being used in a script.
For this reason whenever the Remove Object is selected this dialog will be displayed. The default
setting is not to remove if any references exist. If you uncheck the check box then the removal
will go ahead potentially making calculations and other function block values invalid.
To check to see whether cross references exist click on the Show Cross-reference… button. Cross
references can also be viewed using the Exaquantum Cross Reference Support Tool (Session 8).

In this instance the function block 00FC001 has four references.

The Bulk Update Tool accessed from the Tag Editor Pop-up Menu can be used to update any or
all affected tags(See Day 2 Slides 5, 32 and 33).
Re-running the Tag Generation job that created the tags in the first place will also update existing
tags to reflect the current values of the associated template (see Session 5).
It is possible to lock a tag so that updates are ignored or manual changes can be made directly for
a particular tag. Locked tags will appear as such when a tag generation job is re-run (see Session
5).
A list of tags not built to the current template version can be viewed using the Tag Configuration
Viewer Support Tool (see Session 8).

Note the red text immediately under Settings.
Clicking on the Lock button will prevent the tag being updated by any tag generation method. If
this box is checked then it can only be updated using the Tag Editor. It can be used to ensure that
any manual changes are not overwritten by a tag generation job (see Session 5).
You will need to uncheck the Lock Status box again if at some time in the future you wish it to be
affected by any tag generation job.
The Lock Status has no effect on the ability to edit the tag via the Tag Editor.

Click in the Settings column to insert the necessary information. In the example on this slide it
would expect an existing Tag to be attached.
The FB Offline Action buttons provide the ability to switch all OPC and Calculated tags in this
function block on and offline.

The Upgrade to Latest option appears on the pop-up menu no matter which node of the Data
Selector is selected however the tool will only look for changes at the current folder and any sub-
folders of the selected folder. To update all changes right mouse click on the Root folder.

An item will be updated if there is a tick in the check box. By default all items are check accept
where the tag or function block is locked as in the case of the first two tags in the example above.
Note that it is not possible to use this tool if you have added a new OPC Tag or Shortcut to a
Function Block template.
Once all the items that are to be updated are selected. Click the Upgrade… button
An example report is provided in the NTPP901 Solutions folder for Session 4.

Setting the lock does not prevent manual changes to the tag or its value but will prevent any
generation job (see session 5) updating this tag should the template upon which it is built change.
This means that until the lock is released the configuration of this tag can only be changed
manually.

No automatic updates will be made to tags which are in the offline state.
The primary quality of offline tags is set to Assumed.
Any manual update to offline tags will result in a secondary quality of Replaced being set.
Individual tags and all OPC and Calculated tags in a Function block can be set offline either using
the tag editor or via the API.
See Day 2 Slide 30 for the method of setting individual OPC and Calculated Tags offline.

Here a function block has three tags; one Manual, one OPC and one Calculated Tag.
Clicking on the Offline Button will mark both the OPC and Calculated Tag offline.
For the result of this see next slide.

Note here that the OPC and Calculated tag now have Assumed Quality.

Note that the quality of the Value tag is now Good as this was the quality set but the Secondary
Quality is now set to Replaced.
The value of the Calculated Tag remains unchanged.



The check here is performed on the Object Name. If it is the same in both templates then it is
assumed to be the same. If the names are different then they are different tags.
Hence in this example the PV tag has its template modified where as the SV and MODE are
deleted to be replaced with Controller State and Set Point.
The Value tag is completely new.




There is no mechanism in OPC to update Reference Data for just those tags that have had there
value changed on the DCS. The methods described here just read the current value of the
Reference Data for all OPC tags that are configured with reference data. The OPC foundation
specification refers to this type of data as Property Values.

Note that all reference data which has been configured for tags from the selected OPC Gateway
will be updated.

This is a command line tool and therefore it needs to be run from the command prompt or from a
command file.
When the command is issued with no parameters then all reference data is updated. If you wish to
update reference data from a particular OPC Server then the command can be executed by a white
space separated list of OPC Gateway names as configured in the OPC Gateway Screen (i.e. not
the name of the computer on which the OPC Server is running). For example, supposing you had
three OPC Gateways configured called Area1, Area2 and Area3 then the command above would
update reference data from all three. To update Area1 and Area3 but not Area2 you would use the
following command:
QOPCReferenceUpdate Area1 Area3
The order you specify the gateways in does not matter.
No indication is given if the operation succeeds.

In Windows each user has their own list of Scheduled Tasks, which you will find in the Scheduled
Tasks folder from the Start Menu under Programs\Accessories\System Tools\.
You should ensure that the user configured to run the task has Exaquantum Administrators Rights
(see Session 6).

This is not designed to provide a course is vbscript but there are several things which are specific
to Exaquantum that have either been added to or need to be explained. The following examples
provide this overview.

The subscripted numbers in the code do not form part of the actual script itself but are used to aid
reference.
Point 1 shows the declaration of local variables. All VBScript variables are Variant and therefore
you do not specify the type as you would in VB or VBA.
Point 2 shows the use of an item other than the Value Item. It is possible to access any item
including aggregated items from within a script. It also shows the use of the Parent keyword. The
main use of the Parent keyword in a Calculation is when the calculation is part of a Function
Block. In general it will normally be used in coding a Calculation Tag as part of a function block
template when the actual parent will be different for every instance of the template. In the case of
manually created calculations normally you would expect fully qualified tag references. It can
however also be used to describe a Tag in the same folder in the case of a Flat Calculation Tag.
Point 3 shows the method by which the value of the Tag is set. The [Result] keyword can appear
on either side of the equal sign and will be loaded with the current value of the tag at the start of
the script. This allows codes such as
[Result] = [Result] + 1
to be coded. This line also shows a reference to an absolute tag value.
Point 4 shows a fully qualified tag.
Point 5 shows the method of accessing the Quality or Timestamp Elements of an item.

The subscripted numbers in the code do not form part of the actual script itself but are used to aid
reference.
This example shows the use of the Quality built-in functions and also the use of the [Result]
keyword on the right as well as the left.
Point 1 shows the use of the IsGood built-in function. Exaquantum provides several built-in
functions to handle quality. These include:
IsGood, IsBad, IsUncertain, RawQuality
Point 2 again shows the use of the Parent keyword. In this case the Tag InterConst and PV are in
the same function block. This method also works to access other tags in the same folder as a
calculated tag which is not part of a function block. It also shows the ability to use items other
than the Value Item in a script.
Point 3 shows that it is possible to use the [Result] keyword on both sides of the equal sign. This
allows equations which require intermediate checking to be made without the need for temporary
variables. This will also be loaded with the current value of the tag so that this can be used for
example in an accumulator. Any other form of recursion is not permitted.
Point 4 shows the use of the RawQuality built-in function using enumerated variables instead of
absolute values for Quality. Using these keywords will insure that the correct values are set even
if they were to be changed internally. It also makes the code more readable and easier to maintain.
Both primary and secondary quality can be assigned in this way.
Note that the QQualityHelper function is an example of a COM Library configured into
Exaquantum. It is possible via the CalcLibrary table in the QConfig Database to configure user
defined libraries. Configuration of user defined libraries is out of the scope of this course

This example shows the ability to assign a value to more than one tag from within a script.
You should note that it is not possible to use the same tag as both an input and an output.
However as with the example on previous slide it is possible to use the [Result.[…]] notation on
both sides of the = sign. You can also us it in an if statement.
For example:-
If [Result.[Root.Tag1.Value]] <= 100 then
[Result.[Root.Tag1.Value]] = [Result.[Root.Tag1.Value]] + 1
Else
[Result.[Root.Tag1.Value]] = 1
End If

Simple timers can be used to schedule a reset for example or to schedule a script to run so many
seconds after the completion of the last time it ran. This will ensure that there is a specific gap
between the finishing and starting again. The script will run again some seconds after the
StartTimer call has been executed.
Periodic Timers however allow for calculations to be executed at known moments in time. The
offset allows amongst other things for the calculation load to be spread.


This script calculates the mean temperature within the Distillation column which has 8
temperature probes at various locations.
It is simplified in as much as only two of the 8 temperature tags are shown.
This calculation will get fired every time any of the temperatures change but the mean will only
be calculated once every minute.
The call to StartPeriodicTimer as the first line will not cause the script to be rescheduled. This is
because the run time engine has been designed so that if a periodic timer call is encountered with
the same parameters then it is ignored. If however one is encountered with different parameters
this will override the first.

This topic will not be covered in detail on this course (See NTPP903 Exaquantum Developers
Course for details).
For completeness however when dealing with Exaquantum Calculated Tags it is briefly covered.

Even though Event Generation is not covered on this course, for completeness a code fragment is
provided here showing how an event would be generated from within a Calculated Tag.
Unless the Event Generator mechanism is configured this code when executed will have no
effect. When configured correctly this code will cause the Event Generator to queue a request to
an Event Handler which is selected using the first parameter. All other parameters are optional
and depend on the configuration.

See Day 1 Slides 74 and 75 for template configuration.
See the next slide for an example of part of a aggregation calculation.

Exaquantum provides the ability to write calculated scripts to replace the Aggregation algorithms
for either the Hour, Day or Monthly Aggregation periods. In order to do this you must create a
calculated tag template which has the aggregation supplied by calculation option set. This will
then allow you to use the syntax defined at point 2 above to write to the aggregation.
Note that any aggregations dependent on this aggregation will be affected by this. For example
Daily aggregations depend on a calculated Hourly.
It is however not possible within one calculation to update aggregations of more than one
independent aggregation period, for example shift and hour.
Point 1 shows the ability to check to see which of the inputs actually caused the calculation to
fire. This mechanism can be used in any calculation, not just those involving aggregation
calculations. This provides a way to perform different processings dependent on which of the
inputs actually changed. It would also be possible to only do calculations if a particular tag value
changed, not every time an input changed. In the example above changing the value of the tag
Root.Scale would not result in a change in the aggregated value to update.
If this mechanism is used then all aggregations selected in the template must be calculated and
updated in the script otherwise an error will be generated.


It should again be remembered that the Tag Editor would not normally be used for engineering a
system but for making minor changes or for diagnostic purposes. But it does show some of the
features which will be hidden when using the Tag Generation methods.
This exercise however does cover all the features of the Tag Editor and reinforces the points
covered during the session.




way.

The configuration of History Catch-Up is discussed at the end of this session. In the exercises,
however, it will not be set up until session 8.

It might seem that having four separate methods over-complicates things but in actual fact there is
no overlap in the function of the methods and each method is useful under different
circumstances.
Yokogawa Exaopc Equalisation

As the name of this method suggests this is only useful when you are obtaining
your data from Exaopc. Currently we can only equalise with Exaopc. The browse facility
provided in the Exaquantum OPC Client does not support equalisation with any other
OPC Server.
The other limitation is that the Function Block names in Exaquantum will be
exactly the same as those on the PCS. There is no mechanism in this method to change
these. The tag names can however vary from the Data Item names used in the PCS.
This method uses wildcard filters and therefore a strong naming convention is also
required in order that this method works without the need for too many individual filters.
OPC Tag Import

This method does not depend on there being an Exaopc to which data is being
acquired but still requires the OPC Item ID to be in the form <PCS Tag>.<Data Item>.
This method also assumes that the PCS Tag name and the Exaquantum Function Block
name are to be the same. For this reason this is a good method when equalisation is not
available or inpractical.

Notes for type one and two are on the previous slide as there is not enough room on one slide.
Generic Function Block Import

This method is the most flexible of the function block generation methods. It allows full
control over the naming convention used in Exaquantum and can also build Exaquantum
Function Blocks containing OPC Tags from different OPC Servers. It is therefore a useful
method if a file in the correct format can be generated automatically. Being the most
flexible it is also the most complex file format.
General Tag Import

This will only allow the creation of flat tags of any types. You cannot use this method to
generate Exaquantum Function Blocks.
HIS Tag Generation

This method is actually the simplest method but is perhaps the least flexible. It can be
used to populate the database with all or a subset of the tags configured into the trend
groups on the CS 3000/1000 system. It will automatically create tag templates, folders and
flat tags. This method is the method used in the CS3000 LTTH package.
The HIS Tag Generation screen is located under the Advanced Node in the Administration
Tools Tree rather than the Tag Generation Node.



There will be one template for each type of tag (Analogue (AI) or Digital (DI)) and each OPC
Period required by the selection.



This shows the tag tree in the Tag Editor for a series of tags created using the HIS TAG
Generation method.

In many existing process management application databases creation needs to be done using
tools, which effectively means re-entering data already known by the DCS. This means that a lot
of time is consumed populating the database.
Exaquantum provides a method which will automatically populate the database with function
block information if this is provided by the OPC Server. Yokogawa’s Exaopc provides this
information.
This method is referred to as Equalisation because it equalises the Exaquantum Database with
that known by the OPC Server.
Equalisation can be configurable so that only information required by the monitoring system is
transferred. This is known as filtering. Exaquantum provides both inclusive and exclusive
filtering on function block names.
The Equalisation wizard guides the administrator through the steps one by one. It is also possible
to move back through the steps to change any parameter, for example, to include another
inclusion filter (see later in the discussion).
Equalisation can only be performed on the Server.

Exaquantum refers to the process of performing Tag Generation as a Job. There is a specific Job
Viewer screen for each of the Tag Generation methods. This shows the OPC Equalisation Job
Viewer.
This job maintains all the options and filters entered whilst the Tag Generation Wizard is running.
This allows the same job to be re-run. Re-running a job will be required when new function
blocks/tags are to be added or changes have been made to the Tag or Function Block templates.
To re-run the Job, double click on the name or select the name and click the Select button.
The Delete button can be used to remove a job from the Configuration Database.
A separate OPC Equalization Job will be required for each Exaopc Gateway configured.

This screen allows you to specify a unique name by which this job will be known and also to
select the OPC Gateway through which the information will be acquired.
If you have defined multiple OPC Gateways then these will be listed in the edit box on the right
of the screen. The Gateways displayed on this screen are those that have been configured already
via the OPC Gateway Configuration Screen (discussed in Session 2).
Note:
Only Exaopc servers are supported by this method of Tag Generation.

Clicking on the Next button on the OPC Server Screen will cause the equalisation process to
attempt to connect to the specified OPC Server.
If the Equalisation wizard cannot make a connection to the OPC server, an error will be generated
and the Equalisation process will terminate.
If an error occurs during this phase there may be something wrong with the network or OPC
Server.
If all is well then the list of Function Blocks will be created in memory. Nothing will have been
committed to the database at this stage. During this process the Progress viewer displays
Processing station as the Current Task, the progress of processing the station and an overall
process.

There is no single way of selecting function blocks to be included in a particular equalization job.
This depends to a large extent on the naming convention used.
To fine tune the selection process, as well as to cater for personal choice, Exaquantum provides a
two phase selection process for function blocks:
1. Inclusion filters are applied to just include those function blocks which
match given specifications.
2. Exclusion filters are then applied to the list of function blocks
included from the first phase.
It is possible to have an inclusion filter (*) which will pass all function blocks to the second phase
or to provide no exclusion filters and therefore use only inclusion filters to select the function
blocks required.
In most cases however both filter types will be used.
Each Inclusion Filter specified is associated with a Target Folder and a Function Block Template.

The filters in the above example are fairly simple. A more complex example would be
F#0#P?D0[1-4]0* which will include all function blocks of at least 10 characters starting with the
letter F followed by 3 numbers where the middle digit is 0 then 3 alphanumeric characters of
which the first must be a P and the last a D then 3 further numbers of which the first and last are
both 0 and the middle digit will be either a 1, 2, 3 or 4. The final * indicates that we do not care
how many characters follow the given specification.
To add a new filter, click the New button, enter the new filter in the Inclusion name filters edit
field, select the required Target Folder and Function Block Template and press the Apply button.
Pressing the Apply button will copy the filter from the Inclusion name filters box to the Applied
Filters list adding all the function blocks matching this new filter into the right hand side of the
display.
To remove an existing filter, select the filter specification and click the Delete button.
The Target Folder can be set by clicking on the … button to the right of the edit box. This will
display the Folder Selector. See the next slide.
For each filter added you specify the Function Block Template to use and the Target Folder. A
single job can consist of many such Filter/Function Block Template/Target Folder settings.
Any Manual or Calculated Tags in the selected Function Block template will not be shown on this
screen. When the job creates the Function Block, it will create all the tags configured in the
selected Function Block.


The area outlined in Red on the slide shows the list of PCS tags read from the OPC Server.
Check the Show PCS Tags to show all the Function Blocks read from the OPC Server.
You should note that when entering or editing a filter this list will show all the PCS tags which
match the selected Instrument Type. This can therefore be used to help with the addition of filters
ensuring that the filter added does match what is required.

By default you will not be allowed to continue if there are Candidate Errors.
Candidate Errors will be caused when a selected PCS entity does not contain one or more of the
requested attributes.
In the example shown above a template with Tag names of MODE, MV, PV and SV has been
selected but the specified filter *TI* has selected at least one PCS Function Block which does not
contain an MV, PV or SV attribute.
You cannot tell from this screen which Function Block is missing what attributes.
By default you cannot continue from this screen until there are no candidate errors.
Check the Ignore Candidate Errors option if you expect that some of the candidates selected will
not match the selected template and therefore cause errors. This will enable you to continue. All
candidates which generated an analysis error will be automatically excluded.

By default the screen will use the Tag Names configured into the template as the PCS Item
Names. This can be changed by entering the actual PCS Item Name replacing the default name. If
you click at the right hand end of the line then a drop down list will appear. This lists all the PCS
Item Names already used during the configuration.

Given the list included by the Inclusion Filters, we can now remove some. In this way a fine
tuning can be obtained on exactly which function blocks will be included in this Equalization Job.
Adding and removing filters is performed in the same way as for Inclusion Filters.
A blank exclusion filter list means that all included candidates are used in future processing.

This dialog draws together all the information entered in the other screens of the wizard. It
summarizes what the Generation Engine will actually perform.
At this point the user has four options:

1. Click the Cancel button. This will result in the Equalisation Job not being recorded
and will not, therefore, appear in the Job screen. This option is available on all
screens.
2. Use the Back button to return to earlier screens and make any further
modifications prior to equalisation. Again this is available to you on all the screens
except the first one.
3. Click the Finish button. This will result in no equalisation taking place but unlike
the Cancel button, the Job information will be saved so that it may be run again at
some later date.
4. Click the Generate button. This will cause the Tag Generation Engine to process
the information and create the entries in the Configuration Database.
Before clicking the Generate button you should review the summary info displayed. This is to
ensure that the generation engine will do what you expect it to do. It is possible that the options
you have chosen may, for example, cause some, possibly hundreds or even thousands of tags to
be deleted, together with any associated historical data.
The locked count indicates existing function blocks which have been selected as candidates but
will not be changed by the generation engine.

This shows what was actually done and how long it took to complete. It also summarizes all the
information used during the installation process.
Clicking the Finish button will close the wizard and record the information in the job screen.
The Summary report is similar for all job types and will not be shown again during this session.

In this example the filters used resulted in 63 candidates being selected.
Of these 14 where newly added to the DCS and 49 need some modification due to a change in the
template.
These changes where associated with a template which had 1 tag removed and 2 new tags added.
There had also been changes to the calc tag included in the function block.

Remember that the Folder is used to group tags and function blocks. It will also be displayed in
the Data Selector of Exaquantum/Explorer, the tag editor and other Exaquantum tools.


Like all files that may be required more than once they should be stored in a central location;
perhaps on a central file server if available or on the server in a folder with the other product files.
This will apply to all files used for tag generation. They should also be protected against
modification by anyone other than those in the Exaquantum Administrators Group
(QAdministratorGroup in the Legacy Model or QTM_MAINTENANCE in the Security Model)
This screen is the same for OPC File Generation and Generic Function Block Equalisation.

# Indicates a comment which can appear anywhere in the file and will be ignored during
processing. The first line in any file must be a comment.
The ITEM keyword maps a TEMPLATE (Attribute) entry to the DCS ItemID Extension.
The OPCSERVER must be the name of a configured OPC Gateway.
You should only define the OPC items from the template in this file. All non-OPC items will be
automatically created for each of the candidates.
CANDIDATES is a list of PCS entities that are to be used as instances of function blocks using
the specified type. The above just shows two function blocks, in practice there could be many
more.
The OPC Import File method assumes that the OPC Item ID will be of the form Candidate
Name.Item extension e.g 00FC001.PV and the Function Block Name will be the same as the
Candidate Name. This method cannot therefore be used if the OPC Item ID does not fit this
model. You will need to use the Generic Function Block generation method if this is not the case.
You must also use a different file for each TEMPLATE, TARGETPATH and OPCSERVER to be
configured.






The import file lists all the OPC tags to be created. Any manual or calculated tags in the template
will be created but there is no configuration effort once the template has been created.
You need to specify either the Tag name and OPC Gateway or the full path of an existing OPC
Tag.
Shortcuts were discussed in the last session.
This example shows a template called Tank which contains three OPC tags called Level, Flow In
and Flow Out. Flow In and Flow Out are to obtain data from two different flow controller PV
attributes and the Level is to be a shortcut to an existing PV tag of a Level Controller.
The above example also shows the fact that you include tags from more than one OPC Gateway.





The import syntax provides a mechanism (FULLPATH keyword) to override the default folder on
a per tag basis. If the FULLPATH keyword is specified and the path(s) provided do not exist then
a dialog will be displayed asking whether these should be created or not.

Build the folder tree into which the tags will be built.

Manual Tag Format:

TAG=name,TAGTYPE=MAN,TAGTEMPL=template_name,
DESCRIPTION=Value1,HIGHENG=value2,LOWENG=value3,
UNITS=value4,VALUE=value
Calculation Tag:
TAG=name,TAGTYPE=CALC,TAGTEMPL=template_name,
UNITS=value4,SCRIPT=Any_Valid_VBScript
The VBScript must either be on one line with statements separated with a : or enclosed in double
quotes.
OPC Tags:
TAG=name,TAGTYPE=OPC,TAGTEMPL=template_name,
UNITS=value4, ITEMID=item_id,OPCGATEWAY=gateway_name
An example ItemID would be 00FC001.PV. Note the actual tag name may be the same as the
ItemID or may be different.
The FULLPATH keyword can be used to override the default target folder for any tag.
DESCRIPTION, HIGHENG, LOWENG and UNITS are optional and must not appear if they are
not configured in the associated Tag Template.
Comment line should be preceded by a # character.









To use History Catch-up you must have at least one OPC Station that supports HDA 1.1. If the
OPC server is installed on the Exaquantum Server itself then it will be of no use for History
Catch-up should the actual Exaquantum Server machine go down.
You must configure the OPC Server to store the data locally on its hard drive. There is therefore a
physical limit to the amount of data available for the Catch up mechanism. This will depend on
the amount of available disk space and the number and communications settings of the OPC
items.
The History catch-up process must be performed during the Exaquantum system start-up. A full
History Catch Up is expected to take around one twentieth of the shut down period.
If a 20,000 tag Exaquantum system is shutdown for eight hours, the History catch-up and
Exaquantum Start-up time should be less than 30 minutes.
Note:
The times given in the example will vary depending on the specifications of the computers used
in your Exaquantum system.

History Catch-up is performed when the system is restarted after the shutdown. It is possible to
control this mechanism using the Exaquantum Service Manager (see Day 3 Slides 7 and 8).
If Abort on first failure is selected and an OPC HDA request fails for the OPC Server, the
Exaquantum start-up will be abandoned. This will cause the Exaquantum start-up to fail. Failing
start-up gives the administrator the opportunity to correct the error and restart Exaquantum. In
this case, History Catch-up is automatically restarted from a clean point prior to the failure. As the
Exaquantum system has not started, the data should not be lost. The History Catch-up period will
cover the period of the attempted, and subsequent, restarts.
The Alarm and Event History Catch-up process runs in parallel with the live Exaquantum system.
When the Exaquantum system is live, the current Alarm and Event data is collected, stored and is
available for viewing as normal. In parallel, Alarm and Event history catch-up starts to fill the gap
and, depending on the length of the downtime, it may be some time before the gap in Alarm and
Event history is filled. The Alarm and Event History catch-up is complete when it reaches the
time that Exaquantum went live after starting up. This is identical to the end time of the catch-up
of the item data that took place during start up.
For more information on Exaquantum History Catch-up see section 4-10 of Exaquantum
Engineering Guide Volume 1 (pages 4-33 to 4-35).


Note this tool can also be used to configure Exaquantum to start automatically when the operating
system starts up.
Exaquantum can also be configured to shutdown automatically when the system shuts down. This
procedure is described in the Exaquantum Engineering Guide Volume 1, Chapter 4 from page 4-
37 to the end of the chapter.

For history catch-up to work the Exaopc Station must be configured to store data locally. This is
not the default configuration and therefore the configuration must be altered using the Exaopc
Station Setup program.
This slide shows the settings of the training room Exaopc Station at Yokogawa Marex.
The Scope of Keeping describes what is going to be kept. This can be Nothing which is the
default, Specific Items or All. Normally this will be set to All but using a wildcard filter it is
possible just to save only particular items. If using the Specific Items option is also possible to
configure Exaopc to save values periodically rather then on change.
The Number of Records governs the amount of data for each data item that will be stored. This is
a fixed number of records and the buffer is circular. When the buffer is full the earliest records
will be overwritten. The default number is 2880. The amount of data this will store depends on
how often the item updates. For example assuming that value changes every scan then the
following the default number of records for a selection of update rates is given in the following
table.
Update Rate Period Covered
1 sec 48 minutes
5 sec 4 hours
10 sec 8 hours
1 minute 2 days
2 minute 4 days
10 minute 20 days
1 hour 120 days
Notes continued on the next slide which does not form part of the presentation.

This slide is not part of the presentation and continues the notes from the previous slide.
The Data Gathering Mode can be set to either store data when the item values change or
periodically based on the Interval specified in the Scope of Keeping (see previous slide). The
Deadband can be set if required to limit the amount of data stored. Care needs to be taken here as
unlike Exaquantum there is only one Deadband value. You should however note that it is this
deadband that gets used to store data on the OPC Server not that configured for items in
Exaquantum. This means that during History Catch-up it is possible that the resolution of data
(amount of data retrieved) may be different from that collected had the Exaquantum Server not
needed to run History Catch-up to recover it.
The Extension After Removing option is the time that data for any item will be maintained after it
has been deregistered by all clients. This means that, if the Exaquantum Server is down for longer
than this and if it is the only client then data will be no longer available. This can be overridden
by setting the Permanent flag on the bottom right of the dialog.
The Save Folder is the location where Exaopc will create and maintain the historical records for
each item. The disk space usage can be estimated by using the following formula:
Disk Space = (Storage Period (secs)/Interval (secs)) x Items x 32
The options in the Historical Events group is are similar to those for data items although all
categories of events are stored in a single file.


The main purpose of this exercise is to show the features of each of the Generation Methods. It
should confirm the comments made during the session about when each method is applicable and
its limitations.
To make the file generation methods more interesting the files provided are not absolutely correct
and must be edited in order to complete the task. You will use the files as provided initially and
then edit them from within the interface in order to complete the generation.




way.

Both Read and Write groups are included in this discussion.
Backward compatibility issues with clients running with an Exaquantum release prior to 2.10.50
is also covered.


The Microsoft Windows user/group mechanism provides a Discretionary Access Control.
Use of Local or Global groups in the Domain paradigm is the prerogative of the Domain
Administrator. Global Groups under the control of a Domain Administrator is the most secure but
Local groups would provide for a distribution of control of Exaquantum Access. This would mean
that someone other than the Domain Administrator could be responsible for the security on the
Exaquantum Machine.
By default Exaquantum uses local users and groups to control access.

Exaquantum will check the users access rights in order to control access. If this is not possible
then access will be denied.
When clients login to Domain based accounts the Exaquantum Server must also be a member
server of the domain.

Windows users can be a member of any number of groups.
In the case of Exaquantum, all users should belong to as many groups as is required. A user
should never have more rights than he needs to do his job in most cases.
Memberships of user groups are assigned by the Domain Administrator if global groups are being
used and/or a Local Administrator of the Exaquantum Server if local groups are to be used. This
is performed using the Windows Active Directory Users and Computers Tool or Windows Users
and Control Panel/Administrative Tools/Computer Management Tool.

Exa products include Exaquantum, Exaopc, Exapilot and Exaplog amongst others.
Security Model is selected early in the installation or can be set using the IT Security Setting
Tool.
The Standard Security Model has two varieties (Standalone and Domain) both selectable on the
tool and during installation and from the tool (See Day 2 Slides 136 and 137 for differences
between the two)

The difference between standalone and domain management configuration is covered after the
discussion of the users, groups and other security considerations(see Day 2 Slides 136 and 137).

Anybody who requires access to Exaquantum must be a member of the QTM_DATA_READ

group.
Only those users who are in the QTM_DATA_WRITE or QTM_MAINTENANCE groups will be
able to update data.
In order to install Exaquantum the user must be a member of the EXA_MAINTENANCE group.

Membership of either the QTM_MAINTENANCE or the QTM_EXPLORER_DESIGN is

required to add Mimics and Report to the Exaquantum/Web Database.
QTM_EXPLORER_DESIGN group membership is also required in order to publish Web

Graphics and other Web Pages to the Legacy Exaquantum/Web Database.
Users in the QTM_MAINTENANCE group must also be in the Local Administrators Group. A
user in the QTM_MAINTENANCE group can change any item value and make any
configuration changes via the Exaquantum Administration tools.

The password for the QTM_PROCESS, QTM_SQLSERVER and EXA_PROCESS users can be
changed using application supplied on the Exaquantum Installation DVD. If you change these
password they must be the same where ever they are used for example on clients and in multi-
server environments.
The Password for the OPC_PROCESS should not be changed.
None of these accounts allow interactive logins to be made.
The QTM_PROCESS is in all the QTM groups and is a Local Administrator
The EXA_PROCESS is in no groups by default
The QTM_SQLSERVER is in the QTM_MAINTENANCE group and is a Local Administrator
The OPC_PROCESS user is in the QTM_MAINTENANCE group but is not a Local

Administrator
THE QTM_SQLSERVER is also in the SQL Server User group and the SQL Server Agent User
Group

A series of windows command files are provided in the Tools\DCSecurityBatch folder on the
Exaquantum Installation DVD to aid the correct Domain Controller Configuration.

The EXA_MAINTENANCE_LCL group can be created using the QTMPreSetStdModelDom.bat

tool in the tools folder of the Installation DVD.
Creating these groups locally provides the ability for non-domain clients to get data from
Exaquantum via OPC (QTM_OPC_LCL) and also allows maintenance of Exaquantum if the
domain controller cannot be contacted for some reason (EXA_MAINTENANCE and
QTM_MAINTENANCE).
The are also used by the service users described on Day 2 Slide 135.

An example of a complex security model would be when a customer has a number of different
independent Exaquantum Systems on the same domain and access to each system must be
individually controlled. Users who can connect to one server should not be able to connect to
another unless this is explicitly configured.
See following three slides for details of Legacy Model Service User and Groups.

An example of a complex security model would be when a customer has a number of different
independent Exaquantum Systems on the same domain and access to each system must be
individually controlled. Users who can connect to one server should not be able to connect to
another unless this is explicitly configured.
The Secure Lockdown mechanism provides a way to change a number of the Legacy Module
settings including the Exaquantum and SQL Server Service Users and switch to domain based
service users and/or groups. Performing a Secure Lockdown is out of the scope of this course and
is covered on the Exaquantum Installation and Configuration course (NTPP902).
See following three slides for details of Legacy Model Service User and Groups.

A user in the QAdministratorGroup has access to the Exaquantum Administration tools and
therefore can update such things as item values, tag templates and function block templates as
well as add, modify and delete tags etc.
Membership of either the QAdministratorGroup or the QExplorerDesignGroup is also required to

add Mimics and Report to the Exaquantum/Web Database.
Membership of the QExplorerDesignGroup is require to publish any web pages when using the
Legacy Exaquantum/Web.
These groups are only used when the Legacy Model is selected. They are always created locally
on the Exaquantum Server.

Password is user specified during installation but must be the same on all servers and clients. If
the QuantumUser password is reset then it is necessary to reset the security using the IT Security
Setting Tool.
Set the local security policies to deny local login to the QuantumUser account.
If a Secure Lockdown has been performed then the Service User Name may be different to
QuantumUser and the Exaquantum and SQL Server Services may be configured to “run as”
different users.

By Intrinsic here we are referring to that created during installation or the IT Security Tool. It is
not dependent on whether Legacy or Standard Security is being used.


This is the default namespace used by all users in the QUserGroup who are not members of any
RBNS group. You should note that as this is the default case any user who is not placed in an
RBNS group will see all tags configured into the system.

There are no hard coded names for role based groups. They are defined on a case by case basis
and depend on the actual use of the system.
What a user can or cannot see is defined on a per group basis by the Exaquantum Administrator.
The Exaquantum/Explorer Data Selector will show a drop down list if a user is a member of more
than one role.
All users will still need to be members of the basic access group (QUserGroup or
QTM_DATA_READ depending on the Security Model in use).
Each role is assigned two groups a Read Group and a Write Group. Only users in the specific
Write Group and the basic Data Write Group (QDataWriteGroup or QTM_DATA_WRITE) or the
basic maintenance group (QAdministratorGroup or QTM_MAINTENANCE) will be able to
write to those tags which have been given write access.
Users will also need to be a member of Explorer Design group (QExplorerDesignGroup or

QTM_EXPLORER_DESIGN) if full access to Exaquantum/Explorer is required.
All users configured to use a particular role see the same view of the data.



This shows the situation when 3 servers are configured. You should note that each server must
have a unique licence code otherwise errors will be generated in the event log. You should also
note that Exaquantum will periodically check to see if it can see all Server which have been
configured. If this is not possible again errors will be generated. The interval between checks and
other multi-server check parameters are configurable using the System Configuration tool (See
Day 3 Slide 147 - 152)

The name of the role doesn’t need to match the name of the Windows Group. In this case a Read
and a Write Group is configured.
It is possible for either or both the Read and the Write Group to be null. For a discussion on the
effect of null groups see Day 2 Slides 168 - 170.

Enter the Name in the Name field and then click on the … buttons to obtain a list of groups (see
next slide). You can also type the name of a valid group directly in the edit box if you prefer.

This shows the list of available groups which are known to the Server. This slide shows the Local
Groups on a machine called YMX032 and other domains or workgroups which the administration
client can see. You should only select Local Groups if the Server is in a Workgroup but you can
select either Local or groups on the Domain Control for the domain to which the server belongs.

This shows the pop up menus that allow you to configure the data tree for the selected role.
Note there are four options:
Reference Folders – This allows existing folders and all their function blocks and tags and sub-
folders to be accessible from this role. The name of the folder in the role data selector may be the
same or different to the actual folder name.
Folder – This is a new folder which will be displayed by the data selector when using this role. It
does not map to anything else in the Exaquantum system.
Function Blocks – This allows you to map individual function blocks into the view.
Tags – This allows you to map individual tags into the view.

This will create a sub-folder under the role name.
It does not map to anything in the default name space.

In a multi-server configuration you will also need to specify which server you wish to link to. The
… button will display the Intrinsic Data Selector to allow you to select existing folders (see Day 2
Slide 158). This will be automatically generated from the selected server.
Even when referencing a folder you may not wish to include all the Function Blocks or Tags. The
various options on the Filter Tab are used to filter in or out those which are required or not
required.
The filters here use the Regular Expression mechanism provided by VB, see next few slides for
some details.
By default the ‘Show aggregations’ option is unchecked and the ‘Include sub-folder’ option is
checked.
Please note the last line of the dialog which shows that the Tags filter affects all tags whether
within a function block or not.

For examples of use and other explanations use SQL Server Books Online and enter the word
pattern into the edit box. Double click on “pattern searching” and then “Pattern Matching in
Search Condition” from the pop up dialog.



This is used to select whatever is required. This depends on whether you are using the Reference
Folder, Function Block or Tag option.

The Security tab performs the same function for each of the options in that it allows you to select
which tags have write access and which ones do not. The actual display however is obviously
different (see later slides).

These dialogs are similar to those for Reference Folders except now we are only talking about
filtering for Tags within individual Function Blocks.

This will just list the selected tags within the specified function block.

At the individual tag leaving the configuration is obviously much simpler.

Effectively these roles are different views of the data.
These may be a sub-set, have different names, contain folders and sub-folders.
Provides access to more than one server transparently.
A user can switch his view from one role to another but if you configure a document using a
particular role then all users of that document must belong to that role or else the tag will not be
accessible.
A document can have tags using more than one role and in this case all users of this document
must be in all the roles used to be able to see all the data.


All of the above tags could well be referencing to the same tag but with different Role Based
Name Spaces employed.

This slide shows the different views pictorially.

This shows the Data Selector with three different Role Based Name Space configurations. The
third example only shows a part of the selector showing the RBNS selector at the top. This is the
situation that would occur if the a user was in more than one RBNS Group.
By default, if a user is in any RBNS group then they do not see the tree starting with Root.
However, this is configurable by selecting the Access Root Folder option on the General tab of
the System Configuration tool (see Day 3 Slide 151). With this option selected Root will appear
as an option in the drop down list wherever the data selected is presented, even if the user is also
in a RBNS group. Note that in a multi-server environment the tag tree displayed under Root will
be that for the Designated Server or the Secondary Server if the Designated Server was
unavailable at the time the client application connected.


The basic access group here depends on the security model used and will be either QUserGroup
or QTM_DATA_READ.
For further details see Exaquantum PIMS User’s Manual section 5.5 pages 5-2 to 5-5.

Data Write group will be either (QDataWriteGroup or QTM_Data_Write) and Maintenance group
will be (QAdministratorGroup or QTM_MAINTENACE) depending of Security Model being
used.

You do not need to configure this unless you are using Role Based Name Spaces. If you do wish
to use this facility then you will need to configure this screen even in a single server system.
If a client has the Exaquantum Administration tools installed then they can be configured to
manage any available server. You do not need to physically log on to the server.

This tool can be used to configure a client to allow the administration tools to connect to a
particular server or to either the designated or secondary server.
The Drop down list only shows those Servers that have been configured in the Server Screen.

To ensure that configuration is identical on Designated and Secondary Servers click on the
Publish button at the bottom of the screen (see next slide).
Note it is possible for all servers to have a different RBNS set up but if the Designated/Secondary
mechanism is used then, if they are different, different behaviour would result and in some cases
data may not be displayed or incorrect data might be displayed.
To avoid this you should always configure RBNS on one server and then publish it to all the other
servers.

Roles can be local to an individual server or can be similar on more than one server. This dialog
allows you to copy all the namespaces configured on this server to any of the other configured
servers.
In the case above there is only one configured server and therefore the operation is not available.
As a general rule RBNS configuration changes should be performed on one machine and
published to all other servers to ensure that the configuration is consistent.

This is a client tool which can change the designated server; it is only available on clients. The
Network Test mechanism is covered in Session 8 (See Day 3 Slides 124 – 128).


It does not matter about the case for the user names but all passwords are in lowercase.
Role Based Name Spaces are again very customer specific and these exercises are designed to
show the techniques and options available and to give you experience in using the Builder Tool.






M037 Exaquantum Administrator Course Day 2

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

M037 Exaquantum Administrator Course Day 2

Încărcat de

Drepturi de autor:

Formate disponibile

NTPP901 - Exaquantum Administrator Course 20th January 2014

Sessions 1 - 3 will be covered on day 1. Sessions 4 -6 will be covered on day 2.

M037 Issue 18 Day 2 Slide No. 1

M037 Issue 18 Day 2 Slide No. 2

The Tag editor can be used for the following:

Two view modes are available:

M037 Issue 18 Day 2 Slide No. 3

M037 Issue 18 Day 2 Slide No. 4

This slide shows the menu when a folder is selected.

Rename allows you to change the name of the selected object.

Refresh Node will re-read the configuration database.

M037 Issue 18 Day 2 Slide No. 5

Five types of objects are supported:

M037 Issue 18 Day 2 Slide No. 6

M037 Issue 18 Day 2 Slide No. 7

M037 Issue 18 Day 2 Slide No. 8

M037 Issue 18 Day 2 Slide No. 9

M037 Issue 18 Day 2 Slide No. 10

Examples of an Exaquantum OPC Item ID would be

M037 Issue 18 Day 2 Slide No. 11

M037 Issue 18 Day 2 Slide No. 12

M037 Issue 18 Day 2 Slide No. 13

M037 Issue 18 Day 2 Slide No. 14

M037 Issue 18 Day 2 Slide No. 15

M037 Issue 18 Day 2 Slide No. 16

M037 Issue 18 Day 2 Slide No. 17

This option is on the RTDB tab (see Day 3 Slide 148).

M037 Issue 18 Day 2 Slide No. 18

M037 Issue 18 Day 2 Slide No. 19

M037 Issue 18 Day 2 Slide No. 20

Select the OPC Gateway using the drop down list.

M037 Issue 18 Day 2 Slide No. 21

M037 Issue 18 Day 2 Slide No. 22

M037 Issue 18 Day 2 Slide No. 23

M037 Issue 18 Day 2 Slide No. 24

M037 Issue 18 Day 2 Slide No. 25

M037 Issue 18 Day 2 Slide No. 26

M037 Issue 18 Day 2 Slide No. 27

In this instance the function block 00FC001 has four references.

M037 Issue 18 Day 2 Slide No. 28

M037 Issue 18 Day 2 Slide No. 29

Note the red text immediately under Settings.

M037 Issue 18 Day 2 Slide No. 30

M037 Issue 18 Day 2 Slide No. 31

M037 Issue 18 Day 2 Slide No. 32

An example report is provided in the NTPP901 Solutions folder for Session 4.

M037 Issue 18 Day 2 Slide No. 33

M037 Issue 18 Day 2 Slide No. 34

The primary quality of offline tags is set to Assumed.

M037 Issue 18 Day 2 Slide No. 35

For the result of this see next slide.

M037 Issue 18 Day 2 Slide No. 36

M037 Issue 18 Day 2 Slide No. 37

The value of the Calculated Tag remains unchanged.

M037 Issue 18 Day 2 Slide No. 38

M037 Issue 18 Day 2 Slide No. 39

M037 Issue 18 Day 2 Slide No. 40

The Value tag is completely new.

M037 Issue 18 Day 2 Slide No. 41

M037 Issue 18 Day 2 Slide No. 42

M037 Issue 18 Day 2 Slide No. 43

M037 Issue 18 Day 2 Slide No. 44

M037 Issue 18 Day 2 Slide No. 45