FBODaily.com | FedBizOpps: PRESOL | E | Replace Universal Network Controller

FBO DAILY - FEDBIZOPPS ISSUE OF JUNE 15, 2016 FBO #5318
SOLICITATION NOTICE

E -- Replace Universal Network Controller

Notice Date: 6/13/2016
Notice Type: Combined Synopsis/Solicitation
NAICS: 238210 — Electrical Contractors and Other Wiring Installation Contractors
Contracting Office: Agricultural Research Service - Plains Area
ZIP Code: 00000
Solicitation Number: AG-6612-S-16-0001
Archive Date: 7/15/2016
Point of Contact: Connie M Pederson, Phone: 7012391204
E-Mail Address: connie.pederson@ars.usda.gov
(connie.pederson@ars.usda.gov)
Small Business Set-Aside: N/A
Description: This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in Subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; quotes are being requested and a written solicitation will not be issued. Solicitation number AG-6612-S-16-0001 is issued as a request for quotation (RFQ). The solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular 2005-73. The associated NAICS code is 238210. This acquisition is for the following item as identified in the Contract Line Item Number (CLIN): SECTION 01 11 00 SUMMARY OF WORK 04/16 PART 1 GENERAL 1.1 WORK COVERED BY CONTRACT DOCUMENTS 1.1.1 Project Description The work includes all necessary labor, equipment and materials to supply and install a Universal Network Controller (UNC) including programming graphics on the Building Automation System (BAS) at the Northern Crops Science Lab (NCSL). The existing UNC has been discontinued by the manufacturer and is no longer supported. Site visit with Contracting Officer's Representative (COR) can be arranged, if necessary. 1.1.2 Location The work shall be located at the USDA ARS NCSL, 1307 18th Street North Fargo, North Dakota approximately as indicated. The exact location will be shown by the COR. 1.1.3 Remove UNC, install and program new UNC Contractor shall have software licenses for Schneider Electric Workplace Tech Tool and Schneider Electric Workplace Pro Tool. Contractor shall be factory trained and authorized for approved software. Contractor shall be regional representative of Schneider Electric I/A Series and Distech Controls systems. Provide all equipment, materials and labor to remove the UNC board in room 203. The metal enclosure shall be reused. a. New UNC shall meet the following: 1. Java based controller/server- Distech Controls EC-BOS-7 or equivalent. 2. Powered by NiagaraAX framework. 3. Processor: IBM 440Epx Power PC 667 MHZ processor. 4. Memory: 1 GB DDR-2 RAM and 512 MB serial flash. 5. Battery backup: shutdown begins within 10 seconds. 6. Real-time clock: 1 year backup via battery at a full charge. 7. Communications, operating system, chassis, environment, and agency listings: Equal or greater than page 5 of 05DI-DSBS7AX-13. b. Program new UNC- Manually re-engineer existing R2 application to run in G3 application environment excluding mag chiller optimization package related points (see paragraph 1.1.4). 1. COR shall approve graphics. 2. Program the BAS alarms (see Section 23 09 23.13 20). 3. Utilize embedded EC-gfx program. Clean up site. 1.1.4 Alternate 1- Program existing mag chiller optimization package points Program existing mag chiller optimization package points into new UNC. Mag chiller optimization related points shall be manually re-engineered from existing R2 application to run in G3 application environment. Contractor shall submit alternate 1 as separate line item on bid. 1.1.5 Alternate 2- EC-NetAX Supervisor Provide and install centralized data logging, archiving and alarming workstation. Data memory shall be "ring type" (newest data overwrites the oldest). Advise COR how much memory (GB) is needed to store data for 1 year (including NCSL and BRL). USDA shall provide PC and/or server, monitor, keyboard and mouse. Contractor shall submit alternate 2 as separate line item on bid. 1.1.6 Alternate 3- EC-NetAX EnerVue Provide and install energy monitoring, reporting and personalized energy dashboard. USDA shall provide kiosk hardware(PC, monitor, keyboard and mouse, as necessary). Contractor shall submit alternate 3 as separate line item on bid. a. Energy dashboard shall contain the following: 1. Header- Date, time, building name and optional text. 2. KWh consumed during previous week. 3. Colored graph with weekday on x-axis and 15 minute KWh interval data on y-axis (current week one color and previous week a different color). 4. Outdoor conditions- temperature and relative humidity. 5. The dashboard shall provide a "kiosk mode" for publication of Dashboard views to a local monitor or kiosk. Provide the ability for user to build custom Screen Tip or informational "pop-up" window to give additional insight on a kiosk slide for the building occupants (EC-NetAX EnerVue p. 2). 6. Real time Gauges- Gauge viewlets allow the USDA to track analog values such as room temperature (quantity 5), compressed air pressure (quantity 1), humidity (quantity 5) and level (quantity 0, for future use). 7. Import a two (2) year history of utility bill data (water, steam and electricity), degree days and real-time electric meter data from chiller. b. Initial dashboard configuration and training session shall be provided by the contractor for USDA staff. The initial configuration shall include: 1. Executive View. 2. Demand Management View. 3. Preferred Guest View. 1.1.7 Alternate 4- Upgrade firmware on controllers to increase network security Upgrade firmware on quantity fourteen (14) controllers. Some controllers are located at the BRL and some are at the NCSL. These controllers are showing up on IT vulnerability scans and upgrading firmware will fix IT vulnerability. 1.2 OCCUPANCY OF PREMISES Building(s) will be occupied during performance of work under this Contract. Before work is started, the Contractor shall arrange with the Contracting Officer a sequence of procedure, means of access, space for storage of materials and equipment, and use of approaches, corridors, and stairways. 1.3 EXISTING WORK In addition to "FAR 52.236-9, Protection of Existing Vegetation, Structures, Equipment, Utilities, and Improvements": a. Remove or alter existing work in such a manner as to prevent injury or damage to any portions of the existing work which remain. b. Repair or replace portions of existing work which have been altered during construction operations to match existing or adjoining work, as approved by the Contracting Officer. At the completion of operations, existing work shall be in a condition equal to or better than that which existed before new work started. PART 2 PRODUCTS Not used. PART 3 EXECUTION Project shall be completed within 90 days after notice to proceed. Bid shall have breakdown of materials and labor. -- End of Section -- SECTION 23 09 23.13 20 BACnet DIRECT DIGITAL CONTROL SYSTEMS FOR HVAC 08/09 PART 1 GENERAL 1.1 REFERENCES The publications listed below form a part of this specification to the extent referenced. The publications are referred to in the text by the basic designation only. AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING ENGINEERS (ASHRAE) ASHRAE 135 (2012; Errata 2013) BACnet-A Data Communication Protocol for Building Automation and Control Networks ASME INTERNATIONAL (ASME) ASME B31.1 (2012; INT 2-6, 8-10, 13, 15, 17-25, 27-31 and 42-46) Power Piping CONSUMER ELECTRONICS ASSOCIATION (CEA) CEA-709.1-C (2010) Control Network Protocol Specification INTERNATIONAL ORGANIZATION FOR STANDARDIZATION (ISO) ISO 8802-3 (2000) Information Technology - Telecommunications and Information Exchange Between Systems - Local and Metropolitan Area Networks - Specific Requirements - Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD)Access Method and Physical Layer Specifications NATIONAL FIRE PROTECTION ASSOCIATION (NFPA) NFPA 70 (2014) National Electrical Code UNDERWRITERS LABORATORIES (UL) UL 506 (2008; Reprint Oct 2012) Specialty Transformers 1.2 DEFINITIONS 1.2.1 ANSI/ASHRAE Standard 135 ANSI/ASHRAE Standard 135: BACnet - A Data Communication Protocol for Building Automation and Control Networks, referred to as "BACnet". ASHRAE developed BACnet to provide a method for diverse building automation devices to communicate and share data over a network. 1.2.2 BACnet Building Automation and Control Network; the common name for the communication standard ASHRAE 135. The standard defines methods and protocol for cooperating building automation devices to communicate over a variety of LAN technologies. 1.2.3 BACnet/IP An extension of BACnet, Annex J, defines this mechanism using a reserved UDP socket to transmit BACnet messages over IP networks. A BACnet/IP network is a collection of one or more IP subnetworks that share the same BACnet network number. See also "BACnet Broadcast Management Device". 1.2.4 BACnet Internetwork Two or more BACnet networks, possibly using different LAN technologies, connected with routers. In a BACnet internetwork, there exists only one message path between devices. 1.2.5 BACnet Network One or more BACnet segments that have the same network address and are interconnected by bridges at the physical and data link layers. 1.2.6 BACnet Segment One or more physical segments of BACnet devices on a BACnet network, connected at the physical layer by repeaters. 1.2.7 BBMD BACnet Broadcast Management Device (BBMD). A communications device, typically combined with a BACnet router. A BBMD forwards BACnet broadcast messages to BACnet/IP devices and other BBMDs connected to the same BACnet/IP network. Every IP subnetwork that is part of a BACnet/IP network must have only one BBMD. See also "BACnet/IP". 1.2.8 BAS Building Automation Systems, including DDC (Direct Digital Controls) used for facility automation and energy management. 1.2.9 BAS Owner The regional or local user responsible for managing all aspects of the BAS operation, including: network connections, workstation management, submittal review, technical support, control parameters, and daily operation. The BAS Owner for this project is Ben LaGasse. 1.2.10 BIBBs BACnet Interoperability Building Blocks. A collection of BACnet services used to describe supported tasks. BIBBs are often described in terms of "A" (client) and "B" (server) devices. The "A" device uses data provided by the "B" device, or requests an action from the "B" device. 1.2.11 BI BACnet International, formerly two organizations: the BACnet Manufacturers Association (BMA) and the BACnet Interest Group - North America (BIG-NA). 1.2.12 BI/BTL BACnet International/BACnet Testing Laboratories (Formerly BMA/BTL). The organization responsible for testing products for compliance with the BACnet standard, operated under the direction of BACnet International. 1.2.13 Bridge Network hardware that connects two or more network (or BACnet internetwork) segments at the physical and data link layers. A bridge may also filter messages. 1.2.14 Broadcast A message sent to all devices on a network segment. 1.2.15 Device Any control system component, usually a digital controller that contains a BACnet Device Object and uses BACnet to communicate with other devices. See also "Digital Controller". 1.2.16 Device Object Every BACnet device requires one Device Object, whose properties represent the network visible properties of that device. Every Device Object requires a unique Object Identifier number on the BACnet internetwork. This number is often referred to as the device instance. 1.2.17 Device Profile A collection of BIBBs determining minimum BACnet capabilities of a device, defined in ASHRAE Standard 135-2004, Annex L. Standard device profiles include BACnet Operator Workstations (B-OWS), BACnet Building Controllers (B-BC), BACnet Advanced Application Controllers (B-AAC), BACnet Application Specific Controllers (B-ASC), BACnet Smart Actuator (B-SA), and BACnet Smart Sensor (B-SS). Each device used in new construction is required to have a PICS statement listing BIBBs supported. 1.2.18 Digital Controller An electronic controller, usually with internal programming logic and digital and analog input/output capability, which performs control functions. In most cases, synonymous with a BACnet device described in this specification. See also "Device". 1.2.19 Direct Digital Control (DDC) Digital controllers performing control logic. Usually the controller directly senses physical values, makes control decisions with internal programs, and outputs control signals to directly operate switches, valves, dampers, and motor controllers. 1.2.20 DDC System A network of digital controllers, communication architecture, and user interfaces. A DDC system may include programming, sensors, actuators, switches, relays, factory controls, operator workstations, and various other devices, components, and attributes. 1.2.21 Ethernet A family of local-area-network technologies providing high-speed networking features over various media. 1.2.22 Firmware Software programmed into read only memory (ROM), flash memory, electrically erasable programmable read only memory (EEPROM), or erasable programmable read only memory (EPROM) chips. 1.2.23 Gateway Communication hardware connecting two or more different protocols, similar to human language translators. The Gateway translates one protocol into equivalent concepts for the other protocol. In BACnet applications, a gateway has BACnet on one side and non-BACnet (usually proprietary) protocols on the other side. 1.2.24 Half Router A device that participates as one partner in a BACnet point-to-point (PTP) connection. Two half-routers in an active PTP connection combine to form a single router. 1.2.25 Hub A common connection point for devices on a network. 1.2.26 Internet Protocol (IP, TCP/IP, UDP/IP) A communication method, the most common use is the World Wide Web. At the lowest level, it is based on Internet Protocol (IP), a method for conveying and routing packets of information over various LAN media. Two common protocols using IP are User Datagram Protocol (UDP) and Transmission Control Protocol (TCP). UDP conveys information to well-known "sockets" without confirmation of receipt. TCP establishes "sessions", which have end-to-end confirmation and guaranteed sequence of delivery. 1.2.27 Input/Output (I/O) Physical inputs and outputs to and from a device, although the term sometimes describes software, or "virtual" I/O. See also "Points". 1.2.28 I/O Expansion Unit An I/O expansion unit provides additional point capacity to a digital controller. 1.2.29 IP subnet Internet protocol (IP) identifies individual devices with a 32-bit number divided into four groups from 0 to 255. Devices are often grouped and share some portion of this number. For example, one device has IP address 209.185.47.68 and another device has IP address 209.185.47.82. These two devices share Class C subnet 209.185.47.00 1.2.30 Local-Area Network (LAN) A communication network that spans a limited geographic area and uses the same basic communication technology throughout. 1.2.31 LonTalk CEA-709.1-C. A communication protocol developed by Echelon Corp. LonTalk is an optional physical and data link layer for BACnet. 1.2.32 MAC Address Media Access Control address. The physical node address that identifies a device on a Local Area Network. 1.2.33 Master-Slave/Token-Passing (MS/TP) ISO 8802-3. One of the LAN options for BACnet. MSTP uses twisted-pair wiring for relatively low speed and low cost communication (up to 4,000 ft at 76.8K bps). 1.2.34 Native BACnet Device A device that uses BACnet as its primary, if not only, method of communication with other BACnet devices without intermediary gateways. A system that uses native BACnet devices at all levels is a native BACnet system. 1.2.35 Network Communication technology for data communications. BACnet approved network types are BACnet over Internet Protocol (IP), Point to Point (PTP) Ethernet, ARCNET, MS/TP, and LonTalk®. 1.2.36 Network Number A site-specific number assigned to each network segment to identify for routing. This network number must be unique throughout the BACnet internetwork. 1.2.37 Object The concept of organizing BACnet information into standard components with various associated properties. Examples include analog input objects and binary output objects. 1.2.38 Object Identifier An object property used to identify the object, including object type and instance. Object Identifiers must be unique within a device. 1.2.39 Object Properties Attributes of an object. Examples include present value and high limit properties of an analog input object. Properties are defined in ASHRAE 135; some are optional and some are required. Objects are controlled by reading from and writing to object properties. 1.2.40 Peer-to-Peer Peer-to-peer refers to devices where any device can initiate and respond to communication with other devices. 1.2.41 Performance Verification Test (PVT) The procedure for determining if the installed BAS meets design criteria prior to final acceptance. The PVT is performed after installation, testing, and balancing of mechanical systems. Typically the PVT is performed by the Contractor in the presence of the Government. 1.2.42 PID Proportional, integral, and derivative control; three parameters used to control modulating equipment to maintain a setpoint. Derivative control is often not required for HVAC systems (leaving "PI" control). 1.2.43 PICS Protocol Implementation Conformance Statement (PICS), describing the BACnet capabilities of a device. See BACnet, Annex A for the standard format and content of a PICS statement. 1.2.44 Points Physical and virtual inputs and outputs. See also "Input/Output". 1.2.45 PTP Point-to-Point protocol connects individual BACnet devices or networks using serial connections like modem-to-modem links. 1.2.46 Repeater A network component that connects two or more physical segments at the physical layer. 1.2.47 Router A BACnet router is a component that joins together two or more networks using different LAN technologies. Examples include joining a BACnet Ethernet LAN to a BACnet MS/TP LAN. 1.2.48 Stand-Alone Control Refers to devices performing equipment-specific and small system control without communication to other devices or computers for physical I/O, excluding outside air and other common shared conditions. Devices are located near controlled equipment, with physical input and output points limited to 64 or less per device, except for complex individual equipment or systems. Failure of any single device will not cause other network devices to fail. BACnet "Smart" actuators (B-SA profile) and sensors (B-SS profile) communicating on a network with a parent device are exempt from stand-alone requirements. 1.3 BACNET DIRECT DIGITAL CONTROL SYSTEMS FOR HVAC DESCRIPTION a. Remove existing and provide new BACnet and merge with existing BACnet DDC systems including associated equipment and accessories. All new devices are accessible using a Web browser interface and communicate using ASHRAE 135 BACnet communications without the use of gateways, unless gateways are shown on the design drawings and specifically requested by the Government. Where gateways are allowed, they must support ASHRAE 135, including all object properties and read-write services shown on Government approved interoperability schedules. Manufacturer's products, including design, materials, fabrication, assembly, inspection, and testing shall be in accordance with ASHRAE 135, ASME B31.1, and NFPA 70, except where indicated otherwise. b. The existing DDC system is manufactured by Schneider Electric. 1.3.1 Design Requirements 1.3.1.1 Control System Drawings Title Sheet Provide a title sheet for the control system drawing set. Include the project title, project location, contract number, the controls contractor preparing the drawings, an index of the control drawings in the set, and a legend of the symbols and abbreviations used throughout the control system drawings. 1.3.1.2 List of I/O Points Also known as a Point Schedule, provide for each input and output point physically connected to a digital controller: point name, point description, point type (Analog Output (AO), Analog Input (AI), Binary Output (BO), Binary Input (BI)), point sensor range, point actuator range, point address, BACnet object, associated BIBBS (where applicable), and point connection terminal number. Typical schedules for multiple identical equipment are allowed unless otherwise requested in design or contract criteria. 1.3.1.3 BACnet Communication Architecture Schematic Provide a schematic showing the project's entire BACnet communication network, including addressing used for LANs, LAN devices including routers and bridges, gateways, controllers, workstations, and field interface devices. If applicable, show connection to existing networks. 1.4 QUALITY ASSURANCE 1.4.1 Standard Products Provide material and equipment that are standard manufacturer's products currently in production and supported by a local service organization. 1.4.2 Delivery, Storage, and Handling Handle, store, and protect equipment and materials to prevent damage before and during installation according to manufacturer's recommendations, and as approved by the Contracting Officer. Replace damaged or defective items. 1.4.3 Operating Environment Protect components from humidity and temperature variation, dust, and contaminants. If components are stored before installation, keep them within the manufacturer's limits. 1.4.4 Verification of Dimensions The contractor shall verify all dimensions in the field, and advise the Contracting Officer of any discrepancy before performing work. 1.4.5 Modification of References The advisory provisions in ASME B31.1 and NFPA 70 are mandatory. Substitute "shall" for "should" wherever it appears and interpret all references to the "authority having jurisdiction" and "owner" to mean the Contracting Officer. 1.4.6 Project Sequence The control system work for this project shall proceed in the following order: a. Perform the control system installation work, including all field check-outs and tuning. b. Submit and receive approval of the Controls System Operators Manual specified under the paragraph "CONTROLS SYSTEM OPERATORS MANUALS." c. Deliver the final Controls System Operators Manuals. d. Conduct the Phase I Training e. Conduct the Phase II Training PART 2 PRODUCTS 2.1 DDC SYSTEM a. Provide a networked DDC system for stand-alone control in compliance with the latest revision of the ASHRAE 135 BACnet standard. Include all programming, objects, and services required to meet the sequence of control. Provide BACnet communications between the DDC system and native BACnet devices furnished with HVAC equipment and plant equipment including chillers and variable frequency drives. 2.1.1 DDC Software 2.1.1.1 Programming Provide graphic-based programming to execute the sequence of operation indicated. Provide all programming and tools to configure and program all controllers. Provide programming routines in simple, easy-to-follow logic with detailed text comments describing what the logic does and how it corresponds to the project's written sequence of operation. a. Graphic-based programming shall use a library of function blocks made from pre-programmed code designed for BAS control. Function blocks shall be assembled with interconnecting lines, depicting the control sequence in a flowchart. If providing a computer with device programming tools as part of the project, graphic programs shall be viewable in real time showing present values and logical results from each function block. 2.1.1.2 Parameter Modification All writeable object properties, and all other programming parameters needed to comply with the project specification shall be adjustable for devices at any network level, including those accessible with web-browser communication, and regardless of programming methods used to create the applications. 2.1.1.3 Short Cycling Prevention Provide setpoint differentials and minimum on/off times to prevent equipment short cycling. 2.1.1.4 Equipment Status Delay Provide an adjustable delay from when equipment is commanded on or off and when the control program looks to the status input for confirmation. 2.1.1.5 Run Time Accumulation Use the Elapsed Time Property to provide re-settable run time accumulation for each Binary Output Object connected to mechanical loads greater than 1 HP, electrical loads greater than 10 KW, or wherever else specified. 2.1.1.6 Time Synchronization Provide time synchronization, including adjustments for leap years, daylight saving time, and operator time adjustments. 2.1.1.7 Scheduling Provide operating schedules as indicated, with equipment assigned to groups. Changing the schedule of a group shall change the operating schedule of all equipment in the group. Groups shall be capable of operator creation, modification, and deletion. Provide capability to view and modify schedules in a seven-day week format. Provide capability to enter holiday and override schedules one full year at a time. 2.1.1.8 Object Property Override Allow writeable object property values to accept overrides to any valid value. Where specified or required for the sequence of control, the Out-Of-Service property of Objects shall be modifiable using BACnet's write property service. When documented, exceptions to these requirement are allowed for life, machine, and process safeties. 2.1.1.9 Alarms and Events Alarms and events shall be capable of having programmed time delays and high-low limits. When a computer workstation or web server is connected to the BACnet internetwork, alarms/events shall report to the dialer as defined by an authorized operator. Otherwise alarms/events shall be stored within a device on the BACnet network until connected to a user interface device and retrieved. Provide alarms/events in agreement with the point schedule, sequence of operation, and the BAS Owner. At a minimum, provide programming to initiate alarms/events any time a piece of equipment fails to operate, a control point is outside normal range or condition shown on schedules, communication to a device is lost, a device has failed, or a controller has lost its memory. 2.1.1.10 Trending Provide BACnet trend services capable of trending all object present values set points, and other parameters indicated for trending on project schedules. Trends may be associated into groups, and a trend report may be set up for each group. Trends are stored within a device on the BACnet network, with operator selectable trend intervals from 10 seconds up to 60 minutes. The minimum number of consecutive trend values stored at one time shall be 100 per variable. When trend memory is full, the most recent data shall overwrite the oldest data. 2.1.1.11 Device Diagnostics Each controller shall have diagnostic LEDs for power, communication, and device fault condition. The DDC system shall recognize and report a non-responsive controller. 2.1.1.12 Power Loss Upon restoration of power, the DDC system shall perform an orderly restart and restoration of control. 2.2 ELECTRICAL POWER AND DISTRIBUTION 2.2.1 Transformers Transformers shall conform to UL 506. For control power other than terminal level equipment, provide a fuse or circuit breaker on the secondary side of each transformer. 2.2.2 Wiring Provide complete electrical wiring for the DDC System, including wiring to transformer primaries. Unless indicated otherwise, provide all normally visible or otherwise exposed wiring in conduit. Where conduit is required, control circuit wiring shall not run in the same conduit as power wiring over 100 volts. Run all circuits over 100 volts in conduit, metallic tubing, covered metal raceways, or armored cable. Use plenum-rated cable for circuits under 100 volts in enclosed spaces. Examples of these spaces include HVAC plenums, within walls, above suspended ceilings, in attics, and within ductwork. 2.2.2.1 Power Wiring The following requirements are for field-installed wiring: a. Wiring for 24 V circuits shall be insulated copper 18 AWG minimum and rated for 300 VAC service. b. Wiring for 120 V circuits shall be insulated copper 14 AWG minimum and rated for 600 VAC service. PART 3 EXECUTION 3.1 INSTALLATION Perform the installation under the supervision of competent technicians regularly employed in the installation of DDC systems. 3.1.1 BACnet Naming and Addressing Coordinate with the BAS Owner and provide unique naming and addressing for BACnet networks and devices. a. MAC Address Every BACnet device shall have an assigned and documented MAC Address unique to its network. For Ethernet networks, document the MAC Address assigned at its creation. For ARCNET or MS/TP, assign from 00 to 64. b. Network Numbering Assign unique numbers to each new network installed on the BACnet internetwork. Provide ability for changing the network number; either by device switches, network computer, or field operator interface. The BACnet internetwork (all possible connected networks) can contain up to 65,534 possible unique networks. c. Device Object Identifier Property Number Assign unique Device "Object_Identifier" property numbers or device instances for each device on the BACnet internetwork. Provide for future modification of the device instance number; either by device switches, network computer, or field interface. BACnet allows up to 4,194,302 possible unique devices per internetwork. d. Device Object Name Property Text The Device Object Name property field shall support 32 minimum printable characters. Assign unique Device "Object_Name" property names with plain-English descriptive names for each device. For example, the Device Object Name that for the device controlling the chiller plant at Building 3408 would be: Device Object_Name = CW System B3408 A Device Object Name for a VAV box controller might be: Device Object_Name = VAV BOX25 e. Object Name Property Text (Other than Device Objects) The Object Name property field shall support 32 minimum printable characters. Assign Object Name properties with plain-English names descriptive of the application. Examples include "Zone 1 Temperature" and "Fan Start/Stop". f. Object Identifier Property Number (Other than Device Objects) Assign Object Identifier property numbers according to design drawings or tables if provided. If not provided, Object Identifier property numbers may be assigned at the Contractor's discretion but must be approved by the Government. In this case they must be documented and unique for like object types within the device. 3.1.2 Minimum BACnet Object Requirements a. Use of Standard BACnet Objects For the following points and parameters, use standard BACnet objects, where all relevant object properties can be read using BACnet's Read Property Service, and all relevant object properties can be modified using BACnet's Write Property Service: all device physical inputs and outputs, all set points, all PID tuning parameters, all calculated pressures, flow rates, and consumption values, all alarms, all trends, all schedules, and all equipment and lighting circuit operating status. b. BACnet Object Description Property The Object Description property shall support 32 minimum printable characters. For each object, complete the description property field using a brief, narrative, plain English description specific to the object and project application. For example: "HW Pump 1 Proof." Document compliance, length restrictions, and whether the description is writeable in the device PICS. c. Analog Input, Output, and Value Objects Support and provide Description and/or Device_Type text strings matching signal type and engineering units shown on the points list. d. Binary Input, Output, and Value Objects Support and provide Inactive_Text and Active_Text property descriptions matching conditions shown on the points list. e. Calendar Object For devices with scheduling capability, provide at least one Calendar Object with ten-entry capacity. All operators may view Calendar Objects; authorized operators may make modifications from a workstation. Enable the writeable Date List property and support all calendar entry data types. f. Schedule Object Use Schedule Objects for all building system scheduling. All operators may view schedule entries; authorized operators may modify schedules from a workstation. g. Loop Object or Equal Use Loop Objects or equivalent BACnet objects in each applicable field device for PID control. Regardless of program method or object used, allow authorized operators to adjust the Update Interval, Setpoint, Proportional Constant, Integral Constant, and Derivative Constant using BACnet read/write services. 3.1.3 Minimum BACnet Service Requirements a. Command Priorities Use commandable BACnet objects to control machinery and systems, providing the priority levels listed below. If the sequence of operation requires a different priority, obtain approval from the Contracting Officer. Priority Level Application 1 Manual-Life Safety 2 Automatic-Life Safety 3 (User Defined) 4 (User Defined) 5 Critical Equipment Control 6 Minimum On/Off 7 (User Defined) 8 Manual Operator 9 (User Defined) 10 (User Defined) 11 Load Shedding 12 (User Defined) 13 (User Defined) 14 (User Defined) 15 (User Defined) 16 (User Defined) b. Alarming (1) Alarm Priorities - Coordinate alarm and event notification with the BAS Owner. (2) Notification Class - Enable writeable Priority, Ack Required, and Recipient List properties of Notification Class objects. (3) Event Notification Message Texts - Use condition specific narrative text and numerical references for alarm and event notification. c. Updating Displayed Property Values Allow workstations to display property values at discrete polled intervals, or based on receipt of confirmed and unconfirmed Change of Value notifications. The COV increment shall be adjustable by an operator using BACnet services, and polled intervals shall be adjustable at the operator workstation. 3.1.4 Accessibility Install all equipment so parts requiring periodic inspection, operation, maintenance, and repair are readily accessible. Install digital controllers, data ports, and concealed actuators, valves, dampers, and like equipment in locations freely accessible through access doors. 3.2 CONTROLS SYSTEM OPERATORS MANUALS Provide one electronic and two printed copies of a Controls System Operators Manual. The manual shall be specific to the project, be written to actual project conditions, and provide a complete and concise depiction of the installed work. Provide information in detail to clearly explain all operation requirements for the control system. Provide with each manual: CDs of the project's control system drawings, control programs, data bases, graphics, and all items listed below. Include gateway back-up data and configuration tools where applicable. Provide CDs in jewel case with printed and dated project-specific labels on both the CD and the case. For text and drawings, use Adobe Acrobat or MS Office file types. When approved by the Government, AutoCAD and Visio files are allowed. Give files descriptive English names and organize in folders. Provide printed manuals in sturdy 3-ring binders with a title sheet on the outside of each binder indicating the project title, project location, contract number, and the controls contractor name, address, and telephone number. Each binder shall include a table of contents and tabbed dividers, with all material neatly organized. Manuals shall include the following: a. A copy of the as-built control system (shop) drawings set, with all items specified under the paragraph "Submittals." Indicate all field changes and modifications. b. A copy of the project's mechanical design drawings, including any official modifications and revisions. c. A copy of the project's approved Product Data submittals provided under the paragraph "Submittals." d. A copy of the project's approved Performance Verification Testing Plan and Report. e. Printouts of all control system programs, including controller setup pages if used. Include plain-English narratives of application programs, flowcharts, and source code. f. Printouts of all physical input and output object properties, including tuning values, alarm limits, calibration factors, and set points. g. A table entitled "AC Power Table" listing the electrical power source for each controller. Include the building electrical panel number, panel location, and circuit breaker number. h. The DDC manufacturer's hardware and software manuals in both print and CD format with printed project-specific labels. Include installation and technical manuals for all controller hardware, operator manuals for all controllers, programming manuals for all controllers, operator manuals for all workstation software, installation and technical manuals for the workstation and notebook, and programming manuals for the workstation and notebook software. i. A list of qualified control system service organizations for the work provided under this contract. Include their addresses and telephone numbers. j. A written statement entitled "Technical Support" stating the control system manufacturer or authorized representative will provide toll-free telephone technical support at no additional cost to the Government for a minimum of two years from project acceptance. Technical support shall be furnished by experienced service technicians, and will be available during normal weekday working hours. Include the toll-free technical support telephone number. k. A written statement entitled "Software Upgrades" stating software and firmware patches and updates will be provided upon request at no additional cost to the Government for a minimum of two years from contract acceptance. Include a table of all DDC system software and firmware provided under this contract, listing the original release dates, version numbers, part numbers, and serial numbers. 3.3 TRAINING REQUIREMENTS Provide a qualified instructor (or instructors) with two years minimum field experience with the installation and programming of similar BACnet DDC systems. Orient training to the specific systems installed. Coordinate training times with the Contracting Officer and BAS Owner after receiving approval of the training course documentation. Training shall take place at the job site and/or a nearby Government-furnished location. A training day shall occur during normal working hours, last no longer than 2 hours. The project's approved Controls System Operators Manual shall be used as the training text. The Contractor shall ensure the manuals are submitted, approved, and available to hand out to the trainees before the start of training. 3.3.1 Phase I Training - Fundamentals The Phase I training session shall last one hour and be conducted in a classroom environment with complete audio-visual aids provided by the contractor. Provide each trainee a printed 8.5 by 11 inch hard-copy of all visual aids used. Upon completion of the Phase I Training, each trainee should fully understand the project's DDC system fundamentals. The training session shall include the following: a. BACnet fundamentals (objects, services, addressing) and how/where they are used on this project b. This project's list of control system components c. This project's list of points and objects d. This project's device and network communication architecture e. This project's sequences of control f. Alarm capabilities g. Trending capabilities h. Troubleshooting communication errors i. Troubleshooting hardware errors 3.3.2 Phase II Training - Operation Provide Phase II Training shortly after completing Phase I Training. The Phase II training session shall last one hour and be conducted at the DDC system workstation, at a notebook computer connected to the DDC system in the field, and at other site locations as necessary. Upon completion of the Phase II Training, each trainee should fully understand the project's DDC system operation. The training session shall include the following: a. A walk-through tour of the mechanical system and the installed DDC components (controllers, valves, dampers, surge protection, switches, thermostats, sensors, etc.) b. A discussion of the components and functions at each DDC panel c. Logging-in and navigating at each operator interface type d. Using each operator interface to find, read, and write to specific controllers and objects e. Modifying and downloading control program changes f. Modifying setpoints g. Creating, editing, and viewing trends h. Creating, editing, and viewing alarms i. Creating, editing, and viewing operating schedules and schedule objects j. Backing-up and restoring programming and databases k. Modifying graphic text, backgrounds, dynamic data displays, and links to other graphics l. Creating new graphics and adding new dynamic data displays and links m. Alarm and Event management n. Adding and removing network devices End of Section -- - 52.211-6 -- Brand Name or Equal (1999) - (a) If an item in this solicitation is identified as "brand name or equal," the purchase description reflects the characteristics and level of quality that will satisfy the Government's needs. The salient physical, functional, or performance characteristics that "equal" products must meet are specified in the solicitation. - (b) To be considered for award, offers of "equal" products, including "equal" products of the brand name manufacturer, must- - (1) Meet the salient physical, functional, or performance characteristic specified in this solicitation; - (2) Clearly identify the item by- - (i) Brand name, if any; and - (ii) Make or model number; - (3) Include descriptive literature such as illustrations, drawings, or a clear reference to previously furnished descriptive data or information available to the Contracting Officer; and - (4) Clearly describe any modification the offeror plans to make in a product to make it conform to the solicitation requirements. Mark any descriptive material to clearly show the modification. - (c) The Contracting Officer will evaluate "equal" products on the basis of information furnished by the offeror or identified in the offer and reasonably available to the Contracting Officer. The Contracting Officer is not responsible for locating or obtaining any information not identified in the offer. - (d) Unless the offeror clearly indicates in its offer that the product being offered is an "equal" product, the offeror shall provide the brand name product referenced in the solicitation. - - (End of provision) This is a Buy Best Value acquisition. The Government will award a Purchase Order resulting from this Request for Quotes to the responsible offeror whose quote is conforming to the solicitation and represents the most advantageous to the Government, price and other factors considered. The following factors shall be used to evaluate offers: EVALUATION FACTORS FOR AWARD 1. Past Performance - Quotes will be evaluated based on the offeor's past performance as provided by the offerors references. 2. Offeror's Technical Solution- The Government will evaluate the performance of the offeror's product for capability and performance. 3. Quality and Reliability- Quotes will be evaluated on the offeror's product for its level of Quality and Reliability. 4. Price- The quoted price is fair and reasonable. NOTE: All evaluation factors other than cost or price, when combined, are significantly more important than cost or price. Factors and sub-factors are prioritized in the following order of importance (i.e. most important first, least important last) for award evaluation 2, 3, 1, 4. The Government will evaluate quotes for award purposes, considering the evaluation factors above, and will award to that offeror whose proposal represents the best value to the Government. Must be on GSA schedule; please list your GSA contract number, make sure you are registered in SAM as well as provide your DUNS number and a point of contact. This quote must be valid until 10/31/2015 Description: Facility Containment Restrictions: Delivery is to the Red River Agriculture Research Center (RRVARC). Contractor employee(s) must adhere to facility safety regulations. RRVARC does not have a loading dock; or a standard fork lift on site for delivery. 52.232-18 Availability of Funds. Availability of Funds (Apr 1984) Funds are not presently available for this contract. The Government's obligation under this contract is contingent upon the availability of appropriated funds from which payment for contract purposes can be made. No legal liability on the part of the Government for any payment may arise until funds are made available to the Contracting Officer for this contract and until the Contractor receives notice of such availability, to be confirmed in writing by the Contracting Officer. (End of Clause) Inspection and Acceptance Terms: Supplies will be inspected and accepted by the End User / Purchasing Agent at destination. Representations: Please include a completed copy of the provision at 52.212-3, Offeror Representations and Certifications -- Commercial Items. Applicable Provisions: The following Federal Acquisition Regulation (FAR) and the Department of Agriculture Acquisition Regulation (AGAR) provisions and clauses apply to this acquisition: FAR 52.204-7 System for Award Management: AGAR 452.204-70 Inquiries; FAR 52.209-6 Protecting the Government's Interests when Subcontracting with Contractors Debarred, Suspended or Proposed for Debarment; FAR 52.212-1 Instructions to Offers-Commercial Items; FAR 52.212-2 Evaluation-Commercial Items (filled in as follows: Technical specifications/support, and price); FAR 52.212-4 Contract Terms and Conditions-Commercial Items; FAR 52.212-5 Contract Terms and Conditions Required to Implement Statutes of Executive Orders-Commercial Items; AGAR 452.219-70 Size Standard and NAICS Code Information; FAR 52.222-3 Convict Labor; FAR 52.222-19 Child Labor - Cooperation with Authorities and Remedies; FAR 52.222-21 Prohibition of Segregated Facilities; FAR 52.222-26, Equal Opportunity Employment; FAR 52.222-36 Affirmative Action for Workers with Disabilities; FAR 52.222-50 Combating Trafficking in Persons; FAR 52.223-18 Encouraging Contractor Policy to Ban Text Messaging While Driving; FAR 52.225-13 Restrictions on Certain Foreign Purchases; FAR 52.225-25 Prohibitions on Contracting with Entities Engaging in Certain Activities or Transactions Relating to Iran-Reps and Certs; FAR 52.232-33 Payment by Electronic Funds Transfer-Central Contractor Registration; FAR 52.233-3 Protest After Award; FAR 52.233-4 Applicable Law for Breach of Contract; FAR 52.252-1 Solicitations Provisions Incorporated by Reference; FAR 52.252-2 Clauses Incorporated by Reference. Invoices must be submitted into the Invoice Processing Platform (IPP). IPP is a government-wide secure web-based payment information service offered free of charge to government agencies and their suppliers by the U.S. Department of Treasury's Financial Management Service (FMS). One-time enrollment in IPP means that you will receive a series of e-mails from Treasury services. The first email will have the IPP Logon ID and link to the IPP application. A second e-mail, containing the password will be sent within 24 hours. Once you receive these emails, please login to the IPP application and complete the registration process. Benefits of registering with IPP include the ability for your company to create invoices directly from a contract award and submit them electronically, as well as: · e-mail notification when invoice(s) are paid · online payment history · remittance download The e-mail notification of payment is sent when a payment is distributed to your bank account and will include all pertinent payment information. The IPP Customer Support Desk is available to assist users Monday through Friday (excluding bank holidays) from 8:00AM - 6:00PM ET, including answering any questions related to accessing IPP or completing the registration process. Their toll-free number is 1-866-973-3131 2 or they can be reached at: IPPCustomerSupport@fms.treas.gov. If you have any questions or concerns, please contact the Controller Operations Division Help Desk at: 1-877-243-3072 or cod.help@usda.gov. The successful vendor must be enrolled in IPP to submit invoices and receive payment. If the successful vendor firm is already enrolled in IPP invoices are to be submitted under the vendors existing IPP enrollment. Clause 52.223-2 requires: The contractor shall report to the environmental point of contact, with a copy to the Contracting Officer, on the product types and dollar value of any USDA-designated biobased products purchased by the contractor during the previous fiscal year. The report must be submitted not later than October 31 of each year during contract performance and at the end of contract performance. See list of attachments for categories of Biobased products, this list and linked descriptions can be found at http://cfr.regstoday.com/7CFR3201.aspx The environmental point of contact is: Ron Buckhalt RonB.Buckhalt@dm.usda.gov Phone: 202-205-4008 Energy Efficient Products Energy policy acts of 1992, 2005, 2007 and Executive Order 13423 require the purchase of energy efficient products--either those labeled "ENERGY STAR" or designated by the U.S. Department of Energy's Federal Energy Management Program (FEMP). The requirement applies both to direct purchases and contracted services, including contracts for design, construction, renovation, or maintenance of a public building. For contracted services, the contractor must provide ENERGY STAR, FEMP qualified, or other energy efficient products. To be eligible for an award, all contractors must be registered in the System for Award Management (SAM). A contractor can contact SAM by calling 1-866-606-8220 or e-mail at www.sam.gov. NO EXCEPTIONS. A DUNS (Dun and Bradstreet) number is required in order to register. Please have all bids valid until 10/31/2016
Web Link: FBO.gov Permalink
(https://www.fbo.gov/notices/40bbaa16b640d785661eecc5d787b5c2)
Place of Performance: Address: 1605 Albrecht Blvd N, fargo, North Dakota, 58102-2765, United States; Zip Code: 58102-2765
Record: SN04147829-W 20160615/160613234743-40bbaa16b640d785661eecc5d787b5c2 (fbodaily.com)
Source: FedBizOpps Link to This Notice
(may not be valid after Archive Date)

| FSG Index | This Issue's Index | Today's FBO Daily Index Page |

Loren Data's SAM Daily™

E -- Replace Universal Network Controller