B.08.03 W912DQ24R4007 Amendment 0006.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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

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

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

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

FAR (48 CFR) 53.243

Fort Riley Hangar, Fort Riley, Kansas The purpose of this amendment is to update information in the SPECIFICATIONS section of the solicitation.

Proposal due date remains unchanged- March 25, 2024 at 11:00a.m.

SEE SF 30 CONTINUATION PAGE

1. CONTRACT ID CODE PAGE OF PAGES

J 1 2

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

16C. DATE SIGNED

BY 19-Mar-2024

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street , County, State and Zip Code) X W912DQ24R4007

X 9B. DATED (SEE ITEM 11)

19-Jan-2024

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

Offer 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 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

19-Mar-2024

CODE

USACE, KANSAS CITY CT

FEDERAL BLDG CT-M 601 E 12TH STREET

KANSAS CITY MO 64106-2896

W912DQ 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W912DQ24R4007

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE (SF 30)

The following have been added by full text:

SUMMARY OF CHANGES

The SOLICITATION is amended as follows:

NOTE: Deleted text is shown in RED with strikethrough. Added text is shown in GREEN with underline.

1. SPECIFICATIONS.

a. 10 51 13 METAL LOCKERS. This section is revised. A copy of the revised specification is attached.

b. 10 81 13, Bird Control Devices, is added. A copy of the specification is attached.

c. 23 09 23.02 – BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS is added. A copy of the specification is attached.

2. Drawings. Drawing S-514 is revised. A copy of the revised drawing is attached.

3. The time and date for submission of proposals remains the same as March 25, 2024, 11:00 AM local time.

4. Offerors are required to acknowledge receipt of this amendment. Failure to acknowledge receipt of all amendments may cause rejection of offeror’s proposal.

5. All other terms and conditions remain unchanged and in full force.

(End of Summary of Changes)

Attack Aviation Battalion Complex W912DQ24-R-4007 Fort Riley, Kansas

SECTION TABLE OF CONTENTS

DIVISION 10 - SPECIALTIES

SECTION 10 51 13

METAL LOCKERS

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 DELIVERY, HANDLING, AND STORAGE

1.4 FIELD MEASUREMENTS

1.5 QUALITY ASSURANCE

1.5.1 Color Chips

PART 2 PRODUCTS

2.1 TYPES

2.1.1 Single-tier Flight Lockers

2.1.2 Double-Tier Flight Locker

2.1.3 Double-Tier Metal Locker

2.1.4 Double-Tier HDPE Locker

2.1.5 ALSE Lockers

2.2 MATERIAL

2.2.1 Steel Sheet

2.2.2 Wire Mesh

2.2.3 High Density Polyethylene (HDPE)

2.2.4 Finish

2.2.4.1 Color

2.3 COMPONENTS

2.3.1 Built-In Locks

2.3.2 Coat Hooks

2.3.3 Hanger Rods

2.3.4 Door Handles

2.3.5 Doors

2.3.5.1 Hinges

2.3.5.2 Latching Mechanisms

2.3.6 Latch Strikes

2.3.7 Silencers

2.3.8 Back and Side Panels, Tops, and Bottoms

2.3.9 Shelves

2.3.10 Base Panels

2.3.11 Number Plates

2.3.12 Label Holders

2.3.13 Fastening Devices

PART 3 EXECUTION

3.1 ASSEMBLY AND INSTALLATION

3.2 NUMBERING SYSTEM

3.3 FIELD QUALITY CONTROL

3.3.1 Testing

10 51 13 - 1

3.3.2 Repairing

3.3.3 Cleaning

-- End of Section Table of Contents --

10 51 13 - 2

SECTION 10 51 13

METAL LOCKERS

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 within the text by the basic designation only.

ASTM INTERNATIONAL (ASTM)

ASTM A1008/A1008M (2021a) Standard Specification for Steel, Sheet, Cold-Rolled, Carbon, Structural, High-Strength Low-Alloy, High-Strength Low-Alloy with Improved Formability, Solution Hardened, and Bake Hardenable

U.S. GENERAL SERVICES ADMINISTRATION (GSA)

FS AA-L-00486 (Rev J) Lockers, Clothing, Steel

1.2 SUBMITTALS

Government approval is required for submittals with a "G" designation;

submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submittals with an "S" are for inclusion in the Sustainability eNotebook, in conformance to Section 01 33 29 SUSTAINABILITY REPORTING. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-02 Shop Drawings

Types ; G, DO

Location ; G, DO

Installation

SD-03 Product Data

Material ; G, DO

Locking Devices ; G, RO

Handles ; G, RO

Finish ; G, DO

Locker components ; G, DO

Assembly instructions

10 51 13 - 3

SD-04 Samples

Color chips ; G, DO

1.3 DELIVERY, HANDLING, AND STORAGE

Deliver lockers and associated materials in their original packages, containers, or bundles bearing the manufacturer's name and the name of the material. Protect from weather, soil, and damage during delivery, storage, and construction.

1.4 FIELD MEASUREMENTS

To ensure proper fits, make field measurements prior to the preparation of drawings and fabrication. Verify correct location

1.5 QUALITY ASSURANCE

1.5.1 Color Chips

Provide a minimum of three color chips, not less than 3 inches square, of each color .

Government may request performance-characteristic tests on assembled lockers. Tests and results must conform to FS AA-L-00486 . Lockers not conforming will be rejected.

PART 2 PRODUCTS

2.1 TYPES

Locker must have the following type and size in the location and quantities indicated. Locker finish colors will be as scheduled.

2.1.1 Single-tier Flight Lockers

Single-tier lockers must be as follows:

Type LK1: Single-tier Metal Flight locker 18 inches wide, 24 inches deep, and 72 inches high , attached to 6-inch /high closed base;

Finish: Gray.

2.1.2 Double-Tier Flight Locker

Double-tier lockers must be as follows:

Type LK2: Double-tier Metal Flight locker 18 inches wide, 24 inches deep, and 72 inches high, attached to 6-inch high closed base; Finish:

Gray.

2.1.3 Double-Tier Metal Locker r

Double-tier lockers must be as follows:

Type LK5: Double-tier Metal locker 18 inches wide, 18 inches deep, and 72 inches high, attached to 6-inch high closed base; Finish: Gray.

10 51 13 - 4

2.1.4 Triple-Tier Double-Tier HDPE Locker

Triple-tier Double-tier lockers must be as follows:

Type LK 6: Triple Double -tier HDPE locker 18 inches wide, 18 inches deep, and 72 inches high. Finish: Grey. Sides, tops, bottoms, backs, and shelves shall be made from high impact, high density, polyethylene (HDPE) formed under pressure into solid plastic components 3/8 inch (9.5 mm) thick with homogenous natural color throughout. Provide end panels and filler panels of plastic material in color of locker unless noted otherwise as an accent color.

2.1.5 ALSE Lockers

ALSE lockers must be as follows:

Type LK 43: ALSE locker 30 inches wide, 30 inches deep, and 80 inches high . ALSE lockers shall be of metal wire mesh construction ALSE lockers shall have pass-through capabilities . ; Finish: Gray. Lockable, vented storage.

2.2 MATERIAL

2.2.1 Steel Sheet

LK1, LK2: ASTM A1008/A1008M , commercial quality, minimized spangle material. Prepare material surfaces for baked enamel finishing in accordance with FS AA-L-00486 . Fabricate locker bodies from not less than 0.0239-inch thick steel sheet.

2.2.2 Wire Mesh

LK3: Assembly shall be constructed of 12 gauge 1 inch by 1 inch welded wire mesh welded into a 14 gauge 1.25 inch by 1.25 inch angle frame for a unitized construction. Prepare material surfaces for baked enamel finishing in accordance with FS AA-L-00486 .

2.2.3 High Density Polyethylene (HDPE)

LK64: Lockers shall be constructed from High Density Polyethylene (HDPE) resins. Material shall be fabricated from polymer resins compounded under high pressure, forming a single component which is waterproof, nonabsorbent and has a self-lubricating surface that resists marks from pens, pencils, markers and other writing instruments.

Plastic components shall resist deterioration and discoloration when subjected to any of the following: acetic acid 80%, acetone, ammonia 12%, ammonium phosphate, bleach 12%, borax, brine, caustic soda, chlorine water, citric acid, copper chloride, core oils, hydrochloric acid 40%, hydrogen peroxide 30%, isopropyl alcohol, lactic acid 25%, lime sulfur, nicotine, potassium bromide; soaps, sodium bicarbonate, trisodium phosphate, urea, urine and vinegar. (Testing in accordance with corrosion testing procedure established by the United States Plastic Corporation.)

HDPE components shall have a smooth "orange peel" finish. Locker doors and door frames shall be the same color.

10 51 13 - 5

2.2.4 Chromium Coating

Nickel and chromium electrodeposited on the specified base metal. Conform to ASTM B456, SC-3, as applicable to the base metal.

2.2.4 Finish

High grade enamel, color as indicated.

2.2.4.1 Color

As selected on interior material finish legend .

2.3 COMPONENTS

2.3.1 Built-In Locks

FS AA-L-00486 . Provide locking devices as a padlock eye in the door latching mechanism.

2.3.2 Coat Hooks

Provide coat hooks in LK1, LK2, and LK6; FS AA-L-00486 , zinc plated.

2.3.3 Hanger Rods

Provide hangar rods in LK1, LK2, and LK6; FS AA-L-00486 .

2.3.4 Door Handles

Metal Lockers: FS AA-L-00486 . Provide zinc alloy or steel handles with a chromium coating.

HDPE Lockers: Provide HDPE integral handle/latch. Latch shall be spring-loaded and securely fastened to the entire length of the door providing a quiet positive latching function

2.3.5 Doors

Metal Lockers: FS AA-L-00486 , not less than 0.0598 inch thick steel sheet.

HDPE Lockers: Made of high impact HDPE with homogeneous color throughout.

2.3.5.1 Hinges

In addition to the requirements of FS AA-L-00486 , provide 5-knuckle hinges, minimum 2 inches high. Fabricate knuckle hinges from not less than

0.0787 inch thick steel sheet. Weld or bolt hinges to the door frame.

Weld, bolt, or rivet hinges to the door.

2.3.5.2 Latching Mechanisms

FS AA-L-00486 .

2.3.6 Latch Strikes

FS AA-L-00486 . Fabricate from not less than 0.0787 inch thick steel sheet, except latch strike may be continuous from top to bottom and fabricated as part of the door framing.

10 51 13 - 6

2.3.7 Silencers

FS AA-L-00486 .

2.3.8 Back and Side Panels, Tops, and Bottoms

Metal Lockers: FS AA-L-00486 , not less than 0.0474 inch thick steel sheet.

HDPE Lockers: Made of high impact HDPE with homogeneous color throughout.

2.3.9 Shelves

Metal Lockers: FS AA-L-00486 . Fabricate from not less than 0.0598 inch thick steel sheet.

2.3.10 Base Panels

Metal Lockers: FS AA-L-00486 .

2.3.11 Number Plates

Metal Lockers: FS AA-L-00486 . Aluminum. Provide consecutive numbers.

2.3.12 Label Holders

Metal Lockers: FS AA-L-00486 .

2.3.13 Fastening Devices

Metal Lockers: Provide bolts, nuts, and rivets as specified in

FS AA-L-00486 .

PART 3 EXECUTION

3.1 ASSEMBLY AND INSTALLATION

Assemble lockers according to the locker manufacturer's instructions.

Align lockers horizontally and vertically. Secure lockers to wall and base with screws as indicated. Bolt adjacent lockers together. Adjust doors to operate freely without sticking or binding and to ensure they close tightly.

3.2 NUMBERING SYSTEM

Install number plates on lockers consecutively with odd numbers on top and even numbers on bottom.

3.3 FIELD QUALITY CONTROL

3.3.1 Testing

Government may request performance-characteristic tests on assembled lockers in accordance with FS AA-L-00486 . Lockers not conforming will be rejected.

3.3.2 Repairing

Remove and replace damaged and unacceptable portions of completed work

10 51 13 - 7 with new.

3.3.3 Cleaning

Clean surfaces of the work, and adjacent surfaces soiled as a result of the work, in an approved manner. Remove equipment, surplus materials, and rubbish from the site.

-- End of Section --

10 51 13 - 8

SECTION TABLE OF CONTENTS

DIVISION 10 - SPECIALTIES

SECTION 10 81 13

BIRD CONTROL DEVICES

PART 1 GENERAL

1.1 SUMMARY

1.2 SUSTAINABILITY REQUIREMENTS

1.3 SUBMITTALS

1.4 QUALITY ASSURANCE

1.5 DELIVERY, STORAGE, AND HANDLING

1.6 WARRANTY

PART 2 PRODUCTS

2.1 NETTING MATERIAL

2.2 ASSESSORIES

PART 3 EXECUTION

3.1 EXAMINATION

3.2 INSTALLATION

3.2.1 WASTE MANAGEMENT

-- End of Section Table of Contents --

10 81 13 - 1

SECTION 10 81 13

BIRD CONTROL DEVICES

PART 1 GENERAL

1.1 SUMMARY

Provide bird netting attached to the bottom chord of the main spanning trusses of the Apache helicopter maintenance hangar bays, structural members spaning the vertical surfaces of the perimeter wall in this project. Refer to the Bird netting plans, elevations and sections for this project. Netting shall be installed continuously across the hangar bays, with no holes, gaps, or openings to allow the perching, roosting or nesting of birds in the hangar truss space. Provide zippers in the bird netting for mechanical equipment to provide access to the mechanical and electrical equipment above the netting.Provide zipper drawings for approval prior to installation with proposed zipper locations in reference to the mechanical and electrical equipment above the netting. The openings for the foam generators shall fit tightly around the foam generator dispersion outlets and any other mechanical, plumbing or electrical penetrations through the netting.

1.2 SUSTAINABILITY REQUIREMENTS

Materials in this technical specification may contribute towards contract compliance with sustainability requirements. See Section 01 33 29 LEED DOCUMENTATION for project requirements.

1.3 SUBMITTALS

Government approval is required for submittals with a "G" designation;

submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. The following shall be submitted in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-02 Shop Drawings

Zippers; G, DO

SD-03 Product Data

Netting Material; G, DO

Assessories

Written Installation Instructions; G, DO

1.4 QUALITY ASSURANCE

The installer shall be experienced in proper bird net installation procedures. The installer shall coordinate the net installation with but not limited to; radiant heaters, light fixtures, foam generators and bridge cranes.

10 81 13 - 2

1.5 DELIVERY, STORAGE, AND HANDLING

Deliver materials in original packages, containers or bundles bearing the brand name and identification of the manufacturer. Provide and maintain dry, off-ground weatherproof storage. Do not stack or place other packaging or objects on bird netting system packaging.

1.6 WARRANTY

Provide 60 month warranty period.

PART 2 PRODUCTS

2.1 NETTING MATERIAL

Provide bird netting attached to the bottom chord of the main spanning trusses of the Apache helicopter maintenance hangar bays in this project.

Netting shall be installed continuously across the hangar bays, with no holes, gaps, or openings to allow the perching, roosting or nesting of birds in the hangar truss space. Provide black, UV resistant and flame resistant multi-strand polypropylene, and having the following physical properties.

A. U.V stabilized knotted polyethylene net. Flame resistant (270 degree melting point).

B. Mesh Size: 3/4 inch squares C. Breaking Strength: ISO 1806 protocal mesh tested in excess of 40 lbs. Proof of Test Certification required.

D. Chemical Properties: High resistance to acid and alkalies. Rot, water, and mildew resistance.

E. Electrical Properties: Non-conductive F. Flame Testing: Tested per UL 94-92 with preparations in ASTM D4706-16 and CRT. Conditioning (pre-annealing) in accordance with ASTM D618-13.

2.2 ASSESSORIES

ACCESSORIES

A. Polyethylene Hardware: manufacturer's proprietary products, UV stabilized black polypropylene, including clips, twist locks, ties, overhead straps and cords.

B. Black heavy duty marine grade, UV resistant black zippers fastened to netting to provide access to mechanical and electrical equipment as noted on drawings.

C. Tensioned Support Cable Hardware: All necessary hardware to connect and support system from building structure at locations indicated, including but not limited to the following connection hardware:

1. Net Cable: Aircraft grade 302/304 stainless steel, 7 x 7 stranded strand, 1/16 inch diameter cable, 480 lbs breaking strength.

2. Turnbuckles: Stainless steel, hook and eye turnbuckles.

3. Ferrules: Zinc plated copper, two ferrules per connection.

4. Wire Rope Clamps: Galvanized or stainless steel, two clamps per connection.

5. Cable Thimble: Stainless steel.

10 81 13 - 3

D. Cable Anchoring Hardware: extreme duty stainless steel eyebolt or zinc plated machine screw anchor, sized to suit application.

PART 3 EXECUTION

3.1 EXAMINATION

Ensure surfaces that will receive netting hardware and all areas that will be behind or inside netting installation are undamaged and suitable to receive netting installation.

Verify dimensions of areas to be enclosed.

Ensure surfaces are clean, dry and free of obstructions before bird control is installed.

3.2 INSTALLATION

Install bird netting hardware in accordance with manufacturer's written installation instructions.

Attach bird netting to installed hardware; install access or additional hardware as specified.

Join multiple pieces together with manufacturer recommended seam fastening hardware.

Secure netting at openings as recommended by netting manufacturer.

Install netting to avoid contact with machinery, cranes, extreme heat, and other obstruction conditions.

Install taut, free of wrinkles, gaps and openings.

3.2.1 WASTE MANAGEMENT

Separate waste in accordance with the Waste Management Plan. Store protected in a well-ventilated, fire-safe area at moderate temperature.

Collect and place scrap/waste debris in containers. Promptly dispose of scrap/waste debris. Do not allow scrap/waste debris to accumulate on-site;

transport scrap/waste debris from government property and legally dispose of them.

10 81 13 - 4

SECTION 23 09 23.02

BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS

02/19, CHG 1: 02/20

PART 1 GENERAL

1.1 SUMMARY

Provide a complete Direct Digital Control (DDC) system, except for the front end which is specified in Section 25 10 10 UTILITY MONITORING AND

CONTROL (UMCS) FRONT END AND INTEGRATION, suitable for the control of the heating, ventilating and air conditioning (HVAC) and other building-level systems as specified and shown and in accordance with Section 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC.

1.1.1 System Requirements

Provide a system meeting the requirements of both Section 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC and this Section and with the following characteristics:

a.

Except for Gateways, the control system must be an open implementation of BACnet technology using ASHRAE 135 as the communications protocol.

The system must use standard ASHRAE 135 Objects and Properties. The system must use standard ASHRAE 135 Services exclusively for communication over the network. Gateways to packaged units must communicate with other DDC hardware using ASHRAE 135 exclusively and may communicate with packaged equipment using other protocols. The control system must be installed such that any two devices on the

Internetwork can communicate using standard ASHRAE 135 Services.

b. Install and configure control hardware to provide ASHRAE 135 Objects and Properties as indicated and as needed to meet the requirements of this specification.

1.1.2 Verification of Specification Requirements

Review all specifications related to the control system installation and advise the Contracting Officer of any discrepancies before performing any work. If Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC or any other Section referenced in this specification is not included in the project specifications advise the Contracting Officer and either obtain the missing Section or obtain Contracting Officer approval before performing any work.

1.2 REFERENCES

The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.

AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING

ENGINEERS (ASHRAE)

ASHRAE 135 (2020; Interpretation 1-8 2021; Errata 1-2

2021; Addenda CD 2021; Addenda BV-CE 2022;

Interpretation 9-12 2022; Interpretation

13-17 2023; Addenda BV-CF 2023; Errata 3

2023) BACnet—A Data Communication Protocol for Building Automation and Control

Networks

BACNET INTERNATIONAL (BTL)

BTL Guide (v.49; 2017) BACnet Testing Laboratory

Implementation Guidelines

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

IEEE 802.3 (2022) Ethernet

TELECOMMUNICATIONS INDUSTRY ASSOCIATION (TIA)

TIA-485 (1998a; R 2012) Electrical Characteristics of Generators and Receivers for Use in

Balanced Digital Multipoint Systems

TRIDIUM, INC (TRIDIUM)

Niagara Framework (2012) NiagaraAX User's Guide

Tridium Open NiCS (2005) Understanding the NiagaraAX

Compatibility Statement (NiCS)

U.S. FEDERAL COMMUNICATIONS COMMISSION (FCC)

FCC Part 15 Radio Frequency Devices (47 CFR 15)

UNDERWRITERS LABORATORIES (UL)

UL 916 (2015; Reprint Oct 2021) UL Standard for

Safety Energy Management Equipment

1.3 DEFINITIONS

For definitions related to this section, see Section 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC.

1.4 SUBMITTALS

Submittal requirements related to this Section are specified in Section

23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC.

PART 2 PRODUCTS

All products used to meet this specification must meet the indicated requirements, but not all products specified here will be required by every project. All products must meet the requirements both Section 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC and this Section.

2.1 NETWORK HARDWARE

2.1.1 BACnet Router

All BACnet Routers must be BACnet/IP Routers and must perform layer 3 routing of ASHRAE 135 packets over an IP network in accordance with

ASHRAE 135 Annex J and Clause 6. The router must provide the appropriate connection to the IP network and connections to one or more ASHRAE 135

MS/TP networks. Devices used as BACnet Routers must meet the requirements for DDC Hardware, and must support the NM-RC-B BIBB.

2.1.2 BACnet Gateways

In addition to the requirements for DDC Hardware, the BACnet Gateway must meet the following requirements:

a. It must perform bi-directional protocol translation from one non-

ASHRAE 135 protocol to ASHRAE 135. BACnet Gateways must incorporate a network connection to an ASHRAE 135 network (either BACnet over IP in accordance with Annex J or MS/TP) and a separate connection appropriate for the non-ASHRAE 135 protocol and media.

b. It must retain its configuration after a power loss of an indefinite time, and must automatically return to their pre-power loss state once power is restored.

c. It must allow bi-directional mapping of data between the non-ASHRAE 135 protocol and Standard Objects as defined in ASHRAE 135. It must support the DS-RP-B BIBB for Objects requiring read access and the

DS-WP-B BIBB for Objects requiring write access.

d. It must support the DS-COV-B BIBB.

Although Gateways must meet DDC Hardware requirements they are not DDC

Hardware and must not be used when DDC Hardware is required.

2.1.3 Ethernet Switch

Ethernet Switches must be managed switches and must autoconfigure between

10,100 and 1000 megabits per second (MBPS).

2.2 CONTROL NETWORK WIRING

a. BACnet MS/TP communications wiring must be in accordance with ASHRAE 135.

The wiring must use shielded, three wire (twisted-pair with reference) cable with characteristic impedance between 100 and 120 ohms.

Distributed capacitance between conductors must be less than 30 pF per foot.

b. Building Control Network Backbone IP Network must use Ethernet media.

Ethernet cables must be CAT-5e at a minimum and meet all requirements of IEEE 802.3 .

2.3 DIRECT DIGITAL CONTROL (DDC) HARDWARE

2.3.1 General Requirements

All DDC Hardware must meet the following requirements:

a. It must be locally powered and must incorporate a light to indicate the device is receiving power.

b. It must conform to the BTL Guide

c. It must be BACnet Testing Laboratory (BTL) Listed.

d. The Manufacturer's Product Data submittal for each piece of DDC

Hardware must include the Protocol Implementation Conformance Statement

(PICS) for that hardware as specified in Section 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC.

e. It must communicate and be interoperable in accordance with ASHRAE 135 and have connections for BACnet IP or MS/TP control network wiring.

f. Other than devices controlling terminal units or functioning solely as a BACnet Router, it must support DS-COV-B, DS-RPM-A and DS-RPM-B BIBBs.

g. Devices supporting the DS-RP-A BIBB must also support the DS-COV-A BIBB.

h. Application programs, configuration settings and communication information must be stored in a manner such that they persist through loss of power:

(1) Application programs must persist regardless of the length of time power is lost.

(2) Configured settings must persist for any loss of power less than

2,500 hours.

(3) Communication information, including but not limited to COV subscriptions, event reporting destinations, Notification Class

Object settings, and internal communication settings, must persist for any loss of power less than 2,500 hours.

i. Internal Clocks:

(1) Clocks in DDC Hardware incorporating a Clock must continue to function for 120 hours upon loss of power to the DDC Hardware.

(2) DDC Hardware incorporating a Clock must support the DM-TS-B or

DM-UTC-B BIBB.

j. It must have all functionality indicated and required to support the application (Sequence of Operation or portion thereof) in which it is used, including but not limited to providing Objects as specified and as indicated on the Points Schedule.

k. In addition to these general requirements and the DDC Hardware

Input-Output (I/O) Function requirements, all DDC Hardware must also meet any additional requirements for the application in which it is used (e.g. scheduling, alarming, trending, etc.).

l. It must meet FCC Part 15 requirements and have UL 916 or equivalent safety listing.

m. Device must support Commandable Objects to support Override requirements as detailed in PART 3 EXECUTION

n. User interfaces which allow for modification of Properties or settings must be password-protected.

o. Devices communicating BACnet MS/TP must meet the following requirements:

(1) Must have a configurable Max_Master Property.

(2) DDC Hardware other than hardware controlling a single terminal unit must have a configurable Max_Info_Frames Property.

(3) Must respond to any valid request within 50 msec with either the appropriate response or with a response of "Reply Postponed".

(4) Must use twisted pair with reference and shield (3-wire media) wiring, or twisted pair with shield (2-wire media) wiring and use half-wave rectification.

p. Devices communicating BACnet/IP must use UDP Port 0xBAC0. Devices with configurable UDP Ports must default to 0xBAC0.

q. All Device IDs, Network Numbers, and BACnet MAC addresses of devices must be fully configurable without limitation, except MS/TP MAC addresses may be limited by ASHRAE 135 requirements.

r. DDC Hardware controlling a single terminal unit must have:

(1) Objects (including the Device Object) with an Object Name Property of at least 8 characters in length.

(2) A configurable Device Object Name.

(3) A configurable Device Object Description Property at least 16 characters in length.

s. Except for Objects in DDC Hardware controlling a single terminal unit, all Objects (including Device Objects) must:

(1) Have a configurable Object Name Property of at least 12 characters in length.

(2) Have a configurable Object Description Property of at least 24 characters in length.

t. For programmable DDC Hardware, provide and license to the project site all programming software required to program the Hardware in accordance with Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC.

u. For programmable DDC Hardware, provide copies of the installed application programs (all software that is not common to every controller of the same manufacturer and model) as source code compatible with the supplied programming software in accordance with

Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC. The submitted application program must be the complete application necessary for controller to function as installed and be sufficient to allow replacement of the installed controller with another controller of the same type.

2.3.2 Hardware Input-Output (I/O) Functions

DDC Hardware incorporating hardware input-output (I/O) functions must meet the following requirements:

2.3.2.1 Analog Inputs

DC Hardware analog inputs (AIs) must be implemented using ASHRAE 135 Analog

Input Objects and perform analog to digital (A-to-D) conversion with a minimum resolution of 8 bits plus sign or better as needed to meet the accuracy requirements specified in Section 23 09 00. Signal conditioning including transient rejection must be provided for each analog input.

Analog inputs must be capable of being individually calibrated for zero and span. Calibration via software scaling performed as part of point configuration is acceptable. The AI must incorporate common mode noise rejection of at least 50 dB from 0 to 100 Hz for differential inputs, and normal mode noise rejection of at least 20 dB at 60 Hz from a source impedance of 10,000 ohms.

2.3.2.2 Analog Outputs

DDC Hardware analog outputs (AOs) must be implemented using ASHRAE 135

Analog Output Objects and perform digital to analog (D-to-A) conversion with a minimum resolution of 8 bits plus sign, and output a signal with a range of 4-20 mAdc or 0-10 Vdc. Analog outputs must be capable of being individually calibrated for zero and span. Calibration via software scaling performed as part of point configuration is acceptable. DDC

Hardware with Hand-Off-Auto (H-O-A) switches for analog outputs must provide for overriding the output through the range of 0 percent to 100 percent

2.3.2.3 Binary Inputs

DDC Hardware binary inputs (BIs) must be implemented using ASHRAE 135

Binary Input Objects and accept contact closures and must ignore transients of less than 5 milli-second duration. Protection against a transient 50VAC must be provided.

2.3.2.4 Binary Outputs

DDC Hardware binary outputs (BOs) must be implemented using ASHRAE 135

Binary Output Objects and provide relay contact closures or triac outputs for momentary and maintained operation of output devices. DDC Hardware with

H-O-A switches for binary outputs must provide for overriding the output open or closed.

2.3.2.4.1 Relay Contact Closures

Closures must have a minimum duration of 0.1 second. Relays must provide at least 180V of isolation. Electromagnetic interference suppression must be provided on all output lines to limit transients to 50 Vac. Minimum contact rating must be 0.5 amperes at 24 Vac.

2.3.2.4.2 Triac Outputs

Triac outputs must provide at least 180 V of isolation. Minimum contact rating must be 0.5 amperes at 24 Vac.

2.3.2.5 Pulse Accumulator

DDC Hardware pulse accumulators must be implemented using either an

ASHRAE 135 Accumulator Object or an ASHRAE 135 Analog Value Object where the Present_Value is the totalized pulse count. Pulse accumulators must accept contact closures, ignore transients less than 5 msec duration, protect against transients of 50 VAC, and accept rates of at least 20 pulses per second.

2.3.2.6 ASHRAE 135 Objects for Hardware Inputs and Outputs

The requirements for use of ASHRAE 135 objects for hardware input and outputs includes devices where the hardware sensor or actuator is integral to the controller (e.g. a VAV box with integral damper actuator, a smart sensor, a VFD, etc.)

2.3.3 Local Display Panel (LDP)

The Local Display Panels (LDPs) must be DDC Hardware with a display and navigation buttons or a touch screen display, and must provide display and adjustment of ASHRAE 135 Properties as indicated on the Points Schedule and as specified. LDPs must be either BTL Listed as a B-OD, B-OWS, B-AWS, or be an integral part of another piece of DDC Hardware listed as a B-BC.

For LDPs listed as B-OWS or B-AWS, the hardware must be BTL listed and the product must come factory installed with all applications necessary for the device to function as an LDP.

The adjustment of values using display and navigation buttons must be password protected.

2.3.4 Expansion Modules and Tethered Hardware

A single piece of DDC Hardware may consist of a base unit and also:

a. An unlimited number of hardware expansion modules, where the individual hardware expansion modules are designed to directly connect, both mechanically and electrically, to the base unit hardware. The expansion modules must be commercially available as an optional add-on to the base unit.

b. A single piece of hardware connected (tethered) to a base unit by a single cable where the cable carries a proprietary protocol between the base unit and tethered hardware. The tethered hardware must not contain control logic and be commercially available as an optional add-on to the base unit as a single package.

Note that this restriction on tethered hardware does not apply to sensors or actuators using standard binary or analog signals (not a communications protocol); sensors or actuators using standard binary or analog signals are not considered part of the DDC Hardware.

Hardware capable of being installed stand-alone, or without a separate base unit, is DDC Hardware and must not be used as expansion modules or tethered hardware.

2.3.5 Supervisory Control Requirements

2.3.5.1 Scheduling Hardware

DDC Hardware used for scheduling must meet the following requirements:

a. It must be BTL Listed as a B-BC and support the SCHED-E-B BIBB.

b. It is preferred, but not required, that devices support the DM-OCD-B

BIBB on all Calendar and Schedule Objects, such that a front end BTL listed as a B-AWS may create or delete Calendar and Schedule Objects.

It is also preferred but not required that devices supporting the

DM-OCD-B BIBB accept any valid value for properties of Calendar and

Schedule Objects. Note that there are additional requirements in the

EXECUTION Part of this Section for Devices which do not support the

DM-OCD-B BIBB as specified.

c. The Date_List property of all Calendar Objects must be writable.

d. The Present_Value Property of Schedule must support the following values: 1, 2, 3, 4.

2.3.5.2 Alarm Generation Hardware

DDC Hardware used for alarm generation must meet the following requirements:

a. Device must support the AE-N-I-B BIBB

b. The Recipient_List Property must be Writable for all Notification Class

Objects used for alarm generation.

c. For all Objects implementing Intrinsic Alarming, the following

Properties must be Writable:

(1) Time_Delay

(2) High_Limit

(3) Low_Limit

(4) Deadband

(5) Event_Enable

(6) If the issue date of this project specification is after 1 January

2016, Time_Delay_Normal must be writable.

d. For Event Enrollment Objects used for alarm generation, the following

Properties must be Writable:

(1) Event_Parameters

(2) Event_Enable

(3) If the issue date of this project specification is after 1 January

2016, Time_Delay_Normal must be writable.

e. It is preferred, but not required, that devices support the DM-OCD-B

BIBB on all Notification Class Objects and Event Enrollment Objects, such that a front end BTL listed as a B-AWS may create or delete

Notification Class Objects and Event Enrollment Objects. It is also preferred, but not required that devices supporting the DM-OCD-B BIBB accept any valid value as an initial value for properties of

Notification Class Objects and Event Enrollment Objects. Note that there are additional requirements in the EXECUTION Part of this Section for devices which do not support the DM-OCD-B BIBB as specified.

f. Devices provided to meet the the requirements indicated under "Support for Future Alarm Generation" in the EXECUTION part of this specification must support the AE-N-E-B BIBB.

2.3.5.3 Trending Hardware

DDC Hardware used for collecting trend data must meet the following requirements:

a. Device must support Trend Log or Trend Log Multiple Objects.

b. Device must support the T-VMT-I-B BIBB.

c. Devices provided to meet the EXECUTION requirement for support of

Future Trending must support the T-VMT-E-B BIBB.

d. The following properties of all Trend Log or Trend Log Multiple Objects must be present and Writable:

Start_Time

Stop_Time

Log_DeviceObjectProperty

Log Interval Log interval must support an interval of at least 60 minutes duration.

e. Trend Log Objects must support using Intrinsic Reporting to send a

BUFFER_FULL event.

f. The device must have a Notification Class Object for the BUFFER_FULL event. The Recipient_List Property must be Writable.

g. Devices must support values of at least 1,000 for Buffer_Size

Properties.

h. It is preferred, but not required, that devices support the DM-OCD-B

BIBB on all Trend Log Objects, such that a front end BTL listed as a

A-AWS may create or delete Trend Log Objects. It is also preferred, but not required that devices supporting the DM-OCD-B BIBB accept any valid value as an initial value for properties of Trend Log Objects. Note that there are additional EXECUTION requirements for devices which do not support the DM-OCD-B BIBB as specified.

PART 3 EXECUTION

3.1 CONTROL SYSTEM INSTALLATION3.1.1 Building Control Network (BCN)

Install the Building Control Network (BCN) as a single BACnet Internetwork consisting of a single IP network as the BCN Backbone and zero or more

BACnet MS/TP networks. Note that in some cases there may only be a single device on the BCN Backbone.

Except as permitted for the non-BACnet side of Gateways, use exclusively

ASHRAE 135 networks.

3.1.1.1 Building Control Network IP Backbone

Install IP Network Cabling in conduit. Install Ethernet Switches in lockable enclosures. Install the Building Control Network (BCN) IP

Backbone such that it is available at the Facility Point of Connection

(FPOC) location as indicated. When the FPOC location is a room number, provide sufficient additional media to ensure that the Building Control

Network (BCN) IP Backbone can be extended to any location in the room.

Use UDP port 0xBAC0 for all BACnet traffic on the IP network.

3.1.1.2 BACnet MS/TP Networks

When using MS/TP, provide MS/TP networks in accordance with ASHRAE 135 and in accordance with the ASHRAE 135 figure "Mixed Devices on 3-Conductor

Cable with Shield" (Figure 9-1.4 in the 2012 version of ASHRAE 135).

Ground the shield at the BACnet Router and at no other point. Ground the reference wire at the BACnet Router through a 100 ohm resistor and do not ground it at any other point. In addition:

a. Provide each segment in a doubly terminated bus topology in accordance with TIA-485.

b. Provide each segment with 2 sets of network bias resistors in accordance with ASHRAE 135, with one set of resistors at each end of the MS/TP network.

c. Use 3 wire (twisted pair and reference) with shield media for all MS/TP media installed inside. Use fiber optic isolation in accordance with

ASHRAE 135 for all MS/TP media installed outside buildings, or between multiple buildings.

d. For 18 AWG cable, use segments with a maximum length of 4000 ft. When using greater distances or different wire gauges comply with the electrical specifications of TIA-485.

e. For each controller that does not use the reference wire provide transient suppression at the network connection of the controller if the controller itself does not incorporate transient suppression.

f. Install no more than 32 devices on each MS/TP segment. Do not use MS/TP to MS/TP routers.

g. Connect each MS/TP network to the BCN backbone via a BACnet Router.

h. For BACnet Routers, configure the MS/TP MAC address to 0. Assign MAC

Addresses to other devices consecutively beginning at 1, with no gaps.

i. Configure the Max_Master Property of all devices to be 31.

3.1.1.3 Building Control Network (BCN) Installation

Provide a building control network meeting the following requirements:

a. Install all DDC Hardware connected to the Building Control Network.

b. Where multiple pieces of DDC Hardware are used to execute one sequence, install all DDC Hardware executing that sequence on a single MS/TP network dedicated to that sequence.

c. Traffic between BACnet networks must be exclusively via BACnet routers.

3.1.2 DDC Hardware

Install all DDC Hardware that connects to an IP network in lockable enclosure. Install other DDC Hardware that is not in suspended ceilings in lockable enclosures. For all DDC hardware with a user interface, coordinate with site to determine proper passwords and configure passwords into device.

a. Except for zone sensors (thermostats), install all Tethered Hardware within 6 feet of its base unit.

b. Install and configure all BTL-Listed devices in a manner consistent with their BTL Listing such that the device as provided still meets all requirements necessary for its BTL Listing.

c. Install and configure all BTL-Listed devices in a manner consistent with the BTL Device Implementation Guidelines such that the device as provided meets all those Guidelines.

3.1.2.1 Device Identifiers, Network Addresses, and IP addresses

a. Do not use any Device Identifier or Network Number already used by another BACnet system at the project site. Coordinate Device IDs and

Network Numbers with the Contracting Officer Representative (COR).

b. Coordinate device IP addresses with the Contracting Officer

Representative (COR).

3.1.2.2 Object Name Property and Object Description Property

Configure the Object_Names and Object_Descriptions properties of all

Objects (including Device Objects) as indicated on the Points Schedule

(Point Name and Point Description) and as specified. At a minimum:

a. Except for DDC Hardware controlling a single terminal unit, configure the Object_Name and Object_Description properties of all Objects

(including Device Objects) as indicated on the Points Schedule and as specified.

b. In DDC Hardware controlling a single terminal unit, configure the

Device Object_Name and Device Object_Description as indicated on the

Points Schedule and as specified.

When Points Schedule entries exceed the length limitations in the device, notify Contracting Officer Representative (COR) and provide recommended alternatives for approval. Do not implement alternative names without approval.

3.1.2.3 Hand-Off-Auto (H-O-A) Switches

Provide Hand-Off-Auto (H-O-A) switches for all DDC Hardware analog outputs and binary outputs used for control of systems other than terminal units, as specified and as indicated on the Points Schedule. Provide H-O-A switches that are integral to the controller hardware, an external device co-located with (in the same enclosure as) the controller, integral to the controlled equipment, or an external device co-located with (in the same enclosure as) the controlled equipment.

a. For H-O-A switches integral to DDC Hardware, meet the requirements specified in paragraph DIRECT DIGITAL CONTROL (DDC) HARDWARE.

b. For external H-O-A switches used for binary outputs, provide for overriding the output open or closed.

c. For eternal H-O-A switches used for analog outputs, provide for overriding through the range of 0 percent to 100 percent.

3.1.2.4 Local Display Panels

Provide LDPs to display and override values of ASHRAE 135 Object Properties as indicated on the Points Schedule. Install LDPs displaying points for anything other than a terminal unit in the same room as the equipment.

Install LDPs displaying points for only terminal units in a mechanical room central to the group of terminal units it serves. For LDPs using

WriteProperty to commandable objects to implement an override, write values with priority 9.

3.1.2.5 MS/TP Slave Devices

Configure all MS/TP devices as Master devices. Do not configure any devices to act as slave devices.

3.1.2.6 Change of Value (COV) and Read Property

a. To the greatest extent possible, configure all devices to support the

SubscribeCOV service (the DS-COV-B BIBB). At a minimum, all devices supporting the DS-RP-B BIBB, other than devices controlling only a single terminal unit, must be configured to support the DS-COV-B BIBB.

b. Whenever supported by the server side, configure client devices to use the DS-COV-A BIBB.

3.1.2.7 Engineering Units

Configure devices to use English (Inch-Pound) engineering units as follows:

a. Temperature in degrees F

b. Air or natural gas flows in cubic feet per minute (CFM)

c. Water in gallons per minute (GPM)

d. Steam flow in pounds per hour (pph)

e. Differential Air pressures in inches of water column (IWC)

f. Water, steam, and natural gas pressures in PSI

g. Enthalpy in BTU/lb

h. Heating and cooling energy in MBTU (1MBTU = 1,000,000 BTU))

i. Cooling load in tons (1 ton = 12,000 BTU/hour)

j. Heating load in MBTU/hour (1MBTU = 1,000,000 BTU)

k. Electrical Power: kilowatts (kW)

l. Electrical Energy: kilowatt-hours (kWh)

3.1.2.8 Occupancy Modes

Use the following correspondence between value and occupancy mode whenever an occupancy state or value is required:

a. OCCUPIED mode: a value of one

b. UNOCCUPIED mode: a value of two

c. WARM-UP/COOL-DOWN (PRE-OCCUPANCY) mode: a value of three

Note that elsewhere in this Section the Schedule Object is required to also support a value of four, which is reserved for future use. Also note that the behavior of a system in each of these occupancy modes is indicated in the sequence of operation for the system.

3.1.2.9 Use of BACnet Objects

Use only standard non-proprietary ASHRAE 135 Objects and services to accomplish the project scope of work as follows:

a. Use Analog Input or Analog Output Objects for all analog hardware I/O.

Do not use Analog Value Object for analog hardware I/O) .

b. Use Binary Input or Binary Output Objects for all binary hardware I/O.

Do not use Binary Value Objects for binary hardware I/O.

c. Use Analog Value Objects for analog setpoints.

d. Use Accumulator Objects or Analog Value Objects for pulse inputs.

e. For occupancy modes, use Multistate Value Objects and the correspondence between value and occupancy mode specified in paragraph

OCCUPANCY MODES.

f. Use Schedule Objects and Calendar Objects for all scheduling. Use

Trend Log Objects or Trend Log Multiple Objects for all trending and

Notification Class Objects for trend log upload. Use a combination of

Event Enrollment Objects,Intrinsic Alarming, and Notification Class

Objects for alarm generation.

g. For all other points shown on the Points Schedule as requiring an

ASHRAE 135 Object, use the Object type shown on the Points Schedule or, if no Object Type is shown, use a standard Object appropriate to the point.

3.1.2.10 Use of Standard BACnet Services

Except as noted in this paragraph, for all DDC Hardware use Standard BACnet

Services as defined in this specification (which excludes some ASHRAE 135 services) exclusively for application control functionality and communication.

DDC Hardware that cannot meet this requirement may use non-standard services provided they can provide identical functionality using Standard

BACnet Services when communicating with BACnet devices from a different vendor. When implementing non-standard services, document all non-standard services in the DDC Hardware Schedule as specified and as specified in

Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC.

3.1.2.11 Device Application Configuration

a. For every property, setting or value shown on the Points Schedule or otherwise indicated as Configurable, provide a value that is retained through loss of power and can be changed via one or more of:

(1) BACnet services (including proprietary services)

(2) Hardware settings on the device

b. For every property, setting or value shown on the Points Schedule or otherwise indicated as Operator Configurable, provide a value that is retained through loss of power and can be changed via one or more of:

(1) A Writable Property of a standard BACnet Object

(2) A Property of a standard BACnet Object that is Writable when

Out_Of_Service is TRUE and Out_Of_Service is Writable.

3.1.3 Scheduling, Alarming, Trending, and Overrides

3.1.3.1 Scheduling

Configure schedules in BACnet Scheduling Objects to schedule systems as indicated on the Points Schedule and as specified using the indicated correspondence between value and occupancy mode.