**Akcel System Inc.**

**Building Automation System Field Reference**

**Version:** 1.0 | **Date:** December 2025

---

Welcome to the heart of our system-level logic and control strategies. This library contains comprehensive Sequence of Operations (SOO) documents for common Building Automation System applications and equipment. Unlike our SSO library which focuses on individual device installation and proof-out, these SOO documents detail the *how* and *why* of an entire system's operation, control logic, interlocks, and performance verification.

Each SOO is designed for **field engineers, programmers, and commissioning specialists** and includes:

- System overview and design intent

- Detailed control sequences (start-up, normal operation, shutdown, economizer, etc.)

- Points list with typical naming conventions

- Operating parameters and setpoints

- Interlocks and safety protocols

- System proof-out and commissioning procedures

- Troubleshooting common operational issues

- Performance optimization strategies

**Format:** Comprehensive, logical flow, application-focused

**Target Users:** Field Specialists, Programmers, Project Managers, Commissioning Agents

---

---

- Key components: Supply Fan VFD, OA/RA/EA dampers, heating coil valve, cooling coil valve.

---

- Key components: VAV damper actuator, reheat coil, occupancy sensor integration.

---

---

---

- `SOO-[SystemType]-[Descriptor].md`

- Example: `SOO-AirHandlingUnit-VAV.md` or `SOO-ChillerPlant-PrimarySecondary.md`

- Each document includes version number and date

- Major revisions increment version (1.0 → 2.0)

- Minor updates increment decimal (1.0 → 1.1)

- Review cycle: Annual or as needed, especially after significant project implementations.

- **Mobile Access:** Available for field reference.

- **Offline Access:** Download all SOOs for offline field use.

- **Search:** Full-text search available in digital library.

- **Updates:** Subscribe to notifications for document updates.

---

1. Review the relevant SOO *before* commissioning a system.

2. Understand the control logic and expected system behavior.

3. Utilize the **System Proof-out and Commissioning Procedures** for thorough verification.

4. Reference **Troubleshooting** for operational discrepancies.

1. Use SOOs as the definitive guide for developing and implementing control logic.

2. Ensure your code precisely matches the specified sequences, points lists, and interlocks.

3. Reference **Operating Parameters and Setpoints** for configuration.

1. Leverage SOOs for project scope definition and client expectation setting.

2. Ensure that system design and implementation align with documented sequences.

3. Use for quality control and verification during project handover.

1. Study SOOs to gain a deeper understanding of integrated system control.

2. Connect individual device functions (from SSOs) to overall system operation.

---

- **Errors or Omissions:** Submit via Service Fusion ticket to Technical Training.

- **Suggested Improvements:** Email [training@example.com].

- **New System Requests:** Request SOO for systems not in library.

1. Field feedback collected quarterly.

2. Technical review by senior specialists.

3. Updates approved by Technical Lead.

4. New version published and distributed.

5. Notification sent to all relevant staff.

---

⚠️ **CRITICAL SAFETY REMINDERS**

- **Always prioritize safety**: These documents detail operational sequences, but always adhere to all safety protocols, Lockout/Tagout procedures, and company policies.

- **Verify all interlocks**: Ensure all safety interlocks are functioning correctly before initiating system operation.

- **Qualified personnel**: Only qualified personnel should perform work on operational systems.

- **When in doubt, ask**: Never proceed if unsure about a system's behavior or safety implications.

---

- ASHRAE Guideline 36: High-Performance Sequences of Operation for HVAC Systems

- Manufacturer control specifications for specific equipment

- Local building codes and energy efficiency regulations

- **Technical Training:** [Phone/Email]

- **Safety Manager:** [Phone/Email]

- **Dispatch Coordinator:** [Phone]

- **After-Hours Emergency:** [Phone]

---

**Document Owner:** Technical Training Department

**Last Updated:** December 2025

**Next Review:** March 2026

**Feedback:** training@example.com

---