New Construction Controls Commissioning — A Practical Playbook for Education Portfolios

New Construction Controls Commissioning — A Practical Playbook for Education Portfolios
Build quality in (don't just close projects)
This comprehensive guide provides higher education facilities directors, project managers, and commissioning professionals with practical strategies to ensure effective controls commissioning in new construction projects. By focusing on quality throughout the process rather than treating commissioning as a closeout activity, institutions can achieve better performing buildings, avoid costly rework, and enable smoother transitions to operations.
www.JacksonControl.com
[email protected]
How to use this guide
This playbook is designed to be both comprehensive and practical, allowing you to either read it cover-to-cover or jump directly to specific sections based on your immediate needs. The document flows from core principles and common challenges to specific implementation guidance and ready-to-use resources.
I've organized the content to support different reading approaches:
Strategic overview: Skim the chapters for a high-level understanding of effective controls commissioning
Tactical implementation: Grab the appendices for copy/paste specifications, checklists, and worksheets you can immediately incorporate into your projects
Problem-solving: Use the detailed tags to quickly locate specific guidance related to challenges you're currently facing
Each section includes specific tags (e.g., #governance, #IT, #training) to facilitate quick searches and navigation. These tags create a consistent index throughout the document, making it easier to find related content across different sections.
Pro tip: Consider sharing relevant sections with project stakeholders at specific milestones to establish shared expectations and align understanding of roles and responsibilities.
This guide reflects collective wisdom gathered from multiple K-12 and higher education institutions facing similar challenges with controls commissioning. The recommendations are vendor-neutral and designed to work across diverse campus environments and building automation system platforms.
www.JacksonControl.com
[email protected]
Table Of Contents
Table of Contents
Reframing Commissioning: Quality vs. Project Closure
Engage Earlier, On Purpose
Early IT Integration (Reality > Theory)
The Fragility of New-Build Controls
Top 10 Failure Modes in NCCx (Controls-Centric)
Procurement & Accountability
Testing That Proves Performance
Coordination Gates: TAB — Controls — IT
Plan Seasonal & Integrated Testing Upfront
Campus Realities to Design Around
From Lessons to Standards (Institutionalizing What Works)
Appendices
A. IT Pre-Flight Packet (Owner Acceptance Gate)
B. Commissionable Controls Submittal Checklist
C. TAB–Controls Handshake SOP
D. Acceptance-Criteria Matrix (Testable OPR)
E. Spec Clause Library (Drop-In, Vendor-Neutral)
F. Workshop Worksheet (5-Minute Team Exercise)
G. Glossary of Terms and Accronyms
H. Helpful Links
www.JacksonControl.com
[email protected]
1. Reframing Commissioning: Quality vs. Project Closure
#governance #roles #quality #closeout
The problem we see
Across multiple higher education campuses, we've observed a troubling trend: commissioning has gradually shifted from functioning as the owner's subject matter expert role into merely a construction closeout barrier. The consequences of this shift are significant - while paperwork may technically "pass" requirements, the actual sequences of operation and systems integrations often remain unproven in real-world conditions.
This fundamental misalignment creates several downstream issues:
Controls commissioning becomes a checkbox exercise rather than a quality assurance process
Systems appear functional during testing but fail to perform as intended during actual operation
Operational staff inherit systems they don't fully understand and cannot effectively maintain
Energy performance and occupant comfort suffer despite significant investment in advanced control systems
What good looks like
Effective new construction controls commissioning (NCCx) takes a fundamentally different approach by:
Participating early in the pre-design phase to shape outcomes
Establishing and maintaining clear Owner's Project Requirements (OPR) and Basis of Design (BOD) documents
Performing thorough design and submittal reviews with trackable resolution of issues
Verifying actual performance through comprehensive functional testing with measurable criteria
Transferring capability to operations staff through effective training and usable systems documentation
This approach aligns perfectly with the process timeline in your planning deck, emphasizing quality integration throughout rather relevant than inspection at the end.
www.JacksonControl.com
[email protected]
1. Reframing Commissioning: Implementation Strategy
#governance #roles #quality #closeout
1
Focus on Verifiable Performance
Redefine success criteria to prioritize actual system performance over mere documentation. This ensures projects are evaluated on demonstrated functionality rather than just completion of paperwork.
2
Empower Your Cx Provider
Position your Commissioning (Cx) provider as a true advocate for the owner. Contractually ensure their early involvement and continuous engagement from pre-design through seasonal testing.
3
Measure What Matters
Establish clear, objective performance criteria within your Owner's Project Requirements (OPR). These criteria should be measurable through testing and trend data analysis, fostering accountability for actual system performance.
www.JacksonControl.com
[email protected]
2. Engage Earlier, On Purpose
#pre-design #OPR #BOD #designreviews
What we heard
One of the most consistent challenges reported across institutions is the late engagement of commissioning resources. In many cases, commissioning providers are being assigned at 90–100% design completion, which is far too late to influence critical decisions or prevent costly rework. Even more concerning, teams with internal commissioning capabilities still struggle to secure invitations to participate before schematic design or design development phases.
This pattern creates several significant problems:
Critical design decisions are made without commissioning input, leading to systems that are inherently difficult to commission effectively
Owner's Project Requirements (OPR) documents lack sufficient detail or measurable acceptance criteria
Design reviews occur too late to incorporate meaningful changes without significant cost impacts
Commissioning becomes reactive rather than proactive, focusing on identifying problems rather than preventing them
Late commissioning engagement is consistently cited as the single most significant factor in commissioning challenges across higher education portfolios. The cost of early engagement is minimal compared to the expense of late-stage changes or post-occupancy remediation.
Root causes of late engagement
Common reasons for delayed commissioning involvement include:
Budgetary constraints and misconceptions about commissioning costs
Traditional procurement processes that separate design and construction phases
Lack of awareness about the value of early commissioning input
Compressed project schedules that prioritize speed over quality
www.JacksonControl.com
[email protected]
2. Engage Earlier, On Purpose: Implementation Strategy
#pre-design #OPR #BOD #designreviews
What to do
1
Pre-Design Engagement
Formally insert commissioning at the pre-design phase to help develop comprehensive OPR documents and validate the Basis of Design. This early involvement establishes clear performance expectations and ensures that design decisions align with operational requirements.
2
Structured Commissioning Plan
Require a formal Commissioning Plan that outlines specific activities, responsibilities, and milestones throughout the project lifecycle. Include explicit requirements for design reviews, submittal reviews, and documentation of issue resolution.
3
Transparent Issue Tracking
Implement a formal issues log that tracks all identified concerns through to resolution, with clear documentation of closure criteria. This creates accountability and ensures that problems don't slip through the cracks.
4
Forward-Looking Planning
Incorporate plans for seasonal testing and comprehensive training from day one of the project, ensuring that these critical activities are properly budgeted and scheduled rather than treated as afterthoughts.
www.JacksonControl.com
[email protected]
3. Early IT Integration (Reality > Theory)
#IT #network #ports #VLAN #certificates #BACnetSC
What we heard
A pervasive challenge across campus projects is the exclusion of IT departments from early controls planning conversations. Multiple institutions reported that IT is often bypassed because they're perceived as "slowing things down" with security requirements and approval processes. This avoidance strategy invariably backfires, leading to last-minute scrambles for network ports, whitelist approvals, security certificates, and other critical IT infrastructure elements.
The consequences of this pattern are severe:
Project delays during the critical commissioning and turnover phases
Hurried implementation of network security measures, often with compromises
Emergency change requests overwhelming IT departments
Incomplete or inadequate security configurations that may persist for years
Missed opportunities to implement more secure protocols like BACnet/SC
The increasing convergence of operational technology (OT) and information technology (IT) makes early collaboration between these departments more critical than ever. Modern building automation systems are essentially networked computer systems that require the same security considerations as other enterprise IT assets.
www.JacksonControl.com
[email protected]
3. Early IT Integration (Reality > Theory)
#IT #network #ports #VLAN #certificates #BACnetSC
Make IT a gate (before hardware arrives)
Network Architecture
Develop and obtain formal approval on comprehensive network diagrams showing all control system components, including BACnet/IP routing structures, supervisory controllers, and field controllers.
Port and Protocol Requirements
Create a detailed port/protocol matrix documenting all communications needed for proper system operation, including both internal communications and any external connections (e.g., weather data, remote access).
Network Security Configuration
Establish VLAN assignments, Network Access Control (NAC) policies, and firewall rules appropriate for building control systems while maintaining security requirements.
Time Synch
Define the authoritative time source and synchronization methods to ensure consistent timestamps across all system components, which is critical for accurate trending and alarm management.
Certificate Management
Develop a comprehensive certificate plan addressing how security certificates will be issued, installed, and renewed throughout the life of the system.
BACnet/SC Readiness
Assess and document readiness for implementing BACnet Secure Connect (BACnet/SC) to enhance security while maintaining standard protocol compatibility.
www.JacksonControl.com
[email protected]
3. Early IT Integration: Evidence & Best Practices
#IT #network #ports #VLAN #certificates #BACnetSC
Evidence matters
Beyond IT integration, ensuring that you have sufficient trend data to prove sequence operation is critical. Specify minimum trending requirements during Functional Performance Testing (FPT) to verify that systems are operating as designed. Multiple institutions identified "evidence/trending for FPT" as a common breakdown point in the commissioning process.
Best Practice: Create an IT pre-flight checklist that must be signed off by appropriate IT stakeholders before any control system hardware is ordered or installed. This simple gate can prevent costly delays and rework later in the project.
Implementation tips for successful IT integration
Practical guidance for making IT integration successful includes:
Network Architecture: Develop and obtain formal approval on comprehensive network diagrams showing all control system components, including BACnet/IP routing structures, supervisory controllers, and field controllers.
Port and Protocol Requirements: Create a detailed port/protocol matrix documenting all communications needed for proper system operation, including both internal communications and any external connections (e.g., weather data, remote access).
Network Security Configuration: Establish VLAN assignments, Network Access Control (NAC) policies, and firewall rules appropriate for building control systems while maintaining security requirements.
Time Synchronization: Define the authoritative time source and synchronization methods to ensure consistent timestamps across all system components, which is critical for accurate trending and alarm management.
Certificate Management: Develop a comprehensive certificate plan addressing how security certificates will be issued, installed, and renewed throughout the life of the system.
BACnet/SC Readiness: Assess and document readiness for implementing BACnet Secure Connect (BACnet/SC) to enhance security while maintaining standard protocol compatibility.
www.JacksonControl.com
[email protected]
4. The Fragility of New-Build Controls
#schedule #VE #changes #multitrade #factoryvsfield #IST #turnover
Building automation and control systems in new construction projects are uniquely vulnerable to disruption and failure compared to other building systems. This inherent fragility stems from multiple factors that interact and compound throughout the project lifecycle.
Understanding these fragility factors is essential for developing effective commissioning strategies that can mitigate the associated risks. The complexities of modern building control systems, combined with typical construction project dynamics, create a perfect storm of potential failure points that must be actively managed.
Each of the identified fragility factors represents a specific risk that can be addressed through targeted commissioning activities, careful planning, and strategic checkpoints throughout the project. By recognizing these vulnerabilities early, project teams can implement appropriate countermeasures to ensure successful system implementation.
Schedule Compression
Controls installation and programming are frequently compressed into the final stages of construction, leaving insufficient time for proper testing and troubleshooting.
Value Engineering
Mid-design VE decisions often target controls without considering the full implications for system integration and long-term operational performance.
Late Design Changes
Changes to mechanical or electrical systems late in the design process frequently have unrecognized impacts on controls that aren't properly coordinated.
Multi-Trade Coordination
Controls integration requires coordination across mechanical, electrical, plumbing, fire protection, and IT trades, creating numerous handoff points where communication can break down.
Factory vs. Field Code
Discrepancies between factory-programmed equipment controllers and field-programmed building automation systems create conflicts that can be difficult to diagnose.
Life-Safety Interactions
Integration with fire alarm, smoke control, and other life-safety systems adds complexity and regulatory requirements that demand careful testing and verification.
www.JacksonControl.com
[email protected]
4. The Fragility of New-Build Controls: Mitigation Strategies
#schedule #VE #changes #multitrade #factoryvsfield #IST #turnover
Action Step
Use this list as a risk register for your next project—then push specific counter-measures (gates and sign-offs) into your Commissioning Plan to address each vulnerability. By acknowledging these fragility factors up front, you can develop targeted strategies to mitigate their impact and ensure successful controls implementation.
Specific Mitigation Strategies for Fragility Factors:
Schedule Compression
Build in buffer time and early testing phases
Value Engineering
Require controls impact assessment for all VE decisions
Late Design Changes
Implement change control procedures with controls review
Multi-Trade Coordination
Establish formal handoff protocols and coordination meetings
Factory vs. Field Code
Require code reconciliation and documentation
Life-Safety Interactions
Plan integrated testing with AHJ coordination
Implementing these strategies requires proactive planning, clear communication, and a commitment from all project stakeholders. By addressing each fragility factor with a targeted mitigation strategy, project teams can significantly reduce risks, prevent costly delays, and ensure the successful deployment and operation of building control systems.
Take action today to integrate these best practices into your project workflows, fostering a more resilient and efficient construction process for new-build controls.
www.JacksonControl.com
[email protected]
5. The Top 10 Failure Modes in NCCx (Controls Centric)
#OPR #SOO #submittals #IT #TAB #prefunctional #IST #evidence #graphics #training
Based on extensive experience across multiple higher education institutions, we've identified the most common failure modes in new construction controls commissioning. Understanding these recurring issues can help project teams implement preventive measures to avoid them.
Non-Testable OPR
Owner's Project Requirements lack measurable acceptance criteria, making it impossible to objectively verify whether systems are performing as intended. Requirements like "energy efficient operation" or "comfortable conditions" are too vague to test effectively.
Sequence of Operation Mismatches
Discrepancies between the specified sequence of operation, the submitted control narratives, and the actual implemented code create confusion and performance issues. These mismatches often remain undetected until functional testing.
Incomplete Submittals
Controls submittals frequently lack critical components such as comprehensive points lists, input/output maps, alarm configurations, trending capabilities, or fail to properly match equipment specifications. These gaps make proper review and verification difficult.
Late IT Engagement
Failure to engage IT departments early leads to last-minute scrambles for network ports, VLAN assignments, security certificates, and BACnet/SC implementations, often delaying project completion.
TAB–Controls Miscoordination
Poor coordination between Testing, Adjusting, and Balancing (TAB) and controls contractors results in mismatched setpoints, valve/damper positions, and flow measurements between reports and actual programming.
www.JacksonControl.com
[email protected]
5. The Top 10 Failure Modes in NCCx (Controls-Centric)
#OPR #SOO #submittals #IT #TAB #prefunctional #IST #evidence #graphics #training
Incomplete Pre-functional Verification
Inadequate point-to-point verification and basic instrument checkout during prefunctional testing leads to fundamental issues that stall functional performance testing and compromise system operation.
Unplanned Integrated Systems Testing
Failure to properly plan and coordinate testing of integrated systems, particularly those involving life-safety functions like smoke control, creates last-minute complications and potential regulatory issues.
Evidence Gaps
Insufficient trend data collection and inconsistent naming conventions make it difficult to verify sequence operation and create documentation that supports ongoing maintenance and troubleshooting.
Poor Graphics & Alarm Configuration
Poorly designed user interfaces, inconsistent navigation, and inappropriate alarm priorities/routing make systems difficult to operate effectively after turnover to facilities staff.
Inadequate Training
One-time, event-based training without recorded materials or comprehensive checklists fails to prepare operations staff for ongoing system management, especially when staff turnover occurs.
Additional Critical Failure Modes (Meeting Notes)
Equipment Selection Drift
Deviations from the Basis of Design when selecting equipment, particularly missing options or features, can lead to Frankenstein air handlers and other systems requiring major rework to function properly.
Integration Complexity
Multiple integration pathways between systems create unnecessary complexity that complicates training, troubleshooting, and maintenance. Standardizing on a single integration approach significantly reduces failure points.
Design QA Process Gaps
Failure of consultants to acknowledge and incorporate quality assurance comments often results in repeated failures during system startup. A formal tracking process for design review comments is essential.
www.JacksonControl.com
[email protected]
6. Procurement & Accountability
#prequal #quality #policy #responsibility
Pre-qualify for quality
One of the most impactful strategies discussed in our meetings was the need to shift vendor selection criteria beyond simply seeking the lowest bid. Higher education institutions that have successfully improved their controls commissioning outcomes consistently report implementing more sophisticated pre-qualification processes for controls contractors and commissioning providers.
Effective pre-qualification should focus on demonstrated capabilities in areas that directly impact commissioning success:
Submittal completeness and quality – Review sample submittals from previous projects to assess thoroughness and clarity
Functional Performance Test (FPT) readiness – Evaluate the contractor's standard testing procedures and documentation practices
IT pre-flight maturity – Assess experience with enterprise network integration and security requirements
Staffing continuity – Verify that programming and commissioning staff will remain consistent throughout the project
Training capabilities – Review training materials and methodologies from previous projects
This approach may require modifications to procurement processes but can significantly reduce commissioning challenges and long-term operational issues.
Who owns energy during construction?
A common challenge identified during our discussions was the lack of clear accountability for energy consumption during the construction and commissioning phases. This often results in systems running inefficiently for extended periods, sometimes for months before occupancy, with no clear responsibility for the associated costs.
Recommended approach:
Codify make-ready schedules with specific milestone dates for system activation
Establish baseline expectations for energy performance during pre-occupancy phases
Assign clear accountability for excessive energy use during construction and commissioning
Implement monitoring and reporting requirements to track consumption
Occupied-before-turnover policy
Another recurring challenge is managing situations where spaces become occupied before formal system turnover and acceptance. This creates confusion about responsibility for addressing occupant complaints and can pull building engineers into troubleshooting systems that haven't been properly commissioned.
Recommended policy elements:
Route all occupant complaints directly to the project manager during construction and commissioning phases
Keep building engineers and facilities staff out of the "line of fire" until formal system acceptance
Establish clear criteria for when systems are ready for facilities staff involvement
Document any operational compromises required for early occupancy
www.JacksonControl.com
[email protected]
7. Testing That Proves Performance
#FPT #acceptance #evidence
Build tests to prove sequences
Effective functional performance testing (FPT) requires a fundamental shift in approach from simply observing system behavior to methodically proving that all aspects of the sequence of operation function correctly under various conditions. This means developing test scripts with explicit acceptance criteria defined in terms of measurable points, values, intervals, and durations.
Each test script should:
1
Clearly state the purpose and scope of the test
2
Define specific initial conditions required
3
List step-by-step procedures for the test execution
4
Specify exact expected outcomes with numerical tolerances
5
Include pass/fail criteria for each step and the overall test
6
Identify required trending points, intervals, and durations
7
Document any special tools, access, or assistance needed
Example Acceptance Criteria
Based on the criteria mentioned in your slides, effective acceptance requirements might include:
Supply Air Temperature Control: Maintain SAT within ±2°F of setpoint during normal occupied operation, verified through trend data collected at 15-minute intervals for a minimum of 2 hours
Economizer Operation: Engage when outdoor air temperature is ≤ return air temperature minus 3°F; disable when the differential between outdoor air temperature and return air temperature is ≤ 1°F, verified through trend data showing proper transitions at these thresholds
Demand-Controlled Ventilation: Modulate outdoor air damper to maintain CO₂ levels below 900 ppm during occupied hours, verified through trend data showing damper position responding appropriately to changing CO₂ levels
www.JacksonControl.com
[email protected]
7. Testing That Proves Performance
#FPT #acceptance #evidence
Connect to tools at turnover
Fault Detection & Diagnostics Integration
Several institutions reported success connecting new buildings to Fault Detection and Diagnostics (FDD) platforms at turnover to enhance the acceptance process. This approach provides immediate visibility into system performance and helps identify issues that might not be apparent during standard testing procedures.
Analytics-Enhanced Commissioning
Implementing analytics tools during commissioning allows for more comprehensive verification of sequences through continuous monitoring rather than point-in-time testing. This approach is particularly valuable for complex sequences that respond to varying conditions over time.
Digital Commissioning Workflows
Digital tools that streamline the documentation and verification process can significantly improve the efficiency and effectiveness of commissioning activities. These tools can provide real-time tracking of test completion, issue resolution, and system readiness.
Common Pitfall: Failing to specify the exact trending requirements needed to verify sequence operation is a frequent cause of commissioning delays. Include explicit trending specifications (points, intervals, duration) in your commissioning plan and ensure the controls contractor configures these trends before functional testing begins.
www.JacksonControl.com
[email protected]
8. Coordination Gates: TAB ↔ Controls ↔ IT
#handshake #gates #witness #reports
TAB–Controls Handshake
One of the most critical coordination points in the commissioning process is the interface between Testing, Adjusting, and Balancing (TAB) and controls contractors. This relationship must be carefully managed to ensure that system performance meets design requirements and that both parties are working with consistent information.
Define Authority
Clearly establish who has final authority for setpoints, calibration values, and other shared parameters that affect both TAB and controls operation. Document this authority in the commissioning plan and ensure all parties acknowledge it.
Witness Critical Activities
The commissioning provider should witness both control system start-up procedures and key TAB activities to ensure proper coordination and verify that systems are operating as intended before detailed testing begins.
Establish Acceptance Gates
Treat the accepted TAB report as a formal gate that must be passed before functional performance testing can begin. This ensures that fundamental air and water balancing is complete and accurate before more complex sequence testing occurs.
Field Adjustment Documentation
All field adjustments made during the commissioning process should be meticulously documented in both TAB and controls documentation. This dual documentation ensures consistency and provides a complete record for future reference.
Graphics Verification
A final critical step is verifying that system graphics accurately reflect the actual field conditions and configurations. Discrepancies between the graphical interface and physical reality can lead to significant operational problems after turnover.
www.JacksonControl.com
[email protected]
8. Coordination Gates: TAB ↔ Controls ↔ IT
#handshake #gates #witness #reports
Pre-Flight
Network Architecture Planning
Develop comprehensive network diagrams showing all control system components and their connections to the campus network infrastructure.
Security Requirements Definition
Identify and document all security requirements, including VLAN assignments, firewall rules, and certificate needs.
IT Department Sign-Off
Obtain formal sign-off from IT stakeholders on the network and security plans before proceeding with hardware procurement.
Equipment Installation
Proceed with device installation only after receiving confirmation that network infrastructure and security measures are in place.
Connection Verification
Verify that all devices can communicate properly according to the approved network plan before beginning system programming and configuration.
Best Practice: Create a formal handoff procedure between TAB and controls contractors that includes joint verification of critical values and setpoints. This collaborative approach prevents the finger-pointing that often occurs when issues arise during functional testing.
www.JacksonControl.com
[email protected]
9. Plan Seasonal & Integrated Testing Upfront
#seasonal #IST #smokecontrol #AHJ
Many building systems can only be fully tested under specific seasonal conditions, while others require careful coordination with life safety systems and regulatory authorities. Planning for these specialized testing requirements must occur early in the project to ensure proper scheduling, budgeting, and coordination.
Seasonal Testing Strategies
To effectively manage seasonal testing requirements:
Schedule seasonal windows at the project outset, identifying specific timeframes when heating, cooling, and shoulder-season testing can occur
Define simulation methods for situations where full-load conditions cannot be achieved naturally, including temporary heating/cooling equipment or software simulation approaches
Establish acceptance criteria that account for the limitations of simulated conditions while still verifying fundamental sequence operation
Budget for post-occupancy testing to ensure resources remain available after substantial completion
Document the plan in the OPR and Cx Plan to establish clear expectations with all project stakeholders
Campus tip: For chiller-season testing across multiple buildings, block calendar time and shared staffing resources during pre-construction to ensure availability when needed.
Failing to plan for integrated systems testing, particularly those involving life safety systems like smoke control, can lead to significant delays in occupancy approval and create potential regulatory compliance issues.
www.JacksonControl.com
[email protected]
9. Plan Seasonal & Integrated Testing Upfront
#seasonal #IST #smokecontrol #AHJ
Integrated Systems Testing (IST)
Life Safety Integration
Develop comprehensive testing plans for all building systems that interact with life safety functions, including:
Smoke control and smoke evacuation systems
Fire alarm integration with HVAC systems
Emergency power response sequences
Pressurization systems for stairwells and areas of refuge
Elevator recall and firefighter service operation
AHJ Coordination
Early engagement with the Authority Having Jurisdiction (AHJ) is essential to:
Understand specific testing requirements and expectations
Develop testing procedures that satisfy regulatory requirements
Schedule inspections with sufficient lead time
Address any unique building features that may require special consideration
Document testing plans and procedures for approval
Design Phase
Identify all systems requiring seasonal or integrated testing and document testing requirements in the commissioning plan
Construction Phase
Develop detailed test procedures, coordinate with AHJ, and ensure all prerequisites are in place
Pre-Occupancy
Conduct all feasible testing based on available conditions and simulation methods
Seasonal Verification
Return during appropriate seasonal conditions to verify full system performance under actual operating conditions
Documentation
Compile comprehensive documentation of all testing results for inclusion in final commissioning report
www.JacksonControl.com
[email protected]
10. Campus Realities to Design Around
#multivendor #legacy #badge #storage #deadlines #capacity #security #capexOpex #last5percent
Higher education institutions face unique challenges that must be acknowledged and accommodated in the commissioning process. These campus realities should be treated as design constraints rather than excuses for poor performance. Effective commissioning plans explicitly address these challenges to ensure successful implementation and long-term operation.
Staff Capacity Constraints
Facilities departments typically operate with limited staff resources, constraining their ability to participate in commissioning activities while maintaining ongoing operations. Training and turnover strategies must acknowledge these limitations and provide flexible options for knowledge transfer.
IT Security Reviews
Institutional IT security requirements have become increasingly stringent, often requiring extensive review and approval processes for network-connected systems. These reviews can introduce significant delays if not anticipated and incorporated into project schedules.
CapEx/O&M Budget Splits
The division between capital and operational budgets can create challenges for commissioning activities that span these financial categories, particularly for seasonal testing that occurs after project completion. Clear funding sources must be identified early for all commissioning activities.
The "Last 5% Never Done" Syndrome
Perhaps the most persistent challenge in higher education commissioning is the tendency for the final 5% of commissioning activities to remain incomplete as projects rush to meet occupancy deadlines. This phenomenon must be explicitly acknowledged and addressed through contractual requirements, financial holdbacks, and clear completion criteria.
www.JacksonControl.com
[email protected]
10. Campus Realities to Design Around
#multivendor #legacy #badge #storage #deadlines #capacity #security #capexOpex #last5percent
Multi-Vendor BAS Environments
Most campuses operate building automation systems from multiple vendors, often with limited integration capabilities. Commissioning must address how new systems will coexist with or connect to these legacy platforms, including naming conventions, graphics standards, and network considerations.
Legacy Naming and Standards
Established campuses typically have existing naming conventions and standards that new systems must adopt for consistency. These requirements may not align with contractor preferences but are essential for long-term maintainability and operational efficiency.
Badge and Access Limitations
Security considerations often limit contractor access to campus networks and facilities, which can complicate commissioning activities. Clear protocols for access management must be established early to prevent delays while maintaining appropriate security controls.
Limited Trend Storage Capacity
Many campus BAS servers have constraints on trend data storage that must be considered when specifying trending requirements for commissioning. Strategic approaches to data collection and storage are necessary to balance verification needs with system limitations.
Compressed Summer/Semester Timelines
Academic calendars create rigid deadlines for project completion and limit opportunities for disruptive testing. Commissioning schedules must align with these institutional constraints, often requiring creative approaches to testing and verification.
Adjacent Occupied Spaces
New construction often occurs near or connected to occupied facilities, limiting testing options that might impact existing operations. Commissioning plans must account for these adjacencies and develop testing approaches that minimize disruption.
www.JacksonControl.com
[email protected]
11. From Lessons to Standards (Institutionalizing What Works)
#standardization #QA #issueslog
The ultimate goal of any commissioning improvement effort is to institutionalize successful practices so they become standard operating procedure rather than exceptional efforts by motivated individuals. This section outlines strategies for converting the lessons learned from individual projects into campus-wide standards that deliver consistent results across your portfolio.
Standardize integration pathways
One of the clearest messages from our meetings was the value of standardizing on a single integration approach where possible. This simplification yields multiple benefits:
Reduced training burden – Staff only need to learn and maintain proficiency with one integration method
Fewer failure points – Each additional integration pathway introduces potential points of failure
Simplified troubleshooting – Consistent approaches make it easier to diagnose and resolve issues
Enhanced vendor accountability – Standard expectations are easier to enforce across multiple projects
Improved documentation – Consistency allows for more comprehensive and reusable documentation
Consider developing a campus standard for system integration that defines acceptable protocols, data exchange methods, and responsibilities for maintaining integration points. This standard should be referenced in all project documents and enforced through the design review and submittal approval processes.
www.JacksonControl.com
[email protected]
11. From Lessons to Standards (Institutionalizing What Works)
#standardization #QA #issueslog
Implement design QA tracking
Require Formal Comment Acknowledgement
Implement a requirement that consultants must formally acknowledge and respond to all commissioning and design review comments, explaining how each item will be addressed or why it cannot be accommodated.
Maintain a Comprehensive Issues Log
Track all identified issues from design reviews in a formal issues log that follows the project through completion, requiring documented resolution of each item before it can be closed.
Document Resolution Evidence
For each closed issue, require specific evidence demonstrating how the concern was addressed, whether through revised drawings, updated specifications, or other documented changes.
Track Resolution Metrics
Monitor and report on issue resolution rates, time to closure, and recurring issues to identify systemic problems and measure improvement over time.
This structured approach to design quality assurance can significantly reduce the number of issues that persist into construction and commissioning, preventing costly rework and schedule delays.
www.JacksonControl.com
[email protected]
11. From Lessons to Standards (Institutionalizing What Works)
#standardization #QA #issueslog
Keep governance lightweight but visible
RACI Table for Complaint Routing
Develop and publish a clear RACI (Responsible, Accountable, Consulted, Informed) matrix that defines roles and responsibilities for addressing building system issues during different project phases. This matrix should be particularly explicit about the handling of occupant complaints during the construction, commissioning, and warranty periods.
The RACI table should address questions such as:
Who receives initial occupant complaints during construction?
Who is responsible for investigating reported issues?
Who has authority to direct contractors to make corrections?
Who communicates status updates back to occupants?
When does responsibility transition from the project team to facilities?
Standard Commissionable Controls Package
Define a standard "commissionable controls package" that everyone in your organization recognizes. This package should establish the minimum requirements for controls documentation, testing, and verification that must be met on all projects regardless of size or complexity.
Key elements of this standard package should include:
Required submittal contents and format
Standard testing procedures and acceptance criteria
Trending requirements and data formats
Training expectations and deliverables
Documentation standards and deliverables
www.JacksonControl.com
[email protected]
11. From Lessons to Standards (Institutionalizing What Works)
#standardization #QA #issueslog
Continuous Improvement Cycle
Document Lessons
Capture specific issues, challenges, and successes from each project in a structured format that facilitates analysis and knowledge sharing.
Analyze Patterns
Regularly review documented lessons to identify recurring themes, common failure modes, and successful strategies across multiple projects.
Update Standards
Revise campus standards, specifications, and procedures to address identified issues and incorporate successful practices from individual projects.
Train Teams
Ensure all project teams understand updated standards and the rationale behind them through regular training and communication.
Implement on Projects
Apply updated standards and procedures on new projects, monitoring their effectiveness and identifying opportunities for further refinement.
By establishing this continuous improvement cycle, your institution can systematically elevate the quality and consistency of controls commissioning across your entire portfolio, leading to better-performing buildings, reduced operational issues, and more efficient use of resources.
www.JacksonControl.com
[email protected]
Appendices (Copy/Paste) Appendix A — IT Pre-Flight Packet (Owner Acceptance Gate)
#IT #network #ports #VLAN #NAC #time #certs #BACnetSC
The following document template provides a comprehensive structure for the IT Pre-Flight Packet that should be completed, reviewed, and signed off before any control system devices are installed. This packet serves as a formal owner acceptance gate to ensure all IT infrastructure requirements are properly addressed early in the project.
IT Pre-Flight Packet Template
PROJECT NAME: ________________________________
PROJECT NUMBER: ______________________________
DATE SUBMITTED: ______________________________
CONTROLS CONTRACTOR: _________________________
IT REPRESENTATIVE: ____________________________

== REQUIRED DOCUMENTATION CHECKLIST ==

□ Network diagram (with BACnet/IP routing)
□ Port/protocol matrix + firewall requirements
□ VLAN assignments and NAC policies
□ Time sync source/method
□ Certificate management plan
□ BACnet/SC readiness statement

== NETWORK DIAGRAM REQUIREMENTS ==

The network diagram must include:
1. All supervisory controllers with IP addresses
2. All field controllers/device networks
3. All BACnet/IP routing paths
4. Connections to campus networks
5. Firewalls and security boundaries
6. Required ports for each connection
7. Any cloud connections or remote access

www.JacksonControl.com
[email protected]
Appendices (Copy/Paste) Appendix A — IT Pre-Flight Packet (Owner Acceptance Gate)
#IT #network #ports #VLAN #NAC #time #certs #BACnetSC
== PORT/PROTOCOL MATRIX ==

| Source        | Destination   | Protocol | Port | Purpose            |
|---------------|---------------|----------|------|-------------------|
| [Example]     | [Example]     | [Ex]     | [Ex] | [Example]         |
| BAS Server    | Field Network | BACnet/IP| 47808| Device Communication|
| Remote Access | BAS Server    | HTTPS    | 443  | Secure Web Access  |
| [Add rows as needed for all required communication paths]

== VLAN ASSIGNMENTS AND NAC POLICIES ==

VLAN Name: ____________________________
VLAN Number: __________________________
Subnet: _______________________________
Default Gateway: _______________________
DHCP Range (if applicable): ____________
Static IP Range: _______________________
NAC Authentication Method: _____________
Device Registration Process: ___________

== TIME SYNCHRONIZATION ==

Primary Time Source: ___________________
Backup Time Source: ___________________
Synchronization Method: _______________
Synchronization Interval: _____________
Time Zone Configuration: ______________

== CERTIFICATE MANAGEMENT ==
Certificate Authority: ________________
Certificate Type: ____________________
Certificate Issuance Process: ________
Certificate Renewal Process: _________
Certificate Distribution Method: ______
www.JacksonControl.com
[email protected]
Appendices (Copy/Paste) Appendix A — IT Pre-Flight Packet (Owner Acceptance Gate)
#IT #network #ports #VLAN #NAC #time #certs #BACnetSC


== BACnet/SC READINESS ==

□ BACnet/SC will be implemented
□ BACnet/SC will NOT be implemented (explain): _______________________

If implementing BACnet/SC:
Hub Configuration: ___________________
Security Policies: ___________________
Key Management Approach: _____________
== APPROVALS ==
Controls Contractor Representative:
Name: ______________________________ 
Signature: _________________________ Date: __________

IT Department Representative:
Name: ______________________________ 
Signature: _________________________ Date: __________

Commissioning Provider:
Name: ______________________________ 
Signature: _________________________ Date: __________

Owner's Representative:
Name: ______________________________ 
Signature: _________________________ Date: __________
This document should be completed early in the construction process, ideally during the submittal phase, and must be approved before any network-connected control devices are installed. Modifications to the approved plan must be documented and require additional approval from all signatories.
www.JacksonControl.com
[email protected]
Appendix B — Commissionable Controls Submittal Checklist
#SOO #points #IO #alarms #trending #FPT
The following checklist provides a comprehensive framework for evaluating controls submittals to ensure they contain all information necessary for effective commissioning. This checklist can be provided to contractors at the beginning of the project to set clear expectations for submittal content and quality.
Submittal Requirements Checklist
Sequence of Operation (SOO)
Complete narrative description of all control sequences
Clearly identified operational modes (occupied, unoccupied, emergency, etc.)
All setpoints, deadbands, and operational parameters defined
Control loop descriptions including P/I/D parameters
Alignment with drawings and specifications verified
Integration with other systems clearly described
Reset schedules and adaptive strategies detailed
Points List & I/O Mapping
Comprehensive list of all physical and virtual points
Consistent naming convention following campus standards
Point type (AI, AO, DI, DO, virtual) clearly indicated
Engineering units specified for all analog points
Normal/alarm states defined for digital points
Controller assignments for all points
Network addressing and discovery information
Alarm Configuration
Alarm priority matrix with clearly defined levels
Routing instructions for each alarm priority
Alarm delay and debounce settings
Custom alarm messages for each condition
Alarm acknowledgment and reset procedures
Escalation protocols for unacknowledged alarms
Integration with campus-wide alarm management
Trending Configuration
List of all trended points by system
Sample rates for each trend (COV or time-based)
Trend storage duration requirements
Trend export formats and methods
Special trending requirements for commissioning
Buffer sizes and handling of trend data
Long-term trend storage and archiving strategy
Draft Functional Test Scripts
Test procedures for each major system and subsystem
Specific pass/fail criteria for each test step
Required trend data to verify performance
Test prerequisites and required conditions
Special tools or equipment needed for testing
Estimated duration for each test procedure
Roles and responsibilities during testing
www.JacksonControl.com
[email protected]
Appendix B — Commissionable Controls Submittal Checklist
#SOO #points #IO #alarms #trending #FPT
Additional Required Documentation
Graphics and User Interface
Sample graphics for each system type
Navigation structure and organization
User access levels and permissions
Custom dashboard configurations
Mobile/responsive interface details
Hardware Specifications
Controller specifications and capabilities
Field device cut sheets and options
Enclosure details and locations
Power requirements and backup provisions
Environmental operating parameters
Network and IT Requirements
Network infrastructure requirements
Cybersecurity features and configurations
Remote access capabilities and methods
Data backup and recovery procedures
Software licensing and version information
Incomplete control submittals are a leading cause of commissioning delays and performance issues. Review this checklist with contractors during the pre-construction meeting and make it clear that submittals missing these elements will be rejected. This upfront investment in quality documentation pays dividends throughout the project lifecycle.
www.JacksonControl.com
[email protected]
Appendix C — TAB–Controls Handshake SOP
#TAB #witness #authority #reports #graphics
The following Standard Operating Procedure (SOP) outlines the critical handshake process between Testing, Adjusting, and Balancing (TAB) and controls contractors. This coordinated approach ensures consistency between mechanical system performance and control system operation, preventing the common issues that arise when these disciplines operate in isolation.
Failure to properly coordinate TAB and controls activities is a leading cause of performance issues and commissioning delays. This handshake process is not optional—it is a critical component of successful system implementation.
TAB–Controls Coordination Procedure
01
Define Authority for Setpoints/Calibration
Prior to the start of TAB activities, establish and document clear authority for who will determine final setpoints, calibration values, and operational parameters where both TAB and controls have overlapping interests. This designation should be documented in the commissioning plan and acknowledged by all parties.
02
Commissioning Provider Witness Requirements
The Commissioning Provider (CxP) shall witness both control system start-up procedures and critical TAB activities to ensure proper coordination and verify that both systems are operating as intended. The specific activities requiring CxP presence should be identified in the commissioning plan and scheduled with adequate notice.
03
TAB Report as Gate to FPT
A completed and accepted TAB report shall serve as a formal gate that must be passed before Functional Performance Testing (FPT) can begin for the associated systems. This ensures that fundamental air and water balancing is complete and accurate before more complex sequence testing commences.
Field Adjustment Documentation
All field adjustments made during TAB and commissioning activities must be documented in both the TAB report and the controls documentation. This dual documentation ensures consistency and provides a complete record for future reference. Any discrepancies between the two records must be resolved before system acceptance.
Graphics Verification
A final critical step is verifying that system graphics accurately reflect the actual field conditions and configurations. The TAB contractor and controls contractor shall jointly verify that all setpoints, flow values, and system configurations shown in the BAS graphics match the actual field conditions as documented in the TAB report.
www.JacksonControl.com
[email protected]
Appendix C — TAB–Controls Handshake SOP
#TAB #witness #authority #reports #graphics
Coordination Checklist
www.JacksonControl.com
[email protected]
Appendix D — Acceptance-Criteria Matrix (Testable OPR)
#OPR #criteria #trends #intervals #duration
The following matrix template provides a framework for converting vague performance goals into measurable acceptance criteria with specific evidence requirements. This approach transforms the Owner's Project Requirements (OPR) from a conceptual document into a practical testing tool that enables objective verification of system performance.
Acceptance Criteria Matrix Template
www.JacksonControl.com
[email protected]
Appendix D — Acceptance-Criteria Matrix (Testable OPR)
#OPR #criteria #trends #intervals #duration
Extended Acceptance Criteria Examples
Demand-Controlled Ventilation
Criterion: Modulate outdoor air damper to maintain CO₂ levels below 900 ppm during occupied hours
Test Condition: Normal occupancy with varying CO₂ levels
Pass/Fail: CO₂ levels remain below setpoint; damper position responds appropriately to changing CO₂ levels
Evidence: 1-week trend data showing CO₂ levels and damper position at 15-minute intervals
Zone Temperature Control
Criterion: Maintain zone temperature within ±1.5°F of setpoint during occupied hours
Test Condition: Normal occupied operation with typical internal loads
Pass/Fail: Zone temperature remains within tolerance for 95% of occupied hours
Evidence: 1-week trend data for representative zones at 10-minute intervals
Chiller Staging
Criterion: Stage chillers based on load to maintain optimal efficiency
Test Condition: Varying cooling load conditions
Pass/Fail: Chillers stage properly based on specified load thresholds; no hunting or rapid cycling
Evidence: Trend data showing chiller status, load percentage, and system flow at 5-minute intervals during load transitions
Implementation Guidelines
Developing Acceptance Criteria
Start with the OPR and identify key performance requirements
Translate each requirement into specific, measurable criteria
Define clear conditions under which each criterion should be tested
Establish objective pass/fail thresholds
Specify the evidence required to demonstrate compliance
Review criteria with design team and operations staff
Using the Matrix During Commissioning
Include the matrix in the commissioning plan
Reference specific criteria in functional test procedures
Configure trending to collect the required evidence
Document compliance with each criterion
Address any criteria that cannot be met
Include the completed matrix in the final commissioning report
This acceptance criteria matrix should be developed during the design phase and refined as the project progresses. It serves as a concrete expression of the owner's requirements and provides a clear framework for testing and verification.
www.JacksonControl.com
[email protected]
Appendix E — Spec Clause Library (Drop-In, Vendor-Neutral)
#spec #OPR #submittals #IT #TAB #IST
The following specification clauses can be dropped into project documents to establish clear requirements for controls commissioning. These vendor-neutral clauses address the key areas identified as common failure points in the commissioning process. Each clause can be customized to fit specific project requirements while maintaining the core principles that drive successful outcomes.
Testable Owner's Project Requirements (OPR)
Performance criteria shall be expressed as measurable setpoints, tolerances, and modes tied to BAS points. Acceptance requires trend exports demonstrating criteria over defined conditions. Vague requirements such as 'energy efficient operation' or 'occupant comfort' must be translated into specific, measurable parameters with clear acceptance thresholds. The OPR shall include a matrix of acceptance criteria that defines the specific evidence required to verify each performance requirement.
Commissionable Controls Submittal
Controls contractor shall submit sequence of operation (SOO) aligned to drawings/specifications, complete points list with I/O mapping, alarm priority matrix with response protocols, minimum trend plan specifying points, intervals, and duration, and draft functional performance test (FPT) scripts with pass/fail criteria. Submittals missing any of these elements will be rejected as incomplete. The controls submittal must be approved before any control system hardware is ordered or installed.
IT Pre-Flight Requirements
Provide network diagram showing all controllers and communication paths, port/protocol matrix detailing all required network communications, time synchronization source and method, VLAN/NAC requirements, certificate management plan, and BACnet/SC readiness statement. Obtain owner IT department sign-off on this complete package before any device installation. Any changes to the approved IT configuration must be documented and resubmitted for approval before implementation.
www.JacksonControl.com
[email protected]
Appendix E — Spec Clause Library (Drop-In, Vendor-Neutral)
#spec #OPR #submittals #IT #TAB #IST
TAB–Controls Coordination
Identify clear authority for setpoints, valve positions, and calibration values where TAB and controls responsibilities overlap. The Commissioning Provider shall witness both control system start-up and TAB procedures to ensure coordination. Functional performance testing shall commence only upon acceptance of the final TAB report for each system. All field adjustments shall be documented in both TAB and controls documentation. Graphics shall be verified to accurately reflect field conditions before system acceptance.
Seasonal and Integrated Systems Testing
Include placeholder schedule and method for seasonal testing when full-load conditions cannot be achieved at the time of initial commissioning. Provide detailed integrated systems test plan for all life-safety interactions (e.g., smoke control, emergency power response) and coordinate testing procedures with the Authority Having Jurisdiction (AHJ). Budget and planning documents shall include provisions for commissioning activities that extend beyond substantial completion to verify seasonal performance.
Trending Requirements for Commissioning
Configure trend logs for all points necessary to verify sequences of operation and performance criteria. Trend data shall be collected at intervals appropriate to the system dynamics (typically 5-15 minutes for most HVAC applications) and for durations sufficient to demonstrate stable operation (minimum 24 hours for basic functions, up to one week for weather-dependent functions). Trend data shall be provided in a format that allows for analysis by the commissioning team and shall be included in the final commissioning documentation.
www.JacksonControl.com
[email protected]
Appendix E — Spec Clause Library (Drop-In, Vendor-Neutral)
#spec #OPR #submittals #IT #TAB #IST
Training and Knowledge Transfer
Provide comprehensive training on control system operation, maintenance, and troubleshooting. Training shall include hands-on sessions with the actual installed systems, recorded video documentation for future reference, detailed system manuals, and checklists for common operational tasks. Training shall be provided in multiple sessions to accommodate different staff schedules and shall include follow-up sessions after the system has been in operation for at least 30 days to address questions that arise during initial operation.
Controls System Documentation
Provide complete as-built documentation including updated sequences of operation, point lists, network diagrams, programming code (where applicable), and user interface screenshots. Documentation shall be provided in both electronic and printed formats, organized in a logical manner that facilitates troubleshooting and maintenance. Electronic documentation shall be provided in non-proprietary formats (PDF, Excel, etc.) that do not require special software to access.
These specification clauses can be incorporated into Division 23, 25, or 01 91 13 (Commissioning) as appropriate for your project structure. Customize the language to align with your institution's terminology and standards while maintaining the core requirements.
www.JacksonControl.com
[email protected]
Appendix F — Workshop Worksheet (5-Minute Team Exercise)
#exercise #hindsight #evidence #tests #coordination
This worksheet is designed to facilitate a quick team exercise that converts lessons from past projects into actionable improvements for future commissioning efforts. The exercise typically takes about 5 minutes per failure mode discussed and can be conducted during project kickoff meetings or commissioning planning sessions.
Instructions
Think about a recent controls commissioning challenge or failure that impacted project completion or building performance. Use this worksheet to break down what went wrong and develop specific strategies to prevent similar issues in the future.
Step 1: Briefly describe the issue
System/Project: _______________________________________

What happened: _______________________________________
_____________________________________________________
_____________________________________________________

When in the project it occurred: _______________________

Impact on schedule/performance: _______________________
_____________________________________________________
This exercise is most effective when conducted with a diverse team including facilities staff, project managers, designers, and contractors. The different perspectives help identify comprehensive solutions.
www.JacksonControl.com
[email protected]
Appendix F — Workshop Worksheet (5-Minute Team Exercise)
#exercise #hindsight #evidence #tests #coordination
Step 2: Convert hindsight into actionable improvements
Evidence Gap Analysis
What data should we have captured to identify or prevent this issue?
Which specific points should have been trended? ________________________________
What trend interval would have revealed the problem? ___________________________
What visualization would have helped identify the issue? ________________________
What threshold should have triggered an alert? _________________________________
Proposed evidence requirement for future projects:
_____________________________________________________
_____________________________________________________
Testing Improvement
What specific acceptance test would have caught this issue before it impacted the project?
Test conditions needed: ___________________________________________________
Specific pass/fail criteria: ________________________________________________
Required duration or repetitions: ___________________________________________
Sequence step or mode to verify: ___________________________________________
Proposed test procedure addition for future projects:
_____________________________________________________
_____________________________________________________
www.JacksonControl.com
[email protected]
Appendix F — Workshop Worksheet (5-Minute Team Exercise)
#exercise #hindsight #evidence #tests #coordination
Step 2: Convert hindsight into actionable improvements
Earlier Coordination
What coordination step should have happened earlier in the process?
Which stakeholders needed to be involved? ____________________________________
What specific information was missing? _______________________________________
What approvals or sign-offs were needed? ____________________________________
When in the project should this have occurred? ________________________________
Proposed coordination gate for future projects:
_____________________________________________________
_____________________________________________________
Specification or Contract Improvement
What language should be added to project documents to prevent recurrence?
Which specification section needs enhancement? _______________________________
What specific requirement should be added? __________________________________
How will compliance be verified? ____________________________________________
What consequences should apply for non-compliance? __________________________
Proposed specification language for future projects:
_____________________________________________________
_____________________________________________________
www.JacksonControl.com
[email protected]
Appendix F — Workshop Worksheet (5-Minute Team Exercise)
#exercise #hindsight #evidence #tests #coordination
Step 2: Convert hindsight into actionable improvements
Step 3: Implementation Plan
www.JacksonControl.com
[email protected]
Appendix G — Glossary of Terms and Acronyms
www.JacksonControl.com
[email protected]
Appendix G — Glossary of Terms and Acronyms
www.JacksonControl.com
[email protected]
Appendix G — Glossary of Terms and Acronyms
www.JacksonControl.com
[email protected]
Appendix G — Glossary of Terms and Acronyms
www.JacksonControl.com
[email protected]
Appendix G — Glossary of Terms and Acronyms
www.JacksonControl.com
[email protected]
Appendix G — Glossary of Terms and Acronyms
www.JacksonControl.com
[email protected]
Appendix H — Helpful Links 
www.JacksonControl.com
[email protected]
Appendix H — Helpful Links and Information
www.JacksonControl.com
[email protected]