Baselines

Baselines are views of a project consisting of all disciplines saved at a particular state. Disciplines can continue to change data and create new revisions of data without changing the project views saved to baselines. Baselines can be created at any time after the initial project configuration has been defined. In practice they are likely to be created at key project milestones. Refer to the Administration User Guide for further information.

Note:
Access to the Baseline Multiple Databases (MDBs) are reserved for system engineers or engineers with responsibility for creating consistent data sets.

Use the Baseline window to define tags and attributes and populate the baseline.

Note:
The project must be in Controlled Object Revisioning (COR) mode and the System Engineer must be logged into a Baseline MDB for the option to be available.

Attributes

Use the Filter Attributes window to define attributes which are displayed for the filtered tags. A set of attributes is displayed for each discipline, the required attributes can be moved from the Available attributes list to the Selected attributes list by using the arrow buttons.

Use Clear All to remove all attributes from the Selected attributes list.

List Tags

Populates the Baseline window with all tags that can be brought into the current baseline from the discipline teams.

Governing discipline

The Governing discipline drop-down contains a list of all available disciplines, but it will remain disabled until the tags list is populated. The Governing discipline column is populated when the Governing discipline selection is changed, but the selected discipline is only applied to the current set of filtered in columns.

The discipline cell is populated if the tag does not have issued component data for the selected discipline.

Each cell in the Governing discipline column contains a drop-down list of disciplines available for the tag to override the common value.

Accept Filtered

Accepts and adds all the filtered-in tags to the current selection, based on what is visible as a result of the current filter. A tag cannot be accepted until it has a discipline assigned.

Clear Filtered

Clears accepted tags.

Note:
Using List Tags clears any accepted tags, filters and the governing discipline. If any attribute selected for filtering is not valid on a particular tag then a blank value is displayed. Unset values are displayed blank.

Accept Column

Defines the tags that are accepted for baseline population.

If the check box is selected, the tag is accepted for baseline population.

If the check box is not selected, the tag is not accepted for baseline population.

Tag Column

Displays the tag name (NAME attribute).

Baseline Column

Defines all tags that have already been added to the current baseline.

If the check box is selected, the tag has already been added to the current baseline.

If the check box is not selected, the tag has already been added to the current baseline.

Relationship Column

Set to the project default and can be changed using a drop-down list.

System

Displays the systems to which the tag belongs (SCSYSF attribute).

Revisions Column

Once the governing discipline has been set for a tag, the list of available revisions for that discipline component is populated.

When a different revision is selected, a new set of related component revisions are displayed for the other discipline components in the tag. Other discipline component revisions can only be changed by the system engineer in the Interface Attributes window.

Populate

Populates the current baseline with all of the accepted tags. For each tag, the component that corresponds to the selected discipline will be brought down at its latest revision. All other components are brought down using the related revisions recorded for the governing discipline component.

Interface Attributes

A discipline component has an interface to other discipline components in a tag. The interface is a set of attributes that are considered to be of interest to that discipline. In the baseline functionality, the interface attributes are used to determine a level of compatibility between revisions of a component.

For example: consider a tag with mechanical, process and electrical components.

The mechanical component has an interface with the process and electrical components. The interface with the process component can be defined as the operating temperature and operating pressure. The interface with the electrical component can be defined as the power load and power rating.

The process component has an interface with the mechanical and electrical components. The interface with the mechanical component can be defined as the fluid code and test medium. The interface with the electrical component can be defined as the power load, power rating and current.

COR takes the attributes in subscriptions set up by a discipline team as the interface attributes. The discipline team should create a database view that contains the attributes required as interface attributes. In the first example above, the mechanical team would create a database view containing mechanical attributes, plus the interface attributes from the other components.

A discipline team is a team that is associated with a discipline. This association is done on the Team definition window in AVEVA Administration. More than one discipline can be associated with a team. The first discipline in the list is considered to be the primary discipline. This is the discipline that COR uses in this context.

Select a single tag using the row selector and clicking Interface or double-click the tag row selector to display the Interface Attributes window.

The Interface Attributes window responds to a new tag selection and is populated with the governing discipline or relationship.

The first row of the Interface Attributes window is populated with the component revisions currently selected in the tag list. The second (preview) row shows revisions from the opposite relationship, for example: if the issued against relationship is currently set for a tag, the preview row shows component revisions as if the consumed by relationship is selected.

The governing discipline is placed first in the row, the available revisions on other components can be selected.

Differences between attribute values of the current revision and the previous revision are highlighted.

Update

Transfers changes back to the main menu and accepts the tag ready for population.

Related Revisions and Discipline Classification

A system engineer can use these baseline features to bring down a set of issued tags into the baseline.