INTEGRATED AUTOMATION SYSTEM IAS COMMISSIONING

This section defines how the IAS Contractor will interact with a Commissioning Authority CxA, it can also be used to define the Construction Administration process for projects that do not include the services of a CxA.

INTEGRATED AUTOMATION SYSTEM IAS COMMISSIONING

  • GENERAL

    • RELATED DOCUMENTS
      1. Drawings and general provisions of the Contract, including General and Supplementary Conditions and Division 01 Specification Sections, apply to this Section.
      2. Specifications throughout all Divisions of the Project Manual are directly applicable to this Section, and this Section is directly applicable to them.
      3. <Add a reference to specific Commissioning Specifications, if any, that apply to the IAS, coordinate the contents of this section with the Commissioning Specifications for the overall project>
      4. <Develop forms for submission of CCO and other performance data. Add a reference to the forms>

  • SUMMARY

    1. Section includes:
      1. IAS and equipment testing and Start-up.
      2. Validation of proper and thorough installation of IAS and equipment.
      3. Functional testing of control systems.
      4. Documentation of tests, procedures, and installations.
      5. Details pertaining to Contractor’s Check Out / CCO scope of work
      6. Details pertaining to Commissioning Authority’s Scope of work.

<Do not use the term Commissioning “Agent” unless specifically requested. The use of “Agent” will have legal ramifications on the project and they must be understood and accepted by the Owner and CxA. “Authority” does not carry the same level of legal weight or liability.>

    1. Summary of system acceptance.
    1. Refer to <01 91 00 and 23 05 93 (confirm or modify specification references, include reference in 1.01 RELATED DOCUMENTS)> for project specific requirements pertaining to system commissioning and Testing, Adjusting and Balancing (TAB).
    2. This Section defines responsibilities of the Contractor to test, calibrate, check out and document the proper operation of the IAS referred to as “Contractor Check Out” or CCO.
    3. The term “Commissioning Authority” or “CxA” shall refer to a representative hired at the option of the Owner or the Architect that shall coordinate, oversee, and perform system commissioning and or functional dynamic mode testing of the IAS. The CxA shall follow the requirements defined in the contractor check out (CCO) procedure. The scope of the CxA also involves the commissioning and fine tuning of the Graphical User Interface as defined in the software optimizations section of this specification. The contracting of a CxA by the Owner or Architect does not release the contractor from their obligation to perform and deliver the CCO as defined in this section.
    4. Contractor Check Out (CCO) to be performed by the controls contractor is the process of ensuring and documenting that all building systems are installed and perform interactively according to the design intent, the systems are functioning in an efficient and cost effective manner, and that the performance of the system is in 100% compliance with the design documents, design intent and Owner’s operational needs. The CCO serves as a tool to minimize post-occupancy operational problems. It establishes testing and communication protocols in an effort to advance the building systems from installation to full dynamic operation and optimization. The CCO shall be performed prior to or, at the option of the CxA, in unison with the testing and commissioning activities to be performed by the CxA.
    5. In the absence of a Commissioning Authority the Contractor shall direct, coordinate, and oversee the CCO process and witness functional performance testing in coordination with the Owner’s Representative. The contractor shall notify the Owner’s/CxA Representative of all equipment functional tests for Owner/CxA witnessing, at their option.
    6. The contractor shall meet with the Owner/CxA when applicable to review any specific requirements pertaining to documentation or test procedures which the Owner/CxA may enforce while evaluating the system performance and acceptance. The contractor shall abide by these requirements.
    7. The contractor shall include the time required to work with the CxA in their Base Bid.

  • REFERENCE STANDARDS

    • The latest published edition of a reference shall be applicable to this Project unless identified by a specific edition date.
    • All reference amendments adopted prior to the effective date of this Contract shall be applicable to this Project.
    • All materials, installation and workmanship shall comply with the applicable requirements and standards addressed within references.

  • Contractor Responsibilities for contractor check out procedures

    1. Completely install and thoroughly inspect, startup, test, adjust, balance, and document all systems and equipment in accordance with Part Three, Execution, of this section.
    2. Assist the Owner/CxA, and/or TAB Firm in verification and functional performance testing and GUI acceptance testing. This will generally include the following <Coordinate with the Commissioning Specifications>:
      • Attend Commissioning progress and coordination meetings.
      • Prepare and submit required draft check-out forms and systems information to be reviewed and approved by the Owner and/or CxA.
      • Provide the submittal requirements as defined in this section to the CxA for their use in the commissioning and testing of the system.
      • Establish trend logs of system operation as specified herein and as required by the CxA.
      • Demonstrate system operation.
      • Manipulate systems and equipment to facilitate testing. Providing staff to do so as required.
      • Provide instrumentation necessary for verification and performance testing.
      • Manipulate control systems to facilitate verification and performance testing. This may include providing the software or staff required to manipulate points which are not exposed to the GUI for the testing and acceptance of the system by the TAB, Owner, and/or CxA.
      • Provide dedicated and unique GUI system log in, user name(s) and password(s) with override access rights, to the CxA, Owner, and/or TAB for their use in testing and commissioning the system. Provide end user training to these users for system manipulation.
      • Meet with the CxA to review and demonstrate the GUI for the purpose of obtaining GUI acceptance. This shall include multiple meetings where in the CxA will provide feedback on the basic operation, look, feel, graphic placement and function of the graphics for the contractor’s correction as part of this scope of work.
    3. Provide an IAS Technician to work at the direction of Owner and or CxA for software optimization assistance for the number of hours specified herein. Refer to Part Three of this Section for a description of the software optimization.
      1. Contractor shall provide <40 hours> of software optimization assistance
    4. Compensation for Retesting: Contractor shall compensate Owner for site time necessitated by incompleteness of systems or equipment at time of functional performance testing.  All testing failures, which require on-Site time for retesting, will be considered actual damages to the Owner. All parties under Contract with the Owner who are affected by the retesting shall be included in the Contract modification.

<Requests for functional testing prior to confirmation of operation is a common occurrence to justify progress payments ahead of or to meet schedule. This is an important concept that holds the Contractor liable for scheduling functional tests when equipment is not ready for testing. It is highly recommended that this clause be included and enforced. Costs for retesting should be highlighted in the pre-bid meeting> 

  • Submittals

    1. The following items outline the general submittal requirements as they pertain to the commissioning of the system. The following data shall be provided to the CxA for approval. In the event that the Owner has not executed their right to contract a CxA, the following documentation will be provided directly to the Owner.
      • The contractor will receive a written request from the Owner/CxA requesting specific information needed about each piece of commissioned equipment or system. The contractor shall abide by this request.
      • Provide to the CxA a copy of all general submittals as outlined in section 25 00 00.
      • An updated version of the general submittals defined in section 25 00 00 which indicate As-built conditions.
      • Start-Up Checklists and manufacturer’s start-up procedures for all equipment provided by the Contractor.
      • IAS Start-Up Test Agenda and Schedule for review and approval.
      • Completed IAS Start-Up Reports and initial draft of the Operating and Maintenance (O&M) Manuals.
      • Field check out sheets completed by installation representatives or manufacturer’s factory testing check out forms as requested by the CxA. This shall extend to all major pieces of equipment such as but not limited to <(List specific equipment within IAS scope of Work) AHU, pumps, fans, UPS, Generators, Switchgear, Chillers, Boilers, and the like.>
      • Point to Point check out documentation including corrective actions taken for all issues resolved.
      • Sequence of Operation verifications forms. Documentation indicating tests and check-out procedures performed by the contractor to verify Sequence of Operation and functional testing of each piece of equipment.
      • Project proposed schedule as it relates to the IAS installation and the CCO procedures. The schedule shall include, milestone dates, completion dates, and CCO activities. This schedule shall be provided to the CxA and/or Owner 45 days prior to the first CCO activity taking place.
      • Logic Flow diagrams indicating how the sequence of operations were achieved and programmed by the Contractor. These flow diagrams shall be graphical in nature and shall be intuitive to decipher. No advanced programming experience shall be required to evaluate these documents. They shall logically depict the decisions, calculations and process involved with each sequence. Math and formulas for PID logic blocks need not be exposed however parameters used shall be indicated. Standard industry process flow diagrams are acceptable.
      • Print out of all Network Variables and Bindings required for operation.
      • Submit protocol analyzer reports for each channel indicating that the message traffic is less than 50% of the available bandwidth for the installed media/transceivers <LonWorks, BACnet, MODBUS>.
      • Certification of fully calibrated testing equipment used by the contractor for CCO testing.
      • Sample Screen captures demonstrating the basic look, feel, function, and navigation to be achieved via the Graphical User Interface. This shall include sample screen captures of the following:

<The GUI for the expansion of an existing system must utilize the same look, feel and function of the existing system. The process of commissioning the GUI will verify that the new system seamlessly integrates with the existing>

    • Home Page
    • Summary pages
    • Dash boards
    • Navigation Tree
    • Alarm pages
    • Major equipment such as <AHU’s, Central Plants, VAV>
    • Trend Data illustrations
    • Basic Graphics to be utilized
    • <Add reference to any project specific screens that require commissioning>
  1. Contractor’s responsibility for deviations in submittals from requirements of the Contract Documents is not relieved by the Commissioning Authority’s or Design Team’s review.

  • PRODUCTS

    • GENERAL

      • All materials shall meet or exceed all applicable referenced standards, federal, state and local requirements, and conform to codes and ordinances of authorities having jurisdiction.

    • INSTRUMENTATION

      • Instrumentation required to verify readings and to test the system and equipment performance shall be provided by Contractor and made available to Owner and or CxA. Generally, no testing equipment will be required beyond that required to perform Contractor’s Work under these Contract Documents. All equipment used for testing and calibration shall be NIST/NBS traceable and calibrated within the preceding 6-month period.  Certificates of calibration shall be submitted to the Owner/CxA.

    • TAB and CxA Portable operators terminal

      • Contractor shall provide unique and dedicated user names and passwords with full read-write access to the TAB and CxA contractor(s) for their access to the web based GUI system. When access to the system is limited to the GUI the TAB/CxA will furnish the laptop for this use. The contractor shall provide and coordinate local on-floor access to the system for the needs of the TAB/CxA contractor(s) and assist with their access and use of the system.
      • In the event that the TAB/CxA contractor(s) requires more advanced access to the system affecting the DDC controller database, the Contractor shall furnish and supply the software, user names, and passwords and/or the portable terminal device required by the TAB/CxA contractors for system balancing or commissioning. This software or device shall support all functions and allow querying and editing of all parameters required for proper calibration and Start-up.
      • Connections shall be provided local to the device being calibrated. For instance, <(use a relevant example requiring local control and validation such as…) for VAV terminal units, connection of the operator’s terminal shall be either at the sensor or at the terminal unit>.  Otherwise a wireless system shall be provided to facilitate this local functionality.

  • WORK EXECUTION

    • INSTALLATION

      • Installation shall meet or exceed all applicable federal, state and local requirements, referenced standards and conform to codes and ordinances of authorities having jurisdiction.
      • All installation shall be in accordance with manufacturer’s published recommendations.

    • IAS Contractor’s check out (CCO) Start-Up TESTING, ADJUSTING, CALIBRATION

      1. Work and/or systems installed under this Division shall be fully functioning prior to Demonstration and Acceptance Phase. Contractor shall conduct the CCO which addresses the start-up, testing, adjustments, and calibrations of all work and/or systems under this Contract, and as described below in this section. Contractor shall provide documentation which verifies that the following tests were performed and that each task passes the stated test.
      2. All CCO testing procedures listed below shall be documented in the CCO report to be provided by the contractor to the Owner/CxA.
        1. Inspect the installation of all devices. Review the manufacturer’s installation instructions and validate that the device is installed in accordance with them.
        2. Verify proper electrical voltages and amperages, and verify that all circuits are free from faults. Verify that proper emergency circuits have been used when required.
        3. Verify integrity/safety and installation practices of all electrical connections.
        4. Coordinate with Owner’s <Contractor’s> TAB Firm to obtain [and CxA to fine-tucontrol settings that are determined from balancing procedures. Record the following control settings as obtained from Owner’s <Contractor’s> TAB Firm, and note any TAB deficiencies in the IAS CCO Report: <The following list must be modified to reflect the performance characteristics of the equipment that is to be controlled>
          • <Optimum duct static pressure setpoints for VAV air handling units.>
          • <Minimum outside air damper settings for air handling units.>
          • Optimum temperature setpoints for all systems.
          • <Calibration parameters for flow control devices such as VAV terminal units and flow measuring stations.
            1. Contractor shall provide system access to the GUI or DDC database as needed via software, usernames, passwords, or hand-held device to the TAB Firm to facilitate calibration. Connection for any given device shall be local to it (i.e. at the VAV terminal unit or at the thermostat).  Hand-held device or portable operator’s terminal shall allow querying and editing of parameters required for proper calibration and start-up.>
        5. Test, calibrate, and set all digital and analog sensing and actuating devices. Calibrate each instrumentation device by making a comparison between the IAS GUI display and the reading at the device, using an instrument traceable to the National Bureau of Standards, which shall be at least twice as accurate as the device to be calibrated (e.g., if field device is +/-0.5 percent accurate, test equipment shall be +/-0.25 percent accurate over same range).  Record the measured value and displayed value for each device in the IAS CCO Report.
        6. Check and set zero and span adjustments for all transducers and transmitters.
        7. <Dampers and Valves:
          • Check for adequate installation including free travel throughout range and adequate seal.
          • Where control loops are sequenced, check for proper control without overlap.>
        8. <Actuators:
          • Check to insure that device seals tightly when the appropriate signal is applied to the operator. Document any leakage in the CCO report.
          • Check for appropriate fail position, and that the stroke and range is as required.
          • For pneumatic operators, adjust the operator spring compression as required to achieve close-off. If the positioner or volume booster is installed on the operator, calibrate per manufacturer’s procedure to achieve spring range indicated.  Check split-range positioners to verify proper operation.  Record settings for each device in the IAS CCO Report.
          • For sequenced electronic actuators, calibrate per manufacturer’s instructions to required ranges.>
        9. Check each digital control point by making a comparison between the control command at the CU and the status of the controlled device. Check each digital input point by making a comparison of the state of the sensing device and the Operator Interface display.  Record the results for each device in the IAS CCO Report.
        10. Calibrate ranges to establish proper parameters for outputs to reset other manufacturer’s devices (e.g. VSDs and flow stations) and for feedback from the devices. Coordinate with the representative of the respective manufacturer and obtain their approval of the design and installation.
        11. Verify proper sequences by using the approved checklists to record results and submit with IAS CCO Report. Verify proper sequence and operation of all specified functions.
        12. Verify that all safety devices trip at appropriate conditions. Adjust setpoints accordingly.
        13. Tune all control loops to obtain the fastest stable response without hunting, offset, overshoot, or hysteresis. Record tuning parameters and response test results for each control loop in the IAS CCO Report. Except from a startup, maximum allowable variance from set point for controlled variables under normal load fluctuations shall be as follows.  Within 3 minutes of any upset (for which the system has the capability to respond) in the control loop, tolerances shall be maintained (exceptions noted): <The following list must be modified to reflect the Scope of Work>
          • <Duct air temperature: [±1 degrees F].
          • Space Temperature: [±1 degrees F within 30 minutes].
          • Chilled Water: [±1 degrees F].
          • Hot water temperature: [±3 degrees F].
          • Duct pressure: [± 0.25 inches wg].
          • Water pressure: [±1 psid].
          • Duct or space Humidity: [±5 percent within 30 minutes].
          • Air flow control: [±5 percent of setpoint velocity].
          • Space Pressurization (on active control systems): [±0.05 inches wg] with no door or window movements.>
        14. Interface and DDC control panels:
          • Ensure devices are properly installed with adequate clearance for maintenance and with clear labels in accordance with the as-built record Drawings.
          • Ensure that terminations are safe, secure and labeled in accordance with the as-built record Drawings.
          • Check power supplies for proper voltage ranges and loading.
          • Ensure that wiring and tubing are run in a neat and workman-like manner, either bound or enclosed in trough.
          • Check for adequate signal strength on communication networks.
          • Check for standalone performance of controllers by disconnecting the controller from the FACLAN and DLN. Verify the event is annunciated at Operator Interfaces.
          • Ensure that all outputs and devices fail to their proper positions/states.
          • Ensure that buffered and/or volatile information is held through power outage.
          • With all system and communications operating normally, sample and record update/annunciation times for critical alarms fed from the panel to the Operator Interface.
          • Check for proper grounding of all DDC panels and devices.
          • Test and document the bandwidth utilization on all networks accessed in any way by the IAS devices or users.
        15. Operator Interfaces:
          • Verify that all elements on the graphics are functional and are properly bound to physical devices and/or virtual points, and that hot links or page jumps are functional and logical.
          • Verify that the graphics were developed using the correct or specified graphic standards. <Graphics must match existing graphics developed for previous phases>.
          • Verify that GUI navigations are as specified or per client standards. <Graphic navigation must match existing navigation developed for previous phases>.
          • Output all specified IAS reports for review and approval.
          • Verify that the alarm printing and logging is functional and per requirements.
          • Verify that trends are archiving to disk and provide a sample to the Owner/CxA for review.
          • <Verify that paging/email alarm annunciation is functional.>
          • Verify the functionality of remote Operator Interfaces and that a robust connection can be established consistently and securely.
          • <Verify that required third party software applications required with the bid are installed and are functional.>
          • <Start-up and check out control air compressors, air drying, and filtering systems in accordance with the appropriate Section and with manufacturer’s instructions.>
          • <Verify proper interface with fire alarm system.>
          • <Add reference to any other project specific operations that must be verified>
          • Demonstrate to the Owner/CxA that the above are complete.
      3. Contractor shall coordinate CCO tests with related tests and startup procedures within other divisions in order to fully test each aspect and conditions of the IAS as it pertains to electro-mechanical system operation. The tests shall include, but shall not be limited to, start up procedures and tests of <switch gear, UPS’s, generators, chillers and the like> so that various conditions such as power or equipment failures can be tested with respect to IAS operation. When such tests are to occur notify the Owner/CxA seven (7) calendar days in advance so that they may witness such tests. Provide documentation of all such tests to the Owner/CxA.
      4. Submit CCO Test Report: Report shall be completed, submitted, and approved by Owner/CxA prior to Substantial Completion and prior to additional testing or commissioning to be performed by the CxA. The report shall provide detailed documentation of all the requirements listed with in Part Three of this section.

    • Sensor Checkout and Calibration

      1. General Checkout: Verify that all sensor locations are appropriate and are away from causes of erratic operation. Verify that sensors with shielded cable are grounded only at one end.  For sensor pairs that are used to determine a temperature or pressure difference, make sure they are reading within <0.2 degrees F> of each other for temperature and within a tolerance equal to <2 percent> of the reading of each other for pressure.  Tolerances for critical applications may be tighter.
      2. Calibration: Calibration and verification of sensor calibration is required. For every sensor associated with major operating equipment such as AHU, MAU, etc. calibrate 100% of the sensors using one of the two methods below. For Space and VAV applications in non-critical areas the calibration rate can be reduced to 10% of the total count if and only if the 10% tested yields a passing percentage higher than 95% within specified tolerance. If not a higher random sample will be required and documented until the sample selected reaches a 95% passing rate or all sensors have been calibrated. Calibrate all sensors using one of the following procedures:
        • Sensors without Transmitters (RTD type) – Standard Application: Make a reading with a calibrated test instrument within 6 inches of the site sensor at various points across the range.  Verify that the sensor reading (via the permanent thermostat, gauge or IAS) is within the tolerances specified for the sensor.  If not, adjust offset and range, or replace sensor.  Where sensors are subject to wide variations in the sensed variable, calibrate sensor within the highest and lowest 20 percentage of the expected range.
        • Sensors with Transmitters – Standard Application: Disconnect sensor.  Connect a signal generator in place of sensor.  Connect ammeter in series between transmitter and IAS control panel.  Using manufacturer’s resistance-temperature data, simulate minimum desired temperature.  Adjust transmitter potentiometer zero until the ammeter reads 4 mA.  Repeat for the maximum temperature matching 20 mA to the potentiometer span or maximum and verify at the OI. Record all values and recalibrate controller as necessary to conform to tolerances.  Reconnect sensor.  Make a reading with a calibrated test instrument within 6 inches of the site sensor.  Verify that the sensor reading (via the permanent thermostat, gauge or IAS) is within the tolerances specified. If not, replace sensor and repeat.  For pressure sensors, perform a similar process with a suitable signal generator.
      3. Sensor Tolerance: Sensors shall be within the tolerances specified for the device. Refer to Section 25 11 00.

    • Coil Valve Leak Check

      1. Verify proper close-off of the valves. Ensure the valve seats properly seat by simulating the maximum anticipated pressure difference across the circuit.  Demonstrate to the Owner/CxA the verification of zero flow by measuring the coil differential pressure.   If there is pressure differential, close the isolation valves to the coil to ensure the conditions change.  If they do, this validates the valve is not closing.  Remedy the condition by adjusting the stroke and range, increasing the actuator size/torque, replacing the seat, or replacing the valve as applicable.

    • Valve Stroke Setup and Check

      1. For all valve and actuator positions checked, verify the actual position against the Operator Interface readout.
      2. Set pumps to normal operating mode. Command valve closed, verify that valve is closed, and adjust output zero signal as required.  Command valve open, verify position is full open and adjust output signal as required.  Command the valve to various few intermediate positions.  If actual valve position doesn’t reasonably correspond, replace actuator or add pilot positioner (for pneumatics).

    • Acceptance of third party interfaces

      1. The controls contractor shall be responsible for integrating and testing all intelligent communicating interfaces. Submit a list of <LonMark, MODBUS, BACnet or other> communications devices that have been installed by other divisions that are found to be defective during the network management or installation process.  It shall be the installing trade’s responsibility to repair.

    • Summary of IAS Acceptance Procedure

      • The following outlines the general requirements and procedures for the IAS acceptance procedure. Detailed requirements of each task or phase are defined with in the Division 25 specifications. These items should be followed and documented as noted. The CxA reserves the right to modify the acceptance procedure and to request information in advance as the official commissioning authority contracted by the Owner.
        • Submit product data and Shop Drawings submittals per section 25 00 00 to the Engineer of Record, and receive approval.
        • Submit IAS logic documentation to the Engineer of Record, and receive approval.
        • Submit background graphic screens to the Engineer of Record and CxA, and receive approval.
        • Install IAS. Obtain Owner/CxA acceptance of each phase of installation when installation consists of a renovation in an occupied space.
        • Provide the Owner/CxA a copy of all submittals approved by the engineer of record. Submittals shall reflect as-built conditions.
        • Provide the Owner/CxA an agenda and schedule of CCO testing activities for approval and coordination.
        • Submit Start-Up Checklists and manufacturer’s start-up procedures for all equipment provided by the Contractor for Owner/CxA approval.
        • Prepare and initiate trend log data storage and format trend graphs.
        • Submit completed IAS CCO Reports and initial draft of the Operating and Maintenance (O&M) Manuals for approval by Owner/CxA.
        • Schedule time to meet with Owner/CxA/Engineer to review system operation and developed system graphics for allotted improvements and revisions. Complete enhancements and review with Owner/CxA/Engineer.
        • Provide written notice that the system is ready for Owner acceptance testing. Schedule IAS Demonstrations and Owner/CxA Commissioning.
        • Meet with Owner/CxA to review GUI operation. Contractor to address all requests.
        • Demonstrate IAS systems to Owner/CxA/Engineer.
        • Owner/CxA to provide detailed punch list to contractor
        • Contractor to repair issues on Owner/CxA punch list in seven (7) calendar days.
        • Owner/CxA to review contractor corrections until satisfied.
        • Submit Trend Logs in format specified.
        • Receive demonstration approval and approval to schedule Acceptance Period.
        • Begin Acceptance Phase.
        • Two-week Operational Test.
        • Contractor to correct issues found during two week operational test
        • Owner/CxA to perform functional performance testing including point to point verification to graphical interface.
        • Receive Acceptance Period approval, which is substantial completion for the IAS.
        • Owner issues letter to contractor declaring that system is substantially complete. Date of this letter starts the warrantee period.
        • Begin Warranty Phase.
        • Train Owner on final sequences and modes of operation.
        • Turn over all usernames, passwords, software, GUI and DDC databases, licenses, and application programming tool(s) to the Owner.
        • Revise and re-submit as-built record Drawings and O&M Manuals.
        • Schedule and begin Opposite Season acceptance period.
        • Receive Opposite Season acceptance period approval.
        • Final Acceptance. Owner issues letter to contractor accepting system.
        • End-of-Warranty date/period.

    • IAS DEMONSTRATION

      1. All IAS Demonstration shall take place using workstations connected to the main Control Systems Server and Facility WAN when applicable. The IAS Demonstration shall include or provide all documentation and criteria listed below. This information shall be documented by the contractor and provided to and approved by the Owner/CxA.
        • Updated IAS submittals in electronic and hard copy to Owner/CxA including the updated riser diagram for the system. Verify that this information is saved and accessible on the Control System Server and is accessible via the GUI navigation.
        • Reports on verification of Network Layout Verification including but not limited to Building Controller locations, cable routes with length of cable between controllers and any trunk extenders or trunk isolators.
        • Reports on verification of electrical characteristics of IAS network, communications and electrical integrity of Building Controllers.
        • Reports on verification of traffic on IAS Network including but not limited to COVs between Building Controllers, point commands by the operator, point commands by program across the network, alarm reporting on the network, any unresolved points in the system, integrity of the ports on any Building Controller isolator/extender and results of Building Controller tests running at selected baud rate.
        • Demonstrate to Owner/CxA the updates of databases without errors or faults between the Control Systems Server and Building Controllers.
        • Reports on verification of system log files, interruption of log files of system traffic, bandwidth utilization and overall acceptable operation of the system.
      2. Demonstrate the operation of the IAS hardware, software, and all related components and systems to the satisfaction of the Owner/CxA. Schedule the demonstration with the Owner/CxA seven (7) calendar days in advance.  Demonstration shall not be scheduled until all hardware and software submittals, and the CCO Test Report are approved by the Owner/CxA.  If the Work fails to conform to the Contract Documents, so as to require scheduling of additional Site visits by the Owner/CxA for re-demonstration, Contractor shall reimburse Owner/CxA for costs of subsequent Site visits.
      3. The Contractor shall supply all personnel and equipment for the demonstration, including, but not limited to, instruments, ladders, temporary taps tees, valves gauges, piping, etc. Contractor-supplied personnel must be competent with and knowledgeable of all project-specific hardware, software, and the HVAC systems. All training documentation and submittals shall be at the Project Site.
      4. The Contractor shall repair all damage resulting from failure or lack of performances of the IAS while under test or by either the contractor, or the Owner/CxA or while under pre-mature system operation by the contractor.
      5. Demonstration shall be performed using the same operator interface (GUI) in which the end users of the system will utilize.
      6. Demonstration shall typically involve small representative samples of systems/equipment randomly selected by the Owner/CxA.
      7. The contractor shall demonstrate routine operating sequences, as well as emergency mode conditions, responses and sequences. This should include responses due to emergency conditions and the associated action, shut down, and start-up of related equipment.
      8. The system shall be demonstrated following the same procedures used in the CCO Test by using the approved checkout checklists. Demonstration shall include, but not necessarily be limited to, the following:
        1. Demonstrate that required software is installed on IAS workstations. Demonstrate that graphic screens, alarms, trends, and reports are installed as submitted and approved.
        2. Demonstrate that points specified and shown can be interrogated and/or commanded (as applicable) from all workstations, as specified.
        3. Demonstrate that remote communication abilities are in accordance with these Specifications and the Owner’s network security requirements.
        4. Demonstrate correct calibration of input/output devices using the same methods specified for the CCO Tests. A maximum of 10 percent of I/O points shall be selected at random by the Owner/CxA for demonstration. Upon failure of any device to meet the specified end-to-end accuracy, an additional 10 percent of I/O points shall be selected at random by Owner/CxA for demonstration.  This process shall be repeated until 100 percent of randomly selected I/O points have been demonstrated to meet specified end-to-end accuracy.
        5. Demonstrate that all DDC and other software programs exist at respective field panels. The Direct Digital Control (DDC) programming and point data IAS’s shall be as submitted and approved.
        6. Demonstrate that all DDC programs accomplish the specified sequence of operation.
        7. Demonstrate that the panels and DDC network of panels automatically recover from power failures within five (5) minutes after power is restored.
        8. Demonstrate that the stand-alone operation of panels meets the requirements of these Specifications. Demonstrate that the panels’ response to FACLAN communication failures meets the requirements of these Specifications.
        9. Identify access to equipment selected by the Owner/CxA. Demonstrate that access is sufficient to perform required maintenance.
        10. Demonstrate that required trend graphs and trend logs are set up per the requirements. Provide a sample of the data archive.  Indicate the file names and locations.
      9. IAS Demonstration shall be completed and approved prior to Substantial Completion.
      10. Any tests successfully completed during the demonstration will be recorded as passed for the functional performance testing and will not have to be retested. Failed testes shall result in the issue or problem being corrected by the contractor and then re-tested or re-demonstrated to the Owner/CxA.

    • IAS ACCEPTANCE PERIOD and procedure

      1. After approval of the IAS Demonstration and prior to Contract Close out the Acceptance Period shall commence. The Acceptance Period shall not begin until all HVAC systems are in operation and equipment has been accepted, and all required cleaning and lubrication has been performed. completed (i.e., filters changed, piping flushed, strainers cleaned, and the like), and TAB report has been submitted and approved.
      2. Operational Test: At the beginning of the Acceptance Phase, the system shall operate properly for two (2) weeks without malfunction, without alarm caused by control action or device failure, and with smooth and stable control of systems and equipment in conformance with these Specifications.  At the end of the two weeks, Contractor shall forward the trend logs to the Owner/CxA for review.  Owner/CxA shall determine if the system is ready for functional performance testing and document any problems requiring Contractor’s action.
        • If the systems are not ready for functional performance testing, Contractor shall correct problems and provide notification to the Owner/CxA that all problems have been corrected. The Acceptance Period shall be restarted at a mutually scheduled time for an additional (1) one-week period.
        • This process shall be repeated until Owner/CxA issues notice that the IAS is ready for functional performance testing to be conducted by the Owner/CxA.
      3. During the Acceptance Period, the Contractor shall maintain an electronic log of all alarms generated by the IAS. For each alarm received, Contractor shall diagnose the cause of the alarm, and shall list on the log for each alarm, the diagnosed cause of the alarm, and the corrective action taken.  If in the Contractor’s opinion, the cause of the alarm is not the responsibility of the Contractor, Contractor shall immediately notify the Owner/CxA.
      4. Following the acceptance phase and at the Owner’s option the Owner/CxA will functionally test and or commission the system. These tests will include a detailed review of the performance and operation of the GUI as well as a functional test of the equipment and the sequences associated with the equipment. Any issues determined by the Owner/CxA will be delivered to the contractor for correction.
      5. Following the Owner’s/CxA approval of the acceptance period and the following the successful completion of the functional test performed by the Owner/CxA the system will be declared substantially complete. The Owner will issue a letter to the contractor stating that the system is substantially complete. The date of this letter shall start the warrantee period. In the event that the Owner fails to issue this letter the contractor shall contact the Owner directly requesting the acceptance letter.
      6. After substantial completion is grated the following will be required before the system is granted finial acceptance by the Owner.
        • The contractor shall deliver the following documents or services
          • Training onsite and the scheduling of offsite training
          • The turnover of all user names, passwords, software, GUI and DDC databases, license files, and application programming tool(s) to the Owner.
          • Operational and Maintenance Manuals
          • As-built documentations
          • Applicable software updates.
          • Receive Opposite Season acceptance period approval

    • Trend Logs

      • Contractor shall configure and analyze all trends required under Section 25 15 00.

    • TREND Graphs

      • Trend graphs as specified in Section 25 15 00 shall generally be used during the Acceptance Phase to facilitate and document testing. Prepare controller and workstation software to display graphical format trends during the Acceptance Period.  Trend graphs shall demonstrate compliance with Contract Documents.
      • Each graph shall be clearly labeled with HVAC subsystem title, date, and times.

    • SOFTWARE OPTIMIZATION ASSISTANCE

      • The Contractor shall provide the services of an IAS Technician as specified above at the Project Site to be at the disposal of the Owner/CxA. The purpose of this requirement is to make changes, enhancements and additions to control methods, sequence of operation, and/or workstation graphics that have been identified by the Owner/CxA during the construction and commissioning of the Project and that are beyond the specified Contract Document requirements.  The cost for this service shall be included with the bid. Requests for assistance shall be for contiguous or non-contiguous 8-hour days, unless otherwise mutually agreed upon by Contractor and Owner/CxA. The Owner/CxA shall notify Contractor two (2) days in advance of each day of requested assistance.  Refer to Part One of this Section for additional requirements.
      • The IAS Technician provided shall be thoroughly trained in the programming and operation of the controller and workstation software. If the IAS Technician provided cannot perform every software task requested by the Owner/CxA in a timely fashion, Contractor shall provide additional qualified personnel at the Project Site as requested by the Owner/CxA, to meet the total specified requirement [per building] on-Site.
      • Refer to section 25 70 00, training requirements for additional details pertaining to software optimization assistance.
      • The software optimization includes working with the Owner/CxA to review and modify the look, feel, performance, navigation, features, and tools associated with graphical user interface. The contractor shall make the corrections as directed by the Owner/CxA. The Owner/CxA shall be the final authority on the acceptance of the graphical user interface.

    • Warranty Phase IAS Opposite Season Trending and Testing

      • Trending: Throughout the Warranty Phase, trend logs shall be maintained.  Contractor shall forward archive trend logs to the Owner/CxA for review upon Owner/CxA request.  Owner/CxA will review these and notify Contractor of any warranty work required.
      • Opposite Season Testing: Within twelve (12) months of Substantial Completion, Contractor shall schedule and conduct with Owner/CxA, Opposite Season functional performance testing. IAS Provider shall participate in this testing and remedy any deficiencies identified. Opposite season functional performance testing shall adhere to all of the requirements listed above.

Leave a Comment

error: Content is Protected.