PPRU - CAN
5.5 HERRAMIENTAS DE GESTIÓN DEL PLAN PARCIAL A CARGO DE LA ENTIDAD GESTORA
This chapter covers the configuration and setup of dictionary (LEXICON) elements required for the implementation of object revisioning and interdisciplinary project activities.
Revision configuration for datasheets instances will be covered in chapter 6 (Datasheet configurations)Create Revision Configuration World (REVCWL)
Select the topmost element in the dictionary explorer (Dictionary World), right click to display the context menu. Select the ‘Create’
entry, to display a sub list of dictionary elements worlds, and select the ‘REVCWL: Revision Configuration World.
Within the Current Element Editor, fill in the attribute details of the created REVCWL as shown.
Create Revision Configuration Group (REVCGP)
Select the newly created
111
www.aveva.com
© Copyright 1974 to current year.
Within the Current Element Editor, fill in the attribute details of the created REVCGP as shown.
Create Revision Number Definition (REVNOD)
Select the newly created REVCGP, display the context menu and click ‘Create’ >
‘REVNOD: Revision Number Definition’ to create a Revision Number Definition.
The REVNOD element allows for the specification of revision numbering for controlled engineering objects.
Here for example, a ‘working’ and an ‘issued’ numbering and number format can be defined for controlled objects after a status change.
Within the Current Element Editor, fill in the attribute details of the created REVNOD as shown.
Configure the revision number format by editing the REVNOD as described.
www.aveva.com
Select the newly created REVNOD, display the context menu and click ‘Edit Revision Number Definition’
and within the Revision Number Definition, fill in the entries details as shown.
‘Working revision text’ value will be appended to an object which is at a status referenced by this number definition. Enter an asterix (*) in the field. This will be further explained in the next section.
‘Number of Parts’ specifies the number of combined characters the numbering format should take on.
For example, (A1, A2, B1, B2 etc.).
Each part can be configured as a numeric or alphabetic characters.
With the ‘Formatting’ section of the form, the length of the revision number characters can be increased from 1 character to 10 characters (per part), with Alphabetic characters being padded with an ‘A’ or Numeric characters padded with a ‘0’.
For Example (AA1, AA2, AAA1, A01, A02, A03, A001 etc.).The ‘Fixed length’ check box will have to be checked before the length of the part can be increased.
Customised revision numbering texts/format can be utilised, from clicking on the ‘Custom’ radio button113
www.aveva.com
© Copyright 1974 to current year.
Click the ‘Test’ button to preview the configured numbering format.
Click the ‘OK’ button to accept the changes.
The ‘Working revision text’ value (*) will now be visible in the entry field.
Create Revision Configuration (REVCON)
Select the created REVCGP, display the context menu and click ‘Create’ > ‘REVCON:
Revision Configuration’ to create a Revision Configuration.
For element name, enter: ENGR-REVISION-CONFIGURATION’.
www.aveva.com
The revision configuration (REVCON) brings together essential elements required for the revisioning of objects. It allows for the selection and referencing of appropriate status definition (STADEF), revisioning numbering and relevant element types.
Select the created Revision configuration ‘ENGR-REVISION-CONFIGURATION’, display the context menu and click Edit Revision configuration’ fill in the entries details as shown.
Click on the browse button to display the ‘Select Element Types’ form, and select the required objects which have their revisioning controlled by this configuration:
Include the following:
115
www.aveva.com
© Copyright 1974 to current year.
Select the status definition from the pick list as shown.
This selection will populate the pick lists of ‘Create working revision at:’ and ‘Issue revision at:’ entries with all available status values of the STADEF.
This means that when the status of an item (based on a selected element type) is changed to ‘working’, the revision number value (*) will be applied to that item.
This is also the case when the status of an item is transitioned to ‘Issued’ state, then the revision number of that item will be applied to the object. (For example A1)
The Revision numbers on controlled objects are called from the value of a special attribute: ‘RVCURR’Select the required revision number definition as shown:
The revision number mechanism will now apply to objects controlled by this revision configuration.
The Revision block definitions are required for the creation and setup of datasheets revision blocks.This will be demonstrated later in this guide
Click the ‘OK’ button to accept the changes.
www.aveva.com
Select the created Version control configuration fill in the entries details as shown.
The version Control configuration (VERCON) specifies the behaviour of an engineering object when it attains a defined status level.
According to the pre setup maturity levels, extract objects will have data changes/modifications dynamically
‘Issued’ to the next higher level and revisioned as soon as that object has its status is set to a pre-configured value.
This behaviour is demonstrable from within the Engineering Tags application.
Please see the AVEVA Engineering User training manual for details on controlling objectsNote: The VERCON element must be named. It has been named ‘Tags’ in this case.
The required Revision configuration is selected from the pick list as shown:
Selecting the Revision configuration will automatically have the ‘States to issue extracts’ pick list populated. This is because the Status Definition information (which includes Status values) is extracted from the selected revision configuration.
117
www.aveva.com
© Copyright 1974 to current year.
The ‘States to issue extracts’ allows for the selection of required status values from a pick form.
Click the ‘OK’ button to accept the changes.
Data from the nominated element types are now ready to be transitioned across from an extract level to another (As configured).
Log into the Engineering Tags application as a user with access to the extract databases (For example a user at the ‘Working’ maturity level JNR.ELEC-A, MDB: ACE_ELEC_WORK) Set the status of a selected object to ‘Working’ this should dynamically give it the revision value of (*).
Make data changes and promote the status of that item to ‘Pending approval’. This should trigger a dynamic ‘Issue’. A user at the
‘Approving’ maturity level logged in as SNR.ELEC-A, MDB: ACE_ELEC_APRV will simply need to run a ‘Get work’. This will have his view updated with the data and changes made by the user within the lower extracts/level
www.aveva.com
If the approving user (Senior Engineer) at the
‘Approving’ maturity level is happy with the data, a promotion to an approved state can be
initiated. This will trigger a dynamic ‘Issue’ where by the data will be made available to the master or ‘Released’ level and database. A revision number can also be selected during the promotion.
The Shared services mechanism will need to be setup and configured before the full functionality of interdisciplinary workflow can be tested. This is covered in the following SectionExercise 7
1. Create a new revision configuration and revision numbering definition as demonstrated
119
www.aveva.com
© Copyright 1974 to current year.