• Beta
Creating PLSS Schedules (Assessment, Inspection, CAIR, Preventative)
  • 09 Aug 2024
  • 5 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Creating PLSS Schedules (Assessment, Inspection, CAIR, Preventative)

  • Dark
    Light
  • PDF

Article summary

Take Note
This overview explains how to create Schedules in IMS-PLSS.

Creating a Schedule

 To create a Schedule:

  • On the Main Menu of the Schedules Main Screen or from the Equipment Details Page, click on the Plus button.
  • Select Schedule Type and fill in the date (“when”)
  • Select the Scope (or checklist) (“what”)
  • Select the Plan code (“what”)
  • Enter Narrative (“how”)
  • Add Attachments
  • Final approval (Scope, Timing, and Narrative are clear)

Adding a Schedule

  • Click the Plus button on the Schedules Main Screen:
Click the Plus button to add a new Schedule.
  • Or click the Plus button on the Equipment Details Page:
Or click the Plus button on the Equipment Details Page.
  • Fill in the data in the dialog below:
Take Note
The yellow fields have to be filled in.
Fill in the data to create a Schedule.This dialog contains the following parameters:
FieldDescription

Equipment ID

The Equipment for which the Schedule has to be created. This field is auto populated based on the object from which you are creating the Schedule. 

Hierarchy

Hierarchy path for this Schedule (read-only).

Schedule Type

A list box with the following options:

  • an Inspection (ILI run, collect CP data, …).                       
  • an Assessment ( RBA assessment, internal corrosion assessment, …).                          
  • a Corrective Action (a once-off activity).
  • Preventative Maintenance (cleaning pigging, hydrotest, …).


Description

A Description.

Active

Active or inactive.

TA Candidate

Turn Around (TA Candidate) (true/false). (See Tying Schedules to Upcoming Events.) If ticked, then it can be used for filtering later.

Intrusive

Intrusive Schedule (true / false), if ticked then it can be used for filtering.

Recurring

Recurring Schedule (true / false). If ticked, the Interval has to be specified on the right side of the dialog.

If not ticked, this information will not be displayed.

If you set this to be true, you will also need to specify a Time Interval. Note: CAIRs cannot be recurring.

Offline

Offline Schedule (true / false), if it is ticked it can be used for filtering.

Legal / local inspection / jurisdiction

Should activity be performed for legal reasons? If ticked, it can be used for filtering.

CMMS Tracking ID

Here the CMMS Tracking ID can be filled in. Otherwise, the tracking ID will start with 11 followed by the schedule number.

Discipline
  • Pipeline and Subsea
  • NRB
  • Fabric Maintenance

Schedule Driver

A list box with the following options:

  • Fabric Maintenance.
  • Jurisdiction.
  • Other.
  • Pipeline RBA.
  • PLSS.
  • Recommendation.

Resp. Discipline

A list box with the following options:

  • EI Only.
  • ME Only
  • PLSS.
  • PLSS and ME.

For sites where IMS is linked to CMMS, “ME Only” or “PLSS and ME” should be selected to trigger the SAP notification.....

Schedule Category

A list box with the following options:

  • Category 1
  • Category 2
  • Category 3

MTO

Manage Threats & Opportunities, if ticked a text can be added.

MOC

Management of Change, if ticked a text can be added.

User Date

The date before the Schedule has to be executed.

Event Date

You can search for a Planned Event. By default, the planned events for the Unit will show. See Tying PLSS Schedules to Upcoming Events.

User interval

This field is only available if the Schedule is Recurring. If available, you can also select the default.

Static schedule

If a Recurring Schedule is credited in the ECH then on the new created Schedule the Next Inspection date is set to Condition date + User interval.

If this Static Schedule box has been ticked, then after crediting the Schedule in the ECH the next inspection on the new created Schedule is the User Date on the credited schedule + user Interval.

Example:

  • the User date = 24 Dec 2021, time interval 12 months.
  • the work has been executed on 25 Sep 2021 and the condition date on the ECH is 25 Sep 2021.

If the Static schedule box has not been ticked then the Next Inspection Date on the Schedule is 25 Sep 2022, the ECH condition date + 12 months.

If the static Schedule box is ticked then the Next Inspection Date on the Schedule is 24 Dec 2022. (User Date on the Schedule + 12 months).

SAP Release Date

Add SAP Release Date if applicable

Applicale AreaThe Area-FLOC to which the Equipment is asigned. Only available for the CAIR Schedules if the Schedule Driver is "Fabric Maintenance" and the Available Area exists).
Break-inCheck if applicable.
Labels


Custom labels which can be assigned to each record.


Let’s assume a Schedule has to be created to record the CP data every year starting 21 Jan 2021. Then we have:

User Interval
Schedule TypeActiveRecurSchedule driverResp. DiscSchedule CategoryUser Date

INSPECTION

TRUE

TRUE

PIPELINE RBA

PLSS

CAT 1

24-Dec-2021

12

which will result in:

Schedule to record CP data every year starting 21 Jan 2022.
  • When done click on the Save button. The Main Screen the Schedule will be displayed.

Schedule Categories

Category 1

Category 1 deals with Integrity issues. The required work has a fixed due date (non-priority based) which reflects the date by which the results of the activity should be complete to prevent an Integrity issue within the premised run-length. Also, this involves work required to maintain the license to operate Equipment beyond the due date of compliance with code or legal requirements. Legal auditing is carried out for this category.

The Scope or Due date of a Cat 1 can be challenged and optimized, but changes are only made by EI and require an extension per an official process.

Category 2

Category 2 deals with Reliability issues. The required work has a proposed due date (priority based) which reflects the date by which the results of the activity should be complete to prevent a Reliability issue within the premised run length. Note: as time goes by, a Category 2 job could be upgraded to Category 1.

The Scope or due date of a Cat 2 can be challenged and optimized and changes can be made by ME with PLSS input.

Category 3

Category 3 deals with long-term Reliability and Infrastructure issues. The required work has a proposed due date (priority based) which reflects the date by which the activity should be complete to prevent longer-term, lifecycle, and infrastructure issues. Note: as time goes by a Cat. 3 job could be upgraded to Cat. 1.

The Scope and Due Date of a Cat 3 can be challenged and optimized and changes can be made by with PLSS input.

These categories have been defined to manage significant differences in ‘Aim of the Request’, ‘Who can change dates & scopes’ and ‘Management of Metrics’. 

This is summarized in the table below.

Schedule Categories Summarized:

Cat

AIM

Who can /.ç/.ç

Overdue EI Metric

1

Integrity

PLSS (with ME)

Zero target, report to Sr Management

2

Reliability

ME (with PLSS)

Zero target, report to PU Manager

3

Long term

ME (with PLSS)

PU target, report to PU Engineer


Was this helpful? Click to add feedback comments

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.
ESC

Eddy AI, facilitating knowledge discovery through conversational intelligence