FUNCTIONAL DESIGN SPECIFICATION

Ref # :Rev # :Date :OV-141113-FDSA12-Feb-2015

Project Title :

Customer :End User :Expansion of Modicon PCS and ESD PLC for MOL Bijel 1OilServMOL-Iraq

Project Title :Customer :End User :Project Title :Customer :End User :

REVISION HISTORY

A12-Feb-2015Issued For ApprovalHSJRBF

Rev #DateDescriptionWRTByRVWByAPPByAPP ByAPP ByComments

INTECHCUSTEND USER

NOTICES, COPYRIGHTS AND TRADEMARKS Electronic controlled copy is available to all corresponding, on the corporate intranet with secure access controls and respective rights. This Document contains proprietary information of INTECH Process Automation.Information contained herein is for the sole use of the customer receiving this document. Acceptance of the document by the customer constitutes agreement by the customer that they shall not disclose proprietary information by INTECH Process Automation to any third party and shall not transmit any documents or copies thereof containing proprietary information of INTECH Process Automation to any third party except as may by authorized in writing by INTECH Process Automation.No part of this document may be used, translated into another language, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written consent of INTECH Process Automation.While every effort has been made to ensure the accuracy of this document, INTECH Process Automation assumes no responsibility for omissions and errors. Neither is any liability assumed for damages resulting from the use of information contained herein.

Questions or comment regarding this document or the product to which it relates should be directed to:

INTECH Process Automation Inc.4903 W Sam Houston Parkway N, Suite A100Houston, Texas 77041, USATel: +1 713 849 1000Fax: +1 713 856 0785Email: info@intechww.comURL: www.intechww.com

INTECH, TAP and FPM are registered logotypes and trademarks of INTECH Process Automation.

Copyright 2004 INTECH Process Automation Inc. All Rights Reserved.

All other logotypes, trademarks, brands and product names in this document are acknowledged as properties of their respective companies/owners.

TABLE OF CONTENTS1.INTRODUCTION81.1.SCOPE OF DOCUMENT81.2.REFERENCE DOCUMENTS91.3.ACRONYM USED IN THIS DOCUMENT101.4.SYSTEM ARCHITECTURE112.SCOPE OF WORK122.1.HARDWARE SCOPE OF SUPPLY122.2.SOFTWARE SCOPE OF SUPPLY133.HMI SOFTWARE DESIGN143.1.INTRODUCTION143.2.SOFTWARE VERSION143.3.HMI SYSTEM CONFIGURATION144.OPERATOR INTERACTION154.1.HMI SCREENS LIST154.1.1.HMI SCREEN164.1.1.1.OVERVIEW_3164.1.1.2.OVERVIEW_4174.2.ALARM SUMMARY185.PLC SOFTWARE DESIGN GUIDELINES195.1.INTRODUCTION195.2.SOFTWARE ENVIRONMENT SETTINGS195.3.APPLICATION STRUCTURE205.3.1.PROCESS PLC APPLICATION STRUCTURE205.3.2.ESD PLC APPLICATION STRUCTURE215.4.REMOTE IO HARDWARE CONFIGURAION225.4.1.PROCESS PLC225.4.2.ESD PLC235.4.3.MAST (MASTER TASKS)245.4.4.SECTIONS245.5.PLC OBJECT FUNCTIONALITY265.5.1.INTRODUCTION265.5.2.ANALOG INPUT SCALING BLOCK265.5.3.PID CONTROLLER BLOCK285.5.4.PUMP OBJECT305.6.CONTROLLER TAGS305.6.1.PROCESS PLC305.6.2.ESD PLC306.hmi OBJECT FUNCTIONALITY316.1.INTRODUCTION316.2.OBJECT TYPES317.ANALOG INPUT327.1.OBJECT OVERVIEW327.2.VARIABLE NAMING NOMENCLATURE328.PID CONTROL VALVE348.1.PID OBJECT OVERVIEW348.2.GRAPHICAL REPRESENTATION348.3.CONTROLLER IO & VARIABLE NOMENCLATURE358.4.PCV ANIMATION DETAILS359.DISCRETE INPUT369.1.OBJECT OVERVIEW369.2.GRAPHICAL REPRESENTATION369.3.CONTROLLER I/O & VARIABLE NOMENCLATURE369.4.ANIMATION DETAILS3710.PUMP WITH COMMAND AND FEEDBACK3810.1.PUMP P-170A/B OBJECT OVERVIEW3810.2.ANIMATION DETAILS3811.SHUTDOWN VALVE object4011.1.OBJECT OVERVIEW4011.2.GRAPHICAL REPRESENTATION4011.3.IMPLEMENTATION TABLE4011.4.ANIMATION DETAILS4111.5.DETAILED SPECIFICATIONS42

1.INTRODUCTION81.1.SCOPE OF DOCUMENT81.2.REFERENCE DOCUMENTS91.3.ACRONYM USED IN THIS DOCUMENT101.4.SYSTEM ARCHITECTURE112.SCOPE OF WORK122.1.HARDWARE SCOPE OF SUPPLY122.2.SOFTWARE SCOPE OF SUPPLY123.HMI SOFTWARE DESIGN GUIDELINES133.1.INTRODUCTION133.2.SOFTWARE ENVIRONMENT SETTINGS133.3.HMI SYSTEM CONFIGURATION134.OPERATOR INTERACTION144.1.HMI SCREENS LIST144.1.1.HMI SCREEN144.1.1.1.OVERVIEW_3154.1.1.2.OVERVIEW_4164.2.ALARM SUMMARY165.PLC SOFTWARE DESIGN GUIDELINES175.1.INTRODUCTION175.2.SOFTWARE ENVIRONMENT SETTINGS175.3.APPLICATION STRUCTURE185.3.1.PROCESS PLC APPLICATION STRUCTURE185.3.2.ESD PLC APPLICATION STRUCTURE195.4.HARDWARE CONFIGURAION205.4.1.PROCESS PLC205.4.2.ESD PLC215.4.3.MAST (MASTER TASKS)225.4.4.SECTIONS225.5.PLC OBJECT FUNCTIONALITY235.5.1.INTRODUCTION235.5.2.ANALOG INPUT SCALING BLOCK235.5.3.PID CONTROLLER BLOCK255.6.CONTROLLER TAGS275.6.1.PROCESS PLC275.6.2.ESD PLC276.hmi OBJECT FUNCTIONALITY286.1.INTRODUCTION286.2.OBJECT TYPES287.ANALOG INPUT297.1.FIT-0013 OBJECT OVERVIEW297.2.VARIABLE NAMING NOMENCLATURE297.3.ALARM MANAGEMENT CYCLE308.PID CONTROL VALVE318.1.PIT-0010 - OBJECT OVERVIEW318.2.GRAPHICAL REPRESENTATION318.3.CONTROLLER IO & VARIABLE NOMENCLATURE328.4.ANIMATION DETAILS329.DISCRETE INPUT339.1.OBJECT OVERVIEW339.2.GRAPHICAL REPRESENTATION339.3.CONTROLLER I/O & VARIABLE NOMENCLATURE339.4.ANIMATION DETAILS3310.PUMP WITH COMMAND AND FEEDBACK3510.1.PUMP P-170A/B OBJECT OVERVIEW3510.2.ANIMATION DETAILS3511.discrete output objects3711.1.ESD-9002 OBJECT OVERVIEW3711.2.GRAPHICAL REPRESENTATION3711.3.IMPLEMENTATION TABLE3711.4.ANIMATION DETAILS3811.5.DETAILED SPECIFICATIONS39

LIST OF FIGURES

Figure 1: System Architecture11Figure 2: Overview_3 Screen16Figure 3: Overview_4 Screen17Figure 4: Alarm Summary Screen18Figure 5: Process PLC Application Structure20Figure 6: ESD PLC Application Structure21Figure 7: Process PLC Expansion Rack22Figure 8: ESD PLC Expansion Rack23Figure 9: Process PLC Sections Structure24Figure 10: ESD PLC Sections Structure25Figure 11: AI Scaling Formula26Figure 12: AI Scaling Block26Figure 13: PID Control Block28Figure 14: Controller Tag Name 32Figure 15: Graphical representation(s) of analog Object32Figure 16: Graphical Representation of PIT-0010 Controlling PID34Figure 17: Controller Tag Name35Figure 18: Graphical Representation of DI_0136Figure 19: Controller Tag Name36Figure 20: ESD/SDV Object (Typical)40

Figure 1: System Architecture11Figure 2: Overview_3 Screen15Figure 3: Overview_4 Screen16Figure 4: Process PLC Application Structure18Figure 5: ESD PLC Application Structure19Figure 6: Process PLC Expansion Rack20Figure 7: ESD PLC Expansion Rack21Figure 8: Process PLC Sections Structure22Figure 9: ESD PLC Sections Structure23Figure 10: AI Scaling Formula23Figure 11: AI Scaling Block24Figure 12: PID Control Block25Figure 13: Graphical representation(s) of analog Object29Figure 14: Graphical Representation of PIT-0010 Controlling PID31Figure 15: Controller Tag Name32Figure 16: Graphical Representation of DI_0133Figure 17: ESD/SDV Object (Typical)37

LIST OF TABLES

Table 1: Reference Documents9Table 2: Acronym List10Table 3: HMI Software Environment Settings14Table 4: HMI System Configuration14Table 5: HMI Screen List15Table 6: PLC Software Environment Settings19Table 7: Process IO Rack Hardware Configuration22Table 8: Process IO Rack Hardware Configuration23Table 9: AI Scaling Block IO Elements27Table 10: PID Control Block Intput Element29Table 11: PID Control Block Output Element29Table 12: Process Controller Tags30Table 13: ESD Controller Tags30Table 14: HMI Object details31Table 15: Variable Naming Nomenclature32Table 16: I/O Variable Name35Table 17: Animation Details for Object PIT-001035Table 18: I/O Variable Name36Table 19: Pump P-170A States Indications39Table 20: ESD/SDV implementation table40Table 21: SDV States Indications41Table 22: SDV/BDV Object Detailed Specification42

Table 1: Reference Documents9Table 2: Acronym List10Table 3: HMI Software Environment Settings13Table 4: HMI System Configuration13Table 5: HMI Screen List14Table 6: PLC Software Environment Settings17Table 7: Process IO Rack Hardware Configuration20Table 8: Process IO Rack Hardware Configuration21Table 9: AI Scaling Block IO Elements24Table 10: PID Control Block Intput Element26Table 11: PID Control Block Output Element26Table 12: Process Controller Tags27Table 13: ESD Controller Tags27Table 14: HMI Object details28Table 15: Variable Naming Nomenclature29Table 16: I/O Variable Name32Table 17: Animation Details for Object PIT-001032Table 18: I/O Variable Name33Table 19: Pump P-170A States Indications36Table 20: ESD/SDV implementation table37Table 21: SDV States Indications38Table 22: SDV/BDV Object Detailed Specification39

INTRODUCTIONCurrent Beijell-1 facility is equipped with Schneider Electric M340 PLC as Process Control PLC and Quantum PLC as safety Control PLC. An expansion in system is required due to addition of new Instruments in the field, toC.To aAccommodate new addition of instruments it is required to add new IO racks for both PCS and Safety PLC systems because there is no more space for new IOs in existing PLC racks. facility an expansion IO rack has to be installed that shall communicate with existing system.Keeping in view the space limitations at control room INTECH is providing a combined enclosure* for both PCS and safety PLCs. In addition of the enclosure INTECH will be providing a EWS and an OWS station also which will provide monitoring and control of system.INTECH is also responsible of integration of following 3rd party systems with SCADA system: VRU PLC Nitrogen Generator PLC Generator Control System Loading Controller Station SCOPE OF DOCUMENTThis document details the minimum hardware and software requirements for the design, procurement, implementation, documentation and testing of the PLC/HMI based system for expansion of Modicon ESD Safety and PCS system for MOL Bijel1..It will be used as a basis for the development and implementation work.. It covers the following aspects: System Aarchitecture PCS and ESD Logic Ddesign Ddetails HMI Screen List HMI Object Ffunctionality HMI Screen lList

Note: Combined Enclosure in this document will refer to INTECH provided control panel cabinet.

REFERENCE DOCUMENTS

Sr.Reference DocumentsRevisionDocument Number

1. Bijell-1B EWT Facility Upgrade Functional Requirements--

2. Flowline ESD Skid P&ID0064-16-02-1200

3. Slug Catcher V-100 P&ID0064-16-02-1201

4. Basket Strainers ST-100A/B P&ID0064-16-02-1201A

5. Flare Knockout Drum V-170 P&ID0064-16-02-1202

6. Flare Knockout Drum Recycle Pumps P-170A/B P&ID0064-16-02-1203

7. HP Flare Stack FS-810 P&ID0064-16-02-1204

8. Instrument Index with IO List020714002-3650-001

9. ESD IO Wiring00OV-141113-ESD-IO

10. PCS IO Wiring00OV-141113-PCS-IO

11. General Assembly Drawings00OV-141113-GA

12. AC and DC Power Distribution00OV-141113-PD

13. Control philosphy000714002-3620-003

14. System ArchitectureAOV-141113-SAR-001

Table 1: Reference Documents

ACRONYM USED IN THIS DOCUMENTAcronymWord/Phrase Represented by Acronym

AIAnalog Input

AOAnalog Output

DIDigital Input

DODigital Output

BOMBill of Materials

FATFactory Acceptance Test

FTFactory Talk

HHHigh High

HMIHuman Machine Interface

I/OInput / Output

LPLow Pressure

MCCMotor Control Center

PCSProcess Control System

PIDProportional Integral Derivative

PLCProgrammable Logic Controller

PVProcess Value

SDVShutdown Valve

SPSet point

Table 2: Acronym ListSYSTEM ARCHITECTURE

Figure 1: System Architecture

SCOPE OF WORKThe scope of work can be divided in two main areas: Hardware scope of supply Software scope of supplyHARDWARE SCOPE OF SUPPLYINTECH is providing a combined enclosure for both PCS and Safety systems due to space constraints. PLC racks in INTECH provided control panel cabinet dont include any PLC controller but only IO Cards and rack expansion modules.

Hardware Scope of supply can be divided as follow: Combined Enclosure for PCS and Safety Remote IO Racks Remote IO Drop Module for Quantum PLC (will be installed on existing Quantum PLC rack) Rack Expansion module for M340 PLC (will be installed on existing M340 PLC rack) Protocol Converters CAN to Modbus RTU for Generator Control System (will be installed in Generator Control System Cabinet) Modbus RTU to Modbus TCP the 3rd Party systems (will be installed in combined enclosure) Engineering and Operator Workstations UPS to provide backup power to workstations Armored Communication Cable for Serial communication of 3rd Party systems

INTECTH is supposed to supply remote IO racks for newly created facility for MOL Iraq.IO racks shall contain Schneider M340 and Quantum IO cards to accommodate newly created IOs.Intech is also supposed to provide platform for third party communications with new facility.SOFTWARE SCOPE OF SUPPLYThe software scope of supply includes the design, PLC hardware configuration, PLC and HMI software implementation, integration and testing.These modifications will include addition of new instruments logic and hardware configuration of remote IO racks to existing PLC applications for both Safety and PCS controllers. INTECH will only be performing addition of new logic; previous logic will not be modified or changed Since PLC application was previously developed in modular routine where multiple routines were created, INTECH will be following the same application structure to add necessary PLC logic. INTECH will perform PLC application additions in new routines which will have no impact on previous logic.

The software scope of supply includes the design, PLC hardware configuration, PLC and HMI software implementation, integration and testing. SSoftware design can be divided in three main areas: 1. HMI Software Design List of HMI Screens added to existing Application Existing HMI Software Environment Existing HMI System Configuration Guidelines Software Environment Settings HMI System Configuration Screen List 2. PLC Software Design Guidelines Existing PLC Software Environment Existing PLC Application Structure Addition of new IO Modules to the H/W configuration of Existing Applications Software Environment Settings. Application Structure. Addition of new routines in existing ApplicationController Tags 3. HMI Object Functionality Detailed functionality of each HMI Object used in new HMI screens as per existing HMI Application

PLC Object Functionality Detailed functionality of each PLC Object used in new PLC logic as per existing PLC Application

HMI SOFTWARE DESIGN GUIDELINESINTRODUCTIONThe HMI provides a monitoring and control window for both the Safety and Process systems. It will enable the operator to view the data being gathered by the PLCs and provide limited control. of the process. This section of the document defines the operational requirement and design basis followed as per existing application. for the project.SOFTWARE ENVIRONMENT VERSIONSETTINGSHMI Development Software Name & VersionVijeo Citect Scada

Firmware Version7.3

Table 3: HMI Software Environment SettingsHMI SYSTEM CONFIGURATIONResolution 640 x 480 800 x 600 1024 x 768 1152 x 864 1280 x 1024 1600 x 1200 Others _____________

Font Size Small Medium Large

Color Palette 256 32768 65536 True Color (16 bit) Others _____________

Screen Background ColorCyan

Table 4: HMI System Configuration

OPERATOR INTERACTIONOperators shall interact with new created facility for MOL bijell-1 through HMIs on Engineering work stations. Real time process control shall be provided through run time GraphicsHMI SCREENS LISTBased on P&IDs and RFQ provided by the customer, the following table shows the list of screens identified for Expansion of Modicon PCS and ESD PLC Bijel 1.

Sr.#P&ID/Screen Name

1Overview_3

2Overview_4

Table 5: HMI Screen List

HMI SCREEN The following are the static graphics screens developed for Expansion of Bijel1.

OVERVIEW_3

Figure 2: Overview_3 Screen

OVERVIEW_4

Figure 3: Overview_4 Screen

ALARM SUMMARYComment by Jawad Rasool: Please provide details of existing Alarm Summary here as reference.It should be noted that new created alarm summary shall be included in existing alarm summary graphic page to keep consistency with existing system.

Figure 4: Alarm Summary Screen

PLC SOFTWARE DESIGN GUIDELINES INTRODUCTIONNTECH received the existing Unity Pro PLC applications from client for both PCS and Safety systems. INTECH will be performing the desired additions to existing logic on both controllersThis section outlines the basis on which the new logic will be added to existing Controller Application will be modified. . It includes the structure and naming convention to be used for modifying the application. It will ensure that the program structure and tagging convention being used remains consistent throughout the application and previous settings has been followed. This document also describes the Object Oriented Approach used by INTECH for implementation of the Process Control requirements.

SOFTWARE ENVIRONMENT SETTINGSSoftware Environment

Operating SystemWindows 7

Controller Application Development SoftwareUnity Pro XLS 7.0

Process Controller TypeQuantum BMX P34 2020

ESD Controller TypeQuantum Safety CPU 140 651 60S

Process Application NamePLC501

ESD Application NamePLC500

Process Controller SlotExisting Rack 0, Slot 0

ESD Controller SlotExisting Rack 1, Slot 2

Programming LanguageLadder Logic

Table 6: PLC Software Environment Settings

APPLICATION STRUCTUREWe have received Unity Pro logic applications from client for both PCS and Safety systems. We will be adding our progam sections to existing logic applications.On the Unity Pro XLS 7.0 platform, the basic element of an application is a TASK. There are different types of task like MAST (Master Task) and FAST (Fast Task) which in turn comprise of different Sections and Sub-routines. We will only explain MAST and Sections topic will be only discussed here as thesewe are only being using thatused in existing and newour application. Application Structure for both PLCs is shown below:PROCESS PLC APPLICATION STRUCTURE

Figure : Process PLC Application Structure

ESD PLC APPLICATION STRUCTURE

Figure : ESD PLC Application Structure

REMOTE IO HARDWARE CONFIGURAIONHardware configuration for the Expansion racks of both Process and SAFETYESD systems are as follows:PROCESS PLCExpansion hardware configuration is shown at Rack 2 in figure below:

Figure : Process PLC Expansion Rack

AREARack NumberSlotModule

PROCESS PLC STATION20BMX DDI 3202K

PROCESS PLC STATION21BMX DRA 1605

PROCESS PLC STATION22BMX AMI 0810

PROCESS PLC STATION23BMX AMI 0810

PROCESS PLC STATION24BMX AMI 0810

PROCESS PLC STATION25BMX AMO 0410

Table 7: Process IO Rack Hardware Configuration

ESD PLCExpansion hardware configuration is shown at Rack 2 in figure below:

Figure : ESD PLC Expansion Rack

AREARack NumberSlotModule

ESD PLC STATION23140 SDI 953 00S

ESD PLC STATION24140 SDO 953 00S

ESD PLC STATION25140 SAI 940 00S

ESD PLC STATION26140 SAI 940 00S

Table 8: Process IO Rack Hardware Configuration

MAST (MASTER TASKS)The master task represents the main task of the application program. It is obligatory and created by default. The master task (MAST) is made up of sections and subroutines. Each section of the master task is programmed in the following languages: LD, FBD, IL, ST or SFC. You can choose the type of master task execution: Cyclic (default selection) Periodic (1 to 255 ms)The master task can be controlled by program, by bits and system words.SECTIONSComment by Jawad Rasool: Please highlight the new modifications.Sections are autonomous programming entities. The identification tags of the instruction lines, the contact networks, etc. are specific to each section (no program jump to another section is possible). These are programmed either in: Ladder language (LD) Functional block language (FBD) Structured Text (ST) Sequential Function Charting (SFC) on condition that the language is accepted in the task. The sections are linked to a task. The same section cannot belong simultaneously to several tasks. The following diagram shows a task structured into sections. The new sections added in existing logic are boxed in green.

Figure : Process PLC Sections Structure

Figure : ESD PLC Sections Structure

Comment by Jawad Rasool: Can we add something about Pump and Digital Input Object.PLC OBJECT FUNCTIONALITYINTRODUCTIONThis section briefly describes the functionality of different blocks like AI scaling block and PID block used in logic development.The functionality of each object is same as in existing logic. INTECH will be following the existing objects. ANALOG INPUT SCALING BLOCK This function block can be used to scale the value of an analog input channel. It carries out the following calculation:

Figure : AI Scaling Formula

The figure below shows Analog Input scaling block.

Figure : AI Scaling Block

The table below describes Input and Output elements of the block in above figure.

ELEMENTDATA TYPEDESCRIPTION

ENBOOLEnables the block

ININTNumerical variable to be scaled

IN_MAXINTUpper limit of the input scale

IN_MININTLower limit of the input scale

OUT_MAXREALLower limit of the output scale

OUT_MINREALUpper limit of output scale

CLIPBOOL"1": the value of the OUT output is limited by OUT_MIN and OUT_MAX.

ENOBOOLEnables Output for other blocks

OUTREALScaled output value

Table 9: AI Scaling Block IO Elements

PID CONTROLLER BLOCKThis function block produces a PID Controller. The function block has the following properties: Real PID controller with independent gain, ti, td setting Operating modes Manual, Halt, Automatic Bump less changeover between manual and automatic Manipulated variable limiting in automatic mode Separately enabled P, I and D componentThe figure below shows PID controller block:

Figure : PID Control Block

The table below describes Input elements of the PID Controller block.ELEMENTDATA TYPEDESCRIPTION

ENBOOLEnables the block

PVREALProcess Value

SPREALSetpoint

FFREALDisturbance input

RCPYREALCopy of the current manipulated variable

MAN_AUTOBOOLController operating mode: "1": Automatic mode "0": Manual mode

PARAPara_PIDFFParameter

TR_IREALInitialization Input

TR_SBOOLInitialization Command

OUTREALAbsolute Value

Table 10: PID Control Block Intput ElementThe table below describes Output elements of the PID Controller block.

ELEMENTDATA TYPEDESCRIPTION

ENOBOOLEnables Output for other blocks

OUT_DREALIncremental value output: Difference between the output of the current and previous cycle

MA_OBOOLCurrent operating mode of the function block: "1": Automatic operating mode "0": other operating mode (i.e. manual or tracking mode)

INFOInfo_PIDFFInformation

STATUSWORDStatus Word

OUTREALStatus word

Table 11: PID Control Block Output Element

PUMP OBJECTIn this expansion project there are two pumps P-170A/B. According to Control Philosophy Doc. No. 0714002-3620-003, these pumps must work in Duty/Standby Configuration. We have made the pump logic in accordance with existing pump modules. The salient features of new pumps logic are as follows: Start / Stop commands to pumps will come from LIT_1700 High/Low alarms or LSH_1701/LSL_1701 level switches. Duty / Standby mode for pumps will be selected from field via Digital Input HS_1700A / B. Pump will shutdown in case of emergency via ESD_1700A / B.CONTROLLER TAGSController tags apply to the entire controller, and can be used by all programs. In other words, the data in a controller tag is available to every task or program within the controller application. These tags can be seen as global variables.Controller Tags data type, description and address types are defined in sections below:PROCESS PLC NAMEADDRESS TYPEDATA TYPE

Analog InputInput WordInteger

Analog OutputOutput WordInteger

Digital Input Input BitBOOL/EBOOL

Digital OutputOutput BitBOOL/EBOOL

Table 12: Process Controller Tags

ESD PLCNAMEADDRESS TYPEDATA TYPE

Analog InputInput WordInteger

Analog OutputOutput WordInteger

Digital Input Input WordInteger

Digital OutputOutput WordInteger

Table 13: ESD Controller Tags

hmi OBJECT FUNCTIONALITYINTRODUCTIONHMI objects will be used to visualize the functionality of the system, different animations are used to represent the multiple states of an object.HMI applications will be developed in a modular Object Oriented Approach. Typical functionalities have been identified, and the corresponding objects have been defined. This approach will facilitate the development as well as further diagnostics and troubleshooting activities. NFurthermore newly created objects not only share consistency with existing system but also functionality to keep system convenient to operators during runtime operationsOBJECT TYPESThis section describes the functionality of such objects.Sr.Object Descriptive NameBrief Description

1. Discrete InputObject for Discrete Input

2. Discrete outputsObject for Discrete outputs

3. Analog InputObject for Analog Input

4. SDV ValvesObject for SDV value accompanying SOV

5. PIDPCVComment by Jawad Rasool: Please use Control Valve as we dont have specific object for PID.Object for PID

6. PumpObject for Pump with Run Status & Start/Stop Commands

Table 14: HMI Object details

ANALOG INPUTOFIT-0013 OBJECT OVERVIEWComment by Jawad Rasool: Please make it generic. No need to mention any object name.Use consistent formatting in this section. FIT-0013 Object has been implemented in Modicon Unity XLS -programming software for Schneider and its HMI interface has been developed in Vijeo Citect Scada V7.3. This object consists of one Analog input only.The raw input from transmitter (which is PV Raw) is scaled in the PLC to calculate process value in engineering units though Created analog object only provides provision of monitoring process analog values.Scaling of PCS analog objects shall be done in Vijeo Citect Scada environment while ESD Analog values shall be scaled in controller to keep consistency with existing HMI/Controller configuration.VARIABLE NAMING NOMENCLATUREP&IDs Tag nameController Object NameHMI Object Name

FIT_0013Process_FIT_0013_ScaledFT_0013Pipeline Pump PBE-310 Suction PressureComment by Jawad Rasool: Use the name used on HMI for display purpose

Table 15: Variable Naming Nomenclature

Figure 14: Controller Tag Name Engineering Units

Device Tag Name

Process Value

Figure : Graphical representation(s) of analog Object

ALARM MANAGEMENT CYCLEComment by Jawad Rasool: If there is no Alarm then please delete the section or explain there is no alarmAnalog object relative tags in case of alarms shall be displayed in alarm summary already built. Since existing system only provides analog objects for monitoring process in runtime environment.

PID CONTROL VALVEPIDPIT-0010 - OBJECT OVERVIEWComment by Jawad Rasool: Same as aboveLIC-0011 object has been implemented in Unity Xls - programming software for Modicon Schneider and its HMI interface has been developed in Vijeo Citect Scada. This object consists of one Analog input and one Analog output only.LIC-0011 Object has analog functionality.Set point can be configured from the Object faceplate.PID can be put in Auto/Manual mode from Object.In Manual mode, PID output can be set manually.Detailed monitoring and control over PID settings are also configurable from HMI.The percentage opening of the regulatory valve is also represented below the valve body.GRAPHICAL REPRESENTATIONComment by Jawad Rasool: Highlight the section of PID in the graphic or provide a scenario without tank Figure : Graphical Representation of PIT-0010 Controlling PID

CONTROLLER IO & VARIABLE NOMENCLATUREP&ID IO Tag NameController/HMI Object NameDescription

PICLIC-00101Process_PITLIC_0010_SCALEDSlug Catcher Pressure controller Level Controller.

Table 16: I/O Variable Name

Figure : Controller Tag NamePCV ANIMATION DETAILSComment by Jawad Rasool: This is for Control ValveThe animation details for the Object PIT-0010 are as follows:

Device StateAlarm text indication

Normal OperationGreen

SOV Off stateRed indication

SOV On stateGreen Indication

PCV stateGreen when Value lies