Smartlogic

Menu

תגית: validation process

ולידציה – SSO for Turbine Air Inlet Cooling

Posted on by אביב צברי

   Schedule of System Operation – SSO

Turbine Air Inlet Cooling

This article is an elaborated example of a schedule of system operaton – sso we did for one of our clients. Of course the actual documents contain all the operational and alarm parameters  

                Scope

This Schedule of System Operation (SSO) covers the required technical data and operation logic regarding the components of Turbine Air Inlet Cooling system, according to the Smartlogic's requirements and the client specifications

              System General Description

 :Turbine Air Inlet Cooling system contains two cold liquid circuits

Primary – 4 chillers and their respective primary pumps

Secondary – 2 pumps for each turbine inlet air cooling coil, 2 pumps for Cogen1, 2 pumps for Cogen2, and 2 pumps for the electric generator cooling (one operating and the other in standby

                Applicable Documents

User Requirements Specification (URS) for Monitoring and Alarm System

Parameters List

            Operational Parameters List

                          Alarm Parameters List

                              Operation Logic

            :Start Conditions of Chiller

COND_SYS_RDY Signal is on
Relevant pumps are waiting for our commands, including their corresponding valves

OIL_PUMP_OK Signal is on

READY Signal from MCC (C-025/RD) is on

READY Signal from Chiller (JM-025/RD) is on

ZS (Freeze protector) Signal is off, not indicating alarm

           : Running Logic for Chiller

Start corresponding Reg_valve (condenser regulate valve) on 100% and wait until valve feedback indicating >= 95%

Delay REG_VALVE_DLY_SP – 10 second

:If number of operating chillers <= 2

Send signal to  Start_cond_pump_1 – Start one Condense Pump

:If number of operating chillers > 2

Send signal to  Start_cond_pump2 – Start Two Condense Pumps

Verify from via communication that relevant cond_pump has

Delay 20 seconds

Perform PID on PDIT using Reg_valve according to relevant PDT-081-4_SP DeltaP SP
(in manual and/or auto mode)

Start CHW_Pump, chilled water pump

Delay 30 second

Verify relevant FS (flow) Signal is on for 20 seconds

Start Chiller

           : Stop operation for each Chiller

Delay 2 minutes , safety in case user changed the operation order of chillers from HMI

Stop Chiller

Wait for signal off from motor MCC feedback

Delay 60 Sec

If current chiller is 3rd , Send signal to stop Cond_pump_2

If current chiller is 1st , Send signal to stop Cond_pump_1

Close Reg_valve, condenser regulate valve

Delay 30 Sec

Stop CHW_Pump, chilled water pump
Interlock: in any case, CHW_Pump will continue operating as long as the corresponding chiller is operating

            Consumers Pump activation

User can always choose primary/secondary pump

If demand cooling for cogen1/2 via .DI 20 for cogen 1, DI 21 for cogen 2

For first activation: Check TT-087 (supply water) is below SP +1

:Perform PID control with relevant Cogen-TT
For Cogen-1 TE-315-022, for Cogen-2 TE-316-093
according to TT_315_022_SP / TT_316_093_SP using cogen-1/2 primary pump

If PID control loop reaches >= START_HZ_SP activate secondary pump and Continue PID control loop with both primary and secondary pumps

If both primary and secondary pumps at work and PID control loop reaches <= STOP_HZ_SP deactivate secondary pump and Continue PID control loop with primary pump only

If outlet air from cogen 1 or 2 below setpoint -2°C and the pump speed in minimum for 3 minute, stop the cogen pump

When the outlet air is above set point +1°C for 1 minute start the pump

*Generator equipment is not connected to the our PLC

           :Consumers Pumps activation for generator

If number of operating chillers <= 2 then activate first pump

If number of operating chillers > 2 then activate second pump

Stop pumps using reverse order

            :Temperature control for generator valves

Perform PID control with TT-090 according to SP using TV-088, If 316-J-21A operates

Perform PID control with TT-090 according to SP using TV-089, If 316-J-21B operate

           :Start Conditions of Chiller sequence

Demand Cooling at least from one of Cogen-1 / Cogen-2 / Generator. slot 4 DI-19-20-21

            :Chiller sequence run-up

Start first chiller according ‎6

The chilled water pump in the first chiller will start all the time even if we are not receive "chiller ready to start", we do need to receive "MCC ready" and do not receive "chiller shut down" . this function are necessary when the chiller stop in" low water temperature"

Delay Run-up Start_Chiller_DelaySP delay – 10 minutes

According to demand, start next chiller

:Perform sequence control using the maximum calculated value from
:{Flow measurement} calculation and {Temp measurement} calculation

:By flow measurement

Chiller #2 operates when total flow is > CH2_FLOW_SP + CH_FLOW_OFFSET_ SP

Chiller #3 operates when total flow is > CH3_FLOW_SP + CH_FLOW_OFFSET_ SP

Chiller #4 operates when total flow is > CH4_FLOW_SP + CH_FLOW_OFFSET_ SP

Chiller #2 stops when total flow is <= CH2_FLOW_SP – CH_FLOW_OFFSET_ SP

Chiller #3 stops when total flow is <= CH3_FLOW_SP – CH_FLOW_OFFSET_ SP

Chiller #4 stops when total flow is <= CH4_FLOW_SP – CH_FLOW_OFFSET_ SP

Total flow = FM1 + FM2 + GenFM

Here are some examples of the PLCs used by Smartlogic: 6XV1830-0EH10, 6ES7131-4BF00*0AA0, 6ES7193-4CA40-0AA0, 6ES7134-4GD00-0AB0, 6ES7193-4CA40-0AA0, 6ES7138-4CA01-0AA0, 6ES7193-4CC20-0AA0, 6ES7590-1AB60-0AA0, 6ES7511-1AK00-0AB0, 6ES7954-8LP01-0AA0, 6ES7155-6AU00-0BN0, 1746-NO4V, 1769-L16ER-BB1B

 

ולידציה – FSD – System Functions and Facilities

Posted on by אביב צברי

ולידציה – FDS – System Functions and Facilities

 This article was written by Iian Shaya, validation,automation and control expert

.The Function Design Specification (FDS) is part of the validation documentation. In this article I will continue to elaborate the  parts of the FSD of system function and the system facilities

Modes of Operation

This section details all modes of operation for the system, including

Automatic/Manual

Start-up/Shutdown

Overrides

Emergency Shutdown

System Failure and Recovery

Functional Operation

This section divides each of the sequential functions into logical areas (determined by the process), and provide complete description of each function, including

Normal Control Functions – such as normal sequencing, control, etc

Interlocks – details of all interlocks within the function

Alarms – lists of all associated alarms and actions for recovery

Operator Requirements

This section describes the interface between the operator and the detailed function. It is probably the most important to the user during the design phase, as it fully details all the functions to be supplied by the system in order to meet the user's requirements. It must be written clearly and concisely, so that operators and users without technical background can visualize the system to be supplied. Inputs from the user should be clearly detailed so that the operational requirements can be determined

Human/Machine Interface – HMI

This section describes in detail all points of operation, local terminals, remote terminal, message displays, pushbutton stations, etc

Where computerized interfaces are used, such as SCADA or HMI, a list of the screens and the proposed content should be included

Dynamic Attributes – dynamic color changes for status

Display Values – Values to be displayed on screen and resolution- No. of decimal places

Input Devices – Operator interaction devices, mouse, keyboard, touch screen, etc

Alarm and Event Displays

Security – Password Access

System Data

All the data gathered, generated or calculated by the system should be detailed. The detailed data should include

Type

Range

Accuracy/Resolution

Scaling

All the data to be stored should be detailed. This includes historical trend data, alarms and events, taking into consideration the following

Location of data to be stored – fixed disk, floppy disk, etc

Retention period – length of time for the data to be maintained

Data Archive – procedures for backup to removable medium

Data Export – export facilities to other formats, such as Excel, Access, Lotus, etc

System interfaces

This section provides complete details of all inputs and outputs from the control system. When separate I/O schedules are generated, these documents must be referenced in the FDS, or else, the complete schedules must be included in the FDS appendix

For digital and analog I/O, this section should provide details of voltage, current, etc., being specific where interfacing to 3rd party equipment. The signal states should be included as follows

Digital inputs – two states

False or Off

True or On

Analog inputs – detailed range

Detailed communication interfaces between systems should include protocols and formats, and also provide complete details of data to be transferred, paying special attention to 3rd party devices

 This article was written by Iian Shaya, validation,automation and control expert

אילן שעיה ilan Shaya

ולידציה – FRS – Regulatory & HMI Requirements

Posted on by אביב צברי

ולידציה – FRS – Regulatory & HMI Requirements

 This article was written by Iian Shaya, validation,automation and control expert

Regulatory Requirements

These requirements cover all the FDA specifications regarding the system compliance with the 21 CFR Part 11 definitions, and also with usual validation documentation demands

Method to provide a computerized system that complies with 21 CFR Part 11 definitions, such as the system access control by the user's managing personnel, who shall be responsible for the content of the electronic records (ERs) contained in the system

Method to restrict logical access to the system according to specified authorization levels

Method to restrict logical access to the system only to specific user ID and password

Method to provide system capability to record the values, alarms, user changes and any other events, and provide readable forms and reports of ER data

Method to allow storage of historical events, current alarms and historical alarms data records on the computerized system database

Capability of data display to the user in "view only" mode, so the user cannot alter or delete data/records

Provision of user's capability to backup data daily, weekly and monthly, according to his procedures, to ensure protection of the records and to enable their accurate and ready retrieval throughout the records retention period

Provision by the supplier of a project plan and quality assurance (QA) processes during development and the testing stages as part of his QA systems

Provision by the supplier of the following documents

Functional Requirements Specification – FRS

Functional Design Specification- FDS

IO List

Schedule of System Operation – SSO

Installation Qualification (IQ) protocol

Operation Qualification (OQ) protocol

Performance Qualification (PQ) protocol

HMI Requirements

These requirements are intended to provide the URS demands from the HMI screens, regarding proper graphic design and functionality for controlling and monitoring the system, as specified in customer's contract with the supplier. The HMI screens provided usually are of the following types

Main Screen

Synoptic screens for displaying online values and status

Parameters screens for displaying temperature, humidity and pressure parameters values

Data logging and storage of historical trends, alarms and events

Tabular screens for displaying alarms

Graphical screens for displaying trends

 This article was written by Iian Shaya, validation,automation and control expert

ולידציה – FRS Contents

Posted on by אביב צברי

ולידציה -FRS Contents

 This article was written by Iian Shaya, validation,automation and control expert

The FRS presents functional requirements for installing and operating a monitoring and control system, in response to and compliance with the user's requirements

For example, the FRS may propose to fulfill the URS requirements using a system that includes a PC with control capabilities using HMI screens, PLC, and varied environmental conditions sensors and control devices. The FRS may also propose a color-code display for ongoing environmental conditions, including indications of alarm conditions. An SMS or e-mail notification may be sent to specified personnel in case of specified alarm conditions.

The FRS requirements are organized accordingly with the same order and numbering of sections as the URS for clear correspondence. These requirements are divided into 4 categories- as the user's requirements

Installation Requirements

Operation Requirements

Regulation Requirements

HMI Requirements

Installation Requirements

These requirements cover all the issues regarding system installation to ensure its proper functionality and reliability. Examples of this type of requirements are

List and characteristics of specified hardware (HW) components capable of meeting the system functional requirements

Labeling and identification method for each HW component

List and characteristics of specified software (SW) programs installed on the system PC and the PLC, capable of performing the required operations

Definition of equipment to meet the storage capacity requirements

Definition of equipment and method for achieving the required connections to various types of sensors, communication units, temperature, humidity and pressure transmitters, illumination devices, etc

Definition of equipment and method for achieving the communication compatibility with equipment already installed at the user's facility without extra sensors

Operation Requirements

These requirements cover all the operations that the system must be capable of performing. Examples of this type of requirements are

Environmental conditions (such as pressure, temperature and humidity) to be monitored and controlled

Type of systems to be monitored and controlled, such as Heating, Ventilation and Air Conditioning (HVAC) system, types of sensors, etc

Definition of computerized system capabilities and starting conditions

Definition of system capabilities to recover from failures

List of internal tests to be performed regularly, and alarm indications to be issued in case of failure

Definition of current and historical alarms to be provided regarding all parameters in any case of deviation from the limits specified in the system

Definition of system real-time screens display capabilities

Provision of the following data and HMI displays

Synoptic screens for displaying online values and status

Data logging and storage of historical trends, events and alarms

Tabular screens for displaying events and alarms

Graphical screens for displaying trends

Display of the following information for each alarm

Status -new/acknowledged alarm

Time at which the alarm was activated

Parameter/Tag/Name of the module that activated the alarm

Alarm Description

Alarm Priority

Display of alarms to warn the user, collect alarm history, and enable the user to view current and historical alarms. The system alarms shall include

Component malfunction/failure

Irregularity in parameter reading – such as disconnection of communication lines

Parameters values exceeding the high/low parameter limits

Deviations of system operation from predefined parameters/operations

Method for providing capability to configure the graphs parameters according to

Date and time

Measured parameters

Predefined number of displayed parameters

Definition of trend graphs with maximum and minimum allowed limits of the monitored parameters

Definition of logging interval defined by the user and configured by the supplier

Method for providing capability of authorized user's personnel to define low and high limits and delay time for each

alarm parameter

On FRS regulatory & HMI Requirements you can find out in our next article

 This article was written by Iian Shaya, validation,automation and control expert

אילן שעיה מרצה Ilan Shaya

ולידציה – URS and FRS Preparation Overview

Posted on by אביב צברי

ולידציה – URS and FRS Preparation Overview

 This article was written by Iian Shaya, validation,automation and control expert

User Requirements Specification (URS) and Functional Requirements Specification (FRS) are the first and starting points of a validation process and a validation documentation file

  – The validation process must comply with regulations issued by the United States Food and Drug Administration FDA

:The FDA regulations that are most relevant to the validation process are

Good Manufacturing Practice  – GMP.

Current Good Manufacturing Practice – cGMP

Good Automated Manufacturing Practice – GAMP

The validation process includes design, installation and operation of a monitoring and control system for a production facility, as well as planning and execution of test procedures, to verify that a monitoring and control system meets the FDA standards

Validation documentation is part of the validation process that includes written and/or electronic records regarding the installation and operation of the monitoring and control system, and the corresponding test procedures for this system

Electronic records are often required to fulfill regulations set by the FDA. These regulations regard the scope and application of Part 11 of Title 21 of the Code of Federal Regulations; Electronic Records; Electronic Signatures (21 CFR Part 11). Electronic Records may contain any combination of text, graphics, audio, pictures, or other information represented in electronic form, which are created, modified, maintained, archived, retrieved or distributed by a computer system

Electronic Signatures may contain computer data compilation of any symbol or series of symbols executed, adopted or authorized by an individual to be legally binding equivalent of the individual's handwritten signature

Electronic records and signatures are generally used in Closed Systems, in which the system access is controlled by personnel responsible for the contents of the system electronic records

The responsibility for writing and approving the URS and FRS is shared in practice by the user, who operates the production facility, and the supplier or vendor, who provides the monitoring and control system for ensuring the proper operation of the production facility. Usually, the URS is written by the user and the FRS by the supplier

:Note

The final contents of the URS and FRS are tailored according to the type and size of the system under validation. Since the URS and FRS regarded herein are generic, they include requirements that may not be necessary in small or simple systems

 This article was written by Iian Shaya, validation,automation and control expert