192 Yer Pe I35 0011

Yanbu Export Refinery Project
PROJECT DESIGN BASIS 192B.1 SPECIFICATIONS - Project Specification For Foundation Fieldbus (FF) Document No.: 192-YER-PE-I35-0011 Revision No.: FF Issue Date: 24 April 2008
TABLE OF CONTENTS 1.0 2.0 2.1 2.2 3.0 3.1 3.2 3.3 3.4 3.5 4.0 4.1 4.2 5.0 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 6.0 PURPOSE................................................................................................................... 4 SCOPE........................................................................................................................ 5 EPC Contractor Deliverables ...................................................................................... 5 MAC Deliverables........................................................................................................ 6 REFERENCE DOCUMENTS & STANDARDS ........................................................... 6 Conflicting Requirements ............................................................................................ 6 YERP Reference Documents...................................................................................... 6 Saudi Aramco Engineering Standards ........................................................................ 6 Saudi Aramco Materials System Specification............................................................ 6 Project Specific Documents and Drawings ................................................................. 7 DEFINITIONS & ABBREVIATIONS ............................................................................ 7 Definitions.................................................................................................................... 7 Abbreviations............................................................................................................. 10 SYSTEMS AND DESIGN.......................................................................................... 10 Operating Areas ........................................................................................................ 11 Foundation Fieldbus Application ............................................................................... 11 Basic Segment Loading Requirements ..................................................................... 12 Segment Execution Time .......................................................................................... 12 Requirements for PID Control in the Field Device..................................................... 13 Final Element Configured Fail State.......................................................................... 13 Segment Loading ...................................................................................................... 14 FF ISD Naming.......................................................................................................... 15 WIRING DESIGN ...................................................................................................... 15
General Confidential Page 2 of 20

6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 7.0 7.1 7.2 8.0 8.1 8.2 8.3 9.0 9.1 9.2 10.0
Segment Topology .................................................................................................... 15 Cable ......................................................................................................................... 15 Field Junction Boxes ................................................................................................. 15 Wiring Polarity ........................................................................................................... 15 Field Wiring Technique.............................................................................................. 16 Fieldbus Power Consumption ................................................................................... 16 Shielding.................................................................................................................... 16 Grounding.................................................................................................................. 16 FIELDBUS DEVICES ................................................................................................ 16 Interoperability........................................................................................................... 16 Temperature Multiplexer Transmitters ...................................................................... 17 NON-DEVICE ELEMENT SECTION......................................................................... 17 FOUNDATION Fieldbus Power Supplies (FFPS).................................................. 17 Terminators ............................................................................................................... 18 Repeater.................................................................................................................... 18 DOCUMENTATION................................................................................................... 18 Piping & Instrumentation Diagrams (P&IDs) ............................................................. 18 Instrument Segment Diagrams.................................................................................. 19 MAINTENANCE SHOP FIELDBUS SYSTEM & TOOLS .......................................... 19

1.0
PURPOSE The purpose of this Specification together with the referenced Saudi Aramco Standards, Specifications, and Project documents is to describe the minimum technical and functional requirements of FOUNDATION Fieldbus (FF) for the Yanbu Export Refinery Project Process Automation System (PAS). This specification defines the requirement for design, specification, installation, configuration, commissioning and maintenance for a FOUNDATION Fieldbus based control system. FOUNDATION Fieldbus systems include instruments and hosts that cover all applications and aspects of instrumentation and control. Therefore, it is intended that all Saudi Aramco standards apply to FOUNDATION Fieldbus systems, except as noted herein. Note, however, that only those standards called out by name within this document are specifically referenced. EPC CONTRACTOR(s) and the Main Automation Contractor (MAC) shall use this document as the basis for design and shall ensure that sound engineering practices are followed throughout. Where EPC CONTRACTOR or MAC wishes to propose an alternative to achieve a more effective system then this will be considered by YERP Project Management Team (PMT). All such comments, conflicts, suggestions or alternatives shall be directed to YERP PMT in writing, and shall receive approval in writing prior to implementation. The final design basis shall be reflected in future revisions of this document. The Yanbu Export Refinery Project (YERP) is the development and installation of a new Grassroots full conversion refinery in the Kingdom of Saudi Arabia that will process Arabian Heavy crude into gasoline, diesel, and LPG products. As currently defined, the refinery will also modify existing terminal facilities for import of crude feed and export of products. The refinery will be located in Yanbu Industrial City on the west coast of Saudi Arabia on the Red Sea. The entire project includes refinery process units, utilities and interconnecting piping, associated feedstock and refined product storage / logistics facilities, as well as the offsite services necessary to support the safe and efficient operation of the refinery. For the purpose of maintaining plant production during maintenance periods or in the event of major failures of equipment the plant has been divided into Operating Areas. The loss of one Operating Area shall not affect the function and operation of control systems and equipment in any other Operating Area.

This includes, but is not limited to, the following process and utility units: 2.0 2.1 Crude Distillation Unit (CDU) Distillate Hydrotreater (DHT) Hydrocracker (HCK) Delayed Coker Unit (DCU) Saturated Gas Plant (SGP) Naphtha Hydrotreater (NHT) Isomerization Unit (ISM) CCR Reformer (CCR) Benzene Extraction Unit (BEU) Hydrogen Generation Unit (HGU) Amine Regeneration Unit (ARU) Sulfur Recovery Unit (SRU) Sour Water Stripper (SWS) Utilities / Waste Water Treating / Steam Generation / Tank Farm
SCOPE EPC Contractor Deliverables EPC CONTRACTOR shall have the overall responsibility for complete site integration of the PAS FF system (with collaboration of the MAC). This may include but need not be restricted to the following: FF Wiring Design FF Field Wiring Field Wiring Blocks (FF Device Couplers) FF Field Terminator FF Field JB Segment Design/Loading Instrument Segment Diagram Designation of the Back-up LAS 1 field device per segment P&IDs Instrument Spec Sheets

2.2
MAC Deliverables The MAC shall have responsibility for all for the following PAS FF System related items. This may include but need not be restricted to the following: H1 Host Foundation Fieldbus Power Supply (FFPS) Bulk Power Supply (BPS) for the FFPS(s) FF Terminator at FFPS Pass through wiring blocks for FF segment trunk in the system cabinet and at the marshalling panel Primary LAS (DCS FF Host) Review of EPC CONTRACTOR documentation to ensure FF suitability of design.
3.0 3.1
REFERENCE DOCUMENTS & STANDARDS Conflicting Requirements Any conflict between this document and any other project specification, or Saudi Aramco standards/specifications, shall be brought to the attention of the YERP PMT for resolution.
3.2
YERP Reference Documents The design, materials and construction of the equipment described herein shall comply with references listed below which are considered part of this specification.
3.3
Saudi Aramco Engineering Standards YERP-SAES-J-902 YERP-SAES-J-904 YERP-SAES-Z-001 Electrical Systems for Instrumentation FOUNDATION Fieldbus (FF) Systems Process Control Systems
3.4
Saudi Aramco Materials System Specification YERP-23-SAMSS-010 YERP-34-SAMSS-913 Distributed Control Systems Instrumentation and Thermocouple Cable

3.5
Project Specific Documents and Drawings 192-YER-PE-I35-0001 192-YER-PE-I35-0002 192-YER-PE-I35-0003 192-YER-PE-I35-0013 192-YER-PE-I35-0027 Main Automation Contractor Scope Definition Project Specification System for Process Automation
Main Automation Contractor Supplier Services Project Specification for Maintenance Training System DCS FF Marshalling Cabinet General Arrangement and Wiring Drawing
4.0 4.1
DEFINITIONS & ABBREVIATIONS Definitions Company Project Management Team (PMT): The Company Project Management Team (PMT) is the group responsible for the management of the entire project and is dedicated to the overall success, development and execution of the work and to ensure alignment across the numerous project interfaces. The PMT consists of Aramco Services Company and ConocoPhillips team members, partner(s), agency personnel, and contractors. These project management resources will form a cohesive, seamless team responsible for the project execution. Saudi Aramco (SA): Saudi Aramco as used in this procedure shall mean Saudi Arabian Oil Company and its affiliated companies, including, but not limited to Aramco Services Company. ConocoPhillips (COP): ConocoPhillips as used in this procedure shall mean ConocoPhillips Company and its affiliated companies, including but not limited to ConocoPhillips Yanbu Ltd. Yanbu Export Refinery Project (YERP): The Yanbu Export Refinery Project (YERP) as used in this procedure, shall also mean the Yanbu Export Refinery Company and its affiliated companies. It is also named as the COMPANY. Contractor or Contractors: Any Design, Construction or Service Contractor(s); Manufacturer(s); Vendor(s); Government Agencies; and other similar organization(s) having a contractual relationship or a prospective contractual relationship with the Company.

When used in this or referenced documents the following words are used in the manner described below: Shall and must are used in the imperative sense. Will is used in the preferred sense. May is used in a permissive sense to state authority or Permission to do the act prescribed or provide the function being defined in the prescribed manner, and the words no person may. Or a person may not. mean that no person is required, authorized, permitted to do the act prescribed, and the words a may not . mean that the item being described is not required, authorized, or permitted in the prescribed manner. Includes means includes but not limited to.
Definitions of Fieldbus terms used in this document are: Connector A connector is a coupling device used to connect the wire medium to a fieldbus device or to another segment of wire. A control loop is a group of function blocks (FBs) that execute at a specified rate within a fieldbus device or distributed across the fieldbus network. A coupler is a physical interface between a trunk and spur, or a trunk and a device. A fieldbus is a digital, two-way, multi-drop communication link among intelligent measurement and control devices. It serves as a local area network (LAN) for advanced process control, remote input/output and high-speed factory automation applications. H1 is a term used to describe a fieldbus network operating at 31.25 kbits/second. Interoperability is the capability to substitute a device from one manufacturer with that of another manufacturer on a fieldbus network without loss of functionality or degree of integration. A link is the logical medium by which H1 fieldbus devices are interconnected. It is composed of one or more physical segments interconnected by a bus.
Control loop
Coupler Fieldbus
H1
Interoperability
Link

Link Active Scheduler (LAS)
A link active scheduler (LAS) is a deterministic, centralized bus scheduler that maintains a list of transmission times for all data buffers in all devices that need to be cyclically transmitted. There is only one active LAS on a H1 fieldbus segment. A link master (LM) is any device containing link active scheduler (LAS) functionality that can control communications on an H1 fieldbus link. There must be at least one LM on an H1 link; one of those LM devices will be elected to serve as LAS. Schedules define when function blocks (FBs) execute and when data and status is published on the bus. A segment is a section of an H1 fieldbus that is terminated in its characteristic impedance. Segments can be linked by repeaters to form a longer H1 fieldbus. Each segment can include up to 32 H1 devices. A spur is an H1 branch line connecting to the trunk that is a final circuit. A spur can vary in length from 1 m (3.28 ft.) to 120 m (394 ft.).
Link Master (LM)
Schedules Segment
Spur
Standard Function (FB)
Block
Standard function blocks (FBs) are built into fieldbus devices as needed to achieve the desired control functionality. Automation functions provided by standard FBs include analog input (AI), analog output (AO) and proportional/integral/derivative (PID) control. The fieldbus foundation has released specifications for 21 types of standard FBs. There can be many types of FBs in a device. The order and definition of standard FB parameters are fixed and defined by the specifications. A terminator is an impedance-matching module used at or near each end of a transmission line. Only two terminators can be used on a single H1 segment. A transducer block (TB) decouples function blocks (FBs) from the local input/output (I/O) functions required to read sensors and command output hardware. Transducer blocks contain information such as calibration date and sensor type. There is usually one TB channel for each input or output of a function block. A transmitter is an active fieldbus device containing circuitry which applies a digital signal on the bus.
Terminator
Transducer Block (TB)
Transmitter

Trunk
A trunk is the main communication highway between devices on an H1 fieldbus network. The trunk acts as a source of main supply to spurs on the network. Configured application layer channels that provide for the transfer of data between applications. Foundation fieldbus describes three types of VCRs: publisher/subscriber, client/server, and source/sink.
Virtual communication relationship (VCR)
A typical fieldbus segment is defined in YERP-SAES-J-904. 4.2 Abbreviations DCS ESD FF FGS HMI ITK IS ISD ISS MOV P&ID PAS PIB PID 5.0 Distributed Control System Emergency Shutdown Foundation Fieldbus Fire And Gas System Human Machine Interface Interoperability Test Kit Intrinsic Safety Instrument Segment Drawing Instrument Specification Sheet Motor Operated Valve Piping And Instrumentation Diagram Process Automation System Process Interface Building Proportional, Integral, Derivative
SYSTEMS AND DESIGN The selection, design and application of process instrumentation and control systems shall meet the requirements stated in this specification, the related YERP specifications as well as referenced Saudi Aramco standards.

5.1
Operating Areas The plant process control system equipment will be grouped on a risk area basis. All field instrumentation and control equipment associated with a particular risk area shall be cabled back to an operating area Process Interface Building (PIB). Details of risk areas and PIBs can be found in Project specifications 192-YERPE-I35-0001 and 192-YER-PE-I35-0002. The design criteria for equipment in classified areas, power supplies, signal wiring, noise and signal interference reduction, and grounding shall be per YERP-SAES-J-902 unless otherwise specified in this document.
5.2
Foundation Fieldbus Application Design of Fieldbus systems shall be per the requirements of YERP-SAES-J-904. The use of Foundation Fieldbus shall be maximized for all regulatory process control devices where a suitable FF device is available and shall also apply to all packaged equipment. The regulatory process control loops shall typically include the following: Monitoring loops (including bearing temperatures) Multiplexed temperature temperatures) Simple PID loops Cascade loops Sequence loops Complex loops MOV control loops monitoring loops (including bearing
Deviation from the above shall be subject to the YERP PMT approval on a case by case basis. Fieldbus will not be used for the following applications: Emergency Shutdown System (ESD) signals due to safety reasons Fire and Gas System (FGS) signals due to safety reasons Time critical applications such as anti-surge control
The FF field junction box must be located in a Zone 2 or safe area, mounting within a Zone 1 area is prohibited. The use of Fieldbus for IS applications shall be subject to approval by the YERP PMT. Deviation from the above and where significant benefits can be demonstrated shall be subject to approval by the YERP PMT.

5.3
Basic Segment Loading Requirements Redundant H1 Interface cards shall be used for all segments. Segments with final control elements shall contain 8 or fewer devices unless approved in writing by the YERP PMT. Segments shall contain no more than 2 final control elements (i.e. control valves, damper actuators, etc.), unless approved in writing by the YERP PMT. On-Off actuators, (i.e. air and motor operated valves - AOVs and MOVs), are not considered final control elements. However when multiple input/output blocks are used for a MOV device, it shall be considered as a final control element and it should have short function block execution time to meet segment execution time requirement. Each segment shall have an enabled backup LAS in a monitoring only field device (i.e. device not used in a control loop). EPC CONTRACTOR shall specify Link Master option in the datasheet of the monitor only device to ensure that the backup LAS function is available. The primary LAS shall reside in the DCS H1 card. Segment hardware and software shall be designed with adequate spare capacity for the future addition of one (1) control loop. (i.e. one (1) transmitter and one (1) final element). This requirement does not prohibit the use of eight (8) devices on a segment, nor the use of 2 (two) final elements. Any time that measurement redundancy is measurements shall be on separate H1 segments. required, the redundant
5.4
Segment Execution Time The suggested number of devices per segment for the following listed execution times are as follows: (Assumption: Control is in the field and function blocks that make up that control loop are on the same H1 segment.). For segments with monitor only measurements, limit segment to twelve (12) devices. For loops requiring 1-second execution time, limit segment to eight (8) devices. For loops requiring 0.5-second execution time, limit segment between four (4) to eight (8) devices (depending upon mix of control loops and monitoring devices). For loops requiring 0.25-second execution time, limit segment to three (3) devices with a maximum of one (1) final control element.

30% of segment Macrocycle time should be allocated for unscheduled communication. 5.5 5.5.1 Requirements for PID Control in the Field Device Single Loop PID Control in the Segment For single PID control in the field device, all function blocks that make up that control loop must reside on the same segment. When all function blocks of a single PID control loop cannot reside on the same segment, the PID control shall reside in the host system controller. When single loop PID control is implemented in the field device, the PID function block shall be implemented in the final control element. 5.5.2 Split Range Control The primary PID control shall be implemented in the DCS host system controller. 5.5.3 Cascade Control The preferred cascade control configuration is to locate each of the cascade loop function blocks and devices on the same segment. The primary PID controller shall reside in the primary measurement transmitter (of master loop) and secondary PID controllers shall reside in the secondary final element (of slave loop). If the primary and secondary loops have devices or function blocks on separate segments, the primary PID control shall be implemented in the DCS host controller. In this case, the secondary loop PID control may be implemented in the secondary final element, if all secondary loop function blocks and devices reside on the same segment. 5.5.4 Testing When software simulation is not available in the host controller, actual field devices shall be used to sample test the PID control in the field devices. 5.6 Final Element Configured Fail State All final control elements shall have a configured fail-state on loss of segment communication.

5.7
Segment Loading The following valve criticality rating and segment loading method shall be used. The valve and associated measurement criticality shall be defined for prudent loading of Fieldbus segments. The following ratings shall be assigned to each final control element (valve).
5.7.1
Level 1 Critical Valves Failure of this valve will result in a total system trip, causing a shutdown of the entire unit, or other unavoidable losses in excess of 1,000,000 US dollars. Level 1 valves and their associated measurement shall reside on H1 segments with no other devices. The Instrument Segment Diagram (ISD) shall show the criticality rating and shall prominently display that no additional devices shall be loaded on this segment. See Exception in YERP-SAES-J-904 paragraph 5.7.3.2.
5.7.2
Level 2 Critical Valves Failure of a Level 2 valve will result in an urgent situation, where prompt operator action would be required to "save" the unit from imminent total shutdown. The material and energy capacity of associated vessels, geographic location, and elevation/accessibility of such valves should be considered. Failure of a Level 2 valve will result in a total system trip, causing a shutdown of the entire unit, or other unavoidable losses in excess of 1,000,000 US dollars. However, the level 2 valve's process dynamics allow time for quick recovery from the failure, either by quickly fixing a fault or by taking manual control. Level 2 valves and their associated measurement shall reside on H1 segments with no other Level 2 valves. The ISD shall show the criticality rating.
5.7.3
Level 3 Valves Failure of this valve will not result in any short-term risk of total unit shutdown. Level 3 valves can go to their fail position without requiring any immediate operator action. Level 3 valves can reside on a H1 segment with other Level 3 valves, or on a segment with a level 2 valve. Consideration should be given to the impact of common mode failures among Level 3 and Level 2 & 3 valves on the same segment. The ISD shall show the criticality rating.

5.8
FF ISD Naming Each Fieldbus ISD will be assigned a name. The Project FF control module and function block naming convention will be developed later.
6.0 6.1
WIRING DESIGN Segment Topology The fieldbus installation shall use the 'tree', 'spur', or 'combination' topology as shown in YERP-SAES-J-904.
6.2 6.2.1
Cable Trunk (Homerun) Cabling Twenty five percent (25%) spare pairs shall be provided for all Fieldbus segment trunk cables, with a minimum of one spare pair. This requirement includes spares on trunk cable runs between marshalling racks and junction boxes and between field junction boxes. Refer to 192-YER-PE-I35-0002 for the reference on Instrument Cable Specifications.
6.3
Field Junction Boxes All trunk cables connections in the field junction boxes, including pass through trunk pairs without spurs, shall be terminated on approved FF Device Coupler (wiring block) specifically made for FOUNDATION Fieldbus networks. MAC will consult with the EPC Contractor to specify the recommended FF Device Coupler. EPC CONTRACTOR will furnish the FF Device Couplers. The FF Device Coupler supplied shall be available in a minimum of six (6) spur and ten (10) spur configuration.
6.4
Wiring Polarity Wiring polarity shall be maintained throughout the segment design and installation.

6.5
Field Wiring Technique The FF device wiring terminations shall be as per requirements specified in YERP-SAES-J-902. No modular wiring components shall be used, (i.e. passive multiport junctions (bricks), molded connector cordsets, plug in junction connectors, etc.).
6.6
Fieldbus Power Consumption The MAC will consult with the EPC CONTRACTOR on the project FF segment design. The EPC CONTRACTOR will provide the FF segment design to the MAC for implementation in the PAS.
6.7
Shielding Fieldbus cable shield terminations shall be per requirements specified in YERPSAES-J-902. Ground the shield of the network cable in one place only. Location of the shield grounding is at the PAS. Shield continuity to be maintained from the PAS to the field device At a field instrument, insulate the shield and do not connect the cable shield to the instrument ground or chassis.
6.8
Grounding Field instruments and instrument stands shall be grounded per requirements specified in YERP-SAES-J-902.
7.0 7.1
FIELDBUS DEVICES Interoperability The FF Device and all function blocks shall be tested and certified by the MAC as part of the design and testing of the PAS Host DCS. The EPC CONTRATOR shall ensure the device supplier delivers devices with the Tag No and Node address set as per the MAC requirements. MAC shall provide a list of devices supported by FF Host (which has passed the HIST) which will ensure they are Interoperability Test Kit (ITK) certified to EPC CONTRACTOR. It is to ensure all proposed fieldbus instruments shall support easy set-up and calibration from the PAS. EPC CONTRACTOR shall arrange unlisted FF devices to be tested in MAC Interoperability Laboratory (IOL).

EPC CONTRACTOR shall ensure field device support menus and methods to allow easy set-up and calibration from the Asset Management System (AMS). EPC CONTRACTOR shall arrange with the suppliers to bring each type of device to MAC engineering location for Factory Acceptance Test (FAT). 7.2 Temperature Multiplexer Transmitters FF temperature multiplexer transmitters may be used where high density temperature measurements are required for PAS indication. Temperature multiplexers shall not be used for control loops without approval by the YERP PMT. Where additional monitoring devices are connected to a segment the quantity of temperature multiplexer transmitters shall be limited to three per segment. With this segment design, communication of the temperature signals from the Multiplexer Analog Input FB will be performed during the unscheduled communication period of the macrocycle. Meaning a delay may be experienced between a change in measured variable and when that change is displayed at the HMI. Evaluation and verification whether this delay is acceptable for the particular process application shall be confirmed. With the approach where a segment shall be dedicated for the use of temperature multiplexers only; then eight multiplexers may be connected to one segment, with two spares for future use. To ensure that failure of an individual temperature multiplexer will not impact on the ability to monitor an item of plant equipment, measurements shall be allocated to different multiplexers, each connected to separate FF segments. Where the density of temperature measurements makes this approach uneconomic, the design shall revert to individual FF temperature transmitters. 8.0 8.1 NON-DEVICE ELEMENT SECTION FOUNDATION Fieldbus Power Supplies (FFPS) FFPS unit alarms may be ganged together within a single FF marshalling cabinet, but kept separate from the common BPS feed and other cabinet alarms. The primary and secondary BPS shall feed both ends of the ganged FFPS per the Aramco Specifications.

Failure or faults in any of the redundant FFPS shall be annunciated in the PAS FF Host system. A common alarm for all FFPS in a single FF marshalling cabinet may be used. The FFPS equipment will be supplied by the MAC and installed in the PAS FF marshalling cabinets. The FF segment trunks will be connected to wiring blocks located in the marshalling panels by MAC. All field wiring connections for the FF segment trunks will connect at the marshalling panels by the EPC CONTRACTOR. 8.2 Terminators A terminator may be incorporated into the design of the selected field FF Device Coupler. 8.3 Repeater Repeaters shall not be used. 9.0 DOCUMENTATION The MAC will supply the FOUNDATION Fieldbus system design documentation, as required, similar to a conventional PAS design. Documents can be altered for FOUNDATION Fieldbus architecture. Documentation alterations, additions, and deletions required for FF use are defined below. 9.1 Piping & Instrumentation Diagrams (P&IDs) Fieldbus instrumentation shall be shown on the P&ID per Saudi Aramco standards with the following exceptions: Fieldbus instrument balloons shall be conventional, with the addition of a FOUNDATION Fieldbus indication on the top right side of the instrument bubble, shown as: FF The line symbology for FF signal wiring shall be shown as standard dashed electric signal. The control or logic function balloons shall be shown independent of the hardware in which it is contained. All functions within the same field device shall be tagged with the same number, with individual function lettering appropriate for the application.

9.2
Instrument Segment Diagrams The Instrument Loop Diagram (ILD) shall be replaced with an Instrument Segment Diagram (ISD) for FF loops. The ISD is a hardware-wiring diagram intended to show the physical connections and layout of the segment. Soft data including display, function block, and configuration data shall not be shown. In addition to standard loop drawing information, ISDs shall include the following FF system details: The title block shall contain the 'segment name'. All segment connections inclusive of the H1 interface card, BPS, FFPS, through the field devices, terminations, junction boxes, and terminators. All segment and field device tagging. All spur cables shall be labeled with the instrument tag number. All cable distances with voltage drop calculation results. The 'risk assessment and segment loading' philosophy chosen by the Proponent Organization shall be clearly shown on the ISD. The Backup LAS device shall be identified. Terminator locations shall be clearly identified.
10.0
MAINTENANCE SHOP FIELDBUS SYSTEM & TOOLS This shall form part of the Maintenance Training System (MTS) covered under 192-YER-PE-I35-0013. The MAC shall be responsible for supplying a complete Fieldbus maintenance system except FF Device couplers which shall be supplied by EPC CONTRACTOR. The intent of this maintenance system is to allow Fieldbus instrument troubleshooting, calibration, and setup in the instrument maintenance shops. The Maintenance Fieldbus system will include all system hardware, software, and auxiliary equipment required to connect and maintain Foundation Fieldbus devices in the shop. Equipment shall include a sample of all PAS hardware and software with Operator/Engineering workstations, control network with appropriate switches, chassis with controller & power supplies, redundant H1 cards, Bulk and FOUNDATION Fieldbus power supply (FFPS), and FF Device Couplers. The Device Couplers shall be externally mounted and easily accessible to maintenance technicians. The I/O chassis, power supplies, wiring and terminal blocks will be pre-wired and installed in an easy to access, caster mounted cabinet.

The MAC shall supply, as required, all standard tools, test software, and test and calibration equipment required for the Foundation Fieldbus system. EPC CONTRACTOR shall supply special tools or device testers special to a device. A list of the above tools, test and calibration equipment shall be submitted to YERP PMT for review and approval. Standard maintenance tools and equipment, defined above, are available from standard catalogs. The list of the standard tools and testing and calibration equipment required shall identify the following:
Description of its service or simulation application.

Manufacturer and Catalog No. Quantity recommended.

192 Yer Pe I35 0011

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

192 Yer Pe I35 0011

Uploaded by

Copyright:

Available Formats

Yanbu Export Refinery Project

Yanbu Export Refinery Project

General Confidential Page 3 of 20

Yanbu Export Refinery Project

General Confidential Page 4 of 20

Yanbu Export Refinery Project

Yanbu Export Refinery Project

General Confidential Page 6 of 20

Yanbu Export Refinery Project

General Confidential Page 7 of 20

Yanbu Export Refinery Project

General Confidential Page 8 of 20

Yanbu Export Refinery Project

Link Active Scheduler (LAS)

Link Master (LM)

Standard Function (FB)

Transducer Block (TB)

Yanbu Export Refinery Project

Virtual communication relationship (VCR)

General Confidential Page 10 of 20

Yanbu Export Refinery Project

Yanbu Export Refinery Project

Yanbu Export Refinery Project

General Confidential Page 13 of 20

Yanbu Export Refinery Project

Yanbu Export Refinery Project

General Confidential Page 15 of 20

Yanbu Export Refinery Project

Yanbu Export Refinery Project

General Confidential Page 17 of 20

Yanbu Export Refinery Project

General Confidential Page 18 of 20

Yanbu Export Refinery Project

General Confidential Page 19 of 20

Yanbu Export Refinery Project

Description of its service or simulation application.

General Confidential Page 20 of 20

You might also like