Description of the Supplied ABA Tasks

To modify the *Report_Labels task, on the Process Drawings Control Tasks window, select *Report_Labels in the Tasks Selected list and click Modify Task to display the /*Report_Labels window. The functionality of the /*Report_Labels window is explained. Refer to Report Labels for further information.

Hyper_Plant

The /*Hyper_Plant task produces a series of files which can be used to interface to the AVEVA HyperPlant product.

The task produces four files, which are linked by a common field ‑ an index number that represents a drawing:

•

Plotfile, for example, -dra1.plt

A base product format plot file, one for each drawing produced during an ABA process run.

•

Hit file, for example, -dra1.hit

A text file that contains data about each label that appears on the drawing, specifying the label location on the page (0,0 is bottom left), the relevant design element reference and name.

One file is produced for each drawing produced during an ABA process run.

•

Sheets file, for example, -[base product]_dsheet.out

A file that provides the link between each drawing and its related plot file and hit file.

A single file is produced for the ABA process run.

•

Items file, for example, -[base product]_item_to_dsheet.out

A file that provides the link between a design element and the sheet on which it appears.

For example, if you wish to know on which drawings the equipment /PUMP1 appears, the four files produced can be:

dra1.plt; dra1.hit; [base product]_dsheet.out; [base product]_item_to_dsheet.out

You can scan the items file [base product]_item_to_dsheet.out to determine the index of the sheets on which /PUMP1 appears.

The sheets file [base product]_dsheet.out can then be read to find which plotfile and hitfile relates to which sheet.

To modify the *Hyper_Plant task, on the Process Drawings Control Tasks window, select *Hyper_Plant in the Tasks Selected list and click Modify Task to display the /*Hyper_Plant window. The functionality of the /*Report_Labels window is explained. Refer to Hyper Plant for further information.

Drawing Tasks

Drawing tasks operate on a specific drawing. Refer to Create and Modify Template Drawings for further information

Keyplan_View

Keyplan_View is the Overlay Sheet method for keyplan production. It produces an OLAY based keyplan at SHEE level. To function correctly, the OVER name specified in the options must exist in the library. The OVER must be constructed with SpPURP ABAT, and it should own a VIEW of SpPURP ABAK.

To process the view, you must be at or below the keyplan overlay sheet (OVER). On the Area tab, in the Create group, click Keyplan Layers to display the Add Hatched Areas to an Overlay window. The functionality of the Add Hatched Areas to an Overlay window is explained. Refer to Overlay Sheet Method for further information.

All the necessary layers corresponding to each of the existing areas built in the area definition library are created.

When the drawing is processed, an OLAY element is created under the SHEE element that references the specified OVER and displays the correct hatched layer for the relevant area. To achieve this the OLAY attribute is set to OSLV to include the design and the layer number that corresponds to the relevant area.

The OLAY is named as per the SHEE name plus the suffix /Keyplan

Report_Labels

Produces a report as specified in Process Tasks, but in this case produces a single report for the relevant drawing.

Schedule

Produces a table which creates a list of given elements according to a specified discipline drawlist. The discipline is normally the same IDLI as that created for the view contents. The table can be created vertically down or horizontally from left to right.

In order to facilitate the table, create the relevant symbol templates for the header, table entry, and last entry (if different), that extracts the relevant data using Intelligent Text.

To position the table on the Sheet and permit overflow areas, create a series of one or more Reserved Areas on the relevant Backing Sheet. The Reserved Area exists in a NOTE on the Backing Sheet and has the function attribute set to Table Data. The LVIS should be set False so that the rectangles do not appear on the final drawing.

Each rectangle should have the Fill Pen (FPEN) attribute set to indicate the order in which they are to be filled. That is, the main reserved area rectangle is set FPEN 1 with subsequent rectangles set to 2 onwards. The origin of the rectangle is important since it determines the position of the first symbol within it. For example, the first reserved area rectangle for a vertical fill would have the origin at the Top Left if the relevant symbols also had their origin at the Top Left.

View Tasks

Views tasks operate on a specific drawing view. Refer to Create ABA Template Drawing and Create and Modify ABA Template View for further information.

Arrange_Labels

Scans the view for existing labels and arranges them around the border of the view to the specified options. For example:

Draw_MeasureLines

A series of lines are produced at the View limits to indicate a rule scale set to dimensions specified in the options.

The lines are produced in a unique LAYE element named as per the VIEW plus a suffix /Measure.

North_Arrow

A north arrow is added to the View and is orientated to indicate the true North direction of that view. The location of the north arrow can be set by creating a Reserved Area on the template drawing.

Create a VNOTE below the template view with LVIS FALSE and under it create a RECTangle with its origin at the centre and part-named with the string ‘n_arrow’. The task looks for this rectangle and uses its position for the north arrow symbol. If the rectangle does not exist, then the symbol is placed at a default position defined as the top-left corner of the view.

The north arrow is orientated to conform to the actual north direction of the view. It also functions correctly with any of the Isometric views, Iso 1 to 4 inclusive. Any other view direction such as elevation view is not given a north arrow.

The user can reposition the created SYMB element if required using the DRAW standard application tools.

The north arrow SYMB is created in a unique LAYE element which is named as per the VIEW plus a suffix /NorthArrow

Name Tasks

When a Template/Area combination is selected during the drawing creation process, the default drawing name is the concatenation of the element names. For example, a drawing which used the template /DRTM-PIPING-A0 and area /A101 would be called /DRTM-PIPING-A0-A101.

An alternative naming method is provided by the inclusion of a user defined naming task, this is a pml function which is run at the time the drawings are added to the drawing process window. It is slightly different to other tasks because the template and area names are inserted into the passed parameters as parameter 1 and 2, and the actual task parameters are appended.

Another difference is that the task function is expected to return a string to ABA. If the return string is empty, the default name is inserted instead.

Name Check in Naming tasks

Naming tasks are used to check if a drawing name is already in use, this is achieved by checking the database for a particular name, but it is possible that the name is also used in the list of drawings about to be created by ABA itself.

To check if a base product name has been used elsewhere, use the following method called from user defined tasks:

!!abanewdrwgs.checkname(!namestring) where namestring is the required name.

The routine returns one of three values. 0, 1, and 2, where:


0	means the drawing name is available
1	means the drawing name has been used in AVEVA E3D™
2	means the drawing name has been used in the list of drawings about to be created by ABA.

An example of code to check this is:

!num = !!abanewdrwgs.checkname(!namestring)


if !num eq 0 then
return !namestring $* its ok so use it
else
!!alert.error(‘Name already used’)
return ‘ ‘ $* return a blank name
endif