W912PL-16-R-0025_Volume_IV_Appendices.pdf

SOLICITATION NO. W912PL 16 R 0025

DATE: FEBRUARY 2016

U.S. ARMY CORPS OF ENGINEERS

ALBUQUERQUE DISTRICT

VOLUME 4 OF 4

FY16 DESIGN/BUILD

F 35A AIRCRAFT MAINTENANCE HANGAR

(SQUADRON 3)

Project No. NEUX123005

Luke Air Force Base

Maricopa County, Arizona

APPENDIX

i

TABLE OF CONTENTS

VOLUME 1

DIVISION 00 – PROCUREMENT AND CONTRACTING REQUIREMENTS

00 10 00 SOLICITATION CONTRACT LINE ITEM (CLIN) SCHEDULE

00 20 00 INSTRUCTIONS FOR PROCUREMENT

00 21 16 INSTRUCTIONS TO PROPOSERS

00 22 00 SUPPLEMENTARY INSTRUCTIONS

00 22 16 SUPPLEMENTARY INSTRUCTIONS TO PROPOSERS

00 45 00 REPRESENTATIONS AND CERTIFICATIONS

00 70 00 CONDITIONS OF THE CONTRACT

00 73 00 SUPPLEMENTARY CONDITIONS

00 73 46 WAGE RATES

DIVISION 01 - GENERAL REQUIREMENTS

01 00 00 GENERAL REQUIREMENTS

01 02 00 SOLE SOURCE JUSTIFICATION

01 04 00 MECHANICAL ROOM LAYOUT AND COORDINATION

01 08 00 PERMITS

01 10 10 DESIGN REQUIREMENTS

01 10 12 DESIGN AFTER AWARD

01 20 00 INTERFACE WITH OTHER WORK

01 31 00 PROJECT MEETINGS

01 32 01 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 33 29 LEED™ DOCUMENTATION

01 34 10 COLOR/FINISH SAMPLE BOARDS

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

ii

VOLUME 1 (Cont’d)

01 43 00 AIRFIELD SAFETY (SPECIAL CONDIDERATIONS)

01 45 01 QUALITY CONTROL

01 45 02 QUALITY CONTROL SYSTEM (QCS)

01 51 00 UTILITIES

01 53 00 TEMPORARY FENCING

01 54 00 SECURITY

01 57 00 TRAFFIC CONTROL

01 57 20 ENVIRONMENTAL PROTECTION

01 58 00 PROJECT IDENTIFICATION

01 58 50 STAGING AREAS

01 62 35 RECYCLED / RECOVERED MATERIALS

01 72 00 AS-BUILT DRAWINGS

01 72 80 TRANSFER AND ACCEPTANCE OF MILITARY REAL PROPERTY

01 73 00 OPERATION AND MAINTENANCE INSTRUCTIONS

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

01 82 00 FUNDAMENTAL COMMISSIONING REQUIREMENTS

01 82 01 ENHANCED COMMISSIONING REQUIREMENTS (BID OPTION)

DIVISION 31 – EARTHWORK

31 00 00 EARTHWORK

DIVISION 32 – EXTERIOR IMPROVEMENTS

32 11 23 AGGREGATE BASE COURSE

32 13 11 CONCRETE PAVEMENT FOR AIRFIELDS AND OTHER HEAVY-DUTY

PAVEMENTS

32 13 73 COMPRESSION JOINT SEALS FOR CONCRETE PAVEMENTS

iii

VOLUME 2

APPENDIX A LUKE ARCHITECTURAL COMPATIBILITY GUIDE

APPENDIX B SELECTED CHAPTERS FROM THE SOUTHWESTERN DIVISION

ARCHITECTURAL AND ENGINEERING INSTRUCTIONS MANUAL

(AEIM):

CHAPTER II CIVIL

CHAPTER III ARCHITECTURAL

CHAPTER IV STRUCTURAL

CHAPTER V MECHANICAL

CHAPTER VI ELECTRICAL

CHAPTER VIII DRAWINGS

CHAPTER XII ENVIRONMENTAL

CHAPTER XIII GEOTECHNICAL

APPENDIX C SPECIFICATION GUIDANCE

APPENDIX D ATTACHMENT F, BUILDING INFORMATION MODELING (BIM)

REQUIREMENTS

APPENDIX E DESIGN ANALYSIS GUIDANCE

APPENDIX F AIRFIELD PAVEMENT DESIGN ANALYSIS

VOLUME 3

APPENDIX G STORMWATER PERMITTING GUIDANCE & LUKE BMPS

APPENDIX H GIS DATA & TOPOGRAPHIC SURVEY (electronic only)

APPENDIX I GEOPHYSICAL INFORMATION (electronic only)

APPENDIX J GEOTECHNICAL INFORMATION

APPENDIX K STRUCTURAL DRAFTING STANDARDS

APPENDIX L FIRE PROTECTION SYSTEMS PRELIMINARY ACCEPTANCE TEST

(PAT) AND FINAL ACCEPTANCE TEST (FAT) CHECK LIST

APPENDIX M UTILITY COST INFORMATION

VOLUME 4

APPENDIX N LUKE AFB EMCS DOCUMENT

APPENDIX O LUKE COMMUNICATIONS 400’ GUIDELINES

APPENDIX P LUKE AFB COMMUNICATIONS DESIGN STANDARDS

APPENDIX Q CONCEPTUAL AESTHETIC CONSIDERATIONS

iv

APPENDIX R CONCEPTUAL PROJECT DRAWINGS

VOLUME 4 (Cont’d)

APPENDIX S ROOM CRITERIA DATA SHEETS

APPENDIX T LEED PROJECT CREDIT GUIDANCE

APPENDIX U LEED OWNER’S PROJECT REQUIREMENTS

APPENDIX V ROOM SUMMARY MATRIX

APPENDIX W REFERENCED DIGITAL SID

APPENDIX X (NOT USED)

APPENDIX Y BLDG 920 ASBESTOS & LEAD REPORTS

APPENDIX Z SUMMARY OF UFC 1-200-02 REQUIRED LIFE CYCLE COST

ANALYSIS

APPENDIX AA LUKE AFB FLOOD CONTROL INVESTIGATION STUDY (JUNE 2013)

-- End of Project Table of Contents --

Corrected Final RFP – Luke AFB F-35 Aircraft Maintenance Hangar 3

Appendix N:

Luke AFB EMCS Specification Section

255100 – 15972

Project: Luke Air Force Base 56th Civil Engineer Squadron, AZ

SECTION 255100 - 15972

ENERGY MANAGEMENT CONTROL SYSTEM (EMCS)

August 31, 2015

PART 1 - GENERAL

1.0 ABBREVIATIONS AND SYMBOLS

1.1 Specification Nomenclature - Acronyms used in this specification are as follows:

EMCS Energy Management Control System DDC Direct Digital Control GUI Graphical User Interface HTTP Hyper Text Transfer Protocol LAN Local Area Network LCU Local Control Unit NCU Network Control Unit OBIX Open Building Information Exchange ODBC Open Data Base Connectivity protocol OOT Object Oriented Technology OPC Object linking and embedding for Process Control OWS Operator Workstation PDA Personnel Data Assistant PICS Protocol Implementation Conformance Statement PWS Portable (Operator) Workstation SNVT Standard Network Variables Types SQL Standard Query Language TCP/IP Transmission Control Protocol / Internet Protocol TCU Terminal Control Unit UPS Uninterruptable Power Supply WAN Wide Area Network WAP Wireless Application Protocol WBI Web Browser Interface XML Extensible Markup Language XIF External Interface Files

2.0 WORK INCLUDED

2.1 Provide an Energy Management Control System to control and monitor the building’s mechanical and electrical systems. The system installed shall seamlessly connect devices other than HVAC as needed throughout the building regardless of subsystem type. LONWORKS components not supplied by the primary manufacturer shall be integrated to share common software for network communications, time scheduling, alarm handling, and history logging.

2.2 Coordinate interface requirements for integration into the EMCS of following building-level equipment and systems:

2.2.1 Variable Frequency Drives

2.2.2 Factory HVAC equipment ie., chillers, computer room air conditioners, etc…

2.3 Provide new controllers of the latest revisions with input and output points as specified herein.

2.4 Provide control valves, control dampers (gravity, fire and smoke control dampers by others), flow switches, thermal wells for pressure and temperature control, and air flow stations as necessary.

2.5 Provide submittal data sheets, control drawings schematics (in Visio or AutoCAD and also PDF), data entry, pneumatic (as required) and electrical installation, programming, startup, test and validation acceptance documentation, as-built, maintenance manuals and system warranties.

2.6 All labor, material, equipment and services not specifically referred to in this specification or on associated drawings that are required to fulfill the functional intent of this specification shall be provided at no additional cost to the Owner.

2.7 The work covered by this specification and related sections consists of providing shop drawings, equipment, labor, materials, engineering, technical supervision, and transportation as required to furnish and install a fully operational EMCS to monitor and control the facilities listed herein, and as required to provide the operation specified in strict accordance with these documents, and subject to the terms and conditions of the contract. The work in general consists of but is not limited to, the following:

2.7.1 The preparation of submittals and provision of all related services.

2.7.2 Operator workstations located as listed in the specifications.

2.7.3 Furnish and install all controllers to achieve system operation, any control devices, conduit and wiring, in the facility as required to provide the operation specified.

2.7.4 Furnish and load all software required to implement a complete and operational EMCS.

2.7.5 Furnish complete operating and maintenance manuals and field training of operators, programmers, and maintenance personnel.

2.7.6 Perform acceptance tests and commissioning as indicated.

2.7.7 Provide full documentation for all application software and equipment.

2.7.8 As needed, provide funding for network data port thru LAFB 56 CS Base I

2.7.8 Miscellaneous work as indicated in these specifications.

3.0 WORK BY OTHERS

3.1 Setting in place of valves and dampers, access doors, flow meters, water pressure and differential taps, flow switches, thermal wells, fire and smoke control dampers, and air flow stations shall be by others.

3.2 Smoke detectors shall be provided under Division 26 00 00. Connection of auxiliary terminals of smoke detectors shall be wired to the building automation system for monitoring purposes by this section.

3.3 High and low temperature thermostats shall be provided by this section.

3.4 The installation of motor starters that are not factory installed, thermal overload switches, and power wiring to motors, starters, thermal overload switches, and contactors, is specified in Division 26 00

00. This Section includes the furnishing and installation of controls and wiring for automatic controls, electric damper and valve operators, terminal control units, interlocks, starting circuits, and wiring to power consuming control devices.

3.4.1 Duct smoke detectors shall be provided, installed and wired by Division 26 00 00.

4.0 APPROVED MANUFACTURERS

4.1 Provide a building automation system supplied by a company regularly engaged in the manufacturing and distribution of Energy Management Control Systems. The EMCS Manufacturer shall meet the following qualifications as a minimum:

4.1.1 The manufacturer of the hardware and software components must be primarily engaged in the manufacture of Energy Management Control Systems as specified herein, and must have been so for a minimum of five (5) years.

4.1.2 The manufacturer of the hardware and software components as well as its subsidiaries must be a member in good standing of the LONMARK Association..

4.1.3 At least 75% of the manufacture product line shall be produced under their own direction, including R&D and assembly. Rebranding of another manufacture product shall not qualify.

4.1.4 The manufacturer of the hardware and software components shall have a technical support group accessible via a toll free number that is staffed with qualified personnel, capable of providing instruction and technical support service for networked control systems.

4.2 Approved manufacturers:

4.2.1 Distech Controls purchased from Factory Authorized Dealer within the State of Arizona.

4.3 Unsolicited bids from Manufacturers or Contractors not listed herein will not be considered.

4.4 Alternate bids will not be considered.

5.0 QUALITY ASSURANCE

5.1 All new building automation system products on this project shall be provided by a firm that is a registered ISO 9001:2005 manufacturer at time of bid.

5.1.1 The manufacturer of the Energy Management Control System digital controllers shall provide documentation supporting compliance with ISO 9001:2005 (Model for Quality Assurance in Design/Development, Production, Installation and Servicing).

5.1.2 Provide a copy of the registration certificate that contains the ISO 9001:2005 Certification bearing the name of the registered auditor.

5.2 The Energy Management Control System shall be furnished, engineered, installed, tested and calibrated by factory certified technicians qualified for this work. Certification must be current with minimum of 1 year experience from the construction start date. The contractor shall have in place a support facility located within 50 miles of the project site with technical staff, spare parts inventory and all necessary test and diagnostic equipment. The contractor shall be a Factory Authorized System Integrator in good standing with the Manufacturer. Factory trained technicians shall provide instruction, routine maintenance, and emergency service within 24 hours upon receipt of request.

5.2.1 Upon request, installer shall present records of successful completion of factory training courses including course outlines.

5.2.2 Upon request the installer shall provide a letter from the manufacturer that they are a Factory Authorized System Integrator in good standing.

5.2.3 If awarded contractor is not a Factory Authorized Dealer per 4.2.1 above, contractor must provide a letter of partnership with one of the three Distech recognized dealerships within the State of Arizona.

-- Synergetic Systems -- Therm-air -- Sigler Controls Division

5.3 Provide satisfactory operation without damage at 110% above and 85% below rated voltage and at 3 hertz variation in line frequency. Provide static, transient, and short circuit protection on all inputs and outputs. Communication lines shall be protected against incorrect wiring, static transients and induced magnetic interference. Bus connected devices shall be AC coupled, or equivalent so that any single device failure will not disrupt or halt bus communication.

5.4 All controllers provided as part of this system and used for indoor applications shall operate under ambient environmental conditions of 32 degF (0 degC) to 122 degF (50 degC) dry bulb and 5% to 90% relative humidity, non-condensing as a minimum.

5.5 All controllers provided as part of this system and used for outdoor applications shall operate under ambient environmental conditions of -40 degF (-40 degC) to 158 degF (70 degC) dry bulb and 5% to 90% relative humidity, non-condensing as a minimum.

6.0 CODES AND STANDARD

6.1 The complete EMCS installation shall be in strict compliance and meet with the requirements of all governing bodies, authorities having jurisdiction, applicable national or local standards and codes, except where the Contract Documents detail a more stringent requirement.

6.2 Apply for, obtain and pay for all permits, licenses, inspections, examinations and fees required. Also submit, if required, information and other data from the Contracting Officer. Should the authorities require the information on specific forms, fill in these forms by transcribing the information provided by the Contracting Officer.

6.3 All electronic equipment shall conform to the following minimum requirements:

6.3.1 UL 916 Underwriters Laboratories Standard for Energy Management Equipment or UL61010

Underwriters Laboratories Standard for Process Control Equipment, Electrical (Canada and United States) and be labeled for the specific use, application and environment to which they are applied.

6.3.1.1 Where there is no alternative to supply equipment that is not UL or ULC certified, submit such equipment to Inspection Authorities having jurisdiction, pay for special inspection and obtain approval before delivery of equipment to site.

6.3.2 International Building Code (IBC), including local amendments.

6.3.2.1 Section 719 Ducts and Air Transfer Openings

6.3.2.2 Chapter 28 Mechanical

6.3.3 International Mechanical Code (IMC)

6.3.4 National Electrical Code (NEC).

6.3.5 FCC Part 15, Subpart B, Class B.

6.3.6 2004/108/EC Electromagnetic compatibility directive (EMC).

6.3.7 2002/96/EC Restriction of hazardous substances in electrical and electronic equipment directive (ROHS).

6.3.8 2002/96/EC Waste electrical and electronic equipment directive (WEEE).

6.4 Arrange for inspection of all work by the authorities having jurisdiction over the Work. On completion of the Work, present to the Contracting Officer the final unconditional certificate of approval of the inspecting authorities.

6.5 Comply with the requirements of the latest edition of the applicable UL standards, the requirements of the Authorities, National, and Local Codes, and all other authorities having jurisdiction. These Codes and Regulations constitute an integral part of these Specifications.

6.6 In case of conflict, applicable Codes take precedence over the Contract Documents. In no instance reduce the standard or Scope of Work or intent established by the Drawings and Specifications by applying any of the Codes referred to herein.

6.7 Before starting any work, submit the required number of copies of documentation to the authorities for their approval and comments. Comply with any changes requested as part of the Contract, but notify the Contracting Officer immediately of such changes, for proper processing of these requirements. Prepare and furnish any additional drawings, details or information as may be required.

7.0 STANDARDS COMPLIANCE

7.1 Where materials or equipment are specified to conform to requirements of the standards of organizations, such as the Underwriter’s Laboratory (UL) that use a label or listing as method of indicating compliance, proof of such conformance shall be submitted and approved, indexed and cross-referenced with the specification. The label or listing of the specified organization will be acceptable evidence. In lieu of the label or listing, the contractor shall submit a certificate from a testing organization adequately equipped and competent to perform such services, and approved by the Contracting Officer, stating that the item has been tested in accordance with the specified organization's test methods and that the item conforms to the specified organization's standard or code. For materials whose compliance with organizational standards or specifications is not regulated by an organization using its own listing or label as proof of compliance, a certificate from the manufacturer shall be furnished to the Contracting Officer stating that the material complies with the applicable referenced standard or specification.

8.0 SYSTEM PERFORMANCE

8.1 The Energy Management Control System shall conform to the following minimum performance standards:

8.1.1 A Graphic screen shall be capable of displaying a minimum of 20 dynamic points with current data being available within 10 seconds.

8.1.2 Binary objects shall react to a command within 10 seconds.

8.1.3 Analog object shall react to a command within 10 seconds.

8.1.4 Alarm Response Time. An object that goes into alarm shall be annunciated at the workstation within 15 seconds.

8.1.5 Custom or standard applications shall be capable of a Program Execution Frequency as often as once every 5 seconds. Controllers shall be able to completely execute direct digital control PID control loops at a frequency of once per second or faster.

8.1.6 Each workstation on the network shall be able to receive an alarm within 5 seconds of other workstations.

8.1.7 System shall be capable to report values with minimum end-to-end accuracy listed in Table 1 System Accuracy.

8.1.8 Control loops shall maintain stability and accuracy as measured by the variable at setpoint within tolerances listed in Table 2 Control Stability and Accuracy.

Table 1 Reporting Accuracy

Measured Variable Reported Accuracy Space Temperature ±0.5ºC (±1ºF) Ducted Air ±0.5ºC (±1ºF) Outside Air ±1.0ºC (±2ºF) Dew Point ±1.5ºC (±3ºF) Water Temperature ±0.5ºC (±1ºF) Delta-T ±0.15ºC (±0.25ºF) Relative Humidity ±5% RH Water Flow ±2% of full scale Airflow (terminal) ±10% of full scale (see Note 1) Airflow (measuring stations) ±5% of full scale Airflow (pressurized spaces) ±3% of full scale Air Pressure (ducts) ±25 Pa (±0.1 in. w.g.)

Air Pressure (space) ±3 Pa (±0.01 in. w.g.)

Water Pressure ±2% of full scale (see Note 2) Electrical (A, V, W, Power Factor) ±1% of reading (see Note 3) Carbon Monoxide (CO) ±5% of reading Carbon Dioxide (CO2) ±50 ppm

Note 1: Accuracy applies to 10% - 100% of scale Note 2: For both absolute and differential pressure Note 3: Not including utility-supplied meters

Table 2 Control Stability and Accuracy

Controlled Variable Control Accuracy Range of Medium

Air Pressure

±50 Pa (±0.2 in. w.g.)

±3 Pa (±0.01 in. w.g.)

0-1.5 kPa (0-6 in. w.g.)

-25 to 25 Pa (-0.1 to 0.1 in.

w.g.)

Airflow ±10% of full scale Space Temperature ±1.0ºC (±2.0ºF) Duct Temperature ±1.5ºC (±3ºF) Humidity ±5% RH

Fluid Pressure

±10 kPa (±1.5 psi) ±250 Pa (±1.0 in.

w.g.)

MPa (1-150 psi) 0-12.5 kPa (0-50 in. w.g.)

differential

9.0 COORDINATION

9.1 All work shall be performed at times acceptable to the Contracting Officer and/or the Construction Manager. Provide work schedule at the start of the job for the approval of the Contracting Officer/Construction Manager. Schedule shall show when all staff and sub-contractors shall be on-site.

9.2 Organize all sub-contractors and ensure that they maintain the schedule.

9.3 Full cooperation shall be shown with other sub-contractors to facilitate installations and to avoid delays in carrying out the work.

9.4 Notify Contracting Officer and/or the Construction Manager of any changes to the schedule. Send any schedule changes and weekly progress reports via e-mail to Contracting Officer/Construction Manager.

9.5 Where, in the judgment of the Contracting Officer and/or the Construction Manager, the work could disrupt the normal operations in or around the building, contractor shall schedule work to eliminate or minimize interference.

9.6 When connecting to the existing systems advise the Contracting Officer and/or the Construction Manager and obtain permission to do so. Perform work at a time acceptable to the Contracting Officer and/or the Construction Manager and Owner.

9.7 Contact the Construction Manager to coordinate with the 56 CES/CEOIH (Foreman, HVAC Shop), to schedule with the EMCS Operators when the work will affect existing EMCS operations or communications with the installed EMCS equipment.

10.0 SUPERVISION OF PERSONNEL

10.1 Maintain qualified personnel and supporting staff at this project with proven experience in erecting, supervising, testing, and adjusting projects of comparable nature and complexity.

10.2 Supervisory personnel and their qualifications are subject to the approval of the Contracting Officer.

10.3 All personnel working on-site shall sign in as required by the Contracting Officer and shall wear company identification.

10.4 When requested and for whatever reason, remove personnel and/or support staff from project. Take immediate action.

11.0 SYSTEM DESIGN AND RESPONSIBILITY

11.1 The drawings do not show conduit size or wire type to link the various elements of the system. The EMCS contractor is responsible for designing these links in view of the present and future capabilities.

11.2 The Contractor is responsible for supplying sufficient Controllers of all types to meet the intent of the specification. The quantity and point content of the Controllers must be approved by the Contracting Officer prior to installation.

12.0 PRODUCTS

12.1 Materials and equipment shall be essentially the catalogued products of manufacturers regularly engaged in production of such materials or equipment and shall be manufacturer's latest standard design that complies with the specification requirements. Where two units of the same class of equipment are required, these units shall be products of a single manufacturer, and the component parts of the system shall be the products of a single manufacturer. Each major component of equipment shall have the manufacturer's name and address and the model and serial number on a nameplate securely attached in a conspicuous place.

13.0 ELECTRICAL WORK, WIRING AND SAFETY

13.1 Electrical work shall be in accordance ANSI/NFPA 70 and the local Electrical Code. Electrical wiring, terminal blocks and other high voltage contacts shall be fully enclosed or properly guarded and marked to prevent accidental injury to personnel. All wiring shall conform to the most stringent requirements of the local electrical authority. Refer to Division 26 00 00 for electrical requirements.

13.2 All wiring associated with and required by the EMCS shall be the responsibility of this contractor. The term "wiring" shall be construed to include furnishing of wire, conduit, and miscellaneous material and labor as required to install a total working system. If departures from the contract documents are deemed necessary by the contractor, details of such departures, including changes in related portions of the project and the reasons therefore, shall be submitted with the drawings to the Contracting Officer for approval.

14.0 MANUFACTURERS RECOMMENDATIONS

14.1 Where installation procedures, or any part thereof, are required to be in accordance with the recommendations of the manufacturer of the material being installed, printed copies of these recommendations shall be furnished to the Contracting Officer with shop drawing submission.

Installation of the item will not be allowed to proceed until the recommendations are received. Failure to furnish these recommendations shall be cause for rejection of the material.

15.0 NAMEPLATES

15.1 Nameplates shall be provided for all control items listed or shown in the submittal and approved control diagrams. Each inscription shall identify its function, such as "mixed air controller", "cold deck sensor" in official languages etc. and when applicable, its position. Size of nameplates shall be 1 inch by 3 inches minimum. Lettering shall be minimum ¼ inch high normal black lettering. Submit duplicate samples of identification tags and lists of wording proposed for approval.

16.0 PRELIMINARY DESIGN REVIEW

16.1 The EMCS contractor shall submit a preliminary design document for review. This document shall contain the following information:

16.1.1 Provide a description of the proposed system along with a system architecture diagram with the intention of showing the contractors solution to meet this specification.

16.1.2 Provide product data sheets and a technical description of all direct digital controller hardware required to meet specifications listed herein.

16.1.3 Open Protocols - For all direct digital controller hardware proof of conformance to LonMark

Certification and interoperability guidelines including the provision of all controller XIF files.

Provide complete description and documentation of any proprietary services and/or objects where used in the system. Provide a description and samples of Operator Workstation graphics and reports.

16.1.4 Provide a URL address for the Contracting Officer to view the proposed web based EMCS through a standard web browser.

16.1.5 Provide an overview of the EMCS contractor’s local/branch organization, local staff, recent related project experience with references, and local service capabilities.

16.1.6 Provide information on the EMCS contractor’s project team including project organization, project manager, project engineer, programmers, project team resumes, and location of staff.

16.1.7 Project Schedule of work indicating:

16.1.7.1 Intended sequence of work items

16.1.7.2 Start date of each work item

16.1.7.3 Duration of each work item

16.1.7.4 Planned delivery dates for ordered material and equipment and expected lead times

16.1.7.5 Milestones indicating possible restraints on work by other trades or situations.

17.0 SUBMITTALS

17.1 Dur ing t he des ig n phase and m in im um 90 days before the start of construction, submit 8 hard copies and 1 soft copy of manufacturer’s information and shop drawings. If the project is awarded as a Design Bid Build type contract, the controls contractor must submit their full EMCS system design prior to “Final Design” phase to ensure Luke EMCS personnel have sufficient review period of the submittal documents. Drawings to be in AutoCAD or VISIO and PDF on a minimum of 11” X 17” paper and Sequence of Operations and Points List (Input/output Summary) shall be in Word and Excel format (latest versions) structured using menu format for easy loading and retrieval on the OWS.

17.2 Provide in completely coordinated and indexed package to assure full compliance with the contract requirements. Piecemeal submittal of data is not acceptable and such submittals will be returned without review. Information shall be submitted for all material and equipment the contractor proposes to furnish under terms of this contract work. Arrange the submittals in the same sequence as these specifications and reference at the upper right-hand corner the particular specification provision for which each submittal is intended. Submittals for each manufactured item shall be manufacturer's descriptive literature (equipment specification), equipment drawings, diagrams, performance and characteristic curves, and catalog cuts, and shall include the manufacturer's name, trade name, catalog model or number, nameplate data, size layout dimension, capacity, specification reference, applicable specification references, and all other information necessary to establish contract compliance.

17.3 Control System Shop Drawings

17.3.1 Schematic diagram of each controlled system. Label control points with point names.

17.3.2 Detailed system architecture showing all points associated with each controller, controller locations, and describing the spare point’s capacity at each controller and EMCS LAN.

17.3.3 Bill of Material for each controlled system. List each control system element in a table. Show element name, type of device, manufacturer, model number, and product data sheet number.

17.3.4 Specification sheets for each item including manufacturers descriptive literature, drawings, diagrams, performance and characteristic curves, manufacturer and model number, size, layout, dimensions, capacity, etc.

17.3.5 Control schematics with narrative description and control descriptive logic fully showing and describing operation and/or manual procedures available to operating personnel to achieve proper operation of the building, including under complete failure of the EMCS.

17.3.6 Shop drawings for each input/output point showing all information associated with each particular point including sensing element type and location; details of associated field wiring schematics and schedules; point address; software and programming details associated with each point; and manufacturer's recommended installation instructions and procedures for each type of sensor and/or transmitter.

17.4 Direct Digital Control System Hardware

17.4.1 LonMark Certification and XIF file for each submitted type of LonWorks controller (This includes Mechanical equipment with Factory Mounted Controls)

17.4.2 Bill of materials indicating quantity, manufacturer, model number, and relevant technical data of equipment to be used.

17.4.3 Manufacturer's description and technical data including product specifications and installation and maintenance instructions for items listed herein:

17.4.3.1 Direct digital controllers (LonWorks Only)

17.4.3.2 Sensors and Transmitters

17.4.3.3 Transducers

17.4.3.4 Actuators

17.4.3.5 Automatic Control Valves

17.4.3.6 Automatic Control Dampers

17.4.3.7 Air Flow Stations

17.4.3.8 Control panels

17.4.3.9 Operator interface equipment

17.4.3.10 Ancillary equipment such as relays, power supplies and wiring

17.4.4 Riser diagrams showing control network layout, communication protocol, and wire types.

17.4.5 Network diagram of control, communication, and power wiring for EMCS Server and OWS installation.

18.0 AS-BUILT DOCUMENTATION (OPERATING and MAINTENANCE MANUALS)

18.1 As-built documentation shall consist of 4 hard copies and one soft copy for all information described below

18.2 The final documentation package shall include:

18.2.1 Hard and soft copies of all control drawings.

18.2.2 Flow charts.

18.2.3 Manufacturer’s technical data sheets for all hardware and software.

18.2.4 Factory operating and maintenance manuals with any customization required.

18.2.5 Soft copies of programming and front-end software and each controller’s database. Hard copy output of programming is not necessary.

18.2.6 Provide clear, concise, typewritten and soft copy descriptions of all control sequences in the working language.

18.2.7 Soft copy text files shall be in Microsoft Word format.

18.2.8 Copy of all graphics files

18.3 Each instruction and reference manual shall be bound in hardback, 3 ring, binders or an approved equivalent shall be provided to the Contracting Officer. Binders to be no more than 2/3 full. Each binder to contain index to full volume. One complete set of manuals shall be furnished prior to the time that the system or equipment tests are performed, and the remaining manuals shall be furnished at acceptance.

The identification of each manual's contents shall be inscribed on the cover and spine. The manuals shall include the names, addresses and telephone numbers of each subcontractor installing equipment systems and of the local representatives for each item of equipment and each system. The manuals shall have a table of contents and be assembled to conform to the table of contents with the tab sheets placed before instructions covering the subject. Additionally, each manual shall contain a comprehensive index of all manuals submitted in accordance with this paragraph. Manuals and specifications shall be furnished which provide full and complete coverage of the following subjects:

18.3.1 Operational Requirements: This document shall describe in concise terms, all the functional and operational requirements for the system and its functions that have been implemented. It shall be written using common terminology for building operation staff and shall not presume knowledge of digital computers, electronics or in-depth control theory.

18.3.2 System Operation: Complete step by step procedures for operation of the system, including required actions at each operator station; operation of computer peripherals; input and output formats; and emergency, alarm and failure recovery. Step-by-step instructions for system startup, back-up equipment operation, and execution of all system functions and operating modes shall be provided.

18.3.3 Maintenance: Documentation of all maintenance procedures for all system components including inspection, periodic preventive maintenance, fault diagnosis, and repair or replacement of defective module. This shall include calibration, maintenance, and repair or replacement of all system hardware.

18.3.4 Test Procedures and Reports: The test implementation shall be recorded with a description of the test exercise script of events and documented as test procedures. A provision for the measurement or observation of results, based on the previously published test specification, forms the test reports. The procedures record and the results of these exercises shall be conveniently bound and documented together.

18.3.5 Configuration Control: Documentation of the basic system design and configuration with provisions and procedures for planning, implementing, and recording any hardware or software modifications required during the installation, test, and operating lifetime of the system. This shall include all information required to ensure necessary coordination of hardware and software changes, data link or message format/content changes, and sensor or control changes in the event system modification are required, and to fully document such new system configurations.

PART 2 – PRODUCTS (GENERAL)

1.0 SYSTEM DESCRIPTION / SCOPE OF WORK

1.1 Energy Management Control System (EMCS) This contractor shall be responsible for the hardware and software for the enterprise framework and system integration required for the complete Energy Management Control System. The EMCS shall be comprised of Network Control Units (NCU) connected to the Building Automation System local area network (EMCS LAN). Access to the EMCS, either through a Workstation on the EMCS LAN or within the building. Each NCU shall communicate to LonMark Certified LonWorks controllers provided under the Programmable Controllers section. The system includes Network Control Unit(s) (NCU), software and programming of the NCU, development of all graphical screens, setup of schedules, trends, logs and alarms, network management and connection of the NCU to the local area network.

2.0 SYSTEM DESIGN

2.1 The system shall consist of a network of Network Control Units (NCUs), interoperable Local Control

Units (LCUs) and Terminal Control Units (TCUs) (VAV Box Controllers, Fan Coil Unit Controllers, etc.).

All controllers for terminal units, air handling units (AHU) and controllers shall communicate and share data, utilizing LonWorks communications protocols only.

2.2 The proposed system must maintain strict adherence to Device Profile and/or Functional Profiles identified in LonMark Interoperability Guideline standards to assure interoperability between all system components. LonWorks system must be certified and listed on LonMark web site. Systems based on vendor specific proprietary hardware or software will not be considered for this project.

2.3 Systems utilizing gateways will not be considered for this project. A gateway is considered to be a device or controller where the sole function is mapping of data points from one protocol to another. A gateway device cannot perform higher-level energy management functions such as Outdoor Air Optimization, Electrical Demand Limiting and the like.

2.4 A hierarchical topology is required to assure reasonable system response times and to manage the flow and sharing of data without unduly burdening the customer’s internal Intranet network. Systems employing a flat single tiered architecture shall not be acceptable. Maximum acceptable response time from any alarm occurrence (at the point of origin) to the point of annunciation shall not exceed 10 seconds for network connected user interfaces.

2.5 User Access - The supplied system must incorporate the ability to access all data using standard Web browsers without requiring proprietary operator interface and configuration programs.

2.6 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 the installed server for all database access. Systems requiring proprietary database and user interface programs shall not be acceptable.

2.7 Software Tools - All software tools needed for full functional use, including programming of controllers, network management and expansion, and graphical user interface use and development, of the EMCS described within these specifications shall be provided to the owner or his/her designated agent. Any licensing required by the manufacturer now and to the completion of the warranty period, including changes to the licensee of the software tools and the addition of hardware corresponding to the licenses, to allow for a complete and operational system for both normal day to day operation and servicing shall be provided. Any such changes to the designated license holders shall be made by the manufacturer upon written request by the owner or his/her agent. Any cost associated with the license changes shall be identified within the EMCS submittals.

2.8 SOFTWARE LICENSE AGREEMENT - The Owner shall sign a copy of the manufacturer's standard software and firmware licensing agreement as a condition of this contract. Such license shall grant use of all programs and application software to Owner as defined by the manufacturer's license agreement, but shall protect manufacturer's rights to disclosure of trade secrets contained within such software. 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, and application-level software developed for the project. This shall include all custom, job specific software code, databases and documentation for all configuration and programming that is generated for a given project and/or configured for use with the NCU, Server, OWS and any related LAN/WAN/Intranet connected routers and devices. Any and all required User IDs and passwords for access to any component or software program shall be provided to the owner.

Network Control Units shall be Tridium based, Minimum version of 3.6:

a. brandid can equal anything but; brandid = “Distech” is preferred.

b. accept.station.in = “*”

c. accept.station.out =”*”

d. accept.wb.in = “*”

e. accept.wb.out = “*”

3.0 DYNAMIC DATA ACCESS

3.1 All operator devices shall have the ability to access all point status and application report data, or execute control functions for any and all other devices via the local area network. Access to data shall be based upon logical identification of building equipment.

4.0 NETWORKS

4.1 Design for the Network LAN (NCU LAN) shall include the following provisions

4.1.1 The Server and OWS shall communication to the NCUs utilizing standard Ethernet to IEEE 802.3 Standards. Products utilizing Manufacturer specific proprietary protocols, gateways, or protocol converters are not acceptable for this project.

4.1.2 The NCU LAN shall be a 100 Megabits/sec Ethernet network supporting Java, XML, HTTP, SOAP, OBIX, SNMP and SMTP for maximum flexibility for integration of building data with enterprise information systems and providing support for multiple Network Control Units (NCUs), user workstations and where specified, a local server. Local area network minimum physical and media access requirements:

4.1.2.1 Ethernet; IEEE standard 802.3

4.1.2.2 Cable; 100 base-T, UTP-8 wire, category 5

4.1.2.3 Minimum throughput; 100 Mbps

4.2 Design for the Building Automation System LAN (LCU and TCU LAN) shall include only LonWorks architecture provisions:

4.2.1 The EMCS must be based on Open Systems. The EMCS can employ LonTalk communications utilizing the Echelon Neuron chip and transceiver, which conforms to ISO/IEC 14908-1: Open Data Communication in Building Automation, Controls and Building Management – Control Network Protocol. The content of messages shall be the manufacturers standard. The Neuron chip and a transformer-isolated transceiver shall provide for 78.8 kbps communications over Echelon approved LonWorks cabling.

PART 2A – OPERATOR WORKSTATION (OWS) HARDWARE

5.0 WORKSTATION HARDWARE REQUIREMENTS:

5.1.1 The work station exists on the Luke Air Force Base local area network. The

Workstation is a server class machine running Windows Server 2003 or newer and must be verified at the time of award. It contains the Graphical User Interface Software, V3.7.106 (as of Aug 31, 2015) and provides the network management functionality for the EMCS. Contractor must coordinate with Luke EMCS personnel regarding current version upon award of the contract.

6.0 GRAPHICAL USER INTERFACE WORKSTATION HARDWARE (LAPTOP COMPUTER):

6.1.1 Provided by Luke Air Force Base

PART 2B: OPERATOR WORKSTATION (OWS) SOFTWARE

7.0 OPERATOR WORKSTATION SOFTWARE

7.1 Operating System: The Operator Workstation software exists at various locations including laptop PC’s used by operating personnel. If required, the software shall run on Microsoft Windows 7 or later.

7.2 The software shall employ browser-like functionality for ease of navigation. It shall include a tree view (similar to Windows Explorer) for quick viewing of, and access to, the hierarchical structure of the database. In addition, menu-pull downs, and toolbars shall employ buttons, commands and navigation to permit the operator to perform tasks with a minimum knowledge of the HVAC Control System and basic computing skills. These shall include, but are not limited to, forward/backward buttons, home button, and a context sensitive locator line (similar to a URL line), that displays the location and the selected object identification.

7.3 Real-Time Displays. The OWS, shall at a minimum, support the following graphical features and functions:

7.3.1 Graphic screens shall be developed using Luke Air Force Base approved Graphic Standards Only. If job specific graphics are developed to satisfy the project requirements, the contractor shall provide an electronic update of the library graphic pages at project completion. Graphic screens shall be developed using GIF, PNG, JPG or ICO file format. Use of proprietary graphic file formats shall not be acceptable. In addition to, or in lieu of a graphic background, the GUI shall support the use of scanned pictures.

7.3.2 Graphic screens shall have the capability to contain objects for text, real-time values, animation, color spectrum objects, logs, graphs, HTML or XML document links, schedule objects, hyperlinks to other URLs, and links to other graphic screens.

7.3.3 Graphics shall support layering and each graphic object shall be configurable for assignment to one a layer. A minimum of six layers shall be supported.

7.4 Modifying common application objects, such as schedules, calendars, and set points shall be accomplished in a graphical manner. Schedule times will be adjusted using a graphical slider, without requiring any keyboard entry from the operator. Holidays shall be set by using a graphical calendar, without requiring any keyboard entry from the operator.

7.5 Commands to start and stop binary objects shall be done by right-clicking the selected object and selecting the appropriate command from the pop-up menu. No entry of text shall be required.

7.6 Analog values shall be adjusted by right-clicking the selected object and using a graphical slider to adjust the value, such as set points. No entry of text shall be required.

7.7 System Configuration. Access to the GUI is performed in two ways: First, LAFB 56th Civil Engineering, EMCS personnel have licensed copies of the GUI software. The LAFB, Communications Squadron, IT Department controls which Work Stations the software is installed and licensed to operate under, and, second, the Workstation contains the operational copy of the GUI. Access to the Workstation is via the Communications Squadron, IT Department, and server farm access. At a minimum, the OWS shall permit the operator to perform the following tasks, with proper password access:

7.7.1 Create, delete or modify control strategies.

7.7.2 Add/delete objects to the system.

7.7.3 Tune control loops through the adjustment of control loop parameters.

7.7.4 Enable or disable control strategies.

7.7.5 Generate hard copy records or control strategies on a printer.

7.7.6 Select points to be alarm-able and define the alarm state.

7.7.7 Select points to be trended over a period of time and initiate the recording of values automatically.

7.8 On-Line Help. Provide a context sensitive, on-line help system to assist the operator in operation and editing of the system. On-line help shall be available for all applications and shall provide the relevant data for that particular screen. Additional help information shall be available through the use of hypertext. All system documentation and help files hall be in HTML format.

7.9 Security. Each operator shall be required to log on to that system with a user name and password in order to view, edit add, or delete data. System security shall be selectable for each operator. The system administrator shall have the ability to set passwords and security levels for all other operators.

Each operator password shall be able to restrict the operators’ access for viewing and/or changing each system application, full screen editor, and object. Each operator shall automatically be logged off of the system if no keyboard or mouse activity is detected for a user adjustable time period. This auto log-off time shall be set per operator password. All system security data shall be stored in an encrypted format.

7.10 System Diagnostics. The system shall automatically monitor the operation of all workstations, printers, modems, network connections, building management panels, and controllers. The failure of any device shall be annunciate to the operator.

7.11 Alarm Console. The system shall be provided with a dedicated alarm window or console. This window will notify the operator of an alarm condition, and allow the operator to view details of the alarm and acknowledge the alarm. The use of the Alarm Console can be enabled or disabled by the system administrator. When the Alarm Console is enabled, a separate alarm notification window will supersede all other windows on the desktop and shall not be capable of being minimized or closed by the operator.

This window will notify the operator of new alarms and un-acknowledged alarms. Alarm notification windows or banners that can be minimized or closed by the operator shall not be acceptable.

7.12 Operator’s workstation software shall contain an easy-to-operate system; allowing configuration of system-wide controllers, including management and display of the controller programming. This system shall provide the capability to configure controller binary and analog inputs/outputs.

7.13 The system shall be capable of utilizing third-party Windows-Based programs for such things as spread sheet analysis, graphing, charting, custom report generation, and graphics design packages. Graphics generation shall be done using standard Windows packages. No proprietary graphics generation software shall be needed.

7.14 Provide software, which enables the non-programmer operator to easily perform, tasks which are likely to be part of his/her daily routine.

7.15 The operator's console shall provide facilities for manual entries and visual displays enabling an operator to enter information into the system and obtain displays and logs of system information. All requests for status, analog, graphic displays, logs, and control shall be selected from the operator's console. The operator interface shall minimize the use of typewriter style keyboard by implementing a mouse or similar pointing device and "point and click" approach to command selection. The facility shall be provided to permit the operator to perform the following tasks:

7.15.1 Automatic logging of digital alarms and change of status message.

7.15.2 Automatic logging of all analog alarms.

7.15.3 System changes (alarm limits, set-points, alarm lock-outs, etc.).

7.15.4 Display specific points as requested by the operator.

7.15.5 Provide reports as requested by the operator and on Scheduled basis where so required.

7.15.6 Display graphics as requested by the operator.

7.15.7 Display help information.

7.15.8 Provide trend logs as required by the operator.

7.15.9 Provide manual control of digital and analog outputs as required by the operator.

7.15.10 Direct the hard copy output of information to the device selected by the operator.

7.15.11 Data displayed on monitor to cyclic update as appropriate.

7.16 Online changes:

7.16.1 Alarm limits

7.16.2 Setpoints

7.16.3 Deadbands

7.16.4 Changes/deletions/additions of points.

7.16.5 Control and change of state changes.

7.16.6 Time of day, day, month, year.

7.16.7 Control loop control description changes for NCU based CMD's.

7.16.8 Control loop tuning changes

7.16.9 Schedule changes

7.16.10 Changes/additions/deletions to system graphics

7.16.11 Changes/additions/deletions to total…