GALIOM Version 2.0 - User Manual
GALIOM Version 2.0 - User Manual
Germanischer Lloyds
GALIOM Version 2.0
GALIOM USER MANUAL
ASSET
INTEGRITY
MANAGEMENT
SYSTEM
(AIM)
INDEX OF CONTENT
1
2
3
4
INTRODUCTION .................................................................................................................... 8
HOW TO INSTALL GALIOM FROM FRONT END..................................................... 8
FAMILIARISATION OF GALIOM ENVIRONMENT .................................................. 9
GALIOM APPLICATION SECURITY.............................................................................. 14
4.1
HOW TOLOGON INTO GALIOM APPLICATION .......................................... 14
4.2
HOW TO REGISTER NEW USER........................................................................... 15
4.3
HOW TO CREATE RESPONSIBILITIES .............................................................. 18
4.4
HOW TO CREATE RESPONSIBLE GROUPS ..................................................... 19
4.5
HOW TO ASSIGN RESPONSIBILITIES TO USER ............................................ 21
4.6
HOW TO ASSIGN GROUP TO USER.................................................................... 23
4.7
HOW TO ASSIGN PROGRAM TO USER ............................................................. 25
5
ADMINSTRATION MODULE........................................................................................... 26
5.1
HOW TO REGISTER NEW MENU......................................................................... 26
5.2
HOW TO REGISTER NEW REPORT..................................................................... 28
5.3
HOW TO REGISTER NEW REFERENCE............................................................ 30
5.4
HOW TO CREATE A NEW USER REFERENCE VALUES............................. 31
5.5
HOW TO CREATE A NEW SYSTEM REFERENCE VALUES ....................... 33
5.6
HOW TO SETUP CLASS LEVEL SETUP............................................................... 34
5.7
HOW TO SETUP ASSET LEVEL SETUP .............................................................. 36
5.8
HOW TO DEFINE FEATURE FOR EQUIPMENT............................................ 38
5.8.1 INSERT FEATURE DIALOG BOX......................................................................... 39
5.8.2 INSERT MONITORING TESTPOINTS DIALOG BOX................................... 41
5.9
HOW TO DEFINE THE FEATURE TYPE PREFIX .......................................... 43
5.10 HOW TO DEFINE MONITORING TYPE PREFIX........................................... 45
5.11 HOW TO DEFINE CLASS VALUES ....................................................................... 47
5.12 HOW TO DEFINE ATTRIBUTE LIST ................................................................... 50
5.13 HOW TO DEFINE DATA FORM LIST.................................................................. 53
5.14 HOW TO DEFINE DATA FORM LOOKUP ENTRY........................................ 56
5.15 HOW TO DEFINE SPANISH LABEL..................................................................... 57
6
ASSET MANAGEMENT MODULE ................................................................................. 58
6.1
ASSET MANAGEMENT SCREEN .......................................................................... 58
6.2
ASSET HIERARCHY.................................................................................................... 61
6.3
HOW TO REGISTER THE TAG AND GEOGRAPHICAL LOCATIONS ... 62
6.4
HOW TO UPDATE MECHANICAL DESIGN DATA ....................................... 63
6.5
ASSIGN FAILURE MECHANISM TO TAG.......................................................... 64
6.6
LINKING DOCUMENTS TO TAG AND FACILITIES..................................... 66
6.7
HOW TO PROCESS DATE FOR A TAG ............................................................... 69
6.8
HOW TO CALICULATE THEORITICAL CORROSION RATES................... 70
6.9
RISK BASE INSPECTION.......................................................................................... 72
6.10 RBI BASIC ASSESSMENT TYPE.............................................................................. 72
6.10.1 CONSEQUENCE OF FAILURE RANKING...................................................... 72
6.10.2 PROBABILITY OF FAILURE RANKING........................................................... 74
6.10.3 RISK RANKING MATRIX....................................................................................... 75
6.11 API 581 SEMI - QUANTITATIVE ASSESSMENT TYPE. .............................. 77
6.11.1 COF RBI SQ ASSESSMENT BY HOLE SIZE.................................................. 77
6.11.2 COF RBI SEMI QUANTITATIVE ASSESSMENT FORM ........................... 78
6.11.3 SQ- THINNING MODEL ........................................................................................ 79
6.11.4 SQ- SCC MODEL........................................................................................................ 80
6.11.5 SQ- FATIGUE MODEL ............................................................................................ 82
Page 2 of 395
Page 7 of 395
INTRODUCTION
This explanation covers the entire steps to install the Galiom Application from the front end.
Pre-requisites
1. The Galiom application is fully build and the application exe should be present.
Page 8 of 395
Select GALIOM.mdb
When you double click the shortcut for GALIOM in desktop, a ticket number would be
generated. And program would expect an activation code for it. Select and highlight the
ticket number field and right click to copy the ticket number. Send it via email to the
following support persons in KL.
1)
2)
3)
4)
galiom.support@gl-group.com
Gareth.Thomas@gl-group.com
Mathews.Varkey@gl-group.com
tong-chang.Lim@gl-group.com
You will receive an activation code for the sent ticket number to activate the program.
Page 9 of 395
Pre-requisites
1. The user is active user of the GALIOM Application.
2. The user should have valid user id and password to login into GALIOM
Application.
Page 10 of 395
Page 11 of 395
Responsibilities
1. Any active GALIOM Application user.
Navigation
Login into GALIOM application - > Login user screen.
Tool Buttons
Modules
Page 12 of 395
Page 13 of 395
INTRODUCTION
GALIOM starts with user authentication. Every user of GALIOM would be assigned with a
user id and password. The user ids are assigned with group code and responsibilities. Based
on the responsibilities, the users could only edit, modify, create and delete the assets in the
GALIOM application. Similar based on the user responsibilities the users can edit, modify,
create and delete the document in the GALIOM application. The user with Administrator
right can edit, create, modify and delete the assets and documents in the GALIOM
application.
4.1
When the GALIOM Application icon, or the application is invoked. The system display the
GALIOM Login screen with User Id, Password, Language columns and also with a window
to select the database.
Pre-requisites
1. The user should be active GALIOM Application user
2. The user should have valid user id and password.
Responsibilities
1. Any Active GALIOM Application user.
Navigation
Click on GALIOM Application icon - > Login user screen
Page 14 of 395
Column Description
1. User Id (M)
a. The user enter user id.
2. Password (M)
a. The user enters the password.
i. The system displays the special characters.
3. Language (M)
a. By default the system selects the English.
b. Based on the language selected, the system displays the menu and column labels
in the selected language.
c. Most of the time the default language is set during the installation time. Once it is
locked during implementation by the implementer, the language dropdown box
will be in disable mode.
4. Logon button (M)
a. Once the user enter the user id and password and clicked ok button, the system
allow the user to enter into GALIOM application
i. The system validate the user id and Password, if they are active and valid
the system permit the user to enter into the GALIOM Application
ii. If the user enters wrong user id or password, the system displays the
following message User id or password is incorrect with ok button.
5. Close button (M)
a. If the user does not want to enter into the GALIOM Application, the press close
button.
1. The system closes the GALIOM Login screen..
Report
None.
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADIMN group user should have Access to invoke this window.
Page 15 of 395
3.
4.
5.
6.
a. When user try to delete the sleeted record, the system displays the following
message You are about to delete the selected record, Do you wish to
continuewith Yes and No buttons.
i. If user selects the Yes button, the system deletes the selected record. If
the user selects the No button, the system will not delete the selected
record.
Save button:- The system save the record.
Refresh button:- The system refresh the current display window.
Exit button:- The system Exit from the GALIOM Application.
RESET PASSWORD button:- The system set user id as password to the selected
user
Responsibilities
1. The user should have ADMIN responsibilities.
Navigation
Click Main menu
Click on Administration
Column Description
1.
User ID (M)
a. Enter the new user GALIOM user id.
i. If the user try to save the record, without entering any value in this
column, the system display the following message User Id is must.
2.
3.
Description (O)
Page 16 of 395
5.
6.
7.
Indicator
a. Enter the department name, to which the user is assigned
8.
9.
Email (O)
a. Enter the email id of the new GALIOM user.
i. Enter the valid email user id.
Report
None.
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Responsibilities
1.
Navigation
Main Menu
Administration
Page 18 of 395
Column Description
1.
2.
3.
Description (O)
a. Enter the description for the responsibilities name.
4.
Active (M)
a. This is one of the columns used as a security option in the GALIOM
application. As long the active check box is selected against the selected
responsibilities, the responsibilities is active and all the users who are assign
with these responsibilities can perform the respective task defines in the
responsibilities. By default the check box is checked (i.e., Active).
i. If the ADMIN uncheck this option against the selected
responsibilities, then that responsibility is no more active group in the
GALIOM application.
5.
6.
Report
None
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Page 19 of 395
Responsibilities
Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Administration
Column Description
1. Group Code (M)
a. Enter the New responsible group code.
i. Once the responsible group code is saved, the value in this column is
not editable. It will be in display mode only.
2. Group Name (O)
a. Enter the responsible group name.
3. Description (O)
a. Enter the description for the responsible group.
4. Head Name (O)
a. Enter the respective head name (user name) against selected responsible
group.
5. Office Phone (O)
a. Enter the Office phone number.
Page 20 of 395
Report
None.
Responsibility
Code
1 ADMIN
Responsibility Name
Administrator
2 ASTEDT
Asset Editor
3 ASTVEW
Asset View
4 CORENG
Corrosion Engineer
5 DOCEDT
Document Editor
Responsibility Description
One who edit the whole Galiom
System
One who edits the Asset Register
Data.
One who wish to view the asset
Register but will not have any
access to add, delete or modify
data.
Corrosion Engineer For RBI
Analysis.
One who does editing of
Page 21 of 395
Responsibility
Code
6 ENGDEL
7 ENGEDT
8 MAINTC
9 MEMOEDT
10 MOCDEL
11 MOCEDIT
12 MONDEL
13 MONEDT
14
15
16
17
PLANDEL
PLANEDIT
REFEDT
RELENG
18 USRMGT
Responsibility Name
Responsibility Description
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Page 22 of 395
Responsibilities
1.
Navigation
Main Menu
Administration
Column Description
1.
2.
Active (M)
a. The system by default assigns the selected responsibility to select user.
i. The ADMIN will uncheck, if any responsibility access is removed to
the selected user.
3.
4.
Report
None.
Pre-requisites
Page 23 of 395
Responsibilities
1.
Navigation
Main Menu
Administration
Column Description
1. Group Code (M)
a. Select the respective responsible group from the drop down, which is going
to assign to the selected user.
2. Update date (D)
a. The system display the updated date, when ever user modifies the data.
3. Updated user (D)
a. The system displays the updated user who ever modifies the data in this
window.
Report
None.
Page 24 of 395
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Responsibilities
1.
Navigation
Main Menu
Administration
Column Description
1.
Active (M)
a. By default, all the modules and menu Items are accessible to the user. If the
ADMIN uncheck the active button against any module/menu item for the
selected user. The system will not display the respective menu item to the
user, when the user login into the GALIOM system.
Page 25 of 395
4.
Report
None
ADMINSTRATION MODULE
INTRODUCTION
This module mainly deals with the configuration setups by the Admistrator in the
GALIOM Application. Most of the configuration setups will be done during the
implimentation stage. All the configuration setup window can only accessed by the
ADMIN resposibility user.
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Page 26 of 395
Exit button:- The system will Exit from the GALIOM application.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
MainMenu
Administration
Column Description
1. Module Name (M)
a. The user is to select the respective module name from the drop down, under
which the new menu should appear.
2. SEQ(O)
a. The seq number defines the position of the menu item in that particular
module.
3. Program code (M)
a. The user should specify the name of design element (i.e., PB window name).
4. Program name (M)
a. The name of the menu item should appear to the GALIOM users.
5. Parameter (O)
a. The parameter column is a provision to ADMIN, to configure a pre defined
value in the menu item based on the client requirements.
6. Active (M)
Page 27 of 395
Report
None
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Responsibilities
Any user having ADMIN Responsibility can edit this window.
Navigation
MainMenu
Administration
Page 28 of 395
Column Description
1. Module Name (M)
a. The user is to select the respective module name from the drop down, under
which the new report should appear.
2. SEQ (O)
a. The seq number defines the position of the report item in that particular
module.
3. Report code (M)
a. The user should specify the name of design element (i.e., PB window name).
4.
Report
None.
Page 29 of 395
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Administration
Page 30 of 395
Column Description
1. Seq (D)
a. The system automatically displays the seq number.
i. The system increment the seq number automatically
2. Reference Type (M)
a. Enter the new reference type
3. Description (O)
a. Enter the description of the reference type.
4. Ref. Group (O)
a. Select the reference group from the drop down.
5. Updated date (D)
a. The system should display the updated date, when ever user (i.e., ADMIN)
modifies the data.
6. Updated User (D)
a. The system should display the updated user, with the Admin user id, when
ever user modifies the data in this window.
Report
None.
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Responsibilities
Page 31 of 395
Navigation
Main Menu
Administration
Column Description
1. Seq (D)
a. Automatically the system displays the seq number.
2. Code (M)
a. Enter the code for the reference.
3. Reference Name (O)
a. Enter the reference name
4. Description (O)
a. Enter the description
5. Active (M)
a. If the check box is checked, the reference value is active. If the check box is
not checked, the reference value is not active.
i. By default the system check the check box.
6. Updated date (D)
a. The system should display the updated date, when ever user (i.e., ADMIN)
modifies the data.
7. Updated User (D)
a. The system should display the updated user, with the Admin user id, when
ever user modifies the data in this window.
Report
None
Page 32 of 395
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Administration
Column Description
1. Seq (D)
a. Automatically the system displays the seq number
Page 33 of 395
Report
None
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Page 34 of 395
Navigation
Main Menu
Administration
Column Description
1. Level (M)
a. Enter the class level name.
2. Description (O)
a. Enter the description for the class
3. Level Group(D)
a. The system set the Level group as CLASSHIER.
i. The column is not editable.
4. Relationship (M)
a. Select the relationship for the class.
5. COF Required (O)
a. Check the check box, if the COF required for the class
6. Approval Required (O)
a. Check the check box, if the Approval required for the class
7. Updated date (D)
a. The system should display the updated date, when ever user (i.e., ADMIN)
modifies the data.
8. Updated User (D)
a. The system should display the updated user, with the Admin user id, when
ever user modifies the data in this window.
9. Created Date (D)
a. The system should display the created date, when ever user (i.e., ADMIN)
setup a class level setup.
10. Create User (D)
a. The system should display the created user, with the Admin user id, when
ever user setup a class level setup.
Page 35 of 395
Report
None
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Administration
Column Description
Page 36 of 395
1. Level (M)
a. Enter the level name to be called or shown in the Asset hierarchal tree
2. Description (O)
a. Enter the description for the level
3. Level Group(M)
a. Select the value from the drop down, whether the level is MAINHER or
SUBHIER
4. Relationship (M)
a. Select the relationship from the drop down based on the Level scope. That is
whether this level is relation ship is one to many/one to one/Many to
many/Many to one
5. COF Required (O)
a. Check the check box, if the level required Consequence of failure.
6. Approval Required (O)
a. Check the check box, if the level required the Approval.
7. Installed (O)
a. Check the check box, if the level is installed or not.
8. Failure Mech.Required (O)
a. Check the check box, if the level required the Failure Mechanism.
9. Document Required (O)
a. Check the check box, if the level required the docuemtns.
10. Updated date (D)
a. The system should display the updated date, when ever user (i.e., ADMIN)
modifies the data
11. Updated User (D)
a. The system should display the updated user, with the Admin user id, when
ever user modifies the data in this window.
12. Created Date (D)
a. The system should display the created date, when ever user (i.e., ADMIN)
setup a asset level setup.
13. Create User (D)
a. The system should display the created user, with the Admin user id, when
ever user setup a asset level setup.
14. Class level (M)
a. Select the class level from the drop down for the selected level
15. Mandatory (M)
a. Check the check box, if the class type is mandatory
Page 37 of 395
Report
None.
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADIMN group user should have Access to invoke this window.
Responsibilities
1. The user should have ADMIN responsibilities.
Navigation
Click Main menu
menu item.
Click on Administration
Page 38 of 395
Column Description
1.
Equipment Type ( M)
a. Select the Equipment from the drop down. System will display all the
active equipments present in the GALIOM application.
2.
Seq No(D)
a. The system automatically display the seq number for each feature defined
to that equipment.
i. The system automatically increment the seq number.
3.
4.
5.
6.
Report
None
5.8.1 INSERT FEATURE DIALOG BOX
The dialog box is the popup window that appears to the user when he wants to insert
Features for the TAG. The Fig 8 below depicts how and where the Option is available to the
user. When the user is at the Tag level in the Asset tree and then the user right clicks the
drop down of the option will be available and the INSERT FEATURE option will help the
user to open the dialog box. On Applying (the option available in the dialog box) will insert
the Feature into the asset tree.
Pre-requisites
1. The user should be GALIOM Application user and should login into GALIOM
application..
2. User should have the ASTEDT or the Asset edit rights to proceed with insertion of
new features into the system.
Page 39 of 395
Responsibilities
1. The user must have ASTEDT Responsibility rights.
Navigation
Asset Hierarchy Tree Tag level Assets Right Click
When user selects Feature the following window will be displayed by the system.
Column Description
1. Seq no (D)
a. Sequence number for the number of feature attached to the TAG
2. Feature type (M)
a. Column classifying the feature type as defined in the Class Values for the
Class FEATYP
3. Feature Name (O)
Page 40 of 395
Report
None.
5.8.2 INSERT MONITORING TESTPOINTS DIALOG BOX
This dialog box is for the user to insert new test points into the system. Based on the
Monitoring type the Prefix appears automatically if it is defined in the window for Define
Prefix for Monitoring types. The other columns in the window help in naming the test
point. Thereby the window appears only at the feature level and not at any other level.
Pre-requisites
1. The user should be GALIOM Application user and should login into GALIOM
application..
2. User should have the ASTEDT or the Asset edit rights to proceed with insertion of
new features into the system.
Responsibilities
1. The user must have ASTEDT Responsibility rights.
Navigation
Asset Hierarchy Tree Feature level Assets Right Click
Page 41 of 395
When user selects Insert Test point, the following window will be displayed by the
system.
Column Description
1. Monitoring Type (M)
a. Drop down for selecting the type of Monitoring testpoint under
consideration and that need to be added under the Feature in the Asset
Hierarchy.
2. Prefix (O)
a. In the prefix that either appears automatically if it is already defined in the
window Define Prefix for the Monitoring type or is editable for the user to
enter or can be left blank such that the Insert from , to sequence no will be
taken into consideration while forming the test point Name.
b. Validation check on the column Please select a Monitoring type appears if
the users presses the apply button without selecting a monitoring type. Since
the Test points created will have a certain class based on the Monitoring type
selected, this column cannot be left blank.
3. Insert From (M)
a. Is the numeric value that holds the test point start number for the test points
under the feature The arrow keys here can be used to increment/decrement
the number by 1.
Page 42 of 395
4. Insert To (M)
a. Is the numeric value that holds the test point to number for the test points
under the feature. The arrow keys here can be used to increment/decrement
the number by 1.
b. Validation check on the column if tried to proceed without having proper
data in the column, the system gives the message Insert to cant be blank.
c. Validation check on the column Insert to cant be less than Insert from ie
The value of insert to column is less than that in the Insert from. This goes
against the system logic and thereby the message. Accordingly the test points
will get created from the sequence no of insert from value to the insert to
value.
5. Apply button:- Once clicked will finally add the Testpoints under the Asset or the
Feature. The popup window will close automatically once it has done with the Adding
of the Testpoints to the Feature. The same will get reflected in the Asset tree
instantaneously.
6. Close button:- . This button is an option available to the user to close the popup
window without doing anything. Short cut is Alt c.
Report
None
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADIMN group user should have Access to invoke this window.
Responsibilities
1. The user should have ADMIN responsibilities.
Navigation
Page 43 of 395
Click on Administration
Column Description
1.
Class (D)
a. The system display all the class values defined in the define class window
under the FEATYP level.
i. The system automatically display all the class values, it will not allow
the user to edit this column.
2.
Description (D)
a. The system display all the description data defined in the define class
window under the FEATYP level.
i. The system automatically display all the description data, it will not
allow the user to edit this column.
3.
Prefix (O)
a. Enter the prefix name.
i. The system will use this prefix name, when user inserts a feature in
the Asset Hierarchy tree.
4.
5.
Report
File
Print Preview
Page 44 of 395
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADIMN group user should have Access to invoke this window.
Responsibilities
1. The user should have ADMIN responsibilities.
Navigation
Click Main menu
Type menu item.
Click on Administration
Page 45 of 395
Column Description
1.
Class (D)
a. The system display all the class values defined in the define class window
under the FEATYP level.
i. The system automatically display all the class values, it will not allow
the user to edit this column.
2.
Description (D)
a. The system display all the description data defined in the define class
window under the MONTYP level.
i. The system automatically display all the description data, it will not
allow the user to edit this column.
3.
Prefix (O)
a. Enter the prefix name
i. The system will use this prefix name, when user inserts a feature in
the Asset Hierarchy tree.
4.
5.
Report
File
Print Preview
Page 46 of 395
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Administration
Column Description
1. ClassId (D)
a. The system displays the id.
i. Automatically the system assigns the unique id to all class values
define in the GALIOM application.
2. Class value (M)
a. Enter the class value.
3. Active (M)
a. If the check box is checked, the class value is active, if the check box is not
checked the class value is not active.
i. By default the system check the check box.
Page 48 of 395
Page 49 of 395
Report
File
Print preview
Pre-requisites
Page 50 of 395
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Administration
Column Description
1. Attribute Name (M)
a. Enter the attribute name
2. label (O)
a. Enter the label for the attribute
Page 51 of 395
3. Description (O)
a. Enter the description for the attribute.
4. Data type (M)
a. Select the Attribute data type from the drop down.
5. Data size (O)
a. Set the data size by using spin control or edit the column to enter the data
size.
6. Dec size (O)
a. Set the Decimal size by using the spin control or edit the column to enter the
decimal values.
7. UOM (O)
a. Select the Unit of Measurement from the drop down.
8. Default Value (O)
a. Enter the default value for this attribute.
9. Ref Type (O)
a. Select the reference type from the drop down.
10. Column Mode (O)
a. Select the column mode (i.e., whether it is Optional, Mandatory, Display and
Hidden) from the drop down.
11. Text case(O)
a. Select the text case (i.e., ANY, UPPER and LOWER) from the drop down.
12. Active (M)
a. The attribute is active, if the check box is checked. The attribute is not active,
if the check box is not checked.
i. By default the system check the check box (i.e., the attribute is active)
13. Formula (O)
a. Set the formula, if the attribute require any formula.
i. The system provides the formula editor to compute the formula.
14. Updated date (D)
e. The system should display the updated date, when ever user (i.e., ADMIN)
modifies the data.
15. Updated User (D)
f. The system should display the updated user, with the Admin user id, when
ever user modifies the data in this window.
Report
File
Print preview
Page 52 of 395
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Page 53 of 395
Column Description
a. ID (D)
i. The system displays the id automatically.
b. Form Name (M)
i. Enter the Form name
c. Form Label (O)
i. Enter the Form label
d. Description (O)
i. Enter the description about the form
e. Active (M)
i. If the checkbox is checked, the form is active. If the check box is not
checked, then the form is not in active.
1. By default the system checks the checkbox (i.e., Active)
f. Number of columns (O)
i. Specify the number of columns required in the new form.
1. By default the system display one column.
g. Update Date (D)
i. The system should display the updated date, when ever user (i.e.,
ADMIN) modifies the data.
h. Update User (D)
i. The system should display the updated user, with the Admin user id,
when ever user modifies the data in this window.
i.
Seq (M)
i. Enter the seq number ( i.e., Position) of the column in data form
j.
2.
3.
4.
5.
Code (M)
i. Select the GLCODE for the columns attribute from the drop down
list.
1. The system displays the values in the drop down from the
attributes list defined in the GALIOM.
2. The system display all the characters of the attribute like
column name, label, Data type, UOM, Data size etc.
Save button:- After entering the From name, press save button. The system save the
new data form.
Delete button:- The system delete the selected record. When user try to delete the
selected record, the system display the following message Do you wish to delete the
selected record with Yes and No options. If the user clicks on No button, the
system will not delete the selected record, if the user select the Yes button, the system
delete the selected record from the database.
Print button:- The system will print the current display window. before the print the
system display the print setup window to select the printer, if there is more than one
printer is configured.
Refresh:- The system will refresh the current display window.
Page 54 of 395
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Administration
Column Description
1. Form Name (D)
a. The system displays the form name.
2. Description (D)
a. The system displays the description of the Data form.
3. Active (D)
a. The system displays whether the data form is active(A) or in active (I)
4. Updated date (D)
a. The system should display the updated date, when ever user (i.e., ADMIN)
modifies the data.
5. Updated User (D)
a. The system should display the updated user, with the Admin user id, when
ever user modifies the data in this window.
Report
None.
Page 55 of 395
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Administration
Column Description
Note:- The columns are generic, based on the data form is selected in the header
Page 56 of 395
Report
None.
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Administration
Column Description
Page 57 of 395
1. ID (D)
a. The system displays the id for each label.
2. Text type (D)
a. The system display what kind of Text type it is i.e., whether the displayed text
is Label/ReportTitile/ErrMsg/Menu/WinTitile/MicroHelp/File etc.
3. English (O/E)
a. The system displays the label language in English.
i. The system allows the user to edit this column, so that user can enter
the proper input.
4. Spanish (O/E)
a. The system display the label Language in Spanish
i. The system allows the user to edit this column, so that user can enter
the proper input.
5. Updated date (D)
a. The system should display the updated date, when ever user (i.e., ADMIN)
modifies the data.
6. Updated User (D)
a. The system should display the updated user, with the Admin user id, when
ever user modifies the data in this window.
Report
None.
Pre-requisites
1. The user should be active GALIOM Application user
2. At least one asset is registered in the asset hierarchy tree.
Delete button:-.*******
Save button:- The system save the new or modify values.
Refresh button:- The system refresh the current active window.
Exit button:- The system will exit from the GALIOM Application.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
1) Select Asset Management from Modules.
2) From the menu Items select and double-click on
Asset Management.
3) Asset management Screen will appear.
4) Click on Asset Hierarchy tab below the menu
options screen.
5) The below image shows the Asset Hierarchy and
Asset Management screen.
Column Description
Asset Details
1. Name (D)
a. The system displays the name of the Asset, which is selected in the asset
hierarchy tree.
Page 59 of 395
Report
None.
Page 60 of 395
6.2
ASSET HIERARCHY
Pre-requisites
1. Study the client asset hierarchy.
2. Classifying the assets into levels.
3. There should be at least one user how should have ADMIN responsibilities in the
GALIOM application.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. The user having ASSET EDIT or ADMIN responsibility can edit the tree.
Navigation
GALIOM Application icon
NOTE: This asset hierarchy can be defined differently by the implementers using the Administration
Module. Asset Hierarchy levels are configurable.
Column Description
None.
Report
None.
Pre-requisites
1. The user should successfully login into the GALIOM Application.
2. The asset are registered and shown in the Asset Hierarchy tree.
Responsibilities
1. The user should be active user of the GALIOM application.
2. Any user having ASSET EDIT Responsibility to edit.
Navigation
Enter into GALIOM Application
Page 62 of 395
Column Description
None.
Report
None.
6.4
This is one of the tab page present in the Asset management window under the other
information section. This tab page is used to define the Mechanical design data of the
selected Asset. The Mechanical design attributes data allows determining some of the Failure
mechanism automatically
Pre-requisites
1. The user should be active GALIOM Application user.
2. The asset is registered in the asset hierarchy tree.
3. The selected asset should have the mechanical design data.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Page 63 of 395
Click on
NOTES:
Attributes are listed based on configuration. Addition of attributes can be done from configuration. Class and
data form configuration allows setting the attributes. Data forms like mechanical design data is only visible if
data forms are attached to the class (In above image - Liquid Filter).
Column Description
1. The Attributes are generically displayed from the configuration, based on the asset
selected in the Asset hierarchy tree.
Report
None.
Page 64 of 395
Pre-requisites
1. The user should be active GALIOM Application user
2. At least one asset is registered in the asset hierarchy tree.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Failure Mechanism tab page.
Select the
Column Description
1. Failure Mode (M)
Page 65 of 395
Report
None
Pre-requisites
1.
2.
3.
4.
Page 66 of 395
2. Delete button:- The system delete the selected document from the document tab
page.
3. Refresh button:- The system refresh the current active window.
4. Exit button:-The system Exit from the GALIOM Application.
Responsibilities
1.
2.
3.
4.
Navigation
Main Menu
Asset Management
the Documents tab.
Click on
Column Description
1. Document name (D)
a. The system displays the document name.
i. The system will automatically generate the document name.
2. Description (O)
a. Enter the description about the document.
3. Doc Type (M)
a. Select the doc type from the drop down.
Page 67 of 395
Report
None.
Page 68 of 395
Pre-requisites
1. The user should be active GALIOM Application user
2. The attributes for the tag is defined in the data form.
Responsibilities
1. Any user having ASSET EDIT Responsibility can edit this window.
2. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Process data tab page.
Select the
Column Description
1. Seq. (D)
a. The system displays the Seq number automatically.
2. Attribute Name (D)
a. The system displays the attributes under the respective group headings with
expand and collapse icon.
Page 69 of 395
Report
None
Pre-requisites
1. The user should be active GALIOM Application user
2. The attributes for the tag is defined in the data form.
Responsibilities
1. Any user having ASSET EDIT Responsibility can edit this window.
2. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Theoritical Corrosion Rates tab page.
Select the
Page 70 of 395
Column Description
1. Seq. (D)
a. The system displays the Seq number automatically.
2. Attribute Name (D)
a. The system displays the attributes under the respective group headings with
expand and collapse icon.
i. The system displays all the attributes for the selected tag defined in
the data from.
ii. The system provides a feature to expand the attributes by clicking (+)
icon and collapse the attribute list, by clicking the (-) icon.
3. Value (O)
a. Enter the value for the attribute, to process the data. If the value is related to
any formula. Using the formula editor user can keen the formula.
i. The system displays the formula editor icon, just after the value
column.
4. UOM (D)
a. Based on the value the system displays the corresponding unit of
measurement.
Report
None
Page 71 of 395
Pre-requisites
1. The user should be active GALIOM Application user
2. At least one asset is registered in the asset hierarchy tree.
3. COF is configured for the selected asset class type in COF setup window, which is
present in Risk Ranking setup.
Responsibilities
1. Any user having ASSET EDIT Responsibility can edit this window.
2. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Select the
Risk Base Inspection Tab.
Select the RBI assessment type in the Assessment type drop
down Click on Consequence tab page.
Page 72 of 395
Column Description
1. COF Heads (D)
a. Display all the configured COF heads for the selected asset class.
i. System displays the data from the COF setup.
2. Answers (E/M)
a. By default the answers are also displayed based on the COF setup for the
selected asset class in COF setup window.
i. System displays the data from the COF setup.
b. If the user wants to set the different answer, Click on answer field and a list
of consequence of options will appear for the COF element.
c. Once the user change the answer, press the SAVE button or Press Ctrl + S
to save the changes.
3. Update date (D)
a. The system should display the updated date, when ever user modifies the
data.
4. Updated user (D)
a. The system displays the user id, when the user is modify the value in this
window.
Report
None
Page 73 of 395
Pre-requisites
1. The user should be active GALIOM Application user
2. At least one asset is registered in the asset hierarchy tree.
3. POF is configured for the selected asset class type in POF setup window, which is
present in Risk Ranking setup.
Responsibilities
1. Any user having ASSET EDIT Responsibility can edit this window.
2. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Select the
Risk Base Inspection Tab
Select the RBI assessment type in the Assessment type drop
down
Click on Probability tab
Page 74 of 395
Column Description
1. POF Heads (D)
a. Display all the configured POF heads for the selected asset class.
i. System displays the data from the POF setup.
ii. Failure Mechanism:- Factor by failure mechanism and effectiveness,
below POF detail shows the failure mechanisms. Select the options
below for each failure mechanism. These failure mechanisms are
same are those selected in the tag level data.
iii. Remaining life: - Factor by remaining life is based on monitored data.
Application allows you to record UT/RT and other inspection data.
Minimum wall thickness is derived and then remaining life is
calculated. User can select manually also
2. Answers (E/M)
a. By default the answers are also displayed based on the POF setup for the
selected asset class in POF setup window.
i. System displays the data from the POF setup.
b. If the user wants to set the different answer, Click on answer field and a list
of consequence of options will appear for the POF element.
c. Once the user change the answer, press the SAVE button or Press Ctrl + S
to save the changes.
3. Update date (D)
a. The system should display the updated date, when ever user modifies the
data.
4. Updated user (D)
a. The system displays the user id, when the user is modify the value in this
window.
5. Failure Mechanism (POF Detail) (D)
a. Select the options below for each failure mechanism
i. For Factor by failure mechanism and effectiveness, the POF details
show the failure mechanisms.
ii. These failure mechanisms are same are those selected in the tag level
data.
6. Failure Mechanism Options (E/M)
a. Select the options from the drop down.
Report
None
6.10.3 RISK RANKING MATRIX
Once consequence of failure and probability of failure assessment is done, risk ranking is
done automatically. All the data displayed on this screen is fully configured. The Risk
Ranking Screen, Consequence and probability values and the color are be configured during
the implementation. The formula for Risk Ranking matrix is Risk = COF x POF.
Page 75 of 395
Pre-requisites
1. The user should be active GALIOM Application user
2. At least one asset is registered in the asset hierarchy tree.
3. POF & COF Assessment is done for the selected asset.
Responsibilities
1. Any user having ASSET EDIT Responsibility can edit this window.
2. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Select the
Risk Base Inspection Tab
Select the RBI assessment type in the Assessment type drop
down Click on Risk Matrix tab
Column Description
1. COF Value (D)
a. The system displays the configured COF value.
2. COF (D)
a. The system displays the configured COF description against each COF value.
3. POF Value (D)
Page 76 of 395
Report
None
Pre-requisites
1. The user should be active GALIOM Application user
2. The dataform should be defined for the selected Asset class in COF & POF setup
for the selected Assessment type.
3. The system should display the tabs based on the no of dataforms selected.
Responsibilities
1. Any user having ASSET EDIT Responsibility can edit this window.
2. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Select the
Risk Base Inspection Tab
Select the API 581-Semi-Quatitative assessment type in the
Assessment type drop down
Click on COF RBI SQ Assessment by Hole size
Page 77 of 395
Column Description
1. Seq(D)
a. The system display the seq no for each attribute defined in the dataform.
i. The system displays the value form the dataform.
2. Attribute Name (D)
a. The system display the attribute defined in the dataform.
i. The system displays the attribute list from the dataform.
3. Value (D)
a. The system display the values defined in the dataform
i. The system displays the attributes values from the dataform.
4. UOM (D)
a. The system display the unit of measurement defined in the dataform.
i. The system displays the attribute UOM from the dataform.
Report
None
6.11.2 COF RBI SEMI QUANTITATIVE ASSESSMENT FORM
This tab show the attributes with their values used to calculate risk base inspection of COF
RBI Semi Quantitative Assessment for the selected asset class. All the data displayed on this
screen is fully configured.
Pre-requisites
1. The user should be active GALIOM Application user
2. The dataform should be defined for the selected Asset class in COF & POF setup
for the selected Assessment type.
3. The system should display the tabs based on the no of dataforms selected.
Responsibilities
1. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Select the
Risk Base Inspection Tab
Select the API 581-Semi-Quatitative assessment type in the
Assessment type drop down
Click on COF RBI Semi Quantitative Assessment Form.
Page 78 of 395
Column Description
1. Seq(D)
a. The system display the seq no for each attribute defined in the dataform.
2. Attribute Name (D)
a. The system display the attribute defined in the dataform.
3. Value (E/D)
a. The system display the values defined in the dataform
b. The system also allow the user to change the values or to keen the formula in
the editable column, by clicking the icon (To invoke the Formula editor)
.
4. UOM (D)
a. The system displays the Unit of measurement from the dataform.
Report
None
6.11.3 SQ- THINNING MODEL
This tab shows the attributes with their values used to calculate risk base inspection of SQ
Thinning Model Assessment for the selected asset class. All the data displayed on this screen
is fully configured.
Pre-requisites
1. The user should be active GALIOM Application user
2. The data form should be defined for the selected Asset class in COF & POF setup
for the selected Assessment type.
3. The system should display the tabs based on the no of dataforms selected.
Page 79 of 395
Responsibilities
1. Any user having ASSET EDIT Responsibility can edit this window.
2. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Select the
Risk Base Inspection Tab
Select the API 581-Semi-Quatitative assessment type in the
Assessment type drop down
Click on SQ-Thinning Model.
Column Description
1. Seq(D)
a. The system display the seq no for each attribute defined in the dataform.
2. Attribute Name (D)
a. The system display the attribute defined in the dataform.
3. Value (E/D)
a. The system display the values defined in the dataform.
b. The system also allows the user to change the values or to keen the formula
in the editable column, by clicking the icon (To invoke the Formula
.
editor).
4. UOM (D)
a. The system displays the Unit of measurement from the dataform
Report
None
6.11.4 SQ- SCC MODEL
This tab shows the attributes with their values used to calculate risk based inspection of SQ
SCC Model Assessment for the selected asset class. All the data displayed on this screen is
fully configured.
Page 80 of 395
Pre-requisites
1. The user should be active GALIOM Application user.
2. The data form should be defined for the selected Asset class in COF & POF setup
for the selected Assessment type.
3. The system should display the tabs based on the no of dataforms selected.
Responsibilities
1. Any user having ASSET EDIT Responsibility can edit this window.
2. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Select the
Risk Base Inspection Tab
Select the API 581-Semi-Quatitative assessment type in the
Assessment type drop down
Click on SQ-SCC Model.
Column Description
1. Seq(D)
a. The system display the seq no for each attribute defined in the dataform.
2. Attribute Name (D)
a. The system display the attribute defined in the dataform.
3. Value (E/D)
a. The system display the values defined in the dataform.
Page 81 of 395
Report
None
6.11.5 SQ- FATIGUE MODEL
This tab shows the attributes with their values used to calculate risk based inspection of SQ
Fatigue Model Assessment for the selected asset class. All the data displayed on this screen
is fully configured.
Pre-requisites
1. The user should be active GALIOM Application user.
2. The data form should be defined for the selected Asset class in COF & POF setup
for the selected Assessment type.
3. The system should display the tabs based on the no of dataforms selected.
Responsibilities
1. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Select the
Risk Base Inspection Tab
Select the API 581-Semi-Quatitative assessment type in the
Assessment type drop down
Click on SQ-Fatigue Model.
Page 82 of 395
Column Description
1. Seq(D)
a. The system display the seq no for each attribute defined in the dataform.
2. Attribute Name (D)
a. The system display the attribute defined in the dataform.
3. Value (E/D)
a. The system display the values defined in the dataform.
b. The system also allows the user to change the values or to keen the formula
in the editable column, by clicking the icon (To invoke the Formula
editor).
4. UOM (D)
a. The system displays the Unit of measurement from the dataform.
Report
None
Pre-requisites
1. The user should be active GALIOM Application user
2. At least one asset is registered in the asset hierarchy tree.
3. POF & COF Assessment is done for the selected asset.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Test FM Tab
Asset Management
Select the
Page 83 of 395
Column Description
1. Failure Mode (D) - The system displays the failure mode from the failure mechanism
tab present in Asset tab in asset management window.
2. ID (D) - The system displays the failure mechanism id from the failure mechanism
tab present in Asset tab in asset management window.
3. Failure Mechanism (D) - The system display the Failure mechanism description from
the failure mechanism tab present in Asset tab in asset management window.
4. Probability (D) - If the failure Mechanism is not tested then the probability column
shows Not Tested. The probability is tested when user press the Check button.
The value can be High/Medium/Low/Immune and Not Tested.
5. Click the Attach All High probability (B) On clicking this button all the High
probability will be attached to the currently selected asset.
6. Click the Attach All Medium Probability(B) - on clicking this button all the
Medium probability will be attached to the current selected asset.
7. Click the Attach All Low Probability(B) On clicking this button all the Low
probability will be attached to the current selected asset.
Report
None
Page 84 of 395
THE
RAMAINING
LIFE
OF
THE
This tab display the reaming life and retirement dates for each monitoring points present
under the selected tag in the Asset Hierarchy. This tab provides the information like the
monitoring type, test point, feature, Rem.Life, Ret date and next due date etc. This tab also
displays the graph showing the details of the retirement dates for each monitoring points.
Pre-requisites
1. At least one asset is registered in the asset hierarchy tree.
2. POF & COF Assessment is done for the selected asset.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Rem. Life Tab
Asset Management
Select the
Page 85 of 395
Column Description
1. Mon.Type (D)
a. The system displays the Monitoring type of the testpoint.
2. Test Point (D)
a. The system displays the test point id
3. Feature (D)
a. The system displays the feature, under which the test point is present.
4. Rem.Life (D)
a. The system displays the Rem.Life.
5. Ret.Date (D)
a. The system displays the Ret.Date.
6. Next Due Date (D)
a. The system displays the next inspection due date.
7. Theo.CR (D)
a. Fsas
8. Rec.CR (D)
a. Sf
9. Ovr. CR (D)
a. Dsfdf
Page 86 of 395
Report
None
Pre-requisites
1. The user should be active GALIOM Application user
2. At least one asset is registered in the asset hierarchy tree.
3. At least one inspection has taken place in the selected tag.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Due Date Tab
Asset Management
Select the
Column Description
Page 87 of 395
Report
None
Pre-requisites
1. The user should be active GALIOM Application user
2. At least one asset is registered in the asset hierarchy tree.
Page 88 of 395
Pre-requisites
1. The user should be active GALIOM Application user
2. At least one asset is registered in the asset hierarchy tree.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW responsibility can view this window.
Navigation
Main Menu
Checklist Tab
Asset Management
Click Asset Management menu Item
Click on Insert button
Select the
Column Description
1. Asset Name (D)
a. The system displays the asset name of the selected tag.
2. Insp. Date (M)
a. Enter the Inspection date.
b. If user try to save the record, without entering any date in this column. The
system display the following message Enter the Insp.Date.
i. By default the system display the current date.
3. Report No (M)
a. Enter the Report name for this Inspection checklist.
Page 89 of 395
Page 90 of 395
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
check list Tab
Asset Management
Select the
Column Description
1. Insp Date (D)
a. The system display the Inspection date.
2. Insp.Type (D)
a. The system display the Inspection Type
3. Checklist (D)
a. The system display the checklist selected for this tag on the respective
Inspection date and Inspection type.
4. Inspected by (D)
a. Display the user Id , who inspected this.
5. Updated Date (D)
a. The system should display the updated date, when ever user modifies the
data.
Page 91 of 395
Report
None
Pre-requisites
1. None.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Column Description
1. Source location (M)
Page 92 of 395
Pre-requisites
1. The user should select the functional group in asset hierarchy tree and the functional
group should have the tag whose class name is piping.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Column Description
Page 93 of 395
Pre-requisites
1. The user should select the functional group in asset hierarchy tree and the functional
group should have the tag whose class name is vessel.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Page 94 of 395
Column Description
1. Tag name (D)
a. The system display the tag name whose class value is vessel..
2. Description (D)
a. The system displays the description of the tag.
3. Attributes (O)
a. Based on the Tag the system displays the attributes.
REPORT
None.
Pre-requisites
1. The user should select the functional group in asset hierarchy tree and the functional
group should have the tag whose class name is piping.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Page 95 of 395
Column Description
1. Tag name (D)
a. The system display the tag name whose class value is piping
2. Description (D)
a. The system displays the description of the tag.
3. Attributes (O)
a. Based on the Tag the system displays the attributes.
REPORT
None.
Pre-requisites
1. The user should select the functional group in asset hierarchy tree and the functional
group should have the tag whose class name is piping.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Page 96 of 395
Column Description
1. Tag name (D)
a. The system display the tag name whose class value is piping
2. Description (D)
a. The system displays the description of the tag.
3. Feature (O)
a. The system displays the feature name present in a tag.
4. Attributes (O)
a. Based on the Feature the system displays the attributes.
REPORT
None.
Pre-requisites
1. The user should select the functional group in asset hierarchy tree and the functional
group should have the tag whose class name is vessel.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Page 97 of 395
Column Description
1. Tag name (D)
a. The system display the tag name whose class value is Vessel
2. Description (D)
a. The system displays the description of the tag.
3. Feature (O)
a. The system displays the feature name present in a tag.
4. Attributes (O)
a. Based on the Feature the system displays the attributes.
REPORT
None.
Pre-requisites
None.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Item.
Asset Management
Page 98 of 395
Column Description
1. Source location (M)
a. Select the Location from the drop down.
2. Source Functional Group (M)
a. Select the Functional group.
3. Destination Location (M)
a. Select the destination location from the drop down.
4. Destination Functional Group (M)
a. Enter the Destination Functional group.
REPORT
None.
Pre-requisites
None.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
menu Item.
Asset Management
Page 99 of 395
Column Description
1. Source Tag (M)
a. Select the tag from the drop down.
2. Source Feature (M)
a. Select the Feature which is decided to move.
3. Destination Tag (M)
a. Select the destination tag from the drop down, to where the feature wants to
move.
4. Destination Feature (M)
a. Enter the Destination Feature name.
REPORT
None.
Pre-requisites
1. The selected location should have the tags.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
menu Item.
Asset Management
Column Description
1. Location (M)
a. Select the Location.
2. Failure mode (M)
a. Select the failure mode from the drop down.
i. Select the failure mode which is going to set for the entire tags
present under the selected location.
3. FM ID (M)
a. Select the Failure Mechanism from the drop down.
i. Select the Failure Mechanism from the drop down which is going to
set fro the entire tags present under the selected location.
4. Failure Mechanism(D)
a. Based on the FM ID selected, the system displays the Failure Mechanism.
REPORT
None.
Pre-requisites
1. The tags should be present in the source functional group.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
another menu Item.
Column Description
1. Source Location (M)
a. Select the source location from the drop down.
2. Destination Location (M)
a. Select the destination location from the drop down.
3. Source Functional Group (M)
a. Select the source functional group from the drop down.
4. Destination Functional group (M)
a. Select t the Destination Functional group from the drop down.
REPORT
None.
Pre-requisites
1. The test points should be present in the source feature.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
menu Item.
Asset Management
Column Description
1. Source Location (M)
a. Select the source location from the drop down.
2. Destination Location (M)
a. Select the destination location from the drop down.
3. Source Functional Group (M)
a. Select the source functional group from the drop down.
Pre-requisites
1. COF setup for piping equipment group should be defined.
2. The COF is configured at least for one assessment type (i.e., Galiom RBI Assessment
or API 581- Semi Quantitative).
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Column Description
1. Select (M)
a. Select the check box of the tag, if the COF is to assign to the tag of the
selected Assessment Type.
2. Tag (D)
a. Based on the class name selected, the system display all the tags, under that
class name..
3. Description (D)
a. The system displays the description of each tag.
4. Functional Group (D)
a. The system display the Functional group of the displayed tag..
Pre-requisites
1. The COF questionnaire is assigned to the equipments.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Item.
Asset Management
Column Description
1. Select Location
a. Location (M)
i. Select the Location from the drop down.
1. The system displays all the Equipments registered under the
selected location.
2. Equipment/Line Tag List
a. Equipment Name (D)
Page 106 of 395
Pre-requisites
1. The POF questionnaire is assigned to the equipments.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Item.
Asset Management
Column Description
1. Select Location
a. Location (M)
i. Select the Location from the drop down.
1. The system displays all the Equipments registered under the
selected location.
2. Equipment/Line Tag List
a. Equipment Name (D)
i. The system displays all the equipments present under the selected
location.
b. Description (D)
i. The system displays the description of the each equipment against
each equipment.
c. Class (D)
i. The system displays the class of the equipment.
d. Class description (D)
i. The system displays the Class description of each equipment.
e. Functional group (D)
i. The system displays the functional group name of the equipment,
under which the equipment is registered.
REPORT
None.
Pre-requisites
Page 108 of 395
1. None.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Column Description
1. Select Location
a. Location (M)
i. Select the Location from the drop down.
1. The system displays all the Equipments registered under the
selected location.
2. Equipment/Line Tag List
a. Equipment Name (D)
i. The system displays all the equipments present under the selected
location.
b. Description (D)
i. The system displays the description of the each equipment against
each equipment.
c. Class (D)
Pre-requisites
1. The tags are registered under the selected location.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Column Description
1. Select Location
a. Location (M)
i. Select the Location from the drop down.
1. The system displays all the Equipments registered under the
selected location.
2. Equipment/Line Tag List
a. Equipment Name (D)
i. The system displays all the equipments present under the selected
location.
b. Description (D)
i. The system displays the description of the each equipment against
each equipment.
c. Class (D)
i. The system displays the class of the equipment.
d. Class description (D)
i. The system displays the Class description of each equipment.
e. Functional group (D)
i. The system displays the functional group name of the equipment,
under which the equipment is registered.
REPORT
None.
Pre-requisites
1. The features are registered under the selected location.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Page 111 of 395
Main Menu
Item.
Asset Management
Column Description
1. Select Location
a. Location (M)
i. Select the Location from the drop down.
1. The system displays all the Equipments registered under the
selected location.
2. Equipment/Line Tag List
a. Equipment Name (D)
i. The system displays all the equipments present under the selected
location.
b. Description (D)
i. The system displays the description of the each equipment against
each equipment.
c. Class (D)
i. The system displays the class of the equipment.
d. Class description (D)
i. The system displays the Class description of each equipment.
e. Functional group (D)
i. The system displays the functional group name of the equipment,
under which the equipment is registered.
REPORT
None.
Pre-requisites
1. The user should be active GALIOM Application user.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
menu Item.
Asset Management
Column Description
1. Busunt Name (D)
a. The system displays the Business Unit name.
2. Complex Name (D).
a. The system displays the Complex name.
3. Location Name (D)
a. The system displays the Location Name.
4. Location Desc (D)
a. The system displays the Location description.
REPORT
None.
Pre-requisites
1. The user should be active GALIOM Application user.
2. There should be inspection dates.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
menu Item.
Asset Management
Column Description
1. Busunt Name (D)
a. The system displays the Business Unit name.
2. Complex Name (D).
a. The system displays the Complex name.
3. Location Name (D)
a. The system displays the Location Name.
4. Location Desc (D)
a. The system displays the Location description.
Pre-requisites
1. The user should be active GALIOM Application user
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report.
Navigation
Main Menu
Asset Management
Click Asset Management Report menu Item
Select the Asset- Inspection report with clamp fitted
REPORT
File
Pre-requisites
1.
2.
3.
4.
5.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Select the Equipment Attributes
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user
2. There should be few asset are registered in GALIOM application.
3. The user should have responsibility right to click on Asset Hierarchy tree.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Asset Management Report menu Item
Select the Equipment summary by class
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Select the List of Items.
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Select List of items with P & ID.
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Select List of items with Serial No
REPORT
File
Pre-requisites
1.
2.
3.
4.
5.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Asset Management Report menu Item
Select List of Tag within functional group.
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Select Piping Attributes.
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Asset Management Report menu Item
Select Preventative maintenance Programme.
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Asset Management Report menu Item
Select Preventative maintenance Programme chart.
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Asset Management Report menu Item
Select Preventative maintenance programme chart with work to be done.
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Asset Management Report menu Item
Select Preventative maintenance schedule.
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Asset Management Report menu Item
Select Preventative maintenance schedule between dates.
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Asset Management Report menu Item
Select Summary of follow up report raised to date.
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Select Tag-Feature Design Data sheet.
REPORT
File
Pre-requisites
1.
2.
3.
4.
5.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Select Tag design data sheet.
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Asset Management Report menu Item
Select Ultrasonic Wall Thickness Measurement.
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Asset Management Report menu Item
Select UTWT Datasheet Between Dates.
RBI REPORTS
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Semi Quantitative Assessment Form
Select. COF-RBI
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
SQ Assessment by hole size.
Select. COF-RBI
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. There are few assets are registered in GALIOM Application.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Consequence of failure Assessment.
Select
REPORT
File
Pre-requisites
1.
2.
3.
4.
5.
6.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Report Tag Risk Status - RBI.
Select Final
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Report Tag risk Status - SQL.
Select Final
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Consequence Area - Graph.
Select Flammable
REPORT
File
Pre-requisites
1.
2.
3.
4.
5.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Page 139 of 395
Main Menu
Asset Management
Tags with Risk Ranking - SQL.
Select List of
REPORT
File
Pre-requisites
1.
2.
3.
4.
5.
Responsibilities
2. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Page 140 of 395
Main Menu
Asset Management
Tags with Risk Ranking -SQL.
Select List of
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Select List of
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Select List of
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Consequence Index.
Select Pipeline
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
corrosion Index.
Select Pipeline
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Design Index.
Asset Management
Select Pipeline
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Operation Index.
Select Pipeline
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click RBI Report menu Item
PREVENTATIVE MAINTENANCE.
Select PIPELINE
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Remaining Life Time Index.
Select Pipeline
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Third party Damage Index.
Select Pipeline
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
of failure assessment - RBI.
Select Probability
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
of failure assessment - SQL.
Select Probability
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
of failure Mechanism Occurrence.
Select Probability
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Classification-RBI.
Select Risk
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Classification-SQL.
Select Risk
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Ranking Report -RBI.
Select Risk
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Ranking Report - SQL.
Select Risk
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click RBI Report menu Item
Ranking Report (Graphical Representation).
Select Risk
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Fatigue Model.
Select SQ-
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
MODEL.
Asset Management
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Thinning Model.
Select SQ-
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Probable Failure Mechanism.
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Release Area - Continuous.
Select Toxic
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Release Area - Instantaneous.
Select Toxic
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Page 165 of 395
Navigation
Main Menu
Asset Management
Click Inspection memo Report menu Item
Select Recommendation Follow up based condition codes.
REPORT
File
9.2 RECOMMENDATION
CONTAINMENT TYPE
FOLLOW
UP
BASED
ON
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Inspection memo Report menu Item
Select Recommendation Follow up based on containment Type
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Inspection memo Report menu Item
Select Recommendation Follow up based on Follow up text.
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Inspection memo Report menu Item
Select Recommendation follow up based on repair codes.
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Inspection memo Report menu Item
Select Recommendation Follow up report.
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Inspection memo Report menu Item
Select Recommendation Follow up report FFP is Green and Completed.
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Inspection memo Report menu Item
Select Recommendation Follow up report FFP is green and Not Completed.
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Inspection memo Report menu Item
Select Recommendation Follow up Report FFP is orange and 30 days to overdue.
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Inspection memo Report menu Item
Select Recommendation Follow up report FFP is Orange and completed.
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Inspection memo Report menu Item
Select Recommendation Follow up report FFP is Orange and not completed.
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Inspection memo Report menu Item
Select Recommendation Follow up report FFP is Orange and Overdue.
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Inspection memo Report menu Item
Select Recommendation follow up report FFP is Red and completed.
REPORT
File
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Inspection memo Report menu Item
Select Recommendation follow up report FFP is Red and Not completed.
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Inspection memo Report menu Item
Select Recommendation follow up report per tag and not closed.
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Monitored Data
Thickness Measurement.
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Measurement
Monitored Data
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Measurement.
Monitored Data
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Monitored Data
Check Measurement
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Measurement
Monitored Data
Select FreeSpan
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Monitored Data
protection Measurement
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Monitored Data
Pigging Inspection
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
coupons
Monitored Data
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Data
Monitored Data
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Data
Monitored Data
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Monitored Data
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
wall thickness
Monitored Data
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Monitored Data
for UTWT (Min.WT < MAWT)
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. The user should have access right to view this report.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Monitored Data
Monitored Data Reports
for UTWT (Min.WT < MAWT + 1.5)
Pre-requisites
1. There should be MOC or OV request with status Open or Approved.
2. The user should have access to view this report.
Responsibilities
None.
Navigation
Main Menu
Management of change
with Open Status.
MOC Reports
Pre-requisites
1. There should be MOC or OV request with status Completed.
2. The user should have access to view this report.
Responsibilities
None.
Navigation
Main Menu
Management of change
with Open Status
MOC Reports
Pre-requisites
1. There should be MOC or OV request with status withdrawn.
2. The user should have access to view this report..
Responsibilities
None.
Navigation
Main Menu
Management of change
with withdrawn Status
MOC Reports
Pre-requisites
1. There should be MOC or OV request with status extended.
Page 195 of 395
Responsibilities
None.
Navigation
Main Menu
Management of change
with extended Status
MOC Reports
Pre-requisites
1. There should be MOC or OV request with status rejected.
2. The user should have access to view this report..
Responsibilities
None.
Navigation
Main Menu
Management of change
with rejected Status
MOC Reports
Pre-requisites
1. There should be MOC or OV request generated in the GALIOM Application.
2. The user should have access to view this report..
Responsibilities
None.
Navigation
Main Menu
Status Graph
Management of change
MOC Reports
Pre-requisites
1. There should be MOC or OV request with status approved and having due date.
2. The user should have access to view this report..
Responsibilities
None.
Navigation
Main Menu
Management of change
MOC/OV due date expire in 30 days
MOC Reports
Pre-requisites
1. There should be MOC or OV request with extended status.
2. The user should have access to view this report.
Responsibilities
None.
Navigation
Main Menu
Management of change
MOC/OV Extension Expires in 14 days.
MOC Reports
Select Number of
Pre-requisites
1. There should be MOC or OV request with status Approved and should not have the
work order.
2. The user should have access to view this report..
Responsibilities
None.
Navigation
Main Menu
Management of change
Request approved without work order
MOC Reports
MODULE
INTRODUCTION
Management of change and Operating variation is the part of GALIOM application. This
module will manage and record the change requirement for Operating variation and
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
3. Press Print button:- The system prints the current display page.
4.
Press Exit button:- The system will Exit from the GALIOM application.
Responsibilities
Any user having ADMIN Responsibility can edit this window.
Navigation
MainMenu
Management of Change
Column Description
1. MOC/OV Due days (O)
a. This column defines in how many days the MOC/OV request should
completed or eligible for extension, once after the MOC/OV request is
approved by the responsible group who are having Final authority.
b. The MOC due date column, present in MOC/OV request from should
display the value, which is the date of MOC/OV approved plus the number
of days specified in this column.
c. If user try to save the record by entering the negative value in this column, the
system display the following message Please Enter the Positive values
2. MOC/OV Extension Valid days (O)
a. This column defines how many days of Extension should the MOC/OV
request will get, Once the Extension request is approved by the responsible
group who are having Final Authority when the MOC/OV request is crossed
the MOC/OV due date and the MOC/OV status is not
completed/rejected/withdrawn.
Page 202 of 395
Print Preview
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Responsibilities
Any user having ADMIN Responsibility can edit this window
Navigation
MainMenu
Management of Change
Column Description
1. Seq No (D)
a. The system automatic generates the seqno and display.
2. Moc status (D)
a. The system automatically displays the Moc status type (i.e., Initiated, Review,
Approval, Withdrawn and Extension). When user select the Responsible
Report
Press File
Print Preview
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Page 206 of 395
Responsibilities
Any user having ADMIN Responsibility can edit this window.
Navigation
MainMenu
Management of Change
Column Description
1. Seq No (D)
a. The system automatic generates the seqno and display.
2. Responsible Group (D)
a. The system will show all the responsible groups who are involved at different
stages of change management and operating variation workflow process.
3. Days (M)
a. The user will enter the days. The value of this column will influence the
workflow process of MOC/OV request. By default 0 days.
i. The system will display the following message The days should not
be Null , when user try to create or modify the existing record,
without entering any data in this column. And the system will not
save the date, unless the user enters the data into this column.
ii. The system will display the following message The days should not
be less than Zero , when user try to create or modify the existing
record, by entering negative number in this column. And the system
will not save the date, unless the user enters the value greater than or
zero.
4. Updated date (D)
Report
Press File
Print Preview
Pre-requisites
1. The login user should be ADMIN group.
2. The login ADMIN group user should have Access to invoke this window.
Responsibilities
Any user having ADMIN Responsibility can edit this window.
Navigation
MainMenu
Management of Change
Column Description
1. Seq No (M)
a. The seq no is unique to each Responsible group. This seq No defines the tab
sequence order of Responsible group in the management of change
/Operating variation Request form and also defines the workflow sequence
followed for the review and approval of MOC/OV request.
i. The system will not allow the user to enter the duplicate seqno. If user
tries to save the record with duplicate seqno the system will display the
user message There should not be duplicate seqno.
ii. The system display the following message Tab Sequence Number is
mandatory. , If the user try to save/create a record without entering
any data in this column
iii.
2. Responsible Group (M)
a. Select the responsible group, who are involve in the MOC/OV workflow
process from the drop down.
Report
1. Press File
Print Preview
Pre-requisites
1. The Microsoft outlook should present in the PC.
2. All the GALIOM users should have the email ID or all the users who are having
MOC/OV initiation, review and approval right.
3. The MOC/OV users and the users who are having MOC/OV initiation right should
have Microsoft outlook access with userid and password.
4. The MOC/OV initiator should have the emailed, if the user wants to receive the
emails.
Press Exit button:- The system will Exit from the GALIOM application.
Responsibilities
The user should be under any one of the responsible groups, which are involved in the
Management of change /Operating variation review and approval process. to check
the workflow related mails.(i.e., the email subject like The MOC/OV is to review.
2. Any GALIOM user, who is having the MOC/OV initiator right for the Management
of change request/ operating variation request.
3. The user should have MOCDEL responsibility to delete the mails.
1.
Navigation
MainMenu
Management of Change
Column Description
1.
Sender (D)
a. The system displays the mail id of the sender.
2.
Subject (D)
a. The system displays the subject of the mail.
3.
4.
5.
From (D)
a. The system display the mail id from whom the selected mail has came.
6.
To (D)
a. The system display the entire mail ids of the users, who and all received this
selected mail.
7.
Subject (D)
a. The system displays the subject of the selected mail.
8.
Message (D)
a. The system displays the mail message of the selected mail.
9.
Status (D)
a. The system displays the status message about the mail process like. Login
success, reading the mails etc.
Report
1. None.
Pre-requisites
1. The login user should have MOC/OV initiator right, to request the management of
change and also to attach the documents in the document tab for that MOC.
2. The login user should have access to invoke the Asset level & Total MOC/OV
Request list menu item.
3. The login user should have Asset view right to select the Asset, for which the user
wants to initiate the Management of change.
Responsibilities
The user should have MOC/OV initiator right.
The user should have MOCDEL responsibility to delete the documents.
The user should have ASTEDT to access the Asset Hierarchy tree, to select the
asset for which the user wants to request the management of change request.
4. The user should have DOC EDIT responsibility to edit the document.
1.
2.
3.
Navigation
MainMenu
Management of Change
Click on MOC Requests menu Item
Press
Insert button (After selecting the respective asset, to which the user wants to initiate the
Management of change).
Column Description
1.
MOC No (D)
a. The MOC number will be automatically generated by the system.
2.
3.
Location (O)
a. The user has to enter the Location of the Asset i.e., company level/ Business
unit level /Complex level/Location level//Functional group level etc
5.
6.
7.
8.
9.
Number (D/E)
a. On saving the Management of change request, the system displays the work
order number, if there is any work order present for this MOC number in the
SAP system, The system display the work order only, when the ADMIN set
the option Automatic for the column MOC/OV work order Number in
MOC/OV workflow configuration window.
i. This column will be display mode, if the ADMIN selects Automatic
option in the MOC/OV work order number column present in the
MOC setup
b.
The column is in editable mode; also show all the work order numbers
present in the SAP system, if the ADMIN selects Manual option in the
MOC/OV work order number column present in the MOC setup.
i. If the user selects any work order number from the drop down, the
system will display the Wo status, Wo priority, Wo close Date of the
selected Wo order.
11. Wo
Status (D)
a. The system displays the Wo status based on the wo order number selected by
the user from the drop down When the MOC request is created, if the system
finds work order in the SAP system for this MOC number, then the system
display the respective Wo status.
12. Wo
Priority (D)
a. The system displays the Wo Priority Based on the wo order number selected
by the user from the drop down When the MOC request is created, if the
system finds work order in the SAP system for this MOC number, then the
system display the respective Wo Priority.
13. Wo
14. Created
Date (D)
a. When the MOC is initiated, the system displays the current day date as
created date.
15. Created
user (D)
a. When the MOC is initiated, the system displays the MOC initiator user id as
created User.
16. Update
date (D)
a. The system display the updated date, when ever modifies the data.
17. Updated
user (D)
a. The system displays the updated user who ever modifies the data in this
window.
Report
1. Press File
Print Preview
Pre-requisites
The login user should have MOC/OV initiator right, to request the management of
change and also to attach the documents in the document tab for that OV.
2. The login user should have access to invoke the Asset level & Total MOC/OV
Request list menu item.
3. The login user should have Asset view right to select the Asset, for which the user
wants to initiate the Operating variation.
4. There should not be any work order exist in the interface table.
1.
Press Insert button:- The system display a message box click yes to create the
management of change/ click No to create the operating variation having Yes and
Note:- If the user wants to insert a document to the OV, the user has to click the
document tab page and press Insert button. If the user does not have the MOC/OV
initiator right, the system displays the following message you do not have the rights
to attach the documents to the selected MOC/OV request.
3.
Press Delete button:- The system delete the selected document from the document
tab page. The user cannot delete the Management of change or operating variation
request from this window. If there is no documents present in the documents tab
page of the selected MOC/OV request, the system display the following message
you do not have any attached documents to delete. If user not selected any
document in the document tab page and press the deleted button, the system will
display the following message select any document in document tab page and press
delete button. When user select the document in the document tab page and press
delete button, the system display the following message You are about to delete the
document selected, do you wish to continue with Yes and No buttons. If the user
press Yes button, the system delete the selected document from the document tab
page. If the user press the No button, the system will not delete the selected
document from the document tab page.
4.
Press Detail button: - The system will display the selected document details. If
there is no document present the system displays the following message You do not
have any attached documents to show details .
5.
Press Save button:- The system will save the new/modified Operating variation
Request. And when the final authority responsible group approves the Operating
variation, insert a record in the Interface table.
6.
Press Refresh button:- The system refresh the current display and If there is a work
order available for the respective Operating variation request in the interface table,
the system will display the Work order number, work order status, work order
priority and work order close date.
7.
Press Print button:- The system will give print job of the current display page.
8.
Press Exit button:- The system will Exit from the GALIOM application.
Responsibilities
1. The user should have MOC/OV initiator right.
2. The user should have MOCDEL responsibility to delete the documents.
3. The user should have ASTEDT to access the Asset Hierarchy tree, to select the asset
for which the user wants to request the management of change request.
4. The user should have DOC EDIT responsibility to edit the document.
Navigation
MainMenu
Management of Change
Click on MOC requests menu Item
Press
Insert button (After selecting the respective asset, to which the user wants to initiate the
operating variation).
Page 218 of 395
Column Description
1.
OV No (D)
a. The OV number will be automatically generated by the system.
2.
3.
4.
Location (O)
a. The user has to enter the Location of the Asset i.e., company level/ Business
unit level /Complex level/Location level//Functional group level etc.
OV Priority (M)
a. The user has to select the OV priority (i.e., HIGH, MEDIUM, LOW)
i. The system display the following message Priority is mandatory. , If
the user try to save/create a record without entering any data in this
column.
6. OV status (M)
a. By default the system display the OV status is OPEN.
5.
8.
9.
10. Wo
Number (D)
a. Once the respective Operating variation is updated with the work order in
the intermediate table, the system will display the respective work order
number.
i. This column will be display mode, once the Interface system updates
the work order number for the respective Operating variation
request.
b. The column is in editable mode, also show all the work order numbers
present in the SAP system, if the ADMIN selects Manual option in the
MOC/OV work order number column present in the MOC setup.
i. If the user selects any work order number from the drop down, the
system will display the Wo status, Wo priority, Wo close Date of the
selected Wo order.
11. Wo
Status (D)
a. The system displays the Wo status based on the wo order number selected by
the user from the drop down When the MOC request is created, if the system
Page 220 of 395
Priority (D)
a. The system displays the Wo Priority Based on the wo order number selected
by the user from the drop down When the MOC request is created, if the
system finds work order in the SAP system for this OV number, then the
system display the respective Wo Priority.
13. Wo
14. Created
Date (D)
a. When the OV is initiated, the system displays the current day date as created
date.
15. Created
user (D)
a. When the OV is initiated, the system displays the MOC initiator user id as
created User.
16. Update
date (D)
a. The system display the updated date, when ever modifies the data.
17. Updated
user (D)
a. The system displays the updated user who ever modifies the data in this
window.
Report
1. Press File
Print Preview
Days
0
1
1
2
2
2
MOC/OV Priority
High
High
High
High
High
High
If a MOC/OV request is raised on 12/09/2006 and the MOC priority is set to high. Based
on the above configuration priority, the system will allow the Engineer user group user to
edit the Engineer tab page on 12/09/2006 (since the days set is 0), and the responsible
user group should have the MOC/OV review rights. And from 13/09/2006, the system
allow the Inspector, Operation user to edit their respective tabs (since the days set is 1),
and the responsible user group should have the MOC/OV review rights. In similar way, the
system allows the HSE, Maintenance and Senior management user to edit their respective tab
pages from 15/09/2006.
The system is smart enough to handle the workflow process of MOC/OV, when the
workflow is not in sequential then the system will work based on the MOC/OV priority
selected for that respective MOC/OV.
Pre-requisites
1. The login user should belong to Engineer responsible group, and should have review
rights and also the group should have MOCEDIT to edit this tab.
Press Exit button:- The system will Exit from the GALIOM application.
Responsibilities
Page 223 of 395
1.
2.
3.
4.
5.
6.
The user should have MOC/OV review right, to enter the review comments.
The user should have the MOC/OV approval right, to approve/reject the respective
MOC/OV request.
The user should have MOCDEL responsibility to delete the documents.
The user should have ASTEDT to access the Asset Hierarchy tree, to select the asset
for which the MOC/OV request is created and pending for the review/approve by
the engineer group.
The user should have DOC EDIT responsibility to edit the document.
The user should have MOCEDIT to access the MOC/OV requests.
Navigation
MainMenu
Management of Change
on Engineer tab.
Click
Column Description
1.
3.
4.
Acceptance (E/O)
a. If the Engineer group has the approval right, the user can take decision (i.e.
Approved/Rejected/Decide later.), for the respective MOC/OV Request.
b. If the Engineer group has the approval right and Final authority to take
decision on MOC/OV Request, then based on the decision ((i.e.
Approved/Rejected/Decide later.), the system will change the MOC status.
i. If the Engineer group has the approval right, and having final
authority to take decision on MOC/OV Request and selected
approved and save the MOC/OV, then the system will change the
MOC status to Approved. And the system will display the MOC due
date (Today + the number of days enter in the MOC/OV due days in
the MOC workflow configuration setup).
ii. If the Engineer group has the approval right, and having final
authority to take decision on MOC/OV Request and selected rejected
and save the MOC/OV, then the system will change the MOC status
to rejected. And the system will not allow the user the edit any of the
columns in the MOC/OV request form, except if the user is admin
or MOC/OV request initiator.
iii. If the Engineer group has the approval right, and having final
authority to take decision on MOC/OV Request and selected decide
later and save the MOC/OV, then the system will not change the
MOC status (i.e., MOC/OV open). And their will not be any value in
the MOC due date or in complete date column.
5.
6.
Report
1. None
Pre-requisites
1.
2.
3.
4.
5.
6.
The login user should belong to inspection responsible group, and should have
review rights and also the group should have MOCEDIT to edit this tab.
The login user is ADMIN or the login user is the MOC/OV creator (i.e., Initiator),
can edit this tab.
When the respective MOC/OV is following sequence or priority days workflow, can
edit this tab.
When the admin selected unlock in After MOC/OV priority days Lock the tabs
column present in MOC workflow configuration, can edit this tab.
The login user should have the access to the Asset Level & Total MOC/OV Request
List menu item.
The system will not allow the user to edit this tab, in the following scenarios.
a. The system will not allow the user to edit the tab, if the respective MOC
status is Approve/Rejected/extended and withdrawn.
b. The system will not allow the user to edit the tab, if MOC/OV request does
not follow either sequential or MOC/OV priority Days workflow.
c. The system will not allow the user to edit the tab, once the MOC priority
Max days is over, and the lock option is selected in the MOC workflow
configuration window.
Access the Asset Level & Total MOC/OV Request List:- The user should click on
the Asset Level & Total MOC/OV Request List menu. Once the window is open,
selected the respective asset in the asset hierarchy, for which the MOC/OV request is
created and pending for the inspection group review/approval and double click on the
MOC/OV request (i.e., the MOC/OV status will be OPEN) .
a. Edit from the Asset Level MOC/OV Request List.:- Once the Asset
Level & Total MOC/OV Request List menu is clicked, selected the
respective asset in the asset hierarchy, for which the MOC/OV request is
created and pending for the inspection group review/approval and double
click on the MOC/OV request (i.e., the MOC/OV status will be OPEN)
b. Edit from the Total MOC/OV Request List:- Once the Asset Level &
Total MOC/OV Request List menu is clicked, select the total MOC/OV
request list tab and after that select the Open tab. And select the respective
MOC/OV request pending for the inspection group review/approval and
double click on the MOC/OV request (i.e., the MOC/OV status will be
OPEN)
2.
3.
Press Print button:- The system will give print job of the current display page.
4.
Press Exit button:- The system will Exit from the GALIOM application.
Responsibilities
1.
2.
3.
4.
5.
6.
The user should have MOC/OV review right, to enter the review comments.
The user should have the MOC/OV approval right, to approve/reject the respective
MOC/OV request.
The user should have MOCDEL responsibility to delete the documents.
The user should have ASTEDT to access the Asset Hierarchy tree, to select the asset
for which the MOC/OV request is created and pending for the review/approve by
the inspection group.
The user should have DOC EDIT responsibility to edit the document.
The user should have MOCEDIT to access the MOC/OV requests.
Navigation
MainMenu
Management of Change
on Inspection tab.
Click
Column Description
1. Review Date (D/O)
a. When user enters any comments in the review comments column, the system
displays the current day date in this column. And also the column is Editable.
i. The review date should not less than MOC/OV raised date.
ii. If the user try to save the review comments by changing the review
date less than the MOC/OV raised date, the system display the
following message The Review Date should be greater than the
MOC Raised Date. And the system will not update the data, unless
user enters the correct date.
iii. If the user try to save the review comments by changing the review
date greater than the current day date, the system display the
following message The Review Date should be not be greater than
or less than the Today's Date. And the system will not update the
data, unless user enters the correct date.
2. Review Comments (E/O)
a. The user will enter the review comments for the respective MOC/OV.
i. If the user does not have review rights, the system will not allow the
user to edit this column.
ii. If the respective MOC/OV is following the sequence workflow, the
system will allow the user to edit this column.
iii. If the respective MOC/OV is following the priority days workflow,
the system should allow the user to edit this column, only after the
user group qualifies the priority days, from the date of MOC/OV
request is raised.
3. Work Order Required (E/O)
a. By default the value for this check box is No. If the user wants to request for
the work order generation for the MOC, the user has to check this option.
i. If the Inspection group has the final authority to approve the MOC
status and the group approves the MOC/OV request, by checking
this option, the system will generate a work order request and create a
row in the Interface table by displaying a user message "The Work
Order is requested for the Following Management of Change".
4. Acceptance (E/O)
a. If the Inspection group has the approval right, the user can take decision (i.e.
Approved/Rejected/Decide later.), for the respective MOC/OV Request.
b. If the Inspection group has the approval right and Final authority to take
decision on MOC/OV Request, then based on the decision ((i.e.
Approved/Rejected/Decide later.), the system will change the MOC status.
i. If the Inspection group has the approval right, and having final
authority to take decision on MOC/OV Request and selected
approved and save the MOC/OV, then the system will change the
MOC status to Approved. And the system will display the MOC due
date (Today + the number of days enter in the MOC/OV due days in
the MOC workflow configuration setup).
ii. If the Inspection group has the approval right, and having final
authority to take decision on MOC/OV Request and selected rejected
and save the MOC/OV, then the system will change the MOC status
to rejected. And the system will not allow the user the edit any of the
Page 228 of 395
Report
1. None
Pre-requisites
1.
2.
3.
4.
5.
6.
The login user should belong to operations responsible group, and should have review
rights and also the group should have MOCEDIT to edit this tab.
The login user is ADMIN or the login user is the MOC/OV creator (i.e., Initiator),
can edit this tab.
When the respective MOC/OV is following sequence or priority days workflow, can
edit this tab.
When the admin selected unlock in After MOC/OV priority days Lock the tabs
column present in MOC workflow configuration, can edit this tab.
The login user should have the access to the Asset Level & Total MOC/OV Request
List menu item.
The system will not allow the user to edit this tab, in the following scenarios.
a. The system will not allow the user to edit the tab, if the respective MOC
status is Approve/Rejected/extended and withdrawn.
b. The system will not allow the user to edit the tab, if MOC/OV request does
not follow either sequential or MOC/OV priority Days workflow.
c. The system will not allow the user to edit the tab, once the MOC priority
Max days is over, and the lock option is selected in the MOC workflow
configuration window.
Access the Asset Level & Total MOC/OV Request List:- The user should click on
the Asset Level & Total MOC/OV Request List menu. Once the window is open,
selected the respective asset in the asset hierarchy, for which the MOC/OV request is
created and pending for the operations group review/approval and double click on the
MOC/OV request (i.e., the MOC/OV status will be OPEN) .
a. Edit from the Asset Level MOC/OV Request List.:- Once the Asset
Level & Total MOC/OV Request List menu is clicked, selected the
respective asset in the asset hierarchy, for which the MOC/OV request is
created and pending for the operations group review/approval and double
click on the MOC/OV request (i.e., the MOC/OV status will be OPEN)
b. Edit from the Total MOC/OV Request List:- Once the Asset Level &
Total MOC/OV Request List menu is clicked, select the total MOC/OV
request list tab and after that select the Open tab. And select the respective
MOC/OV request pending for the operations group review/approval and
double click on the MOC/OV request (i.e., the MOC/OV status will be
OPEN)
2.
3.
Press Print button:- The system will give print job of the current display page.
4.
Press Exit button:- The system will Exit from the GALIOM application.
Responsibilities
1.
2.
3.
4.
5.
6.
The user should have MOC/OV review right, to enter the review comments.
The user should have the MOC/OV approval right, to approve/reject the respective
MOC/OV request.
The user should have MOCDEL responsibility to delete the documents.
The user should have ASTEDT to access the Asset Hierarchy tree, to select the asset
for which the MOC/OV request is created and pending for the review/approve by
the operations group.
The user should have DOC EDIT responsibility to edit the document.
The user should have MOCEDIT to access the MOC/OV requests.
Navigation
MainMenu
Management of Change
on Operation tab.
Click
Column Description
1.
2.
3.
6.
Report
1.
None
Pre-requisites
The login user should belong to maintenance responsible group, and should have
review rights and also the group should have MOCEDIT to edit this tab.
2. The login user is ADMIN or the login user is the MOC/OV creator (i.e., Initiator),
can edit this tab.
1.
Access the Asset Level & Total MOC/OV Request List:- The user should click on
the Asset Level & Total MOC/OV Request List menu. Once the window is open,
selected the respective asset in the asset hierarchy, for which the MOC/OV request is
created and pending for the maintenance group review/approval and double click on
the MOC/OV request (i.e., the MOC/OV status will be OPEN) .
a. Edit from the Asset Level MOC/OV Request List.:- Once the Asset
Level & Total MOC/OV Request List menu is clicked, selected the
respective asset in the asset hierarchy, for which the MOC/OV request is
created and pending for the maintenance group review/approval and double
click on the MOC/OV request (i.e., the MOC/OV status will be OPEN)
b. Edit from the Total MOC/OV Request List:- Once the Asset Level &
Total MOC/OV Request List menu is clicked, select the total MOC/OV
request list tab and after that select the Open tab. And select the respective
MOC/OV request pending for the maintenance group review/approval and
double click on the MOC/OV request (i.e., the MOC/OV status will be
OPEN)
2.
3.
Press Print button:- The system will give print job of the current display page.
4.
Press Exit button:- The system will Exit from the GALIOM application.
Responsibilities
1.
The user should have MOC/OV review right, to enter the review comments.
5.
6.
The user should have the MOC/OV approval right, to approve/reject the respective
MOC/OV request.
The user should have MOCDEL responsibility to delete the documents.
The user should have ASTEDT to access the Asset Hierarchy tree, to select the asset
for which the MOC/OV request is created and pending for the review/approve by
the maintenance group.
The user should have DOC EDIT responsibility to edit the document.
The user should have MOCEDIT to access the MOC/OV requests.
Navigation
MainMenu
Management of Change
on Maintenance tab.
Click
Column Description
1.
2.
4.
Acceptance (E/O)
a. If the Maintenance group has the approval right, the user can take decision
(i.e. Approved/Rejected/Decide later.), for the respective MOC/OV
Request.
b. If the Maintenance group has the approval right and Final authority to take
decision on MOC/OV Request, then based on the decision ((i.e.
Approved/Rejected/Decide later.), the system will change the MOC status.
i. If the Maintenance group has the approval right, and having final
authority to take decision on MOC/OV Request and selected
approved and save the MOC/OV, then the system will change the
MOC status to Approved. And the system will display the MOC due
date (Today + the number of days enter in the MOC/OV due days in
the MOC workflow configuration setup).
ii. If the Maintenance group has the approval right, and having final
authority to take decision on MOC/OV Request and selected rejected
and save the MOC/OV, then the system will change the MOC status
to rejected. And the system will not allow the user the edit any of the
columns in the MOC/OV request form, except if the user is admin
or MOC/OV request initiator.
iii. If the Maintenance group has the approval right, and having final
authority to take decision on MOC/OV Request and selected decide
later and save the MOC/OV, then the system will not change the
MOC status (i.e., MOC/OV open). And their will not be any value in
the MOC due date or in complete date column.
5.
6.
Report
Pre-requisites
1.
2.
3.
4.
5.
6.
The login user should belong to Senior Management responsible group, and should
have review rights and also the group should have MOCEDIT to edit this tab.
The login user is ADMIN or the login user is the MOC/OV creator (i.e., Initiator),
can edit this tab.
When the respective MOC/OV is following sequence or priority days workflow, can
edit this tab.
When the admin selected unlock in After MOC/OV priority days Lock the tabs
column present in MOC workflow configuration, can edit this tab.
The login user should have the access to the Asset Level & Total MOC/OV Request
List menu item.
The system will not allow the user to edit this tab, in the following scenarios.
a. The system will not allow the user to edit the tab, if the respective MOC
status is Approve/Rejected/extended and withdrawn.
b. The system will not allow the user to edit the tab, if MOC/OV request does
not follow either sequential or MOC/OV priority Days workflow.
c. The system will not allow the user to edit the tab, once the MOC priority
Max days is over, and the lock option is selected in the MOC workflow
configuration window.
Access the Asset Level & Total MOC/OV Request List:- The user should click on
the Asset Level & Total MOC/OV Request List menu. Once the window is open,
selected the respective asset in the asset hierarchy, for which the MOC/OV request is
created and pending for the Senior Management group review/approval and double
click on the MOC/OV request (i.e., the MOC/OV status will be OPEN).
a. Edit from the Asset Level MOC/OV Request List.:- Once the Asset
Level & Total MOC/OV Request List menu is clicked, selected the
respective asset in the asset hierarchy, for which the MOC/OV request is
created and pending for the Senior Management group review/approval and
double click on the MOC/OV request (i.e., the MOC/OV status will be
OPEN)
b. Edit from the Total MOC/OV Request List:- Once the Asset Level &
Total MOC/OV Request List menu is clicked, select the total MOC/OV
request list tab and after that select the Open tab. And select the respective
MOC/OV request pending for the Senior Management group
review/approval and double click on the MOC/OV request (i.e., the
MOC/OV status will be OPEN).
3.
Press Print button:- The system will give print job of the current display page.
4.
Press Exit button:- The system will Exit from the GALIOM application.
Responsibilities
1.
2.
3.
4.
5.
6.
The user should have MOC/OV review right, to enter the review comments.
The user should have the MOC/OV approval right, to approve/reject the respective
MOC/OV request.
The user should have MOCDEL responsibility to delete the documents.
The user should have ASTEDT to access the Asset Hierarchy tree, to select the asset
for which the MOC/OV request is created and pending for the review/approve by
the Senior Management group.
The user should have DOC EDIT responsibility to edit the document.
The user should have MOCEDIT to access the MOC/OV requests.
Navigation
MainMenu
Management of Change
on Senior Management tab.
Click
Column Description
1.
3.
4.
Acceptance (E/O)
a. If the Senior Management group has the approval right, the user can take
decision (i.e. Approved/Rejected/Decide later.), for the respective
MOC/OV Request.
b. If the Senior Management group has the approval right and Final authority to
take decision on MOC/OV Request, then based on the decision ((i.e.
Approved/Rejected/Decide later.), the system will change the MOC status.
i. If the Senior Management group has the approval right, and having
final authority to take decision on MOC/OV Request and selected
approved and save the MOC/OV, then the system will change the
MOC status to Approved. And the system will display the MOC due
date (Today + the number of days enter in the MOC/OV due days in
the MOC workflow configuration setup).
ii. If the Senior Management group has the approval right, and having
final authority to take decision on MOC/OV Request and selected
rejected and save the MOC/OV, then the system will change the
MOC status to rejected. And the system will not allow the user the
6.
Report
1. None
Pre-requisites
1.
2.
3.
4.
5.
6.
The login user should belong to HSE responsible group, and should have review rights
and also the group should have MOCEDIT to edit this tab.
The login user is ADMIN or the login user is the MOC/OV creator (i.e., Initiator),
can edit this tab.
When the respective MOC/OV is following sequence or priority days workflow, can
edit this tab.
When the admin selected unlock in After MOC/OV priority days Lock the tabs
column present in MOC workflow configuration, can edit this tab.
The login user should have the access to the Asset Level & Total MOC/OV Request
List menu item.
The system will not allow the user to edit this tab, in the following scenarios.
a. The system will not allow the user to edit the tab, if the respective MOC
status is Approve/Rejected/extended and withdrawn.
b. The system will not allow the user to edit the tab, if MOC/OV request does
not follow either sequential or MOC/OV priority Days workflow.
c. The system will not allow the user to edit the tab, once the MOC priority
Max days is over, and the lock option is selected in the MOC workflow
configuration window
Access the Asset Level & Total MOC/OV Request List.- The user should click on
the Asset Level & Total MOC/OV Request List menu. Once the window is open,
Page 239 of 395
3.
Press Print button:- The system will give print job of the current display page.
4.
Press Exit button:- The system will Exit from the GALIOM application.
Responsibilities
1.
2.
3.
4.
5.
6.
The user should have MOC/OV review right, to enter the review comments.
The user should have the MOC/OV approval right, to approve/reject the respective
MOC/OV request.
The user should have MOCDEL responsibility to delete the documents.
The user should have ASTEDT to access the Asset Hierarchy tree, to select the asset
for which the MOC/OV request is created and pending for the review/approve by
the HSE group.
The user should have DOC EDIT responsibility to edit the document.
The user should have MOCEDIT to access the MOC/OV requests.
Navigation
MainMenu
on HSE tab.
Management of Change
Click
Column Description
1.
2.
3.
Acceptance (E/O)
a. If the HSE group has the approval right, the user can take decision (i.e.
Approved/Rejected/Decide later.), for the respective MOC/OV Request.
b. If the HSE group has the approval right and Final authority to take decision
on MOC/OV Request, then based on the decision ((i.e.
Approved/Rejected/Decide later.), the system will change the MOC status.
i. If the HSE group has the approval right, and having final authority to
take decision on MOC/OV Request and selected approved and save
the MOC/OV, then the system will change the MOC status to
Approved. And the system will display the MOC due date (Today +
the number of days enter in the MOC/OV due days in the MOC
workflow configuration setup).
ii. If the HSE group has the approval right, and having final authority to
take decision on MOC/OV Request and selected rejected and save
the MOC/OV, then the system will change the MOC status to
rejected. And the system will not allow the user the edit any of the
columns in the MOC/OV request form, except if the user is admin
or MOC/OV request initiator.
iii. If the HSE group has the approval right, and having final authority to
take decision on MOC/OV Request and selected decide later and
save the MOC/OV, then the system will not change the MOC status
(i.e., MOC/OV open). And their will not be any value in the MOC
due date or in complete date column.
7.
Report
1. None
12.13.1 HOW TO SET THE COF VALUE IN HSE TAB
This is window is the part of the HSE tab. The system allows only HSE group user and
ADMIN to edit the consequences button present in the HSE tab. The user has to select the
Pre-requisites
The login user should belong to HSE responsible group.
The login user is ADMIN or the login user is the MOC/OV creator (i.e., Initiator),
can click this button.
3. The system will not allow the user to click this button, in the following scenarios.
a. The system will not allow the user to click this button, if the respective MOC
status is Rejected withdrawn.
b. The system will not allow the user to click this button, if MOC/OV request
does not follow either sequential or MOC/OV priority Days workflow.
c. The system will not allow the user to click this button, once the MOC
priority Max days is over, and the lock option is selected in the MOC
workflow configuration window.
1.
2.
Access the Asset Level & Total MOC/OV Request List:- The user should click on
the Asset Level & Total MOC/OV Request List menu. Once the window is open,
selected the respective asset in the asset hierarchy, for which the MOC/OV request is
created and pending for the HSE group review/approval and double click on the
MOC/OV request (i.e., the MOC/OV status will be OPEN).
a. Edit from the Asset Level MOC/OV Request List.:- Once the Asset
Level & Total MOC/OV Request List menu is clicked, selected the
respective asset in the asset hierarchy, for which the MOC/OV request is
created and pending for the HSE group review/approval and double click
on the MOC/OV request (i.e., the MOC/OV status will be OPEN), then
go to HSE tab page.
b. Edit from the Total MOC/OV Request List:- Once the Asset Level &
Total MOC/OV Request List menu is clicked, select the total MOC/OV
request list tab and after that select the Open tab. And select the respective
MOC/OV request pending for the HSE group review/approval and double
click on the MOC/OV request (i.e., the MOC/OV status will be OPEN),
then go to HSE tab page.
2.
Press Ok button:- The system will update the changes made in COF value window to
HSE tab page.
4.
Press close button:- The system will close the COF Value window.
Responsibilities
1.
2.
3.
4.
5.
6.
The user should have MOC/OV review right, to enter the review comments.
The user should have the MOC/OV approval right, to approve/reject the respective
MOC/OV request.
The user should have MOCDEL responsibility to delete the documents.
The user should have ASTEDT to access the Asset Hierarchy tree, to select the asset
for which the MOC/OV request is created and pending for the review/approve by
the HSE group.
The user should have DOC EDIT responsibility to edit the document.
The user should have MOCEDIT to access the MOC/OV requests.
Navigation
MainMenu
HSE tab
Management of Change
Click on MOC Request menu item
Press the Consequences tab.
Click on
Column Description
1.
2.
3.
4.
5.
Report
1. None
Pre-requisites
The login user should have withdrawn request rights.
The MOC/OV status should be open.
If the login user is ADMIN or the login user is the MOC/OV creator (i.e., Initiator),
can edit this tab.
4. When the respective MOC/OV is following sequence or priority days workflow, the
login user having withdrawn rights can edit this tab.
5. The login user should have the access to the Asset Level & Total MOC/OV Request
List menu item.
6. The system will not allow the user to edit this tab, in the following scenarios.
a. The system will not allow the user to edit the tab, if the respective MOC
status is Approve/Rejected/extended and withdrawn.
b. The system will not allow the user to edit the tab, if MOC/OV request does
not follow either sequential or MOC/OV priority Days workflow.
c. The system will not allow the user to edit the tab, once the MOC priority
Max days is over, and the lock option is selected in the MOC workflow
configuration window.
1.
2.
3.
Access the Asset Level & Total MOC/OV Request List:- The user should click on
the Asset Level & Total MOC/OV Request List menu. Once the window is open,
selected the respective asset in the asset hierarchy, for which the MOC/OV request is
created, double click on the MOC/OV request and click on withdrawn tab.
a. Edit from the Asset Level MOC/OV Request List:- Once the Asset Level
& Total MOC/OV Request List menu is clicked, selected the respective asset
in the asset hierarchy, for which the MOC/OV request is created and double
click on the MOC/OV request and click on withdrawn tab.
b. Edit from the Total MOC/OV Request List:- Once the Asset Level &
Total MOC/OV Request List menu is clicked, select the total MOC/OV
request list tab and after that select the Open tab. And select the respective
3.
Press Exit button:- The system will Exit from the GALIOM application.
Responsibilities
The user should have MOC/OV final authority, to approve/reject/decide later the
withdrawn request
2. The user should have the MOC/OV withdrawn right, to make request for withdrawn.
3. The user should have ASTEDT to access the Asset Hierarchy tree, to select the asset
for which the MOC/OV request is created.
4. The user should have MOCEDIT to access the MOC/OV Request.
1.
Navigation
MainMenu
Management of Change
on withdrawn tab.
Click
Column Description
Requested by (O/E)
a. The user will enter the name of the user, who is requesting for the
withdrawn.
2. Withdrawn Comments (O/E)
a. The user enter the reason for the withdrawn request
3. Acceptance (O/E)
a. The system allows only the final authority user to take action on the
withdrawn request made by some other responsible user group or same
responsible user group.
1.
Report
1. None
Pre-requisites
The login user should have extension request right.
The MOC/OV status should be Approved.
The current day date should be greater than MOC/OV due date, to edit this tab.
If the login user is ADMIN or the login user is the MOC/OV creator (i.e., Initiator),
can edit this tab.
5. When the respective MOC/OV is following sequence or priority days workflow, the
login user having extension rights can edit this tab.
6. The login user should have the access to the Asset Level & Total MOC/OV Request
List menu item.
7. The system will not allow the user to edit this tab, in the following scenarios.
a. The system will not allow the user to edit the tab, if the respective MOC
status is rejected withdrawn/open.
b. The system will not allow the user to edit the tab, if MOC/OV request does
not follow either sequential or MOC/OV priority Days workflow.
c. The system will not allow the user to edit the tab, once the MOC priority
Max days is over, and the lock option is selected in the MOC workflow
configuration window.
1.
2.
3.
4.
Access the Asset Level & Total MOC/OV Request List:- The user should click on
the Asset Level & Total MOC/OV Request List menu. Once the window is open,
selected the respective asset in the asset hierarchy, for which the MOC/OV request is
created, double click on the MOC/OV request and click on extension tab.
a. Edit from the Asset Level MOC/OV Request List:- Once the Asset Level
& Total MOC/OV Request List menu is clicked, selected the respective asset
in the asset hierarchy, for which the MOC/OV request is created and double
click on the MOC/OV request and click on extension tab.
b. Edit from the Total MOC/OV Request List:- Once the Asset Level &
Total MOC/OV Request List menu is clicked, select the total MOC/OV
request list tab and after that select the Open tab. And select the respective
MOC/OV request and double click on the MOCOV, then click on extension
tab.
2.
3.
Press Exit button:- The system will Exit from the GALIOM application.
Responsibilities
The user should have MOC/OV final authority, , to approve/reject/decide later the
extension request
2. The user should have the MOC/OV extension right, to make request for withdrawn.
3. The user should have ASTEDT to access the Asset Hierarchy tree, to select the asset
for which the MOC/OV request is created.
4. The user should have MOCEDIT to access the MOC/OV Request.
1.
Navigation
MainMenu
Management of Change
on extension tab
Click
Column Description
1.
2.
3.
4.
5.
Requested by (O/E)
a. The user will enter the name, who is requesting for the Extension
Extension Comments (O/E)
a. The user enters the reason for the extension request.
Requested Date (D)
a. The system display the Requested date, when the user request for the
extension.
Acceptance (O/E)
a. The final authority user group will edit this column, to take decision on
Extension request.
i. If the final authority responsible group reject / decide later on
extension request, the MOC/OV status will not change to Extended.
And the status is approved only.
Validity start date (E)
a. The system will display the validity start date the date of Extension approved.
i. The system automatically displays the Validity start date (i.e. The date
of Extension approved), and validity End date (from the day of
extension approved plus the number of days specified in MOC/OV
extension valid days column present in moc/ov workflow
configuration window), when the MOC/OV extension request is
approved by the final authority user group.
ii. If the user tries to save the record, by entering the Extension start
date, less than the MOC/OV raised date, the system will display the
following message The Extension Start Date should be Greater than
the MOC Raised Date.
iii. If the user try to save the record, by entering the lesser date in
extension end date than extension start date, the system display the
following message The Extension End Date should be greater than
the Extension Start Date.
iv. If the user try to save the record, by entering the extension start date
lesser than the MOC/OV due date, the system display the following
Report
1. None
Pre-requisites
1. The login user should have access to the MOC/OV Request reports menu.
2. The user should have access to the respective report. i.e., the report should be active
in the user access list, in Assign Module/Menu to users window present in
Administration Module.
Responsibilities
1.
None.
Navigation
MainMenu
Management of Change
desired report
Select the
Column Description
1. None.
Discussed below is the step by step overview of the usage and functionality of each of the
above windows
Pre-requisites
1. None
Responsibilities
1. Any user having ENGEDT Responsibility can edit this window.
2. Any user having ENGDEL responsibility can delete the record in this window.
Navigation
Main Menu
Item
Engineering Reference
Column Description
1. List of Reference Section
a. Reference Name (D)
i. Name of the Reference parameter as defined in the Reference Master.
b. Description (D)
i. Description of the reference, again as defined in the Reference Master
in Administration Module.
c. Updated Date (D)
i. GALIOM system date as on which Reference Name was entered.
d. Updated User (D)
i. GALIOM user Id for the information as to who entered the
Reference Name
2. Reference Values Section
a. Seq (D)
i. Name of the Reference parameter as defined in the Reference Master.
b. Code (M)
i. Description of the reference, again as defined in the Reference Master
in Administration Module.
c. Reference name (O)
i. The long name of the code defined for the reference value in the
listing section.
d. Description (O)
i. Definition in details for the Reference Name defined.
e. Active (O)
i. Check box to indicate if the current reference code entered is in
Active status.
f. Updated Date (D)
i. GALIOM system date as on which Reference Code was entered.
g. Updated User (D)
i. GALIOM user Id for the information as to who entered the
Reference Code.
Report
None.
Pre-requisites
1. None
Responsibilities
1. Any user having ENGDEL responsibility can delete the record in this window.
2. Any user having ENGEDT Responsibility can edit this window
Navigation
Main Menu
Item
Engineering Reference
Column Description
1. List of Material Spec
a. Material Spec (D)
i. Name of the Material as defined in the Reference Master.
b. Design Code (D)
i. Display the design code.
2. Material Specification Detail
a. . Material Spec (D)
i. Name of the Material as defined in the Reference Master.
b. Description (O)
i. Text in detail about the Material.
c. Design Code (D)
Page 255 of 395
UOM (O)
i. Displays a dropdown of the reference values as defined in the Define
reference values in Administration
Module for Reference type
UOM.
j.
Stress (O)
i. Design specification data.
m. Active (O)
i. Check box to state the active status of the material.
n. Updated Date (D)
i. GALIOM system date as on which the Material Specs were saved.
Data appears automatically when user presses the Save menu option.
o. Updated User (D)
i. GALIOM user Id for the information as to who entered the data for
Material Specs. The data here gets
loaded automatically once user
uses the Save menu option.
3. Details
a. Stress values
Page 256 of 395
Report
None
Pre-requisites
1. None.
Responsibilities
1. Any user having ENGDEL responsibility can delete the record in this window.
2. Any user having ENGEDT Responsibility can edit this window.
Navigation
Main Menu
Engineering Reference
Column Description
1. List of piping class
a. Piping Class (D)
i. Name of the Piping Class.
b. Description (D)
i. Display short detail of the class
2. Piping class Detail
a. Piping Class (D)
i. Name of the Piping Class
b. Description (O)
i. Text in detail about the Piping Class
c. Design Code(D)
i. Displays a dropdown of the reference values as defined in the Define
reference values in Administration Module for Reference type
DESCOD.
d. Material Type (M)
i. Displays a dropdown of the reference values as defined in the Define
reference values in Administration
Module for Reference type
MATTYP.
e. Design Temp Min (O) ( KPa-unit of measurement)
i. Design specification data
f. Design Temp Max (O) ( KPa-unit of measurement)
i. Design specification data
g. Corrosion Allowance (O) (mm-unit of measurement)
i. Design specification data
h. Long Description (O)
i. Displays a dropdown of the reference values as defined in the Define
reference values in Administration
Module for Reference type
UOM.
i. Active (O)
i. Check box to state the active status of the Piping Class.
j. Updated Date (D)
i. GALIOM system date as on which the Piping Class was saved. Data
appears automatically when user
presses the Save menu option.
k. Updated user (D)
i. GALIOM user Id for the information as to who entered the data for
Piping Class. The data here gets
loaded automatically once user
uses the Save menu option.
3. Nominal OD and Schedule
a. NOM OD (M)
i. Design specific data
b. Schedule (O)
i. Text in detail about the Piping Class.
c. Joint Efficiency (O)
i. Design specific data.
d. Active(O)
i. Check box to state the active status of the Piping Class.
e. Updated Date (D)
Report
None
Pre-requisites
1. None.
Responsibilities
1. Any user having ENGEDT Responsibility can edit this window.
2. Any user having ENGDEL responsibility can delete the record in this window.
Navigation
Page 260 of 395
Main Menu
Item
Engineering Reference
Column Description
1. List of Material Spec
a. Code (D)
i. Displays the code for the material (As the Material category).
b. The Name (D)
i. Display the name given to the Material in the system.
c. Description (D)
i. Details about the material in short
2. Schedule Nominal WT
a. Nominal Pipe Size (M)
i. Pipe specific measurement data in inches
b. Schedule (M)
i. Pipe specific measurement data.
c. NOM WT (O) (mm)
i. Numeric data for the Nominal wall thickness based on the Nominal
pipe size and the schedule entered for the Material category.
d. Active (M)
i. Option for the user to specify if the record is applicable to get the
Nominal Wall thickness of the Asset in the Mechanical
Design
data in Asset Management Window or similar window.
e. Update Date (D)
i. GALIOM system date as on which the Schedule Nominal WT was
saved. Data appears automatically when
user presses the Save
menu option.
f. Update User (D)
i. GALIOM user Id for the information as to who entered the data for
Schedule Nominal WT. The data here gets
loaded automatically
once user uses the Save menu option.
Page 261 of 395
Report
None
Pre-requisites
1. None
Responsibilities
1. Any user having ENGDEL responsibility can delete the record in this window.
2. Any user having ENGEDT Responsibility can edit this window.
Navigation
Main Menu
Engineering Reference
Column Description
1. UOM From (M)
a. Unit of Measurement from which the conversion is to be done.
Page 262 of 395
2. UOM to (M)
a. Unit of Measurements to which the conversion is to be done.
3. Operator (M)
a. Arithmetic operator to be applied for the conversion.
4. Factor (M)
a. Conversion related specific data.
5. Active (M)
a. Option for the user to state if the conversion is applicable and can be used in
the system. If no, the conversion will not actually work in the system.
6. Updated Date (D)
a. GALIOM system date as on which the UOM conversion factors were saved.
Data appears automatically when
user presses the Save menu option.
7. Updated User (D)
a. GALIOM user Id for the information as to who entered the data for UOM
conversion factors. The data here
gets loaded automatically once user
uses the Save menu option.
Report
None
Pre-requisites
1. None.
Responsibilities
1. Any user having ENGEDT Responsibility can edit this window.
2. Any user having ENGDEL responsibility can delete the record in this window.
Navigation
Main Menu
Engineering Reference
Column Description
1. List of Failure Mechanisms
a. Failure Mechanism (D)
i. Displays the Names of Failure Mechanisms already entered into the
system.
b. Description (D)
Report
None
Pre-requisites
1. None.
Responsibilities
1. Any user having ENGDEL responsibility can delete the record in this window.
2. Any user having ENGEDT Responsibility can edit this window.
Navigation
Main Menu
Item
Engineering Reference
Column Description
1. List of Failure Modes
a. ID (D)
i. Unique ID for the Failure Mode defined in the system.
b. Failure Mode (D)
i. Name of the Failure Mode as defined in the system. This is defined in
the Reference Values window in
the Administration Module for
the Code FLRMOD.
2. Connected Failure Mechanism
a. SEQ (D)
i. Unique sequence number for the Mechanisms connected to the
failure.
b. Failure Mechanism (M)
i. Dropdown to select the Failure Mechanism connected to the Failure
Mode.
Report
None
Pre-requisites
1. None.
Responsibilities
1. Any user having ENGEDT Responsibility can edit this window.
2. Any user having ENGDEL responsibility can delete the record in this window.
Navigation
Engineering Reference
Column Description
1. List of Failure Mechanism
a. Failure Mechanism (D)
i. Name of the Failure Mechanism
b. Description (D)
i. Short details about the Failure Mechanism
c. Updated Date (D)
i. GALIOM system date as on which the Failure Mechanisms were
saved. Data appears automatically when
user presses the Save
menu option.
d. Updated User (D)
i. GALIOM user Id for the information as to who entered the data for
Failure Mechanisms. The data here gets loaded automatically once
user uses the Save menu option.
2. Inspection Effectiveness
a. Effectiveness (D)
i. Is the Element Answer as entered in the Head Elements wintion in
the POF setup window for the Head Inspection Effectiveness.
b. POF (M)
i. Is the Element Answers POF as entered in the Head Elements
wintion in the POF setup window for the
Head Inspection
Effectiveness
c. Updated Date (D)
i. GALIOM system date as on which the Inspection Effectiveness data
were saved. Data appears
automatically when user presses the
Save menu option.
Page 268 of 395
Report
None
Pre-requisites
1. None.
Responsibilities
1. Any user having ENGEDT Responsibility can edit this window.
2. Any user having ENGDEL Responsibility can delete the records in this window.
Navigation
Main Menu
Engineering Reference
Column Description
1. List of Failure Mechanism
a. Failure Mechanism (D)
i. Name of the Failure Mechanism
b. Description (D)
i. Short details about the Failure Mechanism.
c. Updated Date (D)
i. GALIOM system date as on which the Failure Mechanisms were
saved. Data appears automatically when
user presses the Save
menu option.
d. Updated User (D)
i. GALIOM user Id for the information as to who entered the data for
Failure Mechanisms. The data here gets loaded automatically once
user uses the Save menu option.
2. POF Options.
a. SEQ (D)
i. Unique ID for the POF option.
b. Options (M)
i. Option name.
c. POF (M)
i. Drop down for POF values.
d. Updated Date (D)
i. GALIOM system date as on which the FM POFs were saved. Data
appears automatically when user presses the Save menu option.
e. Updated User (D)
Page 270 of 395
Report
None
Pre-requisites
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Values Icon.
Click on COF
Column Description
1. COF Values
a. ID (D)
i. The system displays the Id of the COF value
b. COF (D)
i. The system displays the COF value description
c. COF VALUE (D)
i. The system displays the COF values
d. Color (D)
Report
None
14.1.2 COF HEADS
This window is basically to define the kinds of the COFs that be measured in the system. It
again has two sections. This window has two sections 1. COF Heads 2. Data Entry/
Modification
1.COF HEADS:- The system display all the previous COF heads defined in the GALIOM
Application.
2.Data Entry / Modification:- This section display the details of the selected record in the
COF Head section.
Pre-requisites
1. For the COF value setup user should have ADMIN responsibility.
2. The COF values to be defined.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Heads Icon.
Click on COF
Column Description
1. COF Heads
a. COF Head(D)
i. The system displays all the previous defined COF heads.
b. Description (D)
i. The system displays the descriptions of the COF heads against each
COF Head value.
c. Updated Date (D)
i. The system display the date, when the ADMIN user change or create
a new record in this window.
Report
None
14.1.3 HEAD ELEMENTS
This window is used to define the elements for the selected Head and to define the element
answers for the selected head. This window is having four sections 1. Select a head, 2.
Elements of Head, 3. Data Entry/Modification, 4.Element Answers.
1. Select a head :- This section provide a drop down to select the COF heads.
2. Elements of head :- This section display all the elements defined for the selected head
value in the select head section.
3.Data Entry/Modification:- This section display the details of the element selected in the
Elements of head section.
4.Element answers:- This section display all the Answers with respective COF value setup
against each element of head.
Pre-requisites
1. For the COF value setup user should have ADMIN responsibility.
2. The COF heads to be defined.
3. If there is any formula to define for the respective COF elements, the arrtibutes using
in the formula should be defined and have the proper value.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Risk Ranking Setup
Elements Icon.
Click on COF
Column Description
1. Select a head
a. Head name (M)
i. Select the Head name from the drop down.
1. The system displays all the Head values, which are defined in
the COF heads section.
2. Element of Head
a. Seq (D)
Report
None
14.1.4 ASSIGN TO CLASS
This window is used to assign the assessment type for each class. This window is having four
sections 1. select a class, 2.Element of class, 3. Data Entry/Modification, 4. Element
Answers.
1. Select a class :- This section provide a drop down to select the class.
2. Elements of class :- This section display all the elements defined for the selected class
and selected assessment type.
3.Data Entry/Modification:- This section display the details of the element selected in the
Elements of class section.
4.Element answers:- This section display all the
Pre-requisites
1. For the COF value setup user should have ADMIN responsibility.
2. The COF elements to be defined.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Risk Ranking Setup
Assign to class Icon.
Click on
Column Description
1. Select a class
a. Class name (M)
i. Select the class name from the drop down
b. Assessment Type (M)
i. Select the Assessment type from the drop down for the selected class.
c. Formula (O)
i. If there is any formula to be defined, using the formula editor user
can define the formula for the selected class and assessment type.
2. Element of class (D)
a. Based on the class value and type of assessment, the element of class will be
displayed.
3. Data Entry/Modification (D)
a. Based on the class value and type of assessment, the element of class will be
displayed.
4. Element Answers (D)
a. Based on the class value and type of assessment, the element of class will be
displayed.
Report
None
Pre-requisites
1. For the COF value setup user should have ADMIN responsibility.
2. The Assessment Type is defined for the class name.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Risk Ranking Setup
assign to data form Icon.
Click on
Column Description
1. select a class
a. class Name (M)
i. select the class from the drop down
2. List of Assessment name
a. Assessment Name (D)
i. The system display the assessment Name
b. Description (D)
i. The system displays the description of the assessment.
c. Updated Date (D)
i. The system display the date, when the ADMIN user change or create
a new record in this window
d. Updated User (D)
i. The system displays the User Id of the ADIM when user change or
create a new record in this window.
3. Data From Entry/Modification
a. Data form Name (M)
i. Select the data form from the drop down
b. Updated Date (D)
c. The system display the date, when the ADMIN user change or create a new
record in this window
d. Updated User (D)
e. The system displays the User Id of the ADIM when user change or create a
new record in this window
Report
None
Pre-requisites
1. For the POF value setup user should have ADMIN responsibility.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Values Icon.
Click on POF
Column Description
1. POF Values
a. ID (D)
i. The system displays the Id of the POF value
b. POF (D)
i. The system displays the POF value description
c. POF VALUE (D)
Report
None
14.2.2 POF HEADS
This window is basically to define the kinds of the POFs that be measured in the system. It
again has two sections. This window has two sections 1. POF Heads 2. Data Entry/
Modification
1.POF HEADS:- The system display all the previous POF heads defined in the GALIOM
Application.
2.Data Entry / Modification:- This section display the details of the selected record in the
POF Head section.
Pre-requisites
1. For the POF value setup user should have ADMIN responsibility.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Heads Icon.
Click on POF
Column Description
1. POF Heads
a. COF Head(D)
i. The system displays all the previous defined POF heads.
b. Description (D)
i. The system displays the descriptions of the POF heads against each
POF Head value.
c. Updated Date (D)
Report
None
14.2.3 HEAD ELEMENTS
This window is used to define the elements for the selected Head and to define the element
answers for the selected head. This window is having four sections 1. Select a head, 2.
Elements of Head, 3. Data Entry/Modification, 4.Element Answers.
1. Select a head :- This section provide a drop down to select the POF heads.
2. Elements of head :- This section display all the elements defined for the selected head
value in the select head section.
3.Data Entry/Modification:- This section display the details of the element selected in the
Elements of head section.
4.Element answers:- This section display all the Answers with respective POF value setup
against each element of head.
Pre-requisites
1. For the POF value setup user should have ADMIN responsibility.
2. The POF heads to be defined.
3. If there is any formula to define for the respective POF elements, the arrtibutes using
in the formula should be defined and have the proper value.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Risk Ranking Setup
Elements Icon.
Click on POF
Column Description
1. Select a head
a. Head name (M)
i. Select the Head name from the drop down.
1. The system displays all the Head values, which are defined in
the POF heads section.
2. Element of Head
a. Seq (D)
Report
None
14.2.4 ASSIGN TO CLASS
This window is used to assign the assessment type for each class. This window is having four
sections 1. select a class, 2.Element of class, 3. Data Entry/Modification, 4. Element
Answers.
1. Select a class :- This section provide a drop down to select the class.
2. Elements of class :- This section display all the elements defined for the selected class
and selected assessment type.
3.Data Entry/Modification:- This section display the details of the element selected in the
Elements of class section.
4.Element answers:- This section display all the
Pre-requisites
1. For the POF value setup user should have ADMIN responsibility.
2. The POF elements to be defined.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Risk Ranking Setup
Assign to class Icon.
Click on
Column Description
1. Select a class
a. Class name (M)
i. Select the class name from the drop down
b. Assessment Type (M)
i. Select the Assessment type from the drop down for the selected class.
c. Formula (O)
i. If there is any formula to be defined, using the formula editor user
can define the formula for the selected class and assessment type.
2. Element of class (D)
a. Based on the class value and type of assessment, the element of class will be
displayed.
3. Data Entry/Modification (D)
a. Based on the class value and type of assessment, the element of class will be
displayed.
4. Element Answers (D)
a. Based on the class value and type of assessment, the element of class will be
displayed.
Report
None
Pre-requisites
1. For the POF value setup user should have ADMIN responsibility.
2. The Assessment Type is defined for the class name.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Risk Ranking Setup
assign to data form Icon.
Click on
Column Description
1. Select a class
a. class Name (M)
i. select the class from the drop down
2. List of Assessment name
a. Assessment Name (D)
i. The system display the assessment Name
b. Description (D)
i. The system displays the description of the assessment.
c. Updated Date (D)
i. The system display the date, when the ADMIN user change or create
a new record in this window
d. Updated User (D)
i. The system displays the User Id of the ADIM when user change or
create a new record in this window.
3. Data From Entry/Modification
a. Data form Name (M)
i. Select the data form from the drop down
b. Updated Date (D)
i. The system display the date, when the ADMIN user change or create
a new record in this window
c. Updated User (D)
i. The system displays the User Id of the ADIM when user change or
create a new record in this window
Report
None
Pre-requisites
1. The COF setup and POF setup configured.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Column Description
1. select a class and Assessment type
a. class Name (M)
i. select the class from the drop down
b. Assessment type (M)
i. Select the Assessment type from the drop down
The POF values appearing column wise and the COF values Row
wise. The values in this colum appears automatically user needs to set
values in other column in the record.
b. color (O)
i. Color to be displayed for the chosen button.
4. Value (O)
a. The value defines in the each cube. (for example 2 in the above figure)
5. Formula for Buttons (O)
a. As the signifying using this option user can define the formula for the button
using the formula editor.
6. Updated Date (D)
a. The system display the date, when the ADMIN user change or create a new
record in this window
7. Updated User (D)
a. The system displays the User Id of the ADIM when user change or create a
new record in this window.
Report
None
Pre-requisites
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Column Description
1. Select COF
a. COF (M)
i. Select the COF from the drop down
2. Confidence Rating
a. Confidence Criteria (M)
i. Displays a dropdown of the reference values as defined in the Define
reference values in Administration Module for Reference type
CONRAT.
b. Confidence Factor (M)
i. Numeric value given by the Admin user as a measurement of the
Confidence on the Asset based on the Confidence criteria. The value
should be 1 or less then 1but not less than 0.
c. Updated Date (D)
i. GALIOM system date as on which the Confidence criteria record is
saved. Data appears automatically when
user presses the Save
menu option.
d. Updated User (D)
i. GALIOM user Id for the information as to who entered the
Confidence criteria record. The data here gets loaded automatically
once user uses the Save menu option.
Report
None
Pre-requisites
1. ******.
2. *******
Pre-requisites
1. *******.
2. ******.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Insert button.
Press
Column Description
1. Checklist Header
a. Checklist ID(D)
i. The system display the check list Id, when user save the
new checklist..
b. Checklist Name (M)
i. Enter the checklist name
c. Inspection Type (M)
i. Select the inspection type from the drop down.
d. Description (O)
i. Enter the description for the new checklist.
.
e. Updated Date (D)
i. The system display the date, when the ADMIN user
change or create a new record in this window.
f. Updated User (D)
i. The system displays the User Id of the ADIM when user
change or create a new record in this window.
2. Checklist Details
a. Seq (D)
i. The system displays the sequence number.
b. Section (O)
i. Enter the section
c. Subsection (O)
i. Enter the subsection
d. Inspection Description (D)
i. Enter the Inspection description
e. Updated Date (D)
i. The system display the date, when the ADMIN user
change or create a new record in this window.
f. Updated User (D)
i. The system displays the User Id of the ADIM when user
change or create a new record in this window.
Report
None
2. Delete button:- It deletes the selected record from the List of the checklist getting
displayed.
3. Exit button:- The system exit from the GALIOM application.
4. Double click:- Select the record and double click on it. The system display the
details of the selected record in the new window.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
Navigation
Main Menu
Column Description
1. ID (D)
a. The system displays the ID of the checklist.
2. Checklist Name (D)
a. The system displays all the checklist names.
3. Inspection Type (D)
a. The system displays all the type of inspection against each checklist.
4. Description (D)
a. The system displays the description of the checklist.
5. Updated Date (D)
a. The system display the date, when the ADMIN user change or create a new
record in this window.
6. Updated User (D)
a. The system displays the User Id of the ADIM when user change or create a
new record in this window.
Report
None
Pre-requisites
1. *******.
2. ******.
Responsibilities
1. The user needs to have the ADMIN responsibility to edit data in the window
Navigation
Main Menu
setup
.
Column Description
1. Inspection memo Recommendation Listing section
Report
None
Pre-requisites
1. The data form should exist.
2. The data form should be in specific format.
Responsibilities
1. The user needs to have the ADMIN responsibility to edit data in the window
Navigation
Main Menu
item.
Column Description
1. Select Data Form (M)
a. Select the data form from the drop down into which the data is to be loaded.
2. Select File (M)
a. With the help of select file window, select the source file in the system.
Report
None.
16 INTERFACE MANAGEMENT
16.1 INTERFACE SETUP
This window is used to give the information about the interface programmers running with
this Galiom Application (If any). Using this ADMIN will know the schedules to run by the
interface so as to provide the information to the GALIOM Application.
Pre-requisites
1. The Interface should be available and the interface is running successfully.
2. The Interface should have feature to handshake with Galiom Application. Or it is
capable of providing the information to the Galiom Application.
Responsibilities
1. The user needs to have the ADMIN responsibility to edit data in the window
Navigation
Interface Management
Column Description
1. Interface setup List section
a. ID (D)
i. The system display the Id
b. Name (D)
i. The system displays the Interface name
c. Description (D)
i. The system displays the description for the Interface.
d. Category (D)
i. The system displays the Category Name of the interface.
e. Schedule Type (D)
i. The system displays the Schedule for the interface to run.
f. Start Date Time (D)
i. The system displays the schedule start date & Time
g. Updated Date (D)
i. The system displays the Updated Date.
h. Updated User (D)
i. The system displays the Updated User.
2. Interface setup Entry section
a. SeqNo (D)
i. The system displays the seq no.
b. Name (M)
i. Enter the name of the Interface.
c. Description (O)
Report
None.
Pre-requisites
1. The interface should run at least once.
Responsibilities
1. The user needs to have the ADMIN responsibility to edit data in the window
Navigation
Main Menu
Interface Management
Column Description
1. Interface Logs
a. Interface type (D)
i. The system displays the Interface type
b. Sync Date (D)
i. The system displays the date of schedule run
c. Sync Status (D)
i. The system displays the status of the schedule job (i.e., Completed/In
progress/not completed).
2. Interface Logs Details
a. Seq No (D)
i. The system displays the seq no
b. Description (O)
i. The system displays the description of all the messages
c. Message Type (O)
i. The system displays the Message type.
Report
None.
17.1 PM CONCEPT
A concept or maintenance philosophy is always required for every equipment type. The
preventative maintenance activities performed in a pump may not be same as activities
performed in air receivers and filters. Hence the preventative maintenance concept has to be
build for every type of equipments. This assists the planner to know what kind of equipment
need what sort of PM activities due to what failure mechanism and their maintenance
frequencies.
Pre-requisites
1. The user should be active GALIOM Application user.
2. At least one asset is registered in the asset hierarchy tree.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW responsibility can view this window.
Navigation
Main Menu
Preventative Maintenance
Column Description
Report
None
17.2 PM PROGRAMME
Preventative Maintenance Programme helps the planner to organize the planning for
inspection programs designed to run over years. The same preventative measures which are
periodically done are automatically scheduled by the system. When one cycle is complete the
next cycle PM schedule will be planned automatically as soon as the PM schedule status is
changed to complete. In this screen the programme type is the inspection types like
ONSTREAM, SHUTDOWN, and VISUAL etc. The following steps would help in
planning/changing the preventative maintenance program.
Note :- Preventative maintenance is planned mainly in maintenance management system
outside GALIOM and is downloaded into GALIOM for the knowledge and action by the
inspection group.
Pre-requisites
1.
2.
3.
4.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
PM Programme.
Select the
Column Description
1. PM Programme
a. Programme type (D)
i. The system displays all the previously defined program type.
1. System would list all previously defined programs with their
programme type.
b. Freq (D)
i. The system displays all the previously defined freq against respective
programme type
c. UOM (D)
i. The system displays all the previously defined UOM against
respective programme type
d. Start Date (D)
i. The system displays all the previously defined programme start date
against respective programme type.
e. End Date (D)
The system displays all the previously defined programme End date
against respective programme type.
f. Updated Date (D)
i. The system should display the updated date, when ever user modifies
the data.
g. Updated User (D)
i. The system displays the user id, when the user is modify the value in
this window.
2. PM Programme Detail
a. Programme type (M)
i. Select the Programme type (Inspection Type) that needs to be
scheduled for a period of time in a defined frequency.
b. Programme Freq.(M)
i. Enter the frequency with unit of measurement (daily/monthly/yearly)
for the programme
c. Freq.UOM (O)
i. Select the appropriate frequency UOM, based on the selected
frequency.
d. Active (M)
i. If the programme is active, check the check box
1. By default is No. i.e., unchecked.
e. Start date (M)
i. Enter the start date of the programme. This tells the system when the
actual work would start and which year.
f. End Date (M)
i. Enter the stop date of the programme. This tells the system when the
actual work would stop and which year.
g. Programme Description (O)
i. Enter the programme description
h. Updated Date (D)
i. The system should display the updated date, when ever user modifies
the data.
a. Updated User (D)
i. The system displays the user id, when the user is modify the value in
this window.
3. Programme Chart
a. The chart will be displayed by the system.
REPORT
None.
17.3 PM SCHEDULE
GALIOM allows creating PM schedule for tags and facilities either based on PM programme
or it is manually entered for scheduling. PM schedule can either be downloaded thru
interface from maintenance management systems or can be scheduled manually. The
following steps explain how to schedule the preventative maintenance activity.
Note:- When the task is completed the PM schedule status could be changed to
COMPLETED.
Pre-requisites
1. The user should be active GALIOM Application user
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
PM Schedule.
Asset Management
Select the
Column Description
1. PM Schedule
a. Schedule type (D)
i. The system displays the schedule type like RBI, ADHOC, BLI, CVI,
ONSTREAM etc.
Page 310 of 395
REPORT
None.
Pre-requisites
1. The user should be active GALIOM Application user
2. At least one asset is registered in the asset hierarchy tree.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
menu Item.
Preventative Maintenance
Column Description
1. List of Activity
a. Activity code (D)
i. The system displays the activity code.
b. Activity Name (D)
i. The system displays the activity name
c. Description (D)
i. The system displays the Description of the Activity code
d. Activity Type (D)
i. The system displays the Activity type.
e. Active (D)
i. The system display the active value (A/I)
f. Updated date (D)
i. The system should display the updated date, when ever user modifies
the data
g. Updated user (D)
i. The system should display the updated user, when ever user modifies
the data in this window.
2. Activity Detail
a. Activity code (M)
i. Enter the activity code
1. If the user try to save the record, without entering any value
in this column, the system display the following message
Activity code is mandatory
b. Activity Name (M)
i. Enter the activity name
REPORT
None.
Pre-requisites
1. The user should be active GALIOM Application user
2. At least one asset is registered in the asset hierarchy tree.
Responsibilities
Navigation
Main Menu
Preventative Maintenance
Mechanism menu Item.
Column Description
1. List of Failure Mechanism
a. Failure Mechanism (D)
i. The system displays the failure mechanisms
b. Description (D)
i. The system displays the description of the failure mechanisms
c. Updated date (D)
i. The system should display the updated date, when ever user modifies
the data.
d. Updated user (D)
i. The system should display the updated user, when ever user modifies
the data in this window.
2. PM Activities
a. Activity code (M)
i. Select the Activity code from the drop down list
1. if the user does not select any value and try to save this
record, the system displays the following message Activity
code is mandatory
b. Maint.Freq (O)
i. Select the maint.Frq from the drop down list.
c. Freq UOM (O)
j.
REPORT
None.
18 MONITORED DATA
INTRODUCTION
This module will be used to record, manage, analyze the Inspections done on the
equipments/tags in the organization. Different Inspection methods have been incorporated
into the system and user would be able to record their Inspections via different modes.
Based on these records Reports can be generated which can be further used for analysis,
forecasting and scheduling of activities.
The Different Inspection Methods that can be recorded into the system as under:
1) Ultrasonic Wall Thickness
2) Radiography
3) Teletest (Long Range UT)
4) Corrosion Coupon
5) Corrosion Probe
6) MPI
7) LPI
8) Dimension Check
9) Oxide scale thickness measurement
10) Intelligent Pigging
11) Free Span Measurement
12) Cathodic protection.
The Different reports that can be generated for the recorded data are as under
1) Audit Report for Ultra Wall Thickness
2) Audit for Ultra Wall Thickness for MAWT defined
3) Cathodic protection Measurement
4) MPI Measurement
Figure11. Depicting the Asset hierarchy according to which data gets displayed in the
Monitoring tab on the right.
The list will have the columns of
1. Tag
2. Feature.
3. Testpoint
4. Inspection Date
5. Report Number
6. Other related columns for the inspection Method
These columns will precisely give an idea of the Testpoint location and level in the
Hierarchy as well as give the precise dates as on which the measurement were done.
Apart from some details of the inspection.
The details of the Record can be reviewed by selecting the record in the list and the
Details section below will reflect all the concerned details. This is shown below in the
elliptical area.
Pre-requisites
1. The Monitor Data Tab as a whole will appear only once the user is at the Tag or
Feature or Testpoint level of the Asset Hierarchy tree. In the other levels in the Asset
management window the monitoring data tab will not appear and in the window
Single Entry All Inspection methods, nothing appears or it appears blank.
2. The different Inspection Method tabs within the Monitor data tab will appears only
when.
a. For the Monitoring type there is atleast one or more than one test points
defined of the Tag or the Feature. And if user is directly at the testpoint level
then the corresponding tab will appear only if the Monitoring type of the
Testpoint is matching with the Monitoring Tab name.
b. If the testpoints of the Monitoring Type have a approval flag of A ie
Approved.
c. If the link status of the testpoint and the immediate predecessor of the
testpoint in the asset tree under consideration is not D or deleted.
d. If the class values of the Monitoring Type is defined in the window Define
Class values for the class type MONTYP.
e. Only if the Reference code for the desired Monitoring type, is also registered
in the References masters window of Administrative module for the
reference type as LNKIMN. ie for every MONTYP defined in the Class
values have to have a related record in the Reference master table of
sys_reference_t. for example the class value of UTWT has the reference code
of UTWT record in the reference table ( technically ar_class_t record is
linked to the record in sys_reference_t).
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
Navigation
Mainmenu Asset Management Asset Management
Column Description
Note:- based on the Inspection type the columns differ.
Report
None.
Pre-requisites
1. The Monitor Data Tab as a whole will appear only once the user is at the Tag or
Feature or Testpoint level of the Asset Hierarchy tree. In the other levels in the Asset
management window the monitoring data tab will not appear and in the window
Single Entry All Inspection methods, nothing appears or it appears blank.
Responsibilities
1.
2.
3.
4.
5.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Monitoring data tab.
Click on Ultra Wall Thickness tab
Select the
Column Description
1. Feature (M)
a. This column represents the feature name of the testoint under observation
This column represents the feature name of the testoint under observation.
b. Validation check on the column Please select Feature First message is
displayed if the column is left blank on saving.
2. Testpoint(M)
a. The column represents the Testpoint name of the testpoint under
observation.
b. Validation check on the column Please select Testpoint message is
displayed if the column is left blank on saving.
3. Insp . Date (M)
a. This column represents the Inspection date for the record.
b. Validation check on the column if tried to save without proper data , the
system gives the message Inspection date is Mandatory .
4. Report No (M)
a. The column represents the Report Name for the Inspection under
observation.
b. Validation check on the column if tried to save without proper data , the
system gives the message Report Number is Mandatory.
5. Nom.WT (D)
a. This column represents the Nominal wall thickness as defined for the feature
corresponding to the testpoint and gets automatically loaded when the
inspection record is saved.
Pre-requisites
1. The Monitor Data Tab as a whole will appear only once the user is at the Tag or
Feature or Testpoint level of the Asset Hierarchy tree. In the other levels in the Asset
management window the monitoring data tab will not appear and in the window
Single Entry All Inspection methods, nothing appears or it appears blank.
2. The different Inspection Method tabs within the Monitor data tab will appears only
when.
a. For the Monitoring type there is atleast one or more than one test points
defined of the Tag or the Feature. And if user is directly at the testpoint level
then the corresponding tab will appear only if the Monitoring type of the
Testpoint is matching with the Monitoring Tab name.
b. If the testpoints of the Monitoring Type have a approval flag of A ie
Approved.
c. If the link status of the testpoint and the immediate predecessor of the
testpoint in the asset tree under consideration is not D or deleted.
d. If the class values of the Monitoring Type is defined in the window Define
Class values for the class type MONTYP.
e. Only if the Reference code for the desired Monitoring type, is also registered
in the References masters window of Administrative module for the
reference type as LNKIMN. ie for every MONTYP defined in the Class
values have to have a related record in the Reference master table of
sys_reference_t. for example the class value of UTWT has the reference code
of UTWT record in the reference table ( technically ar_class_t record is
linked to the record in sys_reference_t).
Responsibilities
1.
2.
3.
4.
5.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Monitoring data tab.
Click on Radiography Data tab
Select the
Column Description
1. Feature (M)
Page 328 of 395
Pre-requisites
1. The Monitor Data Tab as a whole will appear only once the user is at the Tag or
Feature or Testpoint level of the Asset Hierarchy tree. In the other levels in the Asset
management window the monitoring data tab will not appear and in the window
Single Entry All Inspection methods, nothing appears or it appears blank.
2. The different Inspection Method tabs within the Monitor data tab will appears only
when.
a. For the Monitoring type there is atleast one or more than one test points
defined of the Tag or the Feature. And if user is directly at the testpoint level
then the corresponding tab will appear only if the Monitoring type of the
Testpoint is matching with the Monitoring Tab name.
b. If the testpoints of the Monitoring Type have a approval flag of A ie
Approved.
c. If the link status of the testpoint and the immediate predecessor of the
testpoint in the asset tree under consideration is not D or deleted.
d. If the class values of the Monitoring Type is defined in the window Define
Class values for the class type MONTYP.
e. Only if the Reference code for the desired Monitoring type, is also registered
in the References masters window of Administrative module for the
reference type as LNKIMN. ie for every MONTYP defined in the Class
values have to have a related record in the Reference master table of
sys_reference_t. for example the class value of UTWT has the reference code
of UTWT record in the reference table ( technically ar_class_t record is
linked to the record in sys_reference_t).
3. When there is at least one or more then one UTWT readings has been registered into
the system.
Responsibilities
1.
2.
3.
4.
5.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Monitoring data tab.
Click on Teletest tab
Select the
Column Description
1. Feature (M)
a. This column represents the feature name of the testoint under observation.
b. Validation check on the column Please select Feature First message is
displayed if the column is left blank on saving.
2. Testpoint(M)
a. The column represents the Testpoint name of the testpoint under
observation.
b. Validation check on the column Please select Testpoint message is
displayed if the column is left blank on saving.
Pre-requisites
1. The Monitor Data Tab as a whole will appear only once the user is at the Tag or
Feature or Testpoint level of the Asset Hierarchy tree. In the other levels in the Asset
management window the monitoring data tab will not appear and in the window
Single Entry All Inspection methods, nothing appears or it appears blank.
2. The different Inspection Method tabs within the Monitor data tab will appears only
when.
a. For the Monitoring type there is atleast one or more than one test points
defined of the Tag or the Feature. And if user is directly at the testpoint level
then the corresponding tab will appear only if the Monitoring type of the
Testpoint is matching with the Monitoring Tab name.
Responsibilities
1.
2.
3.
4.
5.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Monitoring data tab.
Click on corrosion coupon tab
Select the
Column Description
1. Feature (M)
a. This column represents the feature name of the testoint under observation.
b. Validation check on the column Please select Feature First message is
displayed if the column is left blank on saving.
2. Testpoint(M)
a. The column represents the Testpoint name of the testpoint under
observation.
b. Validation check on the column Please select Testpoint message is
displayed if the column is left blank on saving.
3. Insp . Date (M)
a. This column represents the Inspection date for the record.
b. Validation check on the column if tried to save without proper data , the
system gives the message Inspection date is Mandatory.
4. Report No (M)
a. The column represents the Report Name for the Inspection under
observation.
b. Validation check on the column if tried to save without proper data , the
system gives the message Report Number is Mandatory.
5. Serial No (O)
a. Inspection specific textual data.
6. Date Install (O)
a. Inspection specific date.
b. Validation check on the column if user attempts to enter a non date specific
data then the system will prompt the message Please Enter Valid date.
7. Date Retrieve (O)
Pre-requisites
1. The Monitor Data Tab as a whole will appear only once the user is at the Tag or
Feature or Testpoint level of the Asset Hierarchy tree. In the other levels in the Asset
management window the monitoring data tab will not appear and in the window
Single Entry All Inspection methods, nothing appears or it appears blank.
2. The different Inspection Method tabs within the Monitor data tab will appears only
when.
a. For the Monitoring type there is atleast one or more than one test points
defined of the Tag or the Feature. And if user is directly at the testpoint level
then the corresponding tab will appear only if the Monitoring type of the
Testpoint is matching with the Monitoring Tab name.
b. If the testpoints of the Monitoring Type have a approval flag of A ie
Approved.
c. If the link status of the testpoint and the immediate predecessor of the
testpoint in the asset tree under consideration is not D or deleted.
d. If the class values of the Monitoring Type is defined in the window Define
Class values for the class type MONTYP.
e. Only if the Reference code for the desired Monitoring type, is also registered
in the References masters window of Administrative module for the
reference type as LNKIMN. ie for every MONTYP defined in the Class
values have to have a related record in the Reference master table of
sys_reference_t. for example the class value of UTWT has the reference code
of UTWT record in the reference table ( technically ar_class_t record is
linked to the record in sys_reference_t).
3. When there is at least one or more then one UTWT readings has been registered into
the system.
Responsibilities
1.
2.
3.
4.
5.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Monitoring data tab.
Click on corrosion Probe tab
Select the
Column Description
1. Feature (M)
a. This column represents the feature name of the testpoint under observation.
b. Validation check on the column Please select Feature First message is
displayed if the column is left blank on saving.
2. Testpoint(M)
Pre-requisites
1. The Monitor Data Tab as a whole will appear only once the user is at the Tag or
Feature or Testpoint level of the Asset Hierarchy tree. In the other levels in the Asset
management window the monitoring data tab will not appear and in the window
Single Entry All Inspection methods, nothing appears or it appears blank.
2. The different Inspection Method tabs within the Monitor data tab will appears only
when.
a. For the Monitoring type there is atleast one or more than one test points
defined of the Tag or the Feature. And if user is directly at the testpoint level
then the corresponding tab will appear only if the Monitoring type of the
Testpoint is matching with the Monitoring Tab name.
b. If the testpoints of the Monitoring Type have a approval flag of A ie
Approved.
Responsibilities
1.
2.
3.
4.
5.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Monitoring data tab.
Click on Magnetic particle inspection tab
Select the
Column Description
1. Feature (M)
a. This column represents the feature name of the testoint under observation.
b. Validation check on the column Please select Feature First message is
displayed if the column is left blank on saving.
2. Testpoint(M)
a. The column represents the Testpoint name of the testpoint under
observation.
b. Validation check on the column Please select Testpoint message is
displayed if the column is left blank on saving.
3. Insp . Date (M)
a. This column represents the Inspection date for the record.
c. Validation check on the column if tried to save without proper data , the
system gives the message Inspection date is Mandatory .
4. Report No (M)
a. The column represents the Report Name for the Inspection under
observation.
b. Validation check on the column if tried to save without proper data , the
system gives the message Report Number is Mandatory.
5. Location (O)
a. Inspection specific textual data.
6. Parts name (O)
a. Inspection specific textual data.
7. Drawing Number (O)
a. Inspection specific text data specifying the drawing number enclosed.
8. Procedure Reference(O)
a. Inspection specific text data specifying the procedure followed for
measurement.
9. Surface condition (O)
a. Dropdown list for the specifying the surface condition during Inspection.
10. Dry or Wet method used (O)
a. List options for the method used for Inspection.
11. HW AC DC Yoke (O)
a. Dropdown list for the specifying conditions during Inspection.
12. Magnetization Type (O)
a. Inspection specific comments on the inspection done.
13. Prod Spacing and magnetization (O)
a. Inspection specific comments on the inspection done.
14. Demagnetized (O)
a. Check box to specify if Demagnetized or not . In case Demagnetized please
check the check box.
15. Examination result (O)
a. Inspection specific comments on the inspection done.
16. Imprint location and relevant indicators (O)
a. Inspection specific comments on the inspection done.
17. Cond.1 (O)
a. Condition code 1 for the inspection done.
18. Cond.2 (O)
a. Condition code 2 for the inspection done.
19. Cond.3 (O)
a. Condition code 3 for the inspection done.
20. Cond.4 (O)
a. Condition code 4 for the inspection done.
21. Accepted (O)
a. Check box to specify if the Inspection data has been accepted.
22. CT Noticed (O)
a. Check box to specify if CT Noticed.
23. Sketch Enclosed (O)
a. Check box to specify if the sketch is enclosed.
24. Updated Date (D)
Pre-requisites
1. The Monitor Data Tab as a whole will appear only once the user is at the Tag or
Feature or Testpoint level of the Asset Hierarchy tree. In the other levels in the Asset
management window the monitoring data tab will not appear and in the window
Single Entry All Inspection methods, nothing appears or it appears blank.
2. The different Inspection Method tabs within the Monitor data tab will appears only
when.
a. For the Monitoring type there is atleast one or more than one test points
defined of the Tag or the Feature. And if user is directly at the testpoint level
then the corresponding tab will appear only if the Monitoring type of the
Testpoint is matching with the Monitoring Tab name.
b. If the testpoints of the Monitoring Type have a approval flag of A ie
Approved.
c. If the link status of the testpoint and the immediate predecessor of the
testpoint in the asset tree under consideration is not D or deleted.
d. If the class values of the Monitoring Type is defined in the window Define
Class values for the class type MONTYP.
e. Only if the Reference code for the desired Monitoring type, is also registered
in the References masters window of Administrative module for the
reference type as LNKIMN. ie for every MONTYP defined in the Class
values have to have a related record in the Reference master table of
sys_reference_t. for example the class value of UTWT has the reference code
of UTWT record in the reference table ( technically ar_class_t record is
linked to the record in sys_reference_t).
3. When there is at least one or more then one UTWT readings has been registered into
the system.
3.
4.
5.
6.
system deletes the selected record. If the user selects the No button, the system will
not delete the selected record.
Save button: - The system save the record.
Refresh button:- Refresh the current display screen.
Print button:- The system display the print setup window, to select the printer by
the user to print the current display screen.
Exit button:- The system will exit from the GALIOM Application
Responsibilities
1.
2.
3.
4.
5.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Monitoring data tab.
Click on Liquid Penetration tab
Select the
Column Description
1. Feature (M)
a. This column represents the feature name of the testoint under observation.
b. Validation check on the column Please select Feature First message is
displayed if the column is left blank on saving.
2. Testpoint(M)
a. The column represents the Testpoint name of the testpoint under
observation.
Pre-requisites
1. The Monitor Data Tab as a whole will appear only once the user is at the Tag or
Feature or Testpoint level of the Asset Hierarchy tree. In the other levels in the Asset
management window the monitoring data tab will not appear and in the window
Single Entry All Inspection methods, nothing appears or it appears blank.
2. The different Inspection Method tabs within the Monitor data tab will appears only
when.
a. For the Monitoring type there is atleast one or more than one test points
defined of the Tag or the Feature. And if user is directly at the testpoint level
then the corresponding tab will appear only if the Monitoring type of the
Testpoint is matching with the Monitoring Tab name.
b. If the testpoints of the Monitoring Type have a approval flag of A ie
Approved.
c. If the link status of the testpoint and the immediate predecessor of the
testpoint in the asset tree under consideration is not D or deleted.
d. If the class values of the Monitoring Type is defined in the window Define
Class values for the class type MONTYP.
e. Only if the Reference code for the desired Monitoring type, is also registered
in the References masters window of Administrative module for the
reference type as LNKIMN. ie for every MONTYP defined in the Class
Responsibilities
1.
2.
3.
4.
5.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Monitoring data tab.
Click on Dimension Check tab
Select the
Column Description
Page 350 of 395
1. Feature (M)
a. This column represents the feature name of the testoint under observation.
b. Validation check on the column Please select Feature First message is
displayed if the column is left blank on saving.
2. Testpoint(M)
a. The column represents the Testpoint name of the testpoint under
observation.
b. Validation check on the column Please select Testpoint message is
displayed if the column is left blank on saving.
3. Insp . Date (M)
a. This column represents the Inspection date for the record.
b. Validation check on the column if tried to save without proper data , the
system gives the message Inspection date is Mandatory .
4. Report No (M)
a. The column represents the Report Name for the Inspection under
observation.
b. Validation check on the column if tried to save without proper data , the
system gives the message Report Number is Mandatory.
5. Diameter (M)
a. Inspection specific data.
b. Validation check on the column Data should be Numeric message will be
displayed if user tries to enter non numeric data in the column and Data
cannot be less than 0 if the number entered is less than 0. The field will only
allow user to enter up to 3 places of decimal only.
c. Validation check on the column if tried to save without proper data in the
column, the system gives the message Diameter Measurement is Mandatory.
6. Thickness (M)
a. Inspection specific data.
b. Validation check on the column Data should be Numeric message will be
displayed if user tries to enter non numeric data in the column and Data
cannot be less than 0 if the number entered is less than 0. The field will only
allow user to enter up to 3 places of decimal only.
c. Validation check on the column if tried to save without proper data in the
column, the system gives the message Thickness Measurement is
Mandatory.
7. Cond.1 (O)
a. Condition code 1 for the inspection done.
8. Cond.2 (O)
a. Condition code 2 for the inspection done.
9. Cond.3 (O)
a. Condition code 3 for the inspection done.
10. Cond.4 (O)
a. Condition code 4 for the inspection done.
Page 351 of 395
18.10 INSPECTION
OF
MEASUREMENT
OXIDE
SCALE
THICKNESS
This window will allow the user to register Oxide Scale Thickness Measurements data
records into the system. Once registered, they can be accessed anytime and anywhere,
wherever the GALIOM Application is available to the user.
Pre-requisites
1. The Monitor Data Tab as a whole will appear only once the user is at the Tag or
Feature or Testpoint level of the Asset Hierarchy tree. In the other levels in the Asset
management window the monitoring data tab will not appear and in the window
Single Entry All Inspection methods, nothing appears or it appears blank.
2. The different Inspection Method tabs within the Monitor data tab will appears only
when.
a. For the Monitoring type there is atleast one or more than one test points
defined of the Tag or the Feature. And if user is directly at the testpoint level
then the corresponding tab will appear only if the Monitoring type of the
Testpoint is matching with the Monitoring Tab name.
b. If the testpoints of the Monitoring Type have a approval flag of A ie
Approved.
c. If the link status of the testpoint and the immediate predecessor of the
testpoint in the asset tree under consideration is not D or deleted.
d. If the class values of the Monitoring Type is defined in the window Define
Class values for the class type MONTYP.
e. Only if the Reference code for the desired Monitoring type, is also registered
in the References masters window of Administrative module for the
reference type as LNKIMN. ie for every MONTYP defined in the Class
values have to have a related record in the Reference master table of
sys_reference_t. for example the class value of UTWT has the reference code
of UTWT record in the reference table ( technically ar_class_t record is
linked to the record in sys_reference_t).
3. When there is at least one or more then one UTWT readings has been registered into
the system.
Responsibilities
1.
2.
3.
4.
5.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Monitoring data tab.
Click on Oxide scale thickness measurement tab
Select the
Column Description
1. Feature (M)
a. This column represents the feature name of the testoint under observation.
b. Validation check on the column Please select Feature First message is
displayed if the column is left blank on saving.
2. Testpoint(M)
a. The column represents the Testpoint name of the testpoint under
observation.
b. Validation check on the column Please select Testpoint message is
displayed if the column is left blank on saving.
3. Insp . Date (M)
Pre-requisites
1. The Monitor Data Tab as a whole will appear only once the user is at the Tag or
Feature or Testpoint level of the Asset Hierarchy tree. In the other levels in the Asset
management window the monitoring data tab will not appear and in the window
Single Entry All Inspection methods, nothing appears or it appears blank.
2. The different Inspection Method tabs within the Monitor data tab will appears only
when.
a. For the Monitoring type there is atleast one or more than one test points
defined of the Tag or the Feature. And if user is directly at the testpoint level
then the corresponding tab will appear only if the Monitoring type of the
Testpoint is matching with the Monitoring Tab name.
b. If the testpoints of the Monitoring Type have a approval flag of A ie
Approved.
c. If the link status of the testpoint and the immediate predecessor of the
testpoint in the asset tree under consideration is not D or deleted.
d. If the class values of the Monitoring Type is defined in the window Define
Class values for the class type MONTYP.
e. Only if the Reference code for the desired Monitoring type, is also registered
in the References masters window of Administrative module for the
reference type as LNKIMN. ie for every MONTYP defined in the Class
values have to have a related record in the Reference master table of
sys_reference_t. for example the class value of UTWT has the reference code
of UTWT record in the reference table ( technically ar_class_t record is
linked to the record in sys_reference_t).
3. When there is at least one or more then one UTWT readings has been registered into
the system.
Responsibilities
1.
2.
3.
4.
5.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Monitoring data tab.
Click on Intelligent Pigging tab
Select the
Column Description
1. Feature (M)
a. This column represents the feature name of the testoint under observation.
b. Validation check on the column Please select Feature First message is
displayed if the column is left blank on saving.
2. Testpoint(M)
Page 356 of 395
Pre-requisites
1. The Monitor Data Tab as a whole will appear only once the user is at the Tag or
Feature or Testpoint level of the Asset Hierarchy tree. In the other levels in the Asset
management window the monitoring data tab will not appear and in the window
Single Entry All Inspection methods, nothing appears or it appears blank.
2. The different Inspection Method tabs within the Monitor data tab will appears only
when.
a. For the Monitoring type there is atleast one or more than one test points
defined of the Tag or the Feature. And if user is directly at the testpoint level
then the corresponding tab will appear only if the Monitoring type of the
Testpoint is matching with the Monitoring Tab name.
b. If the testpoints of the Monitoring Type have a approval flag of A ie
Approved.
c. If the link status of the testpoint and the immediate predecessor of the
testpoint in the asset tree under consideration is not D or deleted.
d. If the class values of the Monitoring Type is defined in the window Define
Class values for the class type MONTYP.
e. Only if the Reference code for the desired Monitoring type, is also registered
in the References masters window of Administrative module for the
reference type as LNKIMN. ie for every MONTYP defined in the Class
values have to have a related record in the Reference master table of
sys_reference_t. for example the class value of UTWT has the reference code
of UTWT record in the reference table ( technically ar_class_t record is
linked to the record in sys_reference_t).
3. When there is at least one or more then one UTWT readings has been registered into
the system.
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
Page 359 of 395
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Monitoring data tab.
Click on Free Span Measurement tab
Select the
Column Description
1. Feature (M)
a. This column represents the feature name of the testoint under observation.
b. Validation check on the column Please select Feature First message is
displayed if the column is left blank on saving.
2. Testpoint(M)
a. The column represents the Testpoint name of the testpoint under
observation.
b. Validation check on the column Please select Testpoint message is
displayed if the column is left blank on saving.
3. Insp . Date (M)
a. This column represents the Inspection date for the record.
c. Validation check on the column if tried to save without proper data , the
system gives the message Inspection date is Mandatory .
4. Report No (M)
a. The column represents the Report Name for the Inspection under
observation.
b. Validation check on the column if tried to save without proper data , the
system gives the message Report Number is Mandatory.
Page 360 of 395
Pre-requisites
1. The Monitor Data Tab as a whole will appear only once the user is at the Tag or
Feature or Testpoint level of the Asset Hierarchy tree. In the other levels in the Asset
management window the monitoring data tab will not appear and in the window
Single Entry All Inspection methods, nothing appears or it appears blank.
2. The different Inspection Method tabs within the Monitor data tab will appears only
when.
a. For the Monitoring type there is atleast one or more than one test points
defined of the Tag or the Feature. And if user is directly at the testpoint level
then the corresponding tab will appear only if the Monitoring type of the
Testpoint is matching with the Monitoring Tab name.
b. If the testpoints of the Monitoring Type have a approval flag of A ie
Approved.
c. If the link status of the testpoint and the immediate predecessor of the
testpoint in the asset tree under consideration is not D or deleted.
d. If the class values of the Monitoring Type is defined in the window Define
Class values for the class type MONTYP.
e. Only if the Reference code for the desired Monitoring type, is also registered
in the References masters window of Administrative module for the
reference type as LNKIMN. ie for every MONTYP defined in the Class
values have to have a related record in the Reference master table of
sys_reference_t. for example the class value of UTWT has the reference code
of UTWT record in the reference table ( technically ar_class_t record is
linked to the record in sys_reference_t).
Responsibilities
1.
2.
3.
4.
5.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Monitoring data tab.
Click on Cathodic Protection tab
Select the
Column Description
1. Feature (M)
1. The Left side or the encircled portion in the figure 23 will show the Feature and the
Testpoint . This is the fixed portion of the window and the horizontal scroll bar
given here need not be touched.
2. The Right side or the non-encircled portion of the window will show all the other
columns related to the measurement for registering the inspection into the system.
The Horizontal scroll will enable the user to do the same.
3. The window will have the Insert, Save, Delete, Print options enabled in tool bar.
4. User will be able to print preview the data in the landscape layout as it will reflect all
the data showing in the window.
Pre-requisites
1. The Tabs the the window will appear only once the user is at the Tag or Feature or
Testpoint level of the Asset Hierarchy tree. In the other levels in the Single Entry
All Inspection methods window nothing appears or it appears blank.
2. The different Inspection Method tabs within the Monitor data tab will appears only
when.
a. For the Monitoring type there is atleast one or more than one test points
defined of the Tag or the Feature. And if user is directly at the testpoint level
then the corresponding UTWT tab will appear only if the Monitoring type of
the Testpoint is UTWT. Thereby these tabs tabs dynamically based on the
testpoints monitoring type for the testpoints under the Tag or Feature.
b. If the testpoints of the Monitoring Type UTWT have a approval flag of A ie
Approved.
c. If the link status of the testpoint and the testpoint under consideration is not
D or deleted.
d. If the class values of the Monitoring Type is defined in the window Define
Class values.
e. Only the Reference code for the desired Monitoring type is also registered in
the references masters module for the reference type as LNKIMN. ie for
every MONTYP defined in the Class values have to have a related record in
the Reference master table of sys_reference_t. for example the class value of
UTWT has the reference code of UTWT record in the reference table (
technically ar_class_t record is linked to the record in sys_reference_t ).
3. When there is at least one or more then one UTWT readings has been registered into
the system.
2.
3.
4.
5.
6.
a. At the feature level Similar to above all the testpoints defined under the
feature and of the inspection Method UTWT will come up as different
records in the Multiple data entry window.
b. At the testpoint level only one record will appear in the screen Multiple
data entry window , since the user is already at the testpoint level.
Delete button:- The system delete the selected record in the Inspection tab. Before
deleting the record, the system display the following message Do you wish to delete
the selected record with Yes and No options. If the user selects the yes button, the
system deletes the selected record. If the user selects the No button, the system will
not delete the selected record.
Save button: - The system save the record.
Refresh button:- Refresh the current display screen.
Print button:- The system display the print setup window, to select the printer by
the user to print the current display screen.
Exit button:- The system will exit from the GALIOM Application
Responsibilities
1.
2.
3.
4.
5.
Navigation
Main Menu
Monitoring data
Column Description
Based on the Inspection tabs select.
REPORT
None.
18.14.1 HOW TO ATTACH THE DOCUMENTS IN THE INSPECTION
TABS
To attach the documents in the inspection tabs, follow the below steps. User can attach one
or more documents depending on the requirement. . Each record hence has one of the two
images discussed below attached to it
Figure :- Document attachment option in the Monitoring data window for UTWT.
volume
-
too.
The usage of the editor is simple, once user clicks on the image above the text editor opens
as the encircled portion in the figure below. User needs to enter the data in this editor and
then apply the changes . On Apply the text entered in the editor will automatically get loaded
in the column. Close button here will just close the Multi line editor without making any
changes to the data in the column.
Figure:- Depiction of the Multi line text editor available to various columns in Monitoring
data windows.
18.14.2 GRAPHICAL PRESENTATION TAB IN INSPECTION TABS
We Take the general example of the Ultra Wall Thickness Graphical presentation tab.
It is a line graph that shows you the Minimum Allowable Wall thickness variation over a
period of time for the Feature Testpoint.
Details of the Graph
Category will be the Feature-Testpoint combination
Value axis - is the data value of MAWT or the Minimum Allowable Wall Thickness.
The series will be according to the Year of measurement.
Responsibilities
1. Any user having ASSET EDIT Responsibility can edit this window.
2. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Workscope Prep tab.
Select the
Column Description
1. Work Scope List
a. ID (D)
i. The system display the ID
b. Workscope Date (D)
i. The system display the work scope date
c. Asset Name (D)
i. The system display the asset name
d. Schedule Type (D)
i. The system displays the Schedule Type.
e. Workscope Desc (D)
i. The system displays the work scope description
f. Updated Date (D)
i. The system should display the updated date, when ever user modifies
the data.
g. Updated User (D)
i. The system displays the user id, when the user is modify the value in
this window.
2. Workscope Details
a. Workscope ID (D)
i. The work scope id is displayed by the system automatically, when
user creates the record in the work scope preparation window
b. Workscope Date (D)
i. The system display the current date.
1. The system will not allow the user to edit this column.
c. Schedule (M)
i. Select the schedule from the drop down.
1. If the user try to save the record without entering any value in
this column, the system display the following message
Schedule is must.
2. The entire schedules displayed in the drop down are defined
in the PM schedule window.
d. Workscope Desc (O)
i. Enter the work scope description.
e. Updated Date (D)
i. The system should display the updated date, when ever user modifies
the data.
f. Updated User (D)
i. The system displays the user id, when the user is modify the value in
this window.
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. There should be a functional group is registered in the GALIOM Application.
Responsibilities
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Click Asset Management Report menu Item
Select Ultrasonic wall thickness measurement datasheet.
REPORT
File
Pre-requisites
1. The user should be active GALIOM Application user.
2. The user should have responsibility right to click on Asset Hierarchy tree.
3. There should be a functional group is registered in the GALIOM Application.
Responsibilities
Page 378 of 395
1. Any user having ASSET VIEW Responsibility can view this Report
Navigation
Main Menu
Asset Management
Select Radiography Datasheet.
REPORT
File
20 INSPECTION MEMO/REPORT
Inspection memo and report screen allows user to record the inspection findings. Inspection
memo and report of GALIOM mainly assist different kind of users to record the inspection
findings and recommendation and maintenance. After the inspection is completed, the
inspector would record its findings for different types of inspections. Some of the inspection
types are Close visual inspection (CVI), Baseline (BLI), On-stream, Shutdown etc. This
screen works with responsibility of different groups like inspectors, document linking,
reliability engineer, maintenance coordinator and operations. After inspector has filled the
inspection findings, the reliability engineer would check for level 1 screening for anomalies
and would record recommendation with due dates for its completion. All critical
recommendations are put in GALIOM with priority high and Fitness for Purpose (FFP)
status as RED. The RED FFP status means it required immediate repair or replacement.
ORANGE FFP status is put when the recommendation could be completed by specified due
dates. This screen is supported with many reports which makes the reporting and highlight
the action list very effectively.
Pre-requisites
1. The user should be active GALIOM Application user
2. At least one tag is registered in the asset hierarchy tree.
3. Select any TAG from the asset hierarchy.
SELECTED TAG
This window is used to add the inspection memo for the selected tag. This window is having
7 tabs. 1. Inspection comment, 2.Failure Mechanism, 3. Memo Documents, 4. Screening
Level 1, 5. CM/PM Follow up, 6. Maintenance Comment and operation Comment.
Pre-requisites
1. The user should be active GALIOM Application user
2. At least one asset is registered in the asset hierarchy tree.
3. Select any TAG from the asset hierarchy.
Responsibilities
1. Any user having ASSET EDIT Responsibility can edit this window.
2. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Memo/Report Tab
Click the Insert button.
Select the
Column Description
1. Report No (D)
a. The system displays the report number.
i. The system automatically displays the Report number.
2. Inspection Type (O)
a. Select the Inspection Type from the drop down window.
3. Location Desc (O)
a. Enter the Location description where the inspection is done.
4. Condition Codes 1 to 4 (O)
a. Select the Condition codes from the dropdown.
5. Inspection Date (O)
a. Enter the Inspection date.
6. Drawing No(O)
a. Enter the Drawing Number.
7. PEFD No (O)
a. Enter the PEFD Number.
8. Memo Status (M)
a. Select the Memo status (i.e., CANCELLED. COMPLETED,
REINSPECTION, RESCHEDULE, REVIEWING) from the drop down.
9. Status Date (O)
a. The system displays the status Date.
10. Maintenance Req. (O)
a. Check the check box, if the Maintenance is required for the selected tag.
11. Contained (O)
a. Check the check box (Yes), if it is contained. Uncheck the check box (No), if
it is not contained.
i. If the contained check box is not selected the system will protect the
Contained Type and Repair code columns.
12. Contained Type (O)
a. Select the contained Type (i.e., Clam fitted, Permanent repair done, reduced
pressure, and temporary repair done) from the drop down.\
i. If the Contained column is unchecked, then the system will not allow
the user to edit this column.
13. Repair code (O)
a. Select the Repair code (i.e., Painting, Plidco clamp ) from the drop down.
i. If the Contained column is unchecked, then the system will not allow
the user to edit this column.
14. Update date (D)
Pre-requisites
1. The user should be active GALIOM Application user
2. At least one asset is registered in the asset hierarchy tree.
3. Inspection to be conducted on at least on feature.
Responsibilities
1.
2.
3.
4.
Navigation
Main Menu
Asset Management
Click Asset Management menu Item
Select
the Memo/Report Tab
Click the insert button or double click on any record present
in the Memo/Report tab
Click on the Memo documents tab.
Column Description
1. Select path (M)
a. Select the path for ht source file, by click the file browse icon.
Material (O)
i. Select the Material from the drop down.
1. The system displays the material data from define Material
specification window present in the Engineering Reference.
j.
Temperature (O)
i. The system display the temperature, based on the feature selected in
the feature column. The system also allows the user to edit this
column.
4. Un confirmed (O)
a. Enter the confirmend /un confirmed
5. Follow up text (O)
a. Enter the follow up text
6. Priority (O)
a. Select the priority from the drop down (i.e., HIGH, LOW, MEDIUM)
7. Follow up date (O)
a. Enter the Follow up date
8. Close out date (O)
a. Enter the close date
9. FFP Status (O)
a. Enter the FFP status
21.Maintenance Comment Tab
1. Follow up seq (D)
a. The system displays the Follow up number
2. Review Date (O)
a. Enter the review date
3. Comments (O)
a. Enter the comments
4. Work Request No (D)
a. The system displays the work request No
5. Work Order No (O)
a. The system displays the work order number.
6. Work Order Status (O)
a. The system displays the work order status
7. Work Order Priority (O)
a. The system displays the work order priority.
8. Work Order close date (O)
a. The system displays the work order close date
9. Actual Start date (O)
a. The system displays the work order actual start date.
10. Actual End Date (O)
a. The system displays the work order actual end date.
11. Updated Date (D)
a. The system should display the updated date, when ever user modifies
the data.
Page 386 of 395
Responsibilities
1. Any user having ADMIN Responsibility can edit this window.
2. Any user having ASSET EDIT Responsibility can edit this window.
3. Any user having ASSET VIEW Responsibility can view this window.
Navigation
Main Menu
Asset Management
Memo/Report Tab
Select the
Column Description
1. Report No (D)
a. The system display the Report No
2. Insp. Type(D)
a. The system displays the inspection Type.
3. CC1 (D)
a. The system display the Condition codes 1
4. CC2 (D)
a. The system display the Condition codes 2
5. CC3 (D)
a. The system display the Condition codes 3
6. CC4 (D)
a. The system display the Condition codes 4
7. Repair Code (D)
a. The system displays the repair code.
8. Contained (D)
a. The system display the contained (Y/N)
9. Updated Date (D)
a. The system should display the updated date, when ever user modifies the
data.
10. Update User (D)
a. The system displays the user id, when the user is modify the value in this
window.
Report
None
Pre-requisites
1. There should be at least one inspection should present.
2. The system show a list of previous inspection memos of the selected TAG.
Responsibilities
1. None.
Navigation
Main Menu
Asset Management
memo /Report tab
. Click on
Column Description
None.
REPORT
None
Select Test point at level 8 for which the wall thickness record will be entered.
Click on historical data tab.
System will show list of previous wall thickness for the point, if any.
Click on Insert tool button.
System will bring up a new empty record for wall thickness entry.
Enter the inspection date, wall thickness etc.
When all the entries are made click on Save tool button.
22 POWER BOILER
22.1 POWER BOILER TAG LEVEL MECHANICAL DESIGN DATA
*****
22.2 POWER BOILER FEATURE LEVEL MECHANICAL DESIGN
DATA PIPING *****
22.3 POWER BOILER FEATURE LEVEL MECHANICAL DESIGN
DATA TUBE ******
22.4 POWER BOILER FEATURE LEVEL MECHANICAL DESIGN
DATA-SHELL *******
22.5 POWER BOILER FEATURE LEVEL MECHANICAL DESIGN
DATA-HEAD ******
23 GENERAL UTILITIES
23.1 HOW THE FILTER OPTION WORKES
This is one the facility provided by the GALIOM application to the user. Using this feature,
the user can filter the data displayed on the current display screen based on the criteria
selected. When user press Options -> Filter, the system display a window with the filter
options. This menu option is enabled/disable based on the functional requirement of
GALIOM Application.
Pre-requisites
1. The filter menu option is enable for the displayed window.
2. The window should have data to apply the filter criteria.
Responsibilities
1. None.
Navigation
Options
Column Description
1. Field name (M)
a. Select the field name on which the filter criterion is constructing.
Pre-requisites
1. The sort menu option is enable for the displayed window.
2. The window should have data to apply the sort.
Responsibilities
1. None.
Navigation
Options
Column Description
1. Field name (D)
a. Select the column from left hand window and release in right hand window.
i. The system display all the fields present in the current display
window.
2. Ascending (M)
a. The system will sort the data in ascending.
b. By default the system always check the check box. (i.e., Ascending)
REPORT
None.
Pre-requisites
1. The change password menu option is enable.
2. The user must be active GALIOM application user.
3. The user must have valid user name and password.
Responsibilities
1. None.
Navigation
Column Description
1. Old password (M)
a. Enter the current password of the user
i. The system displays the data in non numeric characters.
2. New password (M)
a. Enter the new password.
i. The system displays the data in non numeric characters.
3. Verify Password (M)
a. Enter the new password again.
i. The system displays the data in non numeric characters.
REPORT
None.