Amendment4.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE PAGE OF PAGES

2. AMENDMENT/MODIFICATION NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (If applicable)

6. ISSUED BY CODE 7. ADMINISTERED BY (If other than Item 6) CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code) 9A. AMENDMENT OF SOLICITATION NO.

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended, is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or

(c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS,

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print) 16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA

BY

(Signature of Contracting Officer)

16C. DATE SIGNED

PREVIOUS EDITION UNUSABLE STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

This form was electronically produced by USDA/ARS/OCIO/ADB.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO.

IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date,etc.)

SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

04/06/2010

2/13/2010

J 1 95

Amendment 4

USDA-ARS-MWA

1815 N. University Street Peoria, IL 61604

AG-5114-S-10-AA06

N/A

RECOVERY - DFRC - Repair Mechanical Systems; CCRU-Repair Greenhouse Cooling System, Madison, WI

BID OPENING DATE HAS BEEN EXTENDED TO 2:00 PM CENTRAL TIME ON APRIL 27, 2010.

Second site visit available to contractors to walk thru the project, scheduled for 10:00 AM central time on April 13, 2010 at the Cereal Crops Research Unit, 502 Walnut St., Madison, WI.

Revised Section B Attached. Pages Four through through Eighty-eight reflect revisions and additions to the specifications.

Pages Eighty-nine through Ninety-five of the amendment replaces Davis Bacon Wage Determination WI20080005 dated January 15, 2010 with Davis Bacon Wage Determination WI10005 dated April 2, 2010.

SECTION B- SUPPLIES AND SERVICES AND PRICE/COST

B.1 BID SCHEDULE

In order to be considered responsive, a bidder must bid on all items in the quantities stated in the schedule.

Project Title: RECOVERY – DRFC-Repair Mechanical Systems; CCRU-Repair

Greenhouse Cooling System USDA, ARS, MWA, 1925 Linden Drive W and 504 Walnut Street, Madison, WI Location:

The work includes but is not limited to: furnishing all labor, supervision, materials, tools, equipment, transportation, and other necessary work to furnish and install the replacement of fan coil units serving the Greenhouse and associated control system modifications at the Cereal Crops Research Unit (CCRU) as indicated on the Drawings and Specifications.

BASE BID ITEM

LUMP SUM BID FOR BASE BID ITEM ONLY $_______________________

BID OPTION #1

The work includes but is not limited to: furnishing all labor, supervision, materials, tools, equipment, transportation, and other necessary work to furnish and install the replacement of the domestic hot water heat exchanger, associated piping and components located as indicated on the Drawings and Specifications. Heat exchangers are located in the penthouse of the Dairy Forage Research Center

(DFRC).

LUMP SUM BID FOR BID OPTION #1 ONLY $_______________________

BID OPTION #2

The work includes but is not limited to: furnishing all labor, supervision, materials, tools, equipment, transportation, and other necessary work to furnish and install the replacement of the heating and cooling coils and associated components at AHU-1 as indicated on the Drawings and Specifications.

AHU-1 is located in the penthouse of the Dairy Forage Research Center (DFRC).

LUMP SUM BID FOR BID OPTION #2 ONLY $_______________________

BID OPTION #3

The work includes but is not limited to: furnishing all labor, supervision, materials, tools, equipment, transportation, and other necessary work to furnish and install the replacement of the existing modulating dampers and associated components at AHU-1 as indicated on the

Drawings and Specifications. AHU-1 is located in the penthouse of Dairy Forage Research Center (DFRC).

LUMP SUM BID FOR BID OPTION #3 ONLY $_______________________

BID OPTION #4

The work includes but is not limited to: furnishing all labor, supervision, materials, tools, equipment, transportation, and other necessary work to furnish and install the replacement of the heat exchangers and associated components as indicated on the Drawings and Specifications.

Heat exchangers are located in the penthouse of Dairy Forage Research Center (DFRC) and serve the building's radiation system.

LUMP SUM BID FOR BID OPTION #4 ONLY $_______________________

BID OPTION #5

The work includes but is not limited to: furnishing all labor, supervision, materials, tools, equipment, transportation, and other necessary work to replace existing actuator and pheumatic controls associated with terminal air boxes throughout the DFRC with new DOC controls. Replace existing pheumatic controls and actuators associated with HVAC equipment (AR handling units, heat exchangers, standalone equipment, etc.) throughout the DFRC with new DOC controls. Control replacement shall include all valves associated with HVAC systems (Chillers, Heat Exchanges, etc.)

LUMP SUM BID FOR BID OPTION #5 ONLY $______________________

The period of performance is 210 calendar days from date of issuance of the Notice to Proceed for the Base Bid and any Bid Option(s) exercised at time of award. The period for exercise of options at the proposed prices shall extend until September 30, 2010.

All work shall be in strict accordance with the attached Drawings and Specifications.

United States Department of Agriculture` USDA Task Order No. AG-5114-D-09-0083

Contract No: 53-3K15-4-1500

USDA-ARS Madison, WI Dairy Forage Research Center & Cereal Crops Research Unit

Table of Contents

Specifications

Division 01 – General Requirements

Section 01 00 00 General Requirements

Division 22 – Plumbing

Section 22 05 00 Basic Plumbing Requirements

Section 22 05 05 Plumbing Demolition for Remodeling

Section 22 05 29 Plumbing Supports and Anchors

Section 22 09 00 Instrumentation

Section 22 10 00 Plumbing Piping

Section 22 30 00 Plumbing Equipment

Division 23 – HVAC

Section 23 05 00 Basic HVAC Requirements

Section 23 05 03 Through Penetration Firestopping

Section 23 05 05 HVAC Demolition for Remodeling

Section 23 05 29 HVAC Supports and Anchors

Section 23 05 53 HVAC Identification

Section 23 05 93 Testing, Adjusting and Balancing

Section 23 07 13 Ductwork Insulation

Section 23 07 19 HVAC Piping Insulation

Section 23 09 00 Controls

Section 23 09 00-C Controls

Section 23 09 13 Instrumentation

Section 23 21 00 Hydronic Piping

Section 23 22 00 Steam and Steam Condensate Piping

Section 23 22 18 Steam and Steam Condensate Specialties

United States Department of Agriculture` USDA Task Order No. AG-5114-D-09-0083

Contract No: 53-3K15-4-1500

USDA-ARS Madison, WI Dairy Forage Research Center & Cereal Crops Research Unit

Section 23 31 00 Ductwork

Section 23 33 00 Ductwork Accessories

Section 23 57 00 Heat Exchangers

Section 23 82 00 Terminal Heat Transfer Units

Section 23 82 16 Air Coils

Division 26 – Electrical

Section 26 05 00 Basic Electrical Requirements

Section 26 05 05 Electrical Demolition for Remodeling

Section 26 05 13 Wire and Cable

Section 26 05 31 Boxes

Section 26 05 33 Conduit

Section 26 05 53 Electrical Identification

Section 26 24 19 Motor Control

Section 26 28 13 Fuses

Section 26 28 16 Disconnect Switches

Section 26 29 23 Variable Frequency Drives

END OF TOC

USDA-ARS, Madison, WI 23 09 00 - 1 Bailey Edward Project Number: 0413-08-11

SECTION 23 09 00-C

CONTROLS

TABLE OF CONTENTS

PART 1 - GENERAL

1.1 SECTION INCLUDES

1.2 PRODUCTS FURNISHED BUT NOT INSTALLED UNDER THIS SECTION

1.3 REFERENCES

1.4 AGENCY AND CODE APPROVALS

1.5 ACRONYMS

1.6 SUMMARY

1.7 SYSTEM DESCRIPTION

1.8 SUBMITTALS

1.9 SOFTWARE LICENSE AGREEMENT

1.10 DELIVERY, STORAGE AND HANDLING

1.11 JOB CONDITIONS

1.12 QUALITY ASSURANCE

1.13 WARRANTY

1.14 WARRANTY ACCESS

PART 2 - PRODUCTS

2.1 ACCEPTABLE MANUFACTURERS

2.2 SYSTEM ARCHITECTURE

2.3 NETWORKS

2.4 REMOTE NETWORK ACCESS

2.5 NETWORK AREA CONTROLLER (NAC)

2.6 BACNET FMCS

2.7 TERMINAL AIR BOX (TAB) CONTROLLERS

2.8 DATA COLLECTION AND STORAGE (TRENDING REQUIREMENTS)

2.9 AUDIT LOG

2.10 DATABASE BACKUP AND STORAGE

2.11 GRAPHIC USER INTERFACE SOFTWARE

2.12 WEB BROWSER CLIENTS

2.13 SERVER FUNCTIONS AND HARDWARE

2.14 GRAPHIC USER INTERFACE COMPUTER HARDWARE (DESKTOP)

2.15 SYSTEM PROGRAMMING

2.16 DDE DEVICE INTEGRATION

2.17 MODBUS SYSTEM INTEGRATION

2.18 SOFTWARE

2.19 CONTROL DAMPERS

2.20 DAMPER ACTUATORS

2.21 HYDRONIC CONTROL VALVES

2.22 STEAM CONTROL VALVES

2.23 VALVE ACTUATORS

2.24 VALVE SCHEDULE

2.25 CONTROL INSTRUMENTATION

2.26 WIRING, CABLE, AND RACEWAYS

PART 3 - EXECUTION

3.1 GENERAL INSTALLATION

3.2 CONDUIT, WIRING, AND CABLE INSTALLATION

3.3 DDC INSTALLATION

3.4 COMMISSIONING

3.5 PREPARATION FOR BALANCING

3.6 TEST AND BALANCE COORDINATION

3.7 DEMONSTRATION AND ACCEPTANCE

3.8 TRAINING

3.9 INSTALLATION OF SENSORS

USDA-ARS, Madison, WI 23 09 00 - 2

PART 1 - GENERAL

1.1 SECTION INCLUDES

A. Complete System of Automatic Controls.

B. Control Devices, Components, Wiring and Material.

C. Instructions for Owners.

D. Remodeling.

1.2 PRODUCTS FURNISHED BUT NOT INSTALLED UNDER THIS SECTION

A. Control Valves.

B. Flow Switches.

C. Temperature Sensor Sockets.

D. Gauge Taps.

E. Automatic Dampers.

F. Flow Meters.

1.3 REFERENCES

A. AMCA 500 - Test Methods for Louvers, Dampers and Shutters.

B. ANSI/ASHRAE Standard 135-2001: BACnet® – A Data Communication Protocol for Building Automation and Control Networks, including all amendments.

C. ANSI/NEMA 250 - Enclosures for Electrical Equipment (1000 volts Maximum).

D. ANSI/NFPA 70 - National Electrical Code.

E. ANSI/NFPA 90A - Installation of Air-Conditioning and Ventilation Systems.

F. ASHRAE 62.1 – Ventilation for Acceptable Indoor Air Quality.

G. ASHRAE 85 - Automatic Control Terminology for Heating, Ventilating, Air Conditioning.

H. ASHRAE 90.1 – Energy Standard for Buildings Except Low-Rise Residential Buildings.

1.4 AGENCY AND CODE APPROVALS

A. All products shall have the following agency approvals. Provide verification that the approvals exist for all submitted products with the submittal package.

1. UL-916; Energy Management Systems.

2. C-UL listed to Canadian Standards Association C22.2 No. 205-M1983 “Signal

Equipment.”

3. EMC Directive 89/336/EEC (European CE Mark).

4. FCC, Part 15, Subpart J, Class A Computing Devices.

1.5 ACRONYMS

A. Acronyms used in this specification are as follows:

1. B-AAC BACnet Advanced Application Controller.

2. B-ASC BACnet Application Specific Controller.

3. BTL BACnet Testing Laboratories.

4. DDC Direct Digital Controls.

5. FMCS Facility Management and Control System.

6. GUI Graphic User Interface.

USDA-ARS, Madison, WI 23 09 00 - 3

7. IBC Interoperable BACnet Controller.

8. IDC Interoperable Digital Controller.

9. LAN Local Area Network.

10. NAC Network Area Controller.

11. ODBC Open DataBase Connectivity.

12. OOT Object Oriented Technology.

13. OPC Open Connectivity via Open Standards.

14. PICS Product Interoperability Compliance Statement.

15. PMI Power Measurement Interface.

16. POT Portable Operator’s Terminal.

17. TCS Temperature Control System.

18. WAN Wide Area Network.

19. WBI Web Browser Interface.

1.6 SUMMARY

A. Provide new standalone FMCS for this project.

B. Contractor shall furnish all labor, materials, equipment, and service necessary for a complete and operating Temperature Control System (TCS) and Facility Management and Control System (FMCS) using Direct Digital Controls as shown on the drawings and as described herein.

C. All labor, material, equipment and software not specifically referred to herein or on the plans that are required to meet the intent of this specification shall be provided without additional cost to the Owner.

D. The Owner shall be the named license holder of all software associated with any and all incremental work on the project.

1.7 SYSTEM DESCRIPTION

A. The entire TCS shall be comprised of a network of interoperable, standalone digital controllers communicating via the following protocol to an NAC. Temperature Control System products shall be as specified below.

B. The FMCS shall include Network Area Controller or Controllers (NAC) within each facility.

The NAC shall connect to the Owner’s local or wide area network, depending on configuration. Provide access to the system, either locally in each building or remotely from a central site or sites, through standard Web browsers, via the Internet, and/or via local area network.

C. Provide materials and labor necessary to connect factory supplied control components.

D. Provide central and remote hardware, software, and interconnecting wire and conduit.

E. The FMCS shall include automated alarming software capable of calling e-mail compatible cellular telephones and pagers. The e-mail alarm paging system shall be able to segregate users, time schedules, and equipment and be capable of being programmed by the Owner.

F. For the dedicated configuration tool provided, it is preferable that it be launched from within the applicable Network Management Software. If not, include any software required for controller configuration as a leave-behind tool with enough license capability to support the installation.

G. For each operator workstation provided, furnish one legal copy of all software tools, configuration tools, management tools, and utilities used during system commissioning

USDA-ARS, Madison, WI 23 09 00 - 4 and installation. All tools shall be readily available in the market. Contractor shall convey to the Owner all software tools and their legal licenses at project closeout.

1.8 SUBMITTALS

A. Equipment Coordination:

1. The Contractor shall obtain approved equipment submittals from other contractors to determine equipment wiring connections, to choose appropriate controllers, and to provide programming.

2. Control valve selections shall be based on flow rates shown in approved shop drawings.

3. Coordinate the control interface of all equipment with the equipment manufacturers prior to submittal submission.

B. Shop Drawings:

1. Submit shop drawings per Section 23 05 00. In addition, submit an electronic copy of the shop drawings in Adobe Acrobat (.pdf) format to the Owner for review.

2. Cross-reference all control components and point names in a single table located at the beginning of the submittal with the identical nomenclature used in this section.

3. Submittal shall also include a trunk cable schematic diagram depicting operator workstations, control panel locations and a description of the communication type, media and protocol.

4. System Architecture: Provide riser diagrams of wiring between central control unit and all control panels. This shall include specific protocols associated with each level within the architecture. Identify all interface equipment between CPU and control panels. The architecture shall include interface requirements with other systems including, but not limited to, security systems, lighting control, fire alarm, elevator status, and power monitoring system.

5. Diagrams shall include:

a. Wiring diagrams and layouts for each control panel showing all termination numbers.

b. Schematic diagrams for all control, communication, and power wiring.

Provide a schematic drawing of the central system installation. Label all cables and ports with computer manufacturers’ model numbers and functions. Show all interface wiring to the control system.

c. Identification of all control components connected to emergency power.

d. Schematic diagrams for all field sensors and controllers.

e. A schematic diagram of each controlled system. The schematics shall have all control points labeled. The schematics shall graphically show the location of all control elements in the system.

f. A schematic wiring diagram for each controlled system. Each schematic shall have all elements labeled. Where a control element is the same as

USDA-ARS, Madison, WI 23 09 00 - 5 that shown on the control system schematic, label it with the same name.

Label all terminals.

g. A tabular instrumentation list for each controlled system. The table shall show element name, type of device, manufacturer, model number and product data sheet number.

h. All installation details and any other details required to demonstrate that the system will function properly.

i. All interface requirements with other systems.

6. The network infrastructure shall conform to the published guidelines for wire type, length, number of nodes per channel, termination, and other relevant wiring and infrastructure criteria as published. The number of nodes per channel shall be no more than 80% of the defined segment (logical or physical) limit in order to provide future system enhancement with minimal infrastructure modifications.

7. Sequences: Submit a complete description of the operation of the control system, including sequences of operation. The description shall include and reference a schematic diagram of the controlled system. The wording of the control sequences in the submittal shall match verbatim that included in the construction documents to ensure there are no sequence deviations from that intended by the Engineer. Clearly highlight any deviations from the specified sequences on the submittals.

8. Points List Schedule: Submit a complete points list of all points to be connected to the TCS and FMCS. The points list for each system controller shall include both inputs and outputs (I/O), point number, the controlled device associated with the I/O point, the location of the I/O device, and reference drawings. Where a control point is the same as that shown on the control system schematic, label it with the same name. Points list shall specifically identify alarms, trends, event history, archive, totalization, graphic points, and all mapped points from other systems (security systems, lighting control, fire alarm, etc.). Provide points lists, point naming convention, and factory support information for systems provided and integrated into the FMCS.

9. Damper Schedule: Schedule shall include a separate line for each damper and a column for each of the damper attributes:

a. Damper Identification Tag.

b. Location.

c. Damper Type.

d. Damper Size.

e. Duct Size.

f. Arrangement.

g. Blade Type.

h. Velocity.

i. Pressure Drop.

j. Fail Position.

k. Actuator Identification Tag.

l. Actuator Type.

m. Mounting.

10. Valve Schedule: Valve manufacturer shall size valves and create a valve schedule. Schedule shall include a separate line for each valve and a column for each of the valve attributes:

a. Valve Identification Tag.

b. Location.

c. Valve Type.

USDA-ARS, Madison, WI 23 09 00 - 6

d. Valve Size.

e. Pipe Size.

f. Configuration.

g. Flow Characteristics.

h. Capacity.

i. Valve CV.

j. Design Pressure Drop.

k. Pressure Drop at Design Flow.

l. Fail Position.

m. Close-off Pressure.

n. Valve and Actuator Model Number and Type.

11. Airflow Measuring Station Schedule:

a. The manufacturer’s authorized representative shall prepare the airflow measuring station submittal, or review and approve in writing the submittal prepared by the Contractor prior to submission to the engineer and prior to installation. The representative shall review air handling equipment submittals and duct fabrication drawings to ensure that all AFMS locations meet the appropriate parameters to achieve proper installation and the specified accuracy. Comply with all manufacturer’s installation requirements including straight up and downstream duct lengths. Install airflow straighteners if required by the manufacturer based on installation constraints. The Engineer shall be notified for approval of any deviations.

b. Submit product data sheets for airflow measuring devices indicating minimum placement requirements, sensor density, sensor distribution, and installed accuracy to the host control system.

c. Submit installation, operation, and maintenance documentation.

12. Product Data Sheets: Required for each component that includes: unique identification tag that is consistent throughout the submittal, manufacturer’s description, technical data, performance curves, installation/maintenance instructions, and other relevant items. When manufacturer’s literature applies to a product series rather than a specific product, the data specifically applicable to the project shall be highlighted or clearly indicated by other means. Each submitted piece of literature and drawings shall clearly reference the specification and/or drawing that the submittal is to cover. General catalogs shall not be accepted as cutsheets to fulfill submittal requirements.

13. Provide PICS files indicating the BACnet® functionality and configuration of each device.

14. Provide documentation of submitted products that have been tested and listed by the BACnet Testing Laboratory (BTL), or provide a letter on the manufacturer’s company letterhead indicating the anticipated date by which testing is expected to be completed. If, for any reason, BTL testing and listing has not been completed, a written commitment to upgrade installed controls to a version that meets BTL testing and listing requirements in the event that problems are found during BTL testing is required.

15. Graphic Display: Include a sample graphic of each system and component identified in the points list with a flowchart (site map) indicating how the graphics are to be linked to each other for system navigation.

16. Software: A list of operating system software, operator interface software, color graphic software, and third-party software.

USDA-ARS, Madison, WI 23 09 00 - 7

17. Control System Demonstration and Acceptance: Provide a description of the proposed process, along with all reports and checklists to be used.

18. Clearly identify work by others in the submittal.

19. Quantities of items submitted may be reviewed but are the responsibility of the Contractor to verify.

C. Operation and Maintenance Manual:

1. In addition to the requirements of Section 23 05 00, submit an electronic copy of the O&M manuals in PDF format.

2. Provide three complete sets of manuals.

3. Each O&M manual shall include:

a. Table of contents with indexed tabs dividing information as outlined below.

b. Definitions: List of all abbreviations and technical terms with definitions.

c. Warranty Contacts: Names, addresses, and 24-hour telephone numbers of contractors installing equipment and controls and service representatives of each.

d. Licenses, Guarantees, and Warranties: Provide documentation for all equipment and systems.

e. System Components: Alphabetical list of all system components, with the name, address, and telephone number of the vendor.

f. Operating Procedures: Include procedures for operating the control systems; logging on/off; enabling, assigning, and reporting alarms;

generating reports; collection, displaying, and archiving of trended data;

overriding computer control; event scheduling; backing up software and data files; and changing setpoints and other variables.

g. Programming: Description of the programming language (including syntax), statement descriptions (including algorithms and calculations used), point database creation and modification, program creation and modification, and use of the editor.

h. Engineering, Installation, and Maintenance: Explain how to design and install new points, panels, and other hardware; recommended preventive maintenance procedures for all system components, including a schedule of tasks (inspection, cleaning, calibration, etc.), time between tasks, and task descriptions; how to debug hardware problems; and how to repair or replace hardware. A list of recommended spare parts.

i. Original Software: Complete original issue CDs for all software provided, including operating systems, programming language, operator workstation software, and graphics software.

j. Software: One set of CDs containing an executable copy of all custom software created using the programming language, including the setpoints, tuning parameters, and object database.

k. Graphics: A glossary or icon symbol library detailing the function of each graphic icon and graphics creation and modification. One set of CDs containing files of all color graphic screens created for the project.

USDA-ARS, Madison, WI 23 09 00 - 8

D. Training Manual:

1. Provide a course outline and training manuals for each training class.

E. Record Documents:

1. Submit record documentation per Section 23 05 00.

2. Provide a complete set of “as-built” drawings and application software on CDs.

Provide drawings as AutoCAD™ or Visio™ compatible files. Provide two copies of the “as-built” drawings with revisions clearly indicated in addition to the documents on compact disk. All as-built drawings shall also be installed on the FMCS server in a dedicated directory. Provide all product data sheets in PDF format.

3. Submit two hard copies and one electronic copy of as-built versions of the shop drawings, including product data and record drawings with revisions clearly indicated. Provide floor plans showing actual locations of control components including panels, thermostats, sensors, and hardware.

4. Provide all completed testing and commissioning reports and checklists, along with all trend logs for each system identified in the points lists.

5. Submit printouts of all graphic screens with current values (temperatures, pressures, etc.) to the A/E verifying completion and proper operation of all points.

1.9 SOFTWARE LICENSE AGREEMENT

A. The Owner shall be the named license holder of all software associated with any and all incremental work on the project(s). In addition, the Owner shall receive ownership of all job-specific configuration documentation, data files, configuration tools, and application-level software developed for the project. This shall include, but is not limited to, all custom, job-specific software code and documentation for all configuration and programming that is generated for a given project and/or configured for use with the NAC, FMCS Server(s), and any related LAN/WAN/intranet and/or Internet connected routers and devices. Provide the Owner with all required IDs and passwords for access to any component or software program. The Owner shall determine which organizations shall be named in the SI organization ID (“orgid”) of all software licenses. Owner shall be free to direct the modification of the “orgid” in any software license, regardless of supplier.

1.10 DELIVERY, STORAGE AND HANDLING

A. Provide factory-shipping cartons for each piece of equipment and control device.

Maintain cartons through shipping, storage, and handling as required to prevent equipment damage. Store equipment and materials inside and protected from weather.

B. Factory-Mounted Components: Where control devices specified in this section are indicated to be factory mounted on equipment, arrange for shipping control devices to unit manufacturer.

1.11 JOB CONDITIONS

A. Cooperation with Other Trades: Coordinate the Work of this section with that of other sections to ensure that the Work will be carried out in an orderly fashion. It is the Contractor's responsibility to check the Contract Documents for possible conflicts between the Work of this section and that of other crafts in equipment location; pipe, duct and conduit runs; electrical outlets and fixtures; air diffusers; and structural and architectural features.

1.12 QUALITY ASSURANCE

USDA-ARS, Madison, WI 23 09 00 - 9

A. Manufacturer: Company specializing in manufacturing the products specified in this Section with minimum five years experience.

B. Contractor: Company specializing in the work of this section.

C. Technician: Minimum five years experience installing commercial temperature control systems.

1.13 WARRANTY

A. Refer to Section 23 05 00 for warranty requirements.

B. Within the warranty period, any defects in the work provided under this section due to faulty materials, methods of installation or workmanship shall be promptly (within 48 hours after receipt of notice) repaired or replaced by the Contractor at no expense to the Owner.

C. Warranty requirements include furnishing and installing all DDC software upgrades issued by the manufacturer during the one-year warranty period.

D. Update all software and back-ups during warranty period and all user documentation on the Owner’s archived software disks.

1.14 WARRANTY ACCESS

A. The Owner shall grant to this Contractor reasonable access to the TCS and FMCS during the warranty period.

PART 2 - PRODUCTS

2.1 ACCEPTABLE MANUFACTURERS

A. Alerton.

B. Automated Logic: WebCTRL.

C. Delta Controls: ORCA.

D. Honeywell.

E. Johnson Controls: Metasys Extended Architecture.

F. KMC.

G. Siemens Building Technologies: APOGEE.

H. TAC Andover.

I. Trane Summit.

J. Approved Equal.

* Above manufacturers are acceptable for work at Dairy Forage Research Center.

2.2 SYSTEM ARCHITECTURE

A. General:

1. The Temperature Control System (TCS) and Facility Management Control System (FMCS) shall consist of a network of interoperable, standalone digital controllers, a computer system, graphic user interface software, printers, network devices, valves, dampers, sensors, and other devices as specified herein.

2. The installed system shall provide secure password access to all features, functions and data contained in the overall FMCS.

B. Open, Interoperable, Integrated Architectures:

USDA-ARS, Madison, WI 23 09 00 - 10

1. All components and controllers supplied under this Division shall be true “peer-to-peer” communicating devices. Components or controllers requiring “polling” by a host to pass data are not acceptable.

2. The supplied system must be able to access all data using standard Web browsers without requiring proprietary operator interface and configuration programs. An Open DataBase Connectivity (ODBC) or Structured Query Language (SQL) compliant server database is required for all system database parameter storage. This data shall reside on a supplier-installed server for all database access. Systems requiring proprietary database and user interface programs are not acceptable.

3. Hierarchical or “flat” topologies are required to have system response times as indicated below and to manage the flow and sharing of data without unduly burdening the customer’s internal intranet network.

a. Maximum acceptable response time from any alarm occurrence (at the point of origin) to the point of annunciation shall not exceed 5 seconds for network connected user interfaces.

b. Maximum acceptable response time from any alarm occurrence (at the point of origin) to the point of annunciation shall not exceed 60 seconds for remote or dial-up connected user interfaces.

2.3 NETWORKS

A. The Local Area Network (LAN) shall be a 100 megabits/sec Ethernet network supporting BACnet, Java, XML, HTTP, and SOAP. Provide support for multiple Network Area Controllers (NACs), user workstations and, if specified, a local server.

B. Contractor shall provide LAN that is independent of Building IT infrastructure. Contractor shall interconnect all control equipment requiring an Ethernet connection. Connection to Owner’s IT system shall be a single location coordinated with Owner.

C. Local area network minimum physical and media access requirements:

1. Ethernet; IEEE Standard 802.3.

2. Cable; 100 Base-T, UTP-8 wire, Category 5.

3. Minimum throughput; 100 Mbps.

D. Communication conduits shall not be installed closer than six feet from 110VAC or higher transformers or run parallel within six feet of electrical high power cables. Route the cable as far from interference generating devices as possible. Where communication wire must cross 110VAC or higher wire, it must do so at right angles.

E. Ground all shields (earth ground) at one point only to eliminate ground loops. Provide all shield grounding at the controller location, with the shield at the sensor/device end of the applicable wire being left long and “safed” off in an appropriate manner.

F. There shall be no power wiring in excess of 30 VAC rms run in conduit with communications wiring. In cases where signal wiring is run in conduit with communication wiring, run all communication wiring and signal wiring using separate twisted pairs (24awg) in accordance with the manufacturer’s wiring practices.

2.4 REMOTE NETWORK ACCESS

A. For Local Area Network installations, provide access to the LAN from a remote location via the Internet. The Owner shall provide a connection to the Internet to enable this access via high speed cable modem, asynchronous digital subscriber line (ADSL) modem, ISDN line, T1 Line or via the customer’s intranet to a corporate server providing

USDA-ARS, Madison, WI 23 09 00 - 11 access to an Internet Service Provider (ISP). Customer agrees to pay monthly access charges for connection and ISP.

2.5 NETWORK AREA CONTROLLER (NAC)

A. The Contractor shall supply one or more Network Area Controllers (NAC) as part of this contract. Number of NACs required depends on the type and quantity of devices provided under Divisions 23 and 26. The Contractor shall determine the quantity and type of devices.

B. Each NAC shall provide the interface between the LAN or WAN and the field control devices and shall provide global supervisory control functions over the control devices connected to the NAC. It shall execute application control programs to provide:

1. Calendar functions.

2. Scheduling.

3. Trending.

4. Alarm monitoring and routing.

5. Time synchronization.

6. Integration of all controller data.

7. Network Management functions.

C. The Network Area Controller shall provide the following hardware features as a minimum:

1. One Ethernet Port – 10/100 Mbps.

2. One RS-232 port.

3. One LonWorks Interface Port – 78KB FTT-10A (for LonWorks systems only).

4. One RS-485 port.

5. Battery backup.

6. Flash memory for long-term data backup. (If battery backup or flash memory is not supplied, the controller shall contain a hard disk with at least 1 gigabyte storage capacity.)

7. The NAC must be capable of operation over a temperature range of 32°F to 122°F.

8. The NAC must be capable of withstanding storage temperatures of between 0°F and 158°F.

9. The NAC must be capable of operation over a humidity range of 5% RH to 95% RH, non-condensing.

D. The NAC shall provide multiple user access to the system and support for ODBC or SQL.

Databases resident on the NAC shall be ODBC-compliant or must provide an ODBC data access mechanism to read and write data stored within it.

E. The NAC shall support standard Web browser access via the Internet or an intranet and a minimum of five (5) simultaneous users.

F. Event Alarm Notification and Actions:

1. The NAC shall provide alarm recognition, storage; routing, management, and analysis to supplement distributed capabilities of equipment or application specific controllers.

2. The NAC shall be able to route any alarm condition to any defined user location whether connected to a LAN, remote via dial-up telephone connection, or WAN.

3. Alarm generation shall be selectable for annunciation type and acknowledgement requirements including, but not limited to:

a. Alarm.

b. Normal.

USDA-ARS, Madison, WI 23 09 00 - 12

4. Provide for the creation of a minimum of eight alarm classes with different routing and acknowledgement properties, e.g. security, HVAC, Fire, etc.

5. Provide timed (scheduled) routing of alarms by class, object, group, or node.

6. Provide alarm generation from binary object “runtime” and/or event counts for equipment maintenance. The user shall be able to reset runtime or event count values with appropriate password control.

G. Treat control equipment and network failures as alarms and annunciated.

H. Annunciate alarms in any of the following manners as defined by the user:

1. Screen message text.

2. E-mail of the complete alarm message to multiple recipients. Provide the ability to route and e-mail alarms based on:

a. Day of week.

b. Time of day.

c. Recipient.

3. Pagers via paging services that initiate a page on receipt of e-mail message.

4. Graphic with flashing alarm object(s).

5. Printed message, routed directly to a dedicated alarm printer.

I. The FMCS shall record the following for each alarm:

1. Time and date.

2. Location (building, floor, zone, office number, etc.).

3. Equipment tag.

4. Acknowledge time, date, and user who issued acknowledgement.

5. Number of occurrences since last acknowledgement.

J. Give defined users proper access to acknowledge any alarm.

K. A log of all alarms shall be maintained by the NAC and/or a server (if configured in the system) and shall be available for review by the user.

L. Provide a “query” feature to allow review of specific alarms by user-defined parameters.

M. A separate log for system alerts (controller failures, network failures, etc.) shall be provided and available for review by the user.

N. An error log to record invalid property changes or commands shall be provided and available for review by the user.

2.6 BACNET FMCS

A. The intent of this specification is to provide a peer-to-peer networked, standalone, distributed control system with the capability to integrate ANSI/ASHRAE Standard 135-2001 BACnet, MODBUS, OPC, and other open and proprietary communication protocols in one open, interoperable system.

B. The supplied computer software shall employ object-oriented technology (OOT) for representation of all data and control devices in the system. Adherence to industry standards including the latest ANSI/ASHRAE Standard 135 (BACnet) to assure

USDA-ARS, Madison, WI 23 09 00 - 13 interoperability between all system components is required. For each BACnet device, the device supplier must provide a PICS document showing the installed device’s compliance level. Minimum compliance is Level 3; with the ability to support data read and write functionality. Physical connection of BACnet devices shall be via Ethernet (BACnet Ethernet/IP) and/or RS-485 (BACnet MSTP).

C. Interoperable BACnet Controller (IBC):

1. Controls shall be microprocessor based Interoperable BACnet Controllers (IBC) in accordance with the latest ANSI/ASHRAE Standard 135. Provide IBCs for unit ventilators, fan coils, heat pumps, terminal air boxes (TAB) and other applications. The application control program shall reside in the same enclosure as the input/output circuitry that translates the sensor signals. Provide a PICS document showing the installed system’s compliance level to ANSI/ASHRAE Standard 135. Minimum compliance is Level 3.

2. The IBCs shall be listed by the BACnet Testing Laboratory (BTL) as follows:

a. BACnet Building Controller(s) (B-BC).

b. BACnet Advanced Application Controller(s) (B-ACC).

c. BACnet Application Specific Controller(s) (B-ASC).

3. The IBCs shall communicate with the NAC via an Ethernet connection at a baud rate of not less than 10 Mbps.

4. Each IBC sensor shall connect directly to the IBC and shall not use any of the I/O points of the controller. The IBC Sensor shall provide a two-wire connection to the controller that is polarity and wire type insensitive. The IBC sensor shall provide a communications jack for connection to the BACnet communication trunk to which the IBC controller is connected. The IBC sensor, the connected controller, and all other devices on the BACnet bus shall be accessible by the

POT.

5. All IBCs shall be fully application programmable and shall at all times maintain their BACnet Level 3 compliance. Controllers offering application selection only (non-programmable) require a 10% spare point capacity to be provided for all applications. Store all control sequences within or programmed into the IBC in non-volatile memory that does not depend on a battery to be retained.

6. The Contractor supplying the IBCs shall provide documentation for each device, with the following information at a minimum:

a. BACnet Device; MAC address, name, type and instance number.

b. BACnet Objects; name, type and instance number.

7. It is the responsibility of the Contractor to ensure that the proper BACnet objects are provided in each IBC.

D. Object Libraries

1. A standard library of objects shall be included for development and setup of application logic, user interface displays, system services, and communication networks.

2. The objects in this library shall be capable of being copied and pasted into the user’s database and shall be organized according to their function. In addition, the user shall have the capability to group objects created in their application and store the new instances of these objects in a user-defined library.

3. In addition to the standard libraries specified here, the system supplier shall maintain an on-line accessible (over the Internet) library, available to all

USDA-ARS, Madison, WI 23 09 00 - 14 registered users, to provide new or updated objects and applications as they are developed.

4. All control objects shall conform to the control objects specified in the BACnet specification.

5. The library shall include applications or objects for the following functions, at a minimum:

a. Scheduling Object: The schedule must conform to the schedule object as defined in the BACnet specification, providing seven-day plus holiday and temporary scheduling features and a minimum of 10 on/off events per day. Data entry to be by graphic sliders to speed creation and selection of on-off events.

b. Calendar Object: The calendar must conform to the calendar object as defined in the BACnet specification, providing 12-month calendar features to allow for holiday or special event data entry. Data entry to be by graphic “point-and-click” selection. This object must be “linkable” to any or all scheduling objects for effective event control.

c. Override Object: Provide override object that is capable of restarting equipment turned off by other energy saving programs to maintain occupant comfort or for equipment protection.

d. Start-Stop Time Optimization Object: Provide a start-stop time optimization object to start equipment just early enough to bring space conditions to desired conditions by the scheduled occupancy time. Also, allow equipment to be stopped before the scheduled unoccupied time just far enough ahead to take advantage of the building’s “flywheel” effect for energy savings. Provide automatic tuning of all start-stop time object properties based on historical performance.

e. Demand Limiting Object: Provide a demand-limiting object that is capable of controlling demand for any selected energy utility (electric, oil, gas, etc.). The object shall be able to monitor a demand value and predict (using a sliding window prediction algorithm) the demand at the end of the user-defined interval period (1 to 60 minutes). This object shall also accommodate a utility meter time sync pulse for fixed interval demand control. Upon a prediction that will exceed the user-defined demand limit (supply a minimum of 6 per day), the demand limiting object shall issue shed commands to either turn off user specified loads or modify equipment setpoints to provide the desired energy reduction. If the list of sheddable equipment is not enough to reduce the demand to below the setpoint, display a message on the user’s screen (as an alarm) instructing the user to take manual actions to maintain the desired demand. The shed lists are specified by the user and shall be selectable to be shed in either a fixed or rotating order to control which equipment is shed the most often. Upon suitable reductions in demand, the demand-limiting object shall restore the equipment that was shed in the reverse order in which it was shed. Each sheddable object shall have a minimum and maximum shed time property to provide both equipment protection and occupant comfort.

6. The library shall include control objects for the following functions:

a. Analog Input Object: Minimum requirement is to comply with the BACnet standard for data sharing. Allow high, low and failure limits to be assigned for alarming. Also, provide a time delay filter property to prevent nuisance alarms caused by temporary excursions above or below the user defined alarm limits.

USDA-ARS, Madison, WI 23 09 00 - 15

b. Analog Output Object: Minimum requirement is to comply with the BACnet standard for data sharing.

c. Binary Input Object: Minimum requirement is to comply with the BACnet standard for data sharing. The user must be able to specify either input condition for alarming. This object must also include the capability to record equipment runtime by counting the amount of time the hardware input is in an “on” condition. The user must be able to specify either input condition as the “on” condition.

d. Binary Output Object: Minimum requirement is to comply with the BACnet standard for data sharing. Properties to enable minimum on and off times for equipment protection as well as start-to-start delay must be provided. Incorporate the BACnet Command Prioritization priority scheme to allow multiple control applications to execute commands on this object with the highest priority command being invoked. Provide 16 levels of priority as a minimum. Systems not employing the BACnet method of contention resolution are not acceptable.

e. PID Control Loop Object: Minimum requirement is to comply with the BACnet standard for data sharing. Each individual property must be adjustable to allow proportional control only, or proportional with integral control, or proportional, integral and derivative control.

f. Comparison Object: Allow a minimum of two analog objects to be compared to select either the highest, lowest, or equality between the two linked inputs. Also, allow limits to be applied to the output value for alarm generation.

g. Math Object: Allow a minimum of four analog objects to be tested for the minimum or maximum, or the sum, difference, or average of linked objects. Also, allow limits to be applied to the output value for alarm generation.

h. Custom Programming Objects: Provide a blank object template for the creation of new custom objects to meet specific user application requirements. This object must provide a simple BASIC-like programming language that is used to define object behavior. Provide a library of functions including, but not limited to, math and logic functions and string manipulation. Also, provide a comprehensive on-line debug tool to allow complete testing of the new object. Allow new objects to be stored in the library for reuse.

i. Interlock Object: Provide an interlock object that provides a means of coordination of objects within a piece of equipment, such as an air handler or other similar types of equipment. An example is to link the return fan to the supply fan such that, when the supply fan is started, the return fan object is also started automatically without the user having to issue separate commands or to link each object to a schedule object. In addition, the control loops, damper objects, and alarm monitoring (such as return air, supply air, and mixed air temperature objects) will be inhibited from alarming during a user-defined period after startup to allow for stabilization. When the air handler is stopped, the interlocked return fan is also stopped, the outside air damper is closed, and other related objects within the air handler unit are inhibited from alarming, thereby eliminating nuisance alarms during the off period.

j. Temperature Override Object: Provide an object whose purpose is to override a binary output to an “on” state in the event a user-specified high or low limit value is exceeded. Link this object to the desired binary

USDA-ARS, Madison, WI 23 09 00 - 16 output object as well as to an analog object for temperature monitoring to cause the override to be enabled. This object will execute a start command at the Temperature Override level of start/stop command priority, unless changed by the user.

k. Composite Object: Provide a container object that allows a collection of objects representing an application to be encapsulated to protect the application from tampering or to more easily represent large applications.

This object must have the ability to allow the user to select the appropriate parameters of the “contained” application that are represented on the graphic shell of this container.

7. The object library shall include objects to support the integration of devices connected to the Network Area Controller (NAC). Provide the following as part of the standard library included with the programming software:

a. LonMark/LonWorks…