PIPING Work Processes

RFMS PIPING DATA ENTRY & ACD GUIDELINE
RFMS - - RICHMOND REFINERY

OSI - PIPING INSPECTION REV. 1 – May 05, 2009
CONTENTS:
I. PURPOSES OF THIS STANDARD . . . . . . . . . . . . . . . . . . . . . . . . Page 2
II. FOUNDATIONAL DOCUMENTS . . . . . . . . . . . . . . . . . . . . . . . . Page 2
III. RFMS DRAFTING DETAILS FOR MOC UPDATES . . . . . . . . . . . . . . Page 3
IV. CM DATA ENTRY DETAILS FOR MOC UPDATES . . . . . . . . . . . . . . Page 3
V. DETAILS OF HANDLING NEW DRAWING ADDITIONS . . . . . . . . . . . Page 4
VI. DETAILS OF HANDLING DRAWING DELETIONS . . . . . . . . . . . . . . Page 7
VII. DETAILS OF RFMS CM DATA ENTRY AND ANALYSIS . . . . . . . . . . . Page 7
VIII. DETAILS OF RFMS HAND-OFF OF DATA ANALYSIS TO FXD INSP. . . . Page 8
IX. DETAILS OF RFMS AND FXD INSP. CO-USAGE OF CM DATABASE . . . . Page 8
X. DETAILS OF UTILITY PIPING PROGRAM IMPLIMENTED IN 2006 . . . . . Page 10
XI. RFMS OSI WORKFLOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . Page 10
XII. HANDLING HOT TMLS WHICH ARE ALSO INJ. PT. TMLS . . . . . . . . Page 11
XIII. REVIEW OF PIPING ISOMETRICS DURING EXT. VIS. MONITORING . . . Page 12
APPENDIX “A”: Chart of Piping ACD Process . . . . . . . . . . . . . . . . . . . . Page 13
APPENDIX “B”: Tmin Comments to be Inserted into CM . . . . . . . . . . . . . . . . Page 14
APPENDIX “C”: The Four Different Types of Tmin Used in Piping CM . . . . . . . . Page 15
APPENDIX “D”: How MERIDUM CM Data Relates to Other Foundational Documents . Page 16
APPENDIX “E”: OSI Initial Data Analysis Workflow . . . . . . . . . . . . . . . . . . Page 17
APPENDIX “F”: OSI Alert Logic Diagram . . . . . . . . . . . . . . . . . . . . . . . . Page 18
APPENDIX “G”: Piping Utility System Drawing & Inspection Plan Matrix . . . . . . . Page 19
APPENDIX “H”: Piping Circuit Design Data Needed in Meridium . . . . . . . . . . . Page 21
APPENDIX “J”: Piping Circuit System Level Entities . . . . . . . . . . . . . . . . . . Page 23
APPENDIX “K”: Expectation of the Personnel who are Key to Effective Data Analysis . Page 24
APPENDIX “L”: RFMS Drafting: Details of MOC Updates and New Isometrics . . . . Page 27
APPENDIX “M”: OSI CM: Checklist of Items for TML ACD in Meridium . . . . . . . Page 28
APPENDIX “N”: Steam and Condensate Tmin Chart . . . . . . . . . . . . . . . . . . Page 30
APPENDIX “P”: TML NDE Measurement Method Matrix . . . . . . . . . . . . . . . Page 31
APPENDIX “Q”: Chart of OSI Work Process . . . . . . . . . . . . . . . . . . . . . . . Page 32
APPENDIX “R”: Definition of Terminology Used in CM . . . . . . . . . . . . . . . . Page 33
APPENDIX “S”: Form for Collecting Dummy Leg Data on Piping ISO’s . . . . . . . . Page 35
Page 1 of 36
I. PURPOSES OF THIS STANDARD
NOTES:
The major Basic Purpose is to capture work processes associated with the RFMS OSI Piping
Program
• This document is thus a guideline in particular for the RFMS OSI Coordinator
• It is expected that the RFMS OSI Coordinator use and maintain this document as a
foundational guide in executing the RFMS OSI Piping Program
Additional note: There is an Inspection Equipment Document maintained by the
RFMS Drafting personnel that is somewhat of a counterpart to this document
In addition to the major purpose mentioned above, there are various elements that make up this
major purpose which are identified in “A” thru “G” below
Finally besides the major purpose and the additional purposes listed below with regard to
capturing RFMS Work Processes there is also one other purpose to this document - - i.e. to
provide training for RFMS personnel as needed.
A. To Provide Details of Handling MOC updates from Refinery Drafting
1. RFMS Drafting Details for MOC Updates
2. CM Data Entry Details for MOC Updates
B. To Provide Details of Handling New Drawing Additions
C. To Provide Details of Handling Drawing Deletions
D. To Provide Details of RFMS CM data entry and Analysis
E. To Provide Details of RFMS Hand-off of data Analysis to FXD Inspection
F. To Provide Details of RFMS and FXD Inspection Co-usage of the CM Database
G. To Provide Details of Utility Piping Standards implemented since 2006
H. To Provide Details for Handling of Hot Injection Point Circuits
I. To Provide Details for the Proper Field Check of Piping ISO’s for External Monitoring
II. FOUNDATIONAL DOCUMENTS

A. This document is designed to build upon the “Chevron California Refining Piping
Guideline” that was created in 2001 by a joint group of El Segundo and Richmond
personnel
B. Also, this document, like the Piping Guideline reference above, utilizes the API-570 Piping
Inspection Code as a standard that is foundational to details within this document
C. Refinery PSM documentation also underlies our Database data. The primary document for
PSM piping is the P&ID.
D. The final document underlying all our piping database data is the Inspection Piping
Isometric.
E. NOTES: The data in our database relies on all four of the documents referred to above and
builds on top of these documents.
1. The guidelines, codes, P&ID’s, and Inspection Piping Isometrics are fundamental to the
RFMS Piping programs.
2. The data in the database if it conflicts with any of these four is to be corrected to align
with these more foundational documents unless it can be show that they are in error.
F. Refer to Appendix “D” for Chart of Foundational Document Interrelationship
Page 2 of 36
III. RFMS Drafting Details for MOC Updates (& Relabeled / Transferred ISO’s)
A. MOC Piping Isometric Updates - - Origination

1. It is the responsibility of the Refinery Drafting group to maintain the “configuration”
layers of the Inspection Piping Isometrics
• The “configuration” layers are the layers containing all the piping, equipment,
PRD, and instrumentation data
• The “Inspection” layers are the layers which contain TML’s and Inspection Notes
2. Most Changes to the Inspection Piping Isometrics are driven by Engineering MOC’s
3. All changes to Inspection Piping Isometrics are E-mailed to the RFMS Draftspersons
along with the MOC number
4. Once the updated Inspection Piping Isometrics are available to the RFMS draftsperson
then a review of the “Inspection” Layers of the Isometric are needed to determine if any
changes to TML locations and Inspection notes are needed.
5. While the majority of changes at the “configuration” layers are MOC driven there are
other ways in which Inspection Piping Isometric changes can occur (however the work
process is basically the same)
6. Some of the less frequent ways in which Piping Isometric changes occur are:
• Drawings are occasionally relabeled because they actually belong to another Unit or
another System
• A section (or portion) of an existing drawing is transferred to another drawing
because of Pipe Class differences, because of differences is services, because of
difference in corrosion loop criteria, or because of changes made to piping in the
field.
• Discoveries made in the field by NDE Inspection crews, by Engineers, or by Fixed
Equipment Inspection personnel.
B. MOC Piping Isometric Updates - - Review Checklist
1. Refer to Appendix “L” for a Checklist of Items to Review when updating an existing
Piping Isometric based on an MOC from the Refinery Drafting group
2. The same Appendix “L” has a Checklist also for Items to Review when New
Isometrics come from a Project or from the Refinery Drafting group
IV. CM Data Entry Details for MOC Updates (& Relabeled / Transferred ISO’s)
NOTE: Refer to Appendix “M” for additional details of the six ACD processes mentioned below
for TML data
A. For Drawing Deletions (i.e. demolished piping)
1. In general - - all CM data to be deleted
2. In general - - Asset to be Retired
B. For Drawings that are “Out-of-Service”
1. In general - - all TML’s to be inactivated
2. In general - - Asset to be set to Inactive
Page 3 of 36
3. However, must check that circuit is “positively isolated” - - i.e. air-gapped or blinded
C. For Drawings that are “Abandoned in Place”
1. In general - - all TML’s to be inactivated
2. In general - - Asset to be set to Retired
3. However, must check that circuit is “positively isolated” - - i.e. air-gapped or blinded
D. For Drawing Additions
1. Asset to be added to Maximo / Meridium Registry as Active
2. TML design data to be entered into CM
3. Baseline data to be obtained per guidelines in Appendix “M” (Item #D)
E. For Relabeled Drawings (drawings reassigned to another unit or system)
1. In general - - all CM data to be transferred to the new entity (i.e. the old entity
relabeled)
2. Occasionally TML renumbering may occur
3. RFMS Drafting to update WEB links
4. RFMS Drafting to markup P&ID’s with any changes and submit to Refinery Drafting.
F. For Transferred sections of drawings
1. Occasionally a section of an existing drawing is found to belong to a different service,
or a different system, a different pipe class, or a different unit.
2. This section of drawing is then transferred to the appropriate drawing.
3. In general - - all CM data on the transferred portion of the drawing must also be
transferred in Meridium CM to the proper entity in Meridium
4. TML renumbering may be necessary
5. RFMS Drafting to update WEB links
6. RFMS Drafting to markup any changes on P&ID’s and submit to Refinery Drafting
V. Details of Handling New Drawing Additions
A. Reference Appendixes
1. Refer to Appendix “A” for Flowchart
2. Refer to Appendix “K” for Overview of Roles of the Key Personnel
3. Refer to Appendix “H” for Piping Circuit ACD data
4. Refer to Appendix “M” for TML ACD data
B. NEW PIPING CIRCUITS (Drafting Responsibility)
1. Add Note to drawing stating: “This Circuit is New as of ‘DATE’ “
2. Interact with the Area Inspectors to have TML’s assigned
3. CAD the TML’s assigned by the Area Inspector
4. Provide Copy of New Circuit to OSI Coordinator
• To provide baseline data (usually not urgent but can’t be overlooked)
• To provide staging data on TML’s
• To provide insulation data on TML’s
5. Provide Copy of New Circuit to OSI Data Analyst
Page 4 of 36
6. See Section “X”, paragraph “A”, item “3” of this document for handling of Steam
Lines
C. NEW PIPING CIRCUITS (OSI Data Entry Analyst Responsibility)
1. IMPORTANT: Input TML design data into CM right away (this insures that TML’s
will be caught on the next year’s program if baseline data fails to make it into the
system)
2. Input Baseline data when available
NOTE: If new drawing is a utility circuit, then see Section “X” below
D. NEW PIPING CIRCUITS (ACD Coordinator Responsibility)

1. Note Distinctions between Piping Circuit Entities and Piping System Entities
mentioned in Item “F” below.
2. All Piping Circuit Entities and Piping System Entities are first entered into the Maximo
Maintenance Management Database by the RFMS ACD Coordinator
3. The next day the Entity will be available in the Meridium Registry and in CM for
additional data entry
4. The following Categories of Items need to be added to Meridium Registry and
Meridium CM by the RFMS ACD Coordinator (or other delegated representative):
• Basic Asset Registry Data - - - - - - - (for Details see Appendix “H”)
• Basic Location Registry Data - - - - (for Details see Appendix “H”)
• Basic RBI Registry Data - - - - - - - - (for Details see Appendix “H”)
• Basic Piping Plan Registry Data - - - (for Details see Appendix “H”)
• Basic CM Data - - - - - - - - - - - - - - - (for Details see Appendix “H”)
Tmin notes
Note#1: Default Tmin is auto populated
Note#2: However, the following is necessary upfront at the time of initial CM
data entry:
(a) Check if TML is high pressure based on Pipe Class
(b) If high pressure TML then check with RFMS IT Support for proper Tmin
(c) Enter comment indicating where proper Tmin came from
(d) See Appendix “B” for help guide on these comments
(e) Refer to Appendix “C” for understanding of the four different types of
Tmin’s used in Meridium
E. NEW PIPING CIRCUITS (OSI Coordinator Responsibility)

1. Refer to Appendix “A” - - “OSI Coordinator” column
F. NEW PIPING SYSTEMS

1. What is a System Piping Entity in Meridium?
• A System Piping Entity is an artificial entry in the Meridium Database
Its primary purpose is to allow data at the circuit level to be rolled up to a single
system level record (See Item “2” below for greater detail)
Page 5 of 36
Hence (for example) it represents all the circuits in particular system (i.e. xxxx-
xxx-001 thru xxxx-xxx-020 if 20 circuits exist in that system)
This is our way of creating an artificial "cluster" in the database
• A System Piping Entity is created in Meridium just the same as a Circuit Piping
Entity
• However it is distinguished from the “Circuit” entity by its label
All Circuit entities will be labeled with the last three or four digits having
numbers - - (i.e. xxxx-xxx-001; or xxxx-xxx-001A; or xxxx-xxx-A01)
However all System Entities will end with a “000” (i.e. xxxx-xxx-000)
2. The THREE Purposes or Usages of System Level Entities
• See Appendix “J” for the details of the three different usages or System Level
Entities in the 221 piping asset type
• FIRST OF THE THREE PURPOSES - - Used for systems with standard piping isometrics
to capture history at the system level and to capture “External Visual Monitoring” tasks at
the system level.
• SECOND OF THE THREE PURPOSES - - Used for utility systems that don’t have
standard isometrics but which need NDE data. Currently this is only the Utility Steam
systems. All the NDE data for the Steam system is captured at the system level.
• THIRD OF THE THREE PURPOSES - - Used for utility systems that don’t have standard
isometrics and also don’t require NDE data. Used specifically for “External Visual
Monitoring” Task.
3. INSTRUCTIONS when Creating these System Level Entities

• For All Systems with Standard Piping Isometrics do the following:
Delete the “UT Monitoring” and “RT Monitoring” Tasks at time of Creation
Create a “External Visual Monitoring” Task with the appropriate interval
(a) A five (5) year interval if system is an API-Class 1 or Class 2 system
(b) A ten (10) year interval if system is an API-Class 3 or Utility system
(c) See APP 08 – INSPECTION GUIDELINES of the “Chevron California
Refining Piping Guideline” for guide to classification of lines.
Set the “Last Inspection Date” to the Date that the Plant went into Service
• For All Utility System which do not have Standard Piping Isometrics AND which
do have “Highlighted P&IDs with Digital Photographs” do the following:
Create “External Visual Monitoring” Tasks with ten year intervals
Set the “Last Inspection Date’ to the Date that the Plant went into Service
• For All Utility System which do not have Standard Piping Isometrics and which
have “Highlighted P&IDs WITHOUT Digital Photographs” do the following:
Create “External Visual Monitoring” Tasks with ten year intervals
Set the “Last Inspection Date’ to the Date that the Plant went into Service
Delete the “UT Monitoring” and “RT Monitoring” Tasks at time of Creation
G. NEW PIPING CM DATA

1. New CM Data comes about in two ways
• When new Circuits come into existence
• When new TML’s are added to existing circuits
2. Since the same procedure is used for both cases then the following instructions are
pertinent to both
Page 6 of 36
3. For Instructions see Appendix “H”, Section titled “BASIC TML CM DATA”
VI. Details of Handling Drawing Deletions
A. Drawing Deletions are relatively uncomplicated

1. Insure Drawing is cross-hatched with appropriate note.
2. Insure that WEB link or note is updated
3. Insure Meridium CM data is all deleted
4. Insure that Maximo / Meridium entity status is set to “RETIRED”
B. Refer to Appendix “A” for workflow.
VII. Details of RFMS CM data entry and Analysis

A. The KEY Personnel in our RFMS CM Data Analysis
1. The NDE Crew (usually contractors)
2. The NDE Crew Lead (a contractor with “lead” skills)
3. The OSI Data Entry Analyst (usually a contractor)
4. The OSI Coordinator (usually a Chevron employee)
B. Appendixes relation to CM Data Entry and Analysis
1. Appendix “K” provides a more detailed look at the “expectations” required of the four
key personnel above
2. Appendix “E” shows the interrelationship between all four key personnel in the
analysis of data coming in from the field
3. Appendix “F” provides a Logic Flow Diagram for initiating an Alert when data issues
are found.
C. The NDE Crew - - Expectations with regard to OSI and CM Data
1. The NDE Technician (with his assistant) is the front line of defense in finding and
handling CM data
2. They are the “discoverers” of the data and if properly experienced and trained can
immediately make an upfront analysis to determine:
• if there is an issue,
• the severity of the issue,
• and whether additional NDE data should be gathered immediately.
• See Appendix “K” for additional details
D. The NDE Crew Lead - - Expectations with regard to OSI and CM Data
1. The NDE Crew Lead interfaces with all the various teams to accomplish such items as:
• Turning all the various NDE crews into a team
• Facilitating training, safety, and communication of expectations
2. The NDE Crew Lead also interfaces with the OSI Coordinator to address CM issues
discovered in the field and to communicate scheduling and priorities to the crews
3. See Appendix “K” for additional details
E. The OSI Data Entry Analyst - - Expectations with regard to OSI and CM Data
Page 7 of 36
1. The OSI Data Entry Analyst is the first person to see the consequence in Meridium of
the newly entered data from the field
2. This Analyst also is the first person to be able to recognize and correct any data entry
errors
3. See Appendix “K” for more detailed description
F. The OSI Coordinator - - Expectations with regard to OSI and CM Data
1. The OSI Coordinator interfaces between the NDE Company and RFMS to insure a
quality product from the NDE Company
2. The OSI Coordinator also interfaces between RFMS and the Chevron customers to see
that a quality report is delivered to them
3. The OSI Coordinator is therefore (in essence) accountable for the success of the OSI
effort.
4. See Appendix “K” for more detailed description of expectations
VIII. Details of RFMS Hand-off of data Analysis to FXD Inspection
A. Refer to Appendices “E”, “F”, and “K” for information about reporting of OSI results and
issues
B. There are three reports that should be standard reports from RFMS to the customers
C. These reports are the responsibility of the OSI Coordinator
D. The three reports are:
1. A communication within three days of all “URGENT” CM issues -- see Appendix “E”
• This typical should be done via the new CM database communication tool
• But should also be followed up in person for these “Urgent” issues
2. A communication within thirty days of all “ROUTINE” CM issues -- see Appendix “E”
• This should be done via the new CM database communication tool
• But doesn’t necessarily need personal follow-up
3. A communication of all existing CM issues belonging to a specific plant after
completion of the OSI program for that plant.
IX. Details of RFMS and FXD Inspection Co-usage of CM Database
A. Meridium CM data has two major users

1. The FXD Inspection group
• Fixed Inspectors are the primary customer
• They need the data for analysis of piping within their plants.
• It is their responsibility to determine the overall reliability of piping systems within
their areas
2. The RFMS group on the other hand
• Is responsible for the gathering of the majority of data going into CM
• Is responsible for the scheduling of data going into CM
• And is responsible for insuring that the data in CM matches the data from the
Inspection Piping Isometrics
B. The two distinct types of data in Meridium CM
Page 8 of 36
1. In CM there is two types of data displayed from two or three different tables
2. There is the TML data from the RT Datapoint table and the UT Datapoint tables
• This is the “tech” data for the TML - - see Appendix “H” and section entitled
“Basic TML CM Data”
• This “tech” data is what must align with the Inspection Piping Isometric
3. And there is the Measurement data from the Measurement Table
4. In the CM Module one can see both types of data in the same view by clicking the
appropriate check box. - - The “tech” data is then in the top of the view and the
“measurement” data is in the bottom half of the view
C. Possible Issues that can arise from indiscriminant changes to CM data by the members of
these two groups
1. The proper process for changing any “tech” data is to mark-up the change on the
“piping isometric” and provide the mark-up to RFMS drafting - - this will cause both
the Isometric and Meridium CM data to be updated concurrently.
2. Also, indiscriminant changes to the measurement data can affect the OERI metrics and
various OSI CM scheduling tools.
D. The best solution to preventing issues in CM data
1. Occasional training of both Area Inspectors and RFMS personnel on OSI Programs and
work processes.
2. Maintaining a close working relationship between the two groups where issues can be
readily discussed and resolved.
X. Details of New Utility Piping Program (Implemented Since 2006)
A. Refer to Appendix “G” for Listing of Various Utility Systems in the Refinery and the
currently approved plan for Inspection
1. The Utility Systems are listed under the following Five Categories of Utility Systems
• Steam Systems
• Condensate Systems
• Hydrocarbon Systems (Hydrocarbon systems used as utilities such as Lube Oil,
Seal Oil, Flush Oil, Mist Oil, Wash Oil)
• Water Systems (Other than Condensate)
• Other Systems (Primarily Air & Inert Gas)
2. Special Notes on Steam Systems
• All Steam Systems that are Medium Pressure or greater require TML’s and
Condition Monitoring
• However, for cost purposes, we will use marked up P&ID’s rather than the standard
Inspection Isometrics for identifying the TML locations.
The P&ID’s will identify the line
Digital photographs attached to the scanned and highlighted P&ID’s will
identify the TML locations.
• The P&ID’s are to be marked up as if they were laid out like a standard Isometric
Page 9 of 36
The individual lines identified are to be listed on the WEB as if a standard line
However, all the TML’s for that Steam System will be listed under the single
system level entity for that plant in Meridium - - i.e. “xxxx-xxx-000”
3. Responsibilities for new Steam Systems or Steam Drawings that are medium pressure
lines or greater
• RFMS Drafting is responsible for the following:
(a) For each new Steam Line in an Existing Plant
Highlight the new line on a current P&ID
See that Highlighted P&ID is scanned as “pdf” file and added to WEB
See that new WEB entry is given an appropriate name on the WEB
Coordinating with the OSI Coordinator to have someone get an digital
picture of an appropriate location on the new line for getting NDE data
i. Need one close in photo to identify the precise location of TML
ii. Need one wider angle photo to identify the location of piping versus
more major items of equipment that are readily found.
Scan photo’s, label photo’s and add to “pdf” file
(b) For new Steam Lines in New Plant
Review the plant P&ID’s
Determine the appropriate identification of steam system lines
Create appropriate labels for the lines in the new steam system
Work with ACD Coordinator to add entity to Maximo/Meridium for each
new Steam System
Create individual steam line entries on WEB for each new steam system
Follow the process in “(a)” above for each line in the new steam system.
• The ACD Coordinator is responsible for creating steam system entities as needed
• The OSI Data Entry Analyst is responsible for adding all the TML’s for the new
steam lines into CM at the system level
• The OSI Coordinator is responsible for gathering baseline data at the appropriate
time
B. Refer to Appendix “N” for Tmin’s for Condensate and Steam Piping Systems
1. It has been approved that we use 0.07” as a flag Tmin for Condensate and Steam
systems when the piping is four inches (4”) in size or less.
2. For Condensate and Steam piping greater than four inches we are to use 0.10” as the
flag Tmin
3. If Steam or Condensate is higher pressure then one much check to see if the default
Tmin’s mentioned above are adequate.
4. If default Tmin is not adequate then see Appendix “N” to obtain the flag Tmin to use
for higher pressure steam and condensate piping.
XI. Details of RFMS OSI Workflow
A. Refer to Appendix “Q” for Chart of OSI Workflow
Page 10 of 36
B. This chart is a comprehensive overview of the workflow of our OSI Piping and OSI
Equipment Programs
C. This chart is the responsibility of the OSI Coordinator to keep up to date
D. It should be reviewed annually at the end of the yearly OSI Program and prior to the start of
the succeeding yearly program to be sure that it is up to date in that it accurately reflects the
current OSI work practices.
XII. Handling HOT TMLS which are also INJ. PT. TMLS
A. Standard Injection Point Circuits have two type of TML’s

1. Those TML’s on the Circuit which DO NOT pertain to the Injection Point
• These TML’s can be on a ten year interval (or whatever the circuit pipe class calls
for)
• They are a part of the standard drawing in Meridium (i.e. the “xxxx-xxx-xxx”
drawing)
2. The TML’s on the Circuit which are the Injection Point TML’s have the following
qualities:
• They are on a different entity in Meridium (i.e. the “xxxx-xxx-xxx-I” entity)
• This was necessary to put them on the required 3 year interval called for by API-
570
B. NOTE: There are a handful of circuits which are Injection Point Circuits AND are also too
hot to do on the run - - i.e. to hot for OSI.
1. Because they are too hot for OSI they must be done during shutdowns.
2. However, shutdowns frequently occur on a four or five year interval and therefore the
TML’s on these circuits would not be completed within the required compliance
interval
3. The approach that we are using on these very few circuits is as follows:
• We create a third entity in Meridium which is labeled “xxxx-xxx-xxx-S”
• The “S” stands for “shutdown” circuit
• This entity has the exact same TML’s as the “I” circuit - - however the interval on
this entity is five years.
4. These three different entities in Meridium all are based on the one drawing but they
have different responsibilities as described below:
• The “xxxx-xxx-xxx” entity: This entity in Meridium CM is on a ten year interval
and since it is a Hot Circuit the responsibility for these TML’s is the Fixed
Inspection - - the TML’s need to be gauged during shutdowns.
• The “xxxx-xxx-xxx-I” entity: This entity is on a three year interval and the
responsibility belongs to OSI.
(a) OSI is to cut a single cookie on these TML’s between shutdowns (i.e. within
the three year interval)
(b) It is to get a single UT reading and enter this reading into CM.
(c) This completes our OSI efforts on this Hot Circuit TML which is also an
Injection Point Circuit
Page 11 of 36
(d) When the TML comes due again, then if there is more recent data on the same
locations from the shutdowns then this data will be entered into CM by OSI to
bring the three year TML’s up to compliance
• The “xxxx-xxx-xxx-S” entity: This entity is on a five year interval and the
responsibility belongs to Fixed Inspection.
(a) The Area Inspector will see that a more thorough CGUT scan of these TML’s
(the same as are on the “I” entity) is made during shutdowns.
(b) This data is the data that will be used for “Fitness for Service” reviews of the
Injection point circuit.
XIII. Field Check of Piping Isometrics to verify RFMS data during Ext. Vis. Monitoring
A. Refer to the following two Documents for forms and instructions

1. Appendix “S”: Form for collecting Dummy Leg data on Inspection Isometrics
• They are on a different entity in Meridium (i.e. the “xxxx-xxx-xxx-I” entity)
• This was necessary to put them on the required 3 year interval called for by API-570
2. Note that the following Appendix in the Chevron California Refining Piping Inspection
Guideline has been updated: APP 11 - EXTERNAL VISUAL EXAMINATION
CHECKLIST
• This appendix has been updated to reflect the fields in Meridium
• It has an accompany instruction sheet reflecting the needs of RFMS during this
Inspection
• DO NOT use the old form.
B. Comments on Dummy Legs on the Inspection Piping Isometrics
1. All dummy legs on the Inspection Piping Isometrics are to be identified and labeled
2. The Dummy Leg Label is to be a TML in Meridium CM
3. However, this TML is be set to Inactive
4. All the relevant data for a dummy leg is to be recorded in the TML Comment field for
that dummy leg TML
5. See Appendix “S” for the data which is to be collected
C. Comments on External Visual Monitoring Inspections for Piping

1. Any person performing an External Visual Monitoring Inspection is expected to use the
New Checklist.
2. This Checklist is oriented towards the data which is needed per the set of data fields in
Meridium
3. In addition to the data collected on the checklist for Meridium, the Inspector is expected
to take a copy of the Inspection Isometric into the field and to verify / add / update
appropriate information on the Isometrics - - again refer to the new updated Instructions
and Form (i.e. Appendix 11 on the Piping Guideline reference above)
Page 12 of 36
APPENDIX “A”
Chart of RFMS Piping ACD Process
Area RFMS CM Data OSI ACD
Inspection Drafting Entry Analyst Coordinator Coordinator
START
CAD
Changes
Deleted, Delete / Move Change Circuit

moved, or or Inactivate TML’s Status
in Meridium CM in Maximo
OOS Yes
ISO?
No CAD
Changes ADD Circuit
Update WEB To Maximo
As needed
Yes
Add TML’s Yes New

As needed ISO?
No ADD TML’s Review Add any
to Meridium New or Revised Needed Tech Data
CM Piping Isometrics To Meridium
TML’s for New Circuits can’t Refer to Appendix “H”

Significant be added until ACD For details on Tech Data
“Not-in-Kind” Coordinator adds circuit to
Yes Revision? Maximo
NDE CREWS
Mark-up
No
affected
TML’s that Is this Yes
need a new Class 1
Replacement circuit?
Flag
No
“In-Kind”
Replacement
Are TMLs Yes
API-Class 1
Affecting Yes piping?
TML’s?
Is this
No No
Any Piping Isometric
a new Class 2 Yes
Circuit and is
changes discovered by today’s date prior
Area Inspector, NDE
to July?
Crews, Engineers, Ext. Vis.
Monitoring Inspectors, etc Are TML’s
CAD any other Class 2 and do No
changes other TML’s on Yes
to TML’s circuit have
and add Notes
Field Walks if needed
< 20 yrs
R/L?
Mark-up
Changes No
For Drafting
Set Replacement Has
Flag using nominal there been any
Does any Yes thickness for special request Yes
TML Tech Data from AI for baseline
Change? baseline. Get Date
from RFMS Drafting data?
No
No Refer to No
Were Do Mark-up Appendix “H”
any changes Yes changes Changes For details on
Tech Data
to ISO’s affect Yes
discovered? P&ID?
Wait till next
Insure TML has all
year’s OSI Program
No Does any Yes other tech data
to get baseline
Dwg WEB Data updated per this
Change? OSI CM piping
document i.e. API-Class 3
& Utility piping
No should normally
wait until
Update CM with following year
measurement
Get Baseline
Update WEB data and any NDE Measurements
replacement
flags
END END END END
Page 13 of 36
APPENDIX “B”
Tmin Comments to be Inserted into CM
# Type of Comment Sample Comment

NOTES: One should Copy and Paste these “Sample Comments” and then change the data as needed
Else: Type in the comment as closely as possible to the sample comments
1 SAMPLE COMMENT FOR PRE- [Tmin NOTE (7/1/2006): Tmin comes from
EXISTING NON-DEFAULT TMIN Area Inspection]
2 SAMPLE COMMENT FOR Tmin’s [Tmin NOTE (7/15/2006): Default Tmin is

REVIEWED WHICH END UP WITH THE more conservative than Pipe Class Tmin. Used
DEFAULT Tmin DEFAULT versus Refy Pipe Class of "AF1"]
3 SAMPLE COMMENT FOR Tmin’s [Tmin NOTE (7/15/2006): Uses PIPE CLASS
REVIEWED WHICH END UP WITH THE Tmin based on Refinery Pipe Class of "BJ1"
PIPE CLASS Tmin (This is a FLAG Tmin)]
4 SAMPLE COMMENT FOR Tmin’s [Tmin NOTE (7/15/2006): Uses RFMS

REVIEWED WHICH END UP WITH THE Engineered Tmin based on Refinery Pipe Class
RFMS Engineered Tmin of "AJ6". (Upstream Pressure Source is: E-
135A; Des. P is: 730 psig; Des. T is: 650 deg F)]
5 SAMPLE COMMENT FOR PIPING WITH [Tmin NOTE (7/15/2006): Rfry Pipe Class is
150# FLANGE RATING “AB0”. This has 150# Flange Rating. Use
DEFAULT Tmin]
6 SAMPLE COMMENT FOR TRUE [Tmin NOTE (7/15/2006): Tmin provided by

ENGINEERED Tmin Engineering. See History Brief for Details]
• The Engineer should provide E-mail of
details when a Tmin calculation is requested
• The Engineering E-mail with whatever
details are provided is the basis for the
History Brief.
Page 14 of 36
APPENDIX “C”
The Four Different Types of Tmin Used in Piping CM
I. Illustration of the Four Different Types of Tmin used in Piping CM
II. Discussion of the Four Different Types of Tmin used in Piping

A. Default Tmin (this is a FLAG Tmin):
a. When inapplicable it is very wrong i.e. too low
b. Failure to use more appropriate Tmin’s creates “gaps” in our Reliability Efforts.
B. True Tmin
a. Nice to have but hard to obtain
b. Takes engineering 2-3 hours to calculate and may take days to obtain from Engineering
C. RFMS Tmin (this is a FLAG Tmin):
a. Can usually be obtained in only a few minutes
b. Is generally very close to the True Tmin even though should be considered a Flag Tmin
c. The RFMS IT Support person is responsible for generating these Tmin’s
D. Pipe Class Tmin (this is a FLAG Tmin):
a. Easy to obtain (a few seconds) but can be way too conservative
b. When Remaining Life becomes an issue then need to calculate the “RFMS Tmin”
c. The OSI Data Entry / Analyst Support Person is responsible for looking up these Tmin’s
Page 15 of 36
APPENDIX “D”
How the MERIDUM CM Data Relates to Various Foundational Documents
MERIDIUM PIPING CM DATA
INSPECTION PIPING ISOMETRICS
RFMS PIPING WORK PROCESS

REFINERY P&ID’S
(This Document)
CHEVRON CALIFORNIA REFINING

REFINERY PIPE CLASS DATA
PIPING GUIDELINE
PIPING INSPECTION CODE PIPING CONSTRUCTION CODE

API-570 B31.3
Page 16 of 36
APPENDIX “E”
OSI INITIAL DATA ANALYSIS WORKFLOW
NOTES: “Erin” = OSI Data Entry Analyst; “Essie” = OSI Coordinator; “Cordell” = NDE Crew Lead
(Update Personnel on this Chart as Needed)
Page 17 of 36
APPENDIX “F”
OSI INITIAL DATA ANALYSIS WORKFLOW
OSI NDE Crew LAST UPDATE: Monday, May 11, 2009

Collects Data in field
NDE Tech
notices Data at or below
YES OSI Coordinator
Is notified
Tmin*
NO
Data is Delivered to OSI Coordinator Compares

Data Entry Personnel Data from Field with CM
CM flags YES YES

Data can NO ALERT
data is at or below Tmin
Be resolved? REQUIRED
(or >33% wall loss)
NO NO
Coordinator Schedules
NO ALERT
REQUIRED Revisit of Plant
By Senior Technician**
Tech confirms NO NO ALERT

NOTE#1: This document Problem REQUIRED
is designed to articulate
YES
with Appendix “E”.
See Appendix “E” for the OSI Coordinator expands review of
bigger picture. data to determine such issues as:
(A) Is this a totally new finding;
(B) Do previous readings provide
NOTE#2: The “Piping clues to problem;
(C) Do other TML’s on circuit indicate
CM Issues” Access problem is more widespread
database is the new tool
(2009) for aiding this
workflow OSI Coordinator
Issues an Alert
*It is standard procedure for Technician to do a double check of data at this point
**May use alternative NDE method and may expand scope of investigation
Page 18 of 36
APPENDIX “G”
Piping Utility System Drawing & Inspection Plan Matrix
API 570 Condition

P&ID Piping Iso. TML Monitoring EXT. VIS.
Utility Description Req.’d Req.’d Req.’d (If “YES” then 10 yrs) RBI Inspections
STEAM SYSTEMS Note#1: For Medium Pressure Steam use Flag Tmin of 0.07”
on piping <= 4 inches and Flag Tmin of 0.1” on piping > 4 inch. For High Pressure Steam
use standard flag Tmin’s.
NOTE #2: For Ext. Visuals where CM is not required we will use the P&ID’s and not
draw up Piping Inspection ISO’s)
800#/850# Steam Yes No Yes Yes No 10 year VT
(SHH) (use P&ID)
450#/500# Steam (SH) Yes No Yes Yes No 10 year VT
(use P&ID)
150# Steam (SM) Yes No Yes Yes No 10 year VT
(use P&ID)
45#/50# Steam (SL) Yes No No No Yes 10 year VT
30# Steam (SL) Yes No No No Yes 10 year VT
15# Steam (SL) Yes No No No Yes 10 year VT
Snuffing Steam Yes Yes Yes Yes No 10 year VT
Stripping Steam Yes No No No Yes 10 year VT
Steam Out / Pump Out Yes No No No Yes 10 year VT
CONDENSATE SYSTEMS Note: For Medium Pressure Condensate use Flag Tmin
of 0.07” on piping <= 4 inches and Flag Tmin of 0.1” on piping > 4 inch. For High
Pressure Condensate use standard flag Tmin’s.
Condensate (CH – 850# Yes Yes Yes Yes No 10 year VT
to 450#)
Condensate (CM – 150#) Yes Yes Yes Yes No 10 year VT
Condensate (CL – 50# to Yes No No No Yes 10 year VT
15#)
Cold Condensate / Cold Yes No No No Yes 10 year VT
Pumped Condensate
Continuous Blowdown Yes No No No Yes 10 year VT
Intermittant Blowdown Yes No No No Yes 10 year VT
HYDROCARBON SYSTEMS (Note: Please note difference between a self-
contained SEAL OIL / LUBE Oil system and Seal Oil / Lube Oil that is an off-shoot of
the process stream. Historically we have not monitored the Self-Contained systems but
have monitored the systems which are derived from a hydrocarbon process stream)
FLUSH OIL Yes Yes Yes Yes No 10 year VT
LUBE OIL (self-contained) Yes No No No Yes NO VT
LUBE OIL (coming from a Yes Yes Yes Yes No 10 year VT
process stream)
MIST OIL Yes No No No Yes NO VT
Page 19 of 36
APPENDIX “G”
Piping Utility System Drawing & Inspection Plan Matrix
API 570 Condition
P&ID Piping Iso. TML Monitoring EXT. VIS.
Utility Description Req.’d Req.’d Req.’d (If “YES” then 10 yrs) RBI Inspections
SEAL OIL (self-contained) Yes No No No Yes NO VT
SEAL OIL (from a process Yes Yes Yes Yes No 10 year VT
stream)
WASH OIL Yes Yes Yes Yes No 10 year VT
WATER SYSTEMS (Note: Please note difference between Water Systems that
are PROCESS WATER, and Water Systems that are non-Process Water. Historically
we have monitored all water systems that are PROCESS WATER - - i.e. Sour Water,
Stripped Sour Water, Effluent Water, or systems labeled as Process Water. PROCESS
WATER is defined as water that has been pulled off of a process stream in the plant.)
Boiler Feed Water Yes Yes Yes Yes No 10 year VT
Cooling water Yes No No No Yes NO VT
Demineralized Water Yes No No No Yes NO VT
Drinking Water Yes No No No Yes NO VT
Effluent Water (if effluent Yes Yes Yes Yes No 10 year VT
water comes from a process
stream then YES otherwise
NO)
Fire Water Yes No No No Yes NO VT
Flush Water Yes No No No Yes NO VT
Fresh Water Yes No No No Yes NO VT
Plant Water Yes No No No Yes NO VT
Process Water Yes Yes Yes Yes No 10 year VT
RO Water Yes No No No Yes NO VT
Seal Water Yes No No No Yes NO VT
Softened Water Yes No No No Yes NO VT
Stripped Sour Water Yes Yes Yes Yes No 10 year VT
Sour Water Yes Yes Yes Yes No 10 year VT
Tempered Water Yes No No No Yes NO VT
Treated Water Yes No No No Yes NO VT
Utility Water Yes No No No Yes NO VT
Wash Water Yes No No No Yes NO VT
OTHER SYSTEMS
Nitrogen Yes No No No Yes NO VT
Instrument Air Yes No No No Yes NO VT
Utility Air Yes No No No Yes NO VT
Plant Air Yes No No No Yes NO VT
Page 20 of 36
APPENDIX “H”
PIPING CIRCUIT DESIGN DATA NEEDED IN MERIDIUM
Time of Entry
When Plant is
First Created
When Piping
Operational
Entity First
When TML
Created
# Meridium Field View COMMENTS
BASIC ASSET REGISTRY DATA (Responsibility of the ACD Coordinator)
(Assumes that Maximo Registry Data has successfully been populated in Meridium)
1 Description From M’trl & Design X
2 Description To M’trl & Design X
3 Pipe Material M’trl & Design X Use Primary Material on ISO
BASIC LOCATION REGISTRY DATA (Responsibility of the ACD Coordinator)
1 API-570 Pipe Class Identification X From Piping Isometric
2 Refinery Pipe Class (or classes) Identification X From Piping Isometric
3 Service Code Identification X From Piping Isometric
4 Service Description Identification X From Piping Isometric
5 Normal Operating Temperature Identification X From INDX (or SME)
6 Normal Operating Pressure Identification X From INDX (or SME)
BASIC RBI REGISTRY DATA (Responsibility of the ACD Coordinator)
1 Design Temperature Component X From Upstream Equipment
2 Design Pressure Component X From Upstream Equipment
3 Representative Fluid Component X From Upstream Equipment
4 Initial Fluid Phase Component X From Upstream Equipment
5 Toxic Fluid Component X From Upstream Equipment
6 Percent Toxic Component X From Upstream Equipment
7 Inventory (use 50,000) Component X Use Default of 50,000
8 Associated PRD (if known) Relationship X From Piping Isometric
NOTES:
Currently we have done very little Piping RBI and most piping RBI data will come from a Process Engineer or other SME.
However, the items listed above should be captured at the initial Tech Data entry into Meridium in order to maintain the Initial
set of data which Tim Smith originally captured.
BASIC PIPING PLAN REGISTRY DATA (Responsibility of the ACD Coordinator)
1 ??
NOTES:
Piping Plans are still in Filemaker as of May 2009.
After Plans are moved to Meridium, then we should review this section and determine what data should be entered into
Meridium as basic tech data to support the piping plans. (This is a FUTURE RFMS Project which is pending)
BASIC TML CM DATA (Responsibility of the OSI Data Entry Analyst)
1 Datapoint ID (TML Number) CM Module X TML Number from Isometric
2 Brass Tag (Location ID) CM Module X From Piping Isometric
3 Nominal Size CM Module X From Piping Isometric
4 Tmin (Minimum Value) [see Note “A”] CM Module X From Tmin Database (or default)
5 Status Indicator (A, I) CM Module X From Piping Isometric
6 Datapoint Type (Pipe, Elbow, etc) CM Module X From Piping Isometric
7 Datapoint Access [see Note “B”] CM Module X From Piping Isometric
8 Insulation [see Note “B”] CM Module X From Piping Isometric
9 TML Pipe Class (R’fry) [see Note “C”] CM Module X From Piping Isometric
10 Measurement Method [see Note “D”] CM Module X From Piping Isometric
NOTES:
NOTE “A”: Need to tighten up on Piping Tmin’s in CM for new TML’s
Page 21 of 36
APPENDIX “H”
PIPING CIRCUIT DESIGN DATA NEEDED IN MERIDIUM
Time of Entry
When Plant is
First Created
When Piping
Operational
Entity First
When TML
Created
# Meridium Field View COMMENTS
1. When new TML’s on existing circuits or New TML’s on New Piping Circuits are added to CM we have had the tendency in
the past just to use the default Tmin’s (also the case when existing inactive TML”s are activated)
2. This opens the door for creating “out-of-compliance” issues due to negligence on our part (i.e. have a default Tmin on a
high pressure piping circuit.
3. Our standard work process from now on needs to insure proper Tmin’s (with comments) are entered into CM at the time
the New TML is created
NOTE “B”: Every new TML has an associated Datapoint Access and Datapoint Insulation field
1. In the past we would use defaults on these - - the Datapoint Access was set to “GRD” and the Insulation was set to the
same as the Piping Isometric [sometimes] without verification of the specific TML situation.
2. We are now at the place that we need to insure the accuracy of this data
3. Therefore from now on this data has to be field verified and cannot be left blank
4. There are three method’s of field verification:
a. Request the Area Inspector to provide the data at the time they assign the new TML’s
b. Have an NDE crew member do a field walk of the new TML’s and bring back the data to drafting
c. Have our RFMS drafting personnel do a field walk of the new piping circuit and then update the Isometric
5. BOTTOM LINE: from now on no default data is to go on the Piping Isometric for new TML’s - - it must be verified.
NOTE “C”: TML Pipe Class Procedure
1. All NEW TML’s and all TML replacements need to have a Refinery Pipe Class entered for that TML
2. This data is easily obtained from the Piping Isometric - - if not see the RFMS draftsperson.
3. This data is essential to generating an appropriate Tmin for that TML
4. From now on, it is a part of the OSI Data Entry Analyst’s responsibility to see that this data in entered into CM (refer to
Appendix “A”.)
NOTE “D”: Measurement Method Defaults
1. Due to the high cost of RT as opposed to CGUT and the high cost of CGUT versus FPUT the following procedures are to
be followed.
2. Refer to Appendix “P” for procedure
Page 22 of 36
APPENDIX “J”
PIPING CIRCUIT SYSTEM LEVEL ENTITIES
The Three Purposes (or Usages) of System Level Piping Entities in Meridium
“A” - - FIRST OF THE THREE PURPOSES - (All Systems with Standard Piping Isometrics)
• All three purposes build on the idea of using the "-000" piping entity as a system level record
• The "-000" piping entity then serves as a method of writing History Briefs at a system level
• In particular, we use it for our "External Visual Monitoring" Task in Meridium
• All of our piping circuits have to have an External Visual Monitoring Inspection every 5 years (10 years if API-
Class 3 or Utility)
• This means that at the circuit level we would be writing about 10,000 history briefs every 5 years (i.e. 2,000 a
year)
• If instead, we write one history brief at the System level we would need only 1,000 history briefs every 5 years
(200 a year)
• BOTTOM LINE: The great majority of our systems are standard piping isometrics - - all CM data is to be
recorded at the circuit level and the "-000" entity for a system is to be reserved for the History Briefs and
External Visual Monitoring Tasks
NOTE: We do not need and do not want any RT or UT data recorded on these "-000" entities.
“B” - SECOND OF THE THREE PURPOSES - (All Systems using Marked up P&ID’s AND needing NDE)
• These systems will use Highlighted P&ID’s to identify the Circuits and will use Digital Photographs to identify
the TML locations.
• BACKGROUND INFORMATION:
Dan Mason back in 2006 (along with an El Segundo representative, and I assume, representatives of other
refineries in California) negotiated with the State of California about a revised State Safety Order that was
requiring inspections above and beyond that required by API-570
Essentially the state was requiring an inspection program for Utility lines (not required by API-570)
After our Reliability Manager (Brian Garber at that time), the FER Lead (Dan Mason) and the RFMS Lead
(Tom Wisherop) had reviewed all the consequences of the revised State Safety Order it was determined that
we could comply with the Safety Order and yet save money by doing the following:
Instead of spending hundreds of thousands of dollars (perhaps 700K to 800K) on creating additional Inspection
Isometrics on all the Steam Lines in the Refinery
We decided instead to HIGHLIGHT the line on a P&ID
then scan the highlighted P&ID into a PDF document and link to our Circuit WEB page.
we would then take a digital photograph or two of the location that we wanted a TML (only one TML per line)
All the TML's would then be located at the system level
Hence all the CM data for the 150# Steam System in a plant could be found at one location in Meridium CM
Otherwise, if the plant had twenty 150# Steam lines we would have ended up with 20 entities in Meridium each
with a single TML
Thus in the example above we are using the "-000" entity for the 150# Steam System to capture all the CM data
for the entire plant
NOTE: For these System Entities we DO want all CM data at the System (not Circuit) level [and can still
do History Briefs at the System level as needed].
“C” - THIRD OF THE THREE PURPOSES - (All Systems using Marked-up P&ID’s BUT don’t need NDE)
• These are systems which require a ten year External Visual Monitoring Inspections)
• The Highlighted P&ID’s will be linked to the WEB
• Only the System Level Entity will be populated in Meridium
• The only Task on these System Entities should be the “External Visual Monitoring” Task
Page 23 of 36
APPENDIX “K”
Expectation of the Four Personnel who are Key to Effective RFMS Data Analysis
# Expectation COMMENTS
Number One: The NDE Crew (with regard to RFMS CM Data and its Analysis)
1 Expected to have • It is expected that the NDE Crews have adequate NDE training to perform the tasks
adequate NDE needed for capturing our OSI data
Training • This training is the responsibility of the Vendor
2 Expected to have • It is expected that the NDE Crews have adequate Safety training to perform the tasks
adequate Safety needed for capturing our OSI data in a safe manner
Training • This training also is the responsibility of the Vendor
3 Expected to be This includes:
able to read & • Inspection Piping Isometrics
understand our • Inspection Equipment Drawings
RFMS OSI • NDE Recording Sheets
program • Etc.
documentation
4 Expected to This includes such items as:
discover, record • Discrepancies between Inspection Piping Isometrics and “as-built” piping in the field
and report • Inadequate location of TML’s in the field
discrepancies on • Wrong Insulation and Staging data on TML bubbles on the Piping Isometric
OSI documentation • Problems with being able to perform the required NDE on a particular TML
• Etc.
5 Expected to This involves being able to:
understand, record • Recognize Tmin issues or High corrosion issues (this means recognizing abnormal loss
and report “Finds” between the field reading and the previous reading)
• Performing a double check of data
• Doing expanded coverage as needed to gather additional data
• Immediate reporting of the “find” to the NDE Crew Lead or to the OSI Coordinator
6 Expected to This involves being able to:
understand, record • Recognize such issues as abnormal loss, and abnormal growth
and report • Performing a double check of data
“Significant • Doing some common sense sleuthing such as:
Discrepancies” 1. Am I on the wrong location
2. Is there any evidence that the piping has been replaced
3. Could the previous reading been taken on the wrong location - - i.e. a fitting rather
than the pipe.
REMEMBER: The NDE Tech in the field is the First Line of Defense against bad or misunderstood data
Number Two: The NDE Crew Lead (with regard to RFMS CM Data and its Analysis)
1 Other Duties It is recognized that the NDE Crew Lead has other duties; however, a part of his duties is a
responsibility for the efficient gathering of NDE data and the “Quality Assurance” necessary
to provide for the integrity of the data collected
2 Expected to This training includes:
provide training • The “fine-tuning” of craft skills where needed
to NDE Crews in • The training in how to go about their job in the Chevron Richmond Refinery so as to
certain areas avoid wasted effort and maximize efficiency
• The collaboration with the OSI Coordinator so as to train or inform crews of priorities and
scheduling issues
• To see that all NDE Crews understand their responsibility to “Record” and “Report” any
of the items listed under the “NDE Crew” Expectations above
1. Discrepancies on Inspection Piping Isometrics & Equipment Drawings
2. The quick reporting of “finds”
3. The recording and reporting of “Significant Discrepancies”
3 Expected to This Analysis should include:
Page 24 of 36
APPENDIX “K”
provide analysis • A review of film for “Quality Assurance”
of NDE Crew work 1. Is the crew bringing in good film
2. i.e. is their skill adequate or is additional training needed
• A review of crew follow-up for “Data Analysis” & “Data Reporting”
1. Is the crew properly handling the “finds”
2. Is the crew properly handling the data “discrepancies”
3. Is the crew properly handling the drawing “discrepancies”
• Follow up of “Issues” in data
1. Do the crews need to go back out for expanded coverage
2. Do the crews need to recheck data or get missed data
4 Expected to Field support may be needed under certain conditions:
provide field • Does a crew need an audit of its results
support of NDE • Does a crew need an extra hand to get data in a timely manner
Crews • Does a crew need additional expertise on a difficult TML
• Does a crew need higher level representation with a customer or plant
REMEMBER: The NDE Crew Leader turns a set of disparate crews into a team. He provides the needed
interface with the overall OSI program to insure each team is working towards the common goal.
Number Three: The OSI Data Entry Analyst (with regard to RFMS CM Data and its Analysis)
1 Expected to The OSI Data Entry Analyst is directly responsible to the OSI Coordinator in several areas:
interface with OSI • For providing the Crews with their work packages (i.e. drawings and recording sheets)
Coordinator • For inputting measurement data from the field into the CM database
• For doing an initial analysis of newly inputted CM data
• For communicating data issues to the OSI Coordinator (i.e. Tmin issues; Remaining Life
issues; OERI issues, etc.)
2 Expected to The OSI Data Entry Analyst is also directly responsible to the NDE Crew Lead in several
interface with NDE areas:
Crew Lead • For keeping the Lead informed of data issues and data follow-up
• For keeping the Lead informed of Crew issues that come to her desk
• For serving as the NDE Crew Lead’s “eyes” and “ears” in a variety of office related work
3 Expected to The OSI Data Entry Analyst is responsible for certain data entry analysis and follow-up:
perform an Initial • New data entered in CM may generate two categories of Issues
Analysis or Audit of • FIRST CATEGORY: “URGENT Issues”
data going into CM 1. Remaining Life less than one year (this includes Tmin issues where the Remaining
- - [Urgent Issues] Life would be zero)
2. Corrosion rates greater than 50 mpy
3. Wall loss greater than 40 mpy
• These three issues require the following response
1. Review data for data entry issues (short cycle, etc.)
2. Notify the OSI Coordinator immediately (within 24 hours) in person (face-to-face or
phone) and provide all available data
3. And notify the NDE Crew Lead (in person or via E-mail)
4 Expected to • SECOND CATEGORY: “ROUTINE Issues”
perform an Initial 1. Remaining Life less than five years (but greater than one year)
Analysis or Audit of 2. Corrosion rates greater than 30 mpy (but less than 50 mpy)
data going into CM 3. Wall growth greater than 40 mpy
- - [Routine 4. Short Cycles less than one year if they affect Rem. Life
Issues] • These issues require the following response
1. Review data for data entry issues (short cycle, etc.)
2. Notify the NDE Crew Lead within 3 days if additional NDE action is needed
3. Work with the OSI Coordinator to determine if RFMS can resolve data in house.
5 Expected to Utilize The new Access database for Capturing CM Data Issues should be utilized as follows:
new Access
Page 25 of 36
APPENDIX “K”
Database •Refresh the database after every major data entry session (an no less than once per
“Analysis” aid week)
• Review all new issues that show up
• Insure that note or check box indicates that issue was reviewed
• Correct all data issues that are correctable - - i.e. data entry errors, short cycles, etc.
• A note needs to go in the comment box on how issue is being handled if it can’t be
resolved immediately
REMEMBER: The OSI Data Entry Analyst is the First Person to see the consequence in Meridium of the
effects of the New Data entered and the First Person to be able to catch Data Entry errors.
Number Four: The OSI Coordinator (with regard to RFMS CM Data and its Analysis)
1 Expected OSI Among other duties, the OSI Coordinator has the following OSI responsibilities:
Coordinator • Oversee the scheduling of the Annual OSI Program (both piping & Equip)
Responsibilities • Oversee the administration (i.e. execution) of those programs
• Oversee the communication of OSI Program results to the customers
• Each of these three areas operates from a dedicated database
2 Expected The Scheduling Tool:
scheduling • The scheduling tool (currently in Filemaker Pro) needs to be moved to Access
responsibilities • The OSI Coordinator needs to be fully operationally capable on this tool
• The long range plan is that all scheduling of Piping TML’s be handled by the OSI
coordinator
• This plan is to be put into effect in conjunction with the RFMS Computer Support
personnel
NOTE: This will be a separate OSI Scheduling Database for Piping and for Fixed equipment
3 Expected The Administration Tool:
Administration • The administration tool is currently in Filemaker Pro
• This tool currently provides the status of the piping OSI program
NOTE: This tool should be moved to an Access Database in the future and this will be
accomplished by RFMS Computer Support personnel.
4 Expected The Communication Tool:
Communication • This tool has not previously existed but is expected shortly in an MS Access version
• This tool will provide the ability to query Meridium and bring up all CM issues.
• The following standard communications are the responsibility of the OSI Coordinator
1. Communication within three days of all “URGENT” CM issues - - see APPENDIX “E”
for Urgent CM issues.
2. Communication within thirty days of all “ROUTINE” CM issues - - again see
APPENDIX “E” for Routine CM issues.
3. Communication of all issues belonging to a Plant when the OSI yearly program for
that plant has been completed.
NOTE: As mentioned above this tool will be shortly available - - perhaps some
communications features can be added if this will facilitate the OSI program.
REMEMBER: The OSI Coordinator is the person that is accountable for the success of the OSI effort. Also
the OSI Coordinator serves both as the interface between RFMS and its Chevron customers and as the
interface between RFMS and the NDE Vendor companies.
Page 26 of 36
APPENDIX “L”
RFMS Drafting: Details of Handling MOC Updates and New Isometrics
CHECKLIST OF ITEMS TO ADDRESS FOR MOC PIPING ISOMETRIC UPDATES

# ITEM COMMENTS
1 Print copy of the updated Inspection Piping • Print from the E-mailed links from the
Isometric Drafting Group
2 Compare printed copy with the previous revision to • Sometimes highlighted mark-ups are
identify the changes available from the drafting department but
this is not always the case.
• Be very thorough in your comparison so that
nothing is missed
3 Highlight all changes so that the changes are • This highlighted drawing serves as an
distinguished from the piping which is unchanged alternative to the one sometimes provided
by the Refinery Drafting group
4 Insure that any piping changes are identified on the • This is one of the original requests from
drawing with a three line label: i.e. “NEW”, “DATE”, FXD Inspection when moving from hand
“PIPE CLASS” sketches to electronic drawings
5 If piping change is “IN-KIND” or nearly “IN-KIND” then: • Items for “IN-KIND” changes
Restore all Active TML’s if removed by Drafting • For handling of gathering of baseline
Delete all Inactive TML’s measurement data refer to Appendix “A”
Provide the OSI Data Entry Analyst Support
Person with mark-up so replacement flags can
be set in CM and affected Inactive TML’s can
be deleted from CM
6 If piping change is “NOT In-Kind” then: • Items for “NOT-IN-KIND” changes
Interact with appropriate Area Inspector to • For handling of gathering of baseline
determine TML changes needed measurement data refer to Appendix “A”
Update Isometrics per Area Inspector input • Insure that any TML changes (i.e. additions)
Provide mark-up to OSI Data Entry Analyst for have the Staging and Insulation data
CM update validated
CHECKLIST OF ITEMS TO ADDRESS FOR NEW DRAWINGS

# ITEM COMMENTS
1 Add Note to drawing i.e. “This Circuit is New as of ‘DATE’”
2 Interact with the appropriate Area Inspector to • See if Area Inspector can provide staging
assign TML’s and insulation data for the newly assigned
TML’s
3 CAD TML’s to Isometric based on Area Inspector • Insure that all new TML’s added to the
mark-up drawing have accurate staging and
insulation information.
4 Provide copy of Updated Isometric with TML’s to • Need Baseline data
OSI Coordinator • Need Field check of TML Insulation status
• Need Field check of TML Staging Type
5 Provide copy of Updated Isometric with TML’s to • Need TML Design Data Inputted right away
OSI Data Entry Analyst • This insures that if Field Measurement Data
doesn’t get completed then the TML will be
picked up on the next years OSI program
CHECKLIST OF ITEMS TO ADDRESS FOR RELABELED DRAWINGS

# ITEM COMMENTS
1 Crosshatch the old drawing and have note added
that references the new drawing
2 Create the New Drawing and have note added that
Page 27 of 36
APPENDIX “L”
RFMS Drafting: Details of Handling MOC Updates and New Isometrics
references the old drawing.
3 Have ACD Coordinator “RETIRE” the old drawing
and add new drawing to Maximo / Meridium
4 Mark up any revised or new cross-references on the
P&ID and submit mark-ups to Refinery Drafting
5 Provide copy to OSI Data Entry Analyst for ensuring
that the CM data on the old drawing is moved over
to the New Drawing
CHECKLIST OF ITEMS TO ADDRESS FOR DRAWINGS WITH TRANSFERRED DATA

# ITEM COMMENTS
1 Move section of existing drawing that is to be • The second existing drawing may need to be
transferred over to the second existing drawing enlarged from an “A” size (letter size) to a “B”
which is to receive the transferred section. size drawing.
2 Move all TML’s on the transferred section of piping
over to the second drawing.
3 Renumber the moved TML’s if necessary • The transferred TML’s are the ones to be
renumbered if needed - - not the TML’s
which already existed on the isometric.
4 Provide mark-up copy of both drawings to the OSI
Data Entry Analyst for transfer and updating of CM
data as needed.
5 RFMS Drafting to update WEB as needed
6 RFMS Drafting to mark-up P&ID’s and submit to
Refinery Drafting group as needed.
Page 28 of 36
APPENDIX “M”
OSI CM: Checklist of Items to Review for TML ACD in Meridium
[OSI Coordinator is accountable; OSI Data Entry Analyst is responsible]
“A” - DRAWING DELETIONS: CHECKLIST OF ITEMS TO ADDRESS

# ITEM COMMENTS
1 Insure that RFMS Drafting has added a large • This is a needed check by the OSI Data
deletion note or crosshatching to the drawing Entry Analyst before proceeding in order to
avoid deleting data on the wrong Piping
Isometrics
2 Delete ALL CM data (both TML’s and • If the piping doesn’t exist then neither
Measurements) should any piping data in CM
3 Have ACD Coordinator “RETIRE” the piping asset in
Maximo / Meridium
“B” - DRAWINGS “Out-of-Service”: CHECKLIST OF ITEMS TO ADDRESS
# ITEM COMMENTS
1 Check that Drawing has large note saying “OUT- • This is the First of Two checks that are
OF-SERVICE” needed
2 Check that the Drawing shows that the Piping is • This is the Second of Two checks that are
Positively Isolated from any other active piping needed
• A “Positive” Isolation means that the line is
air gaped or is blinded
3 If the Piping Circuit is not Properly Isolated from a • It is RFMS drafting’s responsibility to
visual inspection of the line or if the Circuit has a determine whether the line is properly
note saying that it is “NOT ISOLATED” then isolated
Leave all TML’s active in CM • And also to add a note to the drawing if it is
Leave the drawing active in Registry not properly isolated
4 If circuit is properly isolated then Inactivate all TML’s • The drawing should also show all the TML’s
in Meridium CM to be inactive.
• At all times CM and the Piping Isometric
should be in sync
5 If properly isolated then have ACD Coordinator set
asset status to “INACTIVE” in Maximo / Meridium
“C” - DRAWINGS “Abandoned in Place”: CHECKLIST OF ITEMS TO ADDRESS
# ITEM COMMENTS
1 Check that Drawing has large note saying • This again is the First of Two checks that
“ABANDONED” are needed
2 Check that the Drawing shows that the Piping is • This is the Second of the Two checks that
Positively Isolated from any other active piping are needed
• A “Positive” Isolation means that the line is
air gaped or is blinded
3 If the Piping Circuit is not Properly Isolated from a • It is RFMS drafting’s responsibility to
visual inspection of the line or if the Circuit has a determine whether the line is properly
note saying that it is “NOT ISOLATED” then isolated
Leave all TML’s active in CM • And also to add a note to the drawing if it is
Leave the drawing active in Registry not properly isolated
4 If circuit is properly isolated then Inactivate all TML’s • The drawing should also show all the TML’s
in Meridium CM to be inactive.
NOTE: Do not delete CM data if circuit is abandoned. • At all times CM and the Piping Isometric
Abandoned circuits are sometimes reused and the CM should be in sync
data helps determine if they are fit for service.
Page 29 of 36
APPENDIX “M”
OSI CM: Checklist of Items to Review for TML ACD in Meridium
[OSI Coordinator is accountable; OSI Data Entry Analyst is responsible]
5 If properly isolated then have ACD Coordinator set
asset status to “RETIRED” in Maximo / Meridium
“D” - DRAWING ADDITIONS: CHECKLIST OF ITEMS TO ADDRESS
# ITEM COMMENTS
1 Have ACD Coordinator add piping asset to Maximo • If the piping doesn’t exist then neither
/ Meridium registry as an “ACTIVE” entity should any piping data in CM
2 Enter all the TML Design Data into Meridium • Obtain from the ACD Coordinator or the
NOTE: See Appendix “H” for list of TML Design Data RFMS Computer Support person an
that is necessary. “ACCURATE” Tmin
• Do not use the default Tmin unless verified
by an appropriate SME
• The RFMS Flag Tmin database can provide
the needed calculations
3 Enter all the appropriate Tmin Comments in the • See Appendix “B” for Sample Comments
Comment field for the TML’s and for proper formatting of the Comments
4 Check with the OSI Coordinator as to how to The following suggestions are guidelines only:
proceed to get Baseline data for the new circuit • If New Circuit comes from a project - - then
check with project to see if baseline data
NOTES: has been provided (it should have been)
(a) As a general rule DO NOT use “nominal” pipe • If New Circuit comes from an MOC or from
thickness for baseline data on New Circuits a missed line that the Drafting Group has
(b) Using Nominal thickness for Baselines should be drawn up for RFMS then use following
reserved for when there is adequate other CM data suggestions (see Appendix “A”):
on that circuit to understand the general corrosion • If circuit is API-Class 1 - - then get
rates. baseline.
• If circuit is API-Class 2 AND it is last half of
year - - then wait till TML’s shown up on
next year’s program to get baseline
• If circuits are low priority (i.e. utility or API
class 2 or class 3) - - then wait till next
year
• If Area Inspector needs baseline (upcoming
shutdown, etc.) - - then get baseline.
“E” - “Relabeled” DRAWINGS: CHECKLIST OF ITEMS TO ADDRESS
# ITEM COMMENTS
1 Work with the ACD Coordinator to insure that the
old drawing has been “RETIRED” or “DELETED” in
Maximo / Meridium
2 Work with the ACD Coordinator to insure that the
New drawing has been added to Maximo / Meridium
3 Move all CM data from the old entity in CM over to • In general: the CM data shouldn’t change -
the new entity in CM - just needs being moved over to new entity.
“F” - “Transferred Sections” of DWGS: CHECKLIST OF ITEMS TO ADDRESS
# ITEM COMMENTS
1 Move all TML’s data in CM which is on the
transferred section of piping over to the second
existing piping entity in CM
2 Renumber the moved TML’s if necessary • The updated Isometrics plus mark-ups
should provide all the needed data
Page 30 of 36
APPENDIX “N”
Authorized Tmin’s for Condensate and Steam Piping
PIPING Tmin to Use for STEAM PIPING (and Condensate)
=<2" 3" 4" 6" 8" 10" 12" 14" 16" 18" 20" 22" 24"
150#
STM (or
less 0.07 0.07 0.07 0.10 0.10 0.10 0.10 0.10 0.10 0.10 0.10 0.10 0.10
360#
STM 0.07 0.07 0.07 0.10 0.10 0.102 0.121 0.133 0.152 0.171 0.189 0.208 0.227
450#
STM 0.07 0.07 0.07 0.10 0.102 0.127 0.151 0.166 0.189 0.213 0.236 0.260 0.284
500#
STM 0.07 0.07 0.07 0.10 0.113 0.141 0.167 0.184 0.210 0.236 0.262 0.288 0.315
800#
STM 0.07 0.10 0.103 0.151 0.196 0.244 0.290 0.318 0.364 0.409 0.455 0.500 0.545
850#
STM 0.07 0.10 0.109 0.160 0.208 0.259 0.308 0.338 0.386 0.434 0.482 0.531 0.579
Design P Design T NOTES:
150# 150 250 • The Design Pressure and Design Temperature used for calculating Tmin's
are show to the left.
360# 360 450
• Design Pressure and Temperature for Steam / Condensate less than
450# 450 500 150# use the same Flag Tmin’s as does the 150#.
500# 500 500 • The above are all “Flag Tmin’s” and should be evaluated by an Engineer if
800# 800 550 any real Remaining Life issue is encountered.
850# 850 550
Page 31 of 36
APPENDIX “P”
TML NDE Measurement Method Matrix
Util. API-1 & 2 API-1 & 2 OSI S/D OSI S/D

and (General (Local Hot Hot INJ. INJ.
# PIPE SIZE API- 3 Corr.) Corr.) TML TML TML TML
1 <= 1.5” RT RT RT RT RT RT RT
2 2” Insulated RT RT RT RT RT RT RT
3 2” Un-insulated FPUT FPUT CGUT RT CGUT CGUT CGUT
2” to 8” Elbows RT /
4
(At Pipe Supports)
RT RT RT RT RT RT
CGUT
All other 2” to 8”
5
(Un-insulated)
FPUT FPUT CGUT RT CGUT CGUT CGUT
All other 2” to 8”
5
(Insulated)
FPUT FPUT RT RT CGUT RT CGUT
>8” goes to
6 All piping > 8” FPUT FPUT CGUT S/D
CGUT CGUT CGUT
GENERAL NOTES:
All piping should be FPUT if General Corrosion
If piping is subject to “Local Corrosion” or is an “Injection Point” TML then should be CGUT
EXCEPTIONS:
All OSI Hot Circuits should be RT’d (if Pipe is greater than 8” and is hot then needs to be S/D Hot Circuit)
All TML’s which are 1.5” in size or less or are 2” in size and insulated should be RT’d.
All TML’s which are 8” or less in size and are located at Elbows with Pipe Supports should be RT’d
Piping Circuits subject to “Local Corrosion” should use “RT” if insulated and are 8” or less in size.
GOALS:
Due to lack of instruction and guidelines, past assignment of NDE methods have varied a lot from the above
guidelines.
This results in many tens of thousands of dollars annually in additional OSI costs
An RFMS OSI goal is to review and realign NDE Measurements Methods to this guideline over the next few years
Page 32 of 36
APPENDIX “Q”
Chart of OSI Work Process
AREA INSPECTOR OSI/CUI COORDINATOR SITE SUPERVISOR OSI CREW
A1.1 B1.1 C1.1
Break In Work Identified by Develops OSI work packages
Area Inspector or Other from data pulled from CM Site Supervisor reviews
Customer daabase package or request to identify
Rope Access Package and,
Insulation removal Package C1.2
After Insulation
B1.2 Removal - - Work
OSI Analyst works with Site Package returned to
Supervisor Data Entry Person Site Supervisor for
to Review TML’s on Yearly review
Plan prior to creating work
Packages. Goal is to remove
any TML’s from yearly list that
C1.3
can be reconciled in CM
Insulation YES Work Package given
Removal to Insulation Crew for
Needed ? Insulation Removal
NO
A1.2 B1.2.1 B1.3 C1.4
NDE request is handed Sets Priorities for Is part
Places Plan on YES Site Supervisor
over with W/O number and crews and of Package
WEB and routes Isolates Rope Access
need date to Site produces work Rope Access
link to stakeholders Work and calls RAT
Supervisor packages Work ?
NO
To Site Supervisor
RT or MIX
Additional Determine
NDE whether RT or
NO Required? YES UT or MIX ?
C1.5 UT
Site Supervisor
Reviews concerns
with NDE Crew
NO
B1.4 C1.6 Give to Give to
Recycle as Needed Data Provided to OSI YES Preliminary Site Supervisor is UT Crew. RT Crew.
Analyst for Additional Review given data for NDE NDE
Preliminary Review Accepted? preliminary review performed performed
C1.7
E1.1
Data Returned to Site Tech Reviews
Supervisor with Any Thickness Data
Analyst Concerns
E1.2
Preliminary NO Tech Identifies any
Review Issues with NDE
Accepted? NO Drawing
Data or with
Correction
Needed ? Drawings and Turn
YES Package back to
Site Supervisor
YES
A1.3
B1.5 SITE SUPERVISOR DATA ENTRY PERSON RFMS DRAFTING
ANALYST
Plant Inspector
E-mails Finds to
Reviews Emergency
Area Inspector
Data with Analyst F1.1
Then follows-up
Reviews RL and CR Drafting Updates Drawings
with phone call
Reports at completion Drafting Updates WEB
Then delivers
of Plant Drafting Provides Data
results in person
Entry Person with Needed
D1.1 Updated Data
Data Submitted to
Site Supervisor Data
Entry Person for Input
Data Transmitter to Area Inspector as needed
Any
Follow up NDE into Meridium CM
Needed ?
YES
NO
OSI
Any
Analyst YES
Emergency
Notified Finds ?
A1.4 Immediately
Plant Inspector
Reviews Data in NO
Database
Reconciles Data as OSI Analyst
needed notified YES Any
Significant
within 24 Finds ?
hours
A1.5 NO
Plant Inspector writes OSI Analyst
Inspection notified
Recommendations as when Plant
needed is complete
OSI Complete OSI Complete

(AI Portion) (RFMS Portion)
Page 33 of 36
APPENDIX “R”
Definitions of Terminology Used in CM
[Preliminary Note: This is an older list of definitions and should be reviewed and updated, (or
discarded) prior to finalizing the draft version of this document - - however, this list is potentially
useful for understanding CM and for providing training]
Definitions
1. T-min - The minimum required pipe wall to not exceed code allowable stress values caused by any
load, i.e. internal pressure, temperature, structural, bending, foot traffic, thermal expansion, etc. T-min
is defined during a fitness for service review by a person knowledgeable in the appropriate piping
engineering standards and practices.
2. Internal Pressure Based T-min - The minimum required pipe wall to not exceed code allowable
stress values caused by internal pressure.
3. Throwaway Thickness - The Chevron Fitness For Service Guideline requires detailed and
documented engineering review before allowing piping to generally corrode below 0.100 inches
remaining wall thickness. The practical result is that we often replace pipe at scheduled turnarounds
to avoid going below 0.100 inches. This has earned it the title of “Throwaway Thickness.”
4. Flag Thickness - A minimum thickness used for half life calculations. Flag thickness is based on our
experience that corrosion is tricky to predict and our inspection techniques are imprecise. By setting a
conservative Flag Thickness, we have time to adequately review corrosion mechanisms and
economically plan for replacement at a planned turnaround. Since Flag Thickness is always equal to
or greater than the Throwaway Thickness, it helps us assure safe operation between turnarounds.
Flag Thickness for pipe 4.5 inches OD and below is 0.100 inches.
Flag Thickness for pipe over 4.5 inches OD is 0.140 inches. (However, upon review, it can be
reset to 0.100 inches.)
An experienced inspector may specify a more conservative Flag Thickness based on line history.
Acid lines are a common example.
5. Calculation Minimum Thickness - The thickness used in calculating API 570 half life dates.
Typically the higher of the Internal Pressure Based t-min or the Flag Thickness. The Calculation
Minimum Thickness is never less than t-min.
6. Base Reading - UT readings taken prior to the equipment being put into service. In Meridium
Condition Monitoring, the code tolerance for piping of plus or minus 12 and 1/2% would apply.
Similar tolerances for plate would apply per code allowables.
7. Initial Thickness - The first measured wall thickness after service has started.
8. Previous Reading - UT reading taken prior to the current reading.
9. Tolerance - A user specified range applied to a measured thickness, that indicates measured routine
UT losses or gains are not statistically significant (Error’s can be caused by location uncertainty,
calibration accuracy, temperature changes, technician error.)
10. Current Reading - The latest UT Data value entered into the database. In Meridium Condition
Monitoring, the user configurable, password access, tolerance will be used to screen out statistically
insignificant loss/gain from the half/quarter life calculations.
Page 34 of 36
APPENDIX “R”
Definitions of Terminology Used in CM
11. Long Term Corrosion Rate - Per API 570, the base reading thickness minus the most current
measured wall thickness divided by the time interval. (Use initial reading thickness if base reading is
not available.)
12. Short Term Corrosion Rate - Per API 570, the last measured wall thickness minus the most current
measured wall thickness divided by the time interval.
13. Half Life Date - Per API 570, the time at which a TML will loose half the remaining wall thickness
which is currently above the Calculation Minimum Thickness. (Twice the half life is when
Calculation Minimum Thickness will be reached.) The corrosion rate used to determine half life is the
greater of the Long Term and Short Term Corrosion Rates. Per API 570.
14. Original Nominal Wall Thickness - The wall thickness allowed by the original purchase
specification. (Purchase spec's usually allow +/- 12 1/2% variation from the nominal wall thickness.)
15. End Of Life Date - Date at which a Fitness For Service review indicates it is no longer appropriate to
leave the line in service.
16. Exceptions - Thickness readings which show exceptional loss, or gain, beyond that which would be
caused by reasonable corrosion rates or technique accuracy. Exceptions are also thickness readings
which are below the assigned Calculation Minimum Thickness.
17. Estimated Thickness - A corrosion rate based calculated thickness assigned to a TML.
18. Remaining Wall Thickness - The current total wall thickness at a TML.
19. Corrosion Allowance - The current wall thickness which exceeds the Calculation Minimum
Thickness.
Page 35 of 36
APPENDIX “S”
Form for Collection of Dummy Leg Data on Inspection Piping Isometrics
Enter Circuit ID: i.e. “0101-001-001”: Enter Number of Dummy Legs:
Enter Inspection Date: Enter Inspector Name:
ID Observations Access Req’rmnts Inspection Data Addition Inspection Data
Requires follow-up
Able to Inspect ?
Dummy Leg Size
Requires Slot or
Inspection OK ?
Needs Man-lift?
Needs Ladder?
Has Drain Hole
Needs Ladder
Needs Rope?
Compliance?
Hole /Slot in
Access from
Needs RT ?
Has Cap ?
Special?
Visual ?
Grade?
/Slot?
Cap?
Label INSPECTION COMMENTS
Enter (Y/N) (in) Enter (Y/N) Enter (Y/N)
DL#1
DL#2
DL#3
DL#4
DL#5
DL#6
• Fill out all data for each Dummy Leg on this Circuit • Dummy Leg Labels pre-populated on form: Use only the ones needed
• Dummy Legs to be numbered from Left to Right on the Circuit • Turn in copy of mark-up circuit showing the dummy legs along with this form - - To RFMS Drafting
Page 36 of 36

PIPING Work Processes

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

PIPING Work Processes

Încărcat de

Drepturi de autor:

Formate disponibile

RFMS PIPING DATA ENTRY & ACD GUIDELINE

RFMS - - RICHMOND REFINERY

I. PURPOSES OF THIS STANDARD

II. FOUNDATIONAL DOCUMENTS

A. MOC Piping Isometric Updates - - Origination

V. Details of Handling New Drawing Additions

D. NEW PIPING CIRCUITS (ACD Coordinator Responsibility)

E. NEW PIPING CIRCUITS (OSI Coordinator Responsibility)

F. NEW PIPING SYSTEMS

3. INSTRUCTIONS when Creating these System Level Entities

G. NEW PIPING CM DATA

VI. Details of Handling Drawing Deletions

A. Drawing Deletions are relatively uncomplicated

VII. Details of RFMS CM data entry and Analysis

VIII. Details of RFMS Hand-off of data Analysis to FXD Inspection

IX. Details of RFMS and FXD Inspection Co-usage of CM Database

A. Meridium CM data has two major users

X. Details of New Utility Piping Program (Implemented Since 2006)

XI. Details of RFMS OSI Workflow

A. Refer to Appendix “Q” for Chart of OSI Workflow

A. Standard Injection Point Circuits have two type of TML’s

A. Refer to the following two Documents for forms and instructions

C. Comments on External Visual Monitoring Inspections for Piping

Deleted, Delete / Move Change Circuit

Add TML’s Yes New

TML’s for New Circuits can’t Refer to Appendix “H”

END END END END

# Type of Comment Sample Comment

2 SAMPLE COMMENT FOR Tmin’s [Tmin NOTE (7/15/2006): Default Tmin is

4 SAMPLE COMMENT FOR Tmin’s [Tmin NOTE (7/15/2006): Uses RFMS

6 SAMPLE COMMENT FOR TRUE [Tmin NOTE (7/15/2006): Tmin provided by

I. Illustration of the Four Different Types of Tmin used in Piping CM

II. Discussion of the Four Different Types of Tmin used in Piping

MERIDIUM PIPING CM DATA

INSPECTION PIPING ISOMETRICS

RFMS PIPING WORK PROCESS

CHEVRON CALIFORNIA REFINING

PIPING INSPECTION CODE PIPING CONSTRUCTION CODE

OSI NDE Crew LAST UPDATE: Monday, May 11, 2009

Data is Delivered to OSI Coordinator Compares

CM flags YES YES

Tech confirms NO NO ALERT

API 570 Condition

CHECKLIST OF ITEMS TO ADDRESS FOR MOC PIPING ISOMETRIC UPDATES

CHECKLIST OF ITEMS TO ADDRESS FOR NEW DRAWINGS

CHECKLIST OF ITEMS TO ADDRESS FOR RELABELED DRAWINGS

CHECKLIST OF ITEMS TO ADDRESS FOR DRAWINGS WITH TRANSFERRED DATA

“A” - DRAWING DELETIONS: CHECKLIST OF ITEMS TO ADDRESS

Util. API-1 & 2 API-1 & 2 OSI S/D OSI S/D

OSI Complete OSI Complete

S-ar putea să vă placă și