Docstoc

Specification

Document Sample
Specification Powered By Docstoc
					                                                   SECTION 13442

                             COMPUTER AND NETWORK SUBSYSTEM (CNS)


PART 1 GENERAL

1.1    REFERENCES

       A. The following is a list of standards which may be referenced in this section:
          1. American National Standards Institute (ANSI):
              a. X3.5, Flow Chart Symbols and Their Usage in Information Processing.
          2. Institute of Electrical and Electronics Engineers (IEEE): 802.3, Local Area Networks:
              Carrier Sense Multiple Access with Collision Detection

1.2    SUMMARY

       A. This section covers requirements for Computer Subsystem (CNS) and is in addition to
          requirements in Section 1-13400, Process Instrumentation and Control Systems (PICS). Key
          technical definitions and requirements for CNS are given in Section 1-13400, Process
          Instrumentation and Control Systems (PICS) and Section 1-13401, Programmable Logic
          Controller Subsystem (PLCS).

       B.    CNS functions include data acquisition, historical data storage, text and graphic data display,
             alarming, process control, data analysis, report generation, and program development.
             Requirements listed identify minimum acceptable system performance. Provide all hardware
             and software features required to make system totally operational, with convenient operator
             interface and efficient equipment use.

       C.    The CNS hardware and software will be specified by the OWNERs SCADA consultant.

       D. Configuring of applications software will be provided by Owners SCADA Consultant.

       E.    This projected will be contracted in three (3) phases. A general description of the contracts is
             given below. However, the contract drawings and specifications provide the complete
             contract boundaries.
             1. Contract 1 consists of Preliminary Treatment, Secondary Treatment, Tertiary Treatment
                  and Chemical Storage and Feed systems.
             2. Contract 2 consists of the Solids Handling processes.
             3. Contract 3 consists of the Administration Building.

       F.    DEFINITIONS
             1. Abbreviations:
                a. CPU: Central Processing Unit.
                b. CNS: Computer and Network Subsystem.
                c. OIU: Operator Interface Unit.
                d. PLC: Programmable Logic Controller.
                e. PMCS: Process Monitoring and Control Software.




WESTERN WAKE PARTNERS, NORTH CAROLINA                                COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                    1-13442-1
ARCADIS G&M of North Carolina, Inc.                                                         Printed: 6.17.2012
Project No. NC705009.0000
             2.    Terms:
                   a. Circular Files: Files that are updated such that each record written to file replaces
                       oldest record in file.
                   b. Log a Message: Print a message on an alarm/status printer.
             3.    Types of Variables:
                   a. PLC Variables: Analog inputs, discrete inputs, analog outputs, discrete outputs,
                       pulse inputs, calculated variables, and internal register values.
                   b. Calculated Analog Points (CA): Analog variables computed from inputs from PLCs,
                       manual inputs, calculated discrete points, and other calculated analog points.
                   c. Calculated Discrete Points (CD): Discrete variables computed from inputs from
                       PLCs, manual inputs, calculates analog points, and other calculated discrete points.
                   d. Manual Inputs (MI): Variables whose values are manually entered, e.g. laboratory
                       data.
                   e. Process Variables (PV): Analog variables from PLCs and calculated analog points.

1.3    SUBMITTALS

       A. Shop Drawings, Hardware Submittals:
          1. CNS block diagram and overview description.
          2. Bill of Materials for CNS Components: Component number, manufacturer, model
              number, component description, and quantity.
          3. Room Layout Drawings: For control room show to scale enclosures, furniture, CNS
              equipment, and service area requirements.
          4. Power Connection Diagram: For CNS equipment in show interconnection from power
              sources through uninterruptible power supplies and power distribution panels, to
              computer and peripherals.
          5. Grounding Diagram: For CNS equipment show grounding philosophy and
              implementation.
          6. Interconnecting Wiring and Cabling Diagrams: For CNS equipment, identify terminal
              receptacles, cable ID tags, actual cable lengths, and maximum distance limitations
              between cabinets or components.
          7. Component Submittal: For each CNS component:
              a. General data and description.
              b. Engineering Specifications and data sheets.
              c. Scaled drawings and mounting arrangements.
              d. Equipment weights.
              e. Power and grounding requirements.
              f. External electrical interconnection and interface definitions.
          8. Shop Drawings for Specifically Manufactured CNS Equipment:
              a. A complete connection diagram.
              b. Data sheets on each major item, annotated as necessary to describe specific items
                   furnished.
              c. Scaled layout and fabrication drawings.
                   1) Cable access areas and cable routing.
                   2) Power termination and ground lug location.
                   3) Data cable termination points.
                   4) Anchor bolt size and location.
              d. Installation and mounting detail drawings.



WESTERN WAKE PARTNERS, NORTH CAROLINA                              COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                  1-13442-2
ARCADIS G&M of North Carolina, Inc.                                                       Printed: 6.17.2012
Project No. NC705009.0000
                   e. Equipment weights.
             9.    Power Consumption and Heat Dissipation Summary for CNS Equipment: Voltages,
                   current, phase(s), and maximum heat dissipations in Btu/hr.

       B.    Shop Drawings, Network:
             1. Routing path assignments for all network nodes.
             2. IP address for all network nodes.

       C.    Shop Drawings, Software:
             1. Standard Software Documentation:
                 a. Provide software license in Owner’s name.
                 b. System Software Documentation: Complete reference information for system users.
                     Detailed descriptions including features and limitations of package, how to use
                     package, and how package interfaces with other software packages.
                     1) Extended Documentation for Operating System and Utilities:
                         a) Base Documentation: For day-to-day users of tasks, including editing files
                               and using command procedures.
                         b) General User Documentation:
                               (1) Index to Extended Documentation.
                               (2) Using files, directories, command language, and text editors.
                               (3) Alphabetic list of errors, warning, and informational messages,
                                     including explanation and response required.
                         c) System Manager Documentation:
                               (1) Setting up systems.
                               (2) Maintaining system and files.
                               (3) Optimizing performance.
                               (4) Networking features.
                         d) Programming Documentation:
                               (1) Linking, loading, running, and debugging tasks.
                               (2) Screen management.
                               (3) Librarian and file management.
                               (4) Device support and device drivers.
                         e) Release notes.
                     2) Programming Language: Syntax, execution, use and reference capabilities.
                     3) Online and Offline Diagnostics: How they are used, and various execution
                         options available.
                 c. PMCS: Detailed technical reference manuals and user level manuals.
                     1) Types of Manuals:
                         a) System Manager Documentation:
                               (1) Initial system setup.
                               (2) Database and file structures.
                               (3) Communication with PLCs.
                               (4) Maintaining system and files.
                               (5) Troubleshooting system problems.
                               (6) Optimizing performance.
                         b) System Engineer Documentation: Configuring, applications software.
                         c) Operator Documentation: Using the PMCS with configured applications
                               software.



WESTERN WAKE PARTNERS, NORTH CAROLINA                             COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                 1-13442-3
ARCADIS G&M of North Carolina, Inc.                                                      Printed: 6.17.2012
Project No. NC705009.0000
                        2) PMCS Functions:
                           a) Process database.
                           b) Communication with field devices.
                           c) Calculated analog points and calculated discrete points.
                           d) Input processing.
                           e) Message logging.
                           f) CNS diagnostic alarms.
                           g) Alarm handling.
                           h) Control processor.
                           i) Restart program.
                           j) Man-machine interface-general functions.
                           k) Graphics display generator.
                           l) Types of displays.
                           m) Alarm/Status log history.
                           n) Historical data collection.
                           o) Data retrieval.
                           p) Trending.
                           q) Report generator.
                   d. Disk and Memory Requirements: Table showing CPU and disk memory
                      requirements for each standard software package.
                   e. Typical Examples from Previous Projects: Process graphic displays, historical trend
                      displays, and alarm/status printer output.
                   f. Changes to Standard Software: If changes to standard software packages are needed
                      to meet Specifications, provide detailed descriptions of proposed changes and
                      additions.
                   g. Presoftware Development Submittal: Software System Overview: Written overview
                      description of each major software package.
                   h. Applications Software Implementation Standards: Standards and procedures to be
                      used by persons developing, programming, configuring, and testing all software.
                   i. Applications Software: Outline of applications software to be developed. List
                      programming language or configuration method to be used for each different type of
                      application.
                   j. OIU Display Format Examples:
                      1) Two typical examples for types required for OIU display that are not shown in
                           standard software user’s manuals.
                      2) Typical process graphic displays and historical trend plots used on previous
                           projects.
                   k. Report Formats: For each report required for this Project:
                      1) Name of program used to configure report.
                      2) Page number references to user’s manual(s) that describe these programs.
                      3) Examples of typical reports provided on other projects.
                   l. Alarm/Status Printer Format: Examples of alarm/status printer output formats used
                      on previous projects.
                   m. Disk and Memory Allocations: Tables showing breakdown of relative percentages
                      of CPU and disk memory required, including spare.
                   n. Historical Trend Display Format Examples:
                      1) Short-term trends (less than 24 hours).
                      2) Long-term trends (several days and several months).



WESTERN WAKE PARTNERS, NORTH CAROLINA                             COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                 1-13442-4
ARCADIS G&M of North Carolina, Inc.                                                      Printed: 6.17.2012
Project No. NC705009.0000
                   o. Software Design Submittal: Detailed applications software documentation. Updated
                      version of Presoftware Development Submittal. For standard software
                      documentation, submit changes that have occurred to manuals since previous
                      Submittal. Clearly indicate which pages are to be removed or replaced.
                      1) Process Graphic Displays: Two-step submittal. Following Display Coordination
                           Meeting, provide full set of process graphic displays.
                           a) Step One: Preliminary versions of all displays. Hand drawn displays
                                 permitted at this step.
                           b) Step Two: Machine-generated color copies of displays.
                   p. Process Graphic Displays: Full set of machine-generated color copies based on
                      preliminary displays provided by Engineer.
                   q. Tabular Process Displays: Full set.
                   r. Trend Displays Examples: Typical trend displays for short-term trends (less than
                      24 hours) and long-term trends (several days and several months).
                   s. Reports: Two-step Submittal.
                      1) Step One: Full set of report layouts. Hand drawn displays or copies permitted at
                           this step.
                      2) Step Two: Full set of machine-generated reports.
                           a) All pages for multiple page reports.
                           b) Examples for different time periods (i.e., daily, monthly, yearly) where
                                 applicable.
                           c) Formatted and well commented listings of report configuration data.
                   t. Database Configuration: Configuration data for:
                      1) Process database.
                      2) Historical database.
                      3) I/O list.
                      4) Calculated Analog and Discrete Points: Format similar to lists in these
                           documents. Include description of algorithms used to compute each variable.
                      5) Control Strategies: Detailed written descriptions and P&ID type diagrams
                           depiction of control function.
                      6) Any other process related databases.
                   u. Standard Software Changes and Additions: For programming required to augment
                      Standard Software.
                      1) Detailed written descriptions, block diagrams, and macro level flow charts or
                           pseudo code.
                      2) Pseudo code conforming to software implementation standards in Presoftware
                           Development Submittal.
                   v. Disk Directory: File name, directory/path, file usage, and size.
                   w. Data Files Description: For each data file, list file name, purpose of file, size, and
                      format of each record.
                   x. Description of other data structures used by CNS.
                   y. System Management Plan: Recommendations for how Owner handles:
                      1) System Log: Format and examples for recording computer operations related
                           activities such as software problem, hardware problem, software changes,
                           power failures, and disk backup/reload.
                      2) Disk Backup: Backup frequency, number of backup copies, and storage of
                           backup copies.




WESTERN WAKE PARTNERS, NORTH CAROLINA                               COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                   1-13442-5
ARCADIS G&M of North Carolina, Inc.                                                        Printed: 6.17.2012
Project No. NC705009.0000
                   z.  Preliminary Software Documentation: Fully detailed version of items described in
                       paragraph O&M Manuals, Software Documentation.
                   aa. Term “preliminary” refers only to timing of Submittal, not to level of detail to be
                       provided.
                   bb. Disk or magnetic tape copies required for final software documentation are not
                       required for Preliminary Software Documentation.

       D. Samples: Color and material Samples of hardware enclosures and furniture.

       E.    Informational Submittals:
             1. Testing related Submittals.
             2. O&M Manuals-Hardware:
                  a. Updated version of Hardware Shop Drawings Submittals.
                  b. Component Manufacturers’ O&M Manuals: Instructions for installation, operation,
                      maintenance, troubleshooting, and calibration.
                  c. List of spare parts and expendables provided.
                  d. List of recommended additional spare parts.
             3. O&M Manuals-Software Documentation:
                  a. Updated version of Software Shop Drawing Submittals.
                  b. Initial values for database parameters–PMCS Error List:
                      1) An alphabetical listing of all error, warning, and alarm messages logged by
                           PMCS, except for process alarms.
                      2) For each message, list message, description of condition, brief description of
                           operator action required, and reference to manual covering condition.
                  c. Complete systems generation data.
                  d. Fully commented program listings for high level language programs created for this
                      Project.
                  e. System Programmer Operating Instructions: System operating procedures including
                      system generation, system loading, and startup.
                  f. System Operator Instructions: Computer operations procedures including system
                      restarts, power failure and recovery, report generation, disk backup and reload,
                      manual data entry, plot generation, historical tape operations, and general
                      troubleshooting.
                  g. Process Operator Instructions: Operator oriented procedures for OIUs, printers, and
                      video copiers.
                  h. Applications Software Source Files: Two electronic copies of fully commented
                      source listings and source configuration.
                  i. Third Party Software: For system software that is not a product of the Contractor or
                      his Subcontractors, include manufacturer’s original disks and manuals with
                      hardware shipments.

1.4    ENVIRONMENTAL REQUIREMENTS

       A. Central Control Room: Computer room, air conditioned.

       B.    Other Locations:
             1. Electrical Rooms: Inside, air conditioned.




WESTERN WAKE PARTNERS, NORTH CAROLINA                               COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                   1-13442-6
ARCADIS G&M of North Carolina, Inc.                                                        Printed: 6.17.2012
Project No. NC705009.0000
1.5    MAINTENANCE

       A. Maintenance Service Agreement: Following Final Payment and Acceptance.
          1. Onsite Software Consultant: Support in addition to that required by service agreement.
              a. Duration: 1 year.
              b. Person-Days of Onsite Service: 15 minimum. Provided on a demand basis.
              c. Visits to Plant Site: 5 minimum.
              d. Support by programmer thoroughly familiar with CNS.
              e. Services: Database, display, and report configuration; changes to standard software;
                  optimization of CNS operation; and training in addition to that specified under
                  Article Training.
          2. Service Agreement:
              a. Duration: 1 year.
              b. Services: Manufacturer’s recommended preventive maintenance, check system error
                  counters, and install required engineering changes.
          3. Telephone Support Service:
              a. Duration: 1 year.
              b. Available during normal business week.
              c. Provided by persons thoroughly familiar with CNS supplied.
          4. Subscription to Software Update Service:
              a. Duration: 1 year.
              b. Coverage: Standard software, including both system software and PMCS.
              c. Include new software versions, documentation updates, newsletters, software
                  performance reports, and interim software updates.
          5. Supplemental Training:
              a. Duration: 1 instructor weeks.
              b. Content: Refresher on CNS hardware maintenance. Cover installation, startup,
                  diagnosis, and repair problems that Owner’s staff has encountered in first 6 months
                  of operation.

1.6    EXTRA MATERIALS

       A. Spare Parts:
          1. Two pointing devices of each type supplied.
          2. One complete OIU unit.
          3. One keyboard of each type used for OIU units.

       B.    Expendables:
             1. Two boxes (2,500 sheets per box) of single-part, 20-pound, unlined, white, tractor feed,
                 edge perf, full width, fanfold paper for each impact printer, except for alarm/status
                 printers.
             2. Two boxes (1,500 sheets per box) of two-part, carbonless, 15-pound, green bar, tractor
                 feed, edge perf, full width, fanfold paper for each alarm/status printer.
             3. Two boxes (10 reams, 5,000 sheets per box), 20-pound, white paper for each laser
                 printer.
             4. Six ink cartridges for each noncolor inkjet printer.
             5. Four sets of color ink cartridges for each color printer.




WESTERN WAKE PARTNERS, NORTH CAROLINA                             COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                 1-13442-7
ARCADIS G&M of North Carolina, Inc.                                                      Printed: 6.17.2012
Project No. NC705009.0000
             6.    One toner cartridge kit and one user maintenance kit for laser printer.
             7.    Fifty CDs/DVDs for each computer using CDs/DVDs, including personal computers.
             8.    20 percent, but no less than 10 of each type and current rating of fuse used.


PART 2 PRODUCTS

2.1    SYSTEM PERFORMANCE

       A. Capacity:
          1. Furnish CNS with sufficient capacity to handle equipment required by Contract
              Documents and equipment listed under paragraph Future Components, and still have
              specified spare capacity. Except for software configuring, implementing listed future
              components, shall not require addition of other CNS hardware or software.
          2. Spare capacities are based on size of CNS as required to implement equipment required
              by Contract Documents plus equipment listed under paragraph Future Components. For
              example, total storage capacity furnished for given functions:

                          (CURRENT + FUTURE)*(100 + SPARE)/100
                          Where:
                          CURRENT Equals: Storage capacity required to implement that function for
                          hardware and software furnished under Contract Documents.
                          FUTURE Equals: Storage capacity required to implement that function for
                          equipment listed under paragraph Future Components.
                          SPARE Equals: Percentage spare specified for that function.
             3.    Capacity refers to required physical size, storage capacity, and processing throughput of
                   CNS hardware and software. CNS changes required to implement listed future
                   components shall be limited to “configuring” database tables and system parameters to
                   allow system to recognize the additional equipment.
             4.    In order to verify that system has required capacity, accelerate PLC polling rate and
                   exception reporting rates during all tests to simulate inputs from additional devices listed
                   under paragraph Future Components. For example, if number of future RTUs listed
                   equals the number of RTUs required by contract document, conduct tests using a polling
                   rate that is twice that specified.

       B.    Future Components: Furnish sufficient CNS capacity to implement the following future
             components. Assume that each future PLC has a number of I/O points equal to average
             number of I/O point provided for similar units required by Contract Documents.
             1. PLCs: 2.
             2. CNS Operator Interface Units: 2.

       C.    OIU Response Time:
             1. Under moderately busy conditions, displays on OIUs are brought up and updated with
                 real-time data within number of seconds shown.




WESTERN WAKE PARTNERS, NORTH CAROLINA                                 COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                     1-13442-8
ARCADIS G&M of North Carolina, Inc.                                                          Printed: 6.17.2012
Project No. NC705009.0000
                                                                              Bring Up
                                                   Display Type                              Update
                            Main Menu                                              4            --
                            Help & Legend                                          5            --
                            Process Graphic                                        7            10
                            Alarm Summary                                          6            --
                            Trend, Real-Time, 4 Points                             5            5
                            Trend, 6-Hour, 5-Minute Samples, 4 Points             10            --
                            Trend, 5-Day, 1-Hour Samples, 4 Points                12            --
                         Tabular                                                              10
             2.    Moderately busy conditions are defined as follows:
                   a. Half the OIUs are each alternately requesting process graphic displays and historical
                      trend displays.
                   b. One OIU configuring process database.
                   c. Daily report running.
                   d. Data being transferred from process computer to personal computer.
                   e. PLCs are in operation.
                   f. Analog and discrete input points requiring processing due to exception reports from
                      PLCs occur at average rate of 10 per second.
                   g. Polling rates have been adjusted to simulate devices listed under paragraph Future
                      Components.

       D. End-to-End Response Time: Under moderately busy conditions, maximum time from
          beginning to end of following sequence shall be 10 seconds:
          1. An operator initiates a request from a process graphic display to move a valve, start a
              drive, or stop a drive.
          2. Command is sent to PLC.
          3. Command is executed by PLC.
          4. CNS interrogates status of PLC.
          5. CNS updates process graphic display to show response to the command.

       E.    Dual Computer-Automatic Failover:
             1. Response to Single Failure: No loss of required functions due to single failure of centrally
                 located CNS equipment or software.
             2. CNS Hardware Configuration: Refer to Control System Block Diagram on Drawings.
             3. Modes of Operation:
                 a. Operator selection of either CPU as online CPU and other as hot-standby CPU.
                      Provide for changing the status of the hot-standby computer to stand alone to operate
                      independent of online computer.
                 b. Hot-standby CPU request online CPU to report its status at least every 5 seconds. If
                      online CPU does not respond properly for 10 seconds, hot-standby CPU takes
                      control of online peripherals and PLCs and logs a failover message. Failed CPU then




WESTERN WAKE PARTNERS, NORTH CAROLINA                                COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                    1-13442-9
ARCADIS G&M of North Carolina, Inc.                                                         Printed: 6.17.2012
Project No. NC705009.0000
                        operate independent of online CPU until an operator requests failed system to return
                        to hot-standby mode.
             4.    Online CPU periodically check status of hot-standby CPU and log alarm message if hot-
                   standby CPU fails.
             5.    Maintain all data structures on the hot-standby CPU such that:
                   a. For Process Database, related configuration tables and other data structures needed
                        to fully define all real-time functions: Within 1 minute of time that changes to these
                        data structures occur in online CPU, update hot-standby CPU with these changes.
                   b. For historical disk files and all data structures and disk files not covered in above
                        subparagraph: Within 15 minutes of time that changes to these data structures occur
                        in online CPU, update hot-standby CPU with these changes.

2.2    SYSTEM SOFTWARE

       A. Operating System: General-purpose, multi-user, multiprocessing operating system:
          1. Multiprocessing support for simultaneous execution of process monitoring and control
              software tasks and system support tasks.
          2. Multistream batch processing operating under control of indirect command files.
          3. Priority task scheduler with provisions for job initiation on time of day, elapsed time,
              hardware interrupt, process event, request from another task, or operator request.
          4. Schedule I/O operations on a priority basis with all I/O carried out concurrently with
              program execution.
          5. Spooling (disk storage buffering) of all low speed printing devices.
          6. Device independent input/output system using online reassignable logical unit numbers
              for peripheral devices and file names for disk and files.
          7. Ability to delete, replace, or add process control tasks or system support while online.
          8. Multilevel password protection scheme to control access to different system support tasks
              and disk based data structures.
          9. Systems Generation: Allow configuring of an operating system to meet specific
              requirements of hardware and software configuration.

       B.    Utilities:
             1. File Management:
                  a. General-purpose file system supporting dynamic creation, extension, and deletion of
                        disk files from source programs, object programs, and data files.
                  b. Maintain on each disk a complete file directory including file name, size, location,
                        and type.
                  c. Automatic location on disk of new disk files.
                  d. File protection for online disk file to prevent accidental modification.
                  e. Copy individual files between devices (e.g., disk to disk and disk to printer).
             2. Text Editor: General-purpose, full screen text editor program for editing of source and
                  data files on disk.
                  a. Creating new files, add/delete/modify records, listing files, and so forth.
                  b. Character string search, move, copy, and replacement functions.
             3. Network Communications: General-purpose network communications software to
                  support local area network connection between CNS CPUs and personal computers.
                  Allows for exchange of disk files between computer systems.




WESTERN WAKE PARTNERS, NORTH CAROLINA                                COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                   1-13442-10
ARCADIS G&M of North Carolina, Inc.                                                         Printed: 6.17.2012
Project No. NC705009.0000
             4.    Debugging Aids: Online and offline debugging aids for high and low level language
                   environments.
             5.    System Performance Monitor: Accumulate information on CNS status and display
                   summary on OIU. Monitor loading of CPUs, disks, and other peripheral devices.
             6.    Disk Backup and Reload: Operator-initiated utility for maintaining backup copy on
                   removable disk pack of all CNS disk files.

       C.    Diagnostics:
             1. Online Diagnostics:
                 a. Complete system of diagnostic software to monitor, isolate, identify, tabulate, and
                      alarm system hardware malfunctions and software failures.
                      1) Input/output addressing for all I/O devices (detection of illegal addresses).
                      2) Incorrect data transfers (e.g., parity error).
                      3) No response (or time-out) from I/O device.
                 b. Central mechanism for accumulating and reporting number of soft and hard system
                      errors. Hard errors are errors that persist after multiple retries.
             2. Offline Diagnostics: Exercise and identify problems for all CNS equipment.

2.3    PROCESS MONITORING AND CONTROL SOFTWARE (PMCS) PACKAGE

       A. Configurable Software:
          1. Allows online, interactive, menu driven configuring of applications software.
          2. Concurrent operation of configuring functions and process monitoring and control
              functions.
          3. Function Blocks:
              a. Used to implement data acquisition and control features.
              b. Have fill-in-the-blanks menu which show current status of all parameters associated
                   with a given block.
              c. Unmodified parameters automatically assigned default values. Default values
                   configurable by user.
              d. Can be linked together to form control loops.

       B.    Process Database:
             1. Types of Database Points:
                 a. I/O points from field interface devices.
                 b. PLC Registers. Allow for both integer and floating point values.
                 c. CNS calculated analog and calculated discrete points.
                 d. CNS manual inputs.
             2. Database Fields:
                 a. Tag numbers (minimum of 9 characters).
                 b. Function block/point descriptions (minimum of 40 characters).
                 c. Most recent value read.
                 d. Process I/O hardware addresses.
                 e. Scan rate.
                 f. Scan enable/disable status.
                 g. Engineering units scale conversion factors.
                 h. Digital filter constants.
                 i. Data quality indicators.



WESTERN WAKE PARTNERS, NORTH CAROLINA                             COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                1-13442-11
ARCADIS G&M of North Carolina, Inc.                                                      Printed: 6.17.2012
Project No. NC705009.0000
                   j. Engineering units.
                   k. Alarm enable/disable status.
                   l. Alarm limits.
                   m. Status change log enable/disable status.
                   n. Timer settings.
                   o. Control tuning parameters.
                   p. Control status parameters.
                   q. Process I/O point value.
                   r. Historical data save requirements.
                   s. Real-time trend definitions.
                   t. Historical trend group definitions.
             3.    Documentation: Provide a means for obtaining hard-copy printout of configuration data
                   for process database and function blocks.

       C.    CNS/PLC Communications:
             1.    Poll discrete and analog inputs and outputs for each PLC.
             2.    On demand, read or load internal PLC registers including individual timers, counters,
                   timer/counter preset values, control loop setpoints, high/low limits, computed variables,
                   control loop tuning constants, status indicators, and sequence START/STOP commands.
             3.    Refer to Section 1-13400, Process Instrumentation and Control Systems PICS) and
                   Section 1-13401, Programmable Logic Controller Subsystem (PLCS), for
                   additional requirements.

       D. Calculated Analog Points and Calculated Discrete Points:
          1. Calculated on a real-time basis using configurable, BASIC like equations.
              a. Independent Variables: Analog inputs, discrete inputs, calculated analog points,
                   calculated discrete points, and manual inputs.
              b. Arithmetic Operators: +, -, *, /, and exponentiation.
              c. Boolean Operators: AND, OR, XOR, and NOT.
              d. Relational Operators: LT, LE, EQ, NE, GE, and GT.
              e. Arithmetic Functions: SQRT, LOG, LOG10, EXP, SIN, COS, TAN, MIN, and
                   MAX.
          2. Have same functions as analog inputs and discrete inputs. For example, alarm logging,
              OIU displays, flow integrations, data collection, data retrieval, and trending functions.

       E.    Input Processing: All functions configurable on a per point basis.
             1. Analog Points:
                  a. First order exponential digital filtering or by PLCs with filter factors downloaded
                      from CNS.
                  b. Instrument Failure Detection: Analog input variable not in 4 to 20 mA dc range. Set
                      data quality to indicate “bad” data. If PLC provides detection, then PLC notifies
                      CNS of instrument failure conditions.
                  c. Conversion to Engineering Units: Linear, square root, and polynomial conversions.
                  d. LOW LOW, LOW, HIGH, HIGH HIGH process variable alarm checking. Dead
                      bands individually adjustable for each point.
                  e. Rate-of-change alarm checking.
                  f. Pulse Inputs: Convert pulse rate to engineering units by dividing pulse count by time
                      interval since last reading.



WESTERN WAKE PARTNERS, NORTH CAROLINA                               COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                  1-13442-12
ARCADIS G&M of North Carolina, Inc.                                                        Printed: 6.17.2012
Project No. NC705009.0000
                   g. Accumulate pulses in six-digit, minimum, pulse counters.
             2.    Discrete Points:
                   a. Alarms: Selectable alarm on high, low, or change of state.
                   b. Inversion: Selectable inversion of input state.
                   c. Status Change Logging: Option for status change logging to be activated or
                        deactivated. When activated for a given point, print a status change message on
                        alarm/status printer when point changes state.
                   d. Elapsed Run Time Monitoring:
                        1) Counter Size: Six digits, minimum.
                        2) Counter Resolution: 0.1 hours, minimum.
                   e. Cycle Counters: Counts changes from OFF-state to ON-state.
                        1) Counting done by CNS, or by PLCs with counts sent to CNS.
                        2) Counter Size: Six digits, minimum.
             3.    Authorized users shall have the ability to remove a database point from being scanned by
                   placing the point in “Manual”. The database point value should change color to reflect an
                   old value and use shall be able to manually change values to test algorithms or
                   calculations applied to the HMI top-end.

       F.    Message Logging: For all alarm, status change, parameter change, and event messages
             directed to alarm/status printers:
             1. Messages Format:
                  a. Time of occurrence in 24-hour format (HH:MM:SS).
                  b. OIU identification and user’s initials (for messages produced by an operator action).
                  c. Message type. (i.e., alarm, status, parameter change, event, etc.)
                  d. Facility tag. Component tag number or device number.
                  e. Description of device or parameter.
                  f. Description of condition.
                  g. Process variable or parameter current value (if any).
                  h. Process variable or parameter units (if any).
                  i. Process variable alarm limit (for alarm messages).
             2. Examples: Refer to Article Supplements, Example Alarm/Status Message Formats.
             3. Every hour or once per page log message giving day, month, and year.
             4. Buffer messages if generated faster than printer can print them.

       G. CNS Diagnostic Alarms: Log an alarm message if hardware or software errors, which might
          affect process monitoring and control functions, are detected by online diagnostics.

       H. Alarm Handling: Configure alarm handling as follows:
          1. Alarm Sequence:
              a. When CNS detects alarm condition on enabled point, log “Alarm” message, display
                   alarm message in alarm window of each OIU, and actuate audio alarm at OIU.
              b. Continue audio alarm until alarm condition is acknowledged by entry from OIU.
              c. Log “Alarm Acknowledged” message when alarm is acknowledged.
              d. Log “Clear” message when alarm condition clears.
          2. Alarm Acknowledge: For an alarm to be acknowledged, the alarm condition shall be
              visible on OIU display. Allow acknowledgement from Alarm Summary Display.




WESTERN WAKE PARTNERS, NORTH CAROLINA                               COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                  1-13442-13
ARCADIS G&M of North Carolina, Inc.                                                        Printed: 6.17.2012
Project No. NC705009.0000
                                 Summary of Alarm Requirements (RTN = Return to Normal)
                             Point         Alarm             Symbol &       Blink       On Alarm
                             Alarm        Acknow-   Audio     Message      Alarm        Summary
                             Status        ledged   Alarm      Color       Message       Display
                             Alarm            No     Yes       Alarm          Yes           Yes
                             Alarm            Yes    No        Alarm          No            Yes
                              RTN             No     No       Normal          Yes           Yes
                            RTN         Yes          No       Normal         No            No
             3.    Disable Alarm Processing:
                   a. Selectable by operator on point-by-point basis.
                   b. Does not prevent point status from being shown on graphic process displays.
             4.    Alarm Destination: Configurable.

       I.    Control Processor:
             1. Allow online configuring from OIU of control functions without use of computer
                 programming language.
             2. Controls configured by interconnecting software function blocks. Blocks configurable by
                 entering specific values or connection specifications for individual block parameters.
                 Unmodified parameters take on configured default values.
             3. Function blocks and their associated parameters displayable on OIU.
             4. Documentation: Hard-copy printout of configured database.
             5. Continuous Control Functions:
                 a. PID control.
                 b. Manual loading station.
                 c. Ratio control.
                 d. Cascade control.
                 e. Totalization.
                 f. Add/subtract/multiply/divide.
                 g. Square root.
                 h. Ramp control.
                 i. Function generation.
                 j. Minimum/maximum value select.
                 k. Signal limiter.
                 l. High/low signal selector.
                 m. Signal limit switch.
                 n. Signal deviation switch.
                 o. Lead/lag filter.
                 p. Noise filter.
                 q. Dead time simulation/compensation.
                 r. Moving averages.
             6. Sequential Control Functions:
                 a. Boolean Functions: AND, OR, XOR, and NOT.
                 b. Timers: ON delay, OFF delay, and INTERVAL.
                 c. Counters: Predetermining and totalizing.



WESTERN WAKE PARTNERS, NORTH CAROLINA                             COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                1-13442-14
ARCADIS G&M of North Carolina, Inc.                                                      Printed: 6.17.2012
Project No. NC705009.0000
                   d.   Signal selectors.
                   e.   Drum programmers.
                   f.   Alternators, or SET/RESET “flip-flop” elements.
                   g.   Sequencer:
                        1) Configurable number of discrete control steps, 8 minimum.
                        2) Configurable set of discrete control and logic outputs at each step, 8 minimum.
                        3) Configurable set of discrete inputs at each step, 6 minimum.
                        4) Test function of inputs at each step to initiate advancement to next step.
                        5) A means to manually advance through each step.
                        6) Set error indicator if at any step in a sequence a control device fails to respond
                             within a preset time to a control output.

       J.    Restart Program:
             1. At least every 5 minutes, save on disk, CPU memory resident data needed to completely
                 characterize current status of CNS hardware and software.
             2. When system restart is required, use saved data to initialize CPU memory resident data.
                 Use HMI tool running on server to synchronize all clocks. Execute “housekeeping”
                 required to restore system to normal operation.

       K. Man-Machine Interface-General Functions:
          1. OIUs: Primary method of operator interface with the CNS real-time PMCS.
             a. Configure new CNS process variables and report variables.
             b. Configure, view, and change CNS process database parameters. Refer to paragraph
                  Process Database.
             c. View and change PLC database items such as setpoints, alarm limits, tuning
                  constants, pacing constants, timer/counter preset values, loop status, and sequence
                  START/STOP.
             d. Acknowledge alarms.
             e. Activate Data Retrieval System to get information from Data Collection files for
                  reporting, trending, or listing.
             f. Use log-on, help, legend, index, alarm summary, trend, diagnostic, and
                  configuration.
             g. Configure process graphic displays, tabular displays, and reports.
          2. Full access for each OIU to all OIU displays.
          3. Display Hard Copy:
             a. Initiated by single keystroke on operator OIUs.
             b. Cause full graphic representation current display to be printed on associated display
                  hard copy device.
             c. Works for all OIU displays.
          4. Log Changes: For database parameter changes made through an OIU log a “change”
             message on associated alarm/status printer. Include OIU ID or user ID in message.
          5. Alarm Window: Dedicated area of OIU screen reserved for display of most recent alarm.
          6. Password Protection:
             a. Four-level password protection scheme to prevent unauthorized users from making
                  changes from an OIU.
             b. Security Levels:
                  1) Engineer’s or Supervisor’s: Access to all database parameters.




WESTERN WAKE PARTNERS, NORTH CAROLINA                                COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                   1-13442-15
ARCADIS G&M of North Carolina, Inc.                                                         Printed: 6.17.2012
Project No. NC705009.0000
                        2)   Supervisor’s: Access to alarm limits, alarm inhibit status, scan inhibit status,
                             and all operator level functions.
                        3) Operator Level: Setpoints, control commands (AUTO/MANUAL, ON/OFF,
                             START/STOP, OPEN/CLOSE), timers, counters.
                        4) Display Only: No changes allowed.
                   c. Entry from OIU of a predefined password places that OIU at assigned access level.
                        OIU remains at this level until a different access level is logged or until user logs
                        off. Log-on operation logs messages naming logged-on user. Passwords entered in
                        nondisplay mode.
                   d. Supervisor level display to allow assignment of passwords to at least 40 individual
                        users.
             7.    Keyboard Entries and Targets: Designed to use a minimum number of keystrokes by
                   making use of targets, function keys, and brief mnemonic codes. Codes that will be
                   entered by operator appear on OIU display being used by operator to make entry.
                   a. Targets: Parameter values, status indicators, graphic symbols, or off-page connectors
                        that appear on a OIU display and provide:
                        1) Access to modify parameter value or status indicator.
                        2) Access to additional information on target.
                        3) Access to other related displays.
                        4) Execute functions or programs.
                        5) Target Selection: Primary methods. Mouse positions screen cursor to target.
             8.    Display Organization: Tree structure with major and minor menu displays that identify
                   access to subsequent displays. Menu displays have targets to displays listed.
             9.    Display Access:
                   a. Indirect access by paging down through menu tree for desired display.
                   b. Direct, one step access from display to another desired display by entering
                        identification code of desired display.

       L.    Graphic Display Generator:
             1. Objects and other related graphical display screen layouts shall conform to the Owner’s
                 Standards which include navigation, basic layout, dynamic color selection and symbols.
             2. Online, interactive, object oriented graphic editor for creating and editing text and
                 graphic displays.
             3. Allows user to see static part of display as user is editing it.
             4. Object Editing and Linking: Allows object selection, placement, line drawing, and
                 linking display fields to process database and other graphic displays.
                 a. Objects: Lines, rectangles, polygons, arcs, circles, text, value fields, and graphic
                      symbols.
                 b. Operations: Move, cut, copy, paste, rotate, fill, line weight, font changes, and change
                      color.
             5. Graphic Symbol Library:
                 a. Includes set of predefined process graphic symbols conforming to ISA-S55.
                 b. Allows addition of user defined symbols and editing of all symbols.
             6. Display Formats for Analog Points:
                 a. Numbers: Selectable number of digits and decimal places.
                 b. Bar Charts: Selectable orientation (horizontal or vertical), height, width, and color.




WESTERN WAKE PARTNERS, NORTH CAROLINA                               COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                  1-13442-16
ARCADIS G&M of North Carolina, Inc.                                                        Printed: 6.17.2012
Project No. NC705009.0000
             7.    Analog and Discrete Data Point Status: Selectable display of a data quality, out-of-
                   service, and control inhibit status. Status information able to be placed near point value or
                   symbol.
             8.    Real-Time Displays: Convert static displays created with display editor into dynamic
                   displays that link to process database to and provide real-time updating of dynamic
                   display data.

       M. Types of Displays:
          1. Help Displays: Assist user in learning to use OIU.
              a. Context Sensitive: Display additional information about using OIU functions for
                   current display.
              b. Function key actuated.
              c. Include user interface for adding, deleting, and editing Help displays.
          2. Alarm Summary Display: Shows all existing alarms and unacknowledged alarms. Refer
              to paragraph Alarm Handling.
              a. Display format similar to messages logged on alarm/status printer.
              b. Include time of day at which alarm was detected.
              c. Lists alarms in reverse chronological order.
              d. Unacknowledged alarm messages blink.
              e. Single-key acknowledgement of all alarms shown on a currently displayed page of
                   alarm summary display.
          3. Disabled Alarm Summary Display: Shows all disabled alarms including time and date at
              which each was disabled.
          4. Process Graphic Displays:
              a. Example Displays: Typical displays are shown on process graphic displays on
                   Drawings. These examples further define level of detail required for process
                   schematic type displays.
              b. Display Objects:
                   1) Process Flowstreams: Labeled and color coded.
                   2) Process Structures: e.g., Basins, tanks, wet wells, and channels.
                   3) Major equipment items, e.g., pumps, blowers, drives, and compressors.
                   4) Major control devices, e.g., gates and valves.
                   5) Instruments.
                   6) Targets to allow quick access associated process graphic displays.
                   7) Targets to allow quick access to database point parameters.
          5. Tabular Process Displays:
              a. Implemented through Graphics Display Generator.
              b. Data values shown in alarm/status colors.
              c. Diagnostic Displays: CNS Diagnostic Displays: CNS block diagram graphic
                   showing color coded operational status (online, offline, and failed) for each CNS
                   device.
              d. PLCS Diagnostic Display: Graphic display showing operational status of PCS
                   including data highway, data highway interface, and PLCs.
              e. DCS Diagnostic Display: Graphic display showing operational status of the DCS
                   including data highway, OIU, and the DCUs.

       N. Alarm/Status Log History:
          1. Disk File: Circular file of alarm/status messages logged by alarm/status printer.



WESTERN WAKE PARTNERS, NORTH CAROLINA                                 COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                    1-13442-17
ARCADIS G&M of North Carolina, Inc.                                                          Printed: 6.17.2012
Project No. NC705009.0000
             2.    Retrieval from Disk: Based on operator commands to control.
                   a. Format for Retrieved Data:
                        1) Tabular OIU display.
                        2) Report printed on report printer.
                   b. Data Screening Criteria:
                        1) Time Period: Start and end times/date.
                        2) Type of Message: All, Alarm, Change, Status.
                        3) Points Covered: All, all for a given facility, all for a given field interface device
                             or a tag number.

       O. Historical Data Collection Files: Periodically save designated variables for trending, report
          generation, and historical records. Allow all process variable to be selected for saving in data
          collection files.
          1. Data Quality Propagation:
               a. Along with each data value saved in historical files, include its data quality code.
               b. For such computed values as minimums, maximums, and averages, set data quality
                    to indicate:
                    1) OK: If P < Qlim
                    2) Questionable: If Qlim < P < Blim
                    3) Bad Data: If Blim < P
                    4) Where “P” is percent of time that independent variable had bad or missing data
                          or bad data quality. “Qlim” and “Blim” are adjustable limits.
               c. Bad data values are not used in calculation.
          2. Data Entry for Manual Inputs:
               a. Direct entry into historical files of data values for manual input variables.
               b. Data entered through menus based on configurable groups of related manual inputs.
                    Each group menu includes tag numbers and descriptions for 1 to 20, minimum,
                    manual inputs. Data entry sequence:
                    1) Operator selects a manual input data group.
                    2) Operator enters date for data.
                    3) CNS displays current values (if any) for variables on menu.
                    4) Operator enters values for variables.
                    5) CNS saves values in designated historical file.
          3. Corrections: Provide for correcting through an OIU of data values in historical files. Set
               data quality to indicate “inserted” value.
          4. Disk Files:
               a. High Resolution Data:
                    1) Sample Interval: Adjustable from 1 to 15 minutes.
                    2) Period Covered: Multiple day, adjustable.
                    3) Content: Time of day, date, tag numbers, and values of designated process
                          variable. Value saved shall be either instantaneous value or average over
                          sample interval.
               b. Hourly Data:
                    1) Sample Interval: 1 hour.
                    2) Period Covered: Multiple day, adjustable.
                    3) Content: Time of day, date, tag numbers, and average hourly values of
                          designated process variables.
               c. Daily Data:



WESTERN WAKE PARTNERS, NORTH CAROLINA                                 COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                    1-13442-18
ARCADIS G&M of North Carolina, Inc.                                                          Printed: 6.17.2012
Project No. NC705009.0000
                        1)    Sample Interval: 1 day.
                        2)    Period Covered: Multiple day, adjustable
                        3)    Content:
                              a) For Designated Process Variables:
                                    (1) Daily minimum and maximum values.
                                    (2) Time occurrence of daily minimum and maximum values.
                                    (3) Average daily value.
                                    (4) Daily total for flow and other rate type variables.
                                    (5) Tag numbers.
                              b) End of day values for designated run time counters, cycle counters, and
                                    their tag numbers.
                              c) Daily values for designated report variables, manual inputs, and their tag
                                    numbers.
                        4)    In case CNS is down at midnight, allow manual initiation of this file update at a
                              later time.

       P.    Data Retrieval:
             1. Retrieve data from Historical Data Collection files (disk) for listing, trending, and input
                 to user written programs.
             2. Retrieval Parameters Selectable by User:
                 a. Variable: Process variables, report variable, manual input for, or discrete input
                      which data are desired.
                 b. Data Types:
                      1) Actual value of variable at end of sample interval.
                      2) Minimum value of variable during sample interval.
                      3) Maximum value of variable during sample interval.
                      4) Total value of variable during sample interval.
                      5) Average value of variable during sample interval.
                      6) Run time hours over sample interval (discrete inputs only).
                      7) Cycles over sample interval (discrete inputs only).
                 c. Retrieval Period:
                      1) Time period covered by retrieval request:
                            a) Starting time/date and length of retrieval period, or
                            b) Ending time/date and length of retrieval period.
                      2) Within limits of data in files, complete flexibility for selecting retrieval period.
                            For example:
                            a) Starting 12:45/10-15-94 for 15 minutes.
                            b) Starting 14:30/10-16-94 for 4 hours.
                            c) Ending 8:00/9-30-94 for 5 days.
                            d) Ending 0:00/11-28-95 for 30 days.
                            e) Starting 0:00/12-01-94 for 6 months.
                 d. Sample Interval: Time interval between data points to be output. Within limits of
                      data files, complete flexibility for selection of sample interval. For example: 1 to
                      60 minutes, 1 to 24 hours, 1 to 31 days, 1 to 12 months.
                 e. Type of Output: Listing, MS EXCEL, Lotus output file format or comma delimited
                      test file., or trend plot.
                 f. Output Device: Hardware device to which data are to be output:
                      1) OIU: List or trend plot.



WESTERN WAKE PARTNERS, NORTH CAROLINA                                 COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                    1-13442-19
ARCADIS G&M of North Carolina, Inc.                                                          Printed: 6.17.2012
Project No. NC705009.0000
                        2) Printer: List.
                        3) Disk File: List.
                   g. Scaling for Trend Plots: See paragraph Trending.
             3.    Automatic selection of specific Historical files to access for requested data. Data retrieval
                   from multiple historical tapes if time period to be covered spans more than a single tape.
             4.    Retrieval requests made from programmer OIU and operator OIU.

       Q. Trending:
          1. General Features: Simultaneous trending of different sets of variables on different trend
              output devices.
              a. OIU Trend Resolution: Current.
              b. Variables Per Trend: User selectable, 1 to 4 minimum, all displayed in same trend
                   window.
          2. Trend Types:
              a. Real-Time: Continuous plotting of variables as a function of time.
                   1) Plotable Variables: Process variables, report variables, discrete variables, and
                        manual inputs.
                   2) Minimum Plot Sample Interval: Same as scan rate.
              b. Historical: Plotting variables from Historical Data Collection files as a function of
                   time. Historical trending is a special case of previously specified Data Retrieval
                   function.
          3. Retrieval Parameters: Specific variables, data types, retrieval period, sample interval,
              process variable scales, and output device. Refer to paragraph Data Retrieval.
          4. Process Variable Scales:
              a. Independent selection for each variable of low scale and high scale values in
                   engineering units of process variable axis. For example, if A and B are two variables
                   to be trended on the same graph, and if low scale and high scales for variables A and
                   B are 0.00 to 1.00 and 100 to 200 respectively, and if A equals 0.50 and B equals
                   150, both A and B would plot at exactly the same point (the mid-point of process
                   variable axis).
              b. Display individual, engineering units scales for each variable being trended.
              c. Readout Cursor: Adjustable by user over range of time scale. Values are displayed
                   in engineering units of each trended variable intersected by readout cursor.
              d. Point Descriptions: Tag number and description are shown for each trended variable.
          5. Trend Groups: Aid requesting of frequently used trends.
              a. Each trend group contains all data retrieval parameters needed to specify trend
                   display for up to four variables. Refer to Article Supplement, Example Trend
                   Groups.
              b. Each Trend Group is identified by a 6-character minimum group name and a
                   20-character minimum group description.
              c. Trend group menu allows selection of any individual Trend groups.

       R.    Report Generator:
             1. Table Driven Report Generator: Used to configure and print reports.
                 a. Configuration Process:
                      1) Online function using operaor OIU without need for programming.
                      2) Use of Graphics Display Generator permitted provided that full page size
                          (132 columns by 66 lines) is accessible.



WESTERN WAKE PARTNERS, NORTH CAROLINA                                 COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                    1-13442-20
ARCADIS G&M of North Carolina, Inc.                                                          Printed: 6.17.2012
Project No. NC705009.0000
                   b.  Report Configuration Tables: Used to define:
                       1) Page layout.
                       2) Specific headings and subheadings.
                       3) Variables to be printed.
                       4) Calculations required prior to printing.
                       5) Nonprinting free form “comments” for documentation purposes.
             2.    Report Types:
                   a. Single day.
                   b. Multiple Day: List daily values from 2 to 31 days.
                   c. Multiple Month: List monthly values from 1 to 12 months.
                   d. User defined Adhoc reporting.
             3.    Requesting and Printing Report:
                   a. Reports requested from OIU and printed on report printer.
                   b. Operator specifies name of report, type of report (single day, multiple day, or
                       multiple month), start date, end date, number of copies to be printed.
                   c. Report variables recompute each time report defining those variables is run. If an
                       independent variable used for a calculation has “bad data” or “missing data” codes,
                       calculation of dependent variable is bypassed and its data quality code set to “unable
                       to calculate due to missing data”.
                   d. Multiple reruns of reports are allowed to permit correction of faulty data or entry of
                       previously missing data.
                   e. Report Headings for Each Page of Report: Report title, time period covered, time
                       and date at which report was printed, and page number.
                                                   Examples of Valid Requests for Reports
                                      Report Type         Start Date       End Date           Period
                                                                                             Covered
                                   Single day            13-May-08       13-May-08        Daily report
                                   Multiple day          31-May-08       4-Jun-08         5-Day report
                                   Multiple day          27-Dec-08       2-Jan-09         Weekly report
                                   Multiple day          1-Dec-08        31-Dec-08        Monthly report
                                   Multiple month        Jan-08          Mar-08           Quarterly
                                                                                          report
                                   Multiple month        Oct-08          Mar-09           6-Month report
                                   Multiple month        Jan-08          Dec-08           Annual report


2.4    APPLICATIONS SOFTWARE

       A. CNS Standard Functions: Functional requirements that apply to database variable or of a given
          type. For example, logging alarm messages is a standard function since it applies to all alarm
          points.

       B.    Process Database Spare Capacity: 100 percent for base tables and disk files.



WESTERN WAKE PARTNERS, NORTH CAROLINA                                  COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                     1-13442-21
ARCADIS G&M of North Carolina, Inc.                                                           Printed: 6.17.2012
Project No. NC705009.0000
       C.    CNS/PLC Communications:
             1.    Poll all analog and discrete inputs and outputs for each PLC.
             2.    Read or load internal PLC registers including individual timers, counters, timer/counter
                   preset values, control loop setpoints, high/low limits, computed variables, control loop
                   tuning constants, status indicators, and sequence START/STOP commands.
             3.    Read and load these values as required to support man-machine interface and data
                   collection functions.

       D. Calculated Analog Points (CA):
          1. Provide CAs explicitly defined or implicitly required.
          2. Examples of Typical CAs: Tank volumes based on level; total flows for areas, zones,
              subsystems, and systems; and tank levels in feet of elevation.
          3. Partial listing of calculated CAs is given in Article Supplements, Calculated Analog Point
              Summary. This listing is not intended to be all-inclusive. Provide CAs required to
              provide completely operational system.
          4. Fields in Calculated Analog Point Summary:
              a. PLC Number.
              b. Variable Name: Process variable name or identifier.
              c. Description.
              d. Nominal Range: Approximate minimum and maximum values expected.
              e. Units: Engineering units.
              f. Alarm Limits.
          5. Configure same functions for CAs as for real analog inputs. For example, provide alarm
              logging, OIU displays, flow integrations, data collection, data retrieval, and trending
              functions for CAs.

       E.    Input Processing: Scan all process inputs at frequencies specified under sections defining
             PLCs.
             1.    Analog Inputs:
                   a. Digital Filter Constant: Zero.
                   b. Scale Range and Engineering Units: Refer to Instrument List and Drawings.
                   c. HIGH/LOW Alarm Limits: Refer to I/O Summary. Disable checking if no limits are
                       shown.
                   d. Instrument Failure Detection. Log alarm message when detected. If detection is not
                       handled by PLCs, then set High-High/Low-Low limits to high scale range plus
                       2 percent and low scale range minus 2 percent, respectively.
                   e. Alarm Dead Band: 2 percent of instrument range.
                   f. Rate of change alarm limit set for no alarm.
                   g. Totalize all flow, power, and other rate type variables.
             2.    Discrete Inputs:
                   a. Alarms: If “type” on I/O summary is ALARM, log alarm message when input
                       changes to high state.
                   b. Status Change Logging:
                       1) Deactivated for each point.
                       2) Normally used only for troubleshooting and activated on fewer that 5 percent of
                             points.
                   c. Elapsed Run Time Monitoring: For equipment units with ON/OFF status.




WESTERN WAKE PARTNERS, NORTH CAROLINA                               COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                  1-13442-22
ARCADIS G&M of North Carolina, Inc.                                                        Printed: 6.17.2012
Project No. NC705009.0000
                   d.   Cycle Counters: For all Motors.

       F.    Control:
             1. CNS Special Functions: Configure all controls defined under Section 13400,
                 Instrumentation and Control for Process Systems, paragraphs CNS Special Functions.
             2. CNS Standard Functions:
                 a. No Response Checking: If a control device fails to respond within a preset time to a
                      control output from CNS or a field interface device, log an alarm message that
                      identifies nonresponsive device and requested control output.
                      1) Timer Range: 0 to 60 seconds, adjustable in seconds.
                      2) Initial Timer Setting: 10 seconds.
                 b. Disagree Alarm: Each time a field device is polled, check status of all associated
                      control devices that are currently under CNS control. If a status change has occurred
                      that was not the result of a control output, log a “DISAGREE” message.

       G. Associated Alarm/Status Printers and Hard Copy Devices:
                         OIU Location                   Associated              Associated Hard Copy
                                                    Alarm/Status Printer               Device
                    Operations Building            Operations Building         Operations Building
                    Control Room                   Control Room                Control Room
                    TBD                            TBD                         TBD
                    TBD                            TBD                         TBD
                    TBD                            TBD                         TBD

       H. Process Graphic Displays:
          1. Display Coordination Meeting:
              a. Held prior to entering of process graphic displays.
              b. Purpose is to establish:
                   1) Graphic symbols to be used on displays.
                   2) Color usage conventions.
                   3) Conventions for showing alarm conditions, device status, and process variable
                       values.
                   4) Conventions for naming and identifying devices.
                   5) Breakdown of process into individual displays.
                   6) Preliminary layout for overview displays and for each process graphic
                              display.
             2.    Required Process Graphic Displays: Provide complete set of process graphic displays.
                   These include:
                   a. Process Overview Graphic for In-plant Processes:
                       1) Based on Process Interface Drawing.
                       2) Unit process symbols on overview are targets to associated Unit Process
                            Graphic Displays.
                   b. Unit Process Graphics:
                       1) Detailed displays showing status of all equipment connected to, and all control
                            provided by, PLCS.



WESTERN WAKE PARTNERS, NORTH CAROLINA                                    COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                       1-13442-23
ARCADIS G&M of North Carolina, Inc.                                                             Printed: 6.17.2012
Project No. NC705009.0000
                        2)  Show in P&ID format all monitor and control related data including: equipment
                            status, process variable values, alarm conditions, setpoints, control status,
                            counters, and timers.
                       3) Operator’s normal access to control functions. For example, while viewing
                            these displays operator can change status, i.e., open or close a valve, change a
                            setpoint, initiate a sequence, etc.
                       4) Coordinate with all package control system vendors to determine and
                            implement graphic display requirements. Systems include but ar not limited
                            to, MBR Filtration System, UV Disinfection System, Centrifuge Dewatering
                            Equipment and Electric Generator System.
             3.    Labels: Label all parameters and show all values in engineering units.
             4.    Device Status Colors for Graphic Symbols: Flashing red for alarm, steady red for
                   acknowledged alarm, yellow energized, and green for normal or not energized.
             5.    Access to Point Parameters:
                   a. Each process graphic display provides access for display and modification of
                       database parameters for process I/O point and calculated point shown on the process
                       graphic display. This is operators normal method of checking and changing database
                       parameters including, process variable range/zero, digital filter time constants, alarm
                       limits, time/counter settings, pacing constants, tuning constants, scan status, alarm
                       inhibited status, setpoints, and loop ON/OFF control status.
                   b. Parameters are accessed through use of targets and function keys.
             6.    Spare Capacity for Implementing Process Graphic Displays: 100 percent.

       I.    Other Required Graphic Displays:
             1. Legend for Process Graphic Displays: Defines colors and symbols used on process
                 graphic displays.

       J.    Alarm/Status Log History Circular File Size: 4,000 messages minimum.

       K. Historical Data Collection Files:
          1. High Resolution Data:
               a. Sample Interval: 5 minutes maximum.
               b. Period Covered: 48 hours minimum.
               c. Points Saved: All process variables.
          2. Hourly Data:
               a. Sample Interval: 1 hour.
               b. Period Covered: 62 days.
               c. Points Saved: All process variables.
          3. Daily Data:
               a. Sample Interval: 24 hours.
               b. Period Covered: 62 days.
               c. Points Saved: All process variables, manual inputs, run time counters, cycle
                    counters, and report variables.
               d. Manual Inputs: 200, one value per day.
          4. Spare Capacity: Same as specified under Paragraph, Process Database.
          5. Data Quality Propagation Limits:
               a. Questionable Data Limit: Qlim equals 10 percent.
               b. Bad Data Limit: Blim equals 50 percent.



WESTERN WAKE PARTNERS, NORTH CAROLINA                                COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                   1-13442-24
ARCADIS G&M of North Carolina, Inc.                                                         Printed: 6.17.2012
Project No. NC705009.0000
            B.     Trend Group Capacity: 50 trend groups, minimum.

       L.    Reports:
             1. Required Reports: Provide a total of ten reports. See supplement list of required reports.
                 Exact format and content of reports will be determined during the coordination meeting.
                 Prepare a preliminary submittal based on the supplement and submit for approval prior to
                 meeting.
             2. Spare Capacity for Reports: 100 percent.

2.5    HARDWARE

       A. CNS Block Diagram: Refer to figure CNS Block Diagram on Drawings. Interconnecting lines
          shown on block diagram imply information flow and not necessarily wiring.

       B.    Control Room Layout: Refer to Drawings.

       C.    Equipment Mounting: Unless otherwise noted, mount all CNS components in freestanding
             metal cabinets or provide with suitable metal stands to bring them to normal operating levels.

       D. Color: Color-coordinate CNS components to produce an attractive installation.

       E.    Cables Required:
             1. For interconnection between all CNS components, except where leased telephone lines
                 are shown.
             2. Cables Under 50 Feet Long: Prefabricated with connectors and factory tested with CNS.
             3. Special signal conditioning/repeating equipment as required for proper operation of CNS.
             4. Surge Arrestors: For Connections to CNS from equipment outside Central Control Room.
                 To protect CNS from damage by electrical transients induced in cables by lighting
                 discharges or electrical equipment.

       F.    Power to CNS Equipment:
             1. Central Control Room: Uninterruptible power supply system.
             2. Other Locations: 120-volt ac, single-phase, three-wire, 60-Hz.

       G. Power Failure Detection and AUTO Restart:
          1. Prevents errors due to power failure or short-term power fluctuations that occur when
             UPS is not operating.
          2. Power Failure: Voltage variations in excess of plus or minus 10 percent of normal for a
             duration of 0.5 second or longer. Causes CNS equipment to automatically shut down as
             required to prevent introducing errors on disk.
          3. Short-term Power Fluctuations: Voltage variations in excess of plus or minus 10 percent
             of normal for durations of 0.5 second to 1 millisecond). CNS shuts down as above or is
             buffered to prevent fluctuations from causing errors.
          4. CNS executes Restart program and return to normal operation when power is restored.
             Battery backed-up real-time clock used by CNS during automatic restart to set time and
             date.




WESTERN WAKE PARTNERS, NORTH CAROLINA                               COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                  1-13442-25
ARCADIS G&M of North Carolina, Inc.                                                        Printed: 6.17.2012
Project No. NC705009.0000
2.6    EQUIPMENT

       A. CNS Component List Format:
          1. Quantity: Capacities and quantities shown are minimum. Provide additional capacity or
             units as necessary to meet the functional requirements. Refer to Drawings where no
             quantity is listed here.
          2. Component Identification Code: Refer to Article Supplements, Component
             Specifications.

       B.    CNS Component List: Refer to Article Supplements, Component List.

       C.    Communications Control and Switching: Dual redundant communications control equipment
             for connection to peripheral devices, and PLCs.
             1. Application Servers will be configured in a redundant “mirror image” arrangement
                  connected directly to each other via secondary network interface cards (NICs) such that
                  the direct connect cable supports communications without putting overhead traffic
                  directly on the network backbone.

2.7    SOURCE QUALITY CONTROL

       A. Factory Demonstration Test: Test all nonloop-specific functions including, but not limited to:
          1. Failure mode and backup procedures including power failure, AUTO restart, and disk
              backup and reload.
          2. Dual Computer Operation: Processor transfer modes, peripheral switching, and
              communications switching.
          3. Message logging and alarm handling.
          4. Communication with PLCs.
          5. Data acquisition.
          6. Man-Machine Interface: Database and display configuration and use of all types of
              displays.
          7. Data collection and data retrieval.
          8. Report Generation: Creation of a typical report and production of specified reports.
          9. Control configuration processor.
          10. System Software: Operating system, programming languages, and utility functions.


PART 3 EXECUTION

3.1    FIELD QUALITY CONTROL

       A. Operational Readiness Test.

       B.    Performance Acceptance Test: Include the same types of testing that are specified for Factory
             Demonstration Test.

       C.    Reliability Acceptance Test.

3.2    TRAINING




WESTERN WAKE PARTNERS, NORTH CAROLINA                              COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                 1-13442-26
ARCADIS G&M of North Carolina, Inc.                                                       Printed: 6.17.2012
Project No. NC705009.0000
       A. Operations:
          1. Training Session Duration: 5 instructor days.
          2. Number of Training Sessions: Two.
          3. Location: Project Site.
          4. Content: Using man-machine interface functions from process operator’s standpoint.

       B.    Hardware Maintenance Factory Training:
             1. Training Session Duration: 5 instructor days.
             2. Number of Training Sessions: One.
             3. Location: Factory or training center.
             4. When: Before Factory Demonstration Test.
             5. Number of Students: Three persons.
             6. Content:
                 a. Standard hardware maintenance for CNS equipment.
                 b. How equipment and components are connected and set up for Project.
                 c. Test, adjustment, and calibration procedures.
                 d. Troubleshooting and diagnosis.
                 e. Component removal and replacement.
                 f. Periodic maintenance.

       C.    Hardware Maintenance Onsite Training:
             1. Training Session Duration: 5 instructor days.
             2. Number of Training Sessions: One.
             3. Location: Project Site.
             4. Content: Similar to factory training but uses installed hardware.

       D. Software Maintenance Factory Training:
          1. Training Session Duration: 1 instructor weeks.
          2. Number of Training Sessions: One.
          3. Location: Factory or training center.
          4. When: Before Factory Demonstration Test.
          5. Number of Students: Three persons.
          6. Design training for students having had 1 year of experience in using personal
                   computers, but no experience with mini computers.
             7.    Purpose: To provide Owner staff with sufficient training so that they can maintain CNS
                   software on a day to day basis.
             8.    Content:
                   a. System Overview: Basic system design, configuration, functions, maintenance, and
                        operation.
                   b. System Hardware: Specific hardware provided.
                   c. System Software:
                        1) Operating system, assembler, and compiler details.
                        2) Backup, reload, restart, and failover procedures.
                        3) Utilities, compilers, debugging aids, file management, and system generation.
                        4) Diagnostic Software: Capabilities, usage, and interpretation of results.
                   d. PMCS:
                        1) Process database.



WESTERN WAKE PARTNERS, NORTH CAROLINA                              COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                 1-13442-27
ARCADIS G&M of North Carolina, Inc.                                                       Printed: 6.17.2012
Project No. NC705009.0000
                        2) Communication with field devices.
                        3) Calculated analog and discrete points.
                        4) Input processing.
                        5) Message logging.
                        6) CNS Diagnostic Alarms.
                        7) Alarm Handling.
                        8) Control Processor.
                        9) Restart Program.
                        10) Man-Machine Interface-General Functions.
                        11) Graphics Display Generator.
                        12) Types of Displays.
                        13) Alarm/Status Log History.
                        14) Historical Data Collection, Data Retrieval and Trending.
                        15) Report Generator.
                   e.   Applications Software: Detailed training on database, file, display, report, and
                        control configuring provided.

       E.    Software Maintenance Onsite Training:
             1. Training Session Duration: 1instructor weeks.
             2. Number of Training Sessions: One.
             3. Location: Project Site.
             4. Purpose: To provide Owner staff with sufficient training so that they can maintain CNS
                 software on a day-to-day basis.
             5. Content: Similar to factory training except uses installed hardware and software.


                                                   END OF SECTION




WESTERN WAKE PARTNERS, NORTH CAROLINA                                COMPUTER AND NETWORK SUBSYSTEM (CNS)
Western Wake Regional Water Reclamation Facility                                                   1-13442-28
ARCADIS G&M of North Carolina, Inc.                                                         Printed: 6.17.2012
Project No. NC705009.0000

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:16
posted:6/17/2012
language:English
pages:28