Loading...
The URL can be used to link to this page
Your browser does not support the video tag.
Home
My WebLink
About
1.00 General Application Materials_Part10
ENGINEERING & LAND SURVEYING UELS, LLC Corporate Office * 85 South 200 East Vernal, UT 84078 * (435) 789-1017 REFERENCE AREA MAP REF TOPO LEGEND: SCALE PHOTO: VIEW FROM ABOVE REFERENCE AREA Inland Saltgrass, Western wheatgrass, Alkali bluegrass, Big sagebrush, Bottlebrush squirreltail, Nuttall's alkaligrass, Greasewood, Indian ricegrass, Mat saltbush, Winterfat REFERENCE AREA PLANT COMMUNITY DISTURBED GRASSLAND NATIVE GRASSLAND SHRUB LAND PLAINS RIPARIAN MOUNTAIN RIPARIAN FOREST LAND WETLANDS AQUATIC ALPINE OTHER (Describe): DOMINANT VEGETATION WITHIN THE REFERENCE AREA: 20 0 0 ' 10 0 0 ' 0'20 0 0 ' REFERENCE AREA (NAD 83) LATITUDE 39.539335° LONGITUDE -108.321337° R 98 W T6S 1 : 24000 SURVEYED BY DRAWN BY EXISTING LOCATION: SKR #698-10-BV PAD DAYTON SLAUGH 06-29-23 T.L.L.07-10-23 SKR #698-10-BV PADTRACT 72, SECTIONS 10 & 15, T6S, R98W, 6th P.M.GARFIELD COUNTY, COLORADO CHEVRON U.S.A. INC. WORKING PAD SURFACE REV: 1 08-02-23 T.L.L. (UPDATE TITLE BLOCK & LEGEND) 279 CAMERA ANGLE: NORTHERLY CAMERA ANGLE: EASTERLYPHOTO: VIEW OF REFERENCE AREA PHOTO: VIEW OF REFERENCE AREA UELS, LLC Corporate Office * 85 South 200 East Vernal, UT 84078 * (435) 789-1017 ENGINEERING & LAND SURVEYING REFERENCE AREA PHOTOS REF 1 TAKEN BY DRAWN BY DAYTON SLAUGH 06-29-23 T.L.L.07-10-23 SKR #698-10-BV PADTRACT 72, SECTIONS 10 & 15, T6S, R98W, 6th P.M.GARFIELD COUNTY, COLORADO CHEVRON U.S.A. INC. REV: 1 08-02-23 T.L.L. (UPDATE TITLE BLOCK) 280 CAMERA ANGLE: SOUTHERLY CAMERA ANGLE: WESTERLYPHOTO: VIEW OF REFERENCE AREA PHOTO: VIEW OF REFERENCE AREA UELS, LLC Corporate Office * 85 South 200 East Vernal, UT 84078 * (435) 789-1017 ENGINEERING & LAND SURVEYING REFERENCE AREA PHOTOS REF 2 TAKEN BY DRAWN BY DAYTON SLAUGH 06-29-23 T.L.L.07-10-23 SKR #698-10-BV PADTRACT 72, SECTIONS 10 & 15, T6S, R98W, 6th P.M.GARFIELD COUNTY, COLORADO CHEVRON U.S.A. INC. REV: 1 08-02-23 T.L.L. (UPDATE TITLE BLOCK) 281 9 Custom Soil Resource Report Soil Map SKR 698-10-BV Pad 43 8 0 0 4 0 43 8 0 0 8 0 43 8 0 1 2 0 43 8 0 1 6 0 43 8 0 2 0 0 43 8 0 2 4 0 43 8 0 2 8 0 43 8 0 0 8 0 43 8 0 1 2 0 43 8 0 1 6 0 43 8 0 2 0 0 43 8 0 2 4 0 43 8 0 2 8 0 729960 730000 730040 730080 730120 730160 730200 730240 730280 729960 730000 730040 730080 730120 730160 730200 730240 730280 730320 39° 32' 29'' N 10 8 ° 1 9 ' 2 7 ' ' W 39° 32' 29'' N 10 8 ° 1 9 ' 1 1 ' ' W 39° 32' 21'' N 10 8 ° 1 9 ' 2 7 ' ' W 39° 32' 21'' N 10 8 ° 1 9 ' 1 1 ' ' W N Map projection: Web Mercator Corner coordinates: WGS84 Edge tics: UTM Zone 12N WGS84 0 50 100 200 300Feet 0 25 50 100 150Meters Map Scale: 1:1,700 if printed on A landscape (11" x 8.5") sheet. Soil Map may not be valid at this scale. 282 Map Unit Legend Map Unit Symbol Map Unit Name Acres in AOI Percent of AOI 44 Happle very channery sandy loam, 3 to 12 percent slopes 5.5 86.6% 46 Happle-Rock outcrop association, 25 to 65 percent slopes 0.9 13.4% Totals for Area of Interest 6.4 100.0% Map Unit Descriptions The map units delineated on the detailed soil maps in a soil survey represent the soils or miscellaneous areas in the survey area. The map unit descriptions, along with the maps, can be used to determine the composition and properties of a unit. A map unit delineation on a soil map represents an area dominated by one or more major kinds of soil or miscellaneous areas. A map unit is identified and named according to the taxonomic classification of the dominant soils. Within a taxonomic class there are precisely defined limits for the properties of the soils. On the landscape, however, the soils are natural phenomena, and they have the characteristic variability of all natural phenomena. Thus, the range of some observed properties may extend beyond the limits defined for a taxonomic class. Areas of soils of a single taxonomic class rarely, if ever, can be mapped without including areas of other taxonomic classes. Consequently, every map unit is made up of the soils or miscellaneous areas for which it is named and some minor components that belong to taxonomic classes other than those of the major soils. Most minor soils have properties similar to those of the dominant soil or soils in the map unit, and thus they do not affect use and management. These are called noncontrasting, or similar, components. They may or may not be mentioned in a particular map unit description. Other minor components, however, have properties and behavioral characteristics divergent enough to affect use or to require different management. These are called contrasting, or dissimilar, components. They generally are in small areas and could not be mapped separately because of the scale used. Some small areas of strongly contrasting soils or miscellaneous areas are identified by a special symbol on the maps. If included in the database for a given area, the contrasting minor components are identified in the map unit descriptions along with some characteristics of each. A few areas of minor components may not have been observed, and consequently they are not mentioned in the descriptions, especially where the pattern was so complex that it was impractical to make enough observations to identify all the soils and miscellaneous areas on the landscape. The presence of minor components in a map unit in no way diminishes the usefulness or accuracy of the data. The objective of mapping is not to delineate pure taxonomic classes but rather to separate the landscape into landforms or landform segments that have similar use and management requirements. The delineation of such segments on the map provides sufficient information for the Custom Soil Resource Report 12283 9 Custom Soil Resource Report Soil Map SKR 698-10-BV Pad, Access Road, and Flowline/Pipeline 43 7 9 9 0 0 43 8 0 0 0 0 43 8 0 1 0 0 43 8 0 2 0 0 43 8 0 3 0 0 43 8 0 4 0 0 43 8 0 5 0 0 43 8 0 6 0 0 43 8 0 7 0 0 43 8 0 8 0 0 43 8 0 9 0 0 43 8 1 0 0 0 43 8 1 1 0 0 43 8 1 2 0 0 43 8 1 3 0 0 43 8 1 4 0 0 43 8 0 0 0 0 43 8 0 1 0 0 43 8 0 2 0 0 43 8 0 3 0 0 43 8 0 4 0 0 43 8 0 5 0 0 43 8 0 6 0 0 43 8 0 7 0 0 43 8 0 8 0 0 43 8 0 9 0 0 43 8 1 0 0 0 43 8 1 1 0 0 43 8 1 2 0 0 43 8 1 3 0 0 43 8 1 4 0 0 729300 729400 729500 729600 729700 729800 729900 730000 730100 730200 730300 729300 729400 729500 729600 729700 729800 729900 730000 730100 730200 730300 730400 39° 33' 6'' N 10 8 ° 1 9 ' 5 6 ' ' W 39° 33' 6'' N 10 8 ° 1 9 ' 7 ' ' W 39° 32' 16'' N 10 8 ° 1 9 ' 5 6 ' ' W 39° 32' 16'' N 10 8 ° 1 9 ' 7 ' ' W N Map projection: Web Mercator Corner coordinates: WGS84 Edge tics: UTM Zone 12N WGS84 0 350 700 1400 2100Feet 0 100 200 400 600Meters Map Scale: 1:7,510 if printed on A portrait (8.5" x 11") sheet. Soil Map may not be valid at this scale. 284 MAP LEGEND MAP INFORMATION Area of Interest (AOI) Area of Interest (AOI) Soils Soil Map Unit Polygons Soil Map Unit Lines Soil Map Unit Points Special Point Features Blowout Borrow Pit Clay Spot Closed Depression Gravel Pit Gravelly Spot Landfill Lava Flow Marsh or swamp Mine or Quarry Miscellaneous Water Perennial Water Rock Outcrop Saline Spot Sandy Spot Severely Eroded Spot Sinkhole Slide or Slip Sodic Spot Spoil Area Stony Spot Very Stony Spot Wet Spot Other Special Line Features Water Features Streams and Canals Transportation Rails Interstate Highways US Routes Major Roads Local Roads Background Aerial Photography The soil surveys that comprise your AOI were mapped at 1:24,000. Warning: Soil Map may not be valid at this scale. Enlargement of maps beyond the scale of mapping can cause misunderstanding of the detail of mapping and accuracy of soil line placement. The maps do not show the small areas of contrasting soils that could have been shown at a more detailed scale. Please rely on the bar scale on each map sheet for map measurements. Source of Map: Natural Resources Conservation Service Web Soil Survey URL: Coordinate System: Web Mercator (EPSG:3857) Maps from the Web Soil Survey are based on the Web Mercator projection, which preserves direction and shape but distorts distance and area. A projection that preserves area, such as the Albers equal-area conic projection, should be used if more accurate calculations of distance or area are required. This product is generated from the USDA-NRCS certified data as of the version date(s) listed below. Soil Survey Area: Douglas-Plateau Area, Colorado, Parts of Garfield and Mesa Counties Survey Area Data: Version 16, Aug 22, 2023 Soil map units are labeled (as space allows) for map scales 1:50,000 or larger. Date(s) aerial images were photographed: Jun 24, 2020—Jul 8, 2020 The orthophoto or other base map on which the soil lines were compiled and digitized probably differs from the background Custom Soil Resource Report 10285 MAP LEGEND MAP INFORMATION imagery displayed on these maps. As a result, some minor shifting of map unit boundaries may be evident. Custom Soil Resource Report 11286 Map Unit Legend Map Unit Symbol Map Unit Name Acres in AOI Percent of AOI 28 Cumulic Haploborolls, 1 to 3 percent slopes 0.4 1.2% 44 Happle very channery sandy loam, 3 to 12 percent slopes 15.9 45.0% 45 Happle very channery sandy loam, 12 to 25 percent slopes 2.6 7.4% 46 Happle-Rock outcrop association, 25 to 65 percent slopes 16.4 46.5% Totals for Area of Interest 35.3 100.0% Map Unit Descriptions The map units delineated on the detailed soil maps in a soil survey represent the soils or miscellaneous areas in the survey area. The map unit descriptions, along with the maps, can be used to determine the composition and properties of a unit. A map unit delineation on a soil map represents an area dominated by one or more major kinds of soil or miscellaneous areas. A map unit is identified and named according to the taxonomic classification of the dominant soils. Within a taxonomic class there are precisely defined limits for the properties of the soils. On the landscape, however, the soils are natural phenomena, and they have the characteristic variability of all natural phenomena. Thus, the range of some observed properties may extend beyond the limits defined for a taxonomic class. Areas of soils of a single taxonomic class rarely, if ever, can be mapped without including areas of other taxonomic classes. Consequently, every map unit is made up of the soils or miscellaneous areas for which it is named and some minor components that belong to taxonomic classes other than those of the major soils. Most minor soils have properties similar to those of the dominant soil or soils in the map unit, and thus they do not affect use and management. These are called noncontrasting, or similar, components. They may or may not be mentioned in a particular map unit description. Other minor components, however, have properties and behavioral characteristics divergent enough to affect use or to require different management. These are called contrasting, or dissimilar, components. They generally are in small areas and could not be mapped separately because of the scale used. Some small areas of strongly contrasting soils or miscellaneous areas are identified by a special symbol on the maps. If included in the database for a given area, the contrasting minor components are identified in the map unit descriptions along with some characteristics of each. A few areas of minor components may not have been observed, and consequently they are not mentioned in the descriptions, especially where the pattern was so complex that it was impractical to make enough observations to identify all the soils and miscellaneous areas on the landscape. Custom Soil Resource Report 12287 The presence of minor components in a map unit in no way diminishes the usefulness or accuracy of the data. The objective of mapping is not to delineate pure taxonomic classes but rather to separate the landscape into landforms or landform segments that have similar use and management requirements. The delineation of such segments on the map provides sufficient information for the development of resource plans. If intensive use of small areas is planned, however, onsite investigation is needed to define and locate the soils and miscellaneous areas. An identifying symbol precedes the map unit name in the map unit descriptions. Each description includes general facts about the unit and gives important soil properties and qualities. Soils that have profiles that are almost alike make up a soil series. Except for differences in texture of the surface layer, all the soils of a series have major horizons that are similar in composition, thickness, and arrangement. Soils of one series can differ in texture of the surface layer, slope, stoniness, salinity, degree of erosion, and other characteristics that affect their use. On the basis of such differences, a soil series is divided into soil phases. Most of the areas shown on the detailed soil maps are phases of soil series. The name of a soil phase commonly indicates a feature that affects use or management. For example, Alpha silt loam, 0 to 2 percent slopes, is a phase of the Alpha series. Some map units are made up of two or more major soils or miscellaneous areas. These map units are complexes, associations, or undifferentiated groups. A complex consists of two or more soils or miscellaneous areas in such an intricate pattern or in such small areas that they cannot be shown separately on the maps. The pattern and proportion of the soils or miscellaneous areas are somewhat similar in all areas. Alpha-Beta complex, 0 to 6 percent slopes, is an example. An association is made up of two or more geographically associated soils or miscellaneous areas that are shown as one unit on the maps. Because of present or anticipated uses of the map units in the survey area, it was not considered practical or necessary to map the soils or miscellaneous areas separately. The pattern and relative proportion of the soils or miscellaneous areas are somewhat similar. Alpha-Beta association, 0 to 2 percent slopes, is an example. An undifferentiated group is made up of two or more soils or miscellaneous areas that could be mapped individually but are mapped as one unit because similar interpretations can be made for use and management. The pattern and proportion of the soils or miscellaneous areas in a mapped area are not uniform. An area can be made up of only one of the major soils or miscellaneous areas, or it can be made up of all of them. Alpha and Beta soils, 0 to 2 percent slopes, is an example. Some surveys include miscellaneous areas. Such areas have little or no soil material and support little or no vegetation. Rock outcrop is an example. Custom Soil Resource Report 13288 Douglas-Plateau Area, Colorado, Parts of Garfield and Mesa Counties 28—Cumulic Haploborolls, 1 to 3 percent slopes Map Unit Setting National map unit symbol: jnv6 Elevation: 5,800 to 7,400 feet Mean annual precipitation: 12 to 18 inches Mean annual air temperature: 40 to 46 degrees F Frost-free period: 80 to 110 days Farmland classification: Prime farmland if irrigated and either protected from flooding or not frequently flooded during the growing season Map Unit Composition Cumulic haploborolls and similar soils:90 percent Minor components:10 percent Estimates are based on observations, descriptions, and transects of the mapunit. Description of Cumulic Haploborolls Setting Landform:Flood plains Down-slope shape:Linear Across-slope shape:Linear Parent material:Wasatch shale formation alluvium and/or green river shale formation alluvium Typical profile H1 - 0 to 8 inches: gravelly sandy clay loam H2 - 8 to 20 inches: very channery sandy clay loam H3 - 20 to 28 inches: clay loam H4 - 28 to 60 inches: stratified very gravelly sand to extremely gravelly loamy sand Properties and qualities Slope:1 to 3 percent Depth to restrictive feature:More than 80 inches Drainage class:Well drained Runoff class: Low Capacity of the most limiting layer to transmit water (Ksat):Moderately high to high (0.20 to 1.98 in/hr) Depth to water table:About 36 to 72 inches Frequency of flooding:Occasional Frequency of ponding:None Calcium carbonate, maximum content:10 percent Maximum salinity:Nonsaline to slightly saline (0.0 to 4.0 mmhos/cm) Available water supply, 0 to 60 inches: Low (about 4.6 inches) Interpretive groups Land capability classification (irrigated): None specified Land capability classification (nonirrigated): 4e Hydrologic Soil Group: B Ecological site: R048AY285CO - Foothill Swale Hydric soil rating: No Custom Soil Resource Report 14289 Minor Components Other soils Percent of map unit:10 percent Landform:Flood plains Down-slope shape:Linear Across-slope shape:Linear Hydric soil rating: No 44—Happle very channery sandy loam, 3 to 12 percent slopes Map Unit Setting National map unit symbol: jnvs Elevation: 5,200 to 6,000 feet Mean annual precipitation: 12 to 15 inches Mean annual air temperature: 46 to 52 degrees F Frost-free period: 100 to 150 days Farmland classification: Not prime farmland Map Unit Composition Happle and similar soils:80 percent Minor components:20 percent Estimates are based on observations, descriptions, and transects of the mapunit. Description of Happle Setting Landform:Alluvial fans Down-slope shape:Convex Across-slope shape:Linear Parent material:Green river formation alluvium derived from shale Typical profile H1 - 0 to 7 inches: very channery sandy loam H2 - 7 to 14 inches: very channery sandy loam H3 - 14 to 32 inches: very channery sandy clay loam H4 - 32 to 60 inches: extremely channery sandy loam Properties and qualities Slope:3 to 12 percent Depth to restrictive feature:More than 80 inches Drainage class:Well drained Runoff class: Medium Capacity of the most limiting layer to transmit water (Ksat):Moderately high to high (0.57 to 2.00 in/hr) Depth to water table:More than 80 inches Frequency of flooding:None Frequency of ponding:None Calcium carbonate, maximum content:10 percent Maximum salinity:Nonsaline to very slightly saline (0.0 to 2.0 mmhos/cm) Custom Soil Resource Report 15290 Available water supply, 0 to 60 inches: Low (about 3.4 inches) Interpretive groups Land capability classification (irrigated): None specified Land capability classification (nonirrigated): 4e Hydrologic Soil Group: B Ecological site: R034BY306UT - Upland Loam (Wyoming Big Sagebrush) Hydric soil rating: No Minor Components Cumulic haploborolls Percent of map unit:10 percent Hydric soil rating: No Debeque Percent of map unit:10 percent Hydric soil rating: No 45—Happle very channery sandy loam, 12 to 25 percent slopes Map Unit Setting National map unit symbol: jnvt Elevation: 5,400 to 6,200 feet Mean annual precipitation: 12 to 15 inches Mean annual air temperature: 46 to 52 degrees F Frost-free period: 100 to 150 days Farmland classification: Not prime farmland Map Unit Composition Happle and similar soils:80 percent Minor components:20 percent Estimates are based on observations, descriptions, and transects of the mapunit. Description of Happle Setting Landform:Mountains, alluvial fans Landform position (two-dimensional):Toeslope Landform position (three-dimensional):Mountainflank Down-slope shape:Convex Across-slope shape:Linear Parent material:Green river formation alluvium derived from shale and/or green river formation colluvium derived from shale Typical profile H1 - 0 to 7 inches: very channery sandy loam H2 - 7 to 14 inches: very channery sandy loam H3 - 14 to 32 inches: very channery sandy clay loam H4 - 32 to 60 inches: extremely channery sandy loam Custom Soil Resource Report 16291 Properties and qualities Slope:12 to 25 percent Depth to restrictive feature:More than 80 inches Drainage class:Well drained Runoff class: Medium Capacity of the most limiting layer to transmit water (Ksat):Moderately high to high (0.57 to 2.00 in/hr) Depth to water table:More than 80 inches Frequency of flooding:None Frequency of ponding:None Calcium carbonate, maximum content:10 percent Maximum salinity:Nonsaline to very slightly saline (0.0 to 2.0 mmhos/cm) Available water supply, 0 to 60 inches: Low (about 3.4 inches) Interpretive groups Land capability classification (irrigated): None specified Land capability classification (nonirrigated): 6e Hydrologic Soil Group: B Ecological site: R048AY303CO - Loamy Slopes Hydric soil rating: No Minor Components Toska Percent of map unit:10 percent Hydric soil rating: No Debeque Percent of map unit:10 percent Hydric soil rating: No 46—Happle-Rock outcrop association, 25 to 65 percent slopes Map Unit Setting National map unit symbol: jnvv Elevation: 6,200 to 7,200 feet Mean annual precipitation: 12 to 15 inches Mean annual air temperature: 46 to 52 degrees F Frost-free period: 100 to 150 days Farmland classification: Not prime farmland Map Unit Composition Happle and similar soils:50 percent Rock outcrop:35 percent Minor components:15 percent Estimates are based on observations, descriptions, and transects of the mapunit. Custom Soil Resource Report 17292 Description of Happle Setting Landform:Canyons, mountains Landform position (three-dimensional):Mountainflank Down-slope shape:Convex Across-slope shape:Linear Parent material:Green river formation colluvium derived from shale Typical profile H1 - 0 to 7 inches: very channery sandy loam H2 - 7 to 14 inches: very channery sandy loam H3 - 14 to 32 inches: very channery sandy clay loam H4 - 32 to 60 inches: extremely channery sandy loam Properties and qualities Slope:25 to 65 percent Depth to restrictive feature:More than 80 inches Drainage class:Well drained Runoff class: High Capacity of the most limiting layer to transmit water (Ksat):Moderately high to high (0.57 to 2.00 in/hr) Depth to water table:More than 80 inches Frequency of flooding:None Frequency of ponding:None Calcium carbonate, maximum content:10 percent Maximum salinity:Nonsaline to very slightly saline (0.0 to 2.0 mmhos/cm) Available water supply, 0 to 60 inches: Low (about 3.4 inches) Interpretive groups Land capability classification (irrigated): None specified Land capability classification (nonirrigated): 7e Hydrologic Soil Group: B Ecological site: R034BY334UT - Upland Stony Loam (Wyoming big sagebrush) Hydric soil rating: No Description of Rock Outcrop Typical profile H1 - 0 to 60 inches: unweathered bedrock Properties and qualities Slope:40 to 65 percent Depth to restrictive feature:0 inches to lithic bedrock Runoff class: Very high Capacity of the most limiting layer to transmit water (Ksat):Very low to low (0.00 to 0.00 in/hr) Available water supply, 0 to 60 inches: Very low (about 0.0 inches) Interpretive groups Land capability classification (irrigated): None specified Land capability classification (nonirrigated): 8s Hydric soil rating: No Custom Soil Resource Report 18293 Minor Components Other soils Percent of map unit:15 percent Hydric soil rating: No Custom Soil Resource Report 19294 APPENDIX L ECMC FORM 2A PLANS SKR 698‐10‐BV Pad Township 6 South, Range 98 West, 6th PM Sections 10 & 15: Tract 72 Garfield County, Colorado 295 PLANS AND CONSULATION SUMMARIES INCLUDED DOCUMENTS RULE COMMENTS Emergency Spill Response Plan 304.c.(1) This rule does not apply; not near Type III or GUDI well. Noise MiƟgaƟon Plan 304.c.(2) No RBUs within 2,000’. Refer to requested Lesser Impact Area ExempƟon request. Light MiƟgaƟon Plan 304.c.(3) No RBUs within 2,000’. Refer to requested Lesser Impact Area ExempƟon request. Odor MiƟgaƟon Plan 304.c.(4) This rule does not apply; no RBUs within 2,000’. Dust MiƟgaƟon Plan 304.c.(5) Transporta Ɵon Plan 304.c.(6) OperaƟons Safety Management Plan 304.c.(7) Emergency Response Plan 304.c.(8) Flood Shut‐In Plan 304.c.(9) This rule does not apply; not in a floodplain. Waste Management Plan 304.c.(11) Topsoil ProtecƟon Plan 304.c.(14) Stormwater Management Plan 304.c.(15) Interim ReclamaƟon Plan 304.c.(16) Wildlife Plan 304.c.(17) Water Plan 304.c.(18) CumulaƟve Impacts Plan 304.b.(19) Community Outreach Plan 304.b.(20) This rule does not apply; no RBUs within 2,000’. Geologic Hazard Plan 304.b.(12) Lesser Impact Area ExempƟon 304.c. CPW ConsultaƟon Summary 309.e. Summary of consultaƟons included. Garfield County ConsultaƟon Summary 302.g. Summary of consultaƟons included. 296 Dust Mitigation Plan Date: 11/10/2023 Location: OGDP SKR-698-10-BV / SKR-698-10-BV Pad Legal Description: Tract 72, SWSW Section 10 & NWNW Section 15, Township 6S, Range 98W, 6th PM, Garfield County, Colorado 297 Location Information This document provides site-specific information for the SKR 698-10-BV (Skinner Ridge) Pad (referred to as the “Pad”) located within the OGDP SKR 698-10-BV. A pre-application meeting with Garfield County, CDPHE, ECMC, CPW, and Chevron was held on October 12, 2023. This application will be an amendment to the existing SKR-66S98W/10 SWSW Pad, permitted with ECMC under location ID #336056. This Pad was initially permitted for the drilling and completion of 22 wells; however, those wells were never drilled. Instead, the location was utilized as the Skinner Ridge Storage Facility, permitted by both ECMC, under location ID #447846, and Garfield County, under permit LIPA 6428. The information in this document relates specifically to the time during the construction, drilling, completion, and production of the two (2) proposed horizontal wells on the well pad portion of the location and the construction and operation of the facility portion of the location, which will receive production from the two wells. Additionally, a pilot hole for geothermal testing will be drilled in one of the wells, but the pilot hole will be plugged prior to drilling the horizontal leg of the well. The existing location is located off Garfield County Road 211 (Clear Creek Road) approximately 16.7 miles northwest of De Beque, Colorado. The Pad lies on Tract 72, and is situated on two sections, the SWSW of Section 10 and the NWNW of Section 15, Township 6 South, Range 98 West, 6th P.M. zoned Resource Lands per Garfield County. The existing Skinner Ridge Storage Facility disturbance area is 6.2 acres, and an additional 0.7 acres of disturbance is proposed for construction of stormwater detention ponds and drainage channel at the SKR 698-10-BV Pad. The working pad surface (WPS) will be 3.8 acres. The Pad disturbance area will be reduced to 2.3 acres during interim reclamation. The Pad is located on Garfield County Parcel 213732100008 owned by Chevron U.S.A., Inc. The location is currently used as a storage yard and all storage equipment and facilities will be relocated prior to drilling the proposed wells. The wells on the SKR 698-10-BV Pad will produce to the proposed production facility portion of the location and be tied into Chevron’s existing Central Production Facility (CPF) via a proposed gas and liquids line. Proposed equipment on the Pad will include separators, pigging stations, a gas meter, pipe skid, an instrument air skid, a skid drain vault, a chemical injection skid, a communication tower, solar skids, a maintenance tank, heat trace equipment, a transformer or electric generators, switchracks, and a battery box. A temporary MLVT, located on the nearby Skinner Ridge-66S98W/22NENW Pad (Location ID# 324358), will be utilized for completion operations. Phase Duration (days) Estimated Start Date Construction (Daylight Only) 10 days 2nd Quarter 2024 Drilling 80 days 3rd Quarter 2024 Completion 23 days 3rd Quarter 2025 Flowback N/A Flowing back directly to permanent facility Production 30 years 3rd Quarter 2025 Interim Reclamation (Daylight Only) 60 days 2nd Quarter 2026 298 Potentially Impacted Parties The Working Pad Surface (WPS) of the SKR 698-10-BV Pad is within 2,000 feet of zero (0) Residential Building Units (RBUs), zero (0) High Occupancy Building Units (HOBUs), and zero (0) Designated Outside Activity Areas (DOAAs). The Pad is located within a Disproportionately Impacted Community (DIC). The location is within ECMC designated High Priority Habitat (HPH) per rule 1202.d for Elk Winter Concentration Area and Elk Severe Winter Range and rule 1202.c for Aquatic Sportfish Management Waters. Dust Mitigation Plan Specific Data Soils Pad Soil type(s), 6.9 Disturbed Acres (including 6.2 acres of existing Storage Facility): • 44 - Happle very channery sandy loam, 3 to 12 percent slopes; 46 - Happle-Rock outcrop association, 25 to 65 percent slopes Access Road Soil type(s)*, 0.1 Disturbed Acres: • 44 - Happle very channery sandy loam, 3 to 12 percent slopes; Flowline Corridor Soil type(s)*, 9.5 Disturbed Acres: • 28 - Cumulic Haploborolls, 1 to 3 percent slopes; 44 - Happle very channery sandy loam, 3 to 12 percent slopes; 45 - Happle very channery sandy loam, 12 to 25 percent slopes; 46 - Happle-Rock outcrop association, 25 to 65 percent slopes *NRCS data is not accurate at scale for access roads and flowline corridor. Total area of soil disturbance: 16.4 acres. The existing and proposed access roads are unpaved for approximately 0.2 combined acres before entering unpaved Garfield County Road 211 (Clear Creek Road). Truck Traffic and Cumulative Dust Impacts The table below estimates the number of anticipated truck trips for this location and the combined trips for the entirety of OGDP SKR-698-10-BV, which only includes the SKR-698-10-BV Pad. The trip counts are further divided by individual phase of field operation. Operations for the Pad will convey traffic along Garfield County Road 211 (Clear Creek Road). The daily number of trips will typically be split evenly amongst each day of an operation’s duration. However, the heaviest periods of vehicle traffic will occur during the first two and last two days of both drilling and completions, when additional equipment mobilization will occur. During these days, the trips per day will increase by approximately 80 Heavy Truck Trips and 40 Light Truck Trips. The production phase trips will encompass regular operations and maintenance over a period of 30 years. 299 SKR-698-10-BV Pad Baseline Traffic Summary Phase Heavy Truck Trips per Location Light Truck Trips per Location OGDP SKR-698-10- BV Pad Cumulative Trips Construction 207 98 305 Drilling 6,944 7,164 14,108 Completions 2,512 1,438 3,950 Interim Reclamation 465 50 515 Production* 0 10,950 10,950 *Note: Production trips will be combined for multiple locations within the Piceance Basin whenever possible. The expected travel route for the proposed oil and gas location is indicated on the attached Access Road Map. The travel distribution from the proposed oil and gas location will convey all traffic along Garfield County Road 211 (Clear Creek Road). Mitigation Measures and Best Management Practices Chevron shall employ practices for control of fugitive dust caused by their operations. Such practices shall include but are not limited to the use of speed restrictions, regular road maintenance, pipeline infrastructure to provide takeaway for oil, gas, and produced water (reducing number of trips from heavy trucks), silica dust controls when handling sand used in hydraulic fracturing operations1, and restriction of construction activity during high-wind days. The location will also feature automation of wells and production and this OGDP was designed around consolidation of production facilities, reducing excessive driving on undeveloped or unpaved roads. Chevron additionally has implemented the use of traffic signs when leaving the location to remind drivers of specific routes to utilize. • When Chevron is required to suppress dust, its selected vendor will be reminded of the following: o Use only fresh water sources (non-potable) when watering areas within 300 feet of the ordinary high-water mark of any water body. o Maintain a current Safety Data Sheet (SDS) in their company vehicle when using a dust suppressor containing chemicals, in accordance with OSHA Standard 29 CFR 1910.1200 (Hazard Communication) as well as local and State requirements. o Ensure watering practices are not creating additional hazards on access roads (slick roads, muddy conditions, etc.). • All soil piles created by construction activities will be managed utilizing Hydro-mulch, straw crimping, and/or tracking methods to prevent dust from exiting the location and creating a hazard during pre-production activities. Soil piles will be graded and/or seeded to prevent erosion and the generation of dust post-production. 1 Silica dust control will include dust suppression with non-potable water, well-ventilated work site, pre-planned personnel rotation of work site, as well as other recommended measures included in OSHA Standard 29 CFR 1926.1153 Respirable Crystalline Silica. 300 • Chevron will minimize the amount of fugitive dust using speed restrictions. All vehicles will be subject to a speed limit of 20 MPH on all lease roads to minimize dust. • Chevron will mitigate the creation of fugitive dust through regular road maintenance as coordinated through agreements with Garfield County and any Relevant Local Governments or Agencies with road jurisdiction. • Chevron will use methods including wind breaks and barriers, road or facility surfacing, and soil stockpile stabilization measures to suppress fugitive dust caused solely by wind. • Chevron will avoid the creation of fugitive dust by restricting or limiting construction activity during high wind days. • Chevron will minimize fugitive dust caused by operations or dust originating from areas disturbed by previous operations that becomes windborne by utilizing the dust suppression methods mentioned above. • Chevron will not use any of the following fluids for dust suppression: o Produced water o E&P waste or hazardous waste o Crude oil or any oil specifically designed for road maintenance o Chemical solvents o Process fluids • Access road(s) will be watered or treated with one of the following commercial dust suppressants, as needed: o Roadsaver (magnesium chloride) o Roadsaver Compaction Aid (magnesium chloride) o DuraBlend (magnesium chloride) • Prior to the application of dust suppressant to any county or public roads, coordination will be conducted with Garfield County Department of Public Works by Chevron and any relevant vendors. • Chevron will maintain safety data sheets (“SDS”) for any chemical-based dust suppressant and make the SDS immediately available upon request to the ECMC Director, Garfield County, and to any other Local Government or Agency. Safety Data Sheet(s) for any chemical-based dust suppressant will be archived and maintained until the site passes final site Reclamation and transfer the records upon transfer of property ownership. • All secondary roads created for this project (non-public roadways) will be finished with ½” – ¾” crushed stone road base. 301 • Silica dust from handling sand used in hydraulic fracturing operations will be mitigated by utilization of the enclosed Sand Box delivery systems. As such, no pneumatic transportation of sand will be conducted at this location. • Chevron will take all necessary and reasonable precautions to ensure that dust from the Oil and Gas Location does not unnecessarily impact the health, safety, and welfare of Wildlife occupying any High Priority Habitat within 2,000 feet of the Oil and Gas Location. These actions include: o Identify permanent and temporary housing of resident wildlife and ensure locations are recorded in wildlife reports kept in-house by HSE. o Conduct a daily walkthrough of the location during ongoing operations to ensure no wildlife have built nest(s) in/around equipment. If nest(s) are found, HSE reporting will be issued to appropriate personnel to either remove the nest and/or temporarily abandon the equipment until nest is abandoned. Supplemental Information Chevron will occasionally reach out to third-party vendors to help ensure compliance with all applicable standards. Below is the list of vendors who have been selected: Vendors • Envirotech Services, Inc. 3860 N. Revere St., Suite C 303.903.6079 Exhibits/References/Appendices Access Road Map 302 ACCESS ROAD MAP DRAWN BY SURVEYED BY WORKING PAD SURFACE UELS, LLCCorporate Office * 85 South 200 EastVernal, UT 84078 * (435) 789-1017ENGINEERING & LAND SURVEYING 80 0 ' 40 0 ' 0'80 0 ' OIL & GAS LOCATION (LOD) LEGEND ELK WINTER CONCENTRATION AREA NOTE: - PARCEL DATA SHOWN HAS BEEN OBTAINED FROM VARIOUS SOURCES AND SHOULD BE USED FOR MAPPING, GRAPHIC AND PLANNING PURPOSES ONLY. NO WARRANTY IS MADE BY UINTAH ENGINEERING AND LAND SURVEYING (UELS) FOR ACCURACY OF THE PARCEL DATA. - NO EXISTING RESIDENTIAL BUILDING UNITS WITHIN 2000' OF THE EXISTING ACCESS ROAD. PROPOSED ADDITIONAL ACCESS ROAD PROPERTY LINE 2000' OFFSET FROM EXISTING & PROPOSED ACCESS ROADS CO U N T Y R O A D 2 1 1 T6S R 98 W 16 15 109 AQUATIC SPORTFISH MANAGEMENT WATERS ELK SEVERE WINTER RANGE SCALE 1" = 500'T.L.L.07-10-23 DAYTON SLAUGH 06-29-23 EXISTING LOCATION: SKR #698-10-BV PAD PROPOSED ADDITIONAL ACCESS ROAD 140' +/- 1 2 EXISTING 18" CULVERT EXISTING GATE 1 2 SKR #698-10-BV PADTRACT 72, SECTIONS 10 & 15, T6S, R98W, 6th P.M.GARFIELD COUNTY, COLORADO CHEVRON U.S.A. INC. EXISTING ACCESS ROAD EXISTING ACCESS ROAD 388' +/- C L E A R C R E E K R O A D MAHOGANY ENERGY RESOURCES LLC CHEVRON USA INC BLM CHEVRON USA INC MAHOGANY ENERGY RESOURCES LLC CHEVRON USA INC CHEVRON USA INC CHEVRON USA INC MAHOGANY ENERGY RESOURCES LLCCHEVRON USA INC S E C T I O N L I N E SECTION LINE REV: 3 11-16-23 T.L.L. (UPDATE LOD) 303 Transportation Plan Date: 11/10/2023 Location: OGDP SKR 698-10-BV / SKR 698-10-BV Pad Legal Description: Tract 72, SWSW of Section 10 & NWNW of Section 15, Township 6 South, Range 98 West, 6th P.M., Garfield County, Colorado Location Details Chevron has initiated an oil and gas permit with Garfield County, and a pre-application meeting was held on October 12, 2023. During the pre-application meeting, Chevron provided access routes and other pertinent information related to traffic and transportation to Garfield County and other participants (ECMC, CPW, and CDPHE). As a result of these consultations, the access route provided in the enclosed Haul Route Map was agreed to by all parties, and Chevron committed to continuing the beneficial relationship with Garfield County regarding maintenance of CR 211. The approved access road and haul route are provided as attachments, and specific details of that approval are as follows – •Access to the SKR 698-10-BV Pad from public roads will be from County Road 211 (Clear Creek Road). Chevron commits to continuing the beneficial relationship with Garfield County regarding maintenance of CR 211. 304 The following table provides an estimate of the traffic associated with the various phases of development for the SKR 698-10-BV Pad. SKR-698-10 BV Pad Baseline Traffic Summary Phase Heavy Truck Trips per Location Light Truck Trips per Location SKR-698-10-BV Cumulative Trips Construction 207 98 304 Drilling 6,944 7,164 14,108 Completions 2,512 1,438 3,950 Interim Reclamation 465 50 515 Production 1 0 10,950 10,950 BMP: • At the time of construction, all leasehold roads shall be constructed to accommodate local emergency vehicle access requirements and shall be maintained in a reasonable condition. • Flowlines from the well pad to the production facilities will be constructed prior to starting flowback operations to eliminate truck traffic associated with flowback and production. • Production operations are continuously monitored remotely from Chevron’s Operations Control Center (OCC) to minimize the need for personnel to drive to the location. • A speed limit of 20 MPH will be enforced on the unpaved private roads. • Chevron will employ practices for control of fugitive dust caused by operations, including speed restrictions, regular road maintenance, restriction of construction activity during high wind days, and silica dust controls when handling sand used in hydraulic fracturing operations. Additional management practices such as road surfacing, wind breaks and barriers, or automation of wells to reduce truck traffic may also be used to minimize fugitive dust emissions. Attachments: Access Road Map Haul Route Map 1 Production trips will be combined for multiple locations within the Piceance Basin whenever possible. 305 PROPOSED HAUL ROUTE 4.2 Mi. ± HAUL ROUTE MAP SKR #698-10-BV PADTRACT 72, SECTIONS 10 & 15, T6S, R98W, 6th P.M.GARFIELD COUNTY, COLORADO CHEVRON U.S.A. INC. ENGINEERING & LAND SURVEYING UELS, LLC Corporate Office * 85 South 200 East Vernal, UT 84078 * (435) 789-1017 EXISTING LOCATION LEGEND: 20 0 0 ' 10 0 0 ' 0'20 0 0 ' T7S T6S EXISTING LOCATION: SKR #698-10-BV PAD R 98 W CL E A R C R E E K R D 4. 1 M I . + / - EXISTING ACCESS RD 0.1 MI. +/- CO U N T Y R D 2 0 4 REV: 2 11-07-23 T.L.L. (ADD ACCESS ROAD) RESIDENTIAL BUILDING UNIT DRAWN BY SURVEYED BY SCALE 1" = 2000'T.L.L.03-22-23 DAYTON SLAUGH 06-29-23 D E B E Q U E 1 2 . 5 M I . + / - EXISTING COUNTY RD 211 PROPOSED ACCESS ROAD 140' ± SEE DETAIL "A" DETAIL "A"N.T.S. PROPOSED ACCESS ROAD 140' ± EXISTING ACCESS RD 0.1 MI. +/- EXISTING COUNTY RD 211 CLEAR CREEK 0.1 MI. +/- 0.1 MI. +/- EXISTING SKR #698-10-BV PAD 306 Operations Safety Management Plan Date: 11/10/2023 Location: OGDP SKR 698-10-BV / SKR 698-10-BV Pad Legal Description: Tract 72, SWSW of Section 10 & NWNW of Section 15, Township 6 South, Range 98 West, 6th P.M., Garfield County, Colorado 307 Location Information This document provides site-specific information for the SKR 698-10-BV (Skinner Ridge) Pad (referred to as the “Pad”) located within OGDP SKR 698-10-BV. A pre-application meeting with Garfield County, CDPHE, ECMC, CPW, and Chevron was held on October 12, 2023. This application will be an amendment to the existing SKR-66S98W/10 SWSW Pad, permitted with ECMC under location ID #336056. This Pad was initially permitted for the drilling and completion of 22 wells; however, those wells were never drilled. Instead, the location was utilized as the Skinner Ridge Storage Facility, permitted by both ECMC, under location ID #447846, and Garfield County, under permit LIPA 6428. The information in this document relates specifically to the time during the construction, drilling, completion, and production of the two (2) proposed horizontal wells on the well pad portion of the location and the construction and operation of the facility portion of the location, which will receive production from the two wells. Additionally, a pilot hole for geothermal testing will be drilled in one of the wells, but the pilot hole will be plugged prior to drilling the horizontal leg of the well. The existing location is located off Garfield County Road 211 (Clear Creek Road) approximately 16.7 miles northwest of De Beque, Colorado. The Pad lies on Tract 72, and is situated on two sections, the SWSW of Section 10 and the NWNW of Section 15, Township 6 South, Range 98 West, 6th P.M. zoned Resource Lands per Garfield County. The existing Skinner Ridge Storage Facility disturbance area is 6.2 acres, and an additional 0.7 acres of disturbance is proposed for construction of stormwater detention ponds and drainage channels at the SKR 698-10-BV Pad. The working pad surface (WPS) will be 3.8 acres. The Pad disturbance area will be reduced to 2.3 acres during interim reclamation. The Pad is located on Garfield County Parcel 213732100008 owned by Chevron U.S.A., Inc. The location is currently used as a storage yard and all storage equipment and facilities will be relocated prior to drilling the proposed wells. The wells on the SKR 698-10-BV Pad will produce to the proposed production facility portion of the location and be tied into Chevron’s existing Central Production Facility (CPF) via a proposed gas and liquids line. Proposed equipment on the Pad will include separators, pigging stations, a gas meter, pipe skid, an instrument air skid, a skid drain vault, a chemical injection skid, a communication tower, solar skids, a maintenance tank, heat trace equipment, a transformer or electric generators, switchracks, and a battery box. A temporary MLVT, located on the nearby Skinner Ridge-66S98W/22NENW Pad (Location ID# 324358), will be utilized for completion operations. Phase Duration (days) Estimated Start Date Construction (Daylight Only) 10 days 2nd Quarter 2024 Drilling 80 days 3rd Quarter 2024 Completion 23 days 3rd Quarter 2025 Flowback N/A Flowing back directly to permanent facility Production 30 years 3rd Quarter 2025 Interim Reclamation (Daylight Only) 60 days 2nd Quarter 2026 308 Potentially Impacted Parties The Working Pad Surface (WPS) of the SKR 698-10-BV Pad is within 2,000 feet of zero (0) Residential Building Units (RBUs), zero (0) High Occupancy Building Units (HOBUs), and zero (0) Designated Outside Activity Areas (DOAAs). The Pad is located within a Disproportionately Impacted Community (DIC). The location is within ECMC designated High Priority Habitat (HPH) per rule 1202.d for Elk Winter Concentration Area and Elk Severe Winter Range and rule 1202.c for Aquatic Sportfish Management Waters. Requirements / Plan Elements The Operational Safety Management Program Plan explains how the Operator will comply with Rule 602.d. This Rule addresses changes made at an Oil and Gas Location or Facility regarding equipment, processes or procedures at start up or anytime equipment or processes are placed into or returned to operation. The CMP and PSSR components help ensure that changes to a process do not inadvertently introduce new hazards or unknowingly increase risk of existing hazards. The Operations Safety Management Program Plan should document how the operator has developed, implemented and maintains the following minimum requirements for each of the two key components of the program, the CMP and the PSSR. 1. Change Management Program (CMP) is a written document that addresses: a. How an Operator records changes to technology, equipment, and procedures; and changes to facilities that affect a process, and identifies: i. Where the records are stored; ii. How long records are kept; iii. How soon after a ECMC request the records can be provided; and iv. How often the records are updated. 309 b. The following must be documented for any change to technology, equipment, and procedures, and changes to facilities that affect a process: i. Identify the basis for the proposed change and why it is needed; ii. Identify the potential impacts to Public Health, Safety, Welfare, and the Environment: 1. That may occur from implementing the change; or 2. That may occur from not implementing the change; iii. The level at which employees are allowed to approve changes; iv. Identify if the change is permanent or temporary; and v. If the change is temporary, provide an estimate of how long the equipment or process will be in service. Change Management Program: Purpose and Objectives: The purpose of this Management of Change for Facilities and Operations (MOC-F&O) Process is to manage changes to facilities, operations, procedures and products to prevent incidents, support reliable and efficient operations, and to mitigate, or where possible, eliminate unacceptable risks from being introduced into our business. The objectives of this MOC-F&O process are to: • Define the requirements for permanent, temporary and emergency changes • Establish authority for approving changes • Provide a means to evaluate health, environmental and safety risks of potential changes and identify mitigation by competent experts • Require communication of the change • Required training of personnel impacted by changes to facilities, operations, procedures or products • Establish a mechanism for updates to and maintenance of process safety information (PSI) and other critical OE documentation. • Establish requirements on tracking and reporting of MOC-F&O Leading and Lagging Metrics • Establish requirements to document, track and verify progress 310 Scope: This process applies to all permanent, temporary and emergency changes to facilities, operations, procedures or products that occur at locations owned, operated, leased or controlled by Chevron including operated joint ventures and consolidated subsidiaries. This Management of Change for Facilities and Operations process must be applied when a change results in or is the result of changes to facilities, operations, procedures or products as defined in the Scope of this MOC Process. Procedures: • Changes to Operating and Maintenance procedures that affect the established operating state of the facility, operation, or product where the change could impact health, safety, environment, efficiency, or reliability • Changes to temporary repair procedures • Changing the sequence and the adding or deleting of steps within operating procedures. • Changing the safe operating limits in the operating procedures. • Relocating information on safe upper and lower limits, consequences of deviation, etc., from the operating procedure to a separate referenced document. • Creating a temporary operating procedure Management of Change Procedure: Description: The U&G Management of Change for Facilities and Operations Procedures provides the detailed steps for completing an MOC that is attached to this Operations Safety Plan. The procedure includes the following steps: • Request the Change • Approve to Proceed • Identify, Assign & Perform Functional and Risk Assessment Reviews • Approve to Make Change • Make the Change • Perform Pre-Start-up Safety Review • Approve for Startup • Close out MOC 311 • Temporary Change • Emergency Change Change Management Program Record Retention Management of Change documents are created and stored in the Stature software system. Records are maintained for the active life of the facility + a period of no less than 3 years. Detailed information for the retention period of different categories of process critical documents (information) can be found in table 1. Records are updated when a change has been approved and the change management process is initiated. Records pertaining to critical information about a change can generally be made available within 14 business days of the written notice of request. Critical Process Information The documents and data listed in Table 5 shall be managed and handled as defined by the U&G OEIM standard. Information Risk Management (IRM) Record Categories are established by Chevron Policy 566. Information Protection information classifications are established by the Enterprise Security Architecture System (ESAS) standard #S1336. ‘Critical’ information is all required process documentation and all information captured and created during the operation of the process. ‘Controlled’ is information that requires approval. Table 1. Critical Information U&G and SBU Determined Critical Information Information Protection Classification (IPC) Retention Category Information Format (Structured Unstructured) Process and Procedure documents and related guidance Company Confidential ADM6020 Active +7 years Unstructured Leading and lagging metrics and performance indicators Company Confidential ADM5000 5 years Unstructured Process and procedure related training records Company Confidential HRW8540 5 years Unstructured Process training materials Company Confidential HRW8530 Active +5 years Unstructured MOC Package (includes, but is not limited to, FR checklists, FRA reports, PSSR checklists, Training Records, Communication records) Company Confidential OPR2040 Active +5 years Unstructured MOC Data contained in the OE IMPACT MOC IT Tool Company Confidential ITE8500 3 years Structured 312 2. Pre-Startup Safety Review (PSSR) a. Provide a written description of the safety, technical review, and inspection that is conducted prior to startup of any new or modified equipment or process at an Oil and Gas Location or Facility. i. The description may be broad to cover multiple types of equipment and/or processes to capture the general inspection process implemented prior to conducting startup of any new equipment. If an Operator chooses, this section may contain multiple specific PSSRs grouped by equipment and/or process type (tanks, flowlines, etc). ii. The PSSR will include a checklist to document how the pre-startup review is conduction. The checklist may be broad to cover multiple types of equipment and/or processes to captue the general inspection process implemented prior to conducting startup of any new equipment and/or process specific checklists may be provided as examples. PSSR The most basic intent of a Pre-Startup Safety Review (PSSR) is to ensure safe startups and reliable operations, which is accomplished by systematically performing a series of checks on newly installed, modified, or idled systems. These checks verify that equipment and systems meet design intent and the applicable provisions of a facility’s OE program have been maintained accordingly. PSSRs add value by allowing periodic opportunities to verify that the risk of the new or modified facility is being appropriately managed. This procedure will clearly define the multiple layers that lie within the RMBU PSSR program. There is the Pre-Start-Up Assessment (PSA) which is a review process for small scope changes to facilities or current operations usually conducted in conjunction with Mechanical Integrity, Work Orders or Management of Change (MOC). There is a more formal process referred to as a Pre-Start-Up Safety Review (PSSR) process. A multidiscipline, multiphase review typically required during commissioning of new facilities or facilities that have undergone major modifications (e.g. extended shutdowns/ turnarounds). PSSR Phase 0 – (Pre-Construction Meeting) • PSSR alignment meetings familiarize the team with terms of reference, PSSR checklists, expectations, and key documents available for review. The PSSR alignment meeting will initiate the development of a detailed plan for review activities, a list of participants, a list of the documents and records that should be available for review, and a detailed schedule. The plan should be distributed to all participants as early as possible prior to PSSR Phase 1. PSSR Phase 1 – (Mechanically Complete) • The Phase 1 PSSR meeting is held when facilities construction is mechanically complete. With representation from all key stakeholders. The objective of this meeting 313 is to confirm that the project remains on schedule and is ready to turn the site over to the I&E Department. PSSR Phase 2 – (I&E/Rotating Equipment Complete) • The Phase 2 PSSR meeting occurs at the Project location with an objective to determine completion status of the Project with representation from all key stakeholders. Authorization for Facility Start-up Form • The Authorization for Start-Up form shall be utilized as a means of communicating to the departmental leaders that the project has reached a state of readiness. The PSSR project book along with this form will be provided to these individuals for review and sign off. The purge or start-up of the facility / location shall not proceed unless all involved departmental leaders have reviewed and signed off that their respective deliverables are complete PSSR Phase 3 – (Valve Alignment, Pre-Fill, Purge, ESD Testing, Compressor Commissioning) • PSSR Foreman(s), Production Safety, and Startup Team, (Construction and I&E on standby within a 30- minute drive) Pre-requisites to this meeting for PSSR Team are as follows: • All identified “A” Items complete. • A site-specific Authorization for Startup Form signed off by all Department representatives • PSSR Foreman(s) have UAW of all work prior to the Phase 3 meeting • PSSR Foreman(s) are responsible for coordinating Phase 3 meeting with the Startup Team. • PSSR Foreman(s) are responsible for scheduling and facilitating the Phase 3 • Pre-fill orders are coordinated through the Startup Team. • Rotation bump checks and run tests of rotating equipment. • SOP’s, C&E, updated P&ID’s are on site. • Tree-up for first set of wells complete. • Mid-Stream or third-party operational readiness. PSSR Phase 4 – First Gas Sales Ready (FGS) • A final change of custody will occur upon completion of the facility purge (<8ppm of Oxygen), ESD testing and compressor commissioning. This handover of facility control will change from the Surface Assurance PSSR Foreman(s) to the Production Startup 314 Team. The Phase 4 PSSR is a facility status designation – FGS READY. To formalize this state of readiness, the Handover/Custody Transfer form must be completed documenting the transfer of custody from the PSSR Foreman’s to the Startup Team. This Team will assume custody of facility and coordinate the startup of the facility. After Start-up PSA/PSSR Review • The After Start Up Review will provide an opportunity for the PSA/PSSR team members to implement our continuous improvement model and reflect/provide recommendations on lessons learned. Representatives from all disciplines should be encouraged participate. • Items to be considered should include but are not limited to the following: o Realized gaps in the current PSA/PSSR process. o EHSR challenges o Construction challenges and opportunities o Scheduling challenges o Procurement challenges o Engineering modifications o Training opportunities o 3rd Party challenges o Develop an Action Item list of PSSR “B” Items to be mitigated 30 days post FGS Supplemental Information Exhibits/References/Appendices • DJBU Greenfield MOC Process Flow • DJBU Brownfield MOC Process Flow • RBU PSSR Standard 315 316 Ch a n g e M a n a g e m e n t P r o g r a m R e c o r d R e t e n t i o n 317 Management of Change documents are created and stored in the Stature software system. Records are maintained for the active life of the facility + a period of no less than 3 years. Detailed information for the retention period of different categories of process critical documents (information) can be found in table 1. Records are updated when a change has been approved and the change management process is initiated. Records pertaining to critical information about a change can generally be made available within 14 business days of the written notice of request. Critical Process Information The documents and data listed in Table 5 shall be managed and handled as defined by the U&G OEIM standard. Information Risk Management (IRM) Record Categories are established by Chevron Policy 566. Information Protection information classifications are established by the Enterprise Security Architecture System (ESAS) standard #S1336. ‘Critical’ information is all required process documentation and all information captured and created during the operation of the process. ‘Controlled’ is information that requires approval. Table 1. Critical Information U&G and SBU Determined Critical Information Information Protection Classification Retention Category Information Format (Structured/ (IPC) Unstructured) Process and Procedure documents and related guidance Company Confidential ADM6020 Active +7 years Unstructured Leading and lagging metrics and performance indicators Company Confidential ADM5000 5 years Unstructured Process and procedure related training records Company Confidential HRW8540 5 years Unstructured Process training materials Company Confidential HRW8530 Active +5 years Unstructured MOC Package (includes, but is not limited to, FR checklists, FRA reports, PSSR checklists, Training Records, Communication records) Company Confidential OPR2040 Active +5 years Unstructured MOC Data contained in the OE IMPACT MOC IT Tool Company Confidential ITE8500 3 years Structured 318 PSSR: The most basic intent of a Pre-Startup Safety Review (PSSR) is to ensure safe startups and reliable operations, which is accomplished by systematically performing a series of checks on newly installed, modified, or idled systems. These checks verify that equipment and systems meet design intent and the applicable provisions of a facility’s OE program have been maintained accordingly. PSSRs add value by allowing periodic opportunities to verify that the risk of the new or modified facility is being appropriately managed. This procedure will clearly define the multiple layers that lie within the RMBU PSSR program. There is the Pre-Start-Up Assessment (PSA) which is a review process for small scope changes to facilities or current operations usually conducted in conjunction with Mechanical Integrity, Work Orders or Management of Change (MOC). There is a more formal process referred to as a Pre-Start-Up Safety Review (PSSR) process. A multidiscipline, multiphase review typically required during commissioning of new facilities or facilities that have undergone major modifications (e.g. extended shutdowns/ turnarounds). - PSSR PHASE 0 – (PRE-CONSTRUCTION MEETING) o PSSR alignment meetings familiarize the team with terms of reference, PSSR checklists, expectations, and key documents available for review. The PSSR alignment meeting will initiate the development of a detailed plan for review activities, a list of participants, a list of the documents and records that should be available for review, and a detailed schedule. The plan should be distributed to all participants as early as possible prior to PSSR Phase 1. - PSSR PHASE 1 – (MECHANICALLY COMPLETE) o The Phase 1 PSSR meeting is held when facilities construction is mechanically complete. With representation from all key stakeholders. The objective of this meeting is to confirm that the project remains on schedule and is ready to turn the site over to the I&E Department. - PSSR PHASE 2 – (I&E/ROTATING EQUIPMENT COMPLETE) o The Phase 2 PSSR meeting occurs at the Project location with an objective to determine completion status of the Project with representation from all key stakeholders. - AUTHORIZATION FOR FACILITY START-UP FORM o The Authorization for Start-Up form shall be utilized as a means of communicating to the departmental leaders that the project has reached a state of readiness. The PSSR project book along with this form will be provided to these individuals for review and sign off. The purge or start-up of the facility / location shall not proceed unless all involved departmental leaders have reviewed and signed off that their respective deliverables are complete - PSSR PHASE 3 – (VALVE ALIGNMENT, PRE-FILL, PURGE, ESD TESTING, COMPRESSOR COMMISSIONING) o PSSR Foreman(s), Production Safety, and Startup Team, (Construction and I&E on standby within a 30- minute drive) Pre-requisites to this meeting for PSSR Team are as follows: o All identified “A” Items complete. o A site-specific Authorization for Startup Form signed off by all Department representatives o PSSR Foreman(s) have UAW of all work prior to the Phase 3 meeting o PSSR Foreman(s) are responsible for coordinating Phase 3 meeting with the Startup Team. o PSSR Foreman(s) are responsible for scheduling and facilitating the Phase 3 o Pre-fill orders are coordinated through the Startup Team. 319 o Rotation bump checks and run tests of rotating equipment. o SOP’s, C&E, updated P&ID’s are on site. o Tree-up for first set of wells complete. Mid-Stream or third-party operational readiness. - PSSR PHASE 4 –FIRST GAS SALES READY (FGS) o A final change of custody will occur upon completion of the facility purge (<8ppm of Oxygen), ESD testing and compressor commissioning. This handover of facility control will change from the Surface Assurance PSSR Foreman(s) to the Production Startup Team. The Phase 4 PSSR is a facility status designation – FGS READY. To formalize this state of readiness, the Handover/Custody Transfer form must be completed documenting the transfer of custody from the PSSR Foreman’s to the Startup Team. This Team will assume custody of facility and coordinate the startup of the facility. - AFTER START UP PSA/PSSR REVIEW o The After Start Up Review will provide an opportunity for the PSA/PSSR team members to implement our continuous improvement model and reflect/provide recommendations on lessons learned. Representatives from all disciplines should be encouraged participate. o Items to be considered should include but are not limited to the following: Realized gaps in the current PSA/PSSR process. EHSR challenges Construction challenges and opportunities Scheduling challenges Procurement challenges Engineering modifications Training opportunities 3rd Party challenges Develop an Action Item list of PSSR “B” Items to be mitigated 30 days post FGS - RBU PSSR STANDARD RBU - Upstream Pre-Startup Safety Review (PSSR) Standard Upstream Capability - Base Business and Operations February 2014 – Rev. 0 320 Date Description Revision By 20-Feb-14 Standard approved by EGB. Lauren Bailey (LBHI) 7-July-21 RBU Blue Language added Brian Condray © 2014 Chevron Corporation - All rights reserved. Company confidential - for internal use only This document contains confidential and proprietary information for use by employees and authorized agents of Chevron Corporation and its affiliates (Company). No other use is authorized without prior written permission from Chevron Corporation or its appropriate affiliate. Table of Contents Introduction 10 Executive Summary 10 Purpose 11 Objectives 11 PSSR Triggers 13 When a PSSR is Required 13 PSSR Scope and Timing 14 PSSR Program Requirements 16 Local Regulatory and Chevron Requirements 16 Document Control 16 Building a Team and Participant Responsibilities 16 PSSR Training 20 PSSR Deviation Management 20 PSSR Workflow 23 PSSR Workflow 23 Multiple PSSRs 24 Single PSSRs 27 321 PSSR Checklists 28 Further PSSR Checklists Considerations 28 Continuous Improvement 30 Formal PSSR Audit 30 Informal PSSR Audit 30 Metrics 31 Improvements to Upstream PSSR Standard 31 Abbreviations 32 Definitions 33 References 27 Appendix A: PSSR Checklist Example (Use of the MCBU PSSR Checklist is required) 28 Appendix B: Linkages to Related Processes and Documents 34 Linkage to Operational Excellence 34 Linkage to Process Safety 34 Linkage to Project Operations Planning (POP) 35 Linkage to Upstream Guidance for Operating Procedures 35 Linkage to Upstream Management of Change (MOC) for Facilities & Operations (F&O) Guidance 36 Linkage to Systems Completion 36 Appendix C: Interface with Mechanical Completion, Commissioning, and Startup 38 Appendix D: Systems Completion Certification Process 39 Appendix E: PSSR Standard Requirements 40 322 Introduction The purpose of this document is to standardize PSSR program components and procedure for Pre-Startup Safety Reviews (PSSRs) in Chevron’s Upstream organization. This allows for a fit-for-purpose approach, while ensuring that core requirements are met. Executive Summary The Pre-Startup Safety Review (PSSR) is the final review to ensure that equipment, a system, or a facility is safe to start up and provides reliable operation. It is one mechanism used to manage risk and is a key component of process safety efforts. The PSSR is owned by the operations team in the business unit (BU) but requires support and input from a multi- functional PSSR Team. The PSSR Standard and Checklist will be managed by the PSSR Coordinator. This procedure fulfills the requirements for a PSSR as detailed in Operational Excellence Management System (OEMS) Expectation 2.4. The Upstream PSSR Standard focuses on four dimensions that must be validated in a PSSR: Design, Construction, & Commissioning Specifications Procedures Process Hazard Analysis (PHA) Training To ensure an effective PSSR Program, this document contains: PSSR Standard PSSR Checklist Expectations 323 Purpose The most basic intent of a Pre-Startup Safety Review (PSSR) is to ensure safe startup and reliable operations, which is done by systematically performing a final check on newly installed, modified, or idled systems. This check verifies that equipment and systems meet design intent and the applicable provisions of a facility’s OE program have been maintained accordingly. PSSRs add value by allowing a final opportunity to verify that the risk of the new or modified facility is being appropriately managed. Specific to Chevron, PSSRs are an expectation of the OEMS (Operational Excellence Management System) under OE Element 2: Facilities Design and Construction. This procedure meets the requirements of Expectation 2.4 to “Conduct pre-startup reviews on all new, modified or previously idled facilities prior to startup and after shutdown to confirm they meet applicable regulatory and corporate requirements”. A Major Capital Project (MCP) PSSR program should be aligned with that of its accepting Business Unit (BU). The drawing below underscores the need to provide continuity, ensure basic requirements are achieved, and facilitate a smooth exchange from MCPs to Phase 5 operations. Figure 1: Need for a Common PSSR Standard Objectives A Pre-Start-up Safety Review verifies that the following objectives are achieved: Installation or modification of the equipment / system / facility has been completed in accordance with design specifications and commissioned in alignment with OEMS and BU testing requirements. Documented certification or compliance with appropriate codes, standards, and regulations from both Chevron and the host region. Fulfills Management of Change (MOC) for Facilities & Operations requirements as related to PSSRs. Upon startup, process safety information (PSI) is up to date in the Business Unit’s system of record. An appropriate level of risk assessment (e.g., PHA or HAZOP) has been performed and all pre-startup recommendations have been resolved. Process controls, emergency shutdowns, safety systems, and integrity critical elements are in place, tested, and can function as designed. New or revised Operating Manuals, Operating Procedures, Maintenance Procedures, and Emergency Procedures are in place and updated. 324 Technical, maintenance, operations, and contract personnel affected by the new installation or modified facilities have received the necessary training and materials for on-going training programs have been updated accordingly. Personnel affected by the new installation or modification are aware of new hazards or increased risk and understand key safeguards associated with those hazards. Emergency response plans, procedures, equipment, and training are in place including escape, evacuation, and rescue systems. All warnings, markings, labels, signs and required safety or emergency response equipment (e.g., fire extinguishers, flange shields, safety showers) are installed and ready for service. All action items critical to startup have been completed and post-startup action items are tracked to closure. 325 PSSR Triggers Prior to startup, operations must “assure itself” that the facility is safe for startup. This should be the key consideration in deciding if a PSSR should be performed. This section details: When a PSSR should be performed The scope of the PSSR(s) When a PSSR is Required Defining when a PSSR is to be performed is a required component of a PSSR program and shall be clearly documented. Below are the minimum instances when a PSSR shall be performed. At a minimum, a PSSR is required for: All changes that are in the scope of the Upstream MOC for Facilities and Operations Process. Changes in process safety information (PSI), including greenfield installations or modifications to an existing (brownfield) facility. (See the Upstream Facility Information Management Standard Process, FEF-STD-CUG-0002-Z01, for a full catalogue of PSI.) A significant replacement in kind (RIK) (complex in scope or affecting multiple systems) has been made to an existing system / facility, such as a unit turnaround. A RIK is considered significant if the piece(s) of equipment impacted: Are major pieces of equipment Gas Compressor/Driver 300hp or greater Pump 300hp or greater Vessels Tank PLC/Electrical/Instrumentation (Affecting multiple pieces of equipment or instruments) As the Final Approver The Production Supervisor (PS) has the option to have a PSSR completed on any additional RIK. After an intrusive inspection effort or major repair. For example, disassembly and inspection of an entire train or system within a train of equipment. Additional examples of an intrusive inspection are: Inspection or repair of components which require disassembly of a major piece of equipment (ex. Compressor/Driver annual/overhaul) Internal repair or inspection of vessel or tank As the Final Approver, The Production Supervisor (PS) has the option to have a PSSR completed on any additional intrusive inspection/major repair. 326 A temporary change has been made. Perform a PSSR to start up the process with the temporary change and again when the system is reconfigured to its permanent condition. A “mothballed” or idled process (one that has been out of service for a length of time) is restarting. This requirement is applicable only to pieces of equipment that have been previously removed from service and is not intended to apply to equipment designed to operate infrequently (ex. start up pumps or spared equipment). Any equipment removed from service for more than 6 months shall complete a PSSR. As the Final Approver, The Production Supervisor (PS) has the option to have a PSSR completed on any additional facility/process/equipment that was taken Out of Service. For large MCPs, a PSSR is required for new systems being put into operation for the first time where there is risk for impact to safety upon startup. A person for the facility or project should be designated as the point person for interpreting when a PSSR is needed. For example, this may be an HES, Process Safety, Operations, or FE Manager. When a PSSR is Scalable The PSSR Checklist is scalable, allowing for reducing the size of the PSSR team and checklist based on the type of change. The PSSR Team Leader in conjunction with the Final Approver is responsible for agreeing upon the PSSR Checklist prior to execution of the PSSR. At a minimum, the first grouping of questions listed in Appendix A (“Pre-Startup Operations Checks”) should be asked. Examples of when a scaled-down PSSR Checklist may be used include: Small projects or routine maintenance on non-integrity critical equipment. Changes to operating or maintenance procedures that did not entail a change to an existing system / facility or a significant change in operations. If multiple locations are involved, separate PSSR checks shall be done for each location. Single PSSR form may be modified to show completed checks on multiple locations. The PSSR Checklist Template can be found in the (Still working on the location) Resources SharePoint Site. This template shall be used as a guide. In a fit-for-purpose manner the template can be modified to address specific changes and pre- startup efforts. PSSR Scope and Timing This document applies to instances where a single PSSR is performed and those where multiple, successive PSSRs are performed. In other words, this document applies to both Business Units (BU) where typically a single PSSR is performed and Major Capital Projects (MCP)and Turnarounds that usually require multiple PSSRs. PSSR Scope Depending on the size and complexity of the project or scope of work, multiple PSSRs may need to be performed. For most small projects and BU work that are being driven by an MOC, generally only one PSSR needs to be performed. However, even on small projects, it is relevant to understand where the PSSR fits into the wider facility view. For MCPs 327 where commissioning and startup work is occurring over an extended duration and scope is broad, multiple levels of PSSRs are needed and the MCP must have a clear understanding of signoff protocol and where information needs to be fed forward. The overall goal, regardless of scope size is readiness for startup, consistency in signoffs, and assurance that PSSR objectives have been met. To do this, a system walkthrough shall occur and documentation from previous reviews may be leveraged as supporting evidence. PSSR Timing A PSSR shall be performed prior to a system operating in accordance with its “intended use.” The figure below shows a sequence of events from implementation of a change to startup, and to sustained operations. A PSSR should be performed when construction and commissioning are complete, and startup is imminent. Thought should be given to when startup occurs and when is the most effective time to perform a PSSR. For example, when commissioning a motor, it is energized and technically started up during a “bump test” and then de-energized. It should be pre-determined whether a PSSR will be performed prior to the bump test. This requires sound judgment and pre-planning to determine when the PSSR will be performed during commissioning and startup process. Steps for Determining PSSR Scope Identify “levels” within a project / scope of work. This varies for each project / work; not all levels will be present in each. On MCPs, this should align with systems completions. Determine at which level PSSRs will be performed. The figure shows “levels” that exist on the largest type of MCP, for example in a multi-train LNG facility. The “asset” is the compilation of all the trains, while the facility might be one train. Consistency in signoffs for each level is imperative. If multiple PSSRs are required, they should be compiled for the entire scope of the startup prior to transfer of care, custody, and control to Phase 5 Operations. Figure 2: Representation of PSSR Levels for Various Scopes of Change 328 PSSR PHASES (GREENFIELD) PSSR Program Requirements At a minimum, the following components shall be addressed as part of a PSSR Program. Local Regulatory and Chevron Requirements PSSRs shall follow OEMS principles and must conform to local regulations. Regulatory regimes primarily considered in this PSSR Standard are: OSHA 29 CFR Part 1910.119 HSE (Health and Safety Executive) Safety Case COGCC Additionally, Pre-Startup Safety Reviews link to several existing standards within Chevron, which are detailed in Appendix B. It is relevant to note these key Chevron standards and processes to ensure that criteria detailed in those are being met with respect to PSSRs. Document Control The PSSR Procedure and completed PSSRs shall be stored in a system of record. Completed PSSR information that is captured and tracked includes: Completed and approved (signed) PSSRs PSSR deviations tracked to closure Note that for all PSSRs associated with MOCs, document control is covered as part of the MOC Facilities and Operations (F&O) Procedure. For PSSRs not associated with an MOC, documentation shall be stored in the system of record. Building a Team and Participant Responsibilities At a minimum, the PSSR Team shall comprise of a PSSR Team Leader and a Final Approver; these shall not be the same person. Additionally, there must be representation from operations on the PSSR Team as well as a person with competency to answer technical questions. All PSSR Team Members shall sign off on the PSSR to attest to the answers given on his or her section(s) of the checklist. Depending on the scope of the PSSR, there should be PSSR Team Members who can answer checklist questions from Operations, Systems Completion, Technical, and HES disciplines. Any one of these functions may act as the PSSR Team Figure 3: PSSR Timing 329 Leader. For all PSSRs, the team who will be executing the PSSR should be identified when the PSSR Checklist is being compiled. The contents of the checklist will define what team members are required based on the size and complexity of the PSSR scope. The PSSR Team is responsible for: Ensuring the PSSR Checklist adequately addresses the hazards and risks associated with the new or modified facility. Having the expertise to answer checklist questions and seeking additional support as needed. Answering checklist questions objectively, critically, and carefully. Determining which documentation is appropriate to use and rely upon to answer PSSR Checklist questions. Documentation should be challenged prior to acceptance for use including examining it for content, dates, and signoffs. If the PSSR Team does not feel confident in any of the supporting documentation, the PSSR Team must validate that information firsthand. The following table outlines the roles and responsibilities of the PSSR Team. PSSR Team Role Responsibilities PSSR Team Leader (Required PSSR Team Member) Plans and leads the PSSR, coordinating with operations. Responsible for completion of the PSSR and ensuring resulting action items are completed. Typically, for the RBU this is typically the PSSR foreman or designee, this is the MOC Owner for small projects. For MCPs, the PSSR Team Leader may be from Pre-Operation, Start-up, Facilities, or Systems Completion Teams. Identify the PSSR Team and ensure each team member understands his or her role. Assigns checklist sections to team members. Based on the PSSR scope, review and compile the checklist. Determine if additional checklist items are required. Identify supporting documentation for the PSSR. Validate the checklist with the PSSR Final Approver prior to performing PSSR. Schedule and conduct PSSR planning and walkthroughs. Ensure fulfillment of MOC for Facilities & Operations requirements, as applicable. Determine if any action items are required as a result of the PSSR and captures and assigns those accordingly. Notes action items on the PSSR checklist for the Final Approver’s awareness. Review and sign the PSSR checklist to confirm the PSSR has been performed. Send the final executed PSSR checklist to relevant parties. (For example, the System Lead, MOC Owner, etc.). Ensure final executed PSSR checklist is stored in Business Unit’s system of record. If multiple PSSRs are being performed, ensure that the PSSR documentation is being stored and compiled for the entire scope of startup. Follow up on action items post-startup. PSSR Final Approver (Required for PSSR Approval) The operations lead responsible for the area where the PSSR is taking place. Typically, this is an Ensure participation of operations in the PSSR. Review the PSSR Checklist prior to conducting the PSSR to ensure that it appropriately addresses the nature of the work and the related hazards. Review and sign the PSSR checklist to confirm the facility is safe for startup. 330 Operations Superintendent, Manager or Area Supervisor Has overall responsibility for ensuring safe startup and continued operations of the asset. Therefore, must be confident that the PSSR has asked all the right questions, the right subject matter experts are involved, and adequate supporting documentation exists prior to startup. Operations Representative (Required PSSR Team Member) Serves as the operations contact from the organization that will be accepting the installation / modification. This is a key role and can be thought of as the gatekeeper before the change is started up and handed over. Is familiar with operation of the installation / modification. Inspect jobs during construction and verifies that construction is being completed per design specifications. Participate in PSSR planning and walkthroughs. Validate the final PSSR checklist prior to the walkthrough to ensure it contains all essential checks. Ensure that systems, equipment, lines, etc., are clearly labeled. Ensure that new or revised Operating Manuals, Operating Procedures, Maintenance Procedures, and Emergency Procedures are in place and updated and that appropriate personnel have been trained. Ensure employees are aware of new hazards specific to a process. Coordinate with the HES Representative to review operating plans and ensure safety requirements have been met. Ensure that all required actions are completed prior to startup. Review and sign the PSSR checklist to confirm the PSSR has been performed. Technical Representative Serves as the technical focal point for the area(s) covered by the PSSR checklist. Systems Engineer, Mechanical Engineer, Electrical Engineer, Process Engineer, Facility Engineer, Field Engineer, Equipment Inspector, Sr. Operator, Maintenance Rep, Control System Technician, etc. Participate in PSSR planning and walkthroughs. Confirm that installation or modification of the equipment / system / facility has been completed and commissioned in accordance with design specifications. Ensure the installation / modification complies with appropriate codes, standards, and regulations from both Chevron and the host region. Process controls, emergency shutdowns, safety systems, and integrity critical elements are in place, tested, and can function as designed. Ensure any non-conformance items defined by Asset Integrity Standards are either resolved or suitable for continued service. Leverage information from previous reviews to ensure equipment has been completed as per design. Verify that updated PSI has been incorporated into the existing facility’s PSI. Review and sign the PSSR checklist to confirm the PSSR has been performed. Maintenance Representative Serves as the maintenance contact from the organization that will be accepting the installation / modification. Participate in PSSR planning and walkthroughs. Ensure that work is completed in accordance with the design and maintenance specifications. Verify the equipment has been added to the equipment inspection and maintenance records. 331 Verify that new equipment has been added into the Preventive Maintenance (PM) schedule as required. Ensure that appropriate and accurate maintenance procedures have been included in the operating and maintenance procedures and personnel have been trained in their use. Confirm that tools and equipment have been supplied to maintain new equipment and that maintenance plans and spares have been provided and documented. Review and sign the PSSR checklist to confirm the PSSR has been performed. Health, Environmental and Safety Specialist (HES) Serves as the HES contact from the organization that will be accepting the installation / modification. This role is especially important on scope / changes with a large impact. Participate in PSSR planning and walkthroughs. Ensure the installation complies with applicable Chevron standards and local regulations. Validate that the installation / modification is free of recognizable hazards. Verify that warnings signs and required safety or emergency response equipment (e.g., fire extinguishers, flange shields, safety showers) are installed and ready for service. Ensure recommendations resulting from the PHA (e.g., HAZOP) have been addressed and signed off as closed. Ensure that emergency response and safety procedures have been included in the operating and maintenance procedures, coordinate with operations. Ensure that adequate personal protective equipment has been provided for operating the equipment or facility. Review and sign the PSSR checklist to confirm the PSSR has been performed. Commissioning Representative Serves as the link between commissioning and startup. Generally, this position is related to MCPs. Participate in PSSR planning and walkthroughs. Ensure all documentation and plans from commissioning phase are included in PSSR support documentation. Use knowledge of work that took place during commissioning phase to support PSSR. Review and sign the PSSR checklist to confirm the PSSR has been performed. Construction Representative Serves as the link between construction and startup. Generally, this position is related to small projects in BUs. Participate in PSSR planning and walkthroughs. Ensure all documentation and plans from construction phase are included in PSSR support documentation. Use knowledge of work that took place during construction phase to support PSSR. Review and sign the PSSR checklist to confirm the PSSR has been performed. External Subject Matter Expert Has a specific skill set that is relevant to change? For example, Participate in PSSR planning and walkthroughs. 332 an SME who may have experience with a particular process or piece of equipment. Leverage experience on an analogous project or change to complete checklist questions or support others on the PSSR Team. Review and sign the PSSR checklist to confirm the PSSR has been performed. PSSR Training The two key roles on PSSR Team, the PSSR Team Leader and Final Approver should be familiar with the PSSR Program and understand their roles as well as the roles of the rest of the PSSR Team. Pre-work for the PSSR Team Leader and Final Approver includes: Reading and review of the PSSR Standard Procedure Existing MOC Training (if applicable) If possible, participation on another PSSR Specifically, the PSSR Team Leader and Final Approver should have: Familiarity with Process Safety elements within OEMS Understanding of the purpose of performing a PSSR Understanding of when a PSSR needs to performed Familiarity with PSSR Procedure specifics including the PSSR workflow and the roles and responsibilities of all PSSR Team Members PSSR Deviation Management For MOC F&O and non-MOC PSSR deviations will be tracked on the PSSR form. Factory PSSR deviations will be tracked on a “punch list register”. Upon completion of the PSSR Checklist, there may be some items that were checked as “No” or “Not Complete” on the checklist. These need to be evaluated to determine whether they are critical or non-critical for startup. If they are determined to be non-critical, they must still be addressed and entered into a deviation management process to be completed post-startup. If they are determined to be critical, they must be addressed prior to startup. This process should be led by the PSSR Team Leader in consultation with operations, HES, and the Final Approver. 333 An example of a deviation might be checking “No” to “Has all process safety information required for commissioning and operation been made available to all affected operators, updated and stored in the system of record?” If, for example, P&IDs were red-lined, but not yet updated in the document management system, this question could not be answered as a “Yes”. A determination must be made whether this is a critical item that must be completed prior to startup. The deviation management workflow provides guidance for these types of scenarios. Identify Deviation Upon completion of the PSSR Checklist, the PSSR Team Leader should identify items checked as “No”. Perform analysis to determine if the item must be completed prior to startup: Complete BEFORE- A deficiency that could cause, or result in, actual or potential release of hazardous chemicals or energy sources to environment. The process cannot be safely started or operated until the issue is corrected. Complete AFTER - An issue that does not impact safe startup or operation but, if corrected, enhances process or personal safety. Propose Interim Mitigations If it is determined that the item checked “No” is appropriate to be completed after startup, then actions to mitigate the interim risk of the open PSSR item should be identified. Figure 4: PSSR Deviation Management Complete item prior to startup Are there additional deviations ? Is the item safety - critical? yes no yes no PSSR Deviation Management Work Flow Propose interim mitigations Identify Deviation (“No” on PSSR Checklist) Approval & acceptance Are the deviations approved ? noComplete item prior to startup yes Assign action & track to closure Close action items 1 4 5 3 2 334 Record the interim actions for each deviation and prepare for submittal to the PSSR Final Approver. Approval and Acceptance All deviations should be submitted to the PSSR Final Approver and receive approval prior to the PSSR final approval and startup. If approval is not gained from PSSR Final Approver, the item must be completed prior to start up. Assign Actions and Track to Closure Prior to startup, deviations are recorded, and each has corresponding actions with assigned owners and timing. Deviations must be tracked and closed out in a timely manner after startup. (In MOC F&O terminology, this is considered a P4 action item.) An action tracking system is used to record actions and ensure that those are completed to close the deviation. It is likely that both BUs and MCPs have an existing action tracking system already in place, which should be used in this case. For example, for changes managed within the MOC F&O process, tracking of action items should occur in the OE IMPACT MOC Tool. Close Action Items As actions are completed for each deviation, they will be documented. Action owners are responsible for their assigned action, while the PSSR Team Leader is responsible for completion of the PSSR Deviation Management Process. The PSSR Final Approver is responsible for accepting the risk associated with all deviations. 335 PSSR Workflow PSSR Workflow Assess Against PSSR Triggers The PSSR Trigger section defines when a PSSR needs to be performed. Assess the Change / Installation The extent and of the change / installation is assessed and considered under the context of understanding the scope, risk, and novelty. Determine if Multiple PSSRs are Required The need for multiple PSSRs is determined by the scope of the change. Multiple PSSRs are required when multiple system startups are occurring over a period as in an MCP or major turnaround. Figure 5: PSSR Workflow 336 If multiple PSSRs are required, a PSSR Coordinator is assigned to plan the scope of each PSSR by working in coordination with the systems completion team (if applicable) and operations team. The PSSR Coordinator will ensure that the entire scope of the change will be assessed by PSSRs as well as ensuring that completed PSSRs and associated actions are stored and tracked. A PSSR Team Leader is assigned for each individual PSSR to lead the planning, execution, and follow up. Plan for the PSSR It is unacceptable to perform the PSSR walkthrough before adequate pre-work has been done. This includes identifying the PSSR Team, compiling the PSSR checklist, gathering documentation, and scheduling. Perform PSSR Walkthrough The PSSR will at a minimum include a walkthrough and visual inspection of the change / installation with the entire PSSR Team present. Sections of the PSSR Checklist will be divided among members of the PSSR Team based upon their area of expertise. The sections’ owners are responsible for being able to answer each checklist question with certainty or seeking assistance to do so. The PSSR walkthrough should not be conducted too early, allowing additional changes to potentially occur post-PSSR and pre-startup. Obtain Approval PSSR checklists will receive signoffs from each of the PSSR Team Members. The results of the PSSR will be shared with the Final Approver prior to start up. The Final Approver will review the completed checklist, understand deviations, and decide if the asset is ready for startup and issue his or her approval. If approval is not issued by the Final Approver, then the PSSR Team must ensure necessary changes are made to rectify all gap(s) and then re-perform the affected PSSR sections and resubmit to the Final Approver. The PSSR Checklist will be stored in the system of record. Safely Start Up Startup may commence. Manage Deviations As deviations arise, the PSSR Team Leader will note these and follow the PSSR deviation management process. See above for PSSR Deviation Management. Track Post Startup PSSR Actions (from deviations) Actions stemming from PSSR deviations will be tracked to closure post-startup. Periodically Assess / Audit the PSSR Program Assess deficiencies as well as excesses. Determine whether aspects of the program need to be streamlined and are the efforts generating positive returns. This step does not occur for every PSSR but should occur periodically. Further detail is found the PSSR Audit section. Multiple PSSRs 337 Large-scale installations and modifications will require more than one PSSR to start-up the entire scope. In this case, the PSSR is not a single event, but is a series of PSSRs that have divided up the scope of the installation into manageable and logical components for startup. On large MCPs prior to completing a PSSR, projects follow the systems completion process which is the sequential activities within a project that prove construction, installation, testing, and preparation of systems have been completed as designed, and thus, the facility is ready for start-up and operations. An illustration of this process is shown in Appendix D. The key points recognized are: More than one PSSR is required on an MCP or major turnaround. PSSRs are not meant to simply re-check previous assurances and reviews. The PSSR is a verification and validation, but not intended as rework. The purpose is not to plan excessive numbers of PSSRs, but to determine the systems on which PSSRs should be conducted so that they are impactful. In close consultation with the Systems Completion Team, the installation / modification will be systemized and sequenced for startup and PSSRs should mirror this structure. There should be consistency in PSSR Final Approvers’ signoffs on each level. Timing for Multiple PSSRs MCPs must plan for PSSR performance during CPDEP Phase 3 and update this plan during Phase 4. Significant effort is required to gather required information, ensure budget allocation, assemble PSSR Teams, and schedule. Below are key activities related to PSSRs in Phase 4 along with the timing for when PSSRs occur – during pre-commissioning and commissioning. Refer to the POP Milestones and Deliverables Map (MDM) for details on the deliverables related to PSSRs. Considerations for Multiple PSSRs: Assign a project wide PSSR Coordinator in Phase 4 (typically this is the Start-up Manager). Establish the particulars of the PSSR procedure and checklist based on project needs. The Pre-Operations Team on an MCP should either be leading the PSSR effort or heavily involved. Figure 6: Key PSSR Activities Related to MCPs in CPDEP Phase 4 338 There is interaction between multiple project disciplines for a successful PSSR including: BU Operations (owns PSSR), Commissioning and Startup Teams, Systems Completion, Construction, HES, Subsea, Drilling 1, and Facility Engineering Include PSSR timing and resources in the Project-level resource loaded schedule. During Mechanical Completion walk downs, the PSSR Team Leader (at a minimum) will be present with the PSSR checklist to identify items that can be addressed by the Systems Completions team prior to the PSSR. The startup of systems (particularly of utility systems) frequently begins in fabrication yards, which tend to be at a different location than the final facility location. The project should plan for having the right PSSR Team in the fabrication yard for system startup. PSSR Team Members including the PSSR Team Leader and Final Approver may be rotating to international locations and have a “back-to-back”. Ideally, the PSSR activities on a single system will be performed by the same Team Members. If this is not possible, additional effort (thorough turnover coverage) must be made to share information with back-to- backs or a designee assigned to the PSSR Team. This is especially important for those in the Final Approver role. Contracting strategy can influence PSSRs. For projects where a third-party contractor is responsible for commissioning or startup, Chevron must still lead a PSSR and gain approval from the accepting BUs Operations team. Subsea installations by their nature do not allow for a final “walkthrough”. Projects should at a minimum do a desktop PSSR “walkthrough” and use ROV (remote operated vehicle) capabilities where possible. Additionally, emphasis should be put on early planning of PSSRs for subsea systems so that the proper documentation can be gathered, and systems reviewed prior to installation. On brownfield installations, because work is being done on an existing facility, there will be significant interfacing with the BUs MOC procedure. Each tie-in point will have a BU MOC associated with it. Because of this, additional effort should be made to coordinate and stay aligned with the BU Operations. Projects have the responsibility to build continuity between MCPs and the accepting BU in many aspects of project work. Related to PSSRs, MCPs should: Use the Upstream PSSR Standard that allows for fluency of terms and procedure. Ensure transfer of PSSR Checklists and PSSR supporting documentation to the BU. Major turnarounds can be treated similarly to MCPs when planning PSSRs due to their large scope and effect on multiple systems that will need to be restarted. Typically, a turnaround involves a shutdown of an entire facility or major unit and offers the chance for installations and changes to be made outside of normal operations. Work pack for Multiple PSSRs PSSR Team Leaders develop work packages and gather the documentation that is needed to validate the checks and questions for each PSSR. For each system on which a PSSR is performed, there will be a work pack that includes the following documentation: Commissioning & Startup Procedures and Standard Operating Procedures 1 The PSSR Standard is not intended to govern the startup of drilling equipment. It is noted in this case because information from the drilling discipline may be required for the facility PSSR. 339 MOC (if relevant, as in tie-ins to an existing facility) A & B Check Sheets and Punch lists Operations Readiness Review (ORR) action items HAZID / HAZOP / What-if action items and results Operations and Maintenance Training Records System Test Records (hydrotests, welding certifications, loop checks, etc.) Single PSSRs Considerations for Single PSSRs: PSSRs are required by the MOC Facilities & Operation Procedure, and most PSSRs are tied to and triggered by an MOC. The PSSR Team is likely to be made up of team members who are familiar with the operation. This does not negate the need for a multi-functional team or having operations represented and a representative from operations serving as the Final Approver. Determine PSSR timing and incorporate in relevant work-planning schedules. PSSR Team Leader and Operations Representative (at a minimum) should be present during key construction / installation milestones with the PSSR checklist to identify items that can be addressed prior to the PSSR. Work pack for Single PSSRs PSSR Team Leaders develop work packages and gather the documentation that is needed to validate the questions for each PSSR. The following information should be available to verify PSSR questions: MOC(s) (if applicable) HAZID / HAZOP / What-if action items and results Operations and Maintenance training records System test records (hydrotests, welding certifications, loop checks, etc.) 340 PSSR Checklists There are four main dimensions that must be validated by a PSSR prior to start up. The PSSR checklist must address: Design and Construction Specifications Procedures Process Hazard Analysis Training Additionally, there are specific components that must be included in a PSSR checklist, they are listed below and mapped to the OEMS Elements. Further PSSR Checklists Considerations Element 04: Management of Change Element 05: Reliability and Efficiency Element 06: Third Party Services Element 07: Environmental Stewardship Element 08: Product Stewardship Element 10: Community and Stakeholder Engagement Element 11: Emergency Management Element 12: Compliance Assurance Fulfill MOC Requirements Emergency Response Access / Egress Fire Protection Compliance with Local Laws & Regulations Internal & External Notifications Environmental Element 01: Security of Personnel and Assets Element 02: Facilities Design and Construction Element 03: Safe Operations Electrical Machinery / Equipment Structural Valve & Piping Vessels Communication Operation-Specific (Pipeline , Marine, Subsea, etc) Security Operations & Maintenance Procedures Process Control & Integrity Process Safety Information Training Figure 7: PSSR Expectations Mapped to OE Elements 341 Use of Supporting Information The PSSR checklist does not preclude taking credit for checks or reviews that have already occurred elsewhere (for example Zenator as part of mechanical completion software, or other documented systems completion reviews, ORRs, or CRRs). Previous reviews should be used to support answering questions on the PSSR checklist, but do not take the place of a PSSR. Scalability The PSSR checklist is scalable. Effective PSSR checklists can have a variety of approaches to their design. PSSR can be done simply (for example, a visual inspection and documentation using a shorter checklist) or performed in a more rigorous fashion due to the type of startup and equipment involved. The goal is to make the best use of resources based upon the risk attributed to the equipment and startup. Signoffs and Approvals To promote accountability, all PSSR Team Members shall sign off on the checklist as well as the Final Approver. 342 Continuous Improvement Formal PSSR Audit The PSSR Procedure will be reviewed during the OE Management System Audits to ensure the procedures are being properly used and updated. For PSSRs performed within the context of the Management of Change for Facilities and Operations Process, this will be part of the audit of the MOC process. A PSSR Procedure Review should be conducted (in BUs) every three years to validate compliance and efficacy. For PSSRs performed as part of MOC F&O, this review will be part of the MOC review step. Informal PSSR Audit Much of the PSSR Procedure relies upon consistent, high-level human performance. Reviewers are expected to examine complex systems and then identify risks or issues that have likely been overlooked on a previous reviews or assurances. While training is critical in ensuring performance, audits are an additional way to identify gaps in the PSSR Procedure. Operations Managers or Production Supervisors are typically the Final Approvers of PSSRs and have the ultimate responsibility to ensure that PSSRs are being performed effectively. These approvers do not have the ability to be present for every PSSR, but they do have the ability to lead audits on the procedure. In a sense, the PSSR is a final audit before a system startup and Operations Managers need to essentially “audit that audit.” Formal OEMS Audits support this, but informal audits are equally important and can occur on a more frequent basis. When to perform an internal, informal audit: Determine if changes have occurred in the organization that should be reflected in the PSSR Program such as regulatory changes, workforce reductions or turnover, or organizational restructuring. Internal audits will be conducted under the OE Assurance/PSM audit process scope, if PSSR is identified as an OE priority for a business cycle. Guidelines for performing an internal, informal audit on the PSSR Procedure include: Interview of PSSR Team Members and those involved in PSSRs. Determine whether participants understand their role and audit the efficacy of the checklists. Desktop review of a representative sampling of several recently performed PSSR Checklists and associated PSSR Deviations Desktop review of the PSSR Procedure As part of the audit, the following topics should be addressed to ensure that the PSSR Procedure is functioning and effective: Are there written procedures for performing PSSRs and are they clear and understandable? Have the PSSR Team Leader and PSSR Final Approver been trained on the PSSR Procedure? Did the Final Approver approve the content of the checklist prior to the PSSR? Do PSSR Teams represent multi-functional roles and contain the right skill sets? Did all Team Members sign off on the PSSR? What is the level of operations’ involvement in PSSRs prior to the start-up date? Can PSSR records including signed checklists be easily retrieved? Does the PSSR database work properly? Were review techniques driven by a risk-based approach to PSSRs applied? 343 Were trigger events pre-determined for a facility or MCP and were they identified for each PSSR? How often did a PSSR delay its associated startup? Was the delay helpful in assuring long-term personal and process safety? How often did a PSSR “catch” issues prior to start up? Did startups occur when there were critical to start up items left uncompleted on the PSSR Checklist? Are there overdue action items or deviations in the PSSR Deviation Management system? Were there any bottlenecks in this procedure? What other resources, techniques, or tools could be used to make future PSSRs more effective? Were the questions on the PSSR forms answered with individual consideration (in other words, not just “checking the box” or “pencil-whipping”)? Are regular PSSR audits occurring and are PSSR checklist forms being reviewed? Metrics Below are suggested leading and lagging metrics to validate the efficacy of the PSSR Procedure. Measurement Objective Process Metric PSSR Execution Adherence to PSSR Procedure Number of PSSRs that were not completed prior to startup of a system and why incomplete. (MOC F&O Process requires 100% completion of PSSRs for MOC.) This is already tracked through the MOC process and Non-MOC PSSR metrics will not be developed or tracked as part of this Standard. Post-startup actions are being completed PSSR Deviation Management Number of open and overdue PSSR deviations. This will not be tracked at this point. PSSR Checklist Quality PSSR as Related to MOCs Quality review is performed on 10% of all PSSRs submitted to close MOCs (Required by MOC F&O Process). This is already tracked through the MOC process and Non- MOC PSSR metrics will not be developed or tracked as part of this Standard. Strive for 0 incidents in startup and continued operations Procedure Effectiveness Startup-related incidents with PSSR failure as an identified root cause. This will not be tracked at this point. Improvements to Upstream PSSR Standard Upstream Capability - Base Business & Operations is the owner of the Upstream PSSR Standard and is responsible for its review and update. A review of this procedure is required every three years at a minimum to ensure it remains relevant and current. The Upstream PSSR Standard falls under Upstream governance and requires endorsement by the Enterprise Governance Board for any major changes. Suggested improvements to the procedure should be routed to Upstream Capability - Operations. 344 Abbreviations Acronym Definition AI Asset Integrity BU Business Unit CPDEP Chevron Project Development and Execution Process CRR Construction Readiness Review DRM Deliverables Reference Manual FD&C Facilities, Design & Construction FE Facilities Engineer HAZOP Hazard and Operability HES Health, Environment and Safety HUC Hook-up and Commissioning JSA Job Safety Analysis MCC Motor Control Center MDM Milestones & Deliverables Map MOC F&O Management of Change for Facilities & Operations OE Operational Excellence OEMS Operational Excellence Management System ORR Operations Readiness Reviews – PRC Ph 4 Assurance or; Operational Readiness Review – start-up review called for in Upstream Operating Procedures Guidance OSHA Occupational Safety and Health Administration P&ID Piping and Instrumentation Diagram PFD Process Flow Diagram PHA Process Hazard Analysis POB Persons on Board POP Project Operations Planning PPE Personal Protection Equipment PRC Project Resources Company PSI Process Safety Information PSM Process Safety Management 345 PSSR Pre-Startup Safety Review PSV Pressure Safety Valve RACI Responsible, Accountable, Consulted, Informed RFSU Ready for Startup ROV Remote Operated Vehicle SDS Safety Data Sheet SME Subject Matter Expert SOP Standard Operating Procedures TCCC Transfer of Care, Custody, and Control Definitions Term Definition Brownfield Projects Projects in which an existing facility or system is modified or upgraded. Deviations The use of the word deviations in this document is specific to PSSR deviations, which are instances when a “No” is checked on the PSSR checklist. Greenfield Projects Projects in which no work is needed on an existing facility or system. Major Capital Projects (MCPs) Projects with CAPEX ≥ $50 MM Chevron share. These may be managed by PRC or within the BU. Ongoing Operations When an asset is operating in accordance with its intended use in a routine manner Operational Readiness Review Organizations may use the term Operational Readiness Review (ORR) to describe the check that occurs to restart a process after no change has occurred or as an operational check that occurs at some time after the PSSR. Operations Readiness Review The PRC Assurance event undertaken on MCPs at pre-determined intervals in CPDEP Phase 4 to demonstrate and to determine the status of the following: Project Readiness to complete and turnover an asset that is ready to operate in conformance with Chevron’s OEMS and BU expectations. Business Unit Readiness to receive and operate the Asset in conformance with Chevron’s OEMS requirements. Small Projects Projects with CAPEX ≤ $50 MM Chevron share. These may be expense, capital, or abandonment projects, etc. and are managed within the BU. 346 Risk A measure of potential loss in terms of the consequences and likelihood that the loss will occur. References EPA regulation 40 CFR Part 68 OSHA regulation 29 CFR 1910.119 Petroleum and natural gas industries – Health, Safety, and Environmental Management Systems Guidelines for Performing Effective Pre-Startup Safety Reviews (Center for Chemical Process Safety) Project Operations Planning (POP): Handbook, Milestones & Deliverables Map, and Deliverables Reference Manual (Owned by Production Support – Base Business & Operations) Systems Completion Handbook (Owned by PRC Systems Completion Center of Expertise) Upstream MOC for Facilities & Operations (Owned by Production Support – HES) Upstream Standard Operating Procedures (Owned by Production Support – Base Business & Operations) 347 Page 35 of 48 Appendix A: PSSR Checklist Example (Use of the MCBU PSSR Checklist is required) Change Definition MOC Number OR Work pack Number MOC Title OR System Name Field / Facility / System Description of System Under Review Linkage to Other PSSRs (MCPs or Turnarounds) List of Participants on PSSR Team Name (Print) Signature Position / Section of PSSR Covered Date Name (Print) Signature Position / Section of PSSR Covered Date Name (Print) Signature Position / Section of PSSR Covered Date Name (Print) Signature Position / Section of PSSR Covered Date Final Approval (Operations) To be filled out after completion of the PSSR Checklist Questions below This checklist is acceptance of new or modified equipment and systems and verification that they are ready for start- up. The Final Approver acknowledges the validity of the questions asked below as well as accepts PSSR Deviations to be managed post-start-up. Name (Print) Signature Position / Title Date Approval Yes No Comment Pre-Start-up Operations Checks (Required For All Changes) This section of checks is required for all changes. Overarching PSSR Checks: Design & Construction Specs, Procedures, PHA, Training Yes No N/A Name/Date: Has the equipment design, construction, and commissioning been completed in accordance with specifications? 348 Upstream Pre-Startup Safety Review Standard For MCPs: Were systems completion database and check sheets reviewed? Has all process safety information (SDS, P&IDs, C&Es, SLDs, plot plans, operating limits and parameters, alarms, safe practices and shutdowns etc.) required for commissioning and operation been made available to all affected operators, updated and stored in the system of record? Are commissioning and start-up procedures and plans in place and approved? Are appropriate procedures in place and adequate? (start-up, safety, environmental, operating, maintenance and emergency) Has the communication or training of affected operating, maintenance, emergency, and contractor workers been completed? Has a PHA been completed and are all PHA/HAZOP/HAZID/safety related actions closed out? Have changes made been reviewed and authorized by the facility management of change (MOC) program? Operations Rep: Confirm Overarching PSSR Checks Complete (Name/Sign/Date) Operational Checks Yes No N/A Name/Date: Have new types of controls/equipment been introduced at this facility? Has there been adequate training conducted on the new equipment and operation? Are personnel whose jobs are impacted by this change knowledgeable of the change (all shifts)? Is start-up of this process/equipment compatible with simultaneous operations (e.g., drilling, hot work, plant, compression, operations, etc.)? Has CMMS been updated with maintenance routines for new / modified equipment? Have critical / operations spares been defined / purchased? Have walk downs been complete? Are open-ended valves and piping such as vents and drains, plugged, blinded, or capped? Is any new Fire / Safety Equipment in place (including any required PPE)? Are bypass valves around equipment or control valves either closed or in the correct position for start-up operations? Is all appropriate instrumentation / measurement equipment open to process? (Sensing ports & valves open) Is all new operation & safety signage in place? 349 Upstream Pre-Startup Safety Review Standard Operational Checks Yes No N/A Name/Date: Has loose material been removed from near air intakes, air-cooled exchangers, rotating equipment, or other areas where it could cause damage when equipment is started? Operations Rep: Confirm Operational Checks Complete (Name(s)/Signature(s)/Date) Pre-Start-up Checks (For More Complex Changes & Projects) Facilities, Design & Construction Electrical & Instrumentation Completion Yes No N/A Name/Date: Has the newly installed or modified equipment been tied-in to the ESD system? Does the electrical system comply with the area electrical classification? Are all electrical covers and housings installed properly and bolts in place and tight? Are conduits sealed? Can emergency automatic isolation valves be activated without exposing personnel to hazardous atmospheres in an emergency involving the equipment they are installed to isolate? Are motors, control stations, motor control centres, starters, breakers, junction boxes, apparatus and devices used for operation of control circuits and appliances properly identified with nameplates? Was grounding for new/modified critical equipment installed and function checked? Are all cable trays, conduits, junction boxes, transformers, starters, etc. supported rigidly in place (do not use process or utility piping for support)? Is all wiring routed a sufficient distance from hot surfaces to prevent damage? Are cathodic protection systems installed and reconnected properly? Machinery & Equipment Yes No N/A Name/Date: Has the machinery/equipment been installed so it will be stable and secure during operation? Is the equipment provided with a clearly identified means to securely isolate from all energy sources? Has equipment alignment and rotation been checked? Is belt driven equipment “sheaved” to run at the specified RPM as per the design? Are drive belts installed and properly tightened? Are start/stop switches properly protected from accidental activation by bumping? 350 Upstream Pre-Startup Safety Review Standard Where required, has an inlet piping strainer been installed to protect equipment? Per Chevron SID is safe access provided and equipment properly guarded? Can newly installed equipment be cleaned, isolated and locked out for maintenance work? Structural Yes No N/A Name/Date: Have all handrails, toe boards and floor grating been installed and secured where needed? Are ladders, scaffolds, platforms, ramps, stairs, and walkways caged and guarded adequately, do they meet Chevron’s (SID) safety in design standards? Valve & Piping Yes No N/A Name/Date: Is piping constructed per the piping specs? (Does pipe wall, flange ratings, gaskets, welds coincide with design requirements?) Has a pressure / leak testing been performed on both piping and applicable vessels / equipment? Have temporary / commissioning pipe work and equipment been removed? Are utility systems commissioned and ready? Have instrument air lines and process tubing been properly supported? Are piping supports adequate, as per design, to prevent damage or undue stress due to pipe span, vibration, valve weight, misalignment, etc.? Where PSVs are relieved to atmosphere, is the discharge routed to prevent injury or damage? Are PSVs in the correct location per P&IDs? Are PSVs set at the relieving pressure designated on the P&IDs? Is safe access to all new/existing control valves or isolation block valves provided? Is back flow protection (check valve) provided where required and are check valves in the correct orientation? Has all buried piping, conduit and wiring been correctly identified and indicated on drawings? Have lines been properly labelled? Have all isolation blinds been returned to their proper start-up positions? Are there sufficient clearances between piping (including insulation, pipe clamps, etc.) and surrounding structure and equipment in the expected hot position during and after thermal expansion? Vessel Yes No N/A Name/Date: 351 Upstream Pre-Startup Safety Review Standard Has work done to the separators/vessels been made as per code and specifications and is documentation complete? Have all packing materials, shipping blocks, stops, preservatives, etc. been removed from equipment? Are vessel internals (e.g., trays, packing, mist pads) in place and secured? Have all man ways / openings been properly closed and nozzle connections bolted up correctly? Do pressure vessels have name plates with code stamp and the correct pressure / temperature rating as shown on the P&IDs? Where required and in accordance with design, have anchor bolts and tie- downs been installed to secure pressure vessels or equipment, correct size & type of bolt? Additional Design Checks Yes No N/A Name/Date: Add any BU operation-specific questions, such as questions around pipelines, marine, subsea, or specific equipment. Has new technology, processes, or equipment that is new to the facility been supported by SMEs been involved in its implementation? Has necessary telecom / communication equipment been provided and function tested? Are the utility systems (flare, electrical, process water, etc.) connected at the correct points? Are the utility systems (flare, electrical, process water, etc.) properly sized? Are hot surfaces adequately protected from exposure to flammable materials? Are hot surfaces adequately protected from exposure to employees? Has personal protection been specified for hot surfaces? Are there adequate measures/safeguards in place to prevent unauthorized access to facility, equipment, computers, process systems/software? Are dissimilar metals (such as between aluminium fittings, conduits, etc and steel) kept from contact to prevent galvanic corrosion? Is the commissioning and start-up plan approved? Technical Rep: Confirm Facilities, Design & Construction Checks Complete (Name(s)/Signature(s)/Date) Asset Integrity & Process Control Yes No N/A Name/Date: Have checks and inspections been made to ensure that integrity critical equipment is installed properly and consistent with design specifications, 352