5-Attach I - McKinstry Controls Provider Performance Stand.pdf

Last Revision: 02/2025 1

MCKINSTRY CONTROLS CONTRACTOR PERFORMANCE STANDARDS

Revised February 2025

Relative to commissioning and project closeout, this document serves to clarify McKinstry’s performance expectations of the following points:

Table of Contents

1. Communication

2. Personnel and Support

3. Electrical Subcontractor

4. Quality Assurance

5. Submittals

6. Project Schedule

7. Installation

8. Functional Testing

9. System Usability (GUI)

10. Data Trending

11. Punch list / Deficiency Resolution

12. Owner Training

13. Completion Deliverables

14. Ownership of Proprietary Material

15. Warranty

The following defines and describes the minimum acceptable performance Controls Contractors are required to adhere to on all McKinstry projects. If an Owner does not have a point naming convention, the McKinstry Point Naming Convention shall be used. Please ask your McKinstry representative for the most up to date version of the Point Naming Convention.

1. Communication

a) McKinstry requires Controls Contractors to adhere to communication in accordance with the provisions of the Prime and Subcontract Agreements around questions, comments, clarifications, or concerns, during pre-construction, construction, closeout, commissioning and warranty. This includes but is not limited to:

i) Promptly returning phone calls and e-mails within 24 hours.

ii) Timely response to or delivery of RFIs, punch lists, and observation logs within one (1) week.

iii) Attend and participate in all coordination / start-up meetings.

iv) In buildings with existing controls systems, if the Controls Contractor finds an existing condition/deficiency, the Controls Contractor shall notify McKinstry immediately, no later than 24 hours after the discovery.funct

v) Response to commissioning deficiencies shall occur in the project specific software, such as Cx Alloy.

vi) Acknowledgment of communications shall be made by the Controls Contractor within one business day of initial notification and shall include a resolution and planned date of resolution.

Last Revision: 02/2025 2

b) Email is the preferred means of recordable communication. Unless otherwise directed, emails will carbon copy the appointed McKinstry Project Engineer, Project/Construction manager, and McKinstry’s commissioning lead(s).

c) Dissemination of project specific information to other trades without McKinstry’s consent shall not be allowed without the written consent of McKinstry’s Project/Construction Manager.

d) Any changes, decisions, etc. must be properly documented in accordance with the Prime and Subcontract Agreements. Verbal interpretations, clarifications, conversations, etc., are non- binding without proper documentation.

e) RFIs are to address individual requests only with a proposed solution. Multiple issues or incomplete RFIs will be rejected. Report any discrepancies, conflicts, inadequate conditions, or omissions related to project documentation to the McKinstry project team through an RFI. RFIs shall be written and submitted in the project specific software, such as Procore. RFIs shall include, but not be limited to, the following:

i) Referenced Drawing

ii) Referenced Specification Number/Section

iii) Contact Person

iv) Request and Proposed Solution

v) RFI answers are for clarification only and do not authorize additional work or change orders.

2. Personnel and Support

a) The Controls Contractor is responsible for providing adequate, qualified personnel for the purpose of providing a complete control installation within the constraints of the project schedule. Controls Contractor shall submit in writing their proposed project team and qualifications adhering to i) through vi) below to McKinstry for approval three (3) weeks prior to mobilizing on the job site.

i) The Controls Contractor shall have a minimum of five (5) years of demonstrated technical expertise with building automation system operation, maintenance, and service. The Controls Contractor must also provide documented proof of servicing installations of similar or greater size and complexity as well as provide documented proof of servicing the proposed devices for a minimum of one (1) year.

ii) The Controls Contractor Program Manager shall have a minimum of three (3) years of experience with DDC system installation and must have experience with the installation of the proposed devices on a minimum of two (2) projects of similar or greater size and complexity.

iii) The Controls Contractor Programmer(s) and Lead Installation Technician shall have a minimum of three (3) years of experience with DDC system installation and programming and must have experience with the installation and programming of the proposed devices for a minimum of two

(2) years.

iv) The Controls Contractor Project Manager and Programmer(s) must supply proof of successfully completing the most advanced training offered by the manufacturer of the proposed devices to proficiently install, program, and commission the proposed devices.

v) The Controls Contractor Lead Installation Technician must supply proof of successfully completing training offered by the manufacturer of the proposed devices to proficiently install the proposed devices.

vi) Integration Contractor Personnel Requirements:

(1) The Integration Contractor shall have a minimum of five (5) years of demonstrated technical expertise with building automation system integration. The Integration Contractor must also provide documented proof of servicing installations of similar or greater size and complexity as well as provide documented proof of servicing the proposed devices for a minimum of one (1) year.

(2) The Integration Contractor Program Manager shall have a minimum of three (3) years of experience with BMS integration and must have experience on a minimum of two (2) projects

Last Revision: 02/2025 3 utilizing the proposed devices for projects of similar or greater size and complexity.

(3) The Integration Contractor Programmer(s) shall have a minimum of three (3) years of experience with BMS integration, programming, and graphical user interface generation and must have a minimum of two (2) years’ experience providing integration services for the proposed devices.

(4) The Integration Contractor Project Manager and Programmer(s) must supply proof of successfully completing the most advanced training offered by the manufacturer of the proposed devices to proficiently integrate, program, and generate graphics for the proposed devices.

b) The Controls Contractor is expected to perform all work outlined in the scope of work as well as Pre-functional Testing and Functional Performance Testing. More details on the testing process are outlined in Section 8 – Functional Testing

c) Support is defined as providing personnel meeting McKinstry’s qualification requirements above in 2.a.i) through 2.a.vi) for the task at hand. For example, during functional performance testing, the support person provided by the Controls Contractor shall be a programming-capable engineer, familiar with the system being tested and shall be present alongside the test crew to make necessary changes needed to correct deficiencies found during the testing process.

d) In addition to the specific work to be performed by the Controls Contractor, the Controls Contractor shall anticipate supporting all peripheral functions, including but not limited to:

i) Equipment start-up

ii) Testing, adjusting and balancing (TAB) activities

iii) Owner training

iv) Warranty, hot/cold call support, etc.

e) McKinstry reserves the right to have the Controls Contractor remove and replace incompetent or ineffective personnel. The Owner reserves the right to make the final determination of the qualifications of any Contractor’s employee(s), as well as the right to have the Contractor’s employee(s) removed from the project at Owner’s sole discretion. The Owner and/or McKinstry will provide written notice to Contractor citing the circumstances for Contractor’s employee(s) and the Contractor will replace any removed employee with qualified staff meeting McKinstry’s requirements above within three (3) business days with no impact to project schedule.

f) Controls Contractor will supply McKinstry with any proprietary software, cables, dongles/security keys, etc.

at no cost to McKinstry for the duration of the commissioning effort.

g) If the Controls Contractor is unable to provide software, cables, etc. that can be loaded onto McKinstry-owned hardware, the Controls Contractor will either loan McKinstry pre-configured computers/interface tools or supply Controls Contractor support with the appropriate devices for the duration of the commissioning effort at no additional expense to McKinstry.

h) If the Controls Contractor is unable to supply experienced support personnel, Controls Contractor shall be responsible for schedule cost impacts subject to reimbursement, in accordance with the Prime and Subcontract Agreements.

3. Electrical Subcontractor

a) The Controls Contractor is completely responsible for all sub-tier trades required to complete the Controls Work, including Controls Contractor’s electrical subcontractor, and will be held accountable for any issues relating to:

i) Scope

ii) Schedule

iii) Material delivery or storage

iv) Coordination with various trades

Last Revision: 02/2025 4

v) Workmanship

vi) Staffing

vii) Back charges

viii) Site Specific Safety

4. Quality Assurance

a) Coordinate all related network infrastructure changes with McKinstry. Any changes to network components or infrastructure without prior authorization from McKinstry/the Owner is not permitted.

b) Materials and equipment will be the catalogued products of manufacturers who regularly engage in production and installation of building automation systems. Materials and equipment will be the manufacturer's latest design that complies with the specification requirements.

c) All hardware, software, components, and accessories must be:

i) New from the factory

ii) In production and not a legacy product

iii) Supported by the manufacturer

iv) Free of defects

v) Provided by the same manufacturer for each product type throughout the duration of the project

5. Submittals

a) Submittals must be reviewed by McKinstry, the Owner, the Design Professionals, and/or an Owner’s

Representative for conformity with the design intent. Execution of work will not be performed until the related submittals have been reviewed for conformity with the design intent, and the Contractor has responded to all comments to the satisfaction of the Owner, the Design Professional and/or the Owner’s Representative.

b) Contractor is required to provide their submittals in a timely manner to allow for timely review, resubmittal as needed, and final review before proceeding with work, in accordance with the project schedule. Failure to submit in timely manner does not alleviate Contractor from meeting the project schedule unless they receive approval of schedule change by the Owner, in accordance with the Prime and Subcontract Agreements.

c) The submittal schedule shall be as follows unless otherwise directed by McKinstry and/or the Owner:

i) The first submittal package shall consist of Hardware and Shop Drawings and shall be submitted with a schedule established by McKinstry in project related bid documents.

ii) The second submittal package shall consist of the Controls Contractor’s proposed project team and their qualifications that conform to 2.a.i) through 2.a.vi) above.

iii) The third submittal package shall consist of Programming and Graphics and shall be submitted no less than 30 days before software installation and system integration.

iv) The fourth submittal shall consist of BAS Controls Pre-Functional Test (PFT) Procedures and Blanks

Forms and shall be submitted no less than 30 days prior to performing Functional Testing for the McKinstry Commissioning Agent.

v) The fifth submittal package shall consist of training materials and shall be submitted no less than 14 days prior to conducting the first training class.

d) Submission and Resubmission Procedure:

i) All documents shall be in a word searchable format.

ii) Submittals shall be submitted electronically through the project specific software, such as Procore.

iii) When making corrections:

(1) Revise the initial submittal to resolve review comments and corrections.

(2) Indicate any changes that have been made other than those requested.

(3) Clearly identify resubmittal by original submittal number and revision number.

Last Revision: 02/2025 5

iv) Resubmit revised submittals until no exceptions are taken.

v) Once submittals are accepted with no exceptions taken, provide the following:

(1) Complete submittal of all accepted drawings and products in a single electronic file.

(2) Electronic copies for coordination with other trades.

e) Submittal Package for Hardware and Shop Drawings:

i) Hardware:

(1) Do not submit products that are not used even if included in specifications.

(2) Include a summary table of contents listing for each device submitted for this project. The table shall include:

(a) Location of device within the submittal package (page number or tab)

(b) Device tag noted within this specification or the drawing set.

(c) Whether the device is per specification or a substitution.

(d) Manufacturer

(e) Model

(f) Device Accuracy (if applicable)

(3) The submittal shall include:

(a) Manufacturer’s description

(b) Manufacturer's performance and technical data

(c) Product specification sheets

(d) Installation instructions

(e) PICS statement, BIBB, and BTL listing documents for all BACnet devices

(4) Manufacturer datasheets that contain a series of components must clearly indicate the specific component that is applicable to this project.

(5) Each submitted piece of manufacturer literature will clearly reference the specification or drawing that the submittal is to cover. General catalogs shall not be accepted as cut sheets to fulfill submittal requirements.

ii) Shop Drawings

(1) General Shop Drawing Format:

(a) Sheets shall be consecutively numbered.

(b) Each sheet shall have a title indicating the type of information included and the mechanical/electrical system controlled.

(c) Table of Contents listing sheet titles and sheet numbers.

(d) Legend and list of abbreviations.

(e) All schematics, diagrams, and floorplans listed below.

(2) System architecture one-line diagram indicating schematic location of all field devices, workstations, gateways, switches, etc. The following information shall also be noted on the system architecture one-line diagram:

(a) Network ID for each individual network

(b) Device IDs for each device

(c) DHCP configuration for IP devices

(d) Previous device in daisy chain installation

(e) Hosted Network Information

(3) Schematic flow diagrams for each air, hydronic, and steam system that clearly indicate fans, coils, valves, dampers, pumps, heat exchanging equipment and control devices.

(4) Schematic flow diagrams will reflect schematics provided on the project drawings set with respect to layout and location of control points.

(5) All physical points on the schematic flow diagram shall be indicated with point naming matching the Owner’s standard, descriptors, and point addresses identified as listed in the point summary table. Each physical point shall be labeled with their appropriate range.

(6) Device layout for each unique device requiring the following information:

Last Revision: 02/2025 6

(a) Device layout with enclosure information, enclosure ID, device name, IP address, Device ID, and manufacturer make and model number.

(b) Connection to all peripheral equipment with point naming matching the Owner’s standard, wiring layouts, and bill of material.

(c) Location of installation for each device and expansion module including panel numbers.

(d) Power wiring including power source location, electrical panel number, and breaker number.

(e) Communication wiring including the previous and next device if daisy chain configuration, and switch/port information if IP device.

(f) All electrical wiring diagrams shall be included. Provide both ladder logic type diagrams for motor starter, control, and safety circuits and detailed digital interface panel point termination diagrams with all wire numbers and terminal block numbers identified.

Clearly differentiate between portions of wiring that are factory-installed and portions to be field-installed.

(7) The bill of materials provided with each device layout shall include all materials and equipment, including:

(a) Device tags as indicated in the schematic and actual field labeling. Tags shall be used as indicated in these specifications where applicable.

(b) Description.

(c) Proposed manufacturers make and model.

(d) Range.

(e) Quantity.

(8) Valve sheet providing valve and actuator information, including:

(a) Pipe and valve size

(b) Cv

(c) Design flow

(d) Target pressure drop

(e) Proposed manufacturers make and model

(f) Close off rating

(g) Normal position of fail-safe actuators

(9) Floorplans noting proposed field device installation locations and thermostat locations.

(10) Initial Sequence of Operations

(a) The Controls Contractor Lead Programmer(s) shall review the Sequence of Operations for constructability prior to providing the submittal to McKinstry.

(b) Control sequences cannot be a direct duplication of design sequence and should include any proposed changes, additional details and clarifications from the subcontractor.

f) Submittal Package for Controls Contractor Project Team and Qualifications

i) Please see Personnel and Support Section 2.a.i) through 2.a.vi) for more details.

g) Submittal Package for Programming and Graphics

i) A detailed description of point naming convention conforming to the Owner’s standard to be used for all software and hardware points, integrated with existing database convention.

ii) A list of all hardware and software points identifying their full text names, device addresses and descriptions.

iii) Control logic program listings consistent with the submitted Sequences of Operation for all proposed equipment for this project. Control logic shall be annotated to describe how it accomplishes their respective Sequences of Operation and shall be sufficient to allow an operator to relate each program component to their corresponding portions of their respective Sequences of Operation.

iv) Include an updated written Sequences of Operation that are updated to reflect any suggested changes

Last Revision: 02/2025 7 made by the Contractor to clarify or improve the sequences and provide additional details or clarifications to reflect the actual programmed sequences. New Sequences of Operation shall be fully consistent with the graphical programming.

(1) Include control settings, setpoints, throttling ranges, reset schedules, adjustable parameters and limits.

(2) Submit one complete set of programming and operating manuals for all digital controllers concurrently with control logic documentation.

v) Graphics screens for all required graphics.

vi) List of points that will be trended.

h) Submittal Package for BAS Controls Pre-Functional Test (PFT) Procedures and Blanks Forms

i) The BAS PFTs shall include the following installation and pre-functional checks, and point-to-point tests, as described below (i.e., the procedures shall include more than just point-to-point tests).

(1) Installation verification of the control input and output points (sensors, actuators, relays, etc.)

to verify all points have been installed per the design and the physical installation of each point has been verified.

(2) Checks of the BAS program setup/configuration parameters (i.e., point type, and range / scale) to verify the BAS parameters match the physical sensor/device parameters.

(a) The contractor forms shall include columns for the checking and documenting the BAS program point type and range/scale parameters (and any other applicable parameters), and columns for checking and documenting the actual sensor/device point type and range/scale (and any other applicable parameters). Both sets of columns are required to document the BAS parameters and the actual sensor/device parameters match.

(i) For example, for a differential pressure analog input point, checking and documenting the BAS point type configuration is AI, DPT, 0 to 5 in w.c., 4 to 20 mA, etc., and checking and documenting the actual sensor/device type and range/scale is a DPT, 0 to 5 in w.c., 4 to 20 mA, etc. For this example, the checks confirm the DPT input range in the BAS is indeed 0 to 5 in. (same as the actual DPT) and not 0 to 10 in.

(ii) For example, for a valve actuator analog output point, checking and documenting the BAS point type configuration is AO, proportional 0 to 100% open, 0 to 10 VDC, and documenting the actual valve type and range/scale is a modulating valve actuator, proportional 0 to 10 VDC, etc. For this example, the checks confirm the valve actuator output range in the BAS is indeed 0 to 10 VDC (same as the actual valve actuator) and not 2 to 10 VDC.

(3) Point-to-point tests to verify the BAS input values/reading and output commands at the system graphics matches the actual sensor/device physical reading, operation, or position, and/or to verify the accuracy of any input readings (temperatures, flow rates, etc.).

(a) The BAS Contractor shall provide written procedures as to how they are going test each point type (AO, AI, BO, BI). See below 3.c. through 3.e. for the minimum requirements to be included in the procedures for testing analog inputs and outputs.

Any additional requirements per the design specifications shall also be included in the submitted procedures.

(b) The forms shall include columns for the documenting the BAS input readings or output commands (at the BAS graphics), and documenting the actual physical reading, operation, or position, to verify they match or are within acceptable tolerances.

(c) For analog input (AI) sensors/transmitters that are factory calibrated (no field calibration is required per the Specifications), all sensor readings on the BAS graphics shall be recorded on the forms and shall be verified as follows:

Last Revision: 02/2025 8

(i) If the sensor/transmitter has a local readout, then also record and verify the actual sensor/transmitter reading matches the BAS reading.

(ii) If the sensor/transmitter does not have a local readout, then verify the BAS reading is within the expected range (based on the operating condition and/or compared to other sensors measuring the same condition) OR verify the BAS reading based on a comparison measurement using a hand-held sensor of equal accuracy (as required per the design specifications).

(iii) Sensor readings that are questionable, outside the expected range shall be checked by the BAS Trade Contractor using a hand-held sensor of equal accuracy.

(d) For analog input sensors that require field calibration, follow the manufacturer requirements for calibration and record the calibration results in the PFT forms, including any readings using a hand-held sensor or measurement device of equal accuracy.

(e) For analog output (AO) points (e.g., actuators and VFD speeds), the points shall be physically checked to verify the commanded versus actual position or speed as follows:

(i) the commanded full (100%) open position / speed,

(ii) commanded half (50%) open position / speed and

(iii) commanded fully closed position (0% open) / 0% speed.

(f) For all terminal units (including lab controls), also include the following:

(i) The point-to-point tests are to include disconnecting the sensor / thermostat or adjusting the local thermostat setpoint adjustment to verify it’s connected to and controlling the correct terminal unit.

(ii) Commanding the supply airflow damper / valve to both fully closed and fully open and recording and verifying the airflow readings (i.e., no airflow when closed and near or greater than the design/max airflow when fully open).

(iii) Commanding the reheat coil valve to both fully closed and fully open and recording the unit discharge air temperature (DAT) reading and verifying the DAT readings for both commands (i.e., the DAT is the same as the AHU when the valve is closed, and the DAT is near the design DAT when fully open).

(4) Checks to verify all the network integration points to the BAS via network interface communications (e.g., BACnet, Modbus, etc.), including both read only and writable points.

(5) Checks to verify all the control sequence programming, graphics, trend logs and network communications, including verification that all point values and adjustable setpoints are properly displayed on the system graphics and the sequence of operations programming including alarms is completed per the current sequence of operation.

i) Submittal for Training

i) See Owner Training section below for specific details on what to include in this submittal.

6. Project Schedule

a) All work is to be performed in conjunction with the project schedule, with minimal occupant disruption.

Unless otherwise noted, work shall be done during normal business hours. When working in occupied spaces, Subcontractor may enter spaces at a maximum three (3) times to complete their work (wire pulls, terminations, programming, point-to-point, final commissioning, etc.). Any additional access into occupied spaces must be submitted via written request and approved by McKinstry at least three (3) days in advance of access.

b) Controls Contractor adherence to the performance standards outlined in this document will result in an efficient and timely final validation of the controls system. Any deviation from this performance standard must be communicated to McKinstry immediately for impacts on cost and schedule.

Last Revision: 02/2025 9

7. Installation

a) Ease of access to installed sensors and actuators shall be considered for future maintenance.

b) Exposed wire in occupied areas must be approved by the Owner and shall be in conduit or a raceway. Use of wire mold for exposed wire must be approved by the Owner. Otherwise, assume all wiring should be out of site in occupied areas, supported by structural members and at a minimum of every ten (10) ft.

c) All programming shall be properly commented for future changes and review. At a minimum each block of code shall include a header comment saying what the block is controlling and a quick expected sequence of operation.

d) The Contractor will always maintain red lined copies of as-built drawings on site.

e) Following ASHRAE Guideline 36, the speed analog output (AO) sent to VFDs shall be configured such that

0% speed corresponds to 0 Hz, and 100% speed corresponds to maximum speed configured in the VFD. This will avoid operator confusion, as the speed command point (and speed feedback point, if used) for VFDs are configured so a speed of 0% corresponds to 0 Hz, and 100% corresponds to maximum speed set in the VFD, not necessarily 60 Hz. The maximum speed may be limited below 60 Hz to protect equipment, or it may be above 60 Hz for direct drive equipment. Drives are often configured such that a 0% speed signal corresponds to the minimum speed programmed into the VFD, but that causes the speed AO value and the actual speed to deviate from one another (and thus is not allowed).

f) Labeling

i) Label each controller with the equipment served, device ID (if BACnet), and IP address if it’s an IP controller.

ii) Label all input wires per the project specification requirements – if no project-specific labeling requirements have been defined, the following is the minimum labeling standard: All wires and cables shall be identified with type labels or wire tag at each end.

iii) Wire designators at controllers shall describe the device termination point and function. (i.e. – AC- 1_SAT or EF-1_ Status, AC-1_OSA Dmpr, etc.). The intent is that the wiring tags in the control panels clearly describe the device/service that each wire provides. Labeling shall match the As-Built drawings

– update each to match each other at project completion.

iv) Label thermostats with the device(s) they control.

v) At project completion, update the construction drawings to ‘as-built’ conditions and after the drawing content/accuracy are approved, provide a laminated print or in a plastic sleeve (min. size: 11”x17”) of each panel’s terminations/systems attached to the inside cover or door of each enclosure

vi) Verify that cable labeling is complete at each end of each cable and properly identifies the termination/device at the opposite end – include the labeling information on the point-to-point documentation report.

vii) Labeling of the ceiling grid to identify VAVs, VVTs etc. shall be discussed and agreed upon by the Owner and McKinstry.

8. Functional Testing

a) Completion of the BAS Controls Pre-Functional Tests (PFTs)

i) The BAS Trade Contractor shall complete the PFTs for all systems and equipment (no sampling allowed).

ii) The BAS Trade Contractor shall document the completion of the PFT tasks on the approved PFT forms submitted to McKinstry through project specific software, such as Cx Alloy.

iii) The McKinstry Cx Team will review the completed PFT forms.

iv) McKinstry will also conduct various field observations and reviews of the PFTs.

v) The BAS Trade Contractor shall resolve any PFT issues or results deemed unacceptable by McKinstry.

b) BAS Controls PFT Field Back-Check Verifications and Programming & Graphics Review (prior to Cx FPTs)

i) The BAS Trade Contractor shall support commissioning by participating in the BAS PFT Field Back-check

Last Revision: 02/2025 10

Verifications, in which the BAS Trade Contractor reviews and demonstrates specified results to McKinstry, after completing and submitting the BAS PFT forms, and prior to the Cx FPTs.

(1) The BAS PFT Field Back-check Verifications shall include field review of the control system sensor / device installations and live readings, and field demonstrations (back-check) of the PFTs performed by the Trade Contractors and witnessed by McKinstry, for an approximate sample, to be selected by McKinstry for each major system. Please ask McKinstry what the sampling percentage should be for this project.

(2) Any Cx issues reported by McKinstry shall be reviewed and addressed by the BAS and Mechanical Trade Contractors, and if required, the PFT forms shall be revised and resubmitted, prior to performing any FPTs.

ii) Prior to conducting the FPTs, the BAS Trade Contractor shall meet with McKinstry to review the programmed sequences of operation and sample system graphics with McKinstry.

(1) The lead programmer from the BAS Trade Contractor shall be in attendance.

(2) The intent of this requirement is to reduce field testing time by reviewing with McKinstry the actual programmed sequence logic and graphics relative to the approved submittal, sequences and FPT forms, to confirm the actual programming and graphics prior to field testing, and to allow for any changes and adjustments.

c) Cx Functional Performance Tests (FPTs)

i) The BAS Trade Contractor shall execute the FPTs, with the FPTs witnessed by McKinstry, unless otherwise stated by McKinstry.

ii) The BAS Trade Contractor is responsible for ensuring all systems are installed, operating and performing per the requirements of the contract and design documents, and are ready for the FPTs.

(1) Prior to conducting the FPTs, the BAS Trade Contractor shall place the systems and controls into the operating modes intended for testing. Check all control system safety cutouts, alarms, and interlocks with smoke control and fire-life safety during each mode of operation prior to functional testing. Ensure all systems are operating and performing per the requirements of the contract, design and submittal documents, and have been pre-tested per the FPTs, and are ready for the McKinstry witnessed FPTs.

(2) The BAS Trade Contractor shall provide any necessary control system global or system level commands and setpoint adjustments necessary to conduct the testing as called out in the FPT procedures.

(3) The FPTs shall be conducted onsite by the BAS Trade Contractor’s lead programmer for the project who programmed the sequences of operation and configured the graphics. Conducting the FPTs offsite (remotely) shall only be approved by McKinstry.

iii) A percent sampling approach may be used for executing the FPTs of identical systems and equipment.

The approximate system sampling rates for the manual (direct observation) FPTs will be defined in the Cx Plan.

iv) The acceptance criteria for the FPT sampling shall be zero, meaning, any FPTs that do not pass shall require the Trade Contractor to resolve the issue for all applicable systems and equipment (even those specifically not in the original sample) and new sample rates selected for a re-test executed by the Trade Contractor and witnessed by McKinstry Cx. McKinstry Cx shall deem the FPTs acceptable after all FPTs, including re-tests, have passed and resolution of all issues completed.

v) McKinstry will document the results of all FPTs on the associated FPT forms created by McKinstry, unless indicated otherwise on the FPTs.

vi) If McKinstry finds that a significant percentage of equipment is indicated as ready for commissioning yet doesn’t pass the FPTs, McKinstry reserves the right to back charge Controls Contractor for additional labor and travel to complete commissioning.

9. System Usability (GUI)

Last Revision: 02/2025 11

a) The intent of a graphical user interface is to provide an easy-to-use window into the system components.

As such, the user-interface should have the ability to manipulate the final control devices and all adjustable setpoints directly from the graphics.

i) For example, if there is a chilled water valve being controlled by the BMS system, the operator shall be able to click on the valve, or obvious control link to allow the position to be manually set, locked in place, or released back to automatic control, as required.

b) When a point has been overridden from automatic mode, this state shall be readily displayed or indicated on the system graphic schematic screen without having to drill deep into the controller hardware level of access screens. All overrides shall have a pop-up screen that requires the user to select various times for the override (1 hour, 2 hours, etc.) and has an option for a permanent override.

c) Access Control: When possible, and with the Owner’s consent, provide a minimum of three (3) access levels:

i) Read Only – Ability to review the system operation only. No ability to make system modifications.

ii) Operator – Ability to manipulate the system (setpoints, trends, schedules, etc.) for the purposes of day-to-day system operations.

iii) Full Control – Ability to modify any component or element within the system

d) Alarm Graphics Interlocking.

i) Specific high/low setpoints and requirements should be provided in the project points list and coordinated with McKinstry and facility Owner prior to control system startup.

ii) Verify requirements for alarm definitions, routing, priorities, etc. before the initiation of PFTs. Submit required information early enough in the process so that the lack of information does not impact the commissioning and/or checkout process.

iii) Verify all alarm signals from device initiation through all required notification components.

(Workstation, text message, e-mail, local annunciation, etc.)

e) System Scheduling:

i) System schedules shall be set up by the control contractor as outlined below.

ii) Schedule requirements must meet the design intent/Owner requirements. If not clearly defined in the design intent/Owner requirements, for each start/stop point or terminal unit, provide, at a minimum, a scheduler with eight-day types (M, Tu, W, Th, F, Sa, Su, H), a minimum of four start/stop schedules each day type, 30 holidays each year and ten (10) multiple-day special event schedules each year.

iii) Scheduling may be required to be different for different parts of the building and the Controls Contractor shall accommodate these varying schedules.

f) Graphics:

i) One graphic shall be created for unique equipment. If something needs to be changed, it should be changed once and retroactively applied to all like equipment.

ii) As part of each graphic screen page, provide a menu for switching to associated system screen pages to minimize the amount of menu switching required. (Typically, via key buttons or ‘Forward/Back’ buttons)

iii) Provide one graphic screen for each air handling system and associated exhaust fans, zone pumps, etc.

in schematic format. (Custom-built for each project)

iv) Provide at least one graphic screen for each heating or cooling water system in schematic format, more if the systems are complicated. (Custom-built for each project)

v) Provide one graphic screen for each floor plan (scaled to fit the screen), displaying all zone space temperatures with same display access to each zone controller graphic, and a unique background color for each air handling system (area served) to facilitate easy understanding of the zoning. If a floorplan cannot fit on a single page, it shall be broken into reasonable sections that are approved by McKinstry and the Owner. All units shall have the equipment name and zone served displayed.

vi) Provide dynamic display graphics, to indicate status feedback (i.e., fans spin, and dampers actuate for all control output devices, VAV boxes and hydronic heat pump zones.) If the dynamic graphic is used to indicate command, it should be clearly labeled on the graphic that it is a command value not actual

Last Revision: 02/2025 12 status.

vii) All graphics will be properly labeled including units and spelling. Unused and unnecessary points will be removed from the graphics.

viii) Include a terminal unit report/summary page of damper position, space temperature, heat command, discharge air temperature, fan status, primary air temperature, space set point, etc. The summary page shall be in sections by system.

ix) A direct link to the as-builts with as-built Sequence of Operations shall be included on the main graphics page.

x) For retrofit projects, in the navigation tree, all obsolete points shall be deleted.

g) Setpoints and Variables

i) All sequence setpoints and variables used in the sequence of operation shall be adjustable to the appropriate user from the GUI. Key variables, such as important time delays or offsets shall not be adjustable only in underlying code. All sensor points, set points, and reset logic points shall be displayed.

10. Data Trending

a) Unless otherwise specifically indicated on controls points lists in the scope of work document, all controls points necessary for execution of approved sequences of operation shall have trending established.

i) Analog (AI, AO and software AV points) control points shall be set up to be trended at least as frequently as every five (5) minutes.

ii) Binary (both BI and BO) control points shall be set up to be trended as a change of value.

iii) Programming Submittal shall include points to be trended for review and approval by McKinstry and

Owner.

b) Automation system historians shall be enabled. Building automation systems shall have the capability of trending and storing all points necessary for execution of the approved sequence of operation for a minimum of one year at the required frequency.

c) A trend log that shows all trended points for a piece of equipment overlayed on one page shall be available for each piece of equipment.

d) Controls Contractor shall also include all hardware, software, labor and programming necessary to push trended data from the building automation system to McKinstry’s servers at the frequency specified on a project-by-project basis. If no data push frequency is established elsewhere in these scope of work documents, the frequency shall be daily.

e) Trend Reports: Establish trend reports of system points as requested by McKinstry. Trend reports shall be transmitted as .csv or Excel files.

11. Punch list / Deficiency Resolution

a) If deficiencies are discovered and deemed the responsibility of the Controls Contractor, McKinstry will notify the Controls Contractor through project specific software, such as Cx Alloy. Within one business day of deficiency notification, the Controls Contractor must resolve or provide the earliest possible time and date the deficiency can and will be resolved. The Controls Contractor shall update and closeout the deficiency within the project specific software, such as Cx Alloy.

b) Control deficiencies discovered during McKinstry’s commissioning process that results in the need for McKinstry to retest, are subject to cost impacts.

12. Owner Training

Last Revision: 02/2025 13

a) The Controls Contractor is responsible to provide Owner training on their installed system. A training agenda shall be provided by the Controls Contractor and shall be approved by McKinstry and the Owner prior to training. Owner facility staff attending training sessions "sign off" on attendance sheets and "sign off" on thoroughness of training sessions. Controls Contractor shall supply electronic copies of Training Session attendance sheets and signed Owner Acceptance of Training sheets to McKinstry.

b) The training must be performed by qualified individuals familiar with the specifics of the project for a sufficient duration, a minimum of eight (8) hours that may need to be delivered over multiple sessions, to ensure that facility staff has all the information needed to optimally operate, maintain and replace the commissioned features and systems.

c) Training will not be scheduled until all integrated systems and GUI components are completed, functional, and all commissioning has been completed.

d) If device integration coincides with other subsystem installation, Owner training for subsystems may be completed in parallel with training mentioned within this specification.

e) Provide a factory-trained instructor or representative to give full instructions to designated personnel in the operation, maintenance, and programming of each piece of equipment or system. Instructors shall be thoroughly familiar with all aspects of the subject matter. The Contractor will provide all equipment and material required for classroom training.

f) Proposed training instructor qualifications will be provided to the Owner and subject to approval by the Owner.

g) Training will include classroom instruction and hands-on field instruction.

h) All training is subject to be recorded by the Owner for internal use.

i) Minimum requirements for classroom instruction are the following:

i) Review of project record documentation

ii) Maintenance procedures and schedules

iii) Any pertinent safety requirements

iv) Operator control functions

v) GUI navigation, including:

(1) Login/logout procedures, password setup, and audit log reporting

(2) Menu navigation and broad overview of the various functions and features

vi) Explanation of controller backup procedures

vii) Explanation of procedures to restore any database. Scenarios to explain include:

(1) Corrupted database restoration

(2) Restoration of database in a new controller

viii) Sequence of Operations review

ix) A detailed review of programming, trending, and alarm database management.

x) Training manuals will be provided and include screen captures with detailed instructional annotation for each step required to complete all portions of the training.

xi) Additional topics can be requested by the Owner in advance of the training sessions. Each additional topic will require the Contractor to prepare and submit training manuals with the same level of detail as described above.

j) Minimum requirements for field instruction:

i) Walkthrough of the project to locate integrated components

ii) Demonstration of operation from Supervisor to integrated equipment

13. Completion Deliverables

a) For project closeout, the Controls Contractor will be required to provide the following documentation electronically as well as in paper format if requested:

i) Product data, shop drawings, control logic documentation, sequence of operation, hardware manuals, software manuals, installation guides or manuals, maintenance instructions and spare parts lists.

Last Revision: 02/2025 14

ii) As-built versions of the submittal data.

iii) Operator's manual with procedures for operating control systems: logging on and off, handling alarms, producing point

b) At project completion, ensure that any computer hardware or software necessary for accessing/operating the control system, is permanently installed and functional at the Owner’s user interface, and has the appropriate licensing to allow for full functionality of the system at project turnover. The licensing start date shall be the date of substantial completion, which is determined by the Owner. This shall be at no additional cost to the project. All hardware, software, and license(s) will become the property of the system Owner.

c) At substantial completion, ensure that the version of any installed software is the most-current available from the control manufacturer for the system installed at the project. This shall be at no additional cost to the project.

14. Ownership of Proprietary Material

a) Project specific software and all related documentation will become the property of the Owner. This includes, but is not limited to, the following:

i) Graphical Templates

ii) Project Record Drawings

iii) Station Databases

iv) Custom Logic

15. Warranty

a) Warranty documentation will be submitted for acceptance to McKinstry within 14 days after signed substantial completion from the Owner.

b) Vendor specific warranty information will be provided as part of the Contractor warranty documentation.

Any manufacturer’s warranty that exceeds the established project warranty will be extended to the Owner and documented in a Warranty Spreadsheet. McKinstry will provide the Warranty Spreadsheet template upon project substantial completion.

c) The warranty start date will be the date of substantial completion, determined by the Owner. Please refer to the Standard Scope Requirements for the warranty duration.

d) Device failures during the warranty period will be adjusted, repaired, or replaced with no additional cost to the Owner or McKinstry.

e) Any standard troubleshooting or routine maintenance completed by the Owner will not void any warranty or incur any additional costs.

f) Contractor will respond during normal business hours within 24 hours of a warranty service request.

g) All corrective software modifications made during the warranty period will be updated on all project documentation and updated software files will be provided to the Owner for record purposes.

h) Software fixes and firmware updates will be covered throughout the warranty duration with no additional cost to the Owner or McKinstry. With approval of the Owner and assurance that no existing equipment connections will be adversely affected, patches and updates will be applied within 72 hours of becoming available from the manufacturer.

i) Expiration of the warranty period does not relieve the Contractor of the responsibility to:

j) Correct all deficiencies identified during the warranty period

k) Fulfill all specified obligations during the warranty period

l) The Contractor will not be required to warranty reused devices, except those that have been rebuilt or repaired. Reused devices must demonstrate they are in operable condition at the time of substantial completion.

m) Parts, labor, and travel will be included during the warranty duration.