Skip to main content
DataCenterGuidelines.com
All specifications

Engineering Specification Template

Chilled Water Pump VFD Specification

A vendor-neutral procurement and design specification template for variable frequency drives serving chilled-water pumps in data center plants. Adapt every clause to the project hydraulic design, sequence of operations, applicable codes and Owner requirements before issuing contract documents. This template does not replace the engineer of record.

Complements the general Data Center HVAC VFD Specification. For design context see Variable Frequency Drives in Data Center Cooling Systems and Chilled Water System Architecture.

Download .docxSoon

DCG-SPEC-VFD-CHWP-001

Variable Frequency Drives for Chilled-Water Pump Applications in Data Centers

Rev. B — Engineering Specification Template

1. Scope and Use of This Template

  1. 1.1This document is an Engineering Specification Template for low-voltage variable frequency drives (VFDs) serving chilled-water pumps in data center cooling plants. It is intended as a starting point for project specifications used by MEP consultants, data center designers, EPC contractors, panel builders, controls integrators and commissioning teams.
  2. 1.2This template is not a substitute for project engineering. The engineer of record shall adapt clauses to the approved basis of design, hydraulic design, sequence of operations (SOO), applicable codes and the Owner’s Project Requirements before issuing contract documents.
  3. 1.3Requirements describe required performance and functionality. Manufacturer-specific features may be accepted where they meet or exceed the intent; proprietary terminology shall not be required unless it is an industry-standard term.
  4. 1.4Values, setpoints, protocols, enclosure ratings and failure responses marked [PROJECT] shall be completed by the project engineer. Do not treat blank schedule fields as implied defaults.

2. Application

  1. 2.1Drives covered by this specification serve chilled-water pumping applications, including primary chilled-water pumps, secondary chilled-water pumps and pumps in variable-primary-flow (VPF) plants where scheduled.
  2. 2.2Condenser-water pumps, CRAH/AHU fans, cooling-tower fans and dry-cooler fans are outside the scope of this application-specific template unless expressly scheduled under an equivalent drive specification.
  3. 2.3The drive application shall be coordinated with plant hydraulics, chiller minimum-flow constraints, valve schedules, differential-pressure (DP) sensor locations, pump curves and the approved SOO. Related engineering context is provided in the site guides for VFD design, chilled-water architecture and cooling control strategies.
  4. 2.4Each critical chilled-water pump identified on the mechanical schedules shall be served by a dedicated VFD unless the engineer of record documents an alternative arrangement and its failure-domain consequences.

3. Codes and Standards

  1. 3.1Drives shall be designed, manufactured and tested as adjustable-speed power drive systems consistent with the IEC 61800 series. Electrical safety requirements shall align with IEC 61800-5-1 or the national equivalent accepted by the Authority Having Jurisdiction (AHJ), such as UL 61800-5-1 where applicable.
  2. 3.2Electromagnetic compatibility (EMC) of the power drive system (PDS) shall be addressed under IEC 61800-3 (verify current edition for the project). The Project Data Sheet shall state both (a) the intended IEC 61800-3 installation environment (first environment or second environment) and (b) the applicable PDS category (C1, C2, C3 or C4). Installation environment and PDS category are related but not interchangeable terms; do not treat them as synonyms.
  3. 3.3Facility-level harmonic performance shall be evaluated using IEEE Std 519 (verify project edition; commonly IEEE 519-2022) at the point of common coupling (PCC) defined in the project electrical design criteria. IEEE 519 limits apply to the installation at the PCC and are not a substitute for individual-equipment certification. See Section 10.
  4. 3.4Where BACnet is specified, implementations shall be consistent with ANSI/ASHRAE Standard 135 (current project edition). Where Modbus is specified, the register map and media (RTU/TCP) shall be defined in the controls submittals.
  5. 3.5Installation, conductors, grounding/earthing, disconnecting means and motor protection shall comply with the electrical code adopted by the AHJ and with project electrical specifications.
  6. 3.6Citation of a standard in this template identifies the framework to be applied. It does not reproduce standard text and does not invent mandatory numerical limits beyond those completed in the Project Data Sheet or required by the AHJ.

4. Submittals

  1. 4.1Product data: catalog cuts identifying model, frame, continuous current rating, overload rating for the selected duty, enclosure rating, ambient rating / derating curves, line-side impedance (DC choke or equivalent), control I/O, and EMC filter package associated with the claimed IEC 61800-3 PDS category.
  2. 4.2Dimensional drawings, mounting details, heat-rejection data and clearances required for the installed ambient.
  3. 4.3Wiring diagrams showing power, control, safety and fieldbus / hardwired I/O connections, including any external 24 V DC control-power supply.
  4. 4.4Harmonic performance data for the proposed drive configuration at representative load points (manufacturer data). State clearly whether data are for the drive alone or for a filter/mitigation package.
  5. 4.5EMC declaration and installation guidance stating the claimed IEC 61800-3 installation environment and PDS category (C1–C4), including maximum motor cable length for the proposed filter and switching configuration.
  6. 4.6Short-circuit / fault-current suitability data for the proposed drive assembly (drive, disconnects, protective devices, and bypass components where applicable), including manufacturer-approved protective-device combinations for the required withstand or short-circuit current rating at the point of installation. Express ratings using terminology appropriate to the project’s regulatory framework (for example assembly short-circuit withstand under IEC practice, or SCCR under UL/NFPA practice).
  7. 4.7Communication conformance: BACnet Protocol Implementation Conformance Statement (PICS) and/or Modbus register map, as applicable to the scheduled protocol(s). Where hardwired or analog control is used, provide I/O schedules and signal scaling.
  8. 4.8Recommended motor cable type, screen termination method, and any required output reactor, dV/dt filter or sine-wave filter for the scheduled cable lengths.
  9. 4.9Factory test certificates or routine test summary for each drive serial number, and a draft parameter list reflecting the Project Data Sheet and SOO.

5. Construction and Electrical Ratings

  1. 5.1Drives shall be a standard catalog product of a manufacturer with demonstrated HVAC / pump application experience, local technical support and spare-parts availability for the design life stated by the Owner.
  2. 5.2Drives shall be rated for variable-torque (centrifugal pump) duty. Continuous output current shall be not less than the motor full-load current stated in the Project Data Sheet, after application of any manufacturer ambient, altitude or switching-frequency derating for the installed condition.
  3. 5.3Overload capability shall meet or exceed the manufacturer’s published HVAC / variable-torque overload rating for the selected frame. If the project requires a stated minimum overload (for example a percentage of rated current for a defined time), enter that requirement in the Project Data Sheet; do not assume a universal percentage.
  4. 5.4Drives shall be suitable for the nominal supply voltage and frequency at the point of installation. Allowable supply voltage variation shall be not less than the manufacturer’s published continuous operating range and shall be coordinated with utility and generator voltage schedules.
  5. 5.5Each drive shall include integrated line-side impedance suitable for HVAC pump applications (DC link choke or equivalent documented harmonic-reduction measure) unless an alternate mitigation package is approved through the project harmonic study.
  6. 5.6Where scheduled, drives shall accept an external 24 V DC control-power input so that the control board, keypad and fieldbus communications can remain operational when mains power to the power section is removed.

6. Motor Compatibility

  1. 6.1Motors served by these drives shall be suitable for inverter duty, with insulation systems compatible with the drive’s output voltage stress for the scheduled cable length and any output filtering.
  2. 6.2Motor nameplate data (voltage, frequency, FLA, power, poles, service factor, insulation class) shall be entered into the drive during commissioning and recorded in the O&M documentation.
  3. 6.3Where the motor includes winding-temperature sensors (for example PTC thermistors, other thermistors, RTDs or equivalent devices), the Project Data Sheet shall state whether temperature monitoring and trip/alarm functions are performed by the VFD, by a motor protection relay, or by another control system. Overtemperature alarm and trip behavior shall be coordinated with the SOO and BMS. This specification does not mandate a single sensor technology.
  4. 6.4Where bearing-current risk is identified by motor size, cable length, installation practice or manufacturer guidance, provide shaft grounding, insulated bearings or other mitigation as scheduled by the electrical / mechanical designers. Mitigation shall be coordinated with the motor supplier.
  5. 6.5Maximum motor cable length shall not exceed the drive manufacturer’s published limit for the installed EMC filter, switching frequency and any output accessories. Where limits are exceeded, provide approved output reactors or filters and revise the EMC installation method statement.

7. Pump Application Requirements

  1. 7.1Drive configuration shall support the pumping arrangement indicated on the mechanical drawings: constant primary / variable secondary, variable primary flow, or other arrangement approved in the basis of design.
  2. 7.2Speed control shall be coordinated with the hydraulic design so that pump operation remains on a safe portion of the pump curve. Dead-head operation (pump running against a closed discharge path without an engineered recirculation or minimum-flow path) shall be prevented by the SOO, valve interlocks and/or drive permissive logic as designed by the engineer of record.
  3. 7.3Minimum speed shall be set only after coordination with: pump manufacturer minimum continuous stable flow recommendations; system minimum flow requirements; chiller evaporator minimum flow limits (especially VPF); and any bypass or decoupler controls. Enter the approved minimum and maximum speeds in the Project Data Sheet. Do not adopt a generic percentage without hydraulic justification.
  4. 7.4Acceleration and deceleration ramps shall limit hydraulic transients (including water-hammer risk where rapid valve or speed changes are possible). Ramp times shall be stated in the Project Data Sheet or SOO and verified during commissioning against observed system response.
  5. 7.5For secondary or VPF distribution pumps under differential-pressure control, the DP setpoint, sensor location and sensor range shall be as shown on the controls drawings. Local PID capability in the drive may be used where scheduled; otherwise the plant controller shall provide the speed reference.
  6. 7.6Where multiple pumps operate in a parallel group, the SOO shall define staging, lead/lag selection, duty rotation and whether pumps run together at reduced speed. Drive features that assist multi-pump staging may be used if they implement the approved SOO; they shall not redefine the SOO.
  7. 7.7Pump and VFD failure responses for N+1 (or better) pump groups shall start the standby machine and adjust speed/staging per the SOO. Shared-drive arrangements that place multiple redundant pumps on one drive are not acceptable for critical chilled-water service unless specifically engineered and accepted in writing by the engineer of record.

8. Enclosure and Environmental Requirements

  1. 8.1Enclosure rating shall be as stated in the Project Data Sheet (examples commonly used: IP20 / UL Type 1 for installation inside suitable panels or electrical rooms; higher ingress ratings for stand-alone plant-room mounting). Select the rating for the actual installed location.
  2. 8.2Continuous ambient temperature capability without derating shall meet the Project Data Sheet. Where the installed ambient or altitude exceeds the manufacturer’s published continuous rating, apply published derating or oversize the drive and document the selection in the submittal.
  3. 8.3Provide conformal coating or environmental hardening where the Project Data Sheet identifies corrosive, dusty or high-humidity conditions, consistent with the manufacturer’s published climatic / chemical classifications (for example IEC 60721 guidance as applied by the manufacturer). These installation climatic conditions are distinct from the IEC 61800-3 EMC installation environment and PDS category stated in Sections 3 and 11.
  4. 8.4Cooling air paths shall remain clear per manufacturer instructions. Panel builders shall account for drive heat rejection in enclosure thermal design.

9. Input and Output Protection

  1. 9.1Provide input protection (fuses or circuit breaker) sized and coordinated per the drive manufacturer’s recommendations and the project electrical specifications.
  2. 9.2Drives shall provide electronic motor overload protection meeting the electrical code and project requirements, together with protection against output short circuit, output-side motor-circuit earth-fault / ground-fault conditions, overvoltage, undervoltage, drive overtemperature and input phase loss, as offered in the manufacturer’s standard HVAC product. Output earth-fault / ground-fault protection addressed here is protection associated with the drive’s motor circuit and shall not be confused with upstream facility ground-fault protection or ground-fault protection of equipment required elsewhere by the electrical design.
  3. 9.3The VFD assembly — including the drive, disconnects, protective devices, bypass components where applicable, and associated panel equipment forming the supplied assembly — shall be suitable for the available short-circuit current at the point of installation. The assembly short-circuit withstand capability or short-circuit current rating (SCCR), expressed using terminology appropriate to the project’s IEC-based or UL/NFPA-based regulatory framework, shall be not less than the calculated available fault current stated in the Project Data Sheet. Manufacturer-approved protective-device combinations used to achieve that rating shall be documented in the submittal. Do not apply SCCR terminology as a universal label outside the regulatory context in which it is defined.
  4. 9.4Output contactors, if used, shall be applied only in accordance with manufacturer guidance (including any required sequencing relative to drive enable). Do not interrupt motor cables in a manner that leaves the drive output energized into an open contactor without an approved scheme.
  5. 9.5Safe isolation for maintenance shall include a lockable disconnecting means in the power circuit to each drive/motor combination as required by code and the project electrical specification. Label equipment for pump tag / drive tag correlation.

10. Harmonics and Power Quality

  1. 10.1Distinguish drive input harmonic performance from facility compliance. Manufacturer harmonic data for an individual drive (or drive plus mitigation package) shall be submitted for information and for use in the project harmonic study. Submission of drive data alone does not constitute IEEE 519 compliance of the facility.
  2. 10.2The project shall define the PCC and shall require a harmonic evaluation of the installation covering utility-fed and generator-fed operating modes, including representative chilled-water pump loading. Mitigation (additional line impedance, passive filters, active filters, multi-pulse or active-front-end configurations, or other engineer-approved measures) shall be provided where the study shows it is required to meet the project’s adopted IEEE 519 criteria at the PCC.
  3. 10.3Do not write contract language that states “the drive shall comply with IEEE 519” as if an individual product can guarantee PCC compliance. Where the project elects to place equipment-level harmonic targets in the Project Data Sheet, state them explicitly as project criteria and still require system evaluation at the PCC.
  4. 10.4Drives shall operate without damage or nuisance tripping on the standby generator supply, including during transfer events, when installed and configured per the approved electrical design and restart sequence.

11. EMC and Motor Cable Requirements

  1. 11.1Provide an EMC filter and installation package appropriate to the IEC 61800-3 installation environment and PDS category (C1–C4) stated in the Project Data Sheet. Install the drive and motor cables per the manufacturer’s EMC installation instructions for that claimed category.
  2. 11.2Use screened (shielded) motor cables with 360-degree screen termination at the drive and motor ends unless the manufacturer’s approved method for the claimed category states otherwise and is accepted by the engineer of record.
  3. 11.3Separate power, motor and control/sensor wiring per manufacturer and controls specifications. Sensor and communication cables shall be routed to minimize coupling from PWM motor circuits.
  4. 11.4Bearing-current mitigation, where scheduled, shall be installed and verified (continuity of grounding/earthing path, correct ring/brush installation, insulated bearing orientation as applicable) before continuous operation.

12. Control Modes and Local Operation

  1. 12.1Drives shall provide Hand / Off / Auto (or equivalent) local control via a door- or drive-mounted keypad or HOA station as scheduled. Hand mode shall allow local start/stop and local speed adjustment within configured min/max limits. Auto mode shall follow the automation system, hardwired commands or local PID as scheduled.
  2. 12.2Project control interfaces may include network communications (BACnet MS/TP, BACnet/IP, Modbus RTU, Modbus TCP), analog speed or setpoint references (4–20 mA, 0–10 V), hardwired digital I/O, or combinations of the above, as stated in the Project Data Sheet. The specification is not limited to network-only control.
  3. 12.3Where analog speed or process references are used, signal scaling, engineering units and fail detection shall match the controls drawings. Where the product supports detection of loss of the analog speed-reference signal, such loss shall invoke the [PROJECT] analog reference-loss fallback defined in the Project Data Sheet and SOO (which may differ from network-loss fallback).
  4. 12.4Drives shall include an internal PID controller suitable for closed-loop control of differential pressure, flow or other analog process variable where local PID is scheduled. PID scaling, setpoint source, feedback source and output limits shall match the controls drawings.
  5. 12.5Where required by the SOO, the control architecture shall distinguish among: (a) run command; (b) run permissive / interlock; (c) drive running status; and (d) pump proof-of-operation. Pump proof may be derived from project-approved evidence such as differential pressure, flow, motor current/load, auxiliary contact or other engineered signal. A BMS or controller “Run” command alone shall not be treated as proof that the pump is operating. Loss of a required permissive shall result in the project-defined stop or fallback behavior and alarm indication.
  6. 12.6Skip frequency (critical speed avoidance) bands shall be available where mechanical resonance is identified during commissioning.
  7. 12.7Provide at least two independently configurable acceleration and deceleration ramps, assignable as required by the SOO (for example normal operation versus emergency or maintenance modes).
  8. 12.8Automatic restart after power interruption shall be configurable when the run command is present and required permissives are satisfied, including a restart delay to support staggered restart of pump groups. Flying restart / speed search shall be configurable where appropriate for the pump/motor inertia and hydraulic system; enable only when accepted in the SOO and verified not to create unacceptable hydraulic transients.
  9. 12.9Emergency / plant override inputs, where required by the project, shall force a predefined speed or stop state as defined in the SOO and shall bypass normal network, analog and PID commands by design. Fire/life-safety override functions shall be provided only where specifically required by the project life-safety design; they are not a universal chilled-water-pump VFD requirement.

13. Pump Staging, Lead/Lag and Duty Rotation

  1. 13.1Where two or more chilled-water pumps serve a common header, staging, lead/lag selection and duty rotation shall follow the approved SOO. Drive-resident multi-pump macros may be used only if they implement that SOO without contradiction.
  2. 13.2The SOO shall define whether capacity is met by operating fewer pumps near higher speed or more pumps at reduced speed, subject to hydraulic efficiency, minimum speed and equipment limits.
  3. 13.3On pump failure, loss of pump proof-of-operation, or VFD fault, the standby pump initiation logic, speed recovery and any temporary pressure undershoot/overshoot limits shall be as defined in the SOO and demonstrated during commissioning.
  4. 13.4Duty rotation intervals and equal-runtime objectives, if used, shall not defeat N+1 capacity during maintenance or failure events.

14. Communications and BMS Integration

  1. 14.1Where network control or monitoring is scheduled, communication media and protocol(s) shall be as stated in the Project Data Sheet (for example BACnet MS/TP, BACnet/IP, Modbus RTU, Modbus TCP), used alone or in combination with hardwired digital I/O and analog interfaces described in Section 12. Prefer native drive communications without an external gateway where scheduled; gateways may be accepted only if listed and approved.
  2. 14.2BACnet devices shall provide a PICS with the submittal. Device profile shall meet the BAS specification (commonly B-ASC minimum unless a higher profile is scheduled).
  3. 14.3A configurable communication-loss watchdog shall be provided for networked control. On watchdog timeout, the drive shall execute the network-loss fallback defined in Section 16 and the Project Data Sheet.
  4. 14.4Point lists shall distinguish mandatory control points, mandatory monitoring points and optional / project-specific points as follows. Where control is primarily hardwired or analog, apply the equivalent hardwired signals and retain monitoring points via the scheduled network interface where provided.
  5. 14.5MANDATORY CONTROL POINTS (as a minimum, where the automation system commands the drive): Start/Stop (or Run) command; Speed reference; Fault reset (where remote reset is permitted by the SOO); Hand/Auto or local/remote status feedback used by the sequence.
  6. 14.6MANDATORY MONITORING POINTS (as a minimum): Run status (drive running); Speed feedback (or output frequency); Output current; Output power; Fault status; Fault code; Communication status / watchdog healthy (where networked); Pump proof-of-operation status where scheduled; Drive temperature where available from the product; Energy (kWh) where available from the product.
  7. 14.7OPTIONAL / PROJECT-SPECIFIC POINTS (provide where scheduled): PID setpoint; PID feedback; DP or flow process variable; DC bus voltage; analog outputs mirroring speed or load; motor temperature alarm/trip status; custom alarms; pump seal or vibration inputs if wired through the drive; any additional points required by the Owner’s BMS standards.
  8. 14.8Point naming, engineering units, write authority and alarm class shall follow the project BMS standards and be published as a controlled point list.

15. Network and Cybersecurity

  1. 15.1Ethernet-connected VFDs shall comply with the Owner’s network segmentation and OT/ICS cybersecurity architecture for the facility.
  2. 15.2Where the product supports configuration, only the communication services and protocols required for the project shall be enabled; unused services shall be disabled.
  3. 15.3Where authentication is supported, default credentials shall be changed before turnover. Write and control authority shall be limited to authorized controllers or systems defined by the Owner.
  4. 15.4Firmware and software versions shall be documented at commissioning and included in the O&M package.
  5. 15.5Remote Internet or cloud connectivity shall not be enabled unless expressly approved by the Owner in writing.
  6. 15.6Cybersecurity settings shall not prevent required local Hand / Off / Auto operation or other SOO-required local control during loss of network connectivity.
  7. 15.7IEC 62443 certification or other formal cybersecurity conformity is not universally mandatory under this template. Where the Owner requires IEC 62443 alignment or other cybersecurity standards, state those requirements in the Project Data Sheet; more specific requirements shall defer to the Owner’s OT/ICS cybersecurity standard.

16. Failure Behavior and Redundancy Philosophy

  1. 16.1Critical chilled-water pumps shall use one VFD per pump so that a single drive failure removes only the associated pump from service. Avoid shared drive failure domains across redundant pumps.
  2. 16.2Redundant control power for drive electronics and for upstream controllers shall be provided where the basis of design requires continued visibility or local control during mechanical power loss. Complete the control-power arrangement in the Project Data Sheet.
  3. 16.3Network failure: on loss of BMS/plant-controller communications, the drive shall execute the [PROJECT] network-loss fallback (examples to be selected by the designer: maintain last speed; transfer to local PID if sensors remain valid; ramp to a predefined safe speed; stop). The selected behavior shall be recorded in the SOO and commissioning records. Do not leave factory defaults unverified.
  4. 16.4Analog reference-loss failure: where analog speed or process reference is used and loss detection is supported, the drive shall execute the [PROJECT] analog reference-loss fallback. This behavior shall be defined separately from network-loss fallback where both interfaces are present.
  5. 16.5Sensor failure: when local or remote PID depends on a DP/flow/temperature sensor, sensor-failure behavior shall be [PROJECT] (examples: hold last output; go to predefined speed; stop; transfer control to alternate sensor or plant controller). Coordinate with valve and chiller minimum-flow protections.
  6. 16.6VFD fault: the drive shall trip safely, annunciate locally and to the BMS, and the plant sequence shall start standby capacity per the SOO. Remote fault reset shall be permitted only where safe and scheduled.
  7. 16.7Pump fault or loss of pump proof-of-operation (external overload, seal failure, low suction pressure, missing proof signal, or other hardwired trip): shall remove the run permissive or force stop as designed, and shall initiate standby logic per the SOO. Distinguish pump/process proof failure from drive fault status in alarms where practicable.
  8. 16.8Power restoration: after utility or generator transfer and restoration of power, drives shall restart only according to the approved staggered-restart plan and only when required permissives are present. Restart delays shall be set per pump group and coordinated with generator step-load capability and thermal ride-through analysis.
  9. 16.9Manual override: Hand mode and any emergency / plant override inputs shall be tested and shall not be defeated by network commands. Authorization and indication of override shall be visible to operations.
  10. 16.10Where the correct response depends on plant sequencing, this specification requires the designer to define the behavior in the SOO and Project Data Sheet rather than imposing one universal fallback.

17. Bypass Philosophy and Maintenance Isolation

  1. 17.1Across-the-line bypass is not automatically required. The engineer of record shall state Bypass Required: Yes/No in the Project Data Sheet after evaluating redundancy, DOL starting current, valve positions during bypass and whether full-speed operation is hydraulically and electrically acceptable.
  2. 17.2Where bypass is provided, interlocking shall prevent energizing the motor through bypass while the drive output is active, and shall prevent bypass start into closed valves or unsafe hydraulic conditions. Bypass shall be labeled and trained as a deliberate operating mode. Bypass components included in the assembly shall be included in the short-circuit / fault-current suitability evaluation of Section 9.
  3. 17.3Where genuine N+1 (or better) pump and drive redundancy exists, document the rationale if bypass is omitted in favor of redundant capacity.
  4. 17.4Maintenance isolation: each drive/motor circuit shall be lockable and tagged. Spare drives or spare power sections, if required by the Owner, shall be listed in the Project Data Sheet (quantity, storage location, firmware compatibility).

18. Factory Testing

  1. 18.1Each drive shall receive the manufacturer’s standard routine factory tests. Provide serial-number traceable documentation with shipment.
  2. 18.2Where the project specifies witness testing or special type tests, list them in the Project Data Sheet.

19. Site Commissioning and Functional Testing

  1. 19.1Commissioning shall be performed by qualified personnel (supplier, manufacturer-certified technician and/or commissioning authority as required by the contract) and coordinated with the mechanical, electrical and controls trades.
  2. 19.2Field verification shall include, as a minimum: motor nameplate data entry; correct rotation; maximum and minimum speed limits; acceleration and deceleration ramps; local PID behavior (if used); DP or process sensor scaling and input; analog and/or network control interfaces as scheduled; BMS point mapping; Hand/Off/Auto operation; run command versus permissive versus pump proof-of-operation; alarm and fault history access; motor temperature protection wiring where scheduled; and documentation of firmware version and cybersecurity settings applicable to Section 15.
  3. 19.3Failure and recovery demonstrations shall include, as defined in the commissioning plan and SOO: communication-loss response; analog reference-loss response (where applicable); sensor-failure response; pump-failure / proof-of-operation failure response; VFD-fault response; power interruption and restoration; automatic restart; staggered restart across the pump group; lead/lag and duty rotation; redundant pump takeover; and verification that local control remains available during network loss.
  4. 19.4Tests shall demonstrate the behaviors required by the approved SOO, pump schedule, motor data, hydraulic design and commissioning plan. This template does not invent universal acceptance numeric values; measured results shall be compared to those project documents.
  5. 19.5Where the harmonic study requires it, record input current distortion at representative operating points during commissioning or IST.
  6. 19.6Deliver a complete electronic parameter backup for every drive and include it in the O&M package.

20. Documentation and Warranty

  1. 20.1Provide as-built wiring diagrams, final parameter lists, point lists, PICS/register maps, harmonic and EMC submittal data, short-circuit / protective-device combination data, cybersecurity configuration record, and commissioning records.
  2. 20.2Warranty and technical support terms shall be as stated in the contract; as a minimum identify warranty duration, response expectations and spare-parts lead times for the purchased frames.
  3. 20.3Training shall cover local keypad operation, HOA, fault reset policy, bypass (if provided) and BMS / hardwired interface overview for operations staff.

21. Project Data Sheet and Design Decisions

  1. 21.1Complete all fields below. Items marked [PROJECT] are design decisions for the engineer of record; blank fields are not defaults.
  2. 21.2A. ELECTRICAL
  3. 21.3[PROJECT] Motor voltage (V) / frequency (Hz): ________ / ________
  4. 21.4[PROJECT] VFD continuous output current (A) after derating: ________
  5. 21.5[PROJECT] Overload requirement (if any beyond manufacturer VT rating): ________
  6. 21.6[PROJECT] Enclosure / IP or UL Type rating: ________
  7. 21.7[PROJECT] Design ambient (°C) and altitude (m): ________ / ________
  8. 21.8[PROJECT] Available fault current at point of installation; required assembly short-circuit withstand or SCCR (state units and IEC or UL/NFPA basis): ________
  9. 21.9[PROJECT] External 24 V DC control power: Yes/No; source: ________
  10. 21.10B. MOTOR / MECHANICAL
  11. 21.11[PROJECT] Pump tag(s) / service (primary CHW / secondary CHW / VPF / other): ________
  12. 21.12[PROJECT] Motor power / poles / FLA: ________ / ________ / ________
  13. 21.13[PROJECT] Maximum motor cable length (m) and any output filter: ________
  14. 21.14[PROJECT] Bearing-current mitigation: Yes/No / method: ________
  15. 21.15[PROJECT] Motor temperature sensor type (PTC / RTD / other / none) and monitoring location (VFD / motor protection relay / other): ________
  16. 21.16[PROJECT] Minimum speed / Maximum speed: ________ / ________
  17. 21.17[PROJECT] Acceleration / deceleration times: ________ / ________
  18. 21.18C. CONTROLS
  19. 21.19[PROJECT] Control interface: Network / 4–20 mA / 0–10 V / hardwired / combination / other: ________
  20. 21.20[PROJECT] Control mode: BMS speed reference / local DP PID / other: ________
  21. 21.21[PROJECT] DP (or flow) setpoint and sensor tag: ________
  22. 21.22[PROJECT] Pump proof-of-operation method: ________
  23. 21.23[PROJECT] Analog reference-loss fallback (if analog control used): ________
  24. 21.24D. POWER QUALITY / EMC
  25. 21.25[PROJECT] IEC 61800-3 installation environment (first / second): ________
  26. 21.26[PROJECT] IEC 61800-3 PDS category (C1 / C2 / C3 / C4) and required filter/package: ________
  27. 21.27[PROJECT] Harmonic study required: Yes/No; PCC definition: ________
  28. 21.28[PROJECT] Equipment-level harmonic criteria (if any): ________
  29. 21.29E. RESILIENCE AND FAILURE BEHAVIOR
  30. 21.30[PROJECT] Bypass required: Yes/No; rationale: ________
  31. 21.31[PROJECT] Redundancy philosophy (e.g. N+1 dedicated drive per pump): ________
  32. 21.32[PROJECT] Restart philosophy / stagger delays: ________
  33. 21.33[PROJECT] Network-loss fallback: ________
  34. 21.34[PROJECT] Sensor-failure fallback: ________
  35. 21.35F. COMMUNICATIONS / CYBERSECURITY
  36. 21.36[PROJECT] Communication protocol / network segment: ________
  37. 21.37[PROJECT] Owner OT/ICS cybersecurity requirements (including IEC 62443 or other standards if applicable): ________
  38. 21.38G. MAINTENANCE / SUPPORT
  39. 21.39[PROJECT] Spare drive / spare parts requirements: ________
  40. 21.40[PROJECT] Warranty / support requirements beyond contract General Conditions: ________

Engineering Specification Template from DataCenterGuidelines.com. Requirements must be verified against project design criteria, local codes, the approved sequence of operations and the latest manufacturer documentation before use in contract documents. Manufacturer-specific adaptation may be required.

Related guides