SPECIFICATION FOR FOUNDATION FIELDBUS

INDEX
CLAUSE DESCRIPTION PAGE
1 Scope 4
2 Conflicts and Deviations 4
3 References 4
4 Definitions 5
5 System Design 6
6 Wiring Design 7
7 Fieldbus Devices 12
8 Non-Device Element Selection 13
9 Host Requirements 15
10 Consideration For Detail Engineering 18
11 Documentation 18
12 Factory Acceptance Test (FAT) 20
13 Site Acceptance Test (SAT). 21
14 Installation and Checkout 21
15 Maintenance Shop Fieldbus System and Tools Level Update 21
16 Fieldbus Spare Parts and Revision Program 22
17 Foundation Fieldbus Training 22
Annexure A Fieldbus Glossary of Terms 25

1 SCOPE
The use of FOUNDATION Fieldbus based control system is to be followed in the Refinery expansion
project of Essar Oil Limited, Vadinar, Jamnagar.
This specification defines the requirement for design, specification, installation, configuration;
commissioning and maintenance for FOUNDATION Fieldbus based control systems.
The specification covers the minimum requirements for the design and installation of H1 Foundation
Fieldbus (FF) system based on 31.25 kbps physical layer as defined in ISA 50.02
This specification is intended for use by Detail engineering contractor and by Control System vendor for
integrated services.
FOUNDATION Fieldbus systems include instruments and host that covers all applications and aspects
of instrumentation and control.
A FOUNDATION Fieldbus based control system shall not be used for the following systems
Emergency Shutdown System
Fire and Gas System,
Burner Management System,
Compressor Anti-surge Control System
Close Loop Control with scan time faster than 300 msec.
Discrete Motor Monitoring & Control System
Complex Control loops with multiple maths function
Instruments commercially not available (Nucleonic Instruments)
Packages Control System

2 CONFLICTS AND DEVIATIONS

Any conflicts between this Specification and other applicable Engineering Standard, Materials System
Specifications, Standard Drawings, or industry standards, codes, and forms shall be resolved in writing by
the Essar Engineering Centre, Mumbai.

3 REFERENCES
3.1 Essar Engineering Centre References
3.2 Industry Codes and Standards
The International Society for Measurement and Control (Refer latest standards)
ISA 5.1
ISA 50.02, Part 2
FF-569 FOUNDATION
FF-816 FOUNDATION
FF-890 FOUNDATION
AG-163 FOUNDATION
AG-181 FOUNDATION
AG-140 FOUNDATION

Instrumentation Symbols and Identification

Fieldbus Standard for Use in Industrial Control Systems, Part
2: Physical Layer Specification and Service Definition
Fieldbus Host Interoperability Support Test Procedures
Specification 31.25 kbits/s Physical Layer Profile
Specification Function Block Application Process
Application Guidelines for 31.25kbps & IS System
System Engineering Guidelines.
Application Guidelines for 31.25kbps & wiring system

FF 940 FOUNDATION
IEC61158-2

IEC60079-27

NFPA 70

Communication Profile
Digital data communication for measurement and control
fieldbus for use in Industrial control system Part 2 through Part
6
Electrical apparatus for explosive gas atmosphere Part-27:
Fieldbus intrinsically safe concept (FISCO) and Fieldbus nonincendive concept (FNICO)
National Electrical Codes (National Fire Protection
Association)

4 DEFINITIONS
All definitions of Fieldbus terms and acronyms used in this document can be found in appendix 'A'.
A typical fieldbus segment that shall consist of the following components, reference Figure 1:
H1 - Foundation Fieldbus Interface Card (Redundant)
FFPS - Foundation Fieldbus Power Supply (Redundant)
JB - Junction Box
BPS - Bulk power Supply (24 V DC) (Redundant)
FBB - Foundation Fieldbus Barrier
HPT - High Power Trunk
Fieldbus Devices, (e.g., transmitters, transducers, Temp Multiplexers etc.)

Figure 1 Fieldbus Segment Components

Live Service not allowed on trunk upto last JB
5 SYSTEM DESIGN
The philosophy of selection, design and application of process instrumentation on Foundation Fieldbus
shall be based on intrinsically safe (IS) installation in hazardous areas. The High Power Trunk (HPT)
design shall be adopted which by definition of the HPT is a technique that combines different safety
techniques to allow high power on the trunk and intrinsically safe or energy limited output on the spurs.
The HPT approach meets the intrinsically safe EEx ia FISCO requirement at the field device level and
uses increased safety techniques (EEx e) for the trunk. This combination of safety techniques allows the

full implementation of 32 devices, 1900 m total cable length (Trunk + Spur) with type A cable, 100 m
maximum spur length without compromise, even when connecting to FISCO field devices.
The HPT design for intrinsically safe applications uses the Fieldbus barrier that is situated within an EEx e
enclosure taking its power from 2-wire field bus trunk and behaves like a 4 output EEx ia FISCO power
supply. As the trunk uses EEx e safety techniques for its protection, conventional fieldbus supplies can be
used, providing typical outputs in the region of 24-32V at 350 mA - 500 mA.
The use of conventional fieldbus supplies enables the provision of true redundancy for both the H1 host
and the power supplies, ensuring system availability in the case of failure. By using conventional fieldbus
supplies, Advanced Diagnostics on the fieldbus physical layer also becomes available, providing
predictive maintenance on a part of the installation that typically causes most problems.
The fieldbus barrier design concept shall ensure the following:
1. Intrinsic safety on the outputs (spurs)
2. Galvanic isolation between the non IS fieldbus segment (Trunk) and the IS fieldbus segment (spurs)
and between the output circuits. The Trunk is galvanically isolated from the outputs.
3. Fieldbus terminator connected at both end of the FF trunk.
FF design should be followed for all monitoring & Control loops. For skin temperature monitoring FF
multiplexer shall be used.
5.3 Basic Segment Loading Requirements
Note: Prior to defining Fieldbus segments, the process control strategy should be complete, the P&IDs
available, instruments selected, and instrument locations determined.
Redundant H1 Interface cards shall be used for all segments.
Each segment shall have an enabled backup Link Active Scheduler (LAS) in a field transmitter device.
Note: The preferred location of the backup LAS is in a monitoring only (i.e., not used for control) field
device.
The 'primary' LAS shall reside in the H1 interface card.
5.4 Segment Executions Time
The suggested number of devices per segment, for monitoring shall be limited to twelve (12) devices.
Each segment shall operate with a single specified macrocycle execution time. Multiple macrocycles shall
not be used on a single segment, even if available in a vendor's particular product.
The vendor's configuration software shall automatically allocate sufficient unscheduled (free
asynchronous) time as required by the vendor.
Notes: Function block execution frequencies must be compatible with both system loading and process
control objectives. The execution frequency of all function blocks contained within a single fieldbus
segment is defined by that segment's macrocycle time. This macrocycle time, which can typically range
from 250ms to several seconds (depending on the nature of the application), is configured for each
fieldbus segment. Some vendor's configuration products allow devices on the same segment to operate
at different macrocycle times.
However, backup LAS devices are not capable of managing these multiple macrocycles, so this feature
may not be used. The order of execution should be automatically determined by the vendor's
configuration software, based on the connections between function blocks on the fieldbus segment.

Note that the macrocycle contains unscheduled time required for non-deterministic bus communications,
such as alarm transmission, set point changes, etc. The vendor's recommended unscheduled time should
be allocated for each macrocycle. Note that the minimum may change based on how much bus required
communication is configured as deterministic. While it is hoped that the vendor's configuration software
will manage and maintain minimum unscheduled time, this is not necessarily true, and must be verified.
Network \ Segment Execution Time.
The network/segment macro cycles should match the DCS module execution times. Each
network/segment should operate with a single specified macro cycle execution time. Multiple macro
cycles shall not be used on a single network/segment without the approval of Client. Care should be to
ensure that the network does not become overloaded.
Use a default segment execution time of one (1) second unless otherwise approved by the Client. Further
guidance on segment times is given below.
Network/Segment Execution Time
The network/segment macro cycles should match the module execution times.
Macrocycle
The Macrocycle should have minimum of 50% unscheduled (free asynchronous) time. The unscheduled
time Calculation shall allow for spare capacity requirement. Therefore newly commissioned segment
should have minimum of 50% unscheduled time.
The suggested maximum numbers of devices per segment for the following listed execution times are as
Follows:

For segments with monitor only measurements, limit segment to twelve (12) devices. (10 in use +
2 Spare)
For loops requiring 1-second macrocycle time, limit segment to twelve (12) devices with 4 valves.
(6 TX+ 4 CV+ 2 SPARE)
For loops requiring 0.5-second macrocycle time, limit segment to six (6) devices with 2 valves. (2
TX+ 2 CV+ 2 SPARE)
For loops requiring 0.25-second macrocycle time, limit segment to three (3) devices with 1 valve.
(1 TX+ 1 CV+ 1 SPARE)

Typically

1 Second macro cycle time to be considered for all parameters other than temperature monitoring
2 Second macro cycle time to be considered for temperature monitoring points
Each macro cycle should have a minimum of 50% unscheduled time with allowances for spare
capacity Requirement

In line with the above the segment loading philosophy:

Typical calculation for MUX
- Assuming each MUX has a macro cycle time of 8 x 32 msec = 256 mSec, Max of 4 MUX shall be
connected to each segment having 2 sec macro cycle time. (They can be connected to any FBB).
Each MUX shall be connecting to 6 elements (T/c or RTDs 2 spare channels left for future
elements).
No other FF devices shall be assigned to this segment.
- Assuming each FF device other than MUX has a macro cycle time of 40 mSec, for 12 FF devices,
the scheduled time shall be 12 x 40 = 480mSec. Hence 12 FF devices can be accommodated in

each segment with a 1 sec macro cycle time. As defined in the FF design spec, 10 devices are to
be considered per segment with 2 as future spare.
Generally, MUX will not be combined with other FF devices in the same segment, however, if a
situation arise where combination of FF devices and MUX would be required, the loading of the
devices shall follow the Segment macro cycle time of 1 second.
In such a case, there shall be 1 MUX + max of 6 other FF devices (Including 2 futures spare).
Accordingly the total cycle time would be 1 x 256 mSec + 6 x 40 mSec = 496 mSecs.

5.5 Control Element Definition (FF Loop Criticality)

Criticality Level 1
Failure of a Level 1 valve will result in a total system trip, causing a shutdown of the entire unit, or other
Unavoidable losses in excess of $10M. Normal Valve failure mode is to be used for this classification.
Application: Level 1 positioners with their associated measurement device shall reside on H1 Segment
with no other Control loops. Additional monitoring devices may be allowed.
Criticality Level 2
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 $100K. However, the Level 2 valves process dynamics allow time for
quick recovery from the failure, either by quickly fixing a fault or by taking manual control. The material
and energy capacity of associated vessels, geographic location, and elevation/accessibility of such valves
should be considered. The difference in Level 1 and 2 valves are dependent on operations ability to
respond to a single Failure.
Application: Level 2 positioners with their associated measurement shall reside on H1 Segment with no
other Level 1 or Level 2 Positioners and can have one Level 3 Positioner. (i.e. Total of 2 Positioners
maximum).
Criticality Level 3Failure of this valve will not result in any short-term risk of total unit shut down or major operating losses.
Level 3 valves can go to their fail position without requiring immediate operator action.
Application: Level 3 positioners with their associated measurement shall reside on H1 Segment, up to 2
other level 3 Positioners (i.e. Total of 3 off level-3 positioners maximum). Consideration should be given to
the impact of common mode failure on the same segment. Regulatory control loop associated with
spared vital and essential equipment should be allocated on different segment.
Criticality Level 4- No Control
Failure of this Level 4 devices are measurement only devices that shall not be used for control and may
be configured in a way that could interrupt control on a network/segment. This class includes MAI, MAO,
MDI, and MDO block communication devices.
Application: All Open Loops shall reside on H1 Segment, up to maximum of 12 (10 in use+ 2 Spare)
devices per segment

5.6 FF Control Module & Function Block Naming

Each Fieldbus control strategy or module will be named based on a reasonable and consistent format for
the facility. The naming convention shall be reviewed by Essar Engineering Centre.
5.6.2 Unless specified differently, each FF function block shall use a field device tag name for its main
descriptive =name and a 'suffix' defining the function or block type for which it is defined

(e.g., FT5010_AI, FT5010_AO, etc.).

5.6.3 In the event that a FF device has more than one identical function block, each shall be uniquely
identified with
a sequential numeral
(e.g., FT5010_AI_1, FT5010_AI_2, etc.).

6 WIRING DESIGN
6.1 SEGMENT TOPOLOGY
The fieldbus installation shall use the 'tree', or 'combination' topology as shown in Figure-2. The spur and
daisy chain topology (i.e., routing the trunk directly through each device) shall not be used.
Notes: Components of fieldbus segments can be connected together in various architectures known as
topologies.The topology selected is usually driven by the physical device location in order to reduce
installation costs. Hence, plot plans are used in addition to P&ID's and instrument indexes in the
design of a fieldbus segment.
Most often, after the above design considerations are weighed, the following three topologies are used:
(See
Figure 2)
A tree topology is used when several related instruments are physically located close to
each other. A fieldbus junction box is located close to the instruments with spurs
extending from it to each instrument.
A spur topology is used when several related instruments are located in the same
direction from the host device but not necessarily close to each other. In this case, a
trunk line is extended from the host to the farthest instrument and spurs are extended
from it as it runs past each instrument. It is not to be followed.
A spur/tree topology is used when some combination of the above instrument locales
exists. Note that spurs are permitted to extend only from trunk lines and not from other
spur lines.
Daisy chain topology may appear to reduce total wiring run length and connection cost, but it has a
significant disadvantage. That disadvantage is maintainability and reliability downstream of each device.
When a device is removed from a daisy chain topology segment, all downstream devices are also
disconnected.
Trunk
Spur
To H1
Card

Tree Topology
Junction
Box (JB)
To H1
Card

Spur Topology
To H1
Card
Junction
Box

Combination
Topology
To H1
Card

Daisy-Chain
Topology
(JB) (JB) (JB) (JB)
(JB)

Do Not Use

Figure 2 Fieldbus Topologies

6.2 DISTANCE CONSTRAINTS
6.2.1 The maximum allowed length of a fieldbus segment is 1900 meters (6232 ft.) with Type A cables.
This

total segment length is computed by adding the length of the main trunk line and all the spurs that extend
from it.
Do not use
6.2.2 Total Segment Length = Trunk + All Spurs
Note: The maximum length given is specified in the ISA 50.02 Fieldbus standard. The length of a
segment is limited by voltage drop and signal quality (i.e., attenuation and distortion).

6.3 SPURS
6.3.1 Only one (1) FOUNDATION Fieldbus (FF) device shall be connected to each spur.
6.3.2 Though the maximum spur length can be 120 meters (394 ft.) but 100 meters (max) is to be
considered for
design. The spur length is the length of the cable from the 'wiring block' to the FF device.
Note: A spur is a drop off of the main trunk line. The trunk is considered to be the main cable run and will
contain segment terminators at each end.

6.4 CABLE TYPES

6.4.1 Trunk (Homerun) Cabling
6.4.1.1 Either ISA 50.02 Type 'A' cable 18 AWG , 5 pair individually shielded cable (Belden or
Equivalent) shall be used for all trunk wiring.
6.4.1.2 Four pair shall be used for the 4 segments and the one pair will be kept as spare.
Between integrated JB / primary & secondary JB, the trunk shall be 1 pair, Type A, 18 AWG
6.4.2 Spur Cables
Single pair Type 'A' cable 18 AWG, as defined in ISA 50.02, shall be used for all spur cabling.
6.4.3 Color Coding
6.4.3.1 For all FF cables, spur and trunk, the outer jacket color shall be orange.
6.4.3.2 For all FF cables, spur and trunk, the conductor color code shall be;
(+ Signal) Orange
(- signal) Blue
Drain/shield Tinned copper conductor

6.5 WIRING POLARITY

Wiring polarity shall be maintained throughout the segment design and installation.

6.6 FIELDBUS POWER CONSUMPTION

6.6.1 Fieldbus devices may be powered either from the segment (bus), or locally powered, depending on
the device
design.
6.6.2 The total current draw from all devices on the segment must not exceed the rating of the FFPS '
FOUNDATION Fieldbus Power Supply'. The segment design must take into account:
6.6.2.1 Total device quiescent current draw.
6.6.2.2 One spur short circuit fault (i.e., ~50 mA additional current draw).
6.6.2.3 25% additional current load over and above that calculated from 6.6.2.1 and 6.6.2.2 above.
Commentary Note: The acronym 'FFPS' will be used in lieu of 'fieldbus power supply' throughout this
document to avoid confusion with the bulk power supply (BPS).
6.7.3 The number of bus powered (two-wire) devices on a segment is limited by the following factors:
6.7.3.1 Output voltage of the FFPS.
6.7.3.2 Current consumption of each device.
6.7.3.3 Location of device on the segment, (i.e., voltage drop).
6.7.3.4 Location of the FFPS.
6.7.3.5 Resistance of each section of cable, (i.e., cable 'type').
6.7.3.6 Minimum operating voltage of each device.
6.7.3.7 Additional current consumption due to one spur short circuit fault, ~50 mA.
6.7.3.8 25% spare capacity.
Commentary Note: The length of a fieldbus wiring system and the number of devices on a segment
are limited by power distribution, attenuation and signal distortion. The ISA 50.02 estimates how long
a fieldbus cable can be and still have adequate signal quality, (i.e., acceptable attenuation and
distortion). Calculating power distribution for a segment is relatively simple and can be easily
performed.

6.8 VOLTAGE DROP

6.8.1 Circuit analysis shall be carried out for each fieldbus segment to determine the operating voltage at
each
device. The calculated voltage at the device shall exceed the devices minimum voltage rating by 4 volts,
(e.g., minimum Vdc required by device = 9 volts, therefore the calculated minimum voltage seen at the
device shall be 13 Vdc).The calculated voltage at each device shall be shown on the Instrument Segment
Diagram (ISD) or Bus Coupler Arrangement Drawing.
Commentary Notes: The additional 4-volts at each device have been specified as a spare power margin
for
future device additions to the segment.
Per the FOUNDATION fieldbus specification, field devices must sense a DC voltage between 9 and 32 volts
for
proper operation.
The power used by fieldbus devices varies by device type and manufacturer. Specific minimum voltage
and
current requirements are contained in the product specifications for each device. The voltage and current
requirement for each device shall be taken into consideration while conducting the circuit analysis of the
segment. A Fieldbus FOUNDATION certified device is required to be capable of operating at > 9 Vdc.

6.9 FF SEGMENT EARTHING

6.9.1 FF trunks and spurs cables shall be earthed. FF trunks and spur cables shall be provided with an
overall
shield, which shall only earthed at DCS end. This earth is expected to be located in the satellite building.
The
overall shield shall not be earthed at the FF device end.

6.10 WIRING PRACTICES TO MEET ELECTRICAL HAZARDOUS AREA RATING

6.10.1 Class I Division 2 Areas (and Zone 2) & Class I Division 1 Areas (and Zone1)
6.10.1.1 EExe Enclosure for trunk, EExe isolator switch for barriers, on trunk line, non arcing/non sparking
terminals with connect/disconnect facility, EEx ia spurs.
6.10.1.2'Nonincendive circuits' as defined in NFPA 70, National Electrical Code Section 500- 4(f)(1) shall
not be
used.

7 FIELDBUS DEVICES
7.1 Following are the minimum requirements for Field bus Devices.
7.1.1 The device shall satisfy the requirements of the Fieldbus Foundation specifications and shall have
FF
CHECKMARK. The Devices shall be certified for intrinsic safety EEx ia (ATEX or equivalent certification).
7.1.2 Foundation Field bus Device shall be certified as passing the ITK 4.61 or later and shall include
Device
Description (DD) and Common File Format (CFF) files.
7.1.3 The FF device and all function blocks shall be tested and certified by the vendor of the control
system Host.
7.1.4 The Devices shall be provided with Flash memory for downloading the revised firmware in future.
7.1.5 Function block shall be downloadable into the devices by the end user.
Wiring Block Wiring Block Wiring Block
Marshalling Panel
Satellite Building
Intermediate FF
Junction Box
FF Spur Junction Box
FF Device
1 Pair, Type A
Type A
Trunk
cable
Type A
Trunk

cable
FOUNDATION FIELDBUS EARTHING ARRANGEMENT
7.1.6 Capable of performing continuous diagnostics, including self test functions, to provide specific
diagnostic
information at the Man Machine Interface (MMI).
7.1.7 All Fieldbus instruments shall include menus and methods (wizards) to allow easy setup and
calibration
from the MMI.
7.1.8 FF Device shall have three support files .FFO, SYM and CCF which contain information necessary
to
configure the Host systems. The support files shall include two Device Description Files and one
Capability
File, as defined in Fieldbus Foundation specification FF-940. The capabilities file and DD files shall be
provided by the device vendor and shall not be downloaded from the Foundation Fieldbus website.
7.1.9 Device vendors shall provide DTM (Device Type Manager) files for all devices and shall develop
these file
where they are not available. The DTM files shall be compatible with the host DCS system using
FDT/DTM
technology.
7.1.10 Standard programmatic interface shall follow FDT Group 1.2 standards. Any revision to host
Operating
System or device DD shall not require changes to the DTM for EDD.
7.1.11 Most Foundation Fieldbus devices can be powered directly from the Fieldbus. The DC supply
voltage can
range from 9-32 Vdc. The transmitting device delivers 10 mA at 31.25 kbits/s into a 50 ohm equivalent
load
to create a 1.0 volt peak-to-peak voltage modulated on top of the direct current (DC) supply voltage.
7.1.12 Loss of power or disturbance to one power supply module shall not result in the reset of a field
device in any
circumstances.
7.1.13 In order to reduce commissioning time each field device must be pre configured by the
manufacturer as
indicated on the instrument datasheet.
7.1.14 Temperature multiplexers shall be with 8 input and the input can be RTD or T/C.
7.1.15 None of the device shall be polarity sensitive.
7.1.16 All field bus devices shall have capability to perform continuously their own self diagnostics to
check their
health state.
7.1.17 Where ever specified for FF devices (Transmitters installed on high columns and open area like
tank farms)
shall be provided with necessary surge protection device in the concerned spur in the JB.

7.2 Multi-Input Transmitters

Multi-input transmitters using FOUNDATION Fieldbus Multiple Analog Input (MAI) function block(s) shall be
used for monitor only applications.

7.3 Handheld Fieldbus Testers

Fieldbus testers with following features shall be provided per process unit for the end user as essential
commissioning accessories & also for future field Maintenance.
Monitor signal level, noise level, DC power, LAS, Packet traffic, Device count, Framing errors, monitors
device
add & drop, shield short, Low FF and HF average and peak noise, network health, certified for both zone1
and zone2 and for both IS and Non IS devices and JBs, PC downloadable through USB port.
All data stored in the FBTs shall be downloadable into a PC thru cable.

8 NON-DEVICE ELEMENT SELECTION

8.1 Foundation Fieldbus Power Supplies (FFPS)
8.1.1 FFPS are required for each fieldbus segment.

8.1.2 FFPS shall be redundant and output current limited.

8.1.3 FFPS shall have redundant input power connections.
8.1.4 Two separate, independent, fused circuits shall source power to the FFPS. One (1) circuit shall be
powered from the primary bulk power supply and the second (2) circuits shall be powered from the
secondary (redundant) bulk power supply
8.1.5 All fieldbus power supplies shall be for 4 or 8 segment & true redundant type ie. with separate
redundant
power & conditioning unit built in.
8.1.6 Failure or faults in any of the redundant FFPS shall be annunciated in the Host system.
8.1.7 Fieldbus power supplies shall be encapsulated type & without any exposed component on the
mother board.
8.1.8 All power supply modules shall be hot swappable.
8.1.9 All the power supply modules shall be repairable
8.1.10 All power supply modules shall be fully isolated and having individual LED indication for each
segment.
8.1.11 All power supply modules shall have built in Alarm feature and should support Advance Diagnostic
features.

8.2 Terminators
8.2.1 Each fieldbus segment must have exactly two terminators. The terminator in the field will be at the
end of
trunk. ( last FFB JB of the segment )
8.2.2 All terminators located in the field shall be installed in a junction box. No terminators shall be
installed in
the FF devices.

8.3 Bulk power Supplies (BPS)

8.3.1 The 24 Vdc BPS shall be redundant.
8.3.2 Two separate, independent, UPS circuits shall source power the redundant BPS. The UPS
distribution
panel shall be considered the common point where these two separate circuits originate
8.3.3 Over current protection shall be provided for each feed supplying power to an individual or gang of
FFPS.

8.4 Foundation Fieldbus Barriers (FBB)

8.4.1 The Fieldbus Barrier shall be Bus powered type.
8.4.2 Each FBB shall have four spurs.
8.4.3 All spurs shall be IS and short circuit protected.
8.4.4 LED indication shall be there for power On and Fault condition for each spur.
8.4.5 The Fieldbus Barrier shall have intelligent Power Management features i.e. powering up of each
field device
one by one to avoid high inrush current and maintain low startup current.
8.4.6 The Field bus Barrier shall have ambient Temperature withstanding upto 75 Deg C with 100 % RH.
8.4.7 Each FBB shall have separate earthing bus bar.
8.4.8 All the Trunk and Spur shall have Reverse Polarity protection.
8.4.9 All the Spurs shall have Deenergising feature ie in case of a fault condition the voltage will get
clamped and
there will no current drainage. The Spur will be energized only after the short is removed/repaired. This
will
ensure proper voltage even at the furthest end of the segment.
8.4.10 The enclosure for field bus barrier shall be designed in such a way to accommodate maximum 3
nos of FBB
along with locking type isolation switch for each FBB, SPDs (surge protection device) for Trunks at both
ends. The Trunk and spur cables inside the enclosure shall be properly accessible for servicing purpose.
Proper care shall be taken for proper spacing of components inside the enclosure to avoid heat and
consequent temperature buildup. The total assembly along with FBB shall be tested at manufacturers
facility

and duly certified. Separate DIN mounted Terminator shall be provided inside the enclosure if more than
one
FBB is in the segment.
8.4.11 Fieldbus Sement Device Allocation
Control Loops
FF Barrier
JB Size Critical
Level 1
Critical
Level 2
Critical
Level 3
Max.
Additional
Devices
Total
Spurs
Used
Available
Spares
1 None None 1 3 1
None 1 None 1 3 1
None None 1 1 3 1
1 FB
Junction
Box
( 4 Spur
Max) None None None 3 3 1
1 None None 4 6 2
None 1 None 4 6 2
None 1 1 2 6 2
None None 1 4 6 2
None None 2 2 6 2
None None 3 None 6 2
2 FB
Junction
Box
( 8 Spur
Max)
None None None 6 6 2
1 None None 7 9 3
None 1 None 7 9 3
None 1 1 5 9 3
None None 1 7 9 3
None None 2 5 9 3
None None 3 3 9 3
3 FB
Junction
Box
( 12 Spur
Max)
None None None 9 9 3
Note: Each Controller is taken as one analogue input and one analogue output. Due
allowance for additional loop devices will be required for cascade loops and split
ranged controller application.

8.5 Repeater

Repeaters shall not be used, unless permitted. (See note below)

If a segment (network) needs to extend further than the 1900 meter length constraint, then a repeater
may be
considered.
Note: Using a repeater to extend the segment length shall not be a standard design practice. In the cases
where it is economically justified, a repeater may be considered to extend the total segment length. This
would typically be in cases where the H1 interface card cannot be located relatively close to the process,
(e.g., flare systems). The repeater segment design must be reviewed and approved in writing from client.

9 HOST REQUIREMENTS
9.1 Host FF Interoperability
9.1.1 All FF Host systems shall have completed Host Interoperability Support Testing (HIST) at
FOUNDATION
Fieldbus facilities, based on HIST Procedures document FF-569. FF Host systems shall support all
features
specified in the HIST.
9.1.2 A letter of conformance to the Host Interoperability System Test shall be provided to verify test
completion
and feature support.
9.1.3 All supported FF HIST features shall be integrated seamlessly into the existing control system's
engineering,
configuration, maintenance, and operations system.
9.1.4 The Host System supplier shall have an interoperability test laboratory setup to ensure that all third
party
devices used in the project have been successfully tested and certified with their system, reference
section
9.2 Host Control System Requirements
In addition to the FF requirements specified in this document, Host systems shall meet all requirements
specified in "Distributed Control Systems".
9.3 Host FF Feature Integration
All Host FF functions, including engineering, configuration, maintenance, and operational display
functions,
hall be integrated into a single, seamless Host system. Engineering, configuration, maintenance and
operational features shall apply consistently and seamlessly to conventional analog or discrete I/O, smart
HART and proprietary I/O, bus based I/O, and FF systems. Separate software tools, displays, or
procedures specific for FF and different from conventional - are not acceptable.
9.4 Host-To-Device Revision Download Capability
Hosts shall have the capability to download software revisions to F OUNDATION Fieldbus devices.
9.5 Host Configuration Features
9.5.1 Host FF configuration shall be consistent in method and 'look and feel' with conventional
configuration.
9.5.2 Internal mirror or shadow function blocks used by control systems to map FF function blocks to
internal
proprietary function blocks must be completely transparent to the configurator and operator. Single,
unique
and independent function block and parameter tag names must be used for both configuration and
operation.
Duplicate shadow blocks/parameters with tag names different from FF block/parameters are not
acceptable.
9.5.3 The Host FF configuration tool shall seamlessly and transparently integrate with, and maintain, the
master
configuration database. Saves, restores and partial downloads of the master control system database
shall
be seamlessly and transparently accomplished for both FF and conventional control strategies by the
same
configuration tool.

9.5.4 The Host configuration tool shall be capable of:

9.5.4.1 Offline FF configuration, e.g., to configure FF strategies with no segment or FF devices
connected. The
Host shall be capable of configuring all FF function blocks and parameters and support of Device
Description (DD) services and Common File Format (CFF) specification.
9.5.4.2 Soft simulating and testing any and all FF control strategies.
9.5.4.3 Importing non-native, bulk configuration data for developing configuration of larger project
databases.
9.5.4.4 Simple or complex online FF control strategy creation or modification.
9.5.4.5 Transparently managing the macro cycle schedule including maintaining minimum unscheduled
acyclic time,
coordinating integration of proprietary and FF function block execution times, and providing alerts and
messages for FF configuration errors.
9.5.4.6 Partial or incremental downloads to target function blocks and link schedulers without disrupting
the
operating segment strategies.
9.5.4.7 Master database saves and restores of targeted strategies or FF segments.
9.6 Host Commissioning and Maintenance Functions
9.6.1 The Host shall be capable of commissioning, setup, and maintaining all FF devices. This function
must be
integrated into the Host and available from Host workstations. The following functions shall be supported:
9.6.1.1 Add a new FF device to a segment. Add a future FF device to a segment through use of
placeholder
templates.
9.6.1.2 Move FF devices from/between offline, spare, standby, commissioned, and mismatch states and
manage all
address changes transparently. Manual address changes shall not be required.
9.6.1.3 Simple and complex commissioning functions including transmitter range changes, zeroing, and
control valve
positioner setup.
9.6.1.4 Support for DD methods and menu's (wizards) for all maintenance functions to walk technicians
through the
necessary maintenance procedures.
9.6.1.5 Provide specific maintenance displays, organized in a logical manner, for all FF devices using
English
language descriptors and definitions with access to all parameters. Screens shall not use lists of FF
function
block parameters.
9.6.1.6 Ability to mirror existing FF device configuration (all FBs and parameters) onto a new FF device to
allow quick
device replacements.
9.6.1.7 Display of commissioning and maintenance screens shall be from the operator/engineering
workstation.
9.6.2 Asset Management Systems
Asset Management Systems separate from the Host operator/engineering workstations may be used to
manage and display real-time and historical diagnostic & maintenance information. However, it may not
replace commissioning and maintenance function integrated into the Host as described above.

9.7 Host FF Operating Tools:

FF features required for integration include:
9.7.1 Internal mirror or shadow function blocks used by control systems to map FF function blocks to
internal
proprietary function blocks must be completely transparent to the operator. Operating displays must use
single, unique and independent tag names. Duplicate tag names for the same function are not
acceptable.
9.7.2 FF function block operation, including use of data quality, status, windup and bad value indication
and mode

switching, must be supported by, and transparently integrated into the control system operation and
operating displays. Differences in operation or displays between FF devices or loops and conventional
loops
are not acceptable.
9.7.3 FF process alarms and device alerts must be supported by, and integrated into the control system.
Differences between conventional and FF alarm management and alarm displays are not acceptable.
9.7.4 FF trend data via trend objects shall be supported by the Host control system and transparently
integrated
into real-time and historic trends displays.

10.0 CONSIDERATION FOR DETAIL ENGINEERING

10.1 5 Pair cable shall be used as Trunk cable from FF marshalling to Intermediate JB with 4 pair to be
used
for 4 segments and 1 pair will be spare. 1 pair cable shall be used between Intermediate JB & spur JBs
as
well as between spur JBs and Field devices
10.2 The Trunk + Spur length should not exceed 1700 mtr.
10.3 The trunk length should not exceed 1000 mtr.
10.4 The individual spur length should not exceed 100 mtr.
10.5 Each segment shall be designed for Max 12 devices (10 installed + 2 spare)
10.6 Power requirement shall be designed to cater min 10V to each FF device including spare device as
indicated
in section 10.5.
10.7 Detail engineering contractor (DEC) shall validate FF Instrument Segment Diagram as defined in
section
11.3 by using In-tools validation tool with respect to total cable length (Derived from 3D Model or
Instrument
Plot plan), Device operating Voltage (Min 10 VDC), Total number of devices on segment based on loop
criticality & segment cycle time, Field Bus Barrier voltage requirement (17 VDC) etc guidelines defined in
this
specification. The Segment Loading shall be verified by Integrated DCS System Vendor (ISV) with
respect to
overall loop configuration.

11 DOCUMENTATION
FOUNDATION Fieldbus system design requires the same documentation as conventional control system
designs. However, some documents must be altered for FOUNDATION Fieldbus
architecture.Documentation
alterations, additions, and deletions required for FF use are defined below .

11.1 Control Philosophy Document

11.1.1 A control philosophy guideline document shall be created for all FF projects. The guideline shall
define all
typical control strategies, with control modules, function blocks and all parameter configurations defined.
This
guideline shall set function block and control module philosophy for this and future FF projects at the
facility.
11.1.2 As part of the guideline, a narrative shall be provided for each typical function block and control
module, to
describe in detail the parameter setting and subsequent blocks/module operation. Included shall be
narrative
discussion on parameter configuration and operation for signal 'status', bad value determination, failure
mode
switching, Initialization feature, anti-reset windup feature, etc. The guideline shall highlight any differences
in
configuration or operation between FF and non-FF control strategies .
11.1.3 The control philosophy guideline document shall include a risk assessment philosophy (method)
which

defines how and why specific Fieldbus devices are assigned to segments. The philosophy shall include
consideration for segment loading constraints and multiple segments per H1 card. See section 5.7 for risk
assessment and segment loading criteria.
11.2 PIPING AND INSTRUMENTATION DIGRAMS (P&ID's)
11.2.1 Fieldbus instrumentation shall be shown on the P&ID as per Essar Engineering Centre standards
with the
following exceptions:
11.2.1.1Fieldbus 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
11.2.1.2The line symbology for FF signal wiring shall be the standard 'dashed' electric signal per ISA 5.1.
11.2.1.3 The
control or logic function balloons shall be shown independent of the hardware in which it is contained.
Note: PID, selectors, or arithmetic function blocks shall be shown functionally on the P&ID, (i.e., not
shown as
shared balloons with the device they reside in).
11.2.1.3 The control or logic function balloons shall be independent of the hardware in which it is
contained.
Note: PID, selectors, or arithmetic function blocks shall be shown functionally on the PID, (i.e., not shown
as a
shared balloons with the device they reside in).
11.2.2 All functions within the same field device shall be tagged with the same number, with individual
function
lettering appropriate for the application.
Note: For example using a multi-variable Coriolis meter, the instrument tagging would be FT-1010, DT1010,
and TT-1010 for flow, density and temperature, respectively.
11.2.3 Multivariable Fieldbus transmitters (e.g., multiple process measurements from the same
transmitter) shall be
represented with connected instrument balloons.

11.3 INSTRUMENT SEGMENT DIAGRAMS

The Instrument Loop Diagram (ILD) shall be replaced with an Instrument Segment Diagram (ISD).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:
11.3.1 A consistent method for identifying all signal wires is required in any control system;
The following is a recommended network/ segment naming convention
###ISD-NN MM PP where:
### - Indicates the plant/area number to which the segment is connected
NN - Indicates node number / controller name
MM = module number / card number
PP = segment or port number
The title block shall contain the 'segment name'. The segment name shall consist of the "Plant Area
name
Controller Name, Card Number and Port Number".
For example if the Controller name is '01', card number is '08' and we are using Port 1, the segment name
Shall be 138 ISD-010801.
11.3.2 All segment connections inclusive of the H1 interface card, BPS, FFPS, through the field devices,
terminations, junction boxes, and terminators.
11.3.3 All segment and field device tagging.
11.3.4 All spur cables shall be labeled with the instrument tag number.
11.3.5 All cable distances with voltage drop calculation results.
11.3.6 The Backup LAS device shall be identified.
11.3.7 Terminator locations shall be clearly identified.

11.4 INSTRUMENT SPECIFICATION SHEETS:

FOUNDATION Fieldbus instrumentation shall use the standard Essar Engineering Centre ISS's, with the
following line item additions:
11.4.1 LAS capable (yes/no)
11.4.2 Minimum Operating Voltage (Vdc)
11.4.3 Quiescent Current Draw (mA)
11.4.4 Polarity Sensitive Termination (yes/no)
11.4.5 DD revision level
11.4.6 Channel number and Description, (e.g., Channel 1 - Sensor 1, Channel 2 - Body Temperature,
Channel 3 Sensor 2, etc.).
11.4.7 Function Blocks Available, (e.g., AI_1, AI_2, PID_1, etc.)

12 FACTORY ACCEPATANCE TEST (FAT)

12.1 Systems that are staged at a vendor's facilities shall be tested according to Factory Acceptance Test
(FAT)

procedures produced for each project

12.2 FAT criteria shall be developed by the vendor and approved by consultant/client.
12.3 For any Fieldbus logic not tested during FAT, either because logic simulation is not available or all
fieldbus
devices cannot be connected, then the untested Fieldbus logic must be tested during SAT.
12.4 The following test shall be conducted for each segment:
Each H1 card segment (port), including spares, shall be operationally tested by live connection of at least
one Fieldbus device. The Fieldbus device shall be connected to the terminal block designated for the field
wiring or system cable.
12.5 The following tests shall be conducted one time only on a selected segment :
12.5.1 A complete functional test shall be conducted for one-of-each FF device used on this project (i.e.,
both
third-party and Control System Vendor products). This test will include, but is not limited to, plug-and-play
interconnectivity to Host system; configured fail-safe operation, verify access to all device function blocks,
and actual device operation, (e.g. simulate process inputs for transmitters, etc.
12.5.2 The test shall include configuration, calibration checks, and setup for each type of FF device.
Examples are
changing RTD sensor types; configuring and calibration check of transmitter span, zeroing P & DP
transmitters, zeroing elevation on DP level transmitters, setup etc. The intent of this requirement is to
verify
the ease of access to calibration wizards and setup procedures via the Host system.
12.5.3 All calibration and setup procedures, for each device, shall be demonstrated to Essar Engineering
Centre
personnel. Each procedure shall be documented in detail by the vendor and approved by Essar
Engineering Centre.
12.5.4 Vendor shall develop a redundancy fail-over test procedure for the H1 interface cards and Fieldbus
power
supplies. The test shall verify that automatic fail over shall not cause an upset, (i.e., I/O signal bumps,
loss of
operator view, mode changes, etc.). All H1 interface cards and FFPS shall be tested. Essar Engineering
Centre shall approve the fail-over test procedures.

13 SITE ACCEPTANCE TEST (SAT)

The FF SAT test shall contain the same scope as covered in the FF FAT.
For any Fieldbus logic not tested during FAT, either because logic simulation was not available or
because
all of the fieldbus devices could not be connected, then the untested Fieldbus logic must be tested during
SAT.

14 INSTALLATION AND CHECKOUT

The Control System Vendor shall develop a separate installation and checkout procedure for the Fieldbus

system. This procedure shall be approved in writing by Essar.

15 MAINTENANCE SHOP FIELDBUS SYSTEMS AND TOOLS

15.1 Each project shall supply and install a complete fieldbus maintenance system in the maintenance
shop. The
intent of this maintenance system is to allow Fieldbus instrument troubleshooting, calibration, and setup in
the
Instrument Maintenance shop.
15.2 The Maintenance Fieldbus system will include all system hardware, software, and auxiliary
equipment
required to connect and maintain Fieldbus devices in the shop. Equipment shall include but not be limited
to
a control system with dual Operator/Engineering workstations with complete software, control network
with
appropriate switches, chassis with controller & power supplies, redundant H1 cards, Bulk and F OUNDATION
Fieldbus power supply (FFPS), and FBB JB with isolating switch, FBB & trunk wiring block. All
workstations
will be mounted in appropriate 'shop-proof' furniture. The I/O chassis, power supplies, wiring and terminal
blocks will be pre-wired and installed in an easy to access, caster mounted cabinet.
15.3 All standard and special tools, test software, and test and calibration equipment required for the
Fieldbus
system as specified in 7.3 shall be supplied by the project. A list of the tools, test and calibration
equipment
shall be submitted to Essar for review and approval.
15.4 The list of the standard tools and testing and calibration equipment required shall identify the
following:
15.4.1 Description of its service or simulation application.
15.4.2 Manufacturer and Catalog No.
15.4.3 Quantity recommended.
15.5 Control System Vendor (ISV) shall provide design and performance specifications for all special
tools, test
software, and test and calibration equipment.

16 FILEDBUS SPARE PARTS AND REVISION LEVEL UPDATE PROGRAM

16.1 The Control System Vendor (ISV) shall develop a Fieldbus device spare parts management program
for
this facility within Essar Engineering Centre. This program shall provide management of:
16.1.1 Stocking a sufficient quantity of Fieldbus spare instruments and associated software.
16.1.2 Management, tracking, and update of Fieldbus spare instruments revision levels.
16.1.3 Stocking a sufficient number of Fieldbus non-device element hardware e.g., Foundation fieldbus
power
supplies, terminators, FBB, isolating switch, etc.
16.2 The Control System Vendor shall develop and put in place an update program that assures the
system
revision level stays current.
Notes: The control system must be kept current to assure it will work with new Fieldbus instrument
revisions.
Typically, a current revision level is also backwards compatible with older Fieldbus instrument revisions.
While they look exactly the same, Fieldbus instruments are completely different from, and not replaceable
by, conventional instruments. Thus, spare Fieldbus and conventional instruments must be kept
segregated and identified differently. In addition, Fieldbus instruments may have associated software that
must be stored with it.
For these reasons, a complete Fieldbus instrument spare parts management program must be
developed.

17 FIELDBUS TRAINING
Control System Vendor (ISV) to provide FF training programs targeted for the following categories of
company

personnel:
Engineers(Overview, Maintenance, Advanced)
Operators (Overview)
Maintenance Supervisors (Overview, Maintenance)
Maintenance technicians (Overview, Maintenance)
17.2 Courses and course requirements shall include following, but not limited to:
Foundation Fieldbus Architecture
Foundation Fieldbus terminology
Segment components, power and wiring.
Foundation Fieldbus communication and bandwidth issues.
Review of fieldbus function blocks.
Device Description language review.
17.3 Foundation Fieldbus Maintenance courses shall be as follows:
Foundation Fieldbus Architecture
Foundation Fieldbus terminology
Detailed review of segment components, segment design, power, intrinsic safety and wiring.
Foundation Fieldbus Communication and Bandwidth issues.
Review of Foundation fieldbus blocks.
Device Description language review.
Maintenance tools and troubleshooting.
DD file maintenance and updating
Interface to AMS.
17.4 Foundation Fieldbus Advance course:
H1 datalink layer.
H1 Bus monitor.
H1 System management
Fieldbus message specifications
High Speed Ethernet.
Object Dictionary
Function Block application process.
Advanced Control Strategies
DD file maintenance and updating.
17.5 A training program based at the DCS suppliers facilities may be developed for engineers and
supervisors.
An on-site training program may be developed for the operators and maintenance technicians.
The ISV vendor shall supply quotation for an on-site FF training simulator for on-going FF training support
of
the FF system.
17.6 Training Stages
The ISV vendor to implement FF training in phases as described below:
Engineering Phase
Prior to FAT Phase
Prior to SAT Phase
Company personnel to be trained in each phase shall be indicated by Essar Oil.
Engineering phase and prior to FAT phase training will be held at FF vendor facilities.
Prior to SAT phase training will be held at site.

Annexure A Fieldbus Glossary of Terms

All Fieldbus terms and acronyms defined below are from the 'Glossary of Terms' section on the
FOUNDATION website
www.fieldbus.org. The entire FOUNDATION Fieldbus glossary has been copied to appendix-A.
A
Basic Device: A Basic Device is any device not having the capability to control communications on
an H1 fieldbus segment.
Capabilities File: A Capabilities File describes the communication objects in a fieldbus device. A
configuration device can use Device Description (DD) Files and Capabilities Files to

configure a fieldbus system without having the fieldbus devices online.

Communications Stack: A Communications Stack is device communications software which provides
encoding and decoding of User Layer messages, deterministic control of message
transmission, and message transfer.
Connector: A Connector is a coupling device used to connect the wire medium to a fieldbus
device or to another segment of wire.
Control Loop: 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.
Coupler: A Coupler is a physical interface between a Trunk and Spur, or a Trunk and a
device.
Data Link Layer (DLL): The Data Link Layer (DLL) controls transmission of messages onto the fieldbus,
and
manages access to the fieldbus through the Link Active Scheduler (LAS). The DLL
used by FOUNDATION fieldbus is defined in IEC 61158 and ISA S50. It includes
Publisher/Subscriber, Client/Server and Source/Sink services.
Device Description (DD): A Device Description (DD) provides an extended description of each object in
the
Virtual Field Device (VFD), and includes information needed for a control system or
host to understand the meaning of data in the VFD.
E
Fieldbus: 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.
Fieldbus Access Sublayer (FAS): The Fieldbus Access Sublayer (FAS) maps the Fieldbus Message
Specification
(FMS) onto the Data Link Layer (DLL).
Fieldbus Messaging Specification (FMS): The Fieldbus Messaging Specification (FMS) contains
definitions of
Application Layer services in FOUNDATION fieldbus. The FMS specifies services
and message formats for accessing Function Block (FB) parameters, as well as
Object Dictionary (OD) descriptions for those parameters defined in the Virtual Field
Device (VFD).
Flexible Function Block: A Flexible Function Block (FB) is similar to a Standard FB, except that the
function of
the block, the order and definition of the block parameters, and the time required to
execute the block are determined by an application-specific algorithm created by a
programming tool. Flexible Function Blocks (FBs) are typically used for control of
discrete processes and for hybrid (batch) processes. A Programmable Logic
Controller (PLC) can be modeled as a Flexible Function Block device.
G
H1: H1 is a term used to describe a fieldbus network operating at 31.25 kbit/second.
H1 Field Device: An H1 Field Device is a fieldbus device connected directly to an H1 fieldbus. Typical
H1 Field Devices are valves and transmitters.
H1 Repeater: An H1 Repeater is an active, bus-powered or non-bus-powered device used to
extend the range over which signals can be correctly transmitted and received for a
given medium. A maximum of four Repeaters and/or active Couplers can be used
between any two devices on an H1 fieldbus network.
High Speed Ethernet (HSE): High Speed Ethernet (HSE) is the Fieldbus Foundation's backbone
network running
at 100 Mbit/second.
HSE Field Device: An HSE Field Device is a fieldbus device connected directly to a High Speed
Ethernet (HSE) fieldbus. Typical HSE Field Devices are HSE Linking Devices, HSE
Field Devices running Function Blocks (FBs), and Host Computers.
HSE Linking Device: An HSE Linking Device is a device used to interconnect H1 fieldbus Segments to
High Speed Ethernet (HSE) to create a larger network.

HSE Switch: An HSE Switch is standard Ethernet equipment used to interconnect multiple High
Speed Ethernet (HSE) devices such as HSE Linking Devices and HSE Field Devices
to form a larger HSE network.
Input/Output (I/O) Subsystem Interface: An Input/Output (I/O) Subsystem Interface is a device used to
connect
other types of communications protocols to a fieldbus Segment or Segments.
Interchangeability: Interchangeability 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.
Interoperability: Interoperability is the capability for a device from one manufacturer to interact with
that of another manufacturer on a fieldbus network without loss of functionality.
J
K
Link: A Link is the logical medium by which H1 Fieldbus devices are interconnected. It is
composed of one or more physical segments interconnected by bus Repeaters or
Couplers. All of the devices on a link share a common schedule which is
administered by that link's current LAS.
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. Only one Link Master (LM) device on an H1 fieldbus Link can
be functioning as that link's LAS.
Link Master (LM): 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.
Link Objects: A Link Object contains information to link Function Block (FB) Input/Output (I/O)
parameters in the same device and between different devices. The Link Object links
directly to a Virtual Communications Relationship (VCR).
M
Network Management (NM): Network Management (NM) permits FOUNDATION Network Manager
(NMgr) entities
to conduct management operations over the network by using Network Management
Agents (NMAs). Each Network Management Agent (NMA) is responsible for
managing the communications within a device. The NMgr and NMA communicate
through use of the Fieldbus Messaging Specification (FMS) and Virtual
Communications Relationship (VCR).
Object Dictionary: An Object Dictionary (OD) contains all Function Block (FB), Resource Block (RB)
and Transducer Block (TB) parameters used in a device. Through these parameters,
the blocks may be accessed over the fieldbus network.
Physical Layer: The Physical Layer receives messages from the Communications Stack and converts
the messages into physical signals on the fieldbus transmission medium, and viceversa.
Q
Resource Block (RB): A Resource Block (RB) describes characteristics of the fieldbus device such as
the
device name, manufacturer and serial number. There is only one Resource Block
(RB) in a device.
Schedules: Schedules define when Function Blocks (FBs) execute and when data and status is
published on the bus.
Segment: 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.
Splice: A Splice is an H1 Spur measuring less than 1 m (3.28 ft.) in length.
Spur: 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.).

Standard Function Block (FB): 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.
System Management (SM): System Management (SM) synchronizes execution of Function Blocks (FBs)
and the
communication of Function Block (FB) parameters on the fieldbus, and handles
publication of the time of day to all devices, automatic assignment of device
addresses, and searching for parameter names or "tags" on the fieldbus.
Terminator: 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.
Transducer Block (TB): 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 (TBs) contain information such as calibration date and sensor
type. There is usually one TB channel for each input or output of a Function Block
(FB).
Transmitter: A Transmitter is an active fieldbus device containing circuitry which applies a digital
signal on the bus.
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.
User Application: The User Application is based on "blocks," including Resource Blocks (RBs),
Function Blocks (FBs) and Transducer Blocks (TBs), which represent different types
of application functions.
User Layer: The User Layer provides scheduling of Function Blocks (FBs), as well as Device
Descriptions (DDs) which allow the host system to communicate with devices without
the need for custom programming.
Virtual Communication Relationship (VCR): 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 Field Device (VFD): A Virtual Field Device (VFD) is used to remotely view local device data
described in
the object dictionary. A typical device will have at least two Virtual Field Devices
(VFDs).
W
X
Y
Z