city of calgary - fieldbus foundation · plant hardware digital communication ... why ff bus at...

Name of EventLocation

Current and Future Fieldbus Installationsat The City of Calgary

Water and Wastewater Facilities

Darrol WeissCPIT EI&C Systems Specialist

Vincent Chiew Technology Development and Systems Engineer

City of Calgary Water/Wastewater Business Unit

Calgary End User ConferenceCalgary, Alberta, Canada

June 9-10, 2005© 1999 – 2005 Fieldbus Foundation

2

Presentation OutlinesIntroduction

Current StateRelative plant DCS sizesFieldbus and conventional I/O point countWhy FOUNDATION fieldbusTM at Water and Wastewater PlantsControl System LeveragePlant Hardware Digital Communication ConsiderationsSystem hardware and software ConsiderationsTraining and change managementBusiness management requirements



3

Strategic PlanWhy FOUNDATION fieldbus?Big Picture: Concept Map and Influence DiagramProcess vs Technology ViewsFOUNDATION fieldbus: a system perspectiveSystems Engineering perspective of FOUNDATIONfieldbus



4

Current State

Approximate Glenmore and Bearspaw points count:

(to be built)50% FOUNDATION Fieldbus points30% 4-20mA points20% Discrete points

Approximately ~2500 pointsSource: Waterworks Consultants

Point Counts



5

Background WaterworksBearspaw:FF-H1Pre TreatmentFacility1000DST’sResiduals TreatmentFacility1200DST’s



6

Background Waterworks

Glenmore:FF-H1

HighLift PumpStation750DST’s

SodiumHypoChlorite750DST”s



7

Current State

Approximate Pine Creek points count:(to be built)

30% FOUNDATION fieldbus points30% 4-20mA points connected to FF40% 4-20mA points

Approximately ~2500 points

Source: Pine Creek Consultants

Point Counts



8

Bonnybrook:Background Wastewater

Process: Biological Nutrient Removal (BNR)

Capacity: 500 ML/day

1995 Picture

Headworks

Clarifiers

Digesters

UV Light Disinfection Facility



9

Fishcreek:

Background Wastewater1995 Picture

Process: Oxygen-activated sludge Process (UNOX)

Capacity: 72 ML/day

Headworks

Clarifiers

Digesters

UV Light Disinfection Facility



10

Pinecreek:

Background Wastewater2004 Drawing

Process: Biological Nutrient Removal (BNR)

Capacity: Phase 1: 100 ML/dayPhase 2: 300 ML/dayPhase 3: 300 ML/day



11

Why FF Bus at Water/Wastewater Facilities?



12

Control System Leverage

Push FF devices to work for the system by:Configuration of the active LASDiagnostics to DCSH1 to HSE, where to do advance control algorithmsReport by exception to reduce scan ratesFunction block programming for local PIDReporting to integrated AMSConfiguration and troubleshooting via maintenance work station

Working with your E makes the P and C easy



13

Plant Hardware Communication Considerations

Electrical MCC’s and switchgearElectrical protection relaysActuatorsConventional Instrumentation 4-20maAnalytical devicesDiscrete Position switches



14

System Hardware and Software Considerations

Shock and Awe - System licensing and device tag requirement, what do you need?Who is going to use the additional informationSystem interface to different fieldbus technologies, system architectureSoftware “Hooks” to business enterprise system software, like AMS and data repository or historian



15

Training and Change Management

When do you train and who?What type of instruments do I use to trouble-shoot Fieldbus technologies, computer?What do I need to know before replacing an online Fieldbus device, is it standby LAS?What parameters do I need to set and from where, data file?How do I use the Transducer and Resource BlockHow do I interface to CMMS



16

FF Resource Block



17

FF Transducer Block



18

Business Management Requirements



19

Integration of Plant Equipment



20

Strategic Plan

Reasons why we choose FF:Asset management (Cost and Effective)New Plant – Greenfield TechnologyProven at Waterworks, for WastewaterEvolutionary BenefitsContinuous Process Improvement and OptimizationSimplify System Architecture



21

FoundationFieldbusDevices

Tools

Staff

Knowledge

Training

Concept Map and Influence Diagram

FieldbusFoundation

“Innovative”

Vendor

ReliabilityCentered

Maintenance

StaffingSource

Internal:operation

experience

External:School, SAIT

Industry

OurBusiness

philosophy andstrategy

Conditionbased

management

Assetmanagement

Lifecyclemanagement

OurOperation


Citizens & Citycouncil

Strategic Plan



22

FoundationFieldbusDevices

Tools

Staff

Knowledge

Training

Concept Map and Influence Diagram

FieldbusFoundation

“Innovative”

Vendor

ReliabilityCentered

Maintenance

StaffingSource

Internal:operation

experience

External:School, SAIT

Industry

OurBusiness


Conditionbased

management

Assetmanagement

Lifecyclemanagement

OurOperation


Citizens & Citycouncil

$

$$

Strategic Plan

$ $ $ $ $ $$$

$$

$$$

$ $

$$



23

Strategic Plan

CurrentTechnology

NewTechnology

CurrentProcess

NewProcess

Given

Process and Technology Matrix Views

Leveraging,Cost saving

Want,Enhancement,Sustainment

Enhancement,Enabler



24

Strategic Plan

CurrentTechnology

New FieldbusTechnology

CurrentProcess

New OperationProcess

Given

Process and Technology Matrix Views

Leveraging,Cost saving

Want,Enhancement*,Sustainment*

Improvement*,Optimization*,

Enabler*

Life Cycle Management* Reasons for FOUNDATION fieldbus



25

Strategic Plan

Currently, we have distributed control capabilities such thatDCS > ∑ (Subsystems)The whole is greater than the sum of its parts

Adding FOUNDATION fieldbus Subsystem on to our existing DCS, imply a relation where our DCS capabilities are linear proportion to added FOUNDATION fieldbus Subsystem capabilities;

DCS + FOUNDATION fieldbus Subsystem > (∑ (Subsystems)) + FOUNDATION fieldbusSubsystem

Therefore, we need to build a strategic plan to incorporate FOUNDATION fieldbus into the complete system in a holistic manner to achieve the following:

DCS >> (∑ (Subsystems)) + FOUNDATION fieldbus Subsystem

Note: Bigger the picture, bigger the value of FOUNDATION fieldbus investment

Systems Perspective of FOUNDATIONFieldbus Subsystem



26

Strategic Plan

Site

Host

Controller

Fieldbus

Space,Function HighComplexity

LowComplexity

Time,Execution

SystemStrategy

Aspect/ObjectOriented

StructureOriented

LowComplexity

HighComplexity

Architecture

Peer to Peer Client/Server

Systems Engineering Perspectives

Pipeline,Concurrent,Vector

ProcessProgramming



27

Strategic Plan

Example: Time & Space Complexitiesshowing worst case scenarios

Sorting Algorithms



28

References

Fieldbus Foundation Documents:Systems Engineering Guidelines, 2003-2004Foundation fieldbus Application Guide, FF-950, Rev 1.1, 4 Dec, 2002Technical Overview, FD-043 Rev 3.0, 2003Wiring and Installation 31.25 kbits/s, Voltage Mode, Wire Medium Application Guide, AG-140, Rev 1.0, 199631,25 KBIT/s Intrinsically Safe SystemsPlant WEB University Emerson Process Solutions

Other Documents:Berge, Jonas; 2002, Fieldbus for Process Control: Engineering, Operation and Maintenance, ISA - The Instrumentation, Systems, and Automation Society, Pp. 1-444