Status Control

Status Control
AVEVA Solutions Ltd
Disclaimer
Information of a technical nature, and particulars of the product and its use, is given by AVEVA Solutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaim any and all warranties and conditions, expressed or implied, to the fullest extent permitted by law. Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person or entity for any actions, claims, loss or damage arising from the use or possession of any information, particulars, or errors in this publication, or any incorrect use of the product, whatsoever.
Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every part of it (including source code, object code, any data contained in it, the manual and any other documentation supplied with it) belongs to AVEVA Solutions Ltd or its subsidiaries. All other rights are reserved to AVEVA Solutions Ltd and its subsidiaries. The information contained in this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without the prior written permission of AVEVA Solutions Ltd. Where such permission is granted, it expressly requires that this Disclaimer and Copyright notice is prominently displayed at the beginning of every copy that is made. The manual and associated documentation may not be adapted, reproduced, or copied, in any material or electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also not reverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the product described in this publication may be incorporated into any third-party software, product, machine, or system without the prior written permission of AVEVA Solutions Ltd, save as permitted by law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal prosecution. The AVEVA products described in this guide are to be installed and operated strictly in accordance with the terms and conditions of the respective license agreements, and in accordance with the relevant User Documentation. Unauthorised or unlicensed use of the product is strictly prohibited. First published September 2009 AVEVA Solutions Ltd, and its subsidiaries AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom
Trademarks
AVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthorised use of the AVEVA or Tribon trademarks is strictly forbidden. AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or its subsidiaries, registered in the UK, Europe and other countries (worldwide). The copyright, trade mark rights, or other intellectual property rights in any other product, its name or logo belongs to its respective owner.
Status Control
Status Control
Contents
Page
Status Control
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1 Guide Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Example Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1

Status Control Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2
Configuring Status Definitions in Lexicon . . . . . . . . . . . . . . . . . . . . 3:1 Status Controller in Design and other Constructor Modules . . . . . 4:1
Status Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1 Edit Status Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4 Status History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6 Statistical Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:7 Status Controller Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10 Drag and Drop into Graphical View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10
Status Pseudo Attributes and Commands . . . . . . . . . . . . . . . . . . . . 5:1

Pseudo Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2
Using Status Control with Data Access Control . . . . . . . . . . . . . . . 6:1

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1
2009 AVEVA Solutions Ltd
12.0
Status Control
Example to Prevent Modification of an Object of a Certain Status. . . . . . . . . . . . . . . . . . . . Example to Catch when the Dictionary Database has been Deferred . . . . . . . . . . . . . . . . . Example to Prevent Change of Status after a Certain Level . . . . . . . . . . . . . . . . . . . . . . . . Example to Prevent Removal of Status from an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example where a User may only Amend Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6:1 6:1 6:1 6:2 6:2
Using Status Control with Auto Colours. . . . . . . . . . . . . . . . . . . . . . 7:1

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1
Example Rule for Equipment with Design Status Pending. . . . . . . . . . . . . . . . . . . . . . . . . . 7:1 Example Rule for Equipment with Design Work Completed or Higher . . . . . . . . . . . . . . . . 7:1 Example Rule for Equipment with Design Status Not Controlled. . . . . . . . . . . . . . . . . . . . . 7:1
Customising Status Control using PML . . . . . . . . . . . . . . . . . . . . . . 8:1

Status Events in PML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1
Status Change Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1 Database Change Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2
Customising the StatusProjectHandler PML Object. . . . . . . . . . . . . . . . . . . . . . 8:2

Debug Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to add Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Methods where you can Add Checks and Abort Changes. . . . . . . . . . . . . . . . . . . . . . . . . . Methods where you can make Dependent Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Methods where you can Synchronise External Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Constructors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Methods Intended for the User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Methods to Assign and Remove Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Methods to Promote and Demote Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Methods to Set Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internal Methods not Intended to be Called by User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example to Set and Get Status Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2 8:3 8:3 8:3 8:3 8:4 8:4 8:5 8:5 8:6 8:7 8:7 8:7
Using the StatusData PML Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:3
Using the Core Status Objects from PML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:8

Object STATUSMANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:8 Object STATUSEVENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:8 Example to Add an Event Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:8 Object STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:9 Object STATUSVALUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:11 Object ASSIGNEDSTATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:11 Example to Set and Get Status Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:11
ii
12.0
Status Control
Customising Status Control using C# (.NET) . . . . . . . . . . . . . . . . . . 9:1

Namespaces and Assemblies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1 Classes in .NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1
Class StatusManagement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class StatusValue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class StatusCommand. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Class StatusEvents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status Change Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Change Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1 9:1 9:2 9:3 9:3 9:5 9:5
Distributing Customised Status Layouts . . . . . . . . . . . . . . . . . . . . 10:1 Upgrading Model Manager Status Data . . . . . . . . . . . . . . . . . . . . . 11:1
iii
12.0
Status Control
iv
12.0
Status Control
Introduction
Introduction
Status Control is the ability to control and report on the status of individual model objects as they progress through their lifecycles. It can be applied to any model objects, e.g. tagged items, catalogue components, drawings, etc. It can be expressed in a variety of ways, e.g. Approved for Construction, 80% Complete, Clash Free, etc. The desired project configuration is created by administrators as Status Definitions in Lexicon. It is applied to model objects by end users in any of the constructor modules Design, Outfitting, Paragon, Spooler, Diagrams, Hull, Draft and Hull Drafting - using the Status Controller. Status Control can be tightly coupled with Data Access Control. For example, it can be configured so that only certain users may approve an object. It can also be configured to prevent changes to an object once it has achieved a particular status. A core concept for Status Control is that of a Controlled Object. A Controlled Object is defined as any model object that has one or more Status Values assigned to it. A Controlled Object may be controlled for multiple statuses to suit processes for design, manufacturing, fabrication, construction, etc.
1.1
Assumptions
End users have a basic knowledge of PDMS/Marine. Administrators have a reasonable knowledge of Lexicon, and if required can use the Access Control Assistant in Admin. Developers have a reasonable knowledge of PML and/or C# (.NET).
1.2
Guide Structure
This guide is structured as follows. Introduction Example Workflow Configuring Status Definitions in Lexicon Status Controller in Design and other Constructor Modules presents some concepts and overview illustrates a worked example used throughout this guide and explains the underlying data model describes how administrators can set up the status definitions for their project describes how end users can control the status of their model objects
1:1
12.0
Status Control
Introduction
Status Pseudo Commands
Attributes
and
provides details of syntax available to application writers gives examples for administrators to extend control of data integrity gives examples for administrators to customise graphical views shows developers how to add functionality from PML shows developers how to add functionality from C# shows where Status Layout files are stored describes an approach to convert existing status values in Model Management projects.
Using Status Control with Data Access Control Using Status Control with Auto Colours Customising Status Control using PML Customising Status Control using C# (.NET) Distributing Layouts Customised Status
Upgrading Model Manager Status Data
1:2
12.0
Status Control
Example Workflow
Example Workflow
Consider the following simple workflow for a Design Status definition which will be used as a worked example.
This example has a primary route from starting work through to releasing, with stages for checking and approving, and options at various stages to put back for rework.
2:1
12.0
Status Control
Example Workflow
2.1
Status Control Data Model

The Status Control data model defines an Example Workflow as a Status Definition (STADEF) object owning a set of Status Value (STAVAL) objects. Individual model objects reference the Status Values via Status Link (STALNK) objects, as illustrated below.
Status Link objects reside in the same database as the model objects they reference, so that they are globally distributed with those model objects. The Status Link holds references to the model object and to the Status Value, along with attribute data for comments and history. So status data is not stored directly on the model object and the user does not need write access to the model object in order to set its status. The Status Link objects are not visible to the end user, but the status data is available on the model object as pseudo attributes. Administrators need to know of their existence for purposes of Data Access Control.
2:2
12.0
Status Control
Configuring Status Definitions in Lexicon

Lexicon uses a hierarchy of Status World, Status Definition and Status Value data types to define a Example Workflow. In the Lexicon Dictionary Explorer, right click on the Dictionary WORLD and select New Status World then enter a name in the Current Element Editor.
Right click on the new Status World in the Explorer and select New Status Definition (the user can also create Status Groups to contain Status Definitions). Enter a Name and Description in the Editor Note: These will typically be similar but the description can include spaces and will be used in the Status Controller if it is set.
3:1
12.0
Status Control
The next step is to define the Controllable element types for this Status Definition. Click on the selection button to show the Select element types form.
3:2
12.0
Status Control
Select EQUIPMENT, click Add to list, and then click OK. The user can add other types if the definition is to apply to multiple types of elements. Right click on the Status Definition in the Explorer and select New Status Value. Enter a Name, Description and Numerical value in the Editor. Note: Numerical value is optional and may be used as a percentage or a simple value.
3:3
12.0
Status Control
Note: Status Value name uniqueness applies only within the owning Status Definition. So you can use repeat names such as Preliminary and Released in different definitions. Repeat this process to create the rest of the Status Values. You can then go to each Status Value and set its Valid transitions. Click on the selection button to show the Select valid status transitions window.
Select the status values that will be valid transitions from this value and click OK. In the drop down selection for Promote and Demote, select the appropriate values. Note: Promote and demote are optional and simply denote a main route through the workflow - any valid transitions not marked as promote or demote will still be available in the Status Controller.
3:4
12.0
Status Control
Select the Status Definition again in the Explorer and note its Initial status. Note: It will be set to the first status value by default but the user can change this if required.
The Status Definition is now complete and ready for use. Save work and exit Lexicon.
3:5
12.0
Status Control
3:6
12.0
Status Control
Status Controller in Design and other Constructor Modules

The constructor modules such as Paragon, Design and Outfitting, use the Status Controller to interact with Controlled Objects. Click on Display > Status Controller to display the Status Controller window. Initially this will be empty.
4.1
Status Layout
To display particular status data, click in the drop down list for Status Layout and select New Status Layout.
Alternatively right click in the empty grid area and select Status Layout.
4:1
12.0
Status Control
The Select Status Columns window will be displayed. For the example, check the columns for Design Status.
The Status Controller will display the status data columns. The rows will be populated with those objects that are or could be controlled by the selected status definitions. If more than one Status Definition has been selected, one can be selected as the Focus Status in the drop down list, and this will be used for Edit Status operations.
4:2
12.0
Status Control
The user can display other attribute columns by right clicking in one of the column titles and selecting Column Setup. The pseudo attribute expressions for the status columns already added will be shown in this window.
Note: The user can show the status of a related object in its own column. For example, if the user is managing status of schematic equipment (SCEQUI), they can show the status of a linked EQUI using an expression like STVDSC( /DesignStatus ) of Deslnk numb 1 See Pseudo Attributes for details of status pseudo attributes. The chosen column layout can be saved by right clicking in one of the column titles and selecting Save Status Layout.
4:3
12.0
Status Control
The user will be prompted to enter a name for the layout.
This name will then appear in the Status Layout dropdown list on the Status Controller. Use Save Status Layout As to save the layout with a different name. Note: The other options available on the right click menu from the column titles, including Settings and Export to Excel, which function similarly to in the Search Results.
4.2
Edit Status Operations

In the Status Controller select the rows for the objects to be controlled, right click in the selected area, and click Edit Status.
4:4
12.0
Status Control
This will display the form to edit values of the Focus Status for the selected objects. Initially the objects are Not Controlled, i.e. they have not been assigned a status value (for this status definition - they may have status values for other status definitions). Click on the drop down list and select Assign to the initial value, enter a Comment (optional), and then click on OK or Apply.
The available options for status values will then reflect the valid transitions in the status definition. For example, from Work Completed, there are two transitions.
If Promote and Demote transitions have been defined, these can be selected directly.
4:5
12.0
Status Control
This will display a variant of the Edit Status window showing appropriate options. Note: Actual values will be shown if all selected objects share the same values, otherwise they will be displayed as mixed.
The Remove Status option will delete the status data for the selected objects, so that they will no longer be controlled. The Navigate To option will be enabled for a single row selection and will set the current element.
4.3
Status History
The Status History option displays the Status History window for the selected objects which lists the status transitions along with other session history.
4:6
12.0
Status Control
The Status History also has right click options including Export to Excel.
4.4
Statistical Reports
The Statistical Report option displays the Statistical Report window which display data and charts for the Focus Status on the selected objects.
Hovering the cursor over one of the regions on the chart gives some figures for the objects it represents.
4:7
12.0
Status Control
A right click context menu is available while the cursor is over a region on the chart. The selected option is applied to the objects represented by that region.
For example, selecting List Elements displays a list of the elements for that region (you can copy and paste from this window).
4:8
12.0
Status Control
A right click menu in the background of the window offers various options, including a range of Chart Types.
For example here is a 3D cylinder bar chart.
4:9
12.0
Status Control
The Chart Legend option controls positioning of the legend, e.g. left, right, etc.
4.5
Status Controller Toolbar

The most commonly used functions are available in the Status Controller toolbar.
The icons represent Promote, Demote, Edit Status, Remove Status, Status History, Statistical Report and Save Status Layout.
4.6
Drag and Drop into Graphical View

The user can select one or more rows in the Status Controller and then drag and drop them into the 3D View to add them to the drawlist (provided they are suitable object types).
4:10
12.0
Status Control
Status Pseudo Attributes and Commands

A number of pseudo attributes are available on controlled objects to return their current status data, and a set of commands are provided to set status data. These provide an alternative to using the object methods described above.
5.1
Pseudo Attributes
The following pseudo attributes are available on any controlled object. Attribute STVPRO STVDEM STVLST STVNUM STVDSC STVCOM STVNAM STVVAL STVLNK STVASD STVTRV STVUNR STADEF STADEF STADEF STADEF STADEF STADEF Qualifier STADEF STADEF Returns STAVAL STAVAL STADEF array integer string string string STAVAL STALNK STADEF array STADEF array REF array Remark Get the promote STAVAL element for the assigned STADEF Get the demote STAVAL element for the assigned STADEF Get all assigned STADEFs Get the numerical value for the assigned STAVAL The description of assigned STAVAL The current comment from the latest status command The name of the assigned STAVAL The current STAVAL for the STADEF Ref to the STALNK element (internal) Get all eligible STADEFs, may include currently assigned Get valid transitions from current STVVAL Get a list of unresolved STAVAL references from associated STALNKs
5:1
12.0
Status Control
The following pseudo attributes are available on Status Definitions (STADEF). Attribute STVREF STVUSD Qualifier string/number Returns STAVAL REF array Remark Get the STAVAL with the given name or number (NUMVAL) All elements controlled by this STADEF
The following pseudo attributes are available on Status Values (STAVAL). Attribute STVUSD STVPRO STVDEM Qualifier Returns REF array STAVAL STAVAL Remark All elements controlled by this STADEF and with this STAVAL current Get the promote STAVAL element from this STAVAL Get the demote STAVAL element from this STAVAL
5.2
Commands
STM ASS[ign] /Definition [to SELELE] ['comment'] Assigns Status /Definition to current element or SELELE making it controlled by this status and sets the current status value to INIVAL. If a comment is given, it will be set otherwise any current comment is cleared. STM REM[ove] /Definition [from SELELE] Removes Status /Definition from current element or SELELE making it uncontrolled by this status. STM RESET /Definition [on SELELE] ['comment'] Resets current value of status /Definition on current element or SELELE to INIVAL. There does not need to be a valid transition from current value to initial value. If a comment is given, it will be set otherwise any current comment is cleared. STM DE[mote] /Definition [on SELELE] ['comment'] Sets current value of status /Definition on current element or SELELE to the value defined as demote (STVDEM). If a comment is given, it will be set otherwise any current comment is cleared STM PRO[mote] /Definition [on SELELE] ['comment'] Sets current value of status /Definition on current element or SELELE to the value defined as promote (STVPRO). If a comment is given, it will be set otherwise any current comment is cleared
5:2
12.0
Status Control
STM SET /Definition [/Value] [on SELELE] ['comment'] Sets current value of status /Definition on current element or SELELE to /Value. There need to be a valid transition from current value to /Value. If a comment is given, it will be set otherwise any current comment is cleared.
5:3
12.0
Status Control
5:4
12.0
Status Control
Using Status Control with Data Access Control

Status Control can be tightly coupled with Data Access Control to preserve data integrity. Below are some examples of what can be achieved. They have been created on the basis of Roles where the first PEROP grants all rights on all element and attribute classes, and then successive PEROPs deny some rights under specific conditions.
6.1
6.1.1
Examples
Example to Prevent Modification of an Object of a Certain Status
This is to prevent changes to an object once it has reached a level of completion. Create a PEROP that denies modify and delete operations on equipment for all attributes once the Design Status is greater than or equal to 50%. Here is the condition to use. COND ( ATTRIB STVNUM(ID /DesignStatus ) GE 50 ) A suitable error message would be: DAC: You may not modify object that has status Work Completed
6.1.2
Example to Catch when the Dictionary Database has been Deferred

This traps the situation where a user has tried to defeat the access control by deferring the dictionary database containing the status definitions. Create a PEROP that denies modify and delete operations on equipment for all attributes if the Design Status is not a valid reference. Here is the condition. COND ( BADREF ( ATTRIB STVVAL(ID /DesignStatus ) ) ) A suitable error message would be: DAC: You may not modify an object with an unresolved status
6.1.3
Example to Prevent Change of Status after a Certain Level

This is to allow a user to move an object into a For Check state but prevent them from moving it out. A more privileged user will have the task of promoting it to Checked. Create a PEROP that denies modify and delete operations on STALNK (status link) elements for attribute VALREF (status value reference) if the current value of Design Status is For Check. Here is the condition. COND ( ATTRIB OWNER OF VALREF EQ ID /DesignStatus AND ATTRIB DESC OF VALREF EQ 'For Check' ) A suitable error message would be: DAC: You may not change the Design Status of this object as it is awaiting Check
6:1
12.0
Status Control
6.1.4
Example to Prevent Removal of Status from an Object

This is to prevent a user from removing status from a controlled object. Create a PEROP that denies delete operations on STALNK (status link) elements if they are controlled by Design Status. Here is the condition. COND ( ATTRIB OWNER OF VALREF EQ ID /DesignStatus ) A suitable error message would be: DAC: You may not remove Design Status from this object.
6.1.5
Example where a User may only Amend Status

This example illustrates how to prevent a user from making any changes, other than those related directly to status assignment and transition. Create a PEROP that grants all operations to the status hierarchy. The PEROP should be applied to the following element type: STLNKW HIERARCHY This will apply the PEROP to all objects in the status hierarchy. Assign this PEROP (and only this PEROP) to the user. This is a positive DAC. It grants access rights to objects. It is therefore not possible to define a specific DAC error message which will be shown if the user tries to carry out a forbidden action (for example an attempt to create an element). A generic DAC error message will be shown in these cases
6:2
12.0
Status Control
Using Status Control with Auto Colours

Status values can be used in the Element Rules for Auto Colours.
7.1
7.1.1
Examples
Example Rule for Equipment with Design Status Pending
Rule Name: Equipment Pending Types: EQUI Rule: attrib stvnum( /DesignStatus ) eq 0
7.1.2
Example Rule for Equipment with Design Work Completed or Higher

Rule Name: Equipment Completed Types: EQUI Rule: attrib stvnum( /DesignStatus ) ge 50
7.1.3
Example Rule for Equipment with Design Status Not Controlled

Rule Name: Equipment Not Controlled Types: EQUI Rule: badref ( attrib stvval( /DesignStatus ) ) If these Element Rules are defined, then Auto Colour rules can be added, for example to show completed equipment in green, pending equipment in yellow, and uncontrolled equipment in red.
7:1
12.0
Status Control
7:2
12.0
Status Control
Customising Status Control using PML

Status Control operations can be carried out using PML. All the operations that can be carried out using the Status Controller can also be done using the appropriate objects and syntax. Specific company and project requirements can be implemented using Status Events and a framework is provided for this purpose.
8.1
Status Events in PML

Status Control provides an event mechanism that can be customised for individual company and project requirements. User methods can be added as event handlers and will be called with a single array argument. The following events are supported.
8.1.1
Status Change Events
Event BeforeStatusAssign AfterStatusAssign BeforeStatusRemove AfterStatusRemove BeforeStatusChange AfterStatusChange
Description Before a status is assigned to an object After a status is assigned to an object Before a status is removed from an object After a status is removed from an object Before a status is changed/promoted/demoted on an object After a status is changed/promoted/demoted on an object
BeforeControlledElementDelete Before a controlled object is deleted
Arg No 1 2 3
Type STRING STRING STRING
Description Reference number of controlled object Reference number of status definition Reference number of from status value (may be =0/0)
8:1
12.0
Status Control
4 5
STRING STRING
Reference number of to status value (may be =0/0) Return message aborts operation if set but only on Before operations
8.1.2
Database Change Events
Event BeforeSavework AfterSavework BeforeFlush AfterFlush
Description Before savework when there are changes to status data After savework when there are changes to status data Before flush when there are changes to status data After flush when there are changes to status data
Arg No Type 1 2 3 4 5 STRING ARRAY ARRAY ARRAY STRING
Description Reference number of status definition String reference numbers of objects that had status assigned String reference numbers of objects that had status changed String reference numbers of objects that had status removed Return message aborts operation if set but only on Before operations
8.2
Customising the StatusProjectHandler PML Object

A framework for customising events is provided in the PML object statusProjectHandler.pmlobj in the pmllib\common\objects folder. A global instance of this object is created on entry to the constructor module. It adds the event handlers and has methods for each event.
8.2.1
Debug Mode
The user can switch ON or OFF a debug mode with the following commands. !!statusProjectHandler.debugOn() !!statusProjectHandler.debugOff() In debug mode a line of text is output to the command line for each event. For example here is the output for object P1501A when promoted from Work Suspended to Work Started. statusProjectHandler.beforeStatusChange(/P1501A, /DesignStatus, /WorkSuspended, /WorkStarted) statusProjectHandler.afterStatusChange(/P1501A, /DesignStatus, /WorkStarted, /WorkStarted)
8:2
12.0
Status Control
8.2.2
Where to add Code

Each event method processes its arguments and creates some variables that may be of use to the developer. Each place where customised code can be added is delimited as follows. --========================================================== -- Start of customisation
-- End of customisation --========================================================== Important: Other parts of the statusProjectHandler PML object should not be modified. A number of examples are provided (commented out). These make use of the statusData PML object documented below.
8.2.3
Methods where you can Add Checks and Abort Changes

All of the Before methods can be used to make additional checks and can abort the operation by returning an error message, such as to prevent a status change if a particular condition is not met. A variable has been provided for this purpose, e.g. !returnMessage = |Status error: You may not delete a controlled object| By default, the only check made in the statusProjectHandler is to prevent a general user from deleting a controlled object.
8.2.4
Methods where you can make Dependent Changes

The methods AfterStatusAssign, AfterStatusRemove and AfterStatusChange can be used to make dependent changes when one of these operations is completed, e.g. to cascade a change of status on an assembly to its offspring in the assembly hierarchy.
8.2.5
Methods where you can Synchronise External Systems

The methods AfterSavework and AfterFlush can be used to synchronise data in external systems once the changes to status data have been committed in the Dabacon databases.
8.3
Using the StatusData PML Object

The PML object statusData.pmlobj is provided in the pmllib\common\objects folder to allow easy manipulation of status data from PML. It encapsulates a number of core objects that are documented below and that can be used directly if preferred. Note: The statusData object can hold status data for a single object and status definition combination, or it can hold an array of statusData objects for multiple objects and status definition combinations (see the constructor methods below).
8:3
12.0
Status Control
8.3.1
Members
Member status statusValue element definition list bulk value valname description number comment steps debug refreshMode
Type ARRAY ARRAY DBREF DBREF ARRAY BOOLEAN DBREF STRING STRING REAL STRING ARRAY BOOLEAN STRING
Description Holds a single core Status object for internal usage Holds a single core AssignedStatus object for internal usage Model object Status definition Array of statusData objects for multiple object/ definition combinations True if object holds a list of statusData objects False if object holds status information directly Status value Status value name Status value description Status value number Status comment Available transitions as strings Debug flag Refresh mode - None/Part/Full (set to None by default for best performance)
8.3.2
Constructors
Method statusData()
Description Constructor for all status definitions on CE
statusData( Constructor for single status definition on CE STRING name of status definition ) statusData( DBREF of object ) statusData( ARRAY of DBREF of objects ) statusData( DBREF of object, DBREF of status definition ) Constructor for all status definitions on a single object Constructor for all status definitions on array of objects Constructor for single object and single status definition
8:4
12.0
Status Control
statusData( Constructor for single object and single status DBREF of object, definition STRING name of status definition ) statusData( ARRAY of DBREF of objects, DBREF of status definition ) Constructor for array of objects and single status definition
statusData( Constructor for array of objects and single status ARRAY of DBREF of objects, definition STRING name of status definition )
8.3.3
Methods Intended for the User
Method output() is ARRAY of STRING outputAll() is ARRAY of STRING print() printAll() refresh() refreshModeFull() refreshModeNone() refreshModePart()
Description Return one line status summary per object (automatically does a refresh with refresh mode part) Return multi line status details per object (automatically does a refresh with refresh mode full) Print one line status summary per object Print multi line status details per object Reread status data Set refresh mode to full (slows performance) Set refresh mode to none (best performance) Set refresh mode to part
8.3.4
Methods to Assign and Remove Status
Method assign() assign ( STRING comment ) assignStatus( DBREF of status definition )
Description Assign stored status definition to object(s) Assign stored status definition to object(s) and set comment Assign status definition to object(s)
assignStatus( Assign status definition to object(s) STRING name of status definition ) assignStatus( DBREF of status definition, STRING comment ) Assign status definition to object(s) and set comment
8:5
12.0
Status Control
assignStatus( STRING name of status definition, STRING comment ) remove() removeStatus( DBREF of status definition)
Assign status definition to object(s) and set comment
Remove stored status definition from object(s) Remove status definition from object(s)
removeStatus( Remove status definition from object(s) STRING name of status definition )
8.3.5
Methods to Promote and Demote Status
Method promote() promote( STRING comment ) promoteStatus( DBREF of status definition )
Description Promote stored status for object(s) Promote stored status for object(s) and set comment Promote status for object(s)
promoteStatus( Promote status for object(s) STRING name of status definition ) promoteStatus( DBREF of status definition, STRING comment ) promoteStatus( STRING name of status definition, STRING comment ) demote() demote( STRING comment ) demoteStatus( DBREF of status definition ) Promote status for object(s) and set comment
Promote status for object(s) and set comment
Demote stored status for object(s) Demote stored status for object(s) and set comment Demote status for object(s)
demoteStatus( Demote status for object(s) STRING name of status definition ) demoteStatus( DBREF of status definition, STRING comment ) demoteStatus( STRING name of status definition, STRING comment ) Demote status for object(s) and set comment
Demote status for object(s) and set comment
8:6
12.0
Status Control
8.3.6
Methods to Set Status
Method set( STRING name of status value) set( STRING name of status value, STRING comment ) setStatus( DBREF of status definition, STRING name of status value ) setStatus( STRING name of status definition, STRING name of status value) setStatus( DBREF of status definition, STRING name of status value, STRING comment ) setStatus( STRING name of status definition, STRING name of status value, STRING comment )
Description Set stored status for object(s) Set stored status for object(s) and set comment
Set status for object(s)
Set status for object(s)
Set status for object(s) and set comment
Set status for object(s) and set comment
8.3.7
Internal Methods not Intended to be Called by User
Method init() clear() debugOff() debugOn() getStatus() queryStatus() refreshMode( STRING ) sortSteps()
Description Internal method to initialise member data Internal method to clear member data Internal method to clear debug flag Internal method to set debug flag Internal method to get status data using core object Internal method to get status data using queries Internal method to set refreshMode Internal method to return available transitions
8.3.8
Example to Set and Get Status Data

The example is for the case where there is one available status definition for the current element. The set of commands assigns that status to the current element, promotes it, prints out the data, and gets the current status value description into a string variable.
8:7
12.0
Status Control
!myStatus = object statusData() !myStatus.assign() !myStatus.promote() !myStatus.print() !currentStatus = !myStatus.description
8.4
Using the Core Status Objects from PML

Access to status data is provided via a set of core objects as described below. These require the appropriate import and using namespace commands: import 'Aveva.Pdms.DataManagement.PML' handle any -- ignore if already loaded endhandle using namespace 'Aveva.Pdms.DataManagement.PML'
8.4.1
Object STATUSMANAGEMENT
Holds systems information relating to Status Control. Methods include: Method statuses() Description Returns the available statuses as an array of STATUS
8.4.2
Object STATUSEVENTS
Holds information relating to status events. Methods include: Method statusEvents( STRING name of status definition ) Initialise( STRING name of status definition ) addEventHandler( STRING event name, ANY object name, STRING method name) Description Constructor that initialises for the status definition Initialises for the status definition Adds an event for the stored status definition that will call the method on the object
8.4.3
Example to Add an Event Handler

The example gets the available status definitions and sets an event handler for the first definition. !statusManagement = object statusManagement() !statusDefinitions = !statusManagement.statuses() !statusEvents = object statusEvents()
8:8
12.0
Status Control
!statusEvents.initialise(!statusDefinitions[1]) !statusEvents.addEventHandler('BeforeStatusChange', !!handlerObject, 'beforeStatusChange')
8.4.4
Object STATUS
Represents a status definition. Methods include: Method status( STRING name of status definition ) assign( STRING name of object ) assign ( ARRAY of names of objects ) assign ( STRING name of object, STRING comment ) assign ( ARRAY of names of objects, STRING comment ) controlledElements() demote( STRING name of object ) demote ( ARRAY of names of objects ) demote ( STRING name of object, STRING comment ) demote ( ARRAY of names of objects, STRING comment ) description() initialValue() name() promote( STRING name of object ) promote ( ARRAY of names of objects ) Description Constructor Assign status to object Assign status to objects Assign status to object and set comment
Assign status to objects and set comment
Returns an array of names of objects controlled by this status Demote status on object Demote status on objects Demote status on object and set comment
Demote status on objects and set comment
Returns description of status definition Returns STATUSVALUE initial value of status definition Returns name of status definition Promote status on object Promote status on objects
8:9
12.0
Status Control
promote ( STRING name of object, STRING comment ) promote ( ARRAY of names of objects, STRING comment ) remove( STRING name of object ) remove ( ARRAY of names of objects ) set ( STRING name of object, STRING name of status value) set ( STRING name of object, STATUSVALUE status value) set ( ARRAY of names of objects, STRING name of status value ) set ( ARRAY of names of objects, STATUSVALUE status value) set ( STRING name of object, STRING name of status value, STRING comment ) set ( STRING name of object, STATUSVALUE status value, STRING, comment ) set ( ARRAY of names of objects, STRING name of status value, STRING comment ) set ( ARRAY of names of objects, STATUSVALUE status value, STRING comment ) values()
Promote status on object and set comment
Promote status on objects and set comment
Remove status from object Remove status from objects Set status on object
Set status on object
Set status on objects
Set status on objects
Set status on object and set comment
Set status on object and set comment
Set status on objects and set comment
Set status on objects and set comment
Returns array of STATUSVALUE for this status definition
8:10
12.0
Status Control
8.4.5
Object STATUSVALUE
Represents a status value. Methods include: Method statusValue( STRING name of status definition, STRING valname of status value ) statusValue ( STATUS status definition, STRING valname of status value ) description() name() number() validTransitions() Description Constructor
Constructor
Returns description of status value Returns valname of status value Returns number of status value Returns array of STATUSVALUE that are valid transitions
8.4.6
Object ASSIGNEDSTATUS
Represents the status link data for an object. Methods include: Method assignedStatus( STRING name of status definition, STRING name of model object ) comment() currentValue() definition() thisElement() Description Constructor
Returns comment from status link Returns STATUSVALUE status value that status link refers to Returns STATUS status definition that status value is owned by Returns STRING reference number of model object that status link refers to
8.4.7
Example to Set and Get Status Data

The example assigns Design Status to an equipment item then promotes it with a comment. Then it gets the status data and returns the status value, description, number and comment. The comment comes direct from the assigned status object, but the other values are via the reference to the status value object. !status = object status('/DesignStatus') !status.assign('/E1301') !status.promote('/E1301', 'Ready for checking') !currentStatus = object assignedStatus('/DesignStatus', '/E1301')
8:11
12.0
Status Control
!valueName = !currentStatus.currentValue().name() !description = !currentStatus.currentValue().description() !number = !currentStatus.currentValue().number() !comment = !currentStatus.comment()
8:12
12.0
Status Control
Customising Status Control using C# (.NET)

As an alternative to (or in combination with) PML customisation, customisation can also be undertaken in .NET applications. Examples below are given in the C# language.
9.1
Namespaces and Assemblies

The .NET status objects described below are defined in the Aveva.Pdms.DataManagement.dll assembly, which will be found in the standard PDMS install directory (PDMSEXE). To use these status objects, programmers will need reference to the Aveva.Pdms.Database.dll assembly also found in PDMSEXE. (You may wish to reference other PDMS .NET assemblies - please refer to PDMS.NET documentation for further details.) To access this software from Visual Studio, add the assemblies to the project references and declare interest in the namespaces at the top of the client C# files: using Aveva.Pdms.DataManagement; using Aveva.Pdms.Database;
9.2
Classes in .NET
The following classes are available in C#. These correspond to and have similar functionality to the PML objects described above.
9.2.1
Class StatusManagement
This static class gives access to all the status definition elements in the current MDB. As a static class no instances of the class are created. The class has a single property, Statuses, which returns an array of Status objects (described below), used as follows: Status[] statuses = StatusManagement.Statuses;
9.2.2
Class Status
This class gives access to a named status definition determined in the constructor either by name or as a DbElement: Status status = Status("/DesignStatus"); DbElement statusDefinitionElement; // ... Status status = Status(statusDefinitionElement);
9:1
12.0
Status Control
The screenshot below of the Visual Studio Object Browser details the public interface of the Status class:
9.2.3
Class StatusValue
This class gives access to the data relating to a Status Value (STAVAL element). This represents one of the legal states that an element controlled for a given status definition may have. The status definition and value can be determined via the class constructors: Status status = Status("/DesignStatus"); StatusValue statusValue = StatusValue(status, "/Approved"); Or: DbElement statusValueElement; // ... StatusValue statusValue = StatusValue(statusValueElement);
9:2
12.0
Status Control
Alternatively, the array of all StatusValues for a given status definition can be obtained directly from a Status object: Status status = Status("/DesignStatus"); StatusValue[] statusValues = status.Values; The remaining functions of the StatusValue class are displayed in the Visual Studio Object Browser below:
9.2.4
Class StatusCommand
This static class gives access to all the status functionality. As a static class no instances of the class are created. This class effectively duplicates the functionality otherwise available through instances of the Status class. The Visual Studio Object Browser display is as follows:
9.2.5
Class StatusEvents
This class gives access to all the status change events. An instance of the class cannot be instantiated directly by constructor. Instead an instance can be created from the
9:3
12.0
Status Control
Status.Events property, or from the static functions StatusEvent.GetStatusEventObject(Status s) or StatusEvent.GetStatusEventObject(). The following example shows the registration of an event handler for the BeforeStatusChange event together with a sample implementation of the registered event handler: Status status = Status("/DesignStatus"); StatusEvent statusEvent = status.Event; statusEvent.BeforeStatusChange += new StatusEvent.BeforeStatusChangeEventHandler(My_BeforeStatusChange ); // ... // Event handler private void My_BeforeStatusChange (object sender, CancelStatusEventArgs e) { // Do any extra actions and check status change is allowed if ( /* abort status change required */ ) { e.Cancel = true; e.Message = "reason not to proceed"; } }
The list of available status events is displayed in the Visual Studio Object Browser display as follows:
9:4
12.0
Status Control
9.2.6
Status Change Events

The Before event methods can cancel the operation. Event BeforeStatusAssign AfterStatusAssign BeforeStatusRemove AfterStatusRemove BeforeStatusChange AfterStatusChange BeforeControlledElementDelete StatusEventArgs Name Model Status From To Type DbElement Status StatusValue StatusValue Description The element to be controlled The Status object The from StatusValue object The to StatusValue object Arguments object sender, CancelStatusEventArgs e object sender, StatusEventArgs e object sender, CancelStatusEventArgs e object sender, StatusEventArgs e object sender, CancelStatusEventArgs e object sender, StatusEventArgs e object sender, CancelStatusEventArgs e
CancelStatusEventArgs Name Model Status From To Cancel Message Type DbElement Status StatusValue StatusValue Bool String Description The element to be controlled The Status object The from StatusValue object The to StatusValue object Cancel the ongoing operation With this as the message
9.2.7
Database Change Events

The Before event methods can cancel the operation. Event BeforeSavework AfterSavework Arguments object sender, CancelDBChangeEventArgs e object sender, DBChangeEventArgs e
9:5
12.0
Status Control
BeforeFlush AfterFlush DBChangeEventArgs Name Status Assigned Changed Removed Type Status DbElement[] DbElement[] DbElement[]
object sender, CancelDBChangeEventArgs e object sender, DBChangeEventArgs e
Description The Status object Array of DbElements that had Status assigned Array of DbElements that had Status changed Array of DbElements that had Status removed
CancelDBChangeEventArgs Name Status Assigned Changed Removed Cancel Message Type Status DbElement[] DbElement[] DbElement[] Bool String Description The Status object Array of DbElements that had Status assigned Array of DbElements that had Status changed Array of DbElements that had Status removed Cancel the ongoing operation With this as the message
9:6
12.0
Status Control
Distributing Customised Status Layouts
10

Individual users can customise and save their own status layouts. This process is described in Status Layout in Status Controller in Design and other Constructor Modules. As an administrator you may decide to create a set of project standard status layouts for all users on the project. Status layouts are stored in files in the users Local Settings Application Data folder, for example, for the project BAS the folder will be: C:\Documents and Settings\john.smith\Local Settings\Application Data\Aveva\PDMS\BASStatusGridProfiles An administrator who has created a set of status layouts in their own folder can copy these files and distribute them to other users to include in their own equivalent folders. There is no need to copy the LastSelectedStatusGridProfile or WindowsLayout files in this folder as these will be created automatically.
10:1
12.0
Status Control
10:2
12.0
Status Control
11

This section suggests an approach to upgrading status data created by AVEVA Model Manager. For Model Manager, the equivalent to a Status Definition is a list of values for a particular controlled object type and is defined in VPE. Individual controlled objects then hold one of these values in a specified attribute, e.g. :mmstatus. A Status Definition could be created for each list of values, applied to the particular controlled object type. Where the controlled object type is qualified by a filter, e.g. PIPE with PURP 'Civils', this could be implemented as a UDET, e.g. :CivilsPipe. An allowable transition should be set from the initial value to each other value in the definition, to support the next stage (some of these transitions could be removed later). A macro would then be written, to loop through each controlled object, assign its appropriate status definition then set it to the equivalent status value for its Model Manager status data.
11:1
12.0
Status Control
11:2
12.0
Status Control
Index
C
Change Events Database . . . . . . . . . . . . . . . . . 8:2, 9:5 Status . . . . . . . . . . . . . . . . . . . . . . . . 9:5 Class Status . . . . . . . . . . . . . . . . . . . . . . . . 9:1 StatusCommand . . . . . . . . . . . . . . . . 9:3 StatusEvents . . . . . . . . . . . . . . . . . . 9:3 StatusManagement . . . . . . . . . . . . . 9:1 StatusValue . . . . . . . . . . . . . . . . . . . 9:2 Classes .NET . . . . . . . . . . . . . . . . . . . . . . . . . 9:1 Commands . . . . . . . . . . . . . . . . . . . . . . . 5:2 Customising StatusProject Handler PML Object . . 8:2
L
Lexicon Configuring Status Definitions . . . . . 3:1
M
Methods Abort Changes . . . . . . . . . . . . . . . . . Add Checks . . . . . . . . . . . . . . . . . . . Assign and Remove . . . . . . . . . . . . . Dependent Changes . . . . . . . . . . . . Intended for User . . . . . . . . . . . . . . . Internal . . . . . . . . . . . . . . . . . . . . . . . Promote and Demote . . . . . . . . . . . . Set Status . . . . . . . . . . . . . . . . . . . . Synchronise External Systems . . . . 8:3 8:3 8:5 8:3 8:5 8:7 8:6 8:7 8:3
D
Data Model Status Control . . . . . . . . . . . . . . . . . . 2:2
N
Namespaces and Assemblies . . . . . . . . 9:1
E
Example Add Event Handler . . . . . . . . . . . . . . 8:8 Set and Get Status Data . . . . 8:7, 8:11
O
Object Assignedstatus . . . . . . . . . . . . . . . 8:11 Status . . . . . . . . . . . . . . . . . . . . . . . . 8:9 Statusevents . . . . . . . . . . . . . . . . . . 8:8 Statusmanagement . . . . . . . . . . . . . 8:8 Statusvalue . . . . . . . . . . . . . . . . . . 8:11
G
Graphical View Drag and Drop . . . . . . . . . . . . . . . . 4:10
P
PML Core Status Objects . . . . . . . . . . . . . 8:8
Index page 1
12.0
Status Control
PML Object StatusData . . . . . . . . . . . . . . . . . . . . 8:3 Pseudo Attributes . . . . . . . . . . . . . . . . . . 5:1
R
Reports Statistical . . . . . . . . . . . . . . . . . . . . . 4:7
S
Status Controller Toolbar . . . . . . . . . . . . . . 4:10 Distributing Customised Layouts . . 10:1 Edit Operations . . . . . . . . . . . . . . . . . 4:4 History . . . . . . . . . . . . . . . . . . . . . . . 4:6 Layout . . . . . . . . . . . . . . . . . . . . . . . . 4:1 Status Change Events . . . . . . . . . . . . . . . . . . . . . . . 8:1 Status Control Auto Colours . . . . . . . . . . . . . . . . . . . 7:1 C# . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1 Data Access Control . . . . . . . . . . . . . 6:1 Examples . . . . . . . . . . . . . . . . . 6:1, 7:1 using PML . . . . . . . . . . . . . . . . . . . . 8:1 Status Controller Constructor Modules . . . . . . . . . . . . 4:1 Design . . . . . . . . . . . . . . . . . . . . . . . 4:1 Status Events PML . . . . . . . . . . . . . . . . . . . . . . . . . 8:1
W
Workflow Example . . . . . . . . . . . . . . . . . . . . . . 2:1
Index page 2
12.0

Status Control

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Status Control

Загружено:

Авторское право:

Доступные форматы

Status Control

AVEVA Solutions Ltd

Example Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1

Status Pseudo Attributes and Commands . . . . . . . . . . . . . . . . . . . . 5:1

Using Status Control with Data Access Control . . . . . . . . . . . . . . . 6:1

2009 AVEVA Solutions Ltd

6:1 6:1 6:1 6:2 6:2

Using Status Control with Auto Colours. . . . . . . . . . . . . . . . . . . . . . 7:1

Customising Status Control using PML . . . . . . . . . . . . . . . . . . . . . . 8:1

Customising the StatusProjectHandler PML Object. . . . . . . . . . . . . . . . . . . . . . 8:2

Using the StatusData PML Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:3

Using the Core Status Objects from PML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:8

2009 AVEVA Solutions Ltd

Customising Status Control using C# (.NET) . . . . . . . . . . . . . . . . . . 9:1

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

Status Pseudo Commands

Upgrading Model Manager Status Data

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

Status Control Data Model

2009 AVEVA Solutions Ltd

Configuring Status Definitions in Lexicon

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

Status Controller in Design and other Constructor Modules

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

The user will be prompted to enter a name for the layout.

Edit Status Operations

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

For example here is a 3D cylinder bar chart.

2009 AVEVA Solutions Ltd

Status Controller Toolbar

Drag and Drop into Graphical View

2009 AVEVA Solutions Ltd

Status Pseudo Attributes and Commands

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

Using Status Control with Data Access Control

Example to Catch when the Dictionary Database has been Deferred

Example to Prevent Change of Status after a Certain Level

2009 AVEVA Solutions Ltd

Example to Prevent Removal of Status from an Object

Example where a User may only Amend Status

2009 AVEVA Solutions Ltd

Using Status Control with Auto Colours

Example Rule for Equipment with Design Work Completed or Higher

Example Rule for Equipment with Design Status Not Controlled

2009 AVEVA Solutions Ltd

2009 AVEVA Solutions Ltd

Customising Status Control using PML