Exercise 2 Testing Working Extracts in Design
3.4 Creating Scopes, Roles and Permissible Operations – A Worked Example
The following worked example will create a Scope for ALL areas of the work, a Role for ALL, a Role for a Piping Designer and Permissible Operations for the Piping Designer.
3.4.1 Creating a Scope
Scopes define the area of the plant where the PDMS Designer can work. The following scope gives access to all areas of the plant.
Click the Access Control Assistant button on the main menu to display the Access Control Assistant form.
Select the Scopes tab in the upper pane of the form. Right click on Scopes and select New scope from the pop-up menu to display a new scope row.
Double click in the Scope name field to edit the information contained within it. Enter ALLSCOPE in the Scope name textbox. In a similar manner enter All Scope in the Scope description text box.
Enter ALL in the Scope selection text box.
www.aveva.com
The syntax used to define Scopes is similar to the syntax used in PML. Key words, such as ALL, can be used in a DAC context. An example of the type of syntax used to define a Scope would be: ALL WITH NAME OF SITE EQ ‘<FULL PDMS NAME OF SITE>’.3.4.2 Creating Roles and Permissible Operations
A Role defines the type of objects that can be created. Roles can be created in two ways; by adding access or by removing access. The removal of access may occur in situations where a designer is initially given full access rights which are then restricted.
3.4.2.1 Create Role and Perop for ALL Access
Select the Roles tab in the upper pane of the form. Right click on Roles and select New role from the pop-up menu to display the new role row.
Enter ALL-DESIGNER in the Role name textbox. Enter Can create ALL PDMS elements in the Role description text box.
A new Permissible Operation (Perop) for the role is required.
Right click on the ALL-DESIGNER entry of the Role name and select New perop from the pop-up menu to display the new perop row.
Enter ALLELE in the Perop name textbox, followed by ALL in the Element types textbox. Leave the Qualifying Condition as unset.
Open the Operations options list. Each entry, i.e. Create, Modify, Delete, etc, has three settings, Ignore, Disallow and Allow. Clicking each entry will cycle through these choices. Set all of the entries to Allow. Set the Attributes field to ALL and the Error message field to Can Create All.
3.4.2.2 Create Role and Perops for Piping Designer Access
The Role of the Piping Designer will allow the creation of pipes and pipe branches providing that the pipe has not been issued. The Pipe Designer may also connect to, and orientate, nozzles.
www.aveva.com
Enter PIPING-DESIGNER in the Role name textbox and Piping Designer in the Role description textbox. Right click on PIPE-DESIGNER entry of the Role name and select New perop from the pop-up menu to display the new perop row.Enter PIPE-DESIGNER-PIPE in the Perop name textbox followed by PIPE in the Element types textbox. Enter (Purp of Zone eq 'PIPE' and Function neq ‘ISSUED’) in the Qualifying condition textbox. Set all the Operations entries to Allow and enter ALL in the Attributes textbox.
Enter You can only create pipes in a Piping Zone that has not been Issued in the Error message textbox.
Create a new perop row to allow the Pipe Designer the ability to orientate position and connect to nozzles. Enter PIPE-DESIGNER-NOZZ in the Perop name textbox followed by NOZZ in the Element type textbox. Leave the Qualifying condition as unset.
In the Operations options list set Create, Output, Export and Copy to Disallow, Delete to Disallow and Modify, Claim, Issue and Drop to Allow.
Enter ORI CREF and POS in the Attributes textbox and enter You can only position, rotate and connect to Nozzles in the Error message textbox.
Create another Perop for the Pipe Designer that will allow Branches to be created if the Pipe has not been issued.
Enter PIPE-DESIGNER-BRAN in the Perop name textbox followed by BRANCH HIERAR in the Element types textbox.
Enter Function of Pipe neq ‘ISSUED’ in the Qualifying condition textbox. Set all the Operations entries to Allow then enter ALL in the Attributes textbox.
Enter You cannot create a Branch or Branch Components if the Pipe has been Issued in the Error message textbox.
The following Perops are now available.
Follow a similar process to create Roles and Perops for the Design Supervisor and the Equipment Designer. For the Role of the Equipment Designer, allow the creation of the equipment hierarchy only where the Purpose of the Zone is EQUIP.