i i di p t ltdinvensys india pvt. ltd. - · pdf filetriconex: safety solutions wonderware:...

I I di P t LtdInvensys India Pvt. Ltd.

About Invensys?

INVENSYS, Plc

OPERATIONS MANAGEMENT

RAIL CONTROL

• Annual sales USD4bn (£2.8bn)• FTSE-100• 23,000 employees • 80 countries

EUROTHERM

WONDERWARE

IPS

• Installed base of > £ 20 billion in over 50,000 plants• Software in more than one third of world’s plants• World’s leading provider of appliance controls

Invensys and the Invensys logo are trade marks of Invensys plc

Merging 4 Internal Divisions to form IOM

Invensys and the Invensys logo are trade marks of Invensys plc© Invensys 00/00/00 Invensys proprietary & confidentialSlide 3

IOM Global Leading Brands

Powering Invensys LeadershipAvantis: Plant Asset ManagementAvantis: Plant Asset Management

Eurotherm: Industrial controls, monitoring products and services

Foxboro: Process measurement and control solutionsFoxboro: Process measurement and control solutions

Infusion: Enterprise Control

IMServ: Energy ManagementSe e gy a age e t

Sim-Sci Esscor: Advanced Performance Improvements

Triconex: Safety Solutionsy

Wonderware: Real-time industrial operations management


Invensys Footprint

A truly global business with facilities in more than 50 countries serving customers over 180 countries.

• 23 of the top 25 petroleum companiesp p p• 47 of the top 50 chemical companies• 19 of the top 20 pharmaceutical companies• 6 of the top 7 appliance manufacturers• 6 of the top 7 appliance manufacturers• 50 railway customers and mass transit operators in 30 countries• 17% of the world’s oil refining• 23% of the world’s chemical production• 64% of the world’s LNG production• 20% of the world’s electricity production• 36% of the world’s nuclear energy production


System Advantage on interoperability and

Predictive IntelligencePredictive Intelligence

Agenda

• What is interoperability?

• Why interoperability is important?

• How we will conclude, device has been pass interoperability?

• Or What makes FOUNDATION devices interoperable?

• Benefits of Interoperability


What is Interoperability?

The Fieldbus Foundation defines interoperability as "the ability to operate multiple devices, independent of manufacturer, in the same system, without loss of functionality.“

The term multiple devices refers to a set of fieldbus products that may include a mix of field devices such as valves and transmitters, and host devices such as control systemsdevices such as control systems.

Independent of manufacturer means vendor independence. That is, having the freedom to choose the best technology for the task, regardless of which

d k h dvendor makes the product.

In the same system means within the mix of control equipment that operates as a single automation solution. There are, of course, guidelines foroperates as a single automation solution. There are, of course, guidelines for the number and type of devices that should be combined together within individual segments of the fieldbus network, primarily for electrical and intrinsic safety purposes.


What is Interoperability?

• Without loss of functionality means the devices operate without the loss of any of their designed features. That is, being part of an interoperable network d 't i t f ith f th i f tidoesn't interfere with any of their functions.

• Interoperability refers to the ability of any ITK-registered device to work with any HIST-analyzed host.

• A major requirement of potential Fieldbus users is interoperability, the ability of two or more systems to exchange information and to mutually use the information that has been exchanged. This encompasses open systems, g p p y ,interworking and supplier independence


Why interoperability is important?

• Enables “best-of-breed” deployments –

• Customers may have business requirements that can only be delivered with specific applications or platforms This best-of-breed environment meets thespecific applications or platforms. This best-of-breed environment meets the requirements for rapidly deploying solutions. So interoperability is a key requirement that can help ensure customers meet their demanding business needs.

• Reduces operational cost and complexity –

• Customers will continue to have mixed environments for the foreseeable future. The ability for these systems to work together reduces the cost of building and supporting a heterogeneous infrastructurebuilding and supporting a heterogeneous infrastructure.

• Leverages existing investments


H1 Device Registration

FunctionBlocksH1

StackStack

RegisteredH1 Device

RegisteredH1 Device

H1

DD

H1Testers

RegisteredInvensys and the Invensys logo are trade marks of Invensys plc

gDD

What makes FOUNDATION devices interoperable?

• To be truly interoperable, devices must ……………….

• Be physically and electrically compatible with the fieldbus segment (as defined by the ISA 50.02-2 Physical Layer Specification).

• Include a communication stack that passes the Fieldbus Foundation's Stack Conformance Test.

• Correctly implement the Function Block Application Process Model defined in the FOUNDATION fieldbus specification. This means a device's function blocks must interconnect and interoperate with the device s function blocks must interconnect and interoperate with the function blocks of other devices on the network.


What makes FOUNDATION devices interoperable?

• Device is Registered by the Fieldbus FOUNDATION after it passes these tests:

• FOUNDATION™ fieldbus Physical Layer Conformance Test Specification (FF-830). A basic prerequisite for interoperability is conformance to the relevant specification

• Interoperability Test of Standard Function Blocks, Resource Block and System/network Management Functions

• Device Description (DD) Interoperability Test All Files necessaryDevice Description (DD) Interoperability Test All Files necessary (Capabilities File) for the device definition are included and appropriate.


Conformance Testing

– Conformance test of communication stack confirms compliance withSensor stack confirms compliance with FOUNDATION protocol specification

– Conformance testing is performed only t F h f I tit t i d d tat Fraunhofer Institute, an independent

testing facility in Germany

– Test results from stack under test are

User Layer

Communication Stack compared with those from a system with a known good stack for verification

Physical Layer

Communication Stack


Interoperability Testing

– Interoperability testing of a device ensures devices from different manufacturers candevices from different manufacturers can communicate without loss of functionality

– Performed by Fieldbus Foundation in Austin TexasAustin, Texas

– Tests device operation for compliance with the Foundation Fieldbus specificationFieldbus Device


FF Device Description (DD) files

• Two main file types:

– DD (.ffo) and Capabilities (.cff) filesDD (.ffo) and Capabilities (.cff) files

– Both together are commonly referred to as the DD file

• DD files are identified by:

– Manufacturer’s ID

– Device Type

Device Revision– Device Revision

– DD Revision

• DD files and FF devices both have revision numbers

FF Device Description (DD) files

DD files contain information which allows the controlsystem to understand and work with the device:system to understand and work with the device:

– What function block types are present?

– How many of each?

– How long does each block take to execute in the device?

– What parameters are available in each block?

– What are the parameter data types and descriptions?p yp p

– Where is a parameter found in the device?

– What communication resources are available?

Wh h f h i i f h d i ?– What are the performance characteristics of the device?

– Is the device a Link Master type?

Function Blocks Addressed by FF Interoperability Testingp y g

• AI –Analog Input •AO –Analog Output

• DI –Discrete Input

• PID –PID Control

•DO –Discrete Output

•ISEL –Input Selector

•SC –Signal Characterizer• ARITH–Arithmetic

• MAI –Multiple Analog Input

• INT Integrator

SC Signal Characterizer

•MAO –Multiple Analog Output

•MDI –Multiple Discrete Input• INT –Integrator

•MDO –Multiple Discrete Output


What makes FOUNDATION devices interoperable?te ope ab e

• Interoperability is made possible by the fact that devices and software are conforming to the same standard Testing and registration ensures thatconforming to the same standard. Testing and registration ensures that FOUNDATION devices bearing the official "checkmark" seal can be connected on the same bus or network and exchange information without an heroic integration effort. End users can select the best device for a specificintegration effort. End users can select the best device for a specific measurement or control task, regardless of the manufacturer.

®

FOUNDATION


Device Vendor’s Responsibilities• Primary interest – devices work as intended

• Focused on device functionality – Manufacturer-specific part – transducer blocks

• Products differentiated in Transducer Block

• Rely on third parties (Softing, SMAR, or NI) for stack

• Some purchase FBs from outside sourcesSome purchase FBs from outside sources

• Purchase tools from FF for pre-testing their devices

• Tools do not test algorithm behavior due to Limited testing capability

• Sometimes only using NI Configurator as test tool

• NI Config doesn’t handle, for example, alarm behavior

• Vendors learning, but still focused on making devices work properly and to g g p p yspec

• Help insure FF tests will pass


System Vendor’s Responsibilities

• Primary interest – overall system control behavior• Interfacing to and integrating with FF devices• Customer expects WHOLE system to work correctly. For that reason, p y y

system vendors have strong role in device testing• Today, formal FF interoperability testing programs in place by• Invensys (Foxboro I/A)• Honeywell (PlantScape and Experion PKS)• Emerson (DeltaV and Ovation)• Yokogawa (Centum)Yokogawa (Centum)• ABB (Industrial IT)• Rockwell Automation• SMAR (System 302)• SMAR (System 302)• Practices and policies vary, but end purpose same – ensure devices work

correctly and dependably with the control system


Service Request FormInteroperability Lab Services Request Form

Vendor/Manufacturer:

Company: Street:

Device Information

Device Manufacturer:

Device Model No.:

Device Type (Indicate type with “X”) City: State/Province: Zip/Post code: Country: Web Site:

Device Type (Indicate type with X ) HART FF X Profibus DeviceNet Description:

Business Contact Information:

Your Name: Title: Tel: FAX

Description:

Device Part Number:

Device Revision: Firmware Revision:

Device ID (serial number):FAX: E-Mail:

Technical Contact Information:

Your Name: Title:

DD file: Revision:

CFF file: Revision:

FFO file: Revision:

Title: Tel: FAX: E-Mail:

SYM file: Revision:

DTM file: Revision:

Calib/Diagn DTM file: Revision:


Service Request FormPrerequisite Requirements:Prerequisite Requirements:

DD files and Vendor DTM must be released products. :

Device registered with FF and at ITK test level version 4.5 or newer. :

DTM must be certified by the FDT group. :

HART Foundation DD Cert HART Foundation DTM Cert

Device (FF Registered) ITK Level:

List of Deliverables - Please provide information for each of the items listed below. Note: Deliverable(s) classified “Required” are necessary to fulfill Interoperability test criteria.

Device Support Files; DD and CFF files required, DTM optional 1.

Parameter list indicating whether they are read only or writable and default values where applicable.

Recommended Device Parameter Configurations for primary applications 2.

Parameters generally restricted to use by factory setup or a maintenance engineer and which should NOT be written to during device commissioning or application configuration.

Define Logical Parameter Groups 3.


Combined Efforts from Both System as well as Device Vendorwell as Device Vendor

• Vendors also test because…

• Customers expect system assurancep y

• Problems sometimes found with DD/CFF files

• Problems sometimes found with device behaviors

• (even if FF registered!)

• Host vendors want to debug and improve their systems

• That last reason is very important

• All of this testing makes the control systems stronger as well!

With t Fi ldb i t bilit t ti b th t d th iWithout Fieldbus interoperability testing by the system vendors, there is no guarantee that it all works!


Benefits of Interoperability

• Devices from different manufacturers are able to interact with each other without Host interaction

– Control in the field works seamlessly– Devices do not conflict with each other

• Host can read/write the resource and transducer block parameters

D i di ti b d b th h t• Device diagnostics may be accessed by the host

• Unexpected surprise at plant will be avoid.


FINAL RECOMMENDATION• If you have an upcoming project…

–Contact your system vendor early to make sure that…….

•They having well equipped Interoperability LabThey having well equipped Interoperability Lab

–Identify a precise device for application

•devices are being or have been tested

l t t D i R i i•use latest Device Revision

–Track record for Revision Changes

–Follow the standard procedures p


Customer Responsibilities

Test Case # Test function DescriptionDate of

testingTester Comments

Device Communication Testing

1.1 Connect Device to the Host

1.2 Device identification

1.3 Import Device DD's to create a primary DD template

1.4 Set PD Tag on the device

1.5 Set PD Address on the device

1.6 Physical Layer - Bus Noise test

1.8 Set PD Address on a fully loaded H1 segment


Real Collaboration Real Time ResultsInvensys and the Invensys logo are trade marks of Invensys plc

Real Collaboration. Real-Time Results.

Thank You!

Questions?

i i di p t ltdinvensys india pvt. ltd. - · pdf filetriconex: safety solutions wonderware:...

Documents