This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Foundation Field bus Implementation guideline documentClient specification / ITB requirementsFieldbus type (i.e. General, Entity,FISCO, FNICO, High Power Trunk etc)Network/segment Topology selection Critical loop defination and applicationLoop response timeSegment design consideration / guidelineHardware PlanningDevice requirementsFF Cable typeRedundancySpare RequirementsControl assignmentsPackage supplied FF instrument interfaceEngineering documents format templatesDCS (HOST) system requirementsNaming convention
Documents/Input required for Preliminary segment designP&ID’sPlot Plan / Equipment LayoutApproved Foundation Field bus Implementation guidelineHazardous area classification
Segment design constraintsField bus type (Safe, FISCO, FNICO or High Power Trunk)Voltage drop calculationCurrent calculationSignal attenuation calculationSegment execution time.Segment criticality Rating Spare capacity
Documents/Input required for Final segment designP&ID’sInstrument Location PlansCable tray Layout / Plot Plan / Equipment LayoutApproved Foundation Field bus Implementation guidelineHazardous area classificationControl NarrativesComplex Loop Narratives List of Critical Control Loops List of Loops requiring Loop execution times faster than 1 second. I/O Lists
Device certified for latest interoperability testing Device approved by the Fieldbus Foundation and carry the Foundation fieldbus“Check Mark” logo.Device Description (DD) and Common File Format (CFF) files available. Device have link master capabilities.Device have required function block (AI, PID, AO etc) and execution time.Device minimum operating voltage, current and power consumption.Device should be polarity insensitive.Capable of performing continuous advanced diagnostics, self-test function, provide specific diagnostic information, on-line automation procedures (e.g.calibration) from the DCS, support peer to peer communicationFF device and its function blocks shall be tested and certified by the DCS vendor
Function blocks shall be downloadable into the devices by the system.Device certified for plant hazardous area. Device used in hazardous area should have
Trunk cable can be multi-pair (as per project requirement).Fieldbus Cable is to be unique in color (e.g. Orange with blue strips for I.S. segment)Cable should be armoured for outdoor installation in cable tray
Sufficient space to accommodate termination block / field barrier, surge protector, conventional terminal, isolation switch (for field barrier isolation) etc.Material i.e. Stainless steel, GRP etcInactive spare Fieldbus trunk pairs shall be terminated on conventional terminal blocksComplete box should certified for hazardous area installation i.e. EExe etcWire capacity size 12 – 24 AWGConventional terminal block to be provided suitable for wire size 12 – 24 AWGShort circuit protection & surge protection to be provided with each spur
List of Conventional documents required modification as per Foundation fieldbus engineering
System Conceptual drawingP&IDDatasheet Instrument index / DCS I/O listJunction box wiring diagramLoop wiring diagram / Segment Wiring diagramManufacturer documentation
Newly added documents for Foundation fieldbus engineeringFoundation Fieldbus Implementation Philosophy / GuidelineInstrument Segment/Network DiagramSegment validation reportOff line configuration data document
Following input to be provided for DCS engineering. Tag No.Calibration range and UnitFlow range and UnitOutput typeTransmitter ModelNode Address (To be provided by DCS vendor)Device Type Device Class (Basic / Link master)Device RevisionDD RevisionCFF RevisionPID Function Required
Redundant Power feeder to bulk power supplyRedundant Bulk Power supplies with battery backup (Min. 30 minutes)Redundant system controller power supplyRedundant system controllersRedundant Foundation Fieldbus H1 cardRedundant Foundation Fieldbus power conditionersRedundant controller should not share the same back planeRedundant H1 card should not share the same back planeRedundant FF power supply should not share the same back planeRedundant Link Active scheduler
Segment shall be designed for 25% spare capacity- FFPS supply current : 25% spare current capacity- FF Spur Terminals (wiring block) : 25% spare spur terminal capacity- Spare capacity in segment bandwith (i.e. Function block capacity, Number of
VCR, Macrocycle time etc) 25% spare pair in trunk cable or minimum 1 pair as spare.20% installed hardware spares in Host System (H1 card, FFPS etc)40% spare capacity in Bulk power supply
Include Segment Validation in system vendor’s scope. Consider critical complex loops under conventional I/OConsider FF multiplexer temp transmitter for non-critical temperature monitoring loops e.g. column, furnace, reactor, etc.Make use of FF-type multivariable transmitter & save on pipe penetration.Redundant LAS in Redundant H1 card (if available), other wise one of the field devices in segmentDon’t mix devices with different macro cycle time on same segment.Close co-ordination between engineer, designer and programmer (DCS vendor)Off line configuration data should be available from device vendor.Simple closed loop devices on same segment with PID controller in valve positioner. No control in TransmitterComplex loop controllers / control strategy in Host system controllerPackage supplied FF instruments wire to plant FF junction boxSystem vendor’s Installed Sites and Project sizes
Must have standard system Product (Hardware, software etc) InteroperabilityMust be certified for FF Host Interoperability Support Test (HIST)Host system Fieldbus FunctionalityMust support FF field device DD and CFF files.System should have a configuration tool capable of on-line and Off-line configurationSupport Implementation of the FF function blocks in field devices.System should support Redundant hardware and Bump less transfer for high availabilityTroubleshooting, Maintenance should be possibleShould have dedicated advanced Diagnostics and computer based maintenance system.Must have Asset Management software and Advanced Process Control Must have third party interface capability