1. End User Workshop - Singapore
FOUNDATIONTM Fieldbus
- Challenges & Latest Developments -
July 8, 2004
Hisashi Sasajima
Fieldbus Foundation

2. Agenda Introduction About Fieldbus Foundation The History of Fieldbus
05/03/04
Agenda
Introduction
About Fieldbus Foundation
The History of Fieldbus
End User Initiative
Technology Updates
Installations
Benefit of Fieldbus
Questions and Answers
In 1995 a small number of companies came together with a single vision; a truly interoperable, international Fieldbus standard. Today, that small group has grown to over 350 major control, instrumentation and valve suppliers as well as leading end user companies from around the world.
Why Fieldbus? Industrial companies must reduce operating costs, streamline and enable efficient and effective workforces, accelerate delivery times for goods and meet stringent regulatory requirements. And, they must do this in order to compete effectively on a global scale.
Studies indicate that the global adoption rate for Foundation Fieldbus is growing at a rapid pace. The Foundation has tested and registered over 180 fully interoperable Fieldbus devices and eleven compliant Host Systems have met the test protocol of the Foundation’s Host Interoperability Support Test.
Today you will find Foundation technology as the network of choice in virtually every type of process industry from chemicals and petrochemicals; pulp and paper, refining, mining; to human infrastructure processes such as utilities, water and wastewater treatment.
What do these improvements return to these users? One of the large multinational companies I mentioned has concluded that through the effective use of Foundation fieldbus the technology enables a minimum of a 1% improvement on Asset Utilization; the equivalent to $2 Million a year; a 1% reduction in plant fixed costs returns over $1 Million per year; and t a 1% reduction in variable costs is worth significantly more than Maintenance costs. All of these are fully quantified results.
These are huge commitments by end users. They hold a vision of a truly integrated operating enterprise and the basis for that integration is Foundation Fieldbus.
To be certain, Foundation fieldbus does not solve the operating issues of a plant but it does enable efficient solutions; and it drives innovation. We see more and more applications utilizing control in the field leading to reduced cost for critical control loops.
Credibility of information being transferred is guaranteed by the technology’s system management. Information is checked, sent at fixed time intervals and verified insuring that the right information is received at the right time and in the right place.
The fully integrated Fieldbus architecture optimizes performance at each layer of the enterprise. The combination of the H1 device network and HSE, high Speed control backbone allows and supports integration across the plant and insures interoperability from device to Host, sub system to subsystem and easy integration of legacy systems.
During 2002, the Foundation’s technology under went rigorous testing at Infraserv Hoscht Technik, an independent consultancy in Frankfurt, Germany. The results of this testing confirmed that registered Fieldbus devices provide true interoperability and interchangeability. Further, the testing proved conclusively the reliability of implementing Control in the Field, at the device.
Further studies conducted by Infraserv proved that the savings enabled by Fieldbus technology begin immediately during the design and engineering of the project. Capex or Capital Expenditure costs of Fieldbus technology were compared with those of conventional analog architectures. This study showed the savings gathered to be in the 10 to 15% range versus traditional analog architecture and 5 to 10% versus remote I/O.
Infraserv.
Since that time additional studies have been completed. One such study compared the potential implementations of a Distributed Control System on a Greenfield Super Critical Power plant.
The traditional installation utilized dedicated cables to hardwired non-intelligent field devices to input/output cards. The Digital bus plant installation utilized Fieldbus I/O, high speed field communication networks and intelligent or smart field devices.
The costs were estimated for both implementations in five categories; System Selection, Engineering, Construction, start up and overhead costs. The results were overwhelming. The traditional plant estimate costs were approximately $50 Million. The estimated Digital bus based system costs were $30 Million. Each of the five areas above showed significant savings adding up to a total cost reduction of 39%.
The growth of Fieldbus adoption is driving growth across many areas of our industry.
Our latest initiatives focus on the needs of our users and guaranteeing the viability of the technology.
Over the past year we have worked with the largest group of volunteer end users ever assembled by the Foundation to develop a specification that will enable the diagnostic, information capabilities and reliability of Fieldbus technology to be deployed in Safety Critical Systems. Tomorrow Dave Glanzer, the Foundation’s Director of Technology will tell you about our progress in this area.
Responding to user needs for visualization of complex devices such as valve signatures, radar level gauges and analytical devices, the Foundation has partnered with the HART Foundation and Profibus Organization to develop extensions to Device Description Language that will enable visualization of charts, graphs, images and persistent data storage.
All, these additional features will be brought to the technology improving configurability, calibration, start up processes and operational efficiencies for end users.
These enhancements will build on proven DD technology and standards while protecting the installed base of millions of devices based on the technology and providing for seamless migration of the devices using the enhancements into installed systems.
The ARC Advisory Group projects that the Process Automation System Market will grow at over a 15% compound annual growth rate over the next five years with the market expanding from $531 Million in 2003 to a forecast of 1.0 Billion by 2008.
China, the fastest growing economy in the world is witnessing massive investments in new projects and plant upgrades in almost all process industry segments. Foundation Fieldbus is here, active and proven in use to deliver quantifiable unmatched benefits.
For users, state of the art Foundation Fieldbus is an enabling technology for enhancement of your competitive position both within and out side of China.
For manufacturers, delivering the technology and products that support the end users business driven objectives is a proven path to success.
I look forward to returning here often, witnessing the growth of Foundation Fieldbus and meeting with end users from across your country as your prominence in world markets continues to grow.
Thank you and Enjoy the seminar 2 2
05/03/04

3. Mission of the Fieldbus Foundation
The Fieldbus Foundation is the leading organization
dedicated to a single international, interoperable
fieldbus standard. Established in September 1994 by a merger of WorldFIP North America and the
Interoperable Systems Project (ISP), the foundation is a not-for-profit corporation that consists of nearly 180 of the world's leading suppliers and end users of process control and manufacturing automation products.
Working together, these companies have provided
unparalleled support for a worldwide fieldbus protocol, and have made major contributions to the IEC/ISA fieldbus standards development.

4. FOUNDATION fieldbus Digital presence
05/03/04
FOUNDATION fieldbus Digital presence
At our recent General Assembly held in the United States, we had the pleasure to hear a keynote speech delivered by the Manager of Asset Utilization from Shell Chemicals. He shared with our members and guests the commitment Shell has made to utilization of Foundation technology and why that commitment has led to the installation of over 70,000 fieldbus devices around the world.
As you know China National Offshore Oil Company in partnership with Shell will build a multi-plant facility here in China with over 12,000 registered Fieldbus devices. Additionally, Shanghai SECCO in partnership with BP will build a 10 plant complex with over 25,000 registered Fieldbus devices. In addition, PetroChina and Sinopec have also installed Foundation Fieldbus based projects. These are just a few of the more than 200 Fieldbus based projects currently installed or under development in China.
Around the world leading industrial companies such as Chevron Texaco, ExxonMobil, Bayer, Bohai Chemical, Iranian National Oil Company, Rohm & Haas, BP, Saudi Arabian Oil Company, Oman Gas Company, Petrobras, Guangzhou Petrochemical Company, Coca Cola, Nestle, Hangzhou Steel, Korea Heavy Industries, Pascorp Paper, Akzo Nobel, Galxo Smith Kline, Zhejiang Hisun Pharmaceuticals and Bristol Myers Squib all are stepping forward to improve their competitive position in the world markets by improving plant stability and reliability, through better utilization of plant assets and reductions in operating and maintenance costs, both fixed costs and variable costs.

5. Market Distribution
Global
Industry

6. Market Segmentation in the Region
1st 2nd rd
N.A. (46%) ： Chemical Electric Pulp & Paper
L.A. (14%) ： Chemical Oil & Gas Food & Beverages
EU (28%) ： Chemical Oil & Gas Pharmaceutical
M.E. ( 2%) ： Oil & Gas Chemical
SEA (10%) ： Chemical Oil & Gas Refining
China ( 7%) ： Chemical Refining Electric
Others
Total Chemical Oil & Gas Electric Power

7. Fieldbus Acceptance Has Been Outstanding
FOUNDATION™ fieldbus installations
include leaders in key industries
9 of the top 10 oil and gas companies
24 of the top 25 pharmaceutical companies
23 of the top 25 chemical companies
15 of the top 20 pulp and paper companies
10 of the top 20 food and beverage companies

8. 338 Global Members & Corporate Affiliates 176 Registered Devices
Stronger Than Ever!
338 Global Members & Corporate Affiliates
176 Registered Devices
11 Hosts

9. Freedom to Choose

10. Marketing Committees in Asia Pacific
Japan
Korea
China
Malaysia
Thailand
India
Singapore
Indonesia
Australia
Taiwan
Central Asia
Middle East
ASEAN
Philippine
Far East

11. Asia Pacific Operations
FF Asia Pacific
Fieldbus Foundation
Asia Pacific Operations FF
Japan
EUC Japan FF
Singapore
Marketing
Society
EU Society
East Asia
South East Asia FF
Korea
EUC Korea FF
Indonesia
EUC FF
Thailand
EUC FF
China
CFFC
EUC China FF
India
EUC India

12. End User Council and Training/ Education Center
End User Council (EUC)
Training and Demonstration Site Training and Demonstration Site (Under Planning)

13. The History of Fieldbus（IEC/ISA Standardization)
1984: New Work Item proposal in IEC for Digital Field Communication in Process Measurement and Control Instruments
1985: Working Group established in IEC (SC65C/WG6) and ISA (SP50)
1990: IFC(international Fieldbus Consortium)
ISA SP50 Media Attachment Unit (MAU) 　
　Physical Layer Test at Exxon (‘92)
BP Sunburry　-1,-2
Kaneka, Mitsubishi Chemical, Japan (‘93)
1992 1Nov.:　ISP was formed
1993 May:　 WorldFIP was formed
1993 : IEC Physical Layer became IS(IEC )
1994 Sept. : Fieldbus Foundation established
Field Trial at Monsanto, Tx (‘95)
Field Trial at Syncrude, Canada(‘96)
Chubu Electric, Japan (‘97)
2000 :IEC Data Link/ Application Layer Standardized(IEC ,4,5,6)

14. The History of Fieldbus Foundation
05/03/04
The History of Fieldbus Foundation
WorldFIP
North America
&
ISP
merge
Initial HSE
Specification
released
Early
specification
produced
Conformance
tester
Version 2.0
Redundancy and
Flexible Function Block
Achieve final
Specification status
1994
1996
1998
2000
2002
2004
1995
1997
1999
2001
2003
March
Product
Interoperability
testing begins
Fast Ethernet
Project launched
Scheduled release
of ITK 4.6
Scheduled release of
conformance tester
version 2.3
November
December
January
September
February
Beta
test plat
completed
Number of
registered
devices
Reaches 180
HSE
testing
underway
FISCO
Final
History of the Fieldbus Foundation
The Fieldbus Foundation was created from a merger of
WorldFIP North America and the Interoperability
Systems Project (ISP Foundation) in 1994 with the
emphasis on creating a single, international,
independent fieldbus. The Foundation provides a
sustaining infrastructure that promotes and supports
this technology for the long term.
In early 1995, the Fieldbus Foundation produced the
Initial Review Draft Specification (IRDS) for
FOUNDATIONTM fieldbus. The IRDS outlined process
automation functionality for the Foundation's 31.25
kbps fieldbus. The Draft Preliminary Specification (DPS)
for FOUNDATIONTM fieldbus was completed on May 31 of
that year and released for review to external fieldbus
experts and authorities.
A multi-vendor beta plant test at Monsanto's Chocolate
Bayou facility near Houston, Texas, was undertaken
during the spring of The beta plant test utilized
prototype FOUNDATIONTM fieldbus devices from 11
suppliers. More than a dozen devices were
interconnected on two separate FOUNDATIONTM
fieldbus segments that were used to control a
condensate recovery system. The Monsanto beta plant
test, which was successfully completed by the end of the
first quarter of 1996, confirmed the performance
advantages and cost savings provided by
FOUNDATIONTM fieldbus.
With the formal acceptance of its Interoperability Test Kit
in March of 1998, the Fieldbus Foundation began
interoperability testing of host and field devices based
on the FOUNDATIONTM fieldbus protocol. Devices that
passed interoperability testing received the
Foundation's registration "checkmark".
In March of 2000, the initial specification of the HSE
fieldbus network was released. Later in September,
specifications on Redundancy and Flexible Function
Block achieved Final Specification status.
The first major updates to the specifications were
released in November of The modifications
included changes to the Communication Stack and Part
5 - Function Block specifications and the adoption of the
FISCO specification. Further modifications to the
specifications were released in October of 2003
including updates to the Device Description Language,
High Speed Ethernet, and Part 1,2,3 Function Block
specifications.

15. Original End User Requirements for Fieldbus
05/03/04
Original End User Requirements for Fieldbus
Average distance between Control Room and Plant: shall be :
Cable Distance : 1,200m
Transmission Distance : 2,400m (8,000 ft)
→　H1 Fieldbus Cable Distance : 1,900m （with maximum nodes）
Transmission speed considering for the anti-noise immunity, attenuation and reflection of signal shall be:
50Kbps - 500Kbps.
→　H1 Fieldbus :　31.25Kbps
H2 (High Speed) Fieldbus : 1 Mbps or 2.5 Mbps
(FF Specification)　 H1 Fieldbus + 100Mbps HSE（High Speed Ethernet）
Cable Type: Existing multi-core cables shall be applicable and device power / signal transmission shall be available through single pair cable
→　Type A, B, C, D Cables
The Fieldbus Devices shall be workable in Intrinsic Safe environment with flammable gas atmosphere in Hydrocarbon Processing Industry.
→　Entity Model：Current Limit　(19V、40～60mA), 10mA～30mA/ Device
FISCO Model (Fieldbus Intrinsic Safety Concept) : 110mA
FNICO Model (Fieldbus Non-Incendive Concept) :　350mA
Since the original requirements came from HPI users, Foundation Fieldbus specification includes the functions to meet mission critical application requirements Petrochemical and Chemical applications in HPI market such as Intrinsic Safety, Functional Safety and Plant Asset Management requirements.
Those requirements are pushing to install more intelligent field devices with device/ plant diagnostic and safety considerations into the plant. The device manufactures need to design sophisticated and complex devices requiring more processing power and resources which can run in Intrinsic Safety environments. It is something contradictory and need to go over such technological barriers.
In this sense, Foundation technology is still growing in order to meet such sophisticated industry requirements. For example, there are several new concept of Intrinsic Safety Concept to allow more processing power to field devices, Device Description enhancements and standardization (EDDL), Device Software Down Load and improved Interoperability Testing environments between field devices and host system.
In the following section, the current technology updates will be briefly introduced.

16. IEC61158 Structure (as of June, 2004)
05/03/04
IEC61158 Structure (as of June, 2004)
IEC Part 1-Part 6 (PHL/DL/AL)
Type Proposed by
Type- 1: Fieldbus（ANSI/ISAS50.01) ：IEC/ISA Original Specification
Type- 2: ControlNet ：ControlNet Int’l
Type- 3: Profibus DP/PA ：Profibus Organization
Type- 4: P-Net ：Norwegian Fieldbus Consortium
Type- 5: Fieldbus Foundation HSE ：Fieldbus Foundation
Type- 6: Swiftnet ：
Type- 7: WorldFIP ：WorldFIP
Type- 8: Interbus S ：
Type- 9: Foundation H1 Fieldbus ：Fieldbus Foundation
Type-10: Profinet ： Profibus Organization

17. Fieldbus Protocol Structure
05/03/04
Fieldbus Protocol Structure
USER LAYER
IEC
@ kbit/s
IEC DLL
IEC FMS H1
USER LAYER
IEC
IETF TCP/UDP
IEEE 802.3
MAC
IETF IP
IEC FDA
IEEE 802.3u
@ 100 Mbit/s
HSE
USER LAYER
IEC
TRANSPORT LAYER
SESSION LAYER
PRESENTATION LAYER
APPLICATION LAYER
PHYSICAL LAYER
DATA LINK LAYER
NETWORK LAYER 1 2 3 4 5 6 7
OSI Model
PHYSICAL LAYER 1 2 3 4 5 6 7
COMMUNICATION
STACK 2 12 12 13 12

18. Humble Beginnings H1: 31.25 Kbps Computers Control network Process
controllers
H1 Fieldbus
Junction
box
Field
devices

19. FOUNDATION Fieldbus Architecture
H1 Devices
HSE
ﾊﾞｯﾁｺﾝﾄﾛｰﾗ
MIO
FFB
PLC
Fiber Optic Fieldbus
2000 m
Twisted Pair
100 H1
Fieldbus
Operator
Work Station
Engineering
Data Server
Application
Other Plants
Linking Device
Non-FF
Sensor Bus
H1 Digital I/O

20. Integrated System Architecture
05/03/04
Integrated System Architecture P L
APPLICATION
PACKAGES
MIS
DA Server
Servers access data from the HSE Backbone
Data is used to support Application Packages
such as:
Enterprise Resource Planning
Asset Management
MANAGEMENT INFORMATION SYSTEMS
Access the Data Warehouses
Provide Management Reports
One of the strategic goals of any organization is plant optimization. This need is driven by global pressure to increase product quality, reduce product costs, reduce plant downtime, improve plant safety, reduce time to market, and increase plant flexibility.
To achieve plant optimization the number of different networks, gateways and systems in the plant hierarchy (Figure 1) must be reduced while at the same time increasing information integration between automation systems and Management Information systems (MIS). To be cost-effective the system must be built on standard, high volume, low cost networking technology.
This is accomplished by replacing proprietary automation systems and networks with a single, open, integrated fieldbus architecture. The open fieldbus architecture enables direct integration of sensors, devices, and high speed subsystems resulting in the lean hierarchy.
The open specification allows a complete range of interoperable products from many suppliers.

21. FF-581 System Architecture
05/03/04
Released Specifications
SYSTEM ARCHITECTURE
FF-581 System Architecture
FUNCTION BLOCKS
FF-890 Function Block Part 1 – FBAP Model
FF-891 Function Block Part 2 – Basic
FF-892 Function Block Part 3 – Advanced
FF-893 Function Block Part 4 – Multiple I/O
FF-894 Function Block Part 5 – Flexible
DEVICE DESCRIPTION
FF-103 Capability File
FF-900 DD Language (DDL)
USER
LAYER
UTILITY
FF Common Device Software Download
H1 FIELDBUS (31.25 KBIT/S)
FF-801 Network Management
FF-806 H1-H1 Bridge
FF-816 H1 Profile (Entity, FISCO, Fiber)
FF-821 Data Link Services
FF-822 Data Link Protocol
FF-870 Fieldbus Message Specification
FF-875 Fieldbus Access Sublayer
FF-880 System Management
FF-940 H1 Profile
HSE FIELDBUS (100 MBIT/S)
FF-586 Ethernet Presence
FF-588 Field Device Access
FF-589 HSE System Management
FF-593 HSE Redundant Interface
FF-803 HSE Network Management
FF-941 HSE Profile
NETWORK

22. FOUNDATION fieldbus Specifications
05/03/04
FF Products Roadmap
FOUNDATION fieldbus Specifications
FOUNDATION fieldbus Training Courses
H1 Device Development
H1 Conformance Test Kit
DD Tokenizer
DD Standard Library
H1 Interoperability Test Kit
H1 Device Testing
More Tools
H1 ITK
Automation Toolkit
HSE Device Development
HSE Conformance Test Kit
DD Tokenizer
DD Standard Library
HSE Interoperability Test Kit
HSE Device Testing
HSE Analyzer
Toolkit Professional
More Tools
H1/HSE Host Development
DD Services Software
DD Registered Library
Host Interoperability
Support Testing
(HIST)

23. H1 Development History H1 Today
Over 62 Registered Stacks from 26 suppliers
Over Registered Devices from suppliers
Over 305,000 H1 Devices in the Field
HIST Compliant Hosts sampling: (4500)
ABB
Emerson – Delta V
Honeywell – Plantscape and Experion PKS
Invensys
Smar – System 302
Yamatake – Industrial DEO
Yokogawa – Centum and Stardom
Rockwell – Process Logix

24. HSE Development History
HSE Today
10 Registered Linking Devices
ABB (2 versions)
Emerson
National Instruments
Rockwell
Smar(3)
Softing
HMS Networks
HSE Function Block Devices in Beta Registration Test
HSE Redundant Devices in Lab System Test
Planning for FBCiHAB Demo at BP is Underway
- Includes registered HSE Linking Devices, FB Devices, and HSE Redundancy

25. Fieldbus Foundation
Technology Updates

26. Agenda 1. H1 Interoperability Improvement 2. Development Programs
05/03/04
Agenda
1. H1 Interoperability Improvement
HIST Release 1.2
H1 ITK Release 4.6
H1 Power Supply Registration
2. Development Programs
DD Cooperation Project
Standard Transducer Block Specification
HSE Registration
HSE Device Redundancy
Safety Instrumented Systems

27. HIST Release 1.2 HIST Release 1.2 adds the following feature tests
05/03/04
HIST Release 1.2
HIST Release 1.2 adds the following feature tests
Common Device Software Download
Multi-Variable Optimization
HSE Linking Device Configuration
Flexible Function Blocks
Device Replacement Support
Release Schedule
Comment Period 1 Dec 2003
Comment Period 2 Jan 2004
EUAC GA2004 Feb 2004
TSC Approval May 2004

28. H1 ITK Release 4.6 H1 ITK 4.6 - Basis for DD Self Re-Registration
05/03/04
H1 ITK Release 4.6
H1 ITK Basis for DD Self Re-Registration
Update to support FF-103 FS 1.7 (Capability File) - Instantiation
Library support for Common Device Software Download
Minor bug fixes
Release Schedule
Beta Test Start Mar 2004
Beta Test Complete Apr 2004
TSC Approval May 2004
Policy:
All DD/CF files must be retested* using ITK 4.6
within 6 months of release.
*Either by self-test or by FF

29. Nine power supplies registered and on FF Web Site
05/03/04
H1 Power Supply Registration
Develop self-test specifications and registration testing for power supplies to improve interoperability.
Fieldbus Power Supply Test Specification – Release 1.0
BOD Approval Feb 2003
Project Kickoff May 2003
Draft Test Specifications Completed Jan 2004
Run Beta Registration Tests Feb 2004
(MTL, P+F, Relcom)
Membership review of preliminary specification Mar 2004
TSC Release of Test Specification Apr 2004
First registered Power Supplies Apr 2004
Nine power supplies registered and on FF Web Site

30. IEC 61804-2 EDDL based Extensions for Visualization
05/03/04
DD Cooperation Project
FF/HCF/PNO
IEC EDDL based Extensions for Visualization
2003
Kickoff Meeting Completed – Host FF Feb
Project Plan Issued Mar
2nd Team Meeting – Host PNO Jun
Requirements and Use Cases Agreed
Specifications and Guidelines Identified
3nd Team Meeting – Host HCF Sep
Specification Development
4th Team Meeting – Host FF Oct
Specifications Agreed
Validation Planning Started
2004
5th Team Meeting – Host PNO Jan
Draft of Interoperability Guideline Completed
Project Plan Updated (Revision 1.4) with Validation Plan
6th Team Meeting – Host HCF Mar
Interoperability Guideline Agreed
Review of Validation Test Purposes

31. DD Cooperation Project
It is a Super Set Specification of Device Description Languages (EDDL)
IEC
FF DDL
EDD
HCF DDL
COMMUNICATION FOUNDATION
HART
Working Group Members:
- Volunteers from FF, HCF and PNO

32. FF Validation Schedule HCF Validation Schedule PNO Validation Schedule
05/03/04
DD Cooperation Project
FF Validation Schedule
 Populate Annex F of the IEC specification with the FF profile information. Jan
 Identify host and field device prototype suppliers Apr
Develop extensions to the DD Tokenizer software and DD Services software. Sep
Develop FF host and FF field device lab prototypes (2 vendors) – parallel path to extensions. Sep
Lab validation testing completed Dec
HCF Validation Schedule
2003
 Modify the HCF DDL specification to include DD Cooperation enhancements.
 Send HCF specification to HCF members for ballot (30 days).
 Approval of HCF specification Dec
2004
Modify HCF DD Tokenizer/development tools - make available to HCF membership for testing.
Validation Testing Completed Dec
PNO Validation Schedule
 Draft of specification in IEC format reviewed by the PNO TC4 WG EDDL. Oct
 Distribute specification to PNO advisory board for comments. Nov
 PNO advisory board decides to start PNO member review process. Dec
 PNO member review - 3 month Mar
 Finalize specification and release Apr
2005
Certification (Interoperability Test) Process. Feb

33. Standard Transducer Blocks
05/03/04
Standard Transducer Blocks
Develop specifications and registration testing for transducer blocks to improve interoperability and ease of use (e.g. pressure, temperature)
Transducer Block Standard Structures Release 1.0
Standard Pressure Transducer Block Release 1.0
2002
4Q Project Kickoff
Team: E+H, Fieldbus Inc., Shell, Smar, Syncrude, Yamatake, Yokogawa
2003
1Q Project Plan Approved
2Q Pressure Specification Preliminary Specification
3Q Pressure Devices from 2 vendors Delivered
4Q Specification Validation Lab Test Completed for Pressure
2004
1st Half – Release Pressure Final Specification
2nd Half – Update ITK with Pressure Test Cases – Beta ITK Testing
2005 – First registered Transducer Blocks
Test Cases for the Standard Pressure Transducer Block is included in ITK 4.6

34. Standard Transducer Block Final Specification Released
Standard pressure transducer block is the first to be released
Released - the final specification for a standard pressure transducer block (TB). Like function blocks, TBs are key components of open, integrated FOUNDATION™ fieldbus architecture. TBs reside at the fieldbus User Layer , used to make sensor-related parameters needed for calibration and diagnostics visible to the fieldbus network.
Standard TBs enable end users to realize additional operational benefits from their FOUNDATION™ fieldbus system, reduced setup time when replacing devices, improved consistency - interoperability of operator and maintenance displays between devices from different vendors, and improved asset utilization.
Tested, proven and easy to implement this significant step forward provides end users with improved access to maintenance and diagnostics. supporting operating system independent proven information in interoperable fieldbus devices.

35. Total of Eight HSE Class 42a Linking Devices Registered
HSE Registration
05/03/04
HSE Linking Device Class 42a-1
Supports client/server - Enables H1 configuration and operation from HSE
ABB (2 versions), Emerson, Smar, and Softing devices are registered.
HSE Linking Device Class 42a-2
42a2 includes Function Block Connect Option – easier configuration from host
National Instruments, Rockwell and Smar devices are registered
HSE Linking Device Class 42c Registration 3Q 2004*
42c Includes 42a-2 + H1-H1 Bridging,
H1-HSE Publisher/Subscriber,
Time Sync
HSE Field Device Class 41c Registration 3Q 2004*
41c HSE device with Function Blocks þ
Total of Eight HSE Class 42a Linking Devices Registered
* Depends on vendor schedules

36. HSE Device with Function Blocks
05/03/04
HSE Device Redundancy
FINAL SPECS 
Priority 1
HSE Linking Devices
Class 42a-1, 42a-2 H1 P L
Plant
Standard Internet
Network Equipment
Priority 2
HSE Device with Function Blocks
Class 41 
Priority 3
HSE Device with Redundant Interface
Class 47
Host 
Aug 04
Priority 4
HSE Redundant Device
Class 46

37. HSE Device Redundancy To H1 To H1 Single LAN that is Fault Tolerant
05/03/04
HSE Device Redundancy
Host
Single LAN that is Fault Tolerant
100 Mbit/s
HSE Stitches A B A B
To H1
To H1
Redundant Pair of HSE Linking Devices
Redundant Pair of HSE Linking Devices
Vendor A
Vendor B

38. HSE Device Redundancy Redundant Interface – Class 47
05/03/04
HSE Device Redundancy
Redundant Interface – Class 47
Class 47 Redundant Interface Lab Testing Mar 2002
System Test Plan Approved by TSC May 2002
Vendors Update Prototypes; Run System Test Jan 2003
TSC Release Redundant Interface Final Specification Feb 2003
HSE Analyzer Toolkit Professional Released May 2003
- Supports Redundant Interface Capture
Redundant Device – Class 46
Class 46 Redundant Device Lab/System Test Plan Approved May 2003
Run Class 46 Lab Test (standalone) Dec 2003
Update Specifications and Compete Test Cases May 2004
Update prototypes and Rerun System Test Jun 2004
TSC Release Redundant Device Final Specification Aug 2004
Complete Beta Registration Testing for Redundancy 4Q 2004
TSC Release Redundancy Test Purposes for Registration 1Q 2005
First Registered Class 47/46 Devices Q 2005*
* Depends on vendor schedules

39. Safety Instrumented Systems
05/03/04
Safety Instrumented Systems
IEC based, TÜV certified, concept for application of
FOUNDATION fieldbus to Safety Instrumented Systems
2002
Project approved by BOD Oct
2003
Kickoff (Requirements and planning) hosted by HIMA Jan
Team: ABB, DuPont, ExxonMobil, Emerson, FF, Shell, HIMA, Honeywell,
Invensys/Triconex, Metso, Rotork, Saudi Aramco, Smar Softing, TÜV, Yokogawa
Project Management Plan Approved by TSC Mar
2nd Full Team meeting (Architecture) hosted by Shell Global Solutions Jun
WebEx Review of Architecture with Function Block/DD/CF Teams Aug
3rd Full Team meeting (Protocol and Safety Analysis) hosted by ABB Sep
Technical Team Meeting (Protocol and Function Blocks) hosted by Smar Nov
TÜV Approval of FF-SIS System Concept Dec 15

40. Future Open FF- SIS Today Tomorrow SIS Logics Hard Wired
Operator
Interface
Engineer
Interface
Proprietary Network
SIS Logics
Hard Wired

41. FF-SIS – New Kid on the Block
05/03/04
FF-SIS – New Kid on the Block
USER LAYER
IEC
USER LAYER
IEC
@ kbit/s
IEC DLL
IEC FMS H1
USER LAYER
IEC
IETF TCP/UDP
IEEE 802.3
MAC
IETF IP
IEC FDA
IEEE 802.3u
@ 100 Mbit/s
HSE
USER LAYER
IEC
TRANSPORT LAYER
SESSION LAYER
PRESENTATION LAYER
APPLICATION LAYER
PHYSICAL LAYER
DATA LINK LAYER
NETWORK LAYER 1 2 3 4 5 6 7
OSI Model
FF-SIS
IEC 61508 1 2 3 4 5 6 7
COMMUNICATION
STACK
COMMUNICATION
STACK
Physical Layer
Physical Layer
H1/HSE 2 12 12 13 12

42. FF-SIS Extension Communication Protocol User Layer
05/03/04
FF-SIS Extension
Communication Protocol
IEC Part 2 Section Compliant
Communication Fault Diagnostic
User Layer
IEC Part 3 Section Compliant
Fault Diagnostic Function Block
CRC（Cyclic Redundancy Check)

43. FF-SIS User Layer Extentions
05/03/04
FF-SIS User Layer Extentions
FBAP(Function Block Application Process) – Part 6
SIS Write Protection Lock
SIS Digital Input
SIS Analog Input
SIS Digital Output
SIS Analog Value Selectior
SIS Digital Value Selector
SIS AND/OR/XOR
In addition to Device Resource Block, FF-SIS Diagnostic and Statistical Function Block will be provided.
6.3.2

44. Safety Instrumented Systems
05/03/04
Safety Instrumented Systems
2004
Draft Preliminary Specification (DPS) Expert Review - hosted by Shell Mar
4th Full Team meeting (Validation Planning) - hosted by Shell Mar
Identify Lab Prototype Suppliers and Lab Test site (Infraserve) Apr
TÜV Agreement on Type Approval Steps for FF-SIS Protocol Apr
Editors meeting to resolve DPS review comments – hosted by Triconex Apr
Update specifications to DPS May
SIS and FB Team Review of DPS 0.9 – Update and release DPS 1.0 Jun
Lab Conformance Test Tool Available Jul
5th Full Team Meeting (Profile and Application Guide) – hosted by Infraserve Sep
Lab prototypes available - Begin Lab Specification Validation Tests Sep
Update Specification to Preliminary Specification (PS) status Dec
2005
FF Membership Review of PS 1Q
TÜV Type Approval for FF-SIS protocol 2Q
TSC Release of Final Specifications (FS) 2Q
Beta FF-SIS Testing Kits (Conformance and Interoperability) 3Q
Beta Registration Test (2 beta products) 4Q
Beta Product Evaluation – Shell Global Solutions 4Q
First registered FF-SIS devices TBD*
* Depends on vendor schedules

45. End User Benefit

46. Process Operator Benefits
05/03/04
Process Operator Benefits
What can be achieved by Fieldbus?
Device and Process Diagnostics available by multi-variable devices
Detect gas substance in Mass Flow Meter
Detect and Notify supply air drop of Control Valve
Detect and Notify the stick of Control Valve Stem
Historise the statistical data of Control Valve travel (stem time)
Detect and Notify in-pulse stick of Pressure Transmitter
Detect and Notify open thermocouple situation
Detect and Notify the Unfilled water condition of Magnetic Flowmeter
Detect and Notify the pipe vibration of Colioli Flow Meter
Detect glass electrode corruption of pH Analyzer
Since the original requirements came from HPI users, Foundation Fieldbus specification includes the functions to meet mission critical application requirements Petrochemical and Chemical applications in HPI market such as Intrinsic Safety, Functional Safety and Plant Asset Management requirements.
Those requirements are pushing to install more intelligent field devices with device/ plant diagnostic and safety considerations into the plant. The device manufactures need to design sophisticated and complex devices requiring more processing power and resources which can run in Intrinsic Safety environments. It is something contradictory and need to go over such technological barriers.
In this sense, Foundation technology is still growing in order to meet such sophisticated industry requirements. For example, there are several new concept of Intrinsic Safety Concept to allow more processing power to field devices, Device Description enhancements and standardization (EDDL), Device Software Down Load and improved Interoprability Testing environments between field devices and host system.
In the following section, the current technology updates will be briefly introduced.

47. “Unneeded” Trips To The Field - Avoided Through Remote Diagnostics
63%
Routine
Check No
Problem
Failed
Instrument
Plugged
Lines
Zero
Off
Calibration
Shift
Source: Dow Chemical Company

48. Engineering Savings Task Time/ Device Analog Fieldbus 2 1 0.5 0.3 0.1
Development of Control Strategy (P&ID Development) 2 1
Instrument Index development / production
0.5
I/O Address assignments
0.3
0.1
I/O List Development
1.5
Instrument loop diagram design/documentation 4
Marshalling panel design / documentation .3
Field terminal box design / documentation
Electrical Cabling and termination lists
2.25
0.7
Precommissioning configuration of devices .5
Total
11.65
5.4

49. Repeatable Savings 50% Savings 90% 85% Wiring Commissioning
05/03/04
Repeatable Savings
Wiring
50%
Savings
Commissioning
90%
85%
Control-Room
Space
Ongoing
Maintenance

50. CAPEX/OPEX Savings in Oil Production Platform
By JNOC Study
Oil & Gas Platform model:
Oil reserves: 200 million barrels
Gas reserves: 100 billion cubic feet
Oil production plateau: 75,000 barrels per day
Outage cost per hour: US$ 100,000
Crane
Quarters Platform
Flare Stack
Drill Derrick
Production Platform
Helideck
Bridge

51. CAPEX/OPEX Savings in Oil Production Platform
By JNOC Study
Conventional
Instrumentation
Fieldbus
Reduction(%)
Initial
Expenditure(M$)
19.07
12.20
Expenditure
Reduction(M$) -
6.87
36.0%
Operating
103.57
69.33
44.21
38.9%
Life Cycle
122.64
81.53
51.07
38.5%
Total: $ 100 M for 25 years

52. Result: End User Benefits
CAPEX
Fieldbus reduces capital costs
Reduced engineering and documentation time
Reduced installation and startup time
Reduced controller and I/O equipment
Reduced control room space
And…FASTER TIME TO REVENUE
OPEX
OUTPUT
Output Efficiency
Quality
Throughput
Availability
Operation & Maintenance
Safety, Health & Environment
Utilities
Waste/ Rework
COST
Cost Efficiency

53. End User Participation

54. End User Seminar – Shenzhen, China ( May 26, 2004)
Ronald Szanyi, P.E.
Project Development Leader for ExxonMobil Research & Engineering (EMRE), Fairfax, VA
Member of the Fieldbus Foundation Board of Directors since 2000

55. End User Seminar – Singapore
End User involvement in FF - Why is it important?
Ensure interoperable system
Ensure users needs are met
Prioritize the enhancements
Plan for technology improvement
Take advantage of opportunities
Field trial testing
Identify economic drivers

56. End User Seminar – Singapore
End User involvement in FF - Why is it important?
(cont’d)
Create internal practices - engineering & maintenance
Association with industry innovators and technology leaders
Move to predictive maintenance
Understand what you need to know to engineer a project
Networking (FUN, Fieldbus Facts)
Sharing of successes and failures

57. End User Seminar – Singapore
End User involvement in FF - Why is it important?
(cont’d)
Input to new areas of development
Access to System Engineering Guide
Help educate engineering contractors

58. End User Seminar – Singapore
Some examples of end user involvement successes
Interoperability testing
Device Descriptions enhancement
Flexible Function Blocks
FF-SIS
Transducer Blocks
HIST Host Interoperability Support Test

59. Interoperability “labs”
05/03/04
End User Requests
Strengthen HIST
Interoperability issues are between hosts and field devices, devices are interoperable between selves
Device Connections/ Physical Layer / Power Supplies
Access and Integration of FF data and associated benefits.
Focus on Management layer to define and show life cycle economics / lost opportunity
Presentations to vertical industry groups
Interoperability “labs”
Regional Centers of Excellence
Private or commercial ventures
Animation: None
Transducer Block and ability to operate any asset management tool with anyone’s system key to future OPEX savings.
Possible vertical integration: OPC collaboration, National Petroleum Show, Gartner Group, ARC Forum, etc.
“Amid the convergence of technologies across the IT stack, a host of products emerging from the world of open source, XML, and Web services are challenging traditional notions of open solutions.
IBM, Apple, Microsoft, Sun, and Nokia are passionate about their “open” mantra in the quest to address interoperability concerns. But the strategy itself is under the threat of collapsing under its own weight: Layers of proprietary technology that limit a company’s ability to build genuinely open infrastructure can lurk beneath the surface.” – Open Standards for Business by Ed Scannell, Haether Havenstein, Tom Sullivan in Feb 3, 2003 issue of InfoWorld (emphasis added by self)

60. Directions Short Term (1-2 years)
05/03/04
Directions Short Term (1-2 years)
Technology Issues
Fieldbus for Safety Applications
Transducer Block standardization
HSE Interoperability/ Control Backbone
HSE Applications
Adoption Issues
Interoperability Labs (HIST)
Fieldbus Economics
Flexible Function Block Demonstration
Revision Level Management
FF Knowledge Base
Animation: Mouse Click per side

61. Directions Long Term (5 years)
05/03/04
Directions Long Term (5 years)
Standard Maintenance Suite
Enterprise Integration
ERP benefits
Global Process Industry market leader
Implement White Papers
Animation: None

62. End User Seminar- Singapore
How to get involved
Sign up End User Society Membership
Sign up for Fieldbus Member Forums
Sign up for Fieldbus Users Network (FUN) List
Sign up for Fieldbus Facts news

63. The Future is Bright
Major global projects are specifying FOUNDATION fieldbus
Demonstrated success on retrofit and re-instrumentation projects
Technology enhancements under development!

64. Fieldbus Foundation A Decade of Leadership
05/03/04
Fieldbus Foundation A Decade of Leadership
The EUAC represents the biggest change with the Fieldbus Foundation in the past year.
Accomplishments since February. See the power End Users have. Continue to deliver things of benefit to End Users

65. 05/03/04