BAS BPA Amendment 2 Combined 240620.pdf

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

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

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

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

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

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

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

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

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

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

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

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

D. OTHER (Specify type of modification and authority)

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

15C. DATE SIGNED

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

16C. DATE SIGNED

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

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

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

Previous edition unusable

6P1QE

Amendment 002 is here by issued to incorporate the answers to questions.

All other terms and conditions remain unchanged.

U.S. General Services Administration Capital Construction and IDV Branch Public Buildings Service, Region 6 2300 Main Street Kansas City, MO 64108

06/20/2024

INSTRUCTIONS (Back Page):

Instructions for items other than those that are self-explanatory, are as follows:

Item 1 (Contract ID Code). Insert the contract type identification code that appears in the title block of the contract being modified.

Item 3 (Effective date).

(1)

(2)

(3)

(4)

(5)

For a solicitation amendment, change order, or administrative change, the effective date shall be the issue date of the amendment, change order, or administrative change.

For a supplemental agreement, the effective date shall be the date agreed to by the contracting parties.

For a modification issued as an initial or confirming notice of termination for the convenience of the Government, the effective date and the modification number of the confirming notice shall be the same as the effective date and modification number of the initial notice.

For a modification converting a termination for default to a termination for the convenience of the Government, the effective date shall be the same as the effective date of the termination for default.

For a modification confirming the contracting officer's determination of the amount due in settlement of a contract termination, the effective date shall be the same as the effective date of the initial decision.

(a)

(b)

(c)

(d)

(e)

(f)

Item 6 (Issued By). Insert the name and address of the issuing office. If applicable, insert the appropriate issuing office code in the code block.

Item 8 (Name and Address of Contractor). For modifications to a contract or order, enter the contractor's name, address, and code as shown in the original contract or order, unless changed by this or a previous modification.

Items 9, (Amendment of Solicitation Number - Dated), and 10, (Modification of Contract/Order Number - Dated). Check the appropriate box and in the corresponding blanks insert the number and date of the original solicitation, contract, or order.

Item 12 (Accounting and Appropriation Data).

When appropriate, indicate the impact of the modification on each affected accounting classification by inserting one of the following entries:

(2) Accounting classification Net decrease $

Include subject matter or short title of solicitation/contract where feasible.

Item 16B. The contracting officer's signature is not required on solicitation amendments. The contracting officer's signature is normally affixed last on supplemental agreements.

(i)

NOTE: If there are changes to multiple accounting classifications that cannot be placed in block 12, insert an asterisk and the words "See continuation sheet".

Item 13. Check the appropriate box to indicate the type of modification. Insert in the corresponding blank the authority under which the modification is issued. Check whether or not contractor must sign this document. (See FAR 43.103.)

Item 14 (Description of Amendment/Modification).

Organize amendments or modifications under the appropriate Uniform Contract Format (UCF) section headings from the applicable solicitation or contract. The UCF table of contents, however, shall not be set forth in this document.

Indicate the impact of the modification on the overall total contract price by inserting one of the following entries:

(i) Total contract price increased by $

(ii) Total contract price decreased by $

(iii) Total contract price unchanged.

State reason for modification.

When removing, reinstating, or adding funds, identify the contract items and accounting classifications.

(g)

(h)

When the SF 30 is used to reflect a determination by the contracting officer of the amount due in settlement of a contract terminated for the convenience of the Government, the entry in Item 14 of the modification may be limited to --

(i) A reference to the letter determination; and

(ii) A statement of the net amount determined to be due in settlement of the contract.

(1)

(2)

(3)

(4)

(5)

(6)

STANDARD FORM 30 (REV. 11/2016) BACK

(1) Accounting classification Net increase $

Amendment 0002 is hereby issued to answer provided questions. No additional questions will be answered. Meeting agenda is attached.

S ECTION /R EFERENCE Q UESTION /R EQUEST FOR

C LARIFICATION

G OVERNMENT R ESPONSE

Agreement Section II.A Basis of Pricing/ Quoters shall complete the pricing for the base year and all option years. These rates must include all labor, materials and equipment necessary to complete the orders.

Currently the CLIN structure looks to be set up to price one specific LCAT each (e.g. CLIN 1 is BAS Installation Labor). Can we assume R6 only wants 1 LCAT quoted on each line?

Also, the quantity and type of materials is unknown, can we add into the pricing submittal a standard list price for each device we are likely to use (for example a Lynsxpsring Jenesys 8100 or 9100 controllers?)

Material pricing will be addressed at the order level.

Yes, you can assume R6 only wants 1 LCAT quoted on each line.

Solicitation III.C.4 FAR 52.212-3 Offeror Representations and Certifications – Commercial Products and Commercial Services (May 2024)

Can the Government confirm if the representations and certifications (FAR 52.212-3) are to be included with proposal submission, and, if they are to be included, are they part of the pricing submission or technical submission?

FAR 52.212-3 is completed in SAM.gov, please ensure it is accurate.

Solicitation III.C.1 FAR 52.204-24 Representation Regarding Certain Telecommunications and Video Surveillance Services or Equipment (Nov 2021); Solicitation III.C.2 FAR 52.204-26 Covered Telecommunications Equipment or Services-Representation (Oct 2020);

Solicitation III.C.3 FAR 52.209-11 Representation by Corporations Regarding Delinquent Tax Liability

Can the Government confirm if the fill-in clauses (FAR 52.204-24, FAR52.209-11) need to be completed and submitted with proposal submission, and, if they are to be included, are they part of the pricing submission or technical submission?

FAR 52.204-24 must be completed and submitted with the Pricing Submission.

FAR 52.209-11 is completed in SAM.gov, please ensure it is accurate.

or a Felony Conviction under any Federal Law (Feb 2016)

With the issuance of a new SOW, we request an extension to the due date for proposal submission to allow sufficient time for a compliant and responsive proposal.

No extension has been granted.

Solicitation II.B.1 The Government states that the price submission shall contain an SF1449;

however, no SF1449 was given. Can the Government please provide the SF1449 that is to be submitted?

Please see attached.

RFP instructions As the SOW was just released on 6/13/2024, can we extend the due date for proposals by 2 weeks?

No extension has been granted.

BAS BPA Amendment 1 SOW The SOW does not specify location beyond R6, is the SOW intended to cover replacement of all JCI NAE/NCE and VAV/AHU controllers across the region?

Yes. To be determined at the order level.

BAS BPA Amendment 1 SOW The SOW does not include device count, is there a certain number of each device type we should plan for in order to provide accurate pricing?

Pricing for devices will be determined at the order level.

BAS BPA Amendment 1 SOW Will we have an opportunity to perform a site survey prior to proposal deadline?

No. The sites have not been designated. The awarded vendor will have the opportunity to do site visits at the order level.

BAS BPA Amendment 1 SOW - Removal/Replacement of Preparatory Network VAV Controllers

The SOW identifies Network VAV Controllers. Does this section identify IP-based Networked controllers or do they identify any networked (not stand alone) controllers that may be connected to MSTP, Lonwork, or N2 network? If so, does the GSA want to N2 networked devices to be replaced with non-proprietary controllers and the N2 bus to be changed to either BACnet (preferred) or Lonwork network?

Any controller to be used in the GSA network will be required to be non-proprietary IP based controllers and non-proprietary VAV controllers.

BAS BPA Amendment 1 SOW Section 5.a.iii.3.c.i

Section cites “Region 6 BAS Graphic Guideline”, could you provide the guideline for consideration of LOE for appropriate pricing?

Please see attached.

BAS BPA Amendment 1 SOW Section 7.f.i

Section cites “Region 6 Naming Conventions Guideline” could you provide the guideline for consideration?

Please see attached.

Pricing requirements Will Govt consider allowing additional labor categories to provide flexibility in responding to potential task orders?

No.

JENEsys Edge is typically associated with a specific supplier, will this specific device brand be required, or can we use competing brands of the same product?

JENEsys Edge has been removed from the SOW.

How many servers currently exist and how many are planned and how are they organized?

There is a total of 11 servers currently, 2 are Metasys and 9 are Niagara. Niagara are running the most current version 4.10. Metasys is 9.

Does this project include any CUI, and if so what level of CMMC will be required?

Yes this project contains building systems data, network data, or building diagrams then it contains CUI @ a High level for CMMC.

Do we have to be registered to do business in each of the four states?

No, just Niagara N4 certified.

“Each service employee who will perform the services under the contract will spend only a small portion of his or her time (a monthly average of less than 20 percent of the available hours on an annualized basis, or less than 20 percent of available hours during the contract period if the contract period is less than a month) Servicing the Government contract; …” As a small business we may not be able to adhere to this statement, for example if more than 50% of our annual sales were to come from this contract then surely our technicians will spend more than 20% of their time working on them. Is this a requirement we must uphold?

We are not requesting services under FAR 22.1003-4(c)(1) or (d)(1), this does not apply.

When we are being evaluated will we be graded based on the individual, project, or company?

Please see Section IV - Method of Award in the Solicitation.

We are unable to find a list of buildings for the scope of work. There are evidently 26 buildings within the four states. Will a list of buildings be provided to base our proposal on?

Please see attached.

For the buildings within the scope of work, are there network diagrams (riser diagrams) of the existing BAS infrastructure to base our proposal on?

Your price quote should be based upon the information requested in the Solicitation Section

II.B.

Why is the solicitation for one base year and four option years in lieu of a set PoP?

This RFQ is to establish a Blanket Purchase Agreement for work to be solicited on an order by order basis. Option periods give the Government the right but not obligation to extend the POP of this BPA.

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

1. REQUISITION NUMBER PAGE 1 OF

2. CONTRACT NO. 3. AWARD/EFFECTIVE

DATE

4. ORDER NUMBER 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME b. TELEPHONE NUMBER (No collect 8. OFFER DUE DATE/

9. ISSUED BY

13b. RATING

14. METHOD OF SOLICITATION

CODE

15. DELIVER TO 16. ADMINISTERED BY CODE

18a. PAYMENT WILL BE MADE BY CODE17a. CONTRACTOR/

OFFEROR

CODE

FACILITY

CODE

CODE

TELEPHONE NO.

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN

OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK

BELOW IS CHECKED

RFQ IFB RFP

SEE ADDENDUM

19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Govt. Use Only)

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED

29. AWARD OF CONTRACT: REF. OFFER

DATED . . YOUR OFFER ON SOLICITATION

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR

30b. NAME AND TITLE OF SIGNER (Type or print) 30c. DATE SIGNED

31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

31b. NAME OF CONTRACTING OFFICER (Type or print) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA - FAR (48 CFR) 53.212

10. THIS ACQUISITION IS UNRESTRICTED OR

NAICS:

SIZE STANDARD:

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

SET ASIDE: % FOR:

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

ARE ARE NOT ATTACHED

ARE ARE NOT ATTACHED

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1, 52.212-4. FAR 52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA

SMALL BUSINESS

EDWOSB

8 (A)

HUBZONE SMALL

BUSINESS

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

47PG1024Q0002

Julie Vo 816-308-3601

6P1QE 100

6P1QE

Acquisition Management Division Capital Construction and Indefinite Delivery Vehicle Branch 2300 Main Street Kansas City, MO 64108 USA

See below for additional information

Kristin Gilliland

261210

06/14/2024

LOCAL TIME

07/08/24 10:00

AM (CST

Acquisition Management Division Capital Construction and Indefinite Delivery Vehicle Branch 2300 Main Street K Cit MO 64108 USA

STANDARD FORM 1449 (REV. 2/2012) BACK

19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED:

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE 42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

40. PAID BY

32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f. TELPHONE NUMBER OF AUTHORZED GOVERNMENT REPRESENTATIVE

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

33. SHIP NUMBER 34. VOUCHER NUMBER 35. AMOUNT VERIFIED

CORRECT FOR

PARTIAL FINAL

37. CHECK NUMBER

38. S/R ACCOUNT NO. 39. S/R VOUCHER NUMBER

36. PAYMENT

COMPLETE PARTIAL FINAL

GSA Public Building Services Energy and Sustainability Branch

Revision C - Dated 3/25/2016

Building Automation System (BAS)

Graphic Guidelines

BACKGROUND

The purpose of this document is to serve as a guideline to be used in the modification and creation of graphics on Region 6 building automation systems. In the past, as projects take place graphics were left to the awarded contractor to create which lead to mixed results across the region without standardization between buildings. By instituting a guideline for contractors to work from, it will ensure continuity between locations and provide a platform for contractors to use in developing BAS graphical interfaces used on Region 6 facilities.

APPLICABILITY

This document shall serve as the guideline on all BAS related projects in which graphic displays are used to depict various building automation systems. The applicability of this document shall include all projects that involve the modification of existing building automation systems and projects that involve newly installed building automation systems. In instances that minor additions to a building automation system occurs, this document will also apply to the equipment items installed as part of the small project to match existing conditions or to develop the standard for all future additions to follow. Any modification or updates that occur to the building automation system shall require the awarded contractor to follow these same guidelines.

Exceptions shall be made in like-for-like device replacements for the purposes of repairing a defective device.

AFFECTED SYSTEMS

Building automation systems that are affected by this document shall include building automation systems for HVAC related systems (i.e. chillers, pumps, VAV controllers, etc.), lighting control automation systems and other related building automation systems in which graphics are specified as part of the scope of work.

GRAPHIC GUIDELINES

The following represents the guidelines that will be used in the creation of graphics for building automation systems. Graphics should be designed to allow complete navigation to all HVAC, Lighting, and other building automation equipment. Directory pages may also need to be created for navigation purposes. Guidelines are broken down into sections and sub sections for more specific details. Please verify all sections for applicability.

1. Page Layout

a. Page size - All pages must be formatted for 1024 x 768 dpi.

b. Main page - The initial page must include basic building information such as address, building number, outside air temperature, outside humidity, dedicated link hot-link to the utility page, and may include a picture of the exterior of the facility.

c. Conditional Formatting - If applicable, apply conditional formatting to areas that would visually display status of the equipment. For example, the color of a status box should indicate a green status if the unit is running and a red status if the unit is in alarm. Another example would be zone temperature reference blocks that would indicate a green or white status for a normal zone temperature, red for a hot condition, and blue for a cold condition.

d. Manual Overrides - If applicable, conditional formatting should also apply that will include a color change of the value for operator manual overrides. This will provide a visual indicator that a set point is overridden. Color shall be something other than blue, red, or green.

e. Backgrounds - All page backgrounds must be neutral in color or basic pattern.

Color or basic pattern must be uniform throughout the entire system.

2. Minimum Button Requirements

a. All pages - Each page shall include a “Home” button that takes the user back to the home page as well as a “Previous” button that will navigate to the previous page the user last visited. These buttons shall be uniform throughout each page located in the top right corner.

i. NOTE: If side panel navigation windows are used in the creation of graphics, all referenced buttons as listed in this standard must still be included as part of the minimum graphic requirements.

b. Floor Plans - All pages that represent a specific floor plan shall include a basic diagram of the area, links to each of the devices found on the floor plan, zone temperatures, and buttons used to navigate the user to other floor plans (ie. 1st floor will contain buttons to navigate to floors 2, 3, 4, and etc.).

i. NOTE: Display data shall mimic the location of the equipment in relation to the floor plan. This will ensure a graphical location of devices (ie.

thermostat and corresponding VAV in relation to the floor plan).

c. One click Hotlinks - Added to each equipment graphic page from floor plan pages.

3. Use of equipment specific graphics

a. All equipment graphics used throughout the system shall remain consistent for each piece/type of equipment. This will ensure that all equipment graphics per applicable equipment type look uniform in appearance (ie. all VAV graphics are the same).

i. Special instances - In the case where the graphic does not accurately represent the device configuration accurately (ie. air handler that contains multiple fan motors versus a standard air handler), graphics should represent the equipment appearance instead.

ii. All graphics shall include labeling of all normal positions and ranges of valves. These shall be placed as close to the actual device that it represents on the graphics as is possible.

iii. Point Override Feature - Each displayed point shall be individually enabled/disabled to allow mouse-driven override of digital points or changing of analog points.

1. If applicable: Points that are overridden shall be reported and shall be displayed in a coded color.

iv. All analog values represented on the graphics shall be represented by their range of real values such as 4-20mA, 0-60Hz, etc. if applicable.

These values shall accompany the 0% to 100% ranges when displayed on the graphics.

v. If applicable: Points on the graphics shall be animated to reflect the status. For example, fans shall show rotation while operating and pumps shall depict flow when in operation.

4. Minimum Page Requirements

a. All Graphic Display Pages - Must include outside air temperature, Home and Previous buttons as noted above. Font size shall be a minimum of 10 for standard text and 12 for all titles. Each page shall contain the title of the page and equipment name.

b. Home Page - As noted with the requirements noted above

c. Floor Plan Pages - Minimum of a single page per floor. In the cases where excessive amounts of equipment exists, the floor plan can be split into sections with navigation buttons that will navigate the user to the other sections of the floor.

d. Equipment Specific Pages - Each page related to a specific piece of equipment

(ie. VAV box, Air Handler, Etc.) shall include the standard graphic for that particular piece of equipment, all input data displayed, all output status data displayed, and shall allow operator changes (ie. change a setpoint).

e. Dedicated Central Plant Page - Minimum of a single page depicting the central plant along with all of the following requirements:

i. Chilled Water Leaving Temperature and Temperature Setpoint

ii. Chilled Water Return Temperature

iii. Chilled Water Supply Pressure

iv. Chilled Water Differential Setpoint

v. Condenser Water Leaving Temperature and Temperature Setpoint

vi. Condenser Water Return Temperature

vii. Hot Water Leaving Temperature and Temperature Setpoint

viii. Hot Water Supply Pressure and Pressure Setpoint

ix. Hot Water Return Temperature

x. All Valve Positions

xi. Chiller Run Status and Alarm Condition

xii. Boiler Run Status and Alarm Condition

xiii. All Motor Runs Speeds and Status

xiv. Graphic Representations of the Equipment Used in the Central Plant (ie.

Chillers, Boilers, Pumps, etc.)

xv. Outside Air Temperature and Humidity

xvi. Outside Air Wet Bulb and Setpoint if applicable

xvii. Enthalpy and Setpoint if applicable

xviii. Central Plant Energy Related Data

1. Tower Fans kW

2. Chilled Water Pumps kW

3. Condenser Water Pumps kW

4. Chilled Water BTU usage

5. Chilled Water Efficiency

f. Summary Overview Pages - Included for each piece of equipment such as;

AHU’s, Chillers, Boilers, VAV’s, Fan Powered Boxes, Lighting etc. (see lighting exception noted in the lighting section).

i. AHU page should also contain the following minimum requirements:

1. Outdoor Air Fraction Result, OAF = ((MAT-RAT) / (OAT - RAT))

2. Graphic representation of the AHU along with applicable inputs/outputs displayed

a. Static pressure and setpoint

b. Valve position and status (ie. on/off/auto)

c. Fan speed and status (ie. on/off/auto)

d. All other applicable information and buttons as noted in other sections of this standard

ii. Chiller page should also contain the following minimum requirements:

1. Graphic representation of the Chiller along with applicable chiller data such as:

a. Status

b. Setpoints

c. Temperatures

d. Alarm Condition

e. All other applicable information and buttons as noted in other sections of this standard

iii. Boilers

1. Graphic representation of the boiler along with applicable boiler data displayed

a. Status

b. Setpoints

c. Temperatures

d. Alarm Condition

e. All other applicable information and buttons as noted in other sections of this standard

iv. VAV’s

1. Graphic representation of the VAV along with applicable VAV data data displayed

a. Status

b. Setpoints

c. Temperatures

d. Damper Position

e. Name and location

f. All other applicable information and buttons as noted in other sections of this standard

v. Pumps

1. Graphic representation of the pump along with applicable pump data displayed

a. Status

b. Speed

c. Alarm Condition

d. All other applicable information and buttons as noted in other sections of this standard

vi. Lighting

1. Status

2. Setting (on/off/auto)

3. Name and location

4. All other applicable information and buttons as noted in other sections of this standard

g. Utility Data Page - Data will include all applicable data where the capability exists to monitor gas, electric, water, pulse meters and BACnet/LON/Modbus chemical treatment/cooling tower bleed data points.

5. Use of pictures

a. The use of graphics throughout the BAS shall remain consistent where applicable. For example, all VAV boxes shall use the same graphic, all fan powered VAV boxes shall do the same as well. This shall apply to all equipment.

i. Exceptions shall be made when the graphic does not meet the intended equipment. For example, in the event a non-standard air handler contains multiple fan motors that stage independently, a separate graphic shall be used to represent the air handler accurately. This exception shall supercede the need for uniform graphics to accommodate a more accurate system diagram.

b. The use of pictures to depict equipment is acceptable provided the ability to add the required data as indicated above. This form of graphics creation shall only be permitted in the event that live graphics cannot be generated from the available tools provided by the contractor and/or GSA.

i. Under no circumstance will hotlinked pictures be permitted outside of the GSA BAS network.

6. Graphic Page Override Functionality

a. Graphic pages shall also provide operator level overrides to common settings such as on/off/auto, position, speed, temperature, and other related manual overrides. The following are examples of graphic overrides that should be allowed through graphic pages that are dependent on user rights:

i. Global Pages – Enable (Set/Auto) overrides for global setpoints and global occupied/unoccupied settings

ii. AHU/Humidifier Pages – Enable (Set/Auto) overrides for vales, discharge air static pressure setpoints, damper positions, temperature settings, VFD speed settings, and humidification settings. The supply, return, and outside air fans should also have the (On/Off/Auto) override enabled as well.

iii. FPU/VAV Pages – Enable (Set/Auto) overrides for valves, flow setpoints, damper positions, temperature setpoints, and occupancy setting. In the event of a fan powered unit, enable (On/Off/Auto) overrides for the fan motor.

iv. Chiller/Boiler Plant Pages – Enable (Set/Auto) overrides for valves, flow setpoints, temperature settings, pressure settings, and VFD settings. Also enable (On/Off/Auto) overrides for the enable commands for the chillers, boilers and associated pumps.

v. Pump Pages – Enable (Set/Auto) overrides for valvles, flow setpoints, temperature settings, pressure settings, and VFD settings. Also enable (On/Off/Auto) overrides for the enable commands for the pumps.

vi. Exhaust/Transfer Fan Pages – Enable (On/Off/Auto) overrides for the enable commands for the exhaust/transfer fans. Also enable (Set/Auto) overrides for damper positions, VFD speed settings, and occupancy setting.

vii. Lighting Pages – Enable (On/Off/Auto) overrides for enable commands for the lights. Also enable (Set/Auto) overrides for the occupancy setting.

viii. Miscellaneous Equipment Pages – Enable any relevant (On/Off/Auto) and (Set/Auto) overrides on relevant settings and setpoints. This will include equipment not associated with HVAC or lighting such as plumbing and water system functions.

b. The enabled overrides noted above should be applied as applicable. In the event the equipment does not have the selected feature (ie. No outside air fan installed on the AHU), there is no need to incorporate the override. Otherwise the graphic page override functionality applies to all equipment in which the capability is present to include equipment not mentioned specifically in this section.

7. Backups

a. Backups of the graphics shall be conducted at the completion of projects each time BAS graphics are updated or modified. Backups shall occur directly to the specified location on the GSA network.

i. Location to be provided by GSA during the project implementation process

ii. Secondary backups loaded to a CD ROM are also required after the completion of BAS system upgrades or major system updates completed by the awarded contractor. The CD ROM shall be provided to the Region 6 Smart Building Program Staff and to the Building Manager of the affected facility.

8. Automated Lighting Controls

a. Automated lighting controls when incorporated into building automation systems shall follow the same guidelines with the following exceptions:

i. The use of graphics to display each device is not mandated. A page that contains multiple device instances is permitted provided it contains the following information:

1. Device name and location

2. Device Status which includes on/off as well as lighting percentage where applicable

3. Point Override Feature - Each displayed point shall be individually enabled/disabled to allow mouse-driven override of digital points or changing of analog points.

a. If applicable: Points that are overridden shall be reported and shall be displayed in a coded color.

4. If Applicable: Conditional formatted status block that turn green when on and black or white when off

9. Other Building Automation Systems

a. All other building automated systems shall follow the same guidelines listed above where applicable.

b. In the event that graphical interfaces cannot be generated, seek guidance from

GSA Smart Buildings Program personnel for guidance. It is assumed that all automation equipment shall be represented by graphics so it is best to seek formal guidance for clarification purposes.

RESTRICTIONS

The following is a list of restrictions that apply to graphics residing on GSA building automation systems. Strict adherence to this policy is mandated per GSA regulations. Violation of these restrictions can result in penalties for the awarded contractor.

1. Hotlinks - Not permitted to websites that reside outside of the GSA BAS network. All hotlinks must reside within the BAS network without exception.

2. Old BAS graphics - Not permitted to remain as part of the building automation system. If graphics are no longer in use they are to be removed from the system completely.

3. Prior to loading “Floor Plan” graphic pages, approval is required from the GSA Property

Manager. Once approval is provided, the awarded contractor can load the graphics to the server.

GSA Public Building Services Energy and Sustainability Branch

Revision B - Dated 2/18/2016

Building Automation System (BAS)

Point Naming Convention Guidelines

The intent of this section is to establish and require a consistent means of naming building automation points across the GSA portfolio. The term ‘Point’ is a generic description for the class of object represented by analog and binary inputs, outputs, and values either physical or virtual.

The Contractor shall configure the systems with the perspective of the GSA’s overall portfolio and not just for one project in particular. The value of using an alphanumeric point-naming standard is to provide a unique, logical and concise description of the purpose and function of the point being described.

All systems shall use this naming convention and process. Any deviations from this process require prior approval of the GSA and/or their representative1. Point naming shall be consistent through system drawings, records, files and documents.

A Point Summary Table shall be created and kept current throughout the duration of the Project, by the Contractor, as the Master List of all points for the Project. Project closeout documents shall include an up-to-date accurate Point Summary Table. The Contractor shall submit the final Point Summary Table for approval, prior to final acceptance of the system, for each individual project. The Point Summary Table shall be used as a reference and guide during the Commissioning process.

POINT NAMING AND IDENTIFICATION

The following shall be used as a basis of design. The goal is to apply logic when possible, and keep the design simple and concise, which in turn will minimize the chance of inadvertently introducing needless complexity.

A consistent point naming convention shall be utilized to facilitate familiarity and operational ease across the GSA portfolio. Inter-facility consistency shall be maintained to ensure transparent operability to the greatest degree possible. The tables below detail the object naming convention and general format of the descriptor string. A maximum of 40 characters shall be used.

Other attributes such as point address, descriptors and other system specific information may be required. The same level reasoning should be applied when establishing the framework for this as well.

1 Where not defined by GSA Point Naming Guideline, contractor shall reference Project Haystack

Point / Object Name Requirements (Central Equipment)

Sample: DC0001ZZ _02_AHU_05_ RaTmp

(DC0001ZZ) ‐ Building Code 8 alpha characters – Facility ID

(_) 1 character ‐ Underscore; acts as a separator2

(02) –Equipment Floor Location 2 characters

(_) 1 character ‐ Underscore; acts as a separator2

(AHU) ‐ Equipment Type 3 alpha characters3

2 upper case alpha and/or numeric characters

(_) 1 character ‐ Underscore; acts as a separator2

(RaTmp) –Point Name Component 1 ‐ 15 alpha characters4

Point / Object Name Requirements (Distribution Equipment)

Sample: DC0001ZZ _02_VAV_0005_ RaTmp

(DC0001ZZ) ‐ Building Code 8 alpha characters – Facility ID

(_) 1 character ‐ Underscore; acts as a separator2

(02) –Equipment Floor Location 2 characters

(_) 1 character ‐ Underscore; acts as a separator2

(VAV) ‐ Equipment Type 3 alpha characters3

4 upper case alpha and/or numeric characters2

(_) 1 character ‐ Underscore; acts as a separator

(RaTemp) – Point Name Component 1 – 15 alpha characters4

2 Underscores or other characters are prohibited in point naming by some Building Automation System software. Consult with the system manufacture to confirm proper application and consider possible alternatives.

3 Reference GSA Equipment Naming Standard 4 Reference GSA Std Point Name Components

POINT SUMMARY TABLE

The Point Summary Table shall contain all data fields on a single row per point. The purpose of a Point Summary Table is to have a single master source for all point information in the building that is easily sorted and kept up-to-date. The point description shall be an easily understandable English-language description of the point.

A sample Point Summary Table is displayed below:

Temperature Number Fahrenheit

The following specific references exist as part of the GSA Point Naming Database.xlsx:

‐ GSA Equipment Naming Standard ‐ GSA Standard Point Name Components

R6 BAS connected Buildings