Kamis, 29 Juli 2010

BUILDING AUTOMATION AND SYSTEMS


INTEGRATION ANALYST

DEFINITION


Technical specialist with responsibility for the operation, maintenance, and future expansion of all hardware and software for large, complex Campus Facility Automation Systems at 5 separate campuses. Building Automation Systems include: Energy Management Systems (Honeywell, etc.); HVAC Direct Digital Controls systems, HVAC Pneumatic Controls Systems; Fire Alarm Systems (Simplex, Ademco, etc.); Intrusion Alarm Systems (ADT, Silent Knight, etc.); Card Access Systems (Locknetics); and Lighting Control Systems. The incumbent shall work under the direction of the Director of Utility and Energy Resources and be capable of performing all duties with minimal technical supervision.

TYPICAL DUTIES

General
Assess, plan, budget and manage daily operations and future expansion of the Campus Facility Automation Systems. Technical advisor and resource for College and District staff that are maintainers and end-users of the Campus Facility Automation Systems.

Building Automation System Support

  • Troubleshoot system problems to provide continued operation.

  • Optimize DDC system performance through analysis of trend data.

  • Develop and implement standard specifications, programming standards, standard sequences of operation, and commissioning procedures.

  • Develop and implement plan for re-commissioning existing building systems to achieve optimum energy efficiency.

  • Develop and implement plan for re-commissioning, maintenance and calibration of pneumatic control systems.

  • Develop and implement documentation standards for hardware and cabling.

Programming

  • Design, code, test, and de-bug device-level, microprocessor-based digital controllers

  • Design, code, test, and de-bug network supervisory controllers

  • Design, code, test, and de-bug workstation-level Human-Machine Interfaces (HMI)

  • Design, code, test, and de-bug Graphical User Interfaces (GUI)

  • Design, code, test, and de-bug Internet Interfaces

  • Design, code, test, and de-bug supervisory-level energy conservation strategies

  • Energy management system I/O database development and maintenance

  • Energy management system trend database development and maintenance

  • Develop and implement documentation standards for software

  • Maintain code, code archives, code documentation and backups

Network Support

  • Large-scale control network optimization

  • Install and maintain network components in the organization-wide network

  • Maintain network availability, performance and security

  • Work with campus and district technicians, specialists and analysts to implement and maintain needed connectivity

  • Resolve network connectivity problems

Systems Integration

  • Integrating Building Automation controls networks to HMI workstations via LRCCD WAN.

  • Integrating Energy Management Systems networks to HMI workstations via LRCCD WAN

  • Integrating Fire Alarm networks to HMI workstations via LRCCD WAN.

  • Integrating Intrusion Alarm networks to HMI workstations via LRCCD WAN.

  • Integrating Card Access networks to HMI workstations via LRCCD WAN.

Project Management

  • Project Manager for Facilities projects by contractors to expand Campus Facility Automation System.

  • Define scope of work and specifications, design and produce working drawings, develop budgets, and schedules.

  • Review all hardware designs and submittals, and software programming to determine compliance with specifications.

  • Primary contact for consultants during project design and primary contact for contractors during project execution.

  • Inspect project during installation and act as Commissioning Agent at project completion.

QUALIFICATIONS

EXPERIENCE AND EDUCATION

An Associate degree in computer science or equivalent (or completion of a certificate program equivalent to an Associate degree in computer science) AND two years in class of IT Assistant II with increasingly more responsible activities; OR An Associate degree in computer science or equivalent (or completion of a certificate program equivalent to an Associate degree in computer science) AND five years experience directly related to job duties; OR Combination of training and/or experience totaling eight years that is likely to have provided the required level of knowledge and abilities.

SPECIAL REQUIREMENT
Must possess and maintain a valid California Drivers license. Willingness to monitor projects on other than regular working hours. Pass pre-employment physical and Department of Justice fingerprint/ background investigation.


KNOWLEDGE AND ABILITIES

  • Thorough knowledge of hardware, software, system architecture, network topology, operating systems, programming, telecommunications equipment and protocols of large-scale, multi-campus building automation systems.
  • Energy Management System I/O database structure
  • Energy Management System trend database structure
  • Human-Machine Interfaces (HMI) for building automation systems
  • Graphical User Interfaces (GUI) for building automation systems
  • Internet Interfaces for building automation systems
  • Line Programming, Block Programming and Relay Ladder Logic
  • Internal structure and function of Windows 98, Windows 2000, Windows NT 4.0 server and Windows NT 4.0 workstation operating systems
  • LonWorks, BACnet, Internet enabled systems, and other emerging control system protocols and technologies.
  • Networking topology, protocols and routing including OSI seven-layer model
  • Third party HMI's (CADgraphics, WonderWare , Intellution, etc.)
  • Trend Database structure and trend data analysis techniques
  • PC based instrumentation and data logging devices
  • Application and specification of stand-alone instrumentation, sensors and transmitters
  • Project management software (Microsoft Project)
  • Effective leadership and project management practices and procedures
  • Industry standards for documentation of hardware and cabling
  • HVAC mechanical systems and equipment
  • HVAC DDC controls systems
  • Pneumatic Controls Systems
  • Uniform Building Code    
  • Uniform Mechanical Code
  • National Electric Code
  • Energy conservation strategies for HVAC mechanical equipment
  • Watt Hour meters and energy demand limiting strategies
  • Commissioning procedures for HVAC mechanical equipment
  • Fire Alarm Systems (Simplex, Ademco, etc.)
  • Intrusion Alarm Systems (ADT, Silent Knight, etc.)
  • Card Access Systems (Locknetics)
  • Lighting Control Systems.
  • CAD/reprographics (AutoCAD)
  • Building energy audits
  • Policies and procedures for execution of controls contracts
  • Knowledge of major DDC systems on the market.
  • Must be able to develop and diagnose control drawings and software.
  • Must be able to read and interpret HVAC drawings, control schematics, blueprints, and other construction documents and specifications.
  • Must be competent with standard office software such as Word and Excel.
  • Must be able to perform emergency, planned and preventative maintenance on all control related equipment.
  • Must be able to assume work duties normally completed by control contractors including but not limited to repair, replacement and emergency service of control devices. Control devices include but are not limited to Operator Work Stations, Interface Cards, Controllers, Actuators, Temperature Sensors, Pressure Sensors, and Network Interface Devices. .
  • Must be able to perform corrective measures to resolve urgent building operational issues.
  • Must be competent with tools and instruments used for installing and trouble shooting controls systems such as multimeters, amp meters, etc.
  • Must be able to provide training to other maintenance personnel for the proper ongoing scheduling, operation and continuous improvement of District automation systems.
  • Must be self reliant and able take on diverse responsibilities to ensure quality work.
  • Must be able to master specialty software specific to Honeywell or other vendors used by the District.
  • Must have excellent interpersonal skills and the ability to address contentious technical issues in an expedient and professional manner.
  • Must be able to clearly communicate requirements of control systems.
  • Must have ability to professionally prepare required written documents such as letters, requests for proposals and other job related matters.
  • Written and oral communications must be at a level to insure successful job performance. Must interact with diverse constituency having varying levels of technical and practical expertise.
  • Must have ability to prioritize in scheduling of competing job requirements.
  • Must be able to work with planners, maintenance personnel, consultants, contractors, and inspectors on multiple projects.

Physical and Environmental Factors: Ability to move about freely at construction sites; climb ladders; maneuver through tight and cramped spaces (i.e. trenches, crawl spaces, electrical and mechanical vaults, etc.). Exposure to safety hazards routinely associated with construction sites and maintenance spaces.










Rabu, 28 Juli 2010

Prefunctional Checklist


Project ____________________________________

PC-___    BUILDING AUTOMATION SYSTEM
__ Entire Building
__ Only Floor or Zone _______________________________
Associated checklists: ____________________________________________

1.    Submittal / Approvals
Submittal. The above equipment and systems integral to them are complete and ready for functional testing. The checklist items are complete and have been checked off only by parties having direct knowledge of the event, as marked below, respective to each responsible contractor. This prefunctional checklist is submitted for approval, subject to an attached list of outstanding items yet to be completed. A Statement of Correction will be submitted upon completion of any outstanding areas. None of the outstanding items preclude safe and reliable functional tests being performed.    ___ List attached.

____________________________ ______________ _________________________ _____________
Mechanical Contractor    Date    Controls Contractor    Date

____________________________ ______________ _________________________ _____________
Electrical Contractor    Date    Sheet Metal Contractor    Date

____________________________ ______________ _________________________ _____________
TAB Contractor    Date    General Contractor    Date

Prefunctional checklist items are to be completed as part of startup & initial checkout, preparatory to functional testing.
  • This checklist does not take the place of the manufacturer's recommended checkout and startup procedures or report.
  • Items that do not apply shall be noted with the reasons on this form (N/A = not applicable, BO = by others).
  • If this form is not used for documenting, one of similar rigor shall be used.
  • Contractors assigned responsibility for sections of the checklist shall be responsible to see that checklist items by their subcontractors are completed and checked off.

  • "Contr." column or abbreviations in brackets to the right of an item refer to the contractor responsible to verify completion of this item. A/E = architect/engineer, All = all contractors, CA = commissioning agent, CC = controls contractor, EC = electrical contractor, GC = general contractor, MC = mechanical contractor, SC = sheet metal contractor, TAB = test and balance contractor, ____ = _______________________________________.

    Approvals. This filled-out checklist has been reviewed. Its completion is approved with the exceptions noted below.
    ____________________________ ______________ _________________________ _____________
Commissioning Agent    Date    Owner's Representative    Date

2.    Documentation submitted and approved:    [ All ]

__ manufacturer's cut sheets                __ performance data
__ installation and checkout manual and plan        __ operating manual
__ full written sequences and list of all control strategies    __ completed control drawings
__ written copy of all control parameters, settings        __ design criteria
and setpoints                            __ full descriptive points list
__ O&M manual

  • Documentation complete as per contract documents    ___ YES ___ NO

    3.    Model verification        [ Contr = ________]
    As Specified 
    As Submitted 
    As Installed 
    Manufacturer 
    Model No. 
    Serial No. 
    n/a 
    n/a 
    CPU 
    Monitor 
    Other primary features: 


  • The equipment installed matches the specifications for given trade    ___ YES ___ NO
4.    Initial Setup and Checkout

4.1.    User Terminal Interface and Sub-Panel Checks
Check if Okay. Enter comment or note number if deficient.
Check 
Y / N 
Contr. 
General appearance good, no apparent damage 
Equipment labels affixed 
Layout and location of control panels matches drawings 
Areas or equipment panels serve clear in control drawings 
Wiring labeled inside panels (to controlled components) 
Controlled components labeled/tagged
BAS connection made to labeled terminal(s) as shown on drawings 
Shielded wiring used on electronic sensors 
110 volt AC power available to panel 
Psig compressed air available to panel (if applicable) 
Battery backup in place and operable 
Panels properly grounded 
Environmental conditions according to manufacturer's requirements 
Date and time correct 

  • The above setup and checkout was successfully completed for given trade    ___ YES ___ NO

    4.2.    Device and Point Checkout    [CC]
The following procedures are required to be performed and documented for each and every point in the control system. The following procedures are minimum requirements. The control contractor is encouraged to identify better and more comprehensive checkout procedures in their submitted plan. These procedures are not a substitute for the manufacturer's recommended start-up and checkout procedures, but are to be combined with them, as applicable. The documentation may be provided on the vendor's stock form, as long as all the information in the sample table below can be clearly documented on the form.
Similar checkout and calibration requirements are found on the equipment prefunctional checklists. Redundant documentation is not required. Cross reference, by name and form number, to other forms that contain documentation left blank on the current form.

Procedures
1. [Wire] Verify that the wiring is correct to each point.
2. [Actu] If the device is or has an actuator, verify full free movement through its full range.
3. [Addr] Verify that the software address is correct.
4. [Load] For devices with a controller, verify that current software program with proper setpoints has been downloaded.
5. [DevCal] Device stroke/range calibration. This applies to all controlled valves, dampers, fans, pumps, actuators, etc. Simulate maximum and minimum transmitter signal values and verify minimum and maximum controller output values and positively verify each and every control device minimum and maximum stroke and capacity range. Follow procedure 6.2 below.
6. [SensLoc] Verify that all sensor locations are appropriate and away from causes of erratic operation.
7. [SensCal] Sensor calibration. Calibrate or verify calibration of all sensors and thermostats, including temperature, pressure, flow, current, kW, rpm, Hertz, etc. Verify that the sensor readings in the control system are within the sensor accuracies specified in this section, using hand-held or other external measuring instruments. Follow procedure 6.1 below.
8. [OperCk] For controlled devices (dampers, valves, actuators, VAV boxes, etc.), after mechanical equipment control becomes operational, perform an operational test of each control loop. Follow procedure 6.2 below. Operational checks are preparatory to the later functional testing.
Other Abbreviations:
[BAS]    Building automation system or gage-read value.
[Instru]    Instrument (calibrated) read value.
[Ofset]    Offset programmed into the point to correct the calibration.

Controls Checkout Documentation Table
Field 
Hardware Checks 
SensCal
Final Check 
Point
ID
Object 
Device Type 
Wire 
Actu 
Addr 
Load 
Dev
Cal
Sens
Loc
BAS 
Instru 
Offset 
Oper
Ck
1 
2 
3 
4 
5 
6 
7 
7 
7 
8 
9 
AI-1 
ZN-T
(zone T)
PhJack 
Ö
na 
Ö
na 
na 
Ö
70.2F
71.4F 
+1.2F 
na 
3-2a 
RA-DPR (damper) 
PNEU 
Ö
Ö
Ö
na 
Ö
na 
na 
na 
na 
Ö

  • The initial setup and checkout has been successfully completed as described in Section 4.2 and Section 6 and documented on attached forms    ___ YES ___ NO

5.    Pneumatic System Pressure Test    [ ]
The entire pneumatic system servicing the controls shall be pressure tested as follows:
5.1.    Test the high pressure air piping at [ 150 psi ]________ . Maintain the pressure for 2 hours without loss of pressure. Correct and retest the system if any loss of pressure is indicated.        Pass? (Y/N)______
5.2.    Test the low pressure control tubing at [ 30 psi]_______ . Maintain pressure for 2 hours without pumping. If the pressure drops more than 1 psi, correct leak and retest until successful.     Pass? (Y/N)______


  • The pneumatic system pressure tests were successfully completed    ___ YES ___ NO

    6.    Sensor and Actuator Calibration    [ ]
All field-installed temperature, relative humidity, CO, CO2 and pressure sensors and gages, and all actuators (dampers and valves) shall be calibrated using the methods and tolerances given in the "Calibration and Leak-by Test Procedures" document. All test instruments shall have had a certified calibration within the last 12 months. Sensors installed in a packaged unit at the factory with calibration certification provided need not be field calibrated. All calibrations shall be fully documented, including initial and final readings, offsets etc., on prefunctional checklist or other suitable forms.



-- END OF CHECKLIST --

Formulas For Water Supply Problems

USE OF FORMULAS TO SOLVE PROBLEMS
This appendix gives formulas for use in solving water supply problems often found in the
field. Each formula is accompanied by a problem solved by using the formula.
CONVERSION OF VOLUME TO WEIGHT OF WATER
The formula and a problem for conversion of volume to weight of water are given below.
a. Formula.
Weight of water in pounds = Cubic feet of water x 62.4
b. Illustrative Problem. What is the weight of water in a full tank with a volume of
470 cubic feet?
Weight of water = Cubic feet x 62.4
= 470 x 62.4
= 29,328 pounds
CONVERSION OF VERTICAL FEET OF WATER TO POUNDS
PER SQUARE INCH
The formula and a problem for conversion of vertical feet of water to pounds per square
inch
a.
b.
are given below.
Formula.
Pounds per square inch = Vertical feet of water x 0.43
Illustrative Problem. What is the pressure in pounds per square inch at the bottom of
a storage tank with 25 vertical feet of water? -
Pounds per square inch = Vertical feet of water x 0.43
= 25x 0.43
= 10.75
CONVERSION OF POUNDS PER SQUARE INCH TO
VERTICAL FEET OF WATER
The formula and a problem for conversion of pounds per square inch to vertical feet of
water are given below.
a. Formula.
Vertical feet of water= Pounds per square inch = 2.3
b. Illustrative Problem. How many vertical feet of water are in a tank that is 45 feet
high? A pressure gauge at the bottom of the tank reads 9 pounds per square inch.
Vertical feet of water = Pounds per square inch x 2.3
= 9 x 2.3
= 20.7


formula and a problem for conversion of volume to gallons of water are given below.
a. Formula.
Gallons of water= Cubic feet of water x 7.5
b. Illustrative Problem. How many gallons of water are in a tank with 400 cubic feet of
water?
Gallons of water = Cubic feet of water x 7.5
= 400 x 7.5
= 3.000
CONVERSION OF GALLONS OF WATER TO CUBIC FEET
The formula and a problem for conversion of water to cubic feet are given below,
a. Formula
Cubic feet = Gallons of water
7.5
b. Illustrative Problem. How many cubic feet of tank space are needed to store
1,500 gallons of water?
Cubic feet = Gallons of water
7.5
= 1,500
7.5
= 200
CALCULATION OF VOLUME OF WATER TANKS
The formula and two problems for calculation of volume of water tanks are given below.
a. Formula for Rectangular Tank
V= L x W x H.
where V = Volume in cubic feet
L = Length in feet
W = Width in feet
H = Height in feet
b. Formula for Cylindrical Tank.
V= p  r2H
where V = Volume in cubic feet
p = 3.14 or 22/7, a constant
r = Radius (half of the diameter) of the tank
H = Height in feet


c. Illustrative Problems. What is the volume of a rectangular tank that is 10 feet long,
7 feet wide, and 4 feet high?
V = L x W x H
= 10O x 7 x 4
= 280 cubic feet
What is the volume of a cylindrical tank that has a radius of 4 feet and is 7 feet high?
V= p r2H
= 3.14 x 42 X 7
=3.14 x 16 x 7
= 351.68 cubic feet
CALCULATION OF QUANTITY OF WATER FLOWING IN A STREAM
The formula and a problem for calculation of quantity of water flowing in a stream are
given below.
a. Formula.
Q = 6.4 x A x V
where Q = Quantity of water in gallons per minute
6.4 = Constant.
There are 7.5 gallons of water per cubic foot. However, because of error in
stream measurement, 7.5 is reduced to 6.4.
V = Velocity of the stream in feet per minute.
This figure is obtained by noting the time it takes a twig or floating object
to travel a known distance.
A = Area of the stream in square feet.
This figure is obtained by multiplying the width of the stream by the
depth of the stream.
b. Illustrative Problem. A stream has an average depth of 2 feet and a width of 16 feet. A
twig floats 13.3 feet per minute. How many gallons per minute are flowing in the stream?
Q = 6.4 x A x V
= 6.4 x 2 x 16 x 13.3
= 2,732.8 gallons per minute
CALCULATION OF POUNDS OF CHLORINE
The formula and a problem for calculation of pounds of chlorine are given below.
a. Formula.
Pounds of chlorine = Gallons of water x 8.3 x parts per million
1,000,000


b. Illustrative Problem. If eight parts per million of chlorine are required for
3,000 gallons of water, how many pounds of chlorine will be needed?
Pounds of chlorine = Gallons of water x 8.3 x parts per million
1,000,000
= 3,000 x 8.3 x 8
1,000,000
= 0.1992
CALCULATION OF GALLONS OF WATER THAT CAN BE
TREATED WITH A GIVEN SUPPLY OF CHLORINE
The formula and a problem for calculation of’ gallons of water that can be treated with a
given supply of chlorine are given below.
a.
b.
five
Formula.
Gallons of water =
Illustrative Problem.
Pounds of chlorine x 1,000,000
8.3 x parts per million
There are 4.15 pounds of chlorine on hand. The operator is using
parts per million of chlorine as the average treatment dosage. How many gallons of
water can the operator treat before running out of chlorine?
Gallons of water = Pounds of chlorine x 1,000,000
8.3 x parts per million
= 4.15 x 1,000,000
8.3 x 5
= 100,000
CALCULATION OF THE PARTS PER MILLION OF
CHLORINE PRESENT IN A TREATMENT TANK
The formula and a problem for calculation of parts per million of chlorine present in a
treatment tank are given below.
a. Formula.
Parts per million = Pounds of chlorine x 1,000,000
Gallons of water x 8.3
b. Illustratiue Problem. If 16.6 pounds of chlorine are added to 20,000 gallons of water,
how many parts per million of chlorine are present?
Parts per million = Pounds of chlorine x 1,000,000
Gallons of water x 8.3
= 16.6 x 1,000,000
20,000 x 8.3
= 100
CONVERSION OF POUNDS OF CHLORINE TO
OUNCES OF CALCIUM HYPOCHLORITE
The formula and a problem for conversion of pounds of chlorine to ounces of calcium
hypochlorite are given below.



a. Formula.
Ounces of calcium hypochlorite = Pounds of chlorine x 22.9
b. Illustrative Problem. If 1/2 pound of chlorine will be needed to treat a water source,
how many ounces of calcium hypochlorite will be required?
Ounces of calcium hypochlorite = Pounds of chlorine x 22.9
= 0.5 x 22.9
= 11.45

Sabtu, 24 Juli 2010

PLC Control Systems


Industrial control systems



Industrial control system (ICS) is a general term that encompasses several types of control systems, including supervisory control and data acquisition (SCADA) systems, distributed control systems (DCS), and other smaller control system configurations such as skid-mounted programmable logic controllers (PLC) often found in the industrial sectors and critical infrastructures. ICSs are typically used in industries such as electrical, water, oil and gas, data. Based on information received from remote stations, automated or operator-driven supervisory commands can be pushed to remote station control devices, which are often referred to as field devices. Field devices control local operations such as opening and closing valves and breakers, collecting data from sensor systems, and monitoring the local environment for alarm conditions.

A historical perspective

Industrial control system technology has evolved over the past three to four decades. DCS systems generally refer to the particular functional distributed control system design that exist in industrial process plants (e.g., oil and gas, refining, chemical, pharmaceutical, some food and beverage, water and wastewater, pulp and paper, utility power, mining, metals). The DCS concept came about from a need to gather data and control the systems on a large campus in real time on high-bandwidth, low-latency data networks. It is common for loop controls to extend all the way to the top level controllers in a DCS, as everything works in real time. These systems evolved from a need to extend pneumatic control systems beyond just a small cell area of a refinery. The PLC (programmable logic controller) evolved out of a need to replace racks of relays in ladder form. The latter were not particularly reliable, were difficult to rewire, and were difficult to diagnose. PLC control tends to be used in very regular, high-speed binary controls, such as controlling a high-speed printing press. Originally, PLC equipment did not have remote I/O racks, and many couldn't even perform more than rudimentary analog controls. SCADA's history is rooted in distribution applications, such as power, natural gas, and water pipelines, where there is a need to gather remote data through potentially unreliable or intermittent low-bandwidth/high-latency links. SCADA systems use open-loop control with sites that are widely separated geographically. A SCADA system uses RTUs (remote terminal units, also referred to as remote telemetry units) to send supervisory data back to a control center. Most RTU systems always did have some limited capacity to handle local controls while the master station is not available. However, over the years RTU systems have grown more and more capable of handling local controls. The boundaries between these system definitions are blurring as time goes on. The technical limits that drove the designs of these various systems are no longer as much of an issue. Many PLC platforms can now perform quite well as a small DCS, using remote I/O and analog control loops, and are able to communicate supervisory data. It is not uncommon to have telecommunications infrastructure that is so responsive and reliable that some SCADA systems actually manage closed loop control over long distances. With the increasing speed of today's processors, many DCS products have a full line of PLC-like subsystems that weren't offered when they were initially developed. This has led to the concept of a PAC (programmable automation controller or process automation controller). It is an amalgamation of these three concepts. Time and the market will determine whether this can simplify some of the terminology and confusion that surrounds these concepts today.

DCSs

DCSs are used to control industrial processes such as electric power generation, oil and gas refineries, water and wastewater treatment, and chemical, food, and automotive production. DCSs are integrated as a control architecture containing a supervisory level of control overseeing multiple, integrated sub-systems that are responsible for controlling the details of a localized process. Product and process control are usually achieved by deploying feed back or feed forward control loops whereby key product and/or process conditions are automatically maintained around a desired set point. To accomplish the desired product and/or process tolerance around a specified set point, specific programmable controllers are used ONLY.

PLCs

PLCs provide boolean logic operations, timers, and (in some models) continuous control. The proportional, integral, and/or differential gains of the PLC continuous control feature may be tuned to provide the desired tolerance as well as the rate of self-correction during process upsets. DCSs are used extensively in process-based industries. PLCs are computer-based solid-state devices that control industrial equipment and processes. While PLCs can control system components used throughout SCADA and DCS systems, they are often the primary components in smaller control system configurations used to provide regulatory control of discrete processes such as automobile assembly lines and power plant soot blower controls. PLCs are used extensively in almost all industrial processes.

Development

Early PLCs were designed to replace relay logic systems. These PLCs were programmed in "ladder logic", which strongly resembles a schematic diagram of relay logic. This program notation was chosen to reduce training demands for the existing technicians. Other early PLCs used a form of instruction list programming, based on a stack-based logic solver. Modern PLCs can be programmed in a variety of ways, from ladder logic to more traditional programming languages such as BASIC and C. Another method is State Logic, a very high-level programming language designed to program PLCs based on state transition diagrams.

Programming

Early PLCs, up to the mid-1980s, were programmed using proprietary programming panels or special-purpose programming terminals, which often had dedicated function keys representing the various logical elements of PLC programs. Programs were stored on cassette tape cartridges. Facilities for printing and documentation were very minimal due to lack of memory capacity. The very oldest PLCs used non-volatile magnetic core memory.


Functionality

The functionality of the PLC has evolved over the years to include sequential relay control, motion control, process control, distributed control systems and networking. The data handling, storage, processing power and communication capabilities of some modern PLCs are approximately equivalent to desktop computers. PLC-like programming combined with remote I/O hardware, allow a general-purpose desktop computer to overlap some PLCs in certain applications. The main difference from other computers is that PLCs are armored for severe conditions (such as dust, moisture, heat, cold) and have the facility for extensive input/output (I/O) arrangements. These connect the PLC to sensors and actuators. PLCs read limit switches, analog process variables (such as temperature and pressure), and the positions of complex positioning systems. Some use machine vision. On the actuator side, PLCs operate electric motors, pneumatic or hydraulic cylinders, magnetic relays, solenoids, or analog outputs. The input/output arrangements may be built into a simple PLC, or the PLC may have external I/O modules attached to a computer network that plugs into the PLC.

System scale

A small PLC will have a fixed number of connections built in for inputs and outputs. Typically, expansions are available if the base model has insufficient I/O. Modular PLCs have a chassis (also called a rack) into which are placed modules with different functions. The processor and selection of I/O modules is customised for the particular application. Several racks can be administered by a single processor, and may have thousands of inputs and outputs. A special high speed serial I/O link is used so that racks can be distributed away from the processor, reducing the wiring costs for large plants.

User interface

PLCs may need to interact with people for the purpose of configuration, alarm reporting or everyday control. A Human-Machine Interface (HMI) is employed for this purpose. HMIs are also referred to as MMIs (Man Machine Interface) and GUI (Graphical User Interface). A simple system may use buttons and lights to interact with the user. Text displays are available as well as graphical touch screens. More complex systems use a programming and monitoring software installed on a computer, with the PLC connected via a communication interface. PLC programs are typically written in a special application on a personal computer, then downloaded by a direct-connection cable or over a network to the PLC. The program is stored in the PLC either in battery-backed-up RAM or some other non-volatile flash memory. Often, a single PLC can be programmed to replace thousands of relays. Under the IEC 61131-3 standard, PLCs can be programmed using standards-based programming languages. A graphical programming notation called Sequential Function Charts is available on certain programmable controllers. Initially most PLC's utilized Ladder Logic Diagram Programming, a model which emulated electromechanical control panel devices (such as the contact and coils of relays) which PLC's replaced. This model remains common today. IEC 61131-3 currently defines five programming languages for programmable control systems: FBD (Function block diagram), LD (Ladder diagram), ST (Structured text, similar to the Pascal programming language), IL (Instruction list, similar to assembly language) and SFC (Sequential function chart). These techniques emphasize logical organization of operations. While the fundamental concepts of PLC programming are common to all manufacturers, differences in I/O addressing, memory organization and instruction sets mean that PLC programs are never perfectly interchangeable between different makers. Even within the same product line of a single manufacturer, different models may not be directly compatible.

PLC compared with other control systems

PLCs are well-adapted to a range of automation tasks. These are typically industrial processes in manufacturing where the cost of developing and maintaining the automation system is high relative to the total cost of the automation, and where changes to the system would be expected during its operational life. PLCs contain input and output devices compatible with industrial pilot devices and controls; little electrical design is required, and the design problem centers on expressing the desired sequence of operations. PLC applications are typically highly customized systems so the cost of a packaged PLC is low compared to the cost of a specific custom-built controller design. On the other hand, in the case of mass-produced goods, customized control systems are economic due to the lower cost of the components, which can be optimally chosen instead of a "generic" solution, and where the non-recurring engineering charges are spread over thousands or millions of units. For high volume or very simple fixed automation tasks, different techniques are used. For example, a consumer dishwasher would be controlled by an electromechanical cam timer costing only a few dollars in production quantities. A microcontroller-based design would be appropriate where hundreds or thousands of units will be produced and so the development cost (design of power supplies, input/output hardware and necessary testing and certification) can be spread over many sales, and where the end-user would not need to alter the control. Automotive applications are an example; millions of units are built each year, and very few end-users alter the programming of these controllers. However, some specialty vehicles such as transit busses economically use PLCs instead of custom-designed controls, because the volumes are low and the development cost would be uneconomic. Very complex process control, such as used in the chemical industry, may require algorithms and performance beyond the capability of even high-performance PLCs. Very high-speed or precision controls may also require customized solutions; for example, aircraft flight controls. Programmable controllers are widely used in motion control, positioning control and torque control. Some manufacturers produce motion control units to be integrated with PLC so that G-code (involving a CNC machine) can be used to instruct machine movements. PLCs may include logic for single-variable feedback analog control loop, a "proportional, integral, derivative" or "PID controller." A PID loop could be used to control the temperature of a manufacturing process, for example. Historically PLCs were usually configured with only a few analog control loops; where processes required hundreds or thousands of loops, a distributed control system (DCS) would instead be used. As PLCs have become more powerful, the boundary between DCS and PLC applications has become less distinct. PLCs have similar functionality as Remote Terminal Units. An RTU, however, usually does not support control algorithms or control loops. As hardware rapidly becomes more powerful and cheaper, RTUs, PLCs and DCSs are increasingly beginning to overlap in responsibilities, and many vendors sell RTUs with PLC-like features and vice versa. The industry has standardized on the IEC 61131-3 functional block language for creating programs to run on RTUs and PLCs, although nearly all vendors also offer proprietary alternatives and associated development environments.

Digital and analog signals

Digital or discrete signals behave as binary switches, yielding simply an On or Off signal (1 or 0, True or False, respectively). Push buttons, limit switches, and photoelectric sensors are examples of devices providing a discrete signal. Discrete signals are sent using either voltage or current, where a specific range is designated as On and another as Off. For example, a PLC might use 24 V DC I/O, with values above 22 V DC representing On, values below 2VDC representing Off, and intermediate values undefined. Initially, PLCs had only discrete I/O. Analog signals are like volume controls, with a range of values between zero and full-scale. These are typically interpreted as integer values (counts) by the PLC, with various ranges of accuracy depending on the device and the number of bits available to store the data. As PLCs typically use 16-bit signed binary processors, the integer values are limited between -32,768 and +32,767. Pressure, temperature, flow, and weight are often represented by analog signals. Analog signals can use voltage or current with a magnitude proportional to the value of the process signal. For example, an analog 4-20 mA or 0 - 10 V input would be converted into an integer value of 0 - 32767.
Current inputs are less sensitive to electrical noise (i.e. from welders or electric motor starts) than voltage inputs.

Example :

As an example, say a facility needs to store water in a tank. The water is drawn from the tank by another system, as needed, and our example system must manage the water level in the tank. Using only digital signals, the PLC has two digital inputs from float switches (Low Level and High Level). When the water level is above the switch it closes a contact and passes a signal to an input. The PLC uses a digital output to open and close the inlet valve into the tank. When the water level drops enough so that the Low Level float switch is off (down), the PLC will open the valve to let more water in. Once the water level rises enough so that the High Level switch is on (up), the PLC will shut the inlet to stop the water from overflowing. This rung is an example of seal in logic. The output is sealed in until some condition breaks the circuit. An analog system might use a water pressure sensor or a load cell, and an adjustable (throttling) dripping out of the tank, the valve adjusts to slowly drip water back into the tank. In this system, to avoid 'flutter' adjustments that can wear out the valve, many PLCs incorporate "hysteresis" which essentially creates a "deadband" of activity. A technician adjusts this deadband so the valve moves only for a significant change in rate. This will in turn minimize the motion of the valve, and reduce its wear. A real system might combine both approaches, using float switches and simple valves to prevent spills, and a rate sensor and rate valve to optimize refill rates and prevent water hammer. Backup and maintenance methods can make a real system very complicated.

About PLC Programmer

I began working with PLC's at a major Japanese manufacturer of office equipment in based in Shropshire. There were many PLC's installed in various production lines, assembly equipment and robots. I installed Omron PLC's into a fleet of Automatically Guided Vehicles that I designed. The AGV's carried photocopiers around the plant, automatically transferring between one production line and the next. The PLC installed on board took care of managing the route to take and what to do when it got there. The AGV PLC communicated to the production line PLC's in order to instigate and manage transfer from the vehicle to the conveyor, the PLC also commanded the motion controllers which took care of the drive and differential steering. Another PLC was statically based and kept track of each AGV in the fleet, effectively managing the whole system. This was quite a first PLC project, eventually saving the company over £300,000 against a similar system bought from their usual supplier. After 10 years and studying ONC and HNC I moved on to a new position. PLC based Special purpose machinery for the rubber and plastic industries. Most equipment went into tyre (tire) plants all over the world. I designed PLC control systems , wrote the PLC and motion control software, installed it and commissioned in house and on site all over the world. This was an interesting position with the great opportunity to travel the world while still being involved with PLC control systems. Some small machines such as Tube splicers were installed with various brands of brick PLC as specified by the customer, the larger machines such as Tire builders generally had modular PLC's such as Allen Bradley SLC505. The fully automated bias cutter machines with PLC I/O counts of over 400 had modular PLC's with distributed I/O and SCADA systems. I installed and serviced PLC based tire machinery in the UK, USA, Canada, India, China, Indonesia and got to meet some great people. When I started my own PLC control company I continued to work all over the world but in many different industries, I have installed PLC control systems in Breweries, Power stations, Potato processing plants, steel plants, rubber plants, chemical processing plants and many more, all over the world. As with any technology PLC's progress and PLC's installed 10 or 15 years ago may not be operating your machinery to the optimum, with increased flexibility in good PLC systems such as integrated motion control, increases in quality and efficiency can be achieved. Replacing an outdated control system, PLC with an upto date PLC control system can yield significant benefits.

About PLC's
The main difference from other computers is that PLCs are armored for severe conditions (dust, moisture, heat, cold, etc) and have the facility for extensive input/output (I/O) arrangements. These connect the PLC to sensors and actuators. PLCs read limit switches, analog process variables (such as temperature and pressure), and the positions of complex positioning systems. Some even use machine vision. On the actuator side, PLCs operate electric motors, pneumatic or hydraulic cylinders, magnetic relays or solenoids, or analog outputs. The input/output arrangements may be built into a simple PLC, or the PLC may have external I/O modules attached to a computer network that plugs into the PLC. System scale A small PLC will have a fixed number of connections built in for inputs and outputs. Typically, expansions are available if the base model does not have enough I/O.Modular PLCs have a chassis (also called a rack) into which are placed modules with different functions. The processor and selection of I/O modules is customised for the particular application. Several racks can be administered by a single processor, and may have thousands of inputs and outputs. A special high speed serial I/O link is used so that racks can be distributed away from the processor, reducing the wiring costs for large plants.PLCs may need to interact with people for the purpose of configuration, alarm reporting or everyday controlA Human-Machine Interface (HMI) is employed for this purpose. HMIs are also referred to as MMIs (Man Machine Interface) and GUI (Graphical User Interface).A simple system may use buttons and lights to interact with the user. Text displays are available as well as graphical touch screens. More complex systems use a programming and monitoring software installed on a computer, with the PLC connected via a communication interface.CommunicationsPLCs have built in communications ports usually 9-Pin RS232, and optionally for RS485 and Ethernet. Modbus or DF1 is usually included as one of the communications protocols. Others' options include various fieldbuses such as DeviceNet or Profibus. Other communications protocols that may be used are listed in the List of automation protocols.Most modern PLCs can communicate over a network to some other system, such as a computer running a SCADA (Supervisory Control And Data Acquisition) system or web browser.PLCs used in larger I/O systems may have peer-to-peer (P2P) communication between processors. This allows separate parts of a complex process to have individual control while allowing the subsystems to co-ordinate over the communication link. These communication links are also often used for HMI (Human-Machine Interface) devices such as keypads or PC-type workstations. Some of today's PLCs can communicate over a wide range of media including RS-485, Coaxial, and even Ethernet for I/O control at network speeds up to 100 Mbit/s.PLC compared with other control systemsPLCs are well-adapted to a range of automation tasks. These are typically industrial processes in manufacturing where the cost of developing and maintaining the automation system is high relative to the total cost of the automation, and where changes to the system would be expected during its operational life. PLCs contain input and output devices compatible with industrial pilot devices and controls; little electrical design is required, and the design problem centers on expressing the desired sequence of operations in ladder logic (or function chart) notation. PLC applications are typically highly customized systems so the cost of a packaged PLC is low compared to the cost of a specific custom-built controller design. On the other hand, in the case of mass-produced goods, customized control systems are economic due to the lower cost of the components, which can be optimally chosen instead of a "generic" solution, and where the non-recurring engineering charges are spread over thousands or millions of units.For high volume or very simple fixed automation tasks, different techniques are used. For example, a consumer dishwasher would be controlled by an electromechanical cam timer costing only a few dollars in production quantities.A microcontroller-based design would be appropriate where hundreds or thousands of units will be produced and so the development cost (design of power supplies and input/output hardware) can be spread over many sales, and where the end-user would not need to alter the control. Automotive applications are an example; millions of units are built each year, and very few end-users alter the programming of these controllers. However, some specialty vehicles such as transit busses economically use PLCs instead of custom-designed controls, because the volumes are low and the development cost would be uneconomic.Very complex process control, such as used in the chemical industry, may require algorithms and performance beyond the capability of even high-performance PLCs. Very high-speed or precision controls may also require customized solutions; for example, aircraft flight controls.Programmable controllers are widely used in motion control, positioning control and torque control. Some manufacturers produce motion control units to be integrated with PLC so that G-code (involving a CNC machine) can be used to instruct machine movements.PLCs may include logic for single-variable feedback analog control loop, a "proportional, integral, derivative" or "PID controller." A PID loop could be used to control the temperature of a manufacturing process, for example. Historically PLCs were usually configured with only a few analog control loops; where processes required hundreds or thousands of loops, a distributed control system (DCS) would instead be used. However, as PLCs have become more powerful, the boundary between DCS and PLC applications has become less clear-cut.PLCs have similar functionality as Remote Terminal Units. An RTU, however, usually does not support control algorithms or control loops. As hardware rapidly becomes more powerful and cheaper, RTUs, PLCs and DCSs are increasingly beginning to overlap in responsibilities, and many vendors sell RTUs with PLC-like features and vice versa. The industry has standardized on the IEC 61131-3 functional block language for creating programs to run on RTUs and PLCs, although nearly all vendors also offer proprietary alternatives and associated development environments.Digital and analog signalsDigital or discrete signals behave as binary switches, yielding simply an On or Off signal (1 or 0, True or False, respectively). Push buttons, limit switches, and photoelectric sensors are examples of devices providing a discrete signal. Discrete signals are sent using either voltage or current, where a specific range is designated as On and another as Off. For example, a PLC might use 24 V DC I/O, with values above 22 V DC representing On, values below 2VDC representing Off, and intermediate values undefined. Initially, PLCs had only discrete I/O.Analog signals are like volume controls, with a range of values between zero and full-scale. These are typically interpreted as integer values (counts) by the PLC, with various ranges of accuracy depending on the device and the number of bits available to store the data. As PLCs typically use 16-bit signed binary processors, the integer values are limited between -32,768 and +32,767. Pressure, temperature, flow, and weight are often represented by analog signals. Analog signals can use voltage or current with a magnitude proportional to the value of the process signal. For example, an analog 4-20 mA or 0 - 10 V input would be converted into an integer value of 0 - 32767.Current inputs are less sensitive to electrical noise (i.e. from welders or electric motor starts) than voltage inputs.As an example, say a facility needs to store water in a tank. The water is drawn from the tank by another system, as needed, and our example system must manage the water level in the tank.Using only digital signals, the PLC has two digital inputs from float switches (Low Level and High Level). When the water level is above the switch it closes a contact and passes a signal to an input. The PLC uses a digital output to open and close the inlet valve into the tank.When the water level drops enough so that the Low Level float switch is off (down), the PLC will open the valve to let more water in. Once the water level rises enough so that the High Level switch is on (up), the PLC will shut the inlet to stop the water from overflowing. This rung is an example of seal in logic. The output is sealed in until some condition breaks the circuit.An analog system might use a water pressure sensor or a load cell, and an adjustable (throttling) dripping out of the tank, the valve adjusts to slowly drip water back into the tank.In this system, to avoid 'flutter' adjustments that can wear out the valve, many PLCs incorporate "hysteresis" which essentially creates a "deadband" of activity. A technician adjusts this deadband so the valve moves only for a significant change in rate. This will in turn minimize the motion of the valve, and reduce its wear.A real system might combine both approaches, using float switches and simple valves to prevent spills, and a rate sensor and rate valve to optimize refill rates and prevent water hammer. Backup and maintenance methods can make a real system very complicated.PLC programs are typically written in a special application on a personal computer, then downloaded by a direct-connection cable or over a network to the PLC. The program is stored in the PLC either in battery-backed-up RAM or some other non-volatile flash memory. Often, a single PLC can be programmed to replace thousands of relays.Under the IEC 61131-3 standard, PLCs can be programmed using standards-based programming languages. A graphical programming notation called Sequential Function Charts is available on certain programmable controllers.Recently, the International standard IEC 61131-3 has become popular. IEC 61131-3 currently defines five programming languages for programmable control systems: FBD (Function block diagram), LD (Ladder diagram), ST (Structured text, similar to the Pascal programming language), IL (Instruction list, similar to assembly language) and SFC (Sequential function chart). These techniques emphasize logical organization of operations.hile the fundamental concepts of PLC programming are common to all manufacturers, differences in I/O addressing, memory organization and instruction sets mean that PLC programs are never perfectly interchangeable between different makers. Even within the same product line of a single manufacturer, different models may not be directly compatible.The PLC was invented in response to the needs of the American automotive manufacturing industry. Programmable controllers were initially adopted by the automotive industry where software revision replaced the re-wiring of hard-wired control panels when production models changed.Before the PLC, control, sequencing, and safety interlock logic for manufacturing automobiles was accomplished using hundreds or thousands of relays, cam timers, and drum sequencers and dedicated closed-loop controllers. The process for updating such facilities for the yearly model change-over was very time consuming and expensive, as the relay systems needed to be rewired by skilled electricians.In 1968 GM Hydramatic (the automatic transmission division of General Motors) issued a request for proposal for an electronic replacement for hard-wired relay systems.The winning proposal came from Bedford Associates of Bedford, Massachusetts. The first PLC, designated the 084 because it was Bedford Associates' eighty-fourth project, was the result. Bedford Associates started a new company dedicated to developing, manufacturing, selling, and servicing this new product: Modicon, which stood for MOdular DIgital CONtroller. One of the people who worked on that project was Dick Morley, who is considered to be the "father" of the PLC. The Modicon brand was sold in 1977 to Gould Electronics, and later acquired by German Company AEG and then by French Schneider Electric, the current owner.One of the very first 084 models built is now on display at Modicon's headquarters in North Andover, Massachusetts. It was presented to Modicon by GM, when the unit was retired after nearly twenty years of uninterrupted service. Modicon used the 84 moniker at the end of its product range until the 984 made its appearance.The automotive industry is still one of the largest users of PLCs.Early PLCs were designed to replace relay logic systems. These PLCs were programmed in "ladder logic", which strongly resembles a schematic diagram of relay logic. Modern PLCs can be programmed in a variety of ways, from ladder logic to more traditional programming languages such as BASIC and C. Another method is State Logic, a Very High Level Programming Language designed to program PLCs based on State Transition Diagrams.Many of the earliest PLCs expressed all decision making logic in simple ladder logic which appeared similar to electrical schematic diagrams. This program notation was chosen to reduce training demands for the existing technicians. Other early PLCs used a form of instruction list programming, based on a stack-based logic solver.Early PLCs, up to the mid-1980s, were programmed using proprietary programming panels or special-purpose programming terminals, which often had dedicated function keys representing the various logical elements of PLC programs. Programs were stored on cassette tape cartridges. Facilities for printing and documentation were very minimal due to lack of memory capacity. The very oldest PLCs used non-volatile magnetic core memory.The functionality of the PLC has evolved over the years to include sequential relay control, motion control, process control, distributed control systems and networking. The data handling, storage, processing power and communication capabilities of some modern PLCs are approximately equivalent to desktop computers. PLC-like programming combined with remote I/O hardware, allow a general-purpose desktop computer to overlap some PLCs in certain applications.