How do I ensure my lighting and irrigation scheduling with a setpoint management system is compliant?

To ensure your lighting and irrigation scheduling with a setpoint management system is compliant, you need to align the system settings, automation logic, and records with the specific code, standard, or program you’re being audited against.

Here’s a practical checklist:

1. Identify the compliance basis

Confirm which requirements apply, for example:

• Local building and energy codes
• Utility rebate/program rules
• Environmental / water-use regulations
• Food safety, greenhouse, or controlled-environment agriculture standards
• Internal SOPs or certification requirements

2. Define allowed setpoint ranges

Document approved ranges for:

• Lighting
  • On/off times
  • Dimming limits
  • Photoperiod duration
  • Daylight harvesting behavior, if used
• Irrigation
  • Start/stop windows
  • Moisture or ET-based triggers
  • Maximum runtime per zone
  • Minimum/maximum frequency

Make sure these values match the governing requirement and are locked or permission-controlled where possible.

3. Use schedule overrides carefully

If the system allows manual overrides:

• Restrict who can change schedules
• Require approval for temporary changes
• Set automatic expiration for overrides
• Log who changed what, when, and why

4. Maintain audit trails

Keep records of:

• Schedule settings
• Setpoint changes
• Sensor inputs used for automation
• Alarm events and failures
• Manual overrides and corrections

Auditors usually want to see that the system is controlled and traceable.

5. Verify sensor calibration and control logic

For compliance, the system must be working as intended:

• Calibrate light sensors, soil moisture sensors, flow meters, and timers
• Test logic for daylight compensation, rain shutoff, leak detection, and interlocks
• Validate that the system does not exceed permitted watering or lighting thresholds

6. Establish fail-safe behavior

Define what happens if:

• Sensors fail
• Network connection is lost
• Power is interrupted
• A controller reboots

Compliance often requires the system to default to a safe mode rather than uncontrolled operation.

7. Document commissioning and periodic review

Prepare and retain:

• Commissioning reports
• Functional test results
• Periodic inspection logs
• Recalibration records
• Change-management approvals

8. Coordinate with the manufacturer or integrator

Ask for:

• Compliance documentation
• Control sequence narratives
• Point lists and setpoint schedules
• Software version history
• Any certifications or testing reports

9. Train operators

Operators should know:

• Which settings are locked
• What counts as an allowed override
• How to respond to alarms
• How to record exceptions properly

10. Get a formal review if stakes are high

If this is tied to a permit, certification, or rebate:

• Have a qualified engineer, consultant, or compliance officer review the setup
• Get written confirmation before final deployment if possible

If you want, I can also help you turn this into a compliance checklist or a sample SOP for lighting and irrigation setpoint management.