TECHNICAL SUPPORT IMS Module

Step by Step
CONTENT
1 General Points ....................................................................................................................................... 4
1.1 Access ............................................................................................................................................ 4
1.2 General Features ........................................................................................................................... 5
1.3 Technical Query ............................................................................................................................ 5
1.4 Opening a TQ: TIER 1 Offshore, TIER 1 Onshore or TIER 2 user.................................................... 6
1.4.1 Reference .............................................................................................................................. 7
1.4.2 System ................................................................................................................................... 8
1.4.3 Query................................................................................................................................... 10
1.4.4 Risk Matrix .......................................................................................................................... 11
1.5 Submit a TQ: TIER 1 Offshore, TIER 1 Onshore or TIER 2 user .................................................... 11
1.6 Cancel a TQ ................................................................................................................................. 12
1.7 Answer a TQ forwarded for response: TIER 1 Onshore, TIER 2 or TIER 3 user ........................... 12
1.7.1 Answer a question .............................................................................................................. 12
1.7.2 Answer a question - Invite users from other disciplines (TQ Multidisciplinary) ................. 13
1.7.3 Create Repair Strategy ........................................................................................................ 14
1.8 Approve a response: Leader ....................................................................................................... 16
1.9 Validate Response received: TIER 1 Offshore, TIER 1 Onshore or TIER 2 user ........................... 16
1.10 Indicate if TQ has been successfully implemented or not (Repair Strategy) .............................. 18
1.11 Indicate if TQ is a candidate for lessons learned: TIER 3 ............................................................ 19
1 General Points
1.1 Access
To access the Technical Query IMS Module, follow the steps below:

▪ Access https://ims.modec.com/
▪ If it is your first login to the system, click "First Access / Request new password?". You will receive an
email to register your password.

▪ When entering the IMS, access: "TECHNICAL QUERIES".

4
▪ You can also access the TECHNICAL QUERIES IMS Module by selecting “TECHNICAL QUERIES” option
at the Header of IMS Home Page.

1.2 General Features

Technical Support is a custom web system to manage the Technical Queries(TQ) and Technical
Recommendation(TR) flow with a user-friendly experience to all employees opening, visualizing and
answering TQs and TRs . The system will be used in Modec’s onshore offices and offshore assets.

1.3 Technical Query

To access the TECHNICAL QUERY main screen, select the icon below:

5
The Technical Support Main Screen the will display the TQ/TR with user action pending (My Pending
Actions), TQ/TR open by user (My Queries) and all TQ/TR opened on vessels that the user is registered
(All Queries).

In the main screen the user can open TQ/TR. The opening of TQ is possible for TIER 1 Offshore, TIER 1
Onshore and TIER 2. The opening of TR is possible for TIER 2 and TIER 3.

1.4 Opening a TQ: TIER 1 Offshore, TIER 1 Onshore or TIER 2 user

Click in the “Open New TQ” icon, as shown below:

6
The New TQ “New Technical Query” registration screen will be opened.

A vessel to answer TQ must be selected.

1.4.1 Reference
When the user clicks on the "Reference" field, a combo box with the following options to choose
from wil be shown:

▪ WORK ORDER
▪ RDO
▪ TQ
▪ MOC
▪ NAM
▪ CAPA
▪ OTHER
An optional field of “Reference Number” will also be available.

When the user clicks on the “Base of Requirement” field a field with the following options to choose will
be shown:
▪ PROCESS SAFETY
▪ ENVIRONMENTAL IMPACT
▪ OPEX REDUCTION
▪ ASSET DAMAGE
▪ REGULATION / COMPLIANCE

7
 ▪ OPERATIONAL EFFICIENCY
▪ OTHER
▪ OCCUPATIONAL SAFETY
“Other Requirement” with also appear as an optional field:

1.4.2 System

When selecting the System section, the following options will appear:

▪ 00 - Production Wells
▪ 01 - Water Injection Wells
▪ 02 - Gas Lift / Injection Wells
▪ 03 - Risers / Flowlines
▪ 04 - Umbilicals
▪ 05 - Turret – Valves & Swivels
▪ 06 - Turret Mechanical Component
▪ 07 - Mooring System Component
▪ 08 - Installation Aids
▪ 10 - Inlet Oil Production
▪ 11 - Crude Oil Treating and Stabilization
▪ 12 - Flowline Circulation
▪ 13 - Condensate Handling
▪ 14 - Produced Water Treatment
▪ 15 - Seawater Treatment & Injection
▪ 16 - LNG & LPG Production
▪ 20 - Inlet Gas Production
▪ 21 - LP Gas Compression

8
▪ 22 - Gas Compression (MP)
▪ 23 - Gas Dehydration & Regeneration
▪ 24 - Gas Compression (MP,HP and Re-Injection)
▪ 25 - MEG and Regeneration
▪ 26 - MEG and Regeneration
▪ 27 - Gas Treating
▪ 28 - Acid Gas Injection
▪ 30 - Flare & Vent
▪ 31 - Fuel Gas System - General
▪ 32 - Refrigeration
▪ 33 - Chemical Injection
▪ 34 - Closed / Open Drains
▪ 35 - Heat Medium / Water-based
▪ 36 - Cooling Medium System
▪ 37 - Process Inert Gas (N2)
▪ 40 - Power Generation
▪ 41 - Fuel System - Marine
▪ 43 - Steam and Condensate System
▪ 44 - Fresh Water & Potable Water System
▪ 45 - Compressed (Utility & Instrument) Air System
▪ 46 - Lube Oil System.
▪ 47 - Bilge System
▪ 50 - Life Saving & Emergency Rescue
▪ 51 - Fire Water System
▪ 52 - Deluge System
▪ 53 - Foam System
▪ 54 - Gaseous Fire Fighting System
▪ 55 - Portable Fire Fighting Equipment
▪ 56 - Waste Disposal & Spill Control
▪ 60 - Power Distribution System
▪ 61 - Lighting System
▪ 62 - Facility Control System
▪ 63 - Communication System
▪ 64 - Navigation System
▪ 65 - EMP Data & Position Reference System
▪ 66 - Subsea Control System
▪ 67 - Metering System
▪ 70 - Cargo & Ballast & Slop System
▪ 71 - Cargo Offloading
▪ 72 - IGS & Vent System
▪ 73 - Tank Monitoring System

9
 ▪ 74 - Valve Remote Control System
▪ 75 - Hull Tanks and Structure
▪ 76 - Corrosion Protection
▪ 80 - Propulsion
▪ 81 - Living Quarters (LQ)
▪ 82 - HVAC
▪ 83 - LQ Sewage & Drain System
▪ 84 - Laboratory & Work Shop Spaces
▪ 85 - Material Handling System
▪ 86 - Deck Machinery & Anchoring
▪ 87 – Helideck

1.4.3 Query
When selecting the Query section, the following fields will appear:

▪ A text field “Title” for the TQ title with a 150-character limitation.

▪ “Discipline to Answer” with the disciplines registered in Technical Support. It's possible only
one discipline to choose;
▪ The “Text” field is for filling in the text of TQ.
▪ It is possible for the to attach files with the total limit of 30 MB in the "Add File" button.

10
 1.4.4 Risk Matrix
By selection the Risk Matrix Section, the user will view the following information:

The user can select the fields of "Consequence" and "Likelihood of Consequence". TQ will have the risk
rating “Low”, “Medium” or “High” according to the user's choice based on the Risk Matrix criteria.

Clicking on "Save" button the TQ saves as a draft and the user can modify as many times as he wants. TQ
status will be "Draft" and the user will receive a "Draft Saved" message;

Clicking on "Submit" button will show the message “Would you like to submit this Technical Query?"
with two buttons: "yes" or "no". If "no" will return to the Technical Support main screen, if “yes” then
the TQ will be submitted with the flow started. A message appears for the user “Submitted with
success".

1.5 Submit a TQ: TIER 1 Offshore, TIER 1 Onshore or TIER 2 user

When the user clicks "Submit" on the TQ creation screen, the system will check the author user's TIER to
forward to TIER directly above. And the "Discipline to answer" and "Vessel to Answer" fields that the
author user has selected for opening TQ to forward to the same directly superior TIER Discipline and
Vessel.

TQ status will be “Awaiting TIER X Analysis”. The system will route the TQ to the user who has the least
active TQs under their responsibility, so that the distribution is equal to the users who will respond.

If there is no a directly superior TIER user registered in the system on that vessel, the system directs TQ
to the next hierarchy TIER (TIER 1 Offshore, TIER 1 Onshore, TIER 2 and TIER 3).

If there is still no user registered to reply, the message “There is not a active user for the answer" will
appear to the TQ author user when the user clicks on "Submit" on the TQ open screen.

11
1.6 Cancel a TQ
If the user was the author of the TQ, it is possible to cancel it by selecting the “Cancel TQ” option and
filling a justification, as shown below:

1.7 Answer a TQ forwarded for response: TIER 1 Onshore, TIER 2 or TIER 3 user

1.7.1 Answer a question

By clicking on the answer button, a text box will be opened to fill in the answer. The user can attach files
up to 30MB total in the "Add File" button, indicate if TQ needs a MOC for implementation by checking
the flag "This TQ needs a MOC for implementation”, create a Repair Strategy or invite other users from
other disciplines to collaborate on a response by clicking on the flag “Turn this TQ Multidisciplinary”. It is
mandatory for the user to answer the question “Does this answer require an asset intervention for
implementation?

If yes, the user will have to fill out the repair strategy report (4.6.3 Scenario: Create Repair Strategy). If
not, write an answer without repair strategy. If the user tries to submit to TQ without answering this
question, the message "Answer the question about the need for asset intervention” appears;

Clicking on "Save" button the answer TQ saves as a draft and the user can modify as many times as he
wants. TQ status remains the same;

Clicking on "Submit" button will show the message “Would you like to submit this Technical Query?"
with two buttons: "yes" or "no". If "no" will return to the Technical Support main screen, if “yes” then
the TQ will be submitted with the continued flow. A message appears for the user “Submitted with
success" and TQ status will be “Awaiting TIER X Answer Validation”;

Clicking on "Back" the user returns the previous action options: Answer, Assign, Scale, More
Information, Cancel TQ (admin user) and Back (Return to main system screen).

12
 1.7.2 Answer a question - Invite users from other disciplines (TQ Multidisciplinary)
Given the user has clicked on the flag “Turn this TQ Multidisciplinary”. Then will open a "Select
Discipline" field with all active disciplines registered in the system and the "Name" field with all users
registered in Technical Support of the selected discipline. The user can invite up to 4 users of the same
TIER to collaborate with the answer through the icon . User can delete added user guest via icon

13
Filling in the "Discipline" and "Name" information of the invited users, the user responsible for the
answer clicks "Save" and the TQ will be directed to the invited users, who will have the TQ displayed in
the "My Pending Actions" section.

The guest user can attach files to their answer, indicate if TQ needs a MOC for implementation by
checking the flag "This TQ needs a MOC for implementation”, but cannot create Repair Strategy and the
flag " Turn this TQ Multidisciplinary " does not appear for them.

Clicking on "Save" the guest user saves a draft of their response. Clicking on "Submit" the guest user
submits their response to the replying user who invited him/her and TQ leaves its "My Pending Actions"
section.

Picture 1
The user responsible for the answer can submit the TQ at any time, even if the invited users have not
responded.

Clicking on "Submit" the user responsible for the answer submits the TQ for response validation. If the
system has a registered leader user, the answer will be for the TIER / discipline leader to approve (4.7 As
a leader user, I would like to approve a response).

If the system does not have a registered leader user, the flow will proceed without the approval of a
leader (4.8 As a TIER 1 Offshore, TIER 1 Onshore or TIER 2 user, I would like to validate the response
received).

1.7.3 Create Repair Strategy

Given the user answered "yes" to the question "Does this answer require an asset intervention for
implementation?". Then the "create repair strategy" button will appear. Open the form to fill in the
information (all text fields are required):

▪ WORK LOCATION
Describe the location where the work will be carried out, with TAGS or other Identification.

▪ RESOURCES REQUIREMENTS

- Material
Detail the projects and procedures required to perform the activity.

14
 - Manpower
List manpower needed, if special qualifications, vendor, etc.

▪ DETAILED WORKSCOPE
Detail work steps.

▪ DOCUMENTS (certifications, procedures, etc, IMS Documents)

Detail the projects and procedures required to perform the activity Detail the projects and procedures
required to perform the activity.

▪ Check List
10 validations for user choice (not required field).

In each text field the user can attach files up to 30 MB.

Picture 2
Clicking on "Save" the user saves the completed information in the form. The user can edit the form

before submitting to TQ by clicking on "Edit Repair Strategy" or delete it from the icon .

15
 Picture 3

1.8 Approve a response: Leader

Given that TQ was directed to user as the discipline leader / TIER of the user who answered TQ;

Then TQ will have the status “Awaiting TIER X Leader Answer Validation”

And the user will have the options:

▪ Agree: The leader user agrees with the response given. The leader user can post additional
comments
▪ Reject: Returns TQ for the responding user
▪ More Information: Request more information for the responding user
▪ Assign: Assigns another user (non-leader user) to validate the response. The user who assigns the
validation of the response has no further action on TQ, only the new user assigned. Assignment is
only possible for users of the same TQ discipline/Vessel and TIER as the user who assigned it
▪ Cancel TQ: Cancels QT flow (option for TQ authoring user only)
▪ Back: Return to main screen

1.9 Validate Response received: TIER 1 Offshore, TIER 1 Onshore or TIER 2 user

Given that the user has answered TQ's question. Then the response will be returned to the authoring
user of TQ for validation. In the case of scaled TQ, the response returns for each TIER involved in the TQ
to the TQ authoring user. Users of the TIERs involved can post additional comments or create Repair
Strategy to sum up the answer given.

16
The validation screen shows the options for the user:

▪ Agree: The user agrees with the response received. In case of scaled TQ, by accepting, the user
can post additional comments and create a Repair Strategy (TIER 1 ONSHORE or TIER 2). If the
user has saved additional comments in TQ and clicks the "Back" button, the message "Would you
like to return to the previous options and lose the draft of your answer?" appears.
▪ Clicking on "Back" the user returns the previous action options: Agree, Reject, More
Information, Assign, Cancel TQ (admin user) and Back (Return to main system screen).
▪ Clicking on "Agree" the author continues the flow and TQ's status is "Awaiting Implementation”
(4.8.1 Scenario: Implementation Feedback).
▪ For the TQ scenario scaled to TIER 2 or TIER 3, in the response validation feedback flow, the TIER
1 Onshore user may indicate that TQ will not be implemented. Thus, the flow ends and the user
TIER 1 Offshore is notified of the termination of the TQ.
▪ Reject: Returns TQ for the responding user
▪ More Information: Request more information with the choice of which TIER will respond to the
request for more information
▪ Assign: Assigns another user to validate the response. The user who assigns the validation of the
response has no further action on TQ, only the new user assigned. Assignment is only possible for
users of the same TQ discipline/Vessel and TIER as the user who assigned it
▪ Cancel TQ: Cancels QT flow (option for TQ authoring user only)
▪ Back: Return to main screen

17
1.10 Indicate if TQ has been successfully implemented or not (Repair Strategy)

Given that the authoring user has accepted the answer received. Then the TQ deadline expires and the
authoring user has to indicate whether the TQ has been successfully implemented or not. And the user
can put the MOC number (optional field);

If TQ was successfully implemented, the status will be "Awaiting lessons learned validation" and TQ is
directed to the TIER 3 user who was involved in TQ to record lessons learned. If TIER 3 was not involved
in TQ, it will go to a random TIER 3 user in the distribution of system TQs, respecting the discipline and
vessel of TQ.

If TQ was not successfully implemented, the author user completes the required field "Why this
implementation wasn't success?" and the flow restarts. It is directed to a TIER 2 user to analyze. If a user
of this TIER is already involved in the flow, it returns to that same user. If not, it will go to a new TIER 2
user in the distribution of system TQs, respecting the discipline and vessel of TQ. The status will be
“Awaiting TIER X Analysis”
If TQ was opened by TIER 2 and was unsuccessfully implemented, it will go to TIER 3 to reanalyze.

18
1.11 Indicate if TQ is a candidate for lessons learned: TIER 3

Given the TIER 3 user have received a TQ to indicate if she is a candidate for lessons learned.

Then the user will indicate in TQ with the options "yes" or "no" and in case of "yes" will register the
information in an external system. Clicking submit the TQ stream ends and its status is “Completed”

19