SECTION 17762 *CONTROL SYSTEMS SCADA SOFTWAREpublic.eandm.com/Muni_docs/hughson1.pdf · 2009-06-01 · 1. SCADA Client Workstation: Client workstations shall be provided with all

0

0SECTION 17762

*CONTROL SYSTEMS SCADA SOFTWARE

PART I GENERAL

1.01 SUMMARY

*A. Section Includes:1. General:

a. This section includes SCADA system software to be used for applicationsoftware development and real time operation of the SCADA system.

b- The system software specified as part of this section support SCADAsystem functions including, but not limited to:1) Human Machine Interface (HMI) process graphics development and

*display.2) Rear time point database development and display.3) Historical database generation, collection, and display.

O 4) Alarming subsystem.5) Trending and Report subsystems.6) Drivers and interfaces.

c. PLC programming software is included in Section 17761.

B. Related Sections1. The Contract Documents are a single integrated document, and as such all

Divisions and Sections apply. It is the responsibility of the CONTRACTOR andits Sub-Contractors to review all sections to insure a complete and coordinatedproject.

2. In particular the following sections should be used in conjunction with this*section:

a. Section 17050 - Process Control and Instrumentation Systems General,

C. General requirements:1. Software provided under this Contract represent a complete and operating

control software system. Achieve the functionality described in this and other*sections through a combination of standard control system software and

application software developed specifically for this project.2. The standard control software listed in this section does not represent a

comprehensive list of software necessary to implement the functionalrequirements of the specifications. Provide all necessary supplemental drivers,utility software and application software, as required, to meet the functionalrequirements of the Specifications.

3. Applications software requirements are described in Section 17100 through17199.

4. License all software for proper operation as described in the Specifications.5. License all software provided under this Contract to the OWNER.

D. Provide copies of all software on CD, or equivalent media.

March 2009 - FINAL 17762-1 7554F11pw:/CarotIoDcumenIs/ClientCAJHughsorn7554F 1Specilicaions!17762 (FINAL)

0

E. Related Sections: The Contract Documents are a single integrated document, andas such all Divisions and Sections apply. It is the responsibility of theCONTRACTOR and its Sub-Contractors to review all sections to ensure a completeand coordinated project-

1.02 REFERENCES 0A. Refer to Section 17050.

1.03 DEFINITIONS

A. Definitions of terms are specified in Section 17050 and noted herein:1. National Electrical Code.2. Institute of Electrical and Electronic Engineers.3. Instrument Society of America.4. National Fire Protection Association.

B. SCADA system node descriptors are as listed below:1. SCADA Client Workstation: Client workstations shall be provided with all

graphic display and related software for interacting with the SCADA systemdata. SCADA client's displays shall operate on data maintained by the SCADAServer. Display capabilities shall include, but not be limited to:a. Process mimic displays.b. Real time and historical trend displays.c. Alarm summary and sub-summary displays.d. System utilities.

2. SCADA Development Node: Provide the SCADA system development nodewith software and licenses required to edit the programs and configuration filesas part of the system application development. Unless otherwise indicated, theDevelopment node shall be complete with run time software for fully testing theapplication programs. Functions required at the development node include: 0a. Edit the SCADA database.b. Edit graphic displays.c. Modify alarm files.d. Modify PLC programs.e. Modify programs and scripts executing at any of the workstations.f. Set up trends and historical displays.g. Edit user authorizations. 0h. Other functions as may be required to modify the SCADA system

application software.3. SCADA Server: Provide Server nodes with software and licenses as needed to

communicate with the PLCs and other data providers and maintain a real timedatabase of system values. Unless otherwise indicated, server nodes shall beequipped with client software for the viewing of the real time data. The SCADAserver will include input/output drivers for interfacing with field devices, and 0buffer historical data, and provide data for the Historian Node(s). On systemsnot containing a historian node, the SCADA servers will maintain permanentdata files containing the historical data.

4. Historian Node: The Historian node collects real time data and compresses thevalues into historical records for trending and reporting. Unless otherwiseindicated, the Historian node shall archive data provided by the SCADAserver. The server shall be provided with software for interfacing with standard

March 2009 - FINAL 17762-2 7554F11pw:t/CarolloiDocumentsClient/CKjHughsorJ7554F1 1/Specifications/ 17762 (FINAL)

00*report software packages via MS-SQL, ODBC and other standard interfaces

as described in this Section.5. Alarm Node: Each client workstation is equipped with an alarm window on the

operator display with local annunciation. Where a separate alarm node hasbeen indicated, this node shall handle the interface to telephone, paging andradio alarming systems.

*1.04 SYSTEM DESCRIPTION

A. General:1. The CONTRACTOR shall provide SCADA software, as required for a

complete and functional SCADA system as shown on the Drawings and asdescribed in this Section:a. Provide software on the system nodes as follows:

1) OIS-1:a) Microsoft Windows XP.b) SCADA I/O Server.c) SCADA Development.d) Alarm Dialer.e) Norton Ghost.f) Microsoft Office Professional 2007g) Report Generation.

2) SS-1:*a) Microsoft Windows XP.

b) Historical Server.3) OIS-2:

a) Microsoft Windows XP.b) SCADA I/O Server.

*c) Norton Ghost.b. System Configuration:

1) The system'consists of a primary and backup data serversconfigured for hot failover operation- Server nodes shall be equippedwith 1/O drivers from communicating with networked PLCs.

2) Client machines obtain real time data from the I/O servers. The clientmachines shall monitor the status of the servers and re-establishdata connections with a new server in case the primary server fails.

*1.05 SUBMITTALS

A. Furnish submittals in accordance with Sections 01330 and 16050 Work.

B. Furnish complete submittals as specified in Section 17050, and specifically definedherein.

C. Furnish complete submittals in accordance with:1. Division 1.2- Section 17050 - Process Control and Instrumentation Systems General.3. Section 17762 - Digital Control Systems - General.

D_ Remote Alarm Database:1. After development of the SCADA system database but before system start up,

*provide a list of points configured for alarming and submit to the OWNER andthe ENGINEER. The OWNER/ENGINEER will identify critical alarms for use in

March 2009 - FINAL 17762-3 7554F11pw://Carol&DoumentsClienCAHughson/7554F1 1/Speciiications/1 7762 JFINAL)

0

the extended alarming system (e.g. dialer system, paging) and provideresponse descriptions.

E. Alarm descriptions shall be of sufficient detail for an accurate review by theOWNER.

F. After all shop drawings submittals required herein, have been favorably reviewed bythe ENGINEER, the ICSC shall submit the following items, which must also befavorably reviewed and implemented prior to the start of system testing, the entirecontrol system including all required software packages must be operational prior tothe required Factory Acceptance Test:1. All operator interface display submittals shall be in full color as they will appear

on the display screen.a. This submittal shall be prepared after the requisite Graphics Meetings.b. The submittal shall include:

1) Graphic displays.2) Trend displays.3) Alpha numeric displays.4) Alarm displays.

2. Each display shall be uniquely titled.a. Locations for process data shall be clearly identified either through the

use of simulated data or by showing variables on the displays andproviding a reference list describing those variables.

b. All dynamic points shall be identified by tag number as a minimum andtheir operation shall be described on separate sheets.1) Color change.2) Symbol change-

c- Three sets of submittals, with screen prints in color on a whitebackground, are required for review by the ENGINEER.

d. One set will be returned with comments.3. All periodic and custom reports for the entire control system.

a. Locations for process data shall be clearly identified, either through theuse of simulated data or by showing variables on the report and providinga reference list describing those variables.

b. Three sets of reports shall be submitted for review by the ENGINEER.c. One set will be returned with comments.

G. Pre-acceptance test documentation in accordance with paragraph 1.09 of thisSection.

H. Operator's Reference Manual:1. The ICSC shall prepare and submit a users reference manual for the operator

interface system for use by the operators. This manual shall be bound in athree ring binder and meet the following minimum requirements.a. An index to the manual.b. A list of operator interface:

1) Display screens.2) Trends. 03) Reports.4) With display name and description.

0

March 2009 - FINAL 17762-4 7554F11 0pw:/Caro[io!DocumenlWCIentiCAIHughscn/7554F1 IS pecificaticns/17762 (FINAL)

0

* c. A summary of all possible commands and operator inputs to thesescreens including set points.1) All control actions shall be included.

d. A Control System Block Diagram with names and locations of majorcomponents.

e. Instructions for manually printing screens or reports.* 1) Real time.

2) Historical.f. A summary of security levels and their privileges and limitations.g. Spaces for operators to make notes.

2. A copy of this manual shall be provided to each operator during training on theoperator interface operations.a. The training class shall include a review of this manual with the operators

in addition to more detailed instruction on the operator interface*configuration and its use.

*1. Review Meeting Minutes Submittals:1. Graphics review meeting:

a. Minutes of Graphic Review Meeting No. 1.b. Minutes of Graphic Review Meeting No. 2-

2. Report review meeting:a. Minutes of Report Review Meeting No. 1.b. Minutes of Report Review Meeting No. 2.

*1.06 QUALITY ASSURANCE

A. As specified in Section 17050.

B. The manufacturer must have a formal and documented set of quality assurance*procedures that are applied to the engineering design, development, and

documentation of the software:1. The presence of a formal quality assurance department is required.

C. The manufacturer must also demonstrate that its source code for the product isregularly archived both on-site and off-site in facilities suitable to withstand physicalharm.

D. Software provided under this Section shall be included in the testing specified in

Section 17950.

1.07 DELIVERY, STORAGE, AND HANDLING


1.08 PROJECT OR SITE CONDITIONS

*A. As specified in Section 17050.

1.09 SEQUENCING

*A. The following items shall be submitted with the final sets of technical manualsrequired in accordance with paragraph 1.05 of this Section, 15 working days prior to

*the Pre-commissioning Test as specified in Section 17050.

March 2009 - FINAL 17762-5 7554F11pw:fiCarollcDccumenls/ClienVCkHughson755

4F 1!Specificatiosl 7762 (FINAL)

1. All program manuals supplied by the manufacturers with the standard softwarepackages.

2. All original program disks supplied by the manufacturers with the standardsoftware packages, including any program revisions or updates issued by themanufacturers during the construction period.

3. All PLC program and operator interface application program files stored onlabeled disks:a. The PLC program and operator interface application program file disks

shall also be updated as required if any changes or corrections arerequired in this programming prior to project completion.

B. Operator Interface Graphics Generation:1 . The ICSC through the CONTRACTOR shall schedule the Operator Interface

Graphics Meetings.2. Topics shall include graphics for:

a. HMI graphics.b. Data Acquisition and Graphics Display System.

3. The OWNER and ENGINEER shall attend these meetings.4. Graphics Meeting No. 1.

a. Graphics Meeting No. 1 - The ICSC shall chair and develop an agenda,three weeks in advance of the meeting, which shall address the basiccriteria to be adhered to in the configuration and development of graphicdisplays.1) At this meeting the ICSC shall distribute sample display formats for

illustration purposes.2) As a minimum, this meeting shall address the following issues:

a) All in plant and remote site areas and conventions for identifyingtag names and descriptors.

b) Designation of groups within each plant area along with tagnames and descriptors.

c) The assignment of individual control loops and inputs to specificgroups.

d) Organization of the systems universal display hierarchy.e) Paging schemes to be used to enable the movement from one

display to another.f) An itemization of the type of display to be used at each level in

the graphic hierarchy, i.e. pre-formatted displays, templates,custom graphics, etc.

g) Color convention to be employed on all graphics for theannotation of various status information, differentiation betweenalarms based on alarm priority, background colors, static fieldcolors and dynamic field colors.

h) The utilization of blinking and conditional text.i) Definition of graphic symbolism to be used on the project. This

listing shall include but not be limited to symbols to be used forprocess instrumentation, process equipment, piping, vesselsand valves:(1) All symbolism must be specific as opposed to generic in

that shapes must define both function and type i.e. specificsymbols for each valve design, each pump design, eachtype of flow meter, etc.

March 2009 - FINAL 17762-6 7554F11pw://CaroloiDecumentsiCienCA'HughsOrt7554F 1/Specilicabions17762 (FINAL)

* (2) If the ICSC's library of shapes does not adequatelydescribe plant or field conditions, the ICSC shall developadditional shapes to meet the plant or field requirements.

i (3) Shapes and symbols used on the P&IDs shall be used as a*guideline.

j) Definition of all display select commands that enable theoperator to move within the display hierarchy.

k) The utilization of cursor movement commands which enable theoperator to move within a display.

I) Definition of control input commands which enable the operator*to interact with face plates control stations and custom graphic

displays to implement control functions.m) Definition of data input commands which enable the operator to

*enter numeric values into the Control System.n) Definition of the utilization of "poke" points or fields that are

dynamically sensitive to operator inputs to facilitate operatorentry directly into graphic displays.

o) A review of graphic generation procedures.b. Subsequent to the adjournment of graphics meeting No. 1 the ICSC shall

prepare and formalize a document titled "GRAPHICS CRITERIA" whichshall contain detailed meeting minutes and a definition of all graphic

*guidelines to be adhered to:1) This report shall be supplemented by graphic examples which

illustrate the incorporation and application of each graphic criteria.2) The report shall be submitted within 30 calendar days of the

meeting's adjournment,5. Graphics Meeting No. 2:

a. Subsequent to the finalization of the overall system-wide graphics criteria,the ICSC shall develop graphic packages for the entire operator interfacesbeing furnished under this project.

b. At this meeting the ICSC shall submit 5 copies including:1) A review of the graphic package developed for the process areas for

content and completeness.2) A review of all data fields that display automatically updated process

information.3) A review of all required input commands associated with the graphic

access and control manipulation.c. Subsequent to the adjournment of Graphics Meeting No. 2 the ICSC shall

*prepare a formalized submittal of the graphic package for review alongwith the detailed meeting minutes:1) The report shall be submitted within 30 calendar days of the meeting

*adjournment.

C. Report Generation:1 . The ICSC through the CONTRACTOR shall schedule the Report Generation

Meetings.2. The OWNER and ENGINEER shall attend these meetings.3. Reports Meeting No. 1:

a. The ICSC shall chair and develop an agenda, 3 weeks in advance for ameeting, which shall address the basic criteria to be adhered to in theconfiguration and development of the reports:

March 2009 - FINAL 17762-7 7554F11pw:/ICarol&uDccuments)ClienlICNHughson/7554F1 ISpecificatcrcm17762 (FINAL)

1) At this meeting the ICSC shall distribute sample formats forillustration purposes.

2) As a minimum, this meeting shall address the following issues:a) All in-plant and remote site data and conventions for identifying

tag names and descriptors.b) Designation of groups within each plant area along with tag

names and descriptors.c) The assignment of inputs to specific categories.d) Organization of the systems universal report categories.e) An itemization of the type of report available.f) Definition of terms to be used on the reports.g) Definition of all report commands that enable the operator to

move within the report editor.h) The utilization of cursor movement commands which enable the

operator to move within a report.i) Definition of data input commands which enable the operator to

enter numeric values into the system.j) A review of report generation procedures.

3) Subsequent to the adjournment of the Report Meeting No. 1 theICSC shall prepare and formalize a document titled "REPORTCRITERIA" which shall contain detailed meeting minutes and adefinition of all report guidelines to be adhered to:a) This report shall be supplemented by report examples.b) The report shall be submitted within 30 calendar days of the

meeting's adjournment.4. Reports Meeting No. 2:

a. Subsequent to the finalization of the overall report format criteria, theICSC shall develop report packages for review.

b. At this meeting the ICSC shall submit 5 copies including:1) A review of the report package developed for the process area(s) for

content and completeness.2) A review of all data fields for process information.3) A review of all required input commands associated with the report

access and control manipulation.c. Subsequent to the adjournment of Report Meeting No. 2 the ICSC shall

prepare a formalized submittal of the report package for review along withthe detailed meeting minutes:1) The report shall be submitted within 30 calendar days of the meeting

adjournment.5. Ten additional displays shall be configured on-line during the Pre-

commissioning Test period.0

D. Ten additional reports shall be configured on-line during the Pre-commissioningTest period.

1.10 SCHEDULING (NOT USED)

1.11 WARRANTY 0A. As specified in Section 17050.

B. In accordance with:

March 2009 - FINAL 17762-8 7554F11pw.llCarcloiDocumentsiCient/CAHughson/7554F1 l/Specilicationsl 7762 (FINAL)

1 Section 17050 - Process Control and Instrumentation Systems General.

i C. The manufacturer must provide the capability of delivering extended warrantysupport, as well as after-hours warranty support:1. The Manufacturer shall provide a 2 year warranty which shall include:

a. Extended support which includes:* 1) Dedicated department or handled by programming staff or distributor.* 2) Telephone support available 24 hours per day-

3) Email & Web support addresses.4) FTP download area.5) Knowledge Base.6) Bulletin board service.7) Field service.

D. 24 hour, 7 day a week support available from the Manufacturer.

E, Provide system upgrades and fixes for a period of 2 years from substantial*completion at no additional cost to the OWNER.

0 F. Provide manufacturer's Support Contract for a period of 2 years.

1.12 SYSTEM STARTUP (NOT USED)

1.13 OWNER'S INSTRUCTIONS (NOT USED)

1.14 COMMISSIONING (NOT USED)

1.15 MAINTENANCE-(NOT USED)

PART 2 PRODUCTS

2.01 MANUFACTURERS

A. Provide the following:1. Wonderware, to match existing.2. No Equal.

2.02 EXISTING PRODUCTS (NOT USED)

2.03 MATERIAILS(NOT USED)

2.04 MANUFACTURED UNITS

A. General:1. Unless otherwise indicated provide all run time and development software

*licensed for:a. Unlimited Tags.b. Unlimited Screens-c. No direct limits on the number of connections to a server machine.d. Provide the number of client licenses as indicated by the number of

machines shown or specified, the addition of a new client shall not require*an upgrade to the server license.

March 2009 - FINAL 17762-9 7554F11pw:hCarclcWDouments/Clent/CHughson/7554F11/SpcificaionSl17

76

2(FINAL)

2. Provide software and licenses as required to implement the systemarchitecture and functionality as indicated on the Drawings and as described inParagraph 1.04 System Description of this Section.

3. License/registered all software in the OWNER's name.4. Turn all software installed on the workstation, over to the OWNER with disks,

keys and manuals.

B_ Operating System Software:1. Provide all workstations and servers with operating system software

compatible with the software provided under this section:a. Client Nodes: Windows XP Professional.b. Server Nodes: Windows 2003 Server.

2. Provide all operating system software as a clean install, Where workstationshave been loaded with OEM versions of software containing trial software orother advertisements, Remove the OEM software and reinstall the operatingsystem and all drivers from the original installation disks.

3. Provide all workstations with recovery disks.4. At the completion of site acceptance testing, CONTRACTOR shall create an

image backup made of each workstation and server disk and turn it over to theOWNER.

C. SCADA HMI Run Time Software:1. Provide run time software and licenses for all Control System workstations

provided.2. Include client licenses for I/O server machines.

D. SCADA I/O Server Software:1. Provide software and licenses for a full SCADA system node including I/O

drivers.2. Provide drivers for all control system devices as indicated on the Drawings.3. Configure Historical Data Collectors to provide data for the historical database

on all I/O servers.

E. Development Workstations:1. For development workstations provide all software for the generation and

modification of the of graphic screens, SCADA system databases, accesscontrol files and supervisory control programs.

2. The development node contains all client software and licenses for use as anadditional operator display.

3. The development node shall be equipped with I/O drivers for live testing ofscreens and control programs.

F. Historian Server: 01. Provide the latest version of the Historian software.2. Use Data collectors to buffer historical data in the event of a loss of

communication with the History Server.3. Provide Microsoft SQL Client Access Licenses for all nodes in the system plus

an allowance for 50 percent expansion.G. Licensing: 0

1. Provide hardware keys will utilize the USB form factor.0

March 2009 - FINAL 17762-10 7554F11pwJflCarollo/Ocumenls/ClienMCNfHughsor7554FI 1jS pocicationsI17762 (FINAL)

* H. Alarm Dialer Software:1. Install the alarm Dialer software on the workstation identified as the Alarm

Node.2. The alarm software shall interface with the SCADA system via the SCADA

* system client software and provide an interface to the appropriate externalalarming system.

* 3. Provide 1 copy of the alarm dialing software:a. SCADAIarm Event Notification Software by Wonderware.b. Win9l 1 Event Notification Software by Specter Instruments.c. Or approved equal.

1. Miscellaneous Software:1. Provide the following support software for use on the SCADA system

0computers. Install all software on the appropriate system node. Provide allsoftware CD/DVD media. License all software to the Owner:a. Provide Symantac's Norton Ghost Software for the back up of all system

*nodes to DVD.b. Provide 2 copies Microsoft Office Professional Edition 2007 for generating

and editing of reports.c- Provide 1 copy of Sytech xlReporter Suite for the development of report

templates and the event scheduling of automatically generated reports.d. Provide all nodes with virus protection software-

2.05 EQUIPMENT (NOT USED)

2.06 COMPONENTS (NOT USED)

2.07 A.CCESSORIES (NOT USED)

2.08 MIXES-(NOT USED)

2.09 FABRICATION (NOT USED)

2.10 FINISHES-(NOT USED)

2.11 SOURCE QUALITY CONTROL (NOT USED)

PART 3 EXECUTION

3.01 EXAMINATION


3.02 PREPARATION


3.03 INSTALLATION

*A. As specified in Section 17050,

March 2009 - FINAL 17762-11 7554F11pw:IlCaroloIDccurnentsClientCAlHughson/7554F1 1/Specilicatons!! 7762 (FINAL)

0

B. Install all required software improvement modules (SIMs). At the completion of theproject, and provide installation disk(s) containing all SIMs used on the project tothe OWNER.

3.04 ERECTION, INSTALLATION, APPLICATION, CONSTRUCTION

A- As specified in Section 17050.

3.05 REPAIR/RESTORATION


3.06 RE-INSTALLATION


3.07 FIELD QUALITY CONTROL

A. Test all software provided as part of this Section as part of the system testsspecified in Section 17950.

B. Provide training for 2 of the OWNER's staff in the use of the software packages.

C. The CONTRACTOR shall cover the costs of tuition, training materials, and relatedfees, as well as, travel and subsistence expenses for the attendees if not held at theOWNER'S facility.

3.08 ADJUSTING (NOT USED)

3.09 CLiAtNING (NOT USED)

3.10 DEMONSTRATION AND TRAINING

A- As specified in Section 17050.

3.11 PROT-F-TION-(NOT USED)

3.12 SCHEDULE$-(NOT USED) SS

END OF SECTION 5S

0

March 2009 - FINAL ]17762-12 75541 11pwI/Cardle/Dcurnents/Client]CPHughson/7554F1 I /Specilications/17762 (FINAL)